B.2 Support of rate control of user data
29.0613GPPInterworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)Release 17TS
B.2.0 General
The rate of user data sent to and from a UE (e.g. a UE using CIoT EPS Optimizations) can be controlled in two different ways:
– Serving PLMN rate control
– APN rate control
Serving PLMN rate control is further described in 3GPP TS 23.401 [77].
The APN rate control parameters are a part of the configuration data stored in the GGSN/PGW and is configured on per APN basis.
APN rate control allows HPLMN operators on per APN and user to control the amount of user data sent DL and UL.
This is done with help of policing user data on a maximum number of user data packets per time unit both DL and UL. APN rate control DL policing is done in the GGSN/PGW or the SCEF and the APN rate control policing UL is done in the UE. The GGSN/PGW or SCEF can also do APN rate control UL policing.
For further information on APN rate control UL in the UE, see 3GPP TS 24.301 [84].
For further information on APN rate control in the SCEF, see 3GPP TS 29.128 [110].
NOTE: Existing AMBR mechanisms are not suitable for such a service since, for radio efficiency and UE battery life reasons, an AMBR of e.g. > 100kbit/s is desirable and such an AMBR translates to a potentially large daily data volume.
B.2.1 APN Rate Control in the PGW
To enable APN rate control it shall be configured in the PGW per APN.
The APN rate control parameters, if configured, shall consist of:
– the maximum number of DL user data packets per time unit,
– the maximum number of UL user data packets per time unit,
– an indication whether the UE is allowed to send additional exception reports when the limit for the UL APN rate control has been reached , and
– if UE supports it, the maximum number of additional UL exception reports per time unit.
Possible time units shall be, minute, hour, day or week.
If the UE does not indicate APN rate control support, the GGSN/PGW may refrain from providing APN rate control information to the UE.
NOTE 1: The UE indicates support for APN rate control with help of an indicator in the Protocol Configuration Options IE (PCO IE) or the Extended Protocol Configuration Options IE (ePCO IE), see 3GPP TS 24.008 [54] or 3GPP TS 24.301 [84] for IE definition. The APN rate control indicator within the PCO/ePCO IE is received at IP-CAN session establishment.
NOTE 2: The UE and network support of the ePCO IE, is indicated with help of the Indication IE. The ePCO support indication within the Indication IE can be received at IP-CAN session establishment or at IP-CAN session modification. See 3GPP TS 29.274 [81] for IE definition.
If the APN rate control is supported by the UE and the Indication IE is received indicating support of ePCO IE at the IP-CAN session establishment request and the PGW supports the ePCO IE, the PGW shall in the reply, if configured for the APN used, include APN UL rate control parameters in the ePCO IE, see 3GPP TS 24.008 [54] for IE definition.
If the ePCO IE is not supported the PGW shall use the PCO IE.
The GGSN shall use the PCO IE.
If the APN rate control UL parameter(s) is modified and the ePCO IE is supported, the PGW shall initiate an IP-CAN session modification procedure and include the APN UL rate control parameters in the ePCO IE.
If the ePCO IE is not supported the PGW shall use the PCO IE.
The GGSN shall use the PCO IE.
The GGSN/PGW shall enforce the APN rate control per UE and APN according to the configuration for DL and may enforce APN rate control for UL, e.g. when the PGW have indicated to the UE that the UE is not allowed to send exception reports when the limit for the UL APN rate control has been reached.
NOTE 3: The UE locally enforces this uplink APN rate control instruction. The UE considers this APN rate control instruction as valid until it receives a new one from the GGSN/PGW.
B.2.2 Serving PLMN Rate Control information handling in the PGW
If Serving PLMN rate control information is received in the Serving PLMN Rate Control IE from the MME, the PGW shall store this information and use that for rate control enforcement DL for this UE.
If the PGW previously have received Serving PLMN rate control information, the PGW shall behave as follows:
– If the PGW receives new Serving PLMN rate control information in the Serving PLMN Rate Control IE from the MME, the PGW shall replace the old Serving PLMN rate control information with the new Serving PLMN rate control information and use that for rate control enforcement DL for this UE.
– If the PGW receives no Serving PLMN rate control information in the Serving PLMN Rate Control IE from the MME in an IP-CAN session establishment or an IP-CAN session modification , the PGW shall still consider the latest received Serving PLMN rate control information from the MME as valid.
– If PGW receives an indication that Serving PLMN rate control does not apply in the Serving PLMN Rate Control IE, the PGW shall remove the rate control information based on Serving PLMN rate control information.
See 3GPP TS 29.274 [81] for Serving PLMN Rate Control IE definition.
APN rate control, if configured, also applies for the same IP-CAN session, see subclause B.2.1.
Annex C (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2015-03 |
CT#67 |
CP-150126 |
0444 |
2 |
Paging policy differentiation for IMS voice |
13.0.0 |
|
|
2015-09 |
CT#69 |
CP-150464 |
0450 |
1 |
A |
Usage of the UDP port for default unicast encapsulation mode at the SGmb interface is required to support SYNC protocol. |
13.1.0 |
|
2015-09 |
CT#69 |
CP-150468 |
0453 |
A |
3GPP Type of RADIUS 3GPP-User-Location-Info-Time sub-attribute |
13.1.0 |
|
|
2015-09 |
CT#69 |
CP-150472 |
0455 |
1 |
A |
Correction of SGmB L4 Transport protocol |
13.1.0 |
|
2015-12 |
CT#70 |
CP-150658 |
0456 |
1 |
B |
MBMS bearer establishment and update with cell ID list |
13.2.0 |
|
2015-12 |
CT#70 |
CP-150669 |
0459 |
1 |
A |
Transport protocols of Diameter for signalling plane of non transparent case |
13.2.0 |
|
2016-03 |
CT#71 |
CP-160108 |
0460 |
B |
Support for Non-IP data for CIoT over Sgi |
13.3.0 |
|
|
2016-03 |
CT#71 |
CP-160089 |
0465 |
2 |
B |
Usage of the UDP port for default unicast encapsulation mode at the Gmb interface is required to support SYNC protocol |
13.3.0 |
|
2016-06 |
CT#72 |
CP-160252 |
0466 |
1 |
B |
Support of Non-IP delivery data |
13.4.0 |
|
2016-06 |
CT#72 |
CP-160252 |
0469 |
B |
RAT-Type extension for NB-IoT |
13.4.0 |
|
|
2016-06 |
CT#72 |
CP-160252 |
0471 |
1 |
B |
Non-IP Transport |
13.4.0 |
|
2016-06 |
CT#72 |
CP-160277 |
0472 |
1 |
B |
Support for rate control of CIoT datat |
13.4.0 |
|
2016-06 |
CT#72 |
CP-160281 |
0468 |
1 |
B |
Support of Non-IP delivery data |
14.0.0 |
|
2016-09 |
CT#73 |
CP-160441 |
0474 |
1 |
A |
PDP type extension with Non-IP value |
14.1.0 |
|
2016-09 |
CT#73 |
CP-160441 |
0476 |
1 |
A |
Support of Exception Reports for CIoT |
14.1.0 |
|
2016-09 |
CT#73 |
CP-160459 |
0477 |
B |
APN rate control support in GPRS |
14.1.0 |
|
|
2016-09 |
CT#73 |
CP-160441 |
0479 |
A |
APN rate control DL correction |
14.1.0 |
|
|
2016-09 |
CT#73 |
CP-160452 |
0480 |
2 |
B |
Modify the 3GPP-User-Location Info to support eNB ID Information |
14.1.0 |
|
2016-12 |
CT#74 |
CP-160632 |
0481 |
1 |
B |
Local MBMS related MBMS data delivery |
14.2.0 |
|
2016-12 |
CT#74 |
CP-160613 |
0483 |
1 |
A |
Correction to SGi PtP tunnelling based on UDP/IP |
14.2.0 |
|
2016-12 |
CT#74 |
CP-160616 |
0484 |
1 |
F |
Diameter base protocol specification update |
14.2.0 |
|
2017-03 |
CT#75 |
CP-170076 |
0486 |
1 |
F |
Handling of Vendor-Specific-Application-Id AVP |
14.3.0 |
|
2017-03 |
CT#75 |
CP-170086 |
0487 |
1 |
F |
Support of long and short Macro eNodeB IDs |
14.3.0 |
|
2017-03 |
CT#75 |
CP-170075 |
0489 |
2 |
A |
Correction in APN rate control |
14.3.0 |
|
2017-03 |
CT#75 |
CP-170076 |
0492 |
1 |
F |
Update instance number for the Failed-AVP in answer commands |
14.3.0 |
|
2017-09 |
CT#77 |
CP-172052 |
0493 |
F |
Correction of signalling server address request |
15.0.0 |
|
|
2017-09 |
CT#77 |
CP-172052 |
0496 |
1 |
F |
Correction for QoS modification in MBMS Update Request |
15.0.0 |
|
2017-12 |
CT#78 |
CP-173088 |
0498 |
2 |
F |
Rate control for MO exception data |
15.1.0 |
|
2017-12 |
CT#78 |
CP-173105 |
0499 |
B |
Clarification for MBMS session start procedure |
15.1.0 |
|
|
2018-03 |
CT#79 |
CP-180049 |
0500 |
F |
Addition of a note that input-packets / output-packets are not reported in SGi signalling with CUPS |
15.2.0 |
|
|
2018-06 |
CT#80 |
CP-181023 |
0501 |
B |
Data Volume Reporting for Secondary RAT usage |
15.3.0 |
|
|
2018-06 |
CT#80 |
CP-181013 |
0502 |
2 |
B |
Updates to 3GPP-User-Location-Info AVP |
15.3.0 |
|
2018-06 |
CT#80 |
CP-181012 |
0503 |
B |
Updates to 3GPP-PDP-Type AVP |
15.3.0 |
|
|
2018-06 |
CT#80 |
CP-181183 |
0504 |
3 |
B |
Updates to 3GPP-RAT-Type AVP |
15.3.0 |
|
2018-06 |
CT#80 |
CP-181012 |
0505 |
1 |
B |
Updates to 3GPP-GPRS-Negotiated-QoS-Profile AVP |
15.3.0 |
|
2018-06 |
CT#80 |
CP-181014 |
0506 |
F |
Extended accounting octets for RADIUS |
15.3.0 |
|
|
2018-06 |
CT#80 |
CP-181023 |
0506 |
B |
Differentiation of LTE-M (eMTC) |
15.3.0 |
|
|
2018-09 |
CT#81 |
CP-182015 |
0508 |
F |
3GPP-User-Location-Info AVP extension for 5G |
15.4.0 |
|
|
2018-09 |
CT#81 |
CP-182015 |
0509 |
F |
Correction to 3GPP-GPRS-Negotiated-QoS-Profile AVP |
15.4.0 |
|
|
2018-12 |
CT#82 |
CP-183122 |
0510 |
F |
Correct 3GPP-PDP-Type description in RADIUS VSA |
15.5.0 |
|
|
2020-06 |
CT#88e |
CP-201214 |
0511 |
F |
Correct RAT type |
15.6.0 |
|
|
2020-06 |
CT#88e |
CP-201248 |
0511 |
F |
Support secondary RAT data usage report |
16.0.0 |
|
|
2020-09 |
CT#89e |
CP-202060 |
0526 |
F |
RAT Type extension for 5WWC |
16.1.0 |
|
|
2020-09 |
CT#89e |
CP-202078 |
0525 |
F |
Corrections to Framed IPv6 |
17.0.0 |
|
|
2020-12 |
CT#90e |
CP-203144 |
0527 |
F |
Corrections to IPv4 and IPv6 |
17.1.0 |
|
|
2020-12 |
CT#90e |
CP-203138 |
0529 |
1 |
A |
Corrections to Delegated-IPv6-Prefix |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210216 |
0530 |
D |
Correct figure number |
17.2.0 |
|
|
2021-06 |
CT#92e |
CP-211203 |
0533 |
1 |
A |
Correction to Framed IP |
17.3.0 |
|
2021-06 |
CT#92e |
CP-211233 |
0534 |
D |
Editorial fix |
17.3.0 |
|
|
2021-06 |
CT#92e |
CP-211247 |
0535 |
B |
Updates to support CUPS |
17.3.0 |
|
|
2021-06 |
CT#92e |
CP-211278 |
0536 |
3 |
B |
Updates to support L2TP for CUPS |
17.3.0 |
|
2021-06 |
CT#92e |
CP-211279 |
0537 |
2 |
B |
Updates to support L2TP in RADIUS message flow |
17.3.0 |
|
2021-06 |
CT#92e |
CP-211279 |
0538 |
2 |
B |
Updates to support L2TP in Diameter message flow |
17.3.0 |
|
2021-06 |
CT#92e |
CP-211212 |
0539 |
1 |
B |
Reporting UE local IP to Diameter DN-AAA server |
17.3.0 |
|
2021-06 |
CT#92e |
CP-211212 |
0540 |
1 |
B |
Reporting UE local IP to RADIUS DN-AAA server |
17.3.0 |
|
2021-06 |
CT#92e |
CP-211249 |
0541 |
D |
Remove duplicated text for 3GPP-User-Location-Info |
17.3.0 |
|
|
2021-09 |
CT#93e |
CP-212197 |
0542 |
D |
Fix L2TP procedure |
17.4.0 |
|
|
2021-09 |
CT#93e |
CP-212224 |
0543 |
D |
Editorial fix for unrecognized word |
17.4.0 |
|
|
2021-09 |
CT#93e |
CP-212224 |
0544 |
F |
Obsolete RFC4005 by RFC7155 |
17.4.0 |
|
|
2021-09 |
CT#93e |
CP-212197 |
0545 |
F |
Fix editor notes for Tunnel-Password |
17.4.0 |
|
|
2021-12 |
CT#94e |
CP-213241 |
0547 |
1 |
A |
Correction of the applicability of the counted number of packets |
17.5.0 |
|
2021-12 |
CT#94e |
CP-213244 |
0548 |
1 |
F |
Clarification about the usage of Geographic Location Type values |
17.5.0 |
|
2022-03 |
CT#95e |
CP-220208 |
0549 |
1 |
B |
Update the 3GPP-RAT-Type AVP to support NR RedCap access type |
17.6.0 |