1xEV-DO Broadcast Registration and

Multi-Carrier Operation
Feature Definition Document
80-V9035-1 B
February 6, 2006

Submit technical questions at:

https://support.cdmatech.com

QUALCOMM® Proprietary
Restricted Distribution: This document contains critical information about QUALCOMM products and may not be distributed
to anyone that is not an employee of QUALCOMM, its affiliates or subsidiaries without the approval of Configuration
Management.

All data and information contained in or disclosed by this document is confidential and proprietary information of QUALCOMM
Incorporated and all rights therein are expressly reserved. By accepting this material the recipient agrees that this material and the
information contained therein is to be held in confidence and in trust and will not be used, copied, reproduced in whole or in part,
nor its contents revealed in any manner to others without the express written permission of QUALCOMM Incorporated.

QUALCOMM Incorporated reserves the right to make changes to the product(s) or information contained herein without notice.
No liability is assumed for any damages arising directly or indirectly by their use or application. The information provided in this
document is provided on an “as is” basis.

This document contains QUALCOMM proprietary information and must be shredded when discarded.

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. ARM is a registered trademark of ARM
Limited. QDSP is a registered trademark of QUALCOMM Incorporated in the United States and other countries. Other product
and brand names may be trademarks or registered trademarks of their respective owners.

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

QUALCOMM Incorporated
5775 Morehouse Drive
San Diego, CA 92121-1714
U.S.A.
Copyright © 2005-2006 QUALCOMM Incorporated. All rights reserved.
 1xEV-DO Broadcast Registration and Multi-Carrier Operation

1 1 Introduction

2 1.1 Purpose
3 The purpose of this document is to describe the registration and multi-carrier operation features of
4 the 1xEV-DO broadcast protocol suite implemented in the access terminal (AT).

5 1.2 Scope
6 This document describes some operational details of AMSS with respect to 1xEV-DO broadcast
7 registration and multi-carrier operation.

8 1.3 Conventions
9 The term channel is used consistently in this document to refer to the 1.25 MHz RF channel
10 (carrier frequency) designated for use as a 1xEV-DO air interface.
11 Shading indicates content that has been added or changed in this revision of the document.

12 1.4 Revision history

13 The revision history for this document is shown in Table 1.

14 Table 1 Revision history

Version Date Description

A Jan 2005 Initial release
B Feb 2006 Updated chapter 5; added chapter 6
15

80-V9035-1 B 2 QUALCOMM Proprietary

 1xEV-DO Broadcast Registration and Multi-Carrier Operation

1 1.5 References
2 Reference documents, which may include QUALCOMM®, standards, and resource documents,
3 are listed in Table 2. Reference documents that are no longer applicable are deleted from this
4 table; therefore, reference numbers may not be sequential.

5 Table 2 Reference documents and standards

Ref. Document

QUALCOMM
Q1 Application Note: Software Glossary for Customers CL93-V3077-1
Standards
S1 CDMA2000 High Rate Broadcast-Multicast Packet Data Air 3GPP2 C.S0054 Version 1.0
Interface Specification
6

7 1.6 Technical assistance

8 For assistance or clarification on information in this guide, submit a Service Request to
9 QUALCOMM CDMA Technologies at https://support.cdmatech.com/.
10 If you do not have access to Internet web browsing, you may send email to
11 support.cdmatech@qualcomm.com.

12 1.7 Acronyms
13 For definitions of terms and abbreviations, refer to [Q1].

14 2 Assumptions
15 Per [S1], the access network (AN) will only list flows in the Broadcast Overhead message that are
16 being transmitted.
17 The AN will transmit consistent Broadcast Overhead messages on all channels listed in the
18 SectorParameters message and all channels on which broadcast flows are advertised. For
19 example, on channel A, the AN will not send a Broadcast Overhead message listing a flow as
20 being transmitted on channel B unless the Broadcast Overhead message on channel B also lists
21 that flow as being transmitted on channel B.
22 If more than one channel is used within the network, the AN will either enable registration for
23 paging or page the AT on all channels.

80-V9035-1 B 3 QUALCOMM Proprietary

 1xEV-DO Broadcast Registration and Multi-Carrier Operation

1 3 Recommendations
2 If the AN supports dynamic broadcast, the AN should interpret a registration from the AT as a
3 registration for all sectors within the current subnet that the AT could reach within the current
4 registration period. Note that the AT will not register for that flow again within the registration
5 period, regardless of how far it moves from the sector on which it originally registered. One
6 exception is that the AT will register again if it moves into a new subnet (see Section 4).
7 If the AN transmits a flow on different channels within a subnet, the AN should consider the
8 registration from the AT to pertain to all channels on which the flow is transmitted. For example,
9 the AN should not expect the AT to reregister for dynamic broadcast if it starts monitoring the
10 flow on a new channel.
11 Registration for dynamic broadcast may be used as a roll-call mechanism by negotiating a short
12 registration period for dynamic broadcast, then only enabling registration for dynamic broadcast
13 in the Broadcast Overhead message for short periods, e.g., when considering turning off a flow.

