[Cdg169] Omh Pri Guidelines
-
Upload
praan-sastararuchi -
Category
Documents
-
view
220 -
download
0
Transcript of [Cdg169] Omh Pri Guidelines
-
8/8/2019 [Cdg169] Omh Pri Guidelines
1/94
Open Market Handsets (OMH)PRI Guidelines
(Companion document to CDG169 PRI Workbook)
CDG Document 169Version 3.0
March 2010
CDMA Development Group575 Anton Boulevard, Suite 560Costa Mesa, California 92626
PHONE +1 888 800-CDMA+1 714 545-5211
FAX +1 714 545-4601http://www.cdg.org
Notice
Each CDG member acknowledges that CDG does not review thedisclosures or contributions of any CDG member nor does CDG verifythe status of the ownership of any of the intellectual property rightsassociated with any such disclosures or contributions. Accordingly, each
CDG member should consider all disclosures and contributions as beingmade solely on an as-is basis. If any CDG member makes any use ofany disclosure or contribution, then such use is at such CDG memberssole risk. Each CDG member agrees that CDG shall not be liable to anyperson or entity (including any CDG member) arising out of any use ofany disclosure or contribution including any liability arising out ofinfringement of intellectual property rights.
-
8/8/2019 [Cdg169] Omh Pri Guidelines
2/94
Ref Doc. 169, Ver. 3.0 March 2010 ii
-
8/8/2019 [Cdg169] Omh Pri Guidelines
3/94
Ref Doc. 169, Ver. 3.0 March 2010 iii
Contents1
1. Introduction ........................................................................................................................... 121.1 Purpose and Scope........................................................................................................ 131.2 Outline ........................................................................................................................... 14
2. Handset and R-UIM Identifiers.............................................................................................. 352.1 EFIMSI_M [6F22] .............................................................................................................. 362.2 EFIMSI_T [6F23]............................................................................................................... 4
7
2.3 EFUSGIND [6F42] ........................ ............................ .......................... ............................ ... 582.4 EFMDN [6F44] ........................ ............................ ......................... ............................ ........ 592.5 EFRUIMID [6F31] ......................... ............................ .......................... ............................ ... 6102.6 EFRevision [6F39] ............................................................................................................. 611
3. Analog Service Information .................................................................................................. 7123.1 EFAH [6F39] .......................... ............................ ......................... ............................ ........ 7133.2 EFAOP............................................................................................................................. 7143.3 EFACP ............................................................................................................................. 815
4. CDMA Service Information.................................................................................................. 11164.1 EFCDMAHOME [6F28] ......................... ............................ ......................... ......................... 11174.2 EFACCOLC [6F2C] .......................................................................................................... 11184.3 EFTERM [6F2D] ...................... ............................ ......................... ............................ ...... 12194.4 EFSSCI [6F2E] .............................................................................................................. 12204.5 EFPRL [6F30] ............................................................................................................... 13214.6 EFMAXPRL [6F45] ........................................................................................................... 13224.7 EFSP [6F37] ....................... ........................... .......................... ............................ .......... 14234.8 EFECC [6F47] ................................................................................................................ 14244.9 EFSSFC [6F3F]............................................................................................................... 1525
5. OTASP/OTAPA .................................................................................................................... 17265.1 EFOTAPASPC [6F34]........................................................................................................ 17275.2 EFNAMLOCK [6F35] ....................... ........................... .......................... ............................ . 18285.3 EFOTA [6F36] ................................................................................................................ 19295.4 EFSPC [6F33] ............................................................................................................... 1930
-
8/8/2019 [Cdg169] Omh Pri Guidelines
4/94
PRIGuidelines Contents
Ref Doc. 169, Ver. 3.0 March 2010 iv
5.5 EFSPCS [6F46] ....................... ............................ ......................... ............................. ..... 2016. Carrier Customization ......................................................................................................... 212
6.1 EFSPN [6F41] ............................................................................................................... 2136.2 EFAppLabels [6F92] ......................................................................................................... 224
7. Root Certificates.................................................................................................................. 255
7.1 EFRC [6F91] .................................................................................................................. 2568. SMS Basic......................................................................................................................... 277
8.1 EFSMSCAP [6F76] .......................................................................................................... 2789. SMS Broadcast ................................................................................................................. 299
9.1 EFBCSMScfg [6F5B] ........................................................................................................ 29109.2 EFBCSMSTable [6F5D]...................................................................................................... 29119.3 EFBCSMSP [6F5E] ....................... ............................ .......................... ............................ . 3112
10. 3GPD Basic..................................................................................................................... 331310.1 EFME3GPDOPC [6F48] ................................................................................................... 331410.2 EF3GPDOPM [6F49]....................................................................................................... 331510.3 EFTCPConfig [6F79] ......................... ............................ ......................... ......................... 341610.4 EFDGC [6F7A] ............................................................................................................ 3417
11. 3GPD Simple IP............................................................................................................... 371811.1 EFSIPCAP [6F4A] ......................................................................................................... 371911.2 EFSIPSP [6F4E] ........................ ............................ .......................... ............................ . 382011.3 EFSIPUPP [6F4C] ....................... ........................... .......................... ............................ . 382111.4 EFSIPUPPExt [6F7D] ........................ ............................ ......................... ......................... 392211.5 EFSIPPAPSS [6F50] ......................... ............................ ......................... ......................... 412311.6 EFSIPCHAPSS [Hidden] ......................... ........................... ......................... ..................... 4224
12. 3GPD Mobile IP ............................................................................................................... 432512.1 EFMIPCAP [6F4B] ...................... ............................ .......................... ............................ . 432612.2 EFMIPSP [6F4F] ........................ ............................ .......................... ............................ . 442712.3 EFMIPUPP [6F4D] ....................... ........................... .......................... ............................ . 442812.4 EFMIPUPPExt [6F80] ........................ ............................ ......................... ......................... 472912.5 EFMIPSS [Hidden] ...................... ........................... .......................... ............................ . 493012.6 EFMIPFlags [6F78] ........................................................................................................ 5031
13. 3GPD IPv6....................................................................................................................... 533213.1 EFIPV6CAP [6F77] ........................................................................................................ 5333
14. HRPD.................................................................................................................................. 573414.1 EFHRPDCAP [6F56] ......................... ............................ ......................... ......................... 573514.2 EFHRPDUPP [6F57] ......................... ............................ ......................... ......................... 573614.3 EFHRPDSS [HIDDEN] ......................... ............................ ......................... ..................... 5837
-
8/8/2019 [Cdg169] Omh Pri Guidelines
5/94
-
8/8/2019 [Cdg169] Omh Pri Guidelines
6/94
PRIGuidelines Contents
Ref Doc. 169, Ver. 3.0 March 2010 vi
Revision History1
Date Version Description
March 2010 3.0 y This CDG169 PRI Guidelines document wascreated as a companion document to theCDG169 PRI Workbook. The two documentsshould always be used together. Originally thisinformation was in the CDG169 PRI Workbook.Having a separate companion document allowsfor more complete guidelines, examples, etc. toassist operators in completing the PRI Workbook.
-
8/8/2019 [Cdg169] Omh Pri Guidelines
7/94
Ref Doc. 169, Ver. 3.0 March 2010 1
1. Introduction1
1.1 Purpose and Scope2
This document provides guidelines and recommendations to operators for provisioning3
parameters in R-UIM cards. It also provides a detailed description of each of the4
parameters listed in [CDG169 Part 1] and meaningful information regarding these5
parameters and their significance.6
This document is targeted toward operators who need to:7
understand what a particular parameter is used for,8
know the typical values (or range of values),9
understand the reason behind the choice of typical values, and10
learn the tradeoffs, if any, in setting these parameters to values other than those11recommended.12
1.2 Outline13
A standard template is used for each parameter description, as follows:14
Definition: Brief explanation of the parameter15
Allowed Range: The permitted range and unit of each parameter16
Typical Value: The single value the parameter needs to be set to, which is most17
commonly used by operators18
Notes:19
A brief description of the tradeoffs involved in the setting of this parameter, providing20
an explanation of the effects of setting it too high and too low, beyond the normal21
operating range22
Any other remarks on the parameter setting (e.g., common mistakes, other useful23information)24
25
26
-
8/8/2019 [Cdg169] Omh Pri Guidelines
8/94
PRIGuidelines Introduction
Ref Doc. 169, Ver. 3.0 March 2010 2
1
2
3
4
5
-
8/8/2019 [Cdg169] Omh Pri Guidelines
9/94
Ref Doc. 169, Ver. 3.0 March 2010 3
2. Handset and R-UIM Identifiers1
2.1 EFIMSI_M [6F22]2
Definition: This EF stores the five components of IMSI_M. An IMSI_M is always a class3
0 IMSI.4
Size (bytes): 10 (fixed)5
2.1.1 IMSI_M_CLASS6
Definition: This parameter identifies the class assignment of the International Mobile7
Station Identity (IMSI). An IMSI that is 15 digits in length is called a class 0 IMSI [the8
National Mobile Station Identity (NMSI) is 12 digits in length]; an IMSI that is less than 159
digits in length is called a class 1 IMSI.10
Allowed Range: 0, 111
Typical Value: 012
2.1.2 IMSI_M_S13
Definition: This parameter identifies a 10-digit (34-bit) number derived from the IMSI.14
When an IMSI has 15 digits, IMSI_S is equal to the least significant 10 digits of the IMSI.15
When an IMSI has fewer than 15 digits, zeros are added to the most significant side of16
MSIN to obtain a 15-digit padded IMSI; IMSI_S is equal to the last 10 digits of the17
padded IMSI.18
Allowed Range: Ten decimal digits19
Typical Value: Operator specific20
2.1.3 IMSI_M_11_12 (MNC)21
Definition: This parameter comprises the 11th and 12th digits from the right of the IMSI22
address.23
Allowed Range: Two decimal digits24
Typical Value: Operator specific25
Note: Thisis also known as Mobile Network Code (MNC) and is assigned by the26
International Telecommunication Union (ITU) to the operator.27
-
8/8/2019 [Cdg169] Omh Pri Guidelines
10/94
-
8/8/2019 [Cdg169] Omh Pri Guidelines
11/94
PRIGuidelines Handset andR-UIMIdentifiers
Ref Doc. 169, Ver. 3.0 March 2010 5
2.3 EFUSGIND [6F42]1
Definition: This EF contains the Removable UIM_ID/SF_EUIMID Usage Indicator.2
Size (bytes): 1 (fixed)3
2.3.1 Handset Authentication Indicator4
Definition: This parameter indicates whether to use ESN_ME or UIM_ID for Cellular5
Algorithms for Validation and Encryption (CAVE) authentication and MS identification.6
Allowed Range:7
ESN_ME8
UIM_ID9
Typical Value: Always use UIM_ID for OMH.10
Note: For OMH devices, this should always be set to UIM_ID and not ESN.11
2.3.2 Handset Identification Indicator12
Definition: This parameter indicates whether to use MEID or SF_EUIMID to identify the13
mobile station (MS).14
Allowed Range:15
MEID16
SF_EUIMID17
Typical Value: Always use SF_EUIMID for OMH.18
2.4 EFMDN [6F44]19
Definition: This parameter indicates the dialable number associated with the mobile20
station through a service subscription. A Mobile Directory Number (MDN) is not21
necessarily the same as the mobile station identification on the air interface, i.e., MIN,22
IMSI_M, or IMSI_T. An MDN consists of up to 15 digits. The mobile station should have23
memory to store at least one MDN.24
Size (bytes): 11 (fixed)25
2.4.1 Mobile Directory Number26
Definition: This parameter indicates the MDN.27
Allowed Range: 15 decimal digits programmable28
Typical Value: Operator specific29
2.4.2 Mobile Directory Number Type30
Definition: This parameter indicates the MDN Type.31
-
8/8/2019 [Cdg169] Omh Pri Guidelines
12/94
PRIGuidelines Handset andR-UIMIdentifiers
Ref Doc. 169, Ver. 3.0 March 2010 6
Allowed Range:1
National2
International3
Unknown4
Typical Value: Operator specific5
2.4.3 Mobile Directory Number Plan6
Definition: This parameter indicates the MDN Plan.7
Allowed Range:8
Telephony9
Private10
Unknown11
Typical Value: Operator specific12
2.5EFRUIMID [6F31]13
Definition: This EF contains the R-UIM Identifier.14
Size (bytes): 8 (fixed)15
2.5.1 R-UIM Identifier16
Definition: This parameter contains the R-UIM Identifier.17
Allowed Range: 32-bit number18
Typical Value: This is not to be provisioned by the operator; the value depends on the19
particularR-UIM card vendor.20
2.6EFRevision [6F39]21
Definition: This EF contains the revision number of the R-UIM.22
Size (bytes): 1 (fixed)23
2.6.1 R-UIM Revision24
Definition: This parameter contains the revision number of the R-UIM.25
Allowed Range: 025526
Typical Value: 00000100 (R-UIM complying with [CS0023-D])27
Note: This allows the mobile equipment (ME) to communicate with different versions of28the R-UIM (i.e., R-UIM with different set of capabilities).29
30
31
-
8/8/2019 [Cdg169] Omh Pri Guidelines
13/94
Ref Doc. 169, Ver. 3.0 March 2010 7
3. Analog Service Information1
3.1 EFAH [6F39]2
These EFs pertain to Analog. Since none of the operators are using AMPS, they do3
not need tobe provisioned.4
Definition: This EF indicates the Analog Home SID.5
Size (bytes): 2 (fixed)6
3.1.1 Analog Home SID7
Definition: This parameter indicates the Cellular Service Provider analog home system8
ID for the given NAM. This is automatically filled from the CDMA Home SID.9
Allowed Range: 5 decimal digits from 06553510
Typical Value: Operator specific11
3.2 EFAOP12
Definition: This EF indicates the Analog Operational Parameters, namely, Extended13
Address bit (Exp), the Local Use Mark (LCM), and the Group ID (GID) field.14
Size (bytes): 1 (fixed)15
3.2.1 Extended Address16
Definition: This parameter specifies whether the Extended Address bit is enabled.17
Allowed Range:18
True19
False20
Typical Value: False21
3.2.2 Local Use Mark22
Definition: This parameter specifies whether the Local Use Mark bit is enabled.23
Allowed Range:24
True25
-
8/8/2019 [Cdg169] Omh Pri Guidelines
14/94
PRIGuidelines Analog Service Information
Ref Doc. 169, Ver. 3.0 March 2010 8
False1
Typical Value: False2
3.2.3 Group ID3
Definition: This parameter indicates whether the Group ID bit is enabled or not.4
Allowed Range: 0155
Typical Value: Operator Specific6
3.3 EFACP7
Definition: This EF indicates the Analog Mode Channel Preferences, as determined by8
the service3 provider in accordance with the terms of the subscription. The items9
addressed are the Analog Initial Paging Channel, the Analog First Dedicated Control10
Channel for System A, the Analog First Dedicated Control Channel for System B, and11
the Number of Dedicated Control Channels to scan.12
Size (bytes): 7 (fixed) [CS0023-D]13
3.3.1 Analog Initial Paging Channel14
Definition: This parameter indicates the Analog Initial Paging Channel.15
Allowed Range: 5 decimal digits from 06553516
Typical Value: Operator specific17
3.3.2 Analog First Dedicated Control System A18
Definition: This parameter indicates the Analog First Dedicated Control Channel19
System A.20
Allowed Range: 5 decimal digits from 06553521
Typical Value: Operator specific22
3.3.3 Analog First Dedicated Control System B23
Definition: This parameter indicates the Analog First Dedicated Control Channel24
System B.25
Allowed Range: 5 decimal digits from 06553526
Typical Value: Operator specific27
3.3.4 Analog Number of DCC28
Definition: This parameter identifies the Analog Number of the Dedicated Control29
Channel to scan.30
-
8/8/2019 [Cdg169] Omh Pri Guidelines
15/94
PRIGuidelines Analog Service Information
Ref Doc. 169, Ver. 3.0 March 2010 9
Allowed Range: 02551
Typical Value: Operator specific2
3
4
-
8/8/2019 [Cdg169] Omh Pri Guidelines
16/94
PRIGuidelines Analog Service Information
Ref Doc. 169, Ver. 3.0 March 2010 10
1
2
3
4
5
6
-
8/8/2019 [Cdg169] Omh Pri Guidelines
17/94
Ref Doc. 169, Ver. 3.0 March 2010 11
4. CDMA Service Information1
4.1 EFCDMAHOME [6F28]2
Definition: This EF indicates the CDMA Home System Identification (SID) and Network3
Identification (NID) when the mobile station is operating in CDMA mode.4
Size (bytes): 5 x # of records5
4.1.1 Home SID and NID6
Definition: This parameter indicates the Home SIDs and NIDs for the given NAM.7
Allowed Range: Multiple pairs of up to 5 decimal digits, ranging from 032767; with8
corresponding Band Class.9
Typical Value: 46 pairs10
Note: The first SID cannot be 0. SIDs must be all even or all odd.11
4.1.2 Band Class12
Definition: This parameter indicates the band class supported.13
Allowed Range: This is a 1 byte field that represents the corresponding Band Class.14
Typical Value: Operator Specific15
4.2 EFACCOLC [6F2C]16
Definition: This EF indicates the 4-bit Access Overload Class indicator (ACCOLCp),17
which is used to identify which overload class controls access attempts by the mobile18
station and is used to identify redirected overload classes in global service redirection.19
The mobile station shall store the 4-bit access overload class (ACCOLCp). Mobile20
stations that are not for test or emergency use should be assigned to overload classes21
ACCOLC 0 through ACCOLC 9. For mobile stations that are classified as overload22
classes ACCOLC 0 through ACCOLC 9, the mobile stations 4-bit access overload class23indicator (ACCOLCp) shall be automatically derived from the last digit of the associated24
decimal representation of the IMSI_M by a decimal to binary conversion, as specified in25
[CS0005-A].26
Size (bytes): 1 (fixed)27
-
8/8/2019 [Cdg169] Omh Pri Guidelines
18/94
PRIGuidelines CDMA Service Information
Ref Doc. 169, Ver. 3.0 March 2010 12
4.2.1 Access Overload Class1
Definition: This parameter indicates the Access Overload Class (ACCOLCp).2
Allowed Range: 4-bit access overload class indicator.3
Typical Value: The value is derived from the last digit of the associated decimal4
representation of the IMSI_M.5
4.3 EFTERM [6F2D]6
Definition: This EF indicates the Call Termination Mode Preferences.7
Size (bytes): 1 (fixed)8
4.3.1 Home SID Term Reg9
Definition: This parameter indicates the CDMA mobile-terminated home SID10
registration.11
Allowed Range:12
True13
False14
Typical Value: True15
4.3.2 Foreign SID Term Reg16
Definition: This parameter indicates the CDMA mobile-terminated foreign SID17
registration.18
Allowed Range:19
True20
False21
Typical Value: True22
4.3.3 Home NID Term Reg23
Definition: This parameter indicates the CDMA mobile-terminated home NID24
registration.25
Allowed Range:26
True27
False28
Typical Value: True29
4.4 EFSSCI [6F2E]30
Definition: This EF indicates the Suggested Slot Cycle Index.31
-
8/8/2019 [Cdg169] Omh Pri Guidelines
19/94
PRIGuidelines CDMA Service Information
Ref Doc. 169, Ver. 3.0 March 2010 13
Size (bytes): 1 (fixed)1
4.4.1 Slot Cycle Index2
Definition: This parameter indicates the duration and frequency that the phone checks3
the paging channel.4
Allowed Range: 2 decimal digits, range 075
Typical Value: 26
4.5 EFPRL [6F30]7
Definition: This EF stores the Preferred Roaming List.8
Size (bytes): MAX_PRL_LIST_SIZE.9
Note: See Section 4.6, EFMAXPRL [6F45].10
4.5.1 PR_LIST11
Definition: This parameter indicates the Preferred Roaming List. See [CS0016-C]. This12
may contain IS-683A PRL for 1x only devices or Concatenated PRL (cPRL) with IS-13
683A PRL and IS-683C PRL for EV-DO devices. See the appendix in [CDG167] for14
more information on cPRL.15
Allowed Range: This is the actual PRL.16
Typical Value: Operator specific.17
4.6 EFMAXPRL [6F45]18
Definition: This EF indicates the maximum size for EFPRL and EFEPRL.19
Size (bytes): 2 (fixed)20
4.6.1 Maximum PRL Size for EFPRL21
Definition: This EF indicates the maximum PRL size for EFPRL. The mobile station shall22
set this field to the maximum size, in octets, that the mobile station can support for the23
preferred roaming list (PR_LISTs-p).24
Allowed Range: 06553525
Typical Value: 67k (For both 1X and EVDO systems)26
Note: Operator to specify based upon entries in PRL.27
-
8/8/2019 [Cdg169] Omh Pri Guidelines
20/94
PRIGuidelines CDMA Service Information
Ref Doc. 169, Ver. 3.0 March 2010 14
4.6.2 Maximum PRL Size for EFEPRL (notused in OMH context)1
4.7 EFSP[6F37]2
Definition: This EF identifies Service Preferences.3
Size (bytes): 1 (fixed)4
4.7.1 System A/B Preference5
Definition: This EF indicates the System A/B Preference.6
Allowed Range:7
No preference8
A preferred9
B preferred10
A only11
B only12
Typical Value: No preference13
4.7.2 Analog/CDMA Preference14
Definition: This EF indicates the Analog/CDMA Preference.15
Allowed Range:16
No preference17
Analog preferred18
CDMA preferred19
Analog only20
CDMA only21
Typical Value: CDMA Preferred22
4.8 EFECC[6F47]23
Definition: This EF identifies Emergency Call Codes.24
Size (bytes): 3n (n
-
8/8/2019 [Cdg169] Omh Pri Guidelines
21/94
PRIGuidelines CDMA Service Information
Ref Doc. 169, Ver. 3.0 March 2010 15
Allowed Range: 05 emergency call codes wherein each emergency call code is a1
maximum of 6 digits2
Typical Value: Operator specific3
4.9 EFSSFC[6F3F]4
Definition: This EF identifies the Supplementary Services Feature Code Table. It stores5
the numeric feature code to be used by the ME when a supplementary service is6
invoked in CDMA or analog mode via an implementation-dependent user interface (such7
as a menu) that automatically inserts a feature code into the dialed digit string. Because8
feature codes are service-provider specific, this EF is required to enable the ME to9
perform the mapping to the feature code.10
When a supplementary service is invoked in CDMA or analog mode, the mobile station11
shall determine the feature code by reading the Supplementary Service Feature Code12
Table entry for the selected supplementary service, and pre-pending with an asterisk.13
Size (bytes): Variable14
Note: A feature code of up to four digits shall be encoded via BCD into the two bytes of15
the feature code table entry as follows:16
Represent these four digits as D1D2D3D4.17
If a feature code (FC) of fewer than four digits is used, the digits shall be right justified18and the unused digits shall be set to F.19
The following feature codes are available, each with a maximum size of 4 decimal digits:20
CD Activate Feature Code: Call Delivery21
CD De-Activate Feature Code: Call Delivery22
CFBRegister New Forward-to Number Feature Code: Call Forwarding Busy23
CFBRegister to Voice Mail Feature Code: Call Forwarding Busy24
CFB De-Register Feature Code: Call Forwarding Busy25
CFB Activate Feature Code: Call Forwarding Busy26
CFB De-Activate Feature Code: Call Forwarding Busy27
CFDRegister New Forward-to Number Feature Code: Call Forwarding Default28
CFDRegister to Voice Mail Feature Code: Call Forwarding Default29
CFD De-Register Feature Code: Call Forwarding Default30
CFD Activate Feature Code: Call Forwarding Default31
CFD De-Activate Feature Code: Call Forwarding Default32
CFNA Register New Forward-to Number Feature Code: Call Forwarding No33Answer34
CFNA Register to Voice Mail Feature Code: Call Forwarding No Answer35
CFNA De-Register Feature Code: Call Forwarding No Answer36
CFNA Activate Feature Code: Call Forwarding No Answer37
-
8/8/2019 [Cdg169] Omh Pri Guidelines
22/94
PRIGuidelines CDMA Service Information
Ref Doc. 169, Ver. 3.0 March 2010 16
CFNA De-Activate Feature Code: Call Forwarding No Answer1
CFURegister New Forward-to Number Feature Code: Call Forwarding 2Unconditional3
CFURegister to Voice Mail Feature Code: Call Forwarding Unconditional4
CFU De-Register Feature Code: Call Forwarding Unconditional5
CFU Activate Feature Code: Call Forwarding Unconditional6
CFU De-Activate Feature Code: Call Forwarding Unconditional7
CW Activate Feature Code: Call Waiting8
CW De-Activate Feature Code: Call Waiting9
CW Cancel (Temporarily) Feature Code: Cancel Call Waiting10
CNIR Activate (per-call blocking) Feature Code: Calling Number ID Restriction11
CNIR De-Activate (per-call allowed) Feature Code: Calling Number ID Restriction12
CC Invoke Feature Code: Conference Calling13
CC Invoke Drop Last Party Feature Code: Conference Calling14
DND Activate Feature Code: Do Not Disturb15
DND De-Activate Feature Code: Do Not Disturb16
MWN Activate Alert Pip Tone Feature Code: Message Waiting Notification17
MWN De-Activate Alert Pip Tone Feature Code: Message Waiting Notification18
MWN Activate Pip Tone Feature Code: Message Waiting Notification19
MWN De-Activate Pip Tone Feature Code: Message Waiting Notification20
MWN Cancel (Temporarily) Feature Code: Cancel Message Waiting Notification21
PACA Invoke Feature Code: Priority Access and Channel Assignment22
VMR Invoke Feature Code: Voice Message Retrieval23
CNAP Activate Feature Code: Calling Name Presentation24
CNAP De-Activate Feature Code: Calling Name Presentation25
CNAR Activate Feature Code: Calling Name Restriction26
CNAR De-Activate Feature Code: Calling Name Restriction27
AC Activate Feature Code: Automatic Callback28
AC De-Activate Feature Code: Automatic Callback29
AR Activate Feature Code: AutomaticRecall30
AR De-Activate Feature Code: Automatic Recall31
USCF Register New Directory Number Feature Code: User Selectable Call32Forwarding33
RUAC Activate Feature Code: Rejection of Undesired Annoying Calls34
RUAC De-Activate Feature Code: Rejection of Undesired Annoying Calls35
AOC Invoke Feature Code: Advice of Charge36
COT Invoke Feature Code: Invoke Call Trace37
For a complete list of features, see [CS0023-D].38
-
8/8/2019 [Cdg169] Omh Pri Guidelines
23/94
Ref Doc. 169, Ver. 3.0 March 2010 17
5. OTASP/OTAPA1
5.1 EFOTAPASPC [6F34]2
Definition: This EF identifies OTAPA/SPC_Enable Settings. It contains user-entered3control information that either prevents or (else) permits network manipulation of the4Service Programming Code (SPC), and either prevents or (else) permits OTAPA to be5performed on the NAM.6
Size (bytes): 1 (fixed)7
5.1.1 OTAPA_Enable8
Definition: This sets forth user-entered control information that either prevents or (else)9
permits Over-the-Air Parameter Administration (OTAPA) to be performed on the NAM.10
Allowed Range:11
True12
False13
Typical Value: True14
Note: For OTAPA_Enable, a value of 0 for the NAM indicates that the user consents to15the performance of OTAPA for the NAM by the service provider. A value of 1 indicates16
that the user does not permit OTAPA to be performed on the NAM.17
5.1.2 SPC_Change_Enable18
Definition: This EF sets forth user-entered control information that either prevents or19
(else) permits network manipulation of the SPC.20
Allowed Range:21
True22
False23
Typical Value: True24
Note: For SPC_Change Enable, a value of 0 for the R-UIM indicates that the user25consents to allow the service provider to change the value of the SPC. A value of 126indicates that the user denies permission for the service provider to change the value of27the SPC.28
-
8/8/2019 [Cdg169] Omh Pri Guidelines
24/94
PRIGuidelines OTASP/OTAPA
Ref Doc. 169, Ver. 3.0 March 2010 18
5.2 EFNAMLOCK [6F35]1
Definition: This EF identifies NAM_LOCK Settings.2
Size (bytes): 1 (fixed)3
5.2.1 Current NAM Lock State4
Definition: This indicates whether NAM is locked by the Subscriber Parameter5
Administration Security Mechanism (SPASM).6
Allowed Range:7
Locked8
Unlocked9
Typical Value: Locked10
Note: A value of 1 indicates that the NAM is locked by the SPASM protection11mechanism. A value of 0 indicates that the NAM is unlocked.12
5.2.2 Permanent NAM Lock Setting13
Definition: This indicates whether or not the SPASM protection mechanism must be14
satisfied for network-initiated OTA.15
Allowed Range:16
On17
Off18
Typical Value: On19
Note: A value of 1 indicates that the SPASM protection mechanism must be satisfied20 for network-initiated OTA. A value of 0 indicates that SPASM protection is not required.21
5.2.3 Current OTA Mode22
Definition: This indicates whether the current OTA session is network- or user-initiated.23
Allowed Range:24
Network-initiated25
User-initiated26
Typical Value: User-initiated27
Note: A
value of 0 indicates user-initiated, and a value of 1 indicates network-28initiated.29
-
8/8/2019 [Cdg169] Omh Pri Guidelines
25/94
PRIGuidelines OTASP/OTAPA
Ref Doc. 169, Ver. 3.0 March 2010 19
5.3 EFOTA [6F36]1
Definition: This EF identifies OTASP/OTAPA features. The EF stores a listing of the2
following OTASP/OTAPA features supported by the R-UIM, along with protocol revision3
codes, each with an allowed range of 0255:4
DATA_P_R
EV ID OTA Feature: NAM Download5
DATA_P_REV OTA Feature: NAM Download6
A_KEY_P_REV ID OTA Feature: Key Exchange7
A_KEY_P_REV OTA Feature: Key Exchange8
SSPR_P_REV OTA Feature: System Selection for PreferredRoaming9
SPL_P_REV ID OTA Feature: Service Programming Lock10
SPL_P_REV OTA Feature: Service Programming Lock11
OTAPA_P_REV ID OTA Feature: OTAPA12
OTAPA_P_REV OTA Feature: OTAPA13
PUZL_P_R
EV ID OTA Feature: Preferred User Zone List14
PUZL_P_REV OTA Feature: Preferred User Zone List15
3GPD_P_REV ID OTA Feature: 3GPD16
3GPD_P_REV OTA Feature: 3GPD17
SECURE_MODE_P_REV ID OTA Feature: Secure MODE18
SECURE_MODE_P_REV OTA Feature: Secure MODE19
Size (bytes): 2N+1 (where N is the number of OTASP/OTAPA features supported)20
5.4 EFSPC [6F33]21
Definition: This EF includes the Service Programming Code (SPC).22
Size (bytes): 3 (fixed)23
5.4.1 Service Programming Code24
Definition: This parameter cites the security code that provides access to service25programming for individual service provider networks.26
Allowed Range: 6 decimal digits from 09, random27
Typical Value: Operator specific28
Note: The SPC is a simple means to protect the contents of theR
-UIM from being29
programmed without authorization.30
-
8/8/2019 [Cdg169] Omh Pri Guidelines
26/94
PRIGuidelines OTASP/OTAPA
Ref Doc. 169, Ver. 3.0 March 2010 20
5.5 EFSPCS [6F46]1
Definition: This EF identifies the Security Programming Code Status. This identifies2whether the EFSPC(Service Programming Code) is set to default and internally updated3in the card to reflect the current state of SPC after an OTASP commit if the SPC was4changed.5
Size (bytes): 1 (fixed)6
5.5.1 SPC Status7
Definition: This parameter identifies the Security Programming Code Status.8
Allowed Range:9
OFF: SPC has the default value10
ON: SPC is set to other value11
Typical Value: ON12
13
-
8/8/2019 [Cdg169] Omh Pri Guidelines
27/94
Ref Doc. 169, Ver. 3.0 March 2010 21
6. Carrier Customization1
6.1 EFSPN [6F41]2
Definition: This EF identifies the CDMA Home Service Provider Name (SPN). The3
operator should allocate n17 in EF_CST and provision the following parameters, if4
CDMA Home service provider name is to be displayed when the MS is in the Home5
Service area.6
Size (bytes): 35 (fixed)7
6.1.1 SPN Display Condition8
Definition: This indicates whether or not a Service Provider Name should be displayed9
when the MS is registered in the home service area.10
Allowed Range:11
OFF: display is not required12
ON: display is required13
Typical Value: ON14
6.1.2 SPN Character Encoding15
Definition: This contains encoding for the SPN string.16
Allowed Range:17
7-bit ASCII18
IA519
UNICODE20
Typical Value: 7-bit ASCII21
6.1.3 SPN Language Indicator22
Definition: This contains the Language Indicator for the SPN string.23
Allowed Range:24
English25
French26
Spanish27
Japanese28
-
8/8/2019 [Cdg169] Omh Pri Guidelines
28/94
PRIGuidelines Carrier Customization
Ref Doc. 169, Ver. 3.0 March 2010 22
Korean1
Chinese2
Hebrew3
Typical Value: English4
6.1.4 SPN String5
Definition: This contains the actual Service Provider Name string.6
Allowed Range: 32-byte string7
Typical Value: The value needs to be specified by the Operator.8
6.2 EFAppLabels [6F92]9
Definition: Application Labels are used for carrier customization. They are used by10
devices to display operator-branded services. The text label the operator desires to11
provision in this EF is the text associated with the icon or menu item used to launch the12
application, such as BREW, MMS, Browser, etc.13
These labels are optional and need only be provisioned if an operator desires to override14
the handset vendor-defined labels.15
Note: In the absence of the application labels provisioned by an operator, the device will16
display the default values.17
Size (bytes): 4+N*32 (where N is the number of application labels)18
Typical EF Size (bytes): 132 bytes (assumes 4 application labels)19
Maximum EF Size (bytes): 516 byes (assumes 16 application labels)20
6.2.1 App Label Character Encoding21
Definition: This parameter specifies the encoding for Application Labels.22
Allowed Range:23
Octet (unspecified)24
7-bit ASCII25
IA526
UNICODE unspecified27
Typical Value: 7-bit ASCII28
6.2.2 Language of App Labels29
Definition: This parameter specifies the Language in which application labels are30
provisioned.31
-
8/8/2019 [Cdg169] Omh Pri Guidelines
29/94
PRIGuidelines Carrier Customization
Ref Doc. 169, Ver. 3.0 March 2010 23
Allowed Range:1
English2
French3
Spanish4
Japanese5 Korean6
Chinese7
Hebrew8
Typical Value: 7-bit ASCII9
6.2.3 MMS App Label10
Definition: This parameter specifies the text label for the MMS application icon or menu11
item.12
Allowed Range: 32-byte string13
Typical Value: Operator specific14
6.2.4 WAP Browser App Label15
Definition: This parameter specifies the text label for the WAP Browser application or16
menu item.17
Allowed Range: 32-byte string18
Typical Value: Operator specific19
6.2.5 BREW App Label20
Definition: This parameter specifies the text label for the BREW application downloader21
icon or menu item.22
Allowed Range: 32-byte string23
Typical Value: Operator specific24
6.2.6 Java App Label25
Definition: This parameter specifies the text label for the Java application downloader26
icon or menu item.27
Allowed Range: 32-byte string28
Typical Value: Operator specific29
30
-
8/8/2019 [Cdg169] Omh Pri Guidelines
30/94
PRIGuidelines Carrier Customization
Ref Doc. 169, Ver. 3.0 March 2010 24
1
2
3
4
-
8/8/2019 [Cdg169] Omh Pri Guidelines
31/94
Ref Doc. 169, Ver. 3.0 March 2010 25
7. Root Certificates1
7.1 EFRC[6F91]2
Definition: The root certificates are used for operator-signed applications. If the same3
root certificate is used for all operator-signed applications, then the application bit mask4
is set to Unspecified. If not, the application bit for each application shall be set5
accordingly.6
The operator should allocate n16 in EF_CST and provision the following parameters, if7
root certificates are to be used on its network.8
Note:Root certificates are not mandatory for operators to use. Only in cases where the9
operators applications are signed using root certificates they would need to be10
provisioned.11
Size (bytes): Typical EF size (bytes): 1500 bytes (assumes one 1.5kB certificate)12
7.1.1 Certificate Type13
Definition: This parameter identifies the type of certificate.14
Allowed Range:15
DER Encoded Binary X.50916
Base64 Encoded X.50917
PKCS #718
PKCS #1219
Typical Value: This is the actual certificate type used by the operator.20
7.1.2 Certificate Information21
Definition: This is the actual certificate used by the operator encoded according to the22
type specified in Section 7.1.123
Allowed Range: N/A24
Typical Value: N/A25
7.1.3 Associated Applications26
Definition: This parameter identifies which applications are associated with this27
certificate. One, multiple, or all applications may be associated with a certificate.28
-
8/8/2019 [Cdg169] Omh Pri Guidelines
32/94
PRIGuidelines Root Certificates
Ref Doc. 169, Ver. 3.0 March 2010 26
Allowed Range: 1 or more of the following:1
Unspecified (i.e., all)2
WAP Browser3
BREW4
Java5 LBS6
Terminal7
Typical Value: This parameter identifies the applications selected by an operator to use8
with the actual certificate defined in Section 7.1.2.9
-
8/8/2019 [Cdg169] Omh Pri Guidelines
33/94
Ref Doc. 169, Ver. 3.0 March 2010 27
8. SMS Basic1
8.1 EFSMSCAP [6F76]2
Definition: The operator should allocate n4 in EF_CST and provision the following3
parameters, if SMS service is supported on its network.4
Size (bytes): 4 (fixed)5
8.1.1 SMS Retry Period6
Definition: This is the overall time period (in seconds) during which the Mobile7
Originated (MO) SMS retries can be performed. A value of 0 implies that MO SMS retry8
is disabled.9
Allowed Range: 0255 seconds10
Typical Value: 3060 seconds11
Note: The SMS retry period needs to be larger than the SMS retry interval period.12
8.1.2 SMS Retry Interval13
Definition: This is the time interval (in seconds) that the device shall wait before the14next retry attempt can be made after an MO SMS failure.15
Allowed Range: 0255 seconds16
Typical Value: 35 seconds17
Note: The SMS retry interval needs to be smaller than SMS retry period. Setting this to a18
value smaller than 5 seconds could lead to multiple SMS originations being sent before19
a delayed acknowledgment to the previous SMS attempt is received.20
8.1.3 SMS Send on Access Flag21
Definition: This flag indicates whether the operator wants to allow messages to be sent22over Access Channel.23
Allowed Range:24
True25
False26
Typical Value: True27
-
8/8/2019 [Cdg169] Omh Pri Guidelines
34/94
PRIGuidelines SMS Basic
Ref Doc. 169, Ver. 3.0 March 2010 28
8.1.4 SMS Send on Traffic Flag1
Definition: This flag indicates whether the operator wants to allow messages to be sent2
over Traffic Channel.3
Allowed Range:4
True5
False6
Typical Value: True7
8.1.5 SMS Send Standard EMS Flag8
Definition: This parameter specifies whether to allow Long SMS (LMS) messages to be9
sent as standard Enhanced Messaging Service (EMS) messages.10
Allowed Range:11
True12
False13
Typical Value: False (unless operators network supports EMS)14
8.1.6 SMS Preferred Service Option15
Definition: This is the preferred service option to be used by the device when it sets up16
SMS traffic channel for sending SMS.17
Allowed Range:18
Device Default19
Service Option 620 Service Option 1421
Typical Value: Service Option 622
Note: This is what the device uses for origination, but the traffic channel assignment23
sent by the BS will override the service option if different from that used by the device.24
-
8/8/2019 [Cdg169] Omh Pri Guidelines
35/94
Ref Doc. 169, Ver. 3.0 March 2010 29
9. SMS Broadcast1
9.1 EFBCSMScfg [6F5B]2
Definition: Broadcast SMS messages are messages sent by the Base Station (BS) to3
the Mobile Stations. They can be sent on the Paging Channel, Forward Common Control4
Channel, or the Broadcast Control Channel. These messages can also be sent to5
individual mobile stations on the Forward Traffic Channel.6
The operator should allocate n14 in EF_CST and provision the following parameters, if7
Broadcast SMS service is supported on its network.8
Size (bytes): 1 (fixed)9
9.1.1 Broadcast SMS Config10
Definition: This indicates the operator broadcast configuration setting for Broadcast11SMS. This information, determined by the operator, defines the filtering criteria that can12be used by the ME to receive Broadcast SMS.13
Allowed Range:14
Disallow15
Allow table only16
Allow all17
Typical Value: Allow All18
Note: The choices in the allowed range indicate the following:19
Disallow: This setting disables the mobile stations broadcast SMS capability (i.e., the20mobile station will not process broadcast SMS).21
Allow Table Only: This setting allows the mobile station to receive only broadcast22messages for the service categories that have been programmed in EFBCSMStable.23
Allow All: This setting allows the mobile station to receive broadcast messages for all24service categories.25
9.2 EFBCSMSTable [6F5D]26
Definition: This EF contains information in accordance with comprising service category27program parameters, which can be used by the ME for Broadcast SMS filtering.28
Size (bytes): Variable29
-
8/8/2019 [Cdg169] Omh Pri Guidelines
36/94
PRIGuidelines SMS Broadcast
Ref Doc. 169, Ver. 3.0 March 2010 30
9.2.1 Service Information: Category1
Definition: This field contains the value of the Service Category for the operation.2
UNKNOWN3
EMERGENCY4
ADMIN5
MAINTENANCE6
General News Local7
General News Regional8
Etc.9
Typical Value: Operator specific10
Note: Note that the list of categories above is only a subset and not the complete list11
9.2.2 Service Information: Language12
Definition: This parameter specifies the Language used for the message text.13
Allowed Range:14
English15
French16
Spanish17
Japanese18
Korean19
Chinese20
Hebrew21
Typical Value: English22
9.2.3 Service Information: Max Messages23
Definition: This field shall be set to the Maximum Number of Messages that may be24
stored in the ME for this service category.25
Allowed Range: 025526
Typical Value: 25527
9.2.4 Service Information: Alert Option28
Definition: This parameter specifies the alert option to be used when the mobile station29
receives a message for this service category. This field shall be set according to Table30
4.5.19-1 of [CS0015-B].31
Allowed Range:32
NONE33
-
8/8/2019 [Cdg169] Omh Pri Guidelines
37/94
PRIGuidelines SMS Broadcast
Ref Doc. 169, Ver. 3.0 March 2010 31
MS Default Alert1
VIBRATE_ONCE2
VIBRATE_REPEAT3
VISUAL_ONCE4
VISUAL_R
EPEAT5
LOW_PRIORITY_ONCE6
LOW_PRIORITY_REPEAT7
MEDIUM_PRIORITY_ONCE8
MEDIUM_PRIORITY_REPEAT9
HIGH_PRIORITY_ONCE10
HIGH_PRIORITY_REPEAT11
Typical Value: Operator specific12
9.2.5 Service Information: Label Encoding13
Definition: This parameter defines the encoding scheme used for the label.14
Allowed Range:15
7-bit ASCII16
IA517
UNICODE18
Typical Value: 7-bit ASCII19
9.2.6 Service Information: Label20
Definition: This is the actual text specified by the operator for the service.21
Allowed Range: Up to 258 bytes of characters22
Typical Value: Operator specific23
9.3 EFBCSMSP [6F5E]24
Definition: This EF specifies the parameters used for the Broadcast SMS.25
Size (bytes): 2 (record)26
9.3.1 Service Information: Selected Flag27
Definition: This parameter indicates whether service is selected or not by the operator.28
Allowed Range:29
True30
False31
Typical Value: Operator specific32
-
8/8/2019 [Cdg169] Omh Pri Guidelines
38/94
PRIGuidelines SMS Broadcast
Ref Doc. 169, Ver. 3.0 March 2010 32
9.3.2 Service Information: Priority1
Definition: This parameter identifies the priority level of service.2
Allowed Range:3
Normal4
Urgent5
Emergency6
Typical Value: Normal7
8
-
8/8/2019 [Cdg169] Omh Pri Guidelines
39/94
Ref Doc. 169, Ver. 3.0 March 2010 33
10. 3GPD Basic1
10.1 EFME3GPDOPC [6F48]2
Definition: If either service n20 or n38 is allocated (see Section 3.4.18 of [CS0023-D]),3
this EF shall be present. This parameter specifies the operation modes supported by the4
ME. The ME sets this field in the form of a bitmap as defined in [ CS0016-B].5
Size (bytes): 1 (fixed)6
10.1.1 3GPD Operation Capability7
Definition: This EF stores IP operation capabilities supported by the ME. After the8selection of DFCDMA (7F25) during the initialization, the R-UIM shall set the value of9this byte to 0. Mobile equipment that supports Simple IP or Mobile IP shall set each10subfield to 1 if it supports the corresponding operating mode.11
Allowed Range: One or more of the following:12
SimpleIP Supported13
MobileIP Supported14
MobileIP with SimpleIP Fallback supported15
Typical Value: Does not need to be provisioned by the operator16
10.2 EF3GPDOPM [6F49]17
Definition: If either service n20 or n38 is allocated (see Section 3.4.18 of [CS0023-D]),18this EF shall be present.19
Size (bytes): 1 (fixed)20
10.2.1 3GPD Operation Mode21
Definition: This EF stores the 3GPD Operation Mode Parameter Block. For further22details, refer to 3GPP2 [CS0016-B] and [CS0023-D].23
Allowed Range:24
SimpleIP25
MobileIP26
MobileIP with SimpleIP Fallback27
Typical Value: Simple IP28
-
8/8/2019 [Cdg169] Omh Pri Guidelines
40/94
PRIGuidelines 3GPD Basic
Ref Doc. 169, Ver. 3.0 March 2010 34
10.3 EFTCPConfig [6F79]1
Definition: This EF contains information about Transmission Control Protocol (TCP)2
configurations. If service n20 (3GPD-SIP) or n38 (3GPD-MIP) is allocated and service3
n15 (Messaging and 3GPD Extensions) is allocated, this EF shall be present.4
Size (bytes): 2 (fixed)5
10.3.1 TCP Graceful Close of Dormant Connections6
Definition: This parameter specifies whether the TCP socket should be closed7
gracefully, even if the underlying interface is dormant.8
Allowed Range:9
True10
False11
Typical Value: False12
Note: If the value of this flag is TRUE, this means that the TCP socket should be closed13
gracefully. This in turn means that the network connection will be brought out of14
dormancy and the TCP FIN will be sent out on the network. If the value of this flag is set15
to FALSE, the local TCP connection will be closed forcefully without going through the16
TCP graceful close cycle.17
10.3.2 TCP Keep Alive Idle Timer18
Definition: This configuration item is used primarily to deal with dead TCP peers. If19
there is no TCP message being sent from the peer for the TCP Keep Alive Idle Timer,20
then keep-alive probes will be sent to the peer. With a default value of 120 minutes, the21
mobile would not send keep-alive probes for at least 120 minutes when there is no TCP22
activity from the remote end.23
Allowed Range: 0255 minutes24
Typical Value: 120 minutes25
Note:A value of 0 means that the TCP keep-alive feature is disabled on the ME.26
10.4 EFDGC [6F7A]27
Definition: This EF specifies miscellaneous data configuration items.28
Size (bytes): 3 (fixed)29
10.4.1 Data Dormant Timer30
Definition: This parameter specifies the number of seconds to wait before going into31
data dormant mode, which shall be at least 20 seconds.32
-
8/8/2019 [Cdg169] Omh Pri Guidelines
41/94
PRIGuidelines 3GPD Basic
Ref Doc. 169, Ver. 3.0 March 2010 35
Allowed Range: 20255 seconds1
Typical Value: 30 seconds2
10.4.2 EPZID Type3
Definition:4
Allowed Range:5
Packet Zone ID6
Packet Zone ID plus SID7
Packet Zone ID plus SID and NID8
Typical Value: Packet Zone ID plus SID and NID9
10.4.3 Hysteresis Activation Time10
Definition: This parameter specifies the number of seconds the device should wait11
before it adds a new Packet Zone ID.12
Allowed Range: 0255 seconds13
Typical Value: 30 seconds14
15
16
-
8/8/2019 [Cdg169] Omh Pri Guidelines
42/94
PRIGuidelines 3GPD Basic
Ref Doc. 169, Ver. 3.0 March 2010 36
1
2
3
4
5
-
8/8/2019 [Cdg169] Omh Pri Guidelines
43/94
Ref Doc. 169, Ver. 3.0 March 2010 37
11. 3GPD Simple IP1
11.1 EFSIPCAP [6F4A]2
Definition: This parameter specifies the SimpleIP Capability Parameter Block defined in3
[CS0016-C].4
The operator should allocate n20 in EF_CST and provision the following parameters, if5
3GPD Simple IP is supported on its network.6
Size (bytes): 4 (fixed)7
11.1.1 Simple IP Max Number of NAIs8
Definition: This parameter defines the total number of Network Address Identifiers9
(NAIs) that an operator intends to use. If an operator needs to specify different10
NAIs/usernames for the different applications or groups of applications, then multiple11
profiles are used.12
Allowed Range: 01513
Typical Value: Operator specific14
Note: Most operators worldwide use a single NAI/username profile shared by all15
applications. In cases where an operator requires a separate NAI/password profile for16
each of the applications (or groups of applications) requiring differing treatment* at the17
network end, multiple profiles may be used.18
11.1.2 SIP Max NAI Length19
Definition: This parameter specifies the maximum length of Simple IP NAI. This value20
specifies the maximum memory allocated in the card for this field.21
Allowed Range: 025522
Typical Value: 25523
11.1.3 SIP Max SS Length24
Definition: This parameter specifies the maximum length of the Simple IP password.25
This value specifies the maximum memory allocated in the card for this field.26
* Billing, Routing, etc.
-
8/8/2019 [Cdg169] Omh Pri Guidelines
44/94
PRIGuidelines 3GPD Simple IP
Ref Doc. 169, Ver. 3.0 March 2010 38
Allowed Range: 0311
Typical Value: 312
11.1.4 SIP Authentication Algorithms3
Definition: This parameter specifies the authentication algorithm used for PDSN4authentication.5
Allowed Range:6
PAP7
CHAP8
CHAP & PAP9
Typical Value: CHAP & PAP both10
11.2 EFSIPSP [6F4E]11
Definition: This EF stores the SimpleIP Status Parameters Block defined in [CS0016-B].12
If service n20 is allocated, this EF shall be present.13
Size (bytes): 1 (fixed)14
11.2.1 ACT_NAI_ENTRY_INDEX15
Definition: This specifies the active SimpleIP NAI entry index.16
Allowed Range: 01517
Typical Value: 0 (when all applications are using one profile)18
11.3 EFSIPUPP [6F4C]19
Definition: This parameter specifies the SimpleIP User Profile Parameter Block defined20
in [CS0016-C].21
Size (bytes): Variable [(N*(X+2))+2], where N is the number of Simple IP profiles and N22
is the maximum NAI length.23
11.3.1 NUM_NAI24
Definition: This parameter specifies the number of applications having different simple25
IP profiles.26
Allowed Range: 01527
Typical Value: Operator specific28
Note: In order to enable Mobile IP to Simple IP fallback, NAI Entry Indexes used in SIP29
and MIP User Profiles must be the same.30
-
8/8/2019 [Cdg169] Omh Pri Guidelines
45/94
PRIGuidelines 3GPD Simple IP
Ref Doc. 169, Ver. 3.0 March 2010 39
11.3.2 Profile Information: NAI Entry Index1
Definition: This parameter provides the index to the NAI profile.2
Allowed Range: 0153
Typical Value: Operator specific4
Note: In order to enable Mobile IP to Simple IP fallback, NAI Entry Indexes used in SIP5
and MIP User Profiles must be the same.6
11.3.3 Profile Information: NAI7
Definition: This parameter specifies the Network Address Identifier.8
Allowed Range: Up to 255 ASCII characters9
Typical Value: Operator specific10
Note: The NAI should be chosen and managed using procedures that minimize the11
likelihood of compromise.12
11.3.4 Profile Information: Authentication Algorithm13
Definition: This parameter specifies the authentication algorithm used by the operator14
for PDSN authentication.15
Allowed Range:16
None17
CHAP18
PAP19
CHAP with PAP fallback20
Typical Value: CHAP & PAP21
Note: Always CHAP & PAP for OMH.22
11.4 EFSIPUPPExt [6F7D]23
Definition: This EF contains the additional parameters for Simple IP User Profiles in24
order to fully support the feature of multiple profiles. NUM_NAI is the same as NUM_NAI25
in SIPUPP as per Section 11.3 of this document. Each index in SIPUPP ext maps to the26
same index in SIPUPP.27
Size (bytes): Variable28
Typical EF Size (bytes): 7 bytes (assumes the common usage of one profile for all29applications)30
Maximum EF Size (bytes): 98 bytes (assumes a wildly unlikely usage of 15 different31profiles)32
-
8/8/2019 [Cdg169] Omh Pri Guidelines
46/94
PRIGuidelines 3GPD Simple IP
Ref Doc. 169, Ver. 3.0 March 2010 40
11.4.1 NUM_NAI1
Definition: This parameter specifies the total number of NAIs used for various2
applications.3
Allowed Range: 0154
Typical Value: Operator specific5
11.4.2 Profile Information: NAI Entry Index6
Definition: This parameter indicates the index for the particular application using the7
simple IP profile.8
Allowed Range: 0159
Typical Value: Operator specific10
Note: In order to enable Mobile IP to Simple IP fallback, NAI Entry Indexes used in SIP11
and MIP User Profiles must be the same.12
11.4.3 Profile Information: Applications13
Definition: This parameter specifieswhich applications are associated with this profile.14
One, multiple, or all applications may be associated with a profile. The applications shall15
use the profile with the unspecified bit set in the Applications bit mask if they are not16
present in any other profile.17
Allowed Range:18
Unspecified19
MMS20
WAP Browser21
BREW22
Java23
LBS24
Terminal25
Typical Value: Unspecified26
11.4.4 Profile Information: Priority27
Definition: Application priority. This parameter specifies the priority the device may use28
when launching a particular application.29
Allowed Range:30
Value Priority31
0 Highest priority category32
1 Second highest priority category (lower than 0; higher than 2+)33
-
8/8/2019 [Cdg169] Omh Pri Guidelines
47/94
PRIGuidelines 3GPD Simple IP
Ref Doc. 169, Ver. 3.0 March 2010 41
2 Third highest priority category (lower than 0 or 1; higher than 3+)1
255 Lowest priority2
Typical Value: Operator specific3
11.4.5 Profile Information: Data Rate Mode4
Definition: This parameter specifies whether the data rate mode for a particular profile5
is low speed, medium speed or high speed6
Allowed Range:7
Low8
Medium9
High10
Typical Value: High11
11.4.6 Profile Information: Data Bearer12
Definition: This parameter specifies the data bearer to be used for a particular profile.13
Allowed Range:14
Hybrid 1xEV-DO/1x15
1x Only16
1xEV-DO Only17
Typical Value: Hybrid 1xEV-DO/1x18
11.5 EFSIPPAPSS [6F50]19
Definition: This is the Simple IP PAP password.20
Size (bytes): Variable21
11.5.1 Profile Information: PAP SS22
Definition: This parameter specifies the simple IP PAP Shared Secret the operator uses23
for PDSN authentication.24
Allowed Range: Up to 31 bytes of binary data.25
Typical Value: Operator specific26
Note: The password of choiceshould be a unique NAI and password for each27
subscription. A randomized password should also be selected, preferably of size 1628
bytes.29
-
8/8/2019 [Cdg169] Omh Pri Guidelines
48/94
PRIGuidelines 3GPD Simple IP
Ref Doc. 169, Ver. 3.0 March 2010 42
11.6 EFSIPCHAPSS [Hidden]1
Definition: This EF specifies the Simple IP CHAP shared secret.2
Size (bytes): Operator/R-UIM vendor specific3
11.6.1 Profile Information: CHAP SS4
Definition: This parameter specifies the Simple IP CHAP SS value used by an operator5
for PDSN authentication.6
Allowed Range: 31 bytes of binary data.7
Typical Value: Operator specific8
9
10
-
8/8/2019 [Cdg169] Omh Pri Guidelines
49/94
Ref Doc. 169, Ver. 3.0 March 2010 43
12. 3GPD Mobile IP1
12.1 EFMIPCAP [6F4B]2
Definition: This parameter specifies the MobileIP Capability Parameter Block defined in3
[CS0016-C].4
The operator should allocate n38 in EF_CST and provision the following parameters, if5
3GPD Mobile IP service is supported on its network.6
Size (bytes): 5 (fixed)7
12.1.1 MIP Max Number of NAIs8
Definition: This parameter specifies the maximum number of NAIs used by an operator.9
Allowed Range: 01510
Typical Value: 111
12.1.2 MIP Max NAI Length12
Definition: This parameter specifies the maximum length of the Mobile IP NAI. This13
value specifies the maximum memory allocated in the card for this field.14
Allowed Range: 025515
Typical Value: 25516
12.1.3 MIP Max MN-AAA SS Length17
Definition: This parameter specifies the maximum length, in units of octet, of the shared18
secret data (MN-AAA) supported by the R-UIM. If the SS length is greater than 16 bytes,19
it needs to be ensured that the card vendor supports this SS length. This value specifies20
the maximum memory allocated in the card for this field.21
Allowed Range: 03122
Typical Value: 3123
12.1.4 MIP MN-AAA Authentication Algorithm24
Definition: This parameter specifies theauthentication algorithm (MN-AAA) used by the25
mobile station to authenticate itself to the PDSN/Foreign Agent (FA).26
27
-
8/8/2019 [Cdg169] Omh Pri Guidelines
50/94
PRIGuidelines 3GPD Mobile IP
Ref Doc. 169, Ver. 3.0 March 2010 44
Allowed Range: MD51
Typical Value: MD52
12.1.5 MIP Max MN-HA SS Length3
Definition: Specifies the maximum length, in units of octet, of the shared secret data4(MN-HA) supported by the R-UIM. This value specifies the maximum memory allocated5
in the card for this field.6
Allowed Range: 0317
Typical Value: 318
12.1.6 MIP MN-HA Authentication Algorithm9
Definition: This parameter specifies the authentication algorithm (MN-HA) used by the10
mobile station to authenticate itself to the Home Agent.11
Allowed Range: MD512
Typical Value: MD513
12.2 EFMIPSP [6F4F]14
Definition: This EF specifies the MobileIP Status Parameters Block defined in [CS0016-15
B]. If service n38 is allocated, this EF shall be present.16
Size (bytes): Variable17
Typical Size (bytes): 1 (assuming 1 MIP profile)18
Maximum Size (bytes): 8 (assuming 15 MIP profiles)19
12.2.1 Active NAI Entry Index20
Definition: This parameter specifies the Active MobileIP NAI entry index.21
Allowed Range: 01522
Typical Value: 023
12.3 EFMIPUPP [6F4D]24
Definition: This parameter specifies the Mobile IP User Profiles Profile Parameter Block25
defined in [CS0016-B].26
Size (bytes): Variable27
12.3.1 MIP Registration Max Re-tries28
Definition: This parameter specifies the maximum number of retries for Mobile IP29
Registration.30
-
8/8/2019 [Cdg169] Omh Pri Guidelines
51/94
PRIGuidelines 3GPD Mobile IP
Ref Doc. 169, Ver. 3.0 March 2010 45
Allowed Range: 031
Typical Value: 32
Note: The maximum time until a new Registration Request is sent shouldnot be greater3
than the requested Lifetime of the Registration Request.4
12.3.2 MIP Registration First Retry Timeout5
Definition: This parameter specifies the amount of time elapsed between the first and6
second MobileIP Registration Requests, while the mobile station did not receive the7
MobileIP Registration Reply.8
Allowed Range: 18, in units of 250ms9
Typical Value: 810
Note: 18 should be provisioned on R-UIM as 07, and the device will derive a timeout11
value by adding 1000ms to this timeout value per [RFC 2002].12
12.3.3 MIP Re-Registration Threshold13
Definition: This specifies the time before the lifetime expiration when the mobile14
attempts re-registration. It is the pre-lifetime expiration re-registration timer.15
Allowed Range: 063 minutes16
Typical Value: 6317
Note:Registration lifetime is the number of seconds remaining before the registration is18
considered expired. A value of zero indicates a request for deregistration. A value of19
0xffff indicates infinity.20
12.3.4 Profile Information: NAI Entry Index21
Definition: This parameter specifies the number of profiles used for mobile IP.22
Allowed Range: 01523
Typical Value: The value depends on the number of profiles an operator uses for its24
applications.25
Note: In order to enable Mobile IP to Simple IP fallback, NAI Entry Indexes used in SIP26
and MIP User Profiles must be the same.27
12.3.5 Profile Information: NAI28
Definition: This parameter specifies the actual Network Address Identifier assigned by29
the operator.30
Allowed Range: Up to 255 ASCII characters31
Typical Value: Operator specific32
-
8/8/2019 [Cdg169] Omh Pri Guidelines
52/94
PRIGuidelines 3GPD Mobile IP
Ref Doc. 169, Ver. 3.0 March 2010 46
12.3.6 Profile Information: T_BIT (Reverse Tunneling flag)1
Definition:A reverse tunnel is a tunnel that starts at the mobile nodes care-of address2
and terminates at the home agent. This parameter specifies whether reverse tunneling is3
required or not. Reverse tunneling support is added directly into the Registration4
Request (RRQ) by using one of the "rsvd" bits naming it as T bit. If a foreign or home5
agent that does not support reverse tunnels receives a request with the T bit set, the6
Registration Request fails.7
Allowed Range:8
True9
False10
Typical Value: True11
12.3.7 Profile Information: Home Address12
Definition: This parameter specifies the IP address that is assigned for an extended13
period of time to a mobile node. It remains unchanged, regardless of where the node is14
attached to the Internet.15
Allowed Range:16
Typical Value: Operator specific17
12.3.8 Profile Information: Primary Home Agent18
Definition: This parameter specifies the IP address of the mobile nodes primary home19
agent. A home agent is a router on a mobile nodes home network that tunnels20
datagrams for delivery to the mobile node when it is away from home, and maintains21
current location information for the mobile node.22
Allowed Range:23
Typical Value: Operator specific24
12.3.9 Profile Information: Secondary Home Agent25
Definition: This parameter specifies the IP address of the mobile nodes secondary26
home agent in the form of network byte code.27
Allowed Range:28
Typical Value: Operator specific29
12.3.10 Profile Information: MN-AAA Auth Algorithm30
Definition: This parameter specifies the authentication algorithm used to calculate the31
Mobile IP MN-AAA Authentication Extension.32
-
8/8/2019 [Cdg169] Omh Pri Guidelines
53/94
PRIGuidelines 3GPD Mobile IP
Ref Doc. 169, Ver. 3.0 March 2010 47
Allowed Range:1
None2
MD53
Typical Value: MD54
12.3.11 Profile Information: MN-AAA SPI Indicator5
Definition: This parameter specifies the indicator of the Security Parameter Index (SPI)6
between MN and AAA.7
Allowed Range:8
None9
32-bit number10
Typical Value: Operator specific11
Note: SPI is an index identifying a security context between a pair of nodes among the12
contexts available in the Mobility Security Association.13
12.3.12 Profile Information: MN-HA Auth Algorithm14
Definition: This parameter specifies the authentication algorithm used to calculate the15
Mobile IP MN-HA Authentication Extension, as defined in IETF [RFC 2002].16
Allowed Range:17
None18
MD519
Typical Value: MD520
12.3.13 Profile Information: MN-HA SPI21
Definition: This parameter is an indicator of SPI between MN and HA.22
Allowed Range:23
None24
32-bit number25
Typical Value: Operator specific26
12.4 EFMIPUPPExt [6F80]27
Definition: This EF specifies the additional parameters for MobileIP User Profiles in28
order to fully support the feature of multiple profiles for MobileIP.29
Size (bytes): Variable30
Typical EF Size (bytes): 7 bytes (assumes the common usage of one profile for all31applications)32
-
8/8/2019 [Cdg169] Omh Pri Guidelines
54/94
PRIGuidelines 3GPD Mobile IP
Ref Doc. 169, Ver. 3.0 March 2010 48
Maximum EF Size (bytes): 98 bytes (assumes a wildly unlikely usage of 15 different1profiles)2
12.4.1 NUM_NAI3
Definition: This parameter specifies the number of MIP profiles.4
Allowed Range: 0155
Typical Value: 16
12.4.2 Profile Information: NAI Entry Index7
Definition: This parameter specifies the number of profiles used for8
Allowed Range: 0159
Typical Value: 010
Note: In order to enable Mobile IP to Simple IP fallback, NAI Entry Indexes used in SIP11
and MIP User Profiles must be the same.12
12.4.3 Profile Information: Applications13
Definition: This parameter indicates which applications are associated with this profile.14
One, multiple, or all applications may be associated with a profile.15
Allowed Range:16
Unspecified17
WAP Browser18
BREW19
Java20
LBS21
Terminal22
Typical Value: Unspecified23
12.4.4 Profile Information: Priority24
Definition: This parameter specifies the application priority associated with a particular25
profile.26
Allowed Range: 0 (highest) to 255 (lowest)27
Typical Value: 028
12.4.5 Profile Information: Data Rate Mode29
Definition: This parameter specifies the data rate to be used for a particular profile.30
-
8/8/2019 [Cdg169] Omh Pri Guidelines
55/94
PRIGuidelines 3GPD Mobile IP
Ref Doc. 169, Ver. 3.0 March 2010 49
Allowed Range:1
Low2
Medium3
High4
Typical Value: High5
12.4.6 Profile Information: Data Bearer6
Definition: This parameter specifies the data bearer to be used for a particular profile.7
Allowed Range:8
Hybrid 1xEV-DO/1x9
1x Only10
1xEV-DO Only11
Typical Value: Hybrid 1xEV-DO/1x12
12.5 EFMIPSS [Hidden]13
Definition: This EF specifies the password for Mobile IP.14
Size (bytes): Vendor specific15
12.5.1 Profile Information: MN-AAA Shared Secret16
Definition: This parameter specifies the key MN-AAA key used to compute the17
challenge response to the challenge received in the agent advertisement message. This18
is included in the authentication extension of theRRQ
and must be coordinated and19
provisioned in both the mobile and the AAA server.20
Allowed Range: up to 31 bytes of binary data21
Typical Value: Operator specific22
12.5.2 Profile Information: MN-HA Shared Secret23
Definition: This parameter specifies the shared key used by the mobile and the24
message contents to compute an authenticator value, which is included in this MN-HA25
authentication extension. Upon receiving the RRQ, the HA queries the HAAA to obtain26
the MN-HA shared key. Using its MN-HA shared key and the message contents, the HA27
calculates an authenticator value and compares this calculated value to the one28
provided by the mobile. Upon successful validation, the MIP tunnel is established, and29
the HA returns a registration reply (RRP) to the mobile indicating that MIP registration30
has been accepted.31
Allowed Range: up to 31 bytes of binary data32
Typical Value: Operator specific33
-
8/8/2019 [Cdg169] Omh Pri Guidelines
56/94
PRIGuidelines 3GPD Mobile IP
Ref Doc. 169, Ver. 3.0 March 2010 50
12.6 EFMIPFlags [6F78]1
Definition: This EF specifies the configuration flags for Mobile IP.2
Size (bytes): 1 (fixed)3
12.6.1 MIP 2002bis MN-HA Authentication4
Definition: This parameter specifies the MN-HA authentication that will include the SPI5
in the authenticator calculation.6
Allowed Range:7
True8
False9
Typical Value: True10
12.6.2 MIP Pre-Rev 6 Handoff Optimization11
Definition:This parameter specifies whether Point-to-Point (PPP) re-sync will be12performed proactively between the ME and PDSN to maintain correct PPP framing and13
to avoid not updating PPP framing and PDSN-HA binding when performing an inter-14
PDSN handoff by a ME during a MIP session, which may result in reconnection to a15
latent A10/A11 (R-P) connection. The QUALCOMM cdma2000 1X optimized dormant16
handoff algorithm (QCODH) addresses this by detecting the problematic scenario and17
proactively initiating a PPP resync between the mobile station and PDSN with zombie18
PPP state to maintain correct PPP framing.19
Allowed Range:20
True21
False22
Typical Value: True23
Note: When set to True, the mobile will actively renegotiate PPP and reregister MIP24
when it detects that it might be returning to a previously visited PDSN. This may be25
enabled or disabled by the carrier to match the capability of their deployed network to26
address zombie PPP.27
12.6.3 MIP PPP Re-sync During Hand-Down from 1xEV-DO Rev 0 to 1X28
Definition: This parameter specifies whether PPP resync on hand-down from High Data29
Rate (HDR) to 1X for a MIP call will be done or not.30
Allowed Range:31
True32
False33
Typical Value: False34
-
8/8/2019 [Cdg169] Omh Pri Guidelines
57/94
PRIGuidelines 3GPD Mobile IP
Ref Doc. 169, Ver. 3.0 March 2010 51
12.6.4 MIP Re-Registration Data Transfer to Extend MIP Address Lifetime1
Definition: This parameter specifies the need forMIP Re-Registration only if data has2
been transferred since last registration in order to extend Mobile IP address lifetime. If3
this is set, the MIP and PPP sessions for the mobile will be dropped if the link is inactive4
for the entire duration of a MIP registration. In other words, re-registration will not be5
performed unless user data (not including Mobile IP registration traffic) is transferred6
during the registration lifetime.7
Allowed Range:8
True9
False10
Typical Value: False11
Note: When set to False, the idle data sessions will remain connected indefinitely. The12
mobile will periodically send RegistrationRequests to the PDSN to refresh the mobiles13
MIP registration.14
15
16
-
8/8/2019 [Cdg169] Omh Pri Guidelines
58/94
PRIGuidelines 3GPD Mobile IP
Ref Doc. 169, Ver. 3.0 March 2010 52
1
2
3
4
5
-
8/8/2019 [Cdg169] Omh Pri Guidelines
59/94
Ref Doc. 169, Ver. 3.0 March 2010 53
13. 3GPD IPv61
13.1 EFIPV6CAP [6F77]2
Definition: This EF specifies information about IPv6 capabilities.3
The operator should allocate n31 in EF_CST and provision the following parameters, if4
IPv6 is supported on its network.5
Size (bytes): 21 (fixed)6
13.1.1 IPv6 Initial Neighbor Solicitation Delay Time7
Definition: This parameter identifies the time the mobile waits after the Interface ID (IID)8
has been negotiated during IPv6CP between the ME and the PDSN before sending a9
Router Solicitation (RS) in an attempt to receive a Router Advertisement (RA).10
Allowed Range: 16-bit number, in units of 100ms11
Typical Value: 500ms12
Note: Neighbor Solicitation is sent by a node to determine the link-layer address of a13
neighbor, or to verify that a neighbor is still reachable via a cached link-layer address.14
13.1.2 IPv6 Solicitation Interval15
Definition: This parameter specifies the amount of time the mobile waits before sending16
a subsequent Router Solicitation (RS) after a previous one.17
Allowed Range: 16-bit number, in units of 100ms18
Typical Value: 1000ms19
Note:RSs are sent by the mobile to solicit the router, e.g., PDSN/GGSN, for an IPv620
prefix (RA).21
13.1.3 IPv6 Re-Solicitation Interval22
Definition: This parameter specifies the amount of time between router solicitations sent23
while re-soliciting for a new RA. This interval applies only after the mobile has previously24
received one valid RA and is soliciting for a new one to renew the lifetimes of the current25
prefix or retrieve a non-deprecated prefix.26
Allowed Range: 16-bit number, in units of 100ms27
Typical Value: 2000ms28
-
8/8/2019 [Cdg169] Omh Pri Guidelines
60/94
PRIGuidelines 3GPD IPv6
Ref Doc. 169, Ver. 3.0 March 2010 54
13.1.4 IPv6 Maximum Solicitation Attempts1
Definition: This parameter specifies the number of solicitation attempts to make for2
initial IPv6 session setup, when a RA is not received in response before giving up IPv63
autoconfiguration.4
Allowed Range: 16-bit number5
Typical Value: 36
Note: IfRA is not received and the ME has already transmitted the maximum solicitation7
attempts, then the ME fails and tears down the IPv6 session. RAs are sent by the router8
to advertise IPv6 prefixes, one of which is used by the mobile. They are sent at periodic9
intervals preset by network administrators, as well as in response to an RS sent by the10
mobile.11
13.1.5 IPv6 Maximum Re-Solicitation Attempts12
Definition: This parameter specifies the number of solicitation attempts to make to re-13
solicit for a new RA.14
Allowed Range: 16-bit number15
Typical Value: 316
13.1.6 IPv6 Pre-RA Expiry Re-Solicitation Time17
Definition: This parameter specifies the amount of time before the current RA expires to18
begin re-solicitations.19
Allowed Range: 16-bit number, in units of 100ms20
Typical Value: 021
13.1.7 IPv6 IID22
Definition: This parameter specifies the 64-bit IID. It is very likely to be unique on the23
link or zero, if a good source of uniqueness cannot be found. These are either derived24
from an IEEE identifier or generated through some other technique.25
Allowed Range: 64-bit binary data26
Typical Value: Operator specific27
Note: The IID is the last 64 bits of the IPv6 addresses that is formed by a combination of28
prefix and interface ID, represented in the following format:29
2002:c023:9c17:314:bceb:acb9:5d51:404530
The IPv6 prefix is represented by the first 64 bits (2002:c023:9c17:314) and can also be31
represented in the following format:32
2002:c023:9c17:314::/64.33
-
8/8/2019 [Cdg169] Omh Pri Guidelines
61/94
PRIGuidelines 3GPD IPv6
Ref Doc. 169, Ver. 3.0 March 2010 55
IIDs can be selected to be random; in which case, a 64-bit IID is generated by the mobile1
at power-up or can be pre-specified during provisioning of the mobile. Neither of these2
IIDs are guaranteed to be used, of course, if there is a collision between the two3
negotiated IIDs during IPv6CP negotiation [RFC 2472]. If there is a collision, both the4
mobile and PDSN must generate another random IID.5
13.1.8 IPv6 Enabled6
Definition: This parameter specifies whether IPv6 is enabled or disabled.7
Allowed Range:8
True9
False10
Typical Value: False11
Note: If the CST indicates via n31 that IPv6 is enabled, then this shall be enabled.12
13.1.9 Failover from IPv6 to IPv4 Enabled13
Definition: This parameter specifies whetherfailover from IPv6 to IPv4 is allowed or not.14
This feature is not supported.15
Allowed Range:16
True17
False18
Typical Value: False19
13.1.10 IPv6 PDSN as Proxy DNS Server20
Definition: This parameter specifies whether PDSN acts as the proxy IPv6 Domain21
Name Server (DNS) or not. When enabled, the mobile forwards all DNS requests to the22
PDSN. The PDSN forwards requests to the appropriate DNS server. This parameter is23
meaningful only if the primary and secondary DNS server addresses are not available.24
Allowed Range:25
True26
False27
Typical Value: False28
Note: This is only applicable if the parameter IPv6, as specified in Section 13.1.8 of this29
document, is enabled (set to True).30
31
-
8/8/2019 [Cdg169] Omh Pri Guidelines
62/94
PRIGuidelines 3GPD IPv6
Ref Doc. 169, Ver. 3.0 March 2010 56
1
2
3
4
5
-
8/8/2019 [Cdg169] Omh Pri Guidelines
63/94
Ref Doc. 169, Ver. 3.0 March 2010 57
14. HRPD1
14.1 EFHRPDCAP [6F56]2
Definition: This EF specifies the High-Rate Packet Data (HRPD) Access Authentication3
Capability Parameters as defined in Section 3.5.8.12 of [CS0016-C].4
The operator should allocate n5 in EF_CST and provision the following parameters, if5
HRPD service is supported on its network.6
Size (bytes): 4 (fixed)7
14.1.1 HRPD Maximum NAI Length8
Definition: This parameter specifies the maximum length for NAI for HRPD access9
authentication, thus specifying the maximum memory allocated in the card for this field.10
Allowed Range: 025511
Typical Value: 25512
14.1.2 HRPD Maximum SS Length13
Definition: This parameter specifies themaximum length of the Shared Secret Data for14
HR
PD access authentication, thus specifying the maximum memory allocated in the15 card for this field.16
Allowed Range: 03117
Typical Value: 3118
14.1.3 HRPD Authentication Algorithms19
Definition: This parameter specifies the authentication algorithm used for HRPD access20
authentication.21
Allowed Range: CHAP22
Typical Value:AlwaysCHAP23
14.2 EFHRPDUPP [6F57]24
Definition: This EF specifies theHRPD Access Authentication User Profile Parameters25Block defined in Section 3.5.8.13 of [CS0016-C].26
Size (bytes): Variable27
-
8/8/2019 [Cdg169] Omh Pri Guidelines
64/94
PRIGuidelines HRPD
Ref Doc. 169, Ver. 3.0 March 2010 58
14.2.1 HRPD Profile NAI1
Definition: This parameter specifiesthe Network Access Identifier (NAI), encoded in an2
ASCII string specified by an operator used for AN-AAA ( A12 ) authentication. The NAIis3
of the form [email protected]
Allowed Range: up to 255 ASCII characters5
Typical Value: Operator specific6
Note: The NAI should be chosen and managed using procedures that minimize the7
likelihood of compromise.8
14.2.2 HRPD Profile Authentication Algorithm9
Definition: This parameter specifies the authentication algorithm used for access10
authentication11
Allowed Range: CHAP12
Typical Value: CHAP13
14.3 EFHRPDSS [HIDDEN]14
Definition: This EF specifies the password for HRPD access authentication.15
Size (bytes): 31 (fixed)16
14.3.1 HRPD SS17
Definition: This parameter specifies the password the operator assigns for AN-AAA18
HRPD access authentication.19
Allowed Range: up to 31 bytes of binary data20
Typical Value: Operator specific21
Note: Even if CHAP is being used in an operators network for SIP PPP authentication,22
a separate CHAP secret key must be provisioned in the mobile device to support A1223
authentication (i.e., the device will not use the SIP PPP CHAP secret key for A1224
authentication even if the values are the same). The password should be chosen and25
managed using procedures that minimize the likelihood of compromise (i.e., it should be26
cryptographically strong). The password choice should be unique and randomized for27
each subscription, preferably of size 16 bytes.28
29
-
8/8/2019 [Cdg169] Omh Pri Guidelines
65/94
Ref Doc. 169, Ver. 3.0 March 2010 59
15. WAP Browser1
15.1 EFWAPBrowserCP [6F7B]2
Definition: This EF identifies WAP Browser connectivity parameters.3
The operator should allocate n21 in EF_CST and provision the following parameters, if4
WAP service is supported on its network,5
Multiple sets of WAP Browser Connectivity Parameters may be configured. If so,6
multiple instances of the following fields shall be provided.7
Size