CDMA2000_1XEV-DO_Rel.0(2)

CDMA20001xEV-DO Release 0cdma university

CDMA2000 1xEV-DORelease 0

CDMA2000 1xEV-DORelease 0

Student GuideBook 2

80-31392-2 Rev B

For China Telecom Intensive Training Use only,Nov.-Dec.2008

Material Use RestrictionsThese written materials are to be used only in conjunction with the associated instructor-led class. They are not intended to be used solely as reference material.

No part of these written materials may be used or reproduced in any manner whatsoever without the written permission of QUALCOMM Incorporated.

Copyright 2003 QUALCOMM Incorporated. All rights reserved.

QUALCOMM Incorporated5775 Morehouse DriveSan Diego, CA 92121U.S.A.

Revision History: 80-31392-2 Rev A replaces the previous version, 80-31392-2 X2. The version numbering system was changed for internal tracking purposes only.

Export of this technology may be controlled by the United States Government. Diversion contrary to U.S. law prohibited.

QUALCOMM is a registered trademark and registered service mark of QUALCOMM Incorporated.

cdma2000 is a registered certification mark of the Telecommunications Industry Association. Used under license. All other trademarks and registered trademarks are the property of their respective owners.


CDMA2000 1xEV-DO Release 0 80-31392-2 Rev B

2003 QUALCOMM Incorporated

Table of Contents Book 2

CDMA20001xEV-DO Release 0cdma university

CDMA.HELP

[email protected]

z Email hotline resource to assist our CDMA customers worldwide.

z Experienced CDMA engineers in our Engineering Services Group will answer your technical questions on topics including:

Industry StandardsInfrastructure DesignVoice QualitySystem Design

Network PlanningNetwork OptimizationTest EngineeringTraining

iiiFor China Telecom Intensive Training Use only,Nov.-Dec.2008




This page left blank intentionally.

ivFor China Telecom Intensive Training Use only,Nov.-Dec.2008




v


Acronyms and Abbreviations..............................................................ix CDMA2000 1xEV-DO Book 2 Overview .................................. 8-1

Section 8: Session Layer................................................................. 8-2 Section Introduction ......................................................................... 8-3 Section Learning Objectives ............................................................ 8-4 Session Layer ................................................................................... 8-5 Overview................................................................................ 8-6 Protocols ................................................................................ 8-8 Encapsulation......................................................................... 8-9 Session Management Protocol ....................................................... 8-10 State Diagram (AT).............................................................. 8-12 State Diagram (AN) ............................................................. 8-13 Keep Alive Function ............................................................ 8-14 Messages .............................................................................. 8-15 Address Management Protocol ...................................................... 8-16 State Diagram (AT).............................................................. 8-18 State Diagram (AN) ............................................................. 8-19 Messages .............................................................................. 8-20 Address Assignment ............................................................ 8-22 Subnet .................................................................................. 8-23 Color Codes ......................................................................... 8-24 Color Code and Subnet Mapping......................................... 8-26 Long Code Masks ................................................................ 8-27 Mobility Management and Registration .............................. 8-28 Session Configuration Protocol...................................................... 8-29 State Diagram (AT).............................................................. 8-31 State Diagram (AN) ............................................................. 8-32 Restoring a Prior Session ..................................................... 8-33 Simple Session Negotiation Example.................................. 8-34 Extensive Session Negotiation Example ............................. 8-35 SMP, AMP, and SCP ..................................................................... 8-36 What We Learned in This Section ................................................. 8-37 Session Layer Review ................................................................. 8-38

Section 9: Stream Layer................................................................. 9-1 Section Introduction ......................................................................... 9-2 Section Learning Objectives ............................................................ 9-3 Stream Layer .................................................................................... 9-4 Overview................................................................................ 9-5 Functions................................................................................ 9-6 Stream Configuration Procedure............................................ 9-7 Encapsulation......................................................................... 9-8 Packet ..................................................................................... 9-9





vi

What We Learned in This Section ................................................. 9-10 Stream Layer Review .................................................................. 9-11

Section 10: Application Layer ..................................................... 10-1 Section Introduction ....................................................................... 10-2 Section Learning Objectives .......................................................... 10-3 Application Layer........................................................................... 10-4 Default Signaling Application........................................................ 10-5 Signaling Link Protocol (SLP)............................................. 10-7 Message Encapsulation (Non-fragmented).............. 10-8 Message Encapsulation (Fragmented) ..................... 10-9 SLP-D Header........................................................ 10-10 SLP-F Header......................................................... 10-11 SLP-D Transmit Sequence Number Variables ...... 10-12 SLP-D Receive Sequence Number Variables........ 10-13 Fragmentation Layer.............................................. 10-14 Signaling Network Protocol (SNP).................................... 10-15 Signaling Message Requirements .......................... 10-16 Message Information ............................................. 10-17 Packet Structure ..................................................... 10-18 Default Protocol Stack ........................................... 10-19 Default Packet Application .......................................................... 10-22 Radio Link Protocol ........................................................... 10-24 NAK Messages ...................................................... 10-25 Default Packet Application Encapsulation ............ 10-26 Transmit Sequence................................................. 10-27 Receive Sequence .................................................. 10-28 Location Update Protocol .................................................. 10-29 AT Requirements ................................................... 10-30 IS-2000-Compatible Location Subfields ............... 10-31 LocationNotification Message ............................... 10-32 Flow Control Protocol........................................................ 10-33 Messages and States............................................... 10-34 What We Learned in This Section ............................................... 10-36 Application Layer Review......................................................... 10-37

Section 11: Quality of Service Support....................................... 11-1 Section Introduction ....................................................................... 11-2 Section Learning Objectives .......................................................... 11-3 QoS Functions ................................................................................ 11-4 Admission Control ............................................................... 11-5 Packet Classification............................................................ 11-8 Policing, Marking, and Dropping Packets ........................... 11-9 Marking and Dropping Packets ......................................... 11-10 Flow Control ...................................................................... 11-11 Dropping Non-delay Sensitive Packets Using RED.......... 11-12





vii

Scheduling.......................................................................... 11-14 What We Learned in This Section ............................................... 11-15 Quality of Service Support Review........................................... 11-16

