(Cdg169) Omh Pri Guidelines

1
Open Market Handsets (OMH)

2 PRI Guidelines
3 (Companion document to CDG169 PRI Workbook)
4 CDG Document 169
5 Version 3.0
6 March 2010
7 CDMA Development Group

8 575 Anton Boulevard, Suite 560
9 Costa Mesa, California 92626
10 PHONE +1 888 800-CDMA
11 +1 714 545-5211
12 FAX +1 714 545-4601
13 http://www.cdg.org
14 cdg@cdg.org
15
16 Notice
17 Each CDG member acknowledges that CDG does not review the
18 disclosures or contributions of any CDG member nor does CDG verify
19 the status of the ownership of any of the intellectual property rights
20 associated with any such disclosures or contributions. Accordingly, each
21 CDG member should consider all disclosures and contributions as being
22 made solely on an as-is basis. If any CDG member makes any use of
23 any disclosure or contribution, then such use is at such CDG member’s
24 sole risk. Each CDG member agrees that CDG shall not be liable to any
25 person or entity (including any CDG member) arising out of any use of
26 any disclosure or contribution including any liability arising out of
27 infringement of intellectual property rights.
1
1<page left blank intentionally>
Ref Doc. 169, Ver. 3.0 March 2010

1 Contents
21. Introduction............................................................................................................................... 1
3 1.1 Purpose and Scope........................................................................................................... 1
4 1.2 Outline............................................................................................................................... 1
52. Handset and R-UIM Identifiers................................................................................................. 3
6 2.1 EFIMSI_M [6F22]................................................................................................................... 3
7 2.2 EFIMSI_T [6F23]................................................................................................................... 4
8 2.3 EFUSGIND [6F42]................................................................................................................. 5
9 2.4 EFMDN [6F44]..................................................................................................................... 5
10 2.5 EFRUIMID [6F31].................................................................................................................. 6
11 2.6 EFRevision [6F39].................................................................................................................. 6
123. Analog Service Information..................................................................................................... 7
13 3.1 EFAH [6F39]....................................................................................................................... 7
14 3.2 EFAOP................................................................................................................................. 7
15 3.3 EFACP................................................................................................................................. 8
164. CDMA Service Information..................................................................................................... 11
17 4.1 EFCDMAHOME [6F28]............................................................................................................ 11
18 4.2 EFACCOLC [6F2C]............................................................................................................... 11
19 4.3 EFTERM [6F2D]................................................................................................................. 12
20 4.4 EFSSCI [6F2E].................................................................................................................. 12
21 4.5 EFPRL [6F30]................................................................................................................... 13
22 4.6 EFMAXPRL [6F45]................................................................................................................ 13
23 4.7 EFSP [6F37]...................................................................................................................... 14
24 4.8 EFECC [6F47].................................................................................................................... 14
25 4.9 EFSSFC [6F3F]................................................................................................................... 15
265. OTASP/OTAPA........................................................................................................................ 17
27 5.1 EFOTAPASPC [6F34]............................................................................................................ 17
28 5.2 EFNAMLOCK [6F35]............................................................................................................. 18
29 5.3 EFOTA [6F36].................................................................................................................... 19
30 5.4 EFSPC [6F33]................................................................................................................... 19
31 5.5 EFSPCS [6F46].................................................................................................................. 20
16. Carrier Customization............................................................................................................. 21
2 6.1 EFSPN [6F41]................................................................................................................... 21
3 6.2 EFAppLabels [6F92].............................................................................................................. 22
47. Root Certificates..................................................................................................................... 25
5 7.1 EFRC [6F91]...................................................................................................................... 25
68. SMS – Basic............................................................................................................................. 27
7 8.1 EFSMSCAP [6F76]............................................................................................................... 27
89. SMS – Broadcast..................................................................................................................... 29
9 9.1 EFBCSMScfg [6F5B]............................................................................................................. 29
10 9.2 EFBCSMSTable [6F5D].......................................................................................................... 29
11 9.3 EFBCSMSP [6F5E].............................................................................................................. 31
1210. 3GPD – Basic......................................................................................................................... 33
13 10.1 EFME3GPDOPC [6F48]........................................................................................................ 33
14 10.2 EF3GPDOPM [6F49]........................................................................................................... 33
15 10.3 EFTCPConfig [6F79]........................................................................................................... 34
16 10.4 EFDGC [6F7A]................................................................................................................. 34
1711. 3GPD – Simple IP.................................................................................................................. 37
18 11.1 EFSIPCAP [6F4A].............................................................................................................. 37
19 11.2 EFSIPSP [6F4E]............................................................................................................... 38
20 11.3 EFSIPUPP [6F4C]............................................................................................................. 38
21 11.4 EFSIPUPPExt [6F7D].......................................................................................................... 39
22 11.5 EFSIPPAPSS [6F50]........................................................................................................... 41
23 11.6 EFSIPCHAPSS [Hidden]...................................................................................................... 42
2412. 3GPD – Mobile IP................................................................................................................... 43
25 12.1 EFMIPCAP [6F4B]............................................................................................................. 43
26 12.2 EFMIPSP [6F4F]............................................................................................................... 44
27 12.3 EFMIPUPP [6F4D]............................................................................................................. 44
28 12.4 EFMIPUPPExt [6F80]........................................................................................................... 47
29 12.5 EFMIPSS [Hidden]............................................................................................................ 49
30 12.6 EFMIPFlags [6F78]............................................................................................................. 50
3113. 3GPD – IPv6........................................................................................................................... 53
32 13.1 EFIPV6CAP [6F77]............................................................................................................. 53
3314. HRPD...................................................................................................................................... 57
34 14.1 EFHRPDCAP [6F56]........................................................................................................... 57
35 14.2 EFHRPDUPP [6F57]........................................................................................................... 57

PRI Guidelines Contents
1 14.3 EFHRPDSS [HIDDEN]....................................................................................................... 58

215. WAP Browser........................................................................................................................ 59
3 15.1 EFWAPBrowserCP [6F7B]...................................................................................................... 59
4 15.2 EFWAPBrowserBM [6F7C]...................................................................................................... 61
516. MMS........................................................................................................................................ 63
6 16.1 EFMMSICP [6F67]............................................................................................................. 63
7 16.2 EFMMSConfig [6F7E].......................................................................................................... 66
817. Java Catalog.......................................................................................................................... 69
9 17.1 EFJDL [6F7F].................................................................................................................. 69
1018. BREW Catalog....................................................................................................................... 71
11 18.1 EFBREWDownload [6F81]...................................................................................................... 71
12 18.2 EFBREWTSID [6F82]........................................................................................................... 74
13 18.3 EFBREWSID [6F83]............................................................................................................ 75
14 18.4 EFBREWAEP [6F89]........................................................................................................... 75
1519. Location Based Services...................................................................................................... 77
16 19.1 EFLBSXTRAConfig [6F84]...................................................................................................... 77
17 19.2 EFLBSXSURL [6F85]........................................................................................................... 78
18 19.3 EFLBSV2Config [6F86]......................................................................................................... 79
19 19.4 EFLBSV2PDEADDR [6F87]..................................................................................................... 80
20 19.5 EFLBSV2MPCADDR [6F88]..................................................................................................... 81
2120. Terminology.......................................................................................................................... 83
2221. References............................................................................................................................. 87
23
24
25

PRI Guidelines Contents
1 Revision History
Date Version Description
March 2010 3.0  This CDG169 PRI Guidelines document was

created as a companion document to the
CDG169 PRI Workbook. The two documents
should always be used together. Originally this
information was in the CDG169 PRI Workbook.
Having a separate companion document allows
for more complete guidelines, examples, etc. to
assist operators in completing the PRI Workbook.

1 1. Introduction
21.1 Purpose and Scope
3This document provides guidelines and recommendations to operators for provisioning
4parameters in R-UIM cards. It also provides a detailed description of each of the
5parameters listed in [CDG169 Part 1] and meaningful information regarding these
6parameters and their significance.
7This document is targeted toward operators who need to:
8  understand what a particular parameter is used for,
9  know the typical values (or range of values),
10  understand the reason behind the choice of typical values, and
11  learn the tradeoffs, if any, in setting these parameters to values other than those
12 recommended.
131.2 Outline
14A standard template is used for each parameter description, as follows:
15Definition: Brief explanation of the parameter
16Allowed Range: The permitted range and unit of each parameter
17Typical Value: The single value the parameter needs to be set to, which is most
18commonly used by operators
19Notes:
20  A brief description of the tradeoffs involved in the setting of this parameter, providing
21 an explanation of the effects of setting it “too high” and “too low,” beyond the normal
22 operating range
23  Any other remarks on the parameter setting (e.g., common mistakes, other useful
24 information)
25

1
2
3
4 <page left blank intentionally>
5

1 2. Handset and R-UIM Identifiers
22.1 EFIMSI_M [6F22]
3Definition: This EF stores the five components of IMSI_M. An IMSI_M is always a class
40 IMSI.
5Size (bytes): 10 (fixed)
62.1.1 IMSI_M_CLASS
7Definition: This parameter identifies the class assignment of the International Mobile
8Station Identity (IMSI). An IMSI that is 15 digits in length is called a class 0 IMSI [the
9National Mobile Station Identity (NMSI) is 12 digits in length]; an IMSI that is less than 15
10digits in length is called a class 1 IMSI.
11Allowed Range: 0, 1
12Typical Value: 0
132.1.2 IMSI_M_S
14Definition: This parameter identifies a 10-digit (34-bit) number derived from the IMSI.
15When an IMSI has 15 digits, IMSI_S is equal to the least significant 10 digits of the IMSI.
16When an IMSI has fewer than 15 digits, zeros are added to the most significant side of
17MSIN to obtain a 15-digit padded IMSI; IMSI_S is equal to the last 10 digits of the
18padded IMSI.
19Allowed Range: Ten decimal digits
20Typical Value: Operator specific
212.1.3 IMSI_M_11_12 (MNC)

22Definition: This parameter comprises the 11th and 12th digits from the right of the IMSI
23address.
24Allowed Range: Two decimal digits
26Note: This is also known as Mobile Network Code (MNC) and is assigned by the
27International Telecommunication Union (ITU) to the operator.

12.1.4 IMSI_M_MCC
2Definition: This parameter identifies the Mobile Country Code (MCC).
3Allowed Range: Three decimal digits
4Typical Value: The MCC is assigned by the ITU.
52.2 EFIMSI_T [6F23]

6Definition: IMSI_T is an IMSI that is not associated with the Mobile Identification
7Number (MIN) assigned to the mobile station.
92.2.1 IMSI_T_CLASS
10Definition: This parameter identifies the Class assignment of the IMSI.
11Allowed Range:
12  0
13  1
14Typical Value: 0
15Note: An IMSI_T can be a class 0 or class 1 IMSI.
162.2.2 IMSI_T_S
17Definition: This parameter identifies the last 10 digits of the IMSI. These are the same
1810 digits as the directory number.
19Allowed Range: Ten decimal digits
212.2.3 IMSI_T_11_12
22Definition: This parameter comprises the 11th and 12th digits from the right of the IMSI
23address.
24Allowed Range: Two decimal digits
25Typical Value: This is assigned by the ITU.
262.2.4 IMSI_T_MCC
27Definition: This parameter identifies the Country Code.
28Allowed Range: Three decimal digits
29Typical Value: This is assigned by the ITU.

PRI Guidelines CDMA Service Information
12.3 EFUSGIND [6F42]

2Definition: This EF contains the Removable UIM_ID/SF_EUIMID Usage Indicator.
42.3.1 Handset Authentication Indicator

5Definition: This parameter indicates whether to use ESN_ME or UIM_ID for Cellular
6Algorithms for Validation and Encryption (CAVE) authentication and MS identification.
7Allowed Range:
8  ESN_ME
9  UIM_ID
10Typical Value: Always use UIM_ID for OMH.
11Note: For OMH devices, this should always be set to UIM_ID and not ESN.
122.3.2 Handset Identification Indicator

13Definition: This parameter indicates whether to use MEID or SF_EUIMID to identify the
14mobile station (MS).
15Allowed Range:
16  MEID
17  SF_EUIMID
18Typical Value: Always use SF_EUIMID for OMH.
192.4 EFMDN [6F44]

