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”

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)

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.

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 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

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] than the TunnelInstance MUST point toan 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.

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.

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change 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”.

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change 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.

Value Change 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.

Value Change 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.

Value Change 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.

Value Change 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.

Value Change 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.

Value Change 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.

Value Change 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.

Value Change 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].

Value Change 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.

Value Change 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.

Value Change 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”.

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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.

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.

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.

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.

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.

This measurement provides the number of RRC connection establishment attempts 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”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of RRC establishment failures 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”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of successful RRC establishments 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”.

Value Change Notification requests for this parameter MAY be denied.

This is the reference to an IPsec tunnel instance used by the LTE 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

The TunnelRef 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] than the TunnelRef MUST point toan 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, TunnelRef can contain a unique instance number. In the latter case, TunnelRef under all radio technologies can have the same instance number.

If the value isn’t assigned by the Controller on creation, the Agent MUST choose an initial value that doesn’t conflict with any existing entries.

This measurement provides the number of attempted outbound handover to HeNB by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of successful outbound handover to HeNB by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of failed outbound handover to HeNB by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of attempted inbound handover from HeNB by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of successful inbound handover from HeNB by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of failed inbound handover from HeNB by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of attempted outbound handover to Utran by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of successful outbound handover to Utran by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of failed outbound handover to Utran by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of attempted outbound handover to Geran by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of successful outbound handover to Geran by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of failed outbound handover to Geran by handover 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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

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.

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.

This measurement provides the mean number of attached CSG UEs in the HeNB.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of attempted inbound mobility for UEs to CSG cells or hybrid cells in RRC_CONNECTED mode.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of successful inbound mobility for UEs to CSG cells or hybrid cells in RRC_CONNECTED mode.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of failed successful inbound mobility for UEs to CSG cells or hybrid cells in RRC_CONNECTED mode 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”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of RRC connection establishment attempts 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”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of RRC establishment failures 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”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of successful RRC establishments 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”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of initial E-RABs attempted to setup by QoS level (QCI).

Comma-separated list of strings, where each item is defined as the “QCI level name=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of initial E-RABs successfully established QoS level (QCI).

Comma-separated list of strings, where each item is defined as the “QCI level name=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of initial E-RABs failed to setup by cause.

Comma-separated list of strings, where each item is defined as the “QCI level name=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of E-RABs attempted to setup by QoS level (QCI).

Comma-separated list of strings, where each item is defined as the “QCI level name=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of E-RABs successfully established by QoS level (QCI).

Comma-separated list of strings, where each item is defined as the “QCI level name=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of E-RABs failed to setup by cause.

Comma-separated list of strings, where each item is defined as the “QCI level name=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of E-RABs requested to release initiated by HeNB by QCI.

Comma-separated list of strings, where each item is defined as the “QCI level name=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of E-RABs requested to release initiated by HeNB by cause.

Comma-separated list of strings, where each item is defined as the “QCI level name=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

The value of this parameter is equal to the user plane PDN GW TEID (GTP-based S5) or GRE key (PMIP-based S5). [3GPP-TS.25.401].

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

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

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the number of direct user plane path between HeNB and Local GW E-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 name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the average cell bit-rate of PDCP SDUs on the downlink. This represents the ingress rate of user plane traffic to the HeNB (via S1) by SAE Bearer QoS level (QCI).

Comma-separated list of strings, where each item is defined as the “QCI level=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the average cell bit-rate of PDCP SDUs on the uplink. This represents successful transmissions of user plane traffic; control signalling and retransmissions are excluded from this measure. Measurement is by SAE Bearer QoS level (QCI).

Comma-separated list of strings, where each item is defined as the “QCI level=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the maximum cell bit-rate of PDCP SDUs on the downlink. This represents the maximum ingress rate of user plane traffic to the HeNB (via S1). This is a sum counter measured across all QCIs.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the maximum cell bit-rate of PDCP SDUs measured on the uplink. This represents successful transmissions of user plane traffic; control signalling and retransmissions are excluded from this measure. This is a sum counter measured across all QCIs.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the average (arithmetic mean) PDCP SDU delay on the downlink by ERAB Bearer QoS level (QCI).

