3GPP2-C30-20000327-____

1xHDR Overview
March 27, 2000 Ericsson, Lucent Technologies, QUALCOMM Incorporated Contact: Peter Black, Qualcomm (pblack@qualcomm.com)

2000 Contributing companies. All rights reserved. The information contained in this contribution is provided for the sole purpose of promoting discussion within the 3GPP2 and its Organization Partners and is not binding on the contributor. The contributor reserves the right to add to, amend, or withdraw the statements contained herein.

Proposal for High-Performance Packet Data

Proposed CDMA2000 Companion High Data Rate (HDR) Standard
> network architecture > radio link protocol > signaling > physical layer

Supporting companies
Casio, Denso, Ericsson, Hitachi, Kyocera, LGIC, Lucent Technologies, Qualcomm, Samsung Electronics, Sanyo, Sharp, Si erra Wi r eless, Toshiba

1xHDR Approach
Voice and high-speed packet data for wirel ess internet impose vastly different requirements:
Voice - low speed, symmetric, low latency, uniform GOS Packet Data - high burst rates, asymmetric, variable latency, non-uniform GOS.

Solution - dedicated carrier for packet data services (HDR):

Maintain compatibility with cdma2000 network architectures and plans Maintain compatibility with cdma2000 RF parameters and components Terminal interop between 1x and HDR Dynamic carrier allocation 1x or HDR.

1xHDR S o uti on l
Forward-link
TDMed, full power, variable rate (38.4kbps - 2.4576Mbps) Rapid, low latency channel state feedback (600Hz) Adaptive coding and modulation (R=1/4-1/2, 4-PSK, 8-PSK, 16-QAM) Full power burst pilot No soft handoff Multi-user and multi-antenna receive diversity.

Reverse-Link
Pilot added coherent demodulation (4.8kbps - 153.6kbps) Soft handoff Open/closed loop control.

Adaptive Variable Rate Forward Link

Power

User 2 Rate=307.2 kbps

IDLE

Pilot Bursts

Time User 1 Rate=614.4 kbps User 3 Rate=1.228 Mbps

Channel Estimation and Rate Feedback

Rate Prediction Performance

OTA Sector Capacity Results
2,000,000 1,900,000 1,800,000 1,700,000 1,600,000

Throughput (kbps)

1,500,000 1,400,000 1,300,000 1,200,000 1,100,000 1,000,000 900,000 800,000 700,000 600,000 500,000 0 1 2 3 4 5 6 7 8 9 actual predictor genie-aided predictor

Users
7

Multi-User Diversity Gain

Multi-User and Multi-Antenna Diversity Gain

OTA Sector Capacity - Mobility Run
1,200,000

1,000,000

Throughput (b/s)

800,000

600,000

Single Antenna Antenna Diversity

400,000

200,000

0 0 2 4 6 8 10 12 14 16 18

Active Users

1x HDR Architecture and Requirements

Contact: Ramin Rezaiifar (raminr@qualcomm.com)

10

Terms
AT: Access Terminal IS-2000 Network Access mode: A mode of access in which the AT is communicating with only the IS-2000 RN. HDR Network Access mode: A mode of access in which the AT is communicating with only the 1xHDR RN. Hybrid AT: An Access Terminal that can operate in a 1xHDR Radio Network, IS-2000 Radio Network, or both radio networks. Hybrid Network Access Mode: A mode of access in which the AT is exchanging data with the 1xHDR RN and monitoring the IS-2000 common channels. PCF:Packet Control Function RN: Radio Network. In IS-2000, an RN is the footprint of a PCF. In 1xHDR, RN is the footprint of a 1xHDR BSC.

11

Requirements

The following is a list of requirements that will be respected relative to interaction between the IS-2000 set of specifications and 1xHDR specification: R1. No changes shall be made to the IOS specification (produced by TSG-A):
R1.1. No changes shall be made to the MSC interfaces. R1.2. No changes shall be made to the PDSN interfaces.

R2. No changes shall be made to the IS-2000 specifications. R3. No changes shall be made to the "Wireless IP Network Standard" (produced by TSG-P). R4. The standard should allow support for a Hybrid AT to receive notifications for mobile station terminated voice calls and other services provided by IS-2000 (e.g., Broadcast SMS) even when the AT is exchanging data with a 1xHDR RN.

12

Requirements (contd)