Section 12: Simple and Mobile IP ............................................... 12-1 Section Introduction ....................................................................... 12-2 Section Learning Objectives .......................................................... 12-3 Standards Status ............................................................................. 12-4 1xEV-DO Network Diagram and Protocol Stacks......................... 12-5 New Network Entities and Interface.................................... 12-6 Simple IP ........................................................................................ 12-7 Basics ................................................................................... 12-8 Initiation (PPP)..................................................................... 12-9 Origination and Resource Allocation................................. 12-10 PPP LCP............................................................................. 12-11 PPP CHAP ......................................................................... 12-13 PPP IPCP ........................................................................... 12-14 TCP/IP Header Compression............................................. 12-15 Termination........................................................................ 12-16 Mobile IP...................................................................................... 12-17 Basics Routing................................................................... 12-18 Registration ............................................................ 12-19 Adaptation to 3GPP2 ......................................................... 12-20 Initiation............................................................................. 12-21 PPP LCP................................................................. 12-22 PPP IPCP ............................................................... 12-23 Registration and Authentication Overview................................................................ 12-24 Message Flow ........................................................ 12-25 Phase 1 ................................................................... 12-26 Phase 2 ................................................................... 12-27 Multiple Addresses ............................................................ 12-28 Home Network Access ..................................................... 12-29 PDSN-HA Security............................................................ 12-30 Reverse Tunneling ............................................................. 12-32 Private Address Support .................................................... 12-34 Simple IP versus Mobile IP.......................................................... 12-35 QoS Differentiated Services ...................................................... 12-37 Simple and Mobile IP References ................................................ 12-39 What We Learned in This Section ............................................... 12-40 Simple and Mobile IP Review................................................... 12-41

Section 13: CDMA2000 1X and 1xEV-DO Hybrid Operation. 13-1 Section Introduction ....................................................................... 13-2 Section Learning Objectives .......................................................... 13-3





viii

1X and 1xEV-DO Access Network................................................ 13-4 1X and 1xEV-DO Access Terminal ............................................... 13-5 Acquisition and Synchronization State Operation............... 13-6 Idle State Operation ............................................................. 13-7 Traffic State Operation ...................................................... 13-10 Hybrid AT Responds to Voice Page ............................................ 13-11 Data Session Handoff Idle State 1X to 1xEV-DO................................................. 13-12 Idle State 1xEV-DO to 1X................................................. 13-13 Traffic State 1xEV-DO to 1X............................................ 13-14 What We Learned in This Section ............................................... 13-15 CDMA2000 1X and 1xEV-DO Hybrid Operation Review ...... 13-16

Section 14: Course Summary ...................................................... 14-1 Course Summary ............................................................................ 14-2 What We Learned Section 1 Introduction......................................................... 14-4 Section 2 Key Concepts of 1xEV-DO ................................ 14-5 Section 3 Protocol Overview ............................................... 14-6 Section 4 Physical Layer..................................................... 14-7 Section 5 MAC Layer .......................................................... 14-8 Section 6 Security Layer................................................... 14-10 Section 7 Connection Layer.............................................. 14-11 Section 8 Session Layer .................................................... 14-12 Section 9 Stream Layer..................................................... 14-13 Section 10 Application Layer ........................................... 14-14 Section 11 Quality of Service Support.............................. 14-15 Section 12 Simple and Mobile IP ..................................... 14-16 Section 13 1X and 1xEV-DO Hybrid Operation .............. 14-17

Appendix A: Coverage Analysis .................................................. A-1 Coverage Analysis........................................................................... A-2 1xEV-DO Forward Link Coverage ................................................. A-4 IS-95A Forward Link Coverage Comparison ................................. A-5 1xEV-DO Reverse Link Coverage.................................................. A-6 IS-95A Reverse Link Coverage Comparison.................................. A-7

Appendix B: Field Trial Results....................................................B-1 Field Trial Overview ........................................................................B-2 San Diego Location ..........................................................................B-3 Test Configurations ..........................................................................B-4 Stationary Locations.........................................................................B-5 Mobile Drive Route..........................................................................B-6 SINR Distribution.............................................................................B-7 Field Trial Throughput Numbers .....................................................B-8





ix

Acronyms and Abbreviations

3GPP Third Generation Partnership Project 3GPP2 Third Generation Partnership Project 2 AAA Authentication, Authorization, and Accounting AC Access Channel ACK Acknowledgment ACPAC Access Channel MAC Layer Packet Authentication Code AES Advanced Encryption Standard AF Assured Forwarding AIA Air Interface Authentication AMP Address Management Protocol AN Access Network AP Access Point ARQ Automatic Retransmission Request ASIC Application Specific Integrated Circuit AT Access Terminal ATI Access Terminal Identifier AMP Access Management Protocol AWGN Additive White Gaussian Noise bps Bits Per Second BPSK Binary Phase Shift Keying BS Base Station BSC Base Station Controller BTS Base Station Transceiver System C/I Carrier-to-Interference CC Control Channel CCH Control Channel Header CDG CDMA Development Group CDM Code Division Multiplex CDMA Code Division Multiple Access CHAP Challenge Handshake Authentication Protocol CN Core Network COA Care-of Address CRC Cyclic Redundancy Check CSM Cell Site Modem dB Decibel DH Diffie-Hellman DHCP Dynamic Host Configuration Protocol diff-serv Differentiated Service DNS Domain Name System DO Data Optimized DRC Data Rate Control DRS Data Ready to Send DV Data Voice





x

EF Expedited Forwarding EIA Electronics Industry Association ETACS European Total Access Communications System EV Evolution FA Frequency Assignment FCP Flow Control Protocol FCS Frame Check Sequence FIPS Federal Information Processing Standards FIR Finite Impulse Response FL Forward Link FLM Forward Link Modem FTC Forward Traffic Channel GHz Gigahertz GPS Global Positioning System GRE Generic Routing Encapsulation GSM Global System Mobile HA Home Agent HAT Hybrid Access Terminal HDR High Data Rate HPSK Hybrid Quadrature Phase Shift Keying HRPD High Rate Packet Data HTTP HyperText Transfer Protocol HWG HDR Working Group Hz Hertz I In-Phase component ID Identification IETF Internet Engineering Task Force IKE Internet Key Extension IMSI International Mobile Subscriber Identity IMT International Mobile Telecommunication IP Internet Protocol IPCP IP Control Protocol IS Interim Standard ISP Internet Service Provider ITU International Telecommunications Union IV Initialization Vector JTACS Japanese Total Access Communications System kbps Kilobits Per Second kcps Kilochips Per Second KHz Kilohertz ksps Kilosymbols Per Second LCM Long Code Mask LCP Link Control Protocol LSB Least Significant Bit MAC Medium Access Control Mbps Megabits Per Second





xi

Mcps Megachips Per Second MHz Megahertz MPC Modem Pool Controller MPT Modem Pool Transceiver ms Milliseconds MSC Mobile Switching Center MT Mobile Terminated NAI Network Access Identifier NAK Negative Acknowledgment NAS Network Access Server NID Network Identification NMT Nordic Mobile Telephone Node B A logical node responsible for radio transmission/reception

