CONFIGURE AND ENFORCE MAXIMUM DATA RATE PER UE PER NETWORK SLICE

Abstract

It is provided a method comprising: checking whether a maximum data rate for a subscriber for a network slice is received; monitoring, if the maximum data rate for the subscriber for the network slice is received, whether a hypothetical total data rate of all flows of the subscriber for the network slice would exceed the maximum data rate for the subscriber for the network slice if a grant to transmit data were provided for the subscriber for packets belonging to the network slice; inhibiting providing the grant for the subscriber if the hypothetical total data rate of all flows of the subscriber for the network slice exceeded the maximum data rate of the network slice if the grant were provided.

Claims

1. An apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus to: retrieve subscription information comprising a respective maximum data rate for the subscriber for each of one or more network slices allowed for the subscriber; and provide the respective maximum data rate allowed for the subscriber for each of the one or more network slices allowed for the subscriber.

2. The apparatus according to claim 1, wherein the one or more processors with the memory further cause the apparatus to provide the subscription information in response to the request; and the indication of the respective maximum data rate allowed for the subscriber for each of the one or more network slices allowed for the subscriber is comprised in the subscription information.

3. The apparatus according to claim 1, wherein the one or more processors with the memory further cause the apparatus to: retrieve a respective maximum data rate allowed for the subscriber for each network slice allowed for the subscriber; and provide the indication of the respective maximum data rate allowed for the subscriber for each network slice allowed for the subscriber in response to the request.

4.-8. (canceled)

9. An apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the apparatus to: receive a maximum data rate for a subscriber for a network slice; determine whether a hypothetical total data rate of all flows of the subscriber for the network slice would exceed the maximum data rate for the subscriber for the network slice if a grant to the subscriber is provided; and inhibit providing the grant to the subscriber if the hypothetical total data rate of all flows of the subscriber for the network slice exceeded the maximum data rate of the network slice.

10. The apparatus according to claim 9, wherein the one or more processors with the memory further cause the apparatus to: associate all packet flows of the subscriber for the network slice to a logical channel group used for scheduling of the packet flows for sessions of the subscriber; wherein the monitoring comprises monitoring, if the maximum data rate for the subscriber for the network slice is received, whether a hypothetical total data rate of the logical channel group would exceed the maximum data rate for the subscriber for the network slice if a grant to transmit the data were provided for the logical channel group; and the inhibiting comprises inhibiting providing the grant for the logical channel group if the hypothetical total data rate of the logical channel group would exceed the maximum data rate for the subscriber for the network slice if the grant were provided for the logical channel group.

11. The apparatus according to claim 9, wherein the one or more processors with the memory further cause the apparatus to: monitor if a session for the network slice for the subscriber is to be setup, wherein the session requests a requested guaranteed data rate and comprises one or more flows; check whether an indication of the maximum data rate for the subscriber for the network slice is received; calculate a hypothetical guaranteed data rate as a sum of a current aggregated guaranteed data rate for the subscriber for the network slice and the requested guaranteed data rate if the session setup request is received and the indication of the maximum data rate for the subscriber for the network slice is received; accept the setup of the session and make the current aggregated guaranteed data rate for the network slice equal to the hypothetical guaranteed data rate if the hypothetical guaranteed data rate is not larger than the maximum data rate for the subscriber for the network slice; and reject the setup of at least one of the flows of the session such that a sum of the current aggregated guaranteed data rate for the subscriber for the network slice and the requested guaranteed data rate of the remaining flows of the session is not larger than the maximum data rate for the subscriber for the network slice if the hypothetical guaranteed data rate is larger than the maximum data rate for the subscriber for the network slice.

12. The apparatus according to claim 11, wherein the one or more processors with the memory further cause the apparatus to: reject the setup of the session if the hypothetical guaranteed data rate is larger than the maximum data rate for the subscriber for the network slice.

