22.5.21 NB-IoT/APN rate control for MO exception data
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
22.5.21.1 Test Purpose (TP)
(1)
with { UE supports APN rate control and indicates support of additional APN rate control for exception data reporting }
ensure that {
when { UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with n additional APN rate control parameters for exception data container in the protocol configuration options IE or extended protocol configuration options IE}
then { the UE stores the additional APN rate control parameters for exception data value and use the stored additional APN rate control parameters for exception data value as the maximum allowed limit of uplink exception data related to the APN indicated }
}
22.5.21.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.301, clauses 6.3.9, 6.4.1.3, 6.5.1.2.
[TS 24.301, clause 6.3.9]
If the UE supports APN rate control, the UE shall provide the support indication of APN rate control and additional APN rate control for exception data reporting to the network. If the UE indicates support of additional APN rate control for exception data reporting, the network may provide the APN rate control parameters for exception data to the UE. If the UE does not indicate support of additional APN rate control for exception data reporting, the network shall not provide the APN rate control parameters for exception data to the UE.
If an allowed indication of additional exception reports is provided with the APN rate control parameters and:
– the additional APN rate control parameters for exception data is provided and the limit for additional rate for exception data reporting is not reached; or
– the additional APN rate control parameters for exception data is not provided,
the UE is allowed to send uplink exception reports even if the limit for the APN rate control has been reached.
[TS 24.301, clause 6.4.1.3]
If the UE receives an additional APN rate control parameters for exception data container in the protocol configuration options IE or extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the additional APN rate control parameters for exception data value and use the stored additional APN rate control parameters for exception data value as the maximum allowed limit of uplink exception data related to the APN indicated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message in accordance with 3GPP TS 23.401 [10]. If the UE has a previously stored additional APN rate control parameters for exception data value for this APN, the UE shall replace the stored additional APN rate control parameters for exception data value for this APN with the received additional APN rate control parameters for exception data value.
[TS 24.301, clause 6.5.1.2]If the UE supports APN rate control, the UE shall include an APN rate control support indicator and an additional APN rate control for exception data support indicator in the protocol configuration options IE or extended protocol configuration options IE
22.5.21.3 Test description
22.5.21.3.1 Pre-test conditions
System Simulator:
– Ncell 1 is defined in clause 8.1.4.2 in TS 36.508[18].
– System information combination 1 is defined in TS 36.508[18] clause 8.1.4.3.1.1 is used in NB-IoT cells;
UE:
The UE is equipped with a USIM containing default values (as per TS 36.508) except for those shown in Table 22.5.21.3.1-1.
Table 22.5.21.3.1–1: USIM Configuration
USIM field |
Value |
EFACC |
Type “A” as defined in TS 34.108 clause 8.3.2.15 |
EFNASCONFIG |
“Exception Data Reporting Allowed is set to 01” |
Preamble:
– The UE is in state Switched OFF (state 1-NB) according to TS 36.508 [18].
22.5.21.3.2 Test procedure sequence
Table 22.5.21.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1-12 |
Steps 1A-12 of the generic procedure for UE registration specified in TS 36.508 subclause 8.1.5.2.3 are performed. |
– |
– |
– |
– |
– |
EXCEPTION: Steps 13a1 to 13c1 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place depending on whether the UE is configured for S1_U_DataTransfer and if not then if it is configured to do Attach Without PDN or not. |
– |
– |
– |
– |
13a1 |
IF S1_U_DataTransfer THEN the SS transmits a RRCConnectionReconfiguration-NB message to establish the default bearer with condition DRB(1) according to [8.1.8]. This message includes the ATTACH ACCEPT message and the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in the ATTACH ACCEPT. NOTE: Settings in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST to check additional APN rate control – Additional APN control set for max 1 message per minute; – MTU parameters are not provided – PLMN Rate control not provided SS starts 1 min APN Rate Control Timer |
<– |
RRC: RRCConnectionReconfiguration-NBNAS: ATTACH ACCEPT NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST |
– |
– |
13a2 |
The UE transmits an RRCConnectionReconfigurationComplete-NB message to confirm the establishment of default bearer, |
–> |
RRC: RRCConnectionReconfigurationComplete-NB |
– |
– |
13b1 |
ELSE IF px_DoAttachWithoutPDN THEN SS transmits an ATTACH ACCEPT message and an ESM DUMMY MESSAGE is piggybacked in the ATTACH ACCEPT. |
<– |
RRC: DLInformationTransfer-NB NAS: ATTACH ACCEPT NAS: ESM DUMMY MESSAGE |
– |
– |
13c1 |
ELSE SS transmits an ATTACH ACCEPT message and an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in the ATTACH ACCEPT If PDN type "IP" was included in the PDN CONNECTIVITY REQUEST step 4b1 then the network shall include the PDN type and the PDN address information within the PDN address IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent to the UE NOTE: Settings in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST to check additional APN rate control – Additional APN control set for max 1 message per minute – APN rate control set for max 4 messages per minute – MTU parameters are not provided – PLMN Rate control not provided SS starts 1 min APN Rate Control Timer |
<– |
RRC: DLInformationTransfer-NB NAS: ATTACH ACCEPT NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST |
– |
– |
14a1-14b1 |
Steps 14a1-14b1 of the generic procedure for UE registration specified in TS 36.508 subclause 8.1.5.2.3 are performed. NOTE: For successful completion of IP address allocation, UE may send a Router Solicitation message encapsulated in ESM Data transport message |
– |
– |
||
– |
EXCEPTION: Steps15a1-15a3 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that takes place if the UE did not establish a PDN connection in step 1-14b1. |
– |
– |
– |
– |
– |
Cause the UE to request PDN connectivity. (see Note 1) |
– |
– |
– |
– |
15a1 |
The UE transmits a PDN CONNECTIVITY REQUEST message. |
–> |
RRC: ULInformationTransfer-NB NAS: PDN CONNECTIVITY REQUEST |
– |
– |
15a2 |
The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. NOTE: Settings in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST to check APN rate control – Additional APN control set for max 1 message per minute – APN rate control set for max 4 messages per minute – MTU parameters are not provided – PLMN Rate control not provided SS starts 1 min APN Rate Control Timer |
<– |
RRC: DLInformationTransfer-NB NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST |
– |
– |
– |
EXCEPTION: In parallel to the event described in step 15a3 below the generic procedure for IP address allocation specified in TS 36.508 subclause 8.1.5A.1 takes place performing IP address allocation if requested by the UE. NOTE: For successful completion of IP address allocation, UE may send a Router Solicitation message encapsulated in ESM Data transport message |
– |
– |
– |
– |
15a3 |
The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message. |
–> |
RRC: ULInformationTransfer-NB NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT |
– |
– |
16 |
The SS transmits an RRCConnectionRelease-NB message to release RRC connection and move to RRC_IDLE. |
<– |
RRC: RRCConnectionRelease-NB |
– |
– |
16A |
Wait until APN rate control timer expires. |
– |
– |
– |
– |
– |
Trigger the UE to initiate MO Exception Data. |
– |
– |
– |
– |
17 |
Check: Does the UE transmit an RRCConnectionRequest-NB message on Ncell 1 with establishmentCause-r13 set to mo-ExceptionData? |
–> |
RRCConnectionRequest-NB |
– |
– |
18 |
SS transmits an RRCConnectionSetup-NB message. |
<– |
RRC: RRCConnectionSetup-NB |
– |
– |
19 |
SS starts timer 1 min APN Rate control (see Note 2) |
– |
– |
– |
– |
20 |
Check: Does the UE transmit an RRCConnectionSetupComplete-NB message and a CONTROL PLANE SERVICE REQUEST message containing user data encapsulated in an ESM DATA TRANSPORT message included in the ESM message container IE? |
–> |
RRC: RRCConnectionSetupComplete-NB NAS: CONTROL PLANE SERVICE REQUEST NAS: ESM DATA TRANSPORT |
1 |
P |
21 |
The SS transmits a SERVICE ACCEPT message. |
<– |
RRC: DLInformationTransfer NAS: SERVICE ACCEPT |
– |
– |
– |
EXCEPTION: Steps 21A – 21B are repeated 4 times. |
– |
– |
– |
– |
21A |
Trigger the UE to initiate MO Exception Data (see Note 3) |
– |
– |
– |
– |
21B |
Check: Does the UE send an ESM DATA TRANSPORT message. |
–> |
RRC: ULInformationTransfer-NB TC: ESM DATA TRANSPORT |
1 |
P |
21C |
Trigger the UE to initiate MO Exception Data. |
– |
– |
||
21D |
Check: Does the UE send an ESM DATA TRANSPORT message. |
–> |
RRC: ULInformationTransfer-NB TC: ESM DATA TRANSPORT |
1 |
F |
22 |
Wait until timer 1 min additional APN Rate control expires. |
– |
– |
– |
– |
22A |
Trigger the UE to initiate MO Exception Data. |
– |
– |
– |
– |
23 |
SS starts timer 1 min additional APN Rate control |
– |
– |
– |
– |
24 |
Check: Does the UE send an ESM DATA TRANSPORT message with in 1 min from step 23? |
–> |
RRC: ULInformationTransfer-NB TC: ESM DATA TRANSPORT |
1 |
P |
25 |
Void |
||||
26 |
The SS transmits an RRCConnectionRelease-NB message |
<– |
RRCConnectionRelease-NB |
– |
– |
Note 1: The request of connectivity to a PDN may be performed by MMI or AT command. Note 2: Steps 19 to 22 shall happen within one minute. Note 3: After the last attempt, maximum allowed limit of uplink exception data is reached. |
22.5.21.3.3 Specific message contents
Table 22.5.21.3.3-1: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Step 13a1, Step 13c1, step15a2, Table 22.5.21.3.2-1)
Derivation path: TS 36.508 [18], Table 4.7.3-6. |
||||
Information Element |
Value/Remark |
Comment |
Condition |
|
Protocol discriminator |
ESM |
|||
EPS bearer identity |
An arbitrarily selected value between ‘0101’B and ‘1111’B. |
|||
Procedure transaction identity |
The same value as the value set in the latest PDN CONNECTIVITY REQUEST message sent prior to this message. |
|||
Activate default EPS bearer context request message identity |
‘1100 0001’B |
Activate default EPS bearer context request |
||
EPS bearer identity |
The same value as the value set in the latest ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent prior to this message |
|||
Protocol configuration options |
Not Present |
|||
Extended protocol configuration options |
||||
Container ID n+X+1 |
‘0016’H |
APN rate control support parameters |
pc_APN_RateControl |
|
Length of container ID n+X+1 contents |
4 |
|||
Container ID n+X+1 contents |
The container identifier contents field contains parameters for APN rate control functionality |
|||
Octet 1 AER+Uplink time unit |
‘1001’B |
– Additional exception reports at maximum rate reached are allowed – minute (interval) |
||
Octets 2-4 |
‘00000000 00000000 00000100’B |
Maximum uplink rate (octet 2 to octet 4) is a binary coded representation of the maximum number of messages the UE is restricted to send per time unit. The time unit is indicated in the uplink time unit. If the uplink time unit is set to "unrestricted", the maximum uplink data volume the UE can send is not restricted. |
||
Container ID n+X+2 |
‘0019’H |
Additional APN rate control for exception data parameters |
pc_Additional_APN_RateControl |
|
Length of container ID n+X+2 contents |
3 |
|||
Container ID n+X+2 contents |
The container identifier contents field contains parameters indicate the additional APN rate control parameters for exception data functionality |
|||
Octet 1 Uplink time unit |
‘001’B |
– minute (interval) |
||
Octets 2-3 |
‘00000000 00000001’B |
– Max 1 message per minute |