in one or more cells to/from the User Equipment ns Nanosecond OCQPSK Orthogonal Complex Quadrature Phase Shift Keying OHM Overhead Manager OSI Open System Interconnection PA Power Amplifier PCCC Preferred Control Channel Cycle PCF Packet Control Function PCS Personal Communication System PDA Personal Digital Assistant PDSN Packet Data Serving Node PER Packet Error Rate PN Pseudo-noise PPP Point-to-Point Protocol PRL Preferred Roaming List PSK Phase-Shift Keying PSTN Public Switched Telephone Network PTM Push-To-Media PTT Push-To-Talk Q Quadrature-phase component QAM Quadrature Amplitude Modulation QoS Quality of Service QPSK Quadrature Phase-Shift Keying RA Reverse Activity RAB Reverse Activity Bit RAN Radio Access Network RADIUS Remote Authentication Dial-In User Server RF Radio Frequency RL Reverse Link RLM Reverse Link Modem RLP Radio Link Protocol ROT Rise Over Thermal RPC Reverse Power Control





xii

RRI Reverse Rate Indicator RSVP Resource Reservation Protocol RTC Reverse Traffic Channel RUM RouteUpdate Message Rx Receive SC Synchronous Control SCI Slot Cycle Index SCP Session Configuration Protocol SDP Session Description Protocol sec Second SF Selector Function SHA Secure Hash Algorithm SID System Identification SINR Signal-to-Interference plus Noise Ratio SIP Session Initiated Protocol SLP Signaling Link Protocol SLP-D SLP Delivery SLP-F SLP Fragmentation SMP Session Management Protocol SMR Specialized Mobile Radio SNMP Simple Network Management Protocol SNP Signaling Network Protocol SNR Signal-to-Noise Ratio SO Service Option TACS Total Access Communications System TCP Transmission Control Protocol TE Terminal Equipment TIA Telecommunications Industry Association TDM Time Division Multiplex TMSI Temporary Mobile Subscriber Identity Tx Transmit UATI Unicast Access Terminal Identifier UDP User Datagram Protocol UE User Equipment UTC Universal Coordinated Time VJHC Van Jacobsen Header Compression VoIP Voice over Internet Protocol s Microsecond


CDMA2000 1xEV-DO Release 0Section 8: Session Layer

2003 QUALCOMM Incorporated 8-1

80-31392-2 Rev B

Section 8-1cdma university

CDMA2000 1xEV-DO Release 0

Section 8: Session Layer

Session Layer8SECTION

Notes




80-31392-2 Rev B



SECTION INTRODUCTION

106AC_00.emf

Section Introduction

Session Layer Overview Protocols Encapsulation

Session Management Protocol (SMP)

Address Management Protocol (AMP)

Session Configuration Protocol (SCP)

Notes




80-31392-2 Rev B



Describe the functions of the Session Layer.

Define sessions.

Describe what the Session Management Protocol (SMP) does. Define the keep alive mechanism.

Describe what the Address Management Protocol (AMP) does. Explain how UATIs are assigned.

Discuss subnets and color codes and how they are used.

Describe what the Session Configuration Protocol (SCP) does. Describe how session negotiation takes place.

Section Learning Objectives

Notes




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Session Layer

Air LinkManagement

Protocol

OverheadMessagesProtocol

PacketConsolidation

Protocol

Initialization StateProtocol

Idle StateProtocol

Connected StateProtocol

Route UpdateProtocol

SessionManagement

Protocol

SessionConfiguration

Protocol

StreamProtocol

Radio LinkProtocol

Control ChannelMAC Protocol

Access ChannelMAC Protocol

Reverse TrafficChannel MAC

Protocol

Forward TrafficChannel MAC

Protocol

SecurityProtocol

AuthenticationProtocol

EncryptionProtocol

Default PacketApplication

DefaultSignalingApplication

AddressManagement

Protocol

Key ExchangeProtocol

Physical LayerProtocol

ConnectionLayer

SessionLayer

StreamLayer

ApplicationLayer

MACLayer

SecurityLayer

PhysicalLayer

SignalingLink Protocol

SignalingNetwork Protocol

Location UpdateProtocol

FlowControl Protocol

Notes




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Session Layer Overview

The Session Layer contains protocols to negotiate a session between the Access Terminal (AT) and the Access Network (AN).

A session is a shared state maintained between the AT and the AN.

Opening an IS-856 session is analogous to calling your favorite bank for the first time and opening an account.

You exchange information with the bank, they give you a checkbook, etc. Even after hanging up the phone, you still have an account with the bank. After opening the account, you may call your bank many times for various

transactions, but you dont have to exchange all the information that you exchanged with the bank on the first day.

Session Layer Overview

Except to open a session, an Access Terminal (AT) cannot communicate with an Access Network (AN) without having an open session.




80-31392-2 Rev B



The shared state in the session maintains information such as:

A unicast address (UATI) assigned to the AT Protocols and protocol configuration that were negotiated An estimate of the current AT location

Sessions do not end when the connection ends. They do end when:

The AT is unavailable for a period longer than the session timer. The AT is moved to a different network.

The AN is sent a Close message.

They do not end frequently.

Session Layer Overview (continued)

Session Layer Overview (continued)Do not confuse sessions with connections. During a single session, the AT and AN can open and close one connection multiple times. On the other hand, sessions do not end frequently (the default timer is 54 hours).




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Session Layer Protocols

Session Layer Protocols

Session Management Protocol (SMP) This high-level protocol provides the means to control the activation of the other Session Layer protocols. It also contains a session keep alive mechanism and ensures that the session is still valid, and manages closing of the session.

Address Management Protocol (AMP) This protocol specifies procedures for the initial UATI assignment and maintenance of the AT addresses.

Session Configuration Protocol (SCP) This protocol provides the means to negotiate and provision the protocols used during the session. It also negotiates the AT-specific configuration parameters for these protocols. This protocol uses the Generic Configuration Protocol for protocol negotiation.




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Session Layer Encapsulation

StreamLayerPacket

SessionLayer

Payload

ConnectionLayer

Payload

SessionLayerPacket

Session Layer Encapsulation

The figure shows the relationship between Stream Layer packets, Session Layer packets, and Connection Layer payload. The Session Layer does not modify packets it transmits or receives.




80-31392-2 Rev B



Introduction

Protocol State Diagrams for the AT and AN

Keep Alive Function

Messages

Session Management Protocol

Notes




80-31392-2 Rev B



Controls the activation of the Address Management and Session Configuration Protocols in order before a session is established.

Provides a session keep alive mechanism.

Manages closing of the session.

Session Management Protocol (continued)

Session Management Protocol

The Session Management Protocol (SMP) provides a means to control the activation of the Address Management (AMP) and Session Configuration (SCP) protocols. The actual behavior and message exchanges in each state of this protocol are mainly governed by the AMP and SCP.

This protocol also periodically ensures that the session is still valid (keep alive) and manages the closing of the session.




80-31392-2 Rev B



Session Management Protocol State Diagram (AT)

State Diagram (AT)The figure shows the Session Management Protocol state diagram for the AT. The SMP can be in one of three states:

