tia-eia-683-c

8/12/2019 TIA-EIA-683-C

1/246

TIA

STANDARD

ANSI/TIA-683-C-2003Approved: March 13, 2003

Over the Air Service Provisioning of

Mobile Stations in Spread Spectrum

Systems

TIA-683-C(Revision of TIA/EIA-683-B)

MARCH 2003

TELECOMMUNICATIONS INDUSTRY ASSOCIATION

Representing the telecommunications industry in

association with the Electronic Industries Alliance

8/12/2019 TIA-EIA-683-C

2/246

NOTICE

TIA 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 their particular need. The existence of such Standards and Publicationsshall not in any respect preclude any member or non-member of TIA from manufacturing or selling

products not conforming to such Standards and Publications. Neither shall the existence of such

Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or

internationally.

Standards and Publications are adopted by TIA in accordance with the American National Standards

Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent

owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication.

Further details of the development process are available in the TIA Engineering Manual, located at

http://www.tiaonline.org/standards/sfg/engineering_manual.cfm

This Standard does not purport to address all safety problems associated with its use or all applicable

regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate

safety and health practices and to determine the applicability of regulatory limitations before its use.

(From Standards Proposal No. 3-4742-RV3, formulated under the cognizance of the TIA TR-45.5

Subcommittee on Spread Spectrum Digital Technology.)

Published by

TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2003

Standards and Technology Department

2500 Wilson BoulevardArlington, VA 22201 U.S.A.

PRICE: Please refer to current Catalog of

TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS

AND ENGINEERING PUBLICATIONS

or call Global Engineering Documents, USA and Canada

(1-800-854-7179) International (303-397-7956)

or search online at http://www.tiaonline.org/standards/search_n_order.cfm

All rights reserved

Printed in U.S.A.
http://www.tiaonline.org/standards/sfg/engineering_manual.cfmhttp://www.tiaonline.org/standards/sfg/engineering_manual.cfm

8/12/2019 TIA-EIA-683-C

3/246

NOTICE OF DISCLAIMER AND LIMITATION OF LIABILITY

The document to which this Notice is affixed (the Document) has been prepared by one or more

Engineering Committees or Formulating Groups of the Telecommunications Industry Association (TIA). TIA

is not the author of the Document contents, but publishes and claims copyright to the Document pursuant to

licenses and permission granted by the authors of the contents.

TIA Engineering Committees and Formulating Groups are expected to conduct their affairs in

accordance with the TIA Engineering Manual (Manual), the current and predecessor versions of which are

available at http://www.tiaonline.org/standards/sfg/engineering_manual.cfm. TIAs function is to administer

the process, but not the content, of document preparation in accordance with the Manual and, when appropriate,

the policies and procedures of the American National Standards Institute (ANSI). TIA does not evaluate, test,

verify or investigate the information, accuracy, soundness, or credibility of the contents of the Document. In

publishing the Document, TIA disclaims any undertaking to perform any duty owed to or for anyone.

The use or practice of contents of this Document may involve the use of intellectual property rights (IPR),

including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or

investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed

and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with theManual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the

scope or validity of any claims of IPR.

TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify,

inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents

of the Document.

ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT

LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS,

ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS

MERCHANTABILITY AND ITS NON-INFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL

PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE

ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIESREGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR

REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR

SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH

THE CONTENTS.

TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING

FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING

WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL

DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR

THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT

(INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS AFUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS

WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS.
http://www.tiaonline.org/standards/sfg/engineering_manual.cfmhttp://www.tiaonline.org/standards/sfg/engineering_manual.cfm

8/12/2019 TIA-EIA-683-C

4/246

PLEASE!

DON'T VIOLATE

THE

LAW!

This document is copyrighted by the TIA and may not be reproduced without prior

permission of the Telecommunications Industry Association. For information

consult our website athttp://www.tiaonline.org/about/faqDetail.cfm?id=18

Organizations may obtain permission to reproduce a limited number of copies

through entering into a license agreement. For information, contact:

Global Engineering Documents

15 Inverness Way EastEnglewood, CO 80112-5704 U.S.A. or call

U.S.A. and Canada 1-800-854-7179, International (303) 397-7956
http://www.tiaonline.org/about/faqDetail.cfm?id=18http://www.tiaonline.org/about/faqDetail.cfm?id=18http://www.tiaonline.org/about/faqDetail.cfm?id=18

8/12/2019 TIA-EIA-683-C

5/246

8/12/2019 TIA-EIA-683-C

6/246

TIA-683-C

CONTENTS

ii

3.2.2.3 Starting the OTAPA session.........................................................................3-81

3.3 Programming Procedure.........................................................................................3-82

3.3.1 OTASP Data MessageProcessing .......................................................................3-83

3.3.2 Mobile Station SSD Update and Re-authentication .........................................3-284

3.3.3 Activation of Message Encryption....................................................................3-295

3.3.4 Activation of Voice Privacy...............................................................................3-306

3.3.5 System Selection for Preferred Roaming ..........................................................3-307

3.3.6 Service Programming Lock ..............................................................................3-308

3.3.7 Subscriber Parameter Administration Security Mechanism.............................3-319

3.3.8 Secure Mode ...................................................................................................3-3210

3.3.8.1 Generation of Secure Mode Ciphering Key.................................................3-3211

3.3.8.2 Encryption and Decryption of messages in Secure Mode ...........................3-3312

3.4 Termination of the Programming Procedure .........................................................3-3313

3.5 Reverse Link Message Formats .............................................................................3-3514

3.5.1 Message Contents ...........................................................................................3-3615

3.5.1.1 Configuration Response Message ..............................................................3-3616

3.5.1.2 Download Response Message ....................................................................3-3717

3.5.1.3 MS Key Response Message ........................................................................3-4018

3.5.1.4 Key Generation Response Message............................................................3-4019

3.5.1.5 Re-Authenticate Response Message...........................................................3-4120

3.5.1.6 Commit Response Message .......................................................................3-4221

3.5.1.7 Protocol Capability Response Message ......................................................3-4222

3.5.1.8 SSPR Configuration Response Message .....................................................3-4623

3.5.1.9 SSPR Download Response Message...........................................................3-4724

3.5.1.10 Validation Response Message..................................................................3-4825

3.5.1.11 OTAPA Response Message.......................................................................3-4826

3.5.1.12 PUZL Configuration Response Message ...................................................3-4927

3.5.1.13 PUZL Download Response Message .........................................................3-5128

3.5.1.14 3GPD Configuration Response Message ..................................................3-5329

3.5.1.15 3GPD Download Response Message ........................................................3-5430

3.5.1.16 Secure Mode Response Message..............................................................3-5531

8/12/2019 TIA-EIA-683-C

7/246

TIA-683-C

CONTENTS

iii

3.5.2 NAMParameter Blocks ...................................................................................3-551

3.5.2.1 CDMA/Analog NAM Parameter Block ........................................................3-562

3.5.2.2 Mobile Directory Number ..........................................................................3-593

3.5.2.3 CDMA NAM Parameter Block ....................................................................3-604

3.5.2.4 IMSI_T Parameter Block ............................................................................3-625

3.5.3 SSPR Parameter Blocks ..................................................................................3-636

3.5.3.1 Preferred Roaming List Dimensions Parameter Block ................................3-647

3.5.3.2 Preferred Roaming List Parameter Block ...................................................3-658

3.5.3.3 Extended Preferred Roaming List Dimensions Parameter Block.................3-679

3.5.4 Reserved .........................................................................................................3-6810

3.5.5 Preferred Roaming List and Extended Preferred Roaming List .........................3-6811

3.5.5.1 Preferred Roaming List CRC Calculation ...................................................3-7312

3.5.5.2 Acquisition Records...................................................................................3-7313

3.5.5.2.1 Acquisition Record Formats.................................................................3-7514

3.5.5.2.1.1 Cellular Analog System Acquisition Record....................................3-7515

3.5.5.2.1.2 Cellular CDMA and JTACS CDMA System Acquisition (Standard16

Channels) Record ............................................................................................3-7517

3.5.5.2.1.3 Cellular CDMA and JTACS CDMA System Acquisition (Custom18

Channels) Record ............................................................................................3-7619

3.5.5.2.1.4 Cellular CDMA Preferred System Acquisition Record .....................3-7720

3.5.5.2.1.5 PCS CDMA System Acquisition (Using Blocks) Record ...................3-7721

3.5.5.2.1.6 PCS CDMA and 2 GHz Band CDMA System Acquisition (Using22

Channels) Record ............................................................................................3-7823

3.5.5.2.1.7 JTACS CDMA System Acquisition (Standard Channels) Record .....3-7924

3.5.5.2.1.8 JTACS CDMA System Acquisition (Custom Channels) Record........3-7925

3.5.5.2.1.9 2 GHz Band CDMA System Acquisition (Using Channels) Record ..3-8026

3.5.5.2.2 Extended Acquisition Record Format...................................................3-8127

3.5.5.2.2.1 Cellular Analog System Acquisition Record....................................3-8128

3.5.5.2.2.2 Cellular CDMA System Acquisition (Standard Channels) Record ...3-8129

3.5.5.2.2.3 Cellular CDMA System Acquisition (Custom Channels) Record......3-8230

3.5.5.2.1.4 Cellular CDMA Preferred System Acquisition Record .....................3-8331

3.5.5.2.2.5 PCS CDMA System Acquisition (Using Blocks) Record ...................3-8332

8/12/2019 TIA-EIA-683-C

8/246

TIA-683-C

CONTENTS

iv

3.5.5.2.2.6 PCS CDMA System Acquisition (Using Channels) Record...............3-841

3.5.5.2.2.7 JTACS CDMA System Acquisition (Standard Channels) Record .....3-842

3.5.5.2.2.8 JTACS CDMA System Acquisition (Custom Channels) Record........3-853

3.5.5.2.2.9 2 GHz Band CDMA System Acquisition (Using Channels) Record ..3-854

3.5.5.2.2.10 Generic Acquisition Record for IS-2000 and IS-95 .......................3-865

3.5.5.2.2.11 Generic Acquisition Record for HRPD ..........................................3-876

3.5.5.3 System Record and Extended System Record Format................................3-877

3.5.5.3.1 System Record Format ........................................................................3-878

3.5.5.3.2 Extended System Record Format .........................................................3-899

3.5.5.3.2.1 Common Subnet Table for the HRPD Extended System Record .....3-9510

The Common Subnet Table for the HRPD Extended System Record consists of11

records with the following format:....................................................................3-9512

3.5.6 PUZL Parameter Blocks...................................................................................3-9513

3.5.6.1 PUZL Dimensions Parameter Block ...........................................................3-9614

3.5.6.2 PUZL Priorities Parameter Block................................................................3-9815

3.5.6.3 User Zone Parameter Block .......................................................................3-9916

3.5.6.4 Preferred User Zone List Parameter Block ...............................................3-10117

3.5.7 Preferred User Zone List (PUZL) ....................................................................3-10218

3.5.7.1 User Zone Type Specific Fields ................................................................3-10719

3.5.7.1.1 User Zone Type: Broadcast RF Coverage Based ................................3-10720

3.5.7.1.2 User Zone Type: Broadcast Geo-based ............................................3-10721

3.5.7.1.2.1 Circle...........................................................................................3-10722

3.5.7.1.2.2 Segmented Linear .......................................................................3-10823

3.5.7.1.2.3 Polygon.......................................................................................3-11024

3.5.7.1.3 User Zone Type: Mobile Specific RF Coverage Based - Overhead25

Parameter Determined .....................................................................................3-11226

3.5.7.1.3.1 SID Only......................................................................................3-11227

3.5.7.1.3.2 SID and NID ...............................................................................3-11328

3.5.7.1.3.3 SID and BASE_ID ........................................................................3-11329

3.5.7.1.3.4 Base Station Latitude and Longitude ..........................................3-11430

3.5.7.1.3.5 User Zone Center Point and Radius ............................................3-11531

3.5.7.1.4 User Zone Type: Mobile Specific Geo-Based ....................................3-11632

8/12/2019 TIA-EIA-683-C

9/246

TIA-683-C

CONTENTS

v

3.5.7.1.5 User Zone Type: Mobile Specific Geo-Based Separate Carrier .......3-1161

3.5.8 3GPDParameter Blocks................................................................................3-1172

3.5.8.1 3GPD Operation Capability Parameters ...................................................3-1183

3.5.8.2 3GPD Operation Mode Parameters ..........................................................3-1194

3.5.8.3 SimpleIP Capability Parameters .............................................................3-1205

3.5.8.4 MobileIP Capability Parameters ...............................................................3-1216

3.5.8.5 SimpleIP User Profile Parameters ............................................................3-1237

3.5.8.6 Mobile IP User Profile Parameters............................................................3-1258

3.5.8.12 HRPD Access Authentication Capability Parameters..............................3-1339

3.5.8.13 HRPD Access Authentication User Profile Parameters ...........................3-13310

3.5.8.14 HRPD Access Authentication CHAP SS Parameters ...............................3-13411

4 BASE STATION PROCEDURES ..................................................................................4-112

4.1 Reserved .................................................................................................................4-113

4.2 Initiation of the Programming Procedures ...............................................................4-114

4.2.1 User-Initiated Procedure ...................................................................................4-115

4.2.2 Network-Initiated Procedure..............................................................................4-216

4.3 Programming Data Download ................................................................................4-217

4.3.1 OTA Data Message Processing...........................................................................4-218

4.3.2 SSD Update and re-authentication....................................................................4-519

4.3.3 Activation of Message Encryption......................................................................4-520

4.3.4 Activation of Voice Privacy Mode .......................................................................4-521

4.3.5 Secure Mode .....................................................................................................4-622

4.3.5.1 Generation of Secure Mode Ciphering Key...................................................4-623

4.3.5.2 Encryption and Decryption of messages in Secure Mode .............................4-724

4.4 Termination of the Programming Procedure ............................................................4-725

4.5.1 Message Contents ...........................................................................................4-1026

4.5.1.1 Configuration Request Message.................................................................4-1027

4.5.1.2 Download Request Message ......................................................................4-1028

4.5.1.3 MS Key Request Message ..........................................................................4-1229

4.5.1.4 Key Generation Request Message ..............................................................4-1330

4.5.1.5 Re-Authenticate Request Message.............................................................4-1331

8/12/2019 TIA-EIA-683-C

10/246

TIA-683-C

CONTENTS

vi

4.5.1.6 Commit Request Message..........................................................................4-141

4.5.1.7 Protocol Capability Request Message.........................................................4-142

4.5.1.8 SSPR Configuration Request Message .......................................................4-143

4.5.1.9 SSPR Download Request Message .............................................................4-154

4.5.1.10 Validation Request Message .................................................................4-165

4.5.1.11 OTAPA Request Message ......................................................................4-176

4.5.1.12 PUZL Configuration Request Message .....................................................4-177

4.5.1.13 PUZL Download Request Message ...........................................................4-208

4.5.1.14 3GPD Configuration Request Message.....................................................4-219

4.5.1.15 3GPD Download Request Message ..........................................................4-2210

4.5.1.16 Secure Mode Request Message ................................................................4-2311

4.5.2 NAMParameter Blocks ...................................................................................4-2412

4.5.2.1 CDMA/Analog NAM Download ..................................................................4-2413

4.5.2.2 Mobile Directory Number ..........................................................................4-2714

4.5.2.3 CDMA NAM Download...............................................................................4-2815

4.5.2.4 IMSI_T Parameter Block ............................................................................4-3016

4.5.3 SSPR Parameter Blocks ..................................................................................4-3017

4.5.3.1 Preferred Roaming List Parameter Block ...................................................4-3118

4.5.4 Validation Parameter Blocks ...........................................................................4-3219

4.5.4.1 Verify SPC.................................................................................................4-3220

4.5.4.2 Change SPC ..............................................................................................4-3321

4.5.4.3 Validate SPASM ........................................................................................4-3322

4.5.5 Reserved .........................................................................................................4-3423

4.5.6 PUZL Parameter Blocks...................................................................................4-3424

4.5.6.1 User Zone Insert and User Zone Update ....................................................4-3525

4.5.6.2 User Zone Delete .......................................................................................4-3626

4.5.6.3 User Zone Priority Change.........................................................................4-3727

4.5.6.4 PUZL Flags................................................................................................4-3828

4.5.7 3GPDParameter Blocks..................................................................................4-3929

4.5.7.1 3GPD Operation Mode Parameters ............................................................4-3930

4.5.7.2 SimpleIP User Profile Parameters ..............................................................4-4031

8/12/2019 TIA-EIA-683-C

11/246

TIA-683-C

CONTENTS

vii

4.5.7.3 Mobile IP User Profile Parameters..............................................................4-411

4.5.7.9 HRPD Access Authentication User Profile Parameters ...............................4-482

4.5.7.10 HRPD Access Authentication CHAP SS Parameters .................................4-483

5 KEY EXCHANGE PROCEDURES................................................................................5-14

5.1 Mobile Station Requirements for A_KEY_P_REV < 00000011.................................5-15

5.1.1 Random Number Generation.............................................................................5-16

5.1.2 Mobile Station Result ........................................................................................5-17

5.1.3 A-key Computation ...........................................................................................5-18

5.2 Base Station Requirements for A_KEY_P_REV < 00000011....................................5-19

5.2.1 Generation of the Key Exchange Parameters .....................................................5-110

5.2.2 Base Station Result...........................................................................................5-211

5.2.3 A-key Computation ...........................................................................................5-212

5.3 Mobile Station Requirements for A_KEY_P_REV > 00000010.................................5-213

5.3.1 Random Number Generation For Diffie-Hellman Key Exchange Procedure ........5-214

5.3.2 Mobile Station Result ........................................................................................5-315

5.3.3 A Key and Root Key Computation for A_KEY_P_REV = 00000011 ....................5-316

5.3.4 Root Key Computation for A_KEY_P_REV = 00000100.....................................5-317

5.4 Base Station Requirements for A_KEY_P_REV > 00000010....................................5-318

5.4.1 Generation of the Key Exchange Parameters Root Key ......................................5-319

5.4.2 Base Station Result...........................................................................................5-420

5.4.3 A Key and Root Key Computation for A_KEY_P_REV = 00000011 ....................5-421

5.4.4 Root Key K Computation for A_KEY_P_REV = 00000100..................................5-522

ANNEX A RESERVED...............................................................................................A-123

ANNEX B BIBLIOGRAPHY ....................................................................................... B-124

ANNEX C SYSTEM SELECTION AND ACQUISITION ................................................ C-125

C.1 Introduction ......................................................................................................... C-126

C.2 Accelerated System Selection ................................................................................ C-227

C.2.1 Using Positive and Negative Systems ............................................................... C-228

C.2.2 PCS Block Mode System Selection ................................................................... C-329

C.2.3 Special Cases and Considerations ................................................................... C-330

C.3 Preferred Roaming List Maintenance ..................................................................... C-431

8/12/2019 TIA-EIA-683-C

12/246

TIA-683-C

CONTENTS

viii

ANNEX D SYSTEM SELECTION AND THE PREFERRED USER ZONE LIST.............. D-11

2

8/12/2019 TIA-EIA-683-C

13/246

TIA-683-C

FIGURES

ix

Figure 2.2.1-1 OTASP Data MessageEncapsulation.........................................................2-11

Figure 2.2.1-2 OTASP Data MessageCRC........................................................................2-22

Figure 2.2.2-1 OTASP Data Message Capsule Segmentation on the Forward Analog3

Voice Channel...........................................................................................2-34

Figure 2.2.2-2 OTASP Data MessageCapsule Segmentation on the Reverse Analog Voice5

Channel....................................................................................................2-46

7

8/12/2019 TIA-EIA-683-C

14/246

TIA-683-C

TABLES

x

Table 3.2-1 System Selection Code. .................................................................................3-31

Table 3.2.2.2-1 Valid Service Configuration Attributes for Service Option 18 ..................3-72

Table 3.2.2.2-2 Valid Service Configuration Attributes for Service Option 19 ..................3-73

Table 3.3.6-1 Service Programming Code Values ...........................................................3-314

Table 3.5-1 Reverse Link Messages................................................................................3-355

Table 3.5.1.2-1 Result Codes.........................................................................................3-396

Table 3.5.1.7-1 Feature Identifier ..................................................................................3-447

Table 3.5.1.7-2 Band/mode Capability Information .......................................................3-458

Table 3.5.2-1 NAM Parameter Block Types ....................................................................3-569

Table 3.5.3-1 SSPR Parameter Block Types .................................................................3-6410

Table 3.5.5.2-1 Acquisition Record Type Values ............................................................3-7411

Table 3.5.5.2-2 Extended Acquisition Record Type Values .............................................3-7412

Table 3.5.5.2.1.1-1 Cellular System A/B Selection Type Values.....................................3-7513

Table 3.5.5.2.1.2-1 Cellular CDMA and JTACS CDMA Standard Channel Selection Type14

Values.....................................................................................................................3-7615

Table 3.5.5.2.1.5-1 PCS CDMA Frequency Blocks .........................................................3-7816

Table 3.5.5.2.1.7-1 JTACS CDMA Standard Channel Selection Type Values..................3-7917

Table 3.5.5.3-1 NID_INCL Values ..................................................................................3-8818

Table 3.5.5.3.2-1 Type-specific system ID record ...........................................................3-9119

Table 3.5.5.3.2-2 Type-specific system ID record ...........................................................3-9220

Table 3.5.5.3.2-3 NID_INCL Values................................................................................3-9221

Table 3.5.6-1. PUZL Parameter Block Types .................................................................3-9622

Table 3.5.7-1 User Zone Type Values...........................................................................3-10623

Table 3.5.7.1.2-1 Geo Type Values...............................................................................3-10724

Table 3.5.7.1.3-1 Overhead Parameter (OHP) Type Values...........................................3-11225

Table 3.5.8-1 3GPD Parameter Block Types.................................................................3-11826

Table 3.5.82-1 Operation Mode ...................................................................................3-12027

Table 3.5.8.3-1 AUTH_ALGORITHM Parameter Values ................................................3-12128

Table 3.5.8.4-1 MN-AAA_AUTH_ALGORITHM Parameter Values ..................................3-12229

Table 3.5.8.4-2 MN-HA_AUTH_ALGORITHM Parameter Values....................................3-12330

Table 3.5.8.5-1 Authentication Algorithm Parameter Values for SimpleIP ....................3-12531

8/12/2019 TIA-EIA-683-C

15/246

TIA-683-C

TABLES

xi

Table 3.5.8.6-1 Authentication Algorithm Parameter Values........................................3-1281

Table 4.5-1 Forward Link Messages.................................................................................4-92

Table 4.5.2-1 NAMParameter Block Types ....................................................................4-243

Table 4.5.3-1 SSPR Parameter Block Types ...................................................................4-314

Table 4.5.4-1 Validation Parameter Block Types ............................................................4-325

Table 4.5.4.1-1. BCD Mapping......................................................................................4-336

Table 4.5.6-1 PUZL Parameter Block Types ...................................................................4-357

Table 4.5.7-1 3GPD Parameter Block Types...................................................................4-398

Table C.1-1 Preferred Roaming List ................................................................................ C-19

Table C.1-2 Acquisition Table ......................................................................................... C-110

Table C.1-3 System Table ............................................................................................... C-211

12

8/12/2019 TIA-EIA-683-C

16/246

TIA-683-C

FOREWARD

xii

(This foreword is not part of this Standard)1

These technical requirements form a standard for Over-the-Air Service Provisioning of2

mobile stations. A mobile station operating in either the analog or the spread spectrum3

(CDMA) mode conforming with various versions of the CDMA standards, such as4

TIA/EIA/IS-2000-A, TIA/EIA/IS-2000, TIA/EIA-95-B, TIA/EIA/IS-95-A (inclusive of5

TSB74), or ANSI J-STD-008 and this standard can be activated over the air in any system6

conforming with these standards.7

The scope of this standard covers over-the-air provisioning of mobile station operational8

parameters. This standard does not address the quality or reliability of Over-the-Air9

Service Provisioning, nor does it cover equipment performance or measurement10

procedures.11

12

SECTION SUMMARY13

1.Introduction. This section defines the terms, references, protocols and network14

reference model used in this document.15

2. Message Transmission Procedures. This section describes the lower-layer16

procedures used for transmission of messages for Over-the-Air Service Provisioning.17

3. Mobile Station Procedures. This section describes the mobile station procedures18

for Over-the-Air Service Provisioning.19

4. Base Station Procedures. This section describes the base station procedures for20

Over-the-Air Service Provisioning.21

5. Key Exchange Procedures. This section describes the requirements for key22exchange procedures.23

8/12/2019 TIA-EIA-683-C

17/246

TIA-683-C

NOTES

xiii

1. The following verbal forms are used: Shall and shall not identify requirements to1

be followed strictly to conform to the standard and from which no deviation is2

permitted. Should and should not indicate that one of several possibilities is3

recommended as particularly suitable, without mentioning or excluding others; that4a certain course of action is preferred but not necessarily required; or that (in the5

negative form) a certain possibility or course of action is discouraged but not6

prohibited. May and need not indicate a course of action permissible within the7

limits of the standard. Can and cannot are used for statements of possibility and8

capability, whether material, physical, or causal.9

2. Footnotes appear at various points in this specification to elaborate and further10

clarify items discussed in the body of the specification.11

3. Unless indicated otherwise, this document presents numbers in decimal form.12

Binary numbers are distinguished in the text by the use of single quotation marks.13

In some tables, binary values may appear without single quotation marks if table14

notation clearly specifies that values are binary. The character x is used to15

represent a binary bit of unspecified value. For example xxx00010 represents any16

8-bit binary value such that the least significant five bits equal 00010.17

Hexadecimal numbers (base 16) are distinguished in the text by use of the form18

0xhh where hh represents a string of hexadecimal digits. For example, 0x2fa119

represents a number whose binary value is 0010111110100001 and whose decimal20

value is 12193. Note that the exact number of bits in the binary representation of a21

hexadecimal number strictly depends on the implementation requirements for the22

variable being represented.23

4. Numeric information is used to describe the operation of the mobile station. The24

following subscripts are used in this document to clarify the use of the numeric25

information:26

s indicates a value stored in a mobile stations temporary memory.27

r indicates a value received by a mobile station over a forward analog channel28

or a CDMA Forward Channel.29

p indicates a value set in a mobile stations permanent security and30

identification memory.31

s-p indicates a value stored in a mobile stations semi-permanent security and32


5. The term mobile station is equivalent to the term personal station.34

6. IMSI_T Parameter Block does not apply for the mobile station conforming with35

TIA/EIA/IS-95-A (inclusive of TSB74) or ANSI J-STD-008.36

7. IMSI_M in this document is equivalent to IMSI defined in TIA/EIA/IS-95-A (inclusive37

of TSB74) or ANSI J-STD-008.38

8/12/2019 TIA-EIA-683-C

18/246

TIA-683-C

xiv

The following standards contain provisions that, through reference in this text, constitute1

provisions of this Standard. At the time of publication, the editions indicated were valid.2

All standards are subject to revision, and parties to agreements based upon this Standard3

are encouraged to investigate the possibility of applying the most recent editions of the4

standards indicated below. ANSI and TIA maintain registers of currently valid national5

standards published by them.6

1. TIA/EIA-95-B, Mobile Station-Base Station Compatibility Standard for Dual-Mode7

Spread Spectrum Cellular System.8

2. Common Cryptographic Algorithms, Rev. C. Information disclosed in this document is9

subject to the export jurisdiction of the US Department of Commerce as specified in10

Export Administration Regulations (title 15 CFR parts 730 through 774 inclusive). A11

license issued by the Department of Commerce is required for the export of such12

technical data. Contact the Telecommunications Industry Association, Arlington, VA.13

3. Interface Specification for Common Cryptographic Algorithms, Rev. C. Contact the14

Telecommunications Industry Association, Arlington, VA.15

4. TSB58-E, Administration of Parameter Value Assignments for TIA/EIA Spread16

Spectrum Standards.17

5. TIA/EIA/IS-2000.2-C, Physical Layer Standard for cdma2000 Spread Spectrum18

Systems, May 2002.19

6. TIA/EIA/IS-2000.4-C, Signaling Link Access Control (LAC) Standard for cdma200020

Spread Spectrum Systems, May 2002.21

7. TIA/EIA/IS-2000.5-C, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread22

Spectrum Systems, May 2002.23

8. Enhanced Cryptographic Algorithms, Rev. A. Information disclosed in this document is24

subject to the export jurisdiction of the US Department of Commerce as specified in25

Export Administration Regulations (title 15 CFR parts 730 through 774 inclusive). The26

information contained herein may not be exported or re-exported to Cuba, Iran, Iraq,27

Libya, North Korea, Sudan, or Syria. Contact the Telecommunications Industry28

Association, Arlington, VA or http://ftp.tiaonline.org/tr-29

45/tr45ahag/public%20documents.30

9. TIA/EIA/IS-856-1 cdma2000 High Rate Packet Data Air Interface Specifications,31

Addendum 1, January 2002.32

10. IETF RFC 1334, PPP Authentication Protocols, October 1992.33

11. IETF RFC 1994, PPP Challenge Handshake Authentication Protocol (CHAP), August34

1996.35

12. IETF RFC 2002, IP Mobility Support, October 1996.36

13. IETF RFC 2344, Reverse Tunneling for Mobile IP, August 1996.37
http://ftp.tiaonline.org/tr-45/tr45ahag/public%20documentshttp://ftp.tiaonline.org/tr-45/tr45ahag/public%20documentshttp://ftp.tiaonline.org/tr-45/tr45ahag/public%20documentshttp://ftp.tiaonline.org/tr-45/tr45ahag/public%20documentshttp://ftp.tiaonline.org/tr-45/tr45ahag/public%20documents

8/12/2019 TIA-EIA-683-C

19/246

TIA-683-C

REFERENCES

xv

14. IETF RFC 2486, The Network Access Interface, January 1999.1

15. IETF RFC 3012, Mobile IPv4 Challenge/Response Extensions, November 1999.2

8/12/2019 TIA-EIA-683-C

20/246

TIA-683-C

xvi

No text.1

8/12/2019 TIA-EIA-683-C

21/246

TIA-683-C

1-1

1 INTRODUCTION1

1.1 General Description2

Over-the-Air Service Provisioning (OTASP) consists of the following features provisioned3

over-the-air:4

Download of NAM operational parameters.5

Electronic Key Exchange for securely establishing the A-key and Root Key.6

System Selection for Preferred Roaming (SSPR) for providing mobile stations with7

information allowing acquisition of the preferred system in an area.8

Preferred User Zone List (PUZL) for providing mobile stations which support the9

optional User Zone feature with information allowing usage of the preferred user10

zone in an area.11

Download of 3G packet data operational parameters.12

Service Programming Lock (SPL), if provided, prevents the over-the-air provisioning of13

certain mobile station parameters by an unauthorized network entity.14

This document describes Over-the-Air Service Provisioning in CDMA and analog systems.15

The procedures defined are intended to be extendable and flexible enough to be used with16

future air interface specifications. The procedures in this document do not require support17

for continuation of the service provisioning process following a CDMA-to-analog handoff.18

1.2 Terms and Numeric Information19

1.2.1 Terms20

3GPD.Third Generation Packet Data21

AC. See Authentication Center.22

Access Authentication. A procedure in which the Access Terminal (AT) is authenticated23

by the AN-AAA (Access Network Authentication, Authorization and Accounting entity).24

Activation Code. A user-entered combination of a specified Feature Code (*FC) and25

defined group of at least two dialed digits (System Selection Code) that specify the user26

selection of a Band and a Block operated by the selected service provider.27

A-key. A secret, 64-bit pattern stored in the mobile station and HLR/AC. It is used to28

generate/update the mobile stations Shared Secret Data and to validate SPASM.29

Analog Voice Channel. An analog channel on which a voice conversation occurs and on30

which brief digital messages may be sent from a base station to a mobile station or from a31

mobile station to a base station.32

Authentication. A procedure used by a base station to validate a mobile stations identity.33

Authentication Center (AC). An entity that manages the authentication information34

related to the mobile station.35

8/12/2019 TIA-EIA-683-C

22/246

TIA-683-C

1-2

Base Station. A fixed station used for communicating with mobile stations. Depending1

upon the context, the term base station may refer to a cell, a sector within a cell, an MSC,2

an OTAF, or other part of the wireless system. (See also MSC and OTAF.)3

CRC. See Cyclic Redundancy Code.4

Cyclic Redundancy Code (CRC). A class of linear error detecting codes which generate5

parity check bits by finding the remainder of a polynomial division.6

Electronic Serial Number (ESN). A 32-bit number assigned by the mobile station7

manufacturer, uniquely identifying the mobile station equipment.8

ESN. SeeElectronic Serial Number.9

Forward CDMA Channel. A CDMA Channel from a base station to mobile stations. The10

Forward CDMA Channel contains one or more code channels that are transmitted on a11

CDMA frequency assignment using a particular pilot PN offset.12

Forward Analog Voice Channel (FVC). An analog voice channel used from a base station13

to a mobile station.14

Forward Traffic Channel. A code channel used to transport user and signaling traffic15

from the base station to the mobile station.16

FRESH. A 15-bit value used by the mobile station and the base station as the17

cryptographic synchronizer for encrypting parameter data in Secure Mode. FRESH may be18

set by the encrypting side to any value, including a monotonically incremented counter, as19

long as this value is not repeated for the duration of the Secure Mode in progress.20

HLR. See Home Location Register.21

Home Location Register (HLR). The location register to which a MIN/IMSI is assigned for22

record purposes such as subscriber information.23

Home System. The cellular system in which the mobile station subscribes for service.24

HRPD. High Rate Packet Data. See [9].25

IMSI. See International Mobile Station Identity.26

IMSI_M. MIN based IMSI using the lower 10-digits to store the MIN.27

IMSI_O. The operational value of IMSI used by the mobile station for operation with the28

base station.29

IMSI_T. IMSI not associated with MIN. 15-digits or fewer.30

International Mobile Station Identity (IMSI). A method of identifying stations in the31

land mobile service as specified in ITU-T Recommendation E.212.32

Long Code Mask. A 42-bit binary number that creates the unique identity of the long33

code. See alsoPublic Long Code, Private Long Code, Public Long Code Mask and Private34

Long Code Mask.35

LSB. Least significant bit.36

MCC. See Mobile Country Code.37

8/12/2019 TIA-EIA-683-C

23/246

TIA-683-C

1-3

Mobile Country Code (MCC). A part of the E.212 IMSI identifying the home country. See1

ITU-T Recommendation E.212.2

Mobile Directory Number. A dialable directory number which is not necessarily the same3

as the mobile stations air interface identification, i.e., MIN, IMSI_M or IMSI_T.4

MIN. See Mobile Identification Number.5

MNC. See Mobile Network Code.6

Mobile Identification Number (MIN). The 34-bit number that is a digital representation of7

the 10-digit number assigned to a mobile station.8

Mobile Network Code (MNC). A part of the E.212 IMSI identifying the home network9

within the home country. See ITU-T Recommendation E.212.10

Mobile Station. A station, fixed or mobile, which serves as the end users wireless11

communication link with the base station. Mobile stations include portable units (e.g.,12

hand-held personal units) and units installed in vehicles.13

Mobile Station Originated Call. A call originating from a mobile station.14

Mobile Station Terminated Call. A call received by a mobile station (not to be confused15

with a disconnect or call release).16

Mobile Switching Center (MSC). A configuration of equipment that provides wireless17

radiotelephone service. Also called the Mobile Telephone Switching Office (MTSO).18

MSB. Most significant bit.19

MSC. See Mobile Switching Center.20

NAM. See Number Assignment Module.21

Network. A network is a subset of a wireless system, such as an area-wide wireless22

network, a private group of base stations, or a group of base stations set up to handle a23

special requirement. A network can be as small or as large as needed, as long as it is fully24

contained within a system. See also System.25

Network Identification (NID). A number that uniquely identifies a network within a26

wireless system. See also System Identification.27

NID. See Network Identification.28

Number Assignment Module (NAM). A set of MIN/IMSI-related parameters stored in the29

mobile station.30

OTAF. See Over-the-Air Service Provisioning Function.31

Over-the-Air Service Provisioning Function (OTAF). A configuration of network32

equipment that controls OTASP functionality and messaging protocol.33

OTAPA. See Over-the-Air Parameter Administration.34

OTASP. See Over-the-Air Service Provisioning.35

Over-the-Air Parameter Administration (OTAPA). Network initiated OTASP process of36

provisioning mobile station operational parameters over the air interface.37

8/12/2019 TIA-EIA-683-C

24/246

TIA-683-C

1-4

Over-the-Air Service Provisioning (OTASP). A process of provisioning mobile station1

operational parameters over the air interface.2

Parity Check Bits. Bits added to a sequence of information bits to provide error detection,3

correction, or both.4

Preferred User Zone List (PUZL). A list that provides the mobile station with the5

information for the User Zones to which the mobile user is subscribed.6

PDSN. Packet Data Service Node.7

Private Long Code. The long code characterized by the private long code mask.8

Private Long Code Mask. The long code mask used to form the private long code.9

Public Long Code. The long code characterized by the public long code mask.10

Public Long Code Mask. The long code mask used to form the public long code. The11

mask contains the ESN of the mobile station. See also Private Long Code Mask.12

PUZL. See Preferred User Zone List.13

Release. A process that the mobile station and base station use to inform each other of14

call disconnect.15

Reverse CDMA Channel. The CDMA Channel from the mobile station to the base station.16

From the base stations perspective, the Reverse CDMA Channel is the sum of all mobile17

station transmissions on a CDMA frequency assignment.18

Roamer. A mobile station operating in a wireless system (or network) other than the one19

from which service was subscribed.20

Secure Mode. Network initiated mode of communicating operational parameters between21

a mobile station and network based provisioning entity in an encrypted form.22

SMCK. Secure Mode Ciphering Key.23

Service Option. A service capability of the system. Service options may be applications24

such as voice, data, or facsimile. See [4].25

Service Programming Code (SPC). A secret code assigned to the mobile station and26

known to the authorized network entity.27

Service Programming Lock (SPL). A protection provided for preventing the over-the-air28

provisioning of certain mobile station parameters by unauthorized network entity by way of29

verifying the Service Programming Code (SPC).30

Shared Secret Data (SSD). A 128-bit pattern stored in the mobile station (in semi-31

permanent memory) and known by the base station. SSD is a concatenation of two 64-bit32

subsets: SSD_A, which is used to support the authentication procedures, and SSD_B,33

which serves as one of the inputs to the process generating the encryption mask and34

private long code.35

SID. See System Identification.36

SPASM. See Subscriber Parameter Administration Security Mechanism.37

8/12/2019 TIA-EIA-683-C

25/246

TIA-683-C

1-5

SPC. See Service Programming Code.1

SPL. See Service Programming Lock.2

SSD. See Shared Secret Data.3

SSPR. See System Selection for Preferred Roaming.4

Subscriber Parameter Administration Security Mechanism (SPASM). Security5

mechanism protecting parameters and indicators of active NAM from programming by an6

unauthorized network entity during the OTAPA session.7

System. A system is a wireless telephone service that covers a geographic area such as a8

city, metropolitan region, county, or group of counties. See also Network.9

System Identification (SID). A number uniquely identifying a wireless system.10

System Selection Code. A part of the Activation Code that specifies the user selection of a11

Band and a Block operated by the selected service provider.12

System Selection for Preferred Roaming (SSPR). A feature that enhances the mobile13

station system acquisition process based on the set of additional parameters stored in the14

mobile station in the form of a Preferred Roaming List (PR_LISTs-p).15

Traffic Channel. A communication path between a mobile station and a base station used16

for user and signaling traffic. The term Traffic Channel implies a Forward Traffic Channel17

and Reverse Traffic Channel pair. See also Forward Traffic Channel and Reverse Traffic18

Channel.19

User Zone (UZ). CDMA Tiered Service Offerings are defined by User Zones that are20

geographical groupings of services.21

UZ. See User Zone.22

Voice Channel. See Analog Voice Channel.23

Voice Privacy. The process by which user voice transmitted over a CDMA Traffic Channel24

is afforded a modest degree of protection against eavesdropping over the air.25

1.2.2 Numeric Information26

Numeric information is used to describe the operation of the mobile station. The following27

subscripts are used to clarify the use of the numeric information:28

s indicates a value stored in a mobile stations temporary memory.29

r indicates a value received by a mobile station over a forward analog control30

channel or a CDMA Forward Channel.31

p indicates a value set in a mobile stations permanent security and identification32

memory.33

s-p indicates a value stored in a mobile stations semi-permanent security and34


This section defines numeric information specifically related to the OTASP.36

8/12/2019 TIA-EIA-683-C

26/246

TIA-683-C

1-6

A_KEY_P_REVp- Protocol revision of the mobile station Key Exchange procedure.1

A_KEY_TEMPs- A secret 64-bit pattern temporarily stored in the mobile station.2

AUTH_OTAPAs - The computed 18-bit result AUTH_SIGNATURE used for validating3

SPASM.4

CUR_SSPR_P_REVs-p Protocol revision of the mobile stations current preferred roaming5

list. This information is used to parse PR_LISTs-p. Retained by the mobile station when6

the power is turned off.7

DATA_P_REVp- Protocol revision of the mobile station NAM Download procedure.8

NAM_LOCKp - The locking indicator set in the mobile station by the base station that9

defines SPASM protection of the programmable parameters in the active NAM during the10

OTAPA session.11

NULL- A value that is not in the specified range of the field or variable.12

NAM_LOCKs- A network controlled status of the SPASM protection of the active NAM for13

the subsequent OTAPA session.14

NAM_LOCK_STATE - a locking state of the mobile station programmable parameters for15

OTAPA. If the NAM_LOCK_STATE = 1, the parameters are locked for network initiated16

programming.17

PARAM_Gs- Key exchange parameter G.18

PARAM_Ps- Key exchange parameter P.19

PR_LISTs-p - Preferred Roaming List. Contains information to assist the mobile station20

system selection and acquisition process. Retained by the mobile station when the power21

is turned off.22

PRL_BLOCK_ID_CURRENTs Parameter Block Identifier for the current Preferred23

Roaming List temporarily stored in the mobile station.24

PUZLs-p Preferred User Zone List. Contains information to assist the mobile station25

during user zone selection and acquisition process. Retained by the mobile station when26

the power is turned off.27

PUZL_P_REVp- Protocol revision of the mobile station PUZL Download procedure.28

RAND_SEED A secret 128-bit pattern temporarily stored in the mobile station.29

RKp- A secret 128-bit pattern permanently stored in the mobile station.30

RK_TEMPs- A secret 128-bit pattern temporarily stored in the mobile station.31

SPCp - Service Programming Code. A secret code assigned to the mobile station and32

known to the authorized network entity. The base station uses the code equal to the SPCp33

for unlocking the mobile station parameters for programming or reprogramming.34

SPCs- Service Programming Code temporarily stored in the mobile station.35

SPL_P_REVp- Protocol revision of the mobile station Service Programming Lock.36

8/12/2019 TIA-EIA-683-C

27/246

TIA-683-C

1-7

SP_LOCK_STATE - A locking state of the mobile station programmable parameters. If the1

SP_LOCK_STATE = 1, the parameters are locked for programming.2

SSPR_P_REVp- Protocol revision of the mobile station SSPR Download procedure and the3

PRL format.4

SECURE_MODE_INDS- Secure Mode indicator. If SECURE_MODE_INDS = 1, current5

programming session is in Secure Mode.6

SMCKs Secure Mode Ciphering Key.7

8

8/12/2019 TIA-EIA-683-C

28/246

TIA-683-C

1-8

No text.1

8/12/2019 TIA-EIA-683-C

29/246

TIA-683-C

2-1

2 MESSAGE TRANSPORT PROTOCOL1

2.1 General2

OTASP Data Messages (see Sections 3 and 4) can be sent over the analog voice channel or3

the CDMA Traffic Channel. In either case, the OTASP Data Messages are sent using a4

Layer 2 protocol that provides reliable delivery and duplicate detection.5

The delivery of OTASP Data Messages does not require sequential delivery of messages by6

the Layer 2 protocol because the Over-the-Air Service Provisioning procedures ensure that7

only one OTASP Data Message is outstanding at any time.8

During the analog mode of operation, OTASP Data Messages are sent using the analog9

transport protocol (see 2.2). During the CDMA mode of operation, OTASP Data Messages10

are sent using the CDMA transport protocol (see 2.3).11

2.2 Analog Transport Protocol12

OTASP Data Messages are transmitted over an analog voice channel using the OTASP13

Transport Message. Signaling on the analog voice channel does not have a Layer 2 protocol14

defined in [1,6]. Because of the large amount of data transported for Over-the-Air Service15

Provisioning, this standard defines a Layer 2 protocol to ensure OTASP Data Message16

integrity. This protocol provides message segmentation, segment acknowledgment, error17

detection and re-transmission.18

2.2.1 OTASP Data MessageEncapsulation19

Each OTASP Data MessageUnit transmitted on an analog voice channel shall consist of an20

8-bit message length field (MSG_LENGTH), an OTASP Data Message, as defined in 3.5 and21

4.5, and a 16-bit CRC, in that order (see Figure 2.2.1-1).22

CRC

8 bits 16 b it s

OTASP Data Mes sa geCapsu le

OTASP Data Mes s age Unit Padding

8 - 201 6 bi ts

MSG_LENGTH

as requ ired8 MSG_LENGTH b its

OTASP Data Mes sa ge

23

Figure 2.2.1-1 OTASP Da t a MessageEncapsulation24

8/12/2019 TIA-EIA-683-C

30/246

TIA-683-C

2-2

The MSG_LENGTH field shall be set to the number of octets in the OTASP Data Message1

plus three.2

The 16-bit CRC is calculated on the MSG_LENGTH field and the OTASP Data Message bits.3

The generator polynomial for this CRC shall be as follows:4

g(x) = x16

+

x12

+

x5+

x0

5

The 16-bit CRC shall be computed according to the following procedure using the logic6

shown in Figure 2.2.1-2:7

Initially, all shift register elements shall be set to logical one and the switches shall8

be set in the position A.9

The register shall be clocked with each OTASP Data Messagebit as an input, most10

significant bit first.11

The switches shall be set in the position B, and the register shall be clocked an12

additional 16 times. The 16 additional output bits shall be the CRC bits.13

The 16 CRC bits shall be transmitted in the order calculated.14

Position A for first k bits

Position B for last 16 bits

Input

Outputx15x12x

5x1x0

1

0

Denotes modulo-2 addition

Denotes one-bit storage element

A

B

A

B

A

B

15

Figure 2.2.1-2 OTASP Da t a MessageCRC16

Padding consisting of zero or more 0 bits shall be added immediately following the OTASP17

Data MessageUnit. The length of the padding shall be such that the resulting OTASP Data18

Message Capsule fits into the minimum possible integral number of OTASP Transport19

Messages(see 2.2.2).20

2.2.2 OTASP Data MessageSegmentation21

Each OTASP Data MessageCapsule (see 2.2.1) sent on an analog voice channel shall be22

segmented and transmitted in one or more OTASP Transport Messages, as defined in23

2.2.3.4 and 2.2.4.3. Figures 2.2.2-1 and 2.2.2-2 illustrate the segmentation process for the24

forward and reverse analog voice channels, respectively.25

26

8/12/2019 TIA-EIA-683-C

31/246

TIA-683-C

2-3

...

...

Segment 1 Segment 2 Segment N

OTASP Data MessageCapsule

OTASP Transport Message

...Word 1 Word 2 Word 3 Word 4 Word n

Note: The Contents of the

OTASP Data MessageCapsule is segmentedinto OTASP_DATA fieldsof the Words 3 n of the


OTASP_DATA fields for Word 3

of the OTASP Transport MessageOTASP_DATA fields for Word n of

the OTASP Transport Message

OTASP_DATA fields for Word 4 of

the OTASP Transport Message

1

Figure 2.2.2-1 OTASP Da t a MessageCapsule Segmentation on the Forward Analog2

Voice Channel.3

4

8/12/2019 TIA-EIA-683-C

32/246

TIA-683-C

2-4

...Segment 1 Segment 2 Segment N

OTASP Data MessageCapsule

OTASP_DATA fields for Word 2 ofthe OTAPA Transport Message


Word 1 Word 2 Word 3 Word 4

OTASP_DATA fields for Word 3 of

the OTAPA Transport Message

OTASP_DATA fields for Word 4 ofthe OTAPA Transport Message

Note: The contents of the

OTASP Data MessageCapsule is segmented intothe OTASP_DATA fields of

Word 2-4 of the OTASP

Transport Message

1

Figure 2.2.2-2 OTASP Da t a MessageCapsule Segmentation on the Reverse Analog2

Voice Channel3

2.2.3 Mobile Station Procedures4

OTASP Data Messages are sent and received on analog voice channels only when the5

mobile station is in the Conversation Task (see 2.6.4.4 of [1]). The mobile station shall6

transmit OTASP Transport Messages in accordance with the procedures in 2.7.2 of [1].7

Mobile stations implementing the Over-the-Air Service Provisioning feature shall comply8

with the following requirements in addition to those of 2.6.4.4 of [1].9

2.2.3.1 OTASP Transport MessageAcknowledgment and Re-transmission10

When the mobile station sends an OTASP Transport Message, it starts the OTASP11

acknowledgment timer. The timer is disabled when an OTASP Transport Confirmation12

Messageis received.13

After sending an OTASP Transport Message, the mobile station shall not send a new OTASP14

Transport Message until it has received an OTASP Transport Confirmation Message15

acknowledging the message that has been sent.16

If the OTASP acknowledgment timer expires and the OTASP TransportMessage has been17

sent fewer than three times, the mobile station shall resend the OTASP TransportMessage18

and reset the OTASP acknowledgment timer to two seconds. If the OTASP acknowledgment19

timer expires and the OTASP Transport Message has been sent three times, the mobile20

station shall enter the Release Task (see 2.6.4.5 of [1]).21

8/12/2019 TIA-EIA-683-C

33/246

TIA-683-C

2-5

2.2.3.2 Message Transmission1

While the mobile station is in the Conversation Task, the following messages can be sent in2

addition to those listed in 2.6.4.4 of [1]:3

1. OTASP Transport Message:4

After sending the message, the mobile station shall set the OTASP acknowledgment5

timer to two seconds. The mobile station shall construct the OTASP Transport6

Message as follows:7

If the OTASP_DATA field of the OTASP TransportMessage contains an entire8

OTASP Data MessageCapsule, the mobile station shall set TX_SEQ_NUMsto9

00000, shall set the SEQ_NUM field equal to TX_SEQ_NUMs, and shall set the10

value of the B/F field to 11.11

If the OTASP_DATA field of the OTASP TransportMessage contains the first12

segment of the segmented OTASP Data MessageCapsule, the mobile station13

shall set TX_SEQ_NUMsto 00000, shall set the SEQ_NUM field equal to14

TX_SEQ_NUMsand shall set the value of the B/F field to 10.15

If the OTASP_DATA field of the OTASP TransportMessage contains a segment16

other than the first segment of the segmented OTASP Data MessageCapsule, the17

mobile station shall perform the following:18

- If the OTASP_DATA field of the OTASP TransportMessage contains a19

segment other than the final segment of the OTASP Data MessageCapsule,20

the mobile station shall set TX_SEQ_NUMsto (TX_SEQ_NUMs + 1) modulo21

32, shall set the SEQ_NUM field equal to TX_SEQ_NUMsand shall set the22


- If the OTASP_DATA field of the OTASP TransportMessage contains the final24

segment of the OTASP Data MessageCapsule, the mobile station shall set25

TX_SEQ_NUMsto (TX_SEQ_NUMs + 1) modulo 32, shall set the SEQ_NUM26

field equal to TX_SEQ_NUMsand shall set the value of the B/F field to 01.27

The mobile station shall remain in the Conversation Task.28

2. OTASP Transport Confirmation Message:29

The mobile station shall set the SEQ_ACK field and DMU_CRC_OK field as specified30

in 2.2.3.3. The mobile station shall remain in the Conversation Task.31

2.2.3.3 Message Reception32

While the mobile station is in the Conversation Task, the following messages can be33

received in addition to those listed in 2.6.4.4 of [1]. When any message is received, the34

mobile station shall perform all actions specified in 2.6.4.4 of [1]that apply to a message35

reception. The mobile station shall take the actions specified below for each message:36


If the value of ESNrreceived in the OTASP Transport Messagedoes not match the38

ESNp that identifies the mobile station, the mobile station shall turn off the39

8/12/2019 TIA-EIA-683-C

34/246

TIA-683-C

2-6

transmitter and then enter the Serving-System Determination Task (see 2.6.3.12 of1

[1]).2

If the value of ESNrreceived in theOTASP Transport Messagematches the ESNp,3

the mobile station shall do the following:4

The mobile station shall send an OTASP TransportConfirmation Messagewithin5

750 ms after receiving the last bit of the OTASP Transport Message. The mobile6

station shall set the SEQ_ACK field equal to SEQ_NUMrreceived in the OTASP7

Transport Message. The mobile station shall set the DMU_CRC_OK field as8

specified below.9

If the value of the B/F field of the received message is 11, the OTASP_DATA10

field of the received message contains an OTASP Data MessageCapsule in its11

entirety (i.e., contains an unsegmented OTASP Data MessageCapsule). The12

mobile station shall discard any incomplete OTASP Data MessageCapsule being13

reassembled. If the CRC of the OTASP Data MessageUnit checks (see 2.2.1),14

the mobile station shall set the DMU_CRC_OK field of the OTASP Transport15

Confirmation Messageto 1, and shall process the OTASP Data Messageas16

specified in Section 3; otherwise, the mobile station shall set the DMU_CRC_OK17

field of the OTASP Transport Confirmation Messageto 0, and shall discard the18

OTASP Data Message Capsule.19

If the value of the B/F field of the received message is 10, the mobile station20

shall discard any incomplete OTASP Data MessageCapsule being reassembled,21

and shall store the OTASP_DATA field of the received message as the first22

segment of an OTASP Data MessageCapsule to be reassembled. The mobile23

station shall set RX_SEQ_NUMsto the value of the SEQ_NUM field of the24

received message. The mobile station shall set the DMU_CRC_OK field of the25

OTASP Transport Confirmation Messageto 0.26

If the value of the B/F field of the received message is 00 and a segmented27

OTASP Data MessageCapsule is being reassembled, the mobile station shall28

perform the following:29

- If (RX_SEQ_NUMs+ 1) modulo 32 is equal to the value of the SEQ_NUM field30

of the received message, the mobile station shall store the OTASP_DATA field31

of the received message as the next segment of the OTASP Data Message32

Capsule being reassembled, and shall increment RX_SEQ_NUMs, modulo33

32.34

- If RX_SEQ_NUMsis equal to the value of the SEQ_NUM field of the received35

message, the mobile station shall discard the OTASP_DATA field of the36

received message.37

- If neither RX_SEQ_NUMsnor (RX_SEQ_NUMs+ 1) modulo 32 is equal to the38

value of the SEQ_NUM field of the received message, the mobile station shall39

discard the OTASP_DATA field of the received message and shall discard the40

incomplete OTASP Data MessageCapsule being reassembled.41

8/12/2019 TIA-EIA-683-C

35/246

TIA-683-C

2-7

- The mobile station shall set the DMU_CRC_OK field of the OTASP Transport1

Confirmation Messageto 0.2

If the value of the B/F field of the received message is 00, and if no segmented3


discard the OTASP_DATA field of the received message. The mobile station shall5

set the DMU_CRC_OK field of the OTASP Transport Confirmation Messageto 0.6

If the value of the B/F field of the received message is 01 and if a segmented7



- If (RX_SEQ_NUMs+ 1) modulo 32 is equal to the value of the SEQ_NUM field10

of the received message, the mobile station shall store the OTASP_DATA field11

of the received message as the last segment of the OTASP Data Message12

Capsule being reassembled and shall increment RX_SEQ_NUMs, modulo 32.13

If the CRC of the OTASP Data MessageUnit checks (see 2.2.1), the mobile14

station shall set the DMU_CRC_OK field of the OTASP Transport Confirmation15

Messageto 1 and shall process the OTASP Data Messageas specified in16

Section 3; otherwise, the mobile station shall set the DMU_CRC_OK field of17

the OTASP Transport Confirmation Messageto 0 and shall discard the18

OTASP Data MessageCapsule.19

- If RX_SEQ_NUMsis equal to the value of the SEQ_NUM field of the received20

message, the mobile station shall discard the OTASP_DATA field of the21

received message. If the CRC of the OTASP Data MessageUnit checks (see22

2.2.1), the mobile station shall set the DMU_CRC_OK field of the OTASP23

Transport Confirmation Messageto 1; otherwise, the mobile station shall set24

the DMU_CRC_OK field to 0.25

- If neither RX_SEQ_NUMsnor (RX_SEQ_NUMs+ 1) modulo 32 is equal to the26

value of the SEQ_NUM field of the received message, the mobile station shall27

discard the OTASP_DATA field of the received message and shall discard the28

incomplete OTASP Data MessageCapsule being reassembled. The mobile29

station shall set the DMU_CRC_OK field of the OTASP Transport Confirmation30

Messageto 0.31

If the value of the B/F field of the received message is 01, and if no segmented32


discard the OTASP_DATA field of the received message. The mobile station shall34

set the DMU_CRC_OK field of the OTASP Transport Confirmation Messageto 0.35

The mobile station shall remain in the Conversation Task.36


If the SEQ_ACK field is equal to TX_SEQ_NUMs, the mobile station shall disable the38

OTASP acknowledgment timer; otherwise, the mobile station shall ignore the39

message. The mobile station shall remain in the Conversation Task.40

8/12/2019 TIA-EIA-683-C

36/246

TIA-683-C

2-8

2.2.3.4 Reverse Voice Channel Message Format1

2.2.3.4.1 OTASP Transport Message2

When the mobile station sends the OTASP Transport Message on the Reverse Voice Channel3

(RVC), it shall use the following format:4

Word 1 of the OTASP Transport Message:5

Information Element Length (bits)

F=1 1

NAWC 2

T=1 1

MSG_TYPE=00000 5

ORDQ=000 3

ORDER=11010 5

SEQ_NUM 5

B/F 2

ESN_4 8

RSVD=0000 4

P 12

6



F=0 1

NAWC 2

T=1 1

ESN_3 8

ESN_2 8

ESN_1 8

OTASP_DATA 8

P 12

8

Words 3 and 4 of the OTASP Transport Message:9

8/12/2019 TIA-EIA-683-C

37/246

TIA-683-C

2-9


F=0 1

NAWC 2

T=1 1

OTASP_DATA 32

P 12

1

F - First word field. The mobile station shall set this field to 1 in the2

first word of the message, and to 0 in all other words.3

NAWC - Number of additional words coming field. The mobile station shall4

set this field in each word of the message to the number of remaining5

words not including the current word.6

T - T field. The mobile station shall set this field to 1.7

MSG_TYPE - Message Type field. The mobile station shall set this field to 00000.8

ORDQ - Order qualifier field. The mobile station shall set this field to 000.9

ORDER - Order field. The mobile station shall set this field to 11010.10

SEQ_NUM - Message Sequence Number. The mobile station shall set this field to11

the message sequence number of this OTASP Transport Message.12

B/F - Begin/Final. This field is used to specify whether the OTASP Data13

Message Capsule has been segmented into multiple OTASP Transport14

Messages. If the OTASP Data Message Capsule is completely15

contained in a single OTASP Transport Message, the mobile station16

shall set this field to 11. For an OTASP Data Message Capsule17

contained in multiple OTASP TransportMessages,the mobile station18

shall set the value of this field in the first segment to 10, the value of19

this field in all intermediate segments to 00, and the value of this20

field in the final segment to 01.21

ESN_4 - The mobile station shall set this field to the most significant octet22

(bits d31-d24) of the mobile station ESN.23

ESN_3 - The mobile station shall set this field to the next to the most24

significant octet (bits d23-d16) of the mobile station ESN.25

ESN_2 - The mobile station shall set this field to the next to the least26

significant octet (bits d15-d8) of the mobile station ESN.27

ESN_1 - The mobile station shall set this field to the least significant octet28

(bits d7-d0) of the mobile station ESN.29

RSVD - Reserved for future use; the mobile station shall set all bits as30

indicated.31

8/12/2019 TIA-EIA-683-C

38/246

TIA-683-C

2-10

OTASP_DATA - The mobile station shall set these fields to the corresponding octets1

of the OTASP Data Message Capsule.2

P - Parity field. The mobile station shall set this field as specified in3

2.7.2 of [1].4

2.2.3.4.2 OTASP Transport Confirmation Message5

The mobile station Reverse Voice Channel (RVC) OTASP Transport Confirmation Message6

has the following format:7


F=1 1

NAWC=00 2

T=1 1

MSG_TYPE=00001 5

ORDQ=000 3ORDER=11010 5

SEQ_ACK 5

DMU_CRC_OK 1

RSVD=0000000000000 13

P 12

F - First word field. The mobile station shall set this field to 1.8

NAWC - Number of additional words coming field. The mobile station shall9

set this field to 00.10

T - T field. The mobile station shall set this field to 1.11

MSG_TYPE - Message Type field. The mobile station shall set this field to 00001.12

ORDQ - Order qualifier field. The mobile station shall set this field to 000.13

ORDER - Order field. The mobile station shall set this field to 11010.14

SEQ_ACK - Sequence Number for Acknowledgment by the OTASP Transport15

Confirmation Message. The mobile station shall set this field to the16

value of SEQ_NUM in the OTASP Transport Message being17

acknowledged.18

DMU_CRC_OK - OTASP Data MessageUnit CRC status flag. The mobile station shall19

set this field as specified in 2.2.3.2 to indicate whether or not the20

OTASP Data MessageUnit CRC checks.21

RSVD - Reserved for future use; the mobile station shall set all bits as22

indicated.23

P - Parity field. The mobile station shall set this field as specified in24

2.7.2 of [1].25

8/12/2019 TIA-EIA-683-C

39/246

TIA-683-C

2-11

2.2.4 Base Station Procedures1

OTASP Data Messages are sent and received on the analog voice channel only when the2

base station is in the Conversation Task (see 3.6.4.4 of [1]). The base station shall transmit3

OTASP Transport Messages as specified in 3.7.2 of [1]. Base stations implementing the4

Over-the-Air Service Provisioning feature should comply with the following requirements in5

addition to those of 3.6.4.4 of [1].6

2.2.4.1 Message Transmission7

While the base station is in the Conversation Task, the following messages can be sent in8

addition to those listed in 3.6.4.4 of [1]:9


The base station should construct the OTASP TransportMessage as follows:11

If the OTASP_DATA field of the OTASP TransportMessage contains an entire12

OTASP Data MessageCapsule, the base station should set the value of the13

SEQ_NUM field to 00000 and the value of the B/F field to 11.14

If the OTASP_DATA field of the OTASP TransportMessage contains the first15

segment of the segmented OTASP Data MessageCapsule, the base station16

should set the value of the SEQ_NUM field to 00000 and the value of the B/F17

field to 10.18

If the OTASP_DATA field of the OTASP TransportMessage contains a segment19

other than the first segment of the segmented OTASP Data MessageCapsule, the20

base station should perform the following:21

- If the OTASP_DATA field of the OTASP TransportMessage contains a22

segment other than the final segment of the OTASP Data MessageCapsule,23

the base station should increment SEQ_NUM modulo 32 and should set the24


- If the OTASP_DATA field of the OTASP TransportMessage contains the final26

segment of the OTASP Data Message, the base station should increment27

SEQ_NUM modulo 32 and should set the value of the B/F field to 01.28

The base station should remain in the Conversation Task.29


The base station should set the SEQ_ACK field to the value of the SEQ_NUM field31

received in the OTASP TransportMessage being acknowledged, and should remain32

in the Conversation Task.33

34

8/12/2019 TIA-EIA-683-C

40/246

TIA-683-C

2-12

2.2.4.2 Message Reception1

While the base station is in the Conversation Task, the following messages can be received2

autonomously from the mobile station, in addition to those listed in 3.6.4.4 of [1]. When3

any message is received, the base station should perform all actions specified in 3.6.4.4 of4

[1] that apply to a message reception. The base station shall take the actions specified5

below for each message:6


If the value of ESN received in the OTASP Transport Message does not match the8

ESN that identifies the mobile station being activated, the base station should9

ignore the message.10

If the value of ESN received in the OTASP Transport Messagematches the ESN that11

identifies the mobile station being activated, the base station should do the12

following:13

The base station should send an OTASP TransportConfirmation Message.14

If the value of the B/F field of the received message is 11, the OTASP_DATA15

field of the received message contains the OTASP Data MessageCapsule in its16

entirety. The base station may discard any incomplete OTASP Data Message17

being reassembled, and should process the OTASP Data Messageas specified in18

Section 4.19

If the value of the B/F field of the received message is 10, the base station may20

discard any incomplete OTASP Data Message being reassembled, and should21

store the OTASP_DATA field of the received message as the first segment of an22

OTASP Data Message Capsule to be reassembled. The base station should23

store the value of the SEQ_NUM field of the received message in RX_SEQ_NUM.24


OTASP Data MessageCapsule is being reassembled, the base station should26


- If (RX_SEQ_NUM + 1) modulo 32 is equal to the value of the SEQ_NUM field28

of the received message, the base station should store the OTASP_DATA field29

of the received message as the next segment of the OTASP Data Message30

being reassembled, and increment RX_SEQ_NUM modulo 32.31

- If RX_SEQ_NUM is equal to the value of the SEQ_NUM field of the received32

message, the base station may discard the OTASP_DATA field of the received33

message.34

- If neither RX_SEQ_NUM nor (RX_SEQ_NUM + 1) modulo 32 is equal to the35

value of the SEQ_NUM field of the received message, the base station may36

discard the OTASP_DATA field of the received message and may discard the37

incomplete OTASP Data Message being reassembled.38

8/12/2019 TIA-EIA-683-C

41/246

TIA-683-C

2-13

If the value of the B/F field of the received message is 00, and no segmented1

OTASP Data MessageCapsule is being reassembled, the base station may2

discard the OTASP_DATA field of the received message.3


OTASP Data MessageCapsule is being reassembled, the base station should5


- If (RX_SEQ_NUM + 1) modulo 32 is equal to the value of the SEQ_NUM field7

of the received message, the base station should store the OTASP_DATA field8

of the received message as the last segment of the OTASP Data Message9

Capsule being reassembled, should increment RX_SEQ_NUM modulo 32,10

and should process the OTASP Data Messageas specified in Section 4.11

- If RX_SEQ_NUM is equal to the value of the SEQ_NUM field of the received12

message, the base station may discard the OTASP_DATA field of the received13

message.14

- If neither RX_SEQ_NUM nor (RX_SEQ_NUM + 1) modulo 32 is equal to the15

value of the SEQ_NUM field of the received message, the base station may16

discard the OTASP_DATA field of the received message and may discard the17

incomplete OTASP Data MessageCapsule being reassembled.18

If the value of the B/F field of the received message is 01, and no segmented19

OTASP Data MessageCapsule is being reassembled, the base station may20

discard the OTASP_DATA field of the received message.21

The base station should remain in the Conversation Task.22


If SEQ_ACK is equal to the sequence number of the last OTASP TransportMessage24

sent, the base station may transmit the next OTASP Transport Message; otherwise,25

the base station should ignore the message. If the DMU_CRC_OK field indicates26

that the CRC of the OTASP Data MessageUnit did not check at the mobile station27

(see 2.2.3.3), the base station should resend the OTASP Data Message. The base28

station should remain in the Conversation Task.29

2.2.4.3 Forward Voice Channel Message Format30

2.2.4.3.1 OTASP Transport Message31

When the base station sends an OTASP Transport Messageon the Forward Voice Channel32

(FVC), it shall use the following variable-length message format:33

8/12/2019 TIA-EIA-683-C

42/246

TIA-683-C

2-14



T1T2= 10 2

SCC=11 2

PSCC 2

EF=0 1

SEQ_NUM 5

DATA_WORDS 3

MSG_TYPE=00000 5

ORDQ=000 3

ORDER=11010 5

P 12

2



T1T2= 01 2

B/F 2

ESN_4 8

ESN_3 8

ESN_2 8

P 12

4



T1T2= 01 2

RSVD=00 2

ESN_1 8

OTASP_DATA 16

P 12

6

Word 4 through N of the OTASP Transport Message:7

8/12/2019 TIA-EIA-683-C

43/246

TIA-683-C

2-15


T1T2= 01 2

RSVD=00 2

OTASP_DATA 24

P 12

1

T1T2 - Type field. The base station shall set this field to 10 in the first word2

of the message, and to 01 in all other words.3

SCC - SAT color code for new channel. The base station shall set this field4

to 11.5

PSCC - Present SAT color code. The base station shall set this field to6

indicate the SAT color code associated with the present channel as7

specified in the Table 3.7.1.1-2 of [1].8

EF - Extended