DATA MODEL DEFINITION |
|
The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Broadband Forum Document has been approved by members of the Forum. This Broadband Forum Document is not binding on the Broadband Forum, any of its members, or any developer or service provider. This Broadband Forum Document is subject to change, but only with approval of members of the Forum. This Document is copyrighted by the Broadband Forum, and all rights are reserved. Portions of this Document may be copyrighted by Broadband Forum members.
This Broadband Forum Document is provided AS IS, WITH ALL FAULTS. ANY PERSON HOLDING A COPYRIGHT IN THIS BROADBAND FORUM DOCUMENT, OR ANY PORTION THEREOF, DISCLAIMS TO THE FULLEST EXTENT PERMITTED BY LAW ANY REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY:
By using this Broadband Forum Document, users acknowledge that implementation may require licenses to patents. The Broadband Forum encourages but does not require its members to identify such patents. For a list of declarations made by Broadband Forum member companies, please see http://www.broadband-forum.org. No assurance is given that licenses to patents necessary to implement this Document will be available for license at all or on reasonable and non-discriminatory terms.
ANY PERSON HOLDING A COPYRIGHT IN THIS BROADBAND FORUM DOCUMENT, OR ANY PORTION THEREOF, DISCLAIMS TO THE FULLEST EXTENT PERMITTED BY LAW (A) ANY LIABILITY (INCLUDING DIRECT, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES UNDER ANY LEGAL THEORY) ARISING FROM OR RELATED TO THE USE OF OR RELIANCE UPON THIS DOCUMENT; AND (B) ANY OBLIGATION TO UPDATE OR CORRECT THIS DOCUMENT.
Broadband Forum Documents may be copied, downloaded, stored on a server or otherwise re-distributed in their entirety only, and may not be modified without the advance written permission of the Broadband Forum.
The text of this notice must be included in all copies of this Broadband Forum Document.
| Data Type | Base Type | Description |
|---|---|---|
| Alias | string | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
| [3GPP-TS.22.011] | 3GPP TS 22.011, Service accessibility, 3GPP SA WG1. |
| [3GPP-TS.22.220] | 3GPP TS 22.220, Service requirements for Home Node B (HNB) and Home eNode B (HeNB), 3GPP SA WG1. |
| [3GPP-TS.25.104] | 3GPP TS 25.104, Base Station (BS) radio transmission and reception (FDD), 3GPP RAN WG4. |
| [3GPP-TS.25.331] | 3GPP TS 25.331, Radio Resource Control (RRC); Protocol specification, 3GPP RAN WG2. |
| [3GPP-TS.25.469] | 3GPP TS 25.469, UTRAN Iuh interface Home Node B Application Part (HNBAP) signalling, 3GPP RAN WG3. |
| [3GPP-TS.32.642] | 3GPP TS 32.642, Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM), 3GPP SA WG5. |
| [IANA-portnumbers] | IANA Port Numbers, Port Numbers, IANA. |
| [SOAP1.1] | Simple Object Access Protocol (SOAP) 1.1, W3C. |
| [TR-069a2] | TR-069 Amendment 2, CPE WAN Management Protocol, Broadband Forum, 2007. |
| [TR-098] | TR-098, Internet Gateway Device Data Model for TR-069, Broadband Forum, 2005. |
| [TR-106a5] | TR-106 Amendment 5, Data Model Template for TR-069-Enabled Devices, Broadband Forum, 2010. |
| [TR-181i2] | TR-181 Issue 2, Device Data Model for TR-069, Broadband Forum, 2010. |
For a given implementation of this data model, the CPE MUST indicate support for the highest version number of any object or parameter that it supports. For example, even if the CPE supports only a single parameter that was introduced in version 1.1, then it will indicate support for version 1.1. The version number associated with each object and parameter is shown in the Version column.
| Name | Type | Write | Description | Object Default | Version |
|---|---|---|---|---|---|
| FAPService.{i}. | object | - | The Femto Access Point (FAP) Service Object.
At most one entry in this table can exist with a given value for Alias. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| FAPService.{i}.Capabilities. | object | - | This object contains parameters relating to the hardware capabilities of the FAP device. | - | 1.0 |
| FAPService.{i}.Capabilities.UMTS. | object | - | This object contains parameters relating to the system and RF aspect of the FAP device that supports the UMTS system (i.e. 3G HNB). | - | 1.0 |
| FAPService.{i}.Capabilities.UMTS.SelfConfig. | object | - | This object contains parameters relating to the self-configuration capabilities of the FAP. Self-configuration is enabled in FAPControl.UMTS.SelfConfig. | - | 1.0 |
| MaxFAPTxPowerConfig | boolean | - | This parameter is DEPRECATED and is replaced by MaxFAPTxPowerExpandedConfig in order to define the expanded value range. | - | 1.0 |
| MaxFAPTxPowerExpandedConfig | boolean | - | This parameter replaces 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 CellConfig.UMTS.RAN.FDDFAP.RF.MaxFAPTxPowerExpanded for the FAP to select from. If false only a single value SHOULD be provided in CellConfig.UMTS.RAN.FDDFAP.RF.MaxFAPTxPowerExpanded. |
- | 1.1 |
| FAPService.{i}.FAPControl. | object | - | This object contains parameters relating to state management and provisioning aspects of the FAP. | - | 1.0 |
| FAPService.{i}.FAPControl.UMTS. | object | - | This object contains parameters relating to the UMTS system specific information. | - | 1.0 |
| FAPService.{i}.FAPControl.UMTS.SelfConfig. | object | - | This object contains parameters relating to the controlling of self-configuration capabilities in the FAP. | - | 1.0 |
| MaxFAPTxPowerSelfConfigEnable | boolean | W | This parameter is DEPRECATED and is replaced by MaxFAPTxPowerExpandedSelfConfigEnable in order to define the expanded value range. | - | 1.0 |
| MaxFAPTxPowerExpandedSelfConfigEnable | boolean | W | This parameter replaces 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 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. |
- | 1.1 |
| LACRACURASelfConfigEnable | boolean | W | Indicates whether the self-configuration capability in the FAP is used or not to determine the values of CellConfig.UMTS.CN.LACRAC and CellConfig.UMTS.RAN.URAList. If true The FAP self-configures the value. If false The ACS MUST provide the specific value to be used. |
- | 1.0 |
| FAPService.{i}.FAPControl.UMTS.Gateway. | object | - | This object contains parameters relating to the Gateways that FAP is connected to. | - | 1.0 |
| FAPGWPort | unsignedInt[:65535] | W | Port number of FAP-GW used for initial Iuh SCTP contact. This value is specified as 29169 according to IANA definition per [IANA-portnumbers], registered on 2009-09-08. Use of IANA-defined value is recommended. | - | 1.0 |
| FAPService.{i}.AccessMgmt. | object | - | This object contains parameters relating to Access Management (ACL, CSG, LIPA). Closed Subscriber Group (CSG) service behavior is specified in [3GPP-TS.22.011]. Note: Cell barring and 3GPP access class parameters are contained in CellConfig.UMTS.RAN.FDDFAP.CellRestriction. (UMTS FAP). |
- | 1.0 |
| AccessMode | string | W | Indicates the type of access mode the FAP operates in. Enumeration of:
When the value is not Open Access non-CSG-capable UE are handled according to NonCSGUEAccessDecision. Note: This parameter controls the setting of the CSGindicator bit, specified in MIB in [3GPP-TS.25.331] (for UMTS FAP). The factory default value MUST be Open Access. |
- | 1.0 |
| MaxUEsServed | int[-1:] | W | Maximum number of concurrent UEs allowed at a cell. Valid for any AccessMode. A value of -1 allows an unlimited number of concurrent UEs up to the limit of FAP capacity. The setting does not affect emergency calls. The factory default value MUST be -1. |
- | 1.1 |
| HNBIdentifier | string(48) | W | This parameter is DEPRECATED and is being replaced by HNBName. | - | 1.0 |
| HomeZoneName | string(48) | W | This parameter is DEPRECATED and is being replaced by HNBName. | - | 1.0 |
| HNBName | string(48) | W | This parameter replaces HNBIdentifier and 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 [Section 5.4.2/3GPP-TS.22.220]. Corresponds to parameter 'hnb-Name' specified in SIB20 in [Section 10.2.48.8.23/3GPP-TS.25.331] for an UMTS FAP. |
- | 1.1 |
| MaxConcurrentCSGUsers | int[-1:] | W | This parameter is DEPRECATED and being replaced with MaxCSGMembers. The factory default value MUST be -1. |
- | 1.0 |
| MaxCSGMembers | int[-1:] | W | Maximum number of concurrent CSG member UEs allowed at a hybrid or closed cell. A value of -1 allows an unlimited number of CSG members up to the limit of FAP capacity. The setting cannot be larger than the value of MaxUEsServed. The setting does not affect emergency calls. [3GPP-TS.22.011], [3GPP-TS.22.220]. The factory default value MUST be -1. |
- | 1.1 |
| MaxNonCSGMembers | int[-1:] | W | Maximum number of concurerent non-CSG member UEs allowed at a hybrid cell. Valid only if AccessMode is Hybrid Access. The setting cannot be larger than the value of MaxUEsServed. The setting does not affect emergency calls. The factory default value MUST be -1. |
- | 1.1 |
| MaxResourceNonCSGMembers | unsignedInt[0:100] | W | 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. | - | 1.1 |
| CSGID | unsignedInt[:134217727] | W | Defines the Closed Subscriber Group of the Access Control List. An UMTS FAP broadcasts this CSG ID in SIB3 depending on the AccessMode. | - | 1.0 |
| FAPService.{i}.AccessMgmt.MemberDetail.{i}. | object | W | Details for CSG and Non-CSG members.
At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the CPE MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with a given value for IMSI. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| FAPService.{i}.AccessMgmt.LocalIPAccess. | object | - | Local IP access. | - | 1.0 |
| FAPService.{i}.AccessMgmt.LocalIPAccess.Rules.{i}. | object | W | 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.
At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the CPE MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with all the same values for DestIPAddress, DestSubnetMask and Protocol. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| FAPService.{i}.CellConfig. | object | - | This object contains parameters relating to configuring the FAP. | - | 1.0 |
| FAPService.{i}.CellConfig.UMTS. | object | - | This object contains parameters relating to configuring UMTS system specific information. | - | 1.0 |
| FAPService.{i}.CellConfig.UMTS.RAN. | object | - | This object contains parameters relating to the RAN-level configuration. | - | 1.0 |
| HNBIDRealm | string(182) | W | The "realm" portion of the HNB-ID where HNB-ID is defined in [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 [Table 36/TR-069a2]. <IMSI> is obtained from the USIM if it is equipped in the FAP. |
- | 1.1 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP. | object | - | This object contains parameters relating to the cell-level configuration for FDD mode FAP. | - | 1.0 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.RRCTimers. | object | - | This object contains parameters related to miscellaneous RRC timers and constants. | - | 1.0 |
| T317 | unsignedInt[0, 10, 30, 60, 180, 600, 1200, 1800] | W | Timer measured in seconds. Defined in SIB1 [Section 13.1 and Section 10.3.3.43/3GPP-TS.25.331]. | - | 1.0 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.PowerControl. | object | - | This object contains parameters related to power control and RACH. | - | 1.0 |
| PowerRampSetup | unsignedInt[1:8] | W | This parameter is DEPRECATED and replaced by PowerRampStepUp in order to correct and align the parameter name to the intended purpose. | - | 1.0 |
| PowerRampStepUp | unsignedInt[1:8] | W | This parameter replaces 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 dB, on PRACH preamble when no acquisition indicator (AI) is detected by the UE. Parameter in SIB5. [Section 10.3.6.54/3GPP-TS.25.331] |
- | 1.1 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.RF. | object | - | This object contains parameters relating to the RF configuration. | - | 1.0 |
| MaxFAPTxPower | string(64) | W | This parameter is DEPRECATED and is replaced by MaxFAPTxPowerExpanded in order to expand the value range. | - | 1.0 |
| MaxFAPTxPowerExpanded | string(64) | W | This parameter replaces 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. MaxFAPTxPowerExpanded 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>". MaxFAPTxPowerExpanded identifies the limits between which the FAP can self-configure its maximum transmit power. Self-configuration for maximum transmission power is controlled by Capabilities.UMTS.SelfConfig.MaxFAPTxPowerExpandedConfig from an availability perspective and 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. [Section 6.3.9/3GPP-TS.32.642] [Section 6.2.1/3GPP-TS.25.104] |
- | 1.1 |
| MaxFAPTxPowerInUse | unsignedInt[0:200] | - | This parameter is DEPRECATED and is replaced by MaxFAPTxPowerInUseExpanded in order to expand the value range. | - | 1.0 |
| MaxFAPTxPowerInUseExpanded | int[-300:200] | - | This parameter replaces MaxFAPTxPowerInUse which is DEPRECATED in order to expand the value range. The maximum transmission power measured in dBm currently used by the FAP. Actual values of the maximum transmission power are -30.0 dBm to 20.0 dBm in steps of 0.1 dB. The value of MaxFAPTxPowerInUseExpanded divided by 10 yields the actual value of the maximum transmission power. Self-configuration for maximum transmission power is controlled by Capabilities.UMTS.SelfConfig.MaxFAPTxPowerExpandedConfig from an availability perspective and 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 MaxFAPTxPower. If the self-configuration capability is not available or not enabled, then this parameter contains a value selected by the ACS. |
- | 1.1 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.NeighborList. | object | - | This object contains parameters relating to the neighbor list. | - | 1.0 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}. | object | W | 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.
At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the CPE MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with a given value for PCPICHScramblingCode. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}. | object | W | 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.
At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the CPE MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with the same values for PCPICHScramblingCode and UARFCNDL. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell. | object | - | The inter-RAT cell lists separated by technology. [Section 10.3.7.23/3GPP-TS.25.331] | - | 1.0 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell.GSM.{i}. | object | W | 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.
At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the CPE MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with a given value for BCCHARFCN. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse. | object | - | This object contains parameters relating to the neighbor list used by the FAP based on its self-configuration capability and CellConfig.UMTS.RAN.FDDFAP.NeighborList. configuration of adding and excluding cells. | - | 1.0 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.IntraFreqCell.{i}. | object | - | Table containing the intra-frequency cell list.
At most one entry in this table can exist with a given value for PCPICHScramblingCode, or with a given value for PCPICHScramblingCode. |
- | 1.0 |
| PLMNID | string(6) | - | PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) [3GPP-TS.23.003], [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 PLMNID is 5. |
- | 1.0 |
| RNCID | unsignedInt[0:65535] | - | 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. [Section 9.2.1.39/3GPP-TS.25.413] |
- | 1.0 |
| LAC | unsignedInt[0:65535] | - | Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). [Section 4.1/3GPP-TS.23.003] [Section 9.2.3.6/3GPP-TS.25.413] |
- | 1.0 |
| RAC | unsignedInt[0:255] | - | Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). [Section 4.2/3GPP-TS.23.003] [Section 9.2.3.7/3GPP-TS.25.413] |
- | 1.0 |
| URA | unsignedInt[0:65535] | - | UTRAN Registration Area (URA) [3GPP-TS.23.401]. Indicates to the UE which URA it shall use in case of overlapping URAs. [Section 10.3.2.6/3GPP-TS.25.331] |
- | 1.0 |
| PCPICHScramblingCode | unsignedInt[0:511] | - | Primary CPICH scrambling code. | - | 1.0 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterFreqCell.{i}. | object | - | Table containing the inter-frequency cell list.
At most one entry in this table can exist with the same values for PCPICHScramblingCode and UARFCNDL, or with the same values for PCPICHScramblingCode and UARFCNDL. |
- | 1.0 |
| PLMNID | string(6) | - | PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) [3GPP-TS.23.003], [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 PLMNID is 5. |
- | 1.0 |
| RNCID | unsignedInt[0:65535] | - | 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. [Section 9.2.1.39/3GPP-TS.25.413] |
- | 1.0 |
| LAC | unsignedInt[0:65535] | - | Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). [Section 4.1/3GPP-TS.23.003] [Section 9.2.3.6/3GPP-TS.25.413] |
- | 1.0 |
| RAC | unsignedInt[0:255] | - | Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). [Section 4.2/3GPP-TS.23.003] [Section 9.2.3.7/3GPP-TS.25.413] |
- | 1.0 |
| URA | unsignedInt[0:65535] | - | UTRAN Registration Area (URA) [3GPP-TS.23.401]. Indicates to the UE which URA it shall use in case of overlapping URAs. [Section 10.3.2.6/3GPP-TS.25.331] |
- | 1.0 |
| PCPICHScramblingCode | unsignedInt[0:511] | - | Primary CPICH scrambling code. | - | 1.0 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterRATCell. | object | - | The inter-RAT cell lists separated by technology. [Section 10.3.7.23/3GPP-TS.25.331] | - | 1.0 |
| FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterRATCell.GSM.{i}. | object | - | Table containing the inter-RAT cell list for GSM.
At most one entry in this table can exist with a given value for BCCHARFCN, or with a given value for BCCHARFCN. |
- | 1.0 |
| PLMNID | string(6) | - | PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) [3GPP-TS.23.003], [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 PLMNID is 5. |
- | 1.0 |
| LAC | unsignedInt[0:65535] | - | Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). [Section 4.1/3GPP-TS.23.003] [Section 9.2.3.6/3GPP-TS.25.413] |
- | 1.0 |
| FAPService.{i}.Transport. | object | - | This object contains parameters relating to the transport | - | 1.0 |
| FAPService.{i}.Transport.Tunnel. | object | - | This object contains parameters relating to Tunneling. | - | 1.0 |
| UseForCWMP | boolean | W | 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. |
- | 1.1 |
| FAPService.{i}.Transport.Tunnel.VirtualInterface.{i}. | object | W | Virtual Interfaces used for associating the tunnel (ephemeral) childSA pairs with the QueueManagement framework defined in the used root data model:
At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the CPE MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with the same values for CryptoProfile and DSCPMarkPolicy. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| FAPService.{i}.Transport.Security. | object | - | This object contains parameters relating to Security. | - | 1.0 |
| FAPService.{i}.Transport.Security.Secret.{i}. | object | - | Shared Secret Table. This table gathers information about all types of shared secret-based credentials (UICC).
At most one entry in this table can exist with a given value for UICCCardID, or with a given value for Alias. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| FAPService.{i}.Transport.Security.Pkey.{i}. | object | - | Public Key Table. This table gathers information about all types of public key-based credentials, such as X.509 certificates. [RFC3280].
At most one entry in this table can exist with a given value for SerialNumber, or with a given value for Alias. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| FAPService.{i}.Transport.Security.CryptoProfile.{i}. | object | W | This object contains parameters relating to IKEv2 and IPsec crypto profiles, which are essentially a subset of the typical IPsec SPD. [RFC4301].
At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the CPE MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with all the same values for AuthMethod, IKEEncrypt, IKEPRF, IKEIntegrity, IKEDH, ESPEncrypt and ESPIntegrity. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| FAPService.{i}.FaultMgmt. | object | - | This object contains parameters relating to Fault/Alarm Management. | - | 1.0 |
| FAPService.{i}.FaultMgmt.SupportedAlarm.{i}. | object | - | 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.
At most one entry in this table can exist with all the same values for EventType, ProbableCause, SpecificProblem and PerceivedSeverity, or with a given value for Alias. |
- | 1.0 |
| Alias | string | W | A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069a4] and described in [Appendix II/TR-069a4], the following mandatory constraints MUST be enforced:
|
- | 1.1 |
| Parameter |
|---|
| Parameter |
|---|
| Parameter |
|---|
| Parameter |
|---|
| FAPService.{i}.AccessMgmt. |
| AccessMode |
| Abbreviation | Description |
|---|---|
| R | Read support is REQUIRED. |
| W | Both Read and Write support is REQUIRED. This MUST NOT be specified for a parameter that is defined as read-only. |
| P | The object is REQUIRED to be present. |
| C | Creation and deletion of instances of the object via AddObject and DeleteObject is REQUIRED. |
| A | Creation of instances of the object via AddObject is REQUIRED, but deletion is not REQUIRED. |
| D | Deletion of instances of the object via DeleteObject is REQUIRED, but creation is not REQUIRED. |
| Name | Requirement |
|---|---|
| FAPService.{i}.REM.WCDMAFDD. | P |
| InServiceHandling | W |
| Name | Requirement |
|---|---|
| FAPService.{i}.REM.GSM. | P |
| InServiceHandling | W |
| Name | Requirement |
|---|---|
| FAPService.{i}.AccessMgmt. | P |
| AccessMode | W |
| NonCSGUEAccessDecision | W |
| CSGMembershipDeterminedLocally | W |
| HNBName | W |
| MaxUEsServed | W |
| MaxCSGMembers | W |
| MaxNonCSGMembers | W |
| MaxResourceNonCSGMembers | W |
| CSGID | W |
| AccessControlList | W |
| MaxMemberDetailEntries | R |
| MemberDetailNumberOfEntries | R |
| FAPService.{i}.AccessMgmt.MemberDetail.{i}. | C |
| Enable | W |
| IMSI | W |
| MSISDN | W |
| MembershipExpires | W |