z Inactive state This state applies only to the AT. In this state, the protocol waits for an Activate command, and there is no communication between the AT and the AN. The AT does not maintain any session related state. In addition, the AN may be unaware of the existence of the AT within its coverage area.

z AMP Setup state The AT and AN perform exchanges governed by the AMP, and the AN assigns a UATI to the AT.

z Open state A session is open, and the AT has an assigned UATI.




80-31392-2 Rev B



Session Management Protocol State Diagram (AN)

State Diagram (AN)The figure shows the Session Management Protocol state diagram for the AN. The SMP can be in one of three states:

z AMP Setup state The AT and AN perform exchanges governed by the AMP, and the AN assigns a UATI to the AT.

z Open state A session is open, and the AN has assigned a UATI to the AT.z Close state This state applies only to the AN. The AN waits for a SessionClose message

from the AT or an expiration of the Close state timer which is set to TSMPClose or TSMPMinClose, whichever is larger. In this state, if the AN receives any packet from the AT that contains anything but a SessionClose message, it stays in this state, discards the packet, and responds with a SessionClose message.




80-31392-2 Rev B



Session Management Protocol Keep Alive Function

The keep alive function is a session maintenance mechanism.

Occurs only if there is no directed traffic to/from the AT/AN.

The AT and AN exchange KeepAliveRequest and KeepAliveResponse messages.

Keep alive timer should be much longer than the dormancy timer.

Keep alive mechanism can be disabled by setting TSMPCloseto 0.

Session is closed if there is no traffic between the AT and AN for TSMPClose minutes (default is 54 hours).

Keep Alive Function

The AT and AN monitor the traffic flowing on the Forward Channel and Reverse Channel, respectively, directed to or from the AT. If either the AT or the AN detects a period of inactivity of at least TSMPClose/NSMPKeepAlive minutes, it may send a KeepAliveRequest message. The recipient of the message shall respond by sending the KeepAliveResponse message. When a KeepAliveResponse message is received, the AT shall not send another KeepAliveRequest message for at least TSMPClose/NSMPKeepAlive minutes. After sending NSMPKeepAlive unacknowledged KeepAliveRequest messages, the session times out.

The default value for TSMPClose is 54 hours, and for NSM PKeepAlive the default value is 3 .




80-31392-2 Rev B



Session Management Protocol Messages

SessionClose Used by an AT or AN to terminate the current session. A CloseReason field is set to indicate the reason.

KeepAliveRequest Used by an AT or AN to verify that the peer is still alive.

KeepAliveResponse Used by an AT or AN to respond to a KeepAliveRequest message.

Notes




80-31392-2 Rev B



Introduction Protocol State Diagrams

for the AT and AN Messages Address Assignment Subnets Color Codes Long Code Masks Mobility Management and

Registration

Address Management Protocol

Notes




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Address Management Protocol (continued)

Assigns to each AT a 128-bit UATI that is universally unique.

The 128-bit address is never required to be sent on the Access Channel, and the AN can always send the short (32 bits) version of the UATI.

Defines the concept of subnets for UATI used in subnet-based location update.

The subnet concept replaces the need for packet zone ID, registration zones, TMSI zones, etc.

For example, if a subnet is the footprint of a PCF, the AT sendsa route update message when it crosses PCF boundaries.

Preserves Long Code Mask (LCM) assignments based on UATI.

Notes




80-31392-2 Rev B



Address Management Protocol State Diagram (AT)

State Diagram (AT)The figure shows the Address Management Protocol state diagram for the AT. The AMP operates in one of three states:

z Inactive state No communications between the AT and the AN. The AT does not have an assigned UATI, and the AN does not maintain a UATI for the AT. In addition, the AN may not be aware of the existence of the AT within its coverage area.

z Setup state The AT and the AN perform a UATIRequest/UATIAssignment/UATIComplete exchange to assign the AT a UATI.

z Open state The AT has been assigned a UATI. The AT and the AN may also perform a UATIRequest/UATIAssignment/UATIComplete or a UATIAssignment/ UATICompleteexchange to change the ATs UATI.




80-31392-2 Rev B



Address Management Protocol State Diagram (AN)

State Diagram (AN)The figure shows the Address Management Protocol state diagram for the AN. The AMP operates in one of three states:

z Inactive state No communications between the AT and the AN. The AT does not have an assigned UATI, and the AN does not maintain a UATI for the AT. In addition, the AN may not be aware of the existence of the AT within its coverage area.

z Setup state The AT and the AN perform a UATIRequest/UATIAssignment/UATIComplete exchange to assign the AT a UATI.

z Open state The AT has been assigned a UATI. The AT and AN may also perform a UATIRequest/UATIAssignment/UATIComplete or a UATIAssignment/ UATICompleteexchange to change the ATs UATI.




80-31392-2 Rev B



Address Management Protocol Messages

UpdateUATI Used only in the Open state to change the current UATI assigned to an AT. If the AT receives this command, it sends a UATIRequest message to request a new UATI. If the AN receives this message, it may send a UATIAssignment message.

UATIRequest Used by an AT to request a UATI be assigned or reassigned to it by the AN.

UATIAssignment Used by an AN to assign or reassign a UATI to the AT.

Notes




80-31392-2 Rev B



Address Management Protocol Messages (continued)

UATIComplete Used by the AT to notify the AN that it received the UATIAssignment message.

HardwareIDRequest Used by the AN to query the AT for its Hardware ID information.

HardwareIDResponse Used by the AT to respond to a HardwareIDRequest message, and provide the Hardware ID.

Notes




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Address Assignment

Address Assignment

The AT uses a 32-bit pseudorandom generator to derive a SessionSeed. This SessionSeed is used as the RATI in the UATIRequest message. The RATI is discarded when the AT receives a fresh UATIAssignment message. The AN may include both UATI104 and UATISubnetMaskfields in the UATIAssignment message. If these are not included, the UATI[127:24] is implicitly assigned to be equal to SectorID[127:24], and UATISubnetMask is implicitly assigned to be the SubnetMask of the sector that received the UATIRequest message.




80-31392-2 Rev B



The subnet for an address is obtained by performing a logical AND of the address and the subnet mask.

Each sector advertises its SectorID which is also a 128-bit address. This is how the AT knows it has entered the footprint of a new subnet.

Subnet

Notes




80-31392-2 Rev B



Because the 128-bit UATI does not fit in the LCM, and because sending a 128-bit UATI takes too much space in the Access Channel and Control Channel messages, an 8-bit Color Code (CC) is used as an alias for the subnet address.

The Color Code "compresses" the subnet part of the SectorID into an 8-bit field.When the subnet of the sector changes, the Color Code changes. The network operator has to adopt a reuse scheme for Color Code to ensure neighboring sectors in different subnets do not advertise the same Color Code.

Color Codes

Notes




80-31392-2 Rev B



The Color Code is the same within the same subnet and changes when the subnet changes.

