3GPP 24.501 v20.0.0 — the document's own text
9.11.3.101 S-NSSAI time validity information
Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).
The purpose of the S-NSSAI time validity information information element is to provide S-NSSAI time validity information of one or more S-NSSAIs to the UE.
The S-NSSAI time validity information information element is coded as shown in figures 9.11.3.101.1 and 9.11.3.101.2 and table 9.11.3.101.1.
The S-NSSAI time validity information information element can contain per-S-NSSAI time validity information for maximum 16 S-NSSAIs.
The S-NSSAI time validity information information is a type 4 information element with a minimum length of 23 octets and a maximum length of 257 octets.
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| S-NSSAI time validity information information IEI | octet 1 | |||||||
| Length of S-NSSAI time validity information contents | octet 2 | |||||||
| Per-S-NSSAI time validity information for S-NSSAI 1 | octet 3octet a | |||||||
| Per-S-NSSAI time validity information for S-NSSAI 2 | octet a+1*octet b* | |||||||
| … | octet b+1*octet c* | |||||||
| Per-S-NSSAI time validity information for S-NSSAI n | octet c+1*octet d* |
Figure 9.11.3.101.1: S-NSSAI time validity information information element
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Length of Per-S-NSSAI time validity information for S-NSSAI | octet 3 | |||||||
| S-NSSAI | octet 4octet e | |||||||
| Per-S-NSSAI time validity information for the S-NSSAI | octet e+1octet a |
Figure 9.11.3.101.2: Per-S-NSSAI time validity information for S-NSSAI 1
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Length of Per-S-NSSAI time validity information for the S-NSSAI | octet e+1 | |||||||
| Time window 1 | octet e+2octet f | |||||||
| Time window 2 | octet f+1*octet g* | |||||||
| … | octet g+1*octet h* | |||||||
| Time window m | octet h+1*octet i* |
Figure 9.11.3.101.3: Per-S-NSSAI time validity information for the S-NSSAI
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Length of Time window 1 | octet e+2 | |||||||
| Start time | octet e+3octet e+10 | |||||||
| Stop time | octet e+11octet e+18 | |||||||
| 0Spare | 0Spare | 0Spare | 0Spare | Recurrence pattern | octet e+19* | |||
| Recurrence end time | octet e+20*octet e+27* |
Figure 9.11.3.101.4: Time window 1
Table 9.11.3.101.1: S-NSSAI time validity information information element
| S-NSSAI (octet 6 to octet e)S-NSSAI value is coded as the length and value part of S-NSSAI information element as specified in clause 9.11.2.8 starting with the second octet. | |||||
|---|---|---|---|---|---|
| Start time (octet e+3 to octet e+10) | |||||
| The field indicates the time when the network slice identified by the S-NSSAI becomes available (for the first time if octet e+20 is included) and is represented by the number of seconds since 00:00:00 on 1 January 1970 UTC and is encoded as the 64-bit NTP timestamp format defined in IETF RFC 5905 [36A], where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. | |||||
| Stop time (octet e+11 to octet e+18) | |||||
| The field indicates the time when the network slice identified by the S-NSSAI becomes unavailable (for the first time if octet e+20 is included) and is represented by the number of seconds since 00:00:00 on 1 January 1970 UTC and is encoded as the 64-bit NTP timestamp format defined in IETF RFC 5905 [36A], where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. | |||||
| Recurrence pattern (bit 1 to bit 4 of octet e+19) | |||||
| Bits | |||||
| 4 | 3 | 2 | 1 | ||
| 0 | 0 | 0 | 0 | Everyday | |
| 0 | 0 | 0 | 1 | Every weekday | |
| 0 | 0 | 1 | 0 | Every week | |
| 0 | 0 | 1 | 1 | Every 2 weeks | |
| 0 | 1 | 0 | 0 | Every month (absolute) | |
| 0 | 1 | 0 | 1 | Every month (relative) | |
| 0 | 1 | 1 | 0 | Every quarter (absolute) | |
| 0 | 1 | 1 | 1 | Every quarter (relative) | |
| 1 | 0 | 0 | 0 | Every 6 months (absolute) | |
| 1 | 0 | 0 | 1 | Every 6 months (relative) | |
| All other values are reserved.The recurrence pattern indicates how often the time window is repeated. For example, if the time window starts at 13:00 on Wednesday January 1st 2020 and stops at 13:30 on Wednesday January 1st 2020 and the recurrent pattern is set to: - "Everyday", the time window repeats everyday from 13:00 to 13:30; - "Every week", the time window repeats every Wednesday from 13:00 to 13:30; - "Every month (absolute)", the time window repeats every 1st day of the month from 13:00 to 13:30; and - "Every month (relative)", the time window repeats every month on the first Wednesday from 13:00 to 13:30. | |||||
| Recurrence end time (octet e+20 to octet e+27) | |||||
| The field indicates the time when the repetition of the time window ends. If the field is not included and octet e+19 is included in the IE, the time window is repeated indefinitely.The field is represented by the number of seconds since 00:00:00 on 1 January 1970 UTC and is encoded as the 64-bit NTP timestamp format defined in IETF RFC 5905 [36A], where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. | |||||