[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The type of FAP device.

Enumeration of:

• Standalone
• Integrated

Comma-separated list of strings. Each entry is a type of system that the FAP supports. Each list item is an enumeration of:

• UMTS
• LTE
• CDMA1x
• CDMAHRPD

Active Notification requests for this parameter MAY be denied.

Indicates whether FAP can support beacon transmission.

Active Notification requests for this parameter MAY be denied.

Indicates the mode supported by the FAP. Enumeration of:

• FDDMode

Comma-separated list (at least 1 item) (maximum number of characters 16) of strings. Indicates the UMTS bands that the FAP supports [3GPP-TS.25.104], Release 8. At least one band MUST be supported and multiple bands MAY be supported. [3GPP-TS.25.104] Version 8.3.0 defines 14 UMTS bands (I through XIV). Each individual band is identified by its upper case Roman numeral. The order of the band indicators in the string has no significance. In case a new band is defined in the 3GPP standard in a future release of [3GPP-TS.25.104], the corresponding new upper case Roman numeral will be included in the valid band indicators. The followings are examples of valid values:

“I” (specifies only band-I is supported)

“I,II,V” (specifies 3 bands are supported)

“II,VII,I” (specifies 3 bands are supported)

Comma-separated list of strings. Indicates the GSM receive bands that the FAP supports [3GPP-TS.45.005]. At least one band MUST be supported and multiple bands MAY be supported. [3GPP-TS.45.005] defines 14 GSM bands.

Each list item is an enumeration of:

• T-GSM380
• T-GSM410
• GSM450
• GSM480
• GSM710
• GSM750
• T-GSM810
• GSM850
• P-GSM900
• E-GSM900
• R-GSM900
• T-GSM900
• DCS1800
• PCS1900 The order of the band indicators in the string has no significance. The following is an example of a valid value.

“GSM850,PCS1900”

Indicates the mode supported by the LTE FAP. Enumeration of:

• FDDMode
• TDDMode

Comma-separated list (at least 1 item) (maximum number of characters 16) of unsigned integers (1 to 21, or 33 to 40). Indicates the LTE bands that the LTE FAP supports [Section 5.5/3GPP-TS.36.101]. At least one band MUST be supported and multiple bands MAY be supported. Each individual band is identified by arabic number (1, 2,…). The order of the band indicators in the string has no significance. In case a new band is defined in the 3GPP standard in a future release of [3GPP-TS.36.101], the corresponding new band number will be included in the valid band indicators. The followings are examples of valid values:

“1” (specifies only band-1 is supported)

“1,2,11” (specifies 3 bands are supported)

“2,11,1” (specifies 3 bands are supported)

Comma-separated list (maximum number of characters 16) of strings. Indicates the UMTS receive bands that the LTE FAP supports [3GPP-TS.25.104], Release 8. If UMTSRxSupported is true, then at least one band MUST be supported and multiple bands MAY be supported. Each individual band is identified by its upper case Roman numeral. The order of the band indicators in the string has no significance. In case a new band is defined in the 3GPP standard in a future release of [3GPP-TS.25.104], the corresponding new upper case Roman numeral will be included in the valid band indicators. The followings are examples of valid values:

“I” (specifies only band-I is supported)

“I,II,V” (specifies 3 bands are supported)

“II,VII,I” (specifies 3 bands are supported)

Comma-separated list of strings. Indicates the GSM receive bands that the LTE FAP supports [3GPP-TS.45.005]. If GSMRxSupported is true, then at least one band MUST be supported and multiple bands MAY be supported. [3GPP-TS.45.005] defines 14 GSM bands.

Each list item is an enumeration of:

• T-GSM380
• T-GSM410
• GSM450
• GSM480
• GSM710
• GSM750
• T-GSM810
• GSM850
• P-GSM900
• E-GSM900
• R-GSM900
• T-GSM900
• DCS1800
• PCS1900 The order of the band indicators in the string has no significance. The following is an example of a valid value.

“GSM850,PCS1900”

Comma-separated list (maximum number of characters 16) of strings. Indicates the CDMA2000 receive bands that the LTE FAP supports. If CDMA2000RxSupported is true, then at least one band MUST be supported and multiple bands MAY be supported. The order of the band indicators in the string has no significance. Bandclass is a 1 or 2-digit number as defined in [3GPP2-C.S0057-B]. The following are example values:

“0” (specifies US Cellular)

“1,3,14” (specifies US PCS, Japan Cellular and US PCS 1.9Ghz) specifies 3 bands are supported)

