A non-volatile handle used to reference this instance.
'''This is intended only for use in protocol-independent "common"
definitions, and MUST NOT be used in protocol-specific definitions.'''
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
{{bibref|TR-069|3.6.1}} and described in {{bibref|TR-069|Appendix II}},
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.
IP address, i.e. IPv4 address (or IPv4 subnet mask) or IPv6 address.
All IPv4 addresses and subnet masks MUST be represented as strings in
IPv4 dotted-decimal notation. Here are some examples of valid IPv4
address textual representations:
* 216.52.29.100
* 192.168.1.254
All IPv6 addresses MUST be represented using any of the 3 standard
textual representations defined in {{bibref|RFC4291}} Sections 2.2.1,
2.2.2 and 2.2.3. Both lower-case and upper-case letters can be used, but
use of lower-case letters is RECOMMENDED. Here are some examples of valid
IPv6 address textual representations:
* 1080:0:0:800:ba98:3210:11aa:12dd
* 1080::800:ba98:3210:11aa:12dd
* 0:0:0:0:0:0:13.1.68.3
IPv6 addresses MUST NOT include zone identifiers. Zone identifiers are
discussed in {{bibref|RFC4007|Section 6}}.
Unspecified or inapplicable addresses (or IPv4 subnet masks) MUST be
represented as empty strings unless otherwise specified by the parameter
definition.
3GPP TS 03.03
Numbering, Addressing and Identification
3GPP CT WG4
https://www.3gpp.org/ftp/Specs/html-info/0303.htm
http://www.3gpp.org/ftp/Specs/html-info/0303.htm
3GPP TS 05.05
Radio Transmission and Reception
3GPP GERAN WG1
https://www.3gpp.org/ftp/Specs/html-info/0505.htm
http://www.3gpp.org/ftp/Specs/html-info/0505.htm
3GPP TS 22.011
Service accessibility
3GPP SA WG1
https://www.3gpp.org/ftp/Specs/html-info/22011.htm
http://www.3gpp.org/ftp/Specs/html-info/22011.htm
3GPP TS 22.220
Service requirements for Home Node B (HNB) and Home eNode B (HeNB)
3GPP SA WG1
https://www.3gpp.org/ftp/Specs/html-info/22220.htm
3GPP TS 23.003
Numbering, addressing and identification
3GPP CT WG4
https://www.3gpp.org/ftp/Specs/html-info/23003.htm
http://www.3gpp.org/ftp/Specs/html-info/23003.htm
3GPP TS 23.032
Universal Geographical Area Description (GAD)
3GPP SA WG2
https://www.3gpp.org/ftp/Specs/html-info/23032.htm
http://www.3gpp.org/ftp/Specs/html-info/23032.htm
3GPP TS 23.060
General Packet Radio Service (GPRS); Service description; Stage 2
3GPP SA WG2
https://www.3gpp.org/ftp/Specs/html-info/23060.htm
http://www.3gpp.org/ftp/Specs/html-info/23060.htm
3GPP TS 23.107
Quality of Service (QoS) concept and architecture
3GPP SA WG2
https://www.3gpp.org/ftp/Specs/html-info/23107.htm
http://www.3gpp.org/ftp/Specs/html-info/23107.htm
3GPP TS 23.401
General Packet Radio Service (GPRS) enhancements for Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) access
3GPP SA WG2
https://www.3gpp.org/ftp/Specs/html-info/23401.htm
http://www.3gpp.org/ftp/Specs/html-info/23401.htm
3GPP TS 24.008
Mobile radio interface Layer 3 specification; Core network protocols;
Stage 3
3GPP CT WG1
https://www.3gpp.org/ftp/Specs/html-info/24008.htm
http://www.3gpp.org/ftp/Specs/html-info/24008.htm
3GPP TS 25.104
Base Station (BS) radio transmission and reception (FDD)
3GPP RAN WG4
https://www.3gpp.org/ftp/Specs/html-info/25104.htm
http://www.3gpp.org/ftp/Specs/html-info/25104.htm
3GPP TS 25.133
Requirements for support of radio resource management (FDD)
3GPP RAN WG4
https://www.3gpp.org/ftp/Specs/html-info/25133.htm
http://www.3gpp.org/ftp/Specs/html-info/25133.htm
3GPP TS 25.214
Physical layer procedures (FDD)
3GPP RAN WG1
https://www.3gpp.org/ftp/Specs/html-info/25214.htm
http://www.3gpp.org/ftp/Specs/html-info/25214.htm
3GPP TS 25.304
User Equipment (UE) procedures in idle mode and procedures for cell
reselection in connected mode
3GPP RAN WG2
https://www.3gpp.org/ftp/Specs/html-info/25304.htm
http://www.3gpp.org/ftp/Specs/html-info/25304.htm
3GPP TS 25.331
Radio Resource Control (RRC); Protocol specification
3GPP RAN WG2
https://www.3gpp.org/ftp/Specs/html-info/25331.htm
http://www.3gpp.org/ftp/Specs/html-info/25331.htm
3GPP TS 25.401
UTRAN overall description
3GPP RAN WG3
https://www.3gpp.org/ftp/Specs/html-info/25401.htm
http://www.3gpp.org/ftp/Specs/html-info/25401.htm
3GPP TS 25.413
UTRAN Iu interface Radio Access Network Application Part (RANAP)
signalling
3GPP RAN WG3
https://www.3gpp.org/ftp/Specs/html-info/25413.htm
http://www.3gpp.org/ftp/Specs/html-info/25413.htm
3GPP TS 25.433
UTRAN Iub interface Node B Application Part (NBAP) signalling
3GPP RAN WG3
https://www.3gpp.org/ftp/Specs/html-info/25433.htm
http://www.3gpp.org/ftp/Specs/html-info/25433.htm
3GPP TS 25.469
UTRAN Iuh interface Home Node B Application Part (HNBAP) signalling
3GPP RAN WG3
https://www.3gpp.org/ftp/Specs/html-info/25469.htm
3GPP TS 25.967
FDD Home NodeB RF Requirements
3GPP RAN WG4
https://www.3gpp.org/ftp/Specs/html-info/25967.htm
http://www.3gpp.org/ftp/Specs/html-info/25967.htm
3GPP TS 32.300
Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects
3GPP SA WG5
https://www.3gpp.org/ftp/Specs/html-info/32300.htm
http://www.3gpp.org/ftp/Specs/html-info/32300.htm
3GPP TS 32.405
Telecommunication management; Performance Management (PM); Performance
measurements Universal Terrestrial Radio Access Network (UTRAN)
3GPP SA WG5
https://www.3gpp.org/ftp/Specs/html-info/32405.htm
http://www.3gpp.org/ftp/Specs/html-info/32405.htm
3GPP TS 32.582
Telecommunications management; Home Node B (HNB) Operations,
Administration, Maintenance and Provisioning (OAM&P); Information
model for Type 1 interface HNB to HNB Management System (HMS)
3GPP SA WG5
https://www.3gpp.org/ftp/Specs/html-info/32582.htm
http://www.3gpp.org/ftp/Specs/html-info/32582.htm
3GPP TS 32.642
Telecommunication management; Configuration Management (CM); UTRAN
network resources Integration Reference Point (IRP); Network Resource
Model (NRM)
3GPP SA WG5
https://www.3gpp.org/ftp/Specs/html-info/32642.htm
http://www.3gpp.org/ftp/Specs/html-info/32642.htm
3GPP TS 45.005
Radio transmission and reception
3GPP GERAN WG1
https://www.3gpp.org/ftp/Specs/html-info/45005.htm
http://www.3gpp.org/ftp/Specs/html-info/45005.htm
Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority
Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority
IEEE
March 1997
https://standards.ieee.org/regauth/oui/tutorials/EUI64.html
ITU E.118
The international telecommunication charge card
International Telecommunication Union
May 2006
https://www.itu.int/rec/T-REC-E.118-200605-I/en
http://www.itu.int/rec/T-REC-E.118/en
ITU X.731
Information Technology - Open Systems Interconnection - Systems
Management: State Management Function
International Telecommunication Union
January 1992
https://www.itu.int/rec/T-REC-X.731/en
http://www.itu.int/rec/T-REC-X.731/en
ITU X.733
Information technology - Open Systems Interconnection - Systems
Management: Alarm reporting function
International Telecommunication Union
February 1992
https://www.itu.int/rec/T-REC-X.733/en
http://www.itu.int/rec/T-REC-X.733/en
IANA Port Numbers
Port Numbers
IANA
https://www.iana.org/assignments/port-numbers
IANA Uniform Resource Identifier (URI) Schemes Registry
Uniform Resource Identifier (URI) Schemes
IANA
https://www.iana.org/assignments/uri-schemes
RFC 3550
RTP: A Transport Protocol for Real-Time Applications
IETF
July 2003
https://www.rfc-editor.org/rfc/rfc3550
http://www.ietf.org/rfc/rfc3550.txt
RFC 3873
Stream Control Transmission Protocol (SCTP) Management Information Base
(MIB)
IETF
September 2004
https://www.rfc-editor.org/rfc/rfc3873
http://www.ietf.org/rfc/rfc3873.txt
RFC 3986
Uniform Resource Identifier (URI): Generic Syntax
IETF
RFC
https://www.rfc-editor.org/rfc/rfc3986
RFC 4007
IPv6 Scoped Address Architecture
IETF
RFC
https://www.rfc-editor.org/rfc/rfc4007
RFC 4122
A Universally Unique IDentifier (UUID) URN Namespace
IETF
RFC
2005
https://www.rfc-editor.org/rfc/rfc4122
RFC 4291
IP Version 6 Addressing Architecture
IETF
RFC
2006
https://www.rfc-editor.org/rfc/rfc4291
RFC 4301
Security Architecture for the Internet Protocol
IETF
December 2005
https://www.rfc-editor.org/rfc/rfc4301
http://www.ietf.org/rfc/rfc4301.txt
RFC 4307
Cryptographic Algorithms for Use in the Internet Key Exchange Version 2
(IKEv2)
IETF
December 2005
https://www.rfc-editor.org/rfc/rfc4307
http://www.ietf.org/rfc/rfc4307.txt
RFC 4632
Classless Inter-domain Routing (CIDR): The Internet Address Assignment
and Aggregation Plan
IETF
2006
https://www.rfc-editor.org/rfc/rfc4632
RFC 4960
Stream Control Transmission Protocol
IETF
September 2007
https://www.rfc-editor.org/rfc/rfc4960
http://www.ietf.org/rfc/rfc4960.txt
RFC7159
The JavaScript Object Notation (JSON) Data Interchange Format
IETF
RFC
March 2014
https://www.rfc-editor.org/rfc/rfc7159
RFC 7230
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
IETF
RFC
June 2014
https://www.rfc-editor.org/rfc/rfc7230
RFC 7252
The Constrained Application Protocol (CoAP)
IETF
RFC
June 2014
https://www.rfc-editor.org/rfc/rfc7252
RFC 8141
Uniform Resource Names (URNs)
IETF
RFC
April 2017
https://www.rfc-editor.org/rfc/rfc8141
TR-069 Amendment 2
CPE WAN Management Protocol
Broadband Forum
TR
December 2007
TR-069 Amendment 6
CPE WAN Management Protocol
Broadband Forum
TR
April 2018
TR-098 Amendment 2 Corrigendum 1
Internet Gateway Device Data Model for TR-069
Broadband Forum
TR
December 2014
TR-106 Amendment 2
Data Model Template for TR-069-Enabled Devices
Broadband Forum
TR
November 2008
TR-181 Issue 2 Amendment 15
Device Data Model
Broadband Forum
TR
January 2022
Simple Object Access Protocol (SOAP) 1.1
W3C
https://www.w3.org/TR/2000/NOTE-SOAP-20000508
ZigBee 2007 Specification
ZigBee 2007 Specification
ZigBee Alliance
October 2007
https://csa-iot.org/all-solutions/zigbee
3GPP TS 32.111-5
Telecommunication management; Fault Management; Part 5: Alarm
Integration Reference Point (IRP): eXtensible Markup Language (XML)
definitions
3GPP SA WG5
http://www.3gpp.org/ftp/Specs/html-info/32111-5.htm
RFC 3280
Internet X.509 Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile
IETF
April 2002
http://www.ietf.org/rfc/rfc3280.txt
The number of entries in the FAPService table.
The Femto Access Point (FAP) Service Object.
The type of FAP device.
Specifies the Distinguished Name (DN) Prefix to be used when
constructing full DNs which uniquely identify a FAP object, e.g.
{{param|.FaultMgmt.CurrentAlarm.{i}.ManagedObjectInstance}}. Encodes
the Managed Object Prefix representation in string format as defined
in {{bibref|3GPP-TS.32.300}}. Examples:
"DC=a1.companyNN.com,SubNetwork=1,IRPAgent=1" and "SubNetwork=1"
{{datatype|expand}}
This object contains parameters relating to the hardware capabilities
of the FAP device.
Indicates whether the FAP is equipped with a GPS receiver or not.
Indicates the maximum possible transmit power in {{units}} that the
FAP hardware can support.
{{list}} Each entry is a type of system that the FAP supports.
{{enum}} Other values are "For Future Study" (FFS).
Indicates the maximum number of child SAs per IKE session that the
device is capable of supporting.
Indicates the maximum number of IKE sessions the device is capable of
supporting at any given time.
This object contains parameters relating to the system and RF aspect of
the FAP device that supports the UMTS system (i.e. 3G HNB).
Indicates the mode supported by the FAP. {{enum}} Other values are
"For Future Study" (FFS).
Indicates whether the FAP hardware supports the receiving function of
GSM or not.
Indicates whether the FAP hardware supports the HSDPA capability or
not.
If the FAP hardware supports HSDPA ({{param|HSDPASupported}} is
{{true}}), this parameter indicates the maximum HSDPA data rate in
{{units}} that the device supports.
Indicates whether the FAP hardware supports the HSUPA capability or
not.
If the FAP hardware supports HSUPA ({{param|HSUPASupported}} is
{{true}}), this parameter indicates the maximum HSUPA data rate in
{{units}} that the device supports.
If the FAP hardware supports HSPA family (either
{{param|HSDPASupported}} is {{true}} or {{param|HSUPASupported}} is
{{true}}), this parameter indicates the available number of codes at
the defined spreading factor (SF=16), within the complete code tree.
See {{bibref|3GPP-TS.32.642|Section 6.3.9}} for more details.
If the FAP hardware supports HSPA family (either
{{param|HSDPASupported}} is {{true}} or {{param|HSUPASupported}} is
{{true}}), this parameter indicates the available number of HS-SCCHs
for one cell. See {{bibref|3GPP-TS.32.642|Section 6.3.9}} for more
details.
{{list}} Indicates the UMTS bands that the FAP supports
{{bibref|3GPP-TS.25.104}}, Release 8. At least one band MUST be
supported and multiple bands MAY be supported.
{{bibref|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 {{bibref|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)
{{list}} Indicates the GSM receive bands that the FAP supports
{{bibref|3GPP-TS.45.005}}. At least one band MUST be supported and
multiple bands MAY be supported. {{bibref|3GPP-TS.45.005}} defines 14
GSM bands. {{enum}} The order of the band indicators in the string
has no significance. The following is an example of a valid value.
:“GSM850,PCS1900”
This object contains parameters relating to the self-configuration
capabilities of the FAP. Self-configuration is enabled in
{{object|.FAPControl.UMTS.SelfConfig.}}
Indicates whether the FAP supports the self-configuration capability
to determine the UTRA Absolute Radio Frequency Channel Number
(UARFCN). If {{true}} multiple values MAY be provided in
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.UARFCNDL}} for the FAP to
select from. If {{false}} only a single value SHOULD be provided in
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.UARFCNDL}}.
Indicates whether the FAP supports the self-configuration capability
to determine the Primary Scrambling Code (PSC). If {{true}} multiple
values or a range of values MAY be provided in
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.PrimaryScramblingCode}} for
the FAP to select from. If {{false}} only a single value SHOULD be
provided in
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.PrimaryScramblingCode}}.
This parameter is DEPRECATED and is replaced by
{{param|MaxFAPTxPowerExpandedConfig}} in order to define the expanded
value range.
Indicates whether the FAP supports the self-configuration capability
to determine the P-CPICH power. If {{true}} a range of values MAY be
provided in {{param|.CellConfig.UMTS.RAN.FDDFAP.RF.PCPICHPower}} for
the FAP to select from. If {{false}} only a single value SHOULD be
provided in {{param|.CellConfig.UMTS.RAN.FDDFAP.RF.PCPICHPower}} as
an upper bound.
Indicates whether the FAP supports the self-configuration capability
to determine the Maximum UL Transmit Power. If {{true}} a range of
values MAY be provided in
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.MaxULTxPower}} for the FAP to
select from. If {{false}} only a single value SHOULD be provided in
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.MaxULTxPower}}.
Indicates whether the FAP supports the self-configuration capability
to determine the LAC, RAC, and URA. If {{true}} multiple values MAY
be provided in {{param|.CellConfig.UMTS.CN.LACRAC}} and
{{param|.CellConfig.UMTS.RAN.URAList}} for the FAP to select from. If
{{false}} only a single value SHOULD be provided in
{{param|.CellConfig.UMTS.CN.LACRAC}} and
{{param|.CellConfig.UMTS.RAN.URAList}}.
Indicates whether the FAP supports the self-configuration capability
to determine the neighbor list. If {{true}} the ACS uses the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}.}},
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}.}},
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell.}}
tables to explicitly include or exclude entries and the FAP uses that
information to determine the final configuration found in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.IntraFreqCell.{i}.}},
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterFreqCell.{i}.}},
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterRATCell.}}
tables. If {{false}} the ACS uses the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}.}},
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}.}},
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell.}}
tables to only specify the included entries and the FAP uses that
list.
Indicates whether the FAP supports the self-configuration capability
to determine cell-reselection values. If {{true}}
{{object|.CellConfig.UMTS.RAN.FDDFAP.CellSelection.}} can be
self-configured. If {{false}}
{{object|.CellConfig.UMTS.RAN.FDDFAP.CellSelection.}} is provided by
the ACS.
Indicates whether the FAP supports the self-configuration capability
to determine intra-frequency measurement values. If {{true}}
{{object|.CellConfig.UMTS.RAN.FDDFAP.IntraFreqMeas.}} can be
self-configured. If {{false}}
{{object|.CellConfig.UMTS.RAN.FDDFAP.IntraFreqMeas.}} is provided by
the ACS.
Indicates whether the FAP supports the self-configuration capability
to determine inter-frequency measurement values. If {{true}}
{{object|.CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas.}} can be
self-configured. If {{false}}
{{object|.CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas.}} is provided by
the ACS.
Indicates whether the FAP supports the self-configuration capability
to determine inter-RAT measurement values. If {{true}}
{{object|.CellConfig.UMTS.RAN.FDDFAP.InterRATMeas.}} can be
self-configured. If {{false}}
{{object|.CellConfig.UMTS.RAN.FDDFAP.InterRATMeas.}} is provided by
the ACS.
Indicates whether the FAP supports the self-configuration capability
to determine UE internal measurement values. If {{true}}
{{object|.CellConfig.UMTS.RAN.FDDFAP.UEInternalMeas.}} can be
self-configured. If {{false}}
{{object|.CellConfig.UMTS.RAN.FDDFAP.UEInternalMeas.}} is provided by
the ACS.
This parameter replaces {{param|MaxFAPTxPowerConfig}} which is
DEPRECATED in order to define the expanded value range. Indicates
whether the FAP supports the self-configuration capability to
determine the Maximum FAP Transmit Power. If {{true}} a range of
values MAY be provided in
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.MaxFAPTxPowerExpanded}} for
the FAP to select from. If {{false}} only a single value SHOULD be
provided in
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.MaxFAPTxPowerExpanded}}.
This object contains parameters relating to state management and
provisioning aspects of the FAP.
Current operational state of the FAP as defined in
{{bibref|ITU-X.731}}. If {{true}} the FAP is currently enabled. If
{{false}} the FAP is currently disabled.
Lock or unlock the FAP. This controls the administrative state of the
FAP as defined in {{bibref|ITU-X.731}}. If {{true}} Unlocked with
permission to serve traffic (and enable RF transmitter(s)). If
{{false}} Locked. Transition FAP to state where it is NOT permitted
to serve traffic. RF transmitter is disabled. Given that this command
controls the FAP’s RF transmitter, the underlying expectation is that
the unlock is done when all necessary conditions are met to allow the
transmitter to key on and provide service, including aspects such as:
# location verification (including meeting the governing regulatory
requirements)
# verifying the FAP configuration
# if physical tampering is supported and no physical tampering is
detected. The default value after power-on is {{false}}.
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 {{param|AdminState}} to {{true}}, then the FAP has
permission to turn on the RF transmitter.
:When the ACS sets {{param|AdminState}} to {{false}}, then the FAP is
not allowed to provide service and MUST turn off the RF transmitter.
{{list}} Each item is an event that causes the FAP to perform self
configuration as defined by {{object|.FAPControl.UMTS.SelfConfig.}}
Vendors can extend the enumerated values with vendor-specific
extensions, in which case the rules outlined in
{{bibref|TR-106a2|Section3.3}} MUST be adhered to.
Self-configuration is initiated upon completion of Radio
Environment Measurement (REM) that occurs after sending a
BOOTSTRAP.
This parameter indicates whether or not physical tampering of the
device enclosure occurred, such as illegal opening of the box. If
{{true}} device tampering is detected. If {{false}} no sign of device
tampering is detected. Tampering state must be persisted across
reboots and the device MUST never reset it back from {{true}} to
{{false}} even after a factory reset.
This object contains parameters relating to the UMTS system specific
information.
This object contains parameters relating to the controlling of
self-configuration capabilities in the FAP.
Indicates whether the self-configuration capability in the FAP is
used or not to determine the values of
{{param|.CellConfig.UMTS.RAN.CSG.UARFCNDLList}}. If {{true}} The FAP
self-configures the value. If {{false}} The ACS must provide the
specific value to be used.
Indicates whether the self-configuration capability in the FAP is
used or not to determine the value of
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.PrimaryScramblingCode}}. If
{{true}} the FAP self-configures the value. If {{false}} the ACS must
provide the specific value to be used.
This parameter is DEPRECATED and is replaced by
{{param|MaxFAPTxPowerExpandedSelfConfigEnable}} in order to define
the expanded value range.
Indicates whether the self-configuration capability in the FAP is
used or not to determine the value of
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.PCPICHPower}}. If {{true}} The
FAP self-configures the value. If {{false}} The ACS must provide the
specific value to be used.
Indicates whether the self-configuration capability in the FAP is
used or not to determine the value of
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.MaxULTxPower}}. If {{true}}
The FAP self-configures the value. If {{false}} The ACS must provide
the specific value to be used.
Indicates whether the self-configuration capability in the FAP is
used or not to determine the values of
{{param|.CellConfig.UMTS.CN.LACRAC}} and
{{param|.CellConfig.UMTS.RAN.URAList}}. If {{true}} The FAP
self-configures the value. If {{false}} The ACS MUST provide the
specific value to be used.
Indicates whether the self-configuration capability in the FAP is
used or not to determine the values in the object
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.}} If {{true}} The
FAP self-configures the value. If {{false}} The ACS must provide the
specific value to be used.
Indicates whether the self-configuration capability in the FAP is
used or not to determine Cell Selection/Reselection-related
parameters in {{object|.CellConfig.UMTS.RAN.FDDFAP.CellSelection.}}
If {{true}} The FAP self-configures the value. If {{false}} The ACS
must provide the specific value to be used.
Indicates whether the self-configuration capability in the FAP is
used or not to determine intra-frequency measurement -related
parameters in {{object|.CellConfig.UMTS.RAN.FDDFAP.IntraFreqMeas.}}
If {{true}} The FAP self-configures the value. If {{false}} The ACS
must provide the specific value to be used.
Indicates whether the self-configuration capability in the FAP is
used or not to determine inter-frequency measurement -related
parameters in {{object|.CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas.}}
If {{true}} The FAP self-configures the value. If {{false}} The ACS
must provide the specific value to be used.
Indicates whether the self-configuration capability in the FAP is
used or not to determine inter-RAT measurement -related parameters in
{{object|.CellConfig.UMTS.RAN.FDDFAP.InterRATMeas.}} If {{true}} The
FAP self-configures the value. If {{false}} The ACS must provide the
specific value to be used.
Indicates whether the self-configuration capability in the FAP is
used or not to determine UE internal measurement-related parameters
in {{object|.CellConfig.UMTS.RAN.FDDFAP.UEInternalMeas.}} If {{true}}
The FAP self-configures the value. If {{false}} The ACS must provide
the specific value to be used.
This parameter replaces {{param|MaxFAPTxPowerSelfConfigEnable}} which
is DEPRECATED in order to define the expanded value range. Indicates
whether the self-configuration capability in the FAP is used or not
to determine the value of
{{param|.CellConfig.UMTS.RAN.FDDFAP.RF.MaxFAPTxPowerExpanded}}. If
{{true}} The FAP self-configures the value. If {{false}} The ACS MUST
provide the specific value to be used.
This object contains parameters relating to the Gateways that FAP is
connected to.
First SecGW the FAP attempts to establish connection with. Either
hostname or IPaddress.
Second SecGW the FAP attempts to establish connection with. Either
hostname or IPaddress.
Third SecGW the FAP attempts to establish connection with. Either
hostname or IPaddress.
First FAP-GW the FAP attempts to establish connection with. Either
hostname or IPaddress.
Second FAP-GW the FAP attempts to establish connection with. Either
hostname or IPaddress.
Third FAP-GW the FAP attempts to establish connection with. Either
hostname or IPaddress.
Port number of FAP-GW used for initial Iuh SCTP contact. This value
is specified as 29169 according to IANA definition per
{{bibref|IANA-portnumbers}}, registered on 2009-09-08. Use of
IANA-defined value is recommended.
This object contains parameters relating to Access Management (ACL,
CSG, LIPA). Closed Subscriber Group (CSG) service behavior is specified
in {{bibref|3GPP-TS.22.011}}. Note: Cell barring and 3GPP access class
parameters are contained in
{{object|.CellConfig.UMTS.RAN.FDDFAP.CellRestriction.}} (UMTS FAP).
Indicates the type of access mode the FAP operates in. {{enum}} When
the value is not {{enum|Open Access}} non-CSG-capable UE are handled
according to {{param|NonCSGUEAccessDecision}}. Note: This parameter
controls the setting of the CSGindicator bit, specified in MIB in
{{bibref|3GPP-TS.25.331}} (for UMTS FAP).
FAP does not enforce access control. CSG Identity is not
broadcast.
FAP operates as a CSG cell.
FAP operates as a CSG cell where at the same time, non-CSG
members (incl pre-Rel8 UE) are allowed access.
Indicates how the access decision is made for non-CSG-capable UE.
Parameter is ignored when {{param|AccessMode}} is {{enum|Open
Access|AccessMode}}.
FAP restricts access to members of ACL
FAP queries FGW and acts accordingly.
FAP allows access. Other entity in core MAY impose
restrictions.
Indicates how the access decision is made for CSG-capable UE.
Parameter is ignored when {{param|AccessMode}} is {{enum|Open
Access|AccessMode}}. If {{true}} access decision is determined the
same way as for {{param|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.
{{bibref|3GPP-TS.22.011}}
This parameter is DEPRECATED and is being replaced by
{{param|HNBName}}.
This parameter is DEPRECATED and is being replaced by
{{param|HNBName}}.
This parameter is DEPRECATED and being replaced with
{{param|MaxCSGMembers}}.
Defines the Closed Subscriber Group of the Access Control List. An
UMTS FAP broadcasts this CSG ID in SIB3 depending on the AccessMode.
{{list}} Each entry is an IMSI.
The maximum number of entries available in the
{{object|.AccessMgmt.MemberDetail.{i}.}} table.
The number of entries in the {{object|.AccessMgmt.MemberDetail.{i}.}}
table.
Maximum number of concurrent UEs allowed at a cell. Valid for any
{{param|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.
This parameter replaces {{param|HNBIdentifier}} and
{{param|HomeZoneName}} which are DEPRECATED. Home NodeB name. An
operator-defined string that is broadcast by a CSG cell or a hybrid
cell and displayed on the UE for the purpose of manual cell selection
or indication that the UE is camped on the cell as specified in
{{bibref|3GPP-TS.22.220|Section 5.4.2}}. Corresponds to parameter
'hnb-Name' specified in SIB20 in {{bibref|3GPP-TS.25.331|Section
10.2.48.8.23}} for an UMTS FAP.
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 {{param|MaxUEsServed}}. The setting does not affect
emergency calls. {{bibref|3GPP-TS.22.011}},
{{bibref|3GPP-TS.22.220}}.
Maximum number of concurerent non-CSG member UEs allowed at a hybrid
cell. Valid only if {{param|AccessMode}} is {{enum|Hybrid
Access|AccessMode}}. The setting cannot be larger than the value of
{{param|MaxUEsServed}}. The setting does not affect emergency calls.
Maximum percentage of physical resource that can be assigned to
non-CSG members aggregately at one time. In an UMTS FAP, this applies
to RB resource.
Details for CSG and Non-CSG members.
Enables or disables the MemberDetail entry.
International Mobile Subscriber Identity of the UE.
Mobile Station International Subscriber Identity Number. Set to
{{empty}} if unknown.
Time when the ACL membership expires. An Unknown Time value, as
defined in {{bibref|TR-106a2|Section 3.2}}, indicates that the
membership doesn't expire. Upon expiry the FAP MUST remove the IMSI
from the {{param|.AccessMgmt.AccessControlList}}, but the entry in
{{object|.AccessMgmt.MemberDetail.{i}.}} remains.
{{bibref|3GPP-TS.22.011}}
{{datatype|expand}}
Local IP access.
Enables/disables the Local IP Access (LIA) functionality.
The maximum number of entries available in the
{{object|.AccessMgmt.LocalIPAccess.Rules.{i}.}} table.
The number of enteries in
{{object|.AccessMgmt.LocalIPAccess.Rules.{i}.}} table.
Policy for selecting traffic for local IP access. Originated traffic
will be NAT’ed. The rule is bi-directional, i.e. return traffic is
allowed. Rules do NOT affect traffic to/from the FAP itself (such as
TR-069 or control). The rules are applied to the mobile station data
traffic (PS-domain) via deep packet inspection or similar method.
Enables or disables the forwarding entry.
Destination IP Address. {{empty}} indicates no destination address is
specified. An entry for which {{param}} and {{param|DestSubnetMask}}
are both {{empty}} is a default route.
Destination subnet mask (IPv4) or prefix (IPv6). {{empty}} indicates
no destination subnet mask or prefix is specified. If a destination
subnet mask or prefix is specified, {{param}} is ANDed with the
destination address before comparing with {{param|DestIPAddress}}.
Otherwise, the full destination address is used as-is. An entry for
which {{param|DestIPAddress}} and {{param}} are both {{empty}} is a
default route.
IP Protocol Identifier. -1 matches any protocol.
Action to be taken for traffic matching this rule.
Traffic is tunneled to FGW.
Traffic is NAPT to local interface
Specifies the egress interface when {{param|Action}} is set to
{{enum|NAPT|Action}}. {{reference}} layer-3 connection object.
Example:
InternetGatewayDevice.LANDevice.{i}.LANEthernetInterfaceConfig.{i}.
{{datatype|expand}}
This object contains parameters relating to configuring the FAP.
This object contains parameters relating to configuring UMTS system
specific information.
This object contains parameters relating to configuring UMTS CN.
Type of Public Land Mobile Network (PLMN).
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code
(MNC) {{bibref|3GPP-TS.23.003}}, {{bibref|3GPP-TS.24.008}}. Mobile
Country Code consists of three digits and uniquely identifies the
country of domicile of the subscriber. Mobile Network Code consists
of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of {{param}} is 5.
{{list}} Each item is a PLMNID. PLMN ID consists of Mobile Country
Code (MCC) and Mobile Network Code (MNC) {{bibref|3GPP-TS.23.003}},
{{bibref|3GPP-TS.24.008}}. Mobile Country Code consists of three
digits and uniquely identifies the country of domicile of the
subscriber. Mobile Network Code consists of two or three digits and
identifies the Home PLMN within a country. For a 2-digit MNC the
total string length of the PLMNID is 5.
Service Area Code (SAC) {{bibref|3GPP-TS.23.003}}. The concatenation
of PLMN ID (MCC+MNC), LAC, and SAC uniquely identifies the Service
Area ID (SAI).
{{list}} Each item is a LAC/RAC combination expressed in the
following format:
:<LAC or LACrange>':'<RAC or RACrange> Where LAC and RAC
are single values, while LACrange and RACrange are inclusive and can
be expressed in the following format:
:<Start-value>".."<End-value> 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).
{{bibref|3GPP-TS.23.003|Section 4.1}}
{{bibref|3GPP-TS.25.413|Section 9.2.3.6}}. 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). {{bibref|3GPP-TS.23.003|Section 4.2}}
{{bibref|3GPP-TS.25.413|Section 9.2.3.7}}. The FAP is to select one
LAC and RAC from the combination(s) expressed in this parameter for
use in {{param|LACInUse}} and {{param|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)
The LAC being used by the FAP. Self-configuration for LAC is
controlled by {{param|.Capabilities.UMTS.SelfConfig.LACRACURAConfig}}
from an availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.LACRACURASelfConfigEnable}} from
an enabled perspective. If the self-configuration capability is
available and enabled, this parameter indicates the value selected by
the FAP among the choices provided in {{param|LACRAC}}. If the
self-configuration capability is not available or not enabled, then
this parameter contains the first LAC value in {{param|LACRAC}}.
The RAC being used by the FAP. Self-configuration for RAC is
controlled by {{param|.Capabilities.UMTS.SelfConfig.LACRACURAConfig}}
from an availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.LACRACURASelfConfigEnable}} from
an enabled perspective. If the self-configuration capability is
available and enabled, this parameter indicates the value selected by
the FAP among the choices provided in {{param|LACRAC}}. If the
self-configuration capability is not available or not enabled, then
this parameter contains the first RAC value in {{param|LACRAC}}.
This object contains parameters relating to configuring the CS domain
of the UMTS CN.
T3212 timeout value specified in {{units}}. {{bibref|3GPP-TS.24.008}}
Indicates the UE behavior regarding IMSI attach/detach procedure to
the CN. {{bibref|3GPP-TS.24.008}} If {{true}} UE SHALL apply IMSI
attach and detach procedure If {{false}} UE SHALL NOT apply IMSI
attach and detach procedure
This object contains parameters relating to configuring the PS domain
of the UMTS CN.
Network Mode of Operation of the CN. {{bibref|3GPP-TS.23.060}}
{{bibref|3GPP-TS.24.008}} If {{true}} (Network Mode of Operation II)
Combined procedures between CS and PS domain are not supported (i.e.
Gs interface is not present). If {{false}} (Network Mode of Operation
I) Combined procedures between CS and PS domain are supported (i.e.
Gs interface is present).
This object contains parameters relating to the RAN-level
configuration.
{{list}} Each item is a URA (UTRAN Registration Area) to which the
FAP belongs. The order of the URA values has no significance.
{{bibref|3GPP-TS.25.331|Section 10.3.2.6}}
The URA being used by the FAP. Self-configuration for URA is
controlled by {{param|.Capabilities.UMTS.SelfConfig.LACRACURAConfig}}
from an availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.LACRACURASelfConfigEnable}} from
an enabled perspective. If the FAP’s self-configuration capability
for URA is available and enabled, this parameter indicates the value
selected by the FAP among the choices provided in {{param|URAList}}.
If the self-configuration capability is not available or not enabled,
then this parameter contains the first URA value in
{{param|URAList}}.
RNC-ID allocated to the FAP. It uniquely identifies an RNC within a
PLMN. Normally, RNC-ID consists of 12 bits (i.e. a range of
[0:4095]). However, if the value is larger than 4095, then Extended
RNC-ID (range of [4096:65535]) is used in RANAP. The RNC-ID and
Extended RNC-ID are combined into a single parameter here as there is
no explicit need to have them separated.
{{bibref|3GPP-TS.25.413|Section 9.2.1.39}}
Cell Identity. {{bibref|3GPP-TS.25.331|Section 10.3.2.2}}
Guard period in {{units}} before sending a "RANAP:RESET ACKNOWLEDGE"
message towards the Femto GW. {{bibref|3GPP-TS.25.413|Section 9.5}}
Maximum amount of time in {{units}} that the FAP SHOULD wait for
receiving a "RANAP:RESET ACKNOWLEDGE" message from the Femto GW after
sending a Reset to the Femto GW. {{bibref|3GPP-TS.25.413|Section
9.5}}
Maximum number for RESET procedure that can be repeated in FAP.
{{bibref|3GPP-TS.25.413|Section 8.26.3.2}}
Amount of time in {{units}} used to determine when the additional
level of traffic reduction in CN overload should take place. While
this timer is running all OVERLOAD messages or signalling pointing to
congested information received by the FAP are ignored.
{{bibref|3GPP-TS.25.413|Section 9.5}}
Amount of time in {{units}} used to determine when the CN overload
can be considered cleared. While this timer is running, the FAP is
not allowed to increase traffic. {{bibref|3GPP-TS.25.413|Section
9.5}}
Maximum amount of time in {{units}} for Data Forwarding at FAP. Timer
is started when a "RANAP:SRNS Data Forward Command" message (or a
"RANAP:Relocation Command" message) is received. At timer expiry the
"SRNS Data Forwarding" procedure is completed.
{{bibref|3GPP-TS.25.413|Section 9.5}}
Maximum amount of time in {{units}} for the Relocation Preparation
procedure. Timer is started when a "RANAP:Relocation Required"
message is sent. Timer is stopped when a "RANAP:Relocation Command"
or a "RANAP:Relocation Preparation Failure" message is received.
{{bibref|3GPP-TS.25.413|Section 9.5}}
Maximum amount of time in {{units}} for protection of the overall
Relocation procedure. Timer is started when a "RANAP:Relocation
Command" message is received. Timer is stopped when a "RANAP:Iu
Release Command" is received or the relocation procedure is
cancelled. {{bibref|3GPP-TS.25.413|Section 9.5}}
The "realm" portion of the HNB-ID where HNB-ID is defined in
{{bibref|3GPP-TS.25.469}} v8.2.0 and is shown as follows:
0<IMSI>@<realm> Or
1<OUI>-<SerialNumber>@<realm>
The other identifiers before "@" are device dependent values. Both
<OUI> and <SerialNumber> are defined in
{{bibref|TR-069a2|Table 36}}. <IMSI> is obtained from the USIM
if it is equipped in the FAP.
This object contains parameters relating to the Closed Subscriber Group
(CSG).
The CSG-indicator Information Element (IE) in the Master Information
Block reflects the access mode of the CSG cell. It is hence dependent
on the value of {{param|.AccessMgmt.AccessMode}}. If {{true}} the
CSG-indicator IE is present, reflecting access to the CSG cell is
closed. If {{false}} the CSG-indicator IE is absent, reflecting
access to the CSG cell is not closed. {{bibref|3GPP-TS.25.331|Section
10.2.48.8.1}}
{{list}} Each item is a UTRA Absolute Radio Frequency Channel Number
(UARFCN) in the DL direction dedicated to the CSG cells. {{param}} is
broadcast in SIB 11bis {{bibref|3GPP-TS.25.331|Section
10.2.48.8.14a}}. The corresponding UTRA Absolute Radio Frequency
Channel Number (UARFCN) in the UL direction is derived based on the
fixed offset applicable for the frequency band.
This object contains parameters relating to the Primary Scrambling Code
(PSC) split information for the CSG. Defined in SIB3/11bis
{{bibref|3GPP-TS.25.331|Section 10.3.2.8 and 10.3.2.9}}.
The value of this Information Element (IE) multiplied by 8 specifies
the start PSC value of the first PSC range as specified in
{{bibref|3GPP-TS.25.331|Section 8.6.2.4}}.
This Information Element (IE) specifies the number of PSCs reserved
for CSG cells in each PSC range.
If this Information Element (IE) is included, the UE shall calculate
the second PSC range as specified in {{bibref|3GPP-TS.25.331|Section
8.6.2.4}}. If this Information Element (IE) is not included, the UE
shall consider the second PSC range to be not present.
This object contains parameters relating to the cell-level
configuration for FDD mode FAP.
Enables/disables the HSDPA function in the FAP. If {{true}} HSDPA is
enabled (this is equivalent to a “1” in
{{bibref|3GPP-TS.32.642|Section 6.3.9}}) If {{false}} HSDPA is
disabled (this is equivalent to a “0” in
{{bibref|3GPP-TS.32.642|Section 6.3.9}})
Enables or disables HSDPA in the cell. If {{true}} HSDPA is enabled
(this is equivalent to a “1” in {{bibref|3GPP-TS.32.642|Section
6.3.9}}) If {{false}} HSDPA is not enabled (this is equivalent to a
“0” in {{bibref|3GPP-TS.32.642|Section 6.3.9}}) If {{param|HSFlag}}
is {{false}} then this value MUST be {{false}}.
The number of codes at the defined spreading factor (SF=16), within
the complete code tree. {{bibref|3GPP-TS.32.642|Section 6.3.9}}
The number of HS-SCCHs for one cell. {{bibref|3GPP-TS.32.642|Section
6.3.9}}
This object contains parameters related to cell selection and
reselection.
Which mechanism to use when doing CPICH quality measurements.
{{bibref|3GPP-TS.25.331|Section 10.3.7.47}}
Minimum required quality measure, specified in {{units}}.
{{bibref|3GPP-TS.25.331|Section 10.3.2.3 and Section 10.3.2.4}} This
value is only meaningful if {{param|QualityMeasureCPICH}} has the
value {{enum|Ec/No|QualityMeasureCPICH}} and it MUST otherwise be
ignored.
Offset for {{param|QqualMin}} specified in {{units}}.
{{bibref|3GPP-TS.25.331|Section 10.3.2.3}} This value is only
meaningful if {{param|QualityMeasureCPICH}} has the value
{{enum|Ec/No|QualityMeasureCPICH}} and it MUST otherwise be ignored.
Minimum required RX level in the cell, specified in {{units}}.
{{bibref|3GPP-TS.25.331|Section 10.3.2.3}} Only odd values are valid,
use of an even value MUST be rejected by the CPE. This value is only
meaningful if {{param|QualityMeasureCPICH}} has the value
{{enum|RSCP|QualityMeasureCPICH}} and it MUST otherwise be ignored.
Delta for the minimum required RX level in the cell, specified in
{{units}}. {{bibref|3GPP-TS.25.331|Section 10.3.2.3 and Section
10.3.2.4}} The actual value of {{param|QRxLevMin}} =
{{param|QRxLevMin}} + {{param}} This value is only meaningful if
{{param|QualityMeasureCPICH}} has the value
{{enum|RSCP|QualityMeasureCPICH}} and it MUST otherwise be ignored.
Offset for {{param|QRxLevMin}}, specified in {{units}}.
{{bibref|3GPP-TS.25.331|Section 10.3.2.3}} This value is only
meaningful if {{param|QualityMeasureCPICH}} has the value
{{enum|RSCP|QualityMeasureCPICH}} and it MUST otherwise be ignored.
GSM and FDD Cell reselection hysteresis 1.
{{bibref|3GPP-TS.25.331|Section 10.3.2.3}} Only even values are
valid, use of an odd value MUST be rejected by the CPE. This value is
only meaningful if {{param|QualityMeasureCPICH}} has the value
{{enum|RSCP|QualityMeasureCPICH}} and it MUST otherwise be ignored.
FDD Cell reselection hysteresis 2. {{bibref|3GPP-TS.25.331|Section
10.3.2.3}} Only even values are valid, use of an odd value MUST be
rejected by the CPE. This value is only meaningful if
{{param|QualityMeasureCPICH}} has the value
{{enum|RSCP|QualityMeasureCPICH}} and it MUST otherwise be ignored.
By default when {{param|QHyst1s}} is set and {{param}} is not, then
the value for {{param}} should match the value of {{param|QHyst1s}}.
A member of the set of parameters used for cell reselection
functionality. A UE triggers the reselection of a new cell if the
cell reselection criteria are fulfilled during the time interval in
{{units}}. Parameter defined in SIB3 {{bibref|3GPP-TS.25.331|Section
10.3.2.3}}.
A member of the set of parameters used for cell reselection
functionality. Defines the threshold for intra-frequency
measurements, and for the HCS measurement rules. Only even values are
valid, use of an odd value MUST be rejected by the CPE. Parameter
defined in SIB3 {{bibref|3GPP-TS.25.331|Section 10.3.2.3}}.
A member of the set of parameters used for cell reselection
functionality. Defines the threshold for inter-frequency
measurements, and for the HCS measurement rules. Only even values are
valid, use of an odd value MUST be rejected by the CPE. Parameter
defined in SIB3 {{bibref|3GPP-TS.25.331|Section 10.3.2.3}}.
A member of the set of parameters used for cell reselection
functionality. Defines the threshold for intrafrequency and
interfrequency measurement rules in HCS. Below this limit in the
serving cell, the UE initiates measurements of all intrafrequency and
interfrequency neighbouring cells of the serving cell. Only odd
values are valid, use of an even value MUST be rejected by the CPE.
Parameter defined in SIB3 {{bibref|3GPP-TS.25.331|Section 10.3.2.3}}.
A member of the set of parameters used for cell reselection
functionality. Defines the RAT (GSM) specific threshold for inter-RAT
measurement rules. Only even values are valid, use of an odd value
MUST be rejected by the CPE. Parameter defined in SIB3
{{bibref|3GPP-TS.25.331|Section 10.3.2.3}}.
A member of the set of parameters used for cell reselection
functionality. Defines the RAT (GSM) specific threshold for inter-RAT
measurement rules in HCS. Only odd values are valid, use of an even
value MUST be rejected by the CPE. Parameter defined in SIB3
{{bibref|3GPP-TS.25.331|Section 10.3.2.3}}.
A member of the set of parameters used for cell reselection
functionality. Defines the threshold for skipping inter-RAT
measurement rules in HCS. Above this RAT (GSM) specific threshold in
the serving UTRA cell, the UE does not need to perform any inter-RAT
measurements. Only even values are valid, use of an odd value MUST be
rejected by the CPE. Parameter defined in SIB3
{{bibref|3GPP-TS.25.331|Section 10.3.2.3}}.
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 {{param}} exceeds
{{param|NonHCSNCR}}, high mobility has been detected. Parameter
defined in SIB3 {{bibref|3GPP-TS.25.331|Section 10.3.2.3}}.
A member of the set of parameters used for cell reselection
functionality. Defines the maximum number of cell reselections. If
the number of cell reselections during the {{param|NonHCSTCRMax}}
time period exceeds the value of {{param}}, high mobility has been
detected. Parameter defined in SIB3 {{bibref|3GPP-TS.25.331|Section
10.3.2.3}}.
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
{{param|TCRMax}} no longer exceeds {{param|NCR}}, UE continues
measurements during the time period defined by {{param|TCRMaxHyst}}.
Parameter defined in SIB3 {{bibref|3GPP-TS.25.331|Section 10.3.2.3}}.
A member of the set of parameters used for cell reselection
functionality. Defines the quality threshold levels for applying
prioritised hierarchical cell reselection.
{{bibref|3GPP-TS.25.331|Section 10.3.7.12 and Section 10.3.7.54a}}
A member of the set of parameters used for cell reselection
functionality. Indicate whether HCS is used in this cell or not.
{{bibref|3GPP-TS.25.331|Section 10.3.7.47}}
A member of the set of parameters used for cell reselection
functionality. Defines the HCS priority of this cell.
{{bibref|3GPP-TS.25.331|Section 10.3.7.12}}
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 {{param}} exceeds
{{param|NCR}}, high mobility has been detected. Parameter defined in
SIB3 {{bibref|3GPP-TS.25.331|Section 10.3.7.12}}.
A member of the set of parameters used for cell reselection
functionality. Defines the maximum number of cell reselections. If
the number of cell reselections during the {{param|TCRMax}} time
period exceeds the value of {{param}}, high mobility has been
detected. Parameter defined in SIB3 {{bibref|3GPP-TS.25.331|Section
10.3.7.12}}.
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
{{param|TCRMax}} no longer exceeds {{param|NCR}}, UE continues
measurements during the time period defined by {{param}}. Parameter
defined in SIB3 {{bibref|3GPP-TS.25.331|Section 10.3.7.12}}.
A member of the set of parameters used for cell reselection
functionality. Defines the maximum transmit power level, specified in
{{units}}, that an UE may use when accessing the cell on RACH. Used
to calculate Pcompensation, which is: max(UE_TXPWR_MAX_RACH – P_MAX,
0), where UE_TXPWR_MAX_RACH is {{param}} and P_MAX is the max
transmit power for a UE. {{bibref|3GPP-TS.25.331|Section 10.3.2.3}}
{{bibref|3GPP-TS.25.304|Section 5.2.3}}
This object contains parameters related to miscellaneous RRC timers and
constants.
Timer measured in {{units}}. 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 {{bibref|3GPP-TS.25.331|Section
13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. 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 {{bibref|3GPP-TS.25.331|Section
13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. 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 {{bibref|3GPP-TS.25.331|Section
13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. -1 indicates an unbounded timer in which
there is no update. Defined in SIB1 {{bibref|3GPP-TS.25.331|Section
13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}. -1
indicates an unbounded timer in which there is no update.
Timer measured in {{units}}. Defined in SIB1
{{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Counter. Defined in SIB1 {{bibref|3GPP-TS.25.331|Section 13.1 and
Section 10.3.3.43}}.
Counter. Defined in SIB1 {{bibref|3GPP-TS.25.331|Section 13.1 and
Section 10.3.3.43}}.
Counter. Defined in SIB1 {{bibref|3GPP-TS.25.331|Section 13.1 and
Section 10.3.3.43}}.
Counter. Defined in SIB1 {{bibref|3GPP-TS.25.331|Section 13.1 and
Section 10.3.3.43}}.
Counter. Defined in SIB1 {{bibref|3GPP-TS.25.331|Section 13.1 and
Section 10.3.3.43}}.
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 {{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Counter. Defined in SIB1 {{bibref|3GPP-TS.25.331|Section 13.1 and
Section 10.3.3.43}}.
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 {{bibref|3GPP-TS.25.331|Section 13.1 and Section 10.3.3.43}}.
Time period the UE has to wait before repeating the rejected
procedure. This is an IE used when sending RRC connection reject,
redirecting the requesting UE to another frequency. 0 indicates that
repetition is not allowed. {{bibref|3GPP-TS.25.331|Section
10.3.3.50}}.
This object contains parameters related to DRX parameters.
Defines the DRX cycle length coefficient for CS domain to optimize
paging in idle mode. Defined in SIB1 {{bibref|3GPP-TS.25.331|Section
10.3.3.6}}. {{param}} refers to 'k' in the formula as specified in
{{bibref|3GPP-TS.25.304}}, Discontinuous reception. Used by the CN CS
domain to count paging occasions for discontinuous reception in Idle
Mode. The duration of the DRX cycle is 2 <power> k frames,
where 'k' is the used DRX cycle length coefficient for CN.
Defines the DRX cycle length coefficient for PS domain to optimize
paging in idle mode. Defined in SIB1 {{bibref|3GPP-TS.25.331|Section
10.3.3.6}}. {{param}} refers to 'k' in the formula as specified in
{{bibref|3GPP-TS.25.304}}, Discontinuous reception. Used by the CN PS
domain to count paging occasions for discontinuous reception in Idle
Mode. The duration of the DRX cycle is 2 <power> k frames,
where 'k' is the used DRX cycle length coefficient for CN.
Defines the DRX cycle length used by UTRAN to count paging occasions
for discontinuous reception in Connected Mode. The duration of the
DRX cycle is 2 <power> k frames, where 'k' is the used DRX
cycle length coefficient for UTRAN. {{param}} SHOULD be used by the
UTRAN/FAP for UEs in Cell_PCH/Cell_FACH state.
{{bibref|3GPP-TS.25.331|Section 10.3.3.49}}
This object contains parameters related to power control and RACH.
Used by the UE to calculate the initial output power, specified in
{{units}}, on PRACH according to the open loop power control
procedure. Parameter in SIB5. {{bibref|3GPP-TS.25.331|Section
10.3.6.11}}
This parameter is DEPRECATED and replaced by
{{param|PowerRampStepUp}} in order to correct and align the parameter
name to the intended purpose.
Used for the Uplink Common Channel. Defines the maximum number of
preambles allowed in one preamble ramping cycle. PRACH Preamble
Retrans Max is part of "PRACH power offset" which is part of "PRACH
system information list". Parameter in SIB5.
{{bibref|3GPP-TS.25.331|Section 10.3.6.54}}
Persistence Scaling Factor for overload control. Parameter in SIB5.
The value is the scaling factor multiplied by 10, e.g. 2 is a scaling
factor of 0.2
Maximum number of RACH preamble cycles. Defines how many times the
PRACH preamble ramping procedure can be repeated before UE MAC
reports a failure on RACH transmission to higher layers. Maximum
number of RACH preamble cycles is part of "RACH transmission
parameters" which is part of "PRACH system information list" which is
part of SIB5. {{bibref|3GPP-TS.25.331|Section 10.3.6.67}}
RACH random back-off lower bound. {{param}} is the lower bound of the
waiting time in 10 millisecond increments (i.e. 1 corresponds to 10
ms and 50 corresponds to 500 ms). {{param}} is part of "RACH
transmission parameters" which is part of "PRACH system information
list" which is part of SIB5. {{bibref|3GPP-TS.25.331|Section
10.3.6.67}}
RACH random back-off upper bound. {{param}} is the Upper bound of the
waiting time in 10 millisecond increments (i.e. 1 corresponds to 10
ms and 50 corresponds to 500 ms). {{param}} is part of "RACH
transmission parameters" which is part of "PRACH system information
list" which is part of SIB5. {{bibref|3GPP-TS.25.331|Section
10.3.6.67}}
This parameter replaces {{param|PowerRampSetup}} which is DEPRECATED
in order to correct and align the parameter name to the intended
purpose. Used for the Uplink Common Channel. Defines the Power ramp
setup, specified in {{units}}, on PRACH preamble when no acquisition
indicator (AI) is detected by the UE. Parameter in SIB5.
{{bibref|3GPP-TS.25.331|Section 10.3.6.54}}
This object contains parameters related to cell access restriction.
Indicates whether the FAP is barred from service or not.
{{bibref|3GPP-TS.25.331|Section 10.3.2}}
When {{param|CellBarred}} is {{true}}, this indicates whether the
intra-frequency cell re-selection is allowed or not. {{param}} has no
meaning if {{param|CellBarred}} is {{false}} and MUST be ignored in
such cases. {{true}} means that intra-frequency cell re-selection is
allowed. {{false}} means that intra-frequency cell re-selection is
not allowed. {{bibref|3GPP-TS.25.331|Section 10.3.2}}
The time period in {{units}} during which the UE is barred from
accessing the FAP. {{bibref|3GPP-TS.25.331|Section 10.3.2}}
{{list}} Each entry is an Access Class that is barred from CS
service. The order of the list has no significance.
{{bibref|3GPP-TS.25.331|Section 10.3.2}}
{{list}} Each entry is an Access Class that is barred from PS
service. The order of the list has no significance.
{{bibref|3GPP-TS.25.331|Section 10.3.2}}
Indicates whether the FAP is reserved for operator use or not.
{{bibref|3GPP-TS.25.331|Section 10.3.2}}
This object contains parameters relating to the intra-freq HO control
parameters.
Defines the measurement quantity for intra-freq HO measurement when
the UE is in Cell-DCH state. Enumeration of: {{enum}}
{{bibref|3GPP-TS.25.331|Section 10.3.7.38}}
Defines the equivalent time constant of the low pass filter applied
to the CPICH quality measurements, or {{enum|CPICH
Ec/No|MeasurementQuantity}}. {{bibref|3GPP-TS.25.331|Section 8.6.7.2
and Section 10.3.7.9}}
{{list}} Each entry is an Event ID from the list of: 1a, 1b, 1c, 1d,
1e, 1f, 1g, 1h, 1i Defines the identity of the event used to trigger
UE reporting (in case of event-triggered reporting).
{{bibref|3GPP-TS.25.331|Section 10.3.7.34}} Since the FAP can
determine this on its own, it might not be necessary to configure it.
{{list}} Indicates which cells can trigger Event 1a. {{enum}}
{{bibref|3GPP-TS.25.331|Section 14.1.2 and Section 10.3.7.39}}
{{list}} Indicates which cells can trigger Event 1b. {{enum}}
{{bibref|3GPP-TS.25.331|Section 14.1.2 and Section 10.3.7.39}}
{{list}} Indicates which cells can trigger Event 1e. {{enum}}
{{bibref|3GPP-TS.25.331|Section 14.1.2 and Section 10.3.7.39}}
{{list}} Indicates which cells can trigger Event 1f. {{enum}}
{{bibref|3GPP-TS.25.331|Section 14.1.2 and Section 10.3.7.39}}
Defines a constant in the inequality criterion that needs to be
satisfied for an Event 1a to occur. Actual values of the range are
0.0 to 14.5 {{units}} in steps of 0.5 {{units}}. The value of
{{param}} divided by 2 yields the actual value of the range.
{{bibref|3GPP-TS.25.331|Section 14.1.2 and Section 10.3.7.39}}
Defines a constant in the inequality criterion that needs to be
satisfied for an Event 1b to occur. Actual values of the range are
0.0 to 14.5 {{units}} in steps of 0.5 {{units}}. The value of
{{param}} divided by 2 yields the actual value of the range.
{{bibref|3GPP-TS.25.331|Section 14.1.2 and Section 10.3.7.39}}
Defines the weighting factor for intra-freq HO measurement when the
UE is in Cell-DCH state. Actual values of the weighting factor are
0.0 to 2.0 in steps of 0.1. The value of {{param}} divided by 10
yields the actual value of the weighting factor.
{{bibref|3GPP-TS.25.331|Section 10.3.7.39}}
Defines the weighting factor for intra-freq HO measurement when the
UE is in Cell-DCH state. Actual values of the weighting factor are
0.0 to 2.0 in steps of 0.1. The value of {{param}} divided by 10
yields the actual value of the weighting factor.
{{bibref|3GPP-TS.25.331|Section 10.3.7.39}}
Defines the maximum number of cells allowed in the "active cell set"
for Event 1a to occur. {{bibref|3GPP-TS.25.331|Section 14.1.2 and
Section 10.3.7.39}}
Defines the maximum number of MEASUREMENT REPORT messages sent by the
UE in case of periodic reporting triggered by an Event 1a The value
-1 is used to represent an unbounded maximum.
{{bibref|3GPP-TS.25.331|Section 14.1.2 and Section 10.3.7.39}}
Defines the maximum number of MEASUREMENT REPORT messages sent by the
UE in case of periodic reporting triggered by an Event 1c The value
-1 is used to represent an unbounded maximum.
{{bibref|3GPP-TS.25.331|Section 14.1.2 and Section 10.3.7.39}}
Defines the transmission period in {{units}} of MEASUREMENT REPORT
messages sent by the UE in case of periodic reporting triggered by an
Event 1a. {{bibref|3GPP-TS.25.331|Section 14.1.2 and Section
10.3.7.39}}
Defines the transmission period in {{units}} of MEASUREMENT REPORT
messages sent by the UE in case of periodic reporting triggered by an
Event 1c. {{bibref|3GPP-TS.25.331|Section 14.1.2 and Section
10.3.7.39}}
Defines the hysteresis for intra-freq HO measurement when the UE is
in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps
of 0.5. The value of {{param}} divided by 2 yields the actual value
of the hysteresis. {{bibref|3GPP-TS.25.331|Section 10.3.7.39 and
Section 14.1.2}}
Defines the hysteresis for intra-freq HO measurement when the UE is
in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps
of 0.5. The value of {{param}} divided by 2 yields the actual value
of the hysteresis. {{bibref|3GPP-TS.25.331|Section 10.3.7.39 and
Section 14.1.2}}
Defines the hysteresis for intra-freq HO measurement when the UE is
in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps
of 0.5. The value of {{param}} divided by 2 yields the actual value
of the hysteresis. {{bibref|3GPP-TS.25.331|Section 10.3.7.39 and
Section 14.1.2}}
Defines the hysteresis for intra-freq HO measurement when the UE is
in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps
of 0.5. The value of {{param}} divided by 2 yields the actual value
of the hysteresis. {{bibref|3GPP-TS.25.331|Section 10.3.7.39 and
Section 14.1.2}}
Defines the hysteresis for intra-freq HO measurement when the UE is
in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps
of 0.5. The value of {{param}} divided by 2 yields the actual value
of the hysteresis. {{bibref|3GPP-TS.25.331|Section 10.3.7.39 and
Section 14.1.2}}
Defines the time-to-trigger in {{units}} for intra-freq HO
measurement when the UE is in Cell-DCH state. Only the following
values are considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.39 and Section
10.3.7.64}}
Defines the time-to-trigger in {{units}} for intra-freq HO
measurement when the UE is in Cell-DCH state. Only the following
values are considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.39 and Section
10.3.7.64}}
Defines the time-to-trigger in {{units}} for intra-freq HO
measurement when the UE is in Cell-DCH state. Only the following
values are considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.39 and Section
10.3.7.64}}
Defines the time-to-trigger in {{units}} for intra-freq HO
measurement when the UE is in Cell-DCH state. Only the following
values are considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.39 and Section
10.3.7.64}}
Defines the time-to-trigger in {{units}} for intra-freq HO
measurement when the UE is in Cell-DCH state. Only the following
values are considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.39 and Section
10.3.7.64}}
Defines the reporting threshold for intra-freq HO measurement when
the UE is in Cell-DCH state. This is the “Threshold used frequency”
as defined in {{bibref|3GPP-TS.25.331|Section 10.3.7.39}}. Each valid
value of {{param|MeasurementQuantity}} has a different valid range.
{{enum|CPICH RSCP|MeasurementQuantity}} has a range of -120 dBm to
-25 dBm {{enum|CPICH Ec/No|MeasurementQuantity}} has a range of -24
dB to 0 dB {{enum|Pathloss|MeasurementQuantity}} has a range of 30 dB
to 165 dB
Defines the reporting threshold for intra-freq HO measurement when
the UE is in Cell-DCH state. This is the “Threshold used frequency”
as defined in {{bibref|3GPP-TS.25.331|Section 10.3.7.39}}. Each valid
value of {{param|MeasurementQuantity}} has a different valid range.
{{enum|CPICH RSCP|MeasurementQuantity}} has a range of -120 dBm to
-25 dBm {{enum|CPICH Ec/No|MeasurementQuantity}} has a range of -24
dB to 0 dB {{enum|Pathloss|MeasurementQuantity}} has a range of 30 dB
to 165 dB
Defines the minimum number of cells allowed in the "active cell set"
for Event 1c to occur. {{bibref|3GPP-TS.25.331|Section 14.1.2 and
Section 10.3.7.39}}
This object contains parameters relating to the inter-freq HO related
control parameters.
Defines the measurement quantity for inter-freq HO measurement when
the UE is in Cell-DCH state. Enumeration of: {{enum}}
{{bibref|3GPP-TS.25.331|Section 10.3.7.18}}
Defines the filter coefficient for inter-freq HO measurement when the
UE is in Cell-DCH state. {{bibref|3GPP-TS.25.331|Section 10.3.7.9 and
Section 10.3.7.18}}
{{list}} Each entry is an Event ID from the list of: 2a, 2b, 2c, 2d,
2e,2f Defines the identity of the event used to trigger
inter-frequency UE reporting (in case of event-triggered reporting).
{{bibref|3GPP-TS.25.331|Section 10.3.7.14}}
Defines the weighting factor for inter-freq HO measurement when the
UE is in Cell-DCH state. Actual values of the weighting factor are
0.0 to 2.0 in steps of 0.1. The value of {{param}} divided by 10
yields the actual value of the weighting factor.
{{bibref|3GPP-TS.25.331|Section 10.3.7.19}}
Defines the weighting factor for inter-freq HO measurement when the
UE is in Cell-DCH state. Actual values of the weighting factor are
0.0 to 2.0 in steps of 0.1. The value of {{param}} divided by 10
yields the actual value of the weighting factor.
{{bibref|3GPP-TS.25.331|Section 10.3.7.19}}
Defines the weighting factor for inter-freq HO measurement when the
UE is in Cell-DCH state. Actual values of the weighting factor are
0.0 to 2.0 in steps of 0.1. The value of {{param}} divided by 10
yields the actual value of the weighting factor.
{{bibref|3GPP-TS.25.331|Section 10.3.7.19}}
Defines the weighting factor for inter-freq HO measurement when the
UE is in Cell-DCH state. Actual values of the weighting factor are
0.0 to 2.0 in steps of 0.1. The value of {{param}} divided by 10
yields the actual value of the weighting factor.
{{bibref|3GPP-TS.25.331|Section 10.3.7.19}}
Defines the hysteresis for inter-freq HO measurement when the UE is
in Cell-DCH state. Actual values of the range are 0.0 to 14.5 in
steps of 0.5. The value of {{param}} divided by 2 yields the actual
value of the hysteresis. {{bibref|3GPP-TS.25.331|Section 10.3.7.19}}
Defines the hysteresis for inter-freq HO measurement when the UE is
in Cell-DCH state. Actual values of the range are 0.0 to 14.5 in
steps of 0.5. The value of {{param}} divided by 2 yields the actual
value of the hysteresis. {{bibref|3GPP-TS.25.331|Section 10.3.7.19}}
Defines the hysteresis for inter-freq HO measurement when the UE is
in Cell-DCH state. Actual values of the range are 0.0 to 14.5 in
steps of 0.5. The value of {{param}} divided by 2 yields the actual
value of the hysteresis. {{bibref|3GPP-TS.25.331|Section 10.3.7.19}}
Defines the hysteresis for inter-freq HO measurement when the UE is
in Cell-DCH state. Actual values of the range are 0.0 to 14.5 in
steps of 0.5. The value of {{param}} divided by 2 yields the actual
value of the hysteresis. {{bibref|3GPP-TS.25.331|Section 10.3.7.19}}
Defines the time-to-trigger in {{units}} for inter-freq HO
measurement when the UE is in Cell-DCH state. Only the following
values are considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.19 and Section
10.3.7.64}}
Defines the time-to-trigger in {{units}} for inter-freq HO
measurement when the UE is in Cell-DCH state. Only the following
values are considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.19 and Section
10.3.7.64}}
Defines the time-to-trigger in {{units}} for inter-freq HO
measurement when the UE is in Cell-DCH state. Only the following
values are considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.19 and Section
10.3.7.64}}
Defines the time-to-trigger in {{units}} for inter-freq HO
measurement when the UE is in Cell-DCH state. Only the following
values are considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.19 and Section
10.3.7.64}}
Defines the reporting threshold for inter-freq HO measurement when
the UE is in Cell-DCH state. This is the “Threshold used frequency”
as defined in {{bibref|3GPP-TS.25.331|Section 10.3.7.19}}. Each valid
value of {{param|MeasurementQuantity}} has a different valid range.
{{enum|CPICH RSCP|MeasurementQuantity}} has a range of -120 dBm to
-25 dBm {{enum|CPICH Ec/No|MeasurementQuantity}} has a range of -24
dB to 0 dB
Defines the reporting threshold for inter-freq HO measurement when
the UE is in Cell-DCH state. This is the “Threshold used frequency”
as defined in {{bibref|3GPP-TS.25.331|Section 10.3.7.19}}. Each valid
value of {{param|MeasurementQuantity}} has a different valid range.
{{enum|CPICH RSCP|MeasurementQuantity}} has a range of -120 dBm to
-25 dBm {{enum|CPICH Ec/No|MeasurementQuantity}} has a range of -24
dB to 0 dB
Defines the reporting threshold for inter-freq HO measurement when
the UE is in Cell-DCH state. This is the “Threshold used frequency”
as defined in {{bibref|3GPP-TS.25.331|Section 10.3.7.19}}. Each valid
value of {{param|MeasurementQuantity}} has a different valid range.
{{enum|CPICH RSCP|MeasurementQuantity}} has a range of -120 dBm to
-25 dBm {{enum|CPICH Ec/No|MeasurementQuantity}} has a range of -24
dB to 0 dB
This object contains parameters relating to the inter-RAT HO related
control parameters. This is specifically for GERAN system.
Defines the filter coefficient for inter-RAT HO measurement when the
UE is in Cell-DCH state. {{bibref|3GPP-TS.25.331|Section 10.3.7.9 and
Section 10.3.7.29}}
Indicates whether the BSIC verification is required or not for
inter-RAT HO measurement when the UE is in Cell-DCH state.
{{bibref|3GPP-TS.25.331|Section 10.3.7.29}}
Defines the weighting factor for inter-RAT HO measurement when the UE
is in Cell-DCH state. Actual values of the weighting factor are 0.0
to 2.0 in steps of 0.1. The value of {{param}} divided by 10 yields
the actual value of the weighting factor.
{{bibref|3GPP-TS.25.331|Section 10.3.7.30}}
Defines the hysteresis for inter-RAT HO measurement when the UE is in
Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of
0.5. The value of {{param}} divided by 2 yields the actual value of
the hysteresis. {{bibref|3GPP-TS.25.331|Section 10.3.7.30}}
Defines the time-to-trigger in {{units}} for inter-RAT HO measurement
when the UE is in Cell-DCH state. Only the following values are
considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.30 and Section
10.3.7.64}}
Defines the reporting threshold for inter-RAT HO measurement when the
UE is in Cell-DCH state. This is the “Threshold own system” as
defined in {{bibref|3GPP-TS.25.331|Section 10.3.7.30}}.
Defines the reporting threshold for inter-RAT HO measurement when the
UE is in Cell-DCH state. This is the “Threshold other system” as
defined in {{bibref|3GPP-TS.25.331|Section 10.3.7.30}}.
This object contains parameters relating to the UE internal measurement
control parameters.
Defines the filter coefficient for UE internal measurement.
{{bibref|3GPP-TS.25.331|Section 10.3.7.9 and Section 10.3.7.79}}
Defines the threshold for UE transmit power above which Event 6a is
reported. {{bibref|3GPP-TS.25.331|Section 10.3.7.80}}
Defines the period in {{units}} between detection of Event 6a and
sending of Measurement Report. Only the following values are
considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.80}}
Defines the threshold for UE transmit power above which Event 6b is
reported. {{bibref|3GPP-TS.25.331|Section 10.3.7.80}}
Defines the period in {{units}} between detection of Event 6b and
sending of Measurement Report. Only the following values are
considered valid:
:0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 Any value other than those and the CPE MUST reject the
request. {{bibref|3GPP-TS.25.331|Section 10.3.7.80}}
This object contains parameters relating to the RF configuration.
{{list}} Each item is a DL UTRA Absolute Radio Frequency Channel
Number (UARFCN) in an FDD mode cell. {{bibref|3GPP-TS.25.433|Section
9.2.1.65}} Self-configuration for UARFCN is controlled by
{{param|.Capabilities.UMTS.SelfConfig.UARFCNConfig}} from an
availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.UARFCNSelfConfigEnable}} from an
enabled perspective. If the FAP’s self-configuration capability for
UARFCN is available and enabled, this parameter MAY contain more than
one item and the FAP is expected to select one from the list for
{{param|UARFCNDLInUse}}. If the self-configuration capability is not
available or not enabled, then this parameter SHOULD contain only a
single item. The UARFCN values supplied to the list are derived based
on the formula defined in {{bibref|3GPP-TS.25.104|Section 5.4.3}} The
order of the UARFCN entries has no significance. The carrier spacing
in FDD mode is fixed as defined in {{bibref|3GPP-TS.25.104}}.
Therefore, the FAP can unambiguously derive the UL UARFCN value based
on the selected DL UARFCN.
The DL UARFCN being used by the FAP. Self-configuration for UARFCN is
controlled by {{param|.Capabilities.UMTS.SelfConfig.UARFCNConfig}}
from an availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.UARFCNSelfConfigEnable}} from an
enabled perspective. If the self-configuration capability is
available and enabled, this parameter indicates the value selected by
the FAP among the choices provided in {{param|UARFCNDL}}. If the
self-configuration capability is not available or not enabled, then
this parameter contains the first value in {{param|UARFCNDL}}.
The UL UARFCN being used by the FAP. The UL UARFCN that corresponds
to {{param|UARFCNDLInUse}}.
{{list}} Each item is a DL UARFCNs to be protected from adjacent
channel interference. "Adjacent channel" in this context means offset
from the FAP's UARFCN by 5MHz. {{bibref|3GPP-TS.25.104|Section
6.4.6}} If any of the items in the list are adjacent to the FAP’s own
DL channel, the FAP MUST take the Primary CPICH code power measured
on these channels into account as part of its maximum transmit power
self-configuration. The UARFCNs in the list can belong to any
operator, allowing for protection of the FAP operator's own macro
layer as well as that of other operators (only the latter is mandated
by the {{bibref|3GPP-TS.25.104}} requirements). The list should take
into account the ability of the FAP to self-configure its own DL
UARFCN and so SHOULD include any channels (requiring protection)
which can potentially be adjacent to the UARFCN selected by the FAP.
For example, if only adjacent operator protection is required and the
FAP has the ability to self-configure to any channel owned by its
operator, this list would be populated with the UARFCNs immediately
above and below the range of channels owned by the FAP operator.
Adjacent channel protection can cause the FAP transmit power to be
reduced down to as low as 8dBm. If {{empty}} then it indicates that
there are no channels adjacent to the FAP that require protection, or
that self-configuration of the FAP transmit power is not enabled.
{{list}} Each item is a Primary DL Scrambling Code used by the FDD
mode cell with a numeric range between 0 and 511 inclusive.
{{bibref|3GPP-TS.25.433|Section 9.2.2.34}} Self-configuration for PSC
is controlled by
{{param|.Capabilities.UMTS.SelfConfig.PrimaryScramblingCodeConfig}}
from an availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.PrimaryScramblingCodeSelfConfigEnable}}
from an enabled perspective. If the FAP’s self-configuration
capability for {{param}} is available and enabled, this parameter MAY
contain more than one item and the FAP is expected to select one from
the list for {{param|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.
The PSC being used by the FAP. Self-configuration for PSC is
controlled by
{{param|.Capabilities.UMTS.SelfConfig.PrimaryScramblingCodeConfig}}
from an availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.PrimaryScramblingCodeSelfConfigEnable}}
from an enabled perspective. If the self-configuration capability is
available and enabled, this parameter indicates the value selected by
the FAP among the choices provided in
{{param|PrimaryScramblingCode}}. If the self-configuration capability
is not available or not enabled, then this parameter contains the
first value in {{param|PrimaryScramblingCode}}.
This parameter is DEPRECATED and is replaced by
{{param|MaxFAPTxPowerExpanded}} in order to expand the value range.
This parameter is DEPRECATED and is replaced by
{{param|MaxFAPTxPowerInUseExpanded}} in order to expand the value
range.
Defines the maximum transmission power level a UE can use on PRACH.
{{param}} is expressed as a range of allowed maximum power levels
with “..” (two periods) between the upper and lower values, i.e.
“<Pmax_low>..<Pmax_high>”. {{param}} identifies the
limits between which the FAP can self-configure its maximum transmit
power. Self-configuration for maximum transmission power is
controlled by
{{param|.Capabilities.UMTS.SelfConfig.MaxULTxPowerConfig}} from an
availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.MaxULTxPowerSelfConfigEnable}}
from an enabled perspective. <Pmax_low> and <Pmax_high>
are measured in dBm and have a range of -50 to 33 incremented by 1.
{{bibref|3GPP-TS.25.331|Section 10.3.6.39}}
The maximum transmission power level a UE can use on PRACH.
Self-configuration for maximum transmission power is controlled by
{{param|.Capabilities.UMTS.SelfConfig.MaxULTxPowerConfig}} from an
availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.MaxULTxPowerSelfConfigEnable}}
from an enabled perspective. If the self-configuration capability is
available and enabled, this parameter indicates the value selected by
the FAP among the range provided in {{param|MaxULTxPower}}. If the
self-configuration capability is not available or not enabled, then
this parameter contains a value selected by the ACS.
The value of the transmission power of the Primary Common PIlot
CHannel (P-CPICH). The P-CPICH physical channel carries the common
pilots of the cell. Parameter in SIB5. {{param}} is expressed as a
range of allowed transmission power levels with “..” (two periods)
between the upper and lower values, i.e.
“<Pmax_low>..<Pmax_high>”. {{param}} identifies the
limits between which the FAP can self-configure its transmission
power. Self-configuration for transmission power is controlled by
{{param|.Capabilities.UMTS.SelfConfig.PCPICHPowerConfig}} from an
availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.PCPICHPowerSelfConfigEnable}}
from an enabled perspective. <Pmax_low> and <Pmax_high>
are measured in dBm and have a range of -10.0 to 20.0 incremented by
0.1 dB. {{bibref|3GPP-TS.32.642|Section 6.3.11}}
{{bibref|3GPP-TS.25.104|Section 6.2.1}}
The P-CPICH power measured in {{units}} currently used by the FAP.
Actual values of the maximum transmission power are -10.0 {{units}}
to 20.0 {{units}} in steps of 0.1 dB. The value of {{param}} divided
by 10 yields the actual value of the maximum transmission power.
Self-configuration for transmission power is controlled by
{{param|.Capabilities.UMTS.SelfConfig.PCPICHPowerConfig}} from an
availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.PCPICHPowerSelfConfigEnable}}
from an enabled perspective. If the self-configuration capability is
available and enabled, this parameter indicates the value selected by
the FAP among the range provided in {{param|PCPICHPower}}. If the
self-configuration capability is not available or not enabled, then
this parameter contains a value selected by the ACS.
Defines the power offset between pilot channel and DPDCH. Actual
values of the offset are 0.0 {{units}} to 6.0 {{units}} in steps of
0.25 {{units}}. The value of {{param}} divided by 4 yields the actual
value of the offset. {{bibref|3GPP-TS.25.331|Section 10.3.6.18}}
{{bibref|3GPP-TS.25.214|Section 5.2.1}}
Defines the target value measured in {{units}} for the range of the
FAP’s DL coverage, in terms of RF propagation loss. This value can be
used by the FAP’s self-configuration algorithms to help derive
transmit power levels in the presence of co-channel and adjacent
channel interference. {{bibref|3GPP-TS.25.967|Section 7.2.1}}
Defines the transmission power offset measured in {{units}} of the
Primary SCH relative to the Primary CPICH power. Actual values of the
transmission power offset are -35.0 {{units}} to 15.0 {{units}} in
steps of 0.1 {{units}}. The value of {{param}} divided by 10 yields
the actual value of the transmission power offset.
{{bibref|3GPP-TS.32.642|Section 6.3.11}}
{{bibref|3GPP-TS.25.433|Section 9.1.24 and Section 9.2.1.21}}
Defines the transmission power offset measured in {{units}} of the
Secondary SCH relative to the Primary CPICH power. Actual values of
the transmission power offset are -35.0 {{units}} to 15.0 {{units}}
in steps of 0.1 {{units}}. The value of {{param}} divided by 10
yields the actual value of the transmission power offset.
{{bibref|3GPP-TS.32.642|Section 6.3.11}}
{{bibref|3GPP-TS.25.433|Section 9.1.24 and Section 9.2.1.21}}
Defines the maximum transmission power offset measured in {{units}}
of the PICH channel relative to the Primary CPICH transmission power.
{{bibref|3GPP-TS.32.642|Section 6.3.9}}
{{bibref|3GPP-TS.25.433|Section 9.2.1.49A}}
{{bibref|3GPP-TS.25.331|Section 10.3.6.50}}
Defines the transmission power offset measured in {{units}} of the
PCH relative to the Primary CPICH power. Actual values of the
transmission power offset are -35.0 {{units}} to 15.0 {{units}} in
steps of 0.1 {{units}}. The value of {{param}} divided by 10 yields
the actual value of the transmission power offset.
{{bibref|3GPP-TS.32.642|Section 6.3.9}}
{{bibref|3GPP-TS.25.433|Section 9.1.3.1 and Section 9.2.1.21}}
Defines the transmission power offset measured in {{units}} of the
FACH relative to the Primary CPICH power. Actual values of the
transmission power offset are -35.0 {{units}} to 15.0 {{units}} in
steps of 0.1 {{units}}. The value of {{param}} divided by 10 yields
the actual value of the transmission power offset.
{{bibref|3GPP-TS.32.642|Section 6.3.9}}
{{bibref|3GPP-TS.25.433|Section 9.1.6.1 and Section 9.2.1.21}}
Defines the transmission power offset measured in {{units}} of the
BCH relative to the Primary CPICH power. Actual values of the
transmission power offset are -35.0 {{units}} to 15.0 {{units}} in
steps of 0.1 {{units}}. The value of {{param}} divided by 10 yields
the actual value of the transmission power offset.
{{bibref|3GPP-TS.32.642|Section 9.3.11}}
{{bibref|3GPP-TS.25.433|Section 9.1.24 and Section 9.2.1.21}}
Defines the transmission power offset measured in {{units}} of one
AICH relative to the Primary CPICH power. Parameter defined in SIB5
{{bibref|3GPP-TS.25.331|Section 10.3.6.3}}. Transmission power level
of AICH, AP-AICH and CD/CA-ICH channels compared to CPICH.
{{bibref|3GPP-TS.32.642|Section 6.3.11}}
{{bibref|3GPP-TS.25.433|Section 9.2.2.D}}
The value defines ‘N’ multiples of M(TTI) for CBS DRX calculations at
the UE side.
Value of CBS frame offset (CTCH) on DL FACH. Parameter in SIB5
Defines the number of radio frames in the TTI of the FACH used for
CTCH (MTTI).
This parameter replaces {{param|MaxFAPTxPower}} which is DEPRECATED
in order to expand the value range. Defines the maximum transmission
power allowed on the FAP, maximum value for the linear sum of the
power of all downlink physical channels, that is allowed to be used
in a cell. {{param}} is expressed as a range of allowed maximum power
levels with ".." (two periods) between the upper and lower values,
i.e. "<Pmax_low>..<Pmax_high>". {{param}} identifies the
limits between which the FAP can self-configure its maximum transmit
power. Self-configuration for maximum transmission power is
controlled by
{{param|.Capabilities.UMTS.SelfConfig.MaxFAPTxPowerExpandedConfig}}
from an availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.MaxFAPTxPowerExpandedSelfConfigEnable}}
from an enabled perspective. <Pmax_low> and <Pmax_high>
are measured in dBm and have a range of -30.0 to 20.0 incremented by
0.1 dB. {{bibref|3GPP-TS.32.642|Section 6.3.9}}
{{bibref|3GPP-TS.25.104|Section 6.2.1}}
This parameter replaces {{param|MaxFAPTxPowerInUse}} which is
DEPRECATED in order to expand the value range. The maximum
transmission power measured in {{units}} currently used by the FAP.
Actual values of the maximum transmission power are -30.0 {{units}}
to 20.0 {{units}} in steps of 0.1 dB. The value of {{param}} divided
by 10 yields the actual value of the maximum transmission power.
Self-configuration for maximum transmission power is controlled by
{{param|.Capabilities.UMTS.SelfConfig.MaxFAPTxPowerExpandedConfig}}
from an availability perspective and
{{param|.FAPControl.UMTS.SelfConfig.MaxFAPTxPowerExpandedSelfConfigEnable}}
from an enabled perspective. If the self-configuration capability is
available and enabled, this parameter indicates the value selected by
the FAP among the range provided in {{param|MaxFAPTxPower}}. If the
self-configuration capability is not available or not enabled, then
this parameter contains a value selected by the ACS.
This object contains parameters relating to the neighbor list.
The maximum number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}.}}
table.
The maximum number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}.}}
table.
The number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}.}}
table.
The number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}.}}
table.
Table containing the intra-frequency cell list provided by the ACS. The
table contents may be added/deleted/modified during operation, in which
case these changes shall be reflected in the broadcast information as
soon as possible.
Enables or disables this entry.
Indicates whether this instance of the neighbor shall be included or
excluded in the FAP’s NL configuration.
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code
(MNC) {{bibref|3GPP-TS.23.003}}, {{bibref|3GPP-TS.24.008}}. Mobile
Country Code consists of three digits and uniquely identifies the
country of domicile of the subscriber. Mobile Network Code consists
of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of {{param}} is 5.
RNC-ID of an intra-freq neighbor cell. It uniquely identifies an RNC
within a PLMN. Normally, RNC-ID consists of 12 bits (i.e. a range of
[0:4095]). However, if the value is larger than 4095, then Extended
RNC-ID (range of [4096:65535]) is used in RANAP. The RNC-ID and
Extended RNC-ID are combined into a single parameter here as there is
no explicit need to have them separated.
{{bibref|3GPP-TS.25.413|Section 9.2.1.39}}
Cell Identifier (C-id) that identifies a cell within an RNS. This
Cell Identifier together with the controlling RNC (RNC-ID)
constitutes the UTRAN Cell ID (UC-ID) and is used to identify a cell
uniquely within UTRAN. C-ID is either 12-bit or 16-bit value.
{{bibref|3GPP-TS.25.401|Section 6.1.5}}.
Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and
LAC uniquely identifies the Location Area ID (LAI).
{{bibref|3GPP-TS.23.003|Section 4.1}} {{bibref|3GPP-TS.25.413|Section
9.2.3.6}}
Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC,
and RAC uniquely identifies the Routing Area ID (RAI).
{{bibref|3GPP-TS.23.003|Section 4.2}} {{bibref|3GPP-TS.25.413|Section
9.2.3.7}}
UTRAN Registration Area (URA) {{bibref|3GPP-TS.23.401}}. Indicates to
the UE which {{param}} it shall use in case of overlapping URAs.
{{bibref|3GPP-TS.25.331|Section 10.3.2.6}}
Primary CPICH scrambling code.
Primary CPICH Tx power in {{units}}. Actual values of the power are
-10.0 {{units}} to 50.0 {{units}} in steps of 0.1 dB. The value of
{{param}} divided by 10 yields the actual value of the power.
{{bibref|3GPP-TS.32.642|Section 6.3.11}}
{{bibref|3GPP-TS.25.433|Section 2.2.33}}
{{datatype|expand}}
Table containing the inter-frequency cell list provided by the ACS. The
table contents may be added/deleted/modified during operation, in which
case these changes shall be reflected in the broadcast information as
soon as possible.
Enables or disables this entry.
Indicates whether this instance of the neighbor shall be included or
excluded in the FAP’s NL configuration.
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code
(MNC) {{bibref|3GPP-TS.23.003}}, {{bibref|3GPP-TS.24.008}}. Mobile
Country Code consists of three digits and uniquely identifies the
country of domicile of the subscriber. Mobile Network Code consists
of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of {{param}} is 5.
RNC-ID of an intra-freq neighbor cell. It uniquely identifies an RNC
within a PLMN. Normally, RNC-ID consists of 12 bits (i.e. a range of
[0:4095]). However, if the value is larger than 4095, then Extended
RNC-ID (range of [4096:65535]) is used in RANAP. The RNC-ID and
Extended RNC-ID are combined into a single parameter here as there is
no explicit need to have them separated.
{{bibref|3GPP-TS.25.413|Section 9.2.1.39}}
Cell Identifier (C-id) that identifies a cell within an RNS. This
Cell Identifier together with the controlling RNC (RNC-ID)
constitutes the UTRAN Cell ID (UC-ID) and is used to identify a cell
uniquely within UTRAN. C-ID is either 12-bit or 16-bit value.
{{bibref|3GPP-TS.25.401|Section 6.1.5}}.
Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and
LAC uniquely identifies the Location Area ID (LAI).
{{bibref|3GPP-TS.23.003|Section 4.1}} {{bibref|3GPP-TS.25.413|Section
9.2.3.6}}
Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC,
and RAC uniquely identifies the Routing Area ID (RAI).
{{bibref|3GPP-TS.23.003|Section 4.2}} {{bibref|3GPP-TS.25.413|Section
9.2.3.7}}
UTRAN Registration Area (URA) {{bibref|3GPP-TS.23.401}}. Indicates to
the UE which {{param}} it shall use in case of overlapping URAs.
{{bibref|3GPP-TS.25.331|Section 10.3.2.6}}
The UL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an
FDD mode cell. {{bibref|3GPP-TS.25.433}}
The DL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an
FDD mode cell. {{bibref|3GPP-TS.25.433}}
Primary CPICH scrambling code.
Primary CPICH Tx power in {{units}}. Actual values of the power are
-10.0 {{units}} to 50.0 {{units}} in steps of 0.1 dB. The value of
{{param}} divided by 10 yields the actual value of the power.
{{bibref|3GPP-TS.32.642|Section 6.3.11}}
{{bibref|3GPP-TS.25.433|Section 2.2.33}}
{{datatype|expand}}
The inter-RAT cell lists separated by technology.
{{bibref|3GPP-TS.25.331|Section 10.3.7.23}}
The maximum number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell.GSM.{i}.}}
table.
Number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell.GSM.{i}.}}
table.
Table containing the inter-RAT cell list for GSM provided by the ACS.
The table contents may be added/deleted/modified during operation, in
which case these changes shall be reflected in the broadcast
information as soon as possible.
Enables or disables this entry.
Indicates whether this instance of the neighbor shall be included or
excluded in the FAP’s NL configuration.
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code
(MNC) {{bibref|3GPP-TS.23.003}}, {{bibref|3GPP-TS.24.008}}. Mobile
Country Code consists of three digits and uniquely identifies the
country of domicile of the subscriber. Mobile Network Code consists
of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of {{param}} is 5.
Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and
LAC uniquely identifies the Location Area ID (LAI).
{{bibref|3GPP-TS.23.003|Section 4.1}} {{bibref|3GPP-TS.25.413|Section
9.2.3.6}}
BSIC of the cell per {{bibref|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.
Cell ID of the cell per {{bibref|3GPP-TS.23.003|Section 4.3.1}}.
Indicates how to interpret the BCCH ARFCN. {{enum}}
ARFCN of this cell.
{{datatype|expand}}
This object contains parameters relating to the neighbor list used by
the FAP based on its self-configuration capability and
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.}} configuration of
adding and excluding cells.
The maximum number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}.}}
table.
The maximum number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}.}}
table.
The number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}.}}
table.
The number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}.}}
table.
Table containing the intra-frequency cell list.
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code
(MNC) {{bibref|3GPP-TS.23.003}}, {{bibref|3GPP-TS.24.008}}. Mobile
Country Code consists of three digits and uniquely identifies the
country of domicile of the subscriber. Mobile Network Code consists
of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of {{param}} is 5.
RNC-ID of an intra-freq neighbor cell. It uniquely identifies an RNC
within a PLMN. Normally, RNC-ID consists of 12 bits (i.e. a range of
[0:4095]). However, if the value is larger than 4095, then Extended
RNC-ID (range of [4096:65535]) is used in RANAP. The RNC-ID and
Extended RNC-ID are combined into a single parameter here as there is
no explicit need to have them separated.
{{bibref|3GPP-TS.25.413|Section 9.2.1.39}}
C-ID of the intra-freq neighbour cell {{bibref|3GPP-TS.25.401|Section
6.1.5}}. If {{param|RNCID}} is larger than 4095, then {{param}} will
be 12 bits (i.e. a range of [0:4095]), else {{param}} is 16 bits long
(i.e. range of [4096:65535]). This is needed to facilitate Femto to
Macro handover. Used in {{bibref|3GPP-TS.25.413|Section 9.2.1.28}} as
part of Target Cell ID.
Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and
LAC uniquely identifies the Location Area ID (LAI).
{{bibref|3GPP-TS.23.003|Section 4.1}} {{bibref|3GPP-TS.25.413|Section
9.2.3.6}}
Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC,
and RAC uniquely identifies the Routing Area ID (RAI).
{{bibref|3GPP-TS.23.003|Section 4.2}} {{bibref|3GPP-TS.25.413|Section
9.2.3.7}}
UTRAN Registration Area (URA) {{bibref|3GPP-TS.23.401}}. Indicates to
the UE which {{param}} it shall use in case of overlapping URAs.
{{bibref|3GPP-TS.25.331|Section 10.3.2.6}}
Primary CPICH scrambling code.
Table containing the inter-frequency cell list.
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code
(MNC) {{bibref|3GPP-TS.23.003}}, {{bibref|3GPP-TS.24.008}}. Mobile
Country Code consists of three digits and uniquely identifies the
country of domicile of the subscriber. Mobile Network Code consists
of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of {{param}} is 5.
RNC-ID of an intra-freq neighbor cell. It uniquely identifies an RNC
within a PLMN. Normally, RNC-ID consists of 12 bits (i.e. a range of
[0:4095]). However, if the value is larger than 4095, then Extended
RNC-ID (range of [4096:65535]) is used in RANAP. The RNC-ID and
Extended RNC-ID are combined into a single parameter here as there is
no explicit need to have them separated.
{{bibref|3GPP-TS.25.413|Section 9.2.1.39}}
C-ID of the intra-freq neighbour cell {{bibref|3GPP-TS.25.401|Section
6.1.5}}. If {{param|RNCID}} is larger than 4095, then {{param}} will
be 12 bits (i.e. a range of [0:4095]), else {{param}} is 16 bits long
(i.e. range of [4096:65535]). This is needed to facilitate Femto to
Macro handover. Used in {{bibref|3GPP-TS.25.413|Section 9.2.1.28}} as
part of Target Cell ID.
Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and
LAC uniquely identifies the Location Area ID (LAI).
{{bibref|3GPP-TS.23.003|Section 4.1}} {{bibref|3GPP-TS.25.413|Section
9.2.3.6}}
Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC,
and RAC uniquely identifies the Routing Area ID (RAI).
{{bibref|3GPP-TS.23.003|Section 4.2}} {{bibref|3GPP-TS.25.413|Section
9.2.3.7}}
UTRAN Registration Area (URA) {{bibref|3GPP-TS.23.401}}. Indicates to
the UE which {{param}} it shall use in case of overlapping URAs.
{{bibref|3GPP-TS.25.331|Section 10.3.2.6}}
The UL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an
FDD mode cell. {{bibref|3GPP-TS.25.433}}
The DL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an
FDD mode cell. {{bibref|3GPP-TS.25.433}}
Primary CPICH scrambling code.
The inter-RAT cell lists separated by technology.
{{bibref|3GPP-TS.25.331|Section 10.3.7.23}}
The maximum number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell.GSM.{i}.}}
table.
Number of entries in the
{{object|.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell.GSM.{i}.}}
table.
Table containing the inter-RAT cell list for GSM.
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code
(MNC) {{bibref|3GPP-TS.23.003}}, {{bibref|3GPP-TS.24.008}}. Mobile
Country Code consists of three digits and uniquely identifies the
country of domicile of the subscriber. Mobile Network Code consists
of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of {{param}} is 5.
Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and
LAC uniquely identifies the Location Area ID (LAI).
{{bibref|3GPP-TS.23.003|Section 4.1}} {{bibref|3GPP-TS.25.413|Section
9.2.3.6}}
BSIC of the cell per {{bibref|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.
Cell ID of the cell per {{bibref|3GPP-TS.23.003|Section 4.3.1}}.
Indicates how to interpret the BCCH ARFCN. {{enum}}
ARFCN of this cell.
This object contains parameters relating to Radio Access layers
{{bibref|3GPP-TS.32.405}}
The number of successfully established RABs (with or without
queueing) for CS domain.
The number of RAB establishment failures for CS domain.
The number of successfully established RABs for PS domain.
The number of RABs failed to establish for PS domain.
The number of successfully modified RABs for CS domain.
The number of RABs failed to modify for CS domain.
The number of successfully modified RABs for PS domain.
The number of RABs failed to modify for PS domain.
The number of successfully released RABs for CS domain.
The number of RABs failed to release for CS domain.
The number of successfully released RABs for PS domain.
The number of RABs failed to release for PS domain.
The mean time in {{units}} for a FAP to establish a RAB CS
connection. This measurement is obtained by accumulating the time
intervals for each successful RAB establishment between the receipt
by the FAP of a RANAP "RAB ASSIGNMENT REQUEST" message to establish a
RAB for CS domain, and the first corresponding (based on RAB ID)
transmission by the FAP of a RANAP "RAB ASSIGNMENT RESPONSE" message
for successfully established RABs over a granularity period (Sample
Interval {{bibref|3GPP-TS.32.582|Section 6.3.2}}). This end value of
the time will then be divided by the number of successfully
established RABs observed in the granularity period to give the
arithmetic mean. The accumulator SHALL be reinitialized at the
beginning of each granularity period.
The maximum time in {{units}} for a FAP to establish a RAB CS
connection. This measurement is obtained by monitoring the time
intervals for each successful RAB establishment between the receipt
by the FAP of a RANAP "RAB ASSIGNMENT REQUEST" message to establish a
RAB for CS domain, and the first corresponding (based on RAB ID)
transmission by the FAP of a RANAP "RAB ASSIGNMENT RESPONSE" message
for successfully established RABs. The high tide mark of this time
will be stored in a gauge; the gauge SHALL be reinitialized at the
beginning of each granularity period (Sample Interval
{{bibref|3GPP-TS.32.582|Section 6.3.2}}).
The mean time in {{units}} for a FAP to establish a RAB PS
connection. This measurement is obtained by accumulating the time
intervals for each successful RAB establishment between the receipt
by the FAP of a RANAP "RAB ASSIGNMENT REQUEST" message to establish a
RAB for PS domain, and the first corresponding (based on RAB ID)
transmission by the FAP of a RANAP "RAB ASSIGNMENT RESPONSE" message
for successfully established RABs over a granularity period (Sample
Interval {{bibref|3GPP-TS.32.582|Section 6.3.2}}). This end value of
the time will then be divided by the number of successfully
established RABs observed in the granularity period to give the
arithmetic mean. The accumulator SHALL be reinitialized at the
beginning of each granularity period.
The maximum time in {{units}} for a FAP to establish a RAB PS
connection. This measurement is obtained by monitoring the time
intervals for each successful RAB establishment between the receipt
by the FAP of a RANAP "RAB ASSIGNMENT REQUEST" message to establish a
RAB for PS domain, and the first corresponding (based on RAB ID)
transmission by the FAP of a RANAP "RAB ASSIGNMENT RESPONSE" message
for successfully established RABs. The high tide mark of this time
will be stored in a gauge; the gauge SHALL be reinitialized at the
beginning of each granularity period (Sample Interval
{{bibref|3GPP-TS.32.582|Section 6.3.2}}).
The number of failed Handovers.
The number of successful Handovers.
This object contains parameters relating to the transport
This object contains parameters relating to SCTP as defined in
{{bibref|RFC4960}} and {{bibref|RFC3873}}.
Enables or disables the whole SCTP object and allows the setup or
release of SCTP associations and their related streams.
Heartbeat interval in {{units}}.
Maximum number of consecutive retransmissions to a peer before an
endpoint considers that the peer is unreachable and closes the
association.
Number of retransmission per connection-attempt.
Maximum retransmission per destination address.
Initial value for Retransmit timeout in {{units}}. A retransmission
time value of zero means immediate retransmission.
Maximum value for Retransmit timeout in {{units}}. A retransmission
time value of zero means immediate retransmission.
Minimum value for Retransmit timeout in {{units}}. A retransmission
time value of zero means immediate retransmission. The value of this
parameter MUST be lower than or equal to {{param|RTOMax}}.
Valid cookie life in the 4-way start-up handshake procedure in
{{units}}.
The number of correctly formed SCTP packets, including the proper
checksum, but for which the receiver was unable to identify an
appropriate association.
The number of SCTP packets received with an invalid checksum.
The number of SCTP control chunks sent (retransmissions are not
included).
The number of SCTP ordered data chunks sent (retransmissions are not
included).
The number of SCTP unordered chunks (data chunks in which the U bit
is set to 1) sent (retransmissions are not included).
The number of SCTP control chunks received (no duplicate chunks
included).
The number of SCTP ordered data chunks received (no duplicate chunks
included).
The number of SCTP unordered chunks (data chunks in which the U bit
is set to 1) received (no duplicate chunks included).
The number of user messages that have been sent fragmented.
The number of user messages that have been received fragmented and
submitted to the reassembly process.
The number of SCTP packets sent. Retransmitted DATA chunks are
included.
The number of SCTP packets received. Duplicates are included.
The time of the last discontinuity.
The number of entries in the {{object|.Transport.SCTP.Assoc.{i}.}}
Table
SCTP Association Table
The status of this SCTP association entry.
The Association is active.
The Association establishment is in progress.
The Association graceful shutdown is in progress.
Indicates a locally defined error condition.
The primary IP address of the peer SCTP association entity.
The local SCTP port number used for this SCTP association.
The number of Inbound Streams according to the negotiation at
association start-up.
The number of Outbound Streams according to the negotiation at
association start-up.
The start Time for the present SCTP association.
The time of the last discontinuity.
This object contains parameters relating to Real Time Transport using
RTP.
Enable or disable RTCP.
The number of sent RTP packets.
The number of received RTP packets.
Total number of RTP payload bytes sent.
Total number of RTP payload bytes received.
This object contains performances relating to Real Time Transport using
RTP.
The number of Lost RTP packets in reception.
The number of Far End Lost RTP packets.
Total number of times the receive jitter buffer has overrun.
Total number of times the receive jitter buffer has underrun for a
CS-domain RAB.
The mean Round Trip Time in {{units}} as computed by the source.
{{bibref|RFC3550}}
The maximum Round Trip Time in {{units}} as computed by the source.
{{bibref|RFC3550}}
The mean receive jitter in {{units}} as computed by the source.
{{bibref|RFC3550}}
The maximum receive jitter in {{units}} as computed by the source.
{{bibref|RFC3550}}
The mean far end jitter in {{units}} as computed by the source.
{{bibref|RFC3550}}
The maximum far end jitter in {{units}} as computed by the source.
{{bibref|RFC3550}}
This object contains parameters relating to Packet Transport using
GTP-U.
Echo interval in {{units}}. An Echo interval value of zero means echo
is disabled.
The number of sent GTP-U packets.
The number of received GTP-U packets.
This object contains parameters relating to Tunneling.
The number of entries in the {{object|.Transport.Tunnel.IKESA.{i}.}}
table.
The number of entries in the
{{object|.Transport.Tunnel.ChildSA.{i}.}} table.
The maximum number of virtual interfaces.
The number of entries in the
{{object|.Transport.Tunnel.VirtualInterface.{i}.}} table.
If the SecGW parameters are configured then this parameter determines
whether the CWMP traffic will be sent across the IPsec tunnel or
outside of the IPsec tunnel. If {{false}} then the CWMP traffic will
be sent outside of the IPsec tunnel. If {{true}} then the CWMP
traffic will be sent across the IPsec tunnel.
IKE IPsec Security Association Table. This Table is a member of the
IPsec Security Association Database (SAD). {{bibref|RFC4301}}.
The status of this IKE SA entry.
This value MAY be used by the CPE to indicate a locally defined
error condition.
The IP address of the peer SecGW.
The time that the current IKE SA was set up.
The current IP address assigned to this interface by IKEv2.
The current subnet mask assigned to this interface by IKEv2.
{{list}} Each item is an IP Address of a DNS server for this
interface assigned to this interface by IKEv2.
{{list}} Each item is an IP address of a DHCP server for this
interface. A non empty list instructs the CPE to send any internal
DHCP request to the address contained within this parameter.
The number of inbound packets discarded by the IKE SA due to
Integrity checking errors.
The number of inbound packets discarded by the IKE SA due to other
errors, such as anti-replay errors.
The number of inbound packets discarded by the IKE SA due to
authentication errors.
Child IPsec Security Association Table. This Table is a member of the
IPsec Security Association Database (SAD). {{bibref|RFC4301}}.
{{reference}}
SPI value of the Child SA.
Traffic Direction. If {{true}} this Child SA refers to outbound
traffic. If {{false}} this Child SA refers to inbound traffic.
The time that the current Child SA was set up.
The measured traffic in {{units}} transferred by the Child SA.
The number of inbound {{units}} discarded by the Child SA due to
integrity checking errors.
The number of inbound {{units}} discarded by the Child SA due to
anti-replay errors.
Virtual Interfaces used for associating the tunnel (ephemeral) childSA
pairs with the QueueManagement framework defined in the used root data
model:
* For the Device:2 root model specified in {{bibref|TR-181i2}} the
Device.QoS.Classification.{i}. and Device.QoS.Queue.{i}. objects can
be associated with these interfaces.
* For InternetGatewayDevice root model specified in {{bibref|TR-098}}
the InternetGatewayDevice.QueueManagement.Classification.{i}. and
InternetGatewayDevice.QueueManagement.Queue.{i}. objects can be
associated with these interfaces.
Enables and disables this entry.
{{reference}} If multiple instances of VirtualInterface point to the
same CryptoProfile instance, the associated
{{param|.Transport.Security.CryptoProfile.{i}.MaxChildSA}} determines
whether a new IKE session will be created (dynamically) to negotiate
the child SA(s) for each of the virtual interfaces; otherwise, they
are negotiated through the same IKE session.
DSCP to mark the outer IP header for traffic that is associated with
this virtual interface. A value of -1 indicates copy from the
incoming packet. A value of -2 indicates automatic marking of DSCP as
defined for the UMTS QoS class {{bibref|3GPP-TS.23.107}}. De-tunneled
packets are never re-marked.
{{datatype|expand}}
This object contains parameters relating to Security.
The number of entries in the
{{object|.Transport.Security.Secret.{i}.}} table.
The number of entries in the {{object|.Transport.Security.Pkey.{i}.}}
table.
The number of entries in the
{{object|.Transport.Security.CryptoProfile.{i}.}} table.
Shared Secret Table. This table gathers information about all types of
shared secret-based credentials (UICC).
Enable or disable this Shared Secret entry
The type of this Shared Secret entry.
The status of this Shared Secret entry.
This value MAY be used by the CPE to indicate a locally defined
error condition.
The UICC Card Identifier (UICCID), only numeric values are allowed.
{{bibref|ITU-E.118}}
{{datatype|expand}}
Public Key Table. This table gathers information about all types of
public key-based credentials, such as X.509 certificates.
{{bibref|RFC3280}}.
Enables or disables this Public Key entry.
The last modification time of this Public Key entry.
The Serial Number field in an X.509 certificate
The Issuer field in an X.509 certificate; i.e. the Distinguished Name
(DN) of the entity who has signed the certificate.
The beginning of the certificate validity period; i.e. the Not Before
field in an X.509 certificate.
The end of the certificate validity period; i.e., the Not After field
in an X.509 certificate.
The X.501 Distinguished Name (DN) of the entity associated with the
Public Key; i.e., the Subject field in an X.509 certificate.
{{list}} Each item is a DNS Name. The Subject Alternative Names
extension field in an X.509 certificate.
{{datatype|expand}}
This object contains parameters relating to IKEv2 and IPsec crypto
profiles, which are essentially a subset of the typical IPsec SPD.
{{bibref|RFC4301}}.
Enables and disables this entry.
Specifies the Security mechanism and set of credentials used by the
FAP to authenticate itself. {{reference}} If {{empty}}, the FAP
chooses the authentication method based on local policy. In order to
configure the FAP for both FAP and hosting-party authentication, the
object is populated with an enabled instance of the Pkey object.
Controls the maximum number of child SAs that can be negotiated by a
single IKE session.
IKEv2 encryption algorithm. {{bibref|RFC4307}}
IKEv2 pseudo-random function. {{bibref|RFC4307}}.
IKEv2 integrity function. {{bibref|RFC4307}}
IKEv2 pseudo-random function. {{bibref|RFC4307}}
IPsec encryption algorithm. {{bibref|RFC4307}}
IPsec integrity function. {{bibref|RFC4307}}
The size of the Anti-Replay Window. If 0 Sequence Number Verification
is disabled.
IKEv2 SA rekey timeout in {{units}}.
IPsec SA rekey timeout in {{units}}.
IPsec SA rekey timeout in {{units}}.
DPD timeout in {{units}}.
NAT-T keepalive timeout in {{units}}.
{{datatype|expand}}
This object contains parameters relating to REM (Radio Environment
Measurement).
This object contains parameters relating to radio environment
measurement capabilities for the UMTS system.
FAP REM behavior with respect to ongoing active connections.
Immediately perform REM, even if have active connections or
idle camping UE that may be disrupted.
Wait to initiate REM until no CS bearers or PS bearers of
streaming or higher QoS class are assigned.
Enables or disables Radio Environment Measurement during the FAP
start up.
Enable Periodic Radio Environment Measurement on all enabled RAT.
When {{param|ScanPeriodically}} is {{true}}, this value indicates the
interval in {{units}} which REM is performed while the FAP service is
enabled.
An absolute time reference in UTC to determine when the CPE will
initiate the periodic REM. Each REM MUST occur at (or as soon as
possible after) this reference time plus or minus an integer multiple
of the {{param|PeriodicInterval}}.
{{param}} is used only to set the “phase” of the REM. The actual
value of {{param}} can be arbitrarily far into the past or future.
For example, if {{param|PeriodicInterval}} is 86400 (a day) and if
{{param}} is set to UTC midnight on some day (in the past, present,
or future) then periodic REMs will occur every day at UTC midnight.
These MUST begin on the very next midnight, even if {{param}} refers
to a day in the future. The Unknown Time value defined in
{{bibref|TR-106a2|Section 3.2}} indicates that no particular time
reference is specified. That is, the CPE MAY locally choose the time
reference, and needs only to adhere to the specified
PeriodicInformInterval. If absolute time is not available to the CPE,
its periodic REM behavior MUST be the same as if {{param}} parameter
was set to the Unknown Time value.
{{list}} Each item is a PLMN ID to measure. PLMN ID consists of
Mobile Country Code (MCC) and Mobile Network Code (MNC)
{{bibref|3GPP-TS.23.003}}, {{bibref|3GPP-TS.24.008}}. If {{empty}},
then no specific PLMN ID is provided, meaning that the FAP is
required to scan all available PLMN IDs.
{{list}} Each item is a UMTS Band to measure. Each band is identified
in by a roman numeral {{bibref|3GPP-TS.25.104}}. If {{empty}} then no
specific UMTS band is provided, meaning that the FAP is required to
scan all available bands. The order of the band indicator has no
significance.
{{list}} Each entry is a UARFCN in the DL direction to measure. If
{{empty}}, then no specific UARFCN is provided, meaning that the FAP
is required to scan all UARFCNs that it is aware of.
Specifies the time-out value in {{units}}, measured from the start of
the REM scan, before the REM scan will time out.
Indicates the current status of this scan.
The scan has not been executed and there are no valid scan
results available
Provides more detail when the {{param|ScanStatus}} is either
{{enum|Error|ScanStatus}} or {{enum|Error_TIMEOUT|ScanStatus}}.
The time of the last UMTS system radio environment measurement.
The maximum number of entries available in the
{{object|.REM.WCDMAFDD.Cell.{i}.}} table.
The number entries in the {{object|.REM.WCDMAFDD.Cell.{i}.}} table..
Table indicating the components of the discovered cells.
Table indicating the RF aspect of the discovered cells.
The UTRA Absolute Radio Frequency Channel Number (UARFCN) in the DL
direction of an FDD mode cell. {{bibref|3GPP-TS.25.433}}
Received signal level in {{units}} of the CPICH channel. (Ref. 3GPP
TS 25.133)
Measured EcNo. (energy per chip to interference power density) in
{{units}} received in the downlink pilot channel. Actual values of
the range are -24.0 {{units}} to 0.0 {{units}} in steps of 0.5
{{units}}. The value of {{param}} divided by 2 yields the actual
value of the range. {{bibref|3GPP-TS.25.133|Section 9.1.2.3}}
This measurement is for Inter-frequency handover evaluation, measured
in total {{units}} in the band.
{{bibref|3GPP-TS.25.133|Section9.1.3}}
Primary scrambling code.
Table containing the system information broadcast in the BCCH logical
channel.
Type of Public Land Mobile Network (PLMN).
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code
(MNC) {{bibref|3GPP-TS.23.003}}, {{bibref|3GPP-TS.24.008}}. Mobile
Country Code consists of three digits and uniquely identifies the
country of domicile of the subscriber. Mobile Network Code consists
of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of {{param}} is 5.
Location Area Code (LAC) as defined in SIB 1
{{bibref|3GPP-TS.25.331}}. The concatenation of PLMN ID (MCC+MNC) and
LAC uniquely identifies the LAI (Location Area ID)
{{bibref|3GPP-TS.23.003}}.
Routing Area Code (RAC) as defined in SIB 1
{{bibref|3GPP-TS.25.331}}. The concatenation of PLMN ID (MCC+MNC),
LAC, and RAC uniquely identifies the RAI (Routing Area ID)
{{bibref|3GPP-TS.23.003}}.
Cell Identity as defined in SIB3
{{bibref|3GPP-TS.25.331|Section10.3.2.2}}. {{bibref|3GPP-TS.24.008}}
Primary Common Pilot Channel (CPICH) power level on SIB 5/6
{{bibref|3GPP-TS.25.331|Section10.3.6.55}}.
The CSG-indicator Information Element (IE) in the Master Information
Block reflects the access mode of the CSG cell. It is hence dependent
on the value of {{param|.AccessMgmt.AccessMode}}. If {{true}} the
CSG-indicator IE is present, reflecting closed access to the CSG
cell. If {{false}} the CSG-indicator IE is absent, reflecting the
access mode as “not a closed-access”. {{bibref|3GPP-TS.25.331|Section
10.2.48.8.1}}
Defines the Closed Subscriber Group of the Access Control List. FAP
broadcasts this CSG ID in SIB3
{{bibref|3GPP-TS.25.331|Section10.3.2.8}} depending on the
AccessMode.
{{list}} Each item is a UTRA Absolute Radio Frequency Channel Number
(UARFCN} in the DL direction dedicated to the CSG cells. {{param}} is
broadcast in SIB 11bis {{bibref|3GPP-TS.25.331|Section
10.2.48.8.14a}}. The corresponding UTRA Absolute Radio Frequency
Channel Number (UARFCN} in the UL direction is derived based on the
fixed offset applicable for the frequency band.
This object contains parameters relating to the Primary Scambling Code
(PSC) split information for the CSG. Defined in SIB3/11bis
{{bibref|3GPP-TS.25.331|Section 10.3.2.8 and 10.3.2.9}}.
The value of this Information Element (IE) multiplied by 8 specifies
the start PSC value of the first PSC range as specified in
{{bibref|3GPP-TS.25.331|Section 8.6.2.4}}.
This Information Element (IE) specifies the number of PSCs reserved
for CSG cells in each PSC range.
If this Information Element (IE) is included, the UE shall calculate
the second PSC range as specified in {{bibref|3GPP-TS.25.331|Section
8.6.2.4}}. If this Information Element (IE) is not included, the UE
shall consider the second PSC range to be not present.
This object defines parameters related to the surface point of the
ellipsoid. {{bibref|3GPP-TS.23.032|Section 5}} It is characterized by
the co-ordinates of an ellipsoid point with altitude, distances, and an
angle of orientation. This information is used to refer to a point on
the Earth's surface, or close to the Earth's surface, with the same
longitude and latitude.
This parameter specifies the latitude of the device's position in
degrees, multiplied by 1 million. The positive value signifies the
direction, north of the equator. The negative value signifies the
direction, south of the equator. Range is from: 90°00.00’ South
(-90,000,000) to 90°00.00’ North (90,000,000). Example: A latitude of
13°19.43’ N would be represented as 13,323,833, derived as
(13*1,000,000)+((19.43*1,000,000)/60). Latitude of 50°0.00’ S would
be represented as value -50,000,000. If 0 then SIB15 is not detected
in the specific cell.
This parameter specifies the longitude of the device's position in
degrees, multiplied by 1 million. The positive value signifies the
direction, east of the prime meridian. The negative value signifies
the direction, west of the prime meridian. Range is from: 180°00.00’
West (-180,000,000) to 180°00.00’ East (180,000,000). Example: A
longitude of 13°19.43’ E would be represented as 13,323,833, derived
as (13*1,000,000)+((19.43*1,000,000)/60). A longitude of 50°0’0’’ W
would be represented as value -50,000,000. If 0 then SIB15 is not
detected in the specific cell.
The uncertainty r is derived from the "uncertainty code" k by r = 10
x ( 1.1 <power> (k-1) ) {{bibref|3GPP-TS.23.032|Section6.2}}
The uncertainty r is derived from the "uncertainty code" k by r = 10
x ( 1.1 <power> (k-1) ) {{bibref|3GPP-TS.23.032|Section6.2}}
The Information Element (IE) value 'N' is derived by this formula: 2N
<= a < 2(N+1) Where 'a' is the orientation in degrees (0..179).
The degree of confidence in the ellipsoid's points expressed in
{{units}}.
This object contains parameters relating to GSM REM capabilities.
FAP REM behavior with respect to ongoing active connections.
Immediately perform REM, even if have active connections or
idle camping UE that may be disrupted.
Wait to initiate REM until no CS bearers or PS bearers of
streaming or higher QoS class are assigned.
Enables or disables Radio Environment Measurement during the FAP
start up.
Enable Periodic Radio Environment Measurement on all enabled RAT.
When {{param|ScanPeriodically}} is {{true}}, this value indicates the
interval in {{units}} which REM is performed while the FAP service is
enabled.
An absolute time reference in UTC to determine when the CPE will
initiate the periodic REM. Each REM MUST occur at (or as soon as
possible after) this reference time plus or minus an integer multiple
of the {{param|PeriodicInterval}}.
{{param}} is used only to set the “phase” of the REM. The actual
value of {{param}} can be arbitrarily far into the past or future.
For example, if {{param|PeriodicInterval}} is 86400 (a day) and if
{{param}} is set to UTC midnight on some day (in the past, present,
or future) then periodic REMs will occur every day at UTC midnight.
These MUST begin on the very next midnight, even if {{param}} refers
to a day in the future. The Unknown Time value defined in
{{bibref|TR-106a2|Section 3.2}} indicates that no particular time
reference is specified. That is, the CPE MAY locally choose the time
reference, and needs only to adhere to the specified
PeriodicInformInterval. If absolute time is not available to the CPE,
its periodic REM behavior MUST be the same as if {{param}} parameter
was set to the Unknown Time value.
{{list}} Each item is a PLMNID. PLMN ID consists of Mobile Country
Code (MCC) and Mobile Network Code (MNC) {{bibref|3GPP-TS.23.003}},
{{bibref|3GPP-TS.24.008}}. Mobile Country Code consists of three
digits and uniquely identifies the country of domicile of the
subscriber. Mobile Network Code consists of two or three digits and
identifies the Home PLMN within a country. For a 2-digit MNC the
total string length of the PLMNID is 5. If {{empty}} no specific PLMN
ID is provided, meaning that the FAP is required to report all
available PLMN IDs. If a list is provided, the FAP is expected to
limit the REM measurement to the PLMN(s) specified in this list only
and ignore others even if they are detected.
{{list}} Each item is a GSM Band to measure. {{enum}} If {{empty}}
then no specific GSM band is provided, meaning that the FAP MUST scan
all bands. If a list is provided, the FAP is expected to limit the
REM measurement to the band(s) specified in this list only and ignore
others even if they are detected.
{{list}} Each item is a GSM ARFCN to measure. If {{empty}} then no
specific ARFCN is provided, meaning that the FAP is required to scan
all ARFCNs. If a list is provided, the FAP is expected to limit the
REM measurement to the ARFCN(s) specified in this list only and
ignore others even if they are detected.
Specifies the time-out value in {{units}}, measured from the start of
the REM scan, before the REM scan will time out.
Indicates the current status of this scan.
The scan has not been executed and there are no valid scan
results available
Provides more detail when the {{param|ScanStatus}} is either
{{enum|Error|ScanStatus}} or {{enum|Error_TIMEOUT|ScanStatus}}.
The time of the last GSM radio environment measurement.
The maximum number of entries allowed in the
{{object|.REM.GSM.Cell.{i}.}} table.
The number of entries in the {{object|.REM.GSM.Cell.{i}.}} table.
Table indicating the components of the discovered cells.
Indicates how to interpret the BCCH ARFCN.
Absolute Radio Frequency Channel Number (ARFCN)
{{bibref|3GPP-TS.05.05}}.
Base Station Identity Code {{bibref|3GPP-TS.03.03}}.
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code
(MNC) {{bibref|3GPP-TS.23.003}}, {{bibref|3GPP-TS.24.008}}. Mobile
Country Code consists of three digits and uniquely identifies the
country of domicile of the subscriber. Mobile Network Code consists
of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of the PLMNID is 5.
Location Area Code (LAC) as defined in SIB1
{{bibref|3GPP-TS.25.331}}. The concatenation of PLMN ID (MCC+MNC) and
LAC uniquely identifies the LAI (Location Area ID)
{{bibref|3GPP-TS.23.003}}.
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). {{bibref|3GPP-TS.23.003|Section 4.2}}
{{bibref|3GPP-TS.25.413|Section 9.2.3.7}}
Cell Identity. {{bibref|3GPP-TS.25.331|Section 10.3.2.2}}
Received signal level in {{units}} of the BCCH carrier.
This object contains the parameters relating to the GPS scan.
Enables or disables GPS scans during the FAP start up.
Enables or disables periodic GPS scans.
When {{param|ScanPeriodically}} is {{true}}, this value indicates the
interval in {{units}} which GPS scan is performed while the FAP
service is enabled.
An absolute time reference in UTC to determine when the CPE will
initiate the periodic GPS scan. Each GPS scan MUST occur at (or as
soon as possible after) this reference time plus or minus an integer
multiple of the {{param|PeriodicInterval}}.
{{param}} is used only to set the “phase” of the GPS scan. The actual
value of {{param}} can be arbitrarily far into the past or future.
For example, if {{param|PeriodicInterval}} is 86400 (a day) and if
{{param}} is set to UTC midnight on some day (in the past, present,
or future) then periodic GPS scans will occur every day at UTC
midnight. These MUST begin on the very next midnight, even if
{{param}} refers to a day in the future. The Unknown Time value
defined in {{bibref|TR-106a2|Section 3.2}} indicates that no
particular time reference is specified. That is, the CPE MAY locally
choose the time reference, and needs only to adhere to the specified
PeriodicInformInterval. If absolute time is not available to the CPE,
its periodic GPS scan behavior MUST be the same as if {{param}}
parameter was set to the Unknown Time value.
Whether or not the FAP SHOULD maintain a continuous GPS lock (e.g. as
a frequency stability source).
Specifies the time-out value in {{units}} since the test started
after which the test will time out. A timed out test is to be
reported as {{enum|Error_TIMEOUT|ScanStatus}} with
{{param|ErrorDetails}} indicating “Timed out”.
Indicates the current status of this scan.
The scan has not been executed and there are no valid scan
results available
Provides more detail when the {{param|ScanStatus}} is either
{{enum|Error|ScanStatus}} or {{enum|Error_TIMEOUT|ScanStatus}}.
The time of the last GPS scan.
Specifies the date and time, when the GPS scan last completed
successfully. This value is retained across reboot. The values for
LockedLatitude, LockedLongitute and NumberOfSattelites correspond to
this time. If a scan has never succeeded before, the value will be
the Unknown Time value, as defined in {{bibref|TR-106a2|Section
3.2}}.
This parameter specifies the actual location of the FAP, returned by
the GPS Diagnostics Test. This parameter specifies the latitude of
the device's position in degrees, multiplied by 1 million. The
positive value signifies the direction, north of the equator. The
negative value signifies the direction, south of the equator. Range
is from: 90°00.00’ South (-90,000,000) to 90°00.00’ North
(90,000,000). Example: A latitude of 13°19.43’ N would be represented
as 13,323,833, derived as (13*1,000,000)+((19.43*1,000,000)/60).
Latitude of 50°0.00’ S would be represented as value -50,000,000.
This value is retained across reboots and is only reset after another
scan completes successfully. If a scan has never succeeded before,
the value 0 is reported.
This parameter specifies the actual location of the FAP, returned by
the GPS Diagnostics Test. This parameter specifies the longitude of
the device's position in degrees, multiplied by 1 million. The
positive value signifies the direction, east of the prime meridian.
The negative value signifies the direction, west of the prime
meridian. Range is from: 180°00.00’ West (-180,000,000) to 180°00.00’
East (180,000,000). Example: A longitude of 13°19.43’ E would be
represented as 13,323,833, derived as
(13*1,000,000)+((19.43*1,000,000)/60). A longitude of 50°0’0’’ W
would be represented as value -50,000,000. This value is retained
across reboots and is only reset after another scan completes
successfully. If a scan has never succeeded before, the value 0 is
reported.
The number of satellites that were locked during the test execution.
The greater the number of satellites the better the precision of the
results. This value is retained across reboots and is only reset
after another scan completes successfully. If a scan has never
succeeded before, the value 0 is reported.
This object contains parameters relating to Fault/Alarm Management.
The number of entries in the
{{object|.FaultMgmt.SupportedAlarm.{i}.}} table.
The maximum number of entries allowed in the
{{object|.FaultMgmt.CurrentAlarm.{i}.}} table.
The number of entries in the {{object|.FaultMgmt.CurrentAlarm.{i}.}}
table.
The number of entries in the {{object|.FaultMgmt.HistoryEvent.{i}.}}
table.
The number of entries in the
{{object|.FaultMgmt.ExpeditedEvent.{i}.}} table.
The number of entries in the {{object|.FaultMgmt.QueuedEvent.{i}.}}
table.
Supported Alarm Entries which can be raised by the FAP. The instance
numbers for this table SHOULD be maintained across firmware upgrades of
the device.
Indicates the type of FAP event. See {{bibref|3GPP-TS.32.111-5}} for
information on pre-defined alarm types.
Qualifies the alarm and provides further information than
{{param|EventType}}. See {{bibref|3GPP-TS.32.111-5}} for information
on pre-defined probable causes.
Provides further qualification on the alarm beyond
{{param|EventType}} and {{param|ProbableCause}}. This is not 3GPP
standards based and is vendor defined. This will be {{empty}} if the
FAP doesn’t support unique indexing of the table using {{param}}. The
string can be set to "*" to indicate the default case if only a
subset of {{param}} are to be contained within the table.
Indicates the relative level of urgency for operator attention, see
{{bibref|ITU-X.733}}. {{enum}} Although {{enum|Indeterminate}} is
defined in {{bibref|ITU-X.733}} it SHOULD NOT be used by the FAP as a
{{param}}. This will be {{empty}} if the FAP doesn’t support unique
indexing of the table using {{param}}. The string can be set to “*”
to indicate the default case if only a subset of {{param}} are to be
contained within the table.
{{empty}}
Indicates the reporting mechanism setting of the alarm. {{enum}}
The FAP inserts the alarm into the
{{object|.FaultMgmt.ExpeditedEvent.{i}.}} table and the
{{object|.FaultMgmt.HistoryEvent.{i}.}} table.
The FAP inserts the alarm into the
{{object|.FaultMgmt.QueuedEvent.{i}.}} table and the
{{object|.FaultMgmt.HistoryEvent.{i}.}} table.
The FAP inserts the alarm into the
{{object|.FaultMgmt.HistoryEvent.{i}.}} table.
The FAP ignores the alarm.
{{datatype|expand}}
Contains all currently active alarms (whose
{{param|.FaultMgmt.SupportedAlarm.{i}.PerceivedSeverity}} is not
{{enum|Cleared|.FaultMgmt.SupportedAlarm.{i}.PerceivedSeverity}}). New
raised alarms result in a new entry in this table being added, any
changes to the alarm as a result of an update event are updated in the
existing table entry, and a clear event raised against an alarm results
in the alarm being removed from this table. Active alarms at the time
of a power failure or reboot are removed from this table.
Identifies one Alarm Entry in the Alarm List. This value MUST be
uniquely allocated by the FAP to the alarm instance during the
lifetime of the individual alarm.
Indicates the date and time when the alarm was first raised by the
FAP.
Indicates the date and time when the alarm was last changed by the
FAP.
Specifies the instance of the Informational Object Class in which the
FAP alarm occurred by carrying the Distinguished Name (DN) of this
object instance. This object may or may not be identical to the
object instance actually emitting the notification to the ACS. The
{{param|.DNPrefix}} should be pre-pended to the local DN to create
the ManagedObjectInstance. Encode the Managed Objects representation
in string format as defined in {{bibref|3GPP-TS.32.300}}.
Indicates the type of FAP event. See {{bibref|3GPP-TS.32.111-5}} for
information on pre-defined alarm types.
Qualifies the alarm and provides further information than
{{param|EventType}}. See {{bibref|3GPP-TS.32.111-5}} for information
on pre-defined probable causes.
Provides further qualification on the alarm beyond
{{param|EventType}} and {{param|ProbableCause}}. This is not 3GPP
standards based and is vendor defined. This will be {{empty}} if the
FAP doesn’t support inclusion of this information.
Indicates the relative level of urgency for operator attention, see
{{bibref|ITU-X.733}}. {{enum}} Although {{enum|Indeterminate}} is
defined in {{bibref|ITU-X.733}} it SHOULD NOT be used by the FAP as a
{{param}}.
This provides a textual string which is vendor defined. This will be
{{empty}} if the FAP doesn’t support inclusion of this information.
This contains additional information about the alarm and is vendor
defined.
Alarm events added or updated in
{{object|.FaultMgmt.CurrentAlarm.{i}.}} are simultaneously entered into
the this table. This table also contains alarm clearing events. Active
alarms at the time of a power failure or reboot may not get an alarm
clearing event. If maximum instance number
{{param|.FaultMgmt.HistoryEventNumberOfEntries}} is reached, the next
event overrides the object with instance number 1. Subsequent entries
override objects at sequentially increasing instance numbers. This
logic provides for automatic "rolling" of records. The data in this
table is maintained across reboots.
Indicates the date and time when the alarm event occurs.
Identifies one Alarm Entry in the Alarm List. This value MUST be
uniquely allocated by the FAP to the alarm instance during the
lifetime of the individual alarm.
Indicates the reason for the specific alarm notification event.
{{enum}}
Specifies the instance of the Informational Object Class in which the
FAP alarm occurred by carrying the Distinguished Name (DN) of this
object instance. This object may or may not be identical to the
object instance actually emitting the notification to the ACS. The
{{param|.DNPrefix}} should be pre-pended to the local DN to create
the ManagedObjectInstance. Encode the Managed Objects representation
in string format as defined in {{bibref|3GPP-TS.32.300}}.
Indicates the type of FAP event. See {{bibref|3GPP-TS.32.111-5}} for
information on pre-defined alarm types.
Qualifies the alarm and provides further information than
{{param|EventType}}. See {{bibref|3GPP-TS.32.111-5}} for information
on pre-defined probable causes.
Provides further qualification on the alarm beyond
{{param|EventType}} and {{param|ProbableCause}}. This is not 3GPP
standards based and is vendor defined. This will be {{empty}} if the
FAP doesn’t support inclusion of this information.
Indicates the relative level of urgency for operator attention, see
{{bibref|ITU-X.733}}. {{enum}} Although {{enum|Indeterminate}} is
defined in {{bibref|ITU-X.733}} it SHOULD NOT be used by the FAP as a
{{param}}.
This provides a textual string which is vendor defined. This will be
{{empty}} if the FAP doesn’t support inclusion of this information.
This contains additional information about the alarm and is vendor
defined.
Alarm events added or updated in
{{object|.FaultMgmt.CurrentAlarm.{i}.}} are simultaneously entered into
the this table if their corresponding entry in
{{object|.FaultMgmt.SupportedAlarm.{i}.}} has
{{param|.FaultMgmt.SupportedAlarm.{i}.ReportingMechanism}} set to
{{enum|0 Expedited|.FaultMgmt.SupportedAlarm.{i}.ReportingMechanism}}.
This table also contains alarm clearing events. This object has a fixed
number of entries with instance numbers from 1 to
{{param|.FaultMgmt.HistoryEventNumberOfEntries}}. Initially the table
starts with all instances having {{param|EventTime}} set to the Unknown
Time value, as defined in {{bibref|TR-106a2}}. If maximum instance
number {{param|.FaultMgmt.ExpeditedEventNumberOfEntries}} is reached,
the next event overrides the object with instance number 1. Subsequent
entries override objects at sequentially increasing instance numbers.
This logic provides for automatic "rolling" of records. When a new
alarm replaces an existing alarm, then all parameter values for that
instance are considered as changed for the purposes of value change
notifications to the ACS (even if their new values are identical to
those of the prior alarm).
Indicates the date and time when the alarm event occurs. For an
unpopulated entry, the value is the Unknown Time as defined in
{{bibref|TR-106a2}}.
Identifies one Alarm Entry in the Alarm List. This value MUST be
uniquely allocated by the FAP to the alarm instance during the
lifetime of the individual alarm. For an unpopulated entry, the value
is {{empty}}.
Indicates the reason for the specific alarm notification event.
{{enum}}
Specifies the instance of the Informational Object Class in which the
FAP alarm occurred by carrying the Distinguished Name (DN) of this
object instance. This object may or may not be identical to the
object instance actually emitting the notification to the ACS. The
{{param|.DNPrefix}} should be pre-pended to the local DN to create
the ManagedObjectInstance. Encode the Managed Objects representation
in string format as defined in {{bibref|3GPP-TS.32.300}}.
Indicates the type of FAP event. See {{bibref|3GPP-TS.32.111-5}} for
information on pre-defined alarm types.
Qualifies the alarm and provides further information than
{{param|EventType}}. See {{bibref|3GPP-TS.32.111-5}} for information
on pre-defined probable causes.
Provides further qualification on the alarm beyond
{{param|EventType}} and {{param|ProbableCause}}. This is not 3GPP
standards based and is vendor defined. This will be {{empty}} if the
FAP doesn’t support inclusion of this information.
Indicates the relative level of urgency for operator attention, see
{{bibref|ITU-X.733}}. {{enum}} Although {{enum|Indeterminate}} is
defined in {{bibref|ITU-X.733}} it SHOULD NOT be used by the FAP as a
{{param}}.
This provides a textual string which is vendor defined. This will be
{{empty}} if the FAP doesn’t support inclusion of this information.
This contains additional information about the alarm and is vendor
defined.
Alarm events added or updated in
{{object|.FaultMgmt.CurrentAlarm.{i}.}} are simultaneously entered into
the this table if their corresponding entry in
{{object|.FaultMgmt.SupportedAlarm.{i}.}} has
{{param|.FaultMgmt.SupportedAlarm.{i}.ReportingMechanism}} set to
{{enum|1 Queued|.FaultMgmt.SupportedAlarm.{i}.ReportingMechanism}}.
This table also contains alarm clearing events. This object has a fixed
number of entries with instance numbers from 1 to
{{param|.FaultMgmt.HistoryEventNumberOfEntries}}. Initially the table
starts with all instances having {{param|EventTime}} set to the Unknown
Time value, as defined in {{bibref|TR-106a2}}. If maximum instance
number {{param|.FaultMgmt.QueuedEventNumberOfEntries}} is reached, the
next event overrides the object with instance number 1. Subsequent
entries override objects at sequentially increasing instance numbers.
This logic provides for automatic "rolling" of records. When a new
alarm replaces an existing alarm, then all parameter values for that
instance are considered as changed for the purposes of value change
notifications to the ACS (even if their new values are identical to
those of the prior alarm).
Indicates the date and time when the alarm event occurs. For an
unpopulated entry, the value is the Unknown Time as defined in
{{bibref|TR-106a2}}.
Identifies one Alarm Entry in the Alarm List. This value MUST be
uniquely allocated by the FAP to the alarm instance during the
lifetime of the individual alarm. For an unpopulated entry, the value
is {{empty}}.
Indicates the reason for the specific alarm notification event.
{{enum}}
Specifies the instance of the Informational Object Class in which the
FAP alarm occurred by carrying the Distinguished Name (DN) of this
object instance. This object may or may not be identical to the
object instance actually emitting the notification to the ACS. The
{{param|.DNPrefix}} should be pre-pended to the local DN to create
the ManagedObjectInstance. Encode the Managed Objects representation
in string format as defined in {{bibref|3GPP-TS.32.300}}.
Indicates the type of FAP event. See {{bibref|3GPP-TS.32.111-5}} for
information on pre-defined alarm types.
Qualifies the alarm and provides further information than
{{param|EventType}}. See {{bibref|3GPP-TS.32.111-5}} for information
on pre-defined probable causes.
Provides further qualification on the alarm beyond
{{param|EventType}} and {{param|ProbableCause}}. This is not 3GPP
standards based and is vendor defined. This will be {{empty}} if the
FAP doesn’t support inclusion of this information.
Indicates the relative level of urgency for operator attention, see
{{bibref|ITU-X.733}}. {{enum}} Although {{enum|Indeterminate}} is
defined in {{bibref|ITU-X.733}} it SHOULD NOT be used by the FAP as a
{{param}}.
This provides a textual string which is vendor defined. This will be
{{empty}} if the FAP doesn’t support inclusion of this information.
This contains additional information about the alarm and is vendor
defined.
This object contains parameters relating to Performance Management.
This object contains parameters relating to File Management for
uploading of Performance Files to a designated File Server.
Enables or disables the ability to send FAP information periodically
to a designated File Server.
URL specifying the destination file location. HTTP and HTTPS
transports MUST be supported. Other optional transports MAY be
supported. This argument specifies only the destination file
location, and does not indicate in any way the name or location of
the local file to be uploaded.
Username to be used by the FAP to authenticate with the file server.
This string is set to {{empty}} if no authentication is required.
Password to be used by the FAP to authenticate with the file server.
This string is set to {{empty}} if no authentication is required.
The duration in {{units}} of the interval for which the FAP MUST
create an Performance File and attempt to upload the file to
{{param|URL}} if {{param|PeriodicUploadEnable}} is {{true}}.
An absolute time reference in UTC to determine when the FAP will
initiate the periodic file upload. Each file upload MUST occur at
this reference time plus or minus an integer multiple of the
{{param|PeriodicUploadInterval}}. {{param}} is used only to set the
“phase” of the periodic uploads. The actual value of {{param}} can be
arbitrarily far into the past or future. For example, if
{{param|PeriodicUploadInterval}} is 86400 (a day) and if {{param}} is
set to UTC midnight on some day (in the past, present, or future)
then periodic file uploads will occur every day at UTC midnight.
These MUST begin on the very next midnight, even if {{param}} refers
to a day in the future. The Unknown Time value as defined in
{{bibref|TR-106a2}} indicates that no particular time reference is
specified. That is, the FAP MAY locally choose the time reference,
and is required only to adhere to the specified
{{param|PeriodicUploadInterval}}. If absolute time is not available
to the FAP, its periodic file upload behavior MUST be the same as if
the {{param}} parameter was set to the Unknown Time value.