Workshop
Student Guide
80-W0902-1 Rev C
Not to 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.
This technical data may be subject to U.S. export, re-export or transfer ("export") laws.
Diversion contrary to U.S. law is prohibited.
No part of these written materials may be used or reproduced in any manner whatsoever
without the written permission of QUALCOMM Incorporated.
PRL Technical
About CDMA University Workshop
Notes
PRL Technical
Where Can I Learn More? Workshop
To check out the schedules for these courses and enroll, go to:
www.cdmauniversity.com
May Contain U.S. Export Controlled Information
Notes
PRL Technical
CDMA Courses from CDMA University Workshop
Notes
Table of Contents
PRL Design
System Table.............................................................................. 5-18
Acquisition Table....................................................................... 5-19
PRL Tools
The PRL Editor .......................................................................... 5-20
Spreadsheet ............................................................................... 5-21
PRL Tool Suite – An Excel Add-in ........................................... 5-22
PRESTO ........................................................................................ 5-23
PRL Auditing ........................................................................................ 5-24
PRL PREDICATE ................................................................................. 5-25
PRL PREDICT....................................................................................... 5-26
PRL Design – Section Review............................................................... 5-27
AC Alternating Current
AT Access terminal
DC Direct Current
SECTION
1 Course Overview
Notes
1. Course Overview
2. Introduction to Preferred Roaming Lists
3. How the PRL is Used
4. PRL Process
5. PRL Design
6. PRL Design Checks
7. Hybrid 1X / EV-DO PRL
8. Use of the Hybrid 1X / EV-DO PRL
9. Writing a Hybrid 1X / EV-DO PRL
10. PRL Enhancements
Notes
PRL Technical
Reference Documentation Workshop
Section 1-3
Course References
Course References
Course References
Course References
Course References
964AB_00_revD.emf
Reference Documentation
TIA Name 3GPP2 Name Title / Download Location
IS-856-0 C.S0024-0 v2.0 cdma2000 High Rate Packet Data Air Interface Specification (1.8MB)
http://3gpp2.org/Public_html/specs/C.S0024_v2.0.pdf
IS-856-1 C.S0024-0 v3.0 cdma2000 High Rate Packet Data Air Interface Specification (2.6MB)
http://3gpp2.org/Public_html/specs/C.S0024-0_v3.0.pdf
IS-856-2 C.S0024-0 v4.0 cdma2000 High Rate Packet Data Air Interface Specification (2.3MB)
http://3gpp2.org/Public_html/specs/C.S0024-0_v4.0.pdf
TIA-856-A C.S0024-A v1.0 cdma2000 High Rate Packet Data Air Interface Specification (5.4MB)
http://3gpp2.org/Public_html/specs/C.S0024-A_v1.0_040331.pdf
TIA-1030 C.S0057-0 v1.0 Band-class Specification for CDMA-2000 Spread Spectrum Systems
http://3gpp2.org/Public_html/specs/C.S0057-0_v1.0_020904.pdf
PRL Technical
Reference Documentation (continued) Workshop
Section 1-4
Course References
Course References
Course References
Course References
Course References
964AB_00_revD.emf
Reference Documentation
TIA Name 3GPP2 Name Title / Download Location
TIA/EIA IS-2000 C.S0001-0 v3.0 Introduction to cdma2000 Spread Spectrum Systems Release 0
http://3gpp2.org/Public_html/specs/C.S0001-0_v3.0.pdf
IS-683-A C.S0016-0 v1.0 Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum Systems
http://3gpp2.org/Public_html/specs/C.S0016-0with3Gcover.pdf
TIA-683-B C.S0016-A v2.0 Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum Systems
http://3gpp2.org/Public_html/specs/C.S0016-A_v2.0.pdf
TIA-683-C C.S0016-B v1.0 Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum Standards
http://3gpp2.org/Public_html/Specs/C.S0016-B_v1.0.pdf
TIA-683-D C.S0016-C v1.0 Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum Standards (4.7MB)
http://3gpp2.org/Public_html/specs/C.S0016-C_v1.0_041025.pdf
IS-820 C.S0023-0 v2.0 Removable User Identity Module (RUIM) for cdma2000 Spread Spectrum Systems (357 KB)
http://3gpp2.org/Public_html/specs/CS0023-0.pdf
IS-820-1 C.S0023-0 v4.0 Removable User Identity Module for Spread Spectrum Systems (546 KB)
http://3gpp2.org/Public_html/specs/C.S0023-0_v4.0.pdf
TIA-820-A-1 C.S0023-A v1.0 Removable User Identity Module for Spread Spectrum Systems (558 KB)
http://3gpp2.org/Public_html/specs/C.S0023-A_v1.0.pdf
TIA-820-A-1 C.S0023-A v2.0 Removable User Identity Module for Spread Spectrum Systems (846 KB)
http://3gpp2.org/Public_html/specs/C.S0023-A_v2.0_021004.pdf
TIA-820-A-2[E] C.S0023-A v3.0 Removable User Identity Module for Spread Spectrum Systems (799 KB)
http://3gpp2.org/Public_html/specs/C.S0023-A_v3.0_041220.pdf
TIA-820-B C.S0023-B v1.0 Removable User Identity Module for Spread Spectrum Systems (830 KB)
http://3gpp2.org/Public_html/specs/C.S0023-B_v1.0_040426.pdf
SECTION
Introduction to
2 Preferred Roaming Lists
Notes
PRL Technical
Section Learning Objectives Workshop
Section 2-2
Notes
PRL Technical
Identification of a CDMA Network Workshop
Section 2-3
Regulatory Markets
• Markets are divided into Licensed
areas – Cellular Geographic Service
Areas (CGSAs)
Licenses
• Each license allocates a particular
range of frequencies within a
particular band
• There are multiple licenses available
in multiple bands for one CGSA
Licensees
• Acquire spectrum in one or more
Cellular CGSAs to offer commercial service
Geographic • May not always hold the same
Service Areas
spectrum in adjacent markets
The Market
PRL Technical
Identification of a CDMA Network (continued) Workshop
Section 2-4
Cellular
• Mobile Network Code
Geographic
Service Areas • Radio Frequency (Band Class or Channel)
The Market
Commercial Markets
Regulatory market divisions, while being good administrative tools, may not align with the operator’s commercial markets. Often
the commercial market is a combination of a number of licenses which may span many regulatory markets—which may or may
not be all in the same frequency band. From the commercial operators perspective a commercial market can mean many things; it
can be a city or an area of a city, a county, a state, or some other region defined as a network boundary.
In CDMA, every system identifies itself by broadcasting its name. This name comprises its system identification (SID) and its
network identification (NID). These identities are configured by the operator. One operator may choose to have all systems in a
particular area broadcast the same identity while another may choose a lesser or greater granularity.
System Identification Code
The System Identification code (SID) is a 15-bit binary number that can be represented by a five-digit decimal number. The SID
is used by a network to identify itself. Each SID is globally unique and assigned to a particular operator. The SID is also used
within the MSC Identity and to properly route roaming call records for billing among roaming partners. A SID is allocated to a
carrier by its national telecommunications authority or an appointed agent. The SID is assigned and administered from the
country’s allocation of SID range. A SID range is allocated to an administrator by the International Forum on ANSI-41
Technology (IFAST). There are cases where SIDs are being used outside of the bounds of their IFAST allocation. The known
SID conflicts are detailed on the IFAST web site at http://www.IFAST.org.
In the United States, a SID for the cellular band (800 MHz) used to be assigned by the Federal Communications Commission
(FCC). In August 2002, the FCC adopted an order[1] which transitioned the administration of SIDs to the private sector. There
are six cellular SID administrators that can issue a SID in the US. USA PCS band (1850 – 1990 MHz) SID administration is
performed by CIBERNET. PCS SIDs were originally assigned by CIBERNET according to the FCC auctioned PCS license
areas[2], however, recently there has been consolidation of SIDs to commercial markets.
Network Identification Code
The Network Identification Number (NID) is a 16-bit binary number that can be represented by a five-digit decimal number. The
use of a NID, by the mobile device, to identify a network is optional. The NID is used to subdivide the SID namespace. Each NID
is unique to a particular SID. A NID is locally assigned and administered by the operator owning the SID.
[1] The FCC eliminated the use of SIDs and the SID assignment process in its entirety as part of the license application as a part
of the FCC Year 2000 Biennial Regulatory Review (Amendment of Part 22 of the Commission’s Rules to Modify or Eliminate
Outdated Rules Affecting the Cellular Radiotelephone Service and other Commercial Mobile Radio Services, WT Docket No. 01-
108, Report and Order, FCC 02-229 (released Sept. 24, 2002), the section 22.941 of the Commission Rules, 47 C.F.R. § 22.941).
[2] PCS license areas, which follow the Rand McNally definition of Major Trading Areas (MTAs) and Basic Trading Areas
(BTAs).
PRL Technical
Identification of a CDMA Network (continued) Workshop
Section 2-5
Cellular
• Mobile Network Code
Geographic
Service Areas • Radio Frequency (Band Class or Channel)
The Market
The mobile country code (MCC) identifies the country in which the network operates. An MCC is issued by the
Telecommunications Standardization Body (TSB) of the International Telecommunications Union (ITU) and is
globally unique. A list of existing and valid mobile country codes can be found on the ITU web site at
http://www.itu.int/itudoc/itu-t/ob-lists/icc/index.html.
A mobile network code (MNC) identifies a particular network within a mobile country code and is thus unique
within a particular MCC. While recent standards allow for an MNC of two or three digits, the majority of deployed
commercial infrastructure uses a two digit MNC (irrespective of technology). In CDMA the MNC is often referred
to as the IMSI_11_12. Every CDMA system broadcasts its MCC and IMSI_11_12 (MNC).
An MNC is issued by in-country administrators (a regulatory body or an appointed agent). Administrators are
requested to keep the TSB informed of MNC allocations. A list of existing and valid mobile country codes can be
found on the ITU web site at http://www.itu.int/ITU-T/inr/forms/mnc.html.
Home Network Identity
Every commercial, public service, mobile network can be described by a description known as the Home Network
Identity (HNI). In some technologies, this HNI is referred to as the PLMN-Id (Public Land Mobile Network
Identity). The HNI is comprised of a mobile country code (MCC) and a mobile network code (MNC). Since recent
standards allow for an MNC of two or three digits, some administrators now allocate a six digit HNI (i.e., a 3 digit
MCC and a 3 digit MNC). In the case where the majority of the deployed base of commercial infrastructure can only
use a two digit MNC (again, irrespective of technology) the allocation guidelines have generally been temporarily
adjusted so that only an agreed two of the allocated three digits are broadcast and that integrity is preserved. Such is
the case in the USA.
PRL Technical
Identification of a CDMA Network (continued) Workshop
Section 2-6
PRL Technical
What is a Preferred Roaming List (PRL)? Workshop
Section 2-7
The PRL:
• Indicates frequencies to search
• Indicates systems to select or avoid
• Indicates system preferences
• Speeds up acquisition
• Indicates whether the roam status displays
PRL Technical
Organization of a PRL Database Workshop
Section 2-8
PRL Structure
The PRL comprises three major sections:
z a properties set (header information) that provides general information about the PRL,
z an acquisition table that lists all the frequencies that the device can search, and
z a system table that describes the systems.
PRL Header Information (Properties)
The PRL Header information describes the properties of the whole PRL. These properties describe aspects such as its name (or
identity), default behavior and the type of PRL.
Acquisition Table
The acquisition table contains acquisition records. An acquisition record provides the band and frequencies that the mobile station
is to use when searching to acquire a system. Acquisition records are listed in priority order (highest priority first) in the
acquisition table. The channels in the “CHAN” field of the records are also listed in the priority order.
System Table
The system table contains records describing a system. The System Table is divided into one or more distinct segments; these are
called Geographical Areas, or GEOs. A system record belongs to a Geographical Area. A geographical region would normally be
used to group a set of systems found in the same physical region. Certain other aspects of a system record only have relevance
within the context of a GEO, e.g., priority. A system, in the context of the system table, is identified by its SID and NID. Each
system table record has an indicator, which determines within which geographic area that a particular system belongs.
Other indicators declare whether the system is preferred (permitted) or negative (prohibited). Allowed systems can have relative
priority with respect to each other within a geographic region, effectively making some systems more preferred than others. The
priority that a system has is relative to the other systems in the same GEO. The most preferred system is the most desired system
and what the mobile device will always try to obtain service. There is no limit to the number of priorities that can be present
within a GEO. There can be multiple systems of equal priority.
PRL Technical
Is a PRL Always Required? Workshop
Section 2-9
PRL Technical
Where is the PRL and How Does it Get There? Workshop
Section 2-10
Notes
PRL Technical
Updating the PRL Over the Air Workshop
Section 2-11
Terminology
• Over The Air Service Provisioning (OTASP)
• Over the Air Parameter Administration (OTAPA) –
network initiated
ANSI-41 Core Network
(IS725) • Over The Air Function (OTAF)
• System Selection for Preferred Roaming (SSPR)
Billing Customer Service System AuC (i.e., PRL) download
PSTN
HLR Standards
• IS-683 describes the MS to BTS interaction (and
defines PRL)
• IS-725 describes the network interactions (ANSI-41)
OTA Platform
MSC
OTA platform
• Maintains multiple PRLs (vendor specific, e.g., 256)
CDMA
CDMARAN
RAN(IS-683)
(IS-683)
Process
• User dials OTA feature code (*ACT)
• Selects PRL update at VRU
BS
C
BTS
• CSC selects right PRL
• OTA platform downloads PRL (user hears music)
• Handset resets on completion
PRL Technical
What Does a PRL Look Like? Workshop
Section 2-13
PRL Properties
What you may see in
an Editor:
Acquisition Table
System Table
PRL Technical
Understanding the Properties of a PRL Workshop
Section 2-14
PR_LIST_SIZE 16
PREF_ONLY Description
PR_LIST_ID 16 ‘0’ FALSE - Use only on-negative system
from the System Table AND systems
PREF_ONLY 1
that are not described in the System
DEF_ROAM_IND 8 Table as either
‘1’ TRUE -Only use non-negative systems
NUM_ACQ_RECS 9 in the PRL System Table.
NUM_SYS_RECS 14
ACQ_TABLE variable
If PREF_ONLY is ‘FALSE’ then this is the roaming indicator to use for non-
SYS_TABLE variable PRL systems
PRL Technical
Acquisition Table Workshop
Section 2-15
Editor View:
Acquisition Table
The acquisition table defines, in priority order, the radio environment (frequencies) that are to be
searched for service. The acquisition table consists of a minimum of one and up to 512
acquisition records. Each acquisition record is of a specific type and describes one or a set of
frequencies to search.
The priority ordering of the records in the acquisition table is derived from their sequential order
and is generally used by the system selection process to construct scan lists reflecting the order in
which frequencies appear in the acquisition table. Also, where a set of frequencies are listed
within a record of the acquisition table, the order in which they are listed is often an implied
ordering for scan lists.
An example of what an acquisition table might look like in a PRL editor is shown.
The type of acquisition records that can be defined in a PRL are dependent on the revision of the
standard in use for that particular PRL. The particular types as they apply to revisions A through
C are listed above.
PRL Technical
Cellular Analog Acquisition Record Workshop
Section 2-16
PRL Technical
What are Cellular CDMA Standard Channels? Workshop
Section 2-18
• In the United States, the preferred set of channels that are defined
in IS-2000:
– 283 primary A, 384 primary B
– 691 secondary A, 777 secondary B
What it means:
• Look for 800 MHz CDMA ONLY (Cellular) Systems on
– The list of channels provided
– Scan the channels in the order in which they are listed
May Contain U.S. Export Controlled Information
PRL Technical
Cellular CDMA Preferred Acquisition Record Workshop
Section 2-20
PRL Technical
PCS CDMA Blocks and Channels Workshop
Section 2-21
Channels
CHAN Description
• The list of channels provided. PCS CDMA Channel Number as defined in 6.1.1.1 of
• Scan the channels in the order 25-1175
TIA/EIA 95-B.
in which they are listed. Priority is based on position in the CHAN list. Some of
these channels are ‘conditionally valid”
PRL Technical
PCS CDMA (Using Blocks) Acquisition Record Workshop
Section 2-22
PRL Technical
PCS CDMA (Using Channels) Acquisition Record Workshop
Section 2-23
What it means:
• Look for 1900 MHz CDMA (PCS) Systems ONLY on:
– The list of channels provided
– Scan the channels in the order in which they are listed
– An editor will generally show a meaningful descriptive term for the acquisition type,
as in the example, where it is shown as “CDMA PCS (Channel);” however, in the
standards this is described by the “ACQ_TYPE” field having the actual value “6” to
represent CDMA PCS (using Channels).
z Channels
– This channel fields in the editor describe the channels to be searched within the 1900
MHz PCS bands. This channel field is known as the “CHAN” field in the standards.
There can be from 1 to 31 channels specified in one acquisition record. The table
above shows the channel values that can be used in the PCS CDMA using Channels
acquisition record.
– The standards describe the NUM_CHANS field, which also indicates how many
channels are in this record (1 to 31). Normally, if an editor or some equivalent tool is
used then the tool would calculate and maintain this as part of its housekeeping.
PRL Technical
System Table Workshop
Section 2-24
System Table
The system table contains the descriptions of all the systems permitted to provide service or prohibited from providing service.
Each system is described in a system record. The system table consists of a minimum of one and up to 16,383 system records; the
actual number may be subject to the physical amount of storage available on the device. Each system record describes one or
more CDMA systems that are permitted or prohibited.
In the context of the PRL a system is identified by a broadcast identity ([System Identification, Network Identification] or
[Mobile Country Code, Mobile Network Code]) and the frequency band on which the system was found. System records are
explicitly grouped together. Groups of systems are termed Geographical Areas. Permitted (or preferred) systems can be assigned a
priority. Priority ordering in the system table is explicit, unlike the implicit priority ordering of the records in the acquisition table.
Priority ordering only has scope and relevance within the Geographical Area groups.
System Type and System Record Type
In defining system records, a PRL editor often allows the specification of a system type. The system type in the PRL editor is in
descriptive form (“1X/IS-95,” “HRPD/IS-856” for 1xEV-DO, etc.). The system type would generally translate to a system record
type.
One thing to be aware of here is that system record types did not exist prior to IS-683-C when a new form of system record was
introduced, known as the extended system record format. The extended system record format enabled the PRL description of
systems with different sets of attributes than those used to describe the basic 1X/IS-95 systems. The first such system to be
defined as a new type was the high rate packet data system (1xEV-DO). Prior to this, all system records were of the same type,
which is referred to in this document as the Basic System Record. Often when people talk of the extended PRL, they are referring
to the extended record formats that are offered in IS-683C. With the increasing presence of 1xEV-DO systems the use of extended
system record format is becoming more common.
With the new extended system record format it became possible to identify a type of system record as an explicit field. A basic
system record of IS-683 A and B can be expressed in a the extended system record format using a Type=0. A stored variable in
the mobile device indicates which type of PRL that the device can support. This variable is called SSPR_P_REV. An
SSPR_P_REV value of “1” indicates that the only the basic record formats can be supported. An SSPR_P_REV of “3” indicates
support of an Extended Preferred Roaming List containing Extended System Records.
PRL Technical
System Table Record Workshop
Section 2-25
0 TO 32767
0 SIGNIFIES WILDCARD = ANY SID
Actual System Table Record NID_INCL Description
’00’ NID not included assume 65535
System Record Field Length (bits) ’01’ NID included
’10’ NID not included, assume 0
SID 15 ’11’ Reserved
NID_INCL 2 0 TO 65535
65535 SIGNIFIES WILDCARD = ANY NID
NID 0 OR 16
PREF_NEG Description
PREF_NEG 1 ‘0’ NEGATIVE - Prohibited system
GEO 1 ‘1’ PREFERRED – Permitted system
PRI 0 OR 1 GEO Description
‘0’ NEW Geographic area relative to previous entry
ACQ_INDEX 9
‘1’ SAME geographic area as the previous entry
ROAM_IND 0 OR 8
PRI Description
‘0’ SAME Priority as the FOLLOWING Entry
‘1’ MORE preferred than the FOLLOWING Entry
In an editor this is normally seen as “SAME” and “NEW” as opposed to “1” and “0." The
important aspect of the GEO flag is that it is a relative description with respect to the previous
system table entry; i.e., a GEO is either the “SAME” as the previous or it is not the same as the
previous in which case it is “NEW”—another GEO.
Negative/Preferred
This field is set to ‘1’ if the mobile station is allowed to operate on the system associated with
this record. This field is set to ‘0’ if the mobile station is not allowed to operate on the system
associated with this record.
Priority
Only a preferred system can have priority, negative systems are all equally disliked and equally
prohibited, so if the PREF_NEG field of this system record is equal to ‘0’ then this field is
omitted. Preferred systems on the other hand can be declared in preference order, and indeed
systems can share the same level of preference. The declaration of preference is the implicit
instruction to the handset’s system selection function that it must try and always reach the most-
preferred system.
The priority field is a relative description with respect to the next system table entry; i.e., priority
is either the “SAME” as the next or it is “MORE” than the next record. Since priority only has
relevance within the context of a GEO, the last preferred system record in a GEO, or if the next
record describes a prohibited system, this field has no meaning and is set to ‘0.’
If the system associated with this system record is more desirable than the system associated with
the next system record, this field is set to ‘1.’ If the system described by this system record is as
desirable as the next described system, i.e., it has the same priority, then this field is set to ‘0.’
The important thing to remember here is that unlike the GEO, the priority setting of a system
record affects the subsequent record.
Acquisition Index
This field is set to the index of the acquisition record that specifies the acquisition parameters for
the system associated with this record. Note: The index of the nth acquisition record is n-1. For
example, the index of the first acquisition record in ACQ_TABLE is 0, and the index for the
fourth acquisition record is 3.
Roam Indicator
Only a preferred (or available) system will display a roaming indicator. Negative systems will
not be able to provide service, hence, for those systems, this field is omitted.
PRL Technical
Size Matters Workshop
Section 2-27
ACQ_INDEX
PREF_NEG
ROAM_IND
NID_INCL
Size 5.00
GEO
NID
SID
PRI
W ith (bits) 4.50
0
15
50
1
15
30
45
60
90
Min S ize Bits per extra M ax num extra Max S ize
Acquisition Record Type Number of SIDs
Bits Elem ent elem en ts (bits)
Analog 6 - - 6
C DM A Standard 8 - - 8
CDM A P referred 8 - - 8
P CS (Blo ck) 10 3 5 25
PRL Technical
Introduction to PRL – Section Review Workshop
Section 2-28
Review
1. Systems are identified using SID/NID (enhanced PRLs may also use MCC/MNC as described later).
2. Systems are defined using system records in the system table.
3. Systems are logically grouped together using GEOs (Geographic Areas) in the PRL.
4. Information contained in a system record includes:
z System ID (SID/NID, MCC/MNC)
z System type
z System priority within the GEO
z Whether the system is Preferred or Negative
z Roaming indicator
z Index to an acquisition record
5. The acquisition table defines candidate frequencies/channels that should be scanned, and in what
order. By identifying only channels that should be scanned, rather than all possible channels,
acquisition time is improved.
6. Each of the following may be prioritized in the PRL:
z System records within a GEO (explicitly via the priority field in the system record)
z Acquisition records within the acquisition table (implicitly prioritized—top to bottom)
z Channels within the acquisition record (implicitly prioritized—left to right)
11. What are the two modes in which a PRL can operate?
12. What are two ways an acquisition record can define which
CDMA PCS channels to scan?
7. Yes, a device may operate without a PRL, but only on the standard channels of Band Classes 0 and 1. The
standard channels for Band Class 0 are defined in a handset’s NV-RAM. In the U.S., these are typically set to
the preferred set of channels defined in IS-2000 (i.e., 283 for primary A, 384 primary B, 691 secondary A, and
777 secondary B). Band class 1 standard channels are predefined.
8. The PRL resides either in NV-RAM (non RUIM-equipped devices) or on the RUIM.
z Over the air using OTASP (i.e., user dials an OTASP feature code such as *228)
11. PRLs may operate in closed/restrictive mode (i.e., Preferred_Only = True) or open/permissive mode
(Preferred_Only = False). Closed PRLs will only acquire systems defined in the system table, while open PRLs
may acquire any available system if none of the systems in the systems table are found.
12. Acquisition records can define which CDMA PCS channels to scan by either:
z Using a PCS CDMA using Blocks record type and listing blocks of channels. Using this method, all
channel numbers associated with each block that is listed will be placed in the scan list. The preferred
channels of PCS CDMA blocks are defined in 3GPP2 C.S0057.
z Using a PCS CDMA using Channels record type and listing each channel number. Using this method,
each channel number to be placed in the scan list must be explicitly listed in the acquisition record.
Comments/Notes
SECTION
Notes
PRL Technical
Section Learning Objectives Workshop
Section 3-2
Notes
PRL Technical
System Determination Workshop
Section 3-3
System Determination
System selection is the process the device uses to attempt to:
z Identify the best system for a given mobile device to operate based on the device configuration and the conditions at the
location.
z Acquire the best system as quickly as possible.
For a given set of input stimuli the output of any CDMA System Determination (SD) is:
z Try to acquire a specific system
z Stay and operate on the currently acquired system
z Enter power save mode
SD uses the information in various external factors to achieve this; these factors being:
z Static, programmable information such as a list of preferred and forbidden systems, a list of radio access technologies
z Dynamic information such as the system ID broadcast by available CDMA systems, the RF conditions and protocols in
use on available CDMA systems
z User activity
Performing these tasks can be complicated by the need to support multiple radio access technologies, in a single device, to enable
coexistence of technologies such as AMPS or GSM together with CDMA. Roaming agreements between operators can lead to
complexity in the preference order of systems in the PRL. Often, operators have their own specific system selection requirements;
which can evolve with the technology and their networks. Operator specific requirements arise for a number of reasons (to
overcome network limitations, to support new features, to enforce a desired behavior) but the result is that there are various forms
of system determination in deployed handsets. Any description here is a general guideline.
For devices using the Preferred Roaming List, the PRL provides the data upon which system determination operates. SD can be
understood to have two distinct stages:
z System scanning to find a system, and then,
z Applying system selection criteria to the system that has been found.
Although in reality the two functions are very closely coupled, for the purposes of explanation, each will be described separately.
PRL Technical
System Preferences Workshop
Section 3-4
• Band preference
– Desired bands
• Roaming preference
– Desired roaming value (e.g., home-only)
PRL Technical
System Preferences (continued) Workshop
Section 3-5
PRL Technical
System Scanning Workshop
Section 3-6
System Scanning
The mobile device and the network have a symbiotic and yet fickle relationship. A mobile device
is always in search of a network to which it can attach. All the CDMA and analog networks can
potentially provide that attachment. One of the device’s primary functions is not just to find an
attachment, but to find the attachment that suits it best at that moment.
Of course the network can also be a picky partner and reject the attachment advances of the
mobile device. The PRL is the mobile device’s little black book of networks it can call upon for
attachment and, furthermore, which attachments are considered ‘best’ and better than others.
Each network is on a particular channel within a particular band (Band Class and channel) and
each server has a particular identity (SID/NID).
In the world of commercial mobile networks there are many systems available to choose from
operating on different frequencies and channels. A commercial mobile device, by design, is
capable of operating on potentially many different channels and frequencies; it must, therefore,
search some or all of the channels that may be able to provide service.
Candidate channels that may provide service are indicated to the mobile, primarily through the
descriptions contained in the Acquisition Table of the PRL. The mobile device has to translate
this table into a at a list of channels to search—known as a scan list.
System Determination has the responsibility to build the channels to scan and then search those
channels for service.
PRL Technical
Acquisition Table Expansions Workshop
Section 3-7
PRL Technical
About Guard Band Channels Workshop
Section 3-8
Invalid Channels
While this may not be a rule, a cautionary note here is that for Band Class 0 (800 MHz),
scanning some implementations of system determination may enforce the U.S. guard-bands as
being invalid CDMA channels. (See Table 15-1 for a description of channels and valid CDMA
bands within Band Classes 0 and 1.) This can be significant in building PRLs to roam in CDMA
regions where channels usage may not necessarily conform to the North American standard
primary and secondary definitions (e.g., Korea and India). The guard band channels for Band
Class 0 are shown.
In many implementations this may not be a factor. Which channels, if any, are considered invalid
should be checked with the device manufacturer.
PRL Technical
Most Recently Used Table Workshop
Section 3-9
MRU Table
• A device stores the list of (typically) 12 systems
on which it has most recently operated.
PRL Technical
Scan Lists Workshop
Section 3-10
Scan Lists
• The list of CDMA channels the device searches
for service.
PRL Technical
Normal and Better Service Scan Lists Workshop
Section 3-11
PRL Technical
System Lost Scan List Workshop
Section 3-12
Time
1 2 3 4
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
PRL Technical
How Long is a Scan? Workshop
Section 3-13
PRL Technical
System Selection Workshop
Section 3-14
System Selection
Once a system is detected by the scanning process, the only thing that has been determined is
that a CDMA or analog system has been found. As yet, no selection criteria have been applied to
fulfill the goal of system determination, i.e., find the best system to provide service.
This second stage of is often referred to as the system selection process. It is during this stage
that priorities and preferences are applied. Remember that exactly when system determination is
invoked, even how it is performed, is not standardized. Nonetheless, the general behavior is well
understood and it is still possible to describe the typical events that may cause system
determination to happen. Some of these are caused by the mobile and some of these are caused
by the network.
In earlier discussions the selection process was left as a generic statement of apply selection
criteria. In this section the aspects of system selection process are considered. Shown is a generic
example of the elements that all CDMA system selection processes must exhibit.
The diagram also shows the typical stages at which the PRL and device settings are used in the
system determination process.
PRL Technical
System Types Workshop
Section 3-15
A system defined in the PRL for which the Neg/Pref field is set
Negative
to “Negative.”
Notes
PRL Technical
When System Selection Occurs Workshop
Section 3-16
• After a call
• System lost
z Less Preferred Service. Service from any system that is not the “Most Preferred” generally
causes the device to attempt to obtain service on the system that the PRL has declared as
the Most Preferred. This is often referred to as [Better Service] System Reselection.
z Call Termination Reacquisition. After a call, upon release of the traffic channel, the
mobile will begin to look for the system again.
z System Lost. When the mobile detects that it has lost the signal of its serving system, it
generally begins to search for service again.
PRL Technical
Types of System Selection Workshop
Section 3-17
Initial Acquisition
When the mobile is powered on, it performs initial acquisition and attempts to acquire a system on the channels of
the normal scan list, starting from the top. If a system is acquired that is not listed in the PRL, then that system is
recorded as an available system (on an available systems list) and scanning progresses to the next entry in the scan
list . If a system is acquired that is listed in the PRL’s system table and is the most desirable system in that specific
GEO, then service is provided on that system and all scanning stops until the system is lost. An acquired system that
is listed in the PRL (system table) that it is not the most desirable system in the GEO will cause the device to search
using the better service scan list.
Better Service Reselection
When the mobile device ends up providing service on a “less-preferred” system[1] (which is any system that is not
the most preferred), “Better Service Reselection” occurs (often simply referred to as reselection). This is the
implementation of a policy something like “OK, stay here for now but keep trying to get to a more preferred system
until operating on the most preferred system.” This continues until the most desirable system in the GEO is acquired
or the system is lost. The device implements this policy by use of a reselection timer, reselection period, better
system scan list, and better service scan.
Call Termination Reacquisition
Upon entering idle state, following a call release, a CDMA device normally performs a reselection, often referred to
as call termination reacquisition. This reselection is performed a fixed amount of time (typically 4 seconds) after the
end of a call when the mobile is not on the most preferred system.
System Lost
When a mobile device declares it has lost a system, it invokes its system lost reselection policy. The device
implements this policy by use of a system loss reacquisition schedule, system loss scan list, and system loss service
scan. The system loss reselection is similar to the better service reselection except for the earlier noted changes in
how the scan list is constructed. The “schedule” of attempts to reselect the system that has just been lost is set and
driven by the construction of the system lost scan list. As in better service reselection, if a system is acquired and it
is less-preferred, then better service reselection will be performed. Often the system determination will search
through the GEO first. The signal level that a mobile device declares it loses a system is implementation dependent.
A CDMA system is normally unusable an at Ec/Io of -16 dB or lower.
PRL Technical
Applying Priorities in Selecting a System Workshop
Section 3-19
Roaming Preferences
Earlier in this section we noted that the roaming preference can affect system selection. The
roaming preference setting can be a system table filter that reduces the systems available for
selection. If the roaming preference has a setting of “Home Only” then any system in the system
table with a roaming indicator other than “Roaming Indicator Off” becomes an unavailable for
selection. If the device has a populated “Home SID/NID list,” then, any systems listed become
identified as selectable non-roaming systems. Use of this list with a PRL has the following side
effects:
z Systems in the list that are not in the PRL enter the selectable set regardless of the
PREF_ONLY setting in the PRL properties.
z Systems in the list that are listed in the PRL as roaming systems become selectable as non-
roaming systems.
z Systems in the list that are listed in the PRL as negative systems shed their barred status
and become selectable.
The “Home SID/NID list” is a legacy from the days prior to PRLs and is typically not used in
conjunction with a PRL.
SID/NID Lockout List
This list is effectively a system table filter. Any system listed becomes unavailable for selection.
Use of this list with a PRL has the following side effects:
z Systems that are listed in the PRL are barred from selection regardless of their description
in the PRL.
z Systems that are not in the PRL are barred from selection as an available system regardless
of the PREF_ONLY setting in the PRL properties.
The “SID/NID Lockout list” is a legacy from prior to PRLs and is typically not used in
conjunction with a PRL.
PRL Technical
Applying Priority Workshop
Section 3-21
Priority
• Priority is the factor for system selection within a GEO.
• It is the indicator of whether a system is most preferred or not.
• Scope of priority is limited to within the GEO.
• The prime objective of system selection is to get to the most preferred
system.
• The same priority can be applied to multiple systems.
• When systems have the same priority they are all equally selectable as
the others.
• Priority alone may not be enough, such as:
– Two systems have the same preference and different roaming indications.
– Selection would require selection between two GEOs.
Priority
Priority is normally the primary distinguishing factor for system selection within a GEO and is the major indicator of
whether a system is most preferred or not. Remember that the scope of priority is limited to within the GEO. The
prime objective of system selection is to get to the most preferred system.
Each system record does not require a unique priority; the same priority can be applied to multiple systems. When
systems have the same priority they are all share level in the pecking order of systems. This means that situations
arise where priority does not distinguish between systems. In most cases this is perfectly fine and means that any one
is as equally selectable as the other. However, there are situations where priority alone may not be enough, such as:
z Two systems have the same preference and different roaming indications.
z Selection would require selection between two GEOs.
Equal Priority, Different Roaming Indicator
Where two systems in the same GEO are compared and the only discernable difference is the roaming indicator,
then, in general, a system will be more preferred if it is not roaming.
Geo Changes and System Selection
In the situation where the acquired system and the current serving system are listed in different GEOs, there are
normally some rules to follow to ensure that the “best system” is used. Some typical rules are:
z In the case where only one of the systems is listed in the PRL, then the PRL system would normally be
preferred.
z Where both systems are listed in different GEOs and the roaming indicators are different, then typically
“roaming indicator off” would be preferred over “roaming indicator on” or “roaming indicator flashing;” and
“roaming indicator on” would be preferred over “roaming indicator flashing.”
z When one of the systems is of a higher preference order in its GEO, then it would probably be preferred over
the other.
z All other things being equal, the system operating on the channel that appears first in the acquisition table
may be preferred.
z If one system is CDMA and the other is AMPS, typically the CDMA system would be preferred over AMPS.
PRL Technical
Multi-GEO SIDs Workshop
Section 3-22
PRL Technical
Available System and “Open” PRLs Workshop
Section 3-23
PRL Technical
Understanding Reselection Workshop
Section 3-24
PRL Technical
SID, NID, or Band Class Change Workshop
Section 3-26
– Idle Handoff
– Redirection
The management of the recent channel list is implementation dependent, but typically the band and channel from
which the device acquired the CDMA Sync channel is placed in the recent channel list. During idle operation, if the
channel changes, the new channel is placed in the recent channel list, provided that the band and channel is in the
acquisition table and the device is not operating on an available system.
Questions often arise on behavior when any changes that occur in the SID, NID, or the Band Class change while in
idle mode. There are two aspects to consider here:
z What gets recorded in the Recent Channel List or MRU?
z How is the PRL involved?
In some implementations a change alone in the Band Class may cause no update to the recent channel list, while in
others the new Band Class and channel is placed in MRU, regardless of PRL matching. Typically, any change in any
one of the SID, NID, or the Band Class would re-invoke system selection using the PRL. If the newly encountered
system is not the most preferred, better service reselection would be performed. There are various network
conditions or messages where a SID, NID, or Band Class may occur which are discussed below. However, it should
be noted that these messages more often occur without any change in any of these three items. Some of the situations
where a SID, NID, or Band Class change can be detected by the mobile are:
z Channel List Message
z Idle Handoff
z Hand Off Direction
z Extended Channel Assignment Message
z Redirection
PRL Technical
Avoidance of Unusable Systems Workshop
Section 3-28
PRL Technical
No Selectable System Workshop
Section 3-29
No Selectable System
If the scan list is exhausted and service cannot be provided, system selection behavior is
implementation dependent (and may be specified by the operator in their handset requirements).
Typically, system determination will reset the scan list and start scanning again. If no service is
found after scanning for a period of time (10-15 minutes), the device enters power save mode. A
mobile device will exit power save mode periodically to search for service again.
The figure shows a simplified timeline of the selection behavior, when no service is found. Some
points to bear in mind:
z The length of time of the initial search period is implementation dependent.
z The length of time the mobile sleeps between searches may lengthen by some expansion
factor as subsequent searches do not find service. Any increasing sleep window behavior
and the expansion factor is implementation dependent.
z The length of time the mobile searches during wake up times may decrease by some
compression factor as subsequent searches fail to find service. Any decreasing search
window behavior and the compression factor is implementation dependent.
z Often any user intervention, such as a key press, can reset the power save cycle and
recommence with the search window reset to the initial search time.
Some or all of these behaviors may in fact be included in an operators’ handsets specification.
Review
1. System determination is the process of attempting to, as quickly as possible, identify and acquire the best system
upon which to operate.
2. Three preference settings that can affect system determination are:
z Mode Preference (e.g., CDMA only)
z Band Preference (e.g., Band class 1 only)
z Roaming Preference (e.g., home only)
3. A device can prevent a system from being acquired by:
z Including it in the SID/NID Lockout List
z Identifying it as negative (i.e., not preferred) in the PRL system table
Identifying systems as negative in the PRL is preferable because it allows control over system selection to
remain within the PRL. Using a SID/NID Lockout List essentially complicates system selection by introducing a
separate mechanism outside of the PRL to do what the PRL is capable of doing natively.
4. Home systems can be identified by:
z Including them in the Home SID/NID List
z Identifying them as non- roaming systems (e.g., Roam_Ind = OFF) in the PRL system table
Using the roaming indicator in the PRL is preferable because, as with the previous question, it allows control
over system selection to remain within the PRL.
5. When less preferred systems are acquired, devices periodically perform reselection in an attempt to find a more
preferred system. This results in less battery life and potential missed pages during reselection attempts.
6. What are scan lists and how do they relate to the PRL?
6. A scan list is a list of candidate channels used by the device to search for service. Scan lists are dynamically
built using PRL information, the Most Recently Used (MRU) table, and system preferences.
7. The three types of scan lists are:
z Normal Scan List – used for initial acquisition (i.e., during power up)
z Better Service Reselection (a.k.a. Alternate) Scan List – used to look for a more preferred system
z System Lost Scan List – used when an acquired system is lost
8. A composite GEO is a combination of multiple GEOs. When a SID appears in more than one GEO (i.e., a
multi-GEO SID), a composite GEO is created that combines of all GEOs containing that SID. This composite
GEO is used to build the more preferred list for Better Service Reselection.
9. Because SID 99 is a multi-GEO SID that exists in both GEOs 1 and 2, a composite GEO comprising SIDs in
both GEOs is formed with priorities that pivot around SID 99 as shown below:
z SID 70, priority 1
z SID 10, priority 2
z SID 80, priority 2
z SID 99, priority 3
Once selected, the priorities relative to the selected SID would be used to determine whether to reselect again.
For example, if SID 10 is selected, no further reselection would be performed because it is most preferred in
GEO 1. However, if SID 80 were selected, the handset would continue to look for a more preferred system,
because it is not most preferred in GEO 2.
10. Preferred systems are defined in the PRL. Available system are not. Available systems only occur with open
PRLs (i.e., Preferred_Only = False). If the PRL is open and no preferred systems can be located, other systems
identified during scanning are considered available.
Comments/Notes
PRL Technical
Section 4: PRL Process Workshop
Section 4-1
SECTION
4 PRL Process
Notes
PRL Technical
Section Learning Objectives Workshop
Section 4-2
Notes
PRL Technical
Why is a PRL Process Necessary? Workshop
Section 4-3
PRL Technical
PRL Data Source Management Workshop
Section 4-4
Roaming Partner
Derived sources
May Contain U.S. Export Controlled Information
PRL Technical
Change Identification Analysis Workshop
Section 4-5
Source Released
Data Data
Change Analysis
PRL Technical
PRL Production Workshop
Section 4-6
Change Details
Source Released
Data Data
Production
Pre-release
Data
PRL Production
Ideally, when beginning production of a PRL, all source data is known and current, and changes that affect a PRL are identified.
However, the following constraints can affect how a PRL is designed:
z Physical storage space available in a particular device. Storage space available for a PRL can range from 1 KB to more than
6 KB. Common limits are 1K, 3K, 4K, 6K, and 8K.
z As a result of the size constraint or otherwise, PRLs may be separated by regional, national, and international
categorization.
z Staff availability to manage multiple options. While there may be many novel ways to design PRLs, in the real world
operators have very real constraints on the resources available to produce and maintain them.
z Other process element constraints. For example, in the testing phase: resources available to test multiple PRLs. In the
distribution phase: the number of PRLs that can be distributed by the OTA systems.
PRL production may face these constraints; however, it should always use solid design and implementation practices, backed up
with a reliable record keeping system. These core elements directly relate to how maintainable and traceable PRLs are. For
example, they should address how the PRL_ID property is populated, and should provide sufficient information to yield the full
configuration trail of the PRL.
When produced without a solid and traceable process, a PRL becomes exponentially more expensive to revise. If the PRL design
is not documented, design decisions can be lost and errors (previously designed out) can creep back in, causing extra production
iterations.
The expense of an error in the PRL is directly related to the stage at which the error is detected. If the PRL is already widely
distributed, there is an inherent reluctance to modify it. This reluctance increases as staff turnover occurs, and, in the absence of
documented design, some of the learned “black art” is lost and those lessons have to be relearned. This anxiety can only be
mollified by the presence (and use) of solid process. At the very least, each PRL release should clearly identify any and all source
data, constraints applied, and design decisions made. This process can be as automated or as manual as the operator desires, as
long as it captures the aforementioned essential elements.
PRL Technical
PRL Testing Workshop
Section 4-7
Production
Internal Testing
• Own network test facility
• Partner’s network test facility
Field Testing
• Home Market Field Testing
• Home Country Field Testing
• Foreign Country Field Testing
Test Equipment
• Ensuring all variants of PRL and system determination are covered
May Contain U.S. Export Controlled Information
PRL Testing
In PRLs, as with most things, the earlier an error is discovered, the easier it is to address.
However, because a PRL is describing so many different radio environments and serving systems
(both local and remote), the number of test traces tends to be high and the configuration of a test
harness is not as straightforward as it might be for some other test scenarios.
Testing rigor generally depends on the time and resources available. Various forms of testing can
be applied, both with a PRL in a standalone environment without a handset (off-target testing)
and with a PRL loaded into a handset that is then placed in a real RF environment (on-target
testing).
On-target testing can take various forms. If an operator has access to a network test facility, radio
environments can be simulated and a device loaded with the pre-release PRL. If no such facility
exists, in-market testing can be performed. Since this is the most expensive form of testing,
fraught with coordination difficulties, it tends to test only a selective subset of the PRL. These in-
market tests can include:
z Home market field testing
z Home country field testing
z Foreign country field testing
PRL testing is addressed later in this workshop, including various types of testing and some
sample tests that can be performed.
PRL Technical
Release and Distribution Workshop
Section 4-8
Release Products
• New PRLs
• New TDS
• Release Numbers
After a pre-release production PRL is successfully tested, it is generally given the seal of approval and elevated to a
status of “released.”
Often the group that builds a PRL to include roaming partners is also responsible for releasing their own network
information to roaming partners. The release products of such a group include the following:
z New PRLs
z New Technical Data Sheets (TDS)
For any release, it is important to include a product identity (i.e., identifying what is being released), such as a date
or release numbers:
z PRL list ID – allows a label to be placed in the PRL to identify which release product it is.
z TDS information – often uses a document number or the release date in the title and the TDS itself to
identify the release number.
The release of a new TDS can be the result of diverse activities across a network such as core network changes, SID
consolidation, network build-out, technology upgrades, etc. All of these can directly affect roaming partners and
must be communicated in a timely manner.
Not all TDS changes require partners to change their PRL (i.e., no effect on inbound roaming access) but core
network changes such as line ranges, point codes, switch IDs, or Temporary Local Directory Number (TLDN)
ranges can have a dramatic effect on outbound roaming and negatively affect the ability of inbound roamers to
receive calls.
PRL Technical
PRL Distribution Workshop
Section 4-9
Non-Customer In Service
Targets Targets
Non-Customer Targets
• Electronic file transfer to distribution hubs
• Physical file transfer to distribution hubs
In-Service Targets
• Notification and user-initiated OTASP
• Network initiated OTAPA
• Notification and service center upgrade
PRL Technical
PRL Distribution – Non-Customer Targets Workshop
Section 4-10
Non-Customer In Service
Targets Targets
Non-Customer Targets
Non-customer targets can be internal distribution hubs. In these cases, the PRL will be released
with a specific date and/or action time from which it will be placed in-service. Examples of these
distribution hubs include:
z OTASP platforms
z Roaming partner test groups (for any previously distributed handsets and/or R-UIMs).
If inventory must also be updated and the OTASP platforms cannot be used for this purpose,
other hubs may require the release, including the following:
z Retail outlet inventory
z Warehoused inventory
z Handset manufacturers
z Customer service centers
PRL Technical
Distribution – In-Service Targets Workshop
Section 4-11
Non-Customer In Service
Targets Targets
Changes may not affect all in-service PRLs. Distribution can be prioritized by:
• PRL ID
• Device Type
• Customer Service Area
• User (MIN/ESN)
PRL Technical
PRL Process Timeline Workshop
Section 4-12
• Timeline is well
communicated. Source
Distribution
Data
Process Timeline
For a smooth PRL process, make sure to communicate the timeline to all interested parties. The
process cycle must be short enough to propagate important changes as soon as possible, yet long
enough to ensure a timely and successful PRL release.
Often carriers find that production can be done fairly quickly but coordinating test resources
takes more time, especially for field testing and verification.
The slide shows an example process that results in a PRL release on a quarterly cycle. All stages
up to and including internal test take four weeks; the field test stage takes an additional four to
six weeks. The release and distribution phases are really a function of the number of affected
handsets and the capabilities in the network to distribute the PRLs.
Another major factor in the process may be the number of discrete PRLs being managed. If there
are many PRLs (due to device, calling plan, technology or other specific constraints), then every
PRL may not be updated at every cycle.
The best PRL process is the one that works to achieve the best available quality with the
resources available. Resource constraints may mean that, although the PRL cycle runs quarterly,
only half the PRLs are part of any one cycle; which may result in a six-monthly update cycle
(subject to the compromises discussed earlier).
PRL Technical
PRL Process – Section Review Workshop
Section 4-13
Review
1. Poorly designed PRLs may cause customers to perceive the network as having poor coverage or
unreliable service.
2. The stages of the PRL process are:
z Source Data Management
z Change Analysis
z Production
z Testing
z Release
z Distribution
3. Key considerations when analyzing changes to source data include:
z Do the changes affect any released or in-development PRLs?
Comments/Notes
PRL Technical
Section 5: PRL Design Workshop
Section 5-1
SECTION
5 PRL Design
Notes
PRL Technical
Section Learning Objectives Workshop
Section 5-2
Notes
PRL Technical
PRL Constraints Workshop
Section 5-3
PRL Constraints
• Policy constraints:
– Implementation guidelines and strategy for their PRL.
• Device constraints:
– The mobile device landscape for which PRLs must be designed
and delivered.
PRL Production
This section begins with a discussion on understanding the constraints within which a PRL can
be produced. This is likely one of the most important aspects of PRL design and production.
PRLs require design, and this design often must be performed within a set of constraints.
PRL Constraints
Normally, anything that requires design means that some design decisions have to made. Design
decisions are often subject to some real world constraints. The design of a PRL is no different.
There are two major constraint areas that PRL designers need to understand before beginning
any work:
z Policy constraints
z Device constraints
Policy constraints are the guidelines set in place whereby the operator defines the
implementation guidelines and strategy for their PRL. Policy constraints not only define how
PRL Properties will be set but also structure the coverage plan to be implemented by the
designer.
Device constraints are a way of expressing the mobile device landscape for which PRLs must be
designed and delivered.
PRL Technical
Device Constraints Workshop
Section 5-4
Device Constraints
In CDMA no two devices are ever created equal and often different devices can support different features. While there are many
aspects of a device that can characterize it, this section is concerned only with those that relate to the PRL or its use. Device
constraints may be categorized as:
z Band Class (frequency) constraints
z System technology constraints
z Software version capability constraints
z Physical memory constraints
Band Class Support
Some devices are single band and support only one Band Class, for example, 0, 1, 5, etc. Others are dual band and can support
both Band Class 0 and 1. Generally this should not become a constraint because system selection software normally ignores any
acquisition records for a Band Class that it does not support (subject to any limitations on invalid channels—see below).
However, this may be a chosen constraint to help mitigate other constraints, such as memory map limitations.
Invalid Channels
Some mobile devices may consider the U.S. guard-bands as invalid CDMA channels. Some carriers outside the U.S. may offer
service in these channels and list them in their Technical Data Sheets. It is important to understand any device’s behavior when a
channel that is considered invalid is present in the PRL. In some cases, the behavior may require that no invalid channels be
permitted in the PRL of a particular device.
Technology Support
Not all devices have support for AMPS analog cellular service. Some CDMA devices may not support all CDMA services. Some
older devices may not support 1X/IS-95 and only be capable of IS-95, although these are becoming less common. Other CDMA
devices that do support 1X/IS-95 may not support packet data services. Devices such as PC data cards may not have voice service
support. 1xEV-DO PC data cards may be data only, while 1xEV-DO handset devices support voice and data.
The constraining factors here are the supported PRL version and the presence of acquisition and system record entries that are
unusable by the device. This constraint normally becomes a factor only when it is used to alleviate memory map constraints.
PRL Technical
Device Constraints (continued) Workshop
Section 5-5
D e v ic e M o d e l B a n d -c la s s T e c h n o lo g y
M e m o ry
1x In v a lid C h a n n e ls
M a n u fa c tu re r M odel # SW Ver 0 1 AMPS DO M a p -P R L .
V o ic e D a ta
PRL Technical
Some Potential Device Constraints Workshop
Section 5-6
• Generic
Device Type 1 • Band Class 0 only
• CDMA only, No Analog
• Generic
Device Type 2 • Dual Band, Band Class 0, and Band Class 1
• CDMA only, No Analog
• Specific Manufacturer devices only
Device Type 3 • Band Class 0 only
• CDMA only, No Analog
• Multi-Mode CDMA/GSM
Other Device • 1X Data Cards – data only service
Types to
• EV-DO Data Cards – data only service
consider
• EV-DO Handsets – voice and Data
Notes
PRL Technical
Policy Constraints Workshop
Section 5-7
Policy Constraints
Policy constraints are guidelines an operator chooses to enforce across all PRL development. These
policies can be as basic as the PRL properties to the implementation of the coverage plan and application
of preferences accordingly to the policy on addressing other (device) constraints.
PRL Properties Policy
The PRL properties that must be defined are the PRL preference type and the PRL identity. The PRL
preference type determines whether or not the handset is permitted to use systems other than those
described by the PRL.
In all cases, the PRL is network configuration data that happens to be distributed in the handset. As such, it
must be identifiable for the purposes of version control and troubleshooting. It is normal for a naming
policy to be in place to structure the PRL ID for this purpose. Generally, a policy on numbering is
implemented. Whether a PRL is open or closed varies from operator to operator.
Support System Constraints
PRL distribution is an important factor in any network. Where automatic distribution over-the-air is
deployed, this functionality is delivered by a number of operational support systems in the network
infrastructure. Depending on the OTA system implementations or some other related system issues,
constraints can be imposed, which can include the following:
z Size limitations on the PRLs managed by the platforms
PRL Technical
Mitigation Constraints Workshop
Section 5-8
Mitigation Constraints
Mitigation constraints can be understood to be those policies designed and established to directly
mitigate or work around particular device or network constraints, such as hard memory
limitations. The following are examples of mitigation constraints:
z Single PRL support – A constraint usually imposed to mitigate the limitations of available
resources or support system capabilities. It means that an operator chooses to implement a
single PRL for all devices—and that PRL must be compatible with all devices.
z Maximum size limit on PRL – A constraint imposed to mitigate the situation of limited
memory map allocation for PRLs. Often, an operator has multiple deployed devices that
have varying memory capacity for PRL. The operator may choose to limit the maximum
size of the PRL to a lowest common denominator size.
z Global Segmentation of Roaming Markets – Another way to mitigate the available PRL
memory constraint but can only be supported if there is no single PRL constraint in effect.
This effectively creates a number of PRLs of home plus a subset of roaming partners. The
subset is defined by region, such as SE Asia, Americas, etc.
z Number of Roaming Partners – Another way to mitigate the Available PRL Memory
constraint is to impose a constraint that limits the number of roaming partners that can be
included in a PRL.
z Support System Constraints – Imposing limitations on the size and number of PRLs or on
how many device variants can be supported may be a way of mitigating the constraints of
the support systems in place that are used to manage and distribute PRLs.
PRL Technical
Coverage Plan Workshop
Section 5-9
Coverage Plan
The PRL is, above all else, the implementation of the coverage plan of the operator. The
coverage plan describes the following:
z Roaming partners
z Areas where coverage is available
z Technologies available in those areas
z Where multiple partners exist in an area, the relative preferences (priority) of those
operators’ networks
PRL production depends on having access to this information to design GEOs appropriately and
place system records in the system table correctly.
PRL Technical
Coverage Plan in the PRL Workshop
Section 5-10
PRL Technical
Partner Priority in the PRL Workshop
Section 5-11
Type of Preference
Priority Preference based on Roaming Partner • Each partner has a different priority
• Ordering is important
Roaming Partners all Equally Preferred • All partners have equal preference
• Ordering is not important
Varying Preferences across GEOs
Priority Preference based on Technology
Preferential treatment based on services offered
PRL Technical
Policy Constraints – PRL Structure Workshop
Section 5-12
Use of Wildcards
PRL policy should define if SID wildcards are permitted in a PRL and under what circumstances; also, if NIDs are to be used in
the PRL for system selection. The use of a NID costs an extra 16 bits in the system record and may affect any memory constraint.
The level of partner network detail is further increased.
Geo Definition Policy
The coverage plan does not describe how GEOs are to be defined. There may be a policy guide on GEOs definition. Minimally it
should require a description of each GEO and the rationale behind its definition. Recommendation: One GEO per country for
roaming markets.
Prohibited/Negative Systems Placement Policy
The placement of negative systems in the system table can vary. In some cases a policy can dictate that all negative systems are
placed in their own GEO or a combined GEO. Maintainability is increased if negative systems appear at the bottom of their
appropriate GEO and it also ensures that the frequencies of preferred systems of the GEO are immediately scanned.
Policy of the Use of SIDs in Multiple GEOs
Often toward the border of coverage, operators find that a SID that was least preferred in the home area becomes the most
preferred as home coverage fades and roaming partner coverage takes over. This border coverage condition causes operators to
consider use of the same SID in more than one GEO. This may mean that:
z Each instance is unique as they refer to an acquisition record of different technologies (AMPS, CDMA, etc.)
z Each instance is unique as they refer to different acquisition records of different Band Class (0, 1, etc.)
z Two or more instances are indiscernible—referred to as multi-GEO SIDs. Instances of the same SID in different GEOs
are indistinguishable when they refer to the same acquisition record, or to different records of the same Band Class.
When instances of a SID, NID pair are indiscernible, they are subject to the formation of a composite GEO. A composite GEO is
formed from the GEOs that contain the common instance, and affect subsequent system selection. This is not necessarily an
undesirable behavior. It is good to establish a policy to guide its use.
PRL Technical
Design Aspects to Consider Workshop
Section 5-13
PRL Technical
GEO Design Workshop
Section 5-14
List only systems of operators with roaming agreements. A partner of your Roaming Partner is
not necessarily your Roaming Partner, too.
Are there any coverage holes? Have all systems within the coverage been listed? For a ‘closed’
PRL (Preferred_Only=True), service is not provided on any system that is not listed in the PRL.
PRL Technical
Information for PRL Production Workshop
Section 5-15
Organization of data
• Controlling the source
– Configuration management as for any operational data
• Consider building derived sources
– Internal format of TDS for PRL
– Coverage and Preference Plan
PRL Technical
Information from a Roaming Partner Workshop
Section 5-16
Periodic verification on information to and from roaming partners can be limited to technical
data review or can include test calls and test bills.
PRL Technical
Change Analysis Workshop
Section 5-17
• Identification of change
– TDS often have an update detail note.
• Identification of affected downstream items
– Derived sources
– PRLs
• Assessment of severity of change
– Not every change is a high priority
– Treated like software fixes
– Work assessed and programmed in with other PRL activity
– PRL CYCLE
These questions, in essence, describe the functions of change analysis for the PRL process.
This requires the examination of new data to identify any impacted released data. Once the
affected PRLs are identified, the analysis should extend to figuring out the scope of the change,
and, how it should be included. There can be many factors that affect the priority of an identified
change, such as:
z Resources available to effect the change
z Revenue (or other) impacts of [not doing] the change
z Relative importance of the affected area to the customer base
z When in the PRL process new data arrives, i.e., cut-off or data-freeze dates
All of the factors discussed above are considered, then the result is described in the change
details and/or work orders for PRL production.
PRL Technical
PRL Design – System Table Workshop
Section 5-18
Notes
PRL Technical
PRL Design – Acquisition Table Workshop
Section 5-19
Notes
PRL Technical
PRL Tools – The PRL Editor Workshop
Section 5-20
PRL Editors
• As an Editor
– Often where problems occur
– Akin to writing in assembly
– Limited readability
– Limited editing facilities
Often no undo feature
Simple mistakes can cause major
rework
• As a Compiler
– Can import a text file of the
right format
– Write out the PRL in binary
format
– Source code is protected
elsewhere
May Contain U.S. Export Controlled Information
PRL Editors
Most handset manufacturers provide some form of PRL editor tool. These tools can be
problematic when large PRLs are involved. These are some of the problems that can be
encountered:
z Single Line by Line Entry
z No or limited undo functions
z Limited cut, copy, and paste
z Nowhere to add additional information such as carrier name, market name, or design
decisions
z Restricted to binary format for input and output files
The discipline to save frequently and track major edits as they are complete is often the price to
pay for this environment.
PRL Technical
PRL Tools – Spreadsheet Workshop
Section 5-21
Spreadsheet Editing
• Richer Information format
• More readable Source Change Details Released
• Edits are clearer Data Data
– Carrier information
Text Format Spreadsheet
– Rationale for record
Macros PRL Editor Format Text File
Spreadsheet Production
Understanding the limitations of the PRL editor is all well and good, but many people with PRL
responsibilities find themselves in the situation of OTA systems not yet in place, stringent time
pressures, and only the PRL editors to work with.
The good news is that the PRL editor limitations can be mitigated to some extent. In general,
spreadsheet applications provide much richer editing environments. In addition to the columns
needed for the PRL, developers can have all sorts of supplementary information present, such as
the region, market, carrier name, TDS cross-reference, and whatever else their process requires.
Using a spreadsheet is great but if starting with a binary PRL, how does the PRL get into the
spreadsheet and once the editing and construction are all done how does it get into the binary
form again? There are basically three options here:
z Using the PRL Editor as a compiler
z Tools that transparently handle PRLs negating the need for a PRL editor (e.g., PRL Presto)
z Working with text-only PRLs
PRL Technical
PRL Tool Suite – An Excel Add-in Workshop
Section 5-22
TDS management
10101001101111110 PRL Policy Design
110111000011110011 (PREDICATE)
PRL Testing
(PREDICT)
Motivation
z PRL maintenance is complex
– Actions from the most abstract layer (contract agreements with other carriers) to a
complex computer/headset technical field (binary file) are required.
z TDS maintenance is complex
– Current Datasheets are often incomplete and difficult to track; PREDICATE
provides a geographical organization for TDS and updates!!
z PRL building is obscure
– Using the data coming directly from the TDS read by PREDICATE, we have
available a tool for PRL Policy Design, which leads us to a PRL; easy and errorless.
z System selection is confusing
– PREDICT provides PRL developers a first testing environment for their PRL design
before going to field test. The code inside PREDICT is the same code that is given to
phone manufacturers.
PRL Technical
PRESTO Workshop
Section 5-23
10101001101111110
110111000011110011
binary PRL file
PRESTO RL Editor
(PRL Toolbar Suite) (QPST)
10101001101111110
110111111110010011
Modified binary PRL file
PRESTO’s Functionality
z Read and Write PRL files to and from Excel
z Give us the size of each Acquisition Record, System Record, and PRL file
z Editing primitive functions:
– Over Acquisition records
Insert
Move
Delete
– Over System Records
Insert
Delete
z Special edition functions
– Remove non-referenced Acquisition Records
– Redirect System Records
z Customizable labels
z Dynamic validation
PRL Technical
PRL Auditing Workshop
Section 5-24
System Table
• Verification ofmarkets to SIDs and channels
• Identification of missing data
Acquisition Table
• Identification of unreferenced channels
Auditor Tools
The use of auditing tools is an excellent way to verify that the PRL contains valid information.
Auditing tools provide a form of static testing. Generally an auditor tool performs the following
tasks.
z Verify that every entry in the PRL is described in technical data sheets and that the
description is correct.
z Identify any systems in the PRL that are not described in the technical data.
z Identify any channels that are not described for a particular system in the technical data.
z Identify all unreferenced channels in the acquisition table.
PREDICATE is a utility from QUALCOMM that performs this type of static auditing. Auditing
is difficult for today’s CDMA PRL developers because of the wide range of formats in use for
the exchange of Technical Data Sheets.
PRL Technical
PRL PREDICATE Workshop
Section 5-25
PRESTO
(PRL Toolbar Suite)
TDS information
PRL Information
PREDICATE
Reports PRL Policy
Creation
PRL Auditing
TDS Importing/Management
z Classify your TDS documents independently of where they are located on your hard drive.
z Read the heterogeneous TDS information into a homogeneous database where it can be
easily managed.
z Manage TDS UPDATES automatically.
z Report TDS reading problems such as:
– incoherent values
– missing information
– not valid entries
PRL Policy Creation/Management
z Define PRL Header properties.
z Define each one of the GEOs of your PRL.
– Add Operators and prioritize them
– Add Markets
– Restrict modes of operation and create priorities between them
z All information comes from the previously loaded TDS (No room for mistakes).
PRL Technical
PRL PREDICT Workshop
Section 5-26
PRESTO
PRL Data
Trace PRL
behavior
PREDICT
TDS Information
PREDICATE
PREDICT’s Functionality
z PREDICT is a System Selection code simulator; it uses the same code that’s given to
manufacturers. The simulation is carried out using RF data coming from the TDS
information previously loaded with PREDICATE. That data is narrowed down by clicking
in a specific globe position on the map and selecting a market for which TDS data is
available.
z PRL information will be read with PRESTO, which guarantees that any PRL that
PRESTO can read is be available for use in PREDICT. Some more information regarding
the System Selection process (which is usually hidden) is available to the PRL Tester.
PRL Technical
PRL Design – Section Review Workshop
Section 5-27
Review
1. Device constraints deal with limiting characteristics of devices on which PRLs are loaded. Policy constraints deal with an
operator’s guidelines and strategy for developing and supporting PRLs.
2. Types of device constraints include:
z System technologies supported (e.g., AMPS?)
z Band Classes/frequencies supported (e.g., 800 MHz)
z Whether the device considers certain channels to be invalid
z Whether newer PRL versions are supported (e.g., IS-683-C)
z Maximum memory available for PRL storage
3. PRL properties policies include:
z Whether PRLs will be open or closed (i.e., Preferred_Only property)
z Consistent method for identifying PRLs (i.e., PRL_ID property)
z What default roaming indicator to use for undefined systems acquired by an open PRL
4. Using more GEOs in a PRL provides more efficient scanning and less reselection because each GEO contains a smaller
number of systems and disparate areas.
5. A PRL with more GEOs is easier to maintain because changes are more localized.
6. Among the information contained in a TDS is the system ID (SID/NID, MCC/MNC) and air interface information (Band
Classes, blocks/bands, channels) for each coverage market. This information is required to create PRL system and
acquisition records.
7. The PRL Toolbar Suite includes three components:
z PRESTO – PRL editing
z PREDICATE – PRL auditing against TDS data
z PREDICT – device simulation using PRL and TDS data
Comments/Notes
SECTION
Notes
PRL Technical
Section Learning Objectives Workshop
Section 6-2
Notes
PRL Technical
PRL Design Issues Workshop
Section 6-3
Notes
PRL Technical
Potential Reselection Exits Workshop
Section 6-4
• SIDs from:
– Same carrier
– Same GEO
– Differing priorities
• Geographically disparate SIDs in the same GEO with
differing priority.
– This will cause Reselection exits in the GEO for:
All except the most preferred SIDs
A device would keep attempting to acquire one system in a remote market with
0% chance of acquiring the systems sought.
PRL Technical
Coverage Holes in GEOs Workshop
Section 6-5
PRL Technical
Presence of AMPS Systems Workshop
Section 6-6
PRL Technical
Presence of Unlisted SIDs Workshop
Section 6-7
PRL Technical
Inconsistent Preferences within GEOs Workshop
Section 6-8
PRL Technical
Duplicate System Records Workshop
Section 6-9
PRL Technical
PRL Design Checks – Section Review Workshop
Section 6-10
Review
1a. Their devices will continue to try to acquire the New York system because it is most
preferred even though they have no chance of acquiring it. The continual reselection attempts
result in lower battery life and potential missed pages.
1b. They should make all of their CDMA systems the same priority within the GEO. They may
also want to split the GEO into two or more GEOs that are smaller and more geographically
localized.
2. Priorities within a GEO should only be used to establish preferences between different
technologies (band classes) and roaming partners. System priorities should not be used to
attempt to establish geographic preferences inside of a GEO, as this can often result in
unintentional reselection exists.
3. The behavior of a CDMA Preferred acquisition record is to first look for CDMA; if CDMA is
not found, then look for AMPS before advancing to the next acquisition record. Note that this
behavior may result in AMPS service being selected over CDMA service (i.e., the AMPS
service of a higher priority system will be selected over the CDMA service of a lower priority
system).
4. Camping on a network with no service is caused by the use of a wildcard SIDs, use of an
open PRL (i.e., Preferred_Only = False), or presence of a system record for an unlisted SID
(i.e., SID is not in the TDS) that causes the device to acquire a non-roaming partner system.
Many CDMA systems will not send a RegistrationRejectOrder to the device in this scenario.
SECTION
Notes
PRL Technical
Section Learning Objectives Workshop
Section 7-2
¾ Define 1xEV-DO.
¾ Define a Sector & a Subnet ID.
¾ Explain the changes for IS-683C PRL.
¾ Describe the new records for EV-DO.
¾ Explain the association of 1X and DO systems.
Notes
PRL Technical
The PRL with CDMA2000 1xEv-DO Workshop
Section 7-3
• IS-683C:
– Defines hybrid access terminal operation.
– Is an extension to IS-683A/B.
– Extended to include support for an IS-856 system record type.
– Supports the defining of associations between IS-2000 systems
and IS-856 systems.
May Contain U.S. Export Controlled Information
What is 1xEV-DO?
CDMA2000 1xEV-DO is an evolution of CDMA2000 and an approved 3G standard for fixed,
portable, and mobile applications. CDMA2000 1xEV-DO is Data-Optimized, providing a peak
forward data rate of 2.4 Mbps for Revision 0 and 3.1 Mbps for Revision A, and peak reverse
rates of 153 kbps and 1.8 Mbps for Revision 0 and A, respectively. IS-856 describes the
operation of CDMA2000 1xEV-DO systems.
Understanding some of the basics of an 1xEV-DO network and the mode of operation of the
1xEV-DO device (often called the Access Terminal or AT) is necessary to understand how to
properly construct a PRL and how that PRL is used by the device. Necessary elements are:
z The Sector-ID and its use in 1xEV-DO systems
z The subnet ID and its use in the PRL and how it relates to Sector ID
z Hybrid Mode 1xEV-DO operation
PRL Technical
IS-683C PRL Workshop
Section 7-4
IS-683C:
• New PRL format that adds support for IS-856 (1xEV-DO) systems.
• Includes new:
– Acquisition Record in Acquisition Table
– System Record type in System Table for IS-856 systems
• Acquisition Table
– Generic Acquisition Record for IS-2000/IS-95 and for IS-856
Specifies band class and channel number pairs-
• System Table
– System record type is used to differentiate between IS-2000/IS-95 and
IS-856 systems.
– In IS-856 system record type:
SID- and NID-related fields are replaced with Subnet-ID related fields.
New Association fields to link IS-856 system to an IS-2000 system.
PRL Technical
Sector ID in 1xEV-DO Workshop
Section 7-5
• Suggested provisioning:
– Common set of most significant bits for all sectors
PRL Technical
Subnet ID in the 1xEV-DO PRL Workshop
Section 7-6
• A length of zero:
– Is defined as a wildcard mask.
– Selects any 1xEV-DO system.
Subnet ID in 1xEV-DO
A subnet ID in the PRL is a 128-bit address value formatted according to the IPV6 protocol (not
an IPV6 address). IPV6 format comprises eight 16-bit values separated by colons followed by a
slash and a length value within the range 0 to 127. It is not necessary to write the leading zeros in
an individual field, but there must be at least one numeral in every field, for example:
Just as a SID of zero value meant any SID in 1X, a subnet ID of /0 indicates a wildcard subnet ID
and indicates any 1xEV-DO system is selectable (subject to network authorization and
authentication.)
The length value indicates how much of the subnet-ID is significant. Generally 1xEV-DO
systems are only specified in the PRL at the subnet-ID part (equivalent to SID-only usage in 1X);
thus the length generally will be 104 bits or less.
PRL Technical
IS-683C PRL Structure Workshop
Section 7-7
PRL Technical
IS-683C – The New Records Workshop
Section 7-8
Acquisition Table
Acquisition Index Acquisition type Description
Generic Acquisition Record for
0 1011 HRPD (High Rate Packet Data:
IS-856 systems)
1 1
2 1
System Table
SYS_RECORD_T SUBNET_ID ASSOCIATION_I ASSOC_T PN_ASSOC DATA_AS
YPE NC AG SOC
0001 0:0:0:0:0:0:0:0/26 1 3 No No
PRL Technical
1xEV-DO Acquisition Record Workshop
Section 7-9
ACQ_TYPE 4
• Band Class LENGTH 5
LENGTH/2 occurrences of
• Channel BAND_CLASS 5
CHAN 11
PRL Technical
IS-683C System Record Structure Workshop
Section 7-10
1 Record Type
1 Geo Indicator
1 Preferred or Negative Indicator
0|1 Selection Priority Indicator
0|1 Roam Indicator
1 Acquisition Record Index
1 Sub-Net Identity
PRL Technical
1xEV-DO System Record Workshop
Section 7-11
SYS_RECORD_TYPE 4
PREF_NEG 1
• System Record Type GEO 1
• Negative/Preferred PRI
ACQ_INDEX
1
9
• Geography SUBNET_COMMON_INCLUDED
SUBNET_LSB_LENGTH
1
• Roam Indicator
ASSOCIATION_INC
ASSOCIATION_TAG
1
0 or 8
PN_ASSOCIATION 0 or 1
DATA_ASSOCIATION 0 or 1
PRL Technical
1xEV-DO System Identification Workshop
Section 7-12
SUBNET_COMMON_INCLUDED 1
SUBNET_LSB_LENGTH 7
SUBNET_LSB SUBNET_LSB_LENGTH
SUBNET_COMMON_OFFSET 0 or 12
PRL Technical
Association of IS-856 Systems Workshop
Section 7-13
Association Part
The presence of an association is indicated by the ASSOCIATION_INC field having a value of
1. Three associations form the association part of the system record.
The first, and most significant in use today, is the ASSOCIATION_TAG. This is an 8-bit number
that names the “association set” to which this system record belongs. The set name only has
meaning within the scope of a GEO. System records in the same GEO that have the same
Association Tag are members of the same set. System records in different GEOs that have the
same Association Tag are not members of the same set.
The other two associations, while present in the PRL, are not currently used by system selection
but their description is included here for completeness:
z PN association flag – identifies systems that have the same PN offset assignment (i.e., co-
located).
z Data association flag – identifies systems that can reach the same set of PDSNs (i.e.,
associated).
PRL Technical
Hybrid 1X / EV-DO PRL – Section Review Workshop
Section 7-14
Review
1. IS-683C includes support for EV-DO systems in the PRL.
2. IS-683C supports EV-DO systems by providing:
z New extended system record that supports EV-DO systems
z New generic acquisition record that supports EV-DO systems
z New association fields to link 1X and EV-DO systems
3. The Subnet ID is composed of a 104-bit Subnet ID Part and a 24-bit Sector ID Part. It is used
as the system ID in EV-DO system records. The Subnet ID Part and Sector ID Part are
similar to the SID and NID used with 1X systems.
4. The Subnet ID length indicates how many bits of the Subnet ID are significant. Only these
significant bits are used for matching Sector ID values being broadcast.
5. A Subnet ID length of 0 is a wildcard that indicates that no bits of the Subnet ID are
significant. Therefore, any Sector ID being broadcast will match. The danger in using such
wildcard values is that non-roaming partner systems can be acquired, even though the user
will not be able to receive service from the acquired system.
6. Yes, each association tag value identifies a set of one or more EV-DO systems. Any number
of 1X systems may link to that set of EV-DO systems by using that association tag value.
SECTION
Use of the Hybrid
8 1X / EV-DO PRL
Notes
PRL Technical
Section Learning Objectives Workshop
Section 8-2
Notes
PRL Technical
Hybrid System Determination Workshop
Section 8-3
PRL Technical
Device Settings & Modes of Operation Workshop
Section 8-4
• Preference mode
• Hybrid preference mode
• Single system (non hybrid) mode
– 1xEV-DO-only mode.
– CDMA 1X-only mode.
• Dual system (hybrid) mode
PRL can contain system types Can Operate on Can be in Dual
Preference Mode System (Hybrid)
1x/IS-95 1xEV-DO Analog 1x/IS-95 1xEV-DO Analog
Mode
Digital only 9 9 9* 9 9 9 9
Analog only 9* 9* 9 8 8 9 8
9 8 8 9 8 9 8
Automatic (determine mode
based on PRL) 8 9 8 8 9 8 8
9 9 9 9 9 9 9
1X only 9 9* 9 9 8 8 8
1xEV-DO only 9* 9 9* 8 9 8 8
1X and analog only 9 9* 9 9 8 9 8
* ignored if present
PRL Technical
1xEV-DO Scanning Workshop
Section 8-5
1xEV-Do Scanning
Scanning concepts are similar for 1xEV-DO with some subtle changes.
Recent Channel or Most Recently Used List
Devices maintain a Most Recently Used (MRU) table. Typically, in a 1xEV-DO device, there is
still just one MRU table except now its space is allocated between remembering the 1X/IS-95
systems and the 1xEV-DO systems that have provided service. The MRU table does not record
any association information. The number of total entries in a hybrid mobile device’s MRU list is
implementation dependent but a typical number may be 12. The allocation split between 1X/IS-
95 and 1xEV-DO systems is also implementation dependent but a typical split may be 11/12
entries for 1X/IS-95 and 1/12 entries for 1xEV-DO.
Types of 1xEV-DO Scan List
Just like for 1X/IS-95 operation, the 1xEV-DO device builds a scan list dynamically. The
building of scan lists, their names and uses, is not standardized and is left to the implementation.
Therefore, how the scan list is constructed is a function of the particular vendor’s
implementation of system determination. In general, scan lists are formed from:
z 1xEV-DO channels from the most recently used table
z 1xEV-DO channels from the acquisition table in the PRL
PRL Technical
Hybrid System Selection Workshop
Section 8-7
Power up
PRL Technical
Hybrid System Selection (continued) Workshop
Section 8-8
This slide shows a generalized example of the components of a hybrid system. On initialization, the hybrid device
searches for an available 1X/IS-95 system and attempts to acquire it first (as described by section 5.3.2). During this
time the radio interface is dedicated to 1X/IS-95 system acquisition. In 1X/IS-95 initial system selection, the state of
the environment was simply described as the presence or nonpresence of a usable system. In hybrid operation,
during initialization, the combination of the states of both the 1X/IS-95 and 1xEV-DO environments now yield one
of four possible environment conditions that may exist:
z Both 1X/IS-95 and 1xEV-DO systems are available.
Where both systems are available the hybrid device acquires 1X/IS-95 first. Once idle on 1X/IS-95, it attempts to
acquire a 1xEV-DO system in the association set using channels of the Collocated Scan List (see section scan list,
starting from the top). If a 1xEV-DO system is acquired that is listed in the PRL’s system table and is the most
desirable system in the association set, then service is provided on that system and no further 1xEV-DO scanning is
performed—until the system is lost. If the device acquires a 1xEV-DO system that is listed in the PRL (system table)
that it is not the most desirable system in the association tag scope of its geographic region, the device may search
using the better 1xEV-DO service scan list. Once both systems are acquired the hybrid device enters idle mode
operation on both the 1X/IS-95 system and the 1xEV-DO system.
PRL Technical
EV-DO System Selection Workshop
Section 8-10
PRL Technical
Avoidance of Unusable 1xEV-DO Systems Workshop
Section 8-11
Most implementations will avoid unusable 1xEV-DO systems. The actual period is
implementation dependent. The condition causing the avoidance varies; avoidance times can
range from 30 seconds to 10 minutes. Avoiding a 1xEV-DO system does not imply that a system
is re-acquired after avoidance timer expires; it just means that it is eligible to be scanned again.
During the avoidance time the channel is omitted from the 1xEV-DO scanning process. When
the avoidance timer expires, the channel reenters the next scanning schedule.
Max-Access Probe Exit Scan
When an access attempt fails with maximum number of permitted access probes[1], the mobile
device would normally use a maximum access probe exit scan list for reacquisition. This list is
similar to a power up scan but lacks the channel on which the access attempt failed.
[1] Access Probe is a term used to collectively mean a system access message, sent on the access channel, and the specific power level with which it is sent. If the mobile device
does not get a response, it sends subsequent access probes (same message at increased power levels). Often described as raising its voice until it is heard. There is a predefined
maximum number of probes a device can send and a maximum power it can use.
PRL Technical
System Loss Workshop
Section 8-12
Idle
9 8 1x/IS-95 system lost reselection. 1xEV-D O acquisition m ay also occur
Idle
8 9 1xEV-D O system lost reselection
No action
Connected
8 9 Session is handed down to 1x & 1xEV-
DO acq w hen idle on 1x
9 8 No action until 1xEV-DO idle. Session continues in connected state.
System Lost
With the hybrid device system, lost requires further qualification to determine what should happen. There are three basic pieces of
information that are required to understand what the next steps should be:
z which system is lost
z the relevant system loss scan list
z a relevant system loss service scan
When a mobile device has declared that it has lost a system[1] it invokes its system lost reselection policy. The “schedule” of
attempts to reacquire the system that has just been lost is set and driven by the construction of the system lost scan list. As in
better service reselection, if a system is acquired and it is less-preferred, then better service reselection will be performed. It is
worth noting that often the system determination will search through the GEO first.
1X/IS-95 Idle and 1xEV-DO System Lost while Idle
If a 1xEV-DO system is not available, the AT acquires a 1X system and then, after repeated attempts to acquire a co-located
1xEV-DO system, enters power save mode on the 1xEV-DO system. In idle state, the device monitors both CDMA2000 1X and
1xEV-DO systems. The wakeup slot for 1X should not overlap with the preferred control channel cycle for 1xEV-DO.
1xEV-DO connected and 1X/IS-95 Lost
In some implementations there may be no attempt to acquire 1X/IS-95 service while 1xEV-DO is in the connected state. Other
implementations may permit 1X/IS-95 acquisition but enforce some form of throttling scheme so as not to starve the connected
1xEV-DO session of radio resources. A common throttling scheme is to return to the 1xEV-DO session for a telescoping period
of time while 1X/IS-95 system is unavailable and 1xEV-DO is connected.
1xEV-DO System Lost while in Connected State
If the hybrid device is in a 1xEV-DO connected state and moves to a location where there is no 1xEV-DO coverage, data session
handoff to 1X/IS-95 system takes place.
[1] The signal level that a mobile device declares that it loses a system is implementation dependent. A CDMA system is normally unusable an at
Ec/Io of -16 dB or lower.
Review
1. The Collocated Scan List is built and used after an IS-95/1X system with an association tag
has been successfully acquired (i.e., device is in idle mode on the IS-95/1X system).
2. The Collocated Scan List contain all EV-DO channels referenced by EV-DO system records
with the same association tag as the acquired IS-95/1X system. It also includes EV-DO
channels from the MRU table.
3. Association tags only have meaning within a GEO (i.e., IS-95/1X systems in a GEO can only
be associated with HRPD systems in the same GEO).
4. Most hybrid devices, upon failing to acquire an IS-95/1X system, will build an ‘All
Collocated 1xEV-DO Scan List’ and use it to attempt to acquire an EV-DO system. Because
there is no IS-95/1X system for association, this scan list will include all EV-DO channels
referenced by EV-DO system records with any association tag (as well as EV-DO channels
from the MRU table).
5. The device will periodically attempt to acquire a more preferred EV-DO system from the
same association tag set. This does not effect the acquired IS-95/1X system.
6. Yes, if a new IS-95/1X system with a different association tag is acquired, the device will
attempt to acquire an EV-DO system associated with the new IS-95/1X system.
7. When an EV-DO system is deemed unusable, the device typically starts an avoidance timer
and the unusable channel is omitted from scan lists during this avoidance period.
Comments/Notes
SECTION
Writing a Hybrid
9 1X / EV-DO PRL
Notes
PRL Technical
Section Learning Objectives Workshop
Section 9-2
Notes
Coverage considerations
• What is the coverage of the deployed system going to be?
– EV-DO coverage is always a subset of IS-95(A,B)/1X.
• IS-95(A,B)/1X coverage is essential for Hybrid mode.
Hybrid mode
• EV-DO system is always associated with IS-95(A,B)/1X system.
• Multiple EV-DO systems can be associated with a single IS-95(A,B)
/1X system.
• A single EV-DO system can be associated with multiple IS-95(A,B)
/1X systems.
• A 1X or an EV-DO system can only be in one association.
Notes
PRL Technical
1xEV-DO PRL Design Considerations Workshop
Section 9-4
• Geographical areas
Geographical Areas
As before, the number of geographical regions is an important design consideration.
z For an EV-DO overlay, underlying existing geographical area design is a useful
consideration.
z In this situation, it would be useful to identify which of these geographical regions have
EV-DO service available.
Associating EV-DO with 1X/95 systems
z Within a given region, which 1X/95 systems (SID/NIDs or channels) have associated IS-
856 systems?
– Multiple IS-856 systems, distinguished by channels or subnets, can be associated.
– Some IS-856 systems can be configured to be more preferred than the others.
It is important to understand whether roaming into the EV-DO network of a roaming partner is
permitted. If EV-DO service is to be provided while roaming in an IS-95(A,B)/1X network of a
roaming partner, those systems must be associated with the IS-95(A,B)/1X roaming network.
It is not permitted to associate an EV-DO system with any analog system.
PRL Technical
Varying EV-DO Coverage Workshop
Section 9-5
15001 • Ubiquitous 1X
15:2:3:4:5:6:7:8
coverage
• Varying EV-DO
4001 partner footprints
4:2:3:4:5:6:7:8
• Which partner is
preferred?
9:2:3:4:5:6:7:8
9001
• Which associations
are to be defined?
1X Pri 1X SID Assoc. EV-DO Subnet PRI 1X Pri 1X SID Assoc. EV-DO Subnet PRI
1 9001 9:2:3:4:5:6:7:8 1 1 9001 1 9:2:3:4:5:6:7:8 1
2 4001 1 9:2:3:4:5:6:7:8 2 2 4001 2 9:2:3:4:5:6:7:8 1
3 15001 9:2:3:4:5:6:7:8 3 3 15001 3 9:2:3:4:5:6:7:8 1
Notes
PRL Technical
How to Write an EV-DO PRL Workshop
Section 9-6
Notes
PRL Technical
How to Write an EV-DO PRL (continued) Workshop
Section 9-7
Only the value of the first len bits is important; therefore, only such bits are saved with the PRL
file. Any bits that are outside len may be set to 0. For example: 0:0:0:0:0:0:0111:0/104 Is equal
to: 0:0:0:0:0:0:0100:0/104
To specify a wildcard subnet ID:
z Set len to 0. For example: 0:0:0:0:0:0:0:0/0
z The shorthand notation /0 can also be used to specify the wildcard subnet ID. It is not
necessary to write the leading zeros in an individual field, but there must be at least one
numeral in every field. For example: 0000:0000:0000:0000:0000:0000:0100:0000/104
can also be entered as: 0:0:0:0:0:0:100:0/104
Only the value of the first len bits is important; therefore, only such bits are saved with the PRL
file. Any bits that are outside len may be set to 0. For example: 0:0:0:0:0:0:0111:0/104 is equal
to 0:0:0:0:0:0:0100:0/104
PRL Technical
Association of IS-856 Systems Workshop
Section 9-8
• “PN Association” indicates that the IS-2000 and IS-856 systems have
the same PN offset.
• “Data Association” indicates that the IS-2000 and IS-856 systems are
using the same PDSN.
GEO
1X (SID) EV-DO
Association Tag
systems systems
Association Part
The presence of an association is indicated by the field ASSOCIATION_INC. having a value of
1. There are three associations that comprise the association part of the system record.
The first, and most significant in use today, is the ASSOCIATION_TAG. This is an 8-bit number
that names the “association set” to which this system record belongs. The set name has meaning
only within the scope of a GEO. System records in the same GEO that have the same Association
Tag are members of the same set. System records in different GEOs that have the same
Association Tag are not members of the same set.
The other two associations, while present in the PRL, are not currently used by system selection
but their description is included here for completeness:
z PN association flag – identifies systems that have the same PN offset assignment (i.e.,
collocated).
z Data association flag – identifies systems that can reach the same set of PDSNs (i.e.,
associated).
Section Review
1. No, analog systems cannot be associated with EV-DO systems. Only IS-95/1X systems may
be associated with EV-DO systems.
4. False; while the Subnet ID is represented using the IPv6 address format, Subnet IDs are not
actual IPv6 addresses.
Comments/Notes
SECTION
10 PRL Enhancements
Notes
PRL Technical
Section Learning Objectives Workshop
Section 10-2
Notes
PRL Technical
The Need for PRL Enhancements Workshop
Section 10-3
PRL Technical
CDG Resolution for PRL Enhancements Workshop
Section 10-4
PRL Technical
Identifying a System Workshop
Section 10-5
SID/NID
Currently the CDMA granularity of
MCC/IMSI_11_12 SID/NID
MCC/IMSI_11_12
roaming control is the SID/NID pair.
SID & /NID
MCC & IMSI_11_12
• One description of a particular market
within the carrier’s network as chosen by
the carrier.
• Provides good control for the carrier of
Every CDMA system broadcasts in how to describe the network.
System Parameters messages.
Now the CDMA operator may
• System Identification (SID) describe their network both ways:
• Network Identification (NID)
• Using the granularity of SID/NID for its
• Mobile Country Code (MCC) own users and other roaming partners
• IMSI_11_12 (akin to Mobile Network Code as needed.
– MNC) • Using the MCC + IMSI_11_12
granularity for roaming partner PRLs
that do not require SID/NID information.
• Both can be used in combination.
PRL Technical
PRL Enhancements – How They Work Workshop
Section 10-6
CSC
System Parameters: {SID=8742, NID=65535}
Extended System Parameters: {MCC=310, IMSI_11_12=10} CDMA/OTA
Geo:
Geo: CountryX
CountryX
BSC
MSC
Carrier - System
Permitted Selection Roaming Acquisition
(SID, NID) or
Systems Pref Indicator Index
(MCC/MNC)
MCC/MCC=310,10 First ON 0
MCC/MCC=310,42 Second ON 0 BSC
CDMA Abis
roamer
System Table: Geo entries requires for CountryX
Handset View of the PRL Enhancements Network View of the PRL Enhancements
PRL Use of a valid MCC and IMSI_11_12
• Can describe a system by: • ITU issues MCCs
– SID/NID • Each country administers allocation of Network codes in the
US the administrator is Telcordia (www.imsiadmin.org)
– MCC/MNC
• Full backward compatibility is supported.
• CDMA air interfaces currently support the broadcast of a 2-
digit MNC. (As in GSM)
A PRL can describe a system by SID/NID or MCC/MNC, or both. The MCC and MNC are encoded into the
existing SID and NID fields such that full backward compatibility is achieved.
Handset
An enhanced system determination is needed to use the MCC/MNC system record. This enhanced system
determination has been available in all QUALCOMM MSM 6xxx series chipsets since April 2004. With this
enhanced system determination, the device reads the MCC and MNC information from the Extended System
Parameters Message and uses them to perform PRL matching when dealing with MCC/MNC system record.
If system determination is not updated, and the PRL has MCC/MNC type entries, they will appear as normal
SID/NID entries. Since the two special SIDs used in the PRL encoding are never broadcast on any system, those
entries will never trigger a match and thus have no effect on system selection.
Network
The CDMA 2000 (Revisions 0 and A) air interfaces currently require the broadcast of a 2-digit MNC. (IMSI_11_12)
and a 3-digit MCC in the Extended Systems Parameters message. Since these are mandatory parameters of this
message, each CDMA system must, and currently does, broadcast a value in these fields. These current values may
be the manufacturer default if it has not be set by the operator, or, they may be the wildcard values for MCC and
IMSI_11_12.
For the PRL enhancements to function, the network must be configured to broadcast the real values allocated to the
operator.
PRL Technical
Use of Existing Standards Workshop
Section 10-7
The resolution:
• Does not modify any CDMA standard.
• Describes a uniform method for populating and using existing data
elements currently in use.
PRL Technical
Implementing the CDG Resolution Workshop
Section 10-8
Infrastructure c
Configuration
ii
iii
PRL MS
Management Programming
MS
US Operator Programming e d
Enhanced PRL
Roaming
PRL Technical
CDG Coordination Roles Workshop
Section 10-9
Notes
[MCC, MNC]
Operators are responsible for:
• Obtaining the valid MCC and IMSI_11_12
System Parameters: {SID=8742, NID=65535}
for their network(s).
Extended System Parameters: {MCC=YYY, IMSI_11_12=xx}
[MCC, IMSI_11_12]
• Building and distributing new PRLs with
the more streamlined MCC/MNC entries.
New PRLs
Notes
PRL Technical
PRL Enhancement Resolution – Benefits Workshop
Section 10-13
Notes
PRL Technical
PRL Enhancements – Section Review Workshop
Section 10-14
Review
1. An enhanced PRL is one that supports identification of systems using SID/NID, MCC/MNC, or both.
2. A MCC/MNC pair uniquely describes an operator’s entire network in a country, requiring only one system table
entry. However, the same network may use many SID/NID values, requiring many system table entries.
3. SID/NID provides a finer granularity of control for an operator to describe their own and, perhaps, their
domestic roaming partner networks, while MCC/MNC provides a much more efficient method to describe
international roaming partner networks. As such, it is common for enhanced PRLs to use both SID/NID and
MCC/MNC identifiers.
4. To support enhanced PRL, Base Stations must broadcast correctly populated MCC and IMSI_11_12 (i.e., 2-
digit MNC) values in the Extended System Parameters message (i.e., not manufacturer defaults or wildcard
values).
5. No, this is a common misconception resulting from the fact that enhanced PRL uses MCC and IMSI_11_12.
While these fields would also be used to support full IMSI in the core network, enhanced PRL only requires
them to be correctly populated in the Extended System Parameters message sent over-the-air, regardless of
whether IMSI is implemented.
6. Use of MCC/MNC instead of SID/NID to identify international roaming partner networks makes PRLs much
easier to manage and ensures that roaming partner information is current.