Comma-separated list of strings. Each item is an event that causes the FAP to perform self configuration as defined by FAPControl.UMTS.SelfConfig., FAPControl.CDMA2000.OneX.SelfConfig., or FAPControl.CDMA2000.HRPD.SelfConfig.. Vendors can extend the enumerated values with vendor-specific extensions, in which case the rules outlined in [Section3.3/TR-106a2] MUST be adhered to.

Each list item is an enumeration of:

• InitialREM (Self-configuration is initiated upon completion of Radio Environment Measurement (REM) that occurs after sending a BOOTSTRAP)

Current operational state of the UMTS FAP as defined in [ITU-X.731]. If true the UMTS FAP is currently enabled. If false the UMTS FAP is currently disabled.

This parameter MUST always be included in Inform messages.

Active Notification MUST by default be enabled for this parameter.

1. location verification (including meeting the governing regulatory requirements)
2. verifying the UMTS FAP configuration
3. if physical tampering is supported and no physical tampering is detected. The default value after power-on is false.

Current status of this UMTS FAP RF transmitter. true indicates that the UMTS FAP Tx transmitter is on. false indicates that the UMTS FAP Tx transmitter is off. This state is tied to the Administrative state which is controlled by the ACS.

When the ACS sets AdminState to true, then the UMTS FAP has permission to turn on the RF transmitter.

When the ACS sets AdminState to false, then the UMTS FAP is not allowed to provide service and MUST turn off the RF transmitter.

This parameter MUST always be included in Inform messages.

Active Notification MUST by default be enabled for this parameter.

Current operational state of the LTE FAP as defined in [ITU-X.731]. If true the LTE FAP is currently enabled. If false the LTE FAP is currently disabled.

This parameter MUST always be included in Inform messages.

Active Notification MUST by default be enabled for this parameter.

1. location verification (including meeting the governing regulatory requirements)
2. verifying the LTE FAP configuration
3. if physical tampering is supported and no physical tampering is detected. The default value after power-on is false.

Current status of this LTE FAP RF transmitter. true indicates that the LTE FAP Tx transmitter is on. false indicates that the LTE FAP Tx transmitter is off. This state is tied to the Administrative state which is controlled by the ACS.

When the ACS sets AdminState to true, then the LTE FAP has permission to turn on the RF transmitter.

When the ACS sets AdminState to false, then the LTE FAP is not allowed to provide service and MUST turn off the RF transmitter.

This parameter MUST always be included in Inform messages.

Active Notification MUST by default be enabled for this parameter.

Indicates how many of the configured far-end S1 link address(es),as defined in S1SigLinkServerList, LTE FAP SHOULD attempt to establish connection with simultaneously. If S1ConnectionMode parameter is not explicitly configured, then LTE FAP shall assume the value to be One as default.

Enumeration of:

• One
• All

The local time zone for CDMA2000 operational purposes. E.g., “+HH:MM JST” for Japan. See [3GPP2-C.S0005].

Active Notification requests for this parameter MAY be denied.

The current CDMA System Time (see [3GPP2-C.S0005]), expressed as date and time in the CPE’s local time zone. The format of this field is “YYYY-MM-DDThh:mm:ss.sTZD” (e.g., 1997-07-16T19:20:30.45+01:00), where: YYYY = four-digit year MM = two-digit month (01=January, etc.) DD = two-digit day of month (01 through 31) hh = two digits of hour (00 through 23) (am/pm NOT allowed) mm = two digits of minute (00 through 59) ss = two digits of second (00 through 59) s = one or more digits representing a decimal fraction of a second TZD = time zone designator (Z or +hh:mm or -hh:mm)

Active Notification requests for this parameter MAY be denied.