The same Color Code can be reused at a sufficiently large distance (with an 8-bit code, this distance is allowed to be quite large).

The UATIColorCode is set to the Color Code of the sector on which the AT received the UATIAssignment message.

Color Codes (continued)

Notes




80-31392-2 Rev B



When the AN receives a UATIRequest by a new AT, the AN can optionally request the AT to send it the OldUATI[23+n:24].

This is useful when the AN does not maintain a table that translates Color Code to the corresponding subnet address.

Color Code and Subnet Mapping

Notes




80-31392-2 Rev B



MQ[k] =

MI[k-1], for k = 1,, 41 MQ[0] =

MI[0] MI[1] MI[2] MI[4] MI[5] MI[6] MI[9] MI[15] MI[16] MI[17] MI[18] MI[20] MI[21] MI[24] MI[25] MI[26] MI[30] MI[32] MI[34] MI[41]

Long Code Masks

Long Code Masks

The UATI, Color Code, and SectorID are also used by the MAC Layer to derive the long code masks for the Reverse Traffic Channel and the Access Channel.




80-31392-2 Rev B



PDSN PDSN

BSC/PCF

Subnet

Sector

BSC/PCF

BSC/PCF

BSC/PCF

1 2 3

Event #1:- Idle handoff occurs.- No subnet change.

Event #2:- Idle handoff occurs.- Subnet change occurs.- AT sends its old UATI to the AN.- New AN retrieves the AT session information from the old AN (using information provided in the old UATI).- New AN establishes a new R-P link to the PDSN.- PDSN tears down the old R-P connection.- New AN assigns a new UATI to the AT.

Event #3:- Same as Event #2.

Mobile IP finds the current PDSN (Foreign Agent). HDR Mobility Management allows the current PDSN to route

the packet to the current BSC/PCF.

Mobility Management and Registration

Notes




80-31392-2 Rev B



Introduction

Protocol State Diagrams for the AT and AN

Restoring a Prior Session

Simple and Extensive Session Negotiation Examples

Session Configuration Protocol

Notes




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Session Configuration Protocol (continued)

Negotiates parameters associated with a session.

For each configurable attribute, a default value is defined. If the default values are satisfactory for both sides, no negotiation is

necessary.

Either the AN or the AT can initiate session configuration. The AT sends a ConfigurationRequest, and the AN sends a

ConfigurationStart.

The negotiated attributes and protocols take effect only after the connection is dropped.

This establishes an unambiguous demarcation point for the newly negotiated attributes and protocol to take effect.

Session Configuration Protocol

The default SCP provides for the negotiation and configuration of the set of protocols used during the session.

Two negotiation phases are supported:z AT-initiated negotiation The AT initiates exchanges. This phase is used to negotiate

the protocols that will be used in the session and to negotiate some parameters.z AN-initiated negotiation The AN initiates exchanges. This phase is typically used to

override default values used by the negotiated protocols.This protocol uses the Generic Configuration Protocol procedures and messages when performing the negotiation in each phase. The SCP can also be negotiated; however, the default SCP must be used to do so.




80-31392-2 Rev B



Session Configuration Protocol State Diagram (AT)

State Diagram (AT)This figure shows the Session Configuration Protocol state diagram for the AT. The SCP can be in one of four states:

z Inactive state The protocol waits for an Activate command.z AT-Initiated state Negotiation is performed at the initiative of the AT.z AN-Initiated state Negotiation is performed at the initiative of the AN.z Open state The AT may initiate the session configuration procedure at any time, and the

AN may request the AT to initiate the session configuration at any time.




80-31392-2 Rev B



Session Configuration Protocol State Diagram (AN)

State Diagram (AN)This figure shows the Session Configuration Protocol state diagram for the AN. The SCP can be in one of four states:

z Inactive state The protocol waits for an Activate command.z AT-Initiated state Negotiation is performed at the initiative of the AT.z AN-Initiated state Negotiation is performed at the initiative of the AN.z Open state The AT may initiate the session configuration procedure at any time, and the

AN may request the AT to initiate the session configuration at any time.




80-31392-2 Rev B



Restoring a prior session: The AT has the option of requesting the AN to restore a prior session. This avoids session renegotiation and DH key exchange when there are

coverage holes and the AT travels across them.

AT

Coverage areaof HDR RAN 1

Coverage areaof HDR RAN 2

Est

ablis

hes

ase

ssio

n

1

Crosses a "no coverage zone" and moves to RAN 2

23

Get

s a

new

UA

TI

Req

uest

ress

urac

tion

of th

e ol

d se

ssio

n

4

Retrieve the old session

5

Session Configuration Protocol Restoring a Prior Session

Notes




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Simple Session Negotiation Example

Simple Session Negotiation Example

This figure shows Key Exchange negotiation using only default parameters. Using default parameters greatly reduces session setup time.




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Extensive Session Negotiation Example

Notes




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0SMP, AMP, and SCP

Notes




80-31392-2 Rev B



9 The functions of the Session Layer.9 What sessions are.9 The functions of the Session Control Management Protocol

(SMP).9 What the keep alive mechanism is.9 The functions of the Address Management Protocol (AMP).9 How UATIs are assigned.9 What subnets and color codes are and how they are used.9 The functions of the Session Configuration Protocol (SCP).9 How session negotiation takes place.

What We Learned in This Section

Notes




80-31392-2 Rev B



SECTION REVIEW

105AC_00

Session Layer Overview Protocols Encapsulation

Session Management Protocol (SMP)

Address Management Protocol (AMP)

Session Configuration Protocol (SCP)

Session Layer Review

Notes




80-31392-2 Rev B

Comments/Notes


CDMA2000 1xEV-DO Release 0Section 9: Stream Layer


80-31392-2 Rev B



Section 9: Stream Layer

Stream Layer9SECTION

Notes




80-31392-2 Rev B




106AC_00.emf

Overview Functions Stream Configuration

Procedure Encapsulation Packet

Section Introduction

Notes




80-31392-2 Rev B



Describe the functions of the Stream Layer.

Describe how the Stream Layer encapsulates packets.

Describe the procedures for Stream Layer configuration.

Section Learning Objectives

Notes




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Stream Layer

Air LinkManagement

Protocol


PacketConsolidation

Protocol


Idle StateProtocol



SessionManagement

Protocol


Protocol

StreamProtocol

Radio LinkProtocol




Protocol


Protocol

SecurityProtocol


EncryptionProtocol



AddressManagement

Protocol



ConnectionLayer

SessionLayer

StreamLayer

ApplicationLayer

MACLayer

SecurityLayer

PhysicalLayer





Notes




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Stream Layer Overview

Provides a mechanism to tag Application Layer packets

Notes




80-31392-2 Rev B



Provides a mechanism to tag Application Layer packets by adding a Stream identifier.

The Connection Layers Packet Consolidation Protocol uses tags to prioritize signaling and user traffic.