20Definition: This parameter indicates the dialable number associated with the mobile
21station through a service subscription. A Mobile Directory Number (MDN) is not
22necessarily the same as the mobile station identification on the air interface, i.e., MIN,
23IMSI_M, or IMSI_T. An MDN consists of up to 15 digits. The mobile station should have
24memory to store at least one MDN.
262.4.1 Mobile Directory Number

27Definition: This parameter indicates the MDN.
28Allowed Range: 15 decimal digits programmable
302.4.2 Mobile Directory Number Type

31Definition: This parameter indicates the MDN Type.

1Allowed Range:
2  National
3  International
4  Unknown
62.4.3 Mobile Directory Number Plan

7Definition: This parameter indicates the MDN Plan.
8Allowed Range:
9  Telephony
10  Private
11  Unknown
132.5 EFRUIMID [6F31]

14Definition: This EF contains the R-UIM Identifier.
162.5.1 R-UIM Identifier

17Definition: This parameter contains the R-UIM Identifier.
18Allowed Range: 32-bit number
19Typical Value: This is not to be provisioned by the operator; the value depends on the
20particular R-UIM card vendor.
212.6 EFRevision [6F39]

22Definition: This EF contains the revision number of the R-UIM.
242.6.1 R-UIM Revision

25Definition: This parameter contains the revision number of the R-UIM.
26Allowed Range: 0255
27Typical Value: 00000100 (R-UIM complying with [CS0023-D])
28Note: This allows the mobile equipment (ME) to communicate with different versions of
29the R-UIM (i.e., R-UIM with different set of capabilities).
30
31

1 3. Analog Service Information
23.1 EFAH [6F39]
3These EFs pertain to Analog. Since none of the operators are using AMPS, they do
4not need to be provisioned.
5Definition: This EF indicates the Analog Home SID.
73.1.1 Analog Home SID

8Definition: This parameter indicates the Cellular Service Provider analog home system
9ID for the given NAM. This is automatically filled from the CDMA Home SID.
10Allowed Range: 5 decimal digits from 065535
123.2 EFAOP
13Definition: This EF indicates the Analog Operational Parameters, namely, Extended
14Address bit (Exp), the Local Use Mark (LCM), and the Group ID (GID) field.
163.2.1 Extended Address

17Definition: This parameter specifies whether the Extended Address bit is enabled.
18Allowed Range:
19  True
20  False
21Typical Value: False
223.2.2 Local Use Mark

23Definition: This parameter specifies whether the Local Use Mark bit is enabled.
24Allowed Range:
25  True
26  False
23.2.3 Group ID
3Definition: This parameter indicates whether the Group ID bit is enabled or not.
5Typical Value: Operator Specific
63.3 EFACP
7Definition: This EF indicates the Analog Mode Channel Preferences, as determined by
8the service3 provider in accordance with the terms of the subscription. The items
9addressed are the Analog Initial Paging Channel, the Analog First Dedicated Control
10Channel for System A, the Analog First Dedicated Control Channel for System B, and
11the Number of Dedicated Control Channels to scan.
12Size (bytes): 7 (fixed) [CS0023-D]
133.3.1 Analog Initial Paging Channel

14Definition: This parameter indicates the Analog Initial Paging Channel.
173.3.2 Analog First Dedicated Control System A

18Definition: This parameter indicates the Analog First Dedicated Control Channel
19System A.
223.3.3 Analog First Dedicated Control System B

23Definition: This parameter indicates the Analog First Dedicated Control Channel
24System B.
273.3.4 Analog Number of DCC

28Definition: This parameter identifies the Analog Number of the Dedicated Control
29Channel to scan.


3

1
2
3
4
6

1 4. CDMA Service Information
24.1 EFCDMAHOME [6F28]
3Definition: This EF indicates the CDMA Home System Identification (SID) and Network
4Identification (NID) when the mobile station is operating in CDMA mode.
5Size (bytes): 5 x # of records
64.1.1 Home SID and NID

7Definition: This parameter indicates the Home SIDs and NIDs for the given NAM.
8Allowed Range: Multiple pairs of up to 5 decimal digits, ranging from 032767; with
9corresponding Band Class.
10Typical Value: 4–6 pairs
11Note: The first SID cannot be 0. SIDs must be all even or all odd.
124.1.2 Band Class

13Definition: This parameter indicates the band class supported.
14Allowed Range: This is a 1 byte field that represents the corresponding Band Class.
164.2 EFACCOLC [6F2C]

17Definition: This EF indicates the 4-bit Access Overload Class indicator (ACCOLCp),
18which is used to identify which overload class controls access attempts by the mobile
19station and is used to identify redirected overload classes in global service redirection.
20The mobile station shall store the 4-bit access overload class (ACCOLCp). Mobile
21stations that are not for test or emergency use should be assigned to overload classes
22ACCOLC 0 through ACCOLC 9. For mobile stations that are classified as overload
23classes ACCOLC 0 through ACCOLC 9, the mobile station’s 4-bit access overload class
24indicator (ACCOLCp) shall be automatically derived from the last digit of the associated
25decimal representation of the IMSI_M by a decimal to binary conversion, as specified in
26[CS0005-A].

14.2.1 Access Overload Class
2Definition: This parameter indicates the Access Overload Class (ACCOLCp).
3Allowed Range: 4-bit access overload class indicator.
4Typical Value: The value is derived from the last digit of the associated decimal
5representation of the IMSI_M.
64.3 EFTERM [6F2D]

7Definition: This EF indicates the Call Termination Mode Preferences.
94.3.1 Home SID Term Reg

10Definition: This parameter indicates the CDMA mobile-terminated home SID
11registration.
12Allowed Range:
13  True
14  False
15Typical Value: True
164.3.2 Foreign SID Term Reg

17Definition: This parameter indicates the CDMA mobile-terminated foreign SID
18registration.
19Allowed Range:
20  True
21  False
234.3.3 Home NID Term Reg

24Definition: This parameter indicates the CDMA mobile-terminated home NID
25registration.
26Allowed Range:
27  True
28  False

14.4 EFSSCI [6F2E]

2Definition: This EF indicates the Suggested Slot Cycle Index.
44.4.1 Slot Cycle Index

5Definition: This parameter indicates the duration and frequency that the phone checks
6the paging channel.
7Allowed Range: 2 decimal digits, range 07
8Typical Value: 2
94.5 EFPRL [6F30]

10Definition: This EF stores the Preferred Roaming List.
11Size (bytes): MAX_PRL_LIST_SIZE.
12Note: See Section 4.6, EFMAXPRL [6F45].
134.5.1 PR_LIST
14Definition: This parameter indicates the Preferred Roaming List. See [CS0016-C]. This
15may contain IS-683A PRL for 1x only devices or Concatenated PRL (cPRL) with IS-
16683A PRL and IS-683C PRL for EV-DO devices. See the appendix in [CDG167] for
17more information on cPRL.
18Allowed Range: This is the actual PRL.
19Typical Value: Operator specific.
204.6 EFMAXPRL [6F45]

21Definition: This EF indicates the maximum size for EFPRL and EFEPRL.
234.6.1 Maximum PRL Size for EFPRL

24Definition: This EF indicates the maximum PRL size for EFPRL. The mobile station shall
25set this field to the maximum size, in octets, that the mobile station can support for the
26preferred roaming list (PR_LISTs-p).
28Typical Value: 67k (For both 1X and EVDO systems)
29Note: Operator to specify based upon entries in PRL.

14.6.2 Maximum PRL Size for EFEPRL (not used in OMH context)
24.7 EFSP [6F37]

3Definition: This EF identifies Service Preferences.
54.7.1 System A/B Preference

6Definition: This EF indicates the System A/B Preference.
7Allowed Range:
8  No preference
9  A preferred
10  B preferred
11  A only
12  B only
13Typical Value: No preference
144.7.2 Analog/CDMA Preference

15Definition: This EF indicates the Analog/CDMA Preference.
16Allowed Range:
17  No preference
18  Analog preferred
19  CDMA preferred
20  Analog only
21  CDMA only
22Typical Value: CDMA Preferred
234.8 EFECC [6F47]

24Definition: This EF identifies Emergency Call Codes.
25Size (bytes): 3n (n <=5)
264.8.1 Emergency Call Codes

27Definition: This EF identifies Emergency Call Codes and contains up to five emergency
28call codes. Each digit is encoded in BCD format. The emergency call code is of a
29variable length with a maximum length of 6 digits. Each emergency call code is coded on
30three bytes, with each digit within the code being coded on four bits as shown below. If a
31code of fewer than 6 digits is chosen, then the unused nibbles shall be set to “F.”

1Allowed Range: 05 emergency call codes wherein each emergency call code is a
2maximum of 6 digits
44.9 EFSSFC [6F3F]

5Definition: This EF identifies the Supplementary Services Feature Code Table. It stores
6the numeric feature code to be used by the ME when a supplementary service is
7invoked in CDMA or analog mode via an implementation-dependent user interface (such
8as a menu) that automatically inserts a feature code into the dialed digit string. Because
9feature codes are service-provider specific, this EF is required to enable the ME to
10perform the mapping to the feature code.
11When a supplementary service is invoked in CDMA or analog mode, the mobile station
12shall determine the feature code by reading the Supplementary Service Feature Code
13Table entry for the selected supplementary service, and pre-pending with an asterisk.
14Size (bytes): Variable
15Note: A feature code of up to four digits shall be encoded via BCD into the two bytes of
16the feature code table entry as follows:
17  Represent these four digits as D1D2D3D4.
18  If a feature code (FC) of fewer than four digits is used, the digits shall be right justified
19 and the unused digits shall be set to “F.”
20The following feature codes are available, each with a maximum size of 4 decimal digits:
21  CD Activate – Feature Code: Call Delivery
22  CD De-Activate – Feature Code: Call Delivery
23  CFB Register New Forward-to Number – Feature Code: Call Forwarding – Busy
24  CFB Register to Voice Mail – Feature Code: Call Forwarding – Busy
25  CFB De-Register – Feature Code: Call Forwarding – Busy
26  CFB Activate – Feature Code: Call Forwarding – Busy
27  CFB De-Activate – Feature Code: Call Forwarding – Busy
28  CFD Register New Forward-to Number – Feature Code: Call Forwarding – Default
29  CFD Register to Voice Mail – Feature Code: Call Forwarding – Default
30  CFD De-Register – Feature Code: Call Forwarding – Default
31  CFD Activate – Feature Code: Call Forwarding – Default
32  CFD De-Activate – Feature Code: Call Forwarding – Default
33  CFNA Register New Forward-to Number – Feature Code: Call Forwarding – No
34 Answer
35  CFNA Register to Voice Mail – Feature Code: Call Forwarding – No Answer
36  CFNA De-Register – Feature Code: Call Forwarding – No Answer
37  CFNA Activate – Feature Code: Call Forwarding – No Answer

1  CFNA De-Activate – Feature Code: Call Forwarding – No Answer