13. The apparatus according to claim 11, wherein the one or more processors with the memory further cause the apparatus to: monitor if a modification of the requested guaranteed data rate of the session by a data rate difference is requested; calculate a modified hypothetical guaranteed data rate as a sum of a current aggregated guaranteed data rate for the subscriber for the network slice and the data rate difference if the modification is requested; accept the modification and make the current aggregated guaranteed data rate for the subscriber for the network slice equal to the modified hypothetical guaranteed data rate if the modified hypothetical guaranteed data rate is not larger than the maximum data rate for the subscriber for the network slice; and reject the modification if the modified hypothetical guaranteed data rate is larger than the maximum data rate for the subscriber for the network slice.

14. The apparatus according to claim 13, wherein the one or more processors with the memory further cause the apparatus to: if the modification is a request to release the session, calculate the modified hypothetical guaranteed data rate as a difference of the current aggregated guaranteed data rate minus the guaranteed data rate of the session, and accept the modification.

15. A method comprising: retrieving subscription information comprising a respective maximum data rate for the subscriber for each of one or more network slices allowed for the subscriber; and providing the respective maximum data rate allowed for the subscriber for each of the one or more network slices allowed for the subscriber.

16. The method according to claim 15, further comprising: providing the subscription information in response to the request; wherein the indication of the respective maximum data rate allowed for the subscriber for each of the one or more network slices allowed for the subscriber is comprised in the subscription information.

17. The method according to claim 15, wherein a respective maximum data rate allowed for the subscriber is retrieved for each network slice allowed for the subscriber; the indication of the respective maximum data rate allowed for the subscriber for each network slice allowed for the subscriber is provided in response to the request.

18.-22. (canceled)

23. A method comprising: receiving a maximum data rate for a subscriber for a network slice; determining whether a hypothetical total data rate of all flows of the subscriber for the network slice would exceed the maximum data rate for the subscriber for the network slice if a grant to the subscriber is provided; and inhibiting providing the grant to the subscriber if the hypothetical total data rate of all flows of the subscriber for the network slice exceeded the maximum data rate of the network slice.

24. The method according to claim 23, further comprising: associating all packet flows of the subscriber for the network slice to a logical channel group used for scheduling of the packet flows for sessions of the subscriber; wherein the monitoring comprises monitoring, if the maximum data rate for the subscriber for the network slice is received, whether a hypothetical total data rate of the logical channel group would exceed the maximum data rate for the subscriber for the network slice if a grant to transmit the data were provided for the logical channel group; and the inhibiting comprises inhibiting providing the grant for the logical channel group if the hypothetical total data rate of the logical channel group would exceed the maximum data rate for the subscriber for the network slice if the grant were provided for the logical channel group.

25. The method according to claim 23, further comprising: monitoring if a session for the network slice for the subscriber is to be setup, wherein the session requests a requested guaranteed data rate and comprises one or more flows; checking whether an indication of the maximum data rate for the subscriber for the network slice is received; calculating a hypothetical guaranteed data rate as a sum of a current aggregated guaranteed data rate for the subscriber for the network slice and the requested guaranteed data rate if the session setup request is received and the indication of the maximum data rate for the subscriber for the network slice is received; accepting the setup of the session and make the current aggregated guaranteed data rate for the network slice equal to the hypothetical guaranteed data rate if the hypothetical guaranteed data rate is not larger than the maximum data rate for the subscriber for the network slice; and rejecting the setup of at least one of the flows of the session such that a sum of the current aggregated guaranteed data rate for the subscriber for the network slice and the requested guaranteed data rate of the remaining flows of the session is not larger than the maximum data rate for the subscriber for the network slice if the hypothetical guaranteed data rate is larger than the maximum data rate for the subscriber for the network slice.

26. The method according to claim 25, wherein the setup of the session is rejected if the hypothetical guaranteed data rate is larger than the maximum data rate for the subscriber for the network slice.

27. The method according to claim 25, further comprising: monitoring if a modification of the requested guaranteed data rate of the session by a data rate difference is requested; calculating a modified hypothetical guaranteed data rate as a sum of a current aggregated guaranteed data rate for the subscriber for the network slice and the data rate difference if the modification is requested; accepting the modification and make the current aggregated guaranteed data rate for the subscriber for the network slice equal to the modified hypothetical guaranteed data rate if the modified hypothetical guaranteed data rate is not larger than the maximum data rate for the subscriber for the network slice; and rejecting the modification if the modified hypothetical guaranteed data rate is larger than the maximum data rate for the subscriber for the network slice.