Comma-separated list of strings, where each item is defined as the “QCI level=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the fraction of IP packets (PDCP SDUs) which are dropped on the downlink by ERAB Bearer QoS level (QCI). Only user-plane traffic (DTCH) is considered. A dropped packet is one whose context is removed from the HeNB without any part of it having been transmitted on the air interface. Packets discarded during handover are excluded from the count.

Comma-separated list of strings, where each item is defined as the “QCI level=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the fraction of IP packets (PDCP SDUs) which are lost (not successfully transmitted) on the downlink air interface by ERAB Bearer QoS level (QCI). Only user-plane traffic (DTCH) is considered. A lost packet is one whose context is removed from the HeNB after an attempt has been made to transmit part or all of the packet on the air interface but the whole packet has not been successfully transmittedafter an attempt has been made to transmit part or all of the packet on the air interface but the whole packet has not been successfully transmitted.

Comma-separated list of strings, where each item is defined as the “QCI level=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the fraction of IP packets (PDCP SDUs) which are lost (not successfully received) on the uplink by ERAB Bearer QoS level (QCI). Only user-plane traffic (DTCH) and only PDCP SDUs that have entered PDCP (and given a PDCP sequence number) are considered.

Comma-separated list of strings, where each item is defined as the “QCI level=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the average number of UEs that have user-plane (DTCH) data queued on the downlink by ERAB Bearer QoS level (QCI).

Comma-separated list of strings, where each item is defined as the “QCI level=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the average number of UEs that have user-plane (DTCH) data queued on the uplink by ERAB Bearer QoS level (QCI).

Comma-separated list of strings, where each item is defined as the “QCI level=measurement value”. The total of all the measurements is provided using the name= “sum”.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the total usage, in percentage, of physical resource blocks (PRBs) on the downlink for any purpose.

Value Change Notification requests for this parameter MAY be denied.

This measurement provides the total usage, in percentage, of physical resource blocks (PRBs) on the uplink for any purpose.

Value Change Notification requests for this parameter MAY be denied.

Specifies the status regarding the energy saving in the cell. This parameter is applicable when the value of Enable is true.

Enumeration of:

• IsEnergySaving
• IsNotEnergySaving

{{list: parameter is not a list}}

Enumeration of:

• Monday
• Tuesday
• Wednesday
• Thursday
• Friday
• Saturday
• Sunday

This is the reference to the IPsec tunnel instance used by the CDMA2000 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

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] than the TunnelInstance MUST point toan 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.

Total number of successful voice calls

Value Change Notification requests for this parameter MAY be denied.

Number of HRPD packets(bytes)packets(bytes) sent from PDSN to AT.

Value Change Notification requests for this parameter MAY be denied.

No. of HRPD packets(bytes)packets(bytes) sent from AT to PDSN.

Value Change Notification requests for this parameter MAY be denied.

Comma-separated list of strings. Represents the SIP authentication mechanisms supported by this device.

Each list item is an enumeration of:

• TNA (As defined in [3GPP2-S.S0132])
• SIPDigest (Digest Authentication as defined in [RFC3261])

The number of SCTP control chunks sent (retransmissions are not included).

Value Change Notification requests for this parameter MAY be denied.

The number of SCTP ordered data chunks sent (retransmissions are not included).

Value Change Notification requests for this parameter MAY be denied.

The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent (retransmissions are not included).

Value Change Notification requests for this parameter MAY be denied.

The number of SCTP control chunks received (no duplicate chunks included).

Value Change Notification requests for this parameter MAY be denied.

The number of SCTP ordered data chunks received (no duplicate chunks included).

Value Change Notification requests for this parameter MAY be denied.

The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) received (no duplicate chunks included).

Value Change Notification requests for this parameter MAY be denied.

The number of user messages that have been sent fragmented.

Value Change Notification requests for this parameter MAY be denied.

The number of user messages that have been received fragmented and submitted to the reassembly process.

Value Change Notification requests for this parameter MAY be denied.

The number of SCTP packets sent. Retransmitted DATA chunks are included.

Value Change Notification requests for this parameter MAY be denied.

The number of SCTP packets received. Duplicates are included.

Value Change Notification requests for this parameter MAY be denied.

The start Time for the present SCTP association.

Value Change Notification requests for this parameter MAY be denied.

The time of the last discontinuity.

Value Change Notification requests for this parameter MAY be denied.