2  CFU Register New Forward-to Number – Feature Code: Call Forwarding –
3 Unconditional
4  CFU Register to Voice Mail – Feature Code: Call Forwarding – Unconditional
5  CFU De-Register – Feature Code: Call Forwarding – Unconditional
6  CFU Activate – Feature Code: Call Forwarding – Unconditional
7  CFU De-Activate – Feature Code: Call Forwarding – Unconditional
8  CW Activate – Feature Code: Call Waiting
9  CW De-Activate – Feature Code: Call Waiting
10  CW Cancel (Temporarily) – Feature Code: Cancel Call Waiting
11  CNIR Activate (per-call blocking) – Feature Code: Calling Number ID Restriction
12  CNIR De-Activate (per-call allowed) – Feature Code: Calling Number ID Restriction
13  CC Invoke – Feature Code: Conference Calling
14  CC Invoke Drop Last Party – Feature Code: Conference Calling
15  DND Activate – Feature Code: Do Not Disturb
16  DND De-Activate – Feature Code: Do Not Disturb
17  MWN Activate Alert Pip Tone – Feature Code: Message Waiting Notification
18  MWN De-Activate Alert Pip Tone – Feature Code: Message Waiting Notification
19  MWN Activate Pip Tone – Feature Code: Message Waiting Notification
20  MWN De-Activate Pip Tone – Feature Code: Message Waiting Notification
21  MWN Cancel (Temporarily) – Feature Code: Cancel Message Waiting Notification
22  PACA Invoke – Feature Code: Priority Access and Channel Assignment
23  VMR Invoke – Feature Code: Voice Message Retrieval
24  CNAP Activate – Feature Code: Calling Name Presentation
25  CNAP De-Activate – Feature Code: Calling Name Presentation
26  CNAR Activate – Feature Code: Calling Name Restriction
27  CNAR De-Activate – Feature Code: Calling Name Restriction
28  AC Activate – Feature Code: Automatic Callback
29  AC De-Activate – Feature Code: Automatic Callback
30  AR Activate – Feature Code: Automatic Recall
31  AR De-Activate – Feature Code: Automatic Recall
32  USCF Register New Directory Number – Feature Code: User Selectable Call
33 Forwarding
34  RUAC Activate – Feature Code: Rejection of Undesired Annoying Calls
35  RUAC De-Activate – Feature Code: Rejection of Undesired Annoying Calls
36  AOC Invoke – Feature Code: Advice of Charge
37  COT Invoke – Feature Code: Invoke Call Trace
38For a complete list of features, see [CS0023-D].

1 5. OTASP/OTAPA
25.1 EFOTAPASPC [6F34]
3Definition: This EF identifies OTAPA/SPC_Enable Settings. It contains user-entered
4control information that either prevents or (else) permits network manipulation of the
5Service Programming Code (SPC), and either prevents or (else) permits OTAPA to be
6performed on the NAM.
85.1.1 OTAPA_Enable
9Definition: This sets forth user-entered control information that either prevents or (else)
10permits Over-the-Air Parameter Administration (OTAPA) to be performed on the NAM.
11Allowed Range:
12  True
13  False
15Note: For OTAPA_Enable, a value of “0” for the NAM indicates that the user consents to
16the performance of OTAPA for the NAM by the service provider. A value of “1” indicates
17that the user does not permit OTAPA to be performed on the NAM.
185.1.2 SPC_Change_Enable
19Definition: This EF sets forth user-entered control information that either prevents or
20(else) permits network manipulation of the SPC.
21Allowed Range:
22  True
23  False
25Note: For SPC_Change Enable, a value of “0” for the R-UIM indicates that the user
26consents to allow the service provider to change the value of the SPC. A value of “1”
27indicates that the user denies permission for the service provider to change the value of
28the SPC.

15.2 EFNAMLOCK [6F35]
2Definition: This EF identifies NAM_LOCK Settings.
45.2.1 Current NAM Lock State

5Definition: This indicates whether NAM is locked by the Subscriber Parameter
6Administration Security Mechanism (SPASM).
7Allowed Range:
8  Locked
9  Unlocked
10Typical Value: Locked
11Note: A value of “1” indicates that the NAM is locked by the SPASM protection
12mechanism. A value of “0” indicates that the NAM is unlocked.
135.2.2 Permanent NAM Lock Setting

14Definition: This indicates whether or not the SPASM protection mechanism must be
15satisfied for network-initiated OTA.
16Allowed Range:
17  On
18  Off
19Typical Value: On
20Note: A value of “1” indicates that the SPASM protection mechanism must be satisfied
21for network-initiated OTA. A value of “0” indicates that SPASM protection is not required.
225.2.3 Current OTA Mode

23Definition: This indicates whether the current OTA session is network- or user-initiated.
24Allowed Range:
25  Network-initiated
26  User-initiated
27Typical Value: User-initiated
28Note: A value of “0” indicates user-initiated, and a value of “1” indicates network-
29initiated.

15.3 EFOTA [6F36]

2Definition: This EF identifies OTASP/OTAPA features. The EF stores a listing of the
3following OTASP/OTAPA features supported by the R-UIM, along with protocol revision
4codes, each with an allowed range of 0–255:
5  DATA_P_REV ID – OTA Feature: NAM Download
6  DATA_P_REV – OTA Feature: NAM Download
7  A_KEY_P_REV ID – OTA Feature: Key Exchange
8  A_KEY_P_REV – OTA Feature: Key Exchange
9  SSPR_P_REV – OTA Feature: System Selection for Preferred Roaming
10  SPL_P_REV ID – OTA Feature: Service Programming Lock
11  SPL_P_REV – OTA Feature: Service Programming Lock
12  OTAPA_P_REV ID – OTA Feature: OTAPA
13  OTAPA_P_REV – OTA Feature: OTAPA
14  PUZL_P_REV ID – OTA Feature: Preferred User Zone List
15  PUZL_P_REV – OTA Feature: Preferred User Zone List
16  3GPD_P_REV ID – OTA Feature: 3GPD
17  3GPD_P_REV – OTA Feature: 3GPD
18  SECURE_MODE_P_REV ID – OTA Feature: Secure MODE
19  SECURE_MODE_P_REV – OTA Feature: Secure MODE
20Size (bytes): 2N+1 (where N is the number of OTASP/OTAPA features supported)
215.4 EFSPC [6F33]

22Definition: This EF includes the Service Programming Code (SPC).
245.4.1 Service Programming Code

25Definition: This parameter cites the security code that provides access to service
26programming for individual service provider networks.
27Allowed Range: 6 decimal digits from 09, random
29Note: The SPC is a simple means to protect the contents of the R-UIM from being
30programmed without authorization.

15.5 EFSPCS [6F46]

2Definition: This EF identifies the Security Programming Code Status. This identifies
3whether the EFSPC (Service Programming Code) is set to default and internally updated
4in the card to reflect the current state of SPC after an OTASP commit if the SPC was
5changed.
75.5.1 SPC Status

8Definition: This parameter identifies the Security Programming Code Status.
9Allowed Range:
10  OFF: SPC has the default value
11  ON: SPC is set to other value
12Typical Value: ON
13

1 6. Carrier Customization
26.1 EFSPN [6F41]
3Definition: This EF identifies the CDMA Home Service Provider Name (SPN). The
4operator should allocate n17 in EF_CST and provision the following parameters, if
5CDMA Home service provider name is to be displayed when the MS is in the Home
6Service area.
86.1.1 SPN Display Condition

9Definition: This indicates whether or not a Service Provider Name should be displayed
10when the MS is registered in the home service area.
11Allowed Range:
12  OFF: display is not required
13  ON: display is required
14Typical Value: ON
156.1.2 SPN Character Encoding

16Definition: This contains encoding for the SPN string.
17Allowed Range:
18  7-bit ASCII
19  IA5
20  UNICODE
21Typical Value: 7-bit ASCII
226.1.3 SPN Language Indicator

23Definition: This contains the Language Indicator for the SPN string.
24Allowed Range:
25  English
26  French
27  Spanish

1  Japanese
2  Korean
3  Chinese
4  Hebrew
5Typical Value: English
66.1.4 SPN String

7Definition: This contains the actual Service Provider Name string.
8Allowed Range: 32-byte string
9Typical Value: The value needs to be specified by the Operator.
106.2 EFAppLabels [6F92]

11Definition: Application Labels are used for carrier customization. They are used by
12devices to display operator-branded services. The text label the operator desires to
13provision in this EF is the text associated with the icon or menu item used to launch the
14application, such as BREW, MMS, Browser, etc.
15These labels are optional and need only be provisioned if an operator desires to override
16the handset vendor-defined labels.
17Note: In the absence of the application labels provisioned by an operator, the device will
18display the default values.
19Size (bytes): 4+N*32 (where N is the number of application labels)
20  Typical EF Size (bytes): 132 bytes (assumes 4 application labels)
21  Maximum EF Size (bytes): 516 byes (assumes 16 application labels)
226.2.1 App Label Character Encoding

23Definition: This parameter specifies the encoding for Application Labels.
24Allowed Range:
25  Octet (unspecified)
26  7-bit ASCII
27  IA5
28  UNICODE unspecified

16.2.2 Language of App Labels

2Definition: This parameter specifies the Language in which application labels are
3provisioned.
4Allowed Range:
5  English
6  French
7  Spanish
8  Japanese
9  Korean
10  Chinese
11  Hebrew
136.2.3 MMS App Label

14Definition: This parameter specifies the text label for the MMS application icon or menu
15item.
186.2.4 WAP Browser App Label

19Definition: This parameter specifies the text label for the WAP Browser application or
20menu item.
236.2.5 BREW App Label

24Definition: This parameter specifies the text label for the BREW application downloader
25icon or menu item.
286.2.6 Java App Label

29Definition: This parameter specifies the text label for the Java application downloader
30icon or menu item.

1
2
3

1 7. Root Certificates
27.1 EFRC [6F91]
3Definition: The root certificates are used for operator-signed applications. If the same
4root certificate is used for all operator-signed applications, then the application bit mask
5is set to “Unspecified.” If not, the application bit for each application shall be set
6accordingly.
7The operator should allocate n16 in EF_CST and provision the following parameters, if
8root certificates are to be used on its network.
9Note: Root certificates are not mandatory for operators to use. Only in cases where the
10operator’s applications are signed using root certificates they would need to be
11provisioned.
12Size (bytes): Typical EF size (bytes): 1500 bytes (assumes one 1.5kB certificate)
137.1.1 Certificate Type

14Definition: This parameter identifies the type of certificate.
15Allowed Range:
16  DER Encoded Binary X.509
17  Base64 Encoded X.509
18  PKCS #7
19  PKCS #12
20Typical Value: This is the actual certificate type used by the operator.
217.1.2 Certificate Information

22Definition: This is the actual certificate used by the operator encoded according to the
23type specified in Section 7.1.1
24Allowed Range: N/A
25Typical Value: N/A
267.1.3 Associated Applications

27Definition: This parameter identifies which applications are associated with this
28certificate. One, multiple, or all applications may be associated with a certificate.

1Allowed Range: 1 or more of the following:
2  Unspecified (i.e., all)
3  WAP Browser
4  BREW
5  Java
6  LBS
7  Terminal
8Typical Value: This parameter identifies the applications selected by an operator to use
9with the actual certificate defined in Section 7.1.2.

1 8. SMS – Basic
28.1 EFSMSCAP [6F76]
3Definition: The operator should allocate n4 in EF_CST and provision the following
4parameters, if SMS service is supported on its network.
68.1.1 SMS Retry Period

7Definition: This is the overall time period (in seconds) during which the Mobile
8Originated (MO) SMS retries can be performed. A value of “0” implies that MO SMS retry
9is disabled.
10Allowed Range: 0255 seconds
11Typical Value: 3060 seconds
12Note: The SMS retry period needs to be larger than the SMS retry interval period.
138.1.2 SMS Retry Interval

14Definition: This is the time interval (in seconds) that the device shall wait before the
15next retry attempt can be made after an MO SMS failure.
16Allowed Range: 0–255 seconds
17Typical Value: 35 seconds
18Note: The SMS retry interval needs to be smaller than SMS retry period. Setting this to a
19value smaller than 5 seconds could lead to multiple SMS originations being sent before
20a delayed acknowledgment to the previous SMS attempt is received.
218.1.3 SMS Send on Access Flag

22Definition: This flag indicates whether the operator wants to allow messages to be sent
23over Access Channel.
24Allowed Range:
25  True
26  False

18.1.4 SMS Send on Traffic Flag
2Definition: This flag indicates whether the operator wants to allow messages to be sent
3over Traffic Channel.
4Allowed Range:
5  True
6  False
88.1.5 SMS Send Standard EMS Flag

9Definition: This parameter specifies whether to allow Long SMS (LMS) messages to be
10sent as standard Enhanced Messaging Service (EMS) messages.
11Allowed Range:
12  True
13  False
14Typical Value: False (unless operator’s network supports EMS)
158.1.6 SMS Preferred Service Option

16Definition: This is the preferred service option to be used by the device when it sets up
17SMS traffic channel for sending SMS.
18Allowed Range:
19  Device Default
20  Service Option 6
21  Service Option 14
22Typical Value: Service Option 6
23Note: This is what the device uses for origination, but the traffic channel assignment
24sent by the BS will override the service option if different from that used by the device.