28. The method according to claim 27, wherein, if the modification is a request to release the session, the modified hypothetical guaranteed data rate is calculated as a difference of the current aggregated guaranteed data rate minus the guaranteed data rate of the session, and the modification is accepted.

29. A non-transitory computer-readable medium comprising a set of instructions encoded thereon which, when executed on an apparatus, is configured to cause the apparatus to carry out the method according to claim 15.

30. (canceled)

31. A non-transitory computer-readable medium comprising a set of instructions encoded thereon which, when executed on an apparatus, is configured to cause the apparatus to carry out the method according to claim 23.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0089] Further details, features, objects, and advantages are apparent from the following detailed description of the preferred embodiments of the present invention which is to be taken in conjunction with the appended drawings, wherein:

[0090] FIG. 1 shows a first deployment scenario where some example embodiments of the invention may be deployed;

[0091] FIG. 2 shows a second deployment scenario where some example embodiments of the invention may be deployed;

[0092] FIG. 3 shows a third deployment scenario where some example embodiments of the invention may be deployed;

[0093] FIG. 4 shows maximum data rates for different network slices stored in UDM according to some example embodiments of the invention;

[0094] FIG. 5 shows a table hold in AMF according to some example embodiments of the invention;

[0095] FIG. 6 indicates how the UE registration procedure of FIG. 4.2.2.2.2-1: Registration procedure from 3GPP TS 23.502 may be updated according to some example embodiments of the invention;

[0096] FIG. 7 indicates how the PDU session establishment procedure of FIG. 4.3.2.2.1-1: UE-requested PDU Session Establishment for non-roaming and roaming with local breakout from 3GPP TS 23.502 may be updated according to some example embodiments of the invention;

[0097] FIG. 8 indicates how the PDU session modification procedure of FIG. 4.3.3.2-1: UE or network requested PDU Session Modification (for non-roaming and roaming with local breakout) from 3GPP TS 23.502 may be updated according to some example embodiments of the invention;

[0098] FIG. 9 indicates how the PDU session release procedure of FIG. 4.3.4.2-1: UE or network requested PDU Session Release for non-roaming and roaming with local breakout from 3GPP TS 23.502 may be updated according to some example embodiments of the invention;

[0099] FIG. 10 shows an apparatus according to an embodiment of the invention;

[0100] FIG. 11 shows a method according to an embodiment of the invention;

[0101] FIG. 12 shows an apparatus according to an embodiment of the invention;

[0102] FIG. 13 shows a method according to an embodiment of the invention;

[0103] FIG. 14 shows an apparatus according to an embodiment of the invention;

[0104] FIG. 15 shows a method according to an embodiment of the invention; and

[0105] FIG. 16 shows an apparatus according to an embodiment of the invention.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS

[0106] Herein below, certain embodiments of the present invention are described in detail with reference to the accompanying drawings, wherein the features of the embodiments can be freely combined with each other unless otherwise described. However, it is to be expressly understood that the description of certain embodiments is given by way of example only, and that it is by no way intended to be understood as limiting the invention to the disclosed details.

[0107] Moreover, it is to be understood that the apparatus is configured to perform the corresponding method, although in some cases only the apparatus or only the method are described.

[0108] A method to rate-limit the flows of a UE per S-NSSAI (i.e. network slice) as defined by the GSMA parameters, is currently not available in the 5GS QoS framework. The 5G system enforces a UE-AMBR (UE Aggregate Maximum Bit Rate) but not per network slice, and not for the sum of GBR and non-GBR QoS flows for the network slice. The Grants are also provided to the UE per UE and not per network slice, so the RAN cannot enforce maximum data rate per network slice, as is, in the Uplink direction, unlike the UE-AMBR.

[0109] As per 3GPP TR 23.700-40, related key issue #3 is defined for limitation of data rate per network slice in UL and DL per UE. [0110] Whether and how to limit the data rate of UE for a network slice? (ensuring that the aggregate of the PDU sessions that use the network slice are rate limited to the rate defined for the network slice in DL and UL)