14 4 Registration
15 The AT complies with all requirements of [S1] relevant to sending the BCMCSFlowRegistration
16 message. This compliance is summarized as follows:
17 „ When the registration timer expires, the AT sends a BCMCSFlowRegistration message
18 listing all flows for which registration is required at that time. The AT does not send the
19 BCMCSFlowRegistration message with an empty list of flows.
20 In addition, the AT implements other requirements not included in but permitted by [S1]. These
21 are summarized as follows:
22 „ When a new flow is requested by an application and the flow is listed in the Broadcast
23 Overhead message, the AT shall send a BCMCSFlowRegistration message for the new flow
24 if both of the following conditions are met:
25 ˆ Registration is permitted for the flow (PagingRegistrationPeriod is nonzero or
26 DynamicBroadcastRegistrationPeriod is nonzero).
27 ˆ The AT has not previously registered for this flow in this subnet within the last
28 registration period.
29 „ When a new flow is requested by an application and the flow is not listed in the Broadcast
30 Overhead message, the AT shall send a BCMCSFlowRegistration message for the new flow
31 if both of the following conditions are met:
32 ˆ Registration is permitted for the flow (PagingRegistrationPeriod is nonzero or
33 DynamicBroadcastRegistrationPeriod is nonzero).
34 ˆ The AT has not previously registered for this flow within the last
35 NumPeriods * (2 ^ MonitorPeriod)* 80 ms.
36 „ When the registration timer expires, the AT shall include in the BCMCSFlowRegistration
37 message all requested flows not listed in the Broadcast Overhead message that the AT has not
38 registered for within the last NumPeriods * (2 ^ MonitorPeriod)* 80 ms.

80-V9035-1 B 4 QUALCOMM Proprietary

 1xEV-DO Broadcast Registration and Multi-Carrier Operation

1 5 Multi-Carrier Support
2 The following terms are used in this section:
3 „ Idle channel – Channel the AT monitors while in the Idle state
4 „ Requested flow – A flow that is currently desired by an application
5 „ Available flow – A flow that is listed in the Broadcast Overhead message
6 „ Reference flow – Highest priority requested flow that is available
7 There are no explicit requirements in [S1] governing how the AT tunes to different channels
8 while idle to monitor BCMCS flows. The AT implements the following requirements not
9 included in but permitted by [S1]:
10 „ The AT shall assign a priority to each requested flow based on when it is first requested by
11 the application, with the lowest priority given to the most recently requested flow and highest
12 priority given to the oldest requested flow.
13 „ The AT bases its choice of idle channel on the reference flow. If there are no requested flows,
14 or none of the requested flows are available, then the reference flow is NULL. The AT shall
15 update its reference flow if any of the following events occur:
16 ˆ The reference flow is NULL and a requested flow becomes available
17 ˆ The reference flow becomes unavailable
18 ˆ A higher priority flow becomes available
19 ˆ There is a change to the set of requested flows
20 „ When the reference flow changes, the AT shall choose the idle channel as follows:
21 ˆ If the reference flow is NULL, the idle channel shall be set to the hash channel.
22 ˆ If the reference flow is not NULL, the idle channel shall be the channel on which the
23 reference flow and the greatest number of other desired flows are available. If more than
24 one channel meets these criteria, the one listed first in the Broadcast Overhead message is
25 chosen.
26 „ If the AT is configured to use the enhanced idle protocol 1 and the AT sends a
27 ConnectionRequest message when the reference flow is not NULL, the AT shall set the
28 PreferredChannelCount field to 1 and set the PreferredChannel field to the idle channel.
29 „ If the AT is assigned a traffic channel that is different from the idle channel, the AT shall
30 monitor all requested flows being transmitted on the assigned channel.
31 „ While in the Connected state, if the reference flow changes to be a flow that is not available
32 on the current channel but is available on a different channel, the AT shall close the
33 connection. This causes the AT to return to Idle state, tune to the new idle channel and then
34 send a ConnectionRequest message.

1Configuration attribute with ID 0x0C of the in-use instance of the SessionConfiguration protocol has a
value of 0x0001.

80-V9035-1 B 5 QUALCOMM Proprietary

 1xEV-DO Broadcast Registration and Multi-Carrier Operation

1 6 Broadcast Overhead Message Supervision

2

NOTE This chapter was added to this document revision.

3

4 Broadcast Overhead message supervision is needed only to accommodate a network deployment

5 where the 1xEV-DO broadcast protocol (0x18) is negotiated to subtype 1 as part of the session
6 but certain sectors do not support broadcast services and thus do not send the Broadcast Overhead
7 message. Without supervision of the Broadcast Overhead message, the AT would continue to
8 report to the application that certain flows are available even when on a sector that does not
9 support broadcast.
10 The following algorithm defines the behavior of an AT that has the 1xEV-DO broadcast protocol
11 (0x18) negotiated to subtype 1 as part of its session. This algorithm ensures that the flow status
12 given to the applications is accurate within 3xBroadcastOverheadPeriod. If the default value of 7
13 control channel cycles is used for the BroadcastOverheadPeriod attribute, then the flow status of
14 any previously available flows should change to show that they are unavailable after about 12 sec
15 of being on a sector that does not support broadcast.
16 „ The broadcast supervision timer is started if the broadcast application on the AT has
17 requested one or more flows to be monitored and the AT subsequently enters a sector (either
18 via handoff or reacquisition) where the Broadcast Overhead message has not been received.
19 „ The timer is stopped and reset under the following conditions:
20 ˆ The AT receives the Broadcast Overhead message
21 ˆ The AT loses acquisition on the 1xEV-DO system
22 ˆ The application removes all requests to monitor BCMCS flows
23 „ If the timer expires, the AT changes the status of all requested flows to be unavailable and
24 reports a flow failure to the application.

80-V9035-1 B 6 QUALCOMM Proprietary