1 9. SMS – Broadcast
29.1 EFBCSMScfg [6F5B]
3Definition: Broadcast SMS messages are messages sent by the Base Station (BS) to
4the Mobile Stations. They can be sent on the Paging Channel, Forward Common Control
5Channel, or the Broadcast Control Channel. These messages can also be sent to
6individual mobile stations on the Forward Traffic Channel.
8Broadcast SMS service is supported on its network.
109.1.1 Broadcast SMS Config

11Definition: This indicates the operator broadcast configuration setting for Broadcast
12SMS. This information, determined by the operator, defines the filtering criteria that can
13be used by the ME to receive Broadcast SMS.
14Allowed Range:
15  Disallow
16  Allow table only
17  Allow all
18Typical Value: Allow All
19Note: The choices in the allowed range indicate the following:
20  Disallow: This setting disables the mobile station’s broadcast SMS capability (i.e.,
21 the mobile station will not process broadcast SMS).
22  Allow Table Only: This setting allows the mobile station to receive only broadcast
23 messages for the service categories that have been programmed in EFBCSMStable.
24  Allow All: This setting allows the mobile station to receive broadcast messages for
25 all service categories.
269.2 EFBCSMSTable [6F5D]

27Definition: This EF contains information in accordance with comprising service category
28program parameters, which can be used by the ME for Broadcast SMS filtering.

19.2.1 Service Information: Category
2Definition: This field contains the value of the Service Category for the operation.
3  UNKNOWN
4  EMERGENCY
5  ADMIN
6  MAINTENANCE
7  General News – Local
8  General News – Regional
9  Etc.
11Note: Note that the list of categories above is only a subset and not the complete list
129.2.2 Service Information: Language

13Definition: This parameter specifies the Language used for the message text.
14Allowed Range:
15  English
16  French
17  Spanish
18  Japanese
19  Korean
20  Chinese
21  Hebrew
22Typical Value: English
239.2.3 Service Information: Max Messages

24Definition: This field shall be set to the Maximum Number of Messages that may be
25stored in the ME for this service category.
26Allowed Range: 0–255
27Typical Value: 255

19.2.4 Service Information: Alert Option

2Definition: This parameter specifies the alert option to be used when the mobile station
3receives a message for this service category. This field shall be set according to Table
44.5.19-1 of [CS0015-B].
5Allowed Range:
6  NONE
7  MS Default Alert
8  VIBRATE_ONCE
9  VIBRATE_REPEAT
10  VISUAL_ONCE
11  VISUAL_REPEAT
12  LOW_PRIORITY_ONCE
13  LOW_PRIORITY_REPEAT
14  MEDIUM_PRIORITY_ONCE
15  MEDIUM_PRIORITY_REPEAT
16  HIGH_PRIORITY_ONCE
17  HIGH_PRIORITY_REPEAT
199.2.5 Service Information: Label Encoding

20Definition: This parameter defines the encoding scheme used for the label.
21Allowed Range:
22  7-bit ASCII
23  IA5
24  UNICODE
269.2.6 Service Information: Label

27Definition: This is the actual text specified by the operator for the service.
28Allowed Range: Up to 258 bytes of characters
309.3 EFBCSMSP [6F5E]

31Definition: This EF specifies the parameters used for the Broadcast SMS.
32Size (bytes): 2 (record)

19.3.1 Service Information: Selected Flag

2Definition: This parameter indicates whether service is selected or not by the operator.
3Allowed Range:
4  True
5  False
79.3.2 Service Information: Priority

8Definition: This parameter identifies the priority level of service.
9Allowed Range:
10  Normal
11  Urgent
12  Emergency
13Typical Value: Normal
14

1 10. 3GPD – Basic
210.1 EFME3GPDOPC [6F48]
3Definition: If either service n20 or n38 is allocated (see Section 3.4.18 of [CS0023-D]),
4this EF shall be present. This parameter specifies the operation modes supported by the
5ME. The ME sets this field in the form of a bitmap as defined in [CS0016-B].
710.1.1 3GPD Operation Capability

8Definition: This EF stores IP operation capabilities supported by the ME. After the
9selection of DFCDMA (7F25) during the initialization, the R-UIM shall set the value of
10this byte to “0.” Mobile equipment that supports Simple IP or Mobile IP shall set each
11subfield to “1” if it supports the corresponding operating mode.
12Allowed Range: One or more of the following:
13  SimpleIP Supported
14  MobileIP Supported
15  MobileIP with SimpleIP Fallback supported
16Typical Value: Does not need to be provisioned by the operator
1710.2 EF3GPDOPM [6F49]

18Definition: If either service n20 or n38 is allocated (see Section 3.4.18 of [CS0023-D]),
19this EF shall be present.
2110.2.1 3GPD Operation Mode

22Definition: This EF stores the 3GPD Operation Mode Parameter Block. For further
23details, refer to 3GPP2 [CS0016-B] and [CS0023-D].
24Allowed Range:
25  SimpleIP
26  MobileIP
27  MobileIP with SimpleIP Fallback
28Typical Value: Simple IP

110.3 EFTCPConfig [6F79]
2Definition: This EF contains information about Transmission Control Protocol (TCP)
3configurations. If service n20 (3GPD-SIP) or n38 (3GPD-MIP) is allocated and service
4n15 (Messaging and 3GPD Extensions) is allocated, this EF shall be present.
610.3.1 TCP Graceful Close of Dormant Connections

7Definition: This parameter specifies whether the TCP socket should be closed
8gracefully, even if the underlying interface is dormant.
9Allowed Range:
10  True
11  False
13Note: If the value of this flag is TRUE, this means that the TCP socket should be closed
14gracefully. This in turn means that the network connection will be brought out of
15dormancy and the TCP FIN will be sent out on the network. If the value of this flag is set
16to FALSE, the local TCP connection will be closed forcefully without going through the
17TCP graceful close cycle.
1810.3.2 TCP Keep Alive Idle Timer

19Definition: This configuration item is used primarily to deal with dead TCP peers. If
20there is no TCP message being sent from the peer for the “TCP Keep Alive Idle Timer,”
21then keep-alive probes will be sent to the peer. With a default value of 120 minutes, the
22mobile would not send keep-alive probes for at least 120 minutes when there is no TCP
23activity from the remote end.
24Allowed Range: 0–255 minutes
25Typical Value: 120 minutes
26Note: A value of 0 means that the TCP keep-alive feature is disabled on the ME.
2710.4 EFDGC [6F7A]

28Definition: This EF specifies miscellaneous data configuration items.
3010.4.1 Data Dormant Timer

31Definition: This parameter specifies the number of seconds to wait before going into
32data dormant mode, which shall be at least 20 seconds.


2Typical Value: 30 seconds
310.4.2 EPZID Type

4Definition:
5Allowed Range:
6  Packet Zone ID
7  Packet Zone ID plus SID
8  Packet Zone ID plus SID and NID
9Typical Value: Packet Zone ID plus SID and NID
1010.4.3 Hysteresis Activation Time

11Definition: This parameter specifies the number of seconds the device should wait
12before it adds a new Packet Zone ID.
14Typical Value: 30 seconds
15

1
2
3
5

1 11. 3GPD – Simple IP
211.1 EFSIPCAP [6F4A]
3Definition: This parameter specifies the SimpleIP Capability Parameter Block defined in
4[CS0016-C].
63GPD Simple IP is supported on its network.
811.1.1 Simple IP Max Number of NAIs

9Definition: This parameter defines the total number of Network Address Identifiers
10(NAIs) that an operator intends to use. If an operator needs to specify different
11NAIs/usernames for the different applications or groups of applications, then multiple
12profiles are used.
15Note: Most operators worldwide use a single NAI/username profile shared by all
16applications. In cases where an operator requires a separate NAI/password profile for
17each of the applications (or groups of applications) requiring differing treatment1 at the
18network end, multiple profiles may be used.
1911.1.2 SIP Max NAI Length

20Definition: This parameter specifies the maximum length of Simple IP NAI. This value
21specifies the maximum memory allocated in the card for this field.
2411.1.3 SIP Max SS Length

25Definition: This parameter specifies the maximum length of the Simple IP password.
26This value specifies the maximum memory allocated in the card for this field.
11 Billing, Routing, etc.

2Typical Value: 31
311.1.4 SIP Authentication Algorithms

4Definition: This parameter specifies the authentication algorithm used for PDSN
5authentication.
6Allowed Range:
7  PAP
8  CHAP
9  CHAP & PAP
10Typical Value: CHAP & PAP both
1111.2 EFSIPSP [6F4E]

12Definition: This EF stores the SimpleIP Status Parameters Block defined in [CS0016-B].
13If service n20 is allocated, this EF shall be present.
1511.2.1 ACT_NAI_ENTRY_INDEX
16Definition: This specifies the active SimpleIP NAI entry index.
18Typical Value: 0 (when all applications are using one profile)
1911.3 EFSIPUPP [6F4C]

20Definition: This parameter specifies the SimpleIP User Profile Parameter Block defined
21in [CS0016-C].
22Size (bytes): Variable [(N*(X+2))+2], where N is the number of Simple IP profiles and N
23is the maximum NAI length.
2411.3.1 NUM_NAI
25Definition: This parameter specifies the number of applications having different simple
26IP profiles.
1Note: In order to enable Mobile IP to Simple IP fallback, NAI Entry Indexes used in SIP
2and MIP User Profiles must be the same.
311.3.2 Profile Information: NAI Entry Index

4Definition: This parameter provides the index to the NAI profile.
911.3.3 Profile Information: NAI

10Definition: This parameter specifies the Network Address Identifier.
11Allowed Range: Up to 255 ASCII characters
13Note: The NAI should be chosen and managed using procedures that minimize the
14likelihood of compromise.
1511.3.4 Profile Information: Authentication Algorithm

16Definition: This parameter specifies the authentication algorithm used by the operator
17for PDSN authentication.
18Allowed Range:
19  None
20  CHAP
21  PAP
22  CHAP with PAP fallback
23Typical Value: CHAP & PAP
24Note: Always CHAP & PAP for OMH.
2511.4 EFSIPUPPExt [6F7D]

26Definition: This EF contains the additional parameters for Simple IP User Profiles in
27order to fully support the feature of multiple profiles. NUM_NAI is the same as NUM_NAI
28in SIPUPP as per Section 11.3 of this document. Each index in SIPUPP ext maps to the
29same index in SIPUPP.
31  Typical EF Size (bytes): 7 bytes (assumes the common usage of one profile for all
32 applications)

1  Maximum EF Size (bytes): 98 bytes (assumes a wildly unlikely usage of 15 different

2 profiles)
311.4.1 NUM_NAI
4Definition: This parameter specifies the total number of NAIs used for various
5applications.

9Definition: This parameter indicates the index for the particular application using the
10simple IP profile.
1511.4.3 Profile Information: Applications

16Definition: This parameter specifies which applications are associated with this profile.
17One, multiple, or all applications may be associated with a profile. The applications shall
18use the profile with the “unspecified” bit set in the Applications bit mask if they are not
19present in any other profile.
20Allowed Range:
21  Unspecified
22  MMS
23  WAP Browser
24  BREW
25  Java
26  LBS
27  Terminal
28Typical Value: Unspecified
2911.4.4 Profile Information: Priority

30Definition: Application priority. This parameter specifies the priority the device may use
31when launching a particular application.
32Allowed Range:
33Value Priority

10 Highest priority category

21 Second highest priority category (lower than 0; higher than 2+)
32 Third highest priority category (lower than 0 or 1; higher than 3+)
4255 Lowest priority
611.4.5 Profile Information: Data Rate Mode

7Definition: This parameter specifies whether the data rate mode for a particular profile
8is low speed, medium speed or high speed
9Allowed Range:
10  Low
11  Medium
12  High
13Typical Value: High
1411.4.6 Profile Information: Data Bearer

15Definition: This parameter specifies the data bearer to be used for a particular profile.
16Allowed Range:
17  Hybrid 1xEV-DO/1x
18  1x Only
19  1xEV-DO Only
20Typical Value: Hybrid 1xEV-DO/1x
2111.5 EFSIPPAPSS [6F50]

22Definition: This is the Simple IP PAP password.
2411.5.1 Profile Information: PAP SS