[0111] In an overview, some example embodiments of the invention provide at least one of the following functionalities:

[0112] Configuration Related (UDM) [0113] 1. UE Maximum data rate(s) per network slice (UE-Slice-MBR) is provisioned in the UDM for all S-NSSAIs allowed for the UE by a PLMN.

[0114] Functionality Related (NG-RAN, AMF): [0115] 1. AMF gets UE-Slice-MBR from UDM for allowed S-NSSAIs during the Initial UE registration procedure as part of subscription information retrieval. [0116] 2. During the N1 Initial context set up procedure the AMF provides the NG-RAN with UE-Slice-MBR per S-NSSAI for all the allowed S-NSSAIs for the UE. [0117] 3. NG-RAN enforces data rate limitation per UE per network slice based on UE-Slice-MBR considering both the GBR sessions and the non-GBR sessions for the network slice. [0118] 4. AMF (or RAN) maintains the aggregate GBR values per UE per Network slice. aggregate GBR=sum of GBRs from the active PDU sessions of the UE per network slice. [0119] 5. After successful PDU session(s) establishment or modification or release procedure, AMF (or RAN) updates the aggregate GBR for the UE per network slice. [0120] 6. AMF (or RAN) checks the available bit rate for this network slice before establishing/modifying the PDU session as below:

