9.4.10 NITZ / MM/ Time zone, Time and DST Handling

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

9.4.10.1 Definition

To check that the UE correctly handles time zone, time and DST.

9.4.10.2 Conformance requirement

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 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 timezone information can be utilised by MEs as desired.

When using the default character set (see 3GPP TS 23.038 [3]), 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.

NOTE: Guidance is sought, particularly from non-European operators, as to whether long and short name is required in UCS2 format.

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.

NOTE: Universal time indicates the time at which this information element (see 3GPP TS 24.008 [2]) may have been sent by the network. Thus it can be assumed that the accuracy of the time information when it arrives at the MS is usually within a couple 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.

The TP‑Service‑Centre‑Time‑Stamp field is given in semi‑octet representation, and represents the local time in the following way:

	Year:	Month:	Day:	Hour:	Minute:	Second:	Time Zone
Digits: (Semi‑octets)	2	2	2	2	2	2	2

The Time Zone indicates the difference, expressed in quarters of an hour, between the local time and GMT. In the first of the two semi‑octets, the first bit (bit 3 of the seventh octet of the TP‑Service‑Centre‑Time‑Stamp field) represents the algebraic sign of this difference (0: positive, 1: negative).

The Service‑Centre‑Time‑Stamp, and any other times coded in this format that are defined in the present document, represent the time local to the sending entity.

If the MS has knowledge of the local time zone, then any time received (e.g. Service‑Centre‑Time‑Stamp) at the MS may be displayed in the local time rather than the time local to the sending entity. Messages shall be stored as received without change to any time contained therein.

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, for example in the UK the winter setting is 00000000 and the summer setting is 01000000.

If the MS receives a non‑integer value in the SCTS, it shall assume that the digit is set to 0 but shall store the entire field exactly as received.

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 MM information procedure consists only of the MM INFORMATION message sent from the network to the mobile station. During an RR connection, the network shall send none, one, or more MM INFORMATION messages to the mobile station. If more than one MM INFORMATION message is sent, the messages need not have the same content.

NOTE: 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.

References

3GPP TS 22.042 sub clause 4

3GPP TS 23.040 sub clause 9.2.3.11

3GPP TS 24.008 sub clause 9.4.15a.3, 9.4.15a.4, 4.3.6

9.4.10.3 Test purpose

To verify that a UE 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.

9.4.10.4 Method of test

Related ICS/IXIT statements

Support of FDD Yes/No.

– Support of CS bearer service Yes/No

– Support of Switch on off button Yes/No.

– Support of NITZ DST Yes/No.

– Support of NITZ Universal Time for PLMN Yes/No.

– Support of NITZ Local Time Zone for PLMN Yes/No.

Initial conditions

System Simulator:

One cell (cell A) operating in network operation mode II

IMSI attach/detach allowed in the cell

User Equipment:

– The UE is "idle updated" on cell A.

– The UE is switched off with a valid USIM inserted.

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 UE. The operator verifies then the supported parameters and/or the time and date stored in the UE.

