6 Requirements for O&M
25.4673GPPRelease 17Stage 2TSUTRAN architecture for 3G Home Node B (HNB)
6.1 O&M for HNB
6.1.1 Provisioning Procedure for HNB
Figure 6.1.1-1: Provisioning procedure for HNB.
1. A secure tunnel is established from the HNB to the Security gateway.
2. Location verification shall be performed by the HMS based on information sent by the HNB (e.g. macro neighbour cell scans, global navigational satellite system type of information etc.). HMS determines the serving elements and provides the HNB-GW, HMS and Security Gateway to the HNB. The HMS also provisions configuration parameters to the HNB only after successful location verification in the HMS.
NOTE: Steps 3 & 4 are shown only for completeness. Security Gateway and HMS are shown to highlight the general architecture.
NOTE: In the event information required for verifying location are not available (for example, no macro neighbour cells, no GNSS, no DSL line ID etc. available), HNB-GW discovery may be based on specific operator and/or regulatory policies.
6.1.2 Location Verification
6.1.2.1 General
During location verification, the HNB reports its location information to the HMS. The HMS in turn examines the provided information and verifies the HNB’s location. There are 3 possible types of information for this purpose:
1. Macro-cell Information
2. GNSS location information
3. Broadband connection information, provided that the resulting location information is at least as accurate as location determination based on macro-cell coverage information, whether or not there is macro-cell coverage available at the location of the HNB (e.g. as determined by point 1. above).
NOTE: Not all of this information is mandatory. In fact, the type of reported information is based on factors such as the physical environment in which the HNB is installed and/or possible variations in the HNB’s HW and SW implementation.
6.1.2.2 Macro-cell Information
6.1.2.2.1 General
The HNB is expected to have a radio environment measurement capability. This includes capturing the following type of information from the surrounding environment.
a) UTRAN cell information
– RF level information
– Broadcast information
b) GSM cell information
– RF level information
– Broadcast information
6.1.2.2.2 UTRAN Cell Information
The information in the following table is reported by the HNB to the HMS for each UTRAN cell detected.
Table 6.1.2.2.2-1. UTRAN Cell Information.
|
Information |
Description / Note |
Presence |
3GPP Reference |
|
|
RF information |
UARFCNDL |
UARFCN (DL) |
M |
TS 25.104 [23] sec.5.4, |
|
CPICHRSCP |
RSCP of CPICH |
M |
||
|
PSC |
Primary Scrambling Code |
M |
TS 32.642 [24] sec. 6.3.11 |
|
|
Broadcast information |
PLMN Type |
« GSM-MAP » or « ANSI-41 » |
M |
TS 25.331 [25] sec.10.3.1.12 |
|
MCC |
Mobile Country Code |
M |
TS 24.008 [26], |
|
|
MNC |
Mobile Network Code |
M |
TS 24.008 [26], |
|
|
LAC |
Location Area Code |
M |
TS 24.008 [26] sec.10.5.1.3, TS 32.642 [24] sec. 6.3.10 |
|
|
RAC |
Routing Area Code |
M |
TS 24.008 [26], sec.10.5.1.12.3, TS 25.413 [9], sec.9.2.3.7, TS 32.642 [24] sec. 6.3.10 |
|
|
CellID |
Cell ID |
M |
TS 25.331 [25] sec.10.3.2.2 |
|
|
CSG Cell Info |
<detail per Rel.8 RRC spec> |
O |
Applicable to Rel.8 compliant cell only. |
|
6.1.2.2.3 GSM Cell Information
The information in the following table is reported by the HNB to the HMS for each GSM cell detected.
Table 6.1.2.2.3-1. GSM Cell Information.
|
Information |
Description / Note |
Presence |
3GPP Reference |
|
|
RF information |
ARFCN |
Channel number |
M |
TS 32.652 [27] sec. 6.3.5 |
|
BCCHRSSI |
RSSI of the BCCH carrier. |
M |
TS 32.652 [27] sec. 6.3.5 |
|
|
BSIC |
Base Station ID Code |
M |
TS 32.652 [27] sec. 6.3.5 |
|
|
Broadcast Information |
MCC |
Mobile Country Code |
M |
TS 32.652 [27] sec. 6.3.5 |
|
MNC |
Mobile Network Code |
M |
TS 32.652 [27] sec. 6.3.5 |
|
|
LAC |
Location Area Code |
M |
TS 32.652 [27] sec. 6.3.5 |
|
|
RAC |
Routing Area Code |
M |
TS 32.652 [27] sec. 6.3.5 |
|
|
CellID |
Cell ID |
M |
TS 32.652 [27] sec. 6.3.5 |
|
6.1.2.3 GNSS Location Information
This information consists of, at minimum, latitude and longitude detected by the GNSS receiver (e.g. GPS receiver), if the HNB implementation includes this functionality.
6.1.2.4 Broadband Connection Information
This information consists of the information associated with the broadband connection (e.g. DSL) the HNB is connected with: 1) public IP address assigned to the RGW (e.g. DSL-GW/router), and 2) line identifier to which the RGW is connected with (e.g. DSL line ID) as seen on the broadband service provider. These are applicable only when this information is available to the HNB, and only when the resulting location information is at least as accurate as location determination based on macro-cell coverage information, whether or not there is macro-cell coverage available at the location of the HNB (e.g. as determined by clause 6.1.2.2 above).
6.1.3 HNB-GW Discovery
During the HNB-GW Discovery procedure, the HMS provides the HNB with 3 identities as shown in the following table. The information may be either IP address or FQDN to be resolved by DNS.
Table 6.1.3-1. HNB-GW Discovery Information.
|
Parameter |
Description / Note |
Presence |
3GPP Reference |
|
Serving HMS ID |
One or more IDs may be provided |
M |
|
|
Serving SeGW ID |
One or more IDs may be provided |
M |
|
|
Serving HNB-GW ID |
One or more IDs may be provided |
M |
6.1.4 HNB Provisioning
6.1.4.1 General
During the HNB Provisioning procedure, the HMS transfers the HNB configuration information to the HNB. This includes 3 types of parameters:
1. CN level parameters
2. RAN level parameters
3. RF level parameters
NOTE: The HNB may have auto-configuration capabilities, such that the HMS sends a list/range of values to the HNB, which selects (and returns to HMS) a single value, also based on the information collected measuring the radio environment. The HMS may also provide control parameters of the auto-configuration process.
6.1.4.2 CN Level Parameters
Table 6.1.4.2-1. CN Level Parameters.
|
Parameter |
Description / Note |
Presence |
3GPP Reference |
|
PLMN Type |
“GSM-MAP” or “ANSI-41” |
M |
TS 25.331 [25] sec. 10.3.1.12 |
|
MCC |
Mobile Country Code |
M |
TS 24.008 [26], TS 32.642 [24] sec. 6.3.8 |
|
MNC |
Mobile Network Code |
M |
TS 24.008 [26], TS 32.642 [24] sec. 6.3.8 |
|
LAC |
Location Area Code (one or more LACs may be provided) |
M (Note 1) |
TS 24.008 [26] sec.10.5.1.3, TS 32.642 [24] sec. 6.3.9 |
|
SAC |
Service Area Code |
M |
TS 25.413 [9] sec.9.2.3.9, TS 32.642 [24] sec. 6.3.9 |
|
T3212 |
Periodic LAU timer (CS domain) |
M |
TS 24.008 [26] sec. 10.5.1.12.2 |
|
ATT |
Attach-detach allowed (CS domain) |
M |
TS 24.008 [26] sec. 10.5.1.12.2 |
|
RAC |
Routing area code (PS domain) (one or more RACs may be provided) |
M (Note 1) |
TS 24.008 [26] sec.10.5.1.12.3, TS 32.642 [24] sec. 6.3.9 |
|
NMO |
Network Mode of Operation (Gs i/f) |
M |
TS 24.008 [26] sec. 10.5.1.12.3 |
|
Equivalent PLMN ID |
List of one or more equivalent PLMN ID (MCC + MNC) |
O (Note 2) |
TS 24.008 [26] sec. 10.5.1.13 |
|
Allowed IMSI list |
For access control or membership verification purposes. |
O (Note 3) |
TS 24.008 [26] sec. 10.5.1.4 |
|
CSG Cell Info |
CSG Capability Indication, CSG Id, in case the Cell is CSG capable <any further detail per Rel.8 RRC spec> |
M |
Applicable to Rel.8 compliant cell only. |
|
HNB Location Information |
Location information (Geographical coordinates, Uncertainty code) |
O |
TS 25.413 [9] sec. 9.2.3.11 |
|
SAI for broadcast |
Service Area for broadcast |
M |
TS 25.419 [12] sec. 9.2.11 |
|
Note 1: May be a list/range of values in case the HNB has auto-configuration capabilities. Note 2: This information is operator-dependent based on its circumstance. Note 3: ACL is an optional function at HNB. This information is provided if this function is enabled in the HNB. |
|||
6.1.4.3 RAN Level Parameters
Table 6.1.4.3-1. RAN Level Parameters.
|
Parameter |
Description |
Presence |
3GPP Reference |
|
|
RNCID for HNB |
RNC ID used by HNB |
M |
TS 32.642 [24] sec. 6.3.8 |
|
|
Cell ID |
28-bit “Cell ID” in SIB3 |
M |
TS 25.331 [25] sec. 10.3.2.2 |
|
|
HSPA related |
HSflag |
Whether HSDPA/HSUPA is used or not |
O |
TS 32.642 [24] sec. 6.3.9 |
|
HCS related |
UseOfHCS HCSPrio QHCS |
M |
TS 25.331 [25] sec. 10.3.7.47 and 10.3.7.12, TS 32.642 [24] sec. 6.3.9 |
|
|
Cell selection / reselection related |
Quality measure QqualMin QqualMin-offset QrxlevMin QrxlevMin-offset Sintrasearch Sintersearch SsearchRAT SsearchHCS Treselections UETxPwrMaxRACH QHyst1 |
CPICH Ec/N0 or RSCP if Ec/N0 is used if RSCP is used |
O (Note 1) |
TS 25.331 [25] sec. 10.3.2.3 and 10.3.2.4, TS 32.642 [24] sec. 6.3.9, TS 25.304 [29] |
|
Intra Freq Measurement Related |
Filter coefficient Measurement quantity for freq quality estimate Hysteresis for event 1x Threshold for event 1x TimetoTrigger for event 1x Weighting factor for event 1x Reporting Range Triggering Condition |
Filter coefficient CPICH Ec/No, CPICH RSCP, or pathloss “x” in 1x includes applicable events from 1A to 1J |
O (Note 1) |
TS 25.331 [25] sec. 10.3.7.38 and 10.3.7.39 |
|
Inter-Freq Measurement Related |
Filter coefficient Measurement quantity for freq quality estimate Hysteresis for event 2x Threshold for event 2x TimetoTrigger for event 2x Weighting factor for event 2x |
Filter coefficient CPICH Ec/No, CPICH RSCP “x” in 2x includes applicable events from 2A to 2F |
O (Note 1) |
TS 25.331 [25] sec. 10.3.7.18 and 10.3.7.19 |
|
Inter-RAT Measurement Related |
Filter coefficient BSIC verification required Hysteresis for event 3x Threshold for event 3x TimetoTrigger for event 3x Weighting factor for event 3x |
Filter coefficient “required” / “not required” “x” in 3x includes applicable events from 3A to 3D |
O (Note 1) |
TS 25.331 [25] sec. 10.3.7.29 and 10.3.7.30 |
|
RRC related |
N30x, N31x T30x, T31x, T320 |
RRC constants RRC timers |
O (Note 1) |
TS 25.331 [25] sec. 10.3.3.43 and 10.3.3.44 |
|
Neighbour list (UTRA Intra-Freq cell info list) |
RNCID C-Id LAC RAC PSC |
Defined for each intra-freq cells C-Id is either 12 or 16 bits depending on RNCID length. |
O (Note 2) |
TS 32.642 [24] sec. 6.3.10, TS 25.401 [4] sec. 6.1, TS 25.413 [9] sec. 9.2.1.28 |
|
Neighbour list (UTRA Inter-Freq cell info list) |
RNCID C-Id LAC RAC UARFCN (DL) PSC |
Defined for each inter-freq cells C-Id is either 12 or 16 bits depending on RNCID length |
O (Note 2) |
TS 32.642 [24] sec. 6.3.10, TS 25.401 [4] sec. 6.1, TS 25.413 [9] sec. 9.2.1.28 |
|
Neighbour list (GERAN cell info list) |
CelID BSIC BandIndicator BCCHARFCN |
Defined for each inter-RAT cells (assume GSM cell only). |
O (Note 2) |
TS 32.652 [27] sec. 6.3.5 |
|
HNB Positioning related |
PCAP supported SAS indication |
Indicates if PCAP is supported. Defined if HNB positioning is supported for multiple SASs. |
O |
TS 25.470 [39] |
|
Note 1: Marked as optional based on the operator preference on the extent of provisioning that the HMS performs to the HNB vs. the level of autonomy that HNB has for auto-configuration. In case this IE is absent, default value is assumed (additional implication is that HNB has a set of default parameter values). Note 2: Marked as optional due to several implications: 1) there may be no suitable neighbour cell available based on the RF scanning procedure described earlier, 2) based on operator deployment policy (e.g. dedicated RF channel for HNB layer vs. macro layer), and 3) operator preference on the extent of provisioning that the HMS performs to the HNB vs. the level of autonomy that HNB has for auto-configuration. Regarding 3) above, this may include capabilities such as the HMS to add or remove neighbour cells initially detected by the HNB during the radio environment scanning process, and the HNB to extend the received Neighbour list based on auto-configuration capabilities. |
||||
6.1.4.4 RF Level Parameters
Table 6.1.4.4-1. RF Level Parameters.
|
Parameter |
Description / Note |
Presence |
3GPP Reference |
|
UARFCN (DL) |
Frequency channel number (one or more UARFCNs may be provided) |
O |
TS 25.101 [28] sec. 5.4, TS 25.104 [23] sec. 5.4, TS 32.642 [24] sec. 6.3.11 |
|
PSC |
Primary scrambling code (one or more PSCs may be provided) |
O |
TS 32.642 [24] sec. 6.3.11 |
|
MaxHNBTxPower |
Maximum allowed Tx power of the HNB. |
O |
TS 25.104 [23] sec. 6.2, TS 32.642 [24] sec. 6.3.9 |
|
MaxULTxPower |
The parameter defines the maximum transmission power level a UE can use on PRACH. |
O |
TS 25.101 [28] sec. 6.2, TS 32.642 [24] sec. 6.3.9 |
|
P-CPICHPower |
Transmission power of Primary CPICH (DL config). This may be either a specific value or a range (min / max) of values. |
O |
TS 32.642 [24] sec. 6.3.11 |
|
P-SCHPower |
Primary SCH power offset (DL config) |
O |
TS 32.642 [24] sec. 6.3.11 |
|
S-SCHPower |
Secondary SCH power offset (DL config) |
O |
TS 32.642 [24] sec. 6.3.11 |
|
BCHPower |
BCH power offset (DL config) |
O |
TS 32.642 [24] sec. 6.3.11 |
|
AICHPower |
AICH power offset (DL config, BCCH info) |
O |
TS 25.331 [25] sec. 10.3.6.3, TS 32.642 [24] sec. 6.3.11 |
|
PICHPower |
PICH power offset (DL config, BCCH info) |
O |
TS 25.331 [25] sec. 10.3.6.50, TS 32.642 [24] sec. 6.3.9 |
|
PCHPower |
PCH power offset (DL config, BCCH info) |
O |
TS 32.642 [24] sec. 6.3.9 |
|
FACHPower |
FACH power offset (DL config, BCCH info) |
O |
TS 32.642 [24] sec. 6.3.9 |
|
Note 1: Marked as optional based on the operator preference on the extent of provisioning that the HMS performs to the HNB vs. the level of autonomy that HNB has for auto-configuration. In case this IE is absent, it is assumed that the HNB will derive the suitable value based on its auto-configuration capability. In case this IE is a list/range of values, the HNB will choose a single value based on its auto-configuration capability. UARFCN UL may be automatically determined by the HNB upon UARFCN DL (basing on standard duplex configuration and country-specific spectrum allocation). |
|||
6.2 O&M for HNB-GW
No requirements have been identified.