Top   in Index   Prev   Next

TS 22.042
Network Identity and TimeZone –
Stage 1

V18.0.1 (PDF)2024/03  10 p.
V17.0.0  2022/03  10 p.
V16.0.0  2020/06  10 p.
V15.0.0  2018/06  10 p.
V14.0.0  2017/03  10 p.
V13.0.0  2015/12  10 p.
V12.0.0  2014/10  10 p.
V11.0.0  2012/09  10 p.
V10.0.0  2011/04  10 p.
V9.0.0  2009/12  10 p.
V8.0.0  2009/01  10 p.
V7.0.0  2007/06  10 p.
V6.0.0  2004/12  10 p.
V5.1.0  2003/06  10 p.
V4.2.1  2003/06  10 p.
V3.0.1  1999/10  10 p.
GSM Rel-98 v7.0.0  1999/06  9 p.
GSM Rel-97 v6.0.0  1998/10  9 p.
GSM Rel-96 v5.1.0  1997/12  10 p.
Dr. Scarrone, Enrico

Content for  TS 22.042  Word version:  18.0.1

Here   Top

1  Scopep. 5

The present document describes the feature Network Identity and Timezone (NITZ).
This feature provides the means for serving PLMNs to transfer current identity, time, Daylight Saving Time and the local timezone to Mobile Stations (MS)s, and for the MSs to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the Mobile Equipment (ME) or have changed their name since the ME was sold. Additionally time, Daylight Saving Time and timezone information can be utilised by MEs as desired.

2  Referencesp. 5

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.
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols - Stage 3".
TS 23.038: "Alphabets and Languages".

3  Definitions and abbreviationsp. 5

In addition to the following definitions, abbreviations used in the present document are listed in TR 21.905.
The feature Network Identity and Timezone as described in the present document.
Universal Character Set 2
Universal Time
Local Time Zone, the offset from UT applying in that locality, including any adjustments for summer time, etc.
Daylight Saving Time. Adjustment for summer time.

4  Descriptionp. 6

The feature Network Identities and Timezone shall make it possible for a serving PLMN to transfer its current identity, universal time, DST and LTZ to MSs, and for the MS to store and use this information. Each one of these elements is optional. The feature significantly enhances roaming as itenables the accurate indication of network identities that are either newer than the ME or have changed their name since the ME was manufactured or sold. Additionally time and timezone information can be utilised by MEs as desired.
When using the default character set (see TS 23.038), the serving PLMN shall make both a "short" and a "long" name available to the MS. As an alternative or, in addition, to the default character set, the serving PLMN can make a name available in UCS2. The MS shall be free to choose one of these names depending upon its own characteristics and/or limitations, such as those of its display.
The Network Operator may change the network identity at any time. However the change of network identity need not force immediate transfer of information to the MS.
As a network option, it shall be possible to send universal time (UT) by the network. Time information shall include: Year, Month, Day, Hour, Minute, Second, Timezone and DST. The expected accuracy of the time information is in the order of minutes.
The serving PLMN shall make Local Time Zone (LTZ) available to the MS as an offset from Universal Time in units of 15 minutes.
When the LTZ is compensated for DST (summertime), the serving PLMN shall provide a DST parameter to indicate this. The adjustment for DST can be +1h or +2h.
For PLMNs which cover more than one timezone, it is assumed that the Network Operator will arrange for boundaries between subsets of the PLMN service area to be approximately aligned with timezone boundaries. When an MS changes Local Time Zone the PLMN is not required to immediately transfer new time zone information. Similarly the PLMN will transfer the LTZ changes arising from summer/winter adjustments when convenient to the network operator.
The MS will implement the new time zone information at an appropriate time following receipt.
The information passed to MSs supporting the NITZ feature is controlled by the serving PLMN Operator through administrative interaction. The interface necessary to support this administrative interaction is outside the scope of the present document.

5  Applicabilityp. 6

Network Identity and Timezone is both an optional network feature and an optional MS feature.
The NITZ feature is not intended to replace the existing method of PLMN Indication, nor is it intended to discharge the administration and maintenance of the associated MoU Permanent Document, SE13.

6  Normal procedurep. 7

6.1  Transfer of NITZ informationp. 7

Network name, time, DST and timezone information can be transferred from the serving PLMN to the MS:
  1. Upon registering on the network.
  2. When the MS geographically relocates to a different Local Time Zone.
  3. When the network changes its Local Time Zone, e.g. between summer and winter time.
  4. When the network changes its identity.
  5. At any time during a signalling connection with mobile station.
Transfer of relevant information shall not unduly consume scarce network resources.

6.2  Use of NITZ informationp. 7

Relevant information shall be presented to the MS user at the earliest opportunity.
It is expected that the MS will display the most up to date information transferred to it.
Switching off the MS should not cause the updated name of the network(s) to be deleted.
Removal of the SIM/USIM should not cause the updated name of the network(s) to be deleted.
However, the number of different network identities retained in the ME is a manufacturer issue.
Usage of time information in MS is a ME manufacturer issue. For example, time information can be utilised to time stamp transactions for logging purposes.

$  Change historyp. 8

Up   Top