Both the user and the signaling traffic are tagged.

Applications with different QoS can be assigned separate streams.

Stream Layer Functions

Stream Layer Functions

The Stream Layer provides the following functions:z Multiplexes application streams for one Access Terminal (AT). Stream 0 is always

assigned to the Signaling Application and by default to the Default Signaling Protocol. The other streams can be assigned to applications with different Quality of Service (QoS) requirements, or other applications.

z Provides configuration messages that map applications to streams.The Stream Layer Protocol is used to provide these functions.




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Stream Configuration Procedure

The AT and AN may use the ConfigurationRequestand ConfigurationResponse messages to select the applications carried by each stream.

The ConfigurationRequest and ConfigurationResponse messages may be exchanged only when the session is set up.

The AT and AN shall process the messages as specified in the Generic Configuration Protocol.

Stream Configuration Procedure

Applications can be mapped to the different streams during the AT-initiated state of the Session Configuration Protocol, as well as during the AN-initiated state of that protocol.




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Stream Layer Encapsulation

Session Layer Payload

Stream Layer Payload

Application Layer Payload

Stream Layer Header

Stream Layer Encapsulation

The Stream Layer Protocol receives application packets for transmission from up to four different applications. The protocol adds a 2-bit Stream header that is associated with the application sending the application packet. The protocol forwards the Stream Layer packet to the Session Layer for transmission.

All Stream Layer packets forwarded to the Session Layer are octet aligned.

The protocol receives Stream Layer packets from the Session Layer and removes the Stream Layer header. The application packet obtained in this manner is forwarded to the application indicated by the Stream field of the Stream Layer header.




80-31392-2 Rev B


CDMA2000 1xEV-DO Release 0Stream Layer Packet

Application Layer PacketStream Layer Header

2 Bits

x Bits

x must satisfy the condition, x modulo 8 = 6

Stream Layer Packet

The 2-bit header is used to identify up to four different applications.




80-31392-2 Rev B



9 The functions of the Stream Layer.

9 How the Stream Layer encapsulates packets.

9 The procedures for Stream Layer configuration.

What We Learned in This Section

Notes




80-31392-2 Rev B



SECTION REVIEW

105AC_00

Stream Layer Review

Overview Functions Stream Configuration

Procedure Encapsulation Packet

Notes




80-31392-2 Rev B

Comments/Notes


CDMA2000 1xEV-DO Release 0Section 10: Application Layer

80-31392-2 Rev B




Section 10:Application Layer

Application Layer10SECTION

Notes



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Section Introduction


106AC_00.emf

Default Signaling Application

Signaling Link Protocol (SLP)

Signaling Network Protocol (SNP)

Default Packet Application Radio Link Protocol (RLP) Location Update Protocol Flow Control Protocol

Notes



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Section Learning Objectives

Describe the functions of the Application Layer.

Describe the functions of the Default Signaling Application protocols.

Describe the functions of the Default Packet Application protocols.

Notes



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Application Layer

Air LinkManagement

Protocol


PacketConsolidation

Protocol


Idle StateProtocol



SessionManagement

Protocol


Protocol

StreamProtocol

Radio LinkProtocol




Protocol


Protocol

SecurityProtocol


EncryptionProtocol



AddressManagement

Protocol



ConnectionLayer

SessionLayer

StreamLayer

ApplicationLayer

MACLayer

SecurityLayer

PhysicalLayer





Application Layer

The Application Layer consists of two default applications:z Default Signaling Application Transports 1xEV-DO protocol messages. z Default Packet Application Transports user data.



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Default Signaling Application

Signaling Link Protocol (SLP) Delivery Layer (SLP-D) Fragmentation Layer

(SLP-F) Signaling Network Protocol

(SNP)

Notes



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Default Signaling Application (continued)

The default Signaling Application consists of the Signaling Link Protocol (SLP) and the Signaling Network Protocol (SNP).

SLP provides message fragmentation, reliable and best-effort message delivery, and duplicate detection for messages that are delivered reliably.

SNP is used by 1xEV-DO protocols to exchange messages and application-specific control messages.

Default Signaling Applicationz Signaling Link Protocol (SLP) Provides fragmentation mechanisms, as well as reliable

and best-effort delivery mechanisms for signaling messages. When used in the context of the Default Signaling Application, SLP carries SNP packets.

z Signaling Network Protocol (SNP) Provides message transmission services for signaling messages.



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Signaling Link Protocol (SLP)

Signaling Link Protocol (SLP)The SLP consists of two sublayers:

z Delivery Layer, SLP-D Provides best-effort and reliable delivery for SNP packets. z Fragmentation Layer, SLP-F Provides duplicate detection and retransmission for

messages using reliable delivery. SLP-F provides fragmentation for SLP-D packets.



80-31392-2 Rev B




Signaling Link Protocol:Message Encapsulation (Non-fragmented)

Signaling Link Protocol: Message Encapsulation (Non-fragmented)The figure shows the relationship between a message, SNP packets, SLP packets, and Stream Layer Protocol for a case where the SLP does not fragment the SNP packet.



80-31392-2 Rev B




Signaling Link Protocol:Message Encapsulation (Fragmented)

Signaling Link Protocol: Message Encapsulation (Fragmented)The figure shows the relationship between a message, SNP packets, SLP packets, and Stream Layer Protocol for a case where the SLP does fragment the SNP packet.



80-31392-2 Rev B




Signaling Link Protocol:SLP-D Header

0 or 3SequenceNumber

0 or 1SequenceValid

0 or 3AckSequenceNumber

0 or 1AckSequenceValid

1FullHeaderIncluded

Length (bits)Field

Signaling Link Protocol: SLP-D Header

The SLP-D header contains the following fields:z FullHeaderIncluded SLP-D included flagz The following fields are included only if the FullHeaderIncluded field is set to 1:

AckSequenceValid Set to 1 if the AckSequenceNumber field is valid; otherwise, the sender sets this field to 0.

AckSequenceNumber If the AckSequenceValid field is set to 1, the sender sets this field to the sequence number of the first reliable delivery SLP-D payload

that has not been acknowledged; otherwise, the sender sets this field to 0. SequenceValid Set to 1 if the SequenceNumber field contains a valid value;

otherwise, set to 0. SequenceNumber If the SequenceValid field is set to 1, the sender sets this field

to the sequence number of the reliable SLP-D payload; otherwise, the sender sets this field to 0.



80-31392-2 Rev B




Signaling Link Protocol:SLP-F Header

0 or 1OctetAlignmentPad

0 or 6SequenceNumber

0 or 1End

0 or 1Begin

1Fragmented

4Reserved

Length (bits)Field

Signaling Link Protocol: SLP-F Header

The SLP-F header contains the following fields:z Reserved Sender sets this field to 0.z Fragmented SLP-F header fragmentation indicator.z Begin Start of SLP-D packet flag. Set to 1 if the SLP-F payload contains the beginning

