TS 28.671
★
Home Node B (HNB) Subsystem (HNS) NRM IRP –
Requirements
Use "3GPP‑Page" to get the Word version,
and "ETSI‑search" to get the PDF version
V16.0.0 (PDF)
2020/06 10 p.
V15.0.0
2018/06 10 p.
V14.0.0
2017/03 10 p.
V13.0.0
2016/01 10 p.
V12.0.0
2014/10 10 p.
V11.1.0
2014/06 10 p.
- Rapporteur:
- Mr. Andrianov, Anatoly Nokia Germany
Content for TS 28.671 Word version: 16.0.0
0 Introduction Word‑p. 5
The present document is part of a TS-family covering the 3rd Generation Partnership Project Technical Specification Group Services and System Aspects, Telecommunication Management; as identified below:
28.671:
Telecommunication management; Home Node B Subsystem (HNS) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements
28.672:
Telecommunication management; Home Node B Subsystem (HNS) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)
28.673:
Telecommunication management; Home Node B (HNB) Subsystem (HNS) Network ResourceModel (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
1 Scope Word‑p. 6
The document describes the requirements for Home NodeB Subsystem (HNS), which includes Home NodeB (HNB) and Home NodeB gateway (HNB GW). The HNS NRM IRP requirements are targeted on both HNB and HNB GW NRM.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
-
References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
-
For a specific reference, subsequent revisions do not apply.
-
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 32.101: "Telecommunication management; Principles and high level requirements".
[3]
TS 32.102: "Telecommunication management; Architecture".
[4]
TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
[5]
TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
[6]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[7]
TS 25.467: "UTRAN architecture for 3G Home NodeB; Stage 2".
[8]
TS 32.107: "Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM)".
[9]
TS 28.620: "Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM)".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
Integration Reference Point (IRP):
See TS 32.150.
Information Service (IS):
See TS 32.150.
Solution Set (SS):
See TS 32.150.
IRP Solution Set:
See TS 32.101.
3.2 Abbreviations Word‑p. 7
For the purposes of the present document, the following abbreviations apply:
CN
Core Network
GW
Gateway
HNB
Home Node B
HNS
Home Node B Subsystem
IRP
Integration Reference Point
IOC
Information Object Class
NRM
Network Resource Model
SCTP
Stream Control Transmission Protocol
4 Concepts and background Word‑p. 8
HNB Subsystem is defined in TS 23.060. According to the definition, a HNB subsystem consists of a HNB and a HNB GW. The HNB Subsystem appears as an RNS to the core network and is connected by means of the Iu-CS interface to the MSC and by means of the Iu-PS interface to the SGSN.
Detailed functions of HNB and HNB GW are described in TS 25.467. To be more specific, HNB is a Customer Premise Equipment that offers the Uu Interface to the UE. It provides RAN connectivity and supports RNC like functions as well as UE registration over Iuh. HNB Gateway (HNB-GW) terminates Iuh from HNB and appears as an RNC to the existing Core network using existing Iu interface. It supports HNB registration and UE registration over Iuh.
Based on the above characteristics, this specification defines respective HNS NRM IRP requirements.
5 Requirements
The following general and high-level requirements apply for the present IRP:
a)
IRP-related requirements in TS 32.101.
b)
IRP-related requirements in TS 32.102.
c)
IRP-related requirements in TS 32.600.
The NRM defined by this IRP:
d)
Shall support communications for telecommunication network management purposes, including management of converged networks.
e)
Is a member of the Federated Network Information Model (FNIM) [8] and its information is derived from FNIM Umbrella Information Model (UIM) [9]
In addition to the above, the following more specific requirements apply:
REQ-HNS_GW-CON-001
The Network Resource Model defined by this IRP shall contain HNB GW specific IOCs and related definitions.
REQ-HNS_GW-CON-002
The Network Resource Model defined by this IRP shall provide support for enabling consistency between HNB GW, HNB and related core network nodes.
REQ-HNS_GW-CON-003
The NRM specified by this IRP shall be able to view configuration information of the HNB GW entity. More detailed information is as follows:
Shall allow for the viewing of basic configuration information including version, equipment type, equipment provider and unique identification, etc.
Shall allow for the viewing of network configuration information including IP address, sub-network mask, default gateway and port configuration information, etc.
Shall allow for the viewing of service related configuration information, for example the maximum number of HNB to be registered, the maximum number of packets to be forwarded, etc.
REQ-HNS_GW-CON-004
The NRM specified by this IRP shall capture Iuh interface information of HNB GW. More detailed information is as follows:
Shall allow for the viewing of basic configuration information including Iuh identification etc.
Shall allow for the viewing of network configuration information including SCTP management information, etc.
REQ-HNS_GW-CON-005
The NRM specified by this IRP shall capture the identity of registered HNB.
$ Change History Word‑p. 9
28.671:
Telecommunication management; Home Node B Subsystem (HNS) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements
28.672:
Telecommunication management; Home Node B Subsystem (HNS) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)
28.673:
Telecommunication management; Home Node B (HNB) Subsystem (HNS) Network ResourceModel (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
The document describes the requirements for Home NodeB Subsystem (HNS), which includes Home NodeB (HNB) and Home NodeB gateway (HNB GW). The HNS NRM IRP requirements are targeted on both HNB and HNB GW NRM.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 32.101: "Telecommunication management; Principles and high level requirements".
[3]
TS 32.102: "Telecommunication management; Architecture".
[4]
TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
[5]
TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
[6]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[7]
TS 25.467: "UTRAN architecture for 3G Home NodeB; Stage 2".
[8]
TS 32.107: "Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM)".
[9]
TS 28.620: "Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM)".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
Integration Reference Point (IRP):
See TS 32.150.
Information Service (IS):
See TS 32.150.
Solution Set (SS):
See TS 32.150.
IRP Solution Set:
See TS 32.101.
3.2 Abbreviations Word‑p. 7
For the purposes of the present document, the following abbreviations apply:
CN
Core Network
GW
Gateway
HNB
Home Node B
HNS
Home Node B Subsystem
IRP
Integration Reference Point
IOC
Information Object Class
NRM
Network Resource Model
SCTP
Stream Control Transmission Protocol
Core Network
GW
Gateway
HNB
Home Node B
HNS
Home Node B Subsystem
IRP
Integration Reference Point
IOC
Information Object Class
NRM
Network Resource Model
SCTP
Stream Control Transmission Protocol
4 Concepts and background Word‑p. 8
HNB Subsystem is defined in TS 23.060. According to the definition, a HNB subsystem consists of a HNB and a HNB GW. The HNB Subsystem appears as an RNS to the core network and is connected by means of the Iu-CS interface to the MSC and by means of the Iu-PS interface to the SGSN.
Detailed functions of HNB and HNB GW are described in TS 25.467. To be more specific, HNB is a Customer Premise Equipment that offers the Uu Interface to the UE. It provides RAN connectivity and supports RNC like functions as well as UE registration over Iuh. HNB Gateway (HNB-GW) terminates Iuh from HNB and appears as an RNC to the existing Core network using existing Iu interface. It supports HNB registration and UE registration over Iuh.
Based on the above characteristics, this specification defines respective HNS NRM IRP requirements.
5 Requirements
The following general and high-level requirements apply for the present IRP:
a)
IRP-related requirements in TS 32.101.
b)
IRP-related requirements in TS 32.102.
c)
IRP-related requirements in TS 32.600.
The NRM defined by this IRP:
d)
Shall support communications for telecommunication network management purposes, including management of converged networks.
e)
Is a member of the Federated Network Information Model (FNIM) [8] and its information is derived from FNIM Umbrella Information Model (UIM) [9]
In addition to the above, the following more specific requirements apply:
REQ-HNS_GW-CON-001
The Network Resource Model defined by this IRP shall contain HNB GW specific IOCs and related definitions.
REQ-HNS_GW-CON-002
The Network Resource Model defined by this IRP shall provide support for enabling consistency between HNB GW, HNB and related core network nodes.
REQ-HNS_GW-CON-003
The NRM specified by this IRP shall be able to view configuration information of the HNB GW entity. More detailed information is as follows:
Shall allow for the viewing of basic configuration information including version, equipment type, equipment provider and unique identification, etc.
Shall allow for the viewing of network configuration information including IP address, sub-network mask, default gateway and port configuration information, etc.
Shall allow for the viewing of service related configuration information, for example the maximum number of HNB to be registered, the maximum number of packets to be forwarded, etc.
REQ-HNS_GW-CON-004
The NRM specified by this IRP shall capture Iuh interface information of HNB GW. More detailed information is as follows:
Shall allow for the viewing of basic configuration information including Iuh identification etc.
Shall allow for the viewing of network configuration information including SCTP management information, etc.
REQ-HNS_GW-CON-005
The NRM specified by this IRP shall capture the identity of registered HNB.
$ Change History Word‑p. 9
a)
The NRM defined by this IRP:
IRP-related requirements in TS 32.101.
b)
IRP-related requirements in TS 32.102.
c)
IRP-related requirements in TS 32.600.
d)
In addition to the above, the following more specific requirements apply:
Shall support communications for telecommunication network management purposes, including management of converged networks.
e)
Is a member of the Federated Network Information Model (FNIM) [8] and its information is derived from FNIM Umbrella Information Model (UIM) [9]
REQ-HNS_GW-CON-001
The Network Resource Model defined by this IRP shall contain HNB GW specific IOCs and related definitions.
REQ-HNS_GW-CON-002
The Network Resource Model defined by this IRP shall provide support for enabling consistency between HNB GW, HNB and related core network nodes.
REQ-HNS_GW-CON-003
The NRM specified by this IRP shall be able to view configuration information of the HNB GW entity. More detailed information is as follows:
Shall allow for the viewing of basic configuration information including version, equipment type, equipment provider and unique identification, etc.
Shall allow for the viewing of network configuration information including IP address, sub-network mask, default gateway and port configuration information, etc.
Shall allow for the viewing of service related configuration information, for example the maximum number of HNB to be registered, the maximum number of packets to be forwarded, etc.
REQ-HNS_GW-CON-004
The NRM specified by this IRP shall capture Iuh interface information of HNB GW. More detailed information is as follows:
Shall allow for the viewing of basic configuration information including Iuh identification etc.
Shall allow for the viewing of network configuration information including SCTP management information, etc.
REQ-HNS_GW-CON-005
The NRM specified by this IRP shall capture the identity of registered HNB.