25Definition: This parameter specifies the simple IP PAP Shared Secret the operator uses
27Allowed Range: Up to 31 bytes of binary data.
29Note: The password of choice should be a unique NAI and password for each
30subscription. A randomized password should also be selected, preferably of size 16
31bytes.

111.6 EFSIPCHAPSS [Hidden]

2Definition: This EF specifies the Simple IP CHAP shared secret.
3Size (bytes): Operator/R-UIM vendor specific
411.6.1 Profile Information: CHAP SS

5Definition: This parameter specifies the Simple IP CHAP SS value used by an operator
7Allowed Range: 31 bytes of binary data.
9
10

1 12. 3GPD – Mobile IP
212.1 EFMIPCAP [6F4B]
3Definition: This parameter specifies the MobileIP Capability Parameter Block defined in
4[CS0016-C].
63GPD Mobile IP service is supported on its network.
812.1.1 MIP Max Number of NAIs

9Definition: This parameter specifies the maximum number of NAIs used by an operator.
11Typical Value: 1
1212.1.2 MIP Max NAI Length

13Definition: This parameter specifies the maximum length of the Mobile IP NAI. This
14value specifies the maximum memory allocated in the card for this field.
1712.1.3 MIP Max MN-AAA SS Length

18Definition: This parameter specifies the maximum length, in units of octet, of the shared
19secret data (MN-AAA) supported by the R-UIM. If the SS length is greater than 16 bytes,
20it needs to be ensured that the card vendor supports this SS length. This value specifies
21the maximum memory allocated in the card for this field.
23Typical Value: 31
2412.1.4 MIP MN-AAA Authentication Algorithm

25Definition: This parameter specifies the authentication algorithm (MN-AAA) used by the
26mobile station to authenticate itself to the PDSN/Foreign Agent (FA).
1
2Allowed Range: MD5
3Typical Value: MD5
412.1.5 MIP Max MN-HA SS Length

5Definition: Specifies the maximum length, in units of octet, of the shared secret data
6(MN-HA) supported by the R-UIM. This value specifies the maximum memory allocated
7in the card for this field.
9Typical Value: 31
1012.1.6 MIP MN-HA Authentication Algorithm

11Definition: This parameter specifies the authentication algorithm (MN-HA) used by the
12mobile station to authenticate itself to the Home Agent.
13Allowed Range: MD5
14Typical Value: MD5
1512.2 EFMIPSP [6F4F]

16Definition: This EF specifies the MobileIP Status Parameters Block defined in [CS0016-
17B]. If service n38 is allocated, this EF shall be present.
19  Typical Size (bytes): 1 (assuming 1 MIP profile)
20  Maximum Size (bytes): 8 (assuming 15 MIP profiles)
2112.2.1 Active NAI Entry Index

22Definition: This parameter specifies the Active MobileIP NAI entry index.
24Typical Value: 0
2512.3 EFMIPUPP [6F4D]

26Definition: This parameter specifies the Mobile IP User Profiles Profile Parameter Block
27defined in [CS0016-B].
112.3.1 MIP Registration Max Re-tries

2Definition: This parameter specifies the maximum number of retries for Mobile IP
3Registration.
5Typical Value: 3
6Note: The maximum time until a new Registration Request is sent should not be greater
7than the requested Lifetime of the Registration Request.
812.3.2 MIP Registration First Retry Timeout

9Definition: This parameter specifies the amount of time elapsed between the first and
10second MobileIP Registration Requests, while the mobile station did not receive the
11MobileIP Registration Reply.
12Allowed Range: 1–8, in units of 250ms
13Typical Value: 8
14Note: 1–8 should be provisioned on R-UIM as 0–7, and the device will derive a timeout
15value by adding 1000ms to this timeout value per [RFC 2002].
1612.3.3 MIP Re-Registration Threshold

17Definition: This specifies the time before the lifetime expiration when the mobile
18attempts re-registration. It is the pre-lifetime expiration re-registration timer.
20Typical Value: 63
21Note: Registration lifetime is the number of seconds remaining before the registration is
22considered expired. A value of zero indicates a request for deregistration. A value of
230xffff indicates infinity.

25Definition: This parameter specifies the number of profiles used for mobile IP.
27Typical Value: The value depends on the number of profiles an operator uses for its
28applications.
3112.3.5 Profile Information: NAI

32Definition: This parameter specifies the actual Network Address Identifier assigned by
33the operator.

1Allowed Range: Up to 255 ASCII characters

312.3.6 Profile Information: T_BIT (Reverse Tunneling flag)

4Definition: A reverse tunnel is a tunnel that starts at the mobile node’s care-of address
5and terminates at the home agent. This parameter specifies whether reverse tunneling is
6required or not. Reverse tunneling support is added directly into the Registration
7Request (RRQ) by using one of the "rsvd" bits naming it as T bit. If a foreign or home
8agent that does not support reverse tunnels receives a request with the “T” bit set, the
9Registration Request fails.
10Allowed Range:
11  True
12  False
1412.3.7 Profile Information: Home Address

15Definition: This parameter specifies the IP address that is assigned for an extended
16period of time to a mobile node. It remains unchanged, regardless of where the node is
17attached to the Internet.
18Allowed Range:
2012.3.8 Profile Information: Primary Home Agent

21Definition: This parameter specifies the IP address of the mobile node’s primary home
22agent. A home agent is a router on a mobile node’s home network that tunnels
23datagrams for delivery to the mobile node when it is away from home, and maintains
24current location information for the mobile node.
25Allowed Range:
2712.3.9 Profile Information: Secondary Home Agent

28Definition: This parameter specifies the IP address of the mobile node’s secondary
29home agent in the form of network byte code.
30Allowed Range:

112.3.10 Profile Information: MN-AAA Auth Algorithm

2Definition: This parameter specifies the authentication algorithm used to calculate the
3Mobile IP MN-AAA Authentication Extension.
4Allowed Range:
5  None
6  MD5
7Typical Value: MD5
812.3.11 Profile Information: MN-AAA SPI Indicator

9Definition: This parameter specifies the indicator of the Security Parameter Index (SPI)
10between MN and AAA.
11Allowed Range:
12  None
13  32-bit number
15Note: SPI is an index identifying a security context between a pair of nodes among the
16contexts available in the Mobility Security Association.
1712.3.12 Profile Information: MN-HA Auth Algorithm

18Definition: This parameter specifies the authentication algorithm used to calculate the
19Mobile IP MN-HA Authentication Extension, as defined in IETF [RFC 2002].
20Allowed Range:
21  None
22  MD5
23Typical Value: MD5
2412.3.13 Profile Information: MN-HA SPI

25Definition: This parameter is an indicator of SPI between MN and HA.
26Allowed Range:
27  None
28  32-bit number
3012.4 EFMIPUPPExt [6F80]

31Definition: This EF specifies the additional parameters for MobileIP User Profiles in
32order to fully support the feature of multiple profiles for MobileIP.


2  Typical EF Size (bytes): 7 bytes (assumes the common usage of one profile for all
3 applications)
4  Maximum EF Size (bytes): 98 bytes (assumes a wildly unlikely usage of 15 different
5 profiles)
612.4.1 NUM_NAI
7Definition: This parameter specifies the number of MIP profiles.
9Typical Value: 1

11Definition: This parameter specifies the number of profiles used for…
13Typical Value: 0
1612.4.3 Profile Information: Applications

17Definition: This parameter indicates which applications are associated with this profile.
18One, multiple, or all applications may be associated with a profile.
19Allowed Range:
20  Unspecified
21  WAP Browser
22  BREW
23  Java
24  LBS
25  Terminal
26Typical Value: Unspecified
2712.4.4 Profile Information: Priority

28Definition: This parameter specifies the application priority associated with a particular
29profile.
30Allowed Range: 0 (highest) to 255 (lowest)
31Typical Value: 0

112.4.5 Profile Information: Data Rate Mode

2Definition: This parameter specifies the data rate to be used for a particular profile.
3Allowed Range:
4  Low
5  Medium
6  High
7Typical Value: High
812.4.6 Profile Information: Data Bearer

9Definition: This parameter specifies the data bearer to be used for a particular profile.
10Allowed Range:
11  Hybrid 1xEV-DO/1x
12  1x Only
13  1xEV-DO Only
14Typical Value: Hybrid 1xEV-DO/1x
1512.5 EFMIPSS [Hidden]

16Definition: This EF specifies the password for Mobile IP.
17Size (bytes): Vendor specific
1812.5.1 Profile Information: MN-AAA Shared Secret

19Definition: This parameter specifies the key MN-AAA key used to compute the
20challenge response to the challenge received in the agent advertisement message. This
21is included in the authentication extension of the RRQ and must be coordinated and
22provisioned in both the mobile and the AAA server.
23Allowed Range: up to 31 bytes of binary data
2512.5.2 Profile Information: MN-HA Shared Secret

26Definition: This parameter specifies the shared key used by the mobile and the
27message contents to compute an authenticator value, which is included in this MN-HA
28authentication extension. Upon receiving the RRQ, the HA queries the HAAA to obtain
29the MN-HA shared key. Using its MN-HA shared key and the message contents, the HA
30calculates an authenticator value and compares this calculated value to the one
31provided by the mobile. Upon successful validation, the MIP tunnel is established, and
32the HA returns a registration reply (RRP) to the mobile indicating that MIP registration
33has been accepted.


312.6 EFMIPFlags [6F78]

4Definition: This EF specifies the configuration flags for Mobile IP.
612.6.1 MIP 2002bis MN-HA Authentication

7Definition: This parameter specifies the MN-HA authentication that will include the SPI
8in the authenticator calculation.
9Allowed Range:
10  True
11  False
1312.6.2 MIP Pre-Rev 6 Handoff Optimization

14Definition: This parameter specifies whether Point-to-Point (PPP) re-sync will be
15performed proactively between the ME and PDSN to maintain correct PPP framing and
16to avoid not updating PPP framing and PDSN-HA binding when performing an inter-
17PDSN handoff by a ME during a MIP session, which may result in reconnection to a
18latent A10/A11 (R-P) connection. The QUALCOMM cdma2000 1X optimized dormant
19handoff algorithm (QCODH) addresses this by detecting the problematic scenario and
20proactively initiating a PPP resync between the mobile station and PDSN with zombie
21PPP state to maintain correct PPP framing.
22Allowed Range:
23  True
24  False
26Note: When set to True, the mobile will actively renegotiate PPP and reregister MIP
27when it detects that it might be returning to a previously visited PDSN. This may be
28enabled or disabled by the carrier to match the capability of their deployed network to
29address zombie PPP.
3012.6.3 MIP PPP Re-sync During Hand-Down from 1xEV-DO Rev 0 to 1X

31Definition: This parameter specifies whether PPP resync on hand-down from High Data
32Rate (HDR) to 1X for a MIP call will be done or not.
33Allowed Range:
34  True

1  False
312.6.4 MIP Re-Registration – Data Transfer to Extend MIP Address Lifetime

4Definition: This parameter specifies the need for MIP Re-Registration only if data has
5been transferred since last registration in order to extend Mobile IP address lifetime. If
6this is set, the MIP and PPP sessions for the mobile will be dropped if the link is inactive
7for the entire duration of a MIP registration. In other words, re-registration will not be
8performed unless user data (not including Mobile IP registration traffic) is transferred
9during the registration lifetime.
10Allowed Range:
11  True
12  False
14Note: When set to False, the idle data sessions will remain connected indefinitely. The
15mobile will periodically send Registration Requests to the PDSN to refresh the mobile’s
16MIP registration.
17

1
2
3
5

1 13. 3GPD – IPv6
213.1 EFIPV6CAP [6F77]
3Definition: This EF specifies information about IPv6 capabilities.
5IPv6 is supported on its network.
713.1.1 IPv6 Initial Neighbor Solicitation Delay Time

8Definition: This parameter identifies the time the mobile waits after the Interface ID (IID)
9has been negotiated during IPv6CP between the ME and the PDSN before sending a
10Router Solicitation (RS) in an attempt to receive a Router Advertisement (RA).
11Allowed Range: 16-bit number, in units of 100ms
12Typical Value: 500ms
13Note: Neighbor Solicitation is sent by a node to determine the link-layer address of a
14neighbor, or to verify that a neighbor is still reachable via a cached link-layer address.
1513.1.2 IPv6 Solicitation Interval