of an SLP-D packet; otherwise, set to 0. Included only if the Fragmented field is set to 1.

z End End of SLP-D packet flag. Set to 1 if the SLP-F payload contains the end of an SLP-D packet; otherwise, set to 0. Included only if the Fragmented field is set to 1.

z SequenceNumber SLP-F packet sequence number. Sender increments this field for each new SLP-F packet sent. Included only if the Fragmented field is set to 1.

z OctetAlignmentPad Octet alignment padding. Sender sets this field to 0 if the Fragmented field is set to 1 and the Begin field is set to 0; otherwise, the sender omits this field.



80-31392-2 Rev B




Signaling Link Protocol:SLP-D Transmit Sequence Number Variables

Signaling Link Protocol: SLP-D Transmit Sequence Number Variables

SLP-D is ACK-based with a sequence space of S = 3 bits.

SLP-D maintains the following variables for reliable delivery of SLP-D packet payloads:z V(S) is the sequence number of the next SLP-D packet to be sent.z V(N) is the sequence number of the next expected SLP-D packet.z Rx is a 2S-bit vector. Rx[i] = 1 if the SLP-D packet with sequence number i was

received.



80-31392-2 Rev B




Signaling Link Protocol:SLP-D Receive Sequence Number Variables

Signaling Link Protocol: SLP-D Receive Sequence Number Variables

The SLP-D reliable-delivery receiver maintains a S bit variable, V(N). V(N) contains the sequence number of the next expected SLP-D packet. The receiver also maintains a 2S-bit vector Rx. Rx[k] is set to 1 if the SLP-D packet with sequence number k has been received.



80-31392-2 Rev B




Signaling Link Protocol:Fragmentation Layer

SLP-F is a self-synchronizing, loss detection protocol with a sequence space of S = 6 bits.

SLP-F maintains the following variables for SLP-F packets: V(S) Sequence number of the next SLP-F packet to be sent V(N) Sequence number of the next expected SLP-F packet Sync SLP-F synchronized flag

Signaling Link Protocol: Fragmentation Layer

The sender constructs the SLP-F payload(s) by adding the SLP-F header. The sender constructs the SLP-F payload(s) from an SLP-D packet. If the SLP-D packet exceeds the current maximum SLP-F payload size, then the sender fragments the SLP-D packet.

If the sender does not fragment the SLP-D packet, then the SLP-D packet is the SLP-F payload. If the sender does fragment the SLP-D packet, then each SLP-D packet fragment is an SLP-F payload.



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Signaling Network Protocol (SNP)

SNP is a message-routing protocol that routes messages to protocols according to the Type field provided in the SNP header.

The actual protocol indicated by the Type field is negotiated during session setup.

The remainder of the message following the Type field is processed by the protocol specified in the Type field.

Signaling Network Protocol (SNP)SNP receives messages for transmission from multiple protocols. SNP adds the Type field to each message and forwards it for transmission to the SLP.

SNP receives messages from the SLP and routes these messages to the associated protocols according to the value of the Type field in the SNP header.



80-31392-2 Rev B




Signaling Network Protocol:Signaling Message Requirements

Messages must be octet aligned.

The receiver silently discards all unrecognized messages and fields or fields set to invalid values.

Future revisions will add new fields at the end of the message.

Signaling Network Protocol: Signaling Message Requirements

These signaling message requirements apply to all protocols that carry messages using SNP and that provide for message extensibility.



80-31392-2 Rev B


Each message definition contains the following information:z Physical Layer channel on which the message can be transmitted:

CC Control Channel (synchronous or asynchronous capsule) CCsyn Control Channel synchronous capsule AC Access Channel FTC Forward Traffic Channel RTC Reverse Traffic Channel

z SLP requirements: Best Effort Message sent once and subject to erasure Reliable Erasures detected, and message retransmitted one or more times, if

necessaryz Addressing mode:

Broadcast If a broadcast address can be used with this message Multicast If a multicast address can be used with this message Unicast If a unicast address can be used with this message

z Priority A number between 0 and 255, where lower numbers indicate higher priorities. The Connection Layer (specifically, the Packet Consolidation Protocol) uses this to prioritize messages for transmission.



Signaling Network Protocol:Message Definition



80-31392-2 Rev B




Signaling Network Protocol:Packet Structure

Signaling Network Protocol: Packet Structure

This figure shows the SNP packet structure. The protocol constructs a SNP packet by adding the SNP header in front of the payload. The SNP header is one octet in length, and messages are always an integer number of octets in length. For future revisions, the transmitter shall add new fields only at the end of a message.



80-31392-2 Rev B




Signaling Network Protocol:Default Protocol Stack

Type Protocol Constant Name Layer 0x14 Stream 0 Application NAPP0Type Application

0x15 Stream 1 Application NAPP1Type Application



0x13 Stream Protocol NSTRType Stream

0x10 Session Management Protocol NSMPType Session

0x11 Address Management Protocol NADMPType Session

0x12 Session Configuration Protocol NSCPType Session

0x0a Air Link Management Protocol NALMPType Connection

0x0b Initialization State Protocol NISPType Connection

Signaling Network Protocol: Default Protocol Stack

This table shows the Type definitions associated with the Default Protocol Stack.



80-31392-2 Rev B




Signaling Network Protocol:Default Protocol Stack (continued)

Type Protocol Constant Name Layer 0x0c Idle State Protocol NIDPType Connection

0x0d Connected State Protocol NCSPType Connection

0x0e Route Update Protocol NRUPType Connection

0x0f Overhead Messages Protocol NOMPType Connection

0x09 Packet Consolidation Protocol NPCPType Connection

0x08 Security Protocol NSPType Security

0x05 Key Exchange Protocol NKEPType Security

0x06 Authentication Protocol NAPType Security

0x07 Encryption Protocol NEPType Security

Notes



80-31392-2 Rev B




Signaling Network Protocol:Default Protocol Stack (continued)

Type Protocol Constant Name Layer 0x01 Control Channel MAC Protocol NCCMPType MAC

0x02 Access Channel MAC Protocol NACMPType MAC

0x03 Forward Traffic Channel MAC Protocol NFTCMPType MAC

0x04 Reverse Traffic Channel MAC Protocol NRTCMPType MAC

0x00 Physical Layer Protocol NPHYType Physical

Notes



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Default Packet Application

Radio Link Protocol (RLP) Location Update Protocol

Flow Control Protocol

Notes



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Default Packet Application (continued)

The Default Packet Application provides an octet stream that can be used to carry packets between the AT and the AN.

It consists of

Radio Link Protocol (RLP) Packet Location Update Protocol

Flow Control Protocol

Default Packet Application

The Default Packet Application consists of:z Radio Link Protocol (RLP) Provides in-order delivery of RLP packets, retransmission,

