A.2 Support of rate control of user data
29.5613GPP5G SystemInterworking between 5G Network and external Data NetworksRelease 17Stage 3TS
A.2.1 General
The rate of user data sent to and from a UE (e.g. a UE using 5G CIoT Optimizations) can be controlled in two different ways:
– Serving PLMN rate control
– Small data rate control
Serving PLMN rate control is further described in 3GPP TS 23.501 [2].
Small data rate control allows HPLMN operators on per 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. Small data DL rate control policing is done in the UPF or the NEF and the small data UL rate control policing is done in the UE. The UPF or NEF can also do small data UL rate control policing.
For further information on small data rate control in the UE, see 3GPP TS 24.501 [42].
NOTE 1: Existing Session-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.
NOTE 2: For serving PLMN rate control and small data rate control, whether the UPF or the NEF is used for data policing depends on the CIoT Optimizations mode that UE and network support (CP or UP Optimizations) and the UE subscription data.
A.2.2 Small Data Rate Control
The small data rate control is configured in the (H-)SMF.
The small data 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, and
– the maximum number of additional UL exception reports per time unit.
Possible time units shall be, minute, hour, day or week.
If the small data rate control is supported by the UE as indicated in the Extended Protocol Configuration Options (ePCO) IE included in the PDU session establishment request and if the (H-)SMF is configured to use small data rate control, the (H-)SMF shall include the configured small data UL rate control parameters in the ePCO IE of the PDU session establishment reply, and send the configured small data DL rate control parameters and optionally the UL rate control parameters to the UPF or the NEF. The small data rate control parameters sent to UE, UPF or NEF may include a remaining small data rate control with validity time information that shall be applied first before applying the configured small data rate control parameters.
NOTE 1: The (H-)SMF can receive small data rate control parameters from the AMF.
See 3GPP TS 24.501 [42] for ePCO IE definition.
If the small data UL rate control parameters are modified, the (H-)SMF shall initiate a PDU session modification procedure and include the small data UL rate control parameters in the ePCO IE. The (H-)SMF may also send the updated small data UL rate control parameters to the UPF or the NEF.
If the small data DL rate control parameters are modified, the (H-)SMF shall send the updated small data DL rate control parameters to the UPF or the NEF.
The UPF or the NEF shall enforce the small data DL rate control and may enforce the small data UL rate control per UE.
NOTE 2: The UE locally enforces this uplink small data rate control instruction. The UE considers this small data rate control instruction as valid until it receives a new one from the (H-)SMF.
A.2.3 Serving PLMN Rate Control information handling
The serving PLMN rate control is configured in the (V-)SMF and it applies per PDU session.
This rate control is operator configurable and expressed as "X NAS Data PDUs per deci hour" where X is an integer that shall not be less than 10. There are separate limits for uplink and downlink NAS Data PDUs:
If serving PLMN rate control information is received from the SMF, the UPF or the NEF shall store this information and use that for DL rate control enforcement for this UE.
The UE shall enforce the serving PLMN UL rate control based on the rate control information received from the (V-)SMF.
The (V-)SMF may also enforce the serving PLMN UL and/or DL rate control.
If the UPF or the NEF previously have received Serving PLMN rate control information, it shall behave as follows:
– If the UPF or the NEF receives new Serving PLMN rate control information from the SMF, it shall replace the old Serving PLMN rate control information with the new Serving PLMN rate control information and use that for DL rate control enforcement for this UE.
– If the UPF or the NEF receives no Serving PLMN rate control information from the SMF, it shall still consider the latest received Serving PLMN rate control information from the SMF as valid.
– If UPF or the NEF receives an indication that Serving PLMN rate control does not apply from the SMF, it shall remove the rate control information based on Serving PLMN rate control information.
Small data rate control, if configured, also applies for the same PDU session, see clause A.2.2.
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-10 |
TS skeleton of interworking between 5G Network and external Data Networks |
0.0.0 |
|||||
|
2017-11 |
CT3#92 |
C3-175380 |
Update after CT3#92; inclusion of C3-175241, C3-175286, C3-175287, C3-175288, C3-175289. |
0.1.0 |
|||
|
2017-12 |
CT3#93 |
C3-176400 |
Update after CT3#93; TS number changed to 29.561 and inclusion of C3-176265, C3-176266. |
0.2.0 |
|||
|
2018-01 |
CT3#94 |
C3-180365 |
Update after CT3#94; inclusion of C3-180264, C3-180126, C3-180348, C3-180129, C3-180130. |
0.3.0 |
|||
|
2018-03 |
CT3#95 |
C3-181371 |
Update after CT3#95; inclusion of C3-181043, C3-181044, C3-181261, C3-181047, C3-181099. |
0.4.0 |
|||
|
2018-04 |
CT3#96 |
C3-182519 |
Update after CT3#96; inclusion of C3-182183, C3-182381, C3-182382, C3-182383. |
0.5.0 |
|||
|
2018-06 |
CT3#97 |
C3-183917 |
Update after CT3#97; inclusion of C3-183308, C3-183309, C3-183310, C3-183318, C3-183319, C3-183717, C3-183321, C3-183325, C3-183326, C3-183327, C3-183729. |
0.6.0 |
|||
|
2018-06 |
CT#80 |
CP-181027 |
TS sent to plenary for approval |
1.0.0 |
|||
|
2018-06 |
CT#80 |
CP-181027 |
TS approved by plenary |
15.0.0 |
|||
|
2018-09 |
CT#81 |
CP-182015 |
0001 |
2 |
F |
Add multihoming support in IPv6 stateless address autoconfiguration |
15.1.0 |
|
2018-09 |
CT#81 |
CP-182015 |
0002 |
1 |
F |
IP address change |
15.1.0 |
|
2018-09 |
CT#81 |
CP-182015 |
0003 |
1 |
F |
MAC address change |
15.1.0 |
|
2018-09 |
CT#81 |
CP-182015 |
0004 |
– |
F |
Final result of authentication/authorization from the DN-AAA – Receiving entity |
15.1.0 |
|
2019-06 |
CT#84 |
CP-191188 |
0006 |
4 |
F |
Correct session AMBR |
15.2.0 |
|
2019-06 |
CT#84 |
CP-191070 |
0005 |
– |
B |
Rate control for 5G CIoT |
16.0.0 |
|
2019-09 |
CT#85 |
CP-192150 |
0008 |
A |
3GPP VSA presence for RADIUS |
16.1.0 |
|
|
2019-09 |
CT#85 |
CP-192169 |
0010 |
1 |
B |
Add DN-AAA re-authentication |
16.1.0 |
|
2019-09 |
CT#85 |
CP-192150 |
0012 |
A |
Correct DN-AAA authentication |
16.1.0 |
|
|
2019-09 |
CT#85 |
CP-192150 |
0014 |
2 |
A |
Correct DN-AAA authorization |
16.1.0 |
|
2019-09 |
CT#85 |
CP-192137 |
0017 |
1 |
F |
Correct small data rate control status |
16.1.0 |
|
2019-09 |
CT#85 |
CP-192159 |
0018 |
2 |
B |
IP address allocation via DHCP/AAA Server |
16.1.0 |
|
2019-09 |
CT#85 |
CP-192152 |
0019 |
1 |
B |
DN interworking of UPF for PIM |
16.1.0 |
|
2019-12 |
CT#86 |
CP-193200 |
0022 |
1 |
B |
Support Slice Specific authentication |
16.2.0 |
|
2020-03 |
CT#87e |
CP-200210 |
0023 |
2 |
B |
Call flows of NSSAA procedures |
16.3.0 |
|
2020-03 |
CT#87e |
CP-200198 |
0024 |
– |
F |
Resolve editor note for PLMN rate control |
16.3.0 |
|
2020-03 |
CT#87e |
CP-200211 |
0025 |
– |
F |
IP address pool id encoding |
16.3.0 |
|
2020-06 |
CT#88e |
CP-201226 |
0027 |
1 |
A |
Correct access challenge |
16.4.0 |
|
2020-06 |
CT#88e |
CP-201247 |
0028 |
– |
B |
Support secondary RAT data usage report |
16.4.0 |
|
2020-06 |
CT#88e |
CP-201236 |
0030 |
– |
F |
Replacing AUSF by NSSAAF to support NSSAA |
16.4.0 |
|
2020-06 |
CT#88e |
CP-201237 |
0031 |
– |
F |
IP address pool id in accounting and its IP version |
16.4.0 |
|
2020-06 |
CT#88e |
CP-201247 |
0033 |
1 |
F |
Correct AMF and SMF address |
16.4.0 |
|
2020-06 |
CT#88e |
CP-201274 |
0034 |
1 |
B |
Subscription trigger request UE IP address from DN-AAA server |
16.4.0 |
|
2020-06 |
CT#88e |
CP-201228 |
0035 |
1 |
B |
Ipv6 Prefix Delegation via DHCPv6 |
16.4.0 |
|
2020-06 |
CT#88e |
CP-201331 |
0036 |
1 |
F |
Remove the feature for ip address pool |
16.4.0 |
|
2020-09 |
CT#89e |
CP-202057 |
0040 |
1 |
A |
Correction to 3GPP-UE-MAC-Address |
16.5.0 |
|
2020-09 |
CT#89e |
CP-202057 |
0042 |
1 |
A |
Correction on the authentication and authorization procedure |
16.5.0 |
|
2020-09 |
CT#89e |
CP-202057 |
0046 |
– |
A |
Correction to the Sesson-AMBR |
16.5.0 |
|
2020-09 |
CT#89e |
CP-202067 |
0049 |
– |
F |
Add missing applicable messages for IP pool info |
16.5.0 |
|
2020-09 |
CT#89e |
CP-202081 |
0048 |
1 |
F |
List of allowed VLAN Ids within DN authorization data |
16.5.0 |
|
2020-09 |
CT#89e |
CP-202057 |
0054 |
– |
A |
Correction on the authorization data |
16.5.0 |
|
2020-09 |
CT#89e |
CP-202060 |
0055 |
– |
F |
RAT Type extension for 5WWC |
16.5.0 |
|
2020-09 |
CT#89e |
CP-202059 |
0056 |
– |
F |
User Location extension for 5WWC |
16.5.0 |
|
2020-12 |
CT#90e |
CP-203121 |
0060 |
– |
A |
Correction on the Acct-Session-Id |
16.6.0 |
|
2020-12 |
CT#90e |
CP-203143 |
0064 |
1 |
F |
Correct SGSN address |
16.6.0 |
|
2020-12 |
CT#90e |
CP-203123 |
0066 |
1 |
F |
Correct applicability for User Location extension |
16.6.0 |
|
2020-12 |
CT#90e |
CP-203150 |
0067 |
– |
F |
Correct network identifier for SNPN |
16.6.0 |
|
2020-12 |
CT#90e |
CP-203123 |
0069 |
– |
F |
Updates to IPv6 Prefix Delegation |
16.6.0 |
|
2020-12 |
CT#90e |
CP-203099 |
0072 |
2 |
A |
Correction on PAP/CHAP supporting Rel-15 N1 mode UE |
16.6.0 |
|
2020-12 |
CT#90e |
CP-203134 |
0058 |
1 |
B |
Adding a note for IPv4/IPv6 Non-transparent access to DN using PAP/CHAP |
17.0.0 |
|
2020-12 |
CT#90e |
CP-203134 |
0061 |
1 |
B |
Adding PAP/CHAP in RADIUS message flow(successful case) |
17.0.0 |
|
2020-12 |
CT#90e |
CP-203134 |
0062 |
1 |
B |
Adding PAP/CHAP in Diameter message flow(successful case) |
17.0.0 |
|
2020-12 |
CT#90e |
CP-203144 |
0068 |
– |
F |
Corrections to IPv6 |
17.0.0 |
|
2020-12 |
CT#90e |
CP-203147 |
0070 |
1 |
F |
Corrections on SMF directly connecting DN-AAA server |
17.0.0 |
|
2021-03 |
CT#91e |
CP-210226 |
0076 |
1 |
B |
Interworking scenario support |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210226 |
0077 |
1 |
B |
Reporting Session S-NSSAI to RADIUS DN-AAA server |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210226 |
0078 |
1 |
B |
Reporting Session S-NSSAI to Diameter DN-AAA server |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210227 |
0079 |
3 |
B |
Reporting FQDN of CHF to RADIUS DN-AAA server |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210227 |
0080 |
1 |
B |
Reporting FQDN of CHF to Diameter DN-AAA server |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210226 |
0081 |
1 |
B |
Reporting FQDN of Serving NF to RADIUS DN-AAA server |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210226 |
0082 |
– |
B |
Report FQDN of Serving NF to Diameter DN-AAA server |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210214 |
0083 |
2 |
F |
Update descriptions for PAP/CHAP in RADIUS message flow |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210214 |
0084 |
2 |
F |
Update descriptions for PAP/CHAP in Diameter message flow |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210214 |
0085 |
1 |
B |
5GS interworking with EPS for IPv4IPv6 Non-transparent access using PAPCHAP |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210241 |
0088 |
1 |
B |
5GS interworking with EPS for EAP based secondary AUTH in RADIUS message flow |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210241 |
0089 |
1 |
B |
5GS interworking with EPS for EAP based secondary AUTH in Diameter message flow |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210214 |
0090 |
1 |
F |
Update clarification for PAP/CHAP in RADIUS message flow |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210214 |
0091 |
1 |
F |
Update clarification for PAP/CHAP in Diameter message flow |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210228 |
0092 |
1 |
B |
5GC Support of DHCP signalling for RG |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210202 |
0093 |
1 |
A |
Reporting GCI to RADIUS DN-AAA server |
17.1.0 |
|
2021-03 |
CT#91e |
CP-210202 |
0094 |
1 |
A |
Reporting GCI to Diameter DN-AAA server |
17.1.0 |
|
2021-06 |
CT#92e |
CP-211211 |
0097 |
1 |
F |
Clarification of accounting for the interworking scenario |
17.2.0 |
|
2021-06 |
CT#92e |
CP-211211 |
0102 |
1 |
B |
Updates 5GS interwroking with EPS for EAP based re-auth in Diameter message flow |
17.2.0 |
|
2021-06 |
CT#92e |
CP-211209 |
0105 |
1 |
A |
Correction to Framed IP |
17.2.0 |
|
2021-06 |
CT#92e |
CP-211211 |
0106 |
1 |
F |
Complete AAA triggered re-authentication flow for Diameter |
17.2.0 |
|
2021-06 |
CT#92e |
CP-211280 |
0107 |
3 |
B |
Updates to support L2TP for CUPS |
17.2.0 |
|
2021-06 |
CT#92e |
CP-211280 |
0108 |
2 |
B |
Updates to support L2TP in RADIUS message flow |
17.2.0 |
|
2021-06 |
CT#92e |
CP-211280 |
0109 |
2 |
B |
Updates to support L2TP in Diameter message flow |
17.2.0 |
|
2021-06 |
CT#92e |
CP-211211 |
0110 |
1 |
F |
Correction to Framed Route information |
17.2.0 |
|
2021-06 |
CT#92e |
CP-211281 |
0111 |
1 |
B |
Adding support for providing L2TP information through N6 interface |
17.2.0 |
|
2021-06 |
CT#92e |
CP-211244 |
0112 |
1 |
B |
Reporting UE local IP to RADIUS DN-AAA server |
17.2.0 |
|
2021-06 |
CT#92e |
CP-211244 |
0113 |
1 |
B |
Reporting UE local IP to Diameter DN-AAA server |
17.2.0 |
|
2021-09 |
CT#93e |
CP- 212197 |
0116 |
1 |
B |
L2TP information provision |
17.3.0 |
|
2021-09 |
CT#93e |
CP-212197 |
0119 |
F |
Fix L2TP procedure |
17.3.0 |
|
|
2021-09 |
CT#93e |
CP-212216 |
0121 |
– |
F |
Correct PAP/CHAP description |
17.3.0 |
|
2021-09 |
CT#93e |
CP-212224 |
0122 |
– |
F |
Fix DN-AAA initiated re-authentication |
17.3.0 |
|
2021-09 |
CT#93e |
CP-212224 |
0123 |
1 |
F |
Addressing impersonate attack from AAA-S |
17.3.0 |
|
2021-09 |
CT#93e |
Notes and editor notes formatting issues fixed |
17.3.1 |
||||
|
2021-12 |
CT#94e |
CP-213243 |
0124 |
1 |
B |
Reporting DNAI to RADIUS DN-AAA server |
17.4.0 |
|
2021-12 |
CT#94e |
CP-213243 |
0125 |
1 |
B |
Reporting DNAI to Diameter DN-AAA server |
17.4.0 |
|
2022-03 |
CT#95e |
CP-220206 |
0127 |
B |
Accounting correlation for redundant transmission |
17.5.0 |
|
|
2022-03 |
CT#95e |
CP-220196 |
0128 |
F |
Correct 3GPP-Session-Id |
17.5.0 |
|
|
2022-03 |
CT#95e |
CP-220208 |
0129 |
B |
Update the 3GPP-RAT-Type AVP to support NR RedCap access type |
17.5.0 |
|
|
2022-03 |
CT#95e |
CP-220182 |
0130 |
B |
Interworking with CH using AAA server |
17.5.0 |
|
|
2022-06 |
CT#96 |
CP-221157 |
0131 |
1 |
B |
Adding Charging Id to support roaming scenario |
17.6.0 |
|
2022-06 |
CT#96 |
CP-221157 |
0132 |
1 |
F |
DN-AAA initiated re-auth when UE is not reachable in 5GS |
17.6.0 |
|
2022-06 |
CT#96 |
CP-221158 |
0133 |
2 |
F |
DN-AAA initiated re-auth when UE unreachable |
17.6.0 |
|
2022-06 |
CT#96 |
CP-221120 |
0134 |
B |
Introduction to support 5MBS data delivery |
17.6.0 |
|
|
2022-06 |
CT#96 |
CP-221120 |
0135 |
B |
N6mb and Nmb9 protocol to support 5MBS data delivery |
17.6.0 |
|
|
2022-06 |
CT#96 |
CP-221120 |
0136 |
B |
Nmb8 protocol to support 5MBS data delivery |
17.6.0 |
|
|
2022-06 |
CT#96 |
CP-221138 |
0137 |
1 |
B |
Support for interworking with an AAA server in DCS |
17.6.0 |
|
2022-09 |
CT#97e |
CP-222106 |
0138 |
1 |
F |
UE default credentials for primary and secondary authentication |
17.7.0 |
|
2022-09 |
CT#97e |
CP-222125 |
0139 |
1 |
F |
Close the open issue related to DNAI |
17.7.0 |
|
2022-09 |
CT#97e |
CP-222094 |
0141 |
F |
Updates on interworking with MBS AP |
17.7.0 |
|
|
2022-12 |
CT#98e |
CP-223177 |
0142 |
F |
Corrections to UE default credentials for primary and secondary authentication |
17.8.0 |
|