16Definition: This parameter specifies the amount of time the mobile waits before sending
17a subsequent Router Solicitation (RS) after a previous one.
20Note: RSs are sent by the mobile to solicit the router, e.g., PDSN/GGSN, for an IPv6
21prefix (RA).
2213.1.3 IPv6 Re-Solicitation Interval

23Definition: This parameter specifies the amount of time between router solicitations sent
24while re-soliciting for a new RA. This interval applies only after the mobile has previously
25received one valid RA and is soliciting for a new one to renew the lifetimes of the current
26prefix or retrieve a non-deprecated prefix.
213.1.4 IPv6 Maximum Solicitation Attempts

3Definition: This parameter specifies the number of solicitation attempts to make for
4initial IPv6 session setup, when a RA is not received in response before giving up IPv6
5autoconfiguration.
7Typical Value: 3
8Note: If RA is not received and the ME has already transmitted the maximum solicitation
9attempts, then the ME fails and tears down the IPv6 session. RAs are sent by the router
10to advertise IPv6 prefixes, one of which is used by the mobile. They are sent at periodic
11intervals preset by network administrators, as well as in response to an RS sent by the
12mobile.
1313.1.5 IPv6 Maximum Re-Solicitation Attempts

14Definition: This parameter specifies the number of solicitation attempts to make to re-
15solicit for a new RA.
17Typical Value: 3
1813.1.6 IPv6 Pre-RA Expiry Re-Solicitation Time

19Definition: This parameter specifies the amount of time before the current RA expires to
20begin re-solicitations.
22Typical Value: 0
2313.1.7 IPv6 IID

24Definition: This parameter specifies the 64-bit IID. It is very likely to be unique on the
25link or zero, if a good source of uniqueness cannot be found. These are either derived
26from an IEEE identifier or generated through some other technique.
27Allowed Range: 64-bit binary data
29Note: The IID is the last 64 bits of the IPv6 addresses that is formed by a combination of
30prefix and interface ID, represented in the following format:
31 2002:c023:9c17:314:bceb:acb9:5d51:4045
1The IPv6 prefix is represented by the first 64 bits (2002:c023:9c17:314) and can also be
2represented in the following format:
3 2002:c023:9c17:314::/64.
4IIDs can be selected to be random; in which case, a 64-bit IID is generated by the mobile
5at power-up or can be pre-specified during provisioning of the mobile. Neither of these
6IIDs are guaranteed to be used, of course, if there is a collision between the two
7negotiated IIDs during IPv6CP negotiation [RFC 2472]. If there is a collision, both the
8mobile and PDSN must generate another random IID.
913.1.8 IPv6 Enabled

10Definition: This parameter specifies whether IPv6 is enabled or disabled.
11Allowed Range:
12  True
13  False
15Note: If the CST indicates via n31 that IPv6 is enabled, then this shall be enabled.
1613.1.9 Failover from IPv6 to IPv4 Enabled

17Definition: This parameter specifies whether failover from IPv6 to IPv4 is allowed or not.
18This feature is not supported.
19Allowed Range:
20  True
21  False
2313.1.10 IPv6 PDSN as Proxy DNS Server

24Definition: This parameter specifies whether PDSN acts as the proxy IPv6 Domain
25Name Server (DNS) or not. When enabled, the mobile forwards all DNS requests to the
26PDSN. The PDSN forwards requests to the appropriate DNS server. This parameter is
27meaningful only if the primary and secondary DNS server addresses are not available.
28Allowed Range:
29  True
30  False
32Note: This is only applicable if the parameter IPv6, as specified in Section 13.1.8 of this
33document, is enabled (set to True).

1
2
3
5

1 14. HRPD
214.1 EFHRPDCAP [6F56]
3Definition: This EF specifies the High-Rate Packet Data (HRPD) Access Authentication
4Capability Parameters as defined in Section 3.5.8.12 of [CS0016-C].
6HRPD service is supported on its network.
814.1.1 HRPD Maximum NAI Length

9Definition: This parameter specifies the maximum length for NAI for HRPD access
10authentication, thus specifying the maximum memory allocated in the card for this field.
1314.1.2 HRPD Maximum SS Length

14Definition: This parameter specifies the maximum length of the Shared Secret Data for
15HRPD access authentication, thus specifying the maximum memory allocated in the
16card for this field.
18Typical Value: 31
1914.1.3 HRPD Authentication Algorithms

20Definition: This parameter specifies the authentication algorithm used for HRPD access
21authentication.
22Allowed Range: CHAP
23Typical Value: Always CHAP
2414.2 EFHRPDUPP [6F57]

25Definition: This EF specifies the HRPD Access Authentication User Profile Parameters
26Block defined in Section 3.5.8.13 of [CS0016-C].
214.2.1 HRPD Profile NAI

3Definition: This parameter specifies the Network Access Identifier (NAI), encoded in an
4ASCII string specified by an operator used for AN-AAA ( A12 ) authentication. The NAI is
5of the form user@realm.
6Allowed Range: up to 255 ASCII characters
8Note: The NAI should be chosen and managed using procedures that minimize the
9likelihood of compromise.
1014.2.2 HRPD Profile Authentication Algorithm

11Definition: This parameter specifies the authentication algorithm used for access
12authentication
13Allowed Range: CHAP
14Typical Value: CHAP
1514.3 EFHRPDSS [HIDDEN]

16Definition: This EF specifies the password for HRPD access authentication.
1814.3.1 HRPD SS
19Definition: This parameter specifies the password the operator assigns for AN-AAA
20HRPD access authentication.

23Note: Even if CHAP is being used in an operator’s network for SIP PPP authentication,
24a separate CHAP secret key must be provisioned in the mobile device to support A12
25authentication (i.e., the device will not use the SIP PPP CHAP secret key for A12
26authentication even if the values are the same). The password should be chosen and
27managed using procedures that minimize the likelihood of compromise (i.e., it should be
28cryptographically strong). The password choice should be unique and randomized for
29each subscription, preferably of size 16 bytes.
30
1 15. WAP Browser
215.1 EFWAPBrowserCP [6F7B]
3Definition: This EF identifies WAP Browser connectivity parameters.
5WAP service is supported on its network,
6Multiple sets of WAP Browser Connectivity Parameters may be configured. If so,
7multiple instances of the following fields shall be provided.
9Typical EF Size (bytes): 348 bytes (assumes two Connectivity Parameters TLV objects
10with 70 bytes of Home URL and 104 bytes for gateway information each)
1115.1.1 Domain Name

12Definition: This parameter specifies the WAP Browser Connectivity Parameters:
13PXADDR-FQDN in WAP.
14Allowed Range: Fully qualified domain name
15Note: This may be used instead of Address & Address Type (i.e., enables DNS lookup
16of WAP gateway IP address).
1715.1.2 Address [PXADDR]

18Definition: This parameter specifies that PXADDR can store addresses of different
19kinds, for example an IP address or a SME number.
20Note: This parameter is not required when the operator is using domain name (as in
21Section 15.1.1).
22Allowed Range: Digits or characters
2315.1.3 Address Type [PXADDRTYPE]

24Definition: The parameter PXADDRTYPE indicates the format and the interpretation of
25the PXADDR attribute. The PXADDRTYPE can indicate an IP address, a phone number
26according to the E164 scheme, or a generic alphanumeric address format. This
27parameter MUST be supported by the WAP client. This parameter is not needed if the
28operator is using domain name.
1Allowed Range:
2  IPv4
3  IPv6
4  E164
5  Alpha
6Typical Value: IPv4
715.1.4 Port Number [PORTNBR]

8Definition: This parameter contains the value of the port number. The port number must
9be given as a decimal number and must fit within the range of a 16-bit unsigned integer.
10The PORTNBR must be unique within its enclosed structure, i.e., within the PXLOGICAL
11or the PXPHYSICAL characteristic.
12If the port number is well known, then the service behind the port is implied and the
13parameter SERVICE may be omitted. If the port number is not well known, then no
14service is implied and the service behind the port is defined in parameter SERVICE. If
15the port number is not well known and the parameter SERVICE is omitted, then the ME
16must assume a service according to its preferences.
17If the parameter SERVICE is present, then the definition in the SERVICE parameter
18overrides the implicit meaning.
19This parameter must be supported by the WAP client.
2215.1.5 Service
23Definition: The SERVICE parameter specifies which service is available behind this
24particular port number. This parameter must be supported by the WAP client.
26  WAP connection-less
27  WAP
28  WAP secure connection-less
29  WAP secure
30  WAP WTA secure
31  WAP WTA secure connection-less
32  OTA-HTTP (push) TO-TCP
33  OTA-HTTP secure (push) TO-TCP
1  OTA-HTTP (push) PO-TCP

2  OTA-HTTP secure (push) PO-TCP
3Typical Value: WAP
415.1.6 Authentication Type [PXAUTH-TYPE]

5Definition: The PXAUTH-TYPE indicates the proxy authentication method: HTTP proxy
6authentication or WTLS methods.
7This parameter does not indicate the actual authentication method to use when
8connecting to the proxy, but links the authentication parameters PXAUTH-ID and
9PXAUTH-PW to an authentication method. The PXAUTH-TYPE must be unique within
10its enclosed structure, i.e., within the PXLOGICAL characteristic.
11Allowed Range:
12  HTTP-BASIC
13  HTTP-DIGEST
14  WTLS-SS
15Typical Value: HTTP-BASIC
1615.1.7 Authentication ID [PXAUTH-ID]