and duplicate detection, thus reducing the radio link error rate as seen by the higher layer protocols.

z Packet Location Update Protocol Defines location update procedures and messages in support of mobility management for the Packet Application.

z Flow Control Protocol Provides the flow control mechanism for SN and AN streams.



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Radio Link Protocol (RLP)

Provides an octet stream service with acceptably low erasure rate for higher layer protocols such as TCP.

NAK-based, with one retransmission permitted.

Unaware of higher layer framing and operates on a featureless octet stream.

Sequence numbers are 22 bits in length and octet addressable.

A flush packet is sent at the end of a data burst to detect potentially missing data and to create a NAK.

Radio Link Protocol (RLP)RLP provides an octet stream service with an acceptably low erasure rate for efficient operation of higher layer protocols (for example, TCP). When used as part of the Default Packet Application, the protocol commonly carries variable length PPP packets. When RLP is used with PPP, there is no relationship between the PPP packets and the RLP packets; a large PPP packet may span multiple RLP packets, or a single RLP packet may contain all or part of several small PPP Packets. RLP is unaware of higher layer framing.

RLP uses Negative Acknowledgment (NAK)-based retransmissions. If the receiver fails to receive octets whose retransmission it has already requested once, the receiver forwards the octets it has received to the upper layer, and continues reception beyond the missing octets.

Note: Multiple NAKs are not permitted, because they can cause timeouts of transmit buffers when used with the Transmission Control Protocol (TCP).



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Radio Link Protocol: NAK Messages

A NAK request is specified in terms of the first octet missing from the sequence (FirstErased) and the length of the missing octet sequence(WindowLen).

There are multiple NAK requests per NAK signaling message.

Note



80-31392-2 Rev B




Radio Link Protocol:Default Packet Application Encapsulation

Radio Link Protocol: Default Packet Application Encapsulation

The figure shows the relationship between the octet stream from the upper layer, an RLP packet, and a Stream Layer payload.



80-31392-2 Rev B




Radio Link Protocol:Transmit Sequence

Radio Link Protocol: Transmit Sequence

The RLP transmitter maintains an S-bit variable, V(S), for all transmitted RLP data octets. V(S) is the sequence number of the next RLP data octet to be sent. The sequence number field (SEQ) in each new RLP packet transmitted is set to V(S), which corresponds to the sequence number of the first octet in the packet. The sequence number of the ith octet in the packet (with the first octet being octet 0) is implicitly given by SEQ+i. V(S) is incremented for each octet contained in the packet.

After transmitting a packet, the RLP transmitter starts an RLP flush timer for time TRLPFlush. If the RLP transmitter sends another packet before the RLP flush timer expires, the RLP transmitter resets and restarts the timer. If the timer expires, the RLP transmitter disables the flush timer and sends an RLP packet that contains at least the octet with sequence number V(S)-1. The RLP transmitter allows sufficient time before deleting a packet transmitted for the first time.

Upon receiving a NAK message, the RLP inserts a copy of the requested octet(s) into its output stream, if those octets are available. If the NAK record includes any sequence number greater than or equal to V(S), RLP performs reset procedures. If the NAK record does not include any sequence number greater than or equal to V(S), but the requested octets are not available for retransmission, RLP ignores the NAK.



80-31392-2 Rev B




Radio Link Protocol:Receive Sequence

Radio Link Protocol: Receive Sequence

The RLP receiver shall maintain two S-bit variables for receiving:z V(R) Contains the sequence number of the next octet expected to arrive. z V(N) Contains the sequence number of the first missing octet, as described below.

In addition, the RLP receiver shall keep track of the status of each octet in its resequencing buffer indicating whether or not the octet was received. Three S-bit variables are used:

z V(S) Indicates the sequence number of the next octet to be sent.z V(R) Indicates the sequence number of the next octet expected to be received.z V(N) Indicates the sequence number of the first missing octet.



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Location Update Protocol

The Location Update Protocol defines location update procedures and messages for mobility management for the Default Packet Application.

Location Update Protocol provides procedures for the AN to determine the location of the AT.

These procedure are also used in performing data session handoffs from a 1X to a 1xEV-DO network.

Notes



80-31392-2 Rev B




Location Update Protocol:AT Requirements

If the AT receives a LocationRequest message, it sends a LocationNotification message. The AT sets the LocationType, LocationLength, and LocationValue fields of the LocationNotification message to its stored values of these fields.

If the AT receives a LocationAssignment message, it stores the value of the LocationType, LocationLength, and LocationValue fields of the LocationAssignment message. The AT then sends a LocationComplete message.

If the AT receives a SessionClose indication, it sets LocationValue to NULL.

Notes



80-31392-2 Rev B




Location Update Protocol:IS-2000-Compatible Location Subfields

LocationValue Subfields Number of Bits

SID 15

Reserved 1

NID 16

PACKET_ZONE_ID 8

Location Update Protocol: IS-2000-Compatible Location Subfields

There are two LocationType encoding types: one is for a TIA/EIA-IS-2000-compatible location, and the other is a packet data service identifier. The LocationValue subfields above are compatible with IS-2000.

The LocationValue subfields are:z SID System identifier for the current ANz NID Network identifier for the current ANz PACKET_ZONE_ID Packet zone identifier for the current AN

LocationValue attributes are included in the LocationAssignment message and LocationNotification message.



80-31392-2 Rev B




Location Update Protocol:LocationNotification Message

The AT sends out a LocationNotification message either in response to a LocationRequest message or in an unsolicited manner. The RanHandoff attribute must be set to 1 for this capability.

This procedure of LocationUpdate is used when the AT performs a dormant packet data session handoff from a CDMA2000 network to a 1xEV-DO network. The assumption is that a 1X-to-1xEV-DO session exists.

When the AT with a dormant packet data session on a CDMA2000 network detects a 1xEV-DO signal, it sends an unsolicited LocationNotification message to the AN. This allows the AN to set up an A11-A10 connection between the target PCF and the PDSN.

Notes



80-31392-2 Rev B



CDMA2000 1xEV-DO Release 0Flow Control Protocol

The Flow Control Protocol provides procedures and messages used by the AT and the AN to perform flow control for the Default Packet Application.

Using the procedures defined in this protocol, the Default Packet Application Protocol controls the flow of packets on the AN and SN streams.

Notes



80-31392-2 Rev B




Flow Control Protocol:Messages and States

The AT uses flow control messages, XonRequest and XoffRequest, to indicate whether it can accept data on a particular stream.

If the AT can accept data on the (AN or SN ) stream, it sends anXonRequest message to the AN. The state of the stream is changed to Open.

If the AT cannot accept data on the (AN or SN ) stream, it sends an

Date post:	10-Oct-2015
Category:	Documents
Upload:	pappuamin789
View:	9 times
Download:	0 times

CDMA2000_1XEV-DO_Rel.0(2)

Documents