Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.003  Word version:  16.3.0

Top   Top   Up   Prev   Next
1…   2…   2.8…   3…   4…   5…   6…   7…   8…   9…   10…   11   12…   13…   14…   15…   16…   17…   18…   19…   19.4…   19.5…   20…   21…   22…   23…   24…   25…   26…   27…   28…   28.4…   28.7…   29…   A…   B…   C…   D   E…

 

23  Numbering, addressing and identification for the OAM System |R10|

23.1  Introduction

This clause describes some information needed to access the OAM system as specified in TS 36.300. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document.

23.2  OAM System Realm/Domain

The OAM System Realm/Domain shall be in the form of an Internet domain name, e.g. operator.com, as specified in RFC 1035 and RFC 1123. The OAM System Realm/Domain consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with RFC 1035. Each label shall begin and end with either an alphabetic character or a digit in accordance with RFC 1123. The case of alphabetic characters is not significant.
The OAM System Realm/Domain shall be in the form of "oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org", where "<MNC>" and "<MCC>" fields correspond to the MNC and MCC of the operator's PLMN. Both the "<MNC>" and "<MCC>" fields are 3 digits long. If the MNC of the PLMN is 2 digits, then a zero shall be added at the beginning.
For example, the OAM System Realm/Domain of an IMSI shall be derived as described in the following steps:
  1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see TS 31.102) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning;
  2. use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.3gppnetwork.org" domain name;
  3. add the label "oam" to the beginning of the domain name.
An example of an OAM System Realm/Domain is:
  • IMSI in use: 234150999999999;
Where:
  • MCC = 234;
  • MNC = 15;
  • MSIN = 0999999999;
Which gives the OAM System Realm/Domain name: oam.mnc015.mcc234.3gppnetwork.org.
Up

23.3  Identifiers for Domain Name System proceduresWord‑p. 97

23.3.1  Introduction

This clause describes Domain Name System (DNS) related identifiers used by the procedures specified in TS 29.303.

23.3.2  Fully Qualified Domain Names (FQDNs)

23.3.2.1  General

23.3.2.2  Relay Node Vendor-Specific OAM System

As part of the startup procedure, relay nodes (see TS 36.300, clause 4.7) needs to discover its Operations and Maintainence (OAM) system. A relay node vendor-specific OAM system within an operator's network is identified using the relay node type allocation code from IMEI or IMEISV (IMEI-TAC), MNC and MCC from IMSI and in some cases also tracking area code information associated to the eNB serving the relay node.
A subdomain name for use by E-UTRAN OAM system nodes shall be derived from the MNC and MCC by adding the label "eutran" to the beginning of the OAM System Realm/Domain (see clause 23.2).
The vendor-specific relay node OAM system FQDN shall be constructed as following:
  • tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.imei-tac<IMEI-TAC>.eutran-rn.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org
The IMEI-TAC is 8 decimal digits (see clause 6.2).
The TAC is a 16 bit integer. <TAC-high-byte> is the hexadecimal string of the most significant byte in the TAC and <TAC-low-byte > is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in <TAC-high-byte> or <TAC-low-byte >, "0" digit(s) shall be inserted at the left side to fill the 2 digit coding.
Up

23.3.2.3  Multi-vendor eNodeB Plug-and Play Vendor-Specific OAM System |R12|Word‑p. 98
23.3.2.3.1  General
This clause describes the Fully Qualified Domain Names (FQDNs) used in Multi Vendor Plug and Connect (MvPnC) procedures (see TS 32.508).
The FQDNs used in MvPnC shall be in the form of an Internet domain name and follow the general encoding rules specified in clause 19.4.2.1.
The format of FQDNs used in MvPnC shall follow the "<vendor ID>.<system>.<OAM realm>" pattern.
The <vendor ID> label is optional and is only used in the operator deployments where multiple instances of a particular network entity type are not provided by the same vendor. If present, the <vendor ID> label shall be in the form "vendor<ViD>", where <ViD> field corresponds to the ID of the vendor.
The format of the ViD is vendor specific.
The details of the <system> label are specified in the clauses below.
Up
23.3.2.3.2  Certification Authority server
The Certification Authority server (CA/RA) FQDN shall be derived as follows. The "cara" <system> label is added in front of the operator's OAM realm domain name:
cara.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org
If particular operator deployment scenarios where there are multiple CA/RA servers (one per vendor), the <vendor ID> label is added in front of the "cara" label:
vendor<ViD>.cara.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org
An example of a CA/RA FQDN is:
  • MCC = 123;
  • MNC = 45;
  • ViD = abcd;
which gives the CA/RA FQDN:
  • "cara.oam.mnc045.mcc123.3gppnetwork.org" and "vendorabcd.cara.mnc045.mcc123.3gppnetwork.org".
Up
23.3.2.3.3  Security Gateway
The Security Gateway (SeGW) FQDN shall be derived as follows. The "segw" <system> label is added in front of the operator's OAM realm domain name:
segw.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org
If particular operator deployment scenarios where there are multiple Security Gateways (one per vendor), the <vendor ID> label is added in front of the "segw" label:
  • vendor<ViD>.segw.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org
An example of a SeGW FQDN is:
  • MCC = 123;
  • MNC = 45;
  • ViD = abcd;
which gives the SeGW FQDN:
  • "segw.oam.mnc045.mcc123.3gppnetwork.org" and "vendorabcd.segw.mnc045.mcc123.3gppnetwork.org".
Up
23.3.2.3.4  Element ManagerWord‑p. 99
The Element Manager (EM) FQDN shall be derived as follows. The "em" <system> label is added in front of the operator's OAM realm domain name:
em.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org
If particular operator deployment scenarios where there are multiple Element Managers (one per vendor), the <vendor ID> label is added in front of the "em" label:
vendor<ViD>.em.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org
An example of a EM FQDN is:
  • MCC = 123;
  • MNC = 45;
  • ViD = abcd;
which gives the EM FQDN:
  • "em.oam.mnc045.mcc123.3gppnetwork.org" and "vendorabcd.em.mnc045.mcc123.3gppnetwork.org".
Up


Up   Top   ToC