Professional Documents
Culture Documents
Roaming
CDG Document 86
Version
1.0
1 April 2004
Notice
Each CDG member acknowledges that CDG does not review the
disclosures or contributions of any CDG member nor does CDG verify
the status of the ownership of any of the intellectual property rights
associated with any such disclosures or contributions. Accordingly, each
CDG member should consider all disclosures and contributions as being
made solely on an as-is basis. If any CDG member makes any use of
any disclosure or contribution, then such use is at such CDG member's
sole risk. Each CDG member agrees that CDG shall not be liable to any
person or entity (including any CDG member) arising out of any use of
any disclosure or contribution including any liability arising out of
infringement of intellectual property rights.
2 1. Introduction ................................................................................................................................ 1
3 1.1 Summary ............................................................................................................................ 1
4 1.2 Acronyms and Abbreviations ............................................................................................. 1
5 1.3 Technical Assistance ......................................................................................................... 2
6 2. Background and General Description ..................................................................................... 3
7 2.1 Feature Summary............................................................................................................... 3
8 3. Detailed Description .................................................................................................................. 5
9 3.1 Base Station ....................................................................................................................... 5
10 3.2 Mobile Station..................................................................................................................... 5
11 3.3 Mobile IMSI Programming, Paging, and Access................................................................ 6
12 3.4 Other Possible Uses .......................................................................................................... 6
13 4. Network Code Number Administration.................................................................................... 7
14 4.1 Mobile Network Code ......................................................................................................... 7
15 5. Backward Compatibility: Existing Mobiles and PRLs............................................................ 8
16 5.1 Backward Compatibility ...................................................................................................... 8
17 6. Implementation......................................................................................................................... 10
18 7. Conclusion................................................................................................................................ 12
19 8. IS-683C Support ....................................................................................................................... 13
20 8.1 IS-683C Support............................................................................................................... 13
21 9. Example .................................................................................................................................... 14
22 9.1 Example ........................................................................................................................... 14
23 10. References .............................................................................................................................. 16
24
1 Figures
2 Figure 6-1: Conceptual Representation of PRL organization....................................... 10
3 Figure 6-2: Sample PRL representation using the enhancements .............................. 11
4
5 Tables
6 Table 1-1: Acronyms and Abbreviations ........................................................................ 1
7 Table 5-1: IFAST SID Allocations for PRL Enhancement for International Roaming..... 9
8 Table 6-1: Encoding when MSB of MCC is 0 ............................................................... 11
9 Table 6-2: Encoding when MSB of MCC is 1 ............................................................... 11
10 Table 9-1: Sample PRL Existing Format ...................................................................... 14
11 Table 9-2: Sample PRL with enhancement encoding .................................................. 15
12
13
1 Revision History
2 1.1 Summary
3 This document specifies the system requirements and enhancements to the Preferred
4 Roaming List (PRL) to support International Roaming. The enhancements affect both the
5 base station and mobile station.
Acronym Meaning
MS Mobile Station
Acronym Meaning
3 The Preferred Roaming List (PRL) contains information to assist the mobile station
4 system selection and acquisition process, particularly when the mobile station is
5 roaming.
6 The preferred roaming list can be sent to the mobile station using Over-The-Air Service
7 Provisioning (OTASP). The mobile station retains the preferred roaming list when power
8 is turned off.
9 The preferred networks to be used by a mobile station are identified by SIDs (System
10 IDs) and NIDs (Network IDs).
11 A “SID” typically covers the area of a city or large town. There are currently no strict
12 guidelines for the size of SIDs. Their definition is left to the operators and national
13 authorities. The range of SID assignments per country can be found in ANSI/TIA/EIA-
14 TSB-29E.
15 A “NID” is an optional subdivision of a SID. NIDs can identify, for example, different
16 rating areas, toll areas, private networks, MSC boundaries, or any other subdivision the
17 operator may want to distinguish within a SID.
18 A national operator may have coverage over an entire country. For certain countries, this
19 can amount to tens, and sometimes hundreds of cities/regions being covered, which in
20 turn implies tens or hundreds of SIDs for a single operator.
21 When two operators would like to offer international roaming service between each
22 other, PRL information should be exchanged and reviewed to ensure mobile stations will
23 correctly find the preferred system. If the operators are national operators covering a
24 large number of SIDs, the PRLs get significantly larger due to the inclusion of the
25 roaming partner’s SIDs.
26 Therefore, to support international roaming, the following key issues are identified:
27 ƒ PRL Management: CDMA operators need to collect the roaming partner’s
28 configuration information to construct PRLs. If one of the roaming partners changes
29 its network configurations, such as adding/changing a SID or NID, all other operators
30 may need to update the PRL based on the new configuration. PRL maintenance is
31 complex. This discourages some operators from roaming.
32 ƒ Size of PRL: The present design of the PRL only allows a single entry per SID /NID
33 pair. For a large CDMA network with many roaming partners, this design is sub-
34 optimum, as it requires a large number of (SID,NID) entries to be present in the PRL,
1 which causes a significant impact on the memory requirements of the handset and
2 download times.
3 The enhancement described in this document involves using existing overhead channel
4 information elements to identify a carrier’s network identification.
5 By having each carrier broadcast its own network code, a mobile station can determine if
6 the current network is within its PRL, and a corresponding behavior and/or priority can
7 be assigned.
8 A mobile station would then only need (in most instances) a single PRL entry to describe
9 an operator, instead of the tens or hundreds of entries that would be required if it had to
10 enter each partner’s individual SID and NID.
11 Describing a roaming partner by its network code also alleviates the management and
12 coordination of updating a customer’s PRLs when the roaming partner decides to
13 change, delete, or add SIDs.
19 Note: These network codes only need to be distinct within a country code (MCC).
20 Each country can administer and assign these codes without needing to
21 coordinate with other countries.
22
1 Table 5-1: IFAST SID Allocations for PRL Enhancement for International Roaming
SIDOPER-1 15905 Operator escape code '1' for ANSI/TIA/EIA IS-683 PRLs
2 There are two tables in the PRL, an Acquisition Table and a System Table. Figure 6-1
3 shows a conceptual representation of a PRL divided into Geographical areas.
Acquisition
T bl
Geo 4
Geo 3 Geo 2
Geo 1
Carrier -
System
Selection Roaming Acquisition Channels/
Pref Indicator Index INDEX Network Type
(SID, NID) Block
Permitted
10 Note: This system record is no different in format from the existing PRL. The
11 current OTAF platform should treat this as a regular SID.
12 The only element that will understand the special SIDOPER value and act accordingly is
13 the handset.
14 Figure 6-2 shows a sample PRL with the SIDOPER fields entered as part of the system
15 table, one as a permitted system and the other as a forbidden system.
16 The IFAST assigned values of 15904 for SIDOPER-0 and 15905 for SIDOPER-1 have
17 been used.
Ref Doc 86, Ver 1.0 1 April 2004 10
PRL Enhancements for International Roaming Backward Compatibility
Ca rrie r -
Se le c tion Roa m ing Ac quis ition
Sys te m
Pre f Indic a tor Inde x
(SID, NID)
Pe rm itte d
Ca rr ie r - Sys te m
Forbidde n S ID/NID
Sys te m s 15905/44556
S ID/NID
3 The encoding of MCC and IMSI_11_12 into the SID/NID fields shall be performed as
4 follows:
5 If the Most Significant Bit of the MCC is ‘0’, then SIDOPER-0 should be placed on the
6 SID field. The remaining 9 bits of MCC plus 7 bits of IMSI_11_12 (for a total of 16 bits)
7 shall be placed concatenated in the NID field. For example, since SIDOPER-0 = 15904,
8 then:
10 If the Most Significant Bit of the MCC is ‘1’, then SIDOPER-1 should be placed on the
11 SID field. The remaining 9 bits of MCC plus 7 bits of IMSI_11_12 (for a total of 16 bits)
12 shall be placed concatenated in the NID field. For example, since SIDOPER-1 = 15905,
13 then:
15 All the existing rules and features of an existing system table entry will apply to this
16 record (e.g., roaming preferences, forbidden, priority within a GEO, etc.). For existing
17 handsets that do not support this feature, the entry will have no effect.
Ref Doc 86, Ver 1.0 1 April 2004 11
7. Conclusion
1
2 9.1 Example
3 Let’s assume an operator uses the following PRL System Table:
***********SystemTable***********
***********SystemTable***********