[0121] If {(UE-Slice-MBR>(aggregate GBR+sum of Requested PDU session's GFBR for all flows within the PDU session)}

[0122] Then accept PDU session request or modification request for the UE.

[0123] Else

[0124] GBR flows/session are not admitted and rejected with the cause “maximum data rate per UE for the network slice reached”

}

[0125] In some example embodiments, AMF (or RAN) may reject the session if the UE-Slice-MBR were exceeded due to the requested PDU session establishment or modification. In some example embodiments, AMF (or RAN) may reject only some flows of the requested PDU session establishment or modification such that the UE-Slice-MBR is not exceeded. AMF (or RAN) may indicate the rejection of a session or a flow to SMF. [0126] 7. The RAN associates all the QoS flows (i.e. GBR and non-GBR flows) of a S-NSSAI to a Logical channel group and it provides grants to the logical channel group not to exceed the UE-Slice-MBR.

[0127] Some example embodiments of the invention may be deployed in different deployment scenarios, as shown in FIGS. 1 to 3: [0128] As shown in FIG. 1, a UE may be configured with one or multiple allowed network slices (e.g. NS-1) and UE may have PDU sessions associated with each network slice with different SMF (in FIG. 1, SMF1 and SMF2 manage sessions associated with NS-1). [0129] As shown in FIG. 2, a UE may be configured with multiple allowed network slices (NS-1, NS-2) and UE may have PDU sessions associated with same network slice with different SMFs (in FIG. 1, SMF1 and SMF2 manage sessions associated with NS-1; in addition, SMF2 manages a session associated with NS-2). For example, NSSF may select the network slices based on load sharing properties. [0130] As shown in FIG. 3, a UE may be configured with multiple allowed network slices (NS-1, NS-2) and may have PDU sessions associated with different network slices to be served by same SMF (SMF1 manages sessions across NS-1 and NS-2).

[0131] Configuration Updates and NF Impacts:

[0132] UDM:

[0133] According to some example embodiments, the UE subscription profile is updated with the Maximum data rate per allowed network slice UE-Slice-MBR. An example is shown in FIG. 4. In this example, the network slices (i.e., their identifiers S-NSSAIs) are grouped by the maximum data rates. In some example embodiments, instead, a maximum data rate is indicated for each S-NSSAI.

[0134] AMF:

[0135] During UE registration procedure, AMF gets UE-Slice-MBR from UE subscription data from the UDM. [0136] AMF maintains aggregate GBR for all the PDU sessions per UE per network slice. [0137] During the N2 Initial context set up procedure, the AMF provides the NG-RAN with UE-Slice-MBR for allowed S-NSSAIs. [0138] During each PDU session creation, PDU session modification, and PDU session release, AMF calculates a hypothetical aggregate GBR, considering QoS guaranteed bit rates. [0139] If the hypothetical aggregate GBR exceeds UE-Slice-MBR then no PDU session creation/modification asking for the bit rate exceeding the UE-Slice-MBR is accepted.

[0140] FIG. 5 shows an example table hold in AMF for each UE (1.sup.st column) and each S-NSSAI allowed for the UE (2.sup.nd column). In the 3.sup.rd column, the MBR of this UE and this network slice is indicated (here for both uplink and downlink). The 4.sup.th column indicates the aggregate GBR for all sessions of the UE using the respective network slice. The 4.sup.th column in FIG. 5 includes the sum of the GBRs actually allocated for different sessions using the respective network slice. The actually allocated GBRs are indicated in the r column.

[0141] In the example of FIG. 5, sessions 1 and 2 use the same network slice S-NSSAI 1, and session 3 uses network slice S-NSSAI 2 (5.sup.th column). Both sessions 1 and 3 are managed by SMF1, whereas session 2 is managed by SMF3 (6.sup.th column). Thus, the example of FIG. 5 corresponds to a mixture of the deployment scenario of FIG. 2 (for S-NSSAI 1 being managed by SMF1 and SMF2) and FIG. 3 (for SMF1 managing sessions on S-NSSAI 1 and S-NSSAI 2).

[0142] NG-RAN: [0143] During the N2 Initial context setup procedure, the AMF provides the NG-RAN with UE-Slice-MBR for allowed S-NSSAIs associated to a UE. [0144] he NG-RAN provides grants to the UE not to exceed the UE-Slice-MBR. That is, NG RAN calculates a hypothetical data rate of the UE for each allowed network slice assuming a grant is provided and provides the grant only if the hypothetical data rate does not exceed the respective UE-Slice-MBR for each of the allowed network slices. Thus, NG RAN considers both GBR flows and non-GBR flows for enforcing UE-Slice-MBR. [0145] n some example embodiments, in order to ensure that grants are only provided if the UE Slice-MBR is not exceeded, NG-RAN associates all the QoS flows of a S-NSSAI to a Logical channel group and provides a grant to the LCG only if the hypothetical data rate does not exceed the respective UE-Slice-MBR.

[0146] RAN may identify the slice information for a given PDU session, and QoS flow as per 3GPP TS 23.502, section 4.3.2.2 (step 12): [0147] The PDU Session ID may be used by AN signalling with the UE to indicate to the UE the association between (R)AN resources and a PDU Session for the UE. [0148] A PDU Session is associated to an S-NSSAI of the HPLMN and, if applicable, to a S-NSSAI of the VPLMN, and a DNN. The S-NSSAI provided to the (R)AN, is the S-NSSAI with the value for the Serving PLMN (i.e. the HPLMN S-NSSAI or, in LBO roaming case, the VPLMN S-NSSAI).

[0149] In some example embodiments, instead of or in addition to AMF, NG-RAN may take care that the aggregate GBR of a UE for a network slice does not exceed UE-slice-MBR. The procedure may be the same as described for AMF.

[0150] 3GPP Procedure Updates:

[0151] According to some example embodiments of the invention, at least one of the following procedures is updated over the current version: [0152] 1. UE Registration procedure (FIG. 6); [0153] 2. PDU session establishment (FIG. 7); [0154] 3. PDU session modification (FIG. 8); and [0155] 4. PDU session release (FIG. 9).

[0156] FIGS. 6 to 9 show how the above 3GPP procedures may be updated. In particular, they show examples where the respective actions may be inserted in the respective conventional procedure. [0157] 1. UE Registration procedure:

[0158] Compared to the UE registration procedure according to current FIG. 4.2.2.2.2-1: Registration procedure from 3GPP TS 23.502, the following actions are added, as shown in FIG. 6: [0159] AMF learns from UDM about Maximum data rate for all the S-NSSAIs allowed for the UE during the UE registration procedure. [0160] AMF informs the NG-RAN about the Maximum data rate for all the allowed S-NSSAIs during Initial context setup procedure or at any other time during establishment of the session of the UE.

[0161] 2. PDU Session Establishment Procedure:

[0162] Compared to the PDU session establishment procedure according to current FIG. 4.3.2.2.1-1: UE-requested PDU Session Establishment for non-roaming and roaming with local breakout from 3GPP TS 23.502, the following actions are added, as shown in FIG. 7: [0163] SMF indicates the GBR allocated for each of the QCI flows (i.e., for each flow to which a GBR is allocated); [0164] AMF calculates the sum of the GBR to be newly allocated and the GBR already allocated for the network slice to be used by the PDU session to be established to obtain a hypothetical total GBR. If this hypothetical total GBR exceeds UE-Slice-MBR for the network slice, AMF rejects the session establishment, e.g. with cause “Maximum data rate reached for the network slice” (or similar). On the other hand, if the hypothetical total GBR does not exceed UE-Slice-MBR, AMF may admit the session establishment. Furthermore, latest after establishment of the new session, it updates its maintained value of the GBR allocated for the network slice such that it becomes the hypothetical total value.

[0165] Furthermore, as also shown in FIG. 7, NG-RAN may associate all the QoS flows (i.e. GBR flows and non-GBR flows) of the UE for a S-NSSAI into a respective LCG. Associating into LCG is a preferred option to enforce that the data rate does not exceed UE-slice-MBR, but this association is not mandatory. Then, RAN provides a grant to the UE only if the hypothetical total data rate (GBR+non-GBR) does not exceed UE-Slice-MBR. [0166] 3. PDU Session modification (UE initiated or Network initiated):

[0167] Compared to the PDU session modification procedure according to current FIG. 4.3.3.2-1: UE or network requested PDU Session Modification (for non-roaming and roaming with local breakout) from 3GPP TS 23.502, the following actions are added, as shown in FIG. 8: [0168] SMF indicates that a modified GBR is to be allocated for one of the QCI flows (i.e., for one of the flows to which a GBR is allocated); [0169] AMF calculates the sum of the GBR to be modified and the GBR of the other flows already allocated for the network slice used by the PDU session to obtain a hypothetical total GBR. If this hypothetical total GBR exceeds UE-Slice-MBR for the network slice, AMF rejects the modification, e.g. with cause “Maximum data rate reached for the network slice” (or similar). It may inform SMF accordingly. On the other hand, if the hypothetical total GBR does not exceed UE-Slice-MBR, AMF may admit the session modification. Furthermore, latest after modification of the session, it updates its maintained value of the GBR allocated for the network slice such that it becomes the hypothetical total value.

[0170] In some example embodiments, AMF may reject only a part of the requested modification related to some of the flows of the session and admit the modification of other flows such that the hypothetical total GBR for the network slice for the subsriber does not exceed UE-Slice-MBR.

[0171] The action to be performed by NG-RAN in this case, is the same as that shown in FIG. 7.

[0172] Compared to the PDU session release procedure according to current FIG. 4.3.4.2-1: UE or network requested PDU Session Release for non-roaming and roaming with local breakout from 3GPP TS 23.502, the following actions are added, as shown in FIG. 9:

[0173] A session release may be considered as a session modification such that the new GBR of the session is equal to 0 (i.e. the requested GBR difference of the session is equal to the current GBR of the session). Thus, a detailed description of FIG. 9 is omitted and it is referred to the description of FIG. 8 instead.

[0174] However, in some example embodiments, AMF may omit the check if the hypothetical total GBR exceeds the UE-slice-MBR. Since a session release reduces the total GBR, the condition must be always fulfilled if the condition was fulfilled before session release (unless UE-slice-MBR was modified in the meantime).

[0175] In some example embodiments, NG RAN may perform the actions performed by AMF according to FIGS. 7 to 9 (PDU session establishment/modification/release). RAN may be informed on the GBRs by the following existing procedures: [0176] 1. Step 12 of FIG. 4.3.2.2.1-1 of 3GPP TS 23.502: UE-requested PDU Session Establishment for non-roaming and roaming with local breakout; and [0177] 2. Step 4 of FIG. 4.3.3.2-1 of 3GPP TS 23.502: UE or network requested PDU Session Modification (for non-roaming and roaming with local breakout).

[0178] FIG. 10 shows an apparatus according to an embodiment of the invention. The apparatus may be a data repository, such as an UDM, UDR, or HLR, or an element thereof. FIG. 11 shows a method according to an embodiment of the invention. The apparatus according to FIG. 10 may perform the method of FIG. 11 but is not limited to this method. The method of FIG. 11 may be performed by the apparatus of FIG. 10 but is not limited to being performed by this apparatus.

[0179] The apparatus comprises means for checking 10, means for retrieving 20, and means for providing 30. The means for checking 10, means for retrieving 20, and means for providing 30 may be a checking means, retrieving means, and providing means, respectively. The means for checking 10, means for retrieving 20, and means for providing 30 may be a checker, retriever, and a provider, respectively. The means for checking 10, means for retrieving 20, and means for providing 30 may be a checking processor, retrieving processor, and providing processor, respectively.

[0180] The means for checking 10 checks whether a request for subscription information for a subscriber is received (S10).

[0181] If the request for subscription information is received (S10=yes), the means for retrieving 20 retrieves a respective maximum data rate allowed for the subscriber for each of one or more network slices allowed for the subscriber (S20).

[0182] The means for providing 30 provides an indication of the respective maximum data rate for each of the one or more network slices allowed for the subscriber in response to the request (S30).

[0183] FIG. 12 shows an apparatus according to an embodiment of the invention. The apparatus may be a network function, such as an AMF, or an element thereof. FIG. 13 shows a method according to an embodiment of the invention. The apparatus according to FIG. 12 may perform the method of FIG. 13 but is not limited to this method. The method of FIG. 13 may be performed by the apparatus of FIG. 12 but is not limited to being performed by this apparatus.

[0184] The apparatus comprises means for supervising 120 and means for providing 130. The means for supervising 120 and means for providing 130 may be a supervising means and providing means, respectively. The means for supervising 120 and means for providing 130 may be a supervisor and a provider, respectively. The means means for supervising 120 and means for providing 130 may be a supervising processor and providing processor, respectively.

[0185] The means for supervising 120 supervises if an indication of a respective maximum data rate for a network slice allowed for the subscriber is received (S120).

[0186] If the indication of the respective maximum data rate is received (S120=yes), the means for providing 130 provides the indication of the maximum data rate for the network slice allowed for the subscriber as part of an establishment of a session of the subscriber for the first network slice (S130). For example, the means for providing 130 may provide the indication in response to the session setup request.

[0187] FIG. 14 shows an apparatus according to an embodiment of the invention. The apparatus may be an access network, such as a radio access network, or an element thereof, such as a eNB or gNB, or a component of such an element. FIG. 15 shows a method according to an embodiment of the invention. The apparatus according to FIG. 14 may perform the method of FIG. 15 but is not limited to this method. The method of FIG. 15 may be performed by the apparatus of FIG. 14 but is not limited to being performed by this apparatus.

[0188] The apparatus comprises means for checking 210, means for monitoring 220, and means for inhibiting 230. The means for checking 210, means for monitoring 220, and means for inhibiting 230 may be a checking means, monitoring means, and inhibiting means, respectively. The means for checking 210, means for monitoring 220, and means for inhibiting 230 may be a checker, monitor, and an inhibitor, respectively. The means for checking 210, means for monitoring 220, and means for inhibiting 230 may be a checking processor, monitoring processor, and inhibiting processor, respectively.

[0189] The means for checking 210 checks whether a maximum data rate for a subscriber for a network slice is received (S210).

[0190] If the maximum data rate for the subscriber for the network slice is received (S210=yes), the means for monitoring 220 monitors whether a hypothetical total data rate of all flows of the subscriber for the network slice would exceed the maximum data rate for the subscriber for the network slice if (=assuming that) a grant were provided for the subscriber (S220). The grant is for transmitting data for the subscriber for packets belonging to the network slice.

[0191] If the hypothetical total data rate of all flows of the subscriber for the network slice exceeded the maximum data rate of the network slice if the grant were provided (S220=yes), the means for inhibiting 230 inhibits providing the grant for the subscriber (S230).

[0192] FIG. 16 shows an apparatus according to an embodiment of the invention. The apparatus comprises at least one processor 810, at least one memory 820 including computer program code, and the at least one processor 810, with the at least one memory 820 and the computer program code, being arranged to cause the apparatus to at least perform at least one of the methods according to FIGS. 11, 13, and 15 and related description.

[0193] Some example embodiments may be employed in downlink only. Some example embodiments may be employed on uplink only. Some example embodiments may be employed in both downlink and uplink, wherein the respective maximum data rates of the UE for a network slice may be the same or different for downlink and uplink. Uplink and downlink may be treated separately from each other.

[0194] One piece of information may be transmitted in one or plural messages from one entity to another entity. Each of these messages may comprise further (different) pieces of information.

[0195] Names of network elements, network functions, protocols, and methods are based on current standards. In other versions or other technologies, the names of these network elements and/or network functions and/or protocols and/or methods may be different, as long as they provide a corresponding functionality. For example, instead of the UDM, a UDR or a HLR may store the maximum data rate of a subscriber for a network slice allowed for the subscriber. According to some example embodiments, even a database separate from UDM, UDR, or HLR (such as a dedicated database) may store the maximum data rate of a subscriber for a network slice allowed for the subscriber.

[0196] In some example embodiments, the maximum data rates of the subscriber for all the network slices allowed for the subscriber are stored, evaluated, and enforced. However, in some example embodiments, the maximum data rates of the subscriber for only a subset of all network slices allowed for the subscriber are stored, evaluated, and enforced. For example, OAM may not have provided such a maximum data rate for one or more of the allowed network slices.

[0197] The tables shown in FIGS. 4 and 5 are given as examples only. E.g., the sequence of columns, the sequence of rows, the headers, the units, etc. may be appropriately modified according to some example embodiments of the invention.

[0198] According to current 3GPP specifications, S-NSSAI is used to denote a network slice unambiguously, whereas NSSAI denotes a group of 8 slices. However, the invention is not limited to these denotations. A network slice may be defined by some other identity.

[0199] In the present application, a UE may be considered as the combination of a terminal (hardware) and a user. The terminal may be e.g. a mobile phone, a smart phone, a MTC device, a laptop etc. The user may be a human user or a machine (e.g. in MTC). The terms “user” and “subscriber” are to be considered synonymously.

[0200] If not otherwise stated or otherwise made clear from the context, the statement that two entities are different means that they perform different functions. It does not necessarily mean that they are based on different hardware. That is, each of the entities described in the present description may be based on a different hardware, or some or all of the entities may be based on the same hardware. It does not necessarily mean that they are based on different software. That is, each of the entities described in the present description may be based on different software, or some or all of the entities may be based on the same software. Each of the entities described in the present description may be deployed in the cloud.

[0201] According to the above description, it should thus be apparent that example embodiments of the present invention provide, for example, a repository function such as a UDM, or a component thereof, an apparatus embodying the same, a method for controlling and/or operating the same, and computer program(s) controlling and/or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s). According to the above description, it should thus be apparent that example embodiments of the present invention provide, for example, a network function such as a AMF, or a component thereof, an apparatus embodying the same, a method for controlling and/or operating the same, and computer program(s) controlling and/or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s). According to the above description, it should thus be apparent that example embodiments of the present invention provide, for example, an access network such as a RAN, or a component thereof (e.g. eNB or gNB), an apparatus embodying the same, a method for controlling and/or operating the same, and computer program(s) controlling and/or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s).

[0202] Implementations of any of the above described blocks, apparatuses, systems, techniques or methods include, as non-limiting examples, implementations as hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. Each of the entities described in the present description may be embodied in the cloud.

[0203] It is to be understood that what is described above is what is presently considered the preferred embodiments of the present invention. However, it should be noted that the description of the preferred embodiments is given by way of example only and that various modifications may be made without departing from the scope of the invention as defined by the appended claims.