R5. From the PDSN point of view an RN change from an IS2000 RN to a 1xHDR RN should not be any different than an RN change between two IS-2000 RN's. R6. From the PDSN point of view an RN change from a 1xHDR RN to an IS-2000 RN should not be any different than an RN change between two IS-2000 RN's. R7. It shall be possible for IS-2000 RN and 1xHDR RN to be implemented independently. R8. The 1xHDR RN shall not have any connection to the MSC. R9. The specification shall support the scenarios listed in the Scenario Slides.

13

Network Architecture
1xHDR Radio Network

1xHDR BTS

1xHDR BSC

A10 A11

IS-2000 Radio Network A1 A2 A5 A10 A11

PDSN

IS-2000 BTS

IS-2000 BSC

MSC

The 1xHDR BSC does not require a connection to the MSC. Requirement R4 is satisfied by the AT monitoring the IS-2000 common channels while the AT is exchanging data with the 1xHDR RN.
14

Example of Network Topology

PDSN #1 A10/A11 PDSN #2 A10/A11 IS-41 MSC A1/A2/A5 IS-41 MSC A1/A2/A5

IP cloud A10/A11

SS7

A1/A2/A5

1xHDR RN #1

1xHDR RN #2

IS2k RN #1

IS2k RN #2

AT

The above figure shows an example 1xHDR/IS-2000 network topology. Each 1xHDR RN is connected to a collection of PDSNs through an IP network. The overlapped area between 1xHDR RN #2 and IS-2000 RN #1 signifies an area in which both 1xHDR and IS-2000 carriers are present.
15

Hybrid AT Scenarios
The following is a (non-exhaustive) list of the scenarios that are supported by the 1xHDR specification for a Hybrid AT: Scenario 1:
AT moves from a 1xHDR Radio Network (1xHDR RN#1) to another 1xHDR RN (1xHDR RN#2) while the packet data service is Dormant.

Scenario 2:
While the AT is exchanging data in a 1xHDR RN, it receives a page for an incoming voice service instance from the IS-2000 RN. The AT switches to the IS-2000 RN and continues voice + data in the IS-2000 RN.

Scenario 3:
While the AT is exchanging data in a 1xHDR RN, it initiates a voice call in the IS-2000 RN. The AT switches to the IS-2000 RN and continues voice + data in the IS-2000 RN.

16

Hybrid AT Scenarios (contd)

Scenario 4:
While the AT resides in the coverage area of a 1xHDR RN, the packet data service transitions to the Dormant State. After a certain period of inactivity (which is up to the AT configuration) the AT performs a Dormant handoff to the overlaid IS-2000 RN to ensure that the Dormancy of the packet data service instance is preserved without requiring the AT to monitor both 1xHDR and IS-2000 carriers for an extended period of time.

Scenario 5:
While the AT resides in the coverage area of a 1xHDR RN, the packet data service transitions to the Dormant State. The AT remains in the 1xHDR RN (with the Dormant packet data service) and monitor the IS-2000 common channels as well as the 1xHDR Control Channel.

17

Hybrid AT Scenarios (contd)

Scenario 6:
AT has an active or Dormant packet data service in 1xHDR RN. AT moves away from the coverage area of the 1xHDR RN into the coverage area of an IS-2000 RN (or due to some other trigger decides to switch to the IS-2000 RN). If the packet data service is active, the PPP instance may be preserved and data exchange continues in the IS-2000 RN. If Packet data service is Dormant, then dormancy may be preserved in the IS-2000 RN.

Scenario 7:
AT has an active or Dormant packet data service in IS-2000 RN. AT moves away from the coverage area of the IS-2000 RN into the coverage area of a 1xHDR RN (or due to some other trigger decides to switch to the 1xHDR RN). If the packet data service is active, the PPP instance may be preserved and data exchange continues in the 1xHDR RN. If Packet data service is Dormant, then dormancy may be preserved in the 1xHDR RN.

18

Hybrid AT Scenarios (contd)

Scenario 8:
AT receives an IS-2000 Broadcast SMS while it is exchanging data with the 1xHDR RN.

Scenario 9:
Both voice & data service instances are active in the IS-2000 RN. Voice service instance ends. The AT stays in the IS-2000 RN.

Scenario 10:
Both voice & data service instances are active in the IS-2000 RN. Voice service instance ends. The AT switches to the 1xHDR RN and continue the packet data exchange in the 1xHDR RN (and monitors the common channels of IS-2000 RN).

19