26.7.6 Network Identity and Time zone (NITZ)
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
26.7.6.1 NITZ and CS location update procedures
26.7.6.1.1 NITZ / CS location update / Time zone, Time and DST Handling
26.7.6.1.1.1 Conformance requirement
The feature Network Identities and Time zone 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 it enables 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 time zone information can be utilised by MEs as desired.
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.
The Time Zone code enables the receiver to calculate the equivalent time in GMT from the other semi‑octets in the Service‑Centre‑Time‑Stamp, or indicate the time zone (GMT, GMT+1H etc.), or perform other similar calculations as required by the implementation. The value contained in the Time Zone field must take into account daylight saving time, such that when the sending entity changes from regular (winter) time to daylight saving (summer) time, there is a change to the value in the Time Zone field.
The mobile station should assume that this time zone applies to the Location Area of the cell to which the Channel Request message was sent.
If the local time zone has been adjusted for Daylight Saving Time, the network shall indicate this by including the IE Network Daylight Saving Time.
The network may be able to select particular instants where it can send the MM INFORMATION message without adding delay to, or interrupting, any CM layer transaction, e.g. immediately after the AUTHENTICATION REQUEST message.
Reference(s):
3GPP TS 02.42 / 3GPP TS 22.042 subclause 4
3GPP TS 03.40 / 3GPP TS 23.040 subclause 9.2.3.11
3GPP TS 04.08 / 3GPP TS 24.008 subclause 9.4.19.4, 4.3.6
26.7.6.1.1.2 Test purpose
To verify that a MS supporting any of the NITZ Time related feature (Local Time Zone, Universal Time and DST IE and thus MM Information) is able to handle them properly.
26.7.6.1.1.3 Method of test
Initial conditions
System Simulator:
One cell (cell A)
IMSI attach/detach allowed in the cell
Mobile Station:
The MS has a valid IMSI. MS is powered off.
Specific PICS statements:
– On/Off switch (TSPC_Feat_OnOff)
– Use of NITZ DST (TSPC_NITZ_DST)
– Use of NITZ Universal Time for PLMN (TSPC_NITZ_Universal_Time)
– Use of NITZ Local Time Zone for PLMN (TSPC_NITZ_Time_Zone)
PIXIT statements:
–
Test procedure
During the Location Update procedure on Cell A, SS sends its local time and date (UK, Winter Time) using the MM INFORMATION Message to the MS. The operator verifies then the supported parameters and/or the time and date stored in the MS.
The MS is powered off and then powered on. During the location update the SS sets local time and date (UK, Summer Time). The operator verifies then the supported parameters and/or the time and date stored in the MS.
This is then repeated for the follow scenarios: US East coast summer time (GMT–5+1), US West coast summer time (GMT–8+1), US Mountain time (no summer adjustment) (GMT–7).
Maximum duration of test
10 minutes.
Expected sequence
Step |
Direction |
Message |
Comments |
---|---|---|---|
1 |
MS |
The MS is powered up or switched on (see PICS) and initiates a location update. |
|
2 |
MS -> SS |
LOCATION UPDATE REQUEST |
|
3 |
SS -> MS |
AUTHENTICATION REQUEST |
|
4 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
5 |
SS ->MS |
MM INFORMATION |
Universal Time IE is included: “< Current Year >/ 12/31 06:25:00” for UT “0 hour” for Timezone Local Time Zone IE included: “0 hour” for Timezone No DST IE included See specific message content |
6 |
SS -> MS |
LOCATION UPDATE ACCEPT |
|
7 |
MS |
Operator Action: The use of the supported Fields is checked: Universal Time: Year: < Current Year > Local Time Zone: Timezone: GMT+0 Daylight Saving Time not in use (i.e. winter time) |
|
8 |
MS |
The MS is switched off or power is removed (see PICS). |
|
9 |
MS -> SS |
IMSI DETACH |
Message not sent if power is removed. Detach type = IMSI detach |
10 |
MS |
The MS is powered up or switched on (see PICS) and initiates a location update. |
|
11 |
MS -> SS |
LOCATION UPDATE REQUEST |
|
12 |
SS -> MS |
AUTHENTICATION REQUEST |
|
13 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
14 |
SS ->MS |
MM INFORMATION |
Universal Time IE is included: “< Current Year >/ 12/31 06:25:00” for UT “1 hour” for Timezone (including DST) DST = +1 hour See specific message content |
15 |
SS -> MS |
LOCATION UPDATE ACCEPT |
|
16 |
MS |
Operator Action: The use of the supported Fields is checked: Universal Time: Not sent Daylight Saving Time in use (i.e. summer time) |
|
17 |
MS |
The MS is switched off or power is removed (see PICS). |
|
18 |
MS -> SS |
IMSI DETACH |
Message not sent if power is removed. Detach type = IMSI detach |
19 |
MS |
The MS is powered up or switched on (see PICS) and initiates a location update. |
|
20 |
MS -> SS |
LOCATION UPDATE REQUEST |
|
21 |
SS -> MS |
AUTHENTICATION REQUEST |
|
22 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
23 |
SS ->MS |
MM INFORMATION |
UniversalTime IE is included: “< Current Year >/ 12/31 06:25:00” for UT “-4 hours” for Timezone (including DST) DST = +1 hour See specific message content |
24 |
SS -> MS |
LOCATION UPDATE ACCEPT |
|
25 |
MS |
Operator Action: The use of the supported Fields is checked: Year: < Current Year > Local Time Zone: Not sent Daylight Saving Time in use (i.e. summer time) |
|
26 |
MS |
The MS is switched off or power is removed (see PICS). |
|
27 |
MS -> SS |
IMSI DETACH |
Message not sent if power is removed. Detach type = IMSI detach |
28 |
MS |
The MS is powered up or switched on (see PICS) and initiates a location update. |
|
29 |
MS -> SS |
LOCATION UPDATE REQUEST |
|
30 |
SS -> MS |
AUTHENTICATION REQUEST |
|
31 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
32 |
SS ->MS |
MM INFORMATION |
Universal Time IE is included: “< Current Year >/ 12/31 06:25:00” for UT “-7 hours” for Timezone (including DST) DST = +1 hour See specific message content |
33 |
SS -> MS |
LOCATION UPDATE ACCEPT |
|
34 |
MS |
Operator Action: The use of the supported Fields is checked: Not sent Daylight Saving Time in use (i.e. summer time) |
|
35 |
MS |
The MS is switched off or power is removed (see PICS). |
|
36 |
MS -> SS |
IMSI DETACH |
Message not sent if power is removed. Detach type = IMSI detach |
37 |
MS |
The MS is powered up or switched on (see PICS) and initiates a location update. |
|
38 |
MS -> SS |
LOCATION UPDATE REQUEST |
|
39 |
SS -> MS |
AUTHENTICATION REQUEST |
|
40 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
41 |
SS ->MS |
MM INFORMATION |
Universal Time IE is included: “< Current Year >/ 12/31 06:25:00” for UT “-7 hour” for Timezone No DST IE included See specific message content |
42 |
SS -> MS |
LOCATION UPDATE ACCEPT |
|
43 |
MS |
Operator Action: The use of the supported Fields is checked: Year: < Current Year > Day: 31st Local Time Zone: No sent Daylight Saving Time not in use (i.e. winter time) |
|
44 |
MS |
The MS is switched off or power is removed (see PICS). |
|
45 |
MS -> SS |
IMSI DETACH |
Message not sent if power is removed. Detach type = IMSI detach |
Note: In steps 7, 16, 25, 34 and 43 the “minute” is not so relevant and can be higher than “25” depending on operator’s action time.
Current Year is derived by the SS.
The check of Timezone and DST is done implicitly by checking the time only in case MS does not support the display of these two fields.
Specific message contents
MM Information on step 5:
Information element |
Value/remark |
Universal Time IE |
47 |
Year |
< Current Year > |
Month |
21 – December |
Day |
13 – 31st |
Hour |
60 – 6 hours |
Minute |
52 – 25 Minutes |
Second |
00 – 0 second |
Time Zone |
00 – GMT+0 (0*15 minutes + 0*15 minutes DST) |
Local Time Zone IE |
46 |
Time Zone |
00 – GMT+0 (0*15 minutes + 0*15 minutes DST) |
MM Information on step 14:
Information element |
Value/remark |
UniversalTime IE |
47 |
Year |
< Current Year > |
Month |
21 – December |
Day |
13 – 31st |
Hour |
60 – 6 hours |
Minute |
52 – 25 Minutes |
Second |
00 – 0 second |
Time Zone |
40 – GMT+0+1 (0*15 minutes + (1*4)*15 minutes DST) |
Daylight Saving Time IE |
49 |
Length of DST Content |
1 |
Value |
1 – + 1 hour (summer time) |
MM Information on step 23:
Information element |
Value/remark |
Universal Time IE |
47 |
Year |
< Current Year > |
Month |
21 – December |
Day |
13 – 31st |
Hour |
60 – 6 hours |
Minute |
52 – 25 Minutes |
Second |
00 – 0 second |
Time Zone |
69 – GMT-5+1 ((-5*4)*15 minutes + (1*4)*15 minutes DST) |
Daylight Saving Time IE |
49 |
Length of DST Content |
1 |
Value |
1 – + 1 hour (summer time) |
MM Information on step 32:
Information element |
Value/remark |
UniversalTime IE |
47 |
Year |
< Current Year > |
Month |
21 – December |
Day |
13 – 31st |
Hour |
60 – 6 hours |
Minute |
52 – 25 Minutes |
Second |
00 – 0 second |
Time Zone |
8A – GMT-8+1 ((-8*4)*15 minutes + (1*4)*15 minutes DST) |
Daylight Saving Time IE |
49 |
Length of DST Content |
1 |
Value |
1 – + 1 hour (summer time) |
MM Information on step 41:
Information element |
Value/remark |
Universal Time IE |
47 |
Year |
< Current Year > |
Month |
21 – December |
Day |
13 – 31st |
Hour |
60 – 6 hours |
Minute |
52 – 25 Minutes |
Second |
00 – 0 second |
Time Zone |
8A – GMT-7 ((-7*4)*15 minutes) |