The UE 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 UE.

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).

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			Set the cell type of cell A to the "Serving cell". The UE is powered up or switched on and initiates an attach (see PICS).
2				If PS mode: a GMM attach procedure should be performed
3	->		LOCATION UPDATE REQUEST
4	<-		AUTHENTICATION REQUEST
5	->		AUTHENTICATION RESPONSE
6	SS			The SS starts integrity protection.
7	<-		MM INFORMATION	Universal Time IE is included: “< Current Year >/12/3 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
8	<-		LOCATION UPDATE ACCEPT
9	SS			The SS releases the RRC connection
10	SS			Operator Action: The use of the supported Fields is checked: Universal Time: Year: < Current Year > Month: December Day: 31st Hour: 6 Hours Minute: 25 Minutes Timezone: GMT+0 Local Time Zone: Timezone: GMT+0 DST: Daylight Saving Time not in use (i.e. winter time) (see note)
11	UE			The UE is switched off or power is removed (see PICS).
12	->		IMSI DETACH	Message not sent if power is removed. Detach type = IMSI detach
13	SS			The UE is powered up or switched on and initiates an attach (see PICS).
14	UE			If PS mode: a GMM attach procedure should be performed
15	->		LOCATION UPDATE REQUEST
16	<-		AUTHENTICATION REQUEST
17	->		AUTHENTICATION RESPONSE
18	SS			The SS starts integrity protection.
19	<-		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
20	<-		LOCATION UPDATE ACCEPT
21	SS			The SS releases the RRC connection
22	UE			Operator Action: The use of the supported Fields is checked: Universal Time: Year: < Current Year > Month: December Day: 31st Hour: 7 Hours Minute: 25 Minutes Timezone: GMT+1 Local Time Zone: Not sent DST: Daylight Saving Time in use (i.e. summer time) (see note)
23	UE			The UE is switched off or power is removed (see PICS).
24	->		IMSI DETACH	Message not sent if power is removed. Detach type = IMSI detach
25	SS			The UE is powered up or switched on and initiates an attach (see PICS).
26	UE			If PS mode: a GMM attach procedure should be performed
27	->		LOCATION UPDATE REQUEST
28	<-		AUTHENTICATION REQUEST
29	->		AUTHENTICATION RESPONSE
30	SS			The SS starts integrity protection.
31	<-		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
32	<-		LOCATION UPDATE ACCEPT
33	SS			The SS releases the RRC connection
34	SS			Operator Action: The use of the supported Fields is checked: Universal Time: Year: < Current Year > Month: December Day: 31st Hour: 2 Hours Minute: 25 Minutes Timezone: GMT-4 Local Time Zone: Not sent DST: Daylight Saving Time in use (i.e. summer time)(see note)
35	UE			The UE is switched off or power is removed (see PICS).
36	->		IMSI DETACH	Message not sent if power is removed. Detach type = IMSI detach
37	SS			The UE is powered up or switched on and initiates an attach (see PICS).
38	UE			If PS mode: a GMM attach procedure should be performed
39	->		LOCATION UPDATE REQUEST
40	<-		AUTHENTICATION REQUEST
41	->		AUTHENTICATION RESPONSE
42	SS			The SS starts integrity protection.
43	<-		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
44	<-		LOCATION UPDATE ACCEPT
45	SS			The SS releases the RRC connection
46	UE			Operator Action: The use of the supported Fields is checked: Year: < Current Year > Month: December Day: 31st Hour: 23 Hours Minute: 25 Minutes Timezone: GMT-7 Local Time Zone: Not sent DST: Daylight Saving Time in use (i.e. summer time)(see note)
47	UE			The UE is switched off or power is removed (see PICS).
48	->		IMSI DETACH	Message not sent if power is removed. Detach type = IMSI detach
49	SS			The UE is powered up or switched on and initiates an attach (see PICS).
50	UE			If PS mode: a GMM attach procedure should be performed
51	->		LOCATION UPDATE REQUEST
52	<-		AUTHENTICATION REQUEST
53	->		AUTHENTICATION RESPONSE
54	SS			The SS starts integrity protection.
55	<-		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
56	<-		LOCATION UPDATE ACCEPT
57	SS			The SS releases the RRC connection
58	SS			Operator Action: The use of the supported Fields is checked: Universal Time: Year: < Current Year > Month: December Day: 31st Hour: 23 Hours Minute: 25 Minutes Timezone: GMT-7 Local Time Zone: No sent DST: Daylight Saving Time not in use (i.e. winter time) (see note)
59	UE			The UE is switched off or power is removed (see PICS).
60	->		IMSI DETACH	Message not sent if power is removed. Detach type = IMSI detach
Note: In step 10, 22, 34, 46 and 58 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. In Steps 10, 22, 34, 46, 58 Local Time Zone and DST are to be checked only if the UE supports pc_LocalTimeZone resp. pc_DaylightSavingTime.

Specific message contents:

MM Information, step 7:

Information element	Value/remark
Universal Time IE	47
Year	< Current Year >
Month	50 – May
Day	51 – 15th
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, step 19:

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, step 31:

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, step 43:

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, step 55:

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)

9.4.10.5 Test requirements

In steps 10, 22, 34, 46 and 58 the UE populates the supported fields with the correct received values.