ARIB STD-T64-C.S0017-0

Transcription

1 ARIB STD-T-C.S00-0 Data Service Options for Spread Spectrum Systems Refer to "Industrial Property Rights (IPR)" in the preface of ARIB STD-T for Related Industrial Property Rights. Refer to "Notice" in the preface of ARIB STD-T for Copyrights.

2 TIA/EIA INTERIM STANDARD TIA/EIA/IS-0-A Data Service Options for Wideband Spread Spectrum Systems TIA/EIA/IS-0-A (Revision of TIA/EIA/IS-0) APRIL TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the telecommunications industry in association with the Electronic Industries Alliance

3 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 products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of TIA/EIA from manufacturing or selling products not conforming 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 the standard is to be used either domestically or internationally. Standards and Publications are adopted by TIA/EIA in accordance with the American National Standards 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 information deemed to be of technical 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 a procedural part of the development of a TIA/EIA Standard. TIA/EIA Interim Standards should be reviewed on an annual basis by the formulating Committee and a decision made on whether to proceed to develop a TIA/EIA Standard on this subject. TIA/EIA Interim 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 TIA/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 months from the date of publication. It is expected that following this 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 directed to: Standards & Technology Department, Telecommunications Industry Association, 00 Wilson Boulevard, Arlington, VA 0. (From Project No., formulated under the cognizance of the TIA TR-. Subcommittee on Spread Spectrum Digital Technology.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards & Technology Department 00 Wilson Boulevard Arlington, VA 0 PRICE: Please refer to current Catalog of EIA ELECTRONIC INDUSTRIES ALLIANCE STANDARDS and ENGINEERING PUBLICATIONS or call Global Engineering Documents, USA and Canada (-00--) International (0--) All rights reserved Printed in U.S.A.

4

5 TIA/EIA/IS-0-A. 0 0 CONTENTS INTRODUCTION AND SERVICE GUIDE...-. General Description...-. Revision History...-. Terms...-. References Informative References Normative References...-. Stylistic Conventions...- NETWORK REFERENCE MODEL...-. Simplified Network Reference Model...-. Network Entities...-. Reference Points...- CDMA DATA SERVICES...-. Service Options For Data Services Service Option Format Assigned Service Options...-. Async and Fax Services Service Revision Guide...-. Packet Data Bearer Service Service Revision Guide...-. STU-III Service Service Revision Guide...-. Analog Fax Service Service Revision Guide...-. High Speed Packet Data Bearer Service Service Revision Guide...- INTERSYSTEM SUPPORT...-. Protocol Architecture...-. Intersystem Requirements...- i

6 TIA/EIA/IS-0-A. FIGURES Figure.-. Simplified Network Reference Model for CDMA Data Services...- Figure..-. Service Option Format...- Figure.-. Intersystem Protocol Architecture TABLES Table..-. Service Options for CDMA Data Services...- Table..-. Async Service Revision Guide...- Table..-. Fax Service Revision Guide...- Table..-. Packet Data Bearer Service Revision Guide...- Table..-. Secure Traffic Bearer Service Revision Guide...- Table..-. Analog Fax Service Revision Guide...- Table..-. High Speed Packet Data Bearer Service Revision Guide...- ii

7 TIA/EIA/IS-0-A. INTRODUCTION AND SERVICE GUIDE. General Description This standard describes data services available on spread spectrum systems. It is organized into a series of related recommendations, some of which address functions common to all CDMA data services, and others which describe a specific data service. The recommendations included in this series are: 0 0 IS-0-A. IS-0-A. IS-0-A. IS-0-A. IS-0-A. IS-0-A. IS-0-A. IS-0-A. IS-0-A. Data Service Options for Spread Spectrum Systems: Introduction and Service Guide Data Service Options for Spread Spectrum Systems: Radio Link Protocol Data Service Options for Spread Spectrum Systems: AT Command Processing and the R m Interface Data Service Options for Spread Spectrum Systems: Async Data and Fax Services Data Service Options for Spread Spectrum Systems: Packet Data Services Data Service Options for Spread Spectrum Systems: STU-III Services Data Service Options for Spread Spectrum Systems: Analog Fax Service Data Service Options for Spread Spectrum Systems: Radio Link Protocol Type Data Service Options for Spread Spectrum Systems: High Speed Packet Data Services 0 A recommendation may be referred to by its Interim Standard (IS) designation (e.g., IS-0- A.) or by its relative chapter number (e.g., Chapter means IS-0-A., Chapter means IS-0-A., etc.). This chapter provides an overview of the document s content, describes the simplified network reference model applicable to data services, introduces the data services, and discusses intersystem support for data services. Chapter defines the Radio Link Protocol used by some data services to transport octets between the mobile station (MS) and BS/MSC. Chapter is concerned with AT Command processing and the R m interface. Chapter defines asynchronous (hereafter called async) data service and Group- facsimile (hereafter called fax) service. Chapter details a packet data bearer service compatible with many packet data networks. Chapter describes a service that carries secure communications from U.S. Government digital STU-III terminals. Chapter details how service is provided to analog fax machines connected to a spread spectrum system. Chapter defines Radio Link Protocol Type that uses the services defined in TIA/EIA--B to allow increased transmission speeds. Chapter describes a packet data -

8 TIA/EIA/IS-0-A bearer service that provides higher rates (greater than the rates possible using chapter ) by using RLP Type and other services defined in TIA/EIA--B. The following verbal forms are used throughout all chapters. Shall and shall not identify requirements to be followed strictly to conform to the standard and from which no deviation is permitted. Should and should not indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others; that a certain course of action is preferred but not necessarily required; or that (in the negative form) that a certain possibility or course of action is discouraged but not prohibited. May and may not indicate a course of action permissible within the limits of the standard. Can and cannot are used for statements of possibility and capability, whether material, physical, or causal.. Revision History Revision A includes corrections in chapters and. In addition, it supports the following new capabilities: Chapter contains procedures to support multiple user data encryption modes. Chapter contains support for procedures supporting service switching as described in chapter. Chapter contains procedures to support service switching from a service option other than async data or fax to an async data or fax service option. Chapter contains support for packet zone reconnection control. Chapters,, and are new.. Terms Each chapter contains a section defining the terms used in the chapter. The following defines terms used in this chapter. AT Command. Any of the commands in the command set interface between data terminal equipment (DTE) and data circuit terminating equipment (DCE). Base Station (BS). A station that provides the means for MSs to access network services using radio. BS/MSC. The base station and mobile switching center considered as a single functional entity. IWF. An interworking function provides information conversion. A data service IWF provides functions needed for a mobile station to communicate with data terminal equipment connected to the network. Mobile Switching Center (MSC). The MSC switches MS originated or MS terminated traffic. An MSC is usually connected to at least one BS. It may connect to the other public networks (PSTN, ISDN, etc.), other MSCs in the same network, or MSCs in different networks. Mobile Station (MS). A wireless terminal used by subscribers to access network services over a radio interface. MSs include portable units (e.g., hand-helds), units installed in -

9 TIA/EIA/IS-0-A. 0 vehicles, and somewhat paradoxically, fixed location MSs. The MS is the interface equipment used to terminate the radio path at the subscriber. Mobile Termination 0 (MT0). A self-contained data capable mobile termination that does not support an external interface. Mobile Termination (MT). A mobile termination that provides a non-isdn (R m ) user interface (e.g., CCITT V series or CCITT X series). Terminal Equipment (TE). A data terminal that provides a non-isdn (R m ) usernetwork interface (e.g., CCITT V series or CCITT X series).. References In this standard, any reference to a procedure defined in another standard will cite the earliest version of the referenced standard in which the procedure is defined. Each chapter contains a references section which identifies the documents referenced in the chapter. The following applies to this chapter... Informative References The following references do not contain provisions of this standard. At the time of publication, the editions indicated were valid. ANSI/TIA/EIA- Inband DCE Control for Asynchronous DTE DCE Interfaces. TIA/EIA/IS--A MSC-BS Interface for Public Wireless Communications Systems,. 0 TIA/EIA/IS- Data Services Interworking Function Interface for Wideband Spread Spectrum Systems,. TIA/EIA/IS- Intersystem Link Protocol (ISLP),. TIA/EIA/IS- Intersystem Operations Support for Data Services,. TSB00 TR- Wireless Network Reference Model... Normative References The following references contain provisions which, through reference in this text, constitute provisions of this standard. 0 TIA/EIA--B TIA/EIA/IS- TIA/EIA/IS- TSB Mobile Station-Base Station Compatibility Standard for Dual-Mode Spread Spectrum System. Data Services Option Standard for Wideband Spread Spectrum Digital Cellular System,. Packet Data Service Options for Wideband Spread Spectrum Systems,. Administration of Parameter Value Assignments for TIA/EIA Spread Spectrum Standards. -

10 TIA/EIA/IS-0-A. 0. Stylistic Conventions Subcommittee TIA TR-. has developed and enhanced this standard over a number of years, using multiple versions of word processing tools and guidelines. Because of this, there may be stylistic inconsistencies between some of the chapters in the standard. In particular, in TIA/EIA/IS-0-A, the editor has used the automatic table and figure numbering capabilities of the word processing software in the new chapters. This allows automatic update of references to those tables and figures without manual intervention. The editor has also used the ability of the word processing software to automatically begin a major section on an odd page. This may cause the word processing software to produce a blank page before the major section, when the previous section s text ends on an odd page. However, it allows text insertion and deletion without requiring corresponding manual insertion or deletion of manually produced blank pages preceding a major section. -

11 TIA/EIA/IS-0-A. NETWORK REFERENCE MODEL. Simplified Network Reference Model The simplified network reference model shown in Figure.- applies to all CDMA data services described herein. See the TR- Wireless Network Reference Model for a more complete model. MS MT0 Um BS/MSC x IWF TE Rm MT Key Specific Network Entity Col lective (Composi te E ntity) N Interface Reference Point Figure.-. Simplified Network Reference Model for CDMA Data Services 0 In general, an MS may be implemented as an MT0 or MT/TE pair. Where this standard differs for the two implementations, the standard uses the terms MT0 and MT. Otherwise, the standard refers to either an MS or a mobile station.. Network Entities The only network entity that is by definition a physical device is the MS. Each of the others may be a physical device, it may form part of a physical device, or it may be distributed over a number of physical devices. 0 BS/MSC Interworking Function (IWF) The base station and mobile switching center considered as a single functional entity. See base station and mobile switching center. An interworking function provides information conversion for one or more network entities. It may have an interface to a single network entity, providing -

12 TIA/EIA/IS-0-A. 0 0 Mobile Station (MS) Mobile Switching Center (MSC). Reference Points Reference Point U m Reference Point x services to that entity, or it may have interfaces to each of two network entities that interface to each other, providing services to both. A wireless terminal used by subscribers to access network services over a radio interface. MSs include portable units (e.g., hand-helds), units installed in vehicles, and somewhat paradoxically, fixed location MSs. The MS is the interface equipment used to terminate the radio path at the subscriber. The MSC switches MS originated or MS terminated traffic. An MSC is usually connected to at least one BS. It may connect to the other public networks (PSTN, ISDN, etc.), other MSCs in the same network, or MSCs in different networks. Reference point U m is the interface between the base station and the mobile station, which corresponds to the air interface. Reference point x represents any of a number of interfaces between an interworking function (IWF) and network entity. The following lists interface specifications which support CDMA data services. TIA/EIA/IS- TIA/EIA/IS--A Data Services Interworking Function Interface for Wideband Spread Spectrum Systems MSC-BS Interface for Public Wireless Communications Systems -

13 TIA/EIA/IS-0-A. 0 CDMA DATA SERVICES. Service Options For Data Services.. Service Option Format CDMA data services are identified by Service Options. A Service Option is composed of three fields, the Proprietary Indicator, the Service Option Revision, and the Base Service Option Number (see TSB), as shown in Figure..-. The base data service (e.g., fax) is identified by the Base Service Option Number. The data service feature set is identified by the Service Option Revision. The first feature set for any base data service is assigned Service Option Revision 0, the next is assigned Service Option Revision, and so on, up to Service Option Revision. Proprietary Indicator Service Option Service Option Revision Base Service Option Number bit bits bits.. Assigned Service Options Figure..-. Service Option Format Table..- lists the Service Options used by CDMA data services. -

14 TIA/EIA/IS-0-A. Table..-. Service Options for CDMA Data Services CDMA data service Service Option Base Service Option Number Service Option Revision Oldest Defining Document 0 TIA/EIA/IS- async fax packet data bearer STU-III analog fax high speed packet data bearer 00 TIA/EIA/IS-0. 0 TIA/EIA/IS-0. 0 TIA/EIA/IS- 0 TAI/EIA/IS-0. 0 TIA/EIA/IS-0. 0 TIA/EIA/IS- 0 TIA/EIA/IS-0. 0 TIA/EIA/IS- 0 TIA/EIA/IS-0. 0 TIA/EIA/IS-0. 0 TIA/EIA/IS TIA/EIA/IS-0. 0 TIA/EIA/IS TIA/EIA/IS-0-A. 0 TIA/EIA/IS-0-A. 0 TIA/EIA/IS-0-A. 0 TIA/EIA/IS-0-A. 0 TIA/EIA/IS-0-A. 0 TIA/EIA/IS-0-A. 0 TIA/EIA/IS-0-A. 0 TIA/EIA/IS-0-A. 0 TIA/EIA/IS-0-A. 0 TIA/EIA/IS-0-A.. Async and Fax Services Base Service Option Numbers,,, and provide a modem emulation service for async and fax applications. Base Service Option Numbers and support async applications. Base Service Option Numbers and support fax applications. Chapter presents the procedures and requirements for these services. -

15 TIA/EIA/IS-0-A... Service Revision Guide Table..- provides a guide for the various async service revisions. Table..- provides a guide for the various fax service revisions. Table..-. Async Service Revision Guide Base Service Option Number Service Option Revision Companion IS-0 Chapters 0 None Y n Y n Y n y y n M P X M P X R S R S P R I S E C S I G S O N S N Notes, Y y Y y Y y n y y, 0, y Y y Y Y y n n y Table..-. Fax Service Revision Guide Base Service Option Number Service Option Revision Companion IS-0 Chapters 0 None Y n Y n Y n y y n M P X M P X R S R S P R I S E C S I G S O N S N Notes, Y y Y y Y n n y y, 0, y Y y Y Y n n n y 0 0 Notes. Speaker on operation using signaling traffic to carry RLP frames is no longer allowed. Instead, RLP frames are carried as secondary traffic during the time that voice service uses primary traffic.. Handling of multi-line responses that are carried using ANSI/TIA/EIA- has been clarified. Examples illustrating the handling of multi-line responses when using AT command reflection are included in Chapter, Appendix A. Legend MPX Multiplex Option MPX Multiplex Option RS Rate Set (00, 00, 00, 00) RS Rate Set (00, 00, 00, 00) PRI Primary Traffic SEC Secondary Traffic SIG Signaling Traffic SN Service Negotiation SON Service Option Negotiation y Attribute supported n Attribute not supported -

16 TIA/EIA/IS-0-A. Y Attribute supported and the default -

17 TIA/EIA/IS-0-A.. Packet Data Bearer Service Base Service Option Numbers,,, and provide a packet data bearer service compatible with many packet data networks. Base Service Option Numbers and support Internet Protocol (IP) and Connectionless Network Protocol (CLNP) networks. Base Service Option Numbers and support the Cellular Digital Packet Data (CDPD) network. Chapter presents the procedures and requirements for these services... Service Revision Guide Table..- provides a guide for the various packet data bearer service revisions. 0 Table..-. Packet Data Bearer Service Revision Guide Base Service Option Number Service Option Revision Companion IS-0 Chapters, 0 None Y n Y n Y n n y n M P X M P X R S R S P R I S E C S I G S O N S N Notes,, Y y Y y Y y n y y,,, 0, y Y y Y Y y n n y 0 Notes. Includes optional zone-based reconnection and optional BS control of a packet data dormant timer.. Established the packet data service type concept.. Packet data inactivity timer mandatory within MS with a minimum value of 0 seconds. Legend MPX Multiplex Option MPX Multiplex Option RS Rate Set (00, 00, 00, 00) RS Rate Set (00, 00, 00, 00) PRI Primary Traffic SEC Secondary Traffic SIG Signaling Traffic SN Service Negotiation SON Service Option Negotiation y Attribute supported n Attribute not supported Y Attribute supported and the default 0 -

18 TIA/EIA/IS-0-A.. STU-III Service Base Service Option Numbers 0 and provide a secure traffic bearer service for digital U.S. Government STU-III terminals. Chapter presents the procedures and requirements for these services... Service Revision Guide Table..- provides a guide for the various secure traffic bearer service revisions. Table..-. Secure Traffic Bearer Service Revision Guide Base Service Option Number Service Option Revision Companion IS-0 Chapters 0 0, Y y Y y Y n n n y 0, Y y Y y Y n n n y M P X M P X R S R S P R I S E C S I G S O N S N Notes Notes 0 0 Legend MPX Multiplex Option MPX Multiplex Option RS Rate Set (00, 00, 00, 00) RS Rate Set (00, 00, 00, 00) PRI Primary Traffic SEC Secondary Traffic SIG Signaling Traffic SN Service Negotiation SON Service Option Negotiation y Attribute supported n Attribute not supported Y Attribute supported and the default. Analog Fax Service Base Service Option Numbers 0 and provide a fax service that allows connection of an analog fax machine to a spread spectrum system. Chapter presents the procedures and requirements for this service... Service Revision Guide Table..- provides a guide for the various analog fax service revisions. 0 -

19 TIA/EIA/IS-0-A. Table..-. Analog Fax Service Revision Guide Base Service Option Number Service Option Revision Companion IS-0 Chapters 0 0, Y y Y y Y n n n y 0, y Y y Y Y n n n y M P X M P X R S R S P R I S E C S I G S O N S N Notes Notes 0 0 Legend MPX Multiplex Option MPX Multiplex Option RS Rate Set (00, 00, 00, 00) RS Rate Set (00, 00, 00, 00) PRI Primary Traffic SEC Secondary Traffic SIG Signaling Traffic SN Service Negotiation SON Service Option Negotiation y Attribute supported n Attribute not supported Y Attribute supported and the default. High Speed Packet Data Bearer Service Base Service Option Numbers through provide a packet data bearer service compatible with many packet data networks. Base Service Option Numbers through support Internet Protocol (IP) and Connectionless Network Protocol (CLNP) networks. Base Service Option Numbers through support the Cellular Digital Packet Data (CDPD) network. Chapter presents the procedures and requirements for these services... Service Revision Guide Table..- provides a guide for the various high speed packet data bearer service revisions. -

20 TIA/EIA/IS-0-A. Table..-. High Speed Packet Data Bearer Service Revision Guide Base Service Option Number Service Option Revision Companion IS-0 Chapters MPX F MPX R RS RS, 0, F,R n Y y n n y, 0, F R Y y n n y, 0, R F Y y n n y, 0, n F,R Y y n n y P R I S E C S I G S O N S N Notes Notes 0 Legend MPXF Default Forward Multiplex Option MPXR Default Reverse Multiplex Option RS Rate Set (00, 00, 00, 00) RS Rate Set (00, 00, 00, 00) F Used in the forward direction R Used in the reverse direction PRI Primary Traffic SEC Secondary Traffic SIG Signaling Traffic SN Service Negotiation SON Service Option Negotiation y Attribute supported n Attribute not supported Y Attribute supported and the default -

21 TIA/EIA/IS-0-A. 0 0 INTERSYSTEM SUPPORT. Protocol Architecture Figure.- shows a general model of the protocol architecture for any CDMA circuitswitched data service during intersystem operation (intersystem operation for packet data services is still under study). Intersystem data service support is described in TIA/EIA/IS-. RLP terminates at the Serving BS/MSC. IWF access occurs at the Anchor BS/MSC. Between the Serving and Anchor systems, the data service octets are carried by an intersystem link protocol (ISLP). ISLP is described in TIA/EIA/IS-. The Serving BS/MSC relay function between RLP on the U m interface and the ISLP adaptation layer passes each data service octet transparently, in sequence. The Anchor BS/MSC relay function between the IWF access function and the ISLP adaptation layer passes each data service octet transparently, in sequence. The ISLP adaptation layer accepts data service octets from the relay function in the Serving BS/MSC or Anchor BS/MSC. It then assembles them, in sequence, into blocks of data octets for transmission by ISLP. ISLP calls each block an ISLP SDU (service data unit). The ISLP adaptation layer accepts ISLP SDUs from ISLP and disassembles them into data service octets for delivery, in sequence, to the relay function. For async and fax, the ISLP adaptation layer is functionally equivalent to that described in TIA/EIA/IS- (see Section.). For STU-III, it is functionally equivalent to the SLAL (STU-III L Interface Adaptation Layer, see.. of chapter ). Serving BS/MSC relay function Anchor BS/MSC relay function RLP TIA/EIA--B ISLP Adaptation Layer ISLP ISLP Adaptation Layer ISLP IWF access Figure.-. Intersystem Protocol Architecture. Intersystem Requirements The size of the ISLP SDU produced by the ISLP adaptation layer shall not exceed 0 octets. This provides balance between the need to minimize buffer allocation in the adaptation layer and the need to minimize transmission delay between the Serving and Anchor systems. 0 -

22

23 Data Service Options for Spread Spectrum Systems: Radio Link Protocol TIA/EIA/IS-0-A. (PN-.) Ballot Resolution Version March

24 Copyright TIA

25 TIA/EIA/IS-0-A. CONTENTS INTRODUCTION General Description Terms References... - GENERAL REQUIREMENTS Required Multiplex Option Support Interface to Multiplex Options Primary Traffic Secondary Traffic Traffic Channel Frame Priorities Non-Transparent RLP Transparent RLP... - RLP PROCEDURES Non-Transparent RLP Procedures Initialization/Reset Procedures Non-Encrypted Mode Initialization/Reset Encrypted Mode RLP Initialization/Reset Extended Data Frame Sequence Numbering RLP Data Encryption Negotiation Mobile Station Negotiation Procedures BS/MSC Negotiation Procedures Data Transfer Encryption Decryption Frame Validity Checks Segmentation of Retransmitted Data Frames Transparent RLP Procedures Initialization Data Transfer Frame Validity Checks Traffic Channel Rate Control... - i

26 TIA/EIA/IS-0-A. 0 CONTENTS.. Service Option Negotiation Rate Control Procedures Service Negotiation Rate Control Procedures... - RLP FRAME FORMATS Traffic Channel Frames for Non-Transparent RLP Traffic Channel Frames for Transparent RLP RLP Frame Formats RLP Control Frames RLP Data Frames Unsegmented RLP Data Frames Segmented RLP Data Frames Rate / and Rate / Intersegment Fill Frames Primary Traffic Rate RLP Frame Format A Rate RLP Frame Format B RLP Idle Frames FIGURES Figure..-. RLP Transmit Sequence Number...- Figure..-. RLP Receive Sequence Number Variables...- ii

27 TIA/EIA/IS-0-A. 0 0 TABLES Table..-. Primary Traffic Frame Types Supplied by the RLP to the Multiplex Sublayer...- Table..-. Primary Traffic Frame Types Supplied by the Multiplex Sublayer to the RLP for Multiplex Option...- Table..-. Primary Traffic Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option...- Table..-. Secondary Traffic Frame Types Supplied by the RLP to the Multiplex Sublayer...- Table..-. Secondary Traffic Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option...- Table..-. Secondary Traffic Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option...- Table..-. Fraction of Frames at Rate and Rate / with Rate Reduction...- Table..-. Sequence Parameters for Rate Reduction...- Table...-. Sequence Parameters for Rate Reduction...- Table...-. Service Option Control Message Type-Specific Fields for Traffic Channel Rate Control...-0 Table...-. Fraction of Frames at Rate and Rate / with Rate Reduction...-0 Table...-. Values of the Maximum Allowable Data Length (MAX_LEN)...- Table..-. Modified Nordstrom Robinson Code...- iii

28

29 TIA/EIA/IS-0-A INTRODUCTION. General Description This chapter of TIA/EIA/IS-0 specifies procedures for the Radio Link Protocols supporting the CDMA data services. The Radio Link Protocol specified for the Rate Set multiplex sublayer is a compatible superset of the previous specifications for RLP found in TIA/EIA/IS-, and in TIA/EIA/IS-. The Radio Link Protocol specified for the Rate Set multiplex sublayer includes new frame definitions and new segmentation options. The Radio Link Protocol (RLP) provides an octet stream transport service over forward and reverse traffic channels. RLP is unaware of higher layer framing; it operates on a featureless octet stream, delivering the octets in the order received. The RLP may be either transparent or non-transparent. Transparent RLP provides maximum throughput transmission of service option data over a CDMA traffic channel, while maintaining bit count integrity over the air interface. The error rate for transparent RLP is that observed on the traffic channel itself. Typically this requires that upper layer data transmission protocols provide error recovery techniques equivalent to those provided in the non-transparent RLP. Non-transparent RLP substantially reduces the error rate exhibited by CDMA traffic channels. There is no direct relationship between upper layer packets and the underlying traffic channel frames; a large packet may span multiple traffic channel frames, or a single traffic channel frame may contain all or part of several small upper layer packets. Section below is a general description of RLP that defines its use by any service option for which it is suited. Section defines the RLP procedures for encrypted or nonencrypted applications. Section defines the RLP frame formats.. Terms Base Station (BS). A station in the Domestic Public Cellular Radio Telecommunications Service, other than a mobile station, used for communicating with mobile stations. Depending upon the context, the term base station may refer to a cell, a sector within a cell, or other part of the cellular system. BS/MSC. The base station and mobile switching center considered as a single functional entity. Mobile Station. A station in the Domestic 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. RLP. Radio Link Protocol. -

30 TIA/EIA/IS-0-A.. References TIA/EIA/IS--A TSB TSB Mobile Station-Base Station Compatibility Standard for Dual- Mode Wideband Spread Spectrum Cellular System, May,. Administration of Parameter Value Assignments for TIA/EIA Wideband Spread Spectrum Standards, December,. Support for. kbps Data Rate and PCS Interaction for Wideband Spread Spectrum Cellular Systems, December,. -

31 TIA/EIA/IS-0-A. 0 0 GENERAL REQUIREMENTS. Required Multiplex Option Support For service options supporting an interface with Multiplex Option or with Multiplex Option, non-transparent RLP frames may be transported as primary traffic, or as secondary traffic. Transparent RLP frames shall only be transported as primary traffic.. Interface to Multiplex Options Transparent RLP frames are transported as primary traffic, while non-transparent RLP frames can be carried as primary traffic or secondary traffic. Section.. applies to both transparent and non-transparent RLP frames. Section.. applies to non-transparent RLP frames only... Primary Traffic When carried as primary traffic, the RLP shall generate and supply exactly one frame containing the service option bits to the multiplex sublayer every 0 milliseconds. The frame shall be one of the types as shown in Table..-. The number of bits supplied to the multiplex sublayer for each type of frame shall also be as shown in Table..-. Unless otherwise commanded by Multiplex Option, RLP may supply a Rate, Rate /, Rate / or Blank frame. Unless otherwise commanded by Multiplex Option, RLP may supply a Rate, Rate /, Rate /, Rate / or Blank frame. Upon command, the RLP shall generate a Blank frame. A Blank frame contains no bits and is used for blank-andburst transmission of signaling traffic (see... of TSB) or when the RLP is unable to send a segment of a segmented data frame. Also upon command, the RLP shall generate a non-blank frame with a maximum rate of Rate /. Table..-. Primary Traffic Frame Types Supplied by the RLP to the Multiplex Sublayer RLP Frame Type Multiplex Option One (bits per frame) Multiplex Option Two (bits per frame) Rate Rate / 0 Rate / Not Used Rate / 0 Blank The multiplex sublayer in the mobile station categorizes every received Traffic Channel frame (see... of TSB), and supplies the frame category and accompanying bits, if any, to the RLP. Table..- lists the frame types supplied by the multiplex sublayer when RLP is carried as primary traffic by Multiplex Option. Although RLP does not -

32 TIA/EIA/IS-0-A. generate Rate / frames, Multiplex Option is not required to recognize this fact. RLP declares any received Rate / frames to be erasures (see..). Table..- lists the frame categories supplied by the multiplex sublayer when RLP is carried as primary traffic by Multiplex Option. Table..-. Primary Traffic Frame Types Supplied by the Multiplex Sublayer to the RLP for Multiplex Option RLP Frame Type Bits per Frame Multiplex Option Frame Categories Rate Rate / 0,, Rate / 0,, Rate /,, Blank 0, Erasure 0,0 0 Table..-. Primary Traffic Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option RLP Frame Type Bits per Frame Multiplex Option Frame Categories Rate Rate /,, Rate /,,,, Rate / 0,,0,,,,0,, Blank 0,,,,,, Erasure Secondary Traffic When carried as secondary traffic, RLP shall generate and supply one frame containing the service option bits to the multiplex sublayer every 0 milliseconds. The frame shall be one of the types shown in Table..-. The number of bits supplied to the multiplex sublayer for each type of frame shall also be as shown in Table..-. Upon command, the RLP shall generate a Blank frame. A Blank frame contains no bits and is used for blank-andburst transmission of signaling traffic (see... of TSB), when primary traffic has priority over secondary traffic and the primary traffic service option sends a Rate frame, or when the RLP is unable to send a segment of a segmented data frame (see..). -

33 TIA/EIA/IS-0-A. Table..-. Secondary Traffic Frame Types Supplied by the RLP to the Multiplex Sublayer RLP Frame Type Bits per Frame for Multiplex Option Bits per Frame for Multiplex Option Rate Rate / Rate / 0 Rate / Rate / Not Available Rate / Not Available 0 Rate / Not Used Rate / Not Available Rate / Not Available Rate / Not Available 0 Blank 0 0 The multiplex sublayer in the mobile station categorizes every received Traffic Channel frame (see... of TSB) and supplies the frame category and accompanying bits, if any, to the RLP. Table..- shows the frame types that may be sent to RLP by the multiplex sublayer when RLP is carried as secondary traffic using Multiplex Option. Table..- shows the frame types that may be sent to RLP by the multiplex sublayer when RLP is carried as secondary traffic using Multiplex Option. 0 Table..-. Secondary Traffic Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option RLP Frame Type Bits per Frame Multiplex Option Frame Categories Rate Rate / Rate / Rate / Blank 0 - Erasure 0, 0 -

34 TIA/EIA/IS-0-A. Table..-. Secondary Traffic Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option RLP Frame Type Bits per Frame Multiplex Option Frame Categories Rate Rate / Rate / 0 Rate / Rate / Rate / 0 Rate / Rate / Rate / Rate / 0 0,, Blank 0 -,-,-, Erasure Traffic Channel Frame Priorities.. Non-Transparent RLP Each RLP layer shall classify the frames it sends into three priority classes. In order of priority they are, with highest priority first:. RLP control frames. RLP data frames being resent in response to received NAK RLP control frames. RLP data frames being sent for the first time When the multiplex sublayer indicates that it is ready to send a non-blank RLP frame, RLP shall supply it with the highest priority non-transparent RLP frame available. When RLP is carried as primary traffic, and if no RLP frame in the above three priority classes is available, an RLP idle frame (see..) shall be supplied. When RLP frames are carried as secondary traffic, and if no RLP frames in the above three priority classes are available, an idle frame (see..) shall be supplied if the value of the round-trip frame counter is greater than zero. Whenever RLP supplies a non-blank frame and the value of the round-trip frame counter is greater than zero, RLP shall decrement the round-trip frame counter. When a service option that carries RLP using primary traffic is connected, and there is no service option connected using secondary traffic, the mobile station should observe the following priorities in using the traffic channel: -

35 TIA/EIA/IS-0-A Signaling Traffic. RLP frames in priority class order When a connected service option carries RLP using secondary traffic, and a connected service option that does not use RLP is carried using primary traffic, the mobile station should observe the following priorities in using the traffic channel, if the primary traffic service option permits:. Signaling Traffic. RLP control frames, RLP retransmissions (RLP frames in priority classes and ), and RLP transmissions due to idle timer expiration (see..). If the primary traffic service option permits, the multiplex sublayer should force primary traffic to no more than half rate when these RLP frames are transmitted.. Primary traffic service option data. New RLP data frames When data from a service option that carries RLP using secondary traffic has a lower priority than data from the service option using primary traffic, the blank and burst with secondary traffic frame format (see... of TSB) shall not be used unless the primary traffic service option has no data to send. When service options are connected that carry RLP as both primary and secondary traffic, the mobile station should observe the following priorities in using the traffic channel:. Signaling Traffic. RLP control frames and RLP retransmissions (RLP frames in priority classes and ) from the service option using primary traffic.. RLP control frames, RLP retransmissions (RLP frames in priority classes and ), and RLP transmissions due to idle timer expiration (see..) from the service option using secondary traffic.. New RLP data frames from the service option using primary traffic (RLP frames in priority class ).. New RLP data frames from the service option using secondary traffic (RLP frames in priority class )... Transparent RLP When the multiplex sublayer indicates that it is ready to send a non-blank RLP frame, RLP shall supply it with a transparent RLP data frame. If no transparent RLP data frame is available, an RLP idle frame (see..) shall be supplied. The following priorities should be observed by the mobile station when using the traffic channel:. Signaling Traffic. RLP data frames -

36

37 TIA/EIA/IS-0-A RLP PROCEDURES. Non-Transparent RLP Procedures Non-transparent RLP provides the capability of both non-encrypted mode and encrypted mode data transport. The encryption capability is selected during RLP initialization/reset and is accomplished as a negotiation between the mobile station and the BS/MSC. In addition, a procedure for synchronizing RLP without encryption negotiation is also provided here. The two techniques are compatible with each other and therefore can coexist in systems where encryption negotiation is supported in the infrastructure equipment, but possibly not in some of the mobile stations attempting access to the system... Initialization/Reset Procedures This standard defines two alternate RLP initialization/reset procedures. Non-Encrypted Mode initialization/reset shall be used by mobile stations and BS/MSCs that do not support RLP data frame encryption for the desired service. Encrypted Mode initialization/reset procedures shall be used by mobile stations and BS/MSCs to negotiate the use of RLP data frame encryption.... Non-Encrypted Mode Initialization/Reset Non-transparent RLP is established with a bidirectional handshake, after connection of the service option that uses RLP, to synchronize the connection. To establish the RLP without data encryption all control frames used (SYNC, ACK, and SYNC/ACK) shall indicate that encryption is not supported (see Table..-) and shall exclude both the EM and EXT_SEQ_M fields (see..). When a traffic type carrying RLP frames is activated, when the traffic type carrying RLP frames is changed, and at other times as specified in this standard or in other service option standards, the RLP layer shall perform the initialization/reset procedure below. When the RLP layer is initialized or reset, and when a SYNC RLP control frame is received, the RLP layer shall perform the following: Reset the send and receive state variables V(S), V(R), and V(N) (defined in.. ) to zero. Set the round-trip frame counter to zero. Set the consecutive erasure count E (defined in.. ) to zero. Clear the resequencing buffers (defined in.. ). Disable all NAK retransmission timers and all NAK abort timers. Discard any RLP data frames queued for retransmission. Discard any RLP data frame being reassembled (see..). When the RLP layer is initialized or reset, it shall transmit a continuous stream of SYNC RLP control frames (see..). When the RLP layer receives a SYNC RLP control frame it -

38 TIA/EIA/IS-0-A shall respond with a SYNC/ACK RLP control frame, set a round-trip frame counter to an implementation defined value greater than or equal to, and shall continue sending SYNC/ACK RLP control frames until the next valid non-blank frame which is not a SYNC RLP control frame is received. When the RLP layer receives a SYNC/ACK RLP control frame it shall respond with an ACK RLP control frame, set a round-trip frame counter to an implementation defined value greater than or equal to, and shall continue sending ACK RLP control frames until the next valid non-blank frame which is not a SYNC/ACK control frame is received. When the RLP layer receives an ACK RLP control frame, it shall send no more SYNC, SYNC/ACK or ACK RLP control frames, and should begin sending RLP data frames. When RLP frames are carried as primary or secondary traffic, the RLP layer shall store in RLP_DELAY s the number of frames received between the sending of the last SYNC or SYNC/ACK RLP control frame and reception of the first valid non-blank frame that is not an ACK or SYNC/ACK RLP control frame. RLP_DELAY s is used in NAK retransmission timing, as described in Encrypted Mode RLP Initialization/Reset CDMA mobile stations complying with this standard may support authentication (see.. of TIA/EIA/IS-) and may support encryption of RLP data frames using the procedures defined below. RLP data encryption shall be performed whenever cellular authentication procedures have been performed during the establishment of a CDMA Traffic Channel and RLP data encryption is negotiated (see...).... Extended Data Frame Sequence Numbering Mobile stations and BS/MSCs supporting RLP data encryption shall support the following extended data frame sequence numbering for RLP data frames. RLP shall maintain a 0-bit extended sequence number EXT_V(S). EXT_V(S) shall be set to zero when RLP is initialized following the establishment of a Traffic Channel. For all subsequent initializations/resets of RLP while the Traffic Channel remains established, RLP shall perform the following prior to sending a SYNC or SYNC/ACK control frame whose EM field is set to 0 : If the least significant bits of EXT_V(S) are not zero, RLP shall set the least significant bits of EXT_V(S) to zero, and shall increment the most significant bits of EXT_V(S), modulo. If the least significant bits of EXT_V(S) are zero, RLP shall not change EXT_V(S). For each RLP frame transmitted, RLP shall set the value of V(S) to the least significant bits of EXT_V(S). EXT_V(S) shall be incremented, following the procedures for incrementing V(S) that are contained in.. except that EXT_V(S) shall be incremented modulo 0. A minimum of frames sent following initialization/reset is believed to provide sufficient protection against frame erasure without incurring excessive overhead. -

39 TIA/EIA/IS-0-A RLP shall maintain a 0-bit extended sequence number EXT_V(R). When RLP is initialized or reset, RLP shall set the least significant bits of EXT_V(R) to zero. The most significant bits of EXT_V(R) shall be set as described in... or... as appropriate. When V(R) changes (see..), RLP shall change EXT_V(R) by the same amount.... RLP Data Encryption Negotiation When authentication is performed during the establishment of a CDMA Traffic Channel, the mobile station and BS/MSC shall set the input parameters of the DataKey_Generation procedure defined in Common Cryptographic Algorithms, Revision A. as follows: In the mobile station, RAND shall be set to the stored value of RAND s. In the BS/MSC, RAND shall be set to the value of the RAND field of the Access Parameters Message that was used for mobile station authentication. The mobile station and BS/MSC shall use the value of SSD_B at the time of mobile station authentication. The mobile station and BS/MSC shall then perform the DataKey_Generation procedure. The data encryption key (DataKey) and L table shall not change while the Traffic Channel is established. Mobile stations and BS/MSCs supporting RLP data encryption shall perform negotiation of RLP data encryption using the procedures in... or..., respectively. If the EM field is not included in a received RLP control frame, RLP shall process the message as if EM were included and set to 00. Throughout the following procedures, RLP may omit both the EM and EXT_SEQ_M fields whenever it generates a control frame in which the EM field would be set to 00. If the BS/MSC requests RLP data encryption, the BS/MSC may deny access to service if authentication procedures (see.. of TIA/EIA/IS--A) are not performed during Traffic Channel establishment, or if the mobile station indicates that it does not perform RLP data encryption.... Mobile Station Negotiation Procedures To indicate that the mobile station can perform RLP data encryption, the mobile station shall generate a SYNC control frame whose Encryption_Mode field indicates at least one supported data encryption mode (see Table..-), whose EM field is set to 0, and whose EXT_SEQ_M field is set to the most significant bits of RLP s current value of EXT_V(S). To indicate that the mobile station cannot perform RLP data encryption, RLP shall generate a SYNC control frame whose EM field is set to '00'. When RLP receives a SYNC control frame, it shall perform the following: That is, if the old value of V(R) is A and the new value of V(R) is B, EXT_V(R) is incremented by (+B-A) modulo. All arithmetic operations on EXT_V(R) are modulo 0. -

40 TIA/EIA/IS-0-A If the EM field of the received frame is set to 0, and RLP can perform at least one of the specified encryption modes, RLP shall set the most significant bits of EXT_V(R) to the value of the EXT_SEQ_M field of the received frame. In each SYNC/ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate which of the specified encryption modes it supports (see Table..-), set the EM field to 0, and set the EXT_SEQ_M field to the most significant bits of RLP s current value of EXT_V(S). If the EM field of the received frame is set to any other value, or if RLP cannot perform at least one of the specified encryption modes, RLP shall set the most significant bits of EXT_V(R) to zero. In each SYNC/ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate which of the specified encryption modes it supports (see Table..-) and set the EM field to 00. When RLP receives a SYNC/ACK control frame, it shall perform the following: If the EM field of the received frame is set to 0, and RLP can perform the specified encryption mode, RLP shall set the most significant bits of EXT_V(R) to the value of the EXT_SEQ_M field of the received frame. In each ACK control frame it then sends, RLP shall set the ENCRYPTION_MODE field to indicate the specified encryption mode (see Table..-), set the EM field to 0 and set the EXT_SEQ_M field to the most significant bits of RLP s current value of EXT_V(S). RLP shall encrypt all generated RLP data frames and shall decrypt all received RLP data frames, using the specified encryption mode and following the procedures of... and... If the EM field of the received frame is set to 0, but RLP cannot perform the specified encryption mode, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to any value other than 0, RLP shall set the most significant bits of EXT_V(R) to zero. In each ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate which of the specified encryption modes it supports (see Table..-) and set the EM field to 00. RLP shall neither encrypt nor decrypt RLP data frames. When RLP Layer receives an ACK control frame, it shall perform the following: If the EM field of the received frame is set to 0, and RLP can perform the specified encryption mode, RLP shall encrypt all generated RLP data frames and shall decrypt all received RLP data frames, using the specified encryption mode and following the procedures of... and... If the EM field of the received frame is set to 0, but RLP cannot perform the specified encryption mode, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to any value other than 0, RLP shall neither encrypt nor decrypt RLP data frames. -

41 TIA/EIA/IS-0-A BS/MSC Negotiation Procedures If the BS/MSC requests RLP data encryption, RLP shall generate a SYNC control frame whose ENCRYPTION_MODE field indicates at least one supported data encryption mode (see Table..-), whose EM field is set to '0' and whose EXT_SEQ_M field is set to the most significant bits of the current value of EXT_V(S). RLP should set the ENCRYPTION_MODE field to indicate all supported data encryption modes or may set the ENCRYPTION_MODE field to indicate its desired data encryption mode. If the BS/MSC does not request RLP data encryption, RLP shall generate a SYNC control frame whose ENCRYPTION_MODE field indicates it does not support encryption (see Table..-) and whose EM field is set to '00'. The BS/MSC should not request RLP data encryption if encryption is provided by the Link Layer or higher layers. When RLP Layer receives a SYNC RLP control frame, it shall perform the following: If the EM field of the received frame is set to 0, and the BS/MSC requests RLP data encryption, and RLP can perform at least one of the specified encryption modes (see Table..-), RLP shall set the most significant bits of EXT_V(R) to the value of the EXT_SEQ_M field of the received frame. In each SYNC/ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate its desired encryption mode (see Table..-), set the EM field to 0, and set the EXT_SEQ_M field to the most significant bits of RLP s current value of EXT_V(S). If the EM field of the received frame is set to 0, the BS/MSC requests RLP data encryption, and RLP cannot perform at least one of the specified encryption modes, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to any other value, or if the BS/MSC does not request data encryption, RLP shall set the most significant bits of EXT_V(R) to zero. In each SYNC/ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate that it does not support encryption and set the EM field to 00. When RLP receives a SYNC/ACK control frame, it shall perform the following: If the EM field of the received frame is set to 0, and the BS/MSC requests RLP data encryption, and RLP can perform at least one of the specified encryption modes, RLP shall set the most significant bits of EXT_V(R) to the value of the EXT_SEQ_M field of the received frame. In each SYNC/ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate its desired encryption mode, set the EM field to 0, and set the EXT_SEQ_M field to the most significant bits of RLP s current value of EXT_V(S). RLP shall encrypt all generated RLP data frames and shall decrypt all received RLP data frames, using the desired encryption mode and following the procedures of... and... If the EM field of the received frame is set to 0, the BS/MSC requests RLP data encryption, and RLP cannot perform at least one of the specified encryption modes, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). -

42 TIA/EIA/IS-0-A If the EM field of the received frame is set to 0, but the BS/MSC does not request RLP data encryption, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to any value other than 0, RLP shall set the most significant bits of EXT_V(R) to zero. In each ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate that it does not support encryption and set the EM field to 00. RLP shall neither encrypt nor decrypt RLP data frames. When RLP receives an ACK control frame, it shall perform the following: If the EM field of the received frame is set to 0, and the BS/MSC requests RLP data encryption, and RLP can perform the specified encryption mode, RLP shall encrypt all generated RLP data frames and shall decrypt all received RLP data frames, using the specified encryption mode and following the procedures of... and... If the EM field of the received frame is set to 0, the BS/MSC requests RLP data encryption, and RLP cannot perform the specified encryption mode, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to 0, but the BS/MSC does not request RLP data encryption, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to any value other than 0, RLP shall neither encrypt nor decrypt RLP data frames... Data Transfer When transferring data, non-transparent RLP is a pure NAK-based protocol. That is, the receiver does not acknowledge correct RLP data frames; it only requests the retransmission of RLP data frames that were not received. All operations on RLP frame sequence numbers shall be carried out in unsigned modulo arithmetic. Comparisons of two RLP frame sequence numbers shall also be modulo : for any RLP frame sequence number N, those sequence numbers from (N+) modulo to (N+) modulo, inclusive, shall be considered greater than N while all sequence numbers from (N-) modulo to (N-) modulo, inclusive, shall be considered less than N. The RLP layer shall maintain an -bit sequence number count V(S) for all transmitted RLP data frames (see Figure..-). The sequence number field (SEQ) in each new RLP data frame, each idle frame, and each control frame sent shall be set to V(S). V(S) shall be incremented, modulo, after formatting each new RLP data frame sent that contains a non-zero number of data octets. V(S) shall not be incremented after an RLP idle frame is sent. New RLP data frames shall not be segmented. Note that (N-) modulo is equal to (N+) modulo, and (N-) modulo is equal to (N+) modulo. -

43 TIA/EIA/IS-0-A. L_V(S) = sequence number of the next data frame to be supplied to the multiplex sublayer frames supplied to the multiplex sublayer generated frames to be supplied to the multiplex sublayer Figure..-. RLP Transmit Sequence Number The RLP layer shall maintain two -bit sequence number variables for receiving, V(R) and V(N) (see Figure..-). V(R) contains the expected value of the RLP frame sequence number field in the next new traffic channel frame to be received. V(N) contains the sequence number of the next needed traffic channel frame not received in sequence, as described below. L_V(N) = sequence number of the next data frame needed for sequential delivery data frames received in sequence L_V(R) = sequence number of the next expected new data frame data frames received out of sequence 0 buffer space for new or missing data frames Figure..-. RLP Receive Sequence Number Variables The RLP layer shall provide a storage buffer for resequencing of out-of-sequence RLP data frames both on the transmitting and on the receiving side. These buffers shall each be able to store no fewer than RLP data frames of the maximum size allowed for the traffic type carrying RLP. For each received RLP data frame that is valid and contains a non-zero number of data octets, the RLP layer shall compare the sequence number to V(R) and V(N). Criteria for frame validity are given in... i.e, two such buffers are required in a mobile station. -

44 TIA/EIA/IS-0-A. If the received RLP frame sequence number is less than V(R), then: 0 If the received RLP frame sequence number is less than V(N), or if the RLP data frame is already stored in the resequencing buffer, the RLP data frame shall be discarded as a duplicate. If the received RLP frame sequence number is greater than or equal to V(N) and the RLP data frame is not already stored in the resequencing buffer, then: + If the received frame is an unsegmented RLP data frame the RLP layer shall store the received RLP data frame in the resequencing buffer. + If the received frame is a segmented RLP data frame, the segment shall be reassembled as specified in... + If the complete RLP data frame has been received, and the RLP frame sequence number is equal to V(N), the RLP layer shall pass the data in all contiguous RLP data frames in the resequencing buffer, from V(N) upward, to the higher layer, and shall remove the passed frames from the resequencing buffer. The RLP layer shall then set V(N) to (LAST+) modulo where LAST is the sequence number of the last RLP data frame passed to the higher layer from the resequencing buffer If the received RLP frame sequence number equals V(R), then: - If the received frame is a segmented RLP data frame, the frame shall be discarded without further processing. Otherwise, the frame shall be processed as follows: - If V(R) equals V(N), the RLP layer shall increment V(N) and V(R), modulo, and shall pass all data octets in the RLP data frame to the higher layer. - If V(R) is not equal to V(N), the RLP layer shall increment V(R), modulo, and shall store the received RLP data frame in the resequencing buffer. + If (V(R)-) modulo is greater than V(N), the RLP layer shall perform the initialization/reset procedure specified in... If the received sequence number is greater than V(R), then: - If the received sequence number is less than V(N), the RLP layer shall perform the initialization/reset procedure specified in... - If the received frame is a segmented RLP data frame, the frame shall be discarded without further processing. Otherwise, the frame shall be processed as follows: - The RLP layer shall store the received RLP data frame in the resequencing buffer and shall set V(R) equal to the received sequence number. - The RLP layer shall then send one or more NAK RLP control frames requesting the retransmission of all unreceived RLP data frames from V(N) to (V(R)-) modulo, inclusive. RLP data frames requested in a previous NAK RLP control frame whose NAK retransmission counter or NAK abort counter has not expired should not be included in these NAK RLP control frames. -

45 TIA/EIA/IS-0-A The RLP layer shall then increment V(R), modulo. - If (V(R)-) modulo is greater than V(N), the RLP layer shall perform the initialization/reset procedure specified in... The RLP layer shall also compare the sequence number in each valid received RLP idle frame and NAK RLP control frame to V(R). If the received RLP frame sequence number equals V(R), the RLP layer shall take no further action. If the received RLP frame sequence number is greater than V(R), the RLP layer shall set V(R) to the received frame sequence number, and shall then send one or more NAK control frames requesting the retransmission of all unreceived RLP data frames with sequence numbers V(N) to (V(R)-) modulo, inclusive. RLP data frames requested in a previous NAK RLP control frame whose NAK retransmission counter or NAK abort counter has not expired should not be included in these NAK frames. On receiving a NAK, the RLP layer shall insert copies of the requested RLP data frame(s) into its output stream. If the NAK includes any sequence number greater than or equal to V(S), the RLP layer shall perform the initialization/reset procedures specified in... or... If the size of a retransmitted frame is less than or equal to the number of octets available in the traffic channel frame at the time of retransmission, an unsegmented frame (see... and...) shall be used. If the size of a retransmitted frame exceeds the number of octets available in the traffic channel frame at the time of retransmission, the RLP layer may segment the frame as specified in... The RLP layer shall maintain a NAK retransmission timer for each RLP data frame requested in a NAK RLP control frame. The NAK retransmission timer shall be implemented as a frame counter. The NAK retransmission counter shall be incremented for each valid RLP idle frame and for each valid new RLP data frame (sequence number greater than or equal to V(R)) received on the traffic type where the RLP is carried. When RLP frames are carried as primary traffic, the RLP receiver shall not increment the NAK retransmission counter upon receiving a Blank RLP frame. When RLP is used with Multiplex Option and is carried as secondary traffic, frame types,,, and (see... of TIA/EIA/IS-) are not considered RLP frames and are not counted. When RLP is used with Multiplex Option and is carried as secondary traffic, frame types, and (see... of TIA/EIA/IS-) are not considered RLP frames and are not counted. The NAK retransmission counter shall not be incremented on receiving erasures (as defined in..), RLP control frames, Intersegment Fill frames nor old RLP data frames This would indicate that the NAK process has fallen behind the sequence numbering by more than frames. -

46 TIA/EIA/IS-0-A (sequence number less than V(R)). The NAK retransmission counter shall be considered expired when it is incremented to an implementation dependent value greater than RLP_DELAY s. If any RLP data frame requested has not arrived when its NAK retransmission timer expires, the receiver shall send one or more NAK RLP control frames requesting the retransmission of all unreceived RLP data frames from V(N) upward. RLP data frames requested in a previous NAK RLP control frame whose NAK retransmission timer or NAK abort timer has not expired should not be included in these NAK frames. Each NAK RLP control frame transmitted as the result of a NAK retransmission timer expiration shall be transmitted twice. The RLP layer shall then restart the NAK retransmission timer for the RLP data frames requested. If any RLP data frame requested has not arrived when its NAK retransmission timer expires for the second time, the receiver shall send one or more NAK RLP control frames requesting the retransmission of all unreceived RLP data frames from V(N) upward. RLP data frames requested in a previous NAK RLP control frame whose NAK retransmission timer or NAK abort timer has not expired should not be included in these NAK frames. Each NAK RLP control frame transmitted as the result of a second NAK retransmission timer expiration shall be transmitted three times. The RLP layer shall then start a NAK abort timer for the RLP data frames requested. The NAK abort timer shall be implemented, and shall be considered expired, according to the same rules as a NAK retransmission timer. If any RLP data frame requested has not arrived when its NAK abort timer expires, the RLP layer shall set V(N) to the sequence number of the next missing frame, or to V(R) if there are no remaining missing frames. The RLP layer shall then pass the data in any RLP data frames with sequence numbers less than V(N) in order of sequence number to the higher layer. Further recovery is the responsibility of the upper layer protocols. The RLP layer shall perform the following whenever RLP frames are carried as secondary traffic: Whenever a new RLP data frame is sent, the RLP layer shall start an idle timer. The implementation and expiration criteria for the idle timer shall be the same as for a NAK retransmission timer (see above), except that all traffic channel frames shall be counted toward timer expiration. The RLP layer shall also maintain an idle frame transmission counter, which shall initially be set to zero. The timer shall be restarted, and the idle frame transmission counter shall be reset to zero, following the transmission of any non-blank RLP frame prior to the expiration of the timer. When the idle timer expires, the RLP layer shall transmit an RLP control frame or an RLP idle frame containing the current data frame sequence number V(S), shall It is recommended that a guard interval of five frames be added to the retransmission timeout to account for buffering within the TIA/EIA/IS- mobile or base station and for segmentation of retransmitted frames. When RLP is carried as secondary traffic, an RLP idle frame is an RLP data frame with zero length (see...). -0

47 TIA/EIA/IS-0-A increment the idle frame transmission count, and shall restart the idle timer. If the idle frame transmission count equals, the idle timer shall be disabled.... Encryption When RLP data encryption is negotiated, the Data octets of all transmitted RLP data frames shall be encrypted, using the following procedures. Encryption mask generation shall be in accordance with the Data_Mask procedure defined in Common Cryptographic Algorithms, Revision A.. When an RLP data frame is transmitted, the RLP layer shall set the input parameters of the Data_Mask procedure, HOOK and LEN (see Interface Specification for Common Cryptographic Algorithms, Revision A. ) as follows: If the RLP data frame is transmitted by a mobile station, the RLP layer shall set HOOK equal to EXT_V(S) (see...), with the two most significant bits of HOOK set to 00. If the RLP data frame is transmitted by a BS/MSC, the RLP layer shall set HOOK equal to EXT_V(S) (see...), and shall then set the most significant bits of HOOK to 0. The length of the mask (LEN) shall be equal to the number of octets in the Data part of the RLP data frame. The RLP layer shall then execute the Data_Mask procedure. Each octet of the Data part of the RLP data frame shall be combined with the mask by bitwise exclusive-or, combining successive data octets with mask octets. RLP data frames that are retransmitted shall be encrypted using the same mask as when first transmitted. If an RLP data frame for retransmission is to be sent as segmented RLP data, the data frame shall be encrypted prior to its segmentation.... Decryption For each RLP data frame received, the RLP layer shall form an extended sequence number EXT_SEQ which shall be set equal to EXT_V(R) (see...) minus the difference between V(R) (see..) and the received sequence number. For this calculation, if the received sequence number changes V(R) and EXT_V(R), the new values of V(R) and EXT_V(R) shall be used in the calculation of EXT_SEQ. When an encrypted RLP data frame is received, the RLP layer shall set the input parameters of the Data_Mask procedure (see Interface Specification for Common Cryptographic Algorithms, Revision A. ) as follows: That is, if the received sequence number is N, EXT_SEQ is set to EXT_V(R) - ((+V(R)-N) modulo ). This ensures that the received sequence number is never less than V(R). -

48 TIA/EIA/IS-0-A If the RLP data frame is received from a mobile station, the RLP layer shall set HOOK equal to EXT_SEQ, with the two most significant bits of HOOK set to 00. If the RLP data frame is received from a BS/MSC, the RLP layer shall set HOOK equal to EXT_SEQ, and shall then set the most significant bits of HOOK to 0. The length of the mask (LEN) shall be equal to the number of octets in the Data part of the RLP data frame. The RLP layer shall then execute the Data_Mask procedure. Each octet of the Data part of the RLP data frame shall be combined with the mask by bitwise exclusive-or, combining successive data octets with mask octets. If a retransmitted RLP data frame is received as or more segmented RLP frames, the unsegmented frame shall be reassembled prior to decrypting the data... Frame Validity Checks... Primary Traffic When RLP frames are carried as primary traffic, the RLP layer shall discard as invalid all traffic channel frames received for which any of the following applies:. The traffic channel frame is classified into category,,, 0 or by Multiplex Option (see... of TSB) or into category by Multiplex Option (see... of TSB). All such traffic channel frames shall be counted as erasures 0 by RLP.. For RLP control frames, the FCS field does not check; for Rate / intersegment fill frames and Rate / RLP idle frames, the FCS field is not the correct value for the value of the SEQ field. All such traffic channel frames shall be counted as erasures by RLP.. For Rate / frames, when using Multiplex Option, the last four bits are not '0000' or ''. Such a frame shall be counted as an "erasure" by RLP.. RLP frame TYPE field value is not one of the values defined in... RLP frame LEN field value is not within the range allowed in... RLP frame CTL field value is not a value as defined in... For Rate / idle frames only, the received RLP frame sequence number is not within the range from V(R) to (V(R)+E) modulo, inclusive, where E is the number of consecutive erasures (see () and () above) preceding the current frame, and V(R) is as defined in.... For Rate / idle frames only, the frame is not identical in contents to the preceding Rate / idle frame. 0 The erasures defined here serve to inhibit incrementing of the NAK retransmission timer. They are not to be confused with TIA/EIA/IS- frame erasures. -

49 TIA/EIA/IS-0-A All other traffic channel frames shall be considered valid. If three consecutive identical Rate / idle frames arrive with a sequence number that is out of the acceptable range, as defined in () above, then: If the third received sequence number is greater than V(R), the RLP layer shall consider the third frame and its sequence number as valid and shall process the frame as specified in... If the third received sequence number is less than V(R), the RLP layer shall perform the initialization/reset procedure specified in... The RLP layer shall maintain a count E of the consecutive frames classified as erasures, as defined in (), () and () above. If the consecutive erasure count E exceeds, the RLP layer shall perform the initialization/reset procedure specified in Secondary Traffic When RLP frames are carried as secondary traffic, the RLP layer shall discard as invalid all traffic channel frames received for which any of the following applies:. The traffic channel frame is classified into category or 0 by Multiplex Option or into category by Multiplex Option (see... of TSB). All such frames shall be counted as erasures by RLP. All other frame categories that do not include secondary traffic are ignored by RLP; only those listed here shall be classified as erasures.. For RLP control frames, idle frames and Rate / intersegment fill frames, the FCS field does not check. All such frames shall be counted as erasures by RLP.. For Rate / frames, when using Multiplex Option, the last four bits are not 0000 or. Such a frame shall be counted as an erasure by RLP.. RLP frame TYPE field value is not one of the values defined in... RLP frame LEN field value is not within the range allowed in... RLP frame CTL field value is not a value defined in.. All other traffic channel frames shall be considered valid, and shall be processed by RLP if they contain secondary traffic data. The RLP layer shall maintain a count E of the consecutive frames classified as erasures, as defined in (), () and () above. If the consecutive erasure count E exceeds, the RLP layer shall perform the initialization/reset procedure specified in..... Segmentation of Retransmitted Data Frames The following procedures apply to the segmentation and reassembly of RLP data frames. Segmentation may be necessary when a retransmitted frame size exceeds the number of octets available at the time the retransmission occurs. -

50 TIA/EIA/IS-0-A The RLP layer procedures below assure that no more than three data bearing segments are needed to transmit an RLP frame by requiring all but the last segment to use at least a Rate / frame. A retransmitted RLP data frame may be sent in one, two or three segments. If the retransmitted frame is sent in a single segment, an unsegmented frame (see... and...) is used. If the retransmitted RLP data frame size exceeds the number of octets available at the time the retransmission occurs, the RLP layer should segment the frame. With the exception of intersegment fill frames, all RLP segmented frames except the last segmented frame shall be sent using Rate / or larger RLP frames. When Rate Set is used, an Intersegment Fill frame (see... and...) can be sent by the BS/MSC. Mobile stations complying with this standard shall not transmit intersegment fill frames on the reverse link. When the intersegment fill frame is used the sequence number of an Intersegment Fill frame shall be set equal to the sequence number of the RLP data frame being retransmitted. When a Rate / or Rate / intersegment fill frame is to be sent, RLP shall use the format of... The RLP layer segments the frame using the following procedure: The first segment shall be transmitted using the First Segment frame type (see...). The first segment should contain the maximum number of data octets available. If RLP is carried on Multiplex Option, and less than a Rate / RLP frame is available, a Blank RLP frame should be provided to the multiplex sublayer. Alternately, an Intersegment Fill frame (see... and...) may be sent. If the number of octets remaining after the transmission of a First Segment frame type exceeds the number of octets available at the time of transmission of the next segment, the next segment shall be transmitted using the Second Segment frame type (see...). Otherwise, the next segment shall be transmitted using the Last Segment frame type (see...). If RLP is carried on Multiplex Option, and less than a Rate / RLP frame is available, a Blank RLP frame should be provided to the multiplex sublayer. Alternately, an Intersegment Fill frame (see... and... may be sent. If the number of octets remaining after the transmission of a First or Second Segment frame type is less than or equal to the number of octets available at the time of transmission of the next segment, the next segment shall be transmitted using the Last Segment frame type (see...). If RLP is carried on Multiplex Option, and the number of octets remaining after the transmission of a Second Segment frame type exceeds the number of octets available at the time of transmission of the next segment, a Blank RLP frame should be provided to the multiplex sublayer. Alternately, an Intersegment Fill frame (see... and...) may be sent. For Multiplex Option, the smallest available frame that carries data is Rate /, which is larger than Rate /. -

51 TIA/EIA/IS-0-A Segmented RLP data frames shall not be sent with the LEN field equal to zero. The SEQ fields of all segments shall be set to the sequence number of the RLP data frame being retransmitted. The RLP layer may transmit RLP control frames between segments of a segmented RLP data frame. For Multiplex Option, the RLP layer may transmit Rate / idle frames (see..) between segments of a segmented RLP data frame. For Multiplex Option, the RLP layer shall not transmit idle frames between segments of a segmented RLP data frame. The RLP layer shall not transmit other RLP data frames nor segments with different sequence numbers between segments of a segmented RLP data frame. The RLP layer shall begin frame reassembly on receipt of the first segment of a segmented RLP data frame. When RLP is carried with Multiplex Option, if an Intersegment Fill frame is received, the RLP layer shall discard it. When the last segment of the RLP data frame is received, the RLP layer shall process the RLP data frame in the same manner as if it had been unsegmented (see...). The RLP layer shall discard, without further processing, any segmented RLP data frame that is received under any of the following conditions: If a segment is received out of order (e.g., a last or second segment received without receiving a first segment). If an invalid frame (see..) is received at any time between the first and last segments. If an RLP data frame or segment with a different sequence number is received between the first and last segments. When RLP is carried using Multiplex Option, if an idle frame (see..) is received at any time between the First Segment frame and Last Segment frame.. Transparent RLP Procedures.. Initialization Transparent RLP maintains two state variables, V(S), and V(R) (see..). When a service option using transparent RLP is connected, the transparent RLP layer shall perform the following: Transparent RLP shall set counters V(S) and V(R) to zero. Transparent RLP shall send an initialization indication to the upper layer. Following the initialization procedure the transparent RLP may begin delivering frames to and accepting frames from the multiplex sublayer... Data Transfer Transparent RLP does not provide any retransmission of erased frames. It is the responsibility of the upper layers to provide further synchronization and error recovery when Transparent RLP is used. -

52 TIA/EIA/IS-0-A Transparent RLP shall maintain two eight-bit sequence number variables, V(S) (for transmitting) and V(R) (for receiving). See.. for initialization procedures for these state variables. If Transparent RLP has no data to send, Transparent RLP generates and transmits an idle RLP frame (see..). When an idle RLP frame is sent, transparent RLP shall set the SEQ field to the current value of V(S). V(S) shall not be incremented when Transparent RLP sends an idle RLP frame. When an idle RLP frame is received by Transparent RLP, Transparent RLP may discard it. When a transparent RLP frame is to be transmitted the RLP transmitter shall perform the following: The RLP transmitter shall copy the current value of V(S) into the SEQ field of the frame to be transmitted. The RLP transmitter shall set the LEN field of the frame to the number of data octets to be transmitted. The remainder of the frame shall be formatted in accordance with the valid frame formats for transparent RLP defined in... and... The RLP transmitter shall increment V(S) modulo for every octet of service option data carried in the RLP frame. The RLP transmitter shall deliver the formatted frame to the multiplex sublayer in accordance with the interface requirements for Multiplex Option or as appropriate. When a transparent RLP data frame is received the transparent RLP receiver shall perform the following: The transparent RLP receiver shall compare the value of the received SEQ field with V(R). - If the value of SEQ equals V(R) then: + The RLP receiver shall update V(R) by adding the value of LEN to the value of V(R) modulo and, + The RLP receiver shall pass the contents of the received RLP data frame to the upper layer. - If the value of SEQ is less than the value of V(R) then: + The transparent RLP layer shall pass the value of -(V(R)-SEQ) (the number of octets previously lost) and the contents of the received RLP data frame to the upper layer. + The transparent RLP layer shall set the value of V(R) to the value of (SEQ+LEN) modulo. - If the value of SEQ is greater than the value of V(R) then: -

53 TIA/EIA/IS-0-A The transparent RLP layer shall pass the value of SEQ-V(R) (the number of octets previously lost) and the contents of the received RLP data frame to the upper layer. + The transparent RLP layer shall set the value of V(R) to the value of (SEQ+LEN) modulo. When the transparent RLP receives an idle frame from the multiplex sublayer, the transparent RLP receiver shall discard the frame... Frame Validity Checks Transparent RLP shall discard as invalid all traffic channel frames received which are classified into category or 0 by Multiplex Option (see... of TIA/EIA/IS-). Transparent RLP sublayer shall discard as invalid all traffic channel frames received which are classified into category by Multiplex Option (see... of TIA/EIA/IS-).. Traffic Channel Rate Control The following requirements for traffic channel rate control shall apply to mobile stations having a single connected service option. Traffic channel rate control for mobile stations having multiple connected service options is for further study... Service Option Negotiation Rate Control Procedures The BS/MSC may send a Service Option Control Order to the mobile station on the Forward Traffic Channel (see.. of TIA/EIA/IS--A). The mobile station shall not send Service Option Control Orders for the purpose of rate control to the BS/MSC. If the mobile station receives a Service Option Control Order having an ORDQ field in which the MSBs have values given in Table..-, then the mobile station shall generate the fraction P of those new traffic channel frames normally generated as full-rate frames at either full rate (Rate ) or half rate (Rate /) as specified by the corresponding line in the table. While the traffic channel is active the mobile station shall continue to use these fractions until the mobile station receives a Service Option Control Order that specifies different fractions. Whenever a traffic channel first becomes active, the mobile station shall set the fraction P to. 0 -

54 TIA/EIA/IS-0-A. Table..-. Fraction of Frames at Rate and Rate / with Rate Reduction ORDQ (binary) P = Fraction of Normally Rate Frames to be Rate ( - P) = Fraction of Normally Rate Frames to be Rate / 000XXXXX 0 00XXXXX / / 00XXXXX / / 0XXXXX / / 00XXXXX 0 0 The mobile station may use the following procedure to perform this rate reduction. Sequences of N frames are formed as shown in Table..-. The first L traffic channel frames in this sequence are allowed to be at Rate, the next N-L frames are forced to be Rate /. Whenever the RLP layer has no more octets to send than fit in a Rate / RLP data frame, a Rate / RLP data frame shall be sent, and the sequence shall be reset. This ensures that the first traffic channel frame in a burst of data will be at Rate, unless ORDQ equals 00XXXXX or the RLP layer has been commanded by the multiplex sublayer to generate other than a Rate frame. Table..-. Sequence Parameters for Rate Reduction ORDQ (binary) Sequence Length, N Maximum Number of Contiguous Rate Frames in a Sequence, L Number of Contiguous Rate / Frames in a Sequence, N-L 000XXXXX 0 00XXXXX 00XXXXX 0XXXXX 00XXXXX 0.. Service Negotiation Rate Control Procedures If service negotiation is used, the BS/MSC may send a Service Option Control Message to the mobile station on the Forward Traffic Channel (see... of TIA/EIA/TSB-). The mobile station shall not send a Service Option Control Message to the BS/MSC. -

55 TIA/EIA/IS-0-A Mobile Station Requirements The mobile station shall support one pending rate control Service Option Control Message for the service option. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 000, then at the action time associated with the message, the mobile station shall process the message as follows: If the RATE_REDUC field is equal to a value defined in Table...-, the service option shall generate the fraction of those frames normally generated as Rate frames at either Rate or Rate / as specified by the corresponding line in Table...-. The service option shall continue to use these fractions until either of the following events occur: - The mobile station receives a Service Option Control Message with FIELD_TYPE set to 000 specifying a different RATE_REDUC, or - The service option is re-initialized. If the RATE_REDUC field is not equal to a value defined in Table...-, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to The service option may use the following procedure to perform rate reduction. Sequences of N frames are formed as shown in Table...- are allowed to be at Rate, the next N- L frames are forced to be Rate /. Whenever the RLP layer has no more octets to send than fit in a Rate / RLP data frame, a Rate / RLP data frame shall be sent, and the sequence shall be reset. This ensures that the first Traffic Channel frame in a burst of data will be at Rate, unless RATE_REDUC equals 00 or the RLP layer has been commanded by the multiplex sublayer to generate other than a Rate frame. Table...-. Sequence Parameters for Rate Reduction RATE_REDUC (binary) Sequence Length, N Maximum Number of Contiguous Rate Frames in a Sequence, L Number of Contiguous Rate / Frames in a Sequence, N-L

56 TIA/EIA/IS-0-A.... BS/MSC Requirements The BS/MSC may send a Service Option Control Message to the mobile station for Traffic Channel rate control. If the BS/MSC sends a Service Option Control Message for Traffic Channel rate control, the BS/MSC shall include the type-specific fields shown in Table...-. Table...-. Service Option Control Message Type-Specific Fields for Traffic Channel Rate Control Field Length (bits) RATE_REDUC RESERVED FIELD_TYPE 0 RATE_REDUC - Rate reduction. The BS/MSC shall set this field to the RATE_REDUC value from Table...- corresponding to the rate reduction that the mobile station is to perform. RESERVED - Reserved bits. The BS/MSC shall set this field to 00. FIELD_TYPE - Type-specific field designator. The BS/MSC shall set this field to 000. Table...-. Fraction of Frames at Rate and Rate / with Rate Reduction RATE_REDUC (binary) Fraction of Normally Rate Frames to be Rate Fraction of Normally Rate Frames to be Rate / 000' 0 00 / / 00 / / 0 / / 00 0 All other RATE_REDUC values are reserved. 0-0

57 TIA/EIA/IS-0-A RLP FRAME FORMATS. Traffic Channel Frames for Non-Transparent RLP Non-transparent RLP shall send and receive traffic channel frames in accordance with the requirements of IS- Multiplex Options and. Non-transparent RLP frames can be transmitted as primary traffic or as secondary traffic. Service options may support any subset of the available traffic types and RLP frame types to carry non-transparent RLP. Mobile stations supporting multiple connected service options may support independent instances of non-transparent RLP for each service option, but each traffic type shall carry only a single instance of non-transparent RLP. RLP data frames sent on one traffic type shall not be retransmitted on another traffic type. Non-transparent RLP frames shall not be sent on the Access and Paging Channels. The frame formats defined in.. through.. can be carried by the following Multiplex Option frames (see... and... of TSB): 00 bps primary traffic only (full rate primary traffic). 00 bps primary traffic only (half rate primary traffic). 00 bps primary traffic only (eighth rate primary traffic). Dim and Burst with Rate / primary and signaling traffic, as primary traffic. Dim and Burst with Rate / primary and secondary traffic, either as primary traffic, secondary traffic, or both. Dim and Burst with Rate / primary and secondary traffic, as secondary traffic. Dim and Burst with Rate / primary and secondary traffic, either as primary traffic, secondary traffic, or both. Dim and Burst with Rate / primary and signaling traffic, as primary traffic. Blank and burst with secondary traffic only. The frame formats defined in.. through.. can be carried by the following Multiplex Option frame formats (see... and... of TSB): 00 bps primary traffic only (full rate primary traffic). 00 bps primary traffic only (half rate primary traffic). 00 bps primary traffic only (quarter rate primary traffic). 00 bps primary traffic only (eighth rate primary traffic). RLP would be carried as both primary and secondary traffic simultaneously if there are two service options active (one using primary traffic and the other using secondary traffic), each with its own instance of RLP. -

58 TIA/EIA/IS-0-A Dim and Burst with Rate / primary and signaling traffic, as primary traffic. Dim and Burst with Rate / primary and secondary traffic, as primary traffic, secondary traffic, or both. Dim and Burst with Rate / primary and secondary traffic, as primary traffic, secondary traffic, or both. Dim and Burst with Rate / primary and signaling traffic, as primary traffic, Dim and Burst with Rate / primary and signaling traffic, as primary traffic, Dim and Burst with Rate / primary and secondary traffic, as primary traffic, secondary traffic, or both, Dim and Burst with Rate / primary, secondary, and signaling traffic, as primary traffic, secondary traffic, or both, Blank and burst with secondary traffic only. For full rate primary traffic only, two special frame formats are defined in... The information field of the first format corresponds to an RLP control or data frame as defined in.. and.. respectively. The second frame format contains a sequence number and user data only and allows maximum throughput.. Traffic Channel Frames for Transparent RLP Transparent RLP shall send and receive traffic channel frames in accordance with the requirements of IS- Multiplex Options and. Transparent RLP frames can be transmitted as primary traffic only. Service options may support any subset of the RLP data frame types to carry transparent RLP. Mobile stations supporting multiple connected service options may support a single instance of Transparent RLP. Transparent RLP frames shall not be sent on the Access and Paging Channels. The frame formats defined in.. below can be carried by the following Multiplex Option frames (see... and... of TSB): 00 bps primary traffic only as primary traffic. 00 bps primary traffic only as primary traffic. 00 bps primary traffic only as primary traffic. Dim and Burst with Rate / primary and signaling traffic, as primary traffic. Dim and Burst with Rate / primary and secondary traffic, as primary traffic. RLP would be carried as both primary and secondary traffic simultaneously if there are two service options active (one using primary traffic and the other using secondary traffic), each with its own instance of RLP. With the exception of the last segmented frame, Rate / RLP frames may not carry segmented RLP data frames(see..). -

59 TIA/EIA/IS-0-A. 0 0 Dim and Burst with Rate / primary and secondary traffic, as primary traffic. Blank and burst with secondary traffic only. The frame formats defined in.. below can be carried by the following Multiplex Option frames (see... and... of TSB): 00 bps primary traffic only as primary traffic. 00 bps primary traffic only as primary traffic. 00 bps primary traffic only as primary traffic. 00 bps primary traffic only as primary traffic. Dim and Burst with Rate / primary and signaling traffic, as primary traffic. Dim and Burst with Rate / primary and secondary traffic, as primary traffic. Dim and Burst with Rate / primary and signaling traffic, as primary traffic. Dim and Burst with Rate / primary and secondary traffic, as primary traffic. Dim and Burst with Rate / primary and signaling traffic, as primary traffic. Dim and Burst with Rate / primary and secondary traffic, as primary traffic. Dim and Burst with Rate / primary, secondary, and signaling traffic, as primary traffic. Blank and burst with secondary traffic only. For full rate primary traffic only, transparent RLP may use the Full Rate Format B frame, as defined in.... RLP Frame Formats.. RLP Control Frames RLP control frames are distinguished by the CTL field. RLP control frames are not themselves sequence numbered, but contain the next data sequence number, in order that erased RLP data frames may be quickly detected. The sequence number is not incremented after an RLP control frame. Certain RLP control frames (specifically the NAK message) may refer to the sequence numbers of other RLP data frames. -

60 TIA/EIA/IS-0-A. Field Length (bits) SEQ CTL ENCRYPTION_MODE FIRST LAST EM 0 or EXT_SEQ_M 0 or FCS Padding Variable SEQ - RLP data frame sequence number. See... CTL - RLP frame type. For RLP control frames, the CTL field is defined as follows: NAK (negative acknowledgment). Requests retransmission of RLP data frames numbered FIRST through LAST, inclusive SYNC. Requests return of an RLP control frame with the ACK bit set ACK. Acknowledges receipt of an RLP control frame with the SYNC bit set SYNC/ACK. Indicates both SYNC and ACK. ENCRYPTION_MODE - Encryption Mode. This field indicates the supported or desired user data encryption mode(s), set according to Table..-. FIRST - For NAK RLP control frames, the FIRST field shall contain the sequence number of the first RLP data frame for which retransmission is requested. For all other RLP control frame types, this field shall contain 0x00. LAST - For NAK RLP control frames, the LAST field shall contain the sequence number of the last RLP data frame for which retransmission is requested. For all other RLP control frame types, this field shall contain 0x00. EM - Encryption Request Indicator. This field shall not be included in NAK RLP control frames. 00 (Default) Requests or Acknowledges no RLP data frame encryption (not supported or inactive). 0 Requests or Acknowledges RLP data frame encryption capability. EXT_SEQ_M - This field shall be included when the EM field is included. -

61 TIA/EIA/IS-0-A. 0 When the EM field is set to 0, this field shall carry the most significant bits of the extended data frame sequence number. Otherwise, this field shall be set to all zeros. When included, contents of this field shall be set to the most significant bits of EXT_V(S) (see...). FCS - Frame Check Sequence. The contents shall be as generated by the -bit FCS polynomial specified in. of RFC. The order of transmission of the FCS shall also be as specified in. of RFC. The FCS shall cover all fields before the FCS field. Padding - Padding bits. As required to fill the remainder of the frame. These bits shall be set to 0. Table..- User Data Encryption Modes Encryption Mode (binary) Meaning 00 Encryption not supported (default). This value shall be used in NAK control frames. 0 Enhanced encryption mode. 0 Both basic and enhanced encryption modes. This value shall not be used in ACK control frames. Basic encryption mode... RLP Data Frames... Unsegmented RLP Data Frames Unsegmented RLP data frames carry a variable number of data octets, using a length field to indicate the number of octets. Field Length (bits) SEQ CTL LEN Data Padding xlen Variable 0 SEQ - RLP data frame sequence number. See.. and... -

62 TIA/EIA/IS-0-A. 0 CTL - RLP frame type. For a frame carrying unsegmented data the CTL field shall be set to 0. LEN - Data length. May be any value in the range from 0 to the maximum allowable for the RLP frame. Maximum values of LEN (MAX_LEN) are as given in Table...-. When LEN is zero, the RLP frame is treated as an RLP idle frame, and the sequence number is not advanced. Data - Data octets. Padding - Padding bits. As required to fill the remainder of the frame. These bits shall be set to 0. Table...-. Values of the Maximum Allowable Data Length (MAX_LEN) RLP Frame Type MAX_LEN Multiplex Option MAX_LEN Multiplex Option Primary Traffic Rate (Format A, see...) Rate / Rate / Not Used Secondary Traffic Rate 0 Rate / Rate / Rate / Rate / N/A Rate / N/A 0 Rate / Not Used Rate / N/A... Segmented RLP Data Frames Segmented RLP data frames carry a variable number of data octets, using a length field to indicate the number of octets. This type of data frame shall be used only to carry retransmitted RLP data frames (see..). Note that the most significant bit of the CTL field of a control frame and a segmented data frame is always set to. -

63 TIA/EIA/IS-0-A. Field Length (bits) SEQ CTL LEN 0 or Data Padding 0 or xlen Variable 0 0 SEQ - RLP data frame sequence number. See... CTL - RLP frame type. For segmented RLP data frames, the CTL field is defined as follows: First Segment. Contains the first LEN octets of the segmented RLP data frame Second Segment. Contains the next LEN octets of the segmented RLP data frame Last Segment. Contains the last LEN octets of the segmented RLP data frame. 0 - RLP Intersegment Fill Frame. When Multiplex Option is used, RLP Intersegment Fill Frames can be sent before or between segmented RLP data frames (see..). RLP Intersegment Fill Frames are not used for Multiplex Option. LEN - Data length. When CTL is set to 000, 00, or 00, the LEN field may be any value in the range from to the maximum allowable for the RLP frame, or, whichever is less. Values of the maximum allowable data length (MAX_LEN) are as given in Table...-. When CTL is set to 0 the LEN field shall not be included. Data - Data octets. When CTL is set to 000, 00, or 00, this field shall carry LEN Data octets. When CTL is set to 0 the Data field shall not be included Padding - Padding bits. As required to fill the remainder of the frame. These bits shall be set to Rate / and Rate / Intersegment Fill Frames For Multiplex Option, Rate / primary traffic RLP frames and Rate / secondary traffic RLP frames may be Intersegment Fill frames. -

64 TIA/EIA/IS-0-A. Field Length (bits) SEQ FCS ISF 0 SEQ - RLP data frame sequence number. See... FCS - Frame Check Sequence. This field is identical to the FCS field of an RLP idle frame with matching SEQ field. See... ISF - Intersegment Fill frame indicator. The value indicates an Intersegment Fill frame.... Primary Traffic For RLP frames carried on full rate primary traffic frames, two special frame formats described in... and... shall be used. For RLP frames carried on half-rate or quarter rate frames, RLP data frames or RLP control frames, as defined in.. and..., apply directly.... Rate RLP Frame Format A IS- full rate primary traffic frames of format A can carry either RLP data frames or RLP control frames, as defined in.. and... For Multiplex Option, full rate format A frames are defined as follows: Field Length (bits) Information TYPE 0 Information - RLP control or data frame. Formatted according to the RLP control and data frames described in.. and... TYPE - Frame type. The TYPE field shall be set to '00'. For Multiplex Option, full rate format A frames are defined as follows: Field Length (bits) Information TYPE -

65 TIA/EIA/IS-0-A. Information - RLP control or data frame. Formatted according to the RLP control and data frames described in.. and... TYPE - Frame type. The TYPE field shall be set to Rate RLP Frame Format B For Multiplex Option, format B carries 0 octets of data, as follows: Field Length (bits) SEQ Data 0 TYPE 0 SEQ - Frame sequence number. See.. and... Data - Data octets. This field shall contain 0 octets of data. TYPE - Frame type. The TYPE field shall be set to 00. For Multiplex Option, format B carries octets of data, as follows: Field Length (bits) SEQ Data TYPE 0 SEQ - Frame sequence number. See.. and... Data - Data octets. This field shall contain octets of data. TYPE - Frame type. The TYPE field shall be set to 0... RLP Idle Frames For Multiplex Option, Rate / RLP frames are RLP idle frames. For Multiplex Option, Rate / primary traffic RLP frames and Rate / secondary traffic RLP frames may be RLP idle frames. Higher rate RLP data frames with zero length (LEN = 0) (see...) are also RLP idle frames, and may be sent as an alternative. -

66 TIA/EIA/IS-0-A. Field Length (bits) SEQ FCS Padding 0 or 0 SEQ - RLP frame sequence number. This field is set to the current value of V(S) (see.. and..). FCS - Frame Check Sequence based on a modified Nordstrom-Robinson code. Let the sequence number to be coded be denoted as ( X X X X X X X X 0 ) Let the FCS be denoted as ( Y Y Y Y Y Y Y Y 0 ) The FCS is generated as follows: Y 0 = X X X 0 X X ( X 0 X ) ( X X X X ) ( X X ) ( X X ) Where denotes modulo- addition. Code bits Y through Y are found by cyclically shifting X 0 through X. In other words, X ( i + j) mod is substituted for X i in the generating equation for Y j. Y is a parity bit over the previous bits. 0 The final step in generating the FCS is to complement the last three bits. A table specifying the code is provided in Table..-. Pad - Padding bits. As required to fill the remainder of the frame. These bits shall be set to 0. Table..- presents the modified Nordstrom Robinson code used to protect Rate / and Rate / RLP idle frames. In Table..-, the most significant byte in a word is the SEQ value to be protected and the least significant byte is the FCS. All numbers are hexadecimal. -0

67 TIA/EIA/IS-0-A Table..-. Modified Nordstrom Robinson Code 000 0f 0ee 0 0 a0c c0 e0b 0d ab a ce efd 0a0 d b d df a c ea 0a be d ac cf e 0c a f b a cd ee0 0f a b c 00 ada cc e 0c c f 0 ab ca ee 0 0 eb ec a0f c e 0a 0 d a e af c ed 0c cf b a ab0 cc e0 0a a ac a0e a0 aaea cabc ea 0bf b b0 be b abc cbf ebb 0c cfc c c ce ac ccfb ec 0de d d0b dd dd ad cd edae 0eaf eb e eb ed0 ae ce eecd 0f f fde fd fa aff cfa ef 0bd 0e 00 0c 0c b0 d0 f0ba e db f d b da f0 b e bf de fd e 0 c b bb d0 fce 0 a b bef ddc f0 e f f bc da f fa f ac b d0 fd dd c0 a ba dbf f b a f0 bd df fc c fe b0a d fe acc a a aff ab ba daa fa0 bf bd baa b b0 bbad dbd fb cd c0d ce cca ca bc dc fcb d dbb ded d0 d bdc dd fdf e0 ee e e ed bee dee feb fb fe f f fcb bf df0c fff -

68

69 Data Service Options for Spread Spectrum Systems: AT Command Processing and the R m Interface TIA/EIA/IS-0-A. (PN-.) Ballot Resolution Version March

70 Copyright TIA

71 TIA/EIA/IS-0-A. CONTENTS INTRODUCTION AND OVERVIEW General Description Terms References... - REQUIREMENTS FOR THE Rm INTERFACE Physical Layer Electrical Mechanical Data Service Selection Service Selection for Async Data and Fax Services Service Selection for Packet Data Services Control Functions Rm Interface Protocol Options Service Selection for STU-III Service... - GENERAL REQUIREMENTS FOR AT COMMAND PROCESSING... - AT COMMAND PROCESSING FOR ASYNC DATA AND FAX SERVICES General Requirements Basic AT Command Processing Parameters S-Registers Action Commands Call-Control Command Processing Dial Modifiers Basic Result Codes Service Class.0 AT Commands Facsimile Parameters Description Special Processing Requirements FHS FIS FLP... - i

72 TIA/EIA/IS-0-A. CONTENTS FSP FMI, +FMM, +FMR FPP FPS Facsimile Action Commands Responses Embedded Commands AT Command Set Extensions for Modem Control General Requirements Cellular Extensions to ANSI/TIA/EIA Return to Online Command State Report Dropped Fax Line Facsimile Voice-Request Command Extensions to ANSI/TIA/EIA- for Long Lines Cellular Command Format Cellular AT Command Processing AT+CXT Command Processing AT+CFG Command Processing AT+CAD Command Processing AT+CRM Command Processing AT+CBC Command Processing AT+CQD Command Processing AT+CRC Command Processing AT+CHV Command Processing AT+CDV Command Processing Cellular Identification AT Command Processing AT+CMIP Command Processing AT+CBIP Command Processing AT+CMUX and AT+CSO Command Processing... - AT COMMAND PROCESSING FOR THE PACKET DATA SERVICES AT Command Processing AT Command Processing for Packet Data Services... - ii

73 TIA/EIA/IS-0-A. CONTENTS Basic AT Parameters Basic S-Registers Basic Action Commands Extended AT Configuration Commands Basic Result Codes Extended AT Configuration Commands CDMA AT Parameter Commands Packet Specific AT Commands Packet-Specific Cellular Response Codes Optional AT Commands... - AT COMMAND PROCESSING FOR THE STU-III SERVICES AT Command Processing for STU-III Service Control AT Command Parser States STU-III Service Rate Change... - AT COMMAND FORMATS Basic AT Commands Basic AT Parameters Basic S Registers Basic Action Commands Basic Result Codes ANSI/TIA/EIA- Control Extended AT Commands Facsimile Service Class.0 AT Commands Facsimile Service Class.0 Parameters Fax Action Commands Cellular Extensions AT Commands CDMA AT Parameters Cellular Result Codes... - APPENDIX A: IS-0 REFLECTION EXAMPLES Introduction Example : User Enters at+abc?+q?<cr> Verbose Mode... - iii

74 TIA/EIA/IS-0-A. CONTENTS.. Non-Verbose Mode EXAMPLE : User Enters ats0?+gmm<cr> Verbose Mode Non-Verbose Mode... - FIGURES Figure A.-. Sequence of Events for Command Responses...- iv

75 TIA/EIA/IS-0-A. TABLES Table..-. EIA/TIA--E Circuits...- Table..-. Result Code Sources...- Table..-. Embedded Command Types...- Table..-. Data Stream Transparent Commands...-0 Table..-. Single Character Commands...- Table..-. IWF to Mobile Station Commands...- Table..-. Mobile Station to IWF Commands...- Table..-. Basic AT Parameters...- Table..-. Basic S-Registers...- Table..-. Basic Action Commands...- Table..-. Basic Result Codes...- Table..-. In-Band Control AT Command...- Table.-. Extended AT Configuration Commands (Part of )...- Table.-. Extended AT Configuration Commands (Part of )...- Table.-. Extended AT Configuration Commands (Part of )...- Table.-. Extended AT Configuration Commands (Part of )...- Table.-. Extended AT Configuration Commands (Part of )...-0 Table..-. Fax Parameters (Part of )...- Table..-. Fax Parameters (Part of )...- Table..-. Fax Action Commands...- Table..-. CDMA AT Parameter Commands (Part of )...- Table..-. CDMA AT Parameter Commands (Part of )...- Table..-. CDMA AT Parameter Commands (Part of )...- Table..-. CDMA AT Parameter Commands (Part of )...- Table..-. Cellular AT Command Extensions in Support of Voice Services...-0 Table..-. Cellular Identification AT Command Extensions (Part of )...- Table..-. Cellular Identification AT Command Extensions (Part of )...- Table..-. Cellular AT Commands for Packet Data Services...- Table..-. Cellular Result Codes...- Table..-. Cellular Result Codes for Packet Data Services...- v

76

77 TIA/EIA/IS-0-A INTRODUCTION AND OVERVIEW. General Description This chapter of IS-0 provides requirements for the R m Interface, Service Selection methods, and AT Command processing required and optional for mobile stations and BS/MSCs.. Terms AT Command Set. Command set interface between data terminal equipment (DTE) and data circuit terminating equipment (DCE). Base Station. A station in the Domestic Public Cellular Radio Telecommunications Service, other than a mobile station, used for communicating with mobile stations. Depending upon the context, the term base station may refer to a cell, a sector within a cell, an MSC, an IWF, or other part of the cellular system. BS. See base station. Data Circuit-Terminating Equipment (DCE). A DCE connects a TE to the PSTN. A typical DCE would be a V-series modem. For Group- Fax Service, the DCE and its associated TE are often combined into a single Group- fax machine. Digital Facsimile. That form of facsimile in which densities of the original are sampled and quantified as a digital signal for processing, transmission, or storage. Error Correction Mode (ECM). A mode of operation for T.0 fax service providing end-toend reliable data transport. Facsimile. The process by which a document is scanned, converted into the electrical signals, transmitted, and recorded or displayed as a copy of the original. Fax. An abbreviation for facsimile. Group-. Digital Facsimile equipment per CCITT Recommendation T.. Interworking Function (IWF). An IWF provides the functions needed for terminal equipment connected to a mobile termination to inter-work with terminal equipment connected to the PSTN. A physical implementation may include a pool of modems. Mobile Station. A station in the Domestic 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. Mobile Termination (MT). An MT provides a non-isdn (R m ) user interface, e.g., CCITT V series or CCITT X series. Terminal Equipment (TE). A TE is a data terminal device that has a non-isdn usernetwork interface, e.g., CCITT V series or CCITT X series. -

78 TIA/EIA/IS-0-A. 0. References ANSI X.- Coded Character Set -Bit American National Standard Code for Information Interchange,. EIA/TIA--E Interface Between DTE and DCE Employing Serial Binary Data Interchange. EIA/TIA- Asynchronous Facsimile DCE control Standard - Service Class.0. EIA/TIA-0 Serial Asynchronous Automatic Dialing and Control. EIA/TIA-0 Facsimile DCE-DTE Packet Protocol Standard. EIA/TIA- Extensions to Serial Asynchronous Automatic Dialing and Control. T. Compression/decompression standard for facsimile applications. T.0 Facsimile protocol standard. ANSI/TIA/EIA- Inband DCE Control for Asynchronous DTE DCE Interfaces. TIA/EIA/IS- Data Transmission Systems and Equipment Extensions to Serial Asynchronous Dialing and Control. TIA/EIA/IS- Amendments to TIA- to Support T.0-. -

79 TIA/EIA/IS-0-A. REQUIREMENTS FOR THE Rm INTERFACE 0. Physical Layer The MT shall support the circuits of EIA/TIA--E over the R m reference point as described herein. The MT may also support other physical layer interfaces over the R m reference point. The MT should provide functionality equivalent to that defined by.. for alternative physical layer interfaces... Electrical The MT shall support the EIA/TIA--E circuits for each service as listed in Table..-. For the async data or fax service, the MT should support EIA/TIA--E circuit (Calling Indicator). Note: for the purpose of these circuits, TE is equivalent to Data Terminal Equipment (DTE) as defined in EIA/TIA--E; similarly, MT is equivalent to Data Circuit- Terminating Equipment (DCE). -

80 TIA/EIA/IS-0-A. Table..-. EIA/TIA--E Circuits Ckt Name Description Async & Fax Packet Data STU III 0 AB Signal Common Common ground reference for all circuits. 0 BA Transmitted Data Used to transfer data from the TE to the MT. 0 BB Received Data Used to transfer data from the MT to the TE. 0 CB Clear to Send Used by the MT to signal that the TE may transmit data. 0 CC DCE Ready Used by the MT to signal that it is ready to send or receive data. 0/ CD DTE Ready Used by the TE to signal that it is ready to send or receive data. 0 CF Received Line Signal Detector Used by the MT to indicate capability to transmit and receive data. CE Ring Indicator Used by the MT to signal alerting. CJ Ready for Receiving Used by the TE to signal that it is ready to receive data from the MT. R R R R R R R R R R O R O O R R O R R O O O O R R O O Note: Required signals are marked R while optional signals are marked O for each data service. 0.. Mechanical The MT may support interface connectors other than those specified in Section of EIA/TIA--E. An MT shall support the AT command set defined in EIA/TIA-0, with the modifications specified in this document. The mobile station may support extensions to EIA/TIA-0 directly or by means of the AT+CXT and AT+CFG commands.. Data Service Selection The AT+CRM parameter is used for all CDMA data services to select the service to be supported on the R m interface. All CDMA mobile stations supporting AT command -

81 TIA/EIA/IS-0-A processing on the R m interface shall support appropriate values of the +CRM command in accordance with Table Service Selection for Async Data and Fax Services The MT shall use the +CRM command to select async data or fax services, in accordance with Table..-. To select facsimile service, the MT shall use the +FCLASS command with a value consistent with facsimile service, in accordance with Table Service Selection for Packet Data Services... Control Functions The MT should provide a means for the user to control the features of the packet data service, including selecting the packet data service option. The control method may be provided either through a user interface on the MT or by means of a control protocol on the R m interface, such as an AT command protocol (see.). If no means for user control is provided, the default packet data service features shall be determined by the manufacturer. If packet data service is selected and the mobile station's service configuration permits connecting a packet data service option, the mobile station shall attempt to connect a packet data service option when it is requested. If packet data service is not selected, the mobile station shall not attempt to connect packet data service options.... R m Interface Protocol Options The MT may provide a means for the user to select the R m interface protocol option. The control method may be provided either through a user interface on the MT or by means of a control protocol on the R m interface, such as the AT+CRM command described in Table Service Selection for STU-III Service MTs shall use the AT+CRM command in accordance with Table..- to select STU-III service. State transitions of the STU-III service control function (see Section. of IS- 0.) are shown in Figure...- of IS-0.. If no means for user control is provided, and if STU-III service is supported, the STU-III service shall be selected at all times. Service selection methods for MT0s are left to the manufacturer. The MT may provide a means for the user to control the features of the STU-III service. The control method may be provided either through a user interface on the MT or by means of AT commands on the R m interface. If a means for user control is provided, the following features should be controllable: Multiplex Option. The AT+CMUX command can be used to set the multiplex option to be proposed during the service negotiation procedures for connecting a STU-III secure service option. See Section... of IS-0. for the requirements that -

82 TIA/EIA/IS-0-A. relate the STU-III service data rates (.,. and. kbps) to the choice of multplex option. Audio Pass Through. The AT+CAU command shall enable (or disable) the passing of analog audio signals to the TE. Service control. AT Commands used to provide STU-III service control in the MT are described in. The state transitions of the STU-III Service Control Function in response to these AT commands are shown in Figure..- of IS-0.. -

83 TIA/EIA/IS-0-A. GENERAL REQUIREMENTS FOR AT COMMAND PROCESSING AT commands and result codes sent on the R m interface shall be transmitted as ASCII characters, as defined in ANSI X.. -

84

85 TIA/EIA/IS-0-A AT COMMAND PROCESSING FOR ASYNC DATA AND FAX SERVICES. General Requirements The MT and the IWF emulate the functionality of a landline modem. Since the actual modems reside in the IWF, and the IWF does not store modem configuration information for all potential mobile users, each MT stores the desired configuration of the modem and transfers the configuration information to the IWF after call initiation. Upon establishment of the transport layer, the stored modem configuration is uploaded to the IWF which then implements the functionality of a regular landline modem. Since command and result timing may not be preserved on the U m interface, the MT also processes time dependent aspects of AT commands, such as result codes and time-dependent returns to online command state. This section describes how the mobile station and the IWF process AT commands. The AT commands can be generated by the TE when the mobile station is an MT or by an application when the mobile station is an MT0. Requirements for AT command processing in this section are written with the TE/MT reference model point of view. AT commands may be concatenated on a single command line as described in. of EIA/TIA-. All requirements stated for the R m interface should also be followed by the application interface (see. of IS-0.) in an MT0. MT AT application interface has two states: command state and online state. The MT is in command state when the transport layer is not in the ESTABLISHED state. When in command state the MT processes AT commands received on the R m interface. When the MT is in the online state, the MT passes all data received on the R m interface directly to the IWF, and does not process AT commands received on the R m interface. When the transport layer is in the ESTABLISHED state the IWF reflects all AT commands (following reception of the +CFG command) back over the U m interface to the mobile station, and the mobile station can process the reflected AT commands. The IWF application interface has command, online, and online command states, as defined in TIA/EIA-0. When in the command state or the online command state, the IWF may receive AT commands that are not implemented by the IWF. The handling of such unimplemented commands is described below. AT commands are classified as recognized or unrecognized. An AT command is considered recognized if it is defined for async data or G fax in this standard and complies with all requirements of the service in this standard. An unrecognized AT command is an AT command conforming with the syntax requirements of EIA/TIA- that is not defined for this service, or has a parameter value not mandated by this standard. In some special cases this standard requires that AT commands defined herein be processed in the same manner as an unrecognized command. Recognized AT commands are classified as local commands if they are processed only in the mobile station. Recognized AT commands are classified as remote commands if they are also processed by the IWF (see..). Remote commands are processed only by the MT when the MT is in command state. When the MT is in online state, remote -

86 TIA/EIA/IS-0-A commands are reflected to the MT on the U m interface and are processed by the MT as well as by the IWF. When an AT command line is issued, the entity processing it issues a Command Response. A Command Response may consist of zero or more lines of Information Text, followed by a Result Code. The mobile station and the IWF shall observe the following rules when processing AT commands:. When the MT is in the command state, the MT shall process valid AT parameter commands as follows: Store the parameter provided in a SET command (see EIA/TIA-), both for local and remote commands, return the parameter stored in its memory as the response to a READ command (see EIA/TIA-), both for local and remote commands, return the supported value range as the response to a TEST command (see EIA/TIA-) for local commands, and process the TEST command for a remote command as an unrecognized command (see..). The MT should not store fax parameters (see.) if FCLASS is not set to a value consistent with facsimile service.. When the MT is in the command state, the MT shall send the appropriate response on the R m interface only in response to AT commands received on the R m interface which do not cause the MT to change into the online state.. If the MT receives a SET parameter command (see EIA/TIA/) for a remote command over the R m interface while the MT is in command state, and the parameter value is not in the range mandated by this service, the MT shall process the command as an unrecognized command (see..).. When the MT is in the command state, and a command line received on the R m interface contains any unrecognized command, the MT shall process the entire command line as an unrecognized command. The MT shall process unrecognized AT commands in accordance with the setting of the AT+CXT parameter (see..). If the transport layer is established due to reception of an unrecognized command, the MT shall forward the entire command line to the IWF following the initialization string.. When the transport layer enters the ESTABLISHED state, the mobile station and IWF shall perform the following: When the transport layer enters the ESTABLISHED state, the IWF shall reset its configuration to the default settings. The MT shall transmit the values of remote parameters to the IWF immediately following the establishment of the transport layer connection, prior to the -

87 TIA/EIA/IS-0-A transmission of an ATD, ATA, or an unrecognized command (see.. and..). The MT shall use the AT commands defined herein to deliver this configuration to the IWF. These AT commands may be sent on multiple command lines, each of which contains one or more commands. The MT should omit parameters whose values are set to the default value and should omit the fax parameters (see.) if FCLASS is not set to a value consistent with facsimile service. The MT shall send the configuration string parameter, even if it is a null string, as set by the AT+CFG command (see..), as the last parameter in the initialization. The MT shall use the AT+CFG SET parameter command to deliver the configuration string parameter to the base station. The command line containing the AT+CFG command shall be terminated (i.e., no further AT commands can follow the AT+CFG command in the same command line). Regardless of the setting of the ATE parameter, for mobile-originated data calls (see.. of IS-0.) the IWF shall not echo the characters of the first AT command line received following the AT+CFG command. If extended cellular responses are enabled, the IWF should return a single extended cellular response CERROR: INIT FAILED (see Table..-) with the first offending AT command if it encounters errors processing the AT commands forming part of this configuration. If extended cellular responses are disabled, the IWF should return a single ERROR result code if it encounters errors processing the AT commands forming part of this configuration. The IWF should not return OK result codes for AT commands forming part of this configuration.. When the MT is in the online state, the MT shall forward all characters received on the R m interface to the IWF except for local flow control characters and local data stream transparent commands as specified in... The only processing the MT should perform when forwarding characters is guard time detection pertaining to a request to return to command state (see..).. When the MT is in the online state, the MT shall send the appropriate response on the U m interface in response to all AT commands received on the U m interface (see..).. When the IWF application interface is in the command state or the online command state, the IWF shall process all AT commands, and shall reflect all commands following the +CFG command back to the MT using the method of.. The configuration string is sent in the AT+CFG command, rather than as separate AT commands, because the AT+CFG command serves to indicate the end of the initialization string. These characters will already have been echoed by the MT while the MT was in the command state. -

88 TIA/EIA/IS-0-A The IWF shall respond to all received commands following the +CFG command with the appropriate response, via the U m interface. The MT shall send on the R m interface all received responses observing the timing requirements in EIA/TIA- 0. The IWF shall determine the response as follows: If the command is a local command or is unrecognized by the IWF, the response shall be the result code returned by the MT if the command was reflected to the MT. In all other cases, the IWF shall return the response from the IWF processing of the command. 0. When the IWF receives a command line containing more than one command, it shall process the individual commands in the order they appear on the command line. The IWF shall process each command in sequence, in accordance with rules and, waiting for the response from the MT for each reflected command. The IWF shall send to the MT only a single response for the entire command line. Should processing of a command result in an error, processing shall be terminated, the remainder of the command line shall be ignored, and the ERROR result code shall be issued.. Basic AT Command Processing.. Parameters The MT and the IWF shall support the parameters specified in Table..-. The command &C requires the MT to assert CF when carrier is reported (see..) by the modem in the IWF. The command &D requires the MT to signal the IWF to transition the modem to online command state on the ON-to-OFF transition of circuit 0/ (CD) using the mechanism described in... The MT should remain in the online state. The command &D requires the MT to disconnect following the ON to OFF transition of circuit 0/. The MT should enter the command state. When the MT receives an ATZ (or ATZ0), on either the R m or U m interface, the stored configuration in the MT shall revert to the configuration specified by the default values given in this specification and the MT shall close the transport layer connection, if open, when the ATZ command is received. The MT may store multiple configurations which may be recalled by the ATZn command and forwarded to the IWF at call setup time, using the procedure specified above. When the MT receives an AT&F (or AT&Fn), on either the R m or U m interface, the stored configuration in the MT shall revert to the configuration specified by the manufacturer's It should be noted that the requirements of this standard do not guarantee that the mobile station and IWF process all commands in the same manner. -

89 TIA/EIA/IS-0-A factory default setting. The MT shall close the transport layer connection, if open, when the AT&F command is received... S-Registers The IWF may support the S-registers categorized as Remote in Table..-. The MT shall store the set of S-registers in accordance with Table..- as part of the stored configuration. For the purposes of this specification, S-registers are treated as parameters (see EIA/TIA-). The MT shall permit the TE to modify the stored S-register values using the ATSnn= SET command and read the stored S-register values using the ATSnn? READ command. The mobile station shall use standard EIA/TIA-0 commands when transferring S- register contents to the IWF. The use of register S0 is described in section of IS-0.. The READ and SET operations for register S shall be supported. Support of the TEST operation for register S is optional. IWF support of the pause before blind dial feature is optional. Register S is used by the IWF in accordance with EIA/TIA-0 to time-out a PSTN data call connection and send a NO CARRRIER result code on the U m interface. Register S is used by the IWF in multistage dialing to time the period of the, dial modifier. The IWF should support register S. Register S is used by the IWF as the period to detect a PSTN segment carrier and return carrier detection signaling to the MT. Register S is an extension to EIA/TIA-0. Register S0 is used by the IWF in accordance with EIA/TIA-0 to determine the maximum time to remain connected to the PSTN line after detecting the absence of received line signal. If register S0 is set to, the IWF assumes a carrier is always present. Support of register S is optional... Action Commands The MT and IWF shall support the action commands defined by EIA/TIA-0, and shown in Table..-. When the MT is in the command state, the mobile station shall process the A/ command. Otherwise, the IWF shall process the A/ command. The IWF shall process the repeated command line as if received on the U m interface, including the reflection and result code processing described in.. The IWF shall not return any part of the initialization string (see.) in response to an A/ command... Call-Control Command Processing AT call control commands are described in Table..-. -

90 TIA/EIA/IS-0-A Upon receiving an ATD or ATA on the R m interface, the MT shall perform the processing required in.. of IS-0... However, if an ATD without a dial string is received and a service option has been connected, the MT should initiate service negotiation procedures as indicated in.. of IS-0-A.. Upon receiving this ATD command, the IWF shall generate and send T.0 CNG tone if the initial call was mobile originated and an AT+FCLASS.0 has been received. After sending an ATD with a dial string or ATA command to the IWF, the MT shall enter the online statethe MT shall remain in the online state while the transport layer connection is in the ESTABLISHED state. While in the online state, the MT shall forward all characters received on the R m interface to the IWF, except as specified elsewhere. When the MT is in the online state, the MT shall support at least one method of detecting a TE request to change the IWF to online command state. The MT should detect a request to change to online command state, such as receiving +++ with the appropriate guard times. When the MT detects a request to change to online command state, it shall signal the IWF to change to online command state using the Cellular Escape command (see Table..-). When the IWF receives an ATH command, it shall return the result code and shall then close the transport layer, following the procedures of. of IS-0.. Closing the transport layer shall place the MT in command state. If the MT receives an ATH command while in command state, it shall issue the OK result code on the R m interface... Dial Modifiers If the, modifier appears in the dial string, the MT shall forward the, modifier to the IWF. The IWF should use the value of register S as the delay time between the previous and subsequent digit dialing. If the W modifier appears in the dial string, the MT shall forward the W modifier to the IWF. If the IWF does not detect a second dial tone before a preset time-out (implementation dependent), the IWF should return a NO DIALTONE result code. If the IWF detects a second dial tone, the IWF should process the subsequent characters in the command string. If modifier appears in the dial string, the MT shall forward modifier to the IWF. If the IWF does not detect a five second silence period within the time specified in register S, the IWF should return a NO ANSWER result code. If the IWF detects a five With the appropriate setting, software flow control commands and FAX local data stream transparent commands are not forwarded in the online state. Other mechanisms are dropping circuit 0/ and break. Implementation note: many applications rely on transmission of +++. To avoid losing commands issued immediately after the result code is received, the implementation should ensure that the closure of the transport layer occurs as soon as possible after the transmission of the result code. One method for minimizing the delay is to set the FIN bit in the TCP segment containing the result code. -

91 TIA/EIA/IS-0-A. 0 second silence period within the time specified in register S, the IWF should process the subsequent characters in the command string. If the! modifier appears in the dial string, the MT shall forward the! modifier to the IWF. If this dial modifier is supported, the base station should generate a hook flash or equivalent as a result of this dial modifier. If the $ modifier appears in the dial string, the MT shall forward the $ modifier to the IWF. The IWF should wait for a billing tone before processing the subsequent characters in the command string. If the ; modifier appears in the dial string, the MT shall forward the ; dial modifier to the IWF. The IWF modem shall enter the online command state after dialing... Basic Result Codes The MT and IWF shall support the basic result codes of Table..-. Sources for each result code are shown in Table..-. The IWF shall encapsulate result codes (see Table..-) for transmission over the U m interface using the method defined in... The MT shall decapsulate the result codes and transmit them over the R m interface observing the timing requirements in EIA/TIA- 0. Table..-. Result Code Sources Result Code OK CONNECT <rate> RING NO CARRIER ERROR NO DIALTONE BUSY NO ANSWER Source MT, IWF IWF IWF IWF, MT MT, IWF IWF, MT IWF IWF, MT 0 The ERROR result code shall be returned for all commands which do not comply with the syntax rules of. of EIA/TIA- or Section of EIA/TIA-0.. Service Class.0 AT Commands Service Class.0 AT commands are taken from EIA/TIA- and TIA/EIA/IS-. Mobile stations and IWFs conforming with this standard shall support these command sets for Service Class.0. -

92 TIA/EIA/IS-0-A... Facsimile Parameters... Description The mobile station and the IWF should support the parameters listed in Table..-. The parameters listed in Table..- should be part of the stored configuration maintained by the MT.... Special Processing Requirements FHS For a fax call, the IWF shall send this parameter (via the procedure in.) to the mobile station prior to closing the transport layer connection. If the transport layer connection aborts, the mobile station shall set +FHS to 0x0, 0x0, or 0x0 when the abort occurs in Phase A, Phase B, or Phase C respectively (see.. of EIA/TIA-). The mobile station shall support all values of this parameter. The IWF shall use the SET command construct to set the value of this parameter in the mobile station using the mechanism of.., and shall not issue a result code to the mobile station.... +FIS The mobile station and the IWF shall copy the value of the +FCC parameter to the +FIS parameter whenever a new value is set for the +FCC parameter. At the end of a fax call the mobile station shall set the value of the +FIS parameter to the current value of the +FCC parameter.... +FLP If +FLP is set to, the IWF shall send the mobile station a SET command setting +FLP to 0 immediately after the successful transmission of the fax and prior to closing the transport layer connection. The IWF shall use the SET command construct to set the value of this parameter in the mobile station using the mechanism of.., and shall not issue a result code to the mobile station.... +FSP If +FSP is set to, the IWF shall send the mobile station a SET command setting +FSP to 0 immediately after the successful reception of the fax and prior to closing the transport layer. The IWF shall use the SET command construct to set the value of this parameter in the mobile station using the mechanism of.., and shall not issue a result code to the mobile station.... +FMI, +FMM, +FMR The mobile station shall process +FMI, +FMM, and +FMR as unrecognized commands. The IWF shall process +FMI, +FMM, and +FMR as remote commands. -

93 TIA/EIA/IS-0-A FPP Support of packet protocol (see EIA/TIA-0) is optional. Support of the value for +FPP is optional.... +FPS Support of the values and for +FPS are optional. The IWF shall send a SET command to the mobile station for this parameter whenever it changes its value and prior to closing the transport layer connection. The IWF shall use the SET command construct to set the value of this parameter in the mobile station using the mechanism of.., and shall not issue a result code to the mobile station... Facsimile Action Commands The MT and the IWF should support the facsimile action commands listed in Table..-. If the MT receives a +FDR or +FDT prior to having sent a dialing command to the IWF, the MT shall return an ERROR result code. If the TE issues a +FKS command and the MT is in command state, the MT shall issue the OK result code without further processing... Responses The format of AT command responses to all AT+F commands should be as specified in EIA/TIA-... Embedded Commands There are four types of embedded commands, as shown in Table..-. Table..- lists the data stream transparent commands and their types. Table..- lists the single character commands and their types. Table..-. Embedded Command Types Type To Remote From Remote To Local From Local Interpretation Passed transparently from the TE to the IWF. The MT performs no processing. Passed transparently from the IWF to the TE. The MT performs no processing. Processed and removed from the data stream by the MT. Generated by the MT for processing by the TE. -

94 TIA/EIA/IS-0-A. Table..-. Data Stream Transparent Commands Command Description Type <DLE><DLE> <DLE><SUB> <DLE><mps> <DLE><eom> <DLE><eop> <DLE><pri> <DLE><bc?> <DLE><ETX> <DLE><ETX> <DLE>< A > <DLE>< W > <DLE><ovr> <DLE><?> <DLE><vr0> <DLE><vr> <DLE><ln0> <DLE><ln> <DLE><ln> <DLE><wd0> <DLE><wd> <DLE><wd> <DLE><wd> <DLE><wd> <DLE><df0> <DLE><df> <DLE><df> <DLE><df> <DLE><DC> <DLE><rb0> <DLE><rb> <DLE><rb> <DLE><rb> DLE Transparency Substitute one 0x0 pattern Substitute two 0x0 patterns Transmit Commands End of page, more to follow End of document End of document and session Request procedure interrupt Check buffer credit Acknowledge <CAN> Receive Commands End of page <SOH> in packet data <ETB> in packet data Overrun error marker Requests MT to report TX Buffer Status Transmit Data Format Vertical resolution normal Vertical resolution fine A length B length Unlimited length pels / mm width 0 pels / mm width pels / mm width pels / mm width pels / 0 mm width -D Modified Huffman -D Modified Read -D Uncompressed -D Modified Modified Read Receive Buffer Status Buffer is empty Buffer is 0-0% full Buffer is 0-0% full Buffer is 0-0% full Buffer is 0-00% full Note. Support of procedure interrupt is optional. To Remote or From Remote To Remote or From Remote To Remote To Remote To Remote To Remote for further study To Remote From Remote From Remote From Remote From Remote for further study To Remote To Remote To Remote To Remote To Remote To Remote To Remote To Remote To Remote To Remote To Remote To Remote To Remote To Remote From Local From Local From Local From Local From Local From Local -0

95 TIA/EIA/IS-0-A. Table..-. Single Character Commands Command Description Type <DC> Indicates ready to receive Phase C data. To Remote <? > Requests IWF to report transmit buffer status. To Remote <CAN> Requests mobile station to stop delivering Phase C data. From Remote <CAN> Requests IWF to stop delivering Phase C data. To Remote AT Command Set Extensions for Modem Control.. General Requirements Certain AT commands and all AT result codes are time-sensitive. Since timing is not preserved over the U m interface, a modem control channel is implemented between the mobile station and the IWF. The modem control channel also carries the state of modem control signals between the MT and IWF. Additionally, because the MT is unaware of any AT commands present in the R m data stream while the transport layer connection is in the ESTABLISHED state, a means to deliver local AT commands issued by the TE to the MT is required. This shall be done by reflecting AT commands received by the IWF back to the MT using the formats specified below. The mobile station and the IWF shall support the inband modem control procedures defined in ANSI/TIA/EIA-, including the cellular extensions, as described below. The escape character shall be 0x. Any 0x characters in the input stream shall not be escaped. The character set 0x0-0xE shall be used to build valid in band commands. Processing of ANSI/TIA/EIA- inband commands is part of the application interface layer. Reflected AT commands shall be carried by the AT Cmd construct shown in Table..-. Information text sent from the MT to the IWF shall be carried by the appropriate result code construct as shown in Table..-. Responses delivered from the IWF to the MT shall be carried by zero or more instances of the extend/0x construct (see Table..-) followed by the STATUS report command, as described in.. of ANSI/TIA/EIA-. The MT shall then issue the response received from the IWF over the R m interface. Responses delivered from the MT to the IWF shall be carried by zero or more instances of the extend/0x construct (see Table..-) followed by the appropriate result code construct... Cellular Extensions to ANSI/TIA/EIA- The following extensions to ANSI/TIA/EIA- are employed for cellular use. -

96 TIA/EIA/IS-0-A Return to Online Command State This command shall be inserted into the data stream by the MT after it detects a time sensitive +++ or equivalent escape command. The IWF then processes this in band command, either directly, or by regenerating the time-sensitive instruction for use by existing modem equipment.... Report Dropped Fax Line When a Group- Facsimile is sent from a PSTN user to a mobile station, the air interface may provide a throughput below the PSTN rate. Thus, a buffer is required at the IWF since flow control is not possible. In the event the buffer overflows, the transmission can continue if the IWF drops scan lines when needed. This command informs the MT that a line has been dropped, allowing it to take appropriate action. Note: This technique is not required for fax transmission below 00 bps, or when the fax call utilizes ECM.... Facsimile Voice-Request Command This command is placed into the data stream by the MT in response to user input. The IWF should respond by issuing the appropriate T.0 procedure interrupt. The IWF may wait until the end of the transmission to generate the interrupt. Support of this command is optional.... Extensions to ANSI/TIA/EIA- for Long Lines ANSI/TIA/EIA- provides inband transmission of modem control commands over a serial interface, however there is a limitation ( characters) on the maximum size of a transmitted message. Because a command line or a response line could conceivably exceed this maximum size, ANSI/TIA/EIA- is extended herein for this case. When a command line, response line or result code is to be sent via ANSI/TIA/EIA- messages, the transmitting entity shall perform the following: If the length of the line is less than the maximum message size the transmitting entity shall send the line in a single ANSI/TIA/EIA- message using the appropriate extend code as shown in either Table..-, or Table..-. If the length of the line is greater than or equal to the maximum message size, the transmitting entity shall segment the line into as many maximum size segments as possible. Each maximum size segment shall be sent in order in a separate ANSI/TIA/EIA- message using the appropriate extend code. If there are remaining characters in the line after all maximum length segments have been sent, a ANSI/TIA/EIA- message of length less than the maximum shall be used as the final message in the line. If there are no remaining characters, an empty ANSI/TIA/EIA- message shall be sent. If the response format is set to verbose (the V parameter is set to ), the transmitting entity shall send an empty ANSI/TIA/EIA- response message prior to transmitting a response or result code. -

97 TIA/EIA/IS-0-A When the transmitting entity performs this procedure, it shall not send any intervening, independent ANSI/TIA/EIA- messages. When command lines, response lines or result codes are received via ANSI/TIA/EIA- messages, the receiving entity shall perform the following: If a message of size equal to the maximum length permitted by ANSI/TIA/EIA- is received, the receiving entity shall combine it with any previous maximum length messages of the same type (response or command). If a message of size less than the maximum length permitted by ANSI/TIA/EIA- is received, the receiving entity shall combine it with any previous maximum length messages of the same type to create a single line and perform one of the following: If the line is a response to an AT command, the receiving entity shall append a <CR><LF> to the line. If an empty line is received, the receiving entity shall interpret this as a <CR><LF> pair. If a result code is received while the receiving entity is in verbose mode (the V parameter is set to ), the receiving entity shall append a <CR><LF> pair to the result code. If a result code is received while the receiving entity is in non-verbose mode (the V parameter is set to 0), the receiving entity shall append a <CR> to the result code. The receiving entity shall then perform one of the actions described in Tables..- or..-. If the receiving entity is a mobile station and a result code is received, the mobile station shall combine the result code with the response line received earlier and send the composite response on the Rm interface. For examples of message processing using ANSI/TIA/EIA- inband commands see Appendix A... Cellular Command Format Each cellular extension command consists of an escape character, extend command character, a length octet and additional characters. The length octet specifies the size, in characters, of the Extended Command String. The length value ranges from 0x0 to 0xe, offset by 0xf ( decimal), corresponding to Extended Command String sizes of decimal to decimal. This cellular extension command format is illustrated here: <EM><extend><length><Extended Command String> When reflecting AT commands to the mobile station, the IWF shall omit the initial AT. Except for the omission of the initial AT for AT commands, AT command strings and result code strings sent using the cellular extension commands shall be formatted as required by EIA/TIA-0 and EIA/TIA-. Tables..- and..- give the set of hex codes used to support cellular extensions to ANSI/TIA/EIA-. -

98 TIA/EIA/IS-0-A. Table..-. IWF to Mobile Station Commands Command Sequence Hex Codes Mobile Station Action IWF Action <EM><extend0> <len> <AT Cmd> <0x><0x0> <len><0x> <string> Process command, generate Information Text on the U m interface. Use when reflecting AT commands. <EM><extend> <len> <0x><0x> <len><0x> Repeat previous fax line, or other method. Generate whenever a fax line is dropped. <FAX line dropped> <EM><extend> <len> <response characters> <0x><0x> <len><0x> <string> Wait for Result Code before processing next command and command line. Issue when mobile generates a response to a reflected AT command. -

99 TIA/EIA/IS-0-A. Table..-. Mobile Station to IWF Commands Command Sequence Hex Codes Mobile Station Action IWF Action <EM><extend> <len><escape> <0x><0x> <len><0x> Send in response to TE request to escape to online command state. Escape to online command state. <EM><extend> <len> <Voice Request> <0x><0x> <len><0x> Issue in response to user input. Issue T.0 voice request to participant fax terminal during phase D. <EM><extend> <len> <command unrecognized> <result code> <0x><0x> <len><0x> <string> Issue after receiving an unknown command on the U m interface. Send appropriate result code to the mobile station. <EM><extend> <len> <illegal parameter> <result code> <0x><0x> <len><0x> <string> Issue after receiving a known command with an illegal parameter. Send appropriate result code to the mobile station. <EM><extend> <len> <command valid> <result code> <0x><0x> <len><0x> <string> Issue after receiving and successfully processing a known command. Send appropriate result code to the mobile station. <EM><extend> <len> <long response> <0x><0x> <len><0x> <string> Issue when response is longer than one line, or insert an empty line. Wait for complete response before sending to the mobile station. 0. Cellular AT Command Processing The MT and the IWF shall support the AT command extensions and result codes for CDMA in accordance with Section.... AT+CXT Command Processing The AT+CXT command controls the handling of unrecognized commands by the MT. If the TE issues AT+CXT=0, the MT shall return the ERROR result code when it is in the command state and it receives an unrecognized AT command on the R m interface. If the TE issues AT+CXT=, the MT shall open a transport layer connection to the IWF if it receives an unrecognized command on the R m interface. After establishing the transport -

100 TIA/EIA/IS-0-A layer connection and transmitting the configuration information (see.), the MT shall send the unrecognized command to the IWF. The default mode on power on is AT+CXT=0... AT+CFG Command Processing If a configuration string has been specified via the AT+CFG command, the mobile station shall send the string to the IWF immediately after all other stored configuration data (see. and.)... AT+CAD Command Processing The mobile station shall return result codes (see Table..-) indicating the presence of analog or digital service. This is a local command. AT+CAD is a read-only parameter command... AT+CRM Command Processing Allows the user to set the protocol on the R m interface. The default value, 0, allows async data and fax service. A mobile station may return ERROR if provided with a value that is not within the valid range... AT+CBC Command Processing The mobile station shall return responses (see Table..-) indicating battery status. This is a local command. AT+CBC is a read-only parameter command... AT+CQD Command Processing Allows the user to set the command state inactivity timer (see.. of IS-0. or.. of IS-0-A.)... AT+CRC Command Processing The command enables or disables cellular result codes. Support of cellular result codes is optional... AT+CHV Command Processing The AT+CHV command should only be used to release a call initiated through the AT+CDV command. If the MT receives AT+CHV while in the online state, it shall return the OK result code and shall take no further action... AT+CDV Command Processing When in the command state, the MT shall examine the dial string argument of the AT+CDV command and proceed as follows: If the dial string contains no dial modifiers (see..), the MT shall initiate a voice call, using the dial string as the dialed digits. If the dial string contains any of the following dial modifiers, W,,, and $, the MT should transmit an Origination Message containing a voice service option with -

101 TIA/EIA/IS-0-A the DIGIT_MODE field set to, the NUMBER_TYPE field set to 000, and the NUMBER_PLAN field set to 0000 and shall send the dial string in the Origination Message (and possibly Origination Continuation Message) as the dialed digits. If the dial string contains any other dial modifiers, the MT shall return the ERROR result code. When in the online state, the MT shall return the ERROR result code in response to an AT+CDV command...0 Cellular Identification AT Command Processing The +C commands shown in Table..- take the same arguments as the +G commands taken from TIA/EIA/IS-, except the +C commands are remote and therefore provide information about the IWF. Support for the Cellular Identification AT commands is optional... AT+CMIP Command Processing The mobile station shall return the mobile station s temporary IP address as a character string in the dotted decimal Internet format as defined in RFC, followed by a final result code. If this command is issued when a temporary IP address has not been assigned, the mobile station shall return only a final result code. AT+CMIP is a read-only parameter command. For example, if the temporary IP address is the -bit hexadecimal number 0xc00fe, the mobile station returns:... OK.. AT+CBIP Command Processing The mobile station shall return the IWF IP address as a character string in the dotted decimal Internet format as defined in RFC, followed by a final result code. If this command is issued when the Transport Layer is not in the ESTABLISHED state, the mobile station shall return only a final result code. AT+CBIP is a read-only parameter command. For example, if the IWF s IP address is the -bit hexadecimal number 0xc00fe, the mobile station returns:... OK.. AT+CMUX and AT+CSO Command Processing The AT+CSO and AT+CMUX commands may be used to select alternate service options or multiplex options which are valid within the context of the data service selected by the AT+CRM command. Other uses of these commands are for further study. -

102

103 TIA/EIA/IS-0-A AT COMMAND PROCESSING FOR THE PACKET DATA SERVICES. AT Command Processing The following requirements apply to an MT that supports an AT command protocol on the R m interface for packet data services. Support of an AT command protocol on the R m interface is optional. If the MT supports an AT command protocol on the R m interface, the AT command processing shall have three states for support of packet data service: command state, online state and online command state. In the command state, packet data service shall be in the Inactive State, and the MT shall process all data on the R m interface as AT commands or responses. In the online state, the MT shall process all data on the R m interface (except ANSI/TIA/EIA- in-band control data and software flow control characters, if software flow control is enabled) as packet data. In the online command state, packet data service shall be in the Active State, but the MT shall process all data from the TE as commands, and send responses to the TE. Data received from the IWF during online command state may be either discarded or retained in the MT. Data previously transmitted by the TE and buffered by the MT may be transmitted from the buffer to the IWF during online command state, or discarded, or transmission may be deferred until the MT enters online state. The AT+CRM parameter SET command (see Table..-) can be used to configure the R m interface to carry packet data service, and to enable the setting of any parameters specific to packet data service. The ATD or ATA command can be used to cause packet data service to enter the Active State. When the MT enters the online command state, it shall issue the OK result code. The MT shall enter the online state when any of the following occurs: The packet data service enters the Active State. The MT is directed by the user or the TE to enter online state from online command state. The MT interprets the ATO command as a request to enter online state from online command state. When the MT enters the online state, it should send the CONNECT result code to the TE. If PPP is implemented on the R m interface, the TE should interpret the CONNECT result code as an indication of physical layer establishment. If the MT supports circuit 0 and the &C parameter is set to '', the MT should assert circuit 0 when packet data service is in the Active State, and should deassert circuit 0 when packet data service is in the Inactive State. The TE should interpret the assertion of circuit 0 as an indication of physical layer establishment, and should interpret deassertion of circuit 0 as an indication of physical layer closure. The MT shall enter the online command state from the online state when directed by the user or TE. -

104 TIA/EIA/IS-0-A A means should be provided for the TE to direct the MT to enter the command state. The MT shall enter the command state when the packet data service enters the Inactive State. The packet data service shall enter the Inactive State, when any of the following occurs: The MT powers on or is reset. The AT+CRM or the AT+CPS parameter is changed. The MT is directed by the user or the TE to enter the command state from online command state. The MT interprets the ATH command as a request to enter the command state from online command state.. AT Command Processing for Packet Data Services The following AT processing applies when the +CRM parameter is set to a value specified for a packet data service option (see Table..-). All commands are processed in the MT... Basic AT Parameters MTs implementing AT command processing for packet data services shall support the required basic AT parameters in accordance with Table..-. If the &D parameter is set to, and the MT is in the online state, the MT shall enter the online command state following ON to OFF transition of circuit 0/. The packet data service shall remain in the Active State. If the &D parameter is set to, and the MT is in the online state, the MT shall enter the command state following ON to OFF transition of circuit 0/. The packet data service shall enter the Inactive State. If the &C parameter is set to, the MT shall assert Circuit 0 (CF) when packet data service is in the Active State... Basic S-Registers The MT may support the Basic S registers in accordance with Table Basic Action Commands The MT shall support the Basic Action Commands of Table..-. When the ATA command is issued, the MT shall transition from the command state to the online state. Packet data service shall enter the Active State. When the ATD command is issued, the MT shall transition from the command state to the online state. Packet data service shall enter the Active State. The <dial string> parameter may be omitted from the ATD command when this command is used for packet data services. When the ATH0 command is issued, the MT shall transition from the online command state to the command state. This causes the packet data service to enter the Inactive State. -

105 TIA/EIA/IS-0-A When the ATO0 command is issued, the MT shall enter the online state from the online command state. Packet data service remains in the Active State... Extended AT Configuration Commands The MT shall support the Extended AT Configuration Commands in accordance with Table.-. If the +GCAP command is implemented, an MT conforming to this standard shall include as a minimum the string +CIS0P in the result code for the +GCAP command... Basic Result Codes The MT shall support the basic result codes in accordance with Table Extended AT Configuration Commands The MT shall support the Extended AT Configuration commands in accordance with Table.-... CDMA AT Parameter Commands The MT shall support the CDMA AT Parameter Commands in accordance with Table Packet Specific AT Commands The MT shall support the Packet Specific AT commands in accordance with Table Packet-Specific Cellular Response Codes The MT shall support the packet specific cellular response codes in accordance with Table..-.. Optional AT Commands For MTs implementing AT command processing, the extended AT configuration commands may be supported in accordance with Table.-. An MT conforming to this standard shall include the following item, as a minimum in the result code for the +GCAP command: +CIS0P. An MT conforming to this standard may support the +IBC parameter (See Table..-) for configuration of the inband control services of ANSI/TIA/EIA- on the R m interface. The AT+CSO and AT+CMUX commands may be used to select alternative service options or multiplex options which are valid within the context of the data service selected by the AT+CRM command. Other uses of these commands are for further study. -

106

107 TIA/EIA/IS-0-A AT COMMAND PROCESSING FOR THE STU-III SERVICES. AT Command Processing for STU-III Service Control Issuance of certain AT Commands on the R m interface cause STU-III service state transitions as specified in PN.. The AT+CDV command shall be used to connect a clear(i.e., unencrypted) voice service option over the air interface to the remote STU-III terminal. The AT+CHV command shall be used to release the call when a clear voice service option is connected. The ATH command shall be used to release the call when a STU-III secure service option is connected. The AT+CSO=<n> command shall be used to connect a STU-III secure service option when a clear voice service option is connected. The value of <n> in the AT+CSO command determines which of the STU-III secure service options is connected. The AT+CSO=<n> command shall be used to connect a clear voice service option when a STU-III secure service option is connected. The transitions between the clear and secure service options are part of the STU-III service call control function and are detailed in Section. of IS- 0.. The AT+CMUX=<n> parameter shall determine the initial proposed multiplex option during service negotiation procedures for connecting a STU-III secure service in accordance with Table AT Command Parser States The MT AT command processing shall have three states: Command State Online State Online Command State The following describes AT Command Parser state transitions for the STU-III services. For definitions of the service control function states, see. of IS-0.. When the STU-III service control function is in the Unselected Substate of the Inactive STU- III State or the Selected Substate of the Inactive STU-III State or the Clear Voice Substate of the Inactive STU-III State, the STU-III MT AT command parser shall enter the Command State and Circuit 0/ (CD) can be either asserted or de-asserted. When the STU-III service control function enters either the Secure Transparent Substate of the Active STU-III State or the Secure Non-Transparent Substate of the Active STU-III State, the STU-III MT AT command parser shall enter the Online State. This state transition occurs when the MT detects the assertion of Circuit 0/ (CD) in the STU-III service invocation procedures described in Section.. of IS-0.. When the STU-III service control function is either in the Secure Transparent Substate of the Active STU-III State or in the Secure Non-Transparent Substate of the Active STU-III State, the STU-III MT AT command parser shall enter the Online Command State when the MT detects that Circuit 0/ (CD) is de-asserted. The STU-III MT AT command parser shall enter the Online State if the STU-III service control function remains in either -

108 TIA/EIA/IS-0-A. 0 0 the Secure Transparent Substate of the Active STU-III State or the Secure Non-Transparent Substate of the Active STU-III State and when Circuit 0/ (CD) is reasserted. While in the Online Command State, if the STU-III service control function transitions to either the Clear Voice Substate of the Inactive STU-III State (as a result of issuing the AT+CSO= command) or to the Selected Substate of the Inactive STU-III State (as a result of issuing the ATH command), the STU-III MT AT command parser shall enter the Command State... STU-III Service Rate Change While a STU-III secure service option is connected, a STU-III service rate different from the service rate being used may be negotiated by the STU-III terminals using the protocols specified in FSVS-0 (see IS-0.). This may happen as a result of a user request. If a STU-III secure service option is connected and a STU-III service rate is requested that requires a change in the multiplex option, the TE first issues the AT+CMUX <n> command with a new parameter value corresponding to the desired multiplex option. Subsequently, the TE issues the AT+CSO <n> (where n is a STU-III secure service option) command to connect the STU-III secure service option with a different multiplex option. When the MT receives an AT+CSO <n> command and the service configuration indicated by the AT+CSO and AT+CMUX commands is different from that currently established, the mobile station shall perform service negotiation to establish a service configuration including the STU-III secure service option and the multiplex option indicated by the stored AT+CMUX parameter. The MT shall return a CONNECT result code in response to succesful execution of the AT+CSO command during the STU-III service invocation procedure (see Section.. of IS-0.). If the service configuration indicated by the AT+CSO and AT+CMUX commands is the same as that currently established (i.e., the service configuration remains unchanged), the MT shall not engage in further service negotiation but the MT shall return the CONNECT result code in response to the AT+CSO command. -

109 TIA/EIA/IS-0-A. AT COMMAND FORMATS. Basic AT Commands.. Basic AT Parameters Table..- specifies the basic AT parameters to be supported for the CDMA data services. Exceptions to EIA/TIA-0 are indicated in Table..- by square brackets. Default settings are shown in bold. -

110 TIA/EIA/IS-0-A. Table..-. Basic AT Parameters E0 E Description Do not echo commands in command state or online command state. Echo commands in command state or online command state. Async & Fax Packet Data Parameter STU- III R,M O N/A R,M O N/A L0 Low speaker volume. R,L N/A N/A L Low speaker volume. R,L N/A N/A L Med speaker volume. R,L N/A N/A L High speaker volume. R,L N/A N/A M0 Speaker off. R,M N/A N/A M Speaker on until carrier reported (support of this feature is optional). R,M N/A N/A Q0 Return result codes. R,M R R Q Do not return result codes. R,M R N/A V0 Display result codes as numbers. R,M R R V Display result codes as words. R,M R R X X X Enable additional result code CONNECT <rate>. Disable dial tone and busy detection. R,M N/A N/A Enable additional result codes CONNECT <rate> and NO R,M N/A N/A DIALTONE. Disable busy detection. Enable dial tone detection. Enable additional result codes CONNECT <rate> and R,M N/A N/A BUSY. Enable busy detection. Disable dial tone detection. X Enable additional result codes CONNECT <rate>, BUSY R,M N/A N/A and NO DIALTONE. Enable busy and dial tone detection. Z0 Reset to default configuration. R,L R N/A &C0 Circuit 0 (CF) always ON. R,L R N/A &C Circuit 0 (CF) ON in accordance with the specified service. R,L R N/A &D0 Ignore circuit 0/ (CD). R,L R N/A [&D] &D Enter online command state following ON-to-OFF transition of circuit 0/. See service specific AT command processing for service state transitions. Enter command state following On to Off transition of circuit 0/. See service specific AT command processing for service state processing requirements. R,L R N/A R,L R N/A T Select tone dialing. R,M N/A N/A P Select pulse dialing. R,M N/A N/A &Fn Set to factory-defined configuration n. Effect is implementation dependent. R,L O N/A Note. For async data or fax settings, the dial tone detection settings do not apply. Legend: R=Required, O=Optional, M=Remote AT Command, L=Local AT Command. -

111 TIA/EIA/IS-0-A... Basic S Registers Table..- specifies the basic S Registers to be supported for the CDMA data services. Exceptions to EIA/TIA-0 are indicated in Table..- by square brackets. Default settings are shown in bold. Table..-. Basic S-Registers Register Value Description Async & Fax Packet Data STU- III S0 0 [ to ] Disable automatic answering. [Enable automatic answering after (Value - ) seconds.] R,L N/A N/A S Carriage Return character. R,M O N/A S 0 Line Feed character. R,M O N/A S Backspace character. R,M O N/A S to 0 S to [0] S 0 to [S] 0 to S0 to [] [S] 0- Pause before blind dialing. R,M N/A N/A Number of seconds to establish end-to-end data connection. Number of seconds to pause when, is encountered in dial string. Carrier detect threshold in increments of 0. seconds. Number of tenths of a second from carrier loss to disconnect. [] [Disable carrier detect.] DTMF tone duration and spacing in milliseconds. R,M O N/A R,M N/A N/A R,M N/A N/A R,M N/A N/A O,M N/A N/A 0.. Basic Action Commands Table..- specifies the Basic Action Commands to be supported for the CDMA data services. Exceptions to EIA/TIA-0 are indicated in Table..- by square brackets. Default settings are shown in bold. -

112 TIA/EIA/IS-0-A. Table..-. Basic Action Commands Command Description A/ Re-execute previous command. A D<dial string> H0 O0 Enter the online state. See service specific processing for further details. Causes the MT to transition from the command state to the online state. The <dial string> is optional. For circuit switched data services, the dial string may contain the following characters: Digits 0 to, *, #, A, B, C, and D. The dial string may contain the following dial modifiers: T Tone dialing [ignore] P Pulse dialing [ignore], Pause during dialing W Wait for dial Wait for quiet answer! Hook flash [$] Wait for billing tone (for credit-card calls) ; After dialing, the IWF enters the online command state and maintains the connection Causes the MT to transition from online command state to command state. Use of the digit 0 is optional (see EIA/TIA-0). Causes the MT to transition from online command state to online state. Use of the digit 0 is optional (see EIA/TIA-0)... Basic Result Codes Table..- specifies the Basic Result Codes to be supported for the CDMA data services. Exceptions to EIA/TIA-0 are indicated in Table..- by square brackets. Default settings are shown in bold. The ERROR result code shall be returned for all commands which do not comply with the syntax rules of. of EIA/TIA-, or Section of EIA/TIA-0. -

113 TIA/EIA/IS-0-A. Table..-. Basic Result Codes Numeric Verbal Description Async & Fax Packet Data STU III 0 OK Command executed. R R R CONNECT <rate> Entering online state. R R R RING Alerting signal received from network. R N/A N/A NO CARRIER Unable to activate the service. R R N/A ERROR Command not recognized or could not be executed. NO DIALTONE No dial tone detected within time-out period. R R R R N/A N/A BUSY Reorder (Busy signal) received. R R N/A NO ANSWER Five seconds of silence not detected after ring back dial modifier is used. R N/A N/A.. ANSI/TIA/EIA- Control Table..-. In-Band Control AT Command Command Description Async & Fax Packet Data STU III +IBC In-Band Control Compound Parameter. The AT+IBC compound parameter provides for the enabling, disabling and configuration of In-Band Control Service. See Section of ANSI/TIA/EIA- for a complete description of this command. N/A O N/A. Extended AT Commands -

114 TIA/EIA/IS-0-A. Table.-. Extended AT Configuration Commands (Part of ) Command Value per Description Async & Fax Packet Data STU III +DR IS- Data Compression Reporting. This extendedformat numeric parameter controls whether or not the extended-format +DR: intermediate result code is transmitted from the IWF over the U m interface. +DS IS- Data Compression. This extended-format compound parameter controls the V.bis data compression function on the PSTN link if provided in the IWF. +EB IS- Break Handling in Error Control Operation. This extended-format compound parameter is used to control the manner of V. operation on the PSTN link (if present in the IWF). +EFCS IS- This extended-format numeric parameter controls the use of the -bit frame check sequence option in V. on the PSTN link (if present in the IWF). +ER IS- Error Control Reporting. This extendedformat numeric parameter controls whether or not the extended-format +ER: intermediate result code is transmitted from the IWF over the U m interface. +ES IS- Error Control Selection. This extendedformat compound parameter is used to control the manner of operation of the V. protocol on the PSTN link (if present in the IWF). +ESR IS- This extended-format numeric parameter controls the use of the selective repeat (SREJ) option in V. on the PSTN link (if present in the IWF). +ETBM IS- This extended-format compound parameter controls the handling of data remaining in IWF buffers upon service termination. R,M O N/A R,M O N/A R,M O N/A R,M N/A N/A R,M O N/A R,M N/A N/A R,M N/A N/A R,M O N/A -

115 TIA/EIA/IS-0-A. Table.-. Extended AT Configuration Commands (Part of ) Command Value per Description Async & Fax Packet Data STU III +GCAP IS- This extended-format command causes the MT to transmit one or more lines of information text in a specific format. The content is a list of additional capabilities command +<name>s, which is intended to permit the user of the MT to identify the minimum capabilities of the MT. R,L O N/A An MT conforming to this standard shall include the following items, as a minimum, in the result code for the +GCAP command: +CIS0, +MS, +ES, +DS, +FCLASS +GMI IS- This command causes the MT to transmit one or more lines of information text, determined by the manufacturer, which is intended to permit the user of the MT to identify the manufacturer. Typically, the text will consist of a single line containing the name of the manufacturer, but manufacturers may choose to provide more information if desired (e.g., address, telephone number for customer service, etc.). +GMM IS- This command causes the MT to transmit one or more lines of information text, determined by the manufacturer, which is intended to permit the user of the MT to identify the specific model of the device. Typically, the text will consist of a single line containing the name of the product, but manufacturers may choose to provide any information desired. R.L O N/A R.L O N/A The +CIS0 result code indicates support of the AT commands and result codes in Tables..-,..-,..-, and..-. -

116 TIA/EIA/IS-0-A. Table.-. Extended AT Configuration Commands (Part of ) Command Value per Description Async & Fax Packet Data STU III +GMR IS- This command causes the MT to transmit one or more lines of information text, determined by the manufacturer, which is intended to permit the user of the MT to identify the version, revision level or date, or other pertinent information of the device. Typically, the text will consist of a single line containing the version of the product, but manufacturers may choose to provide any information desired. +GOI IS- This command causes the MT to transmit one or more lines of information text, determined by the manufacturer, which is intended to permit the user of the MT to identify the device, based on the ISO system for registering unique object identifiers. Typically, the text will consist of a single line containing numeric strings delimited by period characters. +GSN IS- This command causes the MT to transmit one or more lines of information text, determined by the manufacturer, which is intended to permit the user of the MT to identify the individual device. Typically, the text will consist of a single line containing a manufacturer determined alpha-numeric string, but manufacturers may choose to provide any information desired. +ICF IS- TE-MT Character Framing. This extendedformat compound parameter is used to determine the local serial port start-stop (asynchronous) character framing that the MT shall use while accepting TE commands and while transmitting information text and result codes to the TE, if this is not automatically determined (see +IPR). R.L O N/A R.L O N/A R.L O N/A R.L R N/A -

117 TIA/EIA/IS-0-A. Table.-. Extended AT Configuration Commands (Part of ) Command Value per Description Async & Fax Packet Data STU III +IFC IS- TE-MT Local Flow Control. This extendedformat compound parameter is used to control the operation of local flow control between the TE and MT []. +ILRR IS- TE-MT Local Rate Reporting. This extended-format numeric parameter controls whether or not the extended-format +ILPR:<rate> information text is transmitted from the MT to the TE. +IPR IS- Fixed R m Rate. This numeric extendedformat parameter specifies the data rate at which the MT will accept commands, in addition to 00 bit/s or 00 bit/s (as required in EIA/TIA-0). It may be used to select operation at rates at which the MT is not capable of automatically detecting the data rate being used by the TE. +MA IS- Modulation Automode Control. This extended-format compound parameter is a list of modulations that the base station may use to connect with the remote DCE in Automode operation, for answering or originating data calls, as additional alternatives to the modulation specified in the +MS command. +MR IS- Modulation Reporting Control. This extended-format numeric parameter controls whether or not the extended-format +MCR:<carrier> and +MRR:<rate> intermediate result codes are transmitted from the IWF to the mobile station. +MS IS- Modulation Selection. This extended-format compound parameter is used to control the manner of operation of the modulation capabilities in the IWF. R.L R N/A R.L O N/A R.L R N/A R.M N/A N/A R.M N/A N/A R.M N/A N/A -

118 TIA/EIA/IS-0-A. Table.-. Extended AT Configuration Commands (Part of ) Command Value per Description Async & Fax Packet Data STU III +MVR IS- V. Reporting Control. This extendedformat numeric parameter controls whether or not the extended-format +MVR: result code is transmitted from the IWF to the mobile station. +MVS IS- V. Selection. This extended-format compound parameter is used to control the manner of operation of the V. capabilities (if present in the IWF). O,M N/A N/A O,M N/A N/A Note. TIA/EIA/IS- states that this command only applies when V. error control is being used, or when fallback to non-error control mode is specified to include buffering and flow control. In this standard this command applies independently of the use and setting of V.. If V. is not used or not configured appropriately data loss may occur.. Facsimile Service Class.0 AT Commands.. Facsimile Service Class.0 Parameters -0

119 TIA/EIA/IS-0-A. Table..-. Fax Parameters (Part of ) Parameter Value (per) Description Type +FAA EIA/TIA- Adaptive-answer parameter (see +FCLASS) +FAP TIA/EIA/IS- Addressing and polling capabilities parameter Remote Remote +FBO EIA/TIA- Phase-C data-bit-order parameter Remote +FBS EIA/TIA- Buffer size parameter (read-only) Local +FBU EIA/TIA- HDLC-frame-reporting parameter Remote +FCC VR [BR] WD [LN] [DF] [EC] BF ST [+FCLASS] EIA/TIA- 0 EIA/TIA- EIA/TIA- EIA/TIA- EIA/TIA- EIA/TIA- EIA/TIA- 0.0 DCE-capabilities parameters Vertical-resolution subparameter Bit-rate subparameter 00 bits/s 00 bits/s 00 bits/s 00 bits/s Page-width subparameter Page-length subparameter Data-compression-format subparameter Error-correction subparameter Binary-file-transfer subparameter Scan-time-per-line subparameter Service-class selection parameter Class-0 [Class- support unavailable] Class-.0 fax service (EIA/TIA-) Remote Remote +FCQ EIA/TIA- Copy-quality-checking parameter Remote [+FCR] EIA/TIA- Capability-to-receive parameter Remote +FCS EIA/TIA- Current-session results parameters Remote +FCT EIA/TIA- DTE Phase-C timeout parameter Remote +FEA EIA/TIA- Phase-C received EOL-alignment parameter Remote -

120 TIA/EIA/IS-0-A. Table..-. Fax Parameters (Part of ) Parameter Value (per) Description Type +FFC EIA/TIA- Format-conversion parameter Remote +FHS EIA/TIA- Call-termination-status parameter Remote +FIE EIA/TIA- Procedure-interrupt-enable parameter Remote +FIS EIA/TIA- Current-session negotiation parameters Remote [+FLI] EIA/TIA- Local-ID-string parameter (TSI or CSI) Remote +FLO EIA/TIA- Flow-control-select parameter Local +FLP EIA/TIA- Indicate-document-to-poll parameter Remote +FMI EIA/TIA- Request DCE manufacturer identification See... +FMM EIA/TIA- Request DCE model See... +FMR EIA/TIA- Request DCE revision See... [+FMS] EIA/TIA- Minimum-Phase-C-speed parameter Remote +FNR EIA/TIA- Negotiation-message-reporting control parameters Remote +FNS EIA/TIA- Nonstandard-frame FIF parameter Remote +FPA TIA/EIA/IS- Selective Polling Address Parameter Remote [+FPI] EIA/TIA- Local-polling-ID-string parameter Remote [+FPP] EIA/TIA- Packet-protocol-control parameter Local +FPR EIA/TIA- Serial-port-rate-control parameter Local [+FPS] EIA/TIA- Page-status parameter Remote +FPW TIA/EIA/IS- Password parameter (Sending or Polling) Remote [+FRQ] EIA/TIA- Receive-quality-threshold parameters Remote +FRY EIA/TIA- ECM-retry-value parameter Remote +FSA TIA/EIA/IS- Subaddress Parameter Remote [+FSP] EIA/TIA- Request-to-poll parameter Remote Notes. Use of option may cause degradations in the quality of certain faxes.. Some values for this parameter are optional in EIA/TIA-. In this standard, all parameters of this command shall be supported.. Class.0 represents EIA/TIA-.. Support of packet protocol is optional.. Values and of this parameter are optional... Fax Action Commands -

121 TIA/EIA/IS-0-A. -

122 TIA/EIA/IS-0-A. Table..-. Fax Action Commands Command Description Type +FDR Receive Phase-C data. Remote +FDT Transmit Phase-C data. Remote +FIP Initialize facsimile parameters. Remote +FKS Terminate session. Remote. Cellular Extensions AT Commands AT command lines containing the commands specified in Tables..-,..-, and..- start with AT and end with a carriage return. Default configurations appear in boldface type... CDMA AT Parameters Table..-. CDMA AT Parameter Commands (Part of ) Command Description Async & Fax Packet Data STU III +CXT=<value> +CFG= <string> +CAD? Cellular Extension. 0 Do not pass unrecognized commands to the IWF. When detecting an unrecognized AT command, open transport layer connection and pass unrecognized command to the IWF. Configuration String. The string (up to and including the termination character) will be stored by the MT and sent to the base station prior to dialing. Each transmission of an AT+CFG command from the TE replaces the contents of the previous string. The string may be up to characters. Query Analog or Digital Service. Returns: 0 if no service is available if CDMA Digital service available if TDMA Digital service available if Analog service is available (values - reserved) R,L N/A N/A R,L N/A N/A O,L O N/A -

123 TIA/EIA/IS-0-A. +CDR U m Interface Data Compression Reporting. This extended-format numeric parameter controls whether or not the extended-format +CDR: intermediate result code is transmitted by the MT. The result code is the same as for the TIA/EIA/IS- +DR: result code. R,L N/A N/A -

124 TIA/EIA/IS-0-A. Table..-. CDMA AT Parameter Commands (Part of ) Command +CDS +CRM=<value> +CBC? Description U m Interface Data Compression. This extended-format compound parameter controls the V.bis data compression function on the U m interface. The command format is the same as for the TIA/EIA/IS- +DS command. Set R m interface protocol. 0 Asynchronous Data or Fax Packet data service, Relay Layer R m interface Packet data service, Network Layer R m interface, PPP Packet data service, Network Layer R m interface, SLIP STU-III Service - Reserved for future use - Reserved for manufacturer specific use Note: The default value for the +CRM parameter shall be 0 if this value is supported by the MT. If 0 is not supported, the default +CRM value shall be manufacturer specific. Battery Charge. Read-only. Returns <BCS>,<BCL> BCS: 0 MT powered by battery, BCL = status MT connected to external power Battery status not available Recognized power fault. Calls inhibited. Async & Fax Packet Data STU III R,L N/A N/A R,L R R R,L O N/A BCL: 0-00 Remaining battery capacity is 0-00%. -

125 TIA/EIA/IS-0-A. Table..-. CDMA AT Parameter Commands (Part of ) Command Description Async & Fax Packet Data STU III +CQD=<value> Command State Inactivity Timer (see...). 0 Ignored - Release call after x<value> seconds have elapsed without activity. The default <value> shall be 0, corresponding to 0 seconds. +CRC=<value> Cellular Result Codes (see Table..-). 0 Disable Cellular Result Codes Enable Cellular Result Codes +CMIP? +CBIP? +CSS? Mobile Station IP Address. Read-only. Returns the mobile station s temporary IP address. Base Station IP Address. Read-only. Returns the base station s IP address. Serving System. Read-only. Returns <Band_Class>,<Band>,<SID> Band_class: 0 The current band class is unsupported by this command. 00 MHz Cellular. 00 MHz PCS. Band: A through F If the band is x, the mobile station is registered with an x-band system under the band class specified in <Band_class>. Z The mobile station is not registered. SID: 0- The mobile station is registered with the system indicated. The mobile station is not registered. R,M N/A N/A R,M N/A N/A R,L N/A N/A R,L O N/A R,L O N/A -

126 TIA/EIA/IS-0-A. Table..-. CDMA AT Parameter Commands (Part of ) Command Description Async & Fax Packet Data STU III +CSQ? Query Received Signal Quality. Returns the Signal Quality Measure <SQM> and the Frame Error Rate <FER> as follows: Signal Quality Measure <SQM> 0- Signal Quality Measurement (see Note ). SQM is not known or is not detectable. All other values are reserved. R,L O N/A Frame Error Rate <FER> 0 <0.0% 0.0% to less than 0.% 0.% to less than 0.% 0.% to less than.0%.0% to less than.0%.0% to less than.0%.0% to less than.0%.0% <FER> is not known or is not detectable. All other values are reserved. AT+CSO = <n> Change Service Option to Service Option <n>. O,L O,L R,L AT+CMUX = <fwd>,<rev> AT+CAU = <n> +CFC=<value> Select Multiplex Option <fwd> is the forward MUX option specified in hexadecimal format (e.g. 0A). <rev> is the reverse MUX option specified in hexadecimal format (note: if <rev> is omitted, it is assumed to have the same value as <fwd>) Audio passthrough between DTE and MT 0 Audio Pass Through Disabled Audio Pass Through Enabled U m Interface Fax Compression. 0 No compression V.bis compression with parameters as set by the +CDS command Modified Modified Read compression O,L O,L R,L N/A N/A R,L R,L N/A N/A -

127 TIA/EIA/IS-0-A. Note. The exact meaning of the Signal Quality Measure shall be manufacturer defined. The lowest quality reported by SQM shall be defined as value 00. The highest quality reported by SQM shall be defined as value. -

128 TIA/EIA/IS-0-A. Table..-. Cellular AT Command Extensions in Support of Voice Services Command Description Async & Fax Packet Data STU III +CHV<value> +CDV<dial string> Hangup Voice 0 Hangup voice call - Reserved Dial command for voice calls. The format of <dial string> is identical to that for the ATD command. This command does not cause the MT to change to the online state. O,L N/A R O,L N/A R -0

129 TIA/EIA/IS-0-A. Table..-. Cellular Identification AT Command Extensions (Part of ) Command Value per Description Async & Fax Packet Data STU III +CGCAP IS- This extended-format command causes the IWF to transmit one or more lines of information text in a specific format. The content is a list of additional capabilities command +<name>s, which is intended to permit the user of the IWF to identify the minimum capabilities of the IWF. O,M N/A N/A IWFs conforming to this standard shall include the following items, as a minimum, in the result code for the +CGCAP command: +CIS0, +MS, +ES, +DS, +FCLASS +CGMI IS- This command causes the IWF to transmit one or more lines of information text, determined by the manufacturer, which is intended to permit the user of the IWF to identify the manufacturer. Typically, the text will consist of a single line containing the name of the manufacturer, but manufacturers may choose to provide more information if desired (e.g., address, telephone number for customer service, etc.). +CGMM IS- This command causes the IWF to transmit one or more lines of information text, determined by the manufacturer, which is intended to permit the user of the IWF to identify the specific model of the device. Typically, the text will consist of a single line containing the name of the product, but manufacturers may choose to provide any information desired. O,M N/A N/A O,M N/A N/A The +CIS0 result code indicates support of the AT commands and result codes in Tables..-,..-,..- and..- and..-. -

130 TIA/EIA/IS-0-A. Table..-. Cellular Identification AT Command Extensions (Part of ) Command Value per Description Async & Fax Packet Data STU III +CGMR IS- This command causes the IWF to transmit one or more lines of information text, determined by the manufacturer, which is intended to permit the user of the IWF to identify the version, revision level or date, or other pertinent information of the device. Typically, the text will consist of a single line containing the version of the product, but manufacturers may choose to provide any information desired. +CGOI IS- This command causes the IWF to transmit one or more lines of information text, determined by the manufacturer, which is intended to permit the user of the IWF to identify the device, based on the ISO system for registering unique object identifiers. Typically, the text will consist of a single line containing numeric strings delimited by period characters. +CGSN IS- This command causes the IWF to transmit one or more lines of information text, determined by the manufacturer, which is intended to permit the user of the IWF to identify the individual device. Typically, the text will consist of a single line containing a manufacturer determined alpha-numeric string, but manufacturers may choose to provide any information desired. O,M N/A N/A O,M N/A N/A O,M N/A N/A Note: The format of these +C commands shall comply with the corresponding format of the +G commands specified in TIA/EIA/IS-. The MT shall treat all commands in this table as unrecognized commands (see.). -

131 TIA/EIA/IS-0-A. Table..-. Cellular AT Commands for Packet Data Services Command +CTA=<value> +CPS=<value> +CPSR=<value> +CPTC=<value> +CPER=<value> Description Set/Read/Test U m packet data inactivity timer. 0 Traffic Channel not released during inactivity periods. 0- Release the Traffic Channel after <value> -second intervals have elapsed since last sending or receiving RLP data frames on the U m interface. Select the service option to be used for packet data service. Values shall be as specified in TSB. Enables/disables packet call state reporting. 0 Disables call state reporting Enables call state reporting Controls Traffic Channel state without affecting the IWF Link Layer connection. 0 Release Traffic Channel Originate Traffic Channel Enables/disables packet call event reporting. 0 Disables call event reporting Enables call event reporting.. Cellular Result Codes Table..-. Cellular Result Codes Result Code +CERROR: BAD REQUEST +CERROR: INIT FAILED <failed command> +CERROR: LINK FAIL +CERROR: NO SERVICE +CERROR: NO <service option> SERVICE +CERROR: PAGE FAIL Description Intercept received after call origination. Initialization string failed (see.). Mobile station has declared a loss of the Traffic Channel. Origination was attempted while the mobile station was not able to monitor a CDMA Paging Channel. The indicated service option was rejected. The <service option> shall be ASYNC or FAX. Mobile station received a page but not an alert. Async & Fax Packet Data STU III R N/A N/A R N/A N/A R N/A N/A R N/A N/A R N/A N/A R N/A N/A -

132 TIA/EIA/IS-0-A. +CERROR: PAGED Mobile station attempted to originate after receiving a page. R N/A N/A +CERROR: RELEASE Indicates call release. R N/A N/A +CERROR: RESPONSE NOT SUPPORTED +CERROR: RETRY +CPROG: ANSWER Indicates that the AT command was processed properly but the proper response code is not supported. Reorder received after call origination. Indicates remote DCE has answered. R,L N/A N/A R N/A N/A R N/A N/A +CPROG: BONGTONE Billing Tone was detected. R N/A N/A +CPROG: DIALING <number> Indicates PSTN Dialing. R N/A N/A +CPROG: DIALTONE Dialtone was detected. R N/A N/A +CPROG: QUIET ANSWER Indicates Quiet Answer. R N/A N/A +CPROG: RINGING Indicates PSTN Ringing. R N/A N/A +CPROG: VOICE RING <service option> Voice detected on the PSTN connection. Specifies active service option. The <service option> shall be ASYNC, FAX or STU-III. R N/A N/A R N/A N/A -

133 TIA/EIA/IS-0-A. Table..-. Cellular Result Codes for Packet Data Services Result Code +CPACKET +CPSR:<value> +CPER:<value> +CERROR: LINK FAIL +CERROR: NO SERVICE +CERROR: RETRY Description May be returned after AT+CRM= or or. Indicates packet data service is in the Active State. Packet call state. Sent autonomously when +CPSR=. 0 Packet data service is in the Inactive State Packet data service is in the Active State, and the call control function is in the Initialization/Idle State Packet data service is in the Active State, and the call control function is in the Initialization/Traffic State Packet data service is in the Active State, the call control function is in the Connected State, and the packet data service option is using primary traffic Packet data service is in the Active State, the call control function is in the Connected State, and the packet data service option is using secondary traffic Packet data service is in the Active State, and the call control function is in the Dormant/Idle State Packet data service is in the Active State, and the call control function is in the Dormant/Traffic State Packet data service is in the Active State, and the call control function is in the Reconnect/Idle State Packet data service is in the Active State, and the call control function is in the Reconnect/Traffic State - Reserved Packet call event. Sent autonomously when +CPER=. 0 Enter Idle State Idle handoff, same system Idle handoff, new system Page received Origination sent Traffic Channel assigned Hard handoff - Reserved Mobile station has declared a loss of the Traffic Channel Mobile station is not able to monitor a Paging Channel Reorder received during reconnect attempt -

134

135 TIA/EIA/IS-0-A. 0 APPENDIX A: IS-0 REFLECTION EXAMPLES. Introduction This appendix contains two examples citing how an MT and IWF would send responses for various commands. Each example shows both the expected action in verbose mode (the V parameter is set to ) and non-verbose mode (the V parameter is set to 0). Consider a command AT+ABC? which would return a single line containing ten copies of each of the letters of the alphabet followed by a CR/LF pair (i.e., 0 characters prior to the <CR><LF>). Let us also say that there was a command called AT+Q? which returns a single line consisting of occurrences of the letter Q followed by a CR/LF pair. Using these fabricated commands, we can give the following examples of how to handle information responses which have or more characters on a single line. Also, consider the real commands S0?, and +GMM, both of which yield informational responses prior to their result codes. Suppose the user enters the command line: at+abc?+q?<cr> or ats0?+gmm<cr> See Example (Section A.) See Example (Section A.) The figure below shows the sequence of events. All reflection messages are shown in thick lines. 0 a b a TE MT IWF b Figure A.-. Sequence of Events for Command Responses The AT command line entered by the user () is passed on by the MT to the IWF (). The IWF reflects the first AT command back to the MT (a) and waits for a response from it (b). The second command is then reflected to the MT (a), after which the MT s response is received (b). Lastly, the IWF sends the result message () to the MT to be forwarded to the user terminal (). -

136 TIA/EIA/IS-0-A.. Example : User Enters at+abc?+q?<cr>.. Verbose Mode The format of the first IWF reflected AT commands and responses are given below. IWF Reflect (Step a, Figure A.-): Hex Code (IS-0): <0x><0x0><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x0><0x><0x>+ABC? MT Response (Step b, Figure A.-): Hex Code (IS-0): <0x><0x><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x0><0x> <0x><0x><0xE><0x>aaa ddd...iiijjjj <0x><0x><0xE><0x>jjjjjj.rrrssssssss <0x><0x><0x><0x>ssttt...yyyzzzzzzzzzz <0x><0x><0x0><0x> <0x><0x><0x><0x>OK Representative of <CR><LF> 0 a s0b s j s j s0k s 0r ss s s s0t s 0z s<cr><lf> <CR><LF> OK<CR><LF> 0 IWF Reflect (Step a, Figure A.-): Hex Code (IS-0): <0x><0x0><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x0><0x><0x>+Q? -

137 TIA/EIA/IS-0-A. MT Response (Step b, Figure A.-): Hex Code (IS-0): <0x><0x><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x><0x0><0x> <0x><0x><0xE><0x>QQQQ QQQQQ <0x><0x><0x0><0x> <0x><0x><0x0><0x> <0x><0x><0x><0x>OK Representative of <CR><LF> Q s <CR><LF> <CR><LF> OK<CR><LF> The result string returned by the IWF (Step, Figure A.-) is of the form: Hex Code (IS-0): <0x><0x><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x><0x0><0x> <0x><0x><0xE><0x>aaaaa jjjj <0x><0x><0xE><0x>jjjjjj ssssssss <0x><0x><0x><0x>ss..yyyyzzzzzzzzzz <0x><0x><0x0><0x> <0x><0x><0xE><0x>QQQQ.QQQQ <0x><0x><0x0><0x> <0x><0x><0x0><0x> <0x><0x0><0x><0x>OK Representative of <CR><LF> 0a s0b s j s j s0k s s s s s0t s 0z s<cr><lf> <CR><LF> Q s <CR><LF> <CR><LF> OK<CR><LF> 0.. Non-Verbose Mode The format of the first IWF reflected AT commands and responses are given below. IWF Reflect (Step a, Figure A.-): Hex Code (IS-0): <0x><0x0><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x0><0x><0x>+ABC? MT Response (Step b, Figure A.-): Hex Code (IS-0): <0x><0x><len><0x><string> -

138 TIA/EIA/IS-0-A. Actual Stream Sent by the IWF to the MT <0x><0x><0xE><0x>aaaaa.iiiii.jjjj <0x><0x><0xE><0x>jjjjjj.rrrrrssssssss <0x><0x><0x><0x>ss..yyyyzzzzzzzzzz <0x><0x><0x><0x>0 Representative of 0a s0b s j s j s0k s s s s s0t s 0z s<cr><lf> 0<CR> IWF Reflect (Step a, Figure A.-): Hex Code (IS-0): <0x><0x0><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x0><0x><0x>+Q? MT Response (Step b, Figure A.-): Hex Code (IS-0): <0x><0x><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x><0xE><0x>QQQQ.QQQQ <0x><0x><0x0><0x> <0x><0x><0x><0x>0 Representative of Q s <CR><LF> 0<CR> -

139 TIA/EIA/IS-0-A. The result string returned by the IWF (Step, Figure A.-) is of the form: Hex Code (IS-0): <0x><0x><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x><0xE><0x>aaaaa jjjj <0x><0x><0xE><0x>jjjjjj ssssssss <0x><0x><0x><0x>ss..yyyyzzzzzzzzzz <0x><0x><0xE><0x>QQQQ.QQQQ <0x><0x><0x0><0x> <0x><0x0><0x><0x>0 Representative of 0a s0b s j s j s0k s s s s s0t s 0z s<cr><lf> Q s <CR><LF> 0<CR>. EXAMPLE : User Enters ats0?+gmm<cr>.. Verbose Mode The format of the first IWF reflected AT commands and responses are given below. IWF Reflect (Step a, Figure A.-): Hex Code (IS-0): <0x><0x0><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x0><0x><0x>S0? 0 MT Response (Step b, Figure A.-): Hex Code (IS-0): <0x><0x><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x><0x0><0x> <0x><0x><0x><0x>000 <0x><0x><0x0><0x> <0x><0x><0x><0x>OK Representative of <CR><LF> 000<CR><LF> <CR><LF> OK<CR><LF> IWF Reflect (Step a, Figure A.-): Hex Code (IS-0): <0x><0x0><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x0><0x><0x>+GMM -

140 TIA/EIA/IS-0-A. MT Response (Step b, Figure A.-): Hex Code (IS-0): <0x><0x><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x><0x0><0x> <0x><0x><0x><0x>REV B <0x><0x><0xB><0x>Model QC-M <0x><0x><0x0><0x> <0x><0x><0x><0x>OK Representative of <CR><LF> REV B<CR><LF> Model QC-M<CR><LF> <CR><LF> OK<CR><LF> -

141 TIA/EIA/IS-0-A. The result string returned by the IWF (Step, Figure A.-) is of the form: Hex Code (IS-0): <0x><0x><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x><0x0><0x> <0x><0x><0x><0x>000 <0x><0x><0x0><0x> <0x><0x><0x><0x>REV B <0x><0x><0xB><0x>Model QC-M <0x><0x><0x0><0x> <0x><0x0><0x><0x>0K Representative of <CR><LF> 000<CR><LF> <CR><LF> Rev B<CR><LF> Model QC-M<CR><LF> <CR><LF> OK<CR><LF>.. Non-Verbose Mode The format of the first IWF reflected AT commands and responses are given below. IWF Reflect (Step a, Figure A.-): Hex Code (IS-0): <0x><0x0><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x0><0x><0x>S0? 0 MT Response (Step b, Figure A.-): Hex Code (IS-0): <0x><0x><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x><0x><0x>000 <0x><0x><0x><0x>0 Representative of 000<CR><LF> 0<CR> IWF Reflect (Step a, Figure A.-): Hex Code (IS-0): <0x><0x0><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x0><0x><0x>+GMM MT Response (Step b, Figure A.-): Hex Code (IS-0): <0x><0x><len><0x><string> -

142 TIA/EIA/IS-0-A. Actual Stream Sent by the IWF to the MT <0x><0x><0x><0x>REV B <0x><0x><0xB><0x>Model QC-M <0x><0x><0x><0x>0 Representative of REV B<CR><LF> Model QC-M<CR><LF> 0<CR> -

143 TIA/EIA/IS-0-A. The result string returned by the IWF (Step, Figure A.-) is of the form: Hex Code (IS-0): <0x><0x><len><0x><string> Actual Stream Sent by the IWF to the MT <0x><0x><0x><0x>000 <0x><0x><0x><0x>REV B <0x><0x><0xB><0x>Model QC-M <0x><0x0><0x><0x>0 Representative of 000<CR><LF> Rev B<CR><LF> Model QC-M<CR><LF> 0<CR> -

144

145 Data Service Options for Spread Spectrum Systems: Async Data and Fax Services TIA/EIA/IS-0-A. (PN-.) Ballot Resolution Version March

146 Copyright TIA

147 TIA/EIA/IS-0-A CONTENTS INTRODUCTION...-. General Description...-. Terms...-. References...- REQUIREMENTS FOR THE ASYNC DATA AND FAX PROTOCOL STACK...-. Overview...-. The Application Interface...-. Transport Layer...-. Network Layer General Requirements Assignment of Network Address...-. Data Link Layer Sub-Network Dependent Convergence Function PPP Layer IPCP Link Control Protocol Requirements for Async Data and Fax Traffic Channel Usage...- REQUIREMENTS FOR THE RADIO INTERFACE...-. Service Option Number...-. Multiplex Option Interface...-. Procedures Using Service Option Negotiation Initialization and Connection of the Service Option Mobile Station Requirements BS/MSC Requirements...-. Procedures Using Service Negotiation Mobile Station Requirements BS/MSC Requirements...- REQUIREMENTS FOR UM INTERFACE CALL PROCESSING...-. Connection Establishment Mobile Origination Mobile Termination...- i

148 TIA/EIA/IS-0-A. 0 CONTENTS.. Service Option Change to Group- Facsimile Service Conversation Substate Traffic Channel Handoff Connection Release Authentication... - RECOMMENDATIONS FOR THE MODEM TO PSTN INTERFACE Recommended Modem Standards Flow Control Flow Control for Async Data Flow Control for Group- Fax... - FIGURES Figure.-. The Async Data and Fax Protocol Stack Architecture TABLES Table.-. IP Type of Service... - Table.-. Compression Options...- Table.-. Group Fax Compression Options...- Table.-. Implicit Service Configuration Attributes for Service Options 00 or 0 when Service Option Negotiation is Used... - Table..-. Valid Service Configuration Attributes for Service Options 00 and Table..-. Valid Service Configuration Attributes for Service Options and... - ii

149 TIA/EIA/IS-0-A INTRODUCTION. General Description Service Options 00 and provide asynchronous (abbreviated as async hereafter) data transmission capability on TIA/EIA/IS--A and TSB wideband spread spectrum systems using the protocols and procedures defined herein. Service Options 0 and provide Group- facsimile (abbreviated as fax hereafter) transmission capability for these systems. Service Options 00 and 0 provide async data and group fax service using a default service configuration including Multiplex Option data rates. Service Options and provide async data and group fax service using a default service configuration including Multiplex Option data rates. Other combinations of service configuration attributes are available for service options 00, 0,, and through the use of service negotiation procedures defined in TSB.. Terms AT Command Set. Command set interface between data terminal equipment (DTE) and data circuit terminating equipment (DCE). Base Station (BS). A station in the Domestic Public Cellular Radio Telecommunications Service, other than a mobile station, used for communicating with mobile stations. Depending upon the context, the term base station may refer to a cell, a sector within a cell, or other part of the cellular system. BS. See base station. BS/MSC. The base station and mobile switching center considered as a single functional entity. Data Circuit-Terminating Equipment (DCE). A DCE connects a TE to the PSTN. A typical DCE would be a V-series modem. For Group- Fax Service, the DCE and its associated TE are often combined into a single Group- fax machine. Digital Facsimile. That form of facsimile in which densities of the original are sampled and quantified as a digital signal for processing, transmission, or storage. Error Correction Mode (ECM). A mode of operation for T.0 fax service providing end-toend reliable data transport. Facsimile. The process by which a document is scanned, converted into the electrical signals, transmitted, and recorded or displayed as a copy of the original. Fax. An abbreviation for facsimile. Fax Calling Station. The fax machine or fax modem initiating the fax call. Group-. Digital Facsimile equipment per CCITT Recommendation T.. ICMP. Internet Control Message Protocol. IANA. Internet Assigned Number Authority. -

150 TIA/EIA/IS-0-A Interworking Function (IWF). An IWF provides the functions needed for terminal equipment connected to a mobile termination to communicate with terminal equipment connected to the PSTN. A physical implementation may include a pool of modems. IP. Internet Protocol. IPCP. Internet Protocol Control Protocol. L. L-Interface. The interface between an IWF and BS/MSC. LCP. PPP Link Control Protocol. Mobile Station. A station in the Domestic 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. Mobile Termination 0 (MT0). An MT0 is a self-contained data-capable mobile termination that does not support an external interface. Mobile Termination (MT). An MT provides a non-isdn (R m ) user interface, e.g., CCITT V series or CCITT X series. Modem Client. The name given to the TCP well-known port used for CDMA async data and fax services in mobile stations. Modem Server. The name given to the TCP well-known port used for CDMA async data and fax services in a BS/MSC. Modem Emulation Service. A wireless data service where the mobile termination appears as a standard telephone modem to a data terminal. MSC. Mobile Switching Center. PPP. Point-to-Point Protocol. PSTN. Public Switched Telephone Network. RFC. Request for Comments. The generic name of a standard developed by the Internet Engineering Task Force (IETF). RLP. Radio Link Protocol. SNDCF. Sub-Network Dependent Convergence Function. TCP. Transmission Control Protocol. Terminal Equipment (TE). A TE is a data terminal device that has a non-isdn usernetwork interface, e.g., CCITT V series or CCITT X series.. References ANSI J-STD-00- ANSI X.- Personal Station-Base Station Compatibility Requirements for. to.0 GHz Code Division Multiple Access (CDMA) Personal Communications Systems,. Coded Character Set -Bit American National Standard Code for Information Interchange,. -

151 TIA/EIA/IS-0-A. 0 0 Bell 0 Bell A EIA/TIA--E EIA/TIA- EIA/TIA-0 EIA/TIA-0 EIA/TIA- RFC RFC RFC RFC RFC RFC 0 RFC RFC RFC RFC RFC RFC RFC RFC RFC 0 RFC RFC 0-00 bps, -wire, full-duplex modem standard. 00 bps, -wire, full-duplex modem standard. Interface Between DTE and DCE Employing Serial Binary Data Interchange. Asynchronous Facsimile DCE control Standard - Service Class.0. Serial Asynchronous Automatic Dialing and Control. Facsimile DCE-DTE Packet Protocol Standard. Extensions to Serial Asynchronous Automatic Dialing and Control. Internet Protocol. Internet Control Message Protocol. Transmission Control Protocol. Telnet Protocol Specification. Telnet Options Specification. Internet Standard Subnetting Procedure. Host Extensions for IP Multicasting. Requirements for Internet Hosts Communication Layers. Requirements for Internet Hosts Application and Support. Compressing TCP/IP Headers for Low-Speed Serial Links. Internet Numbers. Path MTU Discovery. The PPP Internet Protocol Control Protocol (IPCP). Type of Service in the Internet Protocol Suite. PPP LCP Extensions. The Point-to-Point Protocol (PPP). PPP in HDLC Framing. -

152 TIA/EIA/IS-0-A. RFC 00 Assigned Numbers (most recent version). T. Compression/decompression standard for facsimile applications. T.0 Facsimile protocol standard. 0 ANSI/TIA/EIA- TIA/EIA/IS- TIA/EIA/IS- TIA/EIA/IS--A TSB TSB Inband DCE Control for Asynchronous DTE DCE Interfaces. Data Transmission Systems and Equipment Extensions to Serial Asynchronous Dialing and Control. Amendments to TIA- to Support T.0-. Mobile Station-Base Station Compatibility Standard for Dual- Mode Wideband Spread Spectrum Cellular System. Administration of Parameter Value Assignments for TIA/EIA Wideband Spread Spectrum Standards. Telecommunications Systems Bulletin: Support for. kbps Data Rate and PCS Interaction for Wideband Spread Spectrum Cellular Systems. 0 V.,00 bps, wire, half duplex modem standard. V. Operational and Interworking Requirements for Modems Operating in the Text Telephone Mode, International Telecommunications Union,. V. 00 bps, wire, full-duplex modem standard. V. 00/00 bps, wire, full-duplex modem standard. V.bis V.ter 00 bps, wire, full duplex modem standard. 00/00 bps, wire, half-duplex modem standard. V. 00 bps, wire, full duplex modem standard. V. 00 bps, wire, full duplex modem standard. V.bis,00 bps wire, full duplex modem standard. V. Full duplex modem standard up to,00 bps. V. Error-correction procedures for DCEs using asynchronous to synchronous conversion. -

153 TIA/EIA/IS-0-A. V.bis Data compression procedures for DCEs using error correction procedures. -

154

155 TIA/EIA/IS-0-A. REQUIREMENTS FOR THE ASYNC DATA AND FAX PROTOCOL STACK. Overview This chapter specifies requirements for an asynchronous data and group facsimile service for CDMA wireless systems based on the protocol stack reference architecture shown in Figure.-. The service is designed to provide modem emulation functions over a wireless data link to a TE. Although actual implementations may vary with respect to specific network elements, functionality available over the air (U m ) interface shall be in accordance with the requirements specified in this standard. Mobile Station TE MT BS/MSC IWF Application Layer Async or Fax App. Transport Layer Network Layer Link Layer Relay Layer RS- RS- App. Int. TCP ICMP IP SNDCF IPCP PPP RLP IS--A LCP RLP IS--A Relay Layer LCP IC MP TC P IP IPCP SNDCF PPP Relay Layer App. Int. PSTN Data or Fax Modem 0 R m U L m Figure.-. The Async Data and Fax Protocol Stack Architecture 0 The Application Layer consists of an async data or fax user application on a TE, and the associated application interfaces in the MT and in the IWF. The application interfaces in the MT and in the IWF support EIA/TIA standardized modem control commands, and together provide an interface compatible with those encountered in practical modem implementations. The Transport Layer consists of Transmission Control Protocol (TCP). TCP (See RFC ) provides a reliable transport service to all application layer and user data exchanges. The Network Layer consists of ICMP, (see RFC ) and IP (see RFC ) protocols to provide network layer transport of modem control and user data over the CDMA air interface. The Link Layer consists of Point to Point Protocol (PPP), Link Control Protocol (LCP), and Internet Protocol Control Protocol (IPCP). PPP (see RFC and ) provides a multiplexed method to carry higher layer protocol data over serial links. LCP (see RFC 0) provides a mechanism for the Mobile Station and the IWF to negotiate various -

156 TIA/EIA/IS-0-A options provided by PPP. IPCP (see RFC ) allows the Mobile Station request a temporary IP address from the IWF. The Relay Layer consists of physical and logical interface functions required to support the link, network, transport and application layers described above. Central to the relay layer is the inclusion of a Radio Link Protocol (RLP) (see IS-0.) to improve the error characteristics of the wireless link, thereby reducing the need for Transport Layer retransmissions due to lost data. The protocol stack, as specified in this standard, describes a minimal subset of the TCP, IP and PPP protocols for the mobile station. BS/MSC and IWF protocol implementations shall be compatible with mobile stations having the minimal implementation specified herein.. The Application Interface In the mobile station, CDMA async data and fax services shall include an application interface between the data source/destination in the MT0 or TE and the transport protocol layer. In the IWF, the application interface shall reside between the PSTN Data or Fax modem and the transport protocol layer. The application interface shall provide the following functionality: Modem control, as specified in of IS-0.. AT Command processing, as defined in IS-0.. Negotiation of air interface data compression. Data compression over the air interface (optional). In a mobile station, data entering the application interface from the R m interface shall first be parsed to extract locally processed time dependent modem control commands and the associated escape characters. These commands shall be processed in accordance with of IS-0.. The resulting data shall be parsed to extract locally processed AT commands (see Chapter ). ANSI/TIA/EIA- in-band commands shall then be inserted, including any necessary escaping, as described in ANSI/TIA/EIA-. Option negotiation commands shall then be inserted, including any necessary escaping, as described below. The resulting data shall be passed to the transport layer. In a mobile station, data entering the application interface from the transport layer shall first be parsed to extract the option negotiation commands and the associated escaping. The resulting data shall be parsed to extract locally processed ANSI/TIA/EIA- in-band commands (see.. of IS-0.). The resulting data shall be passed to the R m interface. In the IWF, data entering the application interface from the PSTN data or fax modem shall be passed to the transport layer. ANSI/TIA/EIA- in-band commands shall then be inserted, including any necessary escaping, as described in ANSI/TIA/EIA-. Option negotiation commands shall then be inserted, including any necessary escaping, as described below. -

157 TIA/EIA/IS-0-A. 0 In the IWF, data entering the application interface from the transport layer shall first be parsed to extract the option negotiation commands and the associated escaping. The resulting data shall be parsed to extract any ANSI/TIA/EIA- in band modem control commands (see.. of IS-0.). If the IWF application interface is in command state or online command state, the resulting data shall be parsed to extract any AT commands (see of IS-0.). The resulting data shall be passed to the PSTN data or fax modem. The application interface for CDMA async data and fax services shall comply with the requirements of Sections. and. of RFC, with the following modifications: An IWF serving multiple users may be treated as part of a single multi-homed host or as independent hosts. The mobile station application interface should specify type of service as described in RFC. The mobile station and the IWF should specify the types of service shown in Table.-. Table.-. IP Type of Service Service Option Type of Service 00, (Async Data) Low delay 0, (Group- Fax) Max throughput 0 For mobile-originated data calls, the mobile station application interface shall open the transport layer using TCP well-known port 0 ( modem server ) as the destination port. For mobile-terminated data calls, the IWF application layer shall open the transport layer using TCP well-known port ( modem client ) as the destination port. The application interface in the mobile station and the IWF should also support data compression, using the following negotiation protocol. To ensure transparency of user data to compression negotiation commands, the sender shall insert an additional octet of value before each data byte of value, except for IAC octets that are part of negotiation commands. The receiver shall remove the inserted octets of value and any negotiation commands after decompression. This protocol is based on the Telnet option negotiation protocol, as described in Internet RFC. This use of Telnet negotiation does not prevent the use of Telnet applications by means of the CDMA async data service, since the negotiation in the CDMA async data application protocol layer is transparent to the user application, including a user s Telnet session. -

158 TIA/EIA/IS-0-A. The application interface shall support option negotiation commands in accordance with the requirements of RFC, except that only the following commands are required: NAME CODE MEANING SE 0 End of subnegotiation parameters. SB (option code) 0 Indicates that what follows is subnegotiation of the indicated option. WILL (option code) Indicates a desire to begin performing the indicated option. WON'T (option code) Indicates a refusal to perform, or continue performing, the indicated option. DO (option code) Indicates a request that the other station begin performing the indicated option. DON'T (option code) Indicates a demand that the other station stop performing the indicated option. IAC Interpret as Command. The data compression option shall be indicated by setting the option code to the value shown in Table.- for the type of data compression being negotiated. Data compression parameters shall be negotiated using the procedure described in RFC, and further defined below. If data compression is supported by the IWF, the IWF shall initiate negotiation of data compression by sending a WILL command when the transport layer connection is opened. The mobile station shall respond with a DO or DON T command. The mobile station shall not initiate negotiation of data compression. If the mobile station responds with a DO command, the IWF shall transmit a subnegotiation (SB) command followed by the requested data compression control parameters. The mobile station shall respond with a subnegotiation (SB) command with either the same parameters, an alternative set, or a DON T command. If the mobile station replies with an SB command whose parameters are acceptable to the IWF, the IWF shall send a DO command. If the accepted subnegotiation parameters include a request for forward link compression, the IWF shall compress all applicable data following the DO command. The mobile station shall respond to the DO command with a WILL command. The negotiation process is terminated when the IWF receives the WILL command. If the accepted subnegotiation parameters include a request for reverse link These option numbers may overlap Telnet option number assignments. There is no conflict because compression negotiation is hidden from any Telnet application that makes use of the CDMA async data service. -

159 TIA/EIA/IS-0-A. 0 0 compression, the mobile station shall compress all applicable data following the WILL command. Compression shall be applicable only as follows: For Service Options 00 and (async data), if V.bis is employed data passed from the application interface to the transport layer, in the negotiated directions following the DO or WILL command, shall be compressed. Compression may be enabled independently in each direction. For Service Options 0 and (group facsimile), if MMR compression (see CCITT T.) is used, it shall only be applied to the actual fax image data being transmitted. If MMR compression is negotiated during transmission of a page, the compression shall be enabled for subsequent pages. If V.bis is used, compression shall begin immediately following the DO or WILL command. V.bis compression may be enabled independently in each direction. If the mobile station replies with an SB command containing parameters not acceptable to the IWF, the IWF shall send a DON T command. The IWF may re-initiate negotiation at any time. Either side may terminate compression or subnegotiation at any time by sending a DON T command and shall send uncompressed data following the command. Whenever a DON T command is received, the receiver shall respond with a WON T command and shall send uncompressed data following the command. When possible, the timing of these commands relative to the decompression process should be chosen to minimize loss of data. If V.bis compression is negotiated, it shall not be disabled for the duration of the call. Subnegotiation parameters shall be transmitted in the following format. If any octet following the OPTION octet and preceding the next IAC octet has value, an additional octet of value shall be inserted. The value of the PARAMETER_LEN field shall not change as the result of such insertion. The receiver shall remove all such inserted octets prior to processing the subnegotiation parameters. Field Name Size (octets) IAC SB OPTION 0 Zero or more occurrences of the following entry: PARAMETER_ID PARAMETER_LEN PARAMETER_VAL PARAMETER_LEN -

160 TIA/EIA/IS-0-A. The subnegotiation parameter list shall be followed immediately with: IAC SE OPTION - Option value. The application interface shall set this field to the value shown in Table.- corresponding to the type of compression selected. Table.-. Compression Options Option Compression Type 0x00 V.bis compression 0x0 Modified Modified Read Coding (Service Option 0 and only) All other values are reserved PARAMETER_ID - Parameter Identifier. The application interface shall set this field to identify the parameter. All parameters in the subnegotiation command shall be as required for the selected compression option. PARAMETER_LEN - Parameter Length. The application interface shall set this field to the number of octets in this parameter, not including the PARAMETER_ID and PARAMETER_LEN fields. PARAMETER_VAL - Parameter Value. Indicates the desired setting for this parameter. If negotiation does not occur, the default setting shall apply. For the async data and group fax service options the default setting is no compression. If the OPTION field selects V.bis compression, the parameter entries may be configuration parameters, and/or of the compression scheme defined in CCITT Recommendation V.bis. For V.bis compression, these parameters, their identifiers, and lengths, are as defined in V.bis, Annex A. For negotiation of V.bis compression, the IWF is always considered the initiator. For each direction of transmission for which V.bis compression is requested, the compression scheme defined in CCITT Recommendation V.bis shall be applied to all data passed from the application interface to the transport layer, and the corresponding decompression scheme shall be applied to all data passed from the transport layer to the application interface. If the OPTION field selects Modified Modified Read Coding compression, no parameter entries are defined. -

161 TIA/EIA/IS-0-A. When a Group fax service option is connected, and MMR or V.bis compression is negotiated, it shall only be used in accordance with Table.-. Table.-. Group Fax Compression Options PSTN Compression Method Modified Huffman Modified Read Modified Modified Read U m Compression Method Modified Modified Read or V.bis (no additional compression) (no additional compression) 0 0 If Modified Modified Read compression is negotiated, the compression scheme defined in CCITT Recommendation T. shall be applied only to the fax image data passed from the data source to the application interface layer, and the corresponding decompression scheme shall be applied only to the fax image data passed from the application interface layer to the data destination.. Transport Layer The transport layer for CDMA async data and fax services is based on the Internet transport layer protocol known as Transmission Control Protocol (TCP), described in RFC. The implementation shall comply with the requirements of RFC, as amended by RFC, with the following modifications: TCP should always advertise a Maximum Segment Size (MSS), which should be no smaller than octets (which is the default value). TCP should limit the transmitted segment size to no more than 0 octets. TCP should advertise a window size no smaller than twice the advertised MSS, and no larger than times the MSS. For each connection, the transport layer shall use a different source port number than the one used in the previous connection. The port numbers used shall be in the range from 0x000 (decimal 0) to 0xffff (decimal ), inclusive. The mobile station s port number may be initialized to an arbitrary value in this range on power-up. The IP maximum segment lifetime (Time To Live) shall be set to 0xfe (decimal ) if it is not configurable. When provision is made for configuration, the initial value This limit is intended to prevent excessive segment error rates under conditions where the RLP frame error rate is high. The TCP MSS option provides a means for restricting the segment size to a smaller value if required by an implementation. -

162 TIA/EIA/IS-0-A should be the number currently in effect as published in Internet Assigned Numbers. Mobile stations shall handle TCP connection failures using the following procedure, unless disabled by the application interface: (a) During initial connection synchronization, the number of retransmission attempts (R) shall be retransmissions, after which the connection should be closed. (b) After the connection has been established, the default value of R shall be either 00 seconds or 0 retransmissions, after which the connection may be closed. The manufacturer shall provide a means for the application interface to disable this procedure. If this procedure is disabled, there shall be no maximum number of retransmission attempts during synchronization, and an established TCP connection shall remain open until explicitly closed by the mobile station or the IWF. The application interface shall be able to set the value of R. R may be measured in time units or as a count of retransmissions. IWFs shall follow either the procedure of... of RFC, or the procedure above.. Network Layer.. General Requirements The network layer for CDMA async data and fax services is based on the Internet network layer protocol known as the Internet Protocol (IP), as described in RFC. The network layer shall also include the Internet Control Message Protocol (ICMP), as described in RFC. The implementation shall comply with the requirements of RFC as amended by RFC, with the following modifications: The mobile station network layer is not required to support the subnet addressing modes described in RFC 0. The IWF network layer should support subnet addressing as described in RFC 0 and RFC. The mobile station network layer may assume that it is locally connected to the IWF. Mobile stations shall not perform Dead Gateway Detection (see... of RFC ) nor New Gateway Selection (see... of RFC ) in the network layer. The Address Mask Request and Reply are obsolete, and should not be sent. The most recently published value is, per RFC 00. It is recommended that the application keep the connection open, and wait for notification of an improvement in connectivity or link quality before attempting further retransmissions. -

163 TIA/EIA/IS-0-A The mobile station is not required to support the Internet Group Management Protocol (IGMP) as described in RFC. The network layer shall not fragment IP datagrams for transmission on the U m interface. If fragmented datagrams that are received from a network cannot be transmitted on the U m interface after reassembly, they shall be discarded as specified in RFC. The mobile station shall support the End of Option list IP option and the No Operation IP option (see RFC ). The interface between the network layer and the transport layer shall comply with the requirements of. of RFC... Assignment of Network Address The IWF assigns the mobile station a temporary IP address upon call establishment. This IP address shall be valid and should be uniquely assigned to the mobile station for the duration of the call. The IWF transfers the temporary IP address to the mobile station using IPCP (see..).. Data Link Layer.. Sub-Network Dependent Convergence Function The Sub-Network Dependent Convergence Function (SNDCF) performs header compression on the headers of the transport and network layers. This function is negotiated using the PPP Internet Protocol Control Protocol (see..). Mobile stations shall support Van Jacobson TCP/IP header compression, as described in RFC, Compressing TCP/IP Headers for Low-Speed Serial Links. A minimum of compression slot shall be negotiated. The IWF shall support TCP/IP header compression compatible with that required for mobile stations. Negotiation of the parameters of header compression shall be carried out using IPCP, as specified in... The SNDCF sublayer shall accept network layer datagrams from the network layer, perform header compression as required, and pass the datagram to the PPP layer, indicating the appropriate PPP protocol identifier. The SNDCF sublayer shall receive network layer datagrams with compressed or uncompressed headers from the PPP layer, decompress the datagram header as necessary, and pass the datagram to the network layer. The IP address should have a valid format as if it were assigned by IANA. However, for async data and fax services, IP addresses need not be requested from IANA if the Internet is not used as part of the intersystem network. Implementation note: the code provided in RFC will not work with less than compression slots. Also, if the mobile station is to support additional data services, it should allocate additional slots. A minimum of compression slots is recommended for such mobile stations. -

164 TIA/EIA/IS-0-A PPP Layer The data link layer uses PPP, as described in RFC, The Point-to-Point Protocol (PPP), and RFC, PPP in HDLC Framing, for datagram encapsulation and framing, respectively. The PPP Link Control Protocol (LCP) is used for initial link establishment, and to negotiate optional link capabilities. The data link layer uses The PPP Internet Protocol Control Protocol (IPCP), as described in RFC, to negotiate IP addresses and TCP/IP header compression. The PPP layer shall accept header compressed network layer datagrams from the SNDCF, and shall encapsulate them in the PPP Information field. The packet shall be framed using the octet-synchronous framing protocol defined in RFC, except that there shall be no inter-frame fill (see.. of RFC ): No flag octets shall be sent between a flag octet that ends one PPP frame and the flag octet that begins the subsequent PPP frame. The framed PPP packets shall be passed to the RLP layer for transmission. The data link layer shall accept received octets from the RLP layer, and re-assemble the original PPP packets. The PPP process shall discard any PPP packet for which the received Frame Check Sequence (FCS), specified in. of RFC, is not equal to the computed value... IPCP The IPCP sublayer shall support negotiation of the IP-address (type = ) and IP- Compression-Protocol (type = ) parameters. IPCP shall negotiate a temporary IP address for the mobile station whenever a transport layer connection is actively opened. Mobile stations shall maintain the temporary IP address only while a transport layer connection is open or is being opened, and shall discard the temporary IP address when the transport layer connection is closed... Link Control Protocol If the protocol identifier is 0xc0, the PPP layer shall process the packet according to the PPP Link Control Protocol (LCP). If the protocol identifier is 0x0, the IPCP sublayer shall process the packet. For other supported protocol identifiers, the PPP layer shall remove the PPP encapsulation and shall pass the datagram and protocol identifier to the SNDCF. For unsupported protocol identifiers, the LCP Protocol-Reject shall be passed to the RLP layer for transmission. The mobile station shall support the PPP LCP Configure-Request, Configure-Ack, Configure-Nak, Configure-Reject, Terminate-Request, Terminate-Ack, Code-Reject, and Protocol-Reject. Other LCP packet types may also be supported. The PPP LCP shall negotiate the following configuration options: The protocol identifiers required by this standard are 0x00, 0x00d, 0x00f, 0xc0, and 0x0. -0

165 TIA/EIA/IS-0-A. 0 Async control character map. The mobile station shall not require any mapping of control characters. The IWF may negotiate mapping of control characters. Protocol field compression (applied when the protocol number is less than 0xff). Address and control field compression (applied when the protocol number is not 0xc0). The mobile station may support other configuration options (such as maximum receive unit, authentication protocol, link quality protocol, or magic number). When an option is received which is not supported, the Configure-Reject shall be sent as an indication to the peer... Requirements for Async Data and Fax... Traffic Channel Usage The RLP layer supporting the async data or fax service option shall be carried as primary traffic, or secondary traffic. When a traffic channel is activated and the async data or fax service option becomes active, the RLP layer shall perform the initialization/reset procedure specified in.. of IS-0.. -

166

167 TIA/EIA/IS-0-A REQUIREMENTS FOR THE RADIO INTERFACE The mobile station and the BS/MSC shall support the physical layer, multiplex sublayer, radio link management, and call control as defined in TSB. The mobile station and the BS/MSC shall not use quarter-rate frames to carry Service Option 00, 0,, or data when Multiplex Option is negotiated.. Service Option Number The mobile station and the BS/MSC shall use Service Option 00 for asynchronous data service and Service Option 0 for Group- fax service when Multiplex Option is the desired default multiplex option, or when service option negotiation is used. When Multiplex Option is desired as the default multiplex option and service negotiation is used, the mobile station and the BS/MSC shall use Service Option for asynchronous data services and for Group- fax services. Mobile stations supporting Service Option shall also support Service Option 00. Similarly, mobile stations supporting Service Option shall support Service Option 0.. Multiplex Option Interface Service Option 00 and Service Option 0 shall support an interface with Multiplex Option and may support an interface with Multiplex Option. RLP frames for Service Option 00 and Service Option 0 shall only be transported as primary traffic when service option negotiation is used. When service negotiation is used, Service Option 00 and Service Option 0 shall be transported as primary or secondary traffic. Service Option and Service Option shall support an interface with Multiplex Option and may support an interface with Multiplex Option. RLP frames for Service Options and shall only be transported as primary traffic or as secondary traffic.. Procedures Using Service Option Negotiation The mobile station may perform service option negotiation for Service Option 00 and Service Option 0 as described in... of TSB. The BS/MSC may perform service option negotiation for Service Option 00 and Service Option 0 as described in... of TSB. The mobile station and the BS/MSC shall not perform service option negotiation for Service Options and. The implicit service configuration associated with Service Options 00 and 0 when service option negotiation is used is shown in Table.-. -

168 TIA/EIA/IS-0-A. Table.-. Implicit Service Configuration Attributes for Service Options 00 or 0 when Service Option Negotiation is Used Service Configuration Attribute Valid Selections Forward Multiplex Option Multiplex Option Reverse Multiplex Option Multiplex Option Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type Rate Set with full rate, half rate and eighth rate frames enabled. Rate Set with full rate, half rate and eighth rate frames enabled. Primary Traffic Primary Traffic Initialization and Connection of the Service Option... Mobile Station Requirements If the mobile station sends a Service Option Response Order accepting Service Option 00 or Service Option 0 in response to receiving a Service Option Request Order, (see... of TSB), the mobile station shall initialize and connect Service Option 00 or Service Option 0 according to the following: If the mobile station is in the Conversation Substate, the mobile station shall complete the initialization and connection of the transmitting and receiving sides within 00 ms from the later of: - The implicit or explicit action time associated with the Service Option Request Order (see... of TSB), or - The time that the mobile station sends the Service Option Response Order accepting Service Option 00 or Service Option 0. If the mobile station is not in the Conversation Substate, the mobile station shall complete the initialization and connection of the transmitting and receiving sides within 00 ms from the later of: - The implicit or explicit action time associated with the Service Option Request Order, - The time that the mobile station sends the Service Option Response Order accepting Service Option 00 or Service Option 0, or - The time that the mobile station enters the Conversation Substate. If the mobile station receives a Service Option Response Order accepting its request for Service Option 00 or Service Option 0 (see... of TSB), the mobile station shall initialize and connect Service Option 00 or Service Option 0 according to the following: -

169 TIA/EIA/IS-0-A If the mobile station is in the Conversation Substate, the mobile station shall complete the initialization and connection of the transmitting and receiving sides within 00 ms of the implicit or explicit action time associated with the Service Option Response Order (see... of TSB). If the mobile station is not in the Conversation Substate, the mobile station shall complete the initialization and connection of the transmitting and receiving sides within 00 ms from the later of: - The implicit or explicit action time associated with the Service Option Response Order, or - The time that the mobile station enters the Conversation Substate. When the transmitting side of Service Option 00 or Service Option 0 is connected, the service option shall generate and transfer RLP frame data to the multiplex sublayer. When the receiving side is connected, the service option shall transfer and process RLP frame data from the multiplex sublayer. See... of TSB, for the actions to be taken when the transmitting side of a service option is not connected.... BS/MSC Requirements The BS/MSC should wait until the action time associated with the most recently transmitted Service Option Response Order or Service Option Request Order before initializing and connecting Service Option 00 or Service Option 0. When the transmitting side of Service Option 00 or Service Option 0 is connected, the service option shall generate and transfer RLP frame data to the multiplex sublayer. When the receiving side is connected, the service option shall transfer and process RLP frame data from the multiplex sublayer. See... of TSB, for the actions to be taken when the transmitting side of a service option is not connected.. Procedures Using Service Negotiation.. Mobile Station Requirements The mobile station shall perform service negotiation as described in TSB or J-STD-00, and the negotiated service configuration shall include only valid attributes for the negotiated service option as specified in Tables..- and..-. When service negotiation is used, Service Option 00 may be carried on either primary or secondary traffic channels. The default Forward Traffic Type for Service Option 00 shall be primary traffic. Service Option 0 shall be carried as primary traffic only. If Service Option 0 is to be established in accordance with option b of.. (i.e. the modem configuration includes the speaker on until connect feature), Service Option 0 shall be carried as secondary traffic only for the portion of the call during which there is a voice service option simultaneously connected as primary traffic. When service negotiation is used, Service Option may be carried on either primary or secondary traffic channels. The default Forward Traffic Type for Service Option shall be primary traffic. Service Option shall be carried as primary traffic only. If Service Option is to be established in accordance with option b of.. (i.e. the modem configuration includes the speaker on until connect feature), Service Option shall be carried as -

170 TIA/EIA/IS-0-A. secondary traffic only for the portion of the call during which there is a voice service option simultaneously connected as primary traffic. Table..-. Valid Service Configuration Attributes for Service Options 00 and 0 Service Configuration Attribute Valid Selections Forward Multiplex Option Multiplex Option or Reverse Multiplex Option Multiplex Option or Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type Rate Set with full rate, half rate and eighth rate frames enabled. Rate Set with all rates enabled. Rate Set with full rate, half rate and eighth rate frames enabled. Rate Set with all rates enabled. Primary Traffic or Secondary Traffic. Shall be the same as the Forward Traffic Type. Table..-. Valid Service Configuration Attributes for Service Options and Service Configuration Attribute Valid Selections Forward Multiplex Option Multiplex Option or Reverse Multiplex Option Multiplex Option or Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type Rate Set with full rate, half rate and eighth rate frames enabled. Rate Set with all rates enabled. Rate Set with full rate, half rate and eighth rate rates frames enabled. Rate Set with all rates enabled. Primary Traffic or Secondary Traffic Shall be the same as the Forward Traffic Type. 0 If the mobile station accepts a service configuration, as specified in a Service Connect Message, that includes a service option connection using service options 00, 0,, or, the mobile station shall perform the following: -

171 TIA/EIA/IS-0-A If the mobile station is in the Conversation Substate, and the service option connection is not part of the previous service configuration the mobile station shall initialize and connect the service option at the action time associated with the Service Connect Message. The mobile station shall complete the initialization within 00 ms of starting the connection. If the mobile station is not in the Conversation Substate, the mobile station shall initialize and connect the service option no later than the action time associated with the Service Connect Message. The mobile station shall complete the connection of the service option within 00 ms of starting the connection. Commencing at the time when the service option is connected and continuing for as long as the service configuration includes the service option connection, the service option shall generate and transfer RLP frame data to the multiplex sublayer. The service option shall also transfer and process RLP frame data received from the multiplex sublayer. When the transmitting side of the service option is connected, the service option shall generate and transfer RLP frame data to the multiplex sublayer. When the receiving side is connected, the service option shall transfer and process RLP frame data from the multiplex sublayer. See... of TSB for the actions to be taken when the transmitting side of a service option is not connected... BS/MSC Requirements If the BS/MSC establishes a service configuration, as specified in a Service Connect Message, that includes a service option connection using Service Options 00, 0,, or, the BS/MSC shall connect the service option no later than the action time associated with the Service Connect Message. Commencing at the time when the service option is connected and continuing for as long as the service configuration includes the service option connection, the service option shall process received RLP data frames and generate and supply RLP data frames for transmission in accordance with this standard. When the transmitting side of the service option is connected, the service option shall generate and transfer RLP frame data to the multiplex sublayer. When the receiving side is connected, the service option shall transfer and process RLP frame data from the multiplex sublayer. See... of TSB for the actions to be taken when the transmitting side of a service option is not connected. -

172

173 TIA/EIA/IS-0-A REQUIREMENTS FOR UM INTERFACE CALL PROCESSING. Connection Establishment.. Mobile Origination The mobile station shall initiate an async data or fax connection by the following procedure: When the mobile station application interface requests initiation of an async data or fax connection, it shall issue an active OPEN call to the transport layer. The OPEN call shall specify the modem server port number (0) as destination port, with the source and destination IP addresses unspecified. The IP addresses shall be provided to the Network Layer after completion of IPCP configuration. Transport layer data shall not be sent on the U m interface prior to completion of IPCP configuration. Call origination may be carried out in the following ways. BS/MSCs shall support (a) below, and may support (b) and/or (c). Options (a) and (c) are applicable to mobile stations and BS/MSCs that support either service option negotiation or service negotiation procedures. Option (b) below is only applicable to mobile stations and BS/MSCs that support service negotiation procedures. a. If the origination is initiated as a data or fax call (ATD command or appropriate AT+CXT setting followed by unrecognized modem commands) and the modem configuration includes the speaker off setting (ATM0 or default) the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA/IS--A requesting the appropriate data service option number. If the origination is initiated as a result of an ATD command, the mobile station shall place the dial string in the Origination Message. The mobile station shall include as many characters of the dial string as possible without exceeding the message capsule size. The mobile station shall include the entire dial string in the ATD command sent to the IWF. If the origination is initiated as a result of an unrecognized command, the mobile station shall place the unrecognized command, including the initial AT, in the Origination Message. The mobile station shall include as many characters of the command as possible without exceeding the message capsule size. The IWF should assign an IP address for the mobile station and issue a passive OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the modem server port number (0) as the local port, with the IWF s IP address as the local address. Subsequent mobile station and BS/MSC call state transitions shall follow the requirements of TIA/EIA/IS--A and TSB. When the mobile station and the BS/MSC enter the Conversation Substate they may perform service negotiation (see... of TSB) to establish a service configuration including the requested data service option. Following connection of the requested service option, the mobile station, BS/MSC, and IWF shall perform the actions specified in... -

174 TIA/EIA/IS-0-A If the origination is initiated as a result of an ATD command, and the mobile station did not send the complete dial string in the Origination Message, the mobile station shall send the remaining characters of the dial string to the BS/MSC in the Origination Continuation Message. The mobile station shall send the Origination Continuation Message as a message requiring acknowledgment (see... of TIA/EIA/IS--A) within T m seconds (defined in Appendix D of TIA/EIA/IS--A) after entering the Conversation Substate. b. If the origination is initiated as a data or fax call (ATD command or appropriate AT+CXT setting followed by unrecognized modem commands) and the modem configuration includes the speaker on until connect setting (ATM) the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA/IS--A requesting the appropriate data service option number. If the origination is initiated as a result of an ATD command, the mobile station shall place the dial string in the Origination Message. The mobile station shall include as many characters of the dial string as possible without exceeding the message capsule size. The mobile station shall include the entire dial string in the ATD command sent to the IWF. If the origination is initiated as a result of an unrecognized command, the mobile station shall place the unrecognized command, including the initial AT, in the Origination Message. The mobile station shall include as many characters of the command as possible without exceeding the message capsule size. The IWF should assign an IP address for the mobile station and issue a passive OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the modem server port number (0) as the local port, with the IWF's IP address as the local address. Subsequent mobile station and BS/MSC call state transitions shall follow the requirements of TIA/EIA/IS--A and TSB. When the mobile station and BS/MSC enter the Conversation Substate they may perform service negotiation (see... of TSB) to establish a service configuration including the requested data service option. Following connection of the requested service option, the mobile station, BS/MSC, and IWF shall perform the actions specified in... If the origination is initiated as a result of an ATD command, and the mobile station did not send the complete dial string in the Origination Message, the mobile station shall send the remaining characters of the dial string to the BS/MSC in the Origination Continuation Message. The mobile station shall send the Origination Continuation Message as a message requiring acknowledgment (see... of TIA/EIA/IS--A) within T m seconds (defined in Appendix D of TIA/EIA/IS--A) after entering the Conversation Substate. When the transport layer connection is in the ESTABLISHED state, the mobile station should negotiate a service configuration including a voice service option as primary traffic on the forward link and the requested data service option as secondary traffic. -

175 TIA/EIA/IS-0-A When this service configuration is established, the BS/MSC should connect the PSTN audio to the mobile station through the Forward Traffic Channel. The mobile station should transmit Reverse Traffic Channel data in accordance with the requirements of the connected service configuration. The BS/MSC should not connect any reverse link voice signals to the PSTN. While the voice service option is active, the BS/MSC should generate DTMF signals on the PSTN in response to TIA/EIA/IS--A signaling messages pertaining to DTMF, received from the mobile station. When this service configuration is established, the mobile station should send the dialing command (ATD) to the IWF as secondary traffic. Data carried by RLP while the data service option is connected as secondary traffic should be limited to commands from the mobile station application interface layer and responses from the IWF. When the mobile station detects that the IWF has asserted circuit 0 (CF), the mobile station should initiate service negotiation procedures with the BS/MSC to re-establish the initially requested service configuration. The BS/MSC should disconnect the PSTN audio from the Forward Traffic Channel at this time. When the async data or fax service option is connected, the RLP layer shall be reestablished on the traffic type originally negotiated. c. If the origination is initiated as a voice call, the mobile station may either transmit an Origination Message following the requirements of TIA/EIA/IS--A or may send an AT+CDV command, following the procedures of IS-0.. If the mobile station receives an ATD or ATA command on the R m interface while the mobile station is in the Mobile Station Control on the Traffic Channel State, the mobile station should transmit a Service Option Request Order or a Service Request Message to connect the appropriate data or fax service option and should issue an OPEN request to the transport layer, as described above. The IWF should assign an IP address for the mobile station and issue a passive OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the modem server port number (0) as the local port, with the IWF's IP address as the local address. When the data or fax service option is connected, the mobile station, BS/MSC, and IWF shall perform the procedures specified in..... Mobile Termination When a call is to be terminated to a mobile station directory number, the BS/MSC should determine the mobile station ID of the associated mobile station, and send a Page Message or General Page Message to that mobile station. The Page Message or General Page Message should include the appropriate Service Option number. Following connection of Methods for determining the service option number for mobile-terminated async data or fax calls (footnote continues on next page) -

176 TIA/EIA/IS-0-A the requested service option, the mobile station, BS/MSC, and IWF shall perform the actions specified in... For async data and fax calls, the IWF should assign an IP address for the mobile station and issue an active OPEN call to the transport layer. The OPEN call shall specify the modem client port number () as destination, with the IWF's IP address as the source address and the mobile station s assigned IP address as the destination address. The mobile station shall always respond to a Page Message or General Page Message specifying data or fax service options. Mobile stations may also be configurable to accept only async data or fax service options. If so configured, a mobile station may respond to a Page Message or General Page Message by including a request for these service options. When the mobile station user configures the async data or fax service for auto-answer mode (by setting the S0 register to a nonzero value), the mobile station shall perform autoanswer, defined as follows: After the mobile station enters the Waiting for Mobile Station Answer Substate the mobile station shall send a Connect Order after the time specified in register S0, and shall immediately enter the Conversation Substate. If the mobile station enters the Conversation Substate in this manner, the mobile station shall perform the following actions: If a service option other than async data or fax is connected the mobile station shall perform one of the following: + If service option negotiation is used the mobile station shall initiate service option negotiation to change to the async data or fax service option, as appropriate for the current stored modem configuration. Service option negotiation shall be completed as specified in section... and... of TSB. + If service negotiation is used, the mobile station shall negotiate a service configuration to connect the async data or fax service option as appropriate for the current stored modem configuration. Service negotiation shall be completed as specified in section... and... of TSB. The mobile station application interface shall issue a passive OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the modem client port number () without a local network (IP) address. When the async data or fax service option becomes connected while in the Conversation Substate, the mobile station application interface shall send the answer command ( ATA ), are outside the scope of this standard. Approaches include a distinct directory number for each service option, two-stage dialing, and service option switching. -

177 TIA/EIA/IS-0-A preceded by configuration commands as required in.. of IS-0., prior to sending any other data from the R m interface... Service Option Change to Group- Facsimile Service If the mobile station and the BS/MSC are in the Conversation Substate with a connected service option other than Group- fax, service negotiation procedures consistent with... of TSB may be performed to connect a fax service option. Following connection of the negotiated service option, the mobile station, the BS/MSC and the IWF shall perform the actions specified in... Service negotiation may be initiated in one of the following scenarios: If the PSTN fax machine is the fax calling station, either the mobile station or the BS/MSC may detect T.0 CNG tone and initiate service negotiation procedures. If the mobile station is the fax calling station, the MT or MT0 shall initiate service negotiation procedures in response to the ATD command with no dialed number. The BS/MSC should indicate the call type of the initial call: mobile terminated or mobile originated. The IWF should assign an IP address for the mobile station and perform one of the following actions: If the initial call was mobile terminated, the IWF shall issue an active OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the modem client port number () as the destination, with the IWF's IP address as the source address and the mobile station's assigned IP address as the destination address. If the initial call was mobile originated, the IWF shall issue a passive OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specified the client server port (0) as the local port, with the IWF's IP address as the source address. If the PSTN fax machine is the fax calling station, upon receiving an ATA command, the IWF shall send a CED tone to the PSTN fax machine. If the mobile station is the fax calling station, upon receiving an ATD command without a dialed number, the IWF shall send a CNG tone to the PSTN fax machine. When the fax service option becomes connected while in the Conversation Substate, the mobile station shall perform the following actions: If the PSTN fax machine is the fax calling station, the MT shall generate and send a RING result code to the TE after sending the stored configuration string to the IWF. The MT should repeat sending the RING result code as many times as specified in Register S0 until an ATA command is received. If the initial call was mobile terminated, the mobile station application interface shall issue a passive OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the modem client port number () without a local network (IP) address. If the initial call was mobile originated, the mobile station application interface shall issue an active OPEN call to the transport layer. The OPEN call shall specify the -

178 TIA/EIA/IS-0-A modem server port number (0) as destination port, with the source and destination IP addresses unspecified... Conversation Substate When either the mobile station or the BS/MSC enters the Conversation Substate with an async data or fax service option connected, it shall begin RLP initialization/reset as described in.. of IS-0.. The BS/MSC should also open an L-Interface virtual circuit to the IWF prior to the completion of RLP initialization. When the L-Interface virtual circuit has been opened, the IWF relay layer should signal this event to the PPP layer. The PPP layer and IPCP sublayer in the IWF shall then carry out self-configuration, as described in.. and... The IWF shall send an IPCP Configure-Request with an IP-Compression-Protocol parameter set consistent with.. and with the IP-address parameter set to the IP address associated with the assigned IWF. The mobile station shall store the IWF's IP address and shall place the IWF's IP address in the destination address field of all IP datagrams sent while the transport layer remains connected. If the mobile station s IPCP Configure-Request contains an IP address of all zeros, the IWF shall select an IP address to be used by the mobile station and shall send a Configure-Nak with the IP-address parameter set to the IP address selected. The IWF shall select an IP address for each mobile station using async data or group fax service options conforming with the requirements of... The mobile station s IPCP sublayer shall store the assigned address and pass it to the network layer for use as a source address in all IP datagrams sent to the IWF while the transport layer connection remains open. The remaining exchange of IPCP configuration related messages shall be in accordance with RFC. When the transport layer enters the ESTABLISHED state, the transport layer may begin sending and receiving characters to/from the peer application interface. The mobile station shall transmit its stored configuration and the AT command that caused the establishment of the transport layer connection in accordance with. of IS-0.. The IWF should provide a command state inactivity timer 0 that is started when the transport layer connection enters the ESTABLISHED state and is disabled when an ATA or ATD command is received. The command state inactivity timer should be restarted when any data are sent to or received from the mobile station on the L interface. If the command state inactivity timer expires, the transport layer connection should be closed, using the procedures of.. The timer duration is set by the AT+CQD command (see.. of IS- 0.)... Traffic Channel Handoff Soft handoff (see... of TIA/EIA/IS--A) or a CDMA-to-CDMA hard handoff (see... of TIA/EIA/IS--A) entailing only a change in the frame offset field shall not affect the state of any of the protocols for async data or fax. 0 This timer does not apply to the online command state. -

179 TIA/EIA/IS-0-A Following a CDMA-to-CDMA hard handoff (see... of TIA/EIA/IS--A) involving transitions between disjoint sets of BS/MSCs or a frequency change, the RLP layer shall be reset and immediately re-established. This is necessary to ensure proper re-establishment of RLP after an intersystem handoff, which is not distinguishable from other hard handoffs under TIA/EIA/IS--A. Data lost during the reset of RLP will be retransmitted by the transport layer. CDMA-to-analog handoffs are not supported for Service Options 00, 0,, and. The mobile station and the IWF shall close the transport layer connection if the mobile station moves outside of CDMA coverage (see..).. Connection Release The async data or fax service is considered connected when the transport layer is in the ESTABLISHED state. Each of the following conditions shall cause the transport layer connection to be closed by means of the CLOSE call to the transport layer: The application interface directs the transport layer to close the connection. The command state inactivity timer expires, as specified in... The IWF detects that the PSTN connection has been lost or that the remote modem or fax device has released the connection. The IWF is directed to release the call (ATH command). The mobile station moves away from CDMA coverage. The end-to-end connect timer (register S) expires. If the IWF detects a transport layer failure, as specified in., the IWF shall close the transport layer by means of an ABORT call. If the IWF closes the transport layer in this manner, the IWF should release the L-Interface virtual circuit. If the IWF closes the L-Interface virtual circuit, the BS/MSC should release the traffic channel to the Mobile Station, and should release the PSTN call. The BS/MSC should close the L-Interface virtual circuit, and release the PSTN call when any of the following occur: The BS/MSC receives a Release Order with a power-down indication. The BS/MSC cannot support the requested service option. The mobile station releases the traffic channel. A TIA/EIA/IS--A Lock Order is sent to the mobile station. Support of dormant mode and automatic reconnect are for further study. These features will require maintaining the transport layer connection after a call release or drop. -

180 TIA/EIA/IS-0-A. 0 The mobile station shall close the transport layer by means of an ABORT call to the transport layer if any of the following occur: The mobile station powers down. The mobile station receives a TIA/EIA/IS--A Release Order indicating that the requested service option is rejected. A TIA/EIA/IS--A Lock Order is received by the mobile station. When the transport layer is to be closed via a CLOSE call to the transport layer and a traffic channel is active, the mobile station or BS/MSC shall perform the following: If the connection is to be closed because the mobile station is powering down, the mobile station may send a Release Order with power-down indication and immediately power down. In all other cases, the transport layer initiating the close shall close the connection in accordance with the requirements of RFC.. Authentication Authentication of mobile station initiated data calls shall be conducted according to the procedure described in.. of TIA/EIA/IS--A. For mobile-originated data calls, the BS/MSC should complete an authentication Unique Challenge immediately after assigning the traffic channel, and before connecting the async data or fax service option. -

181 TIA/EIA/IS-0-A. 0 0 RECOMMENDATIONS FOR THE MODEM TO PSTN INTERFACE. Recommended Modem Standards The IWF should support the following modem standards for asynchronous data and fax service: V., V., V.bis, V., V.bis, V., V.bis, V., V.ter, and V.. The IWF may support V., Bell 0, and Bell-A. This standard also provides AT command support for Telephone Devices for the Deaf (TDD). IWF manufacturers supporting digital TDD services should support the following modem standards (see ITU-T V. - ): V., V. reversed, V., Baudot, Bell 0, DTMF Coding, and European Deaf Telephone (EDT) mode.. Flow Control.. Flow Control for Async Data The IWF may implement flow control over the A i interface in one of two ways: By use of V.. This protocol allows for flow control between the IWF and the remote PSTN DCE. If software flow control is enabled on the PSTN interface the IWF may send (and shall interpret) XON and XOFF. This allows for flow control between the IWF and the remote terminal... Flow Control for Group- Fax The PSTN interface can operate at higher rates than are possible on the U m interface. The rate discrepancy results in buffering requirements at the BS/MSC and IWF and, eventually, for a need to flow control the land side fax machine. Since Group- fax is a half-duplex service, there is no mechanism for providing true flow control over the PSTN but indirect methods that accomplish a form of flow control can be used under some circumstances. This standard does not specify means for a mobile station to enable or disable software flow control at the IWF. IWFs may implement special purpose AT commands for this purpose. A TE or an MT0 application may transmit such commands using the AT+CXT and AT+CFG cellular extensions. -

182

183 Data Service Options for Spread Spectrum Systems: Packet Data Services TIA/EIA/IS-0-A. (PN-.) Ballot Resolution Version March

184 Copyright TIA

185 TIA/EIA/IS-0-A. CONTENTS INTRODUCTION -. General Description...-. Terms...-. References...-. Overview of Packet Data Service Packet Data Service Types and Configurations Protocol Options Relay Layer Rm Interface Protocol Option Network Layer Rm Interface Protocol Option Packet Data Protocol States IWF Link Layer Connection States Mobile Station Packet Data Service States BS/MSC Packet Data Service States...- RELAY LAYER -. Introduction...-. Um Interface Requirements RLP Requirements Service and Call Control Procedures Mobile Station Procedures Packet Data Service Control Procedures Inactive State Active State Packet Data Service Call Control Function Null State Initialization/Idle State Initialization/Traffic State Connected State Dormant/Idle State Dormant/Traffic State Reconnect/Idle State Reconnect/Traffic State...- i

186 TIA/EIA/IS-0-A CONTENTS... BS/MSC Procedures Packet Data Service Control Procedures Inactive State Active State Packet Data Service Call Control Function Null State IWF Initiated Link Layer Connection Reactivation Mobile Station Originated Link Layer Connection Activation Mobile Station Negotiated Link Layer Connection Activation IWF Link Layer Closure IWF Transfer Paging State Initialization/Idle State Initialization/Traffic State Connected State Initialization and Connection of Packet Data Service Options Procedures Using Service Option Negotiation Mobile Station Procedures BS/MSC Procedures Procedures Using Service Negotiation Mobile Station Procedures BS/MSC Requirements Optional Zone-Based Registration or Reconnection Optional Reconnect After Hard Handoff Optional Packet Data Dormant Timer Control Optional Packet Zone Reconnection Control...-. L Interface Logical Connections Mobile Data...-0 LINK LAYER -. Link Layer Protocols...-. Link Layer Connections...- ii

187 TIA/EIA/IS-0-A. 0 CONTENTS.. IWF Link Layer Connection Opening IWF Link Layer Connection Maintenance IWF Link Layer Connection Closure BS/MSC Closure IWF Closure TE Closure MT Closure...- NETWORK LAYER -. Internet Protocol Support...-. ISO Protocol Support...-. CDPD Application Support...- iii

188 TIA/EIA/IS-0-A. FIGURES Figure...-. Relay Layer Rm Interface Protocol Option... - Figure...-. Network Layer Rm Interface Protocol Option... - Figure...-. Packet Data Service Call Control States in the Mobile Station... - Figure...-. Packet Data Service Call Control States in the BS/MSC TABLES Table...-. Implicit Service Configuration for Service Options 0 and Table...-. Valid Service Configuration Attributes for Service Options 0 and Table...-. Valid Service Configuration Attributes for Service Options and... - Table..-. ORDQ Format and Type-Specific Fields for Zone-Based Registration/Reconnection... - 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..-. Dormant Timer Control Field... - Table..-. Minimum Value of Mobile Station Dormant Timer... - Table..-. Type-Specific Fields for Packet Connection Control... - Table..-. Packet Zone Connection Control Field... - Table..-. Type-Specific Fields for Packet Zone Connection Response... - iv

189 TIA/EIA/IS-0-A INTRODUCTION. General Description This chapter of IS-0 defines requirements for support of packet data transmission capability on TIA/EIA/IS- wideband spread spectrum systems. Packet data transmission is supported on TIA/EIA/IS- Traffic Channels using primary or secondary traffic. For packet data transmission using TIA/EIA/IS- Traffic Channels, the Non- Transparent Radio Link Protocol specified in IS-0. is used. This standard specifies a packet data bearer service for communication between terminal equipment and a packet interworking function (IWF) via a base station/mobile switching center (BS/MSC). It provides procedures that can apply to multiple packet data services e.g., CDPD and Mobile-IP. Service Options 0 and 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. and.). Service Option 0 and are used to request packet data service through an IWF supporting CDPD data services over a PPP interface (see.). Additional packet data service options may be defined in future revisions to select other types of IWF resources or services. Packet data service options provide a means of establishing and maintaining Traffic Channels for packet data service. When TIA/EIA/IS- service negotiation procedures are used, packet data service can be carried as primary or as secondary traffic. When the service option negotiation procedures of TIA/EIA/IS- are used, packet data service can be carried as primary traffic only.. Terms Base Station (BS). A station in the Domestic Public Cellular Radio Telecommunications Service, other than a mobile station, used for communicating with mobile stations. Depending upon the context, the term base station may refer to a cell, a sector within a cell, or other part of the cellular system. BS. See base station. BS/MSC. The base station and mobile switching center considered as a single functional entity. CDPD. Cellular Digital Packet Data. CLNP. Connectionless Network Protocol (See ISO -). Data Circuit-Terminating Equipment (DCE). A DCE connects a DTE to the PSTN. A typical DCE would be a V-series modem. DTE. Data Terminal Equipment. IWF. Interworking Function (see..). IP. Internet Protocol. IPCP. Internet Protocol Control Protocol (see RFC ). -

190 TIA/EIA/IS-0-A. 0 0 LCP. PPP Link Control Protocol (see RFC ). Mobile IP. Mobile Internet Protocol (See RFC 00). Mobile Station. A station in the Domestic 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. MT0. Mobile Termination 0 (see..). MT. Mobile Termination (see..). OSINLCP. OSI Network Layer Control Protocol (see RFC ). PPDN. Public Packet Data Network. PPP. Point to Point Protocol (see RFC ). PSTN. Public Switched Telephone Network. RFC. Request for Comments. The generic name of a specification developed by the Internet Engineering Task Force (IETF). RLP. Radio Link Protocol. SLIP. Serial Line IP. TCP. Transmission Control Protocol. TE. Terminal Equipment (see..).. References 0 ANSI/TIA/EIA- EIA/TIA--E EIA/TIA-0 Inband DCE Control for Asynchronous DTE DCE Interfaces. Common Cryptographic Algorithms Revision A.. An ITAR controlled document subject to restricted distribution. Contact the Telecommunications Industry Association, Washington, D.C., April,. Interface Specification for Common Cryptographic Algorithms Revision A, Telecommunications Industry Association, Washington, D.C., December,. Interface Between DTE and DCE Employing Serial Binary Data Interchange. Serial Asynchronous Automatic Dialing and Control. ISO - Information processing systems -- Data communications -- Protocol for providing the connectionless-mode network service. ISO/IEC TR-0 Information technology -- Telecommunications and information exchange between systems -- Protocol identification in the network layer. -

191 TIA/EIA/IS-0-A. 0 0 RFC RFC 0 RFC RFC RFC RFC 0 RFC RFC RFC 00 RFC 00 TIA/EIA/IS- TIA/EIA/IS- TIA/EIA/IS- TSB TSB Internet Protocol. Nonstandard for transmission of IP datagrams over serial lines: SLIP. Compressing TCP/IP Headers for Low-Speed Serial Links. The PPP Internet Protocol Control Protocol (IPCP). The PPP OSI Network Layer Control Protocol (OSINLCP). PPP LCP Extensions. The Point-to-Point Protocol (PPP). PPP in HDLC-like Framing. Assigned Numbers. IP Mobility Support. Mobile Station-Base Station Compatibility Standard for Dual- Mode Wideband Spread Spectrum Cellular System. Data Services Interworking Function Interface Standard for Wideband Spread Spectrum Digital Cellular System. Cellular Digital Packet Data System Specification. Note that this is a series of standards, each of which begins with the designation TIA/EIA/IS-, and ends with partnumber, where partnumber identifies the particular standard within the series. Administration of Parameter Value Assignments for TIA/EIA Wideband Spread Spectrum Standards. Telecommunications Systems Bulletin: Support for. kbps Data Rate and PCS Interaction for Wideband Spread Spectrum Cellular Systems. 0. Overview of Packet Data Service.. Packet Data Service Types and Configurations Packet Data Service can be of two types. Type Packet Data Service provides packet data connections based on Internet and ISO standard protocol stacks, while Type Packet Data Service provides packet data connections based on CDPD protocol stacks. Two rate sets are supported with two unique service option numbers for each packet data service type. Type Packet Data Service includes service option connections using either Service Option 0 or Service Option. Type Packet Data Service includes service option connections using either Service Option 0 or Service Option. -

192 TIA/EIA/IS-0-A. 0.. Protocol Options This standard provides the requirements for communication protocols on the links between a mobile station and IWF, including requirements for the R m, U m and L interfaces. The Relay Layer provides lower layer communication and packet framing between the entities of the packet data service reference model. Over the R m interface between the TE and the MT, the Relay Layer is a simple EIA/TIA--E interface. Over the U m interface, the Relay Layer is a combination of Non-Transparent RLP (defined in IS-0.) and the TIA/EIA/IS- protocols. On the L interface, the Relay Layer uses the protocols defined in TIA/EIA/IS-. The two options for packet protocol stacks are presented in... and Relay Layer R m Interface Protocol Option The Relay Layer R m interface protocol option supports TE applications in which the TE is responsible for all aspects of packet data service mobility management and network address management (e.g., IPCP and the CDPD registration and authentication protocols). For the Relay Layer R m interface protocol option, the packet data service protocol stack is as shown in Figure...-. Mobile Station TE MT BS/MSC IWF Upper Protocol Layers Upper Protocol Layers Network Layer Network Layer Protocols Network Layer Protocols Link Layer PPP PPP Relay Layer EIA- EIA- RLP IS- RLP IS- Relay Layer Relay Layer 0 R m U m L Figure...-. Relay Layer R m Interface Protocol Option -

193 TIA/EIA/IS-0-A. 0 In this protocol option, the Link Layer is implemented using PPP, as defined in RFC. When using the Relay Layer R m interface protocol option, the Link Layer connection is between the TE and the IWF. The Network Layer includes protocols, such as IP and CLNP, and packet data network registration and authentication protocols, such as MNRP. Recommendations for the use of certain specific protocols are given in Section.... Network Layer R m Interface Protocol Option The Network Layer R m interface protocol option supports TE applications in which the MT is responsible for all aspects of packet mobility management and network address management (e.g., IPCP, and the CDPD registration and authentication protocols). For the Network Layer R m interface protocol option, the packet data service protocol stack is as shown in Figure...-. Mobile Station TE MT BS/MSC IWF Upper Protocol Layers Upper Protocol Layers Network Layer IP or CLNP IP or CLNP Network Layer Protocols Network Layer Protocols Link Layer PPP or SLIP PPP or SLIP PPP PPP Relay Layer EIA- EIA- RLP IS- RLP IS- Relay Layer Relay Layer R m U m L Figure...-. Network Layer R m Interface Protocol Option 0 In this protocol option, there are independent Link Layer connections between the TE and the MT, and between the MT and the IWF. The IWF Link Layer (between the MT and the IWF) is implemented using the Internet Point-to-Point Protocol (PPP) defined in RFC. The R m Link Layer (between the MT and the TE) should be implemented using the Internet Point-to-Point Protocol (PPP) defined in RFC. Alternatively, the SLIP protocol as defined in RFC 0 may be used between the MT and the TE to support the IP network layer protocol. -

194 TIA/EIA/IS-0-A For this R m interface protocol option, the Network Layer also provides independent services between the TE and the MT, and between the MT and the IWF. The TE includes routing protocols, and operates as if locally connected to a network routing server. The MT includes both routing and packet data network registration and authentication protocols... Packet Data Protocol States... IWF Link Layer Connection States The IWF and the mobile station use a Link Layer connection to transmit and receive packet data. The IWF Link Layer connection is opened when a packet data service option is first connected. Once an IWF Link Layer connection is opened, bandwidth (in the form of Traffic Channel assignment) is allocated to the connection on an as-needed basis. The IWF Link Layer connection can be in any of the following states: Closed: The IWF Link Layer connection is closed when the IWF has no Link Layer connection state information for the mobile station. Opened: The IWF Link Layer connection is opened when the IWF has Link Layer connection state information for the mobile station. The opened state has two substates: - Active: An opened IWF Link Layer connection is active when there is an L interface virtual circuit for the mobile station and the mobile station is on a Traffic Channel with a packet data service option connected. - Dormant: An opened IWF Link Layer connection is dormant when there is no L interface virtual circuit for the mobile station, and the mobile station is not on a Traffic Channel with a packet data service option connected. The BS/MSC and IWF maintain the state of the Link Layer connection as defined above. The mobile station maintains the state of the PPP Link Control Protocol (LCP), and manages the IWF Link Layer connection using the LCP opening and closing procedures defined in RFC. When the IWF Link Layer Connection is dormant and either the Mobile Station or the BS/MSC has data to send, it is not necessary to re-open the Link Layer Connection or to re-initialize any upper layer protocols, provided the service type has not changed since the link layer last entered the Dormant State. Thus Mobile Stations and BS/MSCs complying with this standard can freely mix packet data service requests using either rate set within a service type. -

195 TIA/EIA/IS-0-A Mobile Station Packet Data Service States Packet data service processing in the mobile station consists of the following states. Requirements for the transitions between these states are given in... Inactive State - In this state, the mobile station does not provide packet data service. Active State - In this state, the mobile station provides packet data service. The mobile station performs the packet data service call control function described in... As illustrated in Figure...-, the packet data service call control function consists of the following states: Null State - The packet data service call control function is in this state when packet data service has not been activated. Initialization/Idle State - In this state, the mobile station attempts to establish a Traffic Channel for the purpose of initiating packet data service. Initialization/Traffic State - In this state, the mobile station is communicating with the BS/MSC on a Traffic Channel, and attempts to connect a packet data service option for the purpose of initiating packet data service. Connected State - In this state, a packet data service option is connected. The mobile station can transfer packet data. Dormant/Idle State - In this state, the mobile station is not on a Traffic Channel. The mobile station cannot transfer packet data. Dormant/Traffic State - In this state, the mobile station is communicating with the BS/MSC on a Traffic Channel, but the packet data service option has been disconnected. The mobile station cannot transfer packet data. Reconnect/Idle State - In this state, the mobile station attempts to establish a Traffic Channel. Reconnect/Traffic State - In this state, the mobile station is communicating with the BS/MSC on a Traffic Channel, and attempts to connect a packet data service option. -

196 TIA/EIA/IS-0-A. Service option rejected or release; deactivates packet data service Receives release, reorder, etc.; deactivates packet data service Initialization/Idle State Traffic Channel is initialized; requests packet service option Service is activated, mobile station is not on a Traffic Channel; sends origination Null State Service is activated, mobile station is on a Traffic Channel; requests packet service option Traffic Channel is initialized; requests packet service option Service option rejected; deactivates packet data service Reorder Reconnect/Idle State Release Initialization/ Traffic State Reconnect/Traffic State Service option connected Service option connected Connected State Release Note: not all state transitions are shown Service option connected Dormant/Traffic State Traffic Channel initialized Service option disconnected Release Dormant/Idle State Data to send; requests packet service option Serving system change or data to send; sends origination Figure...-. Packet Data Service Call Control States in the Mobile Station... BS/MSC Packet Data Service States Packet data service processing in the BS/MSC consists of the following states. Requirements for the transitions between these states are given in... -

197 TIA/EIA/IS-0-A. 0 Inactive State - In this state, the BS/MSC does not provide packet data service to the mobile station. Active State - In this state, the BS/MSC provides packet data service to the mobile station. The BS/MSC performs the packet data service call control function described in... As illustrated in Figure...-, the packet data service call control function consists of the following states: Null State - In this state, the BS/MSC has no connection of a packet data service option to the mobile station. Paging State - In this state, the IWF has requested that the BS/MSC connect a packet data service option to the mobile station for the delivery of packet data, and the BS/MSC pages the mobile station. Initialization/Idle State - In this state, the BS/MSC is awaiting initialization of a Traffic Channel with the mobile station. Initialization/Traffic State - In this state, the mobile station is on a Traffic Channel. The BS/MSC awaits connection of a packet data service option. Connected State - In this state, a packet data service option has been connected. Packet data is exchanged with the mobile station. -

198 TIA/EIA/IS-0-A. Receives Link Layer reactivation request, mobile station is not on Traffic Channel; pages mobile station Service option rejected; requests IWF Link Layer closure Paging State Receives page response; assigns Traffic Channel Receives origination; initiates Link Layer open or reactivation Null State Service option rejected; requests IWF Link Layer closure Initialization/Idle State Receives service option request for packet service from mobile station is on Traffic Channel or receives Link Layer reactivation request while mobile station is on Traffic Channel; negotiates packet service option Service option rejected; requests IWF Link Layer closure Traffic Channel initialized; negotiates packet service option Initialization/Idle State Note: not all state transitions are shown Service option connected Connected State Service option disconnected Figure...-. Packet Data Service Call Control States in the BS/MSC -0

199 TIA/EIA/IS-0-A. 0 RELAY LAYER. Introduction The Relay Layer spans across the R m, U m and L interfaces. See Section. of IS-0. for R m interface requirements. U m interface requirements and L interface requirements for the Relay Layer are described in the following sections. RLP can be carried either as primary traffic or as secondary traffic. The mobile station and the BS/MSC shall support the physical layer, multiplex options, radio link management, and call control protocols as defined in TIA/EIA/IS-. At the L interface, the BS/MSC and the IWF can use the protocols recommended in TIA/EIA/IS- for transport of end-user data and control information.. U m Interface Requirements RLP Requirements At the U m interface, the mobile station and the BS/MSC shall send packet data on the Traffic Channel using the Non-Transparent Radio Link Protocol defined in IS-0.. In this specification, the Non-Transparent Radio Link Protocol will be called simply RLP. For Service Options 0 and, mobile stations complying with this standard may support encryption of RLP data frames using the procedures defined in IS-0.. For Service Options 0 and, mobile stations complying with this standard shall support RLP data frame encryption using the procedures defined in IS-0.. Packet data encryption shall be performed whenever cellular authentication procedures have been performed during the establishment of a Traffic Channel and RLP data encryption is negotiated (see Section... of IS-0.)... Service and Call Control Procedures... Mobile Station Procedures The packet data service states for mobile stations are described in... Mobile station states are described in. of TIA/EIA/IS-. When power is applied to the mobile station, the packet data service shall enter the Inactive State and the packet data service call control function shall enter the Null State.... Packet Data Service Control Procedures... Inactive State When the packet data service is in the Inactive State, the mobile station does not provide packet data service. The means for determining when the packet data service enters the Active State are left to the mobile station manufacturer. -

200 TIA/EIA/IS-0-A Active State When the packet data service is in the Active State, the mobile station provides packet data service. While the packet data service is in the Active State, the service negotiation procedures described in... and... of TIA/EIA/IS- can be used to simultaneously connect other service options as primary or secondary traffic. This is intended, for example, to permit the simultaneous and independent connection and disconnection of voice and packet data services. Complete mobile station procedures for invoking and controlling such simultaneous connections require further study, and are left for future revisions of this standard. Until other procedures are defined, mobile stations can connect a voice call while the packet data service call control function is in the Connected State by releasing the Traffic Channel, sending an Origination Message containing the voice service option and the dialed digits, and performing service negotiation to connect a service configuration containing voice as primary traffic and packet data as secondary traffic. While voice and packet data service options are connected, the mobile station should process all received and transmitted service-related signaling messages, such as Flash With Information and Alert With Information, as pertaining only to the voice service. Mobile stations can disconnect the voice service option by releasing the Traffic Channel, after which the packet data service call control function automatically reconnects the packet data service option as described in Packet Data Service Call Control Function... Null State The mobile station packet data service call control function is in the Null State whenever the packet data service is in the Inactive State. If the packet data service enters the Active State, the mobile station shall perform the following: If the Network Layer R m interface protocol option is selected, and the R m interface Link Layer is implemented using PPP, the MT shall initiate PPP configuration on the R m interface, using the procedures defined in RFC. If the mobile station is in the Mobile Station Idle State, the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA/IS-. The mobile station should include the packet data service option in the SERVICE_OPTION field of the Origination Message (see... of TIA/EIA/IS-). The packet data service call control function shall enter the Initialization/Idle State with a packet origination indication. If the mobile station is in the Mobile Station Control on the Traffic Channel State, the mobile station shall initiate connection of the packet data service option, as described in... The packet data service call control function shall enter the Initialization/Traffic State. -

201 TIA/EIA/IS-0-A If the mobile station is in any other state or substate, the packet data service call control function shall enter the Initialization/Idle State with a mobile station wait indication.... Initialization/Idle State While the packet data service call control function is in the Initialization/Idle State, the mobile station shall perform the following: If the mobile station enters the Mobile Station Control on the Traffic Channel State, the mobile station shall initiate connection of the packet data service option, as described in... The packet data service call control function shall enter the Initialization/Traffic State. If the Initialization/Idle State was entered with a mobile station wait indication, and the mobile station enters the Mobile Station Idle State, the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA/IS-. The mobile station should include the packet data service option in the SERVICE_OPTION field of the Origination Message (see... of TIA/EIA/IS-). The packet data service call control function shall re-enter the Initialization/Idle State with a packet origination indication. If the Initialization/Idle State was entered with a packet origination indication, the packet data service shall enter the Inactive State if any of the following occur: The mobile station enters the Mobile Station Initialization State; or The mobile station exits the System Access State and enters any state other than the Mobile Station Control on the Traffic Channel State. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State.... Initialization/Traffic State While the packet data service call control function is in the Initialization/Traffic State, the mobile station shall perform the following: The mobile station packet data service call control function shall perform service negotiation or service option negotiation, as described in... of TIA/EIA/IS-, to connect the requested service configuration. If the packet data service option is connected, the packet data service call control function shall enter the Connected State. If the mobile station exits the Mobile Station Control on the Traffic Channel State, the packet data service shall enter the Inactive State and the packet data service call control function shall enter the Null State. If the packet data service option cannot be connected, the packet data service shall enter the Inactive State. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State. If no other service option is connected, -

202 TIA/EIA/IS-0-A the mobile station shall send a Release Order and shall enter the Release Substate of the Mobile Station Control on the Traffic Channel State.... Connected State When the packet data service call control function enters the Connected State, the mobile station begins initialization of the RLP layer (see Section... of IS-0.). While in the Connected State, the mobile station shall perform the following: If the mobile station exits the Mobile Station Control on the Traffic Channel State, the mobile station shall perform the following: If the mobile station has data to send, the packet data service call control function shall enter the Reconnect/Idle State with a channel loss indication. Otherwise, the packet data service call control function shall enter the Dormant/Idle State. The mobile station shall maintain a packet data inactivity timer. The value of this timer shall not be less than 0 seconds. The timer should be reset whenever a nonidle RLP data frame is sent or received. If the packet data inactivity timer expires, the mobile station should disconnect the packet data service option. To disconnect the packet data service option, the mobile station shall perform the following: If the packet data service option is the only connected service option, the mobile station shall send a Release Order and enter the Release Substate of the Mobile Station Control on the Traffic Channel State. Otherwise, the mobile station shall negotiate a service configuration that does not include the packet data service option. If the packet data service option is disconnected and the mobile station remains on the traffic channel, the packet data service call control function shall enter the Dormant/Traffic State. If the packet data service enters the Inactive State, the mobile station shall perform the following: If the Network Layer R m interface protocol option is selected, the MT should close the IWF Link Layer connection (see...) before disconnecting the packet data service option. If the packet data service option is the only connected service option, the mobile station shall send a Release Order and shall enter the Release Substate of the Mobile Station Control on the Traffic Channel State. Otherwise, the mobile station shall negotiate a service configuration that does not include the packet data service option. The packet data service call control function shall enter the Null State. -

203 TIA/EIA/IS-0-A Dormant/Idle State While the packet data service call control function is in the Dormant/Idle State, the mobile station shall perform the following: If the mobile station enters the Mobile Station Control on the Traffic Channel State, the packet data service call control function shall enter the Dormant/Traffic State. The mobile station shall attempt to reconnect the packet data service option, using the procedures specified below, if any of the following occurs: The packet data service has data to send; or The mobile station is in the Mobile Station Idle State and detects that the SID or NID of the serving system has changed; or The mobile is in the Mobile Station Idle State and detects a non-zero PACKET_ZONE_ID S that is not currently stored in its packet data zone identifier list (see..); or The mobile station enters the Mobile Station Idle State after a call release, and the SID or NID of the serving system at the start of the call is unknown, or the SID or NID of the serving system after call release is different from the SID or NID of the serving system at the start of the call. The mobile station shall maintain a packet data dormant timer controllable by the BS/MSC (see..). The default value for this timer shall be 0 seconds. The timer shall be reset upon entering the Dormant/Idle State. The mobile station shall delay any attempt to send an Origination Message requesting a packet data service option until the expiration of this timer. If the mobile station attempts to reconnect the packet data service option while the packet data service call control function is in the Dormant/Idle State, the mobile station shall perform the following: If the mobile station is in the Mobile Station Idle State, the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA/IS-. The mobile station should include the packet data service option in the SERVICE_OPTION field of the Origination Message (see... of TIA/EIA/IS-). The packet data service call control function shall enter the Reconnect/Idle State with a packet origination indication. If the mobile station is in any other state or substate, the packet data service call control function shall enter the Reconnect/Idle State with a mobile station wait indication. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State. The mobile station can enter the Mobile Station Control on the Traffic Channel State as a result of a page from the BS/MSC or an origination of a service by the mobile station. -

204 TIA/EIA/IS-0-A Dormant/Traffic State While in the Dormant/Traffic State, the packet data service call control function shall perform the following: If the packet data service option is connected, the packet data service call control function shall enter the Connected State when the mobile station enters the Conversation Substate. If the mobile station exits the Mobile Station Control on the Traffic Channel State, the packet data service call control function shall enter the Dormant/Idle State. If the packet data service has data to send, or the mobile station has detected a change in the serving system SID or NID or a non-zero PACKET_ZONE_ID S that is not currently stored in its packet data zone identifier list (see..) since the packet data service call control function last entered the Dormant/Traffic State, the mobile station shall perform the following: - If the service configuration of the mobile station permits connecting a packet data service, the mobile station shall initiate connection of the packet data service option. The packet data service call control function shall enter the Reconnect/Traffic State. - If the service configuration of the mobile station does not permit connecting a packet data service option, the mobile station may attempt to initiate connection of a packet data service option. If the mobile station attempts to initiate connection of the packet data service option, the mobile station packet data service call control function shall enter the Reconnect/Traffic State. - If the mobile station does not initiate connection of the packet data service option, either the packet data service call control function may remain in the Dormant/Traffic State, or the packet data service may enter the Inactive State. If the mobile station successfully completes a hard handoff (see... of TIA/EIA/IS-) in which the Active Set or frequency assignment changes, and the Reconnect After Hard Handoff feature is enabled (see..), the mobile station shall initiate connection of the packet data service option, as described in... The packet data service call control function shall enter the Reconnect/Traffic State. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State.... Reconnect/Idle State While the packet data service call control function is in the Reconnect/Idle State, the mobile station shall perform the following: A packet data service option can be connected as a result of service negotiation initiated either by the BS/MSC or by the mobile station. -

205 TIA/EIA/IS-0-A If the mobile station enters the Mobile Station Control on the Traffic Channel State, the mobile station shall initiate connection of the packet data service option, as described in... The packet data service call control function shall enter the Reconnect/Traffic State. If the Reconnect/Idle State was entered with a mobile station wait indication, and the mobile station enters the Mobile Station Idle State, the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA/IS-. The mobile station should include the packet data service option in the SERVICE_OPTION field of the Origination Message (see... of TIA/EIA/IS-). The packet data service call control function shall re-enter the Reconnect/Idle State with a packet origination indication. If the Reconnect/Idle State was entered with a packet origination indication, and the packet data service option has not been rejected, the packet data service call control function shall re-enter the Reconnect/Idle State with a channel loss indication if any of the following occurs: The mobile station enters the Mobile Station Initialization State; or The mobile station exits the System Access State and enters any state other than the Mobile Station Control on the Traffic Channel State. If the Reconnect/Idle State was entered with a channel loss indication, the mobile station shall perform the following: If the mobile station has data to send, the mobile station may discard the data. If the mobile station has no data to send, and the mobile station has not detected a change in the serving system SID or NID since the packet data service call control function last entered the Connected State, and the mobile station has not detected a change in PACKET_ZONE_ID S while in the Reconnect/Idle State, the packet data service call control function shall enter the Dormant/Idle State. Otherwise, the packet data service call control function shall remain in the Reconnect/Idle State, and the mobile station shall perform the remaining actions in this list. The mobile station shall start a reconnect delay timer. The initial length of the reconnect delay timer shall be seconds. For each successive entry or re-entry to the Reconnect/Idle State with a channel loss indication, the mobile station shall quadruple the delay length. The maximum delay length is implementation specific, but should not be less than one hour (00 seconds). When the packet data service call control function enters the Connected State, the delay length shall be reset to seconds. If the reconnect delay timer expires while the packet data service call control function is in the Reconnect/Idle State, the mobile station shall perform the following: Mobile stations supporting applications that include higher-layer data retransmission protocols should always discard such data. -

206 TIA/EIA/IS-0-A If the mobile station is not in the Mobile Station Idle State, the mobile station shall wait until the mobile station enters the Mobile Station Idle State. + When the mobile station is in the Mobile Station Idle State, the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA/IS-. The mobile station should include the packet data service option in the SERVICE_OPTION field of the Origination Message (see... of TIA/EIA/IS-). The packet data service call control function shall reenter the Reconnect/Idle State with a packet origination indication. If the mobile station receives a Release Order indicating that the packet data service option is rejected, the packet data service shall enter the Inactive State. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State.... Reconnect/Traffic State While the packet data service call control function is in the Reconnect/Traffic State, the mobile station shall perform the following: The mobile station packet data service call control function shall perform service negotiation or service option negotiation, as described in... of TIA/EIA/IS-, to connect the requested service configuration. If the packet data service option is connected, the packet data service call control function shall enter the Connected State when the mobile station enters the Conversation Substate. If the mobile station exits the Mobile Station Control on the Traffic Channel State, the packet data service call control function shall enter the Reconnect/Idle State with a channel loss indication. If the packet data service option cannot be connected, the packet data service shall enter the Inactive State. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State.... BS/MSC Procedures... Packet Data Service Control Procedures... Inactive State When the packet data service is in the Inactive State, the BS/MSC does not provide packet data service to the mobile station. The BS/MSC packet data service enters the Active State when the IWF Link Layer connection is opened and a packet data service option is connected. -

207 TIA/EIA/IS-0-A If the BS/MSC packet data service enters the Inactive State while the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection.... Active State When the packet data service is in the Active State, the BS/MSC can provide packet data service to the mobile station. When the packet data service enters the Active State, the BS/MSC should store the mobile station identifier and the connected packet data service type (see..). If the BS/MSC supports connections to multiple IWFs, the BS/MSC should also store an IWF identifier, to identify the IWF during re-activation of IWF Link Layer connections that are in the dormant substate (see...). The BS/MSC packet data service may enter the Inactive State when any of the following occurs: The BS/MSC receives a Registration Message indicating power-down registration. The BS/MSC receives a Release Order with a power down indication. The BS/MSC determines that the mobile station cannot be paged. The mobile station rejects the packet data service option after being paged. The mobile station is handed off to another system or service area that is not connected to the same IWF. The mobile station is handed off to a non-cdma service. The BS/MSC determines that the mobile station has roamed to another system or service area that is not connected to the same IWF while the Link Layer connection is in the dormant substate. The Link Layer connection has been closed. While the packet data service is in the Active State, the service negotiation procedures described in... and... of TIA/EIA/IS- can be used to simultaneously connect other service options as primary or secondary traffic. This is intended, for example, to permit the simultaneous and independent connection and disconnection of voice and packet data services. Complete BS/MSC procedures for invoking and controlling such simultaneous connections require further study, and are left for future revisions of this standard. Until other procedures are defined, the BS/MSC can connect a voice call while the packet data service call control function is in the Connected State by releasing the Traffic Channel, paging the mobile station, requesting a voice service option, and performing service negotiation to connect a service configuration containing voice as primary traffic Normally a registration cancellation message from the HLR would provide this indication. -

208 TIA/EIA/IS-0-A and packet data as secondary traffic. While voice and packet data service options are connected, the BS/MSC should process all received and transmitted service-related signaling messages, such as Alert With Information and Flash With Information, as pertaining only to the voice service. The BS/MSC can disconnect the voice service option by releasing the Traffic Channel, following which the packet data service call control function automatically reconnects the packet data service option as described in Packet Data Service Call Control Function... Null State When the BS/MSC packet data service call control function is in the Null State, packet data are not exchanged with the mobile station. The following events can occur while the packet data service call control function is in this state: The mobile station can request activation of the packet data service by requesting connection of a packet data service option. Either the IWF or the mobile station can initiate the reactivation of an open IWF Link Layer connection. The IWF can inform the BS/MSC that the Link Layer connection is closed. The BS/MSC can initiate transfer of the Link Layer connection to a different IWF. If the service configuration of the mobile station does not permit connecting a packet data service option, the BS/MSC can request that the IWF close the Link Layer connection.... IWF Initiated Link Layer Connection Reactivation If the IWF requests reactivation of the Link Layer connection (see. of TIA/EIA/IS-), the BS/MSC should perform the following: If the mobile station is not on a Traffic Channel, the BS/MSC should page the mobile station, requesting the packet data service option. The packet data service call control function should enter the Paging State. If the mobile station is on a Traffic Channel, and both the BS/MSC and the mobile station support Traffic Channel service negotiation (see... and... of TIA/EIA/IS- ), the BS/MSC should perform the following: If the BS/MSC receives an Origination Message from the mobile station, requesting the packet data service option, while the BS/MSC is paging the mobile station, the BS/MSC can send a Reorder Order to terminate the mobile station s origination, and can continue paging. -0

209 TIA/EIA/IS-0-A If either primary traffic or secondary traffic does not have a connected service option, the BS/MSC should send a Service Request Message in accordance with TIA/EIA/IS-, requesting a valid service configuration (see Table...-) including the packet data service option, using the traffic type available. The packet data service call control function should enter the Initialization/Traffic State. If other service options are already connected as both primary and secondary traffic, the BS/MSC may send a Service Request Message in accordance with TSB, requesting a service configuration in which the packet data service option replaces one of the previously connected service options. If the BS/MSC sends a Service Request Message, the packet data service call control function should enter the Initialization/Traffic State. Otherwise, the BS/MSC may inform the IWF that the Link Layer connection has been deactivated or may request that the IWF close the Link Layer connection. The packet data service call control function should remain in the Null State. If the mobile station is on a Traffic Channel, and either the BS/MSC or the mobile station does not support Traffic Channel service negotiation, but both support Traffic Channel service option negotiation, the BS/MSC should perform the following: If there is no connected service option, the BS/MSC should send a Service Option Request Order in accordance with TIA/EIA/IS-, requesting the packet data service option. The packet data service call control function should enter the Initialization/Traffic State. If there is a connected service option, the BS/MSC may send a Service Option Request Order in accordance with TIA/EIA/IS-, requesting the packet data service option. If the BS/MSC sends a Service Option Request Order, the packet data service call control function should enter the Initialization/Traffic State. Otherwise, the BS/MSC should inform the IWF that the Link Layer connection has been deactivated, and the packet data service call control function should remain in the Null State Mobile Station Originated Link Layer Connection Activation If the BS/MSC receives an Origination Message requesting a packet data service option from the mobile station, the BS/MSC should perform the following: If the service option requested by the mobile station indicates a packet data service type (see..) that is not supported, the BS/MSC should send a Release Order rejecting the requested service option in accordance with TIA/EIA/IS-. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection. The packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. Otherwise, the BS/MSC should perform the following: -

210 TIA/EIA/IS-0-A If IWF resources are temporarily unavailable due to congestion or equipment outage, the BS/MSC should not send a message indicating that the service option has been rejected, as this can inhibit packet data service origination attempts. The BS/MSC should send a Reorder Order to the mobile station. The packet data service call control function should remain in the Null State, and the BS/MSC should not perform the remaining actions in this list. If the packet data service is in the Active State, and the requested service option is supported but indicates a packet data service type that is different from the stored packet data service type (see...), the BS/MSC should request that the IWF close the Link Layer connection, and the packet data service should enter the Inactive State. The packet data service call control function should remain in the Null State, and the BS/MSC should assign the mobile station to a Traffic Channel following the procedures of TIA/EIA/IS-. If the requested packet data service option indicates the same packet data service type as the stored packet data service type, the BS/MSC should perform the following: + If the requested service option and multiplex option are supported and traffic channel resources are available, the BS/MSC should assign the mobile station to a Traffic Channel following the procedures of TIA/EIA/IS-. + If the requested service option or multiplex option is not supported or if traffic channel resources are not available, the BS/MSC should send to the mobile station a Channel Assignment Message with the ASSIGN_MODE field set to 00 and the GRANTED_MODE field set to 00. Subsequently, the BS/MSC should perform service negotiation to establish a suitable service configuration. + If the IWF Link Layer connection is open, the BS/MSC should request that the IWF reactivate the Link Layer connection. If the IWF Link Layer connection is closed, the BS/MSC should request that the IWF open a Link Layer connection for the mobile station. The packet data service call control function should enter the Initialization/Idle State Mobile Station Negotiated Link Layer Connection Activation If the BS/MSC supports service negotiation and the BS/MSC receives a Traffic Channel Service Request Message requesting a service configuration including a packet data service option, or if the BS/MSC supports service option negotiation and the BS/MSC receives a Traffic Channel Service Option Request Order requesting a packet data service option, the BS/MSC should perform the following: If the service option requested by the mobile station indicates a packet data service type (see..) that is not supported, the BS/MSC should reject the requested service option in accordance with TIA/EIA/IS-. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection. -

211 TIA/EIA/IS-0-A. 0 0 The packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. If the packet data service is in the Active State, and the requested service option is supported but indicates a packet data service type that is different from the stored packet data service type (see... ), the BS/MSC should perform the following: The BS/MSC should request that the IWF close the Link Layer connection, and the packet data service should enter the Inactive State. When the IWF Link Layer connection is closed, the BS/MSC should request that the IWF open a new Link Layer connection for the mobile station. The packet data service call control function should enter the Initialization/Traffic State. If the requested service option indicates the same packet data service type as the stored packet data service type, the BS/MSC should perform the following: If the IWF Link Layer connection is open, the BS/MSC should request that the IWF reactivate the Link Layer connection. If the IWF Link Layer connection is closed, the BS/MSC should request that the IWF open a Link Layer connection for the mobile station. The packet data service call control function should enter the Initialization/Traffic State IWF Link Layer Closure If the IWF informs the BS/MSC that the Link Layer connection has been closed, the packet data service should enter the Inactive State, and the packet data service call control function should remain in the Null State.... IWF Transfer If the BS/MSC transfers the Link Layer connection to a new IWF, the BS/MSC should perform the following: The BS/MSC should request that the current IWF close the Link Layer connection. The BS/MSC packet data service should enter the Inactive State. The BS/MSC should then request that the new IWF open a Link Layer connection for the mobile station. When the IWF Link Layer connection is opened, the BS/MSC should perform the procedures for IWF Initiated Link Layer connection Reactivation, as defined in Paging State When the BS/MSC packet data service call control function is in the Paging State, the BS/MSC should perform the following: -

212 TIA/EIA/IS-0-A If the BS/MSC receives a Page Response Message containing a valid, non-zero service option number, the BS/MSC should assign the mobile station to a Traffic Channel, following the procedures of TIA/EIA/IS-. The packet data service call control function should enter the Initialization/Idle State. If the BS/MSC receives a Page Response Message with an invalid service option, the BS/MSC should send a Release Order rejecting the requested service option in accordance with TIA/EIA/IS-. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection. The packet data service should enter the Inactive State, and packet data service call control function should enter the Null State. If the BS/MSC does not receive a Page Response Message or if the BS/MSC receives a Page Response Message with the service option number set to zero, the BS/MSC may request that the IWF close the Link Layer connection. If the BS/MSC requests that the IWF close the Link Layer connection, the packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State.... Initialization/Idle State When the BS/MSC packet data service call control function is in the Initialization/Idle State, the BS/MSC should perform the following: If the BS/MSC initializes a Traffic Channel for the mobile station, the BS/MSC should negotiate connection of a packet data service option. The packet data service call control function should enter the Initialization/Traffic State. If the packet data service option requested by the mobile station is not supported, the BS/MSC should send a Release Order rejecting the requested service option in accordance with TIA/EIA/IS-. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection. The packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. If the requested service option is temporarily unavailable, the BS/MSC may send a Reorder Order to the mobile station to indicate that the service is temporarily unavailable. If a Reorder Order is sent while the packet data service is in the Active State, the BS/MSC should inform the IWF that the Link Layer connection has been deactivated. If a Reorder Order is sent while the packet data service is in the Inactive State, the BS/MSC should request that the IWF close the Link Layer connection, if open. The packet data service call control function should enter the Null State. If the IWF informs the BS/MSC that the Link Layer connection has been closed, the packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. -

213 TIA/EIA/IS-0-A Initialization/Traffic State When the BS/MSC packet data service call control function enters the Initialization/Traffic State, the BS/MSC should perform service negotiation or service option negotiation, as described in... of TIA/EIA/IS-, to connect the requested service configuration. If the BS/MSC has sent a Channel Assignment Message to the mobile station with the ASSIGN_MODE field set to 00 and the GRANTED_MODE field set to 00 (see... and...), the BS/MSC may propose an alternate service configuration. If the BS/MSC supports authentication, it may complete a Unique Challenge of the mobile station (see... of TIA/EIA/IS-) before providing packet data services to the mobile station. If a service configuration including a packet data service option is connected, the packet data service call control function should enter the Connected State. If the IWF informs the BS/MSC that the Link Layer connection has been closed, the packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. If no other service options are connected, the BS/MSC should release the Traffic Channel. If a service configuration including a packet data service option cannot be connected, the BS/MSC should perform the following: If no other service options are connected, the BS/MSC should release the Traffic Channel. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection. The packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. If the Traffic Channel is released, the BS/MSC should perform the following: If the IWF Link Layer connection is open, the BS/MSC should inform the IWF that the Link Layer connection has been deactivated. The packet data service call control function should enter the Null State.... Connected State When the BS/MSC packet data service call control function enters the Connected State, the BS/MSC should perform the following: The BS/MSC should perform RLP initialization in accordance with IS-0.. Upon completing RLP initialization, the BS/MSC should transfer octets in sequence between the RLP layer and the IWF. If the packet data service is in the Inactive State, the packet data service should enter the Active State. -

214 TIA/EIA/IS-0-A If the IWF informs the BS/MSC that the Link Layer connection has been closed, the BS/MSC should perform the following: The packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. If no other service options are connected, the BS/MSC should release the Traffic Channel. Otherwise, the BS/MSC should negotiate a service configuration that does not include the packet data service option. If the BS/MSC transfers the Link Layer connection to a new IWF, the BS/MSC should perform the following: The BS/MSC should request that the current IWF close the Link Layer connection. The BS/MSC packet data service should enter the Inactive State. The packet data service call control function should remain in the Connected State, but data received from the mobile station should be discarded until the packet data service enters the Active State. The BS/MSC should then request that the new IWF open a Link Layer connection for the mobile station. When the IWF Link Layer connection is opened, the BS/MSC packet data service should enter the Active State. While the packet data service call control function is in the Connected State, the BS/MSC should maintain a packet data inactivity timer. The timer should be reset whenever nonidle RLP data frames are sent or received. If the packet data inactivity timer expires, the BS/MSC should perform the following: If no other service options are connected, the BS/MSC should release the Traffic Channel. Otherwise, the BS/MSC should disconnect the packet data service option by negotiating a service configuration that does not include the packet data service option. If the Traffic Channel is released or the packet data service option is disconnected, the BS/MSC should inform the IWF that the Link Layer connection has been deactivated. The packet data service call control function should enter the Null State... Initialization and Connection of Packet Data Service Options Packet data service options shall be negotiated and connected using the service configuration and negotiation procedures defined in... and... of TIA/EIA/IS-. Either service negotiation or service option negotiation, as defined in TIA/EIA/IS-, can be used to negotiate and connect a packet data service option. Mobile stations that support Service Option shall also support Service Option 0. Mobile Stations that support Service Option shall also support Service Option 0. The mobile station shall initiate connection of a packet data service option by performing one of the following: By requesting the packet data service option in either a Page Response Message or an Origination Message. -

215 TIA/EIA/IS-0-A. 0 0 If the service option negotiation procedure is performed, by sending a Service Option Request Order requesting the packet data service option. If the service negotiation procedure is performed, by sending a Service Request Message requesting a service configuration that includes the packet data service option using primary or secondary traffic. After initiating connection of a packet data service option, the mobile station shall connect the service option as specified in... or... as appropriate.... Procedures Using Service Option Negotiation... Mobile Station Procedures Upon successfully completing negotiation for the packet data service option, the mobile station shall connect the packet data service option in accordance with the following requirements: If service option negotiation is completed when the mobile station receives a Service Option Response Order, then the mobile station shall connect the service option at the explicit or implicit action time associated with the Service Option Response Order. If service option negotiation is completed as a result of the mobile station sending a Service Option Response Order, then the mobile station shall connect the service option at the implicit or explicit action time associated with the most recently received Service Option Request Order from the BS/MSC. If a packet data service option is connected when the mobile station enters the Waiting for Mobile Station Answer Substate or the packet data service option becomes connected when the mobile station is already in the Waiting for Mobile Station Answer Substate, then the mobile station should send a Connect Order to the BS/MSC as a message requiring acknowledgment, without waiting for the user to explicitly command the call to be answered. The mobile station shall enter the Conversation Substate. Table...- shows the implicit service configuration when service option negotiation is used to connect Service Option 0 or 0. When the mobile station is implemented as a MT-TE pair, the MT should not send a Connect Order unless the TE is connected to the MT. -

216 TIA/EIA/IS-0-A. Table...-. Implicit Service Configuration for Service Options 0 and 0 Service Configuration Attribute Default Selection Forward Multiplex Option Multiplex Option Reverse Multiplex Option Multiplex Option Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type Rates, / and / enabled Rates, / and / enabled Primary Traffic Primary Traffic BS/MSC Procedures The BS/MSC should wait until the action time associated with the most recently transmitted Service Option Response Order or Service Option Request Order before connecting the packet data service option.... Procedures Using Service Negotiation... Mobile Station Procedures The mobile station performs service negotiation for packet data service options as described in... of TIA/EIA/IS-. The mobile station shall only propose service configurations for Service Option 0 or 0 with attributes as specified in Table...-. The mobile station shall not accept a service configuration including Service Option 0 or 0 that is not consistent with Table...-. The default service configuration for Service Options 0 and 0 shall be as shown in Table...-. The mobile station shall only propose service configurations for Service Option or with attributes specified in Table...-. The mobile station shall not accept a service configuration including Service Option or that is not consistent with Table...-. The default service configuration for Service Options and shall be as shown in Table...- -

217 TIA/EIA/IS-0-A. Table...-. Valid Service Configuration Attributes for Service Options 0 and 0 Service Configuration Attribute Valid Selections Forward Multiplex Option Multiplex Option, Reverse Multiplex Option Multiplex Option, Forward Transmission Rates Primary Traffic: Rates, / and / required, Rate / not required by Service Options 0 and 0. Secondary Traffic: Rate required, Rates /, / and / not required by Service Options 0 and 0. Reverse Transmission Rates Primary Traffic: Rates, / and / required, Rate / not required by Service Options 0 and 0. Secondary Traffic: Rate required, Rates /, / and / not required by Service Options 0 and 0. Forward Traffic Type Reverse Traffic Type Primary or Secondary Traffic Shall be identical to the Forward Traffic Type Table...-. Valid Service Configuration Attributes for Service Options and Service Configuration Attribute Valid Selections Forward Multiplex Option Multiplex Option,, Reverse Multiplex Option Multiplex Option,, Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type All rates enabled All rates enabled Primary or Secondary Traffic Shall be identical to the Forward Traffic Type 0 If a packet data service option is connected when the mobile station enters the Waiting for Mobile Station Answer Substate, or if a packet data service option becomes connected while the mobile station is in the Waiting for Mobile Station Answer Substate, the mobile station should automatically send a Connect Order to the BS/MSC as a message requiring acknowledgment without waiting for the user to explicitly command the call to be answered, except when the service configuration includes any service option that requires -

218 TIA/EIA/IS-0-A user answer. If the mobile station sends a Connect Order, the mobile station shall enter the Conversation Substate.... BS/MSC Requirements The BS/MSC shall propose service configurations for Service Option 0 or 0 with attributes as specified in Table...-. The BS/MSC shall reject any service configuration for Service Option 0 or 0 with attributes not consistent with Table...-. The BS/MSC shall propose service configurations for Service Option or with attributes as specified in Table...-. The BS/MSC shall reject any service configuration for Service Options or with attributes not consistent with Table Optional Zone-Based Registration or Reconnection The BS/MSC may require the mobile station to register or reconnect the packet data service when packet data service is in the Active State, the mobile station is in the Mobile Station Idle State, and the mobile station detects a change in the registration zone (see... of TIA/EIA/IS-). The BS/MSC shall enable and disable zone based registration or zone based reconnection in the mobile station through the Service Option Control Order or the Service Option Control Message. The default state within the mobile station for both zone based registration and zone based reconnection shall be disabled. The BS/MSC may enable either zone based registration or zone based reconnection but not both simultaneously. Once zone based registration or zone based reconnection is enabled by the BS/MSC, the mobile station shall either register or reconnect the packet data service option (depending upon the feature enabled), on detection of a change in Registration Zone, and shall disable the enabled feature when one of the following events occurs: The mobile station receives a Service Option Control Order or Service Option Control Message disabling the enabled feature. The mobile station detects a change in the SID of the serving system. Packet data service enters the Inactive State. If service negotiation is used, the BS/MSC may send a Service Option Control Message (see... of TIA/EIA/IS-) to enable or disable zone based registration or zone based reconnection within the mobile station. The Service Option Control Message shall include the type-specific fields shown in Table

219 TIA/EIA/IS-0-A. Table..-. ORDQ Format and Type-Specific Fields for Zone-Based Registration/Reconnection Field Length (bits) ZREG_CNTL RESERVED FIELD_TYPE 0 ZREG_CNTL - Zone based registration/reconnection control. The BS/MSC shall set this field to the ZREG_CNTL value from Table..- corresponding to the zone-based function that the mobile station is to perform. RESERVED - Reserved bits. The BS/MSC shall set this field to 00. FIELD_TYPE - Type-specific field designator. The BS/MSC shall set this field to 00. The ZREG_CNTL field shall be set appropriately as specified in Table..-. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 00 and the ZREG_CNTL field is not equal to a value defined in Table..-, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to Table..-. Zone Based Registration/Reconnection Control Field ZREG_CNTL (binary) Mobile Station Action 000 Disable zone-based functions 00 Enable zone-based registration 00 Enable zone-based reconnection All other ZREG_CNTL values are reserved. 0 If service option negotiation is used, the BS/MSC may send a Service Option Control Order (see.. of TIA/EIA/IS--A) to enable or disable zone based registration or zone based reconnection within the mobile station. The Order Qualification Code (ORDQ) of the Service Option Control Order shall be formatted as shown in Table..-. If the mobile station receives a Service Option Control Order for the service option with FIELD_TYPE set to 00 and the ZREG_CNTL field is not equal to a value defined in Table..-, the mobile station shall reject the order by sending a Mobile Station Reject Order with the ORDQ field set equal to

220 TIA/EIA/IS-0-A. 0.. Optional Reconnect After Hard Handoff The BS/MSC may require the mobile station to reconnect the packet data service option (see...) when the mobile station successfully completes a hard handoff (see... of TIA/EIA/IS--A) in which the Active Set or frequency assignment changes. The BS/MSC shall enable and disable this feature in the mobile station through the Service Option Control Order or the Service Option Control Message. The default state within the mobile station for this feature shall be disabled. Once enabled by the BS/MSC, the mobile station reconnects the packet data service option after successful completion of a hard handoff in which the Active Set or frequency assignment changes. The mobile station shall disable this feature when one of the following events occurs: The mobile station receives a Service Option Control Order or Service Option Control Message disabling this feature. The mobile station detects a change in the SID of the serving system. Packet data service enters the Inactive State. If service negotiation is used, the BS/MSC may send a Service Option Control Message (see... of TIA/EIA/IS-) to enable or disable this feature. The Service Option Control Message shall include the type-specific fields shown in Table Table..-. ORDQ Format and Type-Specific Fields for Reconnect After Hard Handoff Field Length (bits) HHO_CNTL RESERVED FIELD_TYPE HHO_CNTL - Reconnect After Hard Handoff control. The BS/MSC shall set this field to the HHO_CNTL value from Table..- corresponding to the function that the mobile station is to perform. RESERVED - Reserved bits. The BS/MSC shall set this field to 00. FIELD_TYPE - Type-specific field designator. The BS/MSC shall set this field to The HHO_CNTL field shall be set appropriately as specified in Table..-. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 00 and the HHO_CNTL field is not equal to a value defined in Table..-, the -

221 TIA/EIA/IS-0-A. mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to Table..-. Reconnect After Hard Handoff Control Field HHO_CNTL (binary) Mobile Station Action 000 Disable Reconnect After Hard Handoff 00 Enable Reconnect After Hard Handoff All other HHO_CNTL values are reserved. 0 0 If service option negotiation is used, the BS/MSC may send a Service Option Control Order (see.. of TIA/EIA/IS--A) to enable or disable this feature. The Order Qualification Code (ORDQ) of the Service Option Control Order shall be formatted as shown in Table..-. If the mobile station receives a Service Option Control Order for the service option with FIELD_TYPE set to 00 and the HHO_CNTL field is not equal to a value defined in Table..-, the mobile station shall reject the order by sending a Mobile Station Reject Order with the ORDQ field set equal to Optional Packet Data Dormant Timer Control The BS/MSC may require a mobile station to establish a value for the Packet Data Dormant Timer. If this feature is enabled, a mobile station shall not originate a packet data service option until the timer has exceeded the value established by the BS/MSC. The BS/MSC shall enable and control this feature in the mobile station through the Service Option Control Message. The default state within the mobile station for BS/MSC control of the packet data dormant timer shall be disabled. When this feature is disabled, the mobile station should set its packet data dormant timer to the default value of 0 seconds. The mobile station shall disable BS/MSC control of the dormant timer when one of the following events occurs: The mobile station receives a Service Option Control Message disabling BS/MSC control. The mobile station detects a change in the SID of the serving system. Packet data service enters the Inactive State. If service negotiation is used, the BS/MSC may send a Service Option Control Message (see... of TIA/EIA/IS-) to control this feature. The Service Option Control Message shall include the type-specific fields shown in Table

222 TIA/EIA/IS-0-A. Table..-. Type-Specific Fields for Data Dormant Timer Control Field Length (bits) DORM_CNTL RESERVED FIELD_TYPE DORM_TIME 0 or DORM_CNTL - Dormant Timer control. The BS/MSC shall set this field to the DORM_CNTL value from Table..- corresponding to the function that the mobile station is to perform. RESERVED - Reserved bits. The BS/MSC shall set this field to 00. FIELD_TYPE - Type-specific field designator. The BS/MSC shall set this field to 0. DORM_TIME - Value of packet data dormant timer. If DORM_CNTL is set to 00, the BS/MSC shall include this field and set it to the DORM_TIME value from Table..- corresponding to the value of the packet data dormant timer to be used by the mobile station. The DORM_CNTL field shall be set appropriately as specified in Table..-. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 0 and the DORM_CNTL field is not equal to a value defined in Table..-, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 0 and the DORM_CNTL field set to 000, the mobile station shall disable BS/MSC control of the minimum dormant timer value. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 0 and the DORM_CNTL field set to 00, and the mobile station supports a packet data dormant timer, the mobile station shall enable BS/MSC control of the timer and set the minimum value of the dormant timer to the value specified in the DORM_CNTL field. If the current value of the mobile station s dormant timer is less than the value specified in the DORM_TIME, the mobile station shall set the value of its packet data dormant timer to the value specified in DORM_TIME. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 0 and the mobile station does not support a packet data dormant timer, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to

223 TIA/EIA/IS-0-A. When this feature is enabled, the mobile station s packet data dormant timer shall not be set to a value less than the minimum value specified in the most recently received Service Option Control Message. If the mobile station provides a means for user configuration of the dormant timer, and the user attempts to set the value of the timer to a value less than minimum specified value, the mobile station should provide the user with an error indication. The means for providing the error indication is left to the manufacturer. Table..-. Dormant Timer Control Field DORM_CNTL (binary) Mobile Station Action 000 Disable BS/MSC control of minimum dormant timer 00 Set the minimum dormant timer value to value specified in DORM_TIME field All other DORM_CNTL values are reserved. 0 Table..-. Minimum Value of Mobile Station Dormant Timer DORM_TIME (binary) Description Dormant mode not supported by BS/MSC through Minimum mobile station packet data dormant timer value in tenths of seconds. 0.. Optional Packet Zone Reconnection Control The BS/MSC may require the mobile station to reconnect the packet data service when the packet data service is in the Active State; the packet data call control function is in the Dormant / Idle State, Reconnect/Idle State, or Dormant/Traffic State; and the mobile station detects a change in the non-zero packet data services zone identifier. Packet zone based reconnection causes a mobile station to reconnect the packet data service whenever it moves into a new packet data zone not on its internally stored list of visited packet data zones. A packet data zone is added to the list whenever the mobile station connects the packet data service while in the zone, and is deleted when the number of more recently visited zones is equal to the maximum number of zones retained by the mobile station. The BS/MSC shall enable packet zone based reconnection in the mobile station by transmitting a non-zero packet data services zone identifier (PACKET_ZONE_ID). The -

224 TIA/EIA/IS-0-A BS/MSC may disable the packet zone based reconnection function in the mobile station by sending a Service Option Control Message disabling the enabled feature. The BS/MSC may re-enable the function in the mobile station by sending a Service Option Control Message enabling the feature. The BS/MSC may control the number of entries a mobile station is to retain in its list of visited packet data zones and may clear the list by sending a Service Option Control Message. The default state within the mobile station for the packet zone based reconnection feature shall be disabled. The mobile shall enable the feature upon initial detection of a non-zero packet data services zone identifier (PACKET_ZONE_ID S ). The mobile station shall then add the packet data services zone identifier to its stored list of visited packet data zones. Upon enabling the packet zone reconnection feature, the mobile station shall set the length of the packet zone list to one entry until commanded otherwise by the base station. The mobile station shall provide memory for storing up to zone identifiers. The mobile station shall maintain the list of visited packet data service zone identifiers in most recently visited order sequence with the current zone contained in the first entry of the list. Entries shall be removed from the list in least recently visited order. The mobile station shall disable the feature and clear its list of visited packet data service zone identifiers when one of the following occurs: The mobile station receives a Service Option Control Message disabling the feature. The mobile station detects a PACKET_ZONE_ID S field of value The mobile station determines that the BS/MSC does not support packet zones. Packet data service enters the Inactive State. The mobile station detects a change in SID. Once disabled, the mobile station shall re-enable the feature upon detection of a non-zero PACKET_ZONE_ID S or upon receipt of a Service Option Control Message enabling the feature. If service negotiation is used, the BS/MSC may send a Service Option Control Message (see... of TSB) to control this feature. The Service Option Control Message shall include the type-specific fields shown in Table..-. -

225 TIA/EIA/IS-0-A. Table..-. Type-Specific Fields for Packet Connection Control Field Length (bits) PKT_CON_CNTL RESERVED FIELD_TYPE RESERVED 0 or PKT_ZONE_LIST_LEN 0 or 0 0 PKT_CON_CNTL - Packet Zone Connection Control. The BS/MSC shall set this field to the PKT_CON_CNTL value from Table..- corresponding to the function that the mobile station is to perform. RESERVED - Reserved bits. The BS/MSC shall set this field to 00. FIELD_TYPE - Type-specific field designator. The BS/MSC shall set this field to 00. RESERVED - Reserved bits. The BS/MSC shall set this field to 0000 if PKT_CON_CNTL is set to 00 or 00. The BS/MSC shall omit this field if PKT_CON_CNTL is any other value. PKT_ZONE_LIST_LEN - Packet data zone identifier list length. The BS/MSC shall include this field if PKT_CON_CNTL is set to 00 or 00 to specify the number of packet data service zone identifiers the mobile station is to retain in its packet data zone identifier list. This field shall be within the range 000 through, inclusive. 0 The BS/MSC shall set the PKT_CON_CNTL appropriately as specified in Table..-. The BS/MSC shall set the value of PKT_CON_CNTL to 000 to disable the packet zone based reconnection feature in the mobile station. The BS/MSC shall set the value of PKT_CON_CNTL to 00 to enable packet zone based reconnection feature in the mobile station. The BS/MSC shall also include the PKT_ZONE_LIST_LEN field in the type-specific fields of the Service Option Control Message to specify the number of packet data service zone identifiers the mobile station is to store in its internal list. The BS/MSC shall set the value of PKT_CON_CNTL to 00 to clear the packet data service zone identifier list within the mobile station. The BS/MSC shall also include the PKT_ZONE_LIST_LEN field in the type-specific fields of the -

226 TIA/EIA/IS-0-A. Service Option Control Message to specify the number of packet data service zone identifiers the mobile station is to store in its internal list. The BS/MSC shall set the value of the PKT_CON_CNTL to 0 to request the mobile station to transfer its internally stored packet data services zone identifier list to the BS/MSC. Table..-. Packet Zone Connection Control Field PKT_CON_CNTL (binary) Mobile Station Action 000 Disable packet zone connection control 00 Enable packet zone connection control 00 Clear the packet data zone identifier list 0 Transfer the packet data zone identifier list to BS/MSC All other PKT_CON_CNTL values are reserved. 0 0 If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 00 and the PKT_CON_CNTL field is not equal to a value defined in Table..-, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 00 and the PKT_CON_CNTL field is equal to a value defined in Table..-, the mobile station shall perform the following actions: If the value of PKT_CON_CNTL field is set to 000, the mobile station shall disable the packet zone based reconnection feature and clear its list of stored packet data service zone identifiers. If the value of the PKT_CON_CNTL field is set to 00, and the packet zone based reconnection feature is currently disabled, the mobile station shall enable the feature. The mobile station shall set the number of entries in its packet data services zone identifier list to the value specified in the PKT_ZONE_LIST_LEN field of the Service Option Control Message. If the value of the PKT_CON_CNTL field is set to 00, and the packet zone based reconnection feature is currently enabled, the mobile station shall set the number of entries in its packet data services zone identifier list to the value specified in the PKT_ZONE_LIST_LEN field of the Service Option Control -

227 TIA/EIA/IS-0-A. 0 Message. If the value of the PKT_ZONE_LIST_LEN is greater than or equal to the number of existing entries in the list, the mobile station shall retain the current list entries. If the value of the PKT_ZONE_LIST_LEN represents a decrease in the number of list entries, the mobile station shall delete the least recently visited zone list entries. If the value of the PKT_CON_CNTL field is set to 00, the mobile station shall clear its packet data service zone identifier list. The mobile station shall set the number of entries in its packet data services zone identifier list to the value specified in the PKT_ZONE_LIST_LEN field of the Service Option Control Message. If the value of the PKT_CON_CNTL field is set to 0, the mobile station shall transfer the contents of its stored packet data services zone identifier list to the BS/MSC. The mobile station shall transfer the list using a Service Option Control Message including the type-specific fields shown in Table..-. Table..-. Type-Specific Fields for Packet Zone Connection Response Field Length (bits) PKT_CON_RESP RESERVED FIELD_TYPE RESERVED PKT_ZONE_LIST_LEN The mobile station shall include PKT_ZONE_LIST_LEN occurrences of the following record: PACKET_ZONE_ID 0 PKT_CON_RESP - Packet Zone Connection Response. The mobile station shall set this field to 000. RESERVED - Reserved bits. The mobile shall set this field to 00. FIELD_TYPE - Type-specific field designator. The mobile shall set this field to 00. RESERVED - Reserved bits. The mobile station shall set this field to PKT_ZONE_LIST_LEN - Packet Data Zone Identifier List Length. -

228 TIA/EIA/IS-0-A. 0 0 The mobile station shall set this field to specify the number of reported packet data service zone identifiers within the Service Option Control Message. This field shall be within the range of 000 through, inclusive. PACKET_ZONE_ID - Packet data services zone identifier. The mobile station shall set this field to the packet data services zone identifier for each entry in its stored packet data zone identifier list.. L Interface.. Logical Connections The L interface provides a path for transport of end-user data, and a signaling path for communicating control information. L interface protocols should be as recommended in TIA/EIA/IS-... Mobile Data The L interface supports IWF Link Layer connections to mobile stations. Each opened IWF Link Layer connection can be active or dormant (see...). When the IWF Link Layer connection is activated, an L interface virtual circuit is established. The IWF or BS/MSC initiates release of the L interface virtual circuit for the mobile station when the IWF Link Layer connection is deactivated. The IWF may initiate release of the L interface virtual circuit for the mobile station when the IWF Link Layer connection is closed. The BS/MSC may request that the IWF close the Link Layer connection while initiating release of the L Interface virtual circuit. -0

229 TIA/EIA/IS-0-A LINK LAYER. Link Layer Protocols The IWF maintains a separate instance of the Link Layer protocol for each mobile station having an opened IWF Link Layer connection. The Link Layer protocol used for Service Options 0, 0, and shall be the Internet Point-to-Point Protocol (PPP), in accordance with RFC. The TE, MT (Network Layer R m interface protocol option only) and IWF shall support the PPP Link Control Protocol (LCP) defined in RFC and the LCP extensions defined in RFC 0. The instances of PPP shall support control escaping in accordance with. of RFC. When the Relay Layer R m interface protocol option is selected, the MT shall not perform control escaping, and the provisions of section of RFC do not apply to the MT. The IWF Link Layer shall support negotiation of async control character mapping as defined in RFC. The IWF should not request control character mapping, but should perform control character mapping if negotiated by the mobile station. If PPP is used as the R m interface Link Layer, the R m interface Link Layer shall support negotiation of async control character mapping as defined in RFC. If software flow control is used on the R m interface, the TE shall negotiate mapping for the XON and XOFF control characters. To provide the maximum throughput, the TE should negotiate mapping only for the minimum number of control characters necessary for proper operation. When the Network Layer R m interface protocol option is selected, the MT should not request control character mapping on the R m interface, but shall perform control character mapping on that interface if negotiated by the TE. The TE and MT shall frame PPP packets sent on the R m interface using the asynchronous framing protocol defined in RFC. The MT shall frame PPP packets sent on the U m interface using the octet-synchronous framing protocol defined in RFC, except that there shall be no inter-frame time fill (see.. of RFC ). That is, no flag octets shall be sent between a flag octet that ends one PPP frame and the flag octet that begins the subsequent PPP frame. When the Relay Layer R m interface protocol option is selected, the MT shall perform the necessary framing conversion, except that the MT shall not perform asynchronous control character mapping, and the provisions of section of RFC do not apply to the MT. The IWF shall perform asynchronous control character mapping on L interface data in accordance with the provisions of Section of RFC, in the same manner as if an asynchronous to synchronous framing conversion were performed between the BS/MSC and the IWF. The IWF shall frame PPP packets sent on the L interface using the octet-synchronous framing protocol defined in RFC, except that there shall be no inter-frame time fill Framing conversion in the MT consists of the insertion and removal of start bits, stop bits, and mark characters (see.. and.. of RFC ). -

230 TIA/EIA/IS-0-A (see.. of RFC ). That is, no flag octets shall be sent between a flag octet that ends one PPP frame and the flag octet that begins the subsequent PPP frame. The BS/MSC shall pass octets between the L interface and the MT without any framing conversion. PPP provides a means for interfacing to multiple protocols. The BS/MSC and TE may support any subset of the protocols having a PPP Assigned Protocol Number (see Internet Assigned Numbers ). Requirements for support of Internet Protocol, ISO protocols and CDPD options are given in. through.. All PPP frames with an unknown or unsupported protocol number should be rejected, using the procedures defined in RFC.. Link Layer Connections.. IWF Link Layer Connection Opening If the Network Layer R m Interface Protocol option is selected, and the mobile station packet data service call control function enters the Connected State while the U m interface PPP LCP is not in the Opened state, the MT shall initiate PPP configuration according to the protocol defined in RFC. When the PPP LCP enters the Opened state, the PPP Link Layer shall send an establishment indication to higher protocol layers. If PPP is implemented on the R m interface, the MT shall initiate PPP configuration on the R m interface according to the protocol defined in RFC. If the Relay Layer R m Interface Protocol option is selected, when the mobile station packet data service enters the Active State the MT should send a physical layer establishment indication to the TE (see Section.. and Section of TIA/EIA/IS-0.). If the PPP LCP in the TE is not in the Opened state, the TE shall initiate PPP configuration according to the protocol defined in RFC. When the PPP LCP enters the Opened state, PPP shall send an establishment indication to higher protocol layers. When an IWF Link Layer connection is in the active substate and the PPP LCP is not in the Opened state, the IWF Link Layer shall initiate PPP configuration according to the protocol defined in RFC. When the PPP LCP enters the Opened state, PPP shall send an establishment indication to higher protocol layers. After a PPP establishment indication, all supported network layer protocols shall be configured using the appropriate network control protocols (see Section )... IWF Link Layer Connection Maintenance While the IWF Link Layer is in the Active substate, either the mobile station or the BS/MSC may release the Traffic Channel. Procedures for re-establishing the Traffic Channel are given in... When the Traffic Channel is released, the BS/MSC should inform the IWF that the Link Layer connection has been deactivated. When the IWF is informed of a Link Layer connection deactivation, the IWF Link Layer connection shall enter the dormant substate, unless it is closed as specified in... Currently RFC 00. -

231 TIA/EIA/IS-0-A IWF Link Layer Connection Closure... BS/MSC Closure The BS/MSC should request that the IWF close the Link Layer connection when the packet data service enters the Inactive State (see...).... IWF Closure The IWF should close the Link Layer connection when it receives an LCP Terminate- Request message from the mobile station or when the BS/MSC requests that the Link Layer connection be closed. The IWF should also close the Link Layer connection when it determines that the mobile station is no longer in its service area. When closing the Link Layer connection after receiving an LCP Terminate-Request message from the mobile station, the IWF should first complete the procedures for closing PPP defined in RFC. The IWF should not send an LCP Terminate-Request to the mobile station if the BS/MSC requests that the IWF Link Layer connection be closed. If the IWF initiates closure of the Link Layer connection while the Link Layer connection is active, it should send an LCP Terminate-Request to the mobile station. If the Network Layer R m interface protocol option is selected, the MT packet data service should enter the Inactive State when the MT receives an LCP Terminate-Request. When the IWF closes the Link Layer connection, it should discard the PPP connection state information for the mobile station. The IWF should inform the BS/MSC when the Link Layer connection is closed.... TE Closure Causes for TE closure of the IWF Link Layer connection are implementation dependent. If PPP is implemented on the R m interface, TE manages the Link Layer connection using the PPP LCP opening and closing procedures defined in RFC. When the Network Layer R m interface protocol option is selected, and the SLIP protocol is used between the TE and the MT, the MT may close the IWF Link Layer connection when circuit 0/ is deasserted (provided that the &D parameter is not set to zero (see Table..- of TIA/EIA/IS-0.)). If the PPP protocol is supported in the TE and the TE closes the IWF Link Layer connection, the TE shall follow the procedures for closing PPP defined in RFC. If the Network Layer R m interface protocol option is selected, then when the PPP connection to the TE is closed, the MT shall close the PPP connection to the IWF using the procedures defined in RFC, and then the packet data service shall enter the Inactive State.... MT Closure If the Network Layer R m interface protocol option is selected, the MT manages the Link Layer connection using the PPP LCP opening and closing procedures defined in RFC. The MT cannot initiate closure of the IWF Link Layer connection when the Relay Layer R m interface protocol option is selected. -

232 TIA/EIA/IS-0-A. If the Network Layer R m interface protocol option is selected, the MT should close the IWF Link Layer connection, if opened, when the packet data service enters the Inactive State. If the MT supports circuit 0/ (or equivalent function provided by In-Band Control Service), the MT may close the Link Layer connection when circuit 0/ is deasserted for longer than a period of time which is to be determined by the implementation. If the Network Layer R m interface protocol option is selected, and PPP is implemented as the Link Layer protocol on the R m interface, the MT should close the PPP LCP on the R m interface when the packet data service enters the Inactive State. -

233 TIA/EIA/IS-0-A. NETWORK LAYER. Internet Protocol Support Support of the Internet Protocol (IP) Network Layer (as defined in RFC ) is optional. The following requirements apply for an IWF and mobile station that support an IP network interface. To select IP interworking via a PPP Link Layer, the mobile station should request Service Option 0 or Service Option. For Service Options 0 and, the IWF Link Layer shall support the following PPP protocol numbers: 0 0x00 0x00d 0x00f 0x0 Internet Protocol Van Jacobson Compressed TCP/IP Van Jacobson Uncompressed TCP/IP Internet Protocol Control Protocol 0 For Service Options 0 and, the mobile station shall support the IP Control Protocol (IPCP) defined in RFC. The mobile station shall support Van Jacobson TCP/IP header compression (RFC ). Van Jacobson TCP/IP header compression shall be configured through IPCP negotiation.. ISO Protocol Support Support of the ISO Network Layer protocols, such as the Connectionless Network Protocol (CLNP) as defined in ISO-, is optional. The following requirements apply for an IWF and mobile station that support an OSI network interface. To select OSI interworking via a PPP Link Layer, the mobile station should request Service Option 0 or Service Option. For Service Options 0 and, the IWF Link Layer shall support the following PPP protocol numbers: 0x00 OSI Network Layer 0x0 OSI Network Layer Control Protocol (OSINLCP) 0 For Service Options 0 and, the mobile station shall support the PPP OSI Network Layer Control Protocol (OSINLCP) defined in RFC.. CDPD Application Support Support of CDPD applications (see IS-) is optional. The following requirements apply for an IWF and mobile station that support CDPD applications. To select CDPD As discussed in RFC, the specific OSI protocol is determined according to the first octet in each Network Protocol Data Unit (NPDU), which is the Network Layer Protocol Identifier (NLPID), defined in ISO/TR. -

234 TIA/EIA/IS-0-A. interworking via a PPP Link Layer, the mobile station shall request Service Option 0 or Service Option. For Service Options 0 and, the PPP Layer shall support the following PPP protocol numbers: 0x00 Mobile Network Registration Protocol (MNRP) 0 0 The PPP Layer shall also support the protocol numbers required for either the IP or ISO protocol interface, or both, in accordance with. and/or., respectively. For Service Options 0 and, either the TE (if the Relay Layer R m interface protocol option is selected) or the MT (if the Network Layer R m Interface Protocol option is selected) shall support the Mobile Network Registration Protocol (MNRP) defined in Part 0 of IS-, including the authentication parameters and procedures defined in Part 0 of IS-. MNRP Registration shall be performed after a PPP establishment indication is received. A successful MNRP Registration (including ESH and ISC) shall take place before the network layer control protocols (IPCP or OSINLCP) may begin negotiation. While an IWF Link Layer connection is open for Service Option 0 or, the mobile station shall respond to MNRP query messages (ESQ). If the MT or the TE closes the IWF Link Layer connection, the entity performing the closure should perform MNRP deregistration (ESB) before closing the IWF Link Layer. An IWF supporting Service Option 0 or Service Option shall support CDPD protocols at and above the Network Layer. 0 Requirements for the CDPD protocols are given in IS-. 0 That is, all CDPD protocol layers above the SNDCP layer. -

235 Data Service Options for Wideband Spread Spectrum Systems: STU-III Services TIA/EIA/IS-0-A. (PN-.) Ballot Resolution Version March,

236 Copyright TIA

237 TIA/EIA/IS-0-A. CONTENTS INTRODUCTION...-. General Description...-. STU-III Description...-. Terms...-. References...-. STU-III Service Protocol Stack Reference Model...- REQUIREMENTS FOR THE STU-III SERVICE...-. General Requirements Radio Link Protocol Radio Interface Service Option Numbers Multiplex Options Service Negotiation Um Interface Requirements Connection Establishment Call Origination and Termination Traffic Channel Handoff Resynchronization of STU Traffic Connection Release...-. TIA/EIA/IS- Requirements STU-III Connection Establishment and Release STU-III L Interface Adaptation Layer (SLAL) BS/MSC SLAL Initialization IWF SLAL Initialization Data Transfer BS/MSC SLAL Procedures IWF SLAL Procedures SLAL Frame Format...-. Mobile Station STU-III Service Control Processing Mobile Station STU-III Service Control States Inactive STU-III State...- i

238 TIA/EIA/IS-0-A. 0 CONTENTS... Active STU-III State Mobile Station STU-III Service Control Procedures Unselected Substate Selected Substate Clear Voice Substate Secure Transparent Substate Secure Non-Transparent Substate STU-III Service Invocation Support for STU-III Traffic Resynchronization... - DIGITAL STU-III CALL EXAMPLES (INFORMATIVE) Mobile Initiated Service Change STU-III Secure Mode Invocation - Mobile Initiated STU-III Return to Clear Voice Mode - Mobile Initiated Remote STU Initiated Service Change STU-III Secure Mode Invocation - Remote STU-III Initiated STU-III Return to Clear Voice Mode - Remote STU-III Initiated Half-Duplex Secure Mode Selection Rekey FIGURES Figure.-. STU-III Connection...- Figure.-. The STU-III Service Protocol Stack...- Figure.-. The STU-III Service Protocol Stack with L Interface...- Figure..-. MT Service Control Function State Diagram...- Figure..-. Mobile Initiated Secure and Clear Voice Mode Invocation...- Figure..-. Mobile Terminated Secure and Clear Voice Mode Invocation...- ii

239 TIA/EIA/IS-0-A INTRODUCTION. General Description Service Options 0 and provide a service capable of bearing secure traffic from U.S. Government digital STU-III telephones on TIA wideband spread-spectrum systems using the protocols and procedures defined herein. These service options provide interoperable communications between existing U.S. Government secure telephone units (STU-IIIs), operating in the Public Switched Telephone Network (PSTN) and Government secure digital terminal equipment. Service Option 0 provides a fixed, low delay bit transport with bit-count integrity and uses a transparent radio link protocol that has no retransmissions and no forward error correction beyond that provided by TIA/EIA/IS-. Service Option provides improved error rates by using a radio link protocol with retransmissions for error correction, at the cost of higher delay. The characteristics provided by Service Option 0 are preferred for STU-III voice traffic whereas those provided by Service Option are preferred for STU-III data traffic.. STU-III Description STU-III terminals provide clear and secure voice and secure data communications in the PSTN and over analog cellular networks. A digital version of the STU-III is employed for use over wideband spread spectrum networks to maintain interoperability with the existing analog STU-IIIs. All STU-III calls start as clear (i.e., unencrypted) voice supported using any standard voice service option. Modem control AT commands on the R m interface are used to invoke the STU-III service by connecting either Service Option 0 or. IWF functions supporting the STU-III modem functionality are required for connectivity to STU-IIIs in the PSTN. A STU-III IWF can be implemented as an integral part of the BS/MSC or connected to the BS/MSC via an L interface. STU-III terminals in the PSTN can initiate transitions to secure mode by generating a Go Secure signaling tone exchange (see FSVS-0). Mobile stations complying with this standard detect such tones, and in turn initiate the transition to STU-III services. The digital STU-III can be implemented either as an integrated terminal, or MT0, or as an MT/TE pair. A separate digital STU-III unit can be connected to a compatible data interface provided by the digital cellular mobile terminal (MT). Figure.- illustrates an end-to-end connection of the latter case. Data terminal equipment, such as a computer or digital fax requiring STU-III data mode can interface to the digital STU-III data port and be supported using either STU-III Service Option. -

240 TIA/EIA/IS-0-A. Digital STU-III STU Vocoder Security Black Digital Interface MT BS/MSC PSTN STU-III Data Processing DTE TE STU-III IWF STU Modem Black Digital Interface Figure.-. STU-III Connection. Terms 0 0 APP (Application Interface). AT Command processing layer in the STU-III service protocol stack. AT Command Set. Command set interface between data terminal equipment (DTE) and data circuit terminating equipment (DCE). Base Station (BS). A station in the Domestic Public Cellular Radio Telecommunications Service, other than the mobile station, used for communicating with mobile stations. Depending upon the context, the term base station may refer to a cell, a sector within a cell or other part of the cellular system. Black Digital Interface (BDI). STU-III digital message exchange for signaling use between the STU-III Interworking Function (IWF) and the digital STU-III Terminal Equipment. See FSVS-. BS/MSC. BS/MSC refers to a BS and an MSC considered as a single entity. Clear Voice. Any voice service option where the voice traffic on the PSTN segment is not encrypted. Data Circuit-Terminating Equipment (DCE). A DCE connects a DTE to the PSTN. A typical DCE would be a V-series modem. DTE. Data Terminal Equipment. FR SVC. Frame Relay Switched Virtual Circuit. Go Secure Tone. A 00Hz continuous phase tone as defined in FSVS-0. IWF. Interworking Function. Mobile Station. A station in the Domestic 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. -

241 TIA/EIA/IS-0-A. 0 MSC. Mobile Switching Center. MT0. Mobile Termination 0. MT. Mobile Termination. PSTN. Public Switched Telephone Network. RLP. The Radio Link Protocol. SAL. STU-III Adaptation Layer. SLAL. STU-III L interface Adaptation Layer STU-III. U.S. Government third generation Secure voice and data Telephone Unit. SVC. Switched Virtual Circuit. TE. Terminal Equipment. Transparent RLP. A transparent version of the Radio Link Protocol (see IS-0.).. References 0 EIA/TIA--E EIA/TIA-0 EIA/TIA- FSVS-0 FSVS- FSVS-0 TSB TIA/EIA/IS- TIA/EIA/IS- Interface Between DTE and DCE Employing Serial Binary Data Interchange. Serial Asynchronous Automatic Dialing and Control. Extensions to Serial Asynchronous Automatic Dialing and Control. Signaling Plan - Interoperable Modes for STU-III. Interface Control Document for the STU-III Black Digital Interface. Terminal and Performance Specifications for STU-III. TSB: Support for. kbps Data Rate and PCS Interaction for Wideband Spread Spectrum Cellular Systems. Mobile Station-Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular System. Data Services Interworking Function Interface for Wideband Spread Spectrum Systems. 0. STU-III Service Protocol Stack Reference Model The STU-III service architecture is defined by the protocols used across the different interface points. The Radio Link Protocol (RLP) as defined in IS-0. is used over the TIA/EIA/IS- multiplex sublayer at the U m interface. Communication across the PSTN interface is by one of Bell 0, CCITT V.bis (modified) or CCITT V. (modified) modem protocols as defined in FSVS-0/FSVS-0. Communications across the PSTN spans the A i and W reference points. EIA/TIA--E is used in synchronous or asynchronous mode to communicate across the R m interface point if this interface exists (see IS-0.). The STU-III Adaptation Layer (SAL) provides a traffic management interface between the synchronous STU-III bit stream and the RLP layer. The STU-III IWF can be implemented as an integral part of the BS/MSC or connected to the BS/MSC via an L interface. The -

242 TIA/EIA/IS-0-A. STU-III L interface Adaptation Layer (SLAL) provides a mechanism to extend the SAL-to- RLP interface across the L interface. Figure.- depicts the STU-III service protocol stack when the IWF is an integral part of the BS/MSC. Figure.- depicts the protocol stack when the IWF is connected to the BS/MSC via an L interface. TE BS/MSC/IWF (BMI) 0/0(H) MT APP APP SAL RLP SAL RLP -E -E -E IS- IS- 0/0(L) Rm Um Figure.-. The STU-III Service Protocol Stack TE IWF 0/0(H) MT BS/MSC APP APP SAL RLP RLP SLAL SAL SLAL -E -E -E IS- IS- SVC SVC 0/0(L) 0 Rm Um L Figure.-. The STU-III Service Protocol Stack with L Interface 0 The STU-III protocol stacks shown above are valid for Service Option 0 and Service Option with the following considerations: 0/0(H) refers to the STU-III message signaling and security functions described in FSVS-0 and FSVS-0. 0/0(L) refers to the STU-III physical layer and modem functions described in FSVS-0 and FSVS-0. refers to the STU-III message exchange protocol described in FSVS-. APP refers to the AT command processing layer. See IS-0.. -

243 TIA/EIA/IS-0-A. 0 Service Option 0 uses Transparent RLP. Service Option uses Non-Transparent RLP (see IS-0.). The primary function of the STU-III Adaptation Layer (SAL) is to generate a synchronous bit stream for the land STU-III terminal or for the mobile station. The SAL processes RLP indications (see Figure.- and IS-0.), SLAL indications (see Section...) as well as STU-III service option data. The RLP layer provides the count of lost octets (for Service Option 0 only) to the SAL layer. Implementation of the SAL is left to the manufacturer. SLAL communicates the connected service option, the negotiated rate set and service option data while providing bit count integrity and buffering across the L interface. A detailed description of SLAL is provided in Section.. For Service Option 0, the SLAL provides replacement of lost data octets with octets of value 0xaa to the SAL or RLP. The RLP layer provides the count of lost octets (for Service Option 0 only) to the SLAL layer. The mobile station can be implemented as a TE-MT pair. The TE connects to the MT via an R m interface. This interface supports both synchronous and asynchronous data transfer. The SVC (Switched Virtual Circuit) provides a data link between the BS/MSC and the IWF. The data link procedures are as defined in TIA/EIA/IS-. 0 -

244

245 TIA/EIA/IS-0-A REQUIREMENTS FOR THE STU-III SERVICE. General Requirements Communication across the U m interface for Service Options 0 and is implemented using a protocol stack consisting of physical layer and multiplex sublayer procedures as defined in TIA/EIA/IS- and a Radio Link Protocol (see Figure.-). Service negotiation procedures (see Section... of TSB) are used to connect Service Options 0 or for STU-III service. Service Option 0 uses The Transparent Radio Link Protocol. Service Option uses The Non-Transparent Radio Link Protocol... Radio Link Protocol The procedures for the Transparent and Non-Transparent Radio Link Protocol are defined in IS-0.. For Service Option 0, the Transparent Radio Link Protocol shall be used. Transparent RLP provides the bit-count integrity function for Service Option 0. In the event of a frame erasure, the exact number of dropped data bits is determined and they are replaced by the same number of bits in the data stream. For Service Option, the Non-Transparent Radio Link Protocol shall be used. Non- Transparent RLP provides bit-count integrity as well as an improved error rate at the cost of increased end-to-end delay. The increased delay results from the need to simultaneously support retransmissions and synchronous data delivery. A lower error rate is necessary for the secure data service to improve the throughput of upper layers... Radio Interface The mobile station and the BS/MSC shall support the physical layer, multiplex sublayer, radio link management, and call control as defined in TIA/EIA/IS-.... Service Option Numbers The mobile station and the BS/MSC should use Service Option 0 for STU-III voice service and Service Option for STU-III data service.... Multiplex Options Service Option 0 shall support an interface with TIA/EIA/IS- Multiplex Option. Transparent RLP frames for Service Option 0 shall only be transported as primary traffic. Service Option 0 should support an interface with TIA/EIA/IS- Multiplex Option. Transparent RLP frames for Service Option 0 shall only be transported as primary traffic. Service Option shall support an interface with TIA/EIA/IS- Multiplex Option. Non- Transparent RLP frames for Service Option shall only be transported as primary traffic. Service Option should support an interface with TIA/EIA/IS- Multiplex Option. Non-Transparent RLP frames for Service Option shall only be supported as primary traffic. -

246 TIA/EIA/IS-0-A. 0. kbps and. kbps STU-III services should be carried with Rate Set under Multiplex Option. Data rates at. kbps and higher should be carried with Rate Set under Multiplex Option.... Service Negotiation When the mobile station requests a STU-III secure service option, the mobile station is already on a traffic channel and a clear voice service option is connected (see Section.). The mobile station shall perform service negotiation for Service Option 0 and Service Option as described in TIA/EIA/IS-. The BS/MSC should perform service negotiation for Service Option 0 and Service Option as described in the TIA/EIA/IS- except that the BS/MSC shall not propose an initial default service configuration. The BS/MSC should allocate IWF resources for Service Option 0 and Service Option. This may occur concurrently with the service negotiation procedures for STU-III secure service. Table...- lists the valid service configuration attributes for Service Options 0 and. Table...-. Valid Service Configuration Attributes for Service Options 0 and Service Configuration Attribute Valid Selections Forward Multiplex Options Multiplex Options or Reverse Multiplex Options Multiplex Options or Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type Rate sets or, all rates enabled Rate Sets or, all rates enabled Primary Traffic Primary Traffic.. U m Interface Requirements 0... Connection Establishment... Call Origination and Termination If STU-III service is selected, Service Option 0 or shall be connected only if a clear voice service option is already connected. The setup of clear voice calls, either mobile originated or terminated, shall follow the call processing procedures described in TIA/EIA/IS-. The mobile station shall not use the TIA/EIA/IS- Origination Message to propose an initial default service configuration including Service Option 0 or. The mobile station shall reject a Page Message or General Page Message using Service Option 0 or. The BS/MSC should not page the mobile station using Service Option 0 or. -

247 TIA/EIA/IS-0-A Traffic Channel Handoff Soft handoff (see... of TIA/EIA/IS-), or a CDMA-to-CDMA hard handoff (see... of TIA/EIA/IS-) entailing only a change in the frame offset field shall not change the state of the STU-III service control function (see..). Following a CDMA-to-CDMA hard handoff (see... of TIA/EIA/IS-) involving transitions between disjoint sets of BS/MSCs or a frequency change, the RLP layer shall be immediately initialized according to the initialization procedures for Transparent RLP (for Service Option 0) or Non-Transparent RLP (for Service Option ) as described in IS- 0.. CDMA-to-analog handoffs are not supported for Service Options 0 and.... Resynchronization of STU Traffic Service Option 0 or Service Option shall not be disconnected when a resynchronization of secure traffic occurs.... Connection Release The mobile station shall disconnect the STU-III Service Option when any of the following is true: The mobile station is issued an AT+CSO <n> command where n is a clear voice service option or the mobile station is issued an indication, by manufacturer specific means, to connect a clear voice service option. The MT can receive an AT+CSO command to connect a clear voice service option if an FSVS-0 User Abort or FSVS- 0 (or FSVS-) Failed Call message is received by the mobile station. FSVS-0 User Abort and Failed Call messages can be sent to the mobile station by the remote (land) STU-III terminal. A FSVS- Failed Call message can be sent by the STU-III IWF to the mobile station when the IWF detects a loss of the carrier signal in the PSTN connection for a duration of at least five seconds or if the PSTN connection with the remote (land) STU-III terminal is lost. The mobile station is issued a ATH command or the mobile station is issued an indication, by manufacturer specific means, to release the call. The MT can receive an ATH command to release the call if an FSVS-0 Release message is received by the mobile station from the remote (land) STU-III terminal.. TIA/EIA/IS- Requirements TIA/EIA/IS- specifies procedures on the L interface for support of data services. It defines a path for transport of end-user data between the BS/MSC and IWF, a path for the IWF to access the PSTN, and a signaling path for communicating control information between the BS/MSC and IWF. For STU III service, the L interface protocols and recommendations specified in TIA/EIA/IS- are used, except where noted below. STU III service is treated as a mobile-terminated circuit-mode data service, as there is an existing PSTN call prior to STU III service connection. -

248 TIA/EIA/IS-0-A STU-III Connection Establishment and Release The BS/MSC and IWF use an FR SVC to transmit and receive STU III L Interface Adaptation Layer frames (see..). For STU III service, there is no Link Layer connection between the MS and IWF. Prior to connecting Service Option 0 or Service Option, the BS/MSC should initiate FR SVC establishment between the BS/MSC and the IWF for mobile-terminated circuit-mode service, using the procedures described in Section.. of TIA/EIA/IS-. The BS/MSC should also place a call to the IWF on the PSTN path, following the procedures in Section.. of TIA/EIA/IS-, to connect the existing PSTN call to the IWF. The BS/MSC should not clear an established FR SVC when transitioning between STU III service options. After traffic channel release, or if the BS/MSC negotiates a service configuration that does not include a STU III service option, the BS/MSC should clear the FR SVC, using the procedure described in Section.. of TIA/EIA/IS-. If the IWF clears the PSTN path for a MS with a STU III service option connected, or clears the FR SVC, the BS/MSC should disconnect the STU-III service option... STU-III L Interface Adaptation Layer (SLAL) The STU-III L Interface Adaptation Layer (SLAL) replaces the Adaptation Layer function described in Section. of TIA/EIA/IS-. The SLAL maintains three variables: CURRENT_ST identifies the STU III service currently connected. TRANSMITTED_OC counts the total number of data octets transmitted by the SLAL since CURRENT_ST last changed value. RECEIVED_OC counts the total number of data octets received by the SLAL since CURRENT_ST last changed value. These variables shall have the same length as the corresponding SLAL frame fields: ST and OC, respectively (see..).... BS/MSC SLAL Initialization When the BS/MSC connects a STU III service option, the BS/MSC SLAL shall: Set CURRENT_ST to the appropriate service type value in accordance with the encodings of ST as defined in... Set TRANSMITTED_OC and RECEIVED_OC to IWF SLAL Initialization When the IWF establishes an FR SVC for STU III service, the IWF SLAL shall set all SLAL variables to 0. -

249 TIA/EIA/IS-0-A Data Transfer When transmitting an SLAL frame, SLAL shall copy the value of CURRENT_ST into ST and copy the value of TRANSMITTED_OC into OC. At any time, SLAL may send an SLAL frame with a Data field of length BS/MSC SLAL Procedures Whenever RLP provides the BS/MSC SLAL with an exact number of octets erased on the U m interface, SLAL shall act as if RLP has released that number of new data octets with each octet having value 0xaa. When RLP releases new data of length new_data_length to the BS/MSC SLAL, SLAL shall perform the following: Set TRANSMITTED_OC to (TRANSMITTED_OC + new_data_length) modulo. If each octet of new data has value 0xaa, SLAL may discard it. Otherwise, SLAL shall copy the data into the Data field of the SLAL frame. Send the SLAL frame. When the BS/MSC SLAL receives an SLAL frame, it shall perform the following: If ST does not equal CURRENT_ST, discard the frame. If the frame has not been discarded, pass a total of (OC - RECEIVED_OC) modulo octets of data to the upper layer, where the initial octets have value 0xaa to account for lost octets and the last octets are from the received Data field. Then set RECEIVED_OC to the value of OC.... IWF SLAL Procedures When SAL releases new data of length new_data_length to the IWF SLAL, SLAL shall perform the following: Set TRANSMITTED_OC to (TRANSMITTED_OC + new_data_length) modulo. Copy the data into the Data field of an SLAL frame. Send the SLAL frame. When the IWF SLAL receives an SLAL frame, it shall perform the following: If ST does not equal CURRENT_ST, then: - Set CURRENT_ST to the value of ST. - Set TRANSMITTED_OC and RECEIVED_OC to 0. - Pass an ST change indication to its upper layer with a value of CURRENT_ST. Pass a total of (OC - RECEIVED_OC) modulo octets of data to the upper layer, where the initial octets have value 0xaa to account for lost octets and the last octets are from the received Data field. Then set RECEIVED_OC to the value of OC. -

250 TIA/EIA/IS-0-A... SLAL Frame Format The following SLAL frame is inserted in the Data Block field of the FR SVC UI-frame defined in Figure.- of TIA/EIA/IS-. Field Length (bits) ST OC Data Variable octets ST - Service type. ST is usually identical for SLAL frames in both the forward and reverse directions. The ST field is defined as follows: 0 - None assigned. - Transparent RLP (Service Option 0) with rate set. - Transparent RLP (Service Option 0) with rate set. - Non-transparent RLP (Service Option ) with rate set. - Non-transparent RLP (Service Option ) with rate set. Other values reserved. OC Octet count. OC represents the total number of data octets transmitted in the same direction, modulo, including the data octets in the current frame, since the last time ST changed value. Data Data octets.. Mobile Station STU-III Service Control Processing.. Mobile Station STU-III Service Control States The STU-III service in a mobile station shall consist of the Active State and the Inactive State.... Inactive STU-III State When the STU-III service is in the Inactive State, the mobile station does not provide STU- III secure service. Selection of STU-III service shall be done in the Inactive State. Mobile stations implemented as TE-MT pairs shall use the AT+CRM command to select the STU-III service. Service selection methods for MT0s may be manufacturer specific. The mobile station can provide a clear voice service in the Inactive State. Prior to entering the Active State of STU-III service, a clear voice service option shall be connected. In the Inactive State of the STU-III service, three service control substates are defined: Unselected Substate - Service control procedures in the Unselected Substate are described in Section... -

251 TIA/EIA/IS-0-A. 0 Selected Substate - Service control procedures in the Selected Substate are described in Section... Clear Voice Substate - Service control procedures in the Clear Voice Substate are described in Section Active STU-III State When the STU-III service is in the Active State, the mobile station provides either STU-III secure voice service or STU-III secure data service. Mobile stations implemented as TE- MT pairs shall use the ATH command or the AT+CSO=<n> (n is a clear voice service option) command to enter the Inactive State from the Active State. MT0s may use manufacturer specific methods to enter the Inactive State from the Active State. In the Active State of the STU-III service, two service control substates are defined: Secure Transparent Substate - Service control procedures in the Secure Transparent Substate are described in Section... Secure Non-Transparent Substate - Service control procedures in the Secure Non- Transparent Substate are described in Section... The five service control substates defined above form the basis of the STU-III mobile station service control state diagram shown in Figure..-. -

252 TIA/EIA/IS-0-A... Mobile Station STU-III Service Control Procedures The MT service control function is indicated by the state diagram in Figure..-. Unselected Substate of the Inactive STU-III State Any SO 0 or Connected and AT+CRM AT+CRM= and clear voice SO is connected AT+CRM AT+CRM= and either no clear voice SO connected or an SO not requiring Rm interface connected Selected Substate of the Inactive STU-III State AT+CRM Any SO not requiring Rm interface connected AT+CDV; Connect a Clear Voice SO AT+CHV; Disconnect Clear Voice SO ATH; Terminate STU-III Service Clear Voice Substate of the Inactive STU-III State AT+CSO ; Connect SO AT+CSO 0; Connect SO 0 AT+CSO ; Connect Clear Voice SO Note: Not all state transitions are shown AT+CSO ; Connect Clear Voice SO Secure Non-Transparent Substate of the Active STU-III State AT+CSO ; Connect SO Secure Tranparent Substate of the Active STU-III State AT+CSO 0; Connect SO 0 Figure..-. MT Service Control Function State Diagram -

253 TIA/EIA/IS-0-A Unselected Substate When the mobile station service control function is in the Unselected Substate of the Inactive STU-III State, The AT+CRM parameter has a value other than. Any service option other than Service Options 0 or can be connected. While in the Unselected Substate of the Inactive STU-III State, the mobile station shall perform the following: If the MT receives an AT+CRM= command and a clear voice service option is connected, the mobile station shall select STU-III service and the mobile station service control function shall transition to the Clear Voice Substate of the Inactive STU-III State. If the MT receives an AT+CRM= command and no clear voice service option is connected or a service option not requiring an R m interface is connected, the mobile station shall select STU-III service and the mobile station service control function shall transition to the Selected Substate of the Inactive STU-III State.... Selected Substate When the mobile station is in the Selected Substate of the Inactive STU-III State, The AT+CRM parameter has a value of. Any service option that does not utilize the R m interface and is not a STU-III service option, may be connected. While in the Selected Substate of the Inactive State, the mobile station shall perform the following: If the mobile receives a Page Message from the BS/MSC requesting any service option other than clear voice service options and STU-III service options (0 and ), the mobile station shall attempt to connect the service option requested in accordance with TIA/EIA/IS- provided that the service option does not utilize the R m interface. The mobile station shall reject the request to connect a service option that utilizes the R m interface. Upon connection of the service option, the mobile station service control function shall remain in the Unselected Substate of the Inactive STU-III State. If the mobile receives a Page Message from the BS/MSC requesting a clear voice service option, the mobile station shall attempt to connect the service option requested in accordance with TIA/EIA/IS-. Upon connection of the clear voice service option, the mobile station service control function shall transition to the Clear Voice Substate of the Inactive STU-III State. If the MT receives an AT+CDV command on the R m interface or the user enters a dial string on the MT keypad, the mobile station shall perform the Mobile Station Origination Operation (see TIA/EIA/IS-) to connect a clear voice service option. -

254 TIA/EIA/IS-0-A Upon connection of the clear voice service option, the mobile station service control function shall transition to the Clear Voice Substate of the Inactive STU-III State. If the MT receives an AT+CRM command selecting a different R m interface option than STU-III service, the mobile station service control function shall transition to the Unselected Substate of the Inactive STU-III State.... Clear Voice Substate When the mobile station STU-III service control function is in the Clear Voice Substate of the Inactive STU-III State, The AT+CRM parameter has a value of. A clear voice service option is connected. While in the Clear Voice Substate of the Inactive STU-III State, the mobile station shall perform the following: If the MT receives an AT+CHV command or if the user provides an indication to the mobile station to release the call, the mobile station service control function shall transition to the Selected Substate of the Inactive STU-III State. If the MT receives an AT+CSO=<n> (n is a STU-III service option) or, if the user provides the mobile station an indication to use a STU-III service option, the mobile station shall invoke a STU-III service using the procedures described in Section... Upon completion of the invocation procedures for STU-III service, the mobile station service control function shall transition to the Secure Transparent Substate of the Active STU-III State (if Service Option 0 is connected) or the Secure Non- Transparent Substate of the Active STU-III State (if Service Option is connected). If the MT receives an AT+CRM command selecting a different R m interface option than STU-III service, the mobile station service control function shall transition to the Unselected Substate of the Inactive STU-III State.... Secure Transparent Substate When the mobile station service control function is in the Secure Transparent Substate of the Active STU-III State, The AT+CRM parameter has a value of. Service Option 0 is connected. FSVS- messages for signaling and negotiating STU-III modem parameters at the IWF shall be exchanged between the mobile station and the IWF. When modem training is complete and terminal mode selection and call set up messages are exchanged between the mobile station and the remote STU-III terminal (see FSVS-0 AND FSVS-0), secure traffic can be sent and received by the mobile station. While in the Secure Transparent Substate of the Active STU-III State, the mobile station shall perform the following: -0

255 TIA/EIA/IS-0-A If the MT receives an ATH command or if the MT0 receives an indication from the user to release the call, the mobile station shall release the call. When the call is released, the mobile station service control function shall transition to the Selected Substate of the Inactive STU-III State. If the MT receives an AT+CSO=<n> (n is a clear voice service option) command or if the MT0 receives an indication from the user to use clear voice, the mobile station shall perform service negotiation to connect a clear voice service option. Upon connection of the clear voice service option, the mobile station service control function shall transition to the Clear Voice Substate of the Inactive STU-III State. If the MT receives an AT+CSO=<> command or if the MT0 receives an indication from the user to use Service Option, the mobile station shall perform service negotiation to connect Service Option. Upon connection of Service Option, the mobile station service control function shall transition to the Secure Non- Transparent Substate of the Active STU-III State. If the MT receives an AT+CRM command selecting a different R m interface option than STU-III service, the mobile station service control function shall transition to the Unselected Substate of the Inactive STU-III State. The mobile station may release the PSTN call as a result of the transition.... Secure Non-Transparent Substate When the mobile station service control function is in the Secure Non-Transparent Substate of the Active STU-III State, The AT+CRM parameter has a value of. Service Option is connected. FSVS- messages for signaling and negotiating STU-III modem parameters at the IWF shall be exchanged between the mobile station and the IWF. When modem training is complete and terminal mode selection and call set up messages are exchanged between the mobile station and the remote STU-III terminal (see FSVS-0 AND FSVS-0), secure traffic can be sent and received by the mobile station. While in the Secure Non-Transparent Substate of the Active STU-III State, the mobile station shall perform the following: If the MT receives an ATH command or if the MT0 receives an indication from the user to release the call, the mobile station shall release the call. When the call is released, the mobile station service control function shall transition to the Selected Substate of the Inactive STU-III State. If the MT receives an AT+CSO=<n> (n is a clear voice service option) command or if the MT0 receives an indication from the user to use clear voice, the mobile station shall perform service negotiation to connect a clear voice service option. Upon connection of the clear voice service option, the mobile station service control function shall transition to the Clear Voice Substate of the Inactive STU-III State. If the MT receives an AT+CSO=<0> command or if the MT0 receives an indication from the user to use Service Option 0, the mobile station shall perform service -

256 TIA/EIA/IS-0-A negotiation to connect Service Option 0. Upon connection of Service Option 0, the mobile station service control function shall transition to the Secure Transparent Substate of the Active STU-III State. If the MT receives an AT+CRM command selecting a different R m interface option than STU-III service, the mobile station service control function shall transition to the Unselected Substate of the Inactive STU-III State. The mobile station may release the PSTN call as a result of the transition... STU-III Service Invocation When the remote (land) STU-III terminal initiates the invocation of STU-III service, the mobile station shall detect the Go Secure tone sent by the remote (land) STU-III terminal. This tone is carried by the clear voice service option and initiates a service option change to a secure service option. The mobile station may detect the Go Secure tone by one of the following: The MT may detect the tone and may notify the TE by asserting Circuit (CE). The MT may pass the tone to the TE via an analog voice-band circuit. The AT+CAU parameter shall be set to to enable this transfer. By other manufacturer specific means. When the mobile station detects the Go Secure tone or if the user provides an indication to the mobile station to use a STU-III service option, the MT shall wait for the TE to issue an AT+CSO=<n> command (n is a STU-III secure service option). The mobile station shall then perform service negotiation to connect the secure service option. When a STU-III service option is connected, the mobile station shall perform the following: Transparent RLP (if Service Option 0 is connected) or Non-Transparent RLP (if Service Option is connected) shall be initialized. The MT shall return a CONNECT result code to the TE. The MT shall wait for the TE to assert Circuit 0/ (CD). When Circuit 0/ (CD) is asserted, the MT shall assert Circuit 0 (CC) and deassert Circuit (CE) if used. The mobile station service control function shall transition to the Secure Transparent Substate of the Active STU-III State (if Service Option 0 is connected) or the Secure Non-Transparent Substate of the Active STU-III State (if Service Option is connected)... Support for STU-III Traffic Resynchronization In the Secure Transparent Substate of the Active STU-III State or the Secure Non- Transparent Substate of the Active STU-III State, the MT should provide support for resynchronizing the encryptors of the STU-III traffic when the Adaptation Layer in the MT is unable to maintain the bit count integrity of the STU-III traffic (see FSVS-0 AND FSVS-0). -

257 TIA/EIA/IS-0-A. The MT should notify the TE of this condition by de-asserting Circuit 0 (CC) for an implementation dependent time greater than 0 ms. Should the TE receive such indication, the TE may subsequently re-synchronize the STU-III encryptors according to the procedures defined in FSVS-0 and FSVS-0. -

258

259 TIA/EIA/IS-0-A. 0 DIGITAL STU-III CALL EXAMPLES (INFORMATIVE). Mobile Initiated Service Change.. STU-III Secure Mode Invocation - Mobile Initiated To initiate a change to a STU-III service option from another service option, the mobile station performs service negotiation (see TIA/EIA/IS-) requesting a change to Service Option 0 or Service Option. The BS/MSC then connects a STU-III IWF... STU-III Return to Clear Voice Mode - Mobile Initiated Mobile station initiated returns to a clear voice service option may be caused by an FSVS- 0 User Abort message being sent or an FSVS-0 Failed Call message being sent due to the inability to maintain crypto-synchronization. To return to a clear voice service option from Service Option 0 or Service Option, the mobile station (MT0 or MT) performs service negotiation requesting a change to a clear voice service option. The BS/MSC then disconnects the STU-III IWF. The signaling sequence for transitions between clear and secure modes is illustrated in Figure..-. A description of the signaling protocols numbered in the figure above is presented in Table..-. -

260 TIA/EIA/IS-0-A. STU-III/D Rm Secure MT U MSC m BS Ai PSTN W STU-III AT+CRM= ok AT+CDV connect AT+CSO 0 connect L IWF Clear Mode Voice Traffic Service Request Message SO_REQ=0 Service Connect Message Service Connect Completion Invo ke IWF a b Go Secure - BDI Message Secure Ack - BDI Message Call Setup Secure Traffic 00 Hz - Go Secure P00 - Secure Ack. Modem Training Abort (Secure Mode) AT+CSO ok Service Request Message SO_REQ= Service Connect Message Service Connect Completion IWF Release Clear Mode Voice Traffic Figure..-. Mobile Initiated Secure and Clear Voice Mode Invocation Table..-. Description of Signaling for Mobile Initiated Service Change Number Protocol Description () A Voice Service Option Clear voice precedes STU-III Service Option. () IS-0 User control command to notify MT of secure mode request. () EIA/TIA IS- Service Negotiation Procedures () FSVS- FSVS-0 and FSVS-0 a) BDI message exchange and modem training. b) Signaling and terminal mode selection between end-to-end STU-IIIs. () IS-0 AT+CSO initiates Service Negotiation procedures to connect a clear voice service option. -

261 TIA/EIA/IS-0-A. 0. Remote STU Initiated Service Change.. STU-III Secure Mode Invocation - Remote STU-III Initiated A service request change from clear to secure mode initiated by a land side STU-III terminal requires the mobile station to perform tone detection of the Go Secure tone sent by the remote STU-III terminal. This tone is carried by the voice service option and initiates a change to Service Option 0 or Service Option. The mobile station performs service negotiation requesting a change to Service Option 0 or Service Option... STU-III Return to Clear Voice Mode - Remote STU-III Initiated When the mobile station receives a FSVS-0 Abort or Failed Call message from the land side STU-III terminal, it performs service negotiation requesting a transition to a voice service option. The signaling sequence for remote STU-III initiated service change is illustrated in Figure..-. A description of the signaling protocols numbered in the figure above is presented in Table..-. STU-III /D R m Secure MT Um MS C BS Ai PSTN W STU-III AT+CRM= ok AT+CDV connect L Clear Mode Voice Traffic IWF CE - On AT+CSO 0 connect Service Request Message SO_REQ=0 Service Connect Message Service Connect Completion Go Secure Tone - 00 Hz Invoke IWF a b Go Secure Ack. - BDI Message Call Setup Secure Traffic Abort (Secure Mode) P00 - Secu re Ack. Modem Training AT+CSO Service Request Message SO_REQ= IWF Release Service Connect Message CE off; ok Service Connect Completion Clear Mode Voice Traffic Figure..-. Mobile Terminated Secure and Clear Voice Mode Invocation -

262 TIA/EIA/IS-0-A. Table..-. Description of Signaling for Mobile Terminated Service Change Number Protocol Description () A Voice Service Option STU-III Service Option typically begins in clear voice. () EIA/TIA -E FSVS-0 AND FSVS Hz tone detection required to switch from clear to STU-III secure mode. () TIA/EIA/IS- Service Negotiation Procedures. () FSVS- FSVS-0 AND FSVS- 0 () EIA/TIA -E IS-0 a) BDI message exchange and modem training. b) Signaling and terminal mode selection between end-to-end STU-IIIs. User control command to reset to clear voice service. 0. Half-Duplex Secure Mode Selection Half duplex secure mode operates at. kbps. Half duplex operation may require initiation by the mobile station in some cases. The mobile-initiated call setup procedures for half duplex operation are similar to those for the full-duplex case. A service negotiation is then performed and the STU-III IWF invoked. The digital STU-III then exchange signaling messages with the STU-III IWF as specified in FSVS-. Half duplex secure mode requires the STU-III IWF to send a Go Secure tone that is a P00 Hz (an alternating +/- degree phase modulated) tone to the remote STU-III terminal.. Rekey Periodically, a STU-III mobile terminal is required to call the Key Management Center (KMC). Typically, the keying element has an expiration date which prompts the STU-III terminal to display a message such as Call KMC. Without rekeying at this point a user cannot activate a secure mode. A mobile terminal user should follow rekey procedures as defined by the U.S. Government. Once the rekey process is completed, the STU-III mobile user can operate the STU-III terminal in secure modes until the next expiration date stored on the keying element. Half duplex secure mode may be applicable over wideband spread spectrum networks to support Push-to-Talk communications or an electronic rekey function. -

263 Data Service Options for Spread Spectrum Systems: Analog Fax Service TIA/EIA/IS-0-A. (PN-.) Ballot Resolution Version March,

264 Copyright TIA

265 TIA/EIA/IS-0-A. CONTENTS INTRODUCTION...-. General Description...-. Terms...-. References...- REQUIREMENTS FOR THE FAX PROTOCOL STACK...-. Overview...-. The Application Interface...-. Transport Layer...-. Network Layer General Requirements Assignment of Network Address...-. Data Link Layer Sub-Network Dependent Convergence Function PPP Layer IPCP Link Control Protocol...-0 REQUIREMENTS FOR THE RADIO INTERFACE...-. Service Option Number...-. Multiplex Option Interface...-. Procedures Using Service Negotiation Mobile Station Requirements BS/MSC Requirements...- REQUIREMENTS FOR UM INTERFACE CALL PROCESSING...-. Connection Establishment Mobile Origination Mobile Termination Service Option Change to Analog Fax Service Conversation Substate Traffic Channel Handoff...-. Connection Release...-. Authentication...- MOBILE PROCEDURES...- i

266 TIA/EIA/IS-0-A. CONTENTS Mobile Receiving Fax Mobile Connecting State Wait for Local DIS Substate Wait for Remote DCS Substate Wait for Local CFR/FTT Substate Image Transfer State Post Image Transfer State EOP Substate MPS Substate EOM Substate Mobile Transmitting Fax Mobile Connecting State Wait For Remote DIS Substate Wait For Local DCS Substate Training Substate Image Transfer State Post Image Transfer State EOP Substate MPS Substate EOM Substate Disconnect Substate Flags Transmitter Trained Flag Receiver Trained Flag Rates Receiver Rate Transmitter Rate... - IWF PROCEDURES Mobile Receiving Fax IWF Connecting State Wait For Remote DIS Substate Wait For Local DCS Substate... - ii

267 TIA/EIA/IS-0-A. CONTENTS Training Substate Image Transfer State Post Image Transfer State EOP Substate MPS Substate EOM Substate Disconnect Substate Flags Transmitter Trained Flag Receiver Trained Flag Rates Receiver Rate Transmitter Rate...-. Mobile Transmitting Fax IWF Connecting State Wait for Local DIS Substate Wait for Remote DCS Substate Wait for Local CFR/FTT Substate Image Transfer State Post Image Transfer State EOP Substate MPS Substate EOM Substate...- MESSAGES...-. Messages Over the Analog Interface V. Messages Image Data IWF Identification and Capabilities Messages IWF NSF and IWF NSC Messages IWF NSS Message...-. Messages over the Um Interface Control Messages...- iii

268 TIA/EIA/IS-0-A. CONTENTS Data Message Preamble Message Max Rate Message Start CED Message Formatting octets over the Um interface Bit Format of Octets Control, Preamble, Max Rate, and Start CED Messages Byte Escaping of Flags... - CALL FLOWS Call Set-Up Calls Originating as Analog Fax Calls Originating as Voice, then Transitioning to Analog Fax IWF and MT Procedures During Conversation State... - TIMERS DIS/DTC MODIFICATIONS AT COMMAND PROCESSING General Requirements Basic AT Command Processing Action Commands Basic Result Codes AT Command Set Extensions for Modem Control Cellular AT Command Processing AT+CVF Command Processing AT+CVFQ? Command Processing AT+CFG Command Processing... - iv

269 TIA/EIA/IS-0-A. FIGURES Figure.-. The Analog Fax Protocol Stack Architecture...- Figure.-. MT RX Fax Layer States in a Mobile Receiving Fax Call...- Figure.-. MT TX Fax Layer States in a Mobile Transmitting Fax Call...- Figure.-. IWF TX Fax Layer States in a Mobile Receiving Fax Call...- Figure.-. IWF RX Fax Layer States in a Mobile Transmitting Fax Call...- Figure.-. T.0 V. Message Format...- Figure -. Message and Signal Representation Used in Call Flows...- Figure..-. Call Set-Up for a Mobile Receiving Fax Call Initiated as Analog Fax...- Figure..-. Call Set-Up for a Mobile Transmitting Fax Call Initiated as Analog Fax..- Figure..-. Call Set-Up as Voice Transitioning to Mobile Receiving Fax. Voice Call Shown as Mobile-Terminated and Fax Call Detected Using V. Preamble Detection...- Figure..-. Call Set-Up as Voice Transitioning to Mobile Receiving Fax. Voice Call Shown as Mobile-Originated and Fax Call Detected Using V. Preamble Detection. - Figure..-. Call Set-Up as Voice Transitioning to Mobile Transmitting Fax. Voice Call Shown as Mobile-Originated and Fax Call Detected Using V. Preamble Detection...- Figure..-. Call Set-Up as Voice Transitioning to Mobile Transmitting Fax. Voice Call Shown as Mobile-Terminated and Fax Call is Detected Using V. Preamble Detection...- Figure.-. Typical Mobile Receiving Fax Call Where the Initial Fax Training Rate from the Transmitting Fax Machine is Supported by the Air Interface...- Figure.-. Mobile Receiving Fax Call Where the Initial Fax Training Rate from the Transmitting Fax Machine is Not Supported by the Air Interface...- Figure.-. Mobile Receiving Fax Call Where the Receiving Fax Machine Rejects the Initial Training Rate...-0 Figure.-. Mobile Receiving Fax Call Illustrating the Use of Timer T...- Figure.-. Mobile Receiving Fax Call with an RTP Response from the RX Fax Machine...- Figure.-. Mobile Receiving Fax Call Illustrating Polling (the TE has a document to send which the PSTN fax machine retrieves)...- Figure.-. Mobile Receiving Fax Call with Corrupted HDLC Frames (corrupted DCS and CFR)...- Figure.-. Mobile Receiving Fax Call with Corrupted HDLC frames and Fax CRP Option (corrupted CFR, MPS, and MCF)...- v

270 TIA/EIA/IS-0-A. TABLES 0 0 Table.-. IP Type of Service... - Table.-. Compression Options... - Table.-. Group Fax Compression Options... - Table..-. Valid Service Configuration Attributes for Service Option Table..-. Valid Service Configuration Attributes for Service Option... - Table...-. MSLT Resetting in the DCS... - Table...-. MSLT Resetting in the DCS... - Table...-. IWF NSF and IWF NSC Message Format... - Table...-. FIF Format for the IWF NSF and IWF NSC Messages... - Table...-. INFO Field Format for TYPE=0x00 Information Element... - Table...-. INFO Field Format for TYPE=0x0 Information Element... - Table...-. INFO Field Format for TYPE=0x0 Information Element... - Table...-. IWF NSS Message Format... - Table...-. FIF Format for the IWF NSS Message... - Table...-. INFO Field Format for TYPE=0x00 Information Element... - Table...-. INFO Field Format for TYPE=0x0 Information Element... - Table..-. Control Message Format... - Table..-. Data Message Format... - Table..-. Preamble Message Format Table..-. Max Rate Message Format... - Table..-. FIF Values for the Max Rate Message... - Table..-. Start CED Message Format... - Table 0-. Rate Bit Modifications Table 0-. MSLT Bit Modification Table..-. Basic Action Commands... - Table..-. Basic Result Codes... - Table.-. IWF to Mobile Station Commands... - vi

271 TIA/EIA/IS-0-A INTRODUCTION. General Description Service Options 0 and provide Analog Group- facsimile (abbreviated as fax hereafter) transmission on TIA/EIA/IS--A and TSB wideband spread spectrum systems using the protocols and procedures defined herein. Service Option 0 provides analog group fax service using a default service configuration including Multiplex Option data rates. Service Option provides group fax service using a default service configuration including Multiplex Option data rates. Other combinations of service configuration attributes are available for these service options through the use of service negotiation procedures defined in TSB.. Terms Analog Fax Layer. The functional layer in the MT or IWF that processes T.0 messages from the fax machine and the over the air messages from the U m interface. In the MT, the Analog Fax Layer operates between the U m interface to the IWF and the RJ- interface to the TE. In the IWF, the Analog Fax Layer operates between the U m interface to the MT and the PSTN interface to the PSTN fax machine. AT Command Set. Command set interface between data terminal equipment (DTE) and data circuit terminating equipment (DCE). Analog Interface. Refers to either the RJ- loop or the PSTN. Base Station (BS). A station in the Domestic Public Cellular Radio Telecommunications Service, other than a mobile station, used for communicating with mobile stations. Depending upon the context, the term base station may refer to a cell, a sector within a cell, or other part of the cellular system. BORSCHT. Battery, Over voltage protection, Ringing, Supervision, Coding, Hybrid and Test. It is a collection of signals and controls necessary to operate an analog phone through an RJ- interface. BS. See base station. BS/MSC. The base station and mobile switching center considered as a single functional entity. CED. Called terminal identification tone (see T.0...). CNG. Calling Tone (see T.0... and T.0 Figure ). CFR, CIG, CRP, CSI, DCN, DCS, DIS, DTC, EOM, EOP, FTT, MCF, MPS, NSC, NSF, NSS, PIN, PIP, PRI-xxx, TSI, RTN, RTP. These are V. signaling messages that are transmitted either by the receiving or transmitting fax machine during a fax call (see T.0..). Digital Facsimile. That form of facsimile in which densities of the original are sampled and quantified as a digital signal for processing, transmission, or storage. -

272 TIA/EIA/IS-0-A Error Correction Mode (ECM). A mode of operation for T.0 fax service providing end-toend reliable data transport. Facsimile. The process by which a document is scanned, converted into the electrical signals, transmitted, and recorded or displayed as a copy of the original. Fax. An abbreviation for facsimile. Group-. Digital Facsimile equipment per ITU-T Recommendation T. and T.0. ICMP. Internet Control Message Protocol. IANA. Internet Assigned Number Authority. Interworking Function (IWF). An IWF provides the functions needed for terminal equipment connected to a mobile termination to communicate with terminal equipment connected to the PSTN. A physical implementation may include a pool of modems. IP. Internet Protocol. IPCP. Internet Protocol Control Protocol. L. L Interface. The interface between an IWF and BS/MSC. LCP. PPP Link Control Protocol. Mobile Station. A station in the Domestic 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. Mobile Termination 0 (MT0). An MT0 is a self-contained data-capable mobile termination that does not support an external interface. Mobile Termination (MT). An MT provides a non-isdn (R m ) user interface, e.g., CCITT V series or CCITT X series. Modem Client. The name given to the TCP well-known port used for CDMA analog fax services in mobile stations. Modem Emulation Service. A wireless data service where the mobile termination appears as a standard telephone modem to a data terminal. Modem Server. The name given to the TCP well-known port used for CDMA analog fax services in a BS/MSC. MSC. Mobile Switching Center. PPP. Point-to-Point Protocol. PSTN. Public Switched Telephone Network. PSTN fax machine. The fax machine or fax modem connected to the IWF through the PSTN. Receiving fax machine. The fax machine or fax modem receiving the fax document. RFC. Request for Comments. The generic name of a standard developed by the Internet Engineering Task Force (IETF). -

273 TIA/EIA/IS-0-A. 0 0 RJ-. The analog interface that connects the MT with the subscriber fax machine (TE). RJ- Loop Functions. This is the analog interface function between the subscriber fax machine and the MT. It provides BORSCHT functionality to emulate the PSTN. RLP. Radio Link Protocol. RTC. Return To Control (see T...). This is a signal that is used to indicate the end of the fax document or page. This signal consists of six consecutive End Of Line (EOL) characters. RX Fax Layer. The Analog Fax Layer that directly interfaces through an analog interface to the receiving fax machine. For example, when the TE is transmitting, the Analog Fax Layer in the IWF is the RX Fax Layer. SNDCF. Sub-Network Dependent Convergence Function. Subscriber Fax Machine. The wireless subscriber s fax machine or fax modem connected to the MT through the RJ- interface. Tandem Call or Tandem Analog Fax Call. A call in which the transmitting fax machine and receiving fax machine are served by either a single IWF containing an analog fax layer or by two distinct IWFs each containing an analog fax layer. TCF. This training sequence is sent through the T. modulation system to verify training and to give a first indication of the acceptability of the channel for a fax data rate (see T.0...). TCP. Transmission Control Protocol. Terminal Equipment (TE). A TE is a data terminal device (such as a fax machine) that has a non-isdn user-network interface, e.g., CCITT V series or CCITT X series. Transmitting fax machine. The fax machine or fax modem sending the fax document. TX Fax Layer. The Analog Fax Layer that directly interfaces through an analog interface to the transmitting fax machine. For example, when the TE is transmitting, the Analog Fax Layer in the MT is the TX Fax Layer. U m. The air interface between the MT and the BS/MSC.. References 0 ANSI J-STD-00- ANSI/TIA/EIA- EIA/TIA-0 EIA/TIA- RFC Personal Station-Base Station Compatibility Requirements for. to.0 GHz Code Division Multiple Access (CDMA) Personal Communications Systems,. Inband DCE Control for Asynchronous DTE-DCE Interfaces Serial Asynchronous Automatic Dialing and Control. Extensions to Serial Asynchronous Automatic Dialing and Control. Internet Protocol. -

274 TIA/EIA/IS-0-A. 0 RFC RFC RFC RFC RFC 0 RFC RFC RFC RFC RFC RFC RFC RFC RFC 0 RFC RFC RFC 00 Internet Control Message Protocol. Transmission Control Protocol. Telnet Protocol Specification. Telnet Options Specification. Internet Standard Subnetting Procedure. Host Extensions for IP Multicasting. Requirements for Internet Hosts Communication Layers. Requirements for Internet Hosts Application and Support. Compressing TCP/IP Headers for Low-Speed Serial Links. Internet Numbers. Path MTU Discovery. The PPP Internet Protocol Control Protocol (IPCP). Type of Service in the Internet Protocol Suite. PPP LCP Extensions. The Point-to-Point Protocol (PPP). PPP in HDLC Framing. Assigned Numbers (most recent version). 0 T. Standardization of group facsimile apparatus for document transmission. T.0 Procedures for document facsimile transmission in the general switched telephone network. TIA/EIA/IS--A TSB Mobile Station-Base Station Compatibility Standard for Dual- Mode Wideband Spread Spectrum Cellular System. Administration of Parameter Value Assignments for TIA/EIA Wideband Spread Spectrum Standards. All references to the T.0 standard refer to the March revision. -

275 TIA/EIA/IS-0-A. TSB Telecommunications Systems Bulletin: Support for. kbps Data Rate and PCS Interaction for Wideband Spread Spectrum Cellular Systems. V. A two-wire modem for facsimile applications with rates up to,00 bits/s. V. 00 bits/s duplex modem standardized for use in the general switched telephone network. V.ter 00/00 bit/s modem standardized for use in the general switched telephone network. 0 V. 00 bits/s modem standardized for use on point-to-point, fourwire leased telephone-type circuits. V.,00 bits/s modem standardized for use on point-to-point, four-wire leased telephone-type circuits. V.bis Data compression procedures for DCEs using error correction procedures -

276

277 TIA/EIA/IS-0-A. REQUIREMENTS FOR THE FAX PROTOCOL STACK. Overview This chapter specifies requirements for an analog facsimile service for CDMA wireless systems based on the protocol stack reference architecture shown in Figure.-. The service is designed to provide fax service over a wireless data link to a group fax machine (TE). Although actual implementations may vary with respect to specific network elements, functionality available over the air (U m ) interface shall be in accordance with the requirements specified in this standard. 0RELOHWDWLRQ ( 0 %0&,:) $SSOLFDWLRQ /D\HU $QDORJ )D[ /D\HU $SS,QW $QDORJ )D[ /D\HU $SS,QW UDQVSRUW /D\HU HWZRUN /D\HU /LQN /D\HU XEVFULEHU )D[ 0DFKLQH - /RRS )XQF WLR QV &,&0, '&),& /& /&,&0 &,,& '&),QWHU IDFH HOD\ /D\HU /, /, HOD\ /D\HU HOD\ /D\HU - P / 0 Figure.-. The Analog Fax Protocol Stack Architecture 0 The Application Layer consists of the analog fax layer and the associated application interfaces in the MT and in the IWF. The application interfaces in the MT and in the IWF support a limited set of EIA/TIA standardized modem control commands necessary for call control and together provide an interface compatible with the fax modem emulation functions of the analog fax layer. The Transport Layer consists of Transmission Control Protocol (TCP). TCP (See RFC ) provides a reliable transport service to all application layer and user data exchanges. The Network Layer consists of ICMP, (see RFC ) and IP (see RFC ) protocols to provide network layer transport of modem control and user data over the CDMA air interface. The Link Layer consists of Point to Point Protocol (PPP), Link Control Protocol (LCP), and Internet Protocol Control Protocol (IPCP). PPP (see RFC and ) provides a multiplexed method to carry higher layer protocol data over serial links. LCP (see RFC 0) provides a mechanism for the Mobile Station and the IWF to negotiate various options provided by PPP. IPCP (see RFC ) allows the Mobile Station to request a temporary IP address from the IWF. -

278 TIA/EIA/IS-0-A The Relay Layer consists of physical and logical interface functions required to support the link, network, transport and application layers described above. Central to the relay layer is the inclusion of a Radio Link Protocol (RLP) (see Chapter ) to improve the error characteristics of the wireless link, thereby reducing the need for Transport Layer retransmissions due to lost data. The protocol stack, as specified in this standard, describes a minimal subset of the TCP, IP and PPP protocols for the mobile station. BS/MSC and IWF protocol implementations shall be compatible with mobile stations having the minimal implementation specified herein.. The Application Interface In the mobile station, CDMA analog fax services shall include an application interface between the analog fax layer and the transport protocol layer. In the IWF, the application interface shall reside between the analog fax layer and the transport protocol layer. The application interface shall provide the following functionality: Modem control, as specified in.. AT Command processing, as defined in. Negotiation of air interface data compression. Data compression over the air interface (optional). In a mobile station, ANSI/TIA/EIA- in-band commands, including any necessary escaping, shall be inserted into data entering the application interface from the analog fax layer as described in ANSI/TIA/EIA-. Option negotiation commands shall then be inserted, including any necessary escaping, as described below. The resulting data shall be passed to the transport layer. In a mobile station, data entering the application interface from the transport layer shall first be parsed to extract the option negotiation commands and the associated escaping. The resulting data shall be parsed to extract ANSI/TIA/EIA- in-band messages (see.). The resulting data shall be passed to the analog fax layer. In the IWF, data entering the application interface from the analog fax layer shall be passed to the transport layer. ANSI/TIA/EIA- in-band commands shall then be inserted, including any necessary escaping, as described in ANSI/TIA/EIA-. Option negotiation commands shall then be inserted, including any necessary escaping, as described below. In the IWF, data entering the application interface from the transport layer shall first be parsed to extract the option negotiation commands and the associated escaping. The resulting data shall be parsed to extract any ANSI/TIA/EIA- in band modem control commands (see.). If the IWF application interface is in command state, the resulting data shall be parsed to extract any AT commands (see ). The resulting data shall be passed to the analog fax layer. -

279 TIA/EIA/IS-0-A. The application interface for CDMA analog fax services shall comply with the requirements of Sections. and. of RFC, with the following modifications: An IWF serving multiple users may be treated as part of a single multi-homed host or as independent hosts. The mobile station application interface should specify type of service as described in RFC. The mobile station and the IWF should specify the types of service shown in Table.-. Table.-. IP Type of Service Service Option Type of Service 0, (Analog Fax) Low delay 0 0 For mobile-originated analog fax calls, the mobile station application interface shall open the transport layer using TCP well-known port 0 ( modem server ) as the destination port. For mobile-terminated data calls, the IWF application layer shall open the transport layer using TCP well-known port ( modem client ) as the destination port. The application interface in the mobile station and the IWF should also support data compression, using the following negotiation protocol. To ensure transparency of user data to compression negotiation commands, the sender shall insert an additional octet of value before each data byte of value, except for IAC octets that are part of negotiation commands. The receiver shall remove the inserted octets of value and any negotiation commands after decompression. The application interface shall support option negotiation commands in accordance with the requirements of RFC, except that only the following commands are required: 0 NAME CODE MEANING SE 0 End of subnegotiation parameters. SB (option code) 0 Indicates that what follows is subnegotiation of the indicated option. WILL (option code) Indicates a desire to begin performing the indicated option. WON'T (option code) Indicates a refusal to perform, or continue performing, the indicated option. DO (option code) Indicates a request that the other station begin performing the indicated option. This protocol is based on the Telnet option negotiation protocol, as described in Internet RFC. -

280 TIA/EIA/IS-0-A DON'T (option code) Indicates a demand that the other station stop performing the indicated option. IAC Interpret as Command. The data compression option shall be indicated by setting the option code to the value shown in Table.- for the type of data compression being negotiated. Data compression parameters shall be negotiated using the procedure described in RFC, and further defined below. If data compression is supported by the IWF, the IWF shall initiate negotiation of data compression by sending a WILL command when the transport layer connection is opened. The mobile station shall respond with a DO or DON T command. The mobile station shall not initiate negotiation of data compression. If the mobile station responds with a DO command, the IWF shall transmit a subnegotiation (SB) command followed by the requested data compression control parameters. The mobile station shall respond with a subnegotiation (SB) command with either the same parameters, an alternative set, or a DON T command. If the mobile station replies with an SB command whose parameters are acceptable to the IWF, the IWF shall send a DO command. If the accepted subnegotiation parameters include a request for forward link compression, the IWF shall compress all applicable data following the DO command. The mobile station shall respond to the DO command with a WILL command. The negotiation process is terminated when the IWF receives the WILL command. If the accepted subnegotiation parameters include a request for reverse link compression, the mobile station shall compress all applicable data following the WILL command. Compression shall be applicable only as follows: For Service Options 0 and, if MMR compression (see ITU-T T.) is used, it shall only be applied to the actual fax image data being transmitted. If MMR compression is negotiated during transmission of a page, the compression shall be enabled for subsequent pages. If V.bis is used, compression shall begin with the next full line passed from the application interface to the transport layer. V.bis compression may be enabled independently in each direction. If the mobile station replies with an SB command containing parameters not acceptable to the IWF, the IWF shall send a DON T command. The IWF may re-initiate negotiation at any time. Either side may terminate compression or subnegotiation at any time by sending a DON T command and shall send uncompressed data following the command. Whenever a DON T These option numbers may overlap Telnet option number assignments. There is no conflict because compression negotiation is hidden from any Telnet application that makes use of the CDMA async data service. -

281 TIA/EIA/IS-0-A. 0 command is received, the receiver shall respond with a WON T command and shall send uncompressed data following the command. When possible, the timing of these commands relative to the decompression process should be chosen to minimize loss of data. If V.bis compression is negotiated, it shall not be disabled for the duration of the call. Subnegotiation parameters shall be transmitted in the following format. If any octet following the OPTION octet and preceding the next IAC octet has value, an additional octet of value shall be inserted. The value of the PARAMETER_LEN field shall not change as the result of such insertion. The receiver shall remove all such inserted octets prior to processing the subnegotiation parameters. Field Name Size (octets) IAC SB OPTION Zero or more occurrences of the following entry: PARAMETER_ID PARAMETER_LEN PARAMETER_VAL PARAMETER_LEN The subnegotiation parameter list shall be followed immediately with: IAC SE OPTION - Option value. The application interface shall set this field to the value shown in Table.- corresponding to the type of compression selected. 0 Table.-. Compression Options Option Compression Type 0x00 V.bis compression 0x0 Modified Modified Read Coding All other values are reserved. PARAMETER_ID - Parameter Identifier. -

282 TIA/EIA/IS-0-A. 0 0 The application interface shall set this field to identify the parameter. All parameters in the subnegotiation command shall be as required for the selected compression option. PARAMETER_LEN - Parameter Length. The application interface shall set this field to the number of octets in this parameter, not including the PARAMETER_ID and PARAMETER_LEN fields. PARAMETER_VAL - Parameter Value. Indicates the desired setting for this parameter. If negotiation does not occur, the default setting shall apply. The default setting is no compression. If the OPTION field selects V.bis compression, the parameter entries may be configuration parameters, and/or of the compression scheme defined in ITU-T Recommendation V.bis. For V.bis compression, these parameters, their identifiers, and lengths, are as defined in V.bis, Annex A. For negotiation of V.bis compression, the IWF is always considered the initiator. For each direction of transmission for which V.bis compression is requested, the compression scheme defined in ITU-T Recommendation V.bis shall be applied to all data passed from the application interface to the transport layer (excluding option negotiation commands), and the corresponding decompression scheme shall be applied to all data passed from the transport layer to the application interface. If the OPTION field selects Modified Modified Read Coding compression, no parameter entries are defined. When MMR or V.bis compression is negotiated, it shall only be used in accordance with Table.-. Table.-. Group Fax Compression Options PSTN Compression Method Modified Huffman Modified Read Modified Modified Read U m Compression Method Modified Modified Read or V.bis (no additional compression) (no additional compression) 0 If Modified Modified Read compression is negotiated, the compression scheme defined in ITU-T Recommendation T. shall be applied only to the fax image data passed from the data source to the application interface layer, and the corresponding decompression scheme shall be applied only to the fax image data passed from the application interface layer to the data destination.. Transport Layer The transport layer for CDMA analog fax services is based on the Internet transport layer protocol known as Transmission Control Protocol (TCP), described in RFC. -

283 TIA/EIA/IS-0-A The implementation shall comply with the requirements of RFC, as amended by RFC, with the following modifications: TCP should always advertise a Maximum Segment Size (MSS), which should be no smaller than octets (which is the default value). TCP should limit the transmitted segment size to no more than 0 octets. TCP should advertise a window size no smaller than twice the advertised MSS, and no larger than times the MSS. For each connection, the transport layer shall use a different source port number than the one used in the previous connection. The port numbers used shall be in the range from 0x000 (decimal 0) to 0xffff (decimal ), inclusive. The mobile station s port number may be initialized to an arbitrary value in this range on power-up. The IP maximum segment lifetime (Time To Live) shall be set to 0xfe (decimal ) if it is not configurable. When provision is made for configuration, the initial value should be the number currently in effect as published in Internet Assigned Numbers. Mobile stations shall handle TCP connection failures using the following procedure, unless disabled by the application interface: (a) During initial connection synchronization, the number of retransmission attempts (R) shall be retransmissions, after which the connection should be closed. (b) After the connection has been established, the default value of R shall be either 00 seconds or 0 retransmissions, after which the connection may be closed. The manufacturer shall provide a means for the application interface to disable this procedure. If this procedure is disabled, there shall be no maximum number of retransmission attempts during synchronization, and an established TCP connection shall remain open until explicitly closed by the mobile station or the IWF. The application interface shall be able to set the value of R. R may be measured in time units or as a count of retransmissions. IWFs shall follow either the procedure of... of RFC, or the procedure above. This limit is intended to prevent excessive segment error rates under conditions where the RLP frame error rate is high. The TCP MSS option provides a means for restricting the segment size to a smaller value if required by an implementation. The most recently published value is, per RFC 00. It is recommended that the application keep the connection open, and wait for notification of an improvement in connectivity or link quality before attempting further retransmissions. -

284 TIA/EIA/IS-0-A Network Layer.. General Requirements The network layer for CDMA analog fax services is based on the Internet network layer protocol known as the Internet Protocol (IP), as described in RFC. The network layer shall also include the Internet Control Message Protocol (ICMP), as described in RFC. The implementation shall comply with the requirements of RFC as amended by RFC, with the following modifications: The mobile station network layer is not required to support the subnet addressing modes described in RFC 0. The IWF network layer should support subnet addressing as described in RFC 0 and RFC. The mobile station network layer may assume that it is locally connected to the IWF. Mobile stations shall not perform Dead Gateway Detection (see... of RFC ) nor New Gateway Selection (see... of RFC ) in the network layer. The Address Mask Request and Reply are obsolete, and should not be sent. The mobile station is not required to support the Internet Group Management Protocol (IGMP) as described in RFC. The network layer shall not fragment IP datagrams for transmission on the U m interface. If fragmented datagrams that are received from a network cannot be transmitted on the U m interface after reassembly, they shall be discarded as specified in RFC. The mobile station shall support the End of Option list IP option and the No Operation IP option (see RFC ). The interface between the network layer and the transport layer shall comply with the requirements of. of RFC... Assignment of Network Address The IWF assigns the mobile station a temporary IP address upon call establishment. This IP address shall be valid and should be uniquely assigned to the mobile station for the duration of the call. The IWF transfers the temporary IP address to the mobile station using IPCP (see..). The IP address should have a valid format as if it were assigned by IANA. However, for async data and fax services, IP addresses need not be requested from IANA if the Internet is not used as part of the intersystem network. -

285 TIA/EIA/IS-0-A Data Link Layer.. Sub-Network Dependent Convergence Function The Sub-Network Dependent Convergence Function (SNDCF) performs header compression on the headers of the transport and network layers. This function is negotiated using the PPP Internet Protocol Control Protocol (see..). Mobile stations shall support Van Jacobson TCP/IP header compression, as described in RFC, Compressing TCP/IP Headers for Low-Speed Serial Links. A minimum of compression slot shall be negotiated. The IWF shall support TCP/IP header compression compatible with that required for mobile stations. Negotiation of the parameters of header compression shall be carried out using IPCP, as specified in... The SNDCF sublayer shall accept network layer datagrams from the network layer, perform header compression as required, and pass the datagram to the PPP layer, indicating the appropriate PPP protocol identifier. The SNDCF sublayer shall receive network layer datagrams with compressed or uncompressed headers from the PPP layer, decompress the datagram header as necessary, and pass the datagram to the network layer... PPP Layer The data link layer uses PPP, as described in RFC, The Point-to-Point Protocol (PPP), and RFC, PPP in HDLC Framing, for datagram encapsulation and framing, respectively. The PPP Link Control Protocol (LCP) is used for initial link establishment, and to negotiate optional link capabilities. The data link layer uses The PPP Internet Protocol Control Protocol (IPCP), as described in RFC, to negotiate IP addresses and TCP/IP header compression. The PPP layer shall accept header compressed network layer datagrams from the SNDCF, and shall encapsulate them in the PPP Information field. The packet shall be framed using the octet-synchronous framing protocol defined in RFC, except that there shall be no inter-frame fill (see.. of RFC ): No flag octets shall be sent between a flag octet that ends one PPP frame and the flag octet that begins the subsequent PPP frame. The framed PPP packets shall be passed to the RLP layer for transmission. The data link layer shall accept received octets from the RLP layer, and re-assemble the original PPP packets. The PPP process shall discard any PPP packet for which the received Frame Check Sequence (FCS), specified in. of RFC, is not equal to the computed value... IPCP The IPCP sublayer shall support negotiation of the IP-address (type = ) and IP- Compression-Protocol (type = ) parameters. Implementation note: the code provided in RFC will not work with less than compression slots. Also, if the mobile station is to support additional data services, it should allocate additional slots. A minimum of compression slots is recommended for such mobile stations. -

286 TIA/EIA/IS-0-A. 0 0 IPCP shall negotiate a temporary IP address for the mobile station whenever a transport layer connection is actively opened. Mobile stations shall maintain the temporary IP address only while a transport layer connection is open or is being opened, and shall discard the temporary IP address when the transport layer connection is closed... Link Control Protocol If the protocol identifier is 0xc0, the PPP layer shall process the packet according to the PPP Link Control Protocol (LCP). If the protocol identifier is 0x0, the IPCP sublayer shall process the packet. For other supported protocol identifiers, the PPP layer shall remove the PPP encapsulation and shall pass the datagram and protocol identifier to the SNDCF. For unsupported protocol identifiers, the LCP Protocol-Reject shall be passed to the RLP layer for transmission. The mobile station shall support the PPP LCP Configure-Request, Configure-Ack, Configure-Nak, Configure-Reject, Terminate-Request, Terminate-Ack, Code-Reject, and Protocol-Reject. Other LCP packet types may also be supported. The PPP LCP shall negotiate the following configuration options: Async control character map. The mobile station shall not require any mapping of control characters. The IWF may negotiate mapping of control characters. Protocol field compression (applied when the protocol number is less than 0xff). Address and control field compression (applied when the protocol number is not 0xc0). The mobile station may support other configuration options (such as maximum receive unit, authentication protocol, link quality protocol, or magic number). When an option is received which is not supported, the Configure-Reject shall be sent as an indication to the peer. The protocol identifiers required by this standard are 0x00, 0x00d, 0x00f, 0xc0, and 0x0. -0

287 TIA/EIA/IS-0-A. 0 0 REQUIREMENTS FOR THE RADIO INTERFACE The mobile station and the BS/MSC shall support the physical layer, multiplex sublayer, radio link management, and call control as defined in TSB. The mobile station and the BS/MSC shall not use quarter-rate frames to carry Service Option 0 or data when Multiplex Option is negotiated.. Service Option Number The mobile station and the BS/MSC shall use Service Option 0 when Multiplex Option is the desired default multiplex option. When Multiplex Option is desired as the default multiplex option, the mobile station and the BS/MSC shall use Service Option. Mobile stations supporting Service Option shall also support Service Option 0.. Multiplex Option Interface Service Option 0 shall support an interface with Multiplex Option and may support an interface with Multiplex Option. RLP frames for Service Option 0 shall only be transported as primary traffic. Service Option shall support an interface with Multiplex Option and may support an interface with Multiplex Option. RLP frames for Service Options shall only be transported as primary traffic.. Procedures Using Service Negotiation.. Mobile Station Requirements The mobile station shall perform service negotiation compatible with the procedures described in TSB or J-STD-00, and the negotiated service configuration shall include only valid attributes for the negotiated service option as specified in Tables..- and..-. Service option negotiation procedures are not supported for Service Options 0 and. The mobile station shall not accept a service configuration whose attributes are inconsistent with the valid service configuration attribute table for the service option. The default service configuration for the analog fax service option shall be as shown in the valid service configuration attribute table for the service option. 0 -

288 TIA/EIA/IS-0-A. Table..-. Valid Service Configuration Attributes for Service Option 0 Service Configuration Attribute Valid Selections Forward Multiplex Option Multiplex Option or Reverse Multiplex Option Multiplex Option or Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type Rate Set with full rate, half rate and eighth rate frames enabled. Rate Set with all rates enabled. Rate Set with full rate, half rate and eighth rate frames enabled. Rate Set with all rates enabled. Primary Traffic Primary Traffic Table..-. Valid Service Configuration Attributes for Service Option Service Configuration Attribute Valid Selections Forward Multiplex Option Multiplex Option or Reverse Multiplex Option Multiplex Option or Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type Rate Set with full rate, half rate and eighth rate frames enabled. Rate Set with all rates enabled. Rate Set with full rate, half rate and eighth rate rates frames enabled. Rate Set with all rates enabled. Primary Traffic Primary Traffic 0 If the mobile station accepts a service configuration, as specified in a Service Connect Message, that includes a service option connection using Service Options 0 or, the mobile station shall perform the following: If the mobile station is in the Conversation Substate, and the service option connection is not part of the previous service configuration the mobile station shall initialize and connect the service option at the action time associated with the Service Connect Message. The mobile station shall complete the initialization within 00 ms of starting the connection. If the mobile station is not in the Conversation Substate, the mobile station shall initialize and connect the service option immediately upon entering the -

289 TIA/EIA/IS-0-A. 0 0 Conversation Substate and completing any further service negotiation. The mobile station shall complete the connection of the service option within 00 ms of starting the connection. Commencing at the time when the service option is connected and continuing for as long as the service configuration includes the service option connection, the service option shall generate and transfer RLP frame data to the multiplex sublayer. The service option shall also transfer and process RLP frame data received from the multiplex sublayer. When the transmitting side of the service option is connected, the service option shall generate and transfer RLP frame data to the multiplex sublayer. When the receiving side is connected, the service option shall transfer and process RLP frame data from the multiplex sublayer. See... of TSB for the actions to be taken when the transmitting side of a service option is not connected... BS/MSC Requirements If the BS/MSC establishes a service configuration, as specified in a Service Connect Message, that includes a service option connection using Service Options 0 or, the BS/MSC shall connect the service option no later than the action time associated with the Service Connect Message. Commencing at the time when the service option is connected and continuing for as long as the service configuration includes the service option connection, the service option shall process received RLP data frames and generate and supply RLP data frames for transmission in accordance with this standard. When the transmitting side of the service option is connected, the service option shall generate and transfer RLP frame data to the multiplex sublayer. When the receiving side is connected, the service option shall transfer and process RLP frame data from the multiplex sublayer. See... of TSB for the actions to be taken when the transmitting side of a service option is not connected. -

290

291 TIA/EIA/IS-0-A REQUIREMENTS FOR U M INTERFACE CALL PROCESSING. Connection Establishment.. Mobile Origination The mobile station shall initiate an analog fax connection by the following procedure: When the TE goes off hook on the RJ- interface and requests initiation of an analog fax call, the MT shall issue an active OPEN call to the transport layer. The OPEN call shall specify the modem server port number (0) as destination port, with the source and destination IP addresses unspecified. The IP addresses shall be provided to the Network Layer after completion of IPCP configuration. Transport layer data shall not be sent on the U m interface prior to completion of IPCP configuration. The mobile station shall perform the Mobile Station Origination Operation consistent with... of TIA/EIA/IS--A requesting the appropriate analog fax service option number. The mobile station shall place the dial string in the Origination Message. The mobile station shall include as many characters of the dial string as possible without exceeding the message capsule size. The IWF should assign an IP address for the mobile station and issue a passive OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the modem server port number (0) as the local port, with the IWF s IP address as the local address. Subsequent mobile station and BS/MSC call state transitions shall follow the requirements of TIA/EIA/IS--A and TSB. When the mobile station and BS/MSC enter the Conversation Substate they may perform service negotiation (see... of TSB) to establish a service configuration including the requested data service option. Following connection of the requested service option, the mobile station, the BS/MSC and the IWF shall perform the actions specified in... When the analog fax service option becomes connected while in the Conversation Substate, the mobile station and the IWF shall perform the following actions: The mobile station application interface shall send the dial command (ATD) including the dial string preceded by the configuration command (AT+CFG). Following reception of the ATD command, the IWF shall send CNG tone to the PSTN fax machine. The IWF shall send the Max Rate Message to the mobile station after processing the ATD command. If the IWF detects CED tone from the PSTN fax machine, the IWF shall send a Start CED Message to the mobile station. If the mobile station is implemented as a MT/TE pair, the MT shall send CED tone to the TE prior to sending the first V. message to the TE. The mobile station and the IWF shall follow the Mobile Transmitting Fax procedures (see. and.). -

292 TIA/EIA/IS-0-A Mobile Termination When a call is to be terminated to a mobile station directory number, the BS/MSC should determine the mobile station ID of the associated mobile station, and send a General Page Message to that mobile station. The General Page Message should include the appropriate Service Option number. 0 Following connection of the requested service option, the mobile station the BS/MSC and the IWF shall perform the actions specified in... For analog fax calls, the IWF should assign an IP address for the mobile station and issue an active OPEN call to the transport layer. The OPEN call shall specify the modem client port number () as destination, with the IWF's IP address as the source address and the mobile station s assigned IP address as the destination address. The mobile station shall always respond to a General Page Message specifying an analog fax service option. Mobile stations may also be configurable to accept only analog fax service options. If so configured, a mobile station may respond to a General Page Message by including a request for these service options. After the mobile station enters the Waiting for Mobile Station Answer Substate the mobile station shall send a Connect Order after detecting an off-hook indication on the RJ- loop. The mobile station shall then enter the Conversation Substate. After the mobile station enters the Conversation Substate, the mobile station shall issue a passive OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the modem client port number () without a local network (IP) address. When the analog fax service option becomes connected while in the Conversation Substate, the mobile station and the IWF shall perform the following actions: The mobile station application interface shall send the answer command (ATA) preceded by the configuration command (AT+CFG). The IWF shall send the Max Rate Message to the mobile station after processing the ATA command. If the mobile station is implemented as an MT/TE pair: 0 The MT shall immediately send CNG tone to the TE upon entering the Waiting for Mobile Station Answer Substate. If the MT detects CED tone from the TE, the MT shall send a Start CED Message to the IWF. The IWF shall send CED tone to the PSTN fax machine prior to sending the first V. message to the PSTN fax machine. 0 Methods for determining the service option number for mobile-terminated analog fax calls are outside the scope of this standard. Approaches include a distinct directory number for analog fax service, two-stage dialing, and service option switching. -

293 TIA/EIA/IS-0-A. 0 0 The mobile station and the IWF shall follow the Mobile Receiving Fax procedures (see. and.)... Service Option Change to Analog Fax Service If the mobile station and BS/MSC are in the Conversation Substate with a connected service option other than analog fax, the mobile station or BS/MSC may initiate service negotiation procedures consistent with... of TSB to connect an analog fax service option. The BS/MSC should open an L-Interface virtual circuit to the IWF prior to entering the Conversation Substate with a connected analog fax service option. Since the PSTN path for the call in progress has been previously established, the BS/MSC should establish the L- Interface virtual circuit to the IWF as a mobile terminated call. If the BS/MSC initiated service negotiation to connect the analog fax service option, it should indicate the fax calling station and any requirement for T.0 Phase A signaling. The IWF should assign an IP address for the mobile station. The IWF shall perform the following actions: If the intial call was mobile terminated, the IWF shall issue an active OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the modem client port number () as the destination, with the IWF's IP address as the source address and the mobile station s assigned IP address as the destination address. If the inital call was mobile originated, the IWF shall issue a passive OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the client server port number (0) as the local port, with the IWF s IP address as the source address. After processing the AT+CFG and AT+CVF or AT+CVFQ? commands, the IWF shall send the Max Rate Message to the mobile station. If the IWF determines that T.0 Phase A signaling is required, the IWF shall perform the following actions: 0 If the PSTN fax machine is the fax calling station, the IWF shall send CED tone to the PSTN fax machine prior to sending the first V. message to the PSTN fax machine. If the mobile station is the fax calling station, the IWF shall immediately begin sending CNG tone to the PSTN fax machine. If the IWF detects CED tone from the PSTN fax machine, the IWF should send a Start CED Message to the mobile station. If the PSTN fax machine is the fax calling station, the IWF shall follow the Mobile Receiving Fax procedures (see.). If the mobile station is the fax calling station, the IWF shall follow the Mobile Transmitting Fax procedures (see.). -

294 TIA/EIA/IS-0-A When the analog fax service option becomes connected while in the Conversation Substate, following service negotiation, the mobile station shall perform the following actions: The mobile station shall perform the actions specified in... If the initial call was mobile terminated, the mobile station application interface shall issue a passive OPEN call with the foreign network address and port number unspecified to the transport layer. The OPEN call shall specify the modem client port number () without a local network (IP) address. If the initial call was mobile originated, the mobile station application interface shall issue an active OPEN call to the transport layer. The OPEN call shall specify the modem server port number (0) as destination port, with the source and the destination IP addresses unspecified. If service negotiation was initiated by the BS/MSC to connect the analog fax service option, the mobile station shall send the AT+CVFQ? command to query the IWF for determination of the fax calling station and any requirements for T.0 Phase A signaling. The AT+CVFQ? command shall be preceded by the configuration command (AT+CFG). If service negotiation was initiated by the mobile station to connect the analog fax service option, the mobile station application interface shall send the AT+CVF command indicating the fax calling station and any requirement for T.0 Phase A signaling preceded by the configuration command (AT+CFG). If the PSTN fax machine is the fax calling station, the mobile station is implemented as a MT/TE pair, and the MT determines that T.0 Phase A signaling is required, the MT shall immediately begin sending CNG tone to the TE. If the MT detects CED tone from the TE, the MT should send a Start CED Message to the IWF. The mobile station (MT0 or MT/TE) shall follow the Mobile Receiving Fax procedures (see.). If the mobile station is the fax calling station implemented as a MT/TE pair, and the MT determines that T.0 phase A signaling is required, the MT shall send CED tone to the TE prior to sending the first V. message to the TE. The mobile station (MT0 or MT/TE) shall follow the Mobile Transmitting Fax procedures (see.)... Conversation Substate When either the mobile station or the BS/MSC enters the Conversation Substate with an analog fax service option connected, it shall begin RLP initialization/reset as described in.. of IS-0.. The BS/MSC should also open an L-Interface virtual circuit to the IWF prior to the completion of RLP initialization. When the L-Interface virtual circuit has been opened, the IWF relay layer should signal this event to the PPP layer. The PPP layer and IPCP sublayer in the IWF shall then carry out self-configuration, as described in.. and... The IWF shall send an IPCP Configure-Request with an IP-Compression-Protocol parameter set consistent with.. and with the IP-address parameter set to the IP address associated with the assigned IWF. The mobile station shall store the IWF's IP -

295 TIA/EIA/IS-0-A address and shall place the IWF's IP address in the destination address field of all IP datagrams sent while the transport layer remains connected. If the mobile station s IPCP Configure-Request contains an IP address of all zeros, the IWF shall select an IP address to be used by the mobile station and shall send a Configure-Nak with the IP-address parameter set to the IP address selected. The IWF shall select an IP address for each mobile station using analog fax service options conforming with the requirements of... The mobile station s IPCP sublayer shall store the assigned address and pass it to the network layer for use as a source address in all IP datagrams sent to the IWF while the transport layer connection remains open. The remaining exchange of IPCP configuration related messages shall be in accordance with RFC. When the transport layer enters the ESTABLISHED state, the transport layer may begin sending and receiving data to/from the peer application interface... Traffic Channel Handoff Soft handoff (see... of TIA/EIA/IS--A) or a CDMA-to-CDMA hard handoff (see... of TIA/EIA/IS--A) entailing only a change in the frame offset field shall not affect the state of any of the protocols for analog fax. Following a CDMA-to-CDMA hard handoff (see... of TIA/EIA/IS--A) involving transitions between disjoint sets of BS/MSCs or a frequency change, the RLP layer shall be reset and immediately re-established. This is necessary to ensure proper re-establishment of RLP after an intersystem handoff, which is not distinguishable from other hard handoffs under TIA/EIA/IS--A. Data lost during the reset of RLP will be retransmitted by the transport layer. CDMA-to-analog handoffs are not supported for Service Options 0 and. The mobile station and the IWF shall close the transport layer connection if the mobile station moves outside of CDMA coverage (see..).. Connection Release The analog fax service is considered connected when the transport layer is in the ESTABLISHED state. Each of the following conditions shall cause the transport layer connection to be closed by means of the CLOSE call to the transport layer: The IWF detects that the PSTN connection has been lost or that the PSTN fax machine has released the connection. The MT detects that the RJ- connection has been lost or that the TE has released the connection. No messages have been exchanged over the U m interface for more than T. The mobile station moves away from CDMA coverage. If the IWF detects a transport layer failure, as specified in., the IWF shall close the transport layer by means of an ABORT call. If the IWF closes the transport layer in this manner, the IWF should release the L-Interface virtual circuit. -

296 TIA/EIA/IS-0-A. 0 0 If the IWF closes the L-Interface virtual circuit, the BS/MSC should release the traffic channel to the Mobile Station, and should release the PSTN call. The BS/MSC should close the L-Interface virtual circuit, and release the PSTN call when any of the following occur: The BS/MSC receives a Release Order with a power-down indication. The BS/MSC cannot support the requested service option. The mobile station releases the traffic channel. A TIA/EIA/IS--A Lock Order is sent to the mobile station. The mobile station shall close the transport layer by means of an ABORT call to the transport layer if any of the following occur: The mobile station powers down. The mobile station receives a TIA/EIA/IS--A Release Order indicating that the requested service option is rejected. A TIA/EIA/IS--A Lock Order is received by the mobile station. When the transport layer is to be closed via a CLOSE call to the transport layer and a traffic channel is active, the mobile station or BS/MSC shall perform the following: If the connection is to be closed because the mobile station is powering down, the mobile station may send a Release Order with power-down indication and immediately power down. In all other cases, the transport layer initiating the close shall close the connection in accordance with the requirements of RFC.. Authentication Authentication of mobile station initiated analog fax calls shall be conducted according to the procedure described in.. of TIA/EIA/IS--A. For mobile-originated data calls, the BS/MSC should complete an authentication Unique Challenge immediately after assigning the traffic channel, and before connecting the analog fax service option. -

297 TIA/EIA/IS-0-A. 0 0 MOBILE PROCEDURES In all the states of this section, the following procedures shall take precedence over the specific procedures in the current state: The MT shall continuously monitor both the TE and the U m interface for messages. If there are no messages exchanged over the U m interface for more than T, the MT shall close the transport layer and direct the analog interface to release the call. The MT shall use the format specified in section for messages exchanged over the U m interface. If the MT receives an on-hook signal from the TE, the MT shall close the transport layer. If the MT detects that the transport layer has been closed, the MT shall signal the analog interface to release the call. If the MT detects V. preamble from the TE, the MT shall continuously monitor the analog interface and not send any response to the TE until the V. carrier has dropped. If the MT receives a DCN from the TE, the MT shall send the DCN to the IWF and shall direct the analog interface to release the call. If the MT receives a DCN over the U m interface, the MT shall send the DCN to the TE and wait for the TE to go on hook. If the MT does not receive an on-hook signal within T, the MT shall close the transport layer and direct the analog interface to release the call. If the MT receives a CRP from the TE, the MT shall wait for a period of T and then resend the previous message to the TE. The MT shall not send CRP over the U m interface. If the MT sends an NSF, CSI, DIS, NSC, CIG, DTC, TSI, DCS-TCF, EOP, MPS, EOM, or PRI-XXX message to the TE, the MT shall process the response from the TE as follows: 0 If no response is received within T 0, the MT shall repeat the previous message to the TE in its entirety (i.e. optional frames included) and remain in the same state. If the response is invalid (e.g. it fails the FCS or contains an incomplete frame), the MT shall wait for a period of T, repeat the previous message to the TE in its entirety (i.e. optional frames included), and remain in the same state. -

298 TIA/EIA/IS-0-A. If the response is valid, the MT shall follow the procedures specified in the current state. 0 0 Whenever the MT sends a message to the TE, the MT shall avoid a message collision on the analog interface. In all the states of this section, the following procedures shall apply unless specified otherwise in the current state: If the MT receives a non-final frame message as defined in.. of T.0 over the U m interface, the MT shall store the message. If the MT receives a final frame message as defined in.. of T.0 over the U m interface and the MT is currently not transmitting preamble as a result of receiving a previous Preamble Message (see..), the MT shall send V. preamble to the TE for a period of T. If the MT receives a Preamble Message (see..) over the U m interface, the MT shall immediately send V. preamble to the TE for a period of at least T. The MT shall continue to send preamble until it has received a final frame message over the U m interface. If the MT receives a Data Message (see..) over the U m interface, the MT shall not transmit V. preamble to the TE. If the MT receives a duplicate message from the TE, the message shall be discarded. If the duplicate message is received after the MT has sent a response to the original message, the MT shall resend the previous response to the TE. If the MT receives a message from either the TE or the U m interface that is not expected to be received in the current state, the MT shall discard the message and remain in the current state. If the MT modifies a message with an FCS, the MT shall recompute the FCS. To avoid message collisions, the MT shall use the collision timer, T (see ). A duplicate message is a message that is transmitted by a fax machine more than once in anticipation of a response from the remote fax machine. According to T.0, fax machines will repeat some messages if an appropriate response is not received within a specified amount of time. For example, in response to a DCS from the TE, the MT sends a CFR response. If the MT receives a duplicate DCS message, the MT shall resend the CFR response. -

299 TIA/EIA/IS-0-A.. Mobile Receiving Fax Wait for Local DIS Substate DIS MCF, RTP, or RTN Wait for Remote DCS Substate DCS FTT Wait for Local CFR/FTT Substate CFR RTP or RTN MCF Image Transfer State End of image MPS Post Image Transfer State EOM EOP MPS Substate EOP Substate EOM Substate RTN RTP or MCF End call NOTE: not all transitions and states are shown Figure.-. MT RX Fax Layer States in a Mobile Receiving Fax Call.. Mobile Connecting State... Wait for Local DIS Substate The MT shall process the messages from the TE as follows: If the message is an NSF or NSC, the MT shall examine the capabilities advertised in the message. If the MT cannot support any of the options in the message, the MT shall either discard the message or modify the contents to inhibit such -

300 TIA/EIA/IS-0-A options. If not discarded, the MT shall store this message. The MT shall remain in this substate. If the message is a CSI, DIS, CIG, or DTC, the MT shall store the message and remain in this substate. If any of the above messages is a final frame message and all the stored messages were received correctly, the MT shall forward all the stored messages to the IWF in the order that they were received from the TE and enter the Wait For Remote DCS Substate of the Mobile Connecting State.... Wait for Remote DCS Substate The MT shall process messages received over the U m interface as follows: If the message is a TSI, CIG, or CSI, the MT shall store the message and remain in this substate. If the message is a DCS, the MT shall enter the Wait for Local CFR/FTT Substate of the Mobile Connecting State. If the message is an NSC or NSF, the MT shall examine the capabilities advertised in the message. If the MT cannot support any of the options in the message, the MT shall either discard the message or modify the contents to inhibit such options. If not discarded, the MT shall store the message. The MT shall remain in this substate. If the message is a DTC or DIS, the MT shall modify the bits of the message in accordance with section 0. The MT shall then send NSC or NSF (if any stored), CIG or CSI (if any stored), and DTC or DIS to the TE in the order the messages were received from the IWF. Upon receiving a response from the TE, the MT shall enter the Wait For Local DCS Substate of the Mobile Connecting State under the Mobile Procedures of a Mobile Transmitting Fax Call (see...). If the message is an NSS, the procedures to be followed are left up to the MT manufacturer.... Wait for Local CFR/FTT Substate If this substate is entered from the Wait for Remote DCS Substate, the MT shall perform the following procedures on the DCS received from the IWF: Set the rate bits,,, and to 000 if the rate bits,,, and of the DIS/DTC advertised by the TE were 000 (i.e. the TE is only capable of V. modulation). Set the MSLT bits,, and in accordance with Table...-. Store a copy of the modified DCS. Send the stored TSI (if any) and the modified DCS to the TE. -

301 TIA/EIA/IS-0-A. Table...-. MSLT Resetting in the DCS MSLT bits advertised by the TE New MSLT bits if DCS bit = 0 New MSLT bits if DCS bit = If this substate is entered from either the MPS Substate or the EOP Substate of the Post Image Transfer State, the MT shall send the last stored TSI (if any) and the last stored DCS to the TE. After sending a DCS to the TE, the MT shall wait for T and then generate and send TCF to the TE at the modulation rate specified in the DCS. The MT shall then process messages from the TE as follows: If the message is an FTT, the MT shall forward the message to the IWF. The MT shall then set the modulation rate in the DCS (bits,,, ) to the next lower rate, store a copy of the DCS, and send the stored TSI (if any) and the DCS followed by a TCF to the TE. The TCF shall be sent by the MT at the modulation rate specified in the DCS after maintaining silence for a period of T after the DCS is sent. The MT shall remain in this substate. If an FTT is received again, the MT shall repeat this process until a CFR is received, or until attempts have been made at the lowest supported modulation rate. If an FTT is received after attempts at the lowest supported modulation rate, the MT shall send DCN to the TE and the IWF. The MT shall direct the analog interface to release the call. If the message is a CFR, the MT shall enable page start timer, T, and send the CFR to the IWF. The MT shall enter the Image Transfer State... Image Transfer State The MT shall process messages from the IWF as follows: The lowest rate is determined from the DIS or DTC received from the TE. -

302 TIA/EIA/IS-0-A. The MT shall monitor for a Data Message in order to detect the incoming image data. If page start timer (T ) expires, the MT shall generate and send blank scan lines (see ITU-T T..) in T intervals to the TE until image data is received from the IWF. The MT should maintain a count of inserted blank scan lines and use this to maintain a fixed number of lines in the page. If the image data is received before page start timer expires, the MT shall send the image data to the TE The MT shall not transmit the address, control, and flag fields of the received Data Message over the RJ- interface. The MT shall transmit image data to the TE at the last modulation rate accepted by the TE. The image scan lines shall be sent at intervals that meet the TE MSLT requirement. If the MT does not have image data to send to the TE, the MT shall insert fill bits. When fill bits are inserted, the duration of each image scan line shall not exceed T. The MT shall monitor the received HDLC information for an HDLC flag which indicates the end of the image data. Upon detecting the end of image data, the MT shall drop the high rate carrier to the TE then remain silent on the RJ- interface for a period of at least T. The MT shall then enter the Post Image Transfer State. If the MT receives a DCN over the U m interface, the MT shall stop transmitting any image data to the TE and send V. preamble before forwarding the message to the TE... Post Image Transfer State The MT shall process messages from the IWF as follows: If the message is an EOP, the MT shall enter the EOP Substate. If the message is an MPS, the MT shall enter the MPS Substate. If the message is an EOM, the MT shall enter the EOM Substate. If the message is a procedure interrupt (PRI-XXX), the MT shall discard the message and send a DCN to the TE. The MT shall also send a DCN to the IWF and direct the analog interface to release the call. There is space for a fixed number of lines in a standard size page (i.e. fixed page size). The MT should extract the vertical resolution and page size parameters from the stored DCS and compute the number of lines allowed. If the receiving fax machine uses an unlimited page size (such as a thermal paper roll), it may not be necessary to delete any lines from the page. -

303 TIA/EIA/IS-0-A. 0 0 In all the substates below (...,..., and...), if the message received from the TE is a PIN or PIP, the MT shall forward the message to the IWF and remain in the same substate.... EOP Substate Upon entry to this substate, the MT shall send the EOP to the TE. The MT shall then process messages from the TE as follows: If the message is an MCF or RTP, the MT shall send the message to the IWF and wait for a period of T. The MT shall then send a DCN to the TE and direct the analog interface to release the call. If the message is an RTN, the MT shall send the message to the IWF and enter the Wait For Local CFR/FTT Substate of the Mobile Connecting State.... MPS Substate Upon entry to this substate, the MT shall send the MPS to the TE. The MT shall then process messages from the TE as follows: If the message is an MCF, the MT shall enable page start timer (T, see ), send the MCF to the IWF, and enter the Image Transfer State. If the message is an RTP or RTN, the MT shall forward the message to the IWF and enter the Wait For Local CFR/FTT Substate of the Mobile Connecting State.... EOM Substate Upon entry to this substate, the MT shall send the EOM to the TE and wait for a response. If the message from the TE is an MCF, RTP or RTN, the MT shall send the message to the IWF and enter the Wait For Local DIS Substate of the Mobile Connecting State. -

304 TIA/EIA/IS-0-A.. Mobile Transmitting Fax Wait for Remotel DIS Substate DIS MCF, RTP, or RTN Wait for Local DCS Substate DCS FTT RTN Training Substate RTP or RTN CFR Image Transfer State MCF End of image MPS Post Image Transfer State EOM EOP MPS Substate EOP Substate EOM Substate RTP or MCF Disconnect Substate NOTE: not all transitions and states are shown Figure.-. MT TX Fax Layer States in a Mobile Transmitting Fax Call.. Mobile Connecting State... Wait For Remote DIS Substate The MT shall process messages from the IWF as follows: If the message is a Start CED Message (see..), the MT shall send CED tone to the TE except when the MT enters this substate at the beginning of a call where -

305 TIA/EIA/IS-0-A CED tone was already sent during call set-up. After CED has been sent, the MT shall remain silent for T before transmitting further signals to the TE. The MT shall remain in this substate. If the message is a Control Message (see..) and it is the first Control Message since the beginning of the fax call, the MT shall send CED tone to the TE if Phase A tones are required and CED tone has not already been sent. After CED has been sent, the MT shall remain silent for T before transmitting further signals to the TE. The MT shall process the Control Message as specified below. If the message is an NSF, the MT shall examine the capabilities advertised in the message. If the MT cannot support any of the options in the message, the MT shall either discard the message or modify the contents to inhibit such options. If not discarded, the MT shall store the message. The MT shall remain in this substate. If the message is a CSI, the MT shall store the message and remain in this substate. If the message is a DIS, the MT shall modify the bits of the message in accordance with section 0, store the message, and remain in this substate. If any of the above messages is a final frame message the MT shall send all stored messages to the TE in the order that they were received from the IWF. Upon receiving a response from the TE, the MT shall enter the Wait For Local DCS Substate of the Mobile Connecting State.... Wait For Local DCS Substate If the MT enters this substate from any substate other than the Training Substate, the MT shall clear transmitter trained flag (see...) and receiver trained flag (see...). If a message from the IWF arrives at the MT when either the MT is servicing a response from the TE or collision timer has expired, the MT shall store the message. The MT shall process messages from the TE as follows: If the message is a TSI, and it is the first TSI received by the MT since receiving a DIS or DTC from the IWF, the MT shall forward this message to the IWF and remain in this substate. If the message is a TSI but not the first TSI, the MT shall discard the message and remain in this substate. If the message is a DCS, and it is the first DCS received by the MT since receiving a DIS or DTC from the IWF, the MT shall perform the following in the order specified: Store a copy of the DCS. Send the DCS to the IWF. Set receiver rate (see...) equal to the rate specified in the DCS. Clear receiver trained flag and transmitter trained flag. Set transmitter rate (see...) to the rate specified in the DCS. -

306 TIA/EIA/IS-0-A. Wait for TCF from the TE. If the training attempt is successful, the MT shall set transmitter trained flag. Enter the Training Substate of the Mobile Connecting State. If the message is a DCS, and it is not the first DCS received by the MT since receiving a DIS or DTC from the IWF, the MT shall perform the following in the order specified: 0 Set transmitter rate to the rate specified in the DCS. Wait for TCF from the TE. If the training attempt is successful, the MT shall set transmitter trained flag. Enter the Training Substate of the Mobile Connecting State. 0 If the message is an NSC, NSF, CIG, CSI, DTC, or DIS, the MT shall enter the Wait for Local DIS Substate of the Mobile Connecting State under the Mobile Procedures of a Mobile Receiving Fax Call (see...). If the message is an NSS, the procedures to be followed are left up to the MT manufacturer.... Training Substate If a message from the IWF arrives at the MT when either the MT is servicing a response from the TE or collision timer has expired, the MT shall store the message. The MT shall execute the following procedures in the order specified: The MT shall process all stored messages from the IWF as follows: If the message is a CFR, the MT shall set receiver trained flag. If the message is an FTT, the MT shall check receiver rate. If receiver rate is above the lowest possible modulation rate, the MT shall decrement receiver rate to the next lower rate. If receiver rate is at the lowest possible modulation rate, the MT shall not modify receiver rate. The MT shall compare the modulation rate of the TE with receiver rate. If any of the following conditions are met, the MT shall send an FTT to the TE and enter the Wait for Local DCS Substate of the Mobile Connecting State. 0 The TE modulation rate is greater than the PSTN fax machine modulation rate (transmitter rate > receiver rate). The TE modulation rate is greater than the rate specified in the Max Rate Message. The transmitter is not trained (Transmitter Trained Flag is not set). The lowest rate is determined from the DIS or DTC received from the IWF. The MT shall determine the modulation rate of the TE from the most recently received DCS. -0

307 TIA/EIA/IS-0-A. If none of the above conditions are met, the MT shall check receiver trained flag. If receiver trained flag is set, the MT shall send a CFR to the TE and enter the Image Transfer State. If receiver trained flag is not set and if three consecutive DCS-TCF messages from the TE are unanswered, the MT shall send an FTT to the TE and enter the Wait For Local DCS Substate of the Mobile Connecting State. If receiver trained flag is not set and if the number of unanswered DCS-TCF messages from the TE is less than three, the MT shall enter the Wait For Local DCS Substate of the Mobile Connecting State. 0.. Image Transfer State The MT shall process image data from the TE as follows: Receive image data at the rate specified in the last DCS message from the TE (transmitter rate). Send image data to the IWF in a Data Message (see..). Strip fill bits from the image data before forwarding the data to the IWF. Terminate the Data Message with an HDLC flag and enter the Post Image Transfer State upon detecting the end of image data from the TE. The end of image data shall occur when any of the following is detected by the MT: 0 RTC. Drop of high rate carrier. V. preamble (belonging to the proceeding EOP, MPS, or EOM message or their corresponding PRI versions). 0.. Post Image Transfer State Upon entry into this state, the MT shall wait for post-page messages from the TE. If the MT detects a preamble on the RJ- interface for T continuously and the MT has not sent a Preamble Message to the IWF since entering this state, the MT shall send a Preamble Message over the U m interface. Upon receiving the rest of the message from the TE, the MT shall transmit the message to the IWF. The MT shall process the message from the TE as follows: If the message is an EOP, the MT shall enter the EOP Substate. If the message is an MPS, the MT shall enter the MPS Substate. If the message is an EOM, the MT shall enter the EOM Substate. If the message is a procedure interrupt (PRI-XXX), the MT shall send the message to the IWF and remain in the Post Image Transfer State. In the following substates of the Post Image Transfer State, the MT shall monitor the TE for repeated post-page messages. If the MT receives a total of three () post-page messages from the TE, the MT shall start timer T. Upon expiration of T, the MT -

308 TIA/EIA/IS-0-A shall start sending V. preamble to the TE if a response has not been sent. The MT shall continue to send the V. preamble until it has a response to send to the TE. In the following substates of the Post Image Transfer State, if the message received from the IWF is a PIN or PIP, the MT shall send a DCN to the TE. The MT shall also send a DCN to the IWF and direct the analog interface to release the call.... EOP Substate The MT shall process messages from the IWF as follows: If the message is an MCF or RTP, the MT shall send the message to the TE and enter the Disconnect Substate. If the message is an RTN, the MT shall send the message to the TE and enter the Wait For Local DCS Substate of the Mobile Connecting State.... MPS Substate The MT shall process messages from the IWF as follows: If the message is an MCF, the MT shall send the message to the TE and enter the Image Transfer State. If the message is an RTP or RTN, the MT shall send the message to the TE and enter the Wait For Local DCS Substate of the Mobile Connecting State.... EOM Substate The MT shall wait for a message from the IWF. If the message is an MCF, RTP, or RTN, the MT shall send the message to the TE and enter the Wait for Remote DIS Substate of the Mobile Connecting State.... Disconnect Substate If the MT receives a DCN from the TE, the MT shall discard the DCN, close the transport layer, and direct the analog interface to release the call. If the MT does not receive a DCN from the TE within T, the MT shall close the transport layer and direct the analog interface to release the call... Flags... Transmitter Trained Flag This flag is set by the MT when the MT receives a valid TCF from the TE.... Receiver Trained Flag This flag is set by the MT when the MT receives a CFR from the IWF... Rates... Receiver Rate The current modulation rate being negotiated between the IWF and the PSTN fax machine.... Transmitter Rate The current modulation rate being negotiated between the MT and the TE. -

309 TIA/EIA/IS-0-A. 0 0 IWF PROCEDURES In all the states of this section, the following procedures shall take precedence over the specific procedures in the current state: The IWF shall continuously monitor both the PSTN fax machine and the U m interface for messages. If there are no messages exchanged over the U m interface for more than T, the IWF shall close the transport layer and direct the analog interface to release the call. The IWF shall use the format specified in section for messages exchanged over the U m interface. If the IWF receives an on-hook signal from the PSTN fax machine, the IWF shall close the transport layer. If the IWF detects that the transport layer has been closed, the IWF shall signal the analog interface to release the call. If the IWF detects V. preamble from the PSTN fax machine, the IWF shall continuously monitor the analog interface and not send any response to the PSTN fax machine until the V. carrier has dropped. If the IWF receives a DCN from the PSTN fax machine, the IWF shall send the DCN to the MT and shall direct the analog interface to release the call. If the IWF receives a DCN over the U m interface, the IWF shall send the DCN to the PSTN fax machine and wait for the PSTN fax machine to go on hook. If the IWF does not receive an on-hook signal within T, the IWF shall close the transport layer and direct the analog interface to release the call. If the IWF receives a CRP from the PSTN fax machine, the IWF shall wait for a period of T and then resend the previous message to the PSTN fax machine. The IWF shall not send CRP over the U m interface. If the IWF sends an NSF, CSI, DIS, NSC, CIG, DTC, TSI, DCS-TCF, EOP, MPS, EOM, or PRI-XXX message to the PSTN fax machine, the IWF shall process the response from the PSTN fax machine as follows: 0 If no response is received within T 0, the IWF shall repeat the previous message to the PSTN fax machine in its entirety (i.e. optional frames included) and remain in the same state. If the response is invalid (e.g. it fails the FCS or contains an incomplete frame), the IWF shall wait for a period of T, repeat the previous message to the PSTN fax machine in its entirety (i.e. optional frames included), and remain in the same state. -

310 TIA/EIA/IS-0-A. If the response is valid, the IWF shall follow the procedures specified in the current state Whenever the IWF sends a message to the PSTN fax machine, the IWF shall avoid a message collision on the analog interface. If the IWF is in a tandem call and it receives a message from the PSTN to which it should respond with a V. message, the IWF shall immediately begin sending V. preamble to the PSTN. The IWF shall continue to send V. preamble until it has a message to forward or the IWF determines that the call must be dropped. In all the states of this section, the following procedures shall apply unless specified otherwise in the current state: If the IWF receives a non-final frame message as defined in.. of T.0 over the U m interface, the IWF shall store the message. If the IWF receives a final frame message as defined in.. of T.0 over the U m interface and the IWF is currently not transmitting preamble as a result of receiving a previous Preamble Message (see..), the IWF shall send V. preamble to the PSTN fax machine for a period of T. If the IWF receives a Preamble Message (see..) over the U m interface, the IWF shall immediately send V. preamble to the PSTN fax machine for a period of at least T. The IWF shall continue to send preamble until it has received a final frame message over the U m interface. If the IWF receives a Data Message (see..) over the U m interface, the IWF shall not transmit V. preamble to the PSTN fax machine. If the IWF receives a duplicate message from the PSTN fax machine, the message shall be discarded. If the duplicate message is received after the IWF has sent a response to the original message, the IWF shall resend the previous response to the PSTN fax machine 0. If the IWF receives a message from either the PSTN fax machine or the U m interface that is not expected to be received in the current state, the IWF shall discard the message and remain in the current state. If the IWF modifies a message with an FCS, the IWF shall recompute the FCS. To avoid message collisions, the IWF shall use the collision timer, T (see ). A duplicate message is a message that is transmitted by a fax machine more than once in anticipation of a response from the remote fax machine. According to T.0, fax machines will repeat some messages if an appropriate response is not received within a specified amount of time. 0 For example, in response to an MPS from the PSTN fax machine, the IWF sends an MCF response. If the IWF receives a duplicate MPS message, the IWF shall resend the MCF response. -

311 TIA/EIA/IS-0-A.. Mobile Receiving Fax Wait for Remotel DIS Substate DIS MCF, RTP, or RTN Wait for Local DCS Substate DCS FTT RTN Training Substate RTP or RTN CFR Image Transfer State MCF End of image MPS Post Image Transfer State EOM EOP MPS Substate EOP Substate EOM Substate RTP or MCF Disconnect Substate NOTE: not all transitions and states are shown Figure.-. IWF TX Fax Layer States in a Mobile Receiving Fax Call.. IWF Connecting State... Wait For Remote DIS Substate The IWF shall process messages from the MT as follows: If the message is a Start CED Message (see..), the IWF shall send CED tone to the PSTN fax machine except when the IWF enters this substate at the beginning of a call where CED tone was already sent during call set-up. After CED has been -

312 TIA/EIA/IS-0-A sent, the IWF shall remain silent for T before transmitting further signals to the PSTN fax machine. The IWF shall remain in this substate. If the message is a Control Message (see..) and it is the first Control Message since the beginning of the fax call, the IWF shall send CED tone to the PSTN fax machine if Phase A tones are required and CED tone has not already been sent. After CED has been sent, the IWF shall remain silent for T before transmitting further signals to the PSTN fax machine. The IWF shall process the Control Message as specified below. If the message is an NSF, the IWF shall examine the capabilities advertised in the message. If the IWF cannot support any of the options in the message, the IWF shall either discard the message or modify the contents to inhibit such options. If not discarded, the IWF shall encapsulate this NSF message in the IWF NSF message as described in... and store this IWF NSF message. The IWF shall remain in this substate. If the message is a CSI, the IWF shall store the message and remain in this substate. If the message is a DIS, the IWF shall modify the bits of the message in accordance with section 0, store the message, and remain in this substate. If any of the above messages is a final frame message, the IWF shall send all stored messages to the PSTN fax machine in the order that they were received from the MT. If the IWF has no stored IWF NSF message to send, the IWF shall generate and send an IWF NSF message preceding the stored messages. Upon receiving a response from the PSTN fax machine, the IWF shall enter the Wait For Local DCS Substate of the IWF Connecting State.... Wait For Local DCS Substate If the IWF enters this substate from any substate other than the Training Substate, the IWF shall clear transmitter trained flag (see...) and receiver trained flag (see...). If a message from the MT arrives at the IWF when either the IWF is servicing a response from the PSTN fax machine or collision timer has expired, the IWF shall store the message. The IWF shall process messages from the PSTN fax machine as follows: If the message is a TSI, and it is the first TSI received by the IWF since receiving a DIS or DTC from the MT, the IWF shall forward this message to the MT and remain in this substate. If the message is a TSI but not the first TSI, the IWF shall discard the message and remain in this substate. The inserted IWF NSF shall not contain an Encapsulated TE Non-Standard Facilities information element (see...). -

313 TIA/EIA/IS-0-A. If the message is a DCS, and it is the first DCS received by the IWF since receiving a DIS or DTC from the MT, the IWF shall perform the following in the order specified: 0 Store a copy of the DCS. Send the DCS to the MT. Set receiver rate (see...) equal to the rate specified in the DCS. Clear receiver trained flag and transmitter trained flag. Set transmitter rate (see...) to the rate specified in the DCS. Wait for TCF from the PSTN fax machine. If the training attempt is successful, the IWF shall set transmitter trained flag. Enter the Training Substate of the IWF Connecting State. If the message is a DCS, and it is not the first DCS received by the IWF since receiving a DIS or DTC from the MT, the IWF shall perform the following in the order specified: Set transmitter rate to the rate specified in the DCS. Wait for TCF from the PSTN fax machine. If the training attempt is successful, the IWF shall set transmitter trained flag. Enter the Training Substate of the IWF Connecting State. 0 If the message is an NSC, NSF, CIG, CSI, DTC, or DIS, the IWF shall enter the Wait for Local DIS Substate of the IWF Connecting State under the IWF Procedures of a Mobile Transmitting Fax Call (see...). If the message is an NSS, the IWF shall check if the message is an IWF NSS (see...) and perform the following procedures: 0 If the message is not an IWF NSS, the procedures to be followed are left up to the IWF manufacturer. If the message is an IWF NSS, this shall indicate to the IWF that this is a tandem call. The IWF shall examine any information elements to determine and enable the IWF facilities selected by the other IWF. If the IWF receives a Non- Standard IWF Facilities Set-up information element, the procedures to be followed are left up to the IWF manufacturer. If the IWF does not receive a Non- Standard IWF Facilities Set-up information element, the IWF shall remain in this substate and shall not forward the IWF NSS message to the MT.... Training Substate If a message from the MT arrives at the IWF when either the IWF is servicing a response from the PSTN fax machine or collision timer has expired, the IWF shall store the message. The IWF shall execute the following procedures in the order specified: The IWF shall process all stored messages from the MT as follows: -

314 TIA/EIA/IS-0-A. If the message is a CFR, the IWF shall set receiver trained flag. If the message is an FTT, the IWF shall check receiver rate. If receiver rate is above the lowest possible modulation rate, the IWF shall decrement receiver rate to the next lower rate. If receiver rate is at the lowest possible modulation rate, the IWF shall not modify receiver rate. The IWF shall compare the modulation rate of the PSTN fax machine with receiver rate. If any of the following conditions are met, the IWF shall send an FTT to the PSTN fax machine and enter the Wait for Local DCS Substate of the IWF Connecting State. 0 The PSTN fax machine modulation rate is greater than the TE modulation rate (transmitter rate > receiver rate). The PSTN fax machine modulation rate is greater than the rate specified in the Max Rate Message. The transmitter is not trained (Transmitter Trained Flag is not set). If none of the above conditions are met, the IWF shall check receiver trained flag. 0 If receiver trained flag is set, the IWF shall send a CFR to the PSTN fax machine and enter the Image Transfer State. If receiver trained flag is not set and if three consecutive DCS-TCF messages from the PSTN fax machine are unanswered, the IWF shall send an FTT to the PSTN fax machine and enter the Wait For Local DCS Substate of the IWF Connecting State. If receiver trained flag is not set and if the number of unanswered DCS-TCF messages from the PSTN fax machine is less than three, the IWF shall enter the Wait For Local DCS Substate of the IWF Connecting State. 0.. Image Transfer State The IWF shall process image data from the PSTN fax machine as follows: Receive image data at the rate specified in the last DCS message from the PSTN fax machine (transmitter rate). The IWF shall be able to receive this image data with no fill bits, i.e., image data sent with an MSLT requirement of 0 ms. Send image data to the MT in a Data Message (see..). Strip fill bits from the image data before forwarding the data to the MT. The lowest rate is determined from the DIS or DTC received from the MT. The IWF shall determine the modulation rate of the PSTN fax machine from the most recently received DCS. -

315 TIA/EIA/IS-0-A. Terminate the Data Message with an HDLC flag and enter the Post Image Transfer State upon detecting the end of image data from the PSTN fax machine. The end of image data shall occur when any of the following is detected by the IWF: RTC. Drop of high rate carrier. V. preamble (belonging to the proceeding EOP, MPS, or EOM message or their corresponding PRI versions) Post Image Transfer State Upon entry into this state, the IWF shall wait for post-page messages from the PSTN fax machine. If the IWF detects V. preamble on the PSTN interface for T continuously and the IWF has not sent a Preamble Message to the MT since entering this state, the IWF shall send a Preamble Message over the U m interface. Upon receiving the rest of the message from the PSTN fax machine, the IWF shall transmit the message to the MT. The IWF shall process the message from the PSTN fax machine as follows: If the message is an EOP, the IWF shall enter the EOP Substate. If the message is an MPS, the IWF shall enter the MPS Substate. If the message is an EOM, the IWF shall enter the EOM Substate. If the message is a procedure interrupt (PRI-XXX), the IWF shall send the message to the MT and remain in the Post Image Transfer State. In the following substates of the Post Image Transfer State, the IWF shall monitor the PSTN fax machine for repeated post-page messages. If the IWF receives a total of three () postpage messages from the PSTN fax machine, the IWF shall start timer T. Upon expiration of T, the IWF shall start sending V. preamble to the PSTN fax machine if a response has not been sent. The IWF shall continue to send the V. preamble until it has a response to send to the PSTN fax machine. In the following substates of the Post Image Transfer State, if the message received from the MT is a PIN or PIP, the IWF shall send a DCN to the PSTN fax machine. The IWF shall also send a DCN to the MT and direct the analog interface to release the call.... EOP Substate The IWF shall process messages from the MT as follows: If the message is an MCF or RTP, the IWF shall send the message to the PSTN fax machine and enter the Disconnect Substate. If the message is an RTN, the IWF shall send the message to the PSTN fax machine and enter the Wait For Local DCS Substate of the IWF Connecting State.... MPS Substate The IWF shall process messages from the MT as follows: If the message is an MCF, the IWF shall send the message to the PSTN fax machine and enter the Image Transfer State. -

316 TIA/EIA/IS-0-A. 0 0 If the message is an RTP or RTN, the IWF shall send the message to the PSTN fax machine and enter the Wait For Local DCS Substate of the IWF Connecting State.... EOM Substate The IWF shall wait for a message from the MT. If the message is an MCF, RTP, or RTN, the IWF shall send the message to the PSTN fax machine and enter the Wait for Remote DIS Substate of the IWF Connecting State.... Disconnect Substate If the IWF receives a DCN from the PSTN fax machine, the IWF shall discard the DCN, close the transport layer, and direct the analog interface to release the call. If the IWF does not receive a DCN from the PSTN fax machine within T, the IWF shall close the transport layer and direct the analog interface to release the call... Flags... Transmitter Trained Flag This flag is set by the IWF when the IWF receives a valid TCF from the PSTN fax machine.... Receiver Trained Flag This flag is set by the IWF when the IWF receives a CFR from the MT... Rates... Receiver Rate The current modulation rate being negotiated between the MT and the TE.... Transmitter Rate The current modulation rate being negotiated between the IWF and the PSTN fax machine. -

317 TIA/EIA/IS-0-A.. Mobile Transmitting Fax Wait for Local DIS Substate DIS MCF, RTP, or RTN Wait for Remote DCS Substate DCS FTT Wait for Local CFR/FTT Substate CFR RTP or RTN MCF Image Transfer State End of image MPS Post Image Transfer State EOM EOP MPS Substate EOP Substate EOM Substate RTN RTP or MCF End call NOTE: not all transitions and states are shown Figure.-. IWF RX Fax Layer States in a Mobile Transmitting Fax Call.. IWF Connecting State... Wait for Local DIS Substate The IWF shall process the messages from the PSTN fax machine as follows: If the message is an NSF or NSC, the IWF shall check if the message is an IWF NSF or IWF NSC (see...) and remain in this substate after performing the following procedures: -

318 TIA/EIA/IS-0-A. 0 If the message is not an IWF NSF or IWF NSC, the IWF shall examine the capabilities advertised in the message. If the IWF cannot support any of the options in the message, the IWF shall either discard the message or modify the contents to inhibit such options. If not discarded, the IWF shall store this message. If the message is an IWF NSF or IWF NSC, this shall indicate to the IWF that this is a tandem call. If the message contains an Encapsulated Non-Standard Facilities information element, the IWF shall examine the capabilities advertised. If the IWF cannot support any of the options in the information element, the IWF shall either discard the information element or modify the contents to inhibit such options. If not discarded, the IWF shall store this information element as an NSF or NSC message. 0 0 If the message is a CSI, DIS, CIG, or DTC, the IWF shall store the message and remain in this substate. If any of the above messages is a final frame message and all the stored messages were received correctly, the IWF shall forward all the stored messages to the MT in the order that they were received from the PSTN fax machine and enter the Wait For Remote DCS Substate of the IWF Connecting State.... Wait for Remote DCS Substate The IWF shall process messages received over the U m interface as follows: If the message is a TSI, CIG, or CSI, the IWF shall store the message and remain in this substate. If the message is a DCS, the IWF shall enter the Wait for Local CFR/FTT Substate of the IWF Connecting State. If the message is an NSC or NSF, the IWF shall examine the capabilities advertised in the message. If the IWF cannot support any of the options in the message, the IWF shall either discard the message or modify the contents to inhibit such options. If not discarded, the IWF shall store the message. The IWF shall remain in this substate. If the message is a DTC or DIS, the IWF shall modify the bits of the message in accordance with section 0. The IWF shall then send NSC or NSF (if any stored), CIG or CSI (if any stored), and DTC or DIS to the PSTN fax machine in the order the messages were received from the MT. Upon receiving a response from the PSTN fax machine, the IWF shall enter the Wait For Local DCS Substate of the IWF Connecting State under the IWF Procedures of a Mobile Receiving Fax Call (see...). The IWF shall only store the Encapsulated TE Non-Standard Facilities information element for forwarding to the MT. The rest of the IWF NSF or IWF NSC message shall not be sent to the MT. -0

319 TIA/EIA/IS-0-A. 0 If the message is an NSS, the procedures to be followed are left up to the IWF manufacturer.... Wait for Local CFR/FTT Substate If this substate is entered from the Wait for Remote DCS Substate, the IWF shall perform the following procedures on the DCS received from the MT: Set the rate bits,,, and to 000 if the rate bits,,, and of the DIS/DTC advertised by the PSTN fax machine were 000 (i.e. the PSTN fax machine is only capable of V. modulation). Set the MSLT bits,, and in accordance with Table...-. Store a copy of the modified DCS. Send the stored TSI (if any) and the modified DCS to the PSTN fax machine. If the IWF is in a tandem call, the IWF shall precede these messages with the IWF NSS message. Table...-. MSLT Resetting in the DCS MSLT bits advertised by the PSTN fax machine New MSLT bits if DCS bit = 0 New MSLT bits if DCS bit = If this substate is entered from either the MPS Substate or the EOP Substate of the Post Image Transfer State, the IWF shall send the last stored TSI (if any) and the last stored DCS to the PSTN fax machine. After sending a DCS to the PSTN fax machine, the IWF shall wait for T and then generate and send TCF to the PSTN fax machine at the modulation rate specified in the DCS. The IWF shall then process messages from the PSTN fax machine as follows: If the message is an FTT, the IWF shall forward the message to the MT. The IWF shall then set the modulation rate in the DCS (bits,,, ) to the next lower rate, store a copy of the DCS, and send the stored TSI (if any) and the DCS followed by a TCF to the PSTN fax machine. The TCF shall be sent by the IWF at the modulation rate specified in the DCS after maintaining silence for a period of T -

320 TIA/EIA/IS-0-A. 0 after the DCS is sent. The IWF shall remain in this substate. If an FTT is received again, the IWF shall repeat this process until a CFR is received, or until attempts have been made at the lowest supported modulation rate. If an FTT is received after attempts at the lowest supported modulation rate, the IWF shall send DCN to the PSTN fax machine and the MT. The IWF shall direct the analog interface to release the call. If the message is a CFR, the IWF shall enable page start timer, T, and send the CFR to the MT. The IWF shall enter the Image Transfer State... Image Transfer State The IWF shall process messages from the MT as follows: The IWF shall monitor for a Data Message in order to detect the incoming image data. If page start timer (T ) expires, the IWF shall generate and send blank scan lines (see ITU-T T..) in T intervals to the PSTN fax machine until image data is received from the MT. The IWF should maintain a count of inserted blank scan lines and use this to maintain a fixed number of lines in the page. If the image data is received before page start timer expires, the IWF shall send the image data to the PSTN fax machine. 0 0 The IWF shall not transmit the address, control, and flag fields of the received Data Message over the PSTN interface. The IWF shall transmit image data to the PSTN fax machine at the last modulation rate accepted by the PSTN fax machine. If the IWF is not in a tandem call, the IWF shall transmit image scan lines to the PSTN fax machine at intervals that meet the PSTN fax machine MSLT requirement. If the IWF is in a tandem call, the IWF shall transmit these lines with an MSLT of 0 ms, i.e., the IWF shall not insert fill bits unless it has no lines to send. If the IWF does not have image data to send to the PSTN fax machine, the IWF shall insert fill bits. When fill bits are inserted, the duration of each image scan line shall not exceed T. The IWF shall monitor the received HDLC information for an HDLC flag which indicates the end of the image data. Upon detecting the end of image data, the IWF shall drop the high rate carrier to the PSTN fax machine then remain silent on the The lowest rate is determined from the DIS or DTC received from the PSTN fax machine. There is space for a fixed number of lines in a standard size page (i.e. fixed page size). The IWF should extract the vertical resolution and page size parameters from the stored DCS and compute the number of lines allowed. If the receiving fax machine uses an unlimited page size (such as a thermal paper roll), it may not be necessary to delete any lines from the page. -

321 TIA/EIA/IS-0-A PSTN interface for a period of at least T. The IWF shall then enter the Post Image Transfer State. If the IWF receives a DCN over the U m interface, the IWF shall stop transmitting any image data to the PSTN fax machine and send V. preamble before forwarding the message to the PSTN fax machine... Post Image Transfer State The IWF shall process messages from the MT as follows: If the message is an EOP, the IWF shall enter the EOP Substate. If the message is an MPS, the IWF shall enter the MPS Substate. If the message is an EOM, the IWF shall enter the EOM Substate. If the message is a procedure interrupt (PRI-XXX), the IWF shall discard the message and send a DCN to the PSTN fax machine. The IWF shall also send a DCN to the MT and direct the analog interface to release the call. In all the substates below (...,..., and...), if the message received from the PSTN fax machine is a PIN or PIP, the IWF shall forward the message to the MT and remain in the same substate.... EOP Substate Upon entry to this substate, the IWF shall send the EOP to the PSTN fax machine. The IWF shall then process messages from the PSTN fax machine as follows: If the message is an MCF or RTP, the IWF shall send the message to the MT and wait for a period of T. The IWF shall then send a DCN to the PSTN fax machine and direct the analog interface to release the call. If the message is an RTN, the IWF shall send the message to the MT and enter the Wait For Local CFR/FTT Substate of the IWF Connecting State.... MPS Substate Upon entry to this substate, the IWF shall send the MPS to the PSTN fax machine. The IWF shall then process messages from the PSTN fax machine as follows: If the message is an MCF, the IWF shall enable page start timer (T, see ), send the MCF to the MT, and enter the Image Transfer State. If the message is an RTP or RTN, the IWF shall forward the message to the MT and enter the Wait For Local CFR/FTT Substate of the IWF Connecting State.... EOM Substate Upon entry to this substate, the IWF shall send the EOM to the PSTN fax machine and wait for a response. If the message from the PSTN fax machine is an MCF, RTP or RTN, the IWF shall send the message to the MT and enter the Wait For Local DIS Substate of the IWF Connecting State. -

322

323 TIA/EIA/IS-0-A. 0 MESSAGES. Messages Over the Analog Interface These messages are exchanged between the Analog Fax Layer and the transmitting or receiving fax machine through the RJ- or PSTN interface. The format of these messages is specified in T.0. The following descriptions are provided for informational purposes only... V. Messages V. messages refer to the T.0 control messages transmitted using ITU-T V. modulation over the analog interface. These messages are formatted according to an HDLC frame structure as specified in. of T.0. A single frame is shown in Figure.-. Preamble T.0 Message Flag Flag Address Control HDLC Information Field FCS Flag 0 0 Figure.-. T.0 V. Message Format The preamble precedes all binary coded signaling whenever new transmission of information begins in any direction (see T.0..). The preamble for binary coded signaling at 00 bps is a series of HDLC flags for s ± % (see T.0...). The HDLC flag is an octet (0xe) used to denote the beginning and end of the frame. The trailing flag of one frame may be the leading flag of the following frame (see T.0..). The address field is set to 0xff in all the T.0 messages (see T.0..). The control field represented in binary is of the form '00 X000', where X=0 represents non-final frames, while X= represents final frames (see T.0..). The HDLC information field is of variable length and incorporates specific information for the control and message interchange between two facsimile machines. This field is further divided into two parts, the facsimile control field (FCF) and the facsimile information field (FIF). The values and details regarding these fields are specified in... and... of T.0. The FCS is a bit sequence number used for error detection. The FCS covers the address, control and information fields of the T.0 message (see T.0..)... Image Data This refers to the digitally scanned image sent from the transmitting fax machine to the receiver fax machine. The image is coded according to the appropriate T. image -

324 TIA/EIA/IS-0-A. 0 compression procedures and transmitted using the selected ITU-T V series modulation standard... IWF Identification and Capabilities Messages These are V. messages exchanged between IWF s across the PSTN in a tandem analog fax call.... IWF NSF and IWF NSC Messages The IWF uses the IWF NSF and IWF NSC messages to identify itself as an Analog Fax IWF. The messages also allow the IWF to advertise options that are specific to IWF fax modems. These messages are sent only to the PSTN and formatted according to Table...-. Table...-. IWF NSF and IWF NSC Message Format Field Length (octets) FLAG ADDRESS CONTROL FCF 0 FIF variable FCS FLAG FLAG - HDLC frame delimiter. This octet shall be set to 0xe. ADDRESS - Address field. This octet shall be set to 0xff. CONTROL - Control field. This octet shall be set to 0xc0. FCF - Facsimile control field. This octet shall be set to 0x0 for an NSF message and 0x for an NSC message. FIF - Facsimile information field. The octets in this field shall be formatted according to Table...-. FCS - Frame checking sequence. These two octets shall be set according to the procedures of.. of T.0. FLAG - HDLC frame delimiter. This octet shall be set to 0xe. -

325 TIA/EIA/IS-0-A. Table...-. FIF Format for the IWF NSF and IWF NSC Messages Field Length (octets) COUNTRY MANUF Followed by zero or more instances of the following information element: TYPE LENGTH INFO Variable 0 0 COUNTRY - The T.0 field which identifies the country where the manufacturer code was granted. This octet shall be set to 0xb. MANUF - The T.0 field which identifies the manufacturer of the fax equipment. These two octets shall be set to 0x00a to identify the fax equipment as an Analog Fax IWF. TYPE - The type of information element. This octet shall be set to: 0x00 - for the IWF Facilities information element. This information element identifies the standardized facilities of the IWF. 0x0 - for the Non-Standard IWF Facilities information element. This information element identifies non-standard (manufacturer specific) facilities of the IWF. 0x0 - for the Encapsulated TE Non-Standard Facilities information element. This information element represents the non-standard facilities advertised by the TE and relayed by the MT to the IWF. LENGTH - Length of the INFO field in the information element. This shall indicate the number of octets in the INFO field of the information element. INFO - Information field for the information element. When TYPE=0x00, the INFO field shall be formatted according to Table...-. The length shall indicate the number of octets prior to T.0 bit-stuffing. -

326 TIA/EIA/IS-0-A. When TYPE=0x0, the INFO field shall be formatted according to Table...-. When TYPE=0x0, the INFO field shall contain the NSF or NSC message from the MT and shall be formatted according to Table...-. Table...-. INFO Field Format for TYPE=0x00 Information Element Field Length (octets) RESERVED RESERVED - Reserved bits. This octet shall be set to 0x00. 0 Table...-. INFO Field Format for TYPE=0x0 Information Element Field Length (octets) IWF_MANUF NS_OPTIONS Variable IWF_MANUF - Identifies the manufacturer of the IWF. This octet shall be set to the manufacturer s code as described in TSB. NS_OPTIONS - Non-standard options. The format of these octets is not standardized and shall be defined according to the IWF manufacturer s protocol. Table...-. INFO Field Format for TYPE=0x0 Information Element Field Length (octets) ADDRESS CONTROL FCF 0 FIF variable FCS These fields shall be set according to the corresponding fields in the NSF or NSC message received from the MT.... IWF NSS Message The IWF uses the IWF NSS message to identify itself as an Analog Fax IWF to another IWF that has sent an IWF NSF or IWF NSC. The message also allows the IWF to select options -

327 TIA/EIA/IS-0-A. that are specific to IWF fax modems. This message is sent only to another CDMA IS-0 IWF and formatted according to table...-. Table...-. IWF NSS Message Format Field Length (octets) FLAG ADDRESS CONTROL FCF 0 0 FIF variable FCS FLAG FLAG - HDLC frame delimiter. This octet shall be set to 0xe. ADDRESS - Address field. This octet shall be set to 0xff. CONTROL - Control field. This octet shall be set to 0xc0. FCF - Facsimile control field. This octet shall be set to either 0x or 0xc as described in... and... of T.0. FIF - Facsimile information field. The octet(s) in this field shall be formatted according to Table...-. FCS - Frame checking sequence. These two octets shall be set according to the procedures of.. of T.0. FLAG - HDLC frame delimiter. This octet shall be set to 0xe. Table...-. FIF Format for the IWF NSS Message Field Length (octets) COUNTRY MANUF Followed by zero or more instances of the following information element: -

328 TIA/EIA/IS-0-A. TYPE LENGTH INFO variable 0 0 COUNTRY - The T.0 field which identifies the country where the manufacturer code was granted. This octet shall be set to 0xb. MANUF - The T.0 field which identifies the manufacturer of the fax equipment. These two octets shall be set to 0x00a to identify the fax equipment as an Analog Fax IWF. TYPE - Describes the type of information element. This octet shall be set to: 0x00 - for the IWF Digital Command Signal information element. This information element selects standardized capabilities advertised by the other IWF in the IWF Facilities information element of its IWF NSF or IWF NSC message. 0x0 - for the Non-Standard IWF Facilities Set-up information element. This information element selects nonstandard (manufacturer specific) capabilities advertised by the other IWF in the Non-Standard IWF Facilities information element of its IWF NSF or IWF NSC message. LENGTH - Length of the INFO field in the information element. This shall indicate the number of octets in the INFO field of the information element. INFO - Information field for the information element. When TYPE=0x00, the INFO field shall be formatted according to Table...-. When TYPE=0x0, the INFO field shall be formatted according to Table...-. Table...-. INFO Field Format for TYPE=0x00 Information Element Field Length (octets) 0 RESERVED RESERVED - Reserved bits. This octet shall be set to 0x00. The length shall indicate the number of octets prior to T.0 bit-stuffing. -

329 TIA/EIA/IS-0-A. Table...-. INFO Field Format for TYPE=0x0 Information Element Field Length (octets) IWF_MANUF 0 0 NS_OPTIONS variable IWF_MANUF - Identifies the manufacturer of the IWF. This octet shall be set to the manufacturer s code as described in TSB. NS_OPTIONS - Non-standard options. The format of these octets is not standardized and shall be set according to the IWF manufacturer s protocol.. Messages over the U m Interface These messages are exchanged between the Analog Fax Layers in the IWF and the MT. These messages shall be formatted as follows :.. Control Messages These messages correspond to T.0 V. messages that are received from either the PSTN fax machine or the TE. When the Analog Fax Layer receives a V. message that is to be forwarded over the U m interface, the Analog Fax Layer shall wait to receive the entire V. message, and then generate a corresponding Control Message as follows: Send one HDLC flag over the U m interface (preamble shall not be sent over the U m interface). Forward the values of the ADDRESS, CONTROL, FCF, FIF, and FCS fields of the V.message over the U m interface. Send one HDLC flag over the U m interface to indicate the end of the Control Message. The format of these messages is similar to the T.0 HDLC frame structure for V. messages. -

330 TIA/EIA/IS-0-A. Table..-. Control Message Format Field Length (octets) FLAG ADDRESS CONTROL FCF 0 0 FIF variable FCS FLAG FLAG - HDLC frame delimiter. This octet shall be set to 0xe. ADDRESS - Address field. This octet shall be set to the address field of the received V. message. CONTROL - Control field. This octet shall be set to the control field of the received V. message. FCF - Facsimile control field. This octet shall be set to the facsimile control field of the received V. message. FIF - Facsimile information field. The octet(s) in this field shall be set to the facsimile information field of the received V. message. In some states, the Analog Fax Layer may be required to modify the contents of this field before forwarding it over the U m interface. FCS - Frame checking sequence. These two octets shall be set according to the procedures of.. of T.0. FLAG - HDLC frame delimiter. This octet shall be set to 0xe... Data Message A Data Message corresponds to a single page of image data received from the transmitting fax machine. Image data for a single page is sent in one Data Message (a single HDLC frame 0 ) that is assembled and formatted at the TX Fax Layer. 0 A single HDLC frame may be carried over the Um interface in multiple packets or datagrams. -

331 TIA/EIA/IS-0-A. Table..-. Data Message Format Field Length (octets) FLAG ADDRESS CONTROL 0 0 IMAGE_DATA variable FLAG FLAG - HDLC frame delimiter. Upon detecting the start of image data from the transmitting fax machine, the TX Fax Layer shall set this octet to 0xe and send it over the U m interface. ADDRESS - Address field. The TX Fax Layer shall set this octet to 0xFF. CONTROL - Control field. The TX Fax Layer shall set this octet to 0x0 to indicate that this is a Data Message. IMAGE_DATA - Image Data Field. This field shall contain the image data received by the TX Fax Layer from the transmitting fax machine, including EOL markers and any required escape characters. The TX Fax Layer shall pad this field with 0s if this field does not end on an octet boundary at the end of image data. FLAG - HDLC frame delimiter. The TX Fax Layer shall set this octet to 0xe... Preamble Message The Preamble Message is sent over the U m interface to start V. preamble at the remote Analog Fax Layer. When the IWF receives the Preamble Message over the U m interface, the IWF shall immediately start sending V. preamble to the PSTN fax machine. Similarly, when the MT receives the Preamble Message over the U m interface, the MT shall immediately start sending V. preamble to the TE. The Preamble Message shall be formatted as specified in Table..-. -

332 TIA/EIA/IS-0-A. Table..-. Preamble Message Format Field Length (octets) FLAG ADDRESS CONTROL FCF FIF FCS 0 FLAG FLAG - HDLC frame delimiter. This octet shall be set to 0xe. ADDRESS - Address field. This octet shall be set to 0xFF. CONTROL - Control field. This octet shall be set to 0x. FCF - Facsimile control field. This octet shall be set to 0x0. FIF - Facsimile information field. This octet shall be set to 0x00. FCS - Frame checking sequence. These two octets shall be set according to the procedures of.. of T.0. FLAG - HDLC frame delimiter. This octet shall be set to 0xe... Max Rate Message The Max Rate Message is sent by the IWF to the MT after the initial OK response from the IWF (see..,..,..). The message shall be formatted as specified in Table

333 TIA/EIA/IS-0-A. Table..-. Max Rate Message Format Field Length (octets) FLAG ADDRESS CONTROL FCF FIF FCS 0 FLAG FLAG - HDLC frame delimiter. The IWF shall set this octet to 0xe. ADDRESS - Address field. The IWF shall set this octet to 0xff. CONTROL - Control field. The IWF shall set this octet to 0x. FCF - Facsimile control field. The IWF shall set this octet to 0x00. FIF - Facsimile information field. The IWF shall set the most significant bits of this field according to Table..-. The least significant bits are reserved and shall be set to zero. Table..-. FIF Values for the Max Rate Message Most significant bits of the FIF (binary) Maximum fax rate supported (bits/second) 0000 Reserved FCS - Frame checking sequence. The IWF shall set these two octets according to the procedures of.. of T.0. -

334 TIA/EIA/IS-0-A. FLAG - HDLC frame delimiter. The IWF shall set this octet to 0xe... Start CED Message The Start CED Message should be sent by the RX Fax Layer to the TX Fax Layer to start the generation of CED tone to the transmitting fax machine. Table..-. Start CED Message Format Field Length (octets) FLAG ADDRESS CONTROL FCF FIF FCS FLAG 0 0 FLAG - HDLC frame delimiter. This octet shall be set to 0xe. ADDRESS - Address field. This octet shall be set to 0xff. CONTROL - Control field. This octet shall be set to 0x. FCF - Facsimile control field. This octet shall be set to 0x0. FIF - Facsimile information field. This octet shall be set to 0x00. FCS - Frame checking sequence. These two octets shall be set according to the procedures of.. of T.0. FLAG - HDLC frame delimiter. This octet shall be set to 0xe. By sending a Start CED Message, the call set-up time may be reduced. For example, this message may be sent when the RX Fax Layer detects CED tone or the preamble of the first V. message from the receiving fax machine. -

335 TIA/EIA/IS-0-A Formatting octets over the U m interface.. Bit Format of Octets... Control, Preamble, Max Rate, and Start CED Messages When formatting binary data into octets to be sent over the U m interface, the Analog Fax Layer shall follow the bit ordering specified in. of T.0 (i.e., the binary representation reads with the most significant bit on the left). For example, for a CFR message with Facsimile Control Field set to binary , the Analog Fax Layer shall send this octet to the transport layer as 0x.... Data Messages As the TX Fax Layer receives a stream of image data bits from the transmitting fax machine over its analog interface, the TX Fax Layer shall package the bits into octets starting with the most significant bit first and then proceeding to the least significant bit. For example, when the TX Fax Layer receives the following sequence of bits at the end of an image line, , the TX Fax Layer shall send the octet 0x00 followed by 0xc to the transport layer... Byte Escaping of Flags The IWF and MT shall perform byte escaping of all HDLC messages sent over the U m interface regardless of the message type (Control, Data, Preamble or Max Rate). After computing the Frame Check Sequence (FCS, if any), the IWF and MT shall examine the entire frame between the two Flag Sequence Octets and: Replace each Flag Sequence Octet, 0xe, with the sequence 0xd 0xe Replace each Control Escape Octet, 0xd, with the sequence 0xd 0xd Upon reception of an HDLC message over the U m interface and prior to FCS computation (if any), the IWF and MT shall: Remove each Control Escape Octet from the frame Exclusive-or (XOR) the octet following each removed Control Escape Octet with 0x0. The requirements described in this section are derived from RFC, Section.. -

336

337 TIA/EIA/IS-0-A. CALL FLOWS This section contains example call flows that illustrate the operation of the analog fax service under various call scenarios. The examples provided within this section illustrate one means of providing analog fax service. Alternative, standard-compliant means are also possible. PSTN and RJ- signals fax Phase A tones (CNG/CED) or V. preamble T.0 V. message (when on RJ- or PSTN) Um interface message (when between MT & BS/MSC/IWF) High rate image/training data 0 Figure -. Message and Signal Representation Used in Call Flows. Call Set-Up Calls may be setup as analog fax calls or they may be setup as voice calls and transitioned to analog fax. In addition, calls may be setup from either station, regardless of which station will be sending the fax image data or the CNG and CED tones. Section.. illustrates calls initiated as analog fax calls. Section.. illustrates calls initiated as voice calls which transition to analog fax. For completeness, the figures in section.. show examples of the voice call setup. -

338 TIA/EIA/IS-0-A... Calls Originating as Analog Fax TE MT BS/MSC PSTN PSTN Fax off hook dial tone start CNG tone ring S.O. = Analog Fax Incoming call with dialed digits (AFax DN) DTMF digits (AFax DN) ring BS/MSC/IWF start CNG tone (optional) off hook start CED tone (optional) Synch TCP/IP-PPP-RLP CNG tone (optional) AT+CFG="" 0 V. preamble NSF ATA 0 Max Rate Message off hook CNG tone (optional) CSI Start CED Message start CED tone DIS Relay CSI, DIS V. preamble CSI DIS Figure..-. Call Set-Up for a Mobile Receiving Fax Call Initiated as Analog Fax -

339 TIA/EIA/IS-0-A. TE MT BS/MSC PSTN PSTN Fax off hook dial tone DTMF digits (AFax dial prefix followed by dialed number) S.O. = Analog Fax start CNG tone (optional) BS/MSC/IWF S y nch TCP/IP-PPP-RLP CNG tone (optional) AT+CFG="" 0 ATDT<dialed number> 0 originate call to dialed number start CNG tone connect ring off hook CNG tone (optional) start CED tone Max Rate Messag e Start CED Messag e start CED tone (optional) V. preamble NSF V. preamble CSI Relay CSI, DIS CSI DIS DIS Figure..-. Call Set-Up for a Mobile Transmitting Fax Call Initiated as Analog Fax -

340 TIA/EIA/IS-0-A... Calls Originating as Voice, then Transitioning to Analog Fax TE MT BS/MSC PSTN PSTN Fax off hook dial tone ring S.O. = Voice Incoming call with dialed digits DTMF digits (Voice DN) off hook Connect Order off hook start CNG tone (optional) CNG tone (through vocoders) start CED tone (through vocoders) V. preamble NSF CSI Service Negotiation to S.O. = Analog Fax DIS BS/MSC/IWF S y nch TCP/IP-PPP-RLP AT+CFG="" 0 V. preamble NSF CSI DIS AT+CVF= 0,0 0 Max Rate Message Relay CSI, DIS V. preamble CSI DIS Figure..-. Call Set-Up as Voice Transitioning to Mobile Receiving Fax. Voice Call Shown as Mobile-Terminated and Fax Call Detected Using V. Preamble Detection. -

341 TIA/EIA/IS-0-A. TE MT BS/MSC PSTN PSTN Fax off hook dial tone DTMF digits (dialed number) S.O. = Voice originate call to dialed number ring connect off hook start CNG tone (through vocoders) start CED tone (through vocoders) V. preamble NSF CSI Service Negotiation to S.O. = Analog Fax DIS BS/MSC/IWF S y nch TCP/IP-PPP-RLP AT+CFG="" 0 V. preamble NSF CSI DIS AT+CVF= 0,0 0 Max Rate Message Relay CSI, DIS V. preamble CSI DIS Figure..-. Call Set-Up as Voice Transitioning to Mobile Receiving Fax. Voice Call Shown as Mobile-Originated and Fax Call Detected Using V. Preamble Detection. -

342 TIA/EIA/IS-0-A. TE MT BS/MSC PSTN PSTN Fax off hook dial tone DTMF digits (dialed number) S.O. = Voice originate call to dialed number ring connect off hook start CNG tone (through vocoders) start CED tone (through vocoders) Service Negotiation to S.O. = Analog Fax V. preamble NSF CSI BS/MSC/IWF DIS S y nch TCP/IP-PPP-RLP AT+CFG="" 0 AT+CVFQ? +CVFQ:,0 Max Rate Messag e V. preamble NSF CSI V. preamble CSI Relay CSI, DIS DIS DIS Figure..-. Call Set-Up as Voice Transitioning to Mobile Transmitting Fax. Voice Call Shown as Mobile-Originated and Fax Call Detected Using V. Preamble Detection. -

343 TIA/EIA/IS-0-A. TE MT BS/MSC PSTN PSTN Fax off hook dial tone ring S.O. = Voice Incoming call with dialed digits DTMF digits (Voice DN) off hook Connect Order off hook CNG tone (through vocoders) start CED tone (through vocoders) Service Negotiation to S.O. = Analog Fax V. preamble NSF CSI BS/MSC/IWF DIS S y nch TCP/IP-PPP-RLP AT+CFG="" 0 AT+CVFQ? +CVFQ:,0 Max Rate Messag e V. preamble NSF CSI V. preamble CSI Relay CSI, DIS DIS DIS Figure..-. Call Set-Up as Voice Transitioning to Mobile Transmitting Fax. Voice Call Shown as Mobile-Terminated and Fax Call is Detected Using V. Preamble Detection. -

344 TIA/EIA/IS-0-A.. IWF and MT Procedures During Conversation State The following call flows illustrate various scenarios for Mobile Receiving Fax Calls. For Mobile Transmitting Fax Calls, the procedures are the same except that the functions of the IWF and the MT are reversed. TE MT BS/MSC/IWF PSTN Fax V. preamble NSF CSI DIS Relay CSI, DIS start CED tone V. preamble CSI DIS V. preamble TSI V. preamble TSI Relay TSI, DCS DCS for 00 bps 00 bps DCS for 00 bps 00 bps V. preamble CFR Relay CFR V. preamble CFR imag e 00 bps data messag e imag e 00 bps V. preamble MPS preamble messag e Relay MPS V. preamble MPS V. preamble MCF Relay MCF V. preamble MCF imag e 00 bps data messag e imag e 00 bps V. preamble EOP preamble messag e Relay EOP V. preamble EOP V. preamble MCF Relay MCF V. preamble MCF V. preamble DCN CLOSE transport layer V. preamble DCN Figure.-. Typical Mobile Receiving Fax Call Where the Initial Fax Training Rate from the Transmitting Fax Machine is Supported by the Air Interface -

345 TIA/EIA/IS-0-A. TE MT BS/MSC/IWF PSTN Fax V. preamble TSI V. preamble TSI Relay TSI, DCS DCS for 00 bps 00 bps DCS for 00 bps 00 bps V. preamble FTT V. preamble CFR Relay CFR V. preamble TSI start blank 00 bps DCS for 000 bps 000 bps V. preamble CFR imag e 00 bps data messag e imag e 000 bps V. preamble MPS preamble messag e Relay MPS V. preamble MPS V. preamble MCF Relay MCF V. preamble MCF Figure.-. Mobile Receiving Fax Call Where the Initial Fax Training Rate from the Transmitting Fax Machine is Not Supported by the Air Interface -

346 TIA/EIA/IS-0-A. TE MT BS/MSC/IWF PSTN Fax V. preamble TSI V. preamble TSI Relay TSI, DCS DCS for 00 bps 00 bps DCS for 00 bps 00 bps V. preamble FTT Relay FTT V. preamble FTT V. preamble TSI DCS for 00 bps 00 bps V. preamble TSI DCS for 00 bps 00 bps V. preamble CFR Relay CFR V. preamble FTT V. preamble TSI start blank 00 bps DCS for 00 bps 00 bps V. preamble CFR imag e 00 bps data messag e imag e 00 bps V. preamble MPS preamble messag e Relay MPS V. preamble MPS Figure.-. Mobile Receiving Fax Call Where the Receiving Fax Machine Rejects the Initial Training Rate -0

347 TIA/EIA/IS-0-A. TE MT BS/MSC/IWF PSTN Fax V. preamble CFR Relay CFR V. preamble CFR imag e data data messag e imag e data V. preamble MPS preamble messag e Relay MPS V. preamble MPS V. preamble MPS V. preamble MPS V. preamble MCF V. preamble MPS Timer T expires (start preamble) V. preamble imag e data Relay MCF (delayed OTA by channel) data messag e MCF imag e data V. preamble EOP preamble message Relay EOP V. preamble EOP V. preamble RTP Relay RTP V. preamble RTP V. preamble DCN CLOSE transport layer V. preamble DCN Figure.-. Mobile Receiving Fax Call Illustrating the Use of Timer T -

348 TIA/EIA/IS-0-A. TE MT BS/MSC/IWF PSTN Fax V. preamble CFR Relay CFR V. preamble CFR imag e 00 bps data messag e imag e 00 bps V. preamble MPS preamble messag e Relay MPS V. preamble MPS V. preamble RTP Relay RTP V. preamble RTP V. preamble TSI DCS for 00 bps 00 bps V. preamble TSI DCS for 00 bps 00 bps V. preamble FTT Relay FTT V. preamble TSI DCS for 00 bps 00 bps V. preamble TSI DCS for 00 bps 00 bps V. preamble CFR Relay CFR V. preamble CFR imag e 00 bps data messag e imag e 00 bps V. preamble EOP preamble messag e Relay EOP V. preamble EOP Figure.-. Mobile Receiving Fax Call with an RTP Response from the RX Fax Machine -

349 TIA/EIA/IS-0-A. TE MT BS/MSC/IWF PSTN Fax V. preamble NSF CSI DIS (bit =) Relay CSI, DIS V. preamble CSI DIS (bit =) V. preamble NSC CIG V. preamble CIG Relay CIG, DTC DTC DTC V. preamble TSI 00 bps 00 bps Relay TSI, DCS V. preamble TSI 00 bps 00 bps V. preamble CFR Relay CFR V. preamble CFR imag e 00 bps data messag e imag e 00 bps Figure.-. Mobile Receiving Fax Call Illustrating Polling (the TE has a document to send which the PSTN fax machine retrieves) -

350 TIA/EIA/IS-0-A. TE MT BS/MSC/IWF PSTN Fax V. preamble TSI corrupted DCS for 00 bps 00 bps V. preamble TSI V. preamble TSI Relay TSI, DCS DCS for 00 bps 00 bps DCS for 00 bps 00 bps V. preamble corrupted CFR V. preamble TSI V. preamble TSI DCS for 00 bps 00 bps DCS for 00 bps 00 bps V. preamble FTT V. preamble CFR Relay CFR V. preamble TSI DCS for 00 bps 00 bps start blank 00 bps V. preamble CFR imag e 00 bps data messag e imag e 00 bps Figure.-. Mobile Receiving Fax Call with Corrupted HDLC Frames (corrupted DCS and CFR) -

351 TIA/EIA/IS-0-A. TE MT BS/MSC/IWF PSTN Fax V. preamble TSI V. preamble TSI Relay TSI, DCS DCS for 00 bps 00 bps DCS for 00 bps 00 bps V. preamble CFR Relay CFR V. preamble corrupted CFR V. preamble TSI start blank 00 bps DCS for 00 bps 00 bps V. preamble CFR imag e 00 bps data messag e imag e 00 bps V. preamble corrupted MPS preamble messag e Relay MPS V. preamble MPS V. preamble CRP V. preamble MPS V. preamble MPS V. preamble corrupted MCF V. preamble MPS V. preamble MPS V. preamble MCF Relay MCF V. preamble MCF Figure.-. Mobile Receiving Fax Call with Corrupted HDLC frames and Fax CRP Option (corrupted CFR, MPS, and MCF) -

352

353 TIA/EIA/IS-0-A. TIMERS Timer Definition Value Appears in T T T T T T Minimum amount of time that the Analog Fax Layer should remain silent over its analog interface before switching from V. demodulation to V. modulation. Minimum amount of time the RX Fax Layer should wait before transmitting TCF to the fax machine after the DCS has been sent. Maximum time permitted per scan line transmitted by the RX Fax Layer to the receiving fax machine. Minimum amount of time that the RX Fax Layer should remain silent over its analog interface to the receiving fax machine after transmitting the end of page data. Minimum amount of time for sending V. preamble to a fax machine across an analog interface. The page start timer indicates the time for which the RX Fax Layer should wait for the page data to arrive over the U m interface. If page start timer expires, the RX Fax Layer shall transmit blank scan lines to the receiving fax machine until page data reception begins over the U m interface. 00 msec,...,,... msec...,... second..,.. 00 msec..,.. second, seconds...,..,...,...,..,... T The collision timer determines when transmission of a V.. seconds for, -

354 TIA/EIA/IS-0-A. T T T 0 T T message to a fax machine is permitted. The timer shall be reset to T and enabled upon reception of any final frame V. message from the local fax machine. Transmission is permitted if the timer has not yet expired and inhibited otherwise. Minimum amount of time for which the TX Fax Layer expects to hear a preamble over the analog interface to the transmitting fax machine before sending a Preamble Message over the U m interface. After transmitting CED to the transmitting fax machine, the TX Fax Layer shall wait T before transmitting further signals (see T.0...). Amount of time for which the Analog Fax Layer should wait before sending a repeated message to the fax machine if a response to the message has not been received. The amount of time the Analog Fax Layer shall wait before directing the analog interface to release the call. The Analog Fax Layer shall close the transport layer and direct the analog interface to the MT. seconds for the IWF 00 msec..,.. msec... seconds, sec,...,,... 0 sec, T.0 specifies a.0s +/- % time-out between repeated V. messages for automatic mode calls, and.s +/- % for manual mode calls. This interval forms a transmission window during which the fax machine waits for responses. Setting collision timer at T ensures that transmission of V. messages to the fax machine do not collide with repeated V. messages from the fax machine. -

355 TIA/EIA/IS-0-A. release the call when no messages are exchanged over the U m interface for more than T. T This timer is started by the TX Fax Layer on receiving a total of three post page messages from the transmitting fax machine. Upon expiration of this timer, the TX Fax Layer shall start sending V. preamble to the transmitting fax machine if a response has not been sent. The TX Fax layer shall send V. preamble for a minimum of T and continue sending V. preamble until it has a response to send to the transmitting fax machine.. seconds for the MT. seconds for the IWF..,.. -

356

357 TIA/EIA/IS-0-A. 0 DIS/DTC MODIFICATIONS When the Analog Fax Layer receives a DIS or DTC message over the U m interface, it shall modify the bits of the message as follows: Bits through shall be set to zero. Bits through (rate bits) shall be modified according to Table 0-. Table 0-. Rate Bit Modifications Bits,,, of original DIS/DTC Bits,,, of the modified DIS/DTC based on the maximum fax rate supported over the air (fax rates are in bits/second) * * * * * * * * * * * * * * * * * * * 000 N * * * * * * 00 R * * * * * * 00 N * * * * * * * * 000 N * * * * * * 00 R * * * * * * 00 N * * * * * * * * 00 N * * * * * * 0 R * * * * * * 0 N * * * * * * R * * * * * * An asterix (*) indicates that the bits in the original DIS/DTC are to be left unchanged. Reserved (R) and unused bits (N) are left unchanged. In the event of ITU-T assigning new values to these bits, their values in this table may need to be updated. Bits through (MSLT bits) shall be modified according to Table 0-. To prevent the use of Group and Group fax protocols. 0-

358 TIA/EIA/IS-0-A. Table 0-. MSLT Bit Modification Bits,, of the original DIS/DTC Bits,, of the modified DIS/DTC Bits and higher shall be masked out unless the IWF and MT support the fax options advertised by these bits. After modifying the message, the FCS value shall be recomputed according to.. of T.0. In addition, if the MT or IWF does not support certain fax features, it shall modify the corresponding bits of the DIS or DTC messages received from the fax machine or the U m interface. 0-

359 TIA/EIA/IS-0-A. 0 0 AT COMMAND PROCESSING. General Requirements This section describes how the mobile station and IWF process the limited set of AT commands necessary for control of the analog fax service The mobile station processes AT commands when the transport layer is in the ESTABLISHED state. When the transport layer is in the ESTABLISHED state the IWF reflects all AT commands (following the reception of the +CFG command) back over the Um interface to the mobile station, and the mobile can process the reflected AT commands. AT commands are classified as recognized or unrecognized. An AT command is considered recognized if it is defined for analog fax in this standard and complies with all requirements of the service in this standard. An unrecognized AT command is an AT command conforming with the syntax requirements of EIA/TIA- that is not defined for this service, or has a parameter value not mandated by this standard. When an AT command line is issued, the entity processing it issues a Command Response. A Command Response may consist of zero or more lines of Information Text, followed by a Result Code. The mobile station and the IWF shall observe the following rules when processing AT commands:. When the transport layer enters the ESTABLISHED state, the mobile station and IWF shall perform the following: The mobile station shall send its stored configuration string, if any, to the IWF (see..). If the mobile station has no stored configuration string, it shall send a null string. The mobile station shall use the AT+CFG SET parameter command to deliver the configuration string parameter to the IWF. The command line containing the AT+CFG command shall be terminated (i.e., no further AT commands can follow the AT+CFG command in the same command line). The IWF should return an ERROR result code if it encounters errors processing the AT+CFG command. 0. The IWF shall respond to all received commands following the +CFG command with the appropriate response, via the U m interface.. Basic AT Command Processing.. Action Commands The mobile station and IWF shall support the action commands defined by EIA/TIA-0, and shown in Table..-. -

360 TIA/EIA/IS-0-A. Table..-. Basic Action Commands A Command D<dial string> Description Enter the online state. See service specific processing for further details. Causes the mobile station to transition from the command state to the online state. The <dial string> is optional. The dial string may contain the following characters: Digits 0 to, *, #, A, B, C, and D. The dial string may contain the following dial modifiers: T Tone dialing [ignore] P Pulse dialing [ignore], Pause during dialing W Wait for dial Wait for quiet answer! Hook flash [$] Wait for billing tone (for credit-card calls).. Basic Result Codes The mobile station and IWF shall support the basic result codes of Table..-. The IWF shall encapsulate result codes (see Table..-) for transmission over the U m interface using the method defined in.. The mobile station and IWF shall send the result codes in verbose mode as the default format. The mobile station may request the use of non-verbose (numeric) result codes by setting the V0 basic AT parameter (see EIA/TIA-0) in its stored configuration string (see..). Table..-. Basic Result Codes Numeric Verbal Description Source 0 OK Command executed. MT, IWF Reserved Reserved Reserved RING Alerting signal received from network. IWF NO CARRIER Unable to activate the service. IWF ERROR Command not recognized or could not be executed. MT, IWF NO DIALTONE No dial tone detected within time-out period. IWF BUSY Reorder (Busy signal) received. IWF NO ANSWER Five seconds of silence not detected after ring back dial modifier is used. IWF 0 The ERROR result code shall be returned for all commands which do not comply with the syntax rules of. of EIA/TIA- or Section of EIA/TIA-0. -

361 TIA/EIA/IS-0-A. 0. AT Command Set Extensions for Modem Control The mobile station and IWF shall support the AT command set extensions for modem control as defined in. of IS-0. with the following exceptions: Requirements describing AT command processing actions over the R m interface are not applicable. AT command result codes shall be sent in verbose mode as the default mode. Nonverbose mode is optional. The procedures described in... of IS-0. for returning to on-line command state shall not be supported. The procedures described in... of IS-0. for reporting dropped fax lines shall not be supported. The procedures described in... of IS-0. for facsimile voice-request commands shall not be supported. The IWF shall not perform the AT command reflection procedures described in. of IS-0.. Processing of cellular extensions to ANSI/TIA/EIA- shall be in accordance with.. of IS-0. using only the command sequence listed in Tables.- Table.-. IWF to Mobile Station Commands Command Sequence Hex Codes Mobile Station Action IWF Action <EM><extend> <len> <response characters> <0x><0x> <len><0x> <string> Wait for Result Code before processing next command. Issue when passing AT command response to mobile station Cellular AT Command Processing The mobile station and the IWF shall support the AT command extensions and result codes for CDMA as listed below... AT+CVF Command Processing If the BS/MSC and mobile station are in the Conversation Substate with a connected service option other than analog fax, and the mobile station initiates service negotiation to connect a service configuration including an analog fax service option, the mobile station shall send the AT+CVF command to the IWF to indicate the fax calling station and any requirement for T.0 Phase A signaling. The AT+CVF command shall have the following format: AT+CVF = <calling station>, <phasea> where: -

362 TIA/EIA/IS-0-A. 0 0 <calling station> indicates the fax calling station. <calling station> = 0, when the PSTN fax machine serves as the calling station. <calling station> =, when the TE serves as the calling station. <phasea> is the T.0 Phase A signaling requirement. <phasea> = 0, when T.0 Phase A signaling is not required. <phasea> =, when T.0 Phase A signaling is required. The AT+CVF command shall be preceded by the AT+CFG command... AT+CVFQ? Command Processing If the BS/MSC and mobile station are in the Conversation Substate with a connected service option other than analog fax, and the BS/MSC initiates service negotiation to connect a service configuration including an analog fax service option, the mobile station shall send the AT+CVFQ? query command to the IWF to determine the fax calling station and any requirement for T.0 Phase A signaling. The IWF response to the AT+CVFQ? command shall have the following format: +CVFQ: <calling station>, <phasea> where: <calling station> indicates the fax calling station. <calling station> = 0, when the PSTN fax machine serves as the calling station. <calling station> =, when the TE serves as the calling station. <phasea> is the T.0 Phase A signaling requirement. <phasea> = 0, when T.0 Phase A signaling is not required. <phasea> =, when T.0 Phase A signaling is required. The AT+CVFQ? command shall be preceded by the AT+CFG command... AT+CFG Command Processing The mobile station may send a stored configuration string to the IWF through the AT+CFG command. If the mobile station does not send a stored configuration string to the IWF, it shall send a null configuration string (AT+CFG= ). -

363 Data Service Options for Spread Spectrum Systems: Radio Link Protocol Type TIA/EIA/IS-0-A. (PN-.) Ballot Resolution Version March,

364 Copyright TIA

365 TIA/EIA/IS-0-A. CONTENTS INTRODUCTION...-. General Description...-. Terms...-. References...- GENERAL REQUIREMENTS...-. Required Multiplex Option Support...-. Fundamental Channel Rate Control Service Negotiation Rate Control Procedures Mobile Station Requirements BS/MSC Requirements...-. Interface to Multiplex Options Primary Traffic Secondary Traffic...-. Traffic Channel Frame Priorities...- RLP PROCEDURES...-. RLP Procedures Initialization/Reset Procedures Non-Encrypted Mode RLP Initialization/Reset Encrypted Mode RLP Initialization/Reset Extended Data Frame Sequence Numbering RLP Data Encryption Negotiation Mobile Station Negotiation Procedures BS/MSC Negotiation Procedures Data Transfer Encryption Decryption Frame Validity Checks Primary Traffic Secondary Traffic Segmentation of Retransmitted Data Frames...- RLP FRAME FORMATS...-. Control Frames...- i

366 TIA/EIA/IS-0-A. CONTENTS 0.. SYNC, SYNC/ACK, and ACK Control Frames NAK Control Frame...-. Data Frames Unsegmented Data Frames Segmented Data Frames Rate / and Rate / Intersegment Fill Frames Rate RLP Frames Rate RLP Frame Format A Format A for Primary Traffic Format A for Secondary Traffic Rate RLP Data Frame Format B Format B for Primary Traffic Format B for Secondary Traffic...-. Idle Frames...-0 ii

367 TIA/EIA/IS-0-A. FIGURES Figure RLP Transmit Sequence Number...- Figure RLP Receive Sequence Number Variables TABLES Table Sequence Parameters for Rate Reduction...- Table Service Option Control Message Type-Specific Fields for Fundamental Channel Rate Control...- Table Fraction of Frames at Rate and Rate / with Rate Reduction...- Table Primary Traffic RLP Frame Types Supplied by RLP to the Multiplex Sublayer...- Table Primary Traffic RLP Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option,,,,,,, and...- Table Primary Traffic RLP Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option,,,, 0,,, and...- Table Secondary Traffic RLP Frame Types Supplied by RLP to the Multiplex Sublayer.- Table Secondary Traffic RLP Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option,,,,,,, and...- Table Secondary Traffic RLP Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option,,,, 0,,, and...- Figure RLP Transmit Sequence Number...- Figure RLP Receive Sequence Number Variables...- Table 0 Minimum Resequencing Storage Buffer Size...- Table User Data Encryption Modes...- Table Values of the Maximum Allowable Data Length (MAX_LEN...- Table Modified Nordstrom Robinson Code...- iii

368

369 TIA/EIA/IS-0-A INTRODUCTION. General Description This chapter specifies procedures for Radio Link Protocol Type, which is used with a TIA/EIA--B Traffic Channel to support CDMA data services. For the remainder of this chapter, Radio Link Protocol Type shall be called RLP. RLP provides an octet stream transport service over forward and reverse traffic channels. RLP is unaware of higher layer framing; it operates on a featureless octet stream, delivering the octets in the order received. RLP has procedures to substantially reduce the error rate exhibited by CDMA traffic channels. There is no direct relationship between higher layer packets and the underlying traffic channel frames; a large packet may span multiple traffic channel frames, or a single traffic channel frame may contain all or part of several small higher layer packets. Section below is a general description of RLP that defines its use by any service option for which it is suited. Section defines the RLP procedures for encrypted or non-encrypted applications. Section defines the RLP frame formats.. Terms Base Station (BS). A station in the Domestic Public Cellular Radio Telecommunications Service, other than a mobile station, used for communicating with mobile stations. Depending upon the context, the term base station may refer to a cell, a sector within a cell, or other part of the cellular system. BS. See base station. BS/MSC. The base station and mobile switching center considered as a single functional entity. Data Block. A unit of data transmitted by the mobile/base station, used to transport user data and signaling traffic. For Multiplex Options and, one data block is transmitted by the mobile/base station every 0 ms. For Multiplex Options n -, n = through, at least one data block and at most n data blocks are transmitted by the mobile/base station every 0 ms. For Multiplex Options n, n = through, at least one data block and at most n data blocks are transmitted by the mobile/base station every 0 ms. Forward Fundamental Code Channel. A Fundamental Code Channel operating in the forward direction. Forward Supplemental Code Channel. A Supplemental Code Channel operating in the forward direction. Forward Traffic Channel. One Forward Fundamental Code Channel and optionally up to seven Forward Supplemental Code Channels used to transport data blocks from the base station to the mobile station. Fundamental Code Channel. A portion of a Traffic Channel (Forward or Reverse) that is always present, and carries a fundamental data block and power control information. -

370 TIA/EIA/IS-0-A. 0 0 Fundamental Data Block. A data block that is transmitted on the Fundamental Code Channel. It may contain signaling traffic, primary traffic, and secondary traffic. Fundamental RLP Frame. An RLP frame carried in a fundamental data block. Mobile Station. A station in the Domestic 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. NAK List. A list maintained by RLP to associate the -bit sequence number of a missing data frame with the -bit sequence number contained in the retransmitted data frame. Reverse Fundamental Code Channel. A Fundamental Code Channel operating in the reverse direction. Reverse Supplemental Code Channel. A Supplemental Code Channel operating in the reverse direction. Reverse Traffic Channel. One Reverse Fundamental Code Channel and optionally up to seven Reverse Supplemental Code Channels used to transport data blocks from the mobile station to the base station. RLP. Radio Link Protocol. Supplemental Code Channel. A portion of a Traffic Channel (Forward or Reverse) that is optionally present and carries a supplemental data block. Supplemental Data Block. A data block that is transmitted on a Supplemental Code Channel. It may contain only primary traffic or secondary traffic. Supplemental RLP Frame. An RLP frame carried in a supplemental data block.. References TIA/EIA--B TSB Mobile Station-Base Station Compatibility Standard for Dual-Mode Spread Spectrum System, August,. Administration of Parameter Value Assignments for TIA/EIA Wideband Spread Spectrum Standards, December,. -

371 TIA/EIA/IS-0-A GENERAL REQUIREMENTS. Required Multiplex Option Support Mobile stations supporting RLP shall send and receive traffic channel frames in accordance with the requirements of TIA/EIA--B Multiplex Options through. Mobile stations supporting multiple connected service options may support independent instances of RLP for each service option, but each traffic type shall carry only a single instance of RLP. Non-blank RLP frames may be carried by the following Multiplex Option,,,,,,, or traffic channel frames when sent in a fundamental data block: 00 bps primary traffic only 00 bps primary traffic only 00 bps primary traffic only Dim and Burst with Rate / primary and signaling traffic, as primary traffic Dim and Burst with Rate / primary and secondary traffic, as either primary traffic, secondary traffic, or both Dim and Burst with Rate / primary and secondary traffic, as secondary traffic Dim and Burst with Rate / primary and signaling traffic, as primary traffic Dim and Burst with Rate / primary and secondary traffic, as either primary traffic, secondary traffic, or both Blank and Burst with secondary traffic only Non-blank RLP frames may be carried by the following Multiplex Option,,,,,,, or traffic channel frames when sent in a supplemental data block: 00 bps primary traffic only Blank and Burst with secondary traffic only Non-blank RLP frames may be carried by the following Multiplex Option,,,, 0,,, or traffic channel frames when sent in a fundamental data block: 00 bps primary traffic only 00 bps primary traffic only 00 bps primary traffic only 00 bps primary traffic only Dim and Burst with Rate / primary and signaling traffic, as primary traffic RLP may be carried as both primary and secondary traffic when there are multiple connected service options, each having its own RLP instance. -

372 TIA/EIA/IS-0-A Dim and Burst with Rate / primary and secondary traffic, as either primary traffic, secondary traffic, or both Dim and Burst with Rate / primary and signaling traffic, as primary traffic Dim and Burst with Rate / primary and secondary traffic, as either primary traffic, secondary traffic, or both Dim and Burst with Rate / primary and signaling traffic, as primary traffic Dim and Burst with Rate / primary and secondary traffic, as either primary traffic, secondary traffic, or both Dim and Burst with Rate / primary, secondary, and signaling traffic, as either primary traffic, secondary traffic, or both Blank and Burst with secondary traffic only Non-blank RLP frames may be carried by the following Multiplex Option,,,, 0,,, or traffic channel frames when sent in a supplemental data block: 00 bps primary traffic only Blank and Burst with secondary traffic only. Fundamental Channel Rate Control The following requirements for Fundamental Channel rate control shall apply to mobile stations having a single connected service option. Fundamental Channel rate control for mobile stations having multiple connected service options is for further study... Service Negotiation Rate Control Procedures If service negotiation is used, the BS/MSC may send a Service Option Control Message to the mobile station (see... of TIA/EIA--B). The mobile station shall not send a Service Option Control Message to the BS/MSC.... Mobile Station Requirements The mobile station shall support one pending rate control Service Option Control Message for the service option. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 000, then at the action time associated with the message, the mobile station shall process the message as follows: If the RATE_REDUC field is equal to a value defined in Table, the service option shall generate the fraction of those frames normally generated as Rate frames at either Rate or Rate / as specified by the corresponding line in Table. The RLP may be carried as both primary and secondary traffic when there are multiple connected service options, each having its own RLP instance. -

373 TIA/EIA/IS-0-A. 0 service option shall continue to use these fractions until either of the following events occur: - The mobile station receives a Service Option Control Message with FIELD_TYPE set to 000 specifying a different RATE_REDUC, or - The service option is re-initialized. If the RATE_REDUC field is not equal to a value defined in Table, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to The service option may use the following procedure to perform rate reduction. Sequences of N frames are formed as shown in Table are allowed to be at Rate, the next N-L frames are forced to be Rate /. Whenever RLP voluntarily generates a Rate / RLP data frame, the sequence shall be reset. This ensures that the first Fundamental Channel frame in a burst of data will be at Rate, unless RATE_REDUC equals 00 or RLP has been commanded by the multiplex sublayer to generate other than a Rate frame. Table Sequence Parameters for Rate Reduction RATE_REDUC (binary) Sequence Length, N Maximum Number of Contiguous Rate Fundamental Frames in a Sequence, L Number of Contiguous Rate / Fundamental Frames in a Sequence, N-L BS/MSC Requirements The BS/MSC may send a Service Option Control Message to the mobile station for Fundamental Channel rate control. If the BS/MSC sends a Service Option Control Message for Fundamental Channel rate control, the BS/MSC shall include the type-specific fields shown in Table. -

374 TIA/EIA/IS-0-A. Table Service Option Control Message Type-Specific Fields for Fundamental Channel Rate Control Field Length (bits) RATE_REDUC RESERVED FIELD_TYPE 0 RATE_REDUC - Rate reduction. The BS/MSC shall set this field to the RATE_REDUC value from Table corresponding to the rate reduction that the mobile station is to perform. RESERVED - Reserved bits. The BS/MSC shall set this field to 00. FIELD_TYPE - Type-specific field designator. The BS/MSC shall set this field to 000. Table Fraction of Frames at Rate and Rate / with Rate Reduction RATE_REDUC (binary) Fraction of Normally Rate Fundamental Frames to be Rate Fraction of Normally Rate Fundamental Frames to be Rate / 000' 0 00 / / 00 / / 0 / / 00 0 All other RATE_REDUC values are reserved. 0. Interface to Multiplex Options RLP frames can be carried as primary or secondary traffic. An RLP frame supplied to the multiplex sublayer to be carried in the fundamental data block is called a Fundamental RLP frame. Similarly, an RLP frame supplied to the multiplex sublayer to be carried in a supplemental data block is referred to as a Supplemental RLP frame. -

375 TIA/EIA/IS-0-A. 0.. Primary Traffic When RLP frames are carried as primary traffic, RLP shall generate and supply (+NUM_SUP) RLP frames containing the service option bits to the multiplex sublayer every 0 ms, where NUM_SUP indicates the number of supplemental data blocks allocated for primary traffic. Each RLP frame shall be one of the types as shown in Table. The number of bits supplied to the multiplex sublayer for each type of RLP frame shall also be as shown in Table. Unless otherwise commanded by Multiplex Option,,,,,,, or, RLP may supply a Rate, Rate /, Rate / or Blank Fundamental RLP frame. Unless otherwise commanded by Multiplex Option,,,, 0,,, or, RLP may supply a Rate, Rate /, Rate /, Rate / or Blank Fundamental RLP frame. Upon command, RLP shall generate a Blank RLP frame. A Blank RLP frame contains no bits and is used for blank-and-burst transmission of signaling traffic (see... of TIA/EIA--B) or when RLP is unable to send a segment of a segmented data frame. Also upon command, RLP shall generate a non-blank Fundamental RLP frame with a maximum rate of Rate /. Each Supplemental RLP frame shall be either a Rate or Blank RLP frame. Table Primary Traffic RLP Frame Types Supplied by RLP to the Multiplex Sublayer RLP Frame Type Multiplex Option,,,,,,, and (bits per frame) Multiplex Option,,,, 0,,, and (bits per frame) Can be supplied as a Supplemental RLP frame Rate Yes Rate / 0 No Rate / Not Used No Rate / 0 No Blank 0 0 Yes 0 The multiplex sublayer in the mobile station categorizes every received traffic channel frame (see... of TIA/EIA--B), and supplies the frame s category and accompanying bits, if any, to RLP. Table lists the categories (and corresponding RLP frame types) supplied by the multiplex sublayer when RLP is carried as primary traffic by Multiplex Option,,,,,,, or. Although RLP does not generate Rate / frames, Multiplex Options,,,,,,, and are not required to recognize this fact. RLP declares any Rate / frame received from Multiplex Option,,,,,,, or to be an erasure. Table lists the categories (and corresponding RLP frame types) supplied TIA/EIA--B allows one data block per traffic channel frame. -

376 TIA/EIA/IS-0-A. by the multiplex sublayer when RLP is carried as primary traffic by Multiplex Option,,,, 0,,, or. Table Primary Traffic RLP Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option,,,,,,, and RLP Frame Type Bits per Frame Multiplex Option,,,,,,, and Fundamental Code Channel Frame Categories Multiplex Option,,,,,,, and Supplemental Code Channel Frame Categories Rate Rate / 0,, N/A Rate / 0,, N/A Rate /,, N/A Blank 0, Erasure 0,0 Table Primary Traffic RLP Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option,,,, 0,,, and RLP Frame Type Bits per Frame Multiplex Option,,,, 0,,, and Fundamental Code Channel Frame Categories Multiplex Option,,,, 0,,, and Supplemental Code Channel Frame Categories Rate Rate /,, N/A Rate /,,,, N/A Rate / 0,,0,,,,0,, N/A Blank 0,,,,,, Erasure Secondary Traffic When RLP frames are carried as secondary traffic, RLP shall generate and supply (+NUM_SUP) RLP frames containing the service option bits to the multiplex sublayer -

377 TIA/EIA/IS-0-A. every 0 ms, where NUM_SUP indicates the number of supplemental data blocks allocated for secondary traffic. Each RLP frame shall be one of the types shown in Table. The number of bits supplied to the multiplex sublayer for each type of RLP frame shall also be as shown in Table. Upon command, RLP shall generate a Blank RLP frame. A Blank RLP frame contains no bits and is used for blank-and-burst transmission of signaling traffic (see... of TIA/EIA--B), when primary traffic has priority over secondary traffic and the primary traffic service option does not allow any secondary traffic, or when RLP is unable to send a segment of a segmented data frame (see..). Each Supplemental RLP frame shall be either a Rate or Blank RLP frame. 0 Table Secondary Traffic RLP Frame Types Supplied by RLP to the Multiplex Sublayer RLP Frame Type Bits per Frame for Multiplex Option,,,,,,, and Bits per Frame for Multiplex Option,,,, 0,,, and Can be supplied as a Supplemental RLP frame Rate Yes Rate / No Rate / 0 No Rate / No Rate / Not Available No Rate / Not Available 0 No Rate / Not Used No Rate / Not Available No Rate / Not Available No Rate / Not Available 0 No Blank 0 0 Yes The multiplex sublayer in the mobile station categorizes every received traffic channel frame (see... of TIA/EIA--B) and supplies the frame s category and accompanying bits, if any, to RLP. Table lists the categories (and corresponding RLP frame types) supplied by the multiplex sublayer when RLP is carried as secondary traffic using Multiplex Option,,,,,,, or. Table lists the categories (and TIA/EIA--B allows one data block per traffic channel frame. -

378 TIA/EIA/IS-0-A. corresponding RLP frame types) supplied by the multiplex sublayer when RLP is carried as secondary traffic using Multiplex Option,,,, 0,,, or. Table Secondary Traffic RLP Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option,,,,,,, and RLP Frame Type Bits per Frame Multiplex Option,,,,,,, and Fundamental Code Channel Frame Categories Multiplex Option,,,,,,, and Supplemental Code Channel Frame Categories Rate Rate / N/A Rate / N/A Rate / N/A Blank 0 - Erasure 0, 0 -

379 TIA/EIA/IS-0-A. Table Secondary Traffic RLP Frame Types Supplied by the Multiplex Sublayer to RLP for Multiplex Option,,,, 0,,, and RLP Frame Type Bits per Frame Multiplex Option,,,, 0,,, and Fundamental Code Channel Frame Categories Multiplex Option,,,, 0,,, and Supplemental Code Channel Frame Categories Rate Rate / N/A Rate / 0 N/A Rate / N/A Rate / N/A Rate / 0 N/A Rate / N/A Rate / N/A Rate / N/A Rate / 0 0,, N/A Blank 0 -,-,-, Erasure 0 0. Traffic Channel Frame Priorities RLP shall classify RLP frames into three priority classes. In order of priority they are, with highest priority first:. RLP control frames. Retransmitted data frames (i.e., data frames being resent in response to received NAK control frames). New data frames (i.e., data frames being sent for the first time) When the multiplex sublayer indicates that it is ready to send RLP frames on a traffic channel, RLP shall supply it with the highest priority RLP frames available with the following exceptions:. A control frame shall only be supplied as a Fundamental RLP frame.. Identical retransmitted data frames should not be supplied in the same 0 ms time slot, but instead should be supplied in consecutive time slots, in order to reduce the likelihood that all retransmitted copies will be lost due to a burst error. -

380 TIA/EIA/IS-0-A RLP shall not supply more than Supplemental RLP new data frame (as defined in...) in a 0 ms time slot. When RLP frames are carried as primary traffic, and if no RLP frames in the above three priority classes are available, an idle frame (see.) shall be supplied if a Fundamental RLP frame is needed and a Blank RLP frame shall be supplied if a Supplemental RLP frame is needed. When RLP frames are carried as secondary traffic, and if no RLP frames in the above three priority classes are available, an idle frame (see.) shall be generated and supplied if a Fundamental RLP frame is needed and the value of the round-trip frame counter is greater than zero. If a Supplemental RLP frame is needed, a Blank RLP frame shall be supplied. Whenever RLP supplies a non-blank Fundamental frame and the value of the round-trip frame counter is greater than zero, RLP shall decrement the round-trip frame counter. When a service option is connected that carries RLP frames as primary traffic, and there is no service option connected that uses secondary traffic, the mobile station should observe the following priorities in using the traffic channel:. Signaling Traffic. RLP frames in priority class order When a service option is connected that carries RLP frames as secondary traffic, and a service option not using RLP is connected that uses primary traffic, the mobile station should observe the following priorities in using the traffic channel, if the primary traffic service option permits:. Signaling Traffic. RLP control frames, RLP retransmissions (RLP frames in priority classes and ), and RLP transmissions due to idle timer expiration (see..). If the primary traffic service option permits, the multiplex sublayer should force primary traffic to no more than half rate when these RLP frames are available.. Primary traffic service option data. New data frames When data from a service option that carries RLP frames using secondary traffic has a lower priority than data from the service option using primary traffic, the blank and burst with secondary traffic frame format (see... of TIA/EIA--B) shall not be used unless the primary traffic service option has no data to send. When service options are connected that carry RLP frames as both primary and secondary traffic, the mobile station should observe the following priorities in using the traffic channel:. Signaling Traffic -0

381 TIA/EIA/IS-0-A.. RLP control frames and RLP retransmissions (RLP frames in priority classes and ) from the service option using primary traffic.. RLP control frames, RLP retransmissions (RLP frames in priority classes and ), and RLP transmissions due to idle timer expiration (see..) from the service option using secondary traffic.. New data frames from the service option using primary traffic (RLP frames in priority class ).. New data frames from the service option using secondary traffic (RLP frames in priority class ). 0 -

382

383 TIA/EIA/IS-0-A RLP PROCEDURES. RLP Procedures RLP provides the capability of both non-encrypted mode and encrypted mode data transport. The encryption capability is selected during RLP initialization/reset and is accomplished as a negotiation between the mobile station and the BS/MSC. In addition, a procedure for synchronizing RLP without encryption negotiation is also provided here. The two techniques are compatible with each other and therefore can co-exist in systems where encryption negotiation is supported in the infrastructure equipment, but possibly not in some of the mobile stations attempting access to the system... Initialization/Reset Procedures This standard defines two alternate RLP initialization/reset procedures. Non-Encrypted Mode initialization/reset shall be used by mobile stations and BS/MSCs that do not support RLP data frame encryption for the desired service. Encrypted Mode initialization/reset procedures shall be used by mobile stations and BS/MSCs to negotiate the use of RLP data frame encryption.... Non-Encrypted Mode RLP Initialization/Reset RLP is established with a bi-directional handshake, after connection of the service option that uses RLP, to synchronize the connection. To establish RLP without RLP data encryption all control frames used (SYNC, ACK, and SYNC/ACK) shall indicate that RLP data encryption is not supported (see Table ) and shall exclude both the EM and EXT_SEQ_M fields (see..). When RLP is initialized or reset, and when a SYNC control frame is received, RLP shall perform the following: Reset the send and receive state variables L_V(S), L_V(R), and L_V(N) (defined in..) to zero. Set the round-trip frame counter to zero. Set the consecutive erasure count E (defined in.. ) to zero. Clear the resequencing buffers (defined in..). Disable all NAK retransmission timers and all NAK abort timers. Discard any data frames queued for retransmission. Discard any data frame being reassembled (see..). Clear the NAK List (defined in..). When RLP is initialized or reset, it shall supply a continuous stream of SYNC control frames (see..). When RLP receives a SYNC control frame it shall supply a SYNC/ACK control frame and set a round-trip frame counter to an implementation defined value -

384 TIA/EIA/IS-0-A greater than or equal to, and shall continue supplying SYNC/ACK control frames until it receives the next non-blank valid frame which is not a SYNC control frame. When RLP receives a SYNC/ACK control frame it shall supply an ACK control frame and set a roundtrip frame counter to an implementation defined value greater than or equal to, and shall continue supplying ACK control frames until it receives the next non-blank valid frame which is not a SYNC/ACK control frame. When RLP receives an ACK control frame, it shall not supply SYNC, SYNC/ACK or ACK control frames, and should begin supplying data frames. When RLP frames are carried as primary or secondary traffic, RLP shall store in RLP_DELAY s the number of Fundamental RLP frames received between supplying the last SYNC or SYNC/ACK control frame and receiving the first non-blank valid frame that is not an ACK or SYNC/ACK control frame. RLP_DELAY s is used in NAK retransmission timing, as described in Encrypted Mode RLP Initialization/Reset CDMA mobile stations complying with this standard may support authentication (see.. of TIA/EIA--B) and may support encryption of RLP data frames using the procedures defined below. RLP data encryption shall be performed whenever wireless authentication procedures have been performed during the establishment of a CDMA Traffic Channel and RLP data encryption is negotiated (see...).... Extended Data Frame Sequence Numbering Mobile stations and BS/MSCs supporting RLP data encryption shall support the following extended data frame sequence numbering for data frames. RLP shall maintain a 0-bit extended sequence number EXT_V(S). EXT_V(S) shall be set to zero when RLP is initialized following the establishment of a Traffic Channel. For all subsequent initializations/resets of RLP while the traffic channel remains established, RLP shall perform the following prior to supplying a SYNC or SYNC/ACK control frame whose EM field is set to 0 : If the least significant bits of EXT_V(S) are not zero, RLP shall set the least significant bits of EXT_V(S) to zero, and shall increment the most significant bits of EXT_V(S), modulo. If the least significant bits of EXT_V(S) are zero, RLP shall not change EXT_V(S). For each RLP frame transmitted, RLP shall set the value of L_V(S) (defined in..) to the least significant bits of EXT_V(S). EXT_V(S) shall be incremented, following the procedures for incrementing L_V(S) that are contained in.. except that EXT_V(S) shall be incremented modulo 0. RLP shall maintain a 0-bit extended sequence number EXT_V(R). When RLP is initialized or reset, RLP shall set the least significant bits of EXT_V(R) to zero. The most A minimum of frames sent following intialization/reset is believed to provide sufficient protection against frame erasures without incurring excessive overhead. -

385 TIA/EIA/IS-0-A significant bits of EXT_V(R) shall be set as described in... or... as appropriate. When L_V(R) changes (see..), RLP shall change EXT_V(R) by the same amount.... RLP Data Encryption Negotiation When authentication is performed during the establishment of a CDMA Traffic Channel, the mobile station and BS/MSC shall set the input parameters of the DataKey_Generation procedure defined in Common Cryptographic Algorithms, Revision A. as follows: In the mobile station, RAND shall be set to the stored value of RAND s. In the BS/MSC, RAND shall be set to the value of the RAND field of the Access Parameters Message that was used for mobile station authentication. The mobile station and BS/MSC shall use the value of SSD_B at the time of mobile station authentication. The mobile station and BS/MSC shall then perform the DataKey_Generation procedure. The data encryption key (DataKey) and L table shall not change while the traffic channel is established. Mobile stations and BS/MSCs supporting RLP data encryption shall perform negotiation of RLP data encryption using the procedures in... or..., respectively. If the EM field is not included in a received RLP control frame, RLP shall process the message as if EM were included and set to 00. Throughout the following procedures, RLP may omit both the EM and EXT_SEQ_M fields whenever it generates a control frame in which the EM field would be set to 00. If the BS/MSC desires RLP data encryption, the BS/MSC may deny access to service if authentication procedures (see.. of TIA/EIA--B) are not performed during Traffic Channel establishment, or if the mobile station indicates that it does not perform RLP data encryption.... Mobile Station Negotiation Procedures To indicate that the mobile station can perform RLP data encryption, RLP shall generate a SYNC control frame whose ENCRYPTION_MODE field indicates at least one supported data encryption mode (see Table ), whose EM field is set to '0', and whose EXT_SEQ_M field is set to the most significant bits of RLP s current value of EXT_V(S). To indicate that the mobile station cannot perform RLP data encryption, RLP shall generate a SYNC control frame whose EM field is set to '00'. When RLP receives a SYNC control frame, it shall perform the following: If the EM field of the received frame is set to 0, and RLP can perform at least one of the specified encryption modes, RLP shall set the most significant bits of That is, if the old value of L_V(R) is A and the new value of L_V(R) is B, EXT_V(R) is incremented by (0+B-A) modulo 0. All arithmetic operations on EXT_V(R) are modulo 0. -

386 TIA/EIA/IS-0-A EXT_V(R) to the value of the EXT_SEQ_M field of the received frame. RLP shall set the ENCRYPTION_MODE field to indicate which of the specified encryption modes it supports (see Table ), set the EM field to 0, and set the EXT_SEQ_M field to the most significant bits of RLP s current value of EXT_V(S). If the EM field of the received frame is set to any other value, or if RLP cannot perform at least one of the specified encryption modes, RLP shall set the most significant bits of EXT_V(R) to zero. In each SYNC/ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate which of the specified encryption modes it supports (see Table ) and set the EM field to 00. When RLP receives a SYNC/ACK control frame, it shall perform the following: If the EM field of the received frame is set to 0, and RLP can perform the specified encryption mode, RLP shall set the most significant bits of EXT_V(R) to the value of the EXT_SEQ_M field of the received frame. In each ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate the specified encryption mode (see Table ), set the EM field to 0, and set the EXT_SEQ_M field to the most significant bits of RLP s current value of EXT_V(S). RLP shall encrypt all generated data frames and shall decrypt all received data frames, using the specified encryption mode and following the procedures of... and... If the EM field of the received frame is set to 0, but RLP cannot perform the specified encryption mode, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to any value other than 0, RLP shall set the most significant bits of EXT_V(R) to zero. In each ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate which of the specified encryption modes it supports (see Table ) and set the EM field to 00. RLP shall neither encrypt nor decrypt data frames. When RLP receives an ACK control frame, it shall perform the following: If the EM field of the received frame is set to 0, and RLP can perform the specified encryption mode, RLP shall encrypt all generated data frames and shall decrypt all received data frames, using the specified encryption mode and following the procedures of... and... If the EM field of the received frame is set to 0, but RLP cannot perform the specified encryption mode, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to any value other than 0, RLP shall neither encrypt nor decrypt data frames.... BS/MSC Negotiation Procedures If the BS/MSC requests RLP data encryption, RLP shall generate a SYNC control frame whose ENCRYPTION_MODE field indicates at least one supported data encryption mode (see Table ), whose EM field is set to '0', and whose EXT_SEQ_M field is set to the most -

387 TIA/EIA/IS-0-A significant bits of the current value of EXT_V(S). RLP should set the ENCRYPTION_MODE field to indicate all supported data encryption modes or may set the ENCRYPTION_MODE field to indicate the desired data encryption mode. If the BS/MSC does not request RLP data encryption, RLP shall generate a SYNC control frame whose ENCRYPTION_MODE field indicates it does not support encryption (see Table ) and whose EM field is set to '00'. The BS/MSC should not request RLP data encryption if encryption is provided by the Link Layer or higher layers. When RLP receives a SYNC control frame, it shall perform the following: If the EM field of the received frame is set to 0, and the BS/MSC requests RLP data encryption, and RLP can perform at least one of the specified encryption modes (see Table ), RLP shall set the most significant bits of EXT_V(R) to the value of the EXT_SEQ_M field of the received frame. In each SYNC/ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate its desired encryption mode (see Table ), set the EM field to 0, and set the EXT_SEQ_M field to the most significant bits of the current value of EXT_V(S). If the EM field of the received frame is set to 0, the BS/MSC requests RLP data encryption, and RLP cannot perform at least one of the specified encryption modes, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...) If the EM field of the received frame is set to any other value, or if the BS/MSC does not request RLP data encryption, RLP shall set the most significant bits of EXT_V(R) to zero. In each SYNC/ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate that it does not support RLP data encryption and set the EM field to 00. When RLP receives a SYNC/ACK control frame, it shall perform the following: If the EM field of the received frame is set to 0, and the BS/MSC requests RLP data encryption, and RLP can perform at least one of the specified encryption modes, RLP shall set the most significant bits of EXT_V(R) to the value of the EXT_SEQ_M field of the received frame. In each ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate its desired encryption mode, set the EM field to 0, and set the EXT_SEQ_M field to the most significant bits of RLP s current value of EXT_V(S). RLP shall encrypt all generated data frames and shall decrypt all received data frames, using the desired encryption mode and following the procedures of... and... If the EM field of the received frame is set to 0, the BS/MSC requests RLP data encryption, and RLP cannot perform at least one of the specified encryption modes, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). It is anticipated that future revisions of PPP, IP and other protocols may include encryption. -

388 TIA/EIA/IS-0-A If the EM field of the received frame is set to 0, but the BS/MSC does not request RLP data encryption, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to any value other than 0, RLP shall set the most significant bits of EXT_V(R) to zero. In each ACK control frame it then generates, RLP shall set the ENCRYPTION_MODE field to indicate that it does not support encryption and set the EM field to 00. RLP shall neither encrypt nor decrypt data frames. When RLP receives an ACK control frame, it shall perform the following: If the EM field of the received frame is set to 0, and the BS/MSC requests RLP data encryption, and RLP can perform the specified encryption mode, RLP shall encrypt all generated data frames and shall decrypt all received data frames, using the specified encryption mode and following the procedures of... and... If the EM field of the received frame is set to 0, the BS/MSC requests RLP data encryption, and RLP cannot perform the specified encryption mode, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to 0, but the BS/MSC does not request RLP data encryption, RLP shall perform the Non-Encrypted Mode RLP initialization/reset procedure (see...). If the EM field of the received frame is set to any value other than 0, RLP shall neither encrypt nor decrypt data frames... Data Transfer When transferring data, RLP is a pure NAK-based protocol. That is, the receiver does not acknowledge correct data frames; it only requests the retransmission of data frames that were not received. All operations on RLP frame sequence numbers shall be carried out in unsigned modulo 0 arithmetic. Comparisons of two RLP frame sequence numbers shall also be modulo 0: for any RLP frame sequence number N, those sequence numbers from (N+) modulo 0 to (N+0) modulo 0, inclusive, shall be considered greater than N while all sequence numbers from (N-0) modulo 0 to (N-) modulo 0, inclusive, shall be considered less than N. RLP shall maintain a -bit sequence number count L_V(S) (see Figure ). RLP shall set the sequence number field (SEQ) in each new data frame, each idle frame, and each control frame to the least significant bits of L_V(S). RLP shall set the L_SEQ_HI field in a NAK control frame to the most significant bits of L_V(S). L_V(S) shall be incremented, Note that (N-) modulo 0 is equal to (N+0) modulo 0, and (N-0) modulo 0 is equal to (N+0) modulo 0. -

389 TIA/EIA/IS-0-A. 0 modulo 0, after generating each new data frame that contains a non-zero number of data octets. L_V(S) shall not be incremented after generating an idle or control frame. When RLP generates a new data frame, it shall perform the following: If a format B frame is used, RLP shall set the TYPE field as specified for a new data frame (see...) Otherwise, RLP shall set the REXMIT field to 0 and shall not generate segmented data frames. When RLP generates a retransmitted data frame (in response to a NAK control frame), it shall perform the following: If a format B frame is used, RLP shall set the TYPE field as specified for a retransmitted data frame (see...) Otherwise, RLP shall set the REXMIT field to. When the retransmitted data frame is supplied to the multiplex sublayer, if the size of the retransmitted data frame is less than or equal to the frame size allowed by the multiplex sublayer, an unsegmented data frame (see.. and..) shall be supplied. If the size of the retransmitted data frame exceeds the frame size allowed by the multiplex sublayer, RLP may segment the retransmitted data frame as specified in... L_V(S) = sequence number of the next data frame to be supplied to the multiplex sublayer frames supplied to the multiplex sublayer generated frames to be supplied to the multiplex sublayer Figure RLP Transmit Sequence Number 0 RLP shall maintain two -bit sequence number variables, L_V(R) and L_V(N) (see Figure ). L_V(R) contains the expected value of the RLP frame sequence number field in the next data frame to be received. The least significant bits of L_V(R) is denoted by V(R). L_V(N) contains the sequence number of the next needed data frame not received in sequence. -

390 TIA/EIA/IS-0-A. RLP shall process the received RLP frames every 0 ms. L_V(N) = sequence number of the next data frame needed for sequential delivery L_V(R) = sequence number of the next expected new data frame data frames received in sequence data frames received out of sequence buffer space for new or missing data frames Figure RLP Receive Sequence Number Variables 0 RLP shall provide two storage buffers for resequencing out-of-sequence data frames. One shall be used for the Forward Traffic Channel, and the other for the Reverse Traffic Channel. Each buffer shall each be able to store no fewer than the number of data frames specified in Table 0, with each frame being the maximum size allowed for the traffic type carrying RLP. It is conceivable that RLP frames can be delayed between a sending and receiving RLP, such that a group of frames sent together will not be received together. Detecting this is optional. However, procedures are provided for implementations that support delayed RLP frame detection. -

391 TIA/EIA/IS-0-A. Table 0 Minimum Resequencing Storage Buffer Size Number of Forward Supplemental Code Channels Supported by the Mobile Station Minimum Number of Data Frames in the Forward Resequencing Storage Buffer Number of Reverse Supplemental Code Channels Supported by the Mobile Station Minimum Number of Data Frames in the Reverse Resequencing Storage Buffer RLP shall maintain a NAK List. Each NAK List entry contains the -bit sequence number of a data frame for which a NAK control frame has been generated, and two associated timers (a NAK retransmission timer and a NAK abort timer). When a retransmitted data frame is received, RLP uses the NAK List to map the -bit sequence number of the retransmitted frame to the -bit sequence number of the missing data frame. For each valid received data frame containing a non-zero number of octets, RLP shall form L_SEQ from the SEQ field of the received frame as follows: If the received frame is a retransmitted data frame (i.e., the REXMIT field is set to or the TYPE field is set to 0 or in a Rate Format B frame), RLP shall search the NAK List, in order from oldest to newest entry, to find the entry whose least significant bits match the SEQ field of the received frame. RLP shall set L_SEQ to the -bit sequence number of the matching NAK List entry. If a matching NAK List entry is not found, RLP shall discard the frame. If the received frame is a new data frame (i.e., not a retransmitted data frame), then L_SEQ shall be computed from the following relation: L_SEQ = {L_V(R) + [ +SEQ - V(R)] mod } mod 0. 0 RLP shall process the received data frames in ascending order of L_SEQ as follows: 0 Each 0 ms RLP can receive at most RLP frames; thus L_V(R) can increase at most by each 0 ms. A computed value of L_SEQ that is greater than the maximum number that L_V(R) could have changed indicates that the frame has been delayed. For instance, to detect up to a 0 ms delay, L_SEQ should be compared to the sum of plus the value of L_V(R) 0 ms ago. -

392 TIA/EIA/IS-0-A. If the received frame is not a retransmitted data frame (i.e., the REXMIT field is set to 0 or the TYPE field is set to 00 or 0 in a Rate Format B frame), then RLP shall perform the following: 0 If RLP identifies the frame as a delayed RLP frame, it shall treat it as if it was a retransmitted data frame. If L_SEQ is equal to L_V(R), then: + If L_V(R) is equal to L_V(N), RLP shall increment L_V(N) and L_V(R), modulo 0, and shall pass all data octets in the data frame to the higher layer. + If L_V(R) is not equal to L_V(N), RLP shall increment L_V(R), modulo 0, and shall store the data frame in the resequencing buffer. If L_SEQ is greater than L_V(R), then: + RLP shall create a NAK List entry for each missing data frame from L_V(R) to (L_SEQ-) modulo 0, inclusive. Each NAK List entry shall contain the sequence number of one of the missing data frames. + RLP shall store the data frame in the resequencing buffer and set L_V(R) to (L_SEQ + ) modulo 0. If the received frame is a retransmitted data frame (i.e., the REXMIT field is set to or the TYPE field is set to 0 or in a Rate Format B frame), then RLP shall perform the following: 0 0 If L_SEQ is less than L_V(N), RLP shall discard the frame. If L_SEQ is greater than or equal to L_V(R), RLP shall discard the frame. If L_SEQ is greater than or equal to L_V(N) and less than L_V(R), then: + If the received frame is a segmented data frame, RLP shall perform reassembly as specified in... If, after reassembly, a complete data frame is available, the assembled data frame shall be treated as a retransmitted unsegmented data frame. + If the received frame is an unsegmented data frame, RLP shall store the data frame in the resequencing buffer. If L_SEQ is equal to L_V(N), RLP shall pass to the higher layer, in sequence number order, all data octets in all contiguous data frames in the resequencing buffer, from L_V(N) upward. RLP shall then set L_V(N) to (LAST + ) modulo 0, where LAST is equal to the sequence number of the last data frame whose data octets were passed to the higher layer. For each valid received idle frame, RLP shall compute L_SEQ from the following relation: L_SEQ = {L_V(R) + [ +SEQ - V(R)] mod } mod 0. Each 0 ms RLP can receive at most RLP frames; thus L_V(R) can increase at most by each 0 ms. A computed value of L_SEQ that is greater than the maximum number that L_V(R) could -0

393 TIA/EIA/IS-0-A. If RLP identifies the frame as a delayed RLP frame, it shall discard the frame. If L_SEQ is greater than L_V(R), RLP shall create a NAK List entry for each missing data frame from L_V(R) to (L_SEQ-) modulo 0, inclusive. Each NAK List entry shall contain the sequence number of one of the missing data frames. RLP shall then set L_V(R) to L_SEQ. 0 0 For each valid received NAK control frame, RLP shall compute L_SEQ from the following relation: L_SEQ = {SEQ + [L_SEQ_HI x )}. If L_SEQ is greater than L_V(R), RLP shall create a NAK List entry for each missing data frame from L_V(R) to (L_SEQ-) modulo 0, inclusive. Each NAK List entry shall contain the sequence number of one of the missing data frames. RLP shall then set L_V(R) to L_SEQ. If L_SEQ is less than L_V(R) and RLP has determined that frames are not being delayed, RLP shall perform the initialization/reset procedures specified in... or... RLP shall generate a copy of each requested data frame as a retransmitted data frame. If the NAK requests any sequence number greater than or equal to L_V(S), RLP shall perform the initialization/reset procedures specified in... or... After processing the received RLP frames, RLP shall process the NAK List entries as follows: If the received RLP frames included a valid idle frame or a valid new data frame, RLP shall perform the following for each entry for which RLP has included the missing data frame s sequence number in a NAK control frame: 0 If the entry s abort timer has been set but has not expired, RLP shall decrement the entry s abort timer. If this causes the timer to expire (i.e., its value reaches 0), RLP shall perform the following: + If RLP has received a retransmitted frame for the entry, RLP shall remove the entry from the NAK List. + If RLP has not received a retransmitted frame for the entry, RLP shall set L_V(N) to the sequence number of the next missing data frame, or to L_V(R) if there are no other missing data frames. RLP shall then pass to the higher layer, in sequence number order, all data octets in all contiguous data frames in the resequencing buffer whose sequence number is greater than have changed indicates that the frame has been delayed. For instance, to detect up to a 0 ms delay, L_SEQ should be compared to the sum of plus the value of L_V(R) 0 ms ago. This would indicate that the NAK process has fallen behind the sequence numbering by more than 0 frames. -

394 TIA/EIA/IS-0-A. 0 the missing data frame s sequence number and less than L_V(N). RLP shall then remove this entry. If the entry s retransmission timer has been set but has not expired, RLP shall decrement the entry s retransmission timer. If this causes the timer to expire (i.e., its value reaches 0), RLP shall perform the following: + If RLP has received a retransmitted frame for the entry, RLP shall remove the entry from the NAK List. + If RLP has not received a retransmitted frame for the entry, RLP shall include the missing data frame s sequence number in three NAK control frames. After sending the last NAK control frame, RLP shall set the entry s abort timer to an implementation dependent value greater than RLP_DELAY s. If an entry is a new NAK List entry (i.e., RLP has not yet included the missing data frame s sequence number in a NAK control frame), RLP shall perform the following: 0 If RLP has determined that RLP frames are being delayed, RLP should defer including the missing data frame s sequence number in a NAK control frame for an implementation dependent time, anticipating that the missing frame will arrive during that time. If RLP has received a delayed frame for the entry, RLP shall remove the entry from the NAK List. Otherwise, RLP shall include the missing data frame s sequence number in two NAK control frames. After sending the last NAK control frame, RLP shall set the entry s retransmission timer to an implementation dependent value greater than RLP_DELAY s. 0 Every 0 ms, if RLP supplies any non-blank RLP frame to the multiplex sublayer, RLP shall reset the idle timer to an implementation dependent value greater than RLP_DELAY s and set the idle frame transmission counter to 0. Otherwise, RLP shall decrement the idle timer. If this causes the idle timer to expire (i.e., its value reaches 0), RLP shall generate a control frame or an idle frame, shall reset the idle timer to an implementation dependent value greater than RLP_DELAY s, and shall increment the idle frame transmission counter. When the idle frame transmission counter reaches, the idle timer shall be disabled.... Encryption When RLP data encryption is negotiated, the Data octets of all generated data frames shall be encrypted, using the following procedures. It is recommended that this value be no less than, to account for buffering within the mobile and base station, and for possible segmentation of the retransmitted data frame. When RLP frames are carried as secondary traffic, an RLP idle frame is an RLP data frame with zero length (see...). -

395 TIA/EIA/IS-0-A Encryption mask generation shall be in accordance with the Data_Mask procedure defined in Common Cryptographic Algorithms, Revision A.. When a data frame is generated, RLP shall set the input parameters of the Data_Mask procedure, HOOK and LEN (see Interface Specification for Common Cryptographic Algorithms, Revision A. ) as follows: If the data frame is generated by a mobile station, RLP shall set HOOK equal to EXT_V(S) (see...), with the two most significant bits of HOOK set to 00. If the data frame is generated by a BS/MSC, RLP shall set HOOK equal to EXT_V(S) (see...), and shall then set the most significant bits of HOOK to 0. The length of the mask (LEN) shall be equal to the number of octets in the Data part of the data frame. RLP shall then execute the Data_Mask procedure. Each octet of the Data part of the data frame shall be combined with the mask by bitwise exclusive-or, combining successive data octets with mask octets. Retransmitted data frames shall be encrypted using the same mask as when first generated(i.e., each data octet in a retransmitted data frame shall have the same encrypted value as when originally encrypted). Retransmitted data frames shall be encrypted prior to segmentation.... Decryption For each data frame received, RLP shall form an extended sequence number EXT_SEQ whose most significant bits shall be set to the most significant bits of EXT_V(R) (see...) and whose least significant bits shall be set to L_SEQ. When an encrypted data frame is received, RLP shall set the input parameters of the Data_Mask procedure (see Interface Specification for Common Cryptographic Algorithms, Revision A. ) as follows: If the data frame is received from a mobile station, RLP shall set HOOK equal to EXT_SEQ, with the two most significant bits of HOOK set to 00. If the data frame is received from a BS/MSC, RLP shall set HOOK equal to EXT_SEQ, and shall then set the most significant bits of HOOK to 0. The length of the mask (LEN) shall be equal to the number of octets in the Data part of the data frame. RLP shall then execute the Data_Mask procedure. Each octet of the Data part of the data frame shall be combined with the mask by bitwise exclusive-or, combining successive data octets with mask octets. Segmented frames shall be reassembled prior to decrypting the data... Frame Validity Checks... Primary Traffic When RLP frames are carried as primary traffic, RLP shall discard as invalid any received frame for which any of the following applies: -

396 TIA/EIA/IS-0-A If the frame is a Fundamental RLP frame and either RLP is used with Multiplex Option,,,,,,, or, and the multiplex sublayer classifies the frame as category,,, 0 or, or RLP is used with Multiplex Option,,,, 0,,, or and the multiplex sublayer classifies the frame as category.. RLP shall count the frame as an erasure.. If the frame is a Supplemental RLP frame and RLP is used with Multiplex Option,,,,,,, 0,,,,,, or and the multiplex sublayer classifies the frame as category. RLP shall count the frame as an erasure.. For a control frame, if the FCS field does not check. For a Rate / or Rate / intersegment fill frame or for a Rate / idle frame, if the FCS field is not the correct value for the value of the SEQ field. RLP shall count the frame as an erasure.. If the frame s TYPE field value is not one of the values defined in.. If the frame s LEN field value is not within the range allowed in.. If the frame s CTL field value is not a value defined in.. For Rate / and Rate / frames, L_SEQ is not within the range from L_V(R) to (L_V(R)+E) modulo 0, inclusive, where E is a count of the number of consecutive frames RLP has counted as erasures. All other received frames shall be considered valid. If three consecutive identical Rate / frames arrive that are considered invalid as defined in () above, then: If L_SEQ is greater than L_V(R), RLP shall consider the third frame to be valid and shall process it as specified in... If L_SEQ is less than L_V(R), RLP shall perform the initialization/reset procedure specified in... or... RLP shall maintain a count E of the number of consecutive frames classified as erasures. When E exceeds, RLP shall perform the initialization/reset procedure specified in... or Secondary Traffic When RLP frames are carried as secondary traffic, RLP shall discard as invalid any received frame for which any of the following applies:. If the frame is a Fundamental RLP frame and either RLP is used with Multiplex Option,,,,,,, or, and the multiplex sublayer classifies the frame The erasures defined here help determine when RLP should perform initialization/reset. They should not be confused with TIA/EIA- frame erasures. -

397 TIA/EIA/IS-0-A as category 0, or RLP is used with Multiplex Option,,,, 0,,, or and the multiplex sublayer classifies the frame as category. RLP shall count the frame as an erasure.. If the frame is a Supplemental RLP frame and RLP is used with Multiplex Option,,,,,,, 0,,,,,, or and the multiplex sublayer classifies the frame as category. RLP shall count the frame as an erasure.. For a control frame, if the FCS field does not check. For a Rate / or Rate / intersegment fill frame, if the FCS field is not the correct value for the value of the SEQ field. RLP shall count the frame as an erasure.. If the RLP frame s TYPE field value is not one of the values defined in.. If the RLP frame s LEN field value is not within the range allowed in.. If the RLP frame s CTL field value is not a value defined in. All other received frames shall be considered valid. RLP shall maintain a count E of the number of consecutive frames classified as erasures as defined in (), (), and () above. When E exceeds, RLP shall perform the initialization/reset procedure specified in... or..... Segmentation of Retransmitted Data Frames The following procedures apply to the segmentation and reassembly of data frames. Segmentation may be necessary when a retransmitted data frame s size exceeds the frame size allowed by the multiplex sublayer when the retransmitted data frame is supplied to the multiplex sublayer. Segmented data frames are sent only as Fundamental RLP frames. RLP procedures below assure that no more than three data bearing segments are needed to retransmit a data frame by requiring all but the last segment to use at least a Rate / frame. A retransmitted data frame may be supplied in one, two or three segments. If the retransmitted data frame is supplied in a single segment, an unsegmented frame (see.. and..) is used. If the retransmitted data frame s size exceeds the frame size allowed by the multiplex sublayer when the retransmitted data frame is supplied to the multiplex sublayer, RLP should segment the frame. With the exception of intersegment fill frames, all RLP segmented data frames except the last segmented data frame shall be supplied using Rate / or larger RLP frames. When Rate Set is used, an intersegment fill frame (see...) can be supplied by the BS/MSC. When the intersegment fill frame is used the sequence number of an For Multiplex Option,,,,,,, or, the smallest available frame that carries data is Rate /, which is larger than Rate /. -

398 TIA/EIA/IS-0-A. intersegment fill frame shall be set equal to the sequence number of the data frame being retransmitted. RLP segments the frame using the following procedure: The first segment shall be generated using the First Segment frame type (see..). The segment should contain the maximum number of data octets that can fit in the frame size allowed by the multiplex sublayer. If RLP is used with Multiplex Option,,,, 0,,, or and less than a Rate / RLP frame is allowed, RLP shall perform the following: 0 If RLP cannot supply a Supplemental RLP frame to the multiplex sublayer, a Blank RLP frame should be supplied to the multiplex sublayer as the Fundamental RLP frame. Alternately, an intersegment fill frame (see...) may be supplied. If RLP can supply a Supplemental RLP frame to the multiplex sublayer, RLP should not begin segmentation of the data frame being retransmitted. After supplying a First Segment frame type, if the data frame s size needed to contain the remaining data octets exceeds the frame size allowed by the multiplex sublayer at the time the frame is supplied to the multiplex sublayer, RLP shall perform the following: 0 If RLP cannot supply a Supplemental RLP frame to the multiplex sublayer, the next segment shall be generated using the Second Segment frame type (see..). The segment should contain the maximum number of data octets that can fit in the frame size allowed by the multiplex sublayer. If RLP is used with Multiplex Option,,,, 0,,, or and less than a Rate / RLP frame is allowed, a Blank RLP frame should be supplied to the multiplex sublayer as the Fundamental RLP frame. Alternately, an intersegment fill frame (see...) may be supplied. If RLP can supply a Supplemental RLP frame to the multiplex sublayer, RLP should abort segmentation of the data frame being retransmitted. RLP should supply the entire data frame being retransmitted as a Supplemental RLP frame. 0 0 After supplying a First or Second Segment frame type, if the data frame s size needed to contain the remaining data octets is less than or equal to the frame size allowed by the multiplex sublayer at the time the frame is supplied to the multiplex sublayer, the next segment shall be generated using the Last Segment frame type (see..). After supplying a Second Segment frame type, if RLP is used with Multiplex Option,,,, 0,,, or and the data frame s size needed to contain the remaining data octets exceeds the frame size allowed by the multiplex sublayer at the time the frame is supplied to the multiplex sublayer, a Blank RLP frame should be supplied to the multiplex sublayer. Alternately, an intersegment fill frame (see...) may be supplied. Segmented data frames shall not be supplied with the LEN field equal to zero. -

399 TIA/EIA/IS-0-A. 0 0 The SEQ field of each segment shall be set to the least significant bits of the sequence number of the data frame being retransmitted. RLP may supply control frames between segments of a segmented data frame. If RLP is used with Multiplex Option,,,,,,, or, RLP may supply Rate / idle frames (see.) between segments of a segmented data frame. If RLP is used with Multiplex Option,,,, 0,,, or, RLP shall not supply Fundamental RLP idle frames between segments of a segmented data frame. RLP shall not supply other Fundamental data frames nor a segment with a different sequence number between segments of a segmented data frame. RLP shall begin frame reassembly on receipt of the first segment of a segmented data frame. When RLP is used with Multiplex Option,,,, 0,,, or, if RLP receives a valid an intersegment fill frame, RLP shall discard it. When RLP receives the last segment of the data frame, RLP shall process the data frame in the same manner as if it had been unsegmented. RLP shall discard, without further processing, any segmented data frame that is received under any of the following conditions: If a segment is received out of order (e.g., a last or second segment received without receiving a first segment). If an invalid Fundamental frame (see..) is received at any time between the first and last segments. If a Fundamental data frame or segment with a different sequence number is received between the first and last segments. When RLP is carried using Multiplex Option, if an idle frame (see.) is received at any time between the first and last segments. When a Supplemental frame with a different sequence number is received within the same 0 ms slot as a First or Last segment, the Supplemental frame shall not be discarded. -

400

401 TIA/EIA/IS-0-A. 0 RLP FRAME FORMATS For RLP control frames, RLP shall use the formats defined in.. For Fundamental RLP data frames whose rate is less than Rate, RLP shall use the formats in.. or... For Rate Fundamental or Supplemental RLP data frames, RLP shall use the formats in... For idle frames, RLP shall use the format in... Control Frames Control frames are distinguished by the CTL field. Control frames shall contain the least significant bits of L_V(S), in order that missing data frames may be quickly detected. RLP shall not increment L_V(S) after generating a control frame... SYNC, SYNC/ACK, and ACK Control Frames SYNC, SYNC/ACK, and ACK control frames are used during RLP initialization. Field Length (bits) SEQ CTL ENCRYPTION_MODE EM 0 or EXT_SEQ_M 0 or Padding_ Variable FCS Padding_ Variable 0 SEQ - Data frame sequence number. CTL - RLP frame type. For SYNC, SYNC/ACK, and ACK control frames, the CTL field is defined as follows: SYNC. Requests return of a control frame with the ACK bit set ACK. Acknowledges receipt of a control frame with the SYNC bit set. 0 - SYNC/ACK. Indicates both SYNC and ACK. ENCRYPTION_MODE - Encryption Mode. This field indicates the supported or desired user data encryption mode(s), set according to Table. EM - Encryption Request Indicator. -

402 TIA/EIA/IS-0-A (Default) Requests or Acknowledges no RLP data frame encryption (not supported or inactive). 0 Requests or Acknowledges RLP data frame encryption capability. EXT_SEQ_M - This field shall be included when the EM field is included. When the EM field is set to 0, this field shall be set to the most significant bits of EXT_V(S) (see...). Otherwise, this field shall be set to all zeros. Padding_ - Padding bits. As required to octet align the FCS field. These bits shall be set to 0. FCS - Frame Check Sequence. The contents shall be as generated by the -bit FCS polynomial specified in. of RFC. The FCS shall cover all fields before the FCS field. Padding_ - Padding bits. As required to fill the remainder of the frame. These bits shall be set to 0. Table User Data Encryption Modes Encryption Mode (binary) Meaning 00 Encryption not supported (default). 0 Enhanced encryption mode 0 Both basic and enhanced encryption modes. This value shall not be used in ACK control frames. Basic encryption mode. 0.. NAK Control Frame A NAK control frame requests the retransmission of one or more data frames. -

403 TIA/EIA/IS-0-A. Field Length (bits) SEQ CTL NAK_TYPE L_SEQ_HI If NAK_TYPE = 00, the following fields shall be: FIRST LAST If NAK_TYPE = 0, 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: Padding_ Variable FCS Padding_ variable 0 0 SEQ - Data frame sequence number. CTL NAK. Requests retransmission of data frames. NAK_TYPE - NAK type, as defined below: 00 - Requests retransmission of data frames numbered FIRST through LAST, inclusive. 0 - Requests retransmission of data frames as specified by the NAK Map(s). L_SEQ_HI - The most significant bits of L_V(S). FIRST - The -bit sequence number of the first data frame for which retransmission is requested. LAST - The -bit sequence number of the last data frame for which retransmission is requested. Padding_ - Padding bits. As required to octet align the FCS field. These bits shall be set to 0. FCS - Frame Check Sequence. The contents shall be as generated by the -bit FCS polynomial specified in. of RFC. The FCS shall cover all fields before the FCS field. Padding_ - Padding bits. As required to fill the remainder of the frame. These bits shall be set to 0. -

404 TIA/EIA/IS-0-A. 0 NAK_Map_Count - One less than the number of NAK Maps in this NAK control frame. NAK_Map_SEQ - The -bit sequence number of the first data frame for which retransmission is requested. NAK_Map - A bitmap identifying additional missing data frames for which retransmission is requested. The most significant bit corresponds to the data frame identified by (NAK_Map_SEQ +) modulo 0. Each less significant bit corresponds to the next sequential data frame. A bit set to indicates that the corresponding data frame is missing.. Data Frames.. Unsegmented Data Frames Unsegmented data frames carry a variable number of data octets, using a length field to indicate the number of octets. Field Length (bits) SEQ CTL REXMIT LEN Data Padding xlen Variable 0 SEQ - Data frame sequence number. See... CTL - For a frame carrying unsegmented data the CTL field shall be set to 0. REXMIT - Retransmitted frame indicator. This bit is set to when the frame is a retransmitted data frame. Otherwise, it is set to 0. LEN - Data length. May be any value in the range from 0 to the maximum allowable for the data frame. Maximum values of LEN (MAX_LEN) are given in Table. When LEN is zero, the frame is treated as an idle frame. Data - Data octets. Note that the most significant bit of the CTL field of a control frame and a segmented data frame is always set to. -

405 TIA/EIA/IS-0-A. Padding - Padding bits. As required to fill the remainder of the frame. These bits shall be set to 0. Table Values of the Maximum Allowable Data Length (MAX_LEN RLP Frame Type MAX_LEN Multiplex Options,,,,,,, and MAX_LEN Multiplex Options,,,, 0,,, and Primary Traffic Rate (Format A, see...) Rate / Rate / Not Used Secondary Traffic Rate (Format A, see...) 0 Rate / Rate / Rate / Rate / N/A Rate / N/A 0 Rate / Not Used Rate / N/A.. Segmented Data Frames Segmented data frames carry a variable number of data octets, using a length field to indicate the number of octets. This type of data frame shall only be used to carry retransmitted data frames (see..). 0 Field Length (bits) SEQ CTL LEN 0 or Data Padding 0 or xlen Variable -

406 TIA/EIA/IS-0-A. SEQ - Data frame sequence number. See... 0 CTL - For segmented data frames, the CTL field is defined as follows: First Segment. Contains the first LEN octets of the segmented data frame Second Segment. Contains the next LEN octets of the segmented data frame Last Segment. Contains the last LEN octets of the segmented data frame. 0 - Intersegment Fill Frame. When Multiplex Option,,,, 0,,, or is used, intersegment fill frames can be sent before or between segmented data frames (see..). Intersegment fill frames are not used with Multiplex Option,,,,,,, or. 0 LEN - Data length. When CTL is set to 000, 00, or 00, the LEN field may be any value in the range from to the maximum allowable for the data frame, or, whichever is less. Values of the maximum allowable data length (MAX_LEN) are given in Table. When CTL is set to 0 the LEN field shall not be included. Data - Data octets. When CTL is set to 000, 00, or 00, this field shall carry LEN Data octets. When CTL is set to 0 the Data field shall not be included. Padding - Padding bits. As required to fill the remainder of the frame. These bits shall be set to Rate / and Rate / Intersegment Fill Frames For Multiplex Option,,,, 0,,, or, Rate / primary traffic RLP frames and Rate / secondary traffic RLP frames may be intersegment fill frames. Field Length (bits) SEQ FCS ISF 0 SEQ - Data frame sequence number. See... FCS - Frame Check Sequence. This field is identical to the FCS field of an idle frame with matching SEQ field. See.. -

407 TIA/EIA/IS-0-A. ISF - Intersegment Fill frame indicator. The value indicates an intersegment fill frame... Rate RLP Frames For Rate RLP data frames, two special frame formats are used. Format A RLP data frames are described in... Format B RLP data frames are described in Rate RLP Frame Format A... Format A for Primary Traffic When RLP frames are carried as primary traffic by Multiplex Option,,,,,,, and, a format A frame is defined as follows: 0 Field Length (bits) Information TYPE Information - Control or data frame. Formatted according to the control and data frame formats described in.,.. and... TYPE - Frame type. The TYPE field shall be set to '00'. When RLP frames are carried as primary traffic by Multiplex Option,,,, 0,,, and, a format A frame is defined as follows: Field Length (bits) Information TYPE 0 Information - Control or data frame. Formatted according to the control and data frame formats described in.,.. and... TYPE - Frame type. The TYPE field shall be set to Format A for Secondary Traffic When RLP frames are carried as secondary traffic by Multiplex Option,,,,,,, and, a format A frame is defined as follows: -

408 TIA/EIA/IS-0-A. Field Length (bits) Information TYPE Information - Control or data frame. Formatted according to the control and data frame formats described in.,.. and... TYPE - Frame type. The TYPE field shall be set to '00'. When RLP frames are carried as secondary traffic by Multiplex Option,,,, 0,,, and, a format A frame is defined as follows: Field Length (bits) Information 0 TYPE 0 Information - Control or data frame. Formatted according to the control and data frame formats described in.,.. and... TYPE - Frame type. The TYPE field shall be set to Rate RLP Data Frame Format B... Format B for Primary Traffic When RLP frames are carried as primary traffic by Multiplex Option,,,,,,, and, a format B frame is defined as follows: Field Length (bits) SEQ Data 0 TYPE 0 SEQ - Data frame sequence number. See.. and... Data - Data octets. This field shall contain 0 octets of data. TYPE - Frame type. The TYPE field is set to 00 for a new data frame and set to 0 for a retransmitted data frame. -

409 TIA/EIA/IS-0-A. When RLP frames are carried as primary traffic by Multiplex Option,,,, 0,,, and, a format B frame is defined as follows: Field Length (bits) SEQ Data TYPE 0 SEQ - Data frame sequence number. See.. and... Data - Data octets. This field shall contain octets of data. TYPE - Frame type. The TYPE field is set to 0 for a new data frame and set to for a retransmitted data frame.... Format B for Secondary Traffic When RLP frames are carried as secondary traffic by Multiplex Option,,,,,,, and, a format B frame is defined as follows: Field Length (bits) SEQ Data TYPE 0 SEQ - Data frame sequence number. See.. and... Data - Data octets. This field shall contain octets of data. TYPE - Frame type. The TYPE field is set to for a new data frame and set to for a retransmitted data frame. When RLP frames are carried as primary traffic by Multiplex Option,,,, 0,,, and, a format B frame is defined as follows: Field Length (bits) SEQ Data TYPE -

410 TIA/EIA/IS-0-A. SEQ - Data frame sequence number. See.. and... Data - Data octets. This field shall contain octets of data. TYPE - Frame type. The TYPE field is set to for a new data frame and set to 0000 for a retransmitted data frame. 0. Idle Frames For Multiplex Option,,,,,,, and, Rate / RLP frames are idle frames. For Multiplex Option,,,, 0,,, and, Rate / primary traffic RLP frames and Rate / secondary traffic RLP frames may be idle frames. Higher rate RLP data frames with zero length (LEN = 0) (see..) are also idle frames. Field Length (bits) SEQ FCS Padding 0 or 0 SEQ - Data frame sequence number. See... FCS - Frame Check Sequence based on a modified Nordstrom-Robinson code. Let the sequence number to be coded be denoted as ( X X X X X X X X 0 ) Let the FCS be denoted as ( Y Y Y Y Y Y Y Y 0 ) The FCS is generated as follows: Y 0 = X X X 0 X X ( X 0 X ) ( X X X X ) ( X X ) ( X X ) Where denotes modulo- addition. Code bits Y through Y are found by cyclically shifting X 0 through X. In other words, X ( i + j)mod is substituted for X i in the generating equation for Y j. Y is a parity bit over the previous bits. The final step in generating the FCS is to complement the last three bits. A table specifying the code is provided in Table. -0

411 TIA/EIA/IS-0-A. Pad - Padding bits. As required to fill the remainder of the frame. These bits shall be set to 0. Table presents the modified Nordstrom Robinson code used to protect Rate / and Rate / idle frames. In Table, the most significant byte in a word is the SEQ value to be protected and the least significant byte is the FCS. All numbers are hexadecimal. -

412 TIA/EIA/IS-0-A Table Modified Nordstrom Robinson Code 000 0f 0ee 0 0 a0c c0 e0b 0d ab a ce efd 0a0 d b d df a c ea 0a be d ac cf e 0c a f b a cd ee0 0f a b c 00 ada cc e 0c c f 0 ab ca ee 0 0 eb ec a0f c e 0a 0 d a e af c ed 0c cf b a ab0 cc e0 0a a ac a0e a0 aaea cabc ea 0bf b b0 be b abc cbf ebb 0c cfc c c ce ac ccfb ec 0de d d0b dd dd ad cd edae 0eaf eb e eb ed0 ae ce eecd 0f f fde fd fa aff cfa ef 0bd 0e 00 0c 0c b0 d0 f0ba e db f d b da f0 b e bf de fd e 0 c b bb d0 fce 0 a b bef ddc f0 e f f bc da f fa f ac b d0 fd dd c0 a ba dbf f b a f0 bd df fc c fe b0a d fe acc a a aff ab ba daa fa0 bf bd baa b b0 bbad dbd fb cd c0d ce cca ca bc dc fcb d dbb ded d0 d bdc dd fdf e0 ee e e ed bee dee feb fb fe f f fcb bf df0c fff -

413 Data Service Options for Spread Spectrum Systems: High Speed Packet Data Services TIA/EIA/IS-0-A. (PN-.) Ballot Resolution Version March,

414 Copyright TIA

415 TIA/EIA/IS-0-A. CONTENTS INTRODUCTION...-. General Description...-. Terms...-. References...-. Overview of Packet Data Service Packet Data Service Types and Configurations Protocol Options Relay Layer Rm Interface Protocol Option Network Layer Rm Interface Protocol Option Packet Data Protocol States IWF Link Layer Connection States Mobile Station Packet Data Service States BS/MSC Packet Data Service States...- RELAY LAYER...-. Introduction...-. Um Interface Requirements RLP Requirements Service and Call Control Procedures Mobile Station Procedures Packet Data Service Control Procedures Inactive State Active State Packet Data Service Call Control Function Null State Initialization/Idle State Initialization/Traffic State Connected State Dormant/Idle State Dormant/Traffic State Reconnect/Idle State Reconnect/Traffic State BS/MSC Procedures...- i

416 TIA/EIA/IS-0-A. CONTENTS Packet Data Service Control Procedures Inactive State Active State Packet Data Service Call Control Function Null State IWF Initiated Link Layer Connection Reactivation Mobile Station Originated Link Layer Connection Activation Mobile Station Negotiated Link Layer Connection Activation IWF Link Layer Closure IWF Transfer Paging State Initialization/Idle State Initialization/Traffic State Connected State Initialization and Connection of Packet Data Service Options Mobile Station Procedures BS/MSC Requirements Optional Zone-Based Registration or Reconnection Optional Reconnect After Hard Handoff Optional Packet Data Dormant Timer Control Optional Packet Zone Reconnection Control High Speed Operation Mobile Station Procedures for Reverse High Speed Operation Reverse High Speed Operation Messages General Message Format and Coding Reverse Bandwidth Request Message Request Type Maximum Number of Reverse Supplemental Code Channels Information Element Preferred Number of Reverse Supplemental Code Channels Information Element Requested Duration Information Element...- ii

417 TIA/EIA/IS-0-A. CONTENTS 0... Additional SO Request Information Element Priority Information Element...-. L Interface Logical Connections Mobile Data...- LINK LAYER...-. Link Layer Protocols...-. Link Layer Connections IWF Link Layer Connection Opening IWF Link Layer Connection Maintenance IWF Link Layer Connection Closure BS/MSC Closure IWF Closure TE Closure MT Closure...- NETWORK LAYER...-. Internet Protocol Support...-. ISO Protocol Support...-. CDPD Application Support...- iii

418 TIA/EIA/IS-0-A. FIGURES Figure Relay Layer Rm Interface Protocol Option...- Figure Network Layer Rm Interface Protocol Option...- Figure Packet Data Service Call Control States in the Mobile Station...- Figure Packet Data Service Call Control States in the BS/MSC TABLES Table Valid Service Configuration Attributes for Service Options and...- Table Valid Service Configuration Attributes for Service Options and...- Table Valid Service Configuration Attributes for Service Options and...- Table Valid Service Configuration Attributes for Service Options and...- Table ORDQ Format and Type-Specific Fields for Zone-Based Registration/Reconnection...- Table Zone Based Registration/Reconnection Control Field...- Table ORDQ Format and Type-Specific Fields for Reconnect After Hard Handoff...-0 Table Reconnect After Hard Handoff Control Field...- Table Type-Specific Fields for Data Dormant Timer Control...- Table 0 Dormant Timer Control Field...- Table Minimum Value of Mobile Station Dormant Timer...- Table Type-Specific Fields for Packet Connection Control...- Table Packet Zone Connection Control Field...- Table Type-Specific Fields for Packet Zone Connection Response...- Table Reverse Bandwidth Request Message Contents...- Table Requesting Service Type...- iv

419 TIA/EIA/IS-0-A INTRODUCTION. General Description This chapter defines requirements for support of high speed packet data transmission capability on TIA/EIA--B spread spectrum systems. Packet data transmission is supported on TIA/EIA--B Traffic Channels using primary or secondary traffic. For packet data transmission using TIA/EIA--B Traffic Channels, the Radio Link Protocol Type specified in IS-0-A. is used. This standard specifies a packet data bearer service for communication between terminal equipment and a packet interworking function (IWF) via a base station/mobile switching center (BS/MSC). It provides procedures that can apply to multiple packet data services, e.g., CDPD and Mobile-IP. Packet data service options provide a means of establishing and maintaining Traffic Channels for packet data service. Service Options,,, and 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. and.). Service Options,,, and are used to request packet data service through an IWF supporting CDPD data services over a PPP interface (see.). Additional packet data service options may be defined in future revisions to select other types of IWF resources or services.. Terms Base Station (BS). A fixed station used for communicating with mobile stations. Depending upon the context, the term base station may refer to a cell, a sector within a cell, or other part of the cellular system. BS. See base station. BS/MSC. The base station and mobile switching center considered as a single functional entity. CDPD. Cellular Digital Packet Data. CLNP. Connectionless Network Protocol (See ISO -). Data Circuit-Terminating Equipment (DCE). A DCE connects a DTE to the PSTN. A typical DCE would be a V-series modem. DTE. Data Terminal Equipment. Forward Supplemental Code Channel. A Supplemental Code Channel operating in the forward direction. Fundamental Code Channel. A portion of a Traffic Channel (Forward or Reverse) that is always present, and carries primary traffic, secondary traffic, signaling, and power control information. GHDM. General Handoff Direction Message (see... of TIA/EIA--B). IWF. Interworking Function (see..). IP. Internet Protocol. -

420 TIA/EIA/IS-0-A. 0 0 IPCP. Internet Protocol Control Protocol (see RFC ). LCP. PPP Link Control Protocol (see RFC ). Mobile IP. Mobile Internet Protocol (see RFC 00). Mobile Station. A 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. MT0. Mobile Termination 0 (see..). MT. Mobile Termination (see..). OSINLCP. OSI Network Layer Control Protocol (see RFC ). PPDN. Public Packet Data Network. PPP. Point-to-Point Protocol (see RFC ). PSTN. Public Switched Telephone Network. Reverse Supplemental Code Channel. A Supplemental Code Channel operating in the reverse direction. RFC. Request for Comments. The generic name of a specification developed by the Internet Engineering Task Force (IETF). RLP. Radio Link Protocol. SCAM. Supplemental Channel Assignment Message (see... of TIA/EIA--B). SCRM. Supplemental Channel Request Message (see... of TIA/EIA--B). SLIP. Serial Line IP. Supplemental Code Channel. A portion of a Traffic Channel (Forward or Reverse) that is optionally present, and carries either primary or secondary traffic. TCP. Transmission Control Protocol. TE. Terminal Equipment (see..). Traffic Channel. A 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.. References 0 ANSI/TIA/EIA- Inband DCE Control for Asynchronous DTE DCE Interfaces. Common Cryptographic Algorithms Revision A.. An ITAR controlled document subject to restricted distribution. Contact the Telecommunications Industry Association, Washington, D.C., April,. -

421 TIA/EIA/IS-0-A. EIA/TIA--E EIA/TIA-0 Interface Specification for Common Cryptographic Algorithms Revision A, Telecommunications Industry Association, Washington, D.C., December,. Interface Between DTE and DCE Employing Serial Binary Data Interchange. Serial Asynchronous Automatic Dialing and Control. ISO - Information processing systems -- Data communications -- Protocol for providing the connectionless-mode network service ISO/IEC TR-0 RFC RFC 0 RFC RFC RFC RFC 0 RFC RFC RFC 00 RFC 00 TIA/EIA--B TIA/EIA/IS- TIA/EIA/IS- TSB TSB Information technology -- Telecommunications and information exchange between systems -- Protocol identification in the network layer. Internet Protocol. Nonstandard for transmission of IP datagrams over serial lines: SLIP. Compressing TCP/IP Headers for Low-Speed Serial Links. The PPP Internet Protocol Control Protocol (IPCP). The PPP OSI Network Layer Control Protocol (OSINLCP). PPP LCP Extensions. The Point-to-Point Protocol (PPP). PPP in HDLC-like Framing. Assigned Numbers. IP Mobility Support. Mobile Station-Base Station Compatibility Standard for Dual- Mode Spread Spectrum System. Data Services Interworking Function Interface Standard for Wideband Spread Spectrum Digital Cellular System. Cellular Digital Packet Data System Specification. Note that this is a series of standards, each of which begins with the designation TIA/EIA/IS-, and ends with partnumber, where partnumber identifies the particular standard within the series. Administration of Parameter Value Assignments for TIA/EIA Wideband Spread Spectrum Standards. Telecommunications Systems Bulletin: Support for. kbps Data Rate and PCS Interaction for Wideband Spread Spectrum Cellular Systems. -

422 TIA/EIA/IS-0-A Overview of Packet Data Service.. Packet Data Service Types and Configurations Packet Data Service can be of two types. Type Packet Data Service provides packet data connections based on Internet and ISO standard protocol stacks, while Type Packet Data Service provides packet data connections based on CDPD protocol stacks. Type Packet Data Service includes service option connections using Service Options,,, or. Type Packet Data Service includes service option connections using Service Options,,, or... Protocol Options This standard provides the requirements for communication protocols on the links between a mobile station and IWF, including requirements for the R m, U m and L interfaces. The Relay Layer provides lower layer communication and packet framing between the entities of the packet data service reference model. Over the R m interface between the TE and the MT, the Relay Layer is a simple EIA/TIA--E interface. Over the U m interface, the Relay Layer is a combination of RLP Type (defined in IS-0-A.) and the TIA/EIA/-B protocols. On the L interface, the Relay Layer uses the protocols defined in TIA/EIA/IS-. The two options for packet protocol stacks are presented in... and Relay Layer R m Interface Protocol Option The Relay Layer R m interface protocol option supports TE applications in which the TE is responsible for all aspects of packet data service mobility management and network address management (e.g., IPCP and the CDPD registration and authentication protocols). For the Relay Layer R m interface protocol option, the packet data service protocol stack is as shown in Figure. -

423 TIA/EIA/IS-0-A. Mobile Station TE MT BS/MSC IWF Upper Protocol Layers Upper Protocol Layers Network Layer Network Layer Protocols Network Layer Protocols Link Layer PPP PPP Relay Layer EIA- EIA- RLP IS- RLP IS- Relay Layer Relay Layer R m U m L Figure Relay Layer R m Interface Protocol Option 0 In this protocol option, the Link Layer is implemented using PPP, as defined in RFC. When using the Relay Layer R m interface protocol option, the Link Layer connection is between the TE and the IWF. The Network Layer includes protocols, such as IP and CLNP, and packet data network registration and authentication protocols, such as MNRP. Recommendations for the use of certain specific protocols are given in.... Network Layer R m Interface Protocol Option The Network Layer R m interface protocol option supports TE applications in which the MT is responsible for all aspects of packet mobility management and network address management (e.g., IPCP and the CDPD registration and authentication protocols). For the Network Layer R m interface protocol option, the packet data service protocol stack is as shown in Figure. -

424 TIA/EIA/IS-0-A. Mobile Station TE MT BS/MSC IWF Upper Protocol Layers Upper Protocol Layers Network Layer IP or CLNP IP or CLNP Network Layer Protocols Network Layer Protocols Link Layer PPP or SLIP PPP or SLIP PPP PPP Relay Layer EIA- EIA- RLP IS- RLP IS- Relay Layer Relay Layer R m U m L Figure Network Layer R m Interface Protocol Option 0 0 In this protocol option, there are independent Link Layer connections between the TE and the MT, and between the MT and the IWF. The IWF Link Layer (between the MT and the IWF) is implemented using the Internet Point-to-Point Protocol (PPP) defined in RFC. The R m Link Layer (between the MT and the TE) should be implemented using the Internet Point-to-Point Protocol (PPP) defined in RFC. Alternatively, the SLIP protocol as defined in RFC 0 may be used between the MT and the TE to support the IP network layer protocol. For this R m interface protocol option, the Network Layer also provides independent services between the TE and the MT, and between the MT and the IWF. The TE includes routing protocols and operates as if locally connected to a network routing server. The MT includes both routing and packet data network registration and authentication protocols... Packet Data Protocol States... IWF Link Layer Connection States The IWF and the mobile station use a Link Layer connection to transmit and receive packet data. The IWF Link Layer connection is opened when a packet data service option is first connected. Once an IWF Link Layer connection is opened, bandwidth (in the form of Traffic Channel assignment) is allocated to the connection on an as-needed basis. -

425 TIA/EIA/IS-0-A The IWF Link Layer connection can be in any of the following states: Closed: The IWF Link Layer connection is closed when the IWF has no Link Layer connection state information for the mobile station. Opened: The IWF Link Layer connection is opened when the IWF has Link Layer connection state information for the mobile station. The opened state has two substates: Active: An opened IWF Link Layer connection is active when there is an L interface virtual circuit for the mobile station and the mobile station is on a Traffic Channel with a packet data service option connected. Dormant: An opened IWF Link Layer connection is dormant when there is no L interface virtual circuit for the mobile station, and the mobile station is not on a Traffic Channel with a packet data service option connected. The BS/MSC and IWF maintain the state of the Link Layer connection as defined above. The mobile station maintains the state of the PPP Link Control Protocol (LCP), and manages the IWF Link Layer connection using the LCP opening and closing procedures defined in RFC. When the IWF Link Layer Connection is dormant and either the Mobile Station or the BS/MSC has data to send, it is not necessary to re-open the Link Layer Connection or to re-initialize any upper layer protocols, provided the packet data service type has not changed since the link layer last entered the Dormant State. Thus Mobile Stations and BS/MSCs complying with this standard can freely mix packet data service requests using any supported rate set within a service type.... Mobile Station Packet Data Service States Packet data service processing in the mobile station consists of the following states. Requirements for the transitions between these states are given in... Inactive State - In this state, the mobile station does not provide packet data service. Active State - In this state, the mobile station provides packet data service. The mobile station performs the packet data service call control function described in... As illustrated in Figure, the packet data service call control function consists of the states listed below: Null State - The packet data service call control function is in this state when packet data service has not been activated. Initialization/Idle State - In this state, the mobile station attempts to establish a Traffic Channel for the purpose of initiating packet data service. Initialization/Traffic State - In this state, the mobile station is communicating with the BS/MSC on a Traffic Channel, and attempts to connect a packet data service option for the purpose of initiating packet data service. Connected State - In this state, a packet data service option is connected. The mobile station can transfer packet data. -

426 TIA/EIA/IS-0-A. 0 Dormant/Idle State - In this state, the mobile station is not on a Traffic Channel. The mobile station cannot transfer packet data. Dormant/Traffic State - In this state, the mobile station is communicating with the BS/MSC on a Traffic Channel, but the packet data service option has been disconnected. The mobile station cannot transfer packet data. Reconnect/Idle State - In this state, the mobile station attempts to establish a Traffic Channel. Reconnect/Traffic State - In this state, the mobile station is communicating with the BS/MSC on a Traffic Channel, and attempts to connect a packet data service option. -

427 TIA/EIA/IS-0-A. Service option rejected or release; deactivates packet data service Receives release, reorder, etc.; deactivates packet data service Initialization/Idle State Traffic Channel is initialized; requests packet service option Service is activated, mobile station is not on a Traffic Channel; sends origination Null State Service is activated, mobile station is on a Traffic Channel; requests packet service option Traffic Channel is initialized; requests packet service option Service option rejected; deactivates packet data service Reorder Reconnect/Idle State Release Initialization/ Traffic State Reconnect/Traffic State Service option connected Service option connected Connected State Release Note: not all state transitions are shown. Service option connected Service option disconnected Dormant/Traffic State Traffic Channel initialized Release Dormant/Idle State Data to send; requests packet service option Serving system change or data to send; sends origination Figure Packet Data Service Call Control States in the Mobile Station 0... BS/MSC Packet Data Service States Packet data service processing in the BS/MSC consists of the following states. Requirements for the transitions between these states are given in... Inactive State - In this state, the BS/MSC does not provide packet data service to the mobile station. -

428 TIA/EIA/IS-0-A. 0 Active State - In this state, the BS/MSC provides packet data service to the mobile station. The BS/MSC performs the packet data service call control function described in... As illustrated in Figure, the packet data service call control function consists of the following states: Null State - In this state, the BS/MSC has no connection of a packet data service option to the mobile station. Paging State - In this state, the IWF has requested that the BS/MSC connect a packet data service option to the mobile station for the delivery of packet data, and the BS/MSC pages the mobile station. Initialization/Idle State - In this state, the BS/MSC is awaiting initialization of a Traffic Channel with the mobile station. Initialization/Traffic State - In this state, the mobile station is on a Traffic Channel. The BS/MSC awaits connection of a packet data service option. Connected State - In this state, a packet data service option has been connected. Packet data is exchanged with the mobile station. -0

429 TIA/EIA/IS-0-A. Receives Link Layer reactivation request, mobile station is not on Traffic Channel; pages mobile station Service option rejected; requests IWF Link Layer closure Paging State Receives page response; assigns Traffic Channel Receives origination; initiates Link Layer open or reactivation Null State Service option rejected; requests IWF Link Layer closure Initialization/Idle State Receives service option request for packet service from mobile station is on Traffic Channel or receives Link Layer reactivation request while mobile station is on Traffic Channel; negotiates packet service option Service option rejected; requests IWF Link Layer closure Traffic Channel initialized; negotiates packet service option Initialization/Idle State Note: not all state transitions are shown Service option connected Connected State Service option disconnected Figure Packet Data Service Call Control States in the BS/MSC -

430 TIA/EIA/IS-0-A RELAY LAYER. Introduction The Relay Layer spans across the R m, U m and L interfaces. See Section. of IS-0-A. for R m interface requirements. U m interface requirements and L interface requirements for the Relay Layer are described in the following sections. RLP can be carried either as primary traffic or as secondary traffic. The mobile station and the BS/MSC shall support the physical layer, multiplex options, radio link management, and call control protocols as defined in TIA/EIA--B. At the L interface, the BS/MSC and the IWF can use the protocols recommended in TIA/EIA/IS- for transport of end-user data and control information.. U m Interface Requirements.. RLP Requirements At the U m interface, the mobile station and the BS/MSC shall use the Radio Link Protocol Type defined in IS-0-A.. In this specification, the Radio Link Protocol Type will be called simply RLP. For Service Options,,, and, the mobile station may support RLP user data frame encryption. For Service Options,,, and, the mobile station shall support RLP user data frame encryption... Service and Call Control Procedures... Mobile Station Procedures The packet data service states for mobile stations are described in... Mobile station states are described in. of TIA/EIA--B. When power is applied to the mobile station, the packet data service shall enter the Inactive State and the packet data service call control function shall enter the Null State.... Packet Data Service Control Procedures... Inactive State When the packet data service is in the Inactive State, the mobile station does not provide packet data service. The means for determining when the packet data service enters the Active State are left to the mobile station manufacturer.... Active State When the packet data service is in the Active State, the mobile station provides packet data service. While the packet data service is in the Active State, the service negotiation procedures described in... and... of TIA/EIA--B can be used to simultaneously connect other service options as primary or secondary traffic. This is intended, for example, to permit the simultaneous and independent connection and disconnection of voice and packet data services. Complete mobile station procedures for invoking and -

431 TIA/EIA/IS-0-A controlling such simultaneous connections require further study, and are left for future revisions of this standard. Until other procedures are defined, mobile stations can connect a voice call while the packet data service call control function is in the Connected State by releasing the Traffic Channel, sending an Origination Message containing the voice service option and the dialed digits, and performing service negotiation to connect a service configuration containing voice as primary traffic and packet data as secondary traffic. While voice and packet data service options are connected, the mobile station should process all received and transmitted service-related signaling messages, such as Flash With Information and Alert With Information, as pertaining only to the voice service. Mobile stations can disconnect the voice service option by releasing the Traffic Channel, after which the packet data service call control function automatically reconnects the packet data service option as described in Packet Data Service Call Control Function... Null State The mobile station packet data service call control function is in the Null State whenever the packet data service is in the Inactive State. If the packet data service enters the Active State, the mobile station shall perform the following: If the Network Layer R m interface protocol option is selected, and the R m interface Link Layer is implemented using PPP, the MT shall initiate PPP configuration on the R m interface, using the procedures defined in RFC. If the mobile station is in the Mobile Station Idle State, the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA--B. The mobile station should include the packet data service option in the SERVICE_OPTION field of the Origination Message (see... of TIA/EIA--B). The packet data service call control function shall enter the Initialization/Idle State with a packet origination indication. If the mobile station is in the Mobile Station Control on the Traffic Channel State, the mobile station shall initiate connection of the packet data service option, as described in... The packet data service call control function shall enter the Initialization/Traffic State. If the mobile station is in any other state or substate, the packet data service call control function shall enter the Initialization/Idle State with a mobile station wait indication.... Initialization/Idle State While the packet data service call control function is in the Initialization/Idle State, the mobile station shall perform the following: If the mobile station enters the Mobile Station Control on the Traffic Channel State, the mobile station shall initiate connection of the packet data service option, as -

432 TIA/EIA/IS-0-A described in... The packet data service call control function shall enter the Initialization/Traffic State. If the Initialization/Idle State was entered with a mobile station wait indication, and the mobile station enters the Mobile Station Idle State, the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA--B. The mobile station should include the packet data service option in the SERVICE_OPTION field of the Origination Message (see... of TIA/EIA--B). The packet data service call control function shall re-enter the Initialization/Idle State with a packet origination indication. If the Initialization/Idle State was entered with a packet origination indication, the packet data service shall enter the Inactive State if either of the following occur: The mobile station enters the Mobile Station Initialization State; or The mobile station exits the System Access State and enters any state other than the Mobile Station Control on the Traffic Channel State. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State.... Initialization/Traffic State While the packet data service call control function is in the Initialization/Traffic State, the mobile station shall perform the following: The mobile station packet data service call control function shall perform service negotiation as described in... of TIA/EIA--B, to connect the requested service configuration. If the packet data service option is connected, the packet data service call control function shall enter the Connected State when the mobile station enters the Conversation Substate. If the mobile station exits the Mobile Station Control on the Traffic Channel State, the packet data service shall enter the Inactive State and the packet data service call control function shall enter the Null State. If the packet data service option cannot be connected, the packet data service shall enter the Inactive State. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State. If no other service option is connected, the mobile station shall send a Release Order and shall enter the Release Substate of the Mobile Station Control on the Traffic Channel State.... Connected State When the packet data service call control function enters the Connected State, the mobile station begins RLP initialization (see Section.. of IS-0-A.). While in the Connected State, the mobile station shall perform the following: -

433 TIA/EIA/IS-0-A If the mobile station exits the Mobile Station Control on the Traffic Channel State, the mobile station shall perform the following: If the mobile station has data to send, the packet data service call control function shall enter the Reconnect/Idle State with a channel loss indication. Otherwise, the packet data service call control function shall enter the Dormant/Idle State. The mobile station shall maintain a packet data inactivity timer. The value of this timer shall not be less than 0 seconds. The timer should be reset whenever a non-idle RLP data frame is sent or received. If the packet data inactivity timer expires, the mobile station should disconnect the packet data service option. To disconnect the packet data service option, the mobile station shall perform the following: If the packet data service option is the only connected service option, the mobile station shall send a Release Order and enter the Release Substate of the Mobile Station Control on the Traffic Channel State. Otherwise, the mobile station shall negotiate a service configuration that does not include the packet data service option. If the packet data service option is disconnected and the mobile station remains on the Traffic Channel, the packet data service call control function shall enter the Dormant/Traffic State. If the packet data service enters the Inactive State, the mobile station shall perform the following: If the Network Layer R m interface protocol option is selected, the MT should close the IWF Link Layer connection (see...) before disconnecting the packet data service option. If the packet data service option is the only connected service option, the mobile station shall send a Release Order and enter the Release Substate of the Mobile Station Control on the Traffic Channel State. Otherwise, the mobile station shall negotiate a service configuration that does not include the packet data service option. The packet data service call control function shall enter the Null State. When the amount of user data in the mobile station reaches an implementation defined threshold, the mobile station may request reverse high speed operation (see..).... Dormant/Idle State While the packet data service call control function is in the Dormant/Idle State, the mobile station shall perform the following: -

434 TIA/EIA/IS-0-A If the mobile station enters the Mobile Station Control on the Traffic Channel State, the packet data service call control function shall enter the Dormant/Traffic State. The mobile station shall attempt to reconnect the packet data service option, using the procedures specified below, if any of the following occurs: The packet data service has data to send; or The mobile station is in the Mobile Station Idle State and detects that the SID or NID of the serving system has changed; or The mobile is in the Mobile Station Idle State and detects a non-zero PACKET_ZONE_ID S that is not currently stored in its packet data zone identifier list (see 0); or The mobile station enters the Mobile Station Idle State after a call release, and the SID or NID of the serving system at the start of the call is unknown, or the SID or NID of the serving system after call release is different from the SID or NID of the serving system at the start of the call. The mobile station shall maintain a packet data dormant timer controllable by the BS/MSC (see..). The default value for this timer shall be 0 seconds. The timer shall be reset upon entering the Dormant/Idle State. The mobile station shall delay any attempt to send an Origination Message requesting a packet data service option until the expiration of this timer. If the mobile station attempts to reconnect the packet data service option while the packet data service call control function is in the Dormant/Idle State, the mobile station shall perform the following: If the mobile station is in the Mobile Station Idle State, the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA--B. The mobile station should include the packet data service option in the SERVICE_OPTION field of the Origination Message (see... of TIA/EIA--B). The packet data service call control function shall enter the Reconnect/Idle State with a packet origination indication. If the mobile station is in any other state or substate, the packet data service call control function shall enter the Reconnect/Idle State with a mobile station wait indication. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State.... Dormant/Traffic State While in the Dormant/Traffic State, the packet data service call control function shall perform the following: The mobile station can enter the Mobile Station Control on the Traffic Channel State as a result of a page from the BS/MSC or an origination of a service by the mobile station. -

435 TIA/EIA/IS-0-A If the packet data service option is connected, the packet data service call control function shall enter the Connected State when the mobile station enters the Conversation Substate. If the mobile station exits the Mobile Station Control on the Traffic Channel State, the packet data service call control function shall enter the Dormant/Idle State. If the packet data service has data to send, or the mobile station has detected a change in the serving system SID or NID, or a non-zero PACKET_ZONE_ID S that is not currently stored in its packet data zone identifier list (see 0) since the packet data service call control function last entered the Dormant/Traffic State, the mobile station shall perform the following: If the service configuration of the mobile station permits connecting a packet data service, the mobile station shall initiate connection of the packet data service option. The packet data service call control function shall enter the Reconnect/Traffic State. If the service configuration of the mobile station does not permit connecting a packet data service option, the mobile station may attempt to initiate connection of a packet data service option. If the mobile station attempts to initiate connection of the packet data service option, the mobile station packet data service call control function shall enter the Reconnect/Traffic State. If the mobile station does not initiate connection of the packet data service option, either the packet data service call control function may remain in the Dormant/Traffic State, or the packet data service may enter the Inactive State. If the mobile station successfully completes a hard handoff (see... of TIA/EIA--B) in which the Active Set or frequency assignment changes, and the Reconnect After Hard Handoff feature is enabled (see..), the mobile station shall initiate connection of the packet data service option, as described in... The packet data service call control function shall enter the Reconnect/Traffic State. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State.... Reconnect/Idle State While the packet data service call control function is in the Reconnect/Idle State, the mobile station shall perform the following: If the mobile station enters the Mobile Station Control on the Traffic Channel State, the mobile station shall initiate connection of the packet data service option, as described in... The packet data service call control function shall enter the Reconnect/Traffic State. A packet data service option can be connected as a result of service negotiation initiated either by the BS/MSC or by the mobile station. -

436 TIA/EIA/IS-0-A If the Reconnect/Idle State was entered with a mobile station wait indication, and the mobile station enters the Mobile Station Idle State, the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA--B. The mobile station should include the packet data service option in the SERVICE_OPTION field of the Origination Message (see... of TIA/EIA--B). The packet data service call control function shall re-enter the Reconnect/Idle State with a packet origination indication. If the Reconnect/Idle State was entered with a packet origination indication, and the packet data service option has not been rejected, the packet data service call control function shall re-enter the Reconnect/Idle State with a channel loss indication if any of the following occurs: The mobile station enters the Mobile Station Initialization State; or The mobile station exits the System Access State and enters any state other than the Mobile Station Control on the Traffic Channel State. If the Reconnect/Idle State was entered with a channel loss indication, the mobile station shall perform the following: If the mobile station has data to send, the mobile station may discard the data. If the mobile station has no data to send, and the mobile station has not detected a change in the serving system SID or NID since the packet data service call control function last entered the Connected State, and the mobile station has not detected a change in PACKET_ZONE_ID S while in the Reconnect/Idle State, the packet data service call control function shall enter the Dormant/Idle State. Otherwise, the packet data service call control function shall remain in the Reconnect/Idle State, and the mobile station shall perform the remaining actions in this list. The mobile station shall start a reconnect delay timer. The initial length of the reconnect delay timer shall be seconds. For each successive entry or re-entry to the Reconnect/Idle State with a channel loss indication, the mobile station shall quadruple the delay length. The maximum delay length is implementation specific, but should not be less than one hour (00 seconds). When the packet data service call control function enters the Connected State, the delay length shall be reset to seconds. If the reconnect delay timer expires while the packet data service call control function is in the Reconnect/Idle State, the mobile station shall perform the following: If the mobile station is not in the Mobile Station Idle State, the mobile station shall wait until the mobile station enters the Mobile Station Idle State. Mobile stations supporting applications that include higher-layer data retransmission protocols should always discard such data. -

437 TIA/EIA/IS-0-A When the mobile station is in the Mobile Station Idle State, the mobile station shall perform the Mobile Station Origination Operation as defined in... of TIA/EIA--B. The mobile station should include the packet data service option in the SERVICE_OPTION field of the Origination Message (see... of TIA/EIA--B). The packet data service call control function shall reenter the Reconnect/Idle State with a packet origination indication. If the mobile station receives a Release Order indicating that the packet data service option is rejected, the packet data service shall enter the Inactive State. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State.... Reconnect/Traffic State While the packet data service call control function is in the Reconnect/Traffic State, the mobile station shall perform the following: The mobile station packet data service call control function shall perform service negotiation or service option negotiation, as described in... of TIA/EIA--B, to connect the requested service configuration. If the packet data service option is connected, the packet data service call control function shall enter the Connected State when the mobile station enters the Conversation Substate. If the mobile station exits the Mobile Station Control on the Traffic Channel State, the packet data service call control function shall enter the Reconnect/Idle State with a channel loss indication. If the packet data service option cannot be connected, the packet data service shall enter the Inactive State. If the packet data service enters the Inactive State, the packet data service call control function shall enter the Null State.... BS/MSC Procedures... Packet Data Service Control Procedures... Inactive State When the packet data service is in the Inactive State, the BS/MSC does not provide packet data service to the mobile station. The BS/MSC packet data service enters the Active State when the IWF Link Layer connection is opened and a packet data service option is connected. If the BS/MSC packet data service enters the Inactive State while the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection.... Active State When the packet data service is in the Active State, the BS/MSC can provide packet data service to the mobile station. -

438 TIA/EIA/IS-0-A When the packet data service enters the Active State, the BS/MSC should store the mobile station identifier and the connected packet data service type (see..). If the BS/MSC supports connections to multiple IWFs, the BS/MSC should also store the IWF identifier, to identify the IWF during re-activation of the IWF Link Layer connection from the dormant substate (see...). The BS/MSC packet data service may enter the Inactive State when any of the following occurs: The BS/MSC receives a Registration Message indicating power-down registration. The BS/MSC receives a Release Order with a power down indication. The BS/MSC determines that the mobile station cannot be paged. The mobile station rejects the packet data service option after being paged. The mobile station is handed off to another system or service area that is not connected to the same IWF. The mobile station is handed off to a non-cdma service. The BS/MSC determines that the mobile station has roamed to another system or service area that is not connected to the same IWF while the Link Layer connection is in the dormant substate. The Link Layer connection has been closed. While the packet data service is in the Active State, the service negotiation procedures described in... and... of TIA/EIA--B can be used to simultaneously connect other service options as primary or secondary traffic. This is intended, for example, to permit the simultaneous and independent connection and disconnection of voice and packet data services. Complete BS/MSC procedures for invoking and controlling such simultaneous connections require further study, and are left for future revisions of this standard. Until other procedures are defined, the BS/MSC can connect a voice call while the packet data service call control function is in the Connected State by releasing the Traffic Channel, paging the mobile station, requesting a voice service option, and performing service negotiation to connect a service configuration containing voice as primary traffic and packet data as secondary traffic. While voice and packet data service options are connected, the BS/MSC should process all received and transmitted service-related signaling messages, such as Alert With Information and Flash With Information, as pertaining only to the voice service. Normally a registration cancellation message from the HLR would provide this indication. If the BS/MSC receives an Origination Message from the mobile station, requesting the packet data service option, while the BS/MSC is paging the mobile station, the BS/MSC can send a Reorder Order to terminate the mobile station s origination, and can continue paging. -

439 TIA/EIA/IS-0-A The BS/MSC can disconnect the voice service option by releasing the Traffic Channel, following which the packet data service call control function automatically reconnects the packet data service option as described in Packet Data Service Call Control Function... Null State When the BS/MSC packet data service call control function is in the Null State, packet data are not exchanged with the mobile station. The following events can occur while the packet data service call control function is in this state: The mobile station can request activation of the packet data service by requesting connection of a packet data service option. Either the IWF or the mobile station can initiate the reactivation of an open IWF Link Layer connection. The IWF can inform the BS/MSC that the Link Layer connection is closed. The BS/MSC can initiate transfer of the Link Layer connection to a different IWF. If the service configuration of the mobile station does not permit connecting a packet data service option, the BS/MSC can request that the IWF close the Link Layer connection.... IWF Initiated Link Layer Connection Reactivation If the IWF requests reactivation of the Link Layer connection (see. of TIA/EIA/IS-), the BS/MSC should perform the following: If the mobile station is not on a Traffic Channel, the BS/MSC should page the mobile station, requesting the packet data service option. The packet data service call control function should enter the Paging State. If the mobile station is on a Traffic Channel, and both the BS/MSC and the mobile station support Traffic Channel service negotiation (see... and... of TIA/EIA--B ), the BS/MSC should perform the following: If either primary traffic or secondary traffic does not have a connected service option, the BS/MSC should send a Service Request Message in accordance with TIA/EIA--B, requesting a valid service configuration including the packet data service option, using the traffic type available. The packet data service call control function should enter the Initialization/Traffic State. If other service options are already connected as both primary and secondary traffic, the BS/MSC may send a Service Request Message requesting a service configuration in which the packet data service option replaces one of the previously connected service options. If the BS/MSC sends a Service Request Message, the packet data service call control function should enter the Initialization/Traffic State. Otherwise, the BS/MSC may inform the IWF that the Link Layer connection has been deactivated or may request that the IWF close the Link Layer connection. The packet data service call control function should remain in the Null State. -0

440 TIA/EIA/IS-0-A Mobile Station Originated Link Layer Connection Activation If the BS/MSC receives an Origination Message requesting a packet data service option from the mobile station, the BS/MSC should perform the following: If the service option requested by the mobile station indicates a packet data service type (see..) that is not supported, the BS/MSC should send a Release Order rejecting the requested service option in accordance with TIA/EIA--B. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection. The packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. Otherwise, the BS/MSC should perform the following: If IWF resources are temporarily unavailable due to congestion or equipment outage, the BS/MSC should not send a message indicating that the service option has been rejected, as this can inhibit packet data service origination attempts. The BS/MSC should send a Reorder Order to the mobile station. The packet data service call control function should remain in the Null State, and the BS/MSC should not perform the remaining actions in this list. If the packet data service is in the Active State, and the requested service option is supported but indicates a packet data service type that is different from the stored packet data service type (see...), the BS/MSC should request that the IWF close the Link Layer connection, and the packet data service should enter the Inactive State. The packet data service call control function should remain in the Null State, and the BS/MSC should assign the mobile station to a Traffic Channel following the procedures of TIA/EIA--B. If the requested packet data service option indicates the same packet data service type as the stored packet data service type, the BS/MSC should perform the following: If the requested service option and rate sets are supported and traffic channel resources are available, the BS/MSC should assign the mobile station to a Traffic Channel following the procedures of TIA/EIA--B. If the requested service option or rate set is not supported or if traffic channel resources are not available, the BS/MSC should send to the mobile station a Channel Assignment Message with the ASSIGN_MODE field set to 00 and the GRANTED_MODE field set to 00. Subsequently, the BS/MSC should perform service negotiation to establish a suitable service configuration. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF reactivate the Link Layer connection. If the IWF Link Layer connection is closed, the BS/MSC should request that the IWF open a Link Layer connection for the mobile station. The packet data service call control function should enter the Initialization/Idle State. -

441 TIA/EIA/IS-0-A Mobile Station Negotiated Link Layer Connection Activation If the BS/MSC supports service negotiation and the BS/MSC receives a Traffic Channel Service Request Message requesting a service configuration including a packet data service option, the BS/MSC should perform the following: If the service option requested by the mobile station indicates a packet data service type (see..) that is not supported, the BS/MSC should reject the requested service option in accordance with TIA/EIA--B. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection. The packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. If the packet data service is in the Active State, and the requested service option is supported but indicates a packet data service type that is different from the stored packet data service type (see...), the BS/MSC should perform the following: The BS/MSC should request that the IWF close the Link Layer connection, and the packet data service should enter the Inactive State. When the IWF Link Layer connection is closed, the BS/MSC should request that the IWF open a new Link Layer connection for the mobile station. The packet data service call control function should enter the Initialization/Traffic State. If the requested service option indicates the same packet data service type as the stored packet data service type, the BS/MSC should perform the following: If the IWF Link Layer connection is open, the BS/MSC should request that the IWF reactivate the Link Layer connection. If the IWF Link Layer connection is closed, the BS/MSC should request that the IWF open a Link Layer connection for the mobile station. The packet data service call control function should enter the Initialization/Traffic State.... IWF Link Layer Closure If the IWF informs the BS/MSC that the Link Layer connection has been closed, the packet data service should enter the Inactive State, and the packet data service call control function should remain in the Null State.... IWF Transfer If the BS/MSC transfers the Link Layer connection to a new IWF, the BS/MSC should perform the following: The BS/MSC should request that the current IWF close the Link Layer connection. The BS/MSC packet data service should enter the Inactive State. The BS/MSC should then request that the new IWF open a Link Layer connection for the mobile station. When the IWF Link Layer connection is opened, the -

442 TIA/EIA/IS-0-A BS/MSC should perform the procedures for IWF Initiated Link Layer connection Reactivation, as defined in Paging State When the BS/MSC packet data service call control function is in the Paging State, the BS/MSC should perform the following: If the BS/MSC receives a Page Response Message containing a valid, non-zero service option number, the BS/MSC should assign the mobile station to a Traffic Channel, following the procedures of TIA/EIA--B. The packet data service call control function should enter the Initialization/Idle State. If the BS/MSC receives a Page Response Message with an invalid service option, the BS/MSC should send a Release Order rejecting the requested service option in accordance with TIA/EIA--B. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection. The packet data service should enter the Inactive State, and packet data service call control function should enter the Null State. If the BS/MSC does not receive a Page Response Message or if the BS/MSC receives a Page Response Message with the service option number set to zero, the BS/MSC may request that the IWF close the Link Layer connection. If the BS/MSC requests that the IWF close the Link Layer connection, the packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State.... Initialization/Idle State When the BS/MSC packet data service call control function is in the Initialization/Idle State, the BS/MSC should perform the following: If the BS/MSC initializes a Traffic Channel for the mobile station, the BS/MSC should negotiate connection of a packet data service option. The packet data service call control function should enter the Initialization/Traffic State. If the packet data service option requested by the mobile station is not supported, the BS/MSC should send a Release Order rejecting the requested service option in accordance with TIA/EIA--B. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection. The packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. If the requested service option is temporarily unavailable, the BS/MSC may send a Reorder Order to the mobile station to indicate that the service is temporarily unavailable. If a Reorder Order is sent while the packet data service is in the Active State, the BS/MSC should inform the IWF that the Link Layer connection has been deactivated. If a Reorder Order is sent while the packet data service is in the Inactive State, the BS/MSC should request that the IWF close the Link Layer connection, if open. The packet data service call control function should enter the Null State. -

443 TIA/EIA/IS-0-A If the IWF informs the BS/MSC that the Link Layer connection has been closed, the packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State.... Initialization/Traffic State When the BS/MSC packet data service call control function enters the Initialization/Traffic State, the BS/MSC should perform service negotiation, as described in... of TIA/EIA--B, to connect the requested service configuration. If the BS/MSC has sent a Channel Assignment Message to the mobile station with the ASSIGN_MODE field set to 00 and the GRANTED_MODE field set to 00 (see...), the BS/MSC may propose an alternate service configuration. If the BS/MSC supports authentication, it may complete a Unique Challenge of the mobile station (see... of TIA/EIA--B) before providing packet data services to the mobile station. If a service configuration including a packet data service option is connected, the packet data service call control function should enter the Connected State. If the IWF informs the BS/MSC that the Link Layer connection has been closed, the packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. If no other service options are connected, the BS/MSC should release the Traffic Channel. If a service configuration including a packet data service option cannot be connected, the BS/MSC should perform the following: If no other service options are connected, the BS/MSC should release the Traffic Channel. If the IWF Link Layer connection is open, the BS/MSC should request that the IWF close the Link Layer connection. The packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. If the Traffic Channel is released, the BS/MSC should perform the following: If the IWF Link Layer connection is open, the BS/MSC should inform the IWF that the Link Layer connection has been deactivated. The packet data service call control function should enter the Null State.... Connected State When the BS/MSC packet data service call control function enters the Connected State, the BS/MSC should perform the following: The BS/MSC should perform RLP initialization. Upon completing RLP initialization, the BS/MSC should transfer octets in sequence between RLP and the IWF. If the packet data service is in the Inactive State, the packet data service should enter the Active State. -

444 TIA/EIA/IS-0-A If the IWF informs the BS/MSC that the Link Layer connection has been closed, the BS/MSC should perform the following: The packet data service should enter the Inactive State, and the packet data service call control function should enter the Null State. If no other service options are connected, the BS/MSC should release the Traffic Channel. Otherwise, the BS/MSC should negotiate a service configuration that does not include the packet data service option. If the BS/MSC transfers the Link Layer connection to a new IWF, the BS/MSC should perform the following: The BS/MSC should request that the current IWF close the Link Layer connection. The BS/MSC packet data service should enter the Inactive State. The packet data service call control function should remain in the Connected State, but data received from the mobile station should be discarded until the packet data service enters the Active State. The BS/MSC should then request that the new IWF open a Link Layer connection for the mobile station. When the IWF Link Layer connection is opened, the BS/MSC packet data service should enter the Active State. While the packet data service call control function is in the Connected State, the BS/MSC should maintain a packet data inactivity timer. The timer should be reset whenever nonidle RLP data frames are sent or received. If the packet data inactivity timer expires, the BS/MSC should perform the following: If no other service options are connected, the BS/MSC should release the Traffic Channel. Otherwise, the BS/MSC should disconnect the packet data service option by negotiating a service configuration that does not include the packet data service option. If the Traffic Channel is released or the packet data service option is disconnected, the BS/MSC should inform the IWF that the Link Layer connection has been deactivated. The packet data service call control function should enter the Null State... Initialization and Connection of Packet Data Service Options Packet data service options shall be negotiated and connected using the service configuration and negotiation procedures defined in... and... of TIA/EIA- -B. Mobile stations that support Type Packet Data Service shall support Service Option. Mobile stations that support Type Packet Data Service shall support Service Option. The mobile station shall initiate connection of a packet data service option by performing one of the following: By requesting the packet data service option in either a Page Response Message or an Origination Message. -

445 TIA/EIA/IS-0-A. 0 If the service negotiation procedure is performed, by sending a Service Request Message requesting a service configuration that includes the packet data service option. After initiating connection of a packet data service option, the mobile station shall connect the service option as specified in Mobile Station Procedures The mobile station performs service negotiation for packet data service options as described in... of TIA/EIA--B. For any packet data service option, the mobile station shall not propose a service configuration whose attributes are inconsistent with the valid service configuration attribute table for the service option. The mobile station shall not accept a service configuration whose attributes are inconsistent with the valid service configuration attribute table for the service option. The default service configuration for the packet data service option shall be as shown in the valid service configuration attribute table for the service option. Table Valid Service Configuration Attributes for Service Options and Service Configuration Attribute Valid Selections Forward Multiplex Option Multiplex Option,,,,,,,. Reverse Multiplex Option Multiplex Option,,,,,,,. Forward Transmission Rates Rates, / and / enabled, Rate / not enabled. Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type Rates, / and / enabled, Rate / not enabled. Primary or Secondary Traffic. Shall be identical to the Forward Traffic Type. -

446 TIA/EIA/IS-0-A. Table Valid Service Configuration Attributes for Service Options and Service Configuration Attribute Valid Selections Forward Multiplex Option Multiplex Option,,,,,,,. Reverse Multiplex Option Multiplex Option,,,,0,,,. Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type Rates, / and / enabled, Rate / not enabled. All rates enabled. Primary or Secondary Traffic. Shall be identical to the Forward Traffic Type. Table Valid Service Configuration Attributes for Service Options and Service Configuration Attribute Forward Multiplex Option Reverse Multiplex Option Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type Valid Selections Multiplex Option,,,,0,,,. Multiplex Option,,,,,,,. All rates enabled. Rates, / and / enabled, Rate / not enabled. Primary or Secondary Traffic. Shall be identical to the Forward Traffic Type. Table Valid Service Configuration Attributes for Service Options and Service Configuration Attribute Valid Selections Forward Multiplex Option Multiplex Option,,,,0,,,. Reverse Multiplex Option Multiplex Option,,,,0,,,. Forward Transmission Rates Reverse Transmission Rates Forward Traffic Type Reverse Traffic Type All rates enabled. All rates enabled. Primary or Secondary Traffic. Shall be identical to the Forward Traffic Type. -

447 TIA/EIA/IS-0-A If a packet data service option is connected when the mobile station enters the Waiting for Mobile Station Answer Substate, or if a packet data service option becomes connected while the mobile station is in the Waiting for Mobile Station Answer Substate, the mobile station shall automatically send a Connect Order to the BS/MSC as a message requiring acknowledgment without waiting for the user to explicitly command the call to be answered, except when the service configuration includes any service option that requires user answer. When the mobile station sends a Connect Order, the mobile station enters the Conversation Substate.... BS/MSC Requirements For any service option, the BS/MSC shall not propose a service configuration whose attributes are inconsistent with the valid service configuration attribute table for the service option (see...). The BS/MSC shall not accept a service configuration whose attributes are inconsistent with the valid service configuration attribute table for the service option... Optional Zone-Based Registration or Reconnection The BS/MSC may require the mobile station to register or reconnect the packet data service when packet data service is in the Active State, the mobile station is in the Mobile Station Idle State, and the mobile station detects a change in the registration zone (see... of TIA/EIA--B). The BS/MSC shall enable and disable zone based registration or zone based reconnection in the mobile station through the Service Option Control Message. The default state within the mobile station for both zone based registration and zone based reconnection shall be disabled. The BS/MSC may enable either zone based registration or zone based reconnection but not both simultaneously. Once zone based registration or zone based reconnection is enabled by the BS/MSC, the mobile station shall either register or reconnect the packet data service option (depending upon the feature enabled), on detection of a change in Registration Zone, and shall disable the enabled feature when one of the following events occurs: The mobile station receives a Service Option Control Message disabling the enabled feature. The mobile station detects a change in the SID of the serving system. Packet data service enters the Inactive State. The BS/MSC may send a Service Option Control Message (see... of TIA/EIA--B) to enable or disable zone based registration or zone based reconnection within the mobile station. The Service Option Control Message shall include the typespecific fields shown in Table. -

448 TIA/EIA/IS-0-A. Table ORDQ Format and Type-Specific Fields for Zone-Based Registration/Reconnection Field Length (bits) ZREG_CNTL RESERVED FIELD_TYPE 0 ZREG_CNTL - Zone based registration/reconnection control. The BS/MSC shall set this field to the ZREG_CNTL value from Table corresponding to the zone-based function that the mobile station is to perform. RESERVED - Reserved bits. The BS/MSC shall set this field to 00. FIELD_TYPE - Type-specific field designator. The BS/MSC shall set this field to 00. The ZREG_CNTL field shall be set appropriately as specified in Table. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 00 and the ZREG_CNTL field is not equal to a value defined in Table, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to Table Zone Based Registration/Reconnection Control Field ZREG_CNTL (binary) Mobile Station Action 000 Disable zone-based functions 00 Enable zone-based registration 00 Enable zone-based reconnection All other ZREG_CNTL values are reserved. 0.. Optional Reconnect After Hard Handoff The BS/MSC may require the mobile station to reconnect the packet data service option (see...) when the mobile station successfully completes a hard handoff (see... of TIA/EIA--B) in which the Active Set or frequency assignment changes. The BS/MSC shall enable and disable this feature in the mobile station through the Service Option Control Message. The default state within the mobile station for this feature shall be disabled. Once enabled by the BS/MSC, the mobile station reconnects the packet -

449 TIA/EIA/IS-0-A. data service option after successful completion of a hard handoff in which the Active Set or frequency assignment changes. The mobile station shall disable this feature when one of the following events occurs: The mobile station receives a Service Option Control Message disabling this feature. The mobile station detects a change in the SID of the serving system. Packet data service enters the Inactive State. The BS/MSC may send a Service Option Control Message (see... of TIA/EIA--B) to enable or disable this feature. The Service Option Control Message shall include the type-specific fields shown in Table. 0 Table ORDQ Format and Type-Specific Fields for Reconnect After Hard Handoff Field Length (bits) HHO_CNTL RESERVED FIELD_TYPE 0 HHO_CNTL - Reconnect After Hard Handoff control. The BS/MSC shall set this field to the HHO_CNTL value from Table corresponding to the function that the mobile station is to perform. RESERVED - Reserved bits. The BS/MSC shall set this field to 00. FIELD_TYPE - Type-specific field designator. The BS/MSC shall set this field to 00. The HHO_CNTL field shall be set appropriately as specified in Table. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 00 and the HHO_CNTL field is not equal to a value defined in Table, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to

450 TIA/EIA/IS-0-A. Table Reconnect After Hard Handoff Control Field HHO_CNTL (binary) Mobile Station Action 000 Disable Reconnect After Hard Handoff 00 Enable Reconnect After Hard Handoff All other HHO_CNTL values are reserved. 0.. Optional Packet Data Dormant Timer Control The BS/MSC may require a mobile station to establish a value for the Packet Data Dormant Timer. If this feature is enabled, a mobile station shall not originate a packet data service option until the timer has exceeded the value established by the BS/MSC. The BS/MSC shall enable and control this feature in the mobile station through the Service Option Control Message. The default state within the mobile station for BS/MSC control of the packet data dormant timer shall be disabled. When this feature is disabled, the mobile station should set its packet data dormant timer to the default value of 0 seconds (see...). The mobile station shall disable BS/MSC control of the dormant timer when one of the following events occurs: The mobile station receives a Service Option Control Message disabling BS/MSC control. The mobile station detects a change in the SID of the serving system. Packet data service enters the Inactive State. The BS/MSC may send a Service Option Control Message (see... of TIA/EIA--B) to control this feature. The Service Option Control Message shall include the type-specific fields shown in Table. 0 Table Type-Specific Fields for Data Dormant Timer Control Field Length (bits) DORM_CNTL RESERVED FIELD_TYPE DORM_TIME 0 or DORM_CNTL - Dormant Timer control. The BS/MSC shall set this field to the DORM_CNTL value from Table 0 corresponding to the function that the mobile station is to perform. -

451 TIA/EIA/IS-0-A RESERVED - Reserved bits. The BS/MSC shall set this field to 00. FIELD_TYPE - Type-specific field designator. The BS/MSC shall set this field to 0. DORM_TIME - Value of packet data dormant timer. If DORM_CNTL is set to 00, the BS/MSC shall include this field and set it to the DORM_TIME value from Table corresponding to the value of the packet data dormant timer to be used by the mobile station. The DORM_CNTL field shall be set appropriately as specified in Table 0. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 0 and the DORM_CNTL field is not equal to a value defined in Table 0, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 0 and the DORM_CNTL field set to 000, the mobile station shall disable BS/MSC control of the minimum dormant timer value. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 0 and the DORM_CNTL field set to 00, and the mobile station supports a packet data dormant timer, the mobile station shall enable BS/MSC control of the timer and set the minimum value of the dormant timer to the value specified in the DORM_CNTL field. If the current value of the mobile station s dormant timer is less than the value specified in the DORM_TIME, the mobile station shall set the value of its packet data dormant timer to the value specified in DORM_TIME. If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 0 and the mobile station does not support a packet data dormant timer, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to When this feature is enabled, the mobile station s packet data dormant timer shall not be set to a value less than the minimum value specified in the most recently received Service Option Control Message. If the mobile station provides a means for user configuration of the dormant timer, and the user attempts to set the value of the timer to a value less than minimum specified value, the mobile station should provide the user with an error indication. The means for providing the error indication is left to the manufacturer. -

452 TIA/EIA/IS-0-A. Table 0 Dormant Timer Control Field DORM_CNTL (binary) Mobile Station Action 000 Disable BS/MSC control of minimum dormant timer 00 Set the minimum dormant timer value to value specified in DORM_TIME field All other DORM_CNTL values are reserved. Table Minimum Value of Mobile Station Dormant Timer DORM_TIME (binary) Description Dormant mode not supported by BS/MSC through Minimum mobile station packet data dormant timer value in tenths of seconds Optional Packet Zone Reconnection Control The BS/MSC may require the mobile station to reconnect the packet data service when the packet data service is in the Active State; the packet data call control function is in the Dormant / Idle State, Reconnect/Idle State, or Dormant/Traffic State; and the mobile station detects a change in the non-zero packet data services zone identifier. Packet zone based reconnection causes a mobile station to reconnect the packet data service whenever it moves into a new packet data zone not on its internally stored list of visited packet data zones. A packet data zone is added to the list whenever the mobile station connects the packet data service while in the zone, and is deleted when the number of more recently visited zones is equal to the maximum number of zones retained by the mobile station. The BS/MSC shall enable packet zone based reconnection in the mobile station by transmitting a non-zero packet data services zone identifier (PACKET_ZONE_ID). The BS/MSC may disable the packet zone based reconnection function in the mobile station by sending a Service Option Control Message disabling the enabled feature. The BS/MSC may re-enable the function in the mobile station by sending a Service Option Control Message enabling the feature. The BS/MSC may control the number of entries a mobile station is to retain in its list of visited packet data zones and may clear the list by sending a Service Option Control Message. -

453 TIA/EIA/IS-0-A. 0 0 The default state within the mobile station for the packet zone based reconnection feature shall be disabled. The mobile shall enable the feature upon initial detection of a non-zero packet data services zone identifier (PACKET_ZONE_ID S ). The mobile station shall then add the packet data services zone identifier to its stored list of visited packet data zones. Upon enabling the packet zone reconnection feature, the mobile station shall set the length of the packet zone list to one entry until commanded otherwise by the base station. The mobile station shall provide memory for storing up to zone identifiers. The mobile station shall maintain the list of visited packet data service zone identifiers in most recently visited order sequence with the current zone contained in the first entry of the list. Entries shall be removed from the list in least recently visited order. The mobile station shall disable the feature and clear its list of visited packet data service zone identifiers when one of the following occurs: The mobile station receives a Service Option Control Message disabling the feature. The mobile station detects a PACKET_ZONE_ID S field of value The mobile station determines that the BS/MSC does not support packet zones. Packet data service enters the Inactive State. The mobile station detects a change in SID. Once disabled, the mobile station shall re-enable the feature upon detection of a non-zero PACKET_ZONE_ID S or upon receipt of a Service Option Control Message enabling the feature. If service negotiation is used, the BS/MSC may send a Service Option Control Message (see... of TIA/EIA--B) to control this feature. The Service Option Control Message shall include the type-specific fields shown in Table. Table Type-Specific Fields for Packet Connection Control Field Length (bits) PKT_CON_CNTL RESERVED FIELD_TYPE RESERVED 0 or PKT_ZONE_LIST_LEN 0 or 0 PKT_CON_CNTL - Packet Zone Connection Control. The BS/MSC shall set this field to the PKT_CON_CNTL value from Table corresponding to the function that the mobile station is to perform. -

454 TIA/EIA/IS-0-A RESERVED - Reserved bits. The BS/MSC shall set this field to 00. FIELD_TYPE - Type-specific field designator. The BS/MSC shall set this field to 00. RESERVED - Reserved bits. The BS/MSC shall set this field to 0000 if PKT_CON_CNTL is set to 00 or 00. The BS/MSC shall omit this field if PKT_CON_CNTL is any other value. PKT_ZONE_LIST_LEN - Packet data zone identifier list length. The BS/MSC shall include this field if PKT_CON_CNTL is set to 00 or 00 to specify the number of packet data service zone identifiers the mobile station is to retain in its packet data zone identifier list. This field shall be within the range 000 through, inclusive. The BS/MSC shall set the PKT_CON_CNTL appropriately as specified in Table. The BS/MSC shall set the value of PKT_CON_CNTL to 000 to disable the packet zone based reconnection feature in the mobile station. The BS/MSC shall set the value of PKT_CON_CNTL to 00 to enable packet zone based reconnection feature in the mobile station. The BS/MSC shall also include the PKT_ZONE_LIST_LEN field in the type-specific fields of the Service Option Control Message to specify the number of packet data service zone identifiers the mobile station is to store in its internal list. The BS/MSC shall set the value of PKT_CON_CNTL to 00 to clear the packet data service zone identifier list within the mobile station. The BS/MSC shall also include the PKT_ZONE_LIST_LEN field in the type-specific fields of the Service Option Control Message to specify the number of packet data service zone identifiers the mobile station is to store in its internal list. The BS/MSC shall set the value of the PKT_CON_CNTL to 0 to request the mobile station to transfer its internally stored packet data services zone identifier list to the BS/MSC. -

455 TIA/EIA/IS-0-A. Table Packet Zone Connection Control Field PKT_CON_CNTL (binary) Mobile Station Action 000 Disable packet zone connection control 00 Enable packet zone connection control 00 Clear the packet data zone identifier list 0 Transfer the packet data zone identifier list to BS/MSC All other PKT_CON_CNTL values are reserved. 0 0 If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 00 and the PKT_CON_CNTL field is not equal to a value defined in Table, the mobile station shall reject the message by sending a Mobile Station Reject Order with the ORDQ field set equal to If the mobile station receives a Service Option Control Message for the service option with FIELD_TYPE set to 00 and the PKT_CON_CNTL field is equal to a value defined in Table, the mobile station shall perform the following actions: If the value of PKT_CON_CNTL field is set to 000, the mobile station shall disable the packet zone based reconnection feature and clear its list of stored packet data service zone identifiers. If the value of the PKT_CON_CNTL field is set to 00, and the packet zone based reconnection feature is currently disabled, the mobile station shall enable the feature. The mobile station shall set the number of entries in its packet data services zone identifier list to the value specified in the PKT_ZONE_LIST_LEN field of the Service Option Control Message. If the value of the PKT_CON_CNTL field is set to 00, and the packet zone based reconnection feature is currently enabled, the mobile station shall set the number of entries in its packet data services zone identifier list to the value specified in the PKT_ZONE_LIST_LEN field of the Service Option Control Message. If the value of the PKT_ZONE_LIST_LEN is greater than or equal to the number of existing entries in the list, the mobile station shall retain the current list entries. If the value of the PKT_ZONE_LIST_LEN represents a decrease in the number of list entries, the mobile station shall delete the least recently visited zone list entries. If the value of the PKT_CON_CNTL field is set to 00, the mobile station shall clear its packet data service zone identifier list. The mobile station shall set the number -

456 TIA/EIA/IS-0-A. of entries in its packet data services zone identifier list to the value specified in the PKT_ZONE_LIST_LEN field of the Service Option Control Message. If the value of the PKT_CON_CNTL field is set to 0, the mobile station shall transfer the contents of its stored packet data services zone identifier list to the BS/MSC. The mobile station shall transfer the list using a Service Option Control Message including the type-specific fields shown in Table. Table Type-Specific Fields for Packet Zone Connection Response Field Length (bits) PKT_CON_RESP RESERVED FIELD_TYPE RESERVED PKT_ZONE_LIST_LEN 0 The mobile station shall include PKT_ZONE_LIST_LEN occurrences of the following record: PACKET_ZONE_ID 0 PKT_CON_RESP - Packet Zone Connection Response. The mobile station shall set this field to 000. RESERVED - Reserved bits. The mobile shall set this field to 00. FIELD_TYPE - Type-specific field designator. The mobile shall set this field to 00. RESERVED - Reserved bits. The mobile station shall set this field to PKT_ZONE_LIST_LEN - Packet Data Zone Identifier List Length. The mobile station shall set this field to specify the number of reported packet data service zone identifiers within the Service Option Control Message. This field shall be within the range of 000 through, inclusive. PACKET_ZONE_ID - Packet data services zone identifier. The mobile station shall set this field to the packet data services zone identifier for each entry in its stored packet data zone identifier list. -

457 TIA/EIA/IS-0-A High Speed Operation High speed operation uses Supplemental Code Channels to increase the traffic channel s bandwidth. Forward high speed operation uses Forward Supplemental Code Channels. Reverse high speed operation uses Reverse Supplemental Code Channels. The mobile station requests reverse high speed operation by sending a SCRM to the BS/MSC. The mobile station includes a Reverse Bandwidth Request Message (see...) in the REQ_BLOB field of the SCRM and sets the SIZE_OF_REQ_BLOB field to the number of octets in the Reverse Bandwidth Request Message. The mobile station also uses a Reverse Bandwidth Request Message in the REQ_BLOB field of a SCRM to report changes in the number of Reverse Supplemental Code Channels it can use. The BS/MSC controls both forward and reverse high speed operation by allocating Supplemental Code Channels for some time period. Allocation is specified in either the SCAM or GHDM.... Mobile Station Procedures for Reverse High Speed Operation When the amount of user data in the mobile station reaches an implementation defined threshold, the mobile station may request reverse high speed operation by sending a SCRM to the BS/MSC. The mobile station shall include a Reverse Bandwidth Request Message (see...) in the REQ_BLOB field of the SCRM and shall set the SIZE_OF_REQ_BLOB field to the number of octets in the Reverse Bandwidth Request Message. Once the mobile station has sent the SCRM, it should allow the BS/MSC one second to respond with an allocation message (SCAM or GHDM) before repeating the request. If the mobile station determines that it cannot use the maximum number of Reverse Supplemental Code Channels that it indicated in its request for high speed operation, it may send a SCRM to report the correct number without waiting for an allocation message. The mobile station may cancel an outstanding request by sending a SCRM that does not include a REQ_BLOB field, and whose SIZE_OF_REQ_BLOB field is set to zero. If, during reverse high speed operation, the mobile station determines that the user data in the reverse traffic buffer will exceed its implementation defined threshold when it exits reverse high speed operation, it may send a SCRM to the BS/MSC to request a continuation of reverse high speed operation. The mobile station shall include a Reverse Bandwidth Request Message (see...) in the REQ_BLOB field of the SCRM and set the SIZE_OF_REQ_BLOB field to the number of octets in the Reverse Bandwidth Request Message. Once the mobile station has sent the SCRM, it should allow the BS/MSC one second to respond with an allocation message (SCAM or GHDM) before repeating the request. If the mobile station has not been granted permission to use discontinuous transmission, or permission has been granted and the mobile station discontinues transmission for more than the duration specified by REV_DTX_DURATIONs, it shall perform the following: If the BS/MSC has granted the mobile station reverse high speed operation for a finite duration (i.e., not infinite), the mobile station shall perform the following: -

458 TIA/EIA/IS-0-A If the mobile station discontinues transmission on one or more, but not all, Reverse Supplemental Code Channels and there is at least 00 ms remaining before the mobile station exits reverse high speed operation, it may send a SCRM to the BS/MSC to report the number of Reverse Supplemental Code Channels currently in use. If the mobile station discontinues transmission on all Reverse Supplemental Code Channels, it should send a SCRM to the BS/MSC that does not include a REQ_BLOB field and whose SIZE_OF_REQ_BLOB field is set to zero. If the BS/MSC has granted the mobile station reverse high speed operation for an infinite duration, the mobile station shall perform the following: If the mobile station discontinues transmission on any but the last Reverse Supplemental Code Channel, it shall send a SCRM to the BS/MSC to report the number of Reverse Supplemental Code Channels currently in use. If the mobile station discontinues transmission on the last Reverse Supplemental Code Channels, it shall send a SCRM to the BS/MSC that does not include a REQ_BLOB field and whose SIZE_OF_REQ_BLOB field is set to zero.... Reverse High Speed Operation Messages... General Message Format and Coding A message is a sequence of information elements. Each message details which information elements are mandatory, and which are optional. Unless specified otherwise, a particular information element shall not be present more than once in a given message. In general, the coding of information elements follows the rules below. Two categories of information elements are defined: single octet information elements; and variable length information elements. There are two types of single octet information elements. Type single octet elements provide the information element s identification in the ie_identification field and the element s value in the ie_contents field. The value 00 in the ie_identification field is reserved for type single octet elements. The format of a type single octet information element is: Field Length (bits) ie_type ie_identification ie_contents ie_type - A value of indicates a single octet information element. -

459 TIA/EIA/IS-0-A. ie_identification - Any value from 000 -, except 00. The value 00 is reserved for type single octet information elements. ie_contents - Information element contents. The format of a type single octet information element is: Field Length (bits) ie_type ie_identification ie_type - A value of indicates a single octet information element. ie_identification - Any value from There are two types of variable length information elements. Type variable length elements have content whose size is less than octets. The format of a type variable length information element is: Field Length (bits) ie_type ie_identification size_of_ie_contents ie_contents variable ie_type - A value of 00 indicates a type variable length information element. ie_identification - Any value from size_of_ie_contents - Length of information element contents (octets). ie_contents - Information element contents. -0

460 TIA/EIA/IS-0-A. The format of a type variable length information element is: Field Length (bits) ie_type ie_identification reserved size_of_ie_contents ie_contents variable 0 ie_type - A value of 0 indicates a type variable length information element. ie_identification - Any value from reserved - Reserved bits. These bits shall be set to 0. size_of_ie_contents - Length of information element contents (octets). ie_contents - Information element contents.... Reverse Bandwidth Request Message A Reverse Bandwidth Request Message is used by the mobile station to request reverse high speed operation or report a change in the mobile station s capabilities. Its content is described in Table. The Request Type information element shall be the first information element in the message. Table Reverse Bandwidth Request Message Contents Reverse Bandwidth Request Message contents Information Element Reference Mandatory or Optional Request Type... M Maximum Number of Reverse Supplemental Code Channels Preferred Number of Reverse Supplemental Code Channels... O (Note )... O (Note ) Requested Duration... O (Note ) Additional SO Request... O (Note ) Priority... O -

461 TIA/EIA/IS-0-A. Notes Mandatory when (a) the mobile station cannot use the maximum number of Reverse Supplemental Code Channels allowed by the reverse multiplex option or (b) the mobile station is reporting a reduction in the number of Reverse Supplemental Code Channels in use. Mandatory when the mobile station is requesting reverse high speed operation and the number of channels it prefers to use is less than the explicit or implied Maximum Number of Reverse Supplemental Code Channels. Mandatory when the mobile station is requesting reverse high speed operation. Together, the requested duration and the rate indicated by the preferred number of channels shall indicate the amount of data the mobile station wishes to transmit during this request. Mandatory when requesting reverse high speed operation independently for an additional service option.... Request Type The Request Type information element identifies the service generating the request. Its coding is: Field Length (bits) RESERVED REQUEST_TYPE RESERVED - Reserved bits. These bits shall be set to 0. REQUEST TYPE - Requesting Service. The mobile station shall set this field to one of the values in Table. Table Requesting Service Type Request Type (binary) Meaning 00 TIA/EIA--B Packet Data Service 0 -

462 TIA/EIA/IS-0-A.... Maximum Number of Reverse Supplemental Code Channels Information Element The Maximum Number of Reverse Supplemental Code Channels information element identifies the current maximum number of Reverse Supplemental Code Channels which the mobile station can use. If omitted, the number is assumed to be the same as the maximum number of channels allowed by the reverse multiplex option. It is a type single octet information element. Its coding is: Field Length (bits) IE_TYPE MAX_REV_CHANNELS_ID MAX_REV_CHANNELS 0 0 IE_TYPE - The mobile station shall set this field to. MAX_REV_CHANNELS_ID - The mobile station shall set this field to 00. MAX_REV_CHANNELS - The mobile station shall set this field to the maximum number of Reverse Supplemental Code Channels that it can currently use.... Preferred Number of Reverse Supplemental Code Channels Information Element The Preferred Number of Reverse Supplemental Code Channels information element identifies the number of Reverse Supplemental Code Channels which the mobile station prefers to use for this reverse high speed operation request. If omitted, the number is assumed to be the same as the number of channels indicated by the Maximum Number of Reverse Supplemental Code Channels information element. It is a type single octet information element. Its coding is: Field Length (bits) IE_TYPE PREF_REV_CHANNELS_ID PREF_REV_CHANNELS IE_TYPE - The mobile station shall set this field to. PREF_REV_CHANNELS_ID - The mobile station shall set this field to 0. PREF_REV_CHANNELS - The mobile station shall set this field to the number of Reverse Supplemental Code Channels that it prefers to use for this reverse high speed operation request. Allocation of more Reverse Supplemental Code Channels than requested may not provide additional benefit to the mobile station. -

463 TIA/EIA/IS-0-A.... Requested Duration Information Element The Requested Duration information element identifies the time interval, in units of 0 ms, that the mobile station requires reverse high speed operation using the preferred number of Reverse Supplemental Code Channels. It is a type variable length information element. Its coding is: Field Length (bits) IE_TYPE DURATION_ID DURATION_SIZE DURATION 0 IE_TYPE - The mobile station shall set this field to 00. DURATION_ID - The mobile station shall set this field to 00. DURATION_SIZE - The mobile station shall set this field to 00. DURATION - The mobile station shall set this field to the time interval, in units of 0 ms, that the mobile station requires reverse high speed operation. A value of indicates a request for an infinite duration.... Additional SO Request Information Element The Additional SO Request information element identifies the bandwidth requirements for an additional service option specified in ADD_SO_CHANNELS. It specifies the time interval, in units of 0 ms, that the service option requires reverse high speed operation using ADD_SO_CHANNELS number of Reverse Supplemental Code Channels. It is a type variable length information element. Its coding is: Field Length (bits) IE_TYPE ADD_SO_ID ADD_SO_SIZE ADD_SO_DURATION reserved ADD_SO_CHANNELS 0 IE_TYPE - The mobile station shall set this field to 00. ADD_SO_ID - The mobile station shall set this field to 00. ADD_SO_SIZE - The mobile station shall set this field to 00. -

464 TIA/EIA/IS-0-A. ADD_SO_DURATION - The mobile station shall set this field to the time interval, in units of 0 ms, that this service option requires reverse high speed operation. A value of indicates a request for an infinite duration. reserved - The mobile station shall set these bits to 0. ADD_SO_CHANNELS - The mobile station shall set this field to the number of Reverse Supplemental Code Channels that it prefers to use for this reverse high speed operation request for this service option Priority Information Element The Priority information element identifies the requested priority for this Reverse Bandwidth Request. It is a type single octet information element. Its coding is: Field Length (bits) IE_TYPE PRIORITY_ID PRIORITY 0 IE_TYPE - The mobile station shall set this field to. PRIORITY_ID - The mobile station shall set this field to 00. PRIORITY - The mobile station shall set this field to the requested priority for this Reverse Bandwidth Request, using one of the values shown below: system default (the BS/MSC may determine the relative priority of this request) priority level (highest priority) priority level 00 - priority level priority level 00 - priority level 00 - priority level 0 - priority level xxx - reserved 0. L Interface.. Logical Connections The L interface provides a path for transport of end-user data, and a signaling path for communicating control information. L interface protocols should be as recommended in TIA/EIA/IS-. -

465 TIA/EIA/IS-0-A... Mobile Data The L interface supports IWF Link Layer connections to mobile stations. Each opened IWF Link Layer connection can be active or dormant (see...). When the IWF Link Layer connection is activated, an L interface virtual circuit is established. The IWF or BS/MSC initiates release of the L interface virtual circuit for the mobile station when the IWF Link Layer connection is deactivated. The IWF may initiate release of the L interface virtual circuit for the mobile station when the IWF Link Layer connection is closed. The BS/MSC may request that the IWF close the Link Layer connection while initiating release of the L Interface virtual circuit. -

466 TIA/EIA/IS-0-A LINK LAYER. Link Layer Protocols The IWF maintains a separate instance of the Link Layer protocol for each mobile station having an opened IWF Link Layer connection. The Link Layer protocol used for Service Options,,,,,,, and shall be the Internet Point-to-Point Protocol (PPP), in accordance with RFC. The TE, MT (Network Layer R m interface protocol option only) and IWF shall support the PPP Link Control Protocol (LCP) defined in RFC and the LCP extensions defined in RFC 0. The instances of PPP shall support control escaping in accordance with. of RFC. When the Relay Layer R m interface protocol option is selected, the MT shall not perform control escaping, and the provisions of section of RFC do not apply to the MT. The IWF Link Layer shall support negotiation of async control character mapping as defined in RFC. The IWF should not request control character mapping, but should perform control character mapping if negotiated by the mobile station. If PPP is used as the R m interface Link Layer, the R m interface Link Layer shall support negotiation of async control character mapping as defined in RFC. If software flow control is used on the R m interface, the TE shall negotiate mapping for the XON and XOFF control characters. To provide the maximum throughput, the TE should negotiate mapping only for the minimum number of control characters necessary for proper operation. When the Network Layer R m interface protocol option is selected, the MT should not request control character mapping on the R m interface, but shall perform control character mapping on that interface if negotiated by the TE. The TE and MT shall frame PPP packets sent on the R m interface using the asynchronous framing protocol defined in RFC. The MT shall frame PPP packets sent on the U m interface using the octet-synchronous framing protocol defined in RFC, except that there shall be no inter-frame time fill (see.. of RFC ). That is, no flag octets shall be sent between a flag octet that ends one PPP frame and the flag octet that begins the subsequent PPP frame. When the Relay Layer R m interface protocol option is selected, the MT shall perform the necessary framing conversion, except that the MT shall not perform asynchronous control character mapping, and the provisions of section of RFC do not apply to the MT. The IWF shall perform asynchronous control character mapping on L interface data in accordance with the provisions of Section of RFC, in the same manner as if an asynchronous to synchronous framing conversion were performed between the BS/MSC and the IWF. The IWF shall frame PPP packets sent on the L interface using the octet-synchronous framing protocol defined in RFC, except that there shall be no inter-frame time fill Framing conversion in the MT consists of the insertion and removal of start bits, stop bits, and mark characters (see.. and.. of RFC ). -

467 TIA/EIA/IS-0-A (see.. of RFC ). That is, no flag octets shall be sent between a flag octet that ends one PPP frame and the flag octet that begins the subsequent PPP frame. The BS/MSC shall pass octets between the L interface and the MT without any framing conversion. PPP provides a means for interfacing to multiple protocols. The BS/MSC and TE may support any subset of the protocols having a PPP Assigned Protocol Number (see Internet Assigned Numbers ). Requirements for support of Internet Protocol, ISO protocols and CDPD options are given in.,., and.. All PPP frames with an unknown or unsupported protocol number should be rejected, using the procedures defined in RFC.. Link Layer Connections.. IWF Link Layer Connection Opening If the Network Layer R m Interface Protocol option is selected, and the mobile station packet data service call control function enters the Connected State while the U m interface PPP LCP is not in the Opened state, the MT shall initiate PPP configuration according to the protocol defined in RFC. When the PPP LCP enters the Opened state, the PPP Link Layer shall send an establishment indication to higher protocol layers. If PPP is implemented on the R m interface, the MT shall initiate PPP configuration on the R m interface according to the protocol defined in RFC. If the Relay Layer R m Interface Protocol option is selected, when the mobile station packet data service enters the Active State the MT should send a physical layer establishment indication to the TE (see Section.. and Section of TIA/EIA/IS-0-A.). If the PPP LCP in the TE is not in the Opened state, the TE shall initiate PPP configuration according to the protocol defined in RFC. When the PPP LCP enters the Opened state, PPP shall send an establishment indication to higher protocol layers. When an IWF Link Layer connection is in the active substate and the PPP LCP is not in the Opened state, the IWF Link Layer shall initiate PPP configuration according to the protocol defined in RFC. When the PPP LCP enters the Opened state, PPP shall send an establishment indication to higher protocol layers. After a PPP establishment indication, all supported network layer protocols shall be configured using the appropriate network control protocols (see )... IWF Link Layer Connection Maintenance While the IWF Link Layer is in the Active substate, either the mobile station or the BS/MSC may release the Traffic Channel. Procedures for re-establishing the Traffic Channel are given in... When the Traffic Channel is released, the BS/MSC should inform the IWF that the Link Layer connection has been deactivated. When the IWF is informed of a Link Layer connection deactivation, the IWF Link Layer connection shall enter the dormant substate, unless it is closed as specified in... Currently RFC 00. -

468 TIA/EIA/IS-0-A IWF Link Layer Connection Closure... BS/MSC Closure The BS/MSC should request that the IWF close the Link Layer connection when the packet data service enters the Inactive State (see...).... IWF Closure The IWF should close the Link Layer connection when it receives an LCP Terminate- Request message from the mobile station or when the BS/MSC requests that the Link Layer connection be closed. The IWF should also close the Link Layer connection when it determines that the mobile station is no longer in its service area. When closing the Link Layer connection after receiving an LCP Terminate-Request message from the mobile station, the IWF should first complete the procedures for closing PPP defined in RFC. The IWF should not send an LCP Terminate-Request to the mobile station if the BS/MSC requests that the IWF Link Layer connection be closed. If the IWF initiates closure of the Link Layer connection while the Link Layer connection is active, it should send an LCP Terminate-Request to the mobile station. If the Network Layer R m interface protocol option is selected, the MT packet data service should enter the Inactive State when the MT receives an LCP Terminate-Request. When the IWF closes the Link Layer connection, it should discard the PPP connection state information for the mobile station. The IWF should inform the BS/MSC when the Link Layer connection is closed.... TE Closure Causes for TE closure of the IWF Link Layer connection are implementation dependent. If PPP is implemented on the R m interface, TE manages the Link Layer connection using the PPP LCP opening and closing procedures defined in RFC. When the Network Layer R m interface protocol option is selected, and the SLIP protocol is used between the TE and the MT, the MT may close the IWF Link Layer connection when circuit 0/ is deasserted (provided that the &D parameter is not set to zero (see Table..- of TIA/EIA/IS-0-A.)). If the PPP protocol is supported in the TE and the TE closes the IWF Link Layer connection, the TE shall follow the procedures for closing PPP defined in RFC. If the Network Layer R m interface protocol option is selected, then when the PPP connection to the TE is closed, the MT shall close the PPP connection to the IWF using the procedures defined in RFC, and then the packet data service shall enter the Inactive State.... MT Closure If the Network Layer R m interface protocol option is selected, the MT manages the Link Layer connection using the PPP LCP opening and closing procedures defined in RFC. The MT cannot initiate closure of the IWF Link Layer connection when the Relay Layer R m interface protocol option is selected. -

469 TIA/EIA/IS-0-A. If the Network Layer R m interface protocol option is selected, the MT should close the IWF Link Layer connection, if opened, when the packet data service enters the Inactive State. If the MT supports circuit 0/ (or equivalent function provided by In-Band Control Service), the MT may close the Link Layer connection when circuit 0/ is deasserted for longer than a period of time which is to be determined by the implementation. If the Network Layer R m interface protocol option is selected, and PPP is implemented as the Link Layer protocol on the R m interface, the MT should close the PPP LCP on the R m interface when the packet data service enters the Inactive State. -

470 TIA/EIA/IS-0-A. NETWORK LAYER. Internet Protocol Support Support of the Internet Protocol (IP) Network Layer (as defined in RFC ) is optional. The following requirements apply for an IWF and mobile station that support an IP network interface. To select IP interworking via a PPP Link Layer, the mobile station should request Service Option,,, or. For Service Options,,, and, the IWF Link Layer shall support the following PPP protocol numbers: 0 0x00 0x00d 0x00f 0x0 Internet Protocol Van Jacobson Compressed TCP/IP Van Jacobson Uncompressed TCP/IP Internet Protocol Control Protocol 0 For Service Options,,, and, the mobile station shall support the IP Control Protocol (IPCP) defined in RFC. The mobile station shall support Van Jacobson TCP/IP header compression (RFC ). Van Jacobson TCP/IP header compression shall be configured through IPCP negotiation.. ISO Protocol Support Support of the ISO Network Layer protocols, such as the Connectionless Network Protocol (CLNP) as defined in ISO-, is optional. The following requirements apply for an IWF and mobile station that support an OSI network interface. To select OSI interworking via a PPP Link Layer, the mobile station should request Service Option,,, or. For Service Options,,, and, the IWF Link Layer shall support the following PPP protocol numbers: 0x00 OSI Network Layer 0x0 OSI Network Layer Control Protocol (OSINLCP) 0 For Service Options,,, and, the mobile station shall support the PPP OSI Network Layer Control Protocol (OSINLCP) defined in RFC.. CDPD Application Support Support of CDPD applications (see IS-) is optional. The following requirements apply for an IWF and mobile station that support CDPD applications. To select CDPD interworking via a PPP Link Layer, the mobile station shall request Service Option,,, or. If encrypted data is provided to RLP, the mobile station should request that RLP be established without user data frame encryption. As discussed in RFC, the specific OSI protocol is determined according to the first octet in each Network Protocol Data Unit (NPDU), which is the Network Layer Protocol Identifier (NLPID), defined in ISO/TR. -

471 TIA/EIA/IS-0-A. For Service Options,,, and, the PPP Layer shall support the following PPP protocol numbers: 0x00 Mobile Network Registration Protocol (MNRP) 0 The PPP Layer shall also support the protocol numbers required for either the IP or ISO protocol interface, or both, in accordance with. and/or., respectively. For Service Options,,, and, either the TE (if the Relay Layer R m interface protocol option is selected) or the MT (if the Network Layer R m Interface Protocol option is selected) shall support the Mobile Network Registration Protocol (MNRP) defined in Part 0 of IS-, including the authentication parameters and procedures defined in Part 0 of IS-. MNRP Registration shall be performed after a PPP establishment indication is received. A successful MNRP Registration (including ESH and ISC) shall take place before the network layer control protocols (IPCP or OSINLCP) may begin negotiation. While an IWF Link Layer connection is open for Service Option,,, or, the mobile station shall respond to MNRP query messages (ESQ). If the MT or the TE closes the IWF Link Layer connection, the entity performing the closure should perform MNRP deregistration (ESB) before closing the IWF Link Layer. An IWF supporting Service Option,,, or shall support CDPD protocols at and above the Network Layer. 0 Requirements for the CDPD protocols are given in IS-. 0 That is, all CDPD protocol layers above the SNDCP layer. -

472

473

474