17Definition: The PXAUTH-ID indicates the proxy authentication identifier. If it is missing
18then the Global ID of the device should be used (see Section 6.4 of [WAP-183]. The
19global identifier can be defined, for example, using the ClientIdentity characteristic.
20Allowed Range: Binary data
2215.1.8 Authentication Password [PXAUTH-PW]

23Definition: The PXAUTH-PW indicates the proxy authentication secret. The usage of
24the parameter is defined by the PXAUTH-TYPE.
2715.1.9 Home URL

28Definition: This parameter specifies the URL of the browser’s home page.
29Allowed Range: URL text string

115.2 EFWAPBrowserBM [6F7C]

2Definition: This EF specifies the WAP Browser Bookmarks the operator wants to
3configure.
4Multiple bookmarks may be configured. If so, multiple instances of the following fields
5shall be provided.
7Typical EF Size (bytes): 500 bytes (assumes five bookmarks with 100 bytes for each
8TLV object)
915.2.1 Bookmark URL

10Definition: This parameter specifies the URL of the WAP Browser Bookmarks.
1315.2.2 Bookmark Name

14Definition: This parameter specifies the descriptive name of the bookmark.
15Allowed Range: ASCII string
17

1 16. MMS
216.1 EFMMSICP [6F67]
3Definition: This EF specifies MMS connectivity parameters.
5MMS service is supported on its network.
6Multiple sets of MMS connectivity parameters may be configured. If so, each set should
7be provided with all associated fields described below.
916.1.1 Implementation
10Definition: This parameter specifies the implementation. For OMH, the WAP
11implementation of MMS is supported.
12Allowed Range:
13  WAP
14  SIP
15  I-MAP
16Typical Value: WAP

17Note: Always WAP for OMH.
1816.1.2 Relay/Server Address

19Definition: This parameter specifies the MMS Relay/Server address
20Allowed Range: This is the URL
22
2316.1.3 WAP Domain Name

24Definition: This parameter specifies MMS Connectivity Parameters: PXADDR-FQDN in
25WAP.
26Allowed Range: Fully qualified domain name
2Note: This may be used instead of Address & Address Type (i.e., enables DNS lookup
3of the WAP gateway IP address).
416.1.4 WAP Address

5Definition: This parameter specifies that PXADDR can store addresses of different
6kinds, for example an IP address or a SME number.
7Allowed Range: Digits or characters
916.1.5 WAP Address Type

10Definition: The parameter PXADDRTYPE indicates the format and the interpretation of
11the PXADDR attribute. The PXADDRTYPE can indicate an IP address, a phone number
12according to the E164 scheme, or a generic alphanumeric address format. This
13parameter MUST be supported by the WAP client. This parameter is not needed if the
14Operator is using domain name.
15Allowed Range:
16  IPv4
17  IPv6
18  E164
19  Alpha
21Note: This parameter is not needed if the operator is using domain name.
2216.1.6 WAP Port Number

23Definition: This parameter contains the value of the port number. The port number must
24be given as a decimal number and must fit within the range of a 16-bit unsigned integer.
25The PORTNBR must be unique within its enclosed structure, i.e., within the PXLOGICAL
26or the PXPHYSICAL characteristic.
27If the port number is well known, then the service behind the port is implied and the
28parameter SERVICE may be omitted. If the port number is not well known, then no
29service is implied and the service behind the port is defined in parameter SERVICE. If
30the port number is not well known and the parameter SERVICE is omitted, then the ME
31must assume a service according to its preferences.
32If the parameter SERVICE is present, then the definition in the SERVICE parameter
33overrides the implicit meaning.
1This parameter MUST be supported by the WAP client.

416.1.7 WAP Service

5Definition: The SERVICE parameter specifies which service is available behind this
6particular port number. This parameter must be supported by the WAP client.
8  WAP connection-less
9  WAP
10  WAP secure connection-less
11  WAP secure
12  WAP WTA secure
13  WAP WTA secure connection-less
14  OTA-HTTP (push) TO-TCP
15  OTA-HTTP secure (push)
16  TO-TCP
17  OTA-HTTP (push) PO-TCP
18  OTA-HTTP secure (push) PO-TCP
19Typical Value: WAP secure
2016.1.8 WAP Authentication Type

21Definition: The PXAUTH-TYPE indicates the proxy authentication method: HTTP proxy
22authentication or WTLS methods.
23This parameter does not indicate the actual authentication method to use when
24connecting to the proxy, but links the authentication parameters PXAUTH-ID and
25PXAUTH-PW to an authentication method. The PXAUTH-TYPE must be unique within
26its enclosed structure, i.e., within the PXLOGICAL characteristic.
27Allowed Range:
28  HTTP-BASIC
29  HTTP-DIGEST
30  WTLS-SS
31Typical Value: HTTP-BASIC

116.1.9 WAP Authentication ID [PXAUTH-ID]

2Definition: The PXAUTH-ID indicates the proxy authentication identifier. If it is missing
3then the Global ID of the device should be used (see Section 6.4) of [WAP-183]. The
4global identifier can be defined, for example, using the ClientIdentity characteristic.
716.1.10 WAP Authentication Password [PXAUTH-PW]

8Definition: The PXAUTH-PW indicates the proxy authentication secret. The usage of
9the parameter is defined by the PXAUTH-TYPE.
1216.1.11 WAP Authentication Mechanism

13Definition: This parameter specifies the MMS Connectivity Parameters: MMS
14Authentication Mechanism.
15Allowed Range:
16  CRAM-MD5
17  HTTP Digest (MD5)
18  HTTP Digest (MD5-sess)
19  HTTP Digest (AKAv1-MD5)
20  HTTP Digest (AKAv1-MD5-sess)
21  SASL DIGEST
22  SASL OTP
23  SASL GSSAPI
24Typical Value: HTTP Digest (MD5)
2516.2 EFMMSConfig [6F7E]

26Definition: This EF specifies the operator-specific configuration that the MMS client on
27the device is to use when connecting to the MMS service.
2916.2.1 MMS Max Message Size

30Definition: This parameter specifies the maximum MMS message size allowed by the
31operator.
32Allowed Range: 0 to 232-1 bytes
33Typical Value: 300–600 Kbytes

116.2.2 MMS Retry Times

2Definition: This parameter specifies the number of retries for sending MMS.
3Allowed Range: 0–255 retries
4Typical Value: 3
516.2.3 MMS Retry Interval

6Definition: This parameter specifies the MMS Retry interval before the next retry can be
7made.
9Typical Value: 20–30 seconds
1016.2.4 MMS Center Timeout

11Definition: This parameter specifies the number of seconds for the device to wait for
12response from the Mobile Messaging Service Center (MMSC) before declaring it as an
13MMSC timeout.
15Typical Value: 30 – 60 seconds
16

1
2
3
4
6

1 17. Java Catalog
217.1 EFJDL [6F7F]
3Definition: This EF specifies the JAVA download portal URL.
5Typical EF Size (bytes): 70 bytes
617.1.1 Java Download URL

7Definition: This parameter specifies the URL of the Java download portal.
9Typical Value: N/A
10Note: If WAP Browser Home URL is used for Java download, the same URL should be
11provisioned here.
12
1
2
3
5
1 18. BREW Catalog
218.1 EFBREWDownload [6F81]
3Definition: This EF specifies the configuration for enabling BREW download services.
5BREW service is supported on its network.
718.1.1 BREW Carrier ID

8Definition: This parameter specifies the BREW Carrier ID.
9Allowed Range: 32-bit unsigned integer
11
1218.1.2 BREW A-Key

13Definition: This parameter specifies the BREW A-key to be used.
14Allowed Range: 64-bit binary data
1618.1.3 BREW Download Server

17Definition: This parameter specifies either the IP Address or Domain Name associated
18with the BREW Download Server. The device automatically identifies whether the
19contents of this field are an IP address or domain name; in the case of domain name,
20DNS resolution is performed to obtain the IP address. If there is more than one server
21address, they may be specified with comma delimiters (e.g., address1,address2).
22Allowed Range: Up to 64 bytes of ASCII characters
118.1.4 BREW Use A-Key Flag
2Definition: This flag indicates to the BREW downloader (for example, MobileShop)
3whether to use AKEY or BKEY for mutual authentication/validation with the ADS server.
4Allowed Range:
5  True
6  False
818.1.5 BREW Use MIN for SID Flag

9Definition: This flag informs MobileShop to use the MIN for the SID as the default. This
10allows the operator to avoid the provisioning of the SID at the point of sale. Instead, the
11value of the SID will be that of the MIN, so any existing mechanism for setting the MIN
12(operator keying it in by hand, OTASP, etc.) will effectively set the SID as well.
13Allowed Range:
14  True
15  False
1718.1.6 BREW Prepaid Flag

18Definition: This flag informs BREW that this is a prepay phone and that purchases
19made by using MobileShop need to have the device user’s account balance checked for
20sufficient funds before allowing him or her to download an application. When the
21application downloads successfully, the device user’s account is debited.
22Allowed Range:
23  True
24  False
2618.1.7 BREW No Auto Ack Flag

27Definition: If true, do not force ACKs until the user runs MobileShop.
28Allowed Range:
29  True
30  False
118.1.8 BREW App Encoding Flag

2Definition: This flag indicates whether to use Subscriber ID or ESN for application
3encoding. Before executing applications, BREW will ensure that the SID of the current
4handset matches the SID for which this application was downloaded.
5Allowed Range:
6  Use SID
7  Use ESN
8Typical Value: Use SID
9Note: This should not be set for handsets with R-UIM cards.
1018.1.9 BREW Validate All Apps Flag

11Definition: This parameter specifies whether the subscription applications only or both
12subscription and non-subscription applications will be verified; that is, a check is
13performed to determine if the SID or ESN of the current handset matches the handset on
14which the application was downloaded.
15Allowed Range:
16  True
17  False
19Note: If true, all applications are validated, not just SSN applications. With this flag set to
20False, only the subscription applications will be verified; that is, a check is performed to
21determine if the SID or ESN of the current handset matches the SID or ESN of the
22handset on which the application was downloaded.
2318.1.10 BREW RUIM Delete Override Flag

24Definition: This flag allows the user to delete applications owned by another user. By
25default, BREW will allow deletion of BREW applications only by the original owner; that
26is, the owner who downloaded the applications. To override this behavior and to allow
27one R-UIM user to delete applications owned by another, this flag must be set.
28Allowed Range:
29  True
30  False
3218.1.11 BREW Auto Upgrade Flag

33Definition: This parameter specifies whether to perform an automatic upgrade when
34new uses are purchased.

1Allowed Range:
2  True
3  False
5Note: If a user buys an application and the need arises for it to be renewed, any
6available, new upgrade to this software will automatically be upgraded.
718.1.12 BREW Launch when MOD_ACK_DISABLED Is Set Flag

8Definition: This parameter determines whether an application starts, If true, an
9application with flag MOD_ACK_DISABLE set is not started.
10Allowed Range:
11  True (do not start)
12  False
1418.1.13 BREW Download Auth Policy

15Definition: This parameter specifies the operator’s authentication policy for BREW
16Download.
17Allowed Range:
18  No authentication required
19  SID sent to ADS
20  Prompt user for text “key”
21  Prompt user for numeric “key”
22Typical Value: SID sent to ADS
2318.2 EFBREWTSID [6F82]

24Definition: This EF specifies the Teleservice ID to be used in BREW-directed SMS
25messages.
2718.2.1 BREW Teleservice ID

28Definition: This parameter specifies the Teleservice ID to be used in BREW-directed
29SMS messages.
31Typical Value: 4098 (CMT-95)

118.3 EFBREWSID [6F83]

2Definition: This EF specifies information about the BREW Subscriber ID.
3Size (bytes):
4  Typical EF Size (bytes): 32 bytes
5  Maximum EF Size (bytes): 128 bytes
618.3.1 BREW SID

7Definition: This parameter specifies information about the BREW Subscriber ID.
1018.4 EFBREWAEP [6F89]

11Definition: This EF specifies the BREW Application Execution Policy.
1318.4.1 BREW App Execution Policy

14Definition: This parameter specifies the BREW Application Execution Policy.
15Allowed Range:
16  TRUE-BREW signed applet only
17  Carrier-signed applet only
18  TRUE-BREW and carrier-signed
19  TRUE-BREW or carrier-signed
20Typical Value: TRUE-BREW or carrier-signed
21

1
2
3
5

1 19. Location Based Services
219.1 EFLBSXTRAConfig [6F84]
3Definition: This EF contains the configuration of the LBS XTRA client on the device. If
4service n24 (LBS) is allocated, this EF shall be present.
5The operator should always allocate n24 in EF_CST and provision the following
6parameters, whether LBS service is supported on its network or not, for XTRA to still
7work.
919.1.1 Allow gpsOne XTRA Flag

10Definition: This parameter specifies whether gpsOne XTRA is allowed or not. If this
11feature is enabled, an application resident on the mobile downloads a small data file
12from gpsOne Xtra server that contains forecasted satellite data valid for up to seven
13days. This data file is refreshed if it becomes stale. The mobile uses the downloaded
14data file to make fast(er) GPS fixes.
15Allowed Range:
16  True
17  False
1919.1.2 Allow gpsOne XTRA Automatic Download

20Definition: This parameter indicates whether to allow gpsOne XTRA Automatic
21Download or not.
22Allowed Range:
23  True
24  False
2619.1.3 gpsOne XTRA Download Interval

27Definition: This parameter specifies the number of hours between automatic retrievals
28of gpsOneXTRAAssistance data from the Internet.
1Allowed Range: 1–168 hours
2Typical Value: 24 hours
319.1.4 gpsOne XTRA Download Retries

4Definition: This parameter specifies the number of unsuccessful attempts (i.e., retries)
5made to retrieve gpsOneXTRAAssistance data from the Internet before giving up.
7Typical Value: 3
819.1.5 gpsOne XTRA Download Retry Interval

9Definition: This parameter specifies the time (in minutes) between unsuccessful
10download attempts (i.e., retries).
12Typical Value: 10 minutes
1319.2 EFLBSXSURL [6F85]

14Definition: This EF contains the XTRA Server URLs for LBS. If service n24 (LBS) is
15allocated, this EF shall be present.
16Size (bytes): Typical EF Size (bytes): 300 bytes (assumes 100 bytes for each URL TLV
17object)
1819.2.1 Primary XTRA Server URL

19Definition: This parameter specifies the XTRA Server URLs for LBS.
21Typical Value: http://xtra1.gpsOneXTRA.net/xtra.bin
2219.2.2 Primary XTRA Server Name

23Definition: This parameter specifies the name for the Primary XTRA Server.
24Allowed Range: ASCII text string
2619.2.3 Secondary XTRA Server URL

27Definition: This parameter specifies the URL for the Secondary XTRA Server.
219.2.4 Secondary XTRA Server Name

3Definition: This parameter specifies the name for the Secondary XTRA Server.
4Allowed Range: ASCII text string
619.2.5 Tertiary XTRA Server URL

7Definition: This parameter specifies the URL for the Tertiary XTRA Server.
1019.2.6 Tertiary XTRA Server Name

11Definition: This parameter specifies the name for the Tertiary XTRA Server.
12Allowed Range: ASCII Text string
1419.3 EFLBSV2Config [6F86]

15Definition: This parameter specifies the configuration of the LBS V2 client on the
16device. If service n24 (LBS) is allocated, this EF shall be present.
1819.3.1 LBS V2 Allow Sending System Parameter Info Message

19Definition: This parameter indicates whether to enable the Allow Sending System
20Parameter Info Message. The System Parameter Info message contains the serving
21base station information (SID, NID, Base ID, Frequency, PN, etc.).
22Allowed Range:
23  True
24  False
2619.3.2 LBS V2 Allow Seed Position Use

27Definition: This parameter indicates whether to allow Seed Position Use. If this item is
28enabled, the gpsOne engine will trust and use the broadcasted tower location as a seed
29position.
30Allowed Range:

1  True
2  False
419.3.3 LBS V2 Allow Dynamic Mode

5Definition: This parameter indicates whether to allow Dynamic Mode. If this item is
6enabled, fallback from MS-Based to Standalone mode, and vice versa, is allowed.
7Allowed Range:
8  True
9  False
1119.4 EFLBSV2PDEADDR [6F87]

12Definition: This EF specifies information pertaining to the Position Determination Entity
13(PDE) Server IP address and Port Number for V2 LBS. If service n24 (LBS) is allocated,
14this EF shall be present.
15Size (bytes): Typical EF Size (bytes): 100 bytes (assumes a 96-byte Domain Name)
1619.4.1 LBS V2 Address Type

17Definition: This parameter identifies the type of address contained in the V2 LBS PDE
18Address Information field.
19Allowed Range:
20  Domain name
21  IPv4 address
22  IPv6 address
2419.4.2 LBS V2 PDE Address

25Definition: This parameter specifies the address of the PDE server. The type of PDE
26server address contained in this field is determined by the Address Type field above.
2919.4.3 LBS V2 PDE Port Number

30Definition: This parameter specifies the port Number for the V2 LBS PDE Server.

219.5 EFLBSV2MPCADDR [6F88]

3Definition: This parameter specifies the MPC Server IP address and Port Number for
4V2 LBS. If service n24 (LBS) is allocated, this EF shall be present.
5Size (bytes): Typical EF Size (bytes): 100 bytes (assumes a 96-byte Domain Name)
619.5.1 LBS V2 MPC Address Type

7Definition: This specifies the type of address contained in the V2 LBS MPC Address
8Information field.
9Allowed Range:
10  Domain name (gpsOne needs to perform DNS resolution)
11  IPv4 address
12  IPv6 address
1419.5.2 LBS V2 MPC Address

15Definition: This parameter specifies the type of MPC server address contained in this
16field, as determined by the Address Type field above.
17Allowed Range: 8-bit ASCII (one octet per character) string
1919.5.3 LBS V2 MPC Port Number

20Definition: This parameter specifies the Port Number for the V2 LBS MPC Server.
23

1
2
3
5

1 20. Terminology
Term Meaning
3GPD Third Generation Packet Data

AAA Authentication, Authorization and Accounting
A-Key A secret, 64-bit pattern stored in the mobile station and HLR/AC. It
is used to generate/update the mobile station’s Shared Secret
Data and to validate SPASM.
Authentication A procedure used by a base station to validate a mobile station’s
identity.
BCD Binary-Coded Decimal
BREW Binary Runtime Environment for Windows
CAVE Cellular Algorithms for Validation and Encryption
CHAP Challenge Handshake Authentication Protocol
DNS Domain Name Server. Provides translation between domain
names and IP addresses
EF Elementary File
EMS Enhanced Short Message Service
ESN Electronic Serial Number
FA Foreign Agent
FC Feature Code
GID Group ID
HA Home Agent
HRPD High Rate Packet Data
IID Interface ID
IMSI International Mobile Station Identity
ITU International Telecommunication Union
ITU International Telecommunication Union
LCM Local Use Mark

LMS Long SMS

MCC Mobile Country Code
MDN Mobile Directory Number
ME Mobile Equipment
MIN Mobile Identification Number
MIP MobileIP
MMS Multimedia Messaging Service
MMSC Multimedia Messaging Service Center
MN Mobile Node
MNC Mobile Network Code
MO Mobile Originated
MS Mobile Station
NA Not Applicable
NAI Network Address Identifier
NAM Number Assignment Module
NID Network Identifier
NMSI National Mobile Subscriber Identity
OTA Over The Air
OTAPA Over-the-Air Parameter Administration. Network initiated OTASP
process of provisioning mobile station operational parameters over
the air interface
OTASP Over-the-Air Service Provisioning. A process of provisioning
mobile station operational parameters over the air interface
PAP Password Authentication Protocol
PDSN Packet Data Serving Node
PPP Point-to-Point
RA Router Advertisement
RRP Registration Reply
RRQ Registration Request
RS Router Solicitation
R-UIM Removable User Identity Module

SID System Identification

SIM Subscriber Identity Module
SMS Short Message Service
SPASM Subscriber Parameter Administration Security Mechanism
SPC Service Programming Code
SPC Service Programming Code
SPI Security Parameter Index
SPN Service Provider Name
TCP Transmission Control Protocol
WAP Wireless Application Protocol
WTLS Wireless Transport Layer Security

6 21.

1 22. References
[CDG101] CDG Reference Document 101, “CDMA Mobile Station LBS

Requirements - V2,” v1.0, August 22, 2005. See www.cdg.org
[CDG167] CDG Reference Document 167, “Open Market Handset (OMH)

Device and Network Specification,” v2.0, May 2008. See
www.cdg.org
[CDG169] CDG Reference Document 169, “Open Market Handsets (OMH)

PRI,” v2.1, May 2009. See www.cdg.org
[CR1001-F] 3GPP2 C.R1001-F, “Administration of Parameter Value

Assignments for cdma2000 Spread Spectrum Standards,” v1.0.
Download at http://www.3gpp2.org/Public_html/specs/C.R1001-
F_v1.0_061211.pdf
[CS0015-B] 3GPP2 C.S0015-B, “Short Message Service (SMS) for Wideband

Spread Spectrum Systems,” v2.0, September 2005. Download at
http://www.3gpp2.org/Public_html/specs/C.S0015-
B_v2.0_051006.pdf
[CS0005-A] 3GPP2 C.S0005-A, “Upper Layer (Layer 3) Signaling Standard for

cdma2000 Spread Spectrum Systems – Release A Addendum 2,”
v6.0, February 2002. Download at
http://www.3gpp2.org/Public_html/specs/C.S0005-A_v6.0.pdf
[CS0016-B] 3GPP2 C.S0016-B, “Over-the-Air Service Provisioning of Mobile

Stations in Spread Spectrum Standards,” v.1.0, October 25, 2002.
Download at http://www.3gpp2.org/Public_html/specs/C.S0016-
B_v1.0.pdf
[CS0016-C] 3GPP2 C.S0016-C (TIA-683C), “Over-the-Air Service Provisioning

of Mobile Stations in Spread Spectrum Standards,” v1.0, October
31, 2008. Download at
http://www.3gpp2.org/Public_html/specs/C.S0016-
C_v2.0_081031.pdf
[CS0023-D] C.S0023-D, “Removable User Identity Module for Spread Spectrum

Systems,” v1.0, June 2009. Download at
http://www.3gpp2.org/Public_html/specs/C.S0023-D_v1.0_R-UIM-
090720.pdf
[CS0024-D] C.S0024-D, “cdma2000 High Rate Packet Data Air Interface

Specification,” v.3.0, December 2001. Download at
http://www.3gpp2.org/Public_html/specs/C.S0024-0_v3.0.pdf
[RFC2002] IETF RFC 2002, “IP Mobility Support,” October 1996. Go to

http://www.apps.ietf.org/rfc/rfc2002.html
[RFC2462] RFC 2462, “IPv6 Stateless Address Autoconfiguration,” December

1998. Go to http://www.ietf.org/rfc/rfc2462.txt
[RFC2472] RFC 2472, “IP Version 6 over PPP,” September 2007. Go to

http://tools.ietf.org/rfc/rfc5072.txt
[RFC3041] IETF RFC 3041, “Privacy Extensions for Stateless Address

Autoconfiguration in IPv6,” January 2001. Go to
http://www.apps.ietf.org/rfc/rfc3041.html
[WAP-183] WAP-183-ProvCont-20010724-a, “WAP Provisioning Content,” July

2001. Download at
http://www.openmobilealliance.org/tech/affiliates/wap/wap-183-
provcont-20010724-a.pdf
[XS0016-310-0] 3GPP2 X.S0016-310-0 (TIA-934-310), “MMS MM1 Stage 3 Using

OMA/WAP,” June 2004. Download at
http://www.3gpp2.org/Public_html/specs/X.S0016-310-
0_v2.0_040617.pdf

(Cdg169) Omh Pri Guidelines

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

(Cdg169) Omh Pri Guidelines

Uploaded by

Copyright:

Available Formats

1

Open Market Handsets (OMH)

4 CDG Document 169

7 CDMA Development Group

Ref Doc. 169, Ver. 3.0 March 2010

Ref Doc. 169, Ver. 3.0 March 2010

1 14.3 EFHRPDSS [HIDDEN]....................................................................................................... 58

Ref Doc. 169, Ver. 3.0 March 2010

Date Version Description

March 2010 3.0  This CDG169 PRI Guidelines document was

Ref Doc. 169, Ver. 3.0 March 2010

Ref Doc. 169, Ver. 3.0 March 2010

Ref Doc. 169, Ver. 3.0 March 2010

212.1.3 IMSI_M_11_12 (MNC)

Ref Doc. 169, Ver. 3.0 March 2010

52.2 EFIMSI_T [6F23]

Ref Doc. 169, Ver. 3.0 March 2010

12.3 EFUSGIND [6F42]

42.3.1 Handset Authentication Indicator

122.3.2 Handset Identification Indicator

192.4 EFMDN [6F44]

262.4.1 Mobile Directory Number

302.4.2 Mobile Directory Number Type

Ref Doc. 169, Ver. 3.0 March 2010

62.4.3 Mobile Directory Number Plan

132.5 EFRUIMID [6F31]

162.5.1 R-UIM Identifier

212.6 EFRevision [6F39]

242.6.1 R-UIM Revision

Ref Doc. 169, Ver. 3.0 March 2010

73.1.1 Analog Home SID

163.2.1 Extended Address

223.2.2 Local Use Mark

133.3.1 Analog Initial Paging Channel

173.3.2 Analog First Dedicated Control System A

223.3.3 Analog First Dedicated Control System B

273.3.4 Analog Number of DCC

Ref Doc. 169, Ver. 3.0 March 2010

1Allowed Range: 0255

Ref Doc. 169, Ver. 3.0 March 2010

Ref Doc. 169, Ver. 3.0 March 2010

64.1.1 Home SID and NID

124.1.2 Band Class

164.2 EFACCOLC [6F2C]

Ref Doc. 169, Ver. 3.0 March 2010

64.3 EFTERM [6F2D]

94.3.1 Home SID Term Reg

164.3.2 Foreign SID Term Reg

234.3.3 Home NID Term Reg

Ref Doc. 169, Ver. 3.0 March 2010

14.4 EFSSCI [6F2E]

44.4.1 Slot Cycle Index

94.5 EFPRL [6F30]

12Note: See Section 4.6, EFMAXPRL [6F45].

204.6 EFMAXPRL [6F45]

234.6.1 Maximum PRL Size for EFPRL

Ref Doc. 169, Ver. 3.0 March 2010

24.7 EFSP [6F37]

54.7.1 System A/B Preference

144.7.2 Analog/CDMA Preference

234.8 EFECC [6F47]

264.8.1 Emergency Call Codes

Ref Doc. 169, Ver. 3.0 March 2010