Number of leap seconds (in seconds to be applied between CurrentLocalTime and CDMA System Time. See [3GPP2-C.S0005].

Active Notification requests for this parameter MAY be denied.

Administrative state for 1x

Enumeration of:

• Lock
• Unlock

Operational state of the 1x

Enumeration of:

• Enabled
• Disabled

This parameter MUST always be included in Inform messages.

Active Notification MUST by default be enabled for this parameter.

Current status of this RF transmitter. true indicates that the 3G Tx transmitter is on. false indicates that the 3G Tx transmitter is off. This state is tied to the Administrative state which is controlled by the ACS. When the ACS sets AdminState to true, then the FAP has permission to turn on the RF transmitter. When the ACS sets AdminState to false, then the FAP is not allowed to provide service and MUST turn off the RF transmitter.

This parameter MUST always be included in Inform messages.

Active Notification MUST by default be enabled for this parameter.

Reregister triggers a re-registration of all mobiles. The FAP triggers re-registration of all registered mobiles everytime this number changes

Active Notification requests for this parameter MAY be denied.

Current operational state of the FAP as defined in ITU-X.731 [32]. If true the FAP is currently enabled. If false the FAP is currently disabled.

This parameter MUST always be included in Inform messages.

Active Notification MUST by default be enabled for this parameter.

Current status of this RF transmitter. true indicates that the 3G Tx transmitter is on. false indicates that the 3G Tx transmitter is off. This state is tied to the Administrative state which is controlled by the ACS. When the ACS sets AdminState to true, then the FAP has permission to turn on the RF transmitter. When the ACS sets AdminState to false, then the FAP is not allowed to provide service and MUST turn off the RF transmitter.

This parameter MUST always be included in Inform messages.

Active Notification MUST by default be enabled for this parameter.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Indicates the type of access mode the FAP operates in. Enumeration of:

• Open Access (FAP does not enforce access control. CSG Identity is not broadcast)
• Closed Access (FAP operates as a CSG cell)
• Hybrid Access (FAP operates as a CSG cell where at the same time, non-CSG members (incl pre-Rel8 UE) are allowed access) When the value is not Open Access non-CSG-capable UE are handled according to NonCSGUEAccessDecision. Note: This parameter controls the setting of the CSGindicator bit, specified in MIB in [3GPP-TS.25.331].

The factory default value MUST be Open Access.

Active Notification requests for this parameter MAY be denied.

Indicates how the access decision is made for non-CSG-capable UE. Parameter is ignored when AccessMode is Open Access.

Enumeration of:

• Local (FAP restricts access to members of ACL)
• Query FAPGW (FAP queries FGW and acts accordingly)
• By Core (FAP allows access. Other entity in core MAY impose restrictions)

The factory default value MUST be Local.

Active Notification requests for this parameter MAY be denied.

Indicates how the access decision is made for CSG-capable UE. Parameter is ignored when AccessMode is Open Access. If true access decision is determined the same way as for NonCSGUEAccessDecision. (E.g. if core network doesn’t (yet) support full CSG functionality.) If false FAP always allows access for CSG-capable UE. CSG enforcement is performed by MSC/SGSN (with support from HSS), or by FGW. [3GPP-TS.22.011]

The factory default value MUST be false.

Active Notification requests for this parameter MAY be denied.

Maximum number of concurrent UEs allowed at a cell. Valid for any AccessMode. A value of -1 allows an unlimited number of concurrent UEs up to the limit of FAP capacity. The setting does not affect emergency calls.

The factory default value MUST be -1.

Maximum number of concurrent CSG member UEs allowed at a hybrid or closed cell. A value of -1 allows an unlimited number of CSG members up to the limit of FAP capacity. The setting cannot be larger than the value of MaxUEsServed. The setting does not affect emergency calls. [3GPP-TS.22.011], [3GPP-TS.22.220].

The factory default value MUST be -1.

Maximum number of concurerent non-CSG member UEs allowed at a hybrid cell. Valid only if AccessMode is Hybrid Access. The setting cannot be larger than the value of MaxUEsServed. The setting does not affect emergency calls.

The factory default value MUST be -1.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Enables/disables the Local IP Access (LIPA) functionality.

The factory default value MUST be false.

Indicates the type of access mode the FAP operates in. Enumeration of:

• Open Access (Access control is not enforced. CSG Identity is not broadcast)
• Closed Access (LTE FAP operates as a CSG cell)
• Hybrid Access (LTE FAP operates as a CSG cell where at the same time, non-CSG members are allowed access) Note: This parameter controls the setting of the CSGindicator bit, specified in SIB1 in [3GPP-TS.36.331].

The factory default value MUST be Open Access.

Active Notification requests for this parameter MAY be denied.

Maximum number of concurrent UEs allowed at a cell. Valid for any AccessMode. A value of -1 allows an unlimited number of concurrent UEs up to the limit of FAP capacity. The setting does not affect emergency calls.

The factory default value MUST be -1.

Maximum number of concurrent CSG member UEs allowed at a hybrid or closed cell. A value of -1 allows an unlimited number of CSG members up to the limit of FAP capacity. The setting cannot be larger than the value of MaxUEsServed. The setting does not affect emergency calls. [3GPP-TS.22.011], [3GPP-TS.22.220].

The factory default value MUST be -1.

Maximum number of concurerent non-CSG member UEs allowed at a hybrid cell. Valid only if AccessMode is Hybrid Access. The setting cannot be larger than the value of MaxUEsServed. The setting does not affect emergency calls.

The factory default value MUST be -1.

Enables/disables the Local IP Access (LIPA) functionality.

The factory default value MUST be false.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Enables/disables the Local IP Access (LIPA) functionality.

The factory default value MUST be false.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Action to be taken for traffic matching this rule.

Enumeration of:

• Tunnel (Traffic is tunneled to FGW)
• NAPT (Traffic is NAPT to local interface)

Specifies the egress interface when Action is set to NAPT. The value MUST be the Path Name of a table row. layer-3 connection object.

Example: InternetGatewayDevice.LANDevice.{i}.LANEthernetInterfaceConfig.{i}.

This is the reference to the IPsec tunnel instance used by the UMTS FAP. For all root data models, which use the tunnel definition provided in [TR-262] (InternetGatewayDevice:1 [TR-098] and Device:1 [TR-181i1]) the TunnelInstance MUST point to a row in the ‘FAP.Tunnel.IKESA.{i}.’ table, defined in [TR-262]. If the root data model used is Device:2 [TR-181i2] then the TunnelInstance MUST point to IPsec tunnel instance defined in [TR-181i2].

If the referenced object is deleted, the parameter value MUST be set to an empty string. In case of a multiple-radio-technology FAP product, each radio technology can have its own tunnels or share common tunnels. In the former case, TunnelInstance can contain a unique instance number. In the latter case, TunnelInstance under all radio technologies can have the same instance number.

Type of Public Land Mobile Network (PLMN).

Enumeration of:

• GSM-MAP
• ANSI-41

Comma-separated list (maximum number of characters 256) of strings. Each item is a LAC/RAC combination expressed in the following format:

‘:’ Where LAC and RAC are single values, while LACrange and RACrange are inclusive and can be expressed in the following format:

“..” Location Area Code (LAC) consists of up to 5 numerical characters. The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). [Section 4.1/3GPP-TS.23.003] [Section 9.2.3.6/3GPP-TS.25.413]. Routing Area Code (RAC) consists of up to 3 numerical characters. The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). [Section 4.2/3GPP-TS.23.003] [Section 9.2.3.7/3GPP-TS.25.413]. The FAP is to select one LAC and RAC from the combination(s) expressed in this parameter for use in LACInUse and RACInUse respectively. If a LAC occurs more than once in the list, this shall not increase the chance that it is selected over other LAC values in the list. The following are examples of the valid LACRAC combination formats:

“64000:210”

(one list item with single value for LAC and RAC)

“64000..64100:210, 64101:211”

(two list items, first item has a LAC range)

“64000:210..214, 64001:215..219”

(two list items, both items have a RAC range for a specific LAC value)

“64000..64100:210..214”

(one list item both have a LAC range and a RAC range)

This measurement provides the total number of requested RABs in establishment attempts.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of RABs establishment failures for the CS domain.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of successfully established RABs for the CS domain.

Active Notification requests for this parameter MAY be denied.

This measurement provides the total number of dropped RAB connections for service type CS Domain.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of attempted 3G Macro to HNB CS handovers.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of successful 3G Macro to HNB CS handovers.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of attempted 2G Macro to HNB CS handovers.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of successful 2G Macro to HNB CS handovers.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of requested RAB in establishment attempts for the PS domain by traffic class. Comma-separated list of strings, where each item is defined as the “traffic class name=measurement value”. The total of all the measurements is provided using the traffic class name= “sum”.

Active Notification requests for this parameter MAY be denied.

This measurement provides the total number of successfully established RABs for the PS domain

Active Notification requests for this parameter MAY be denied.

This measurement provides the total number of RABs establishment failures for the PS domain.

Active Notification requests for this parameter MAY be denied.

This measurement provides the total number of abnormally released PS RAB connections.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of uplink User Bits for PS RABs related with EDCH above RLC. The average uplink data throughput on EDCH RABs can be derived from this measurement.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of Uplink User Bits for PS RABs with UL 64 kbps data rate. The average uplink data throughput on 64 kbps RABs can be derived from this measurement.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of Uplink User Bits for PS RABs with UL 128 kbps data rate. The average uplink data throughput on 128 kbps RABs can be derived from this measurement.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of Uplink User Bits for PS RABs with UL 384 kbps data rate. The average uplink data throughput on 384 kbps RABs can be derived from this measurement.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of Downlink User Bits for PS RABs related with HSDPA above RLC. The average downlink data throughput on HSDPA RABs can be derived from this measurement.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of Downlink User Bits for PS RABs (non-HSDPA) with DL 64 kbps data rate above RLC. The average downlink data throughput on 64 kbps RABs (non-HSDPA) can be derived from this measurement.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of Downlink User Bits for PS RABs (non-HSDPA) with DL 128 kbps data rate above RLC. The average downlink data throughput on 128 kbps RABs (non-HSDPA) can be derived from this measurement.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of Downlink User Bits for PS RABs (non-HSDPA) with DL 384 kbps data rate above RLC. The average downlink data throughput on 384 kbps RABs (non-HSDPA) can be derived from this measurement.

Active Notification requests for this parameter MAY be denied.

The value of this parameter is equal to the user plane GGSN TEID that the Gn-SGSN has received or the user plane PDN GW TEID that the S4-SGSN has received. [3GPP-TS.25.413].

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of direct user plane path between HNB and Local GW attempted to setup.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of direct user plane path between HNB and Local GW successfully established.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of direct user plane path between HNB and Local GW RABs failed to setup by cause. Comma-separated list of strings, where each item is defined as the “cause name=measurement value”. The total of all the measurements is provided using the cause name= “sum”.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of successful HNB to UMTS macro cell intra frequency hard handovers.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of attempted HNB to UMTS macro cell intra frequency hard handovers.

Active Notification requests for this parameter MAY be denied.

This measurement provides the number of attempted HNB to UMTS macro cell inter frequency hard handovers.

Active Notification requests for this parameter MAY be denied.

This Information Element (IE) specifies the number of PSCs reserved for CSG cells in each PSC range.

Enumeration of:

• 5
• 10
• 15
• 20
• 30
• 40
• 50
• 64
• 80
• 120
• 160
• 256
• alltherest
• spare3
• spare2
• spare1

Which mechanism to use when doing CPICH quality measurements. [Section 10.3.7.47/3GPP-TS.25.331]

Enumeration of:

• Ec/No
• RSCP

Offset for QqualMin specified in dB. [Section 10.3.2.3/3GPP-TS.25.331] This value is only meaningful if QualityMeasureCPICH has the value Ec/No and it MUST otherwise be ignored.

The factory default value MUST be 1.

Offset for QRxLevMin, specified in dB. [Section 10.3.2.3/3GPP-TS.25.331] This value is only meaningful if QualityMeasureCPICH has the value RSCP and it MUST otherwise be ignored.

The factory default value MUST be 2.

A member of the set of parameters used for cell reselection functionality. Defines the duration in seconds for evaluating the allowed amount of cell reselections. If the number of cell reselections during the time period defined by NonHCSTCRMax exceeds NonHCSNCR, high mobility has been detected. Parameter defined in SIB3 [Section 10.3.2.3/3GPP-TS.25.331].

Enumeration of:

• not used
• 30
• 60
• 120
• 180
• 240

A member of the set of parameters used for cell reselection functionality. Defines the cell reselection hysteresis for reverting from UE high-mobility measurements. The additional time period in seconds before UE reverts to low-mobility measurements. When the number of cell reselections during the time period defined by TCRMax no longer exceeds NCR, UE continues measurements during the time period defined by TCRMaxHyst. Parameter defined in SIB3 [Section 10.3.2.3/3GPP-TS.25.331].

Enumeration of:

• not used
• 10
• 20
• 30
• 40
• 50
• 60
• 70

A member of the set of parameters used for cell reselection functionality. Defines the quality threshold levels for applying prioritised hierarchical cell reselection. [Section 10.3.7.12 and Section 10.3.7.54a/3GPP-TS.25.331]

The factory default value MUST be 0.

A member of the set of parameters used for cell reselection functionality. Defines the HCS priority of this cell. [Section 10.3.7.12/3GPP-TS.25.331]

The factory default value MUST be 0.

A member of the set of parameters used for cell reselection functionality. Defines the duration in seconds for evaluating the allowed amount of cell reselections. If the number of cell reselections during the time period defined by TCRMax exceeds NCR, high mobility has been detected. Parameter defined in SIB3 [Section 10.3.7.12/3GPP-TS.25.331].

Enumeration of:

• not used
• 30
• 60
• 120
• 180
• 240

A member of the set of parameters used for cell reselection functionality. Defines the cell reselection hysteresis for reverting from UE high-mobility measurements. The additional time period in seconds before UE reverts to low-mobility measurements. When the number of cell reselections during the time period defined by TCRMax no longer exceeds NCR, UE continues measurements during the time period defined by TCRMaxHyst. Parameter defined in SIB3 [Section 10.3.7.12/3GPP-TS.25.331].

Enumeration of:

• not used
• 10
• 20
• 30
• 40
• 50
• 60
• 70

Timer measured in milliseconds. Only the following values are considered valid:

100, 200, 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, and 8000 Any value other than those and the CPE MUST reject the request. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 1000.

Timer measured in milliseconds. Only the following values are considered valid:

100, 200, 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, and 8000 Any value other than those and the CPE MUST reject the request. Defined in SIB1 [Section 13.1 and section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 2000.

Timer measured in milliseconds. Only the following values are considered valid:

100, 200, 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, and 8000 Any value other than those and the CPE MUST reject the request. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 4000.

Timer measured in milliseconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 2000.

Timer measured in minutes. -1 indicates an unbounded timer in which there is no update. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 30.

Timer measured in seconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 30.

Timer measured in milliseconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 160.

Timer measured in seconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 5.

Timer measured in milliseconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 160.

Timer measured in milliseconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331].

The factory default value MUST be 2000.

Timer measured in seconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 1.

Timer measured in seconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331].

The factory default value MUST be 3.

Timer measured in seconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331].

The factory default value MUST be 12.

Timer measured in seconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331].

The factory default value MUST be 180.

Timer measured in seconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331]. -1 indicates an unbounded timer in which there is no update.

The factory default value MUST be 30.

Counter. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 3.

Counter. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331].

The factory default value MUST be 2.

Counter. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331].

The factory default value MUST be 3.

Counter. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331].

The factory default value MUST be 2.

Counter. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331].

The factory default value MUST be 4.

Counter. Only the following values are considered valid: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, and 1000. Any value other than those and the CPE MUST reject the request. Defined in SIB1 [Section 13.1 and Section 10.3.3.44/3GPP-TS.25.331].

The factory default value MUST be 1.

Counter. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331].

The factory default value MUST be 20.

Counter. Only the following values are considered valid:

1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, and 1000. Any value other than those and the CPE MUST reject the request. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331].

The factory default value MUST be 1.

Defines the measurement quantity for intra-freq HO measurement when the UE is in Cell-DCH state. Enumeration of: Enumeration of:

• CPICH Ec/No
• CPICH RSCP
• Pathloss [Section 10.3.7.38/3GPP-TS.25.331]

Comma-separated list of strings. Indicates which cells can trigger Event 1a. Each list item is an enumeration of:

• Active
• Monitored
• Active and Monitored
• Detected
• Detected and Monitored [Section 14.1.2 and Section 10.3.7.39/3GPP-TS.25.331]

Comma-separated list of strings. Indicates which cells can trigger Event 1b. Each list item is an enumeration of:

• Active
• Monitored
• Active and Monitored [Section 14.1.2 and Section 10.3.7.39/3GPP-TS.25.331]

Comma-separated list of strings. Indicates which cells can trigger Event 1e. Each list item is an enumeration of:

• Active
• Monitored
• Active and Monitored
• Detected
• Detected and Monitored [Section 14.1.2 and Section 10.3.7.39/3GPP-TS.25.331]

Comma-separated list of strings. Indicates which cells can trigger Event 1f. Each list item is an enumeration of:

• Active
• Monitored
• Active and Monitored [Section 14.1.2 and Section 10.3.7.39/3GPP-TS.25.331]

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Each entry is an Event ID from the list of: Enumeration of:

• 1a
• 1b
• 1c
• 1d
• 1e
• 1f Defines the identity of the event used to trigger UE reporting (in case of event-triggered reporting). [Section 10.3.7.34/3GPP-TS.25.331] This attribute is readable, as it is highly dependent on how the FAP makes use of the event.

Defines the measurement quantity for intra-freq HO measurement when the UE is in Cell-DCH state. Enumeration of: Enumeration of:

• CPICH Ec/No
• CPICH RSCP
• Pathloss [Section 10.3.7.38/3GPP-TS.25.331]

Comma-separated list of strings. Indicates which cells can trigger the event instance. Each list item is an enumeration of:

• Active
• Monitored
• Active and Monitored
• Detected
• Detected and Monitored [Section 14.1.2 and Section 10.3.7.39/3GPP-TS.25.331]

Defines the measurement quantity for inter-freq HO measurement when the UE is in Cell-DCH state. Enumeration of: Enumeration of:

• CPICH Ec/No
• CPICH RSCP [Section 10.3.7.18/3GPP-TS.25.331]

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Each entry is an Event ID from the list of: Enumeration of:

• 2a
• 2b
• 2c
• 2d
• 2e
• 2f Defines the identity of the event used to trigger UE reporting (in case of event-triggered reporting). [Section 10.3.7.14/3GPP-TS.25.331] This attribute is readable, as it is highly dependent on how the FAP makes use of the event.

Defines the measurement quantity for inter-freq HO measurement when the UE is in Cell-DCH state. Enumeration of: Enumeration of:

• CPICH Ec/No
• CPICH RSCP [Section 10.3.7.18/3GPP-TS.25.331]

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Each entry is an Event ID from the list of: Enumeration of:

• 3a
• 3b
• 3c
• 3d Defines the identity of the event used to trigger UE reporting (in case of event-triggered reporting). [Section 10.3.7.14/3GPP-TS.25.331] This attribute is readable, as it is highly dependent on how the FAP makes use of the event.

Comma-separated list (at least 1 item) (maximum number of characters 32) of strings. Each item is a Primary DL Scrambling Code used by the FDD mode cell with a numeric range between 0 and 511 inclusive. [Section 9.2.2.34/3GPP-TS.25.433] Self-configuration for PSC is controlled by Capabilities.UMTS.SelfConfig.PrimaryScramblingCodeConfig from an availability perspective and FAPControl.UMTS.SelfConfig.PrimaryScramblingCodeSelfConfigEnable from an enabled perspective. If the FAP’s self-configuration capability for PrimaryScramblingCode is available and enabled, this parameter MAY contain more than one item and the FAP is expected to select one from the list for PrimaryScramblingCodeInUse. If the self-configuration capability is not available or not enabled, then this parameter SHOULD contain only a single item. The multiplicity of the PSC values can also be expressed by defining a range using “..” (two periods) between two values. In this case, the combination of two values defines the lower-bound and upper-bound of the range inclusive. The following are examples of valid PSC string:

“20”

(explicitly specifies a single PSC value)

“20,30,40”

(specifies 3 possible PSC values to select from) “20..40”

(specifies 21 possible values between 20 and 40, inclusive) “20..40,50”

(specifies 22 possible values between 20 and 40 inclusive and a single value 50) The order of the items has no significance.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

BSIC of the cell per [3GPP-TS.23.003], consisting of:

Bit 7:6 - not used (“00”)

Bit 5:3 - NCC (PLMN Color Code)

Bit 2:0 - BCC (BS color code) For example, if NCC is 7 and BCC is 2 you would have 00111010 (binary) or 0x3A (hex), and the value of this parameter would be 58.

Indicates how to interpret the BCCH ARFCN. Enumeration of:

• GSM 850
• GSM 900
• DCS 1800
• PCS 1900