WO2021254643A1 - Handling conditional policy control and charging rules associated with a packet forwarding control protocol session - Google Patents

Abstract

A method of operating a user plane function, UPF, layer of a network node in a core network of a telecommunication network can include receiving a message from a session management function, SMF, layer of the core network indicating a conditional policy control and charging, PCC, rule to be applied by the UPF during a packet forwarding control protocol, PFCP, session. The conditional PCC rule can include an action to be taken in response to a feature exceeding a threshold value. The method can further include, responsive to determining that the feature exceeds the threshold value, performing the action.

Description

HANDLING CONDITIONAL POLICY CONTROL AND CHARGING RULES ASSOCIATED WITH A PACKET FORWARDING CONTROL PROTOCOL

SESSION

TECHNICAL FIELD

[0001] The present disclosure relates generally communications and more specifically to handling traffic during a packet forwarding control protocol ("PFCP") session.

BACKGROUND

[0002] FIG. 1 illustrates an example of 5th Generation Core ("5GC") network architecture. In this example, the 5GC network includes a unified data repository ("UDR") 110, network exposure function ("NEF") 120, network data analytics function ("NWDAF") 130, application function ("AF") 140, policy control function ("PCF") 150, charging function ("CHF") 160, access and mobility management function ("AMF") 170, and session management function ("SMF") 180 all communicatively coupled to each other and a user plane function ("UPF") 190 communicatively coupled to the SMF 180.

[0003] The PCF layer 150 can support unified policy framework to govern network behavior. The PCF layer 150 can also provide a policy rule to a control plane function to enforce them. The PCF layer 150 can also access subscription information relevant for policy decisions in a unified data repository ("UDR") layer 110.

[0004] In some examples, the SMF 180 can support session establishment, modification, and release. In additional or alternative examples, the SMF 180 can support policy related functionalities like termination of interfaces towards PCF 150. In additional or alternative examples, the SMF 180 can support charging data collection, supporting charging interfaces, and control and coordination of charging data collection at the UPF 190.

[0005] Considering control and user plane split ("CUPS"), the SMF 180 controls the packet processing in the UPF 190 by establishing, modifying or deleting packet forwarding control protocol ("PFCP") Session contexts and by provisioning (i.e. adding, modifying or deleting) PDRs, FARs, QERs, URRs and/or BAR per PFCP session context, whereby an PFCP session context may correspond to an individual PDU session or a standalone PFCP session not tied to any PDU session.

[0006] The UPF 190 can support different functionality, for example, handling of user plane traffic, including packet inspection, packet routing and forwarding. In some examples, the UPF 190 can handle traffic usage reporting or quality of service ("QoS") handling for user plane (e.g. uplink ("UL")/downlink ("DL") rate enforcement).

[0007] Considering CUPS, the UPF 190, for every received packet, can identify the PCFP session for which the packet belongs to and, then, find the highest precedence packet detection rate ("PDR") where the packet is matching, among all the PDRs provisioned for this session by the SMF 180. The PDR matched will include relevant rule identifiers (e.g., forwarding action rule ("FAR"), QoS enforcement rule ("QER"), usage reporting rule ("URR"), and buffering action rule ("BAR")) to be applied.

[0008] In some examples, the PDR can include one unique FAR rule identifier. This FAR rule can include instructions related to how the packet shall be forwarded. The PDR can include zero, one, or more QER rule identifiers, which includes instructions related to the QoS enforcement of the traffic. The PDR can include zero, one, or more URR rule identifiers, which includes instructions related to traffic measurement and reporting. The PDR can include zero or one BAR rule identifier, which includes instructions on how to perform packet buffering.

SUMMARY

[0009] According to some embodiments, a method of operating a user plane function, UPF, layer of a network node in a core network of a telecommunication network is provided. The method includes receiving a message from a session management function, SMF, layer of the core network indicating a conditional policy control and charging, PCC, rule to be applied by the UPF during a packet forwarding control protocol, PFCP, session. The conditional PCC rule including an action to be taken in response to a feature exceeding a threshold value. The method further includes, responsive to determining that the feature exceeds the threshold value, performing the action.

[0010] According to some embodiments, a method of operating a core network node operating in a telecommunication network is provided. The method can include generating, by a policy control function, PCF, layer of the core network node, a conditional policy control and charging, PCC, rule associated with a packet forwarding control protocol, PFCP, session. The conditional PCC rule including an action to be taken in response to a feature exceeding a threshold value. The method can further include providing, by the PCF layer via a session management function, SMF, layer of the core network node, a message to a user plane function, UPF, layer of the core network node, the message requesting the UPF layer measure the feature.

[0011] According to other embodiments, a network node, computer program, and/or computer program product is provided for performing one of the above methods.

[0012] In various embodiments described herein, providing a UPF with conditional PCC rules allows the UPF to apply different rules based on detecting specific criteria. This can result in a faster network reaction to changes in traffic with less signaling due to less communication other 5GC nodes upon detecting a change in traffic. For example, allowing the UPF the freedom to apply different rules based on measured changes in traffic can allow for network automation without complex signaling loops among different 5GC node entities.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0014] FIG. 1 is a block diagram illustrating an example of a 5th generation core ("5GC") network architecture;

[0015] FIG. 2 is a table illustrating an example of user plane ("UP") function features in accordance with some embodiments; [0016] FIG. 3 is a table illustrating an example of information elements ("IEs") in accordance with some embodiments;

[0017] FIG. 4 is a table illustrating an example of a create packet detection rule ("PDR") IE features in accordance with some embodiments;

[0018] FIG. 5 is a table illustrating an example of a quality of service enforcement rule ("QER") IE features in accordance with some embodiments;

[0019] FIG. 6 is a table illustrating an example of a forwarding action rule ("FAR") IE features in accordance with some embodiments;

[0020] FIG. 7 is a signal flow diagram illustrating an example of a process for generating and handling conditional policy control and charging ("PCC") rules in accordance with some embodiments;

[0021] FIG. 8 is a block diagram illustrating an example of a communication device in accordance with some embodiments;

[0022] FIG. 9 is a block diagram illustrating an example of a radio access network ("RAN") node in accordance with some embodiments;

[0023] FIG. 10 is a block diagram illustrating an example of a core network ("CN") node in accordance with some embodiments;

[0024] FIG. 11 is a block diagram illustrating an example of a user plane function ("UPF") node in accordance with some embodiments;

[0025] FIG. 12 is a block diagram illustrating an example of a session management function ("SMF") node in accordance with some embodiments;

[0026] FIG. 13 is a block diagram illustrating an example of a policy control function ("PCF") node in accordance with some embodiments; and

[0027] FIGS. 14-18 are flow charts illustrating examples of processes performed by a network node in accordance with some embodiments.

DETAILED DESCRIPTION

[0028] Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

[0029] FIG. 1 illustrates an example of a 5th generation core ("5GC") network that includes various independent network entities (e.g., a unified data repository ("UDR") 110, network exposure function ("NEF") 120, network data analytics function ("NWDAF") 130, application function ("AF") 140, policy control function ("PCF") 150, charging function ("CHF") 160, access and mobility management function ("AMF") 170, session management function ("SMF") 180, and a user plane function ("UPF") 190) coupled together. However, in some 5GC networks, the network entities are layers included in one or more core network nodes. In this example, the UPF 190 can be connected to the SMF 180 via a N4 3GPP standard interface. The UPF 190 can receive, per PFCP session, the policy control and charging ("PCC") rules to be considered. The rules can include packet detection rules ("PDRs"), forwarding action rules ("FARs"), quality of service enforcement rules ("QERs"), usage reporting rules ("URRs"), and buffering action rules ("BARS").

[0030] In some examples, when an incoming packet is received at the UPF 190, the UPF 190 can evaluate the PDRs instructed for this packet forwarding control protocol ("PFCP") session and execute the rules linked to the associated PDRs. The SMF 180 can derive the rules to be instructed to UPF 190 from the policy rules received by PCF 150 or from static configuration. However, this can result in the UPF 190 strictly adhering to the set of rules that the SMF 180 commands, even if a significant traffic pattern change is detected by the UPF 190. The UPF 190 can detect significant traffic pattern changes including a considerable increase on the payload throughput traversing UPF 190 or a significant increase of traffic congestion events in the networks (e.g., increase of TCP retransmitted packets).

[0031] Reactiveness to network changing conditions (e.g., increase of payload throughput and/or increase on network congestion events) can be slow. In some examples, rules instructed by SMF 180 may need to be readjusted due to traffic pattern changes. The closed loop can span from the UPF/probes to the control plane ("CP") network functions ("NFs") (e.g., the SMF 180, PCF 150, and NWDAF 130) and back again to the UPF 190, where new rules are instructed. This closed loop includes non-negligible delay since the traffic pattern change happens until the mitigation action is applied.

[0032] The SMF 180 can take input from the PCF 150 regarding what traffic management policies to apply. However, these policies can be defined by the operator in an offline way. Therefore, they may not be optimal to adapt to changing traffic conditions.

[0033] Various embodiments herein improve upon the above processes by enabling the UPF 190 to receive, on per PCFP session, on top of the legacy N4 standardized rules, conditional rules that will only be considered if a measurable condition by UPF 190 is matched. Some embodiments herein describe changes to the Sx / N4 interfaces to enable use of the conditional rules.

[0034] In some embodiments, the SMF 180 forwards to the UPF 190, on per PFCP session, needed rules (PDRs, FARs, QERs and/or QeRs) and if any criteria needs to be fulfilled for any of these rules. In some examples, the criteria include something that the UPF 190 can measure. The UPF 190 can store, as part of user^'s PDU session context, the instructed rules together with any possible criteria linked to any of these rules. The UPF 190 can, during payload traffic processing, evaluate the criteria linked to a rule (e.g., a PDR, FAR, or QER). If a criteria is matched, the rule shall be applied. In some examples, the criteria is something measurable by UPF 190, therefore, the UPF 190 knows if the rule shall be applied or not (if not, the rules will not be considered).

[0035] In some embodiments, using conditional rules allow the UPF 190 to achieve the freedom to apply different set of rules based on a criteria, considering this criteria as something the UPF 190 can detect/measure. In additional or alternative embodiments, reactiveness to traffic pattern changes is faster, without bothering any other 5GC node entities, which also means less signaling is involved. In additional or alternative embodiments, using conditional rules allows network automation without the need of complex signaling loops among different 5GC node entities.

[0036] FIG. 8 is a block diagram illustrating elements of a communication device 800 (also referred to as a mobile terminal, a mobile communication terminal, a wireless device, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Communication device 800 may be provided). As shown, communication device 800 may include an antenna 807 and transceiver circuitry 801 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., also referred to as a RAN node) of a radio access network. Communication device 800 may also include processing circuitry 803 (also referred to as a processor) coupled to the transceiver circuitry, and memory circuitry 805 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 805 may include computer readable program code that when executed by the processing circuitry 803 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 803 may be defined to include memory so that separate memory circuitry is not required. Communication device 800 may also include an interface (such as a user interface) coupled with processing circuitry 803, and/or communication device UE may be incorporated in a vehicle.

[0037] As discussed herein, operations of communication device 800 may be performed by processing circuitry 803 and/or transceiver circuitry 801. For example, processing circuitry 803 may control transceiver circuitry 801 to transmit communications through transceiver circuitry 801 over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry 801 from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry 805, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 803, processing circuitry 803 performs respective operations. [0038] FIG. 9 is a block diagram illustrating elements of a radio access network ("RAN") node 900 (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts. (RAN node 900 may be provided). As shown, the RAN node 900 may include transceiver circuitry 901 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node 900 may include network interface circuitry 907 (also referred to as a network interface) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN. The RAN node 900 may also include processing circuitry 903 (also referred to as a processor) coupled to the transceiver circuitry, and memory circuitry 905 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 905 may include computer readable program code that when executed by the processing circuitry 903 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 903 may be defined to include memory so that a separate memory circuitry is not required.

[0039] As discussed herein, operations of the RAN node 900 may be performed by processing circuitry 903, network interface 907, and/or transceiver 901. For example, processing circuitry 903 may control transceiver 901 to transmit downlink communications through transceiver 901 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 901 from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry 903 may control network interface 907 to transmit communications through network interface 907 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 905, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 903, processing circuitry 903 performs respective operations. [0040] According to some other embodiments, a network node may be implemented as a core network CN node without a transceiver. In such embodiments, transmission to a wireless communication device UE may be initiated by the network node so that transmission to the wireless communication device UE is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating transmission may include transmitting through the transceiver.

[0041] FIG. 10 is a block diagram illustrating elements of a core network CN node 1000 (e.g., an SMF node, an AMF node, etc.) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. As shown, the CN node 1000 may include network interface circuitry 1007 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the RAN. The CN node 1000 may also include a processing circuitry 1003 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 1005 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 1005 may include computer readable program code that when executed by the processing circuitry 1003 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 1003 may be defined to include memory so that a separate memory circuitry is not required.

[0042] As discussed herein, operations of the CN node 1000 may be performed by processing circuitry 1003 and/or network interface circuitry 1007. For example, processing circuitry 1003 may control network interface circuitry 1007 to transmit communications through network interface circuitry 1007 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 1005, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1003, processing circuitry 1003 performs respective operations. [0043] FIG. 11 is a block diagram illustrating elements of a UPF node 1100 (e.g., UPF 190 of FIG. 1) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. As shown, the UPF node 1100 may include network interface circuitry 1107 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the RAN. The UPF node 1100 may also include a processing circuitry 1103 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 1105 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 1105 may include computer readable program code that when executed by the processing circuitry 1103 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 1103 may be defined to include memory so that a separate memory circuitry is not required.

[0044] As discussed herein, operations of the UPF node 1100 may be performed by processing circuitry 1103 and/or network interface circuitry 1107. For example, processing circuitry 1103 may control network interface circuitry 1107 to transmit communications through network interface circuitry 1107 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 1105, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1103, processing circuitry 1103 performs respective operations.

[0045] FIG. 12 is a block diagram illustrating elements of a SMF node 1200 (e.g., SMF 180 of FIG. 1) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. As shown, the SMF node 1200 may include network interface circuitry 1207 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the RAN. The SMF node 1200 may also include a processing circuitry 1203 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 1205 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 1205 may include computer readable program code that when executed by the processing circuitry 1203 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 1203 may be defined to include memory so that a separate memory circuitry is not required.

[0046] As discussed herein, operations of the SMF node 1200 may be performed by processing circuitry 1203 and/or network interface circuitry 1207. For example, processing circuitry 1203 may control network interface circuitry 1207 to transmit communications through network interface circuitry 1207 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 1205, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1203, processing circuitry 1203 performs respective operations.

[0047] FIG. 13 is a block diagram illustrating elements of a PCF node 1300 (e.g., PCF 150 of FIG. 1) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. As shown, the PCF node 1300 may include network interface circuitry 1307 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the RAN. The PCF node 1300 may also include a processing circuitry 1303 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 1305 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 1305 may include computer readable program code that when executed by the processing circuitry 1303 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 1303 may be defined to include memory so that a separate memory circuitry is not required.

[0048] As discussed herein, operations of the PCF node 1300 may be performed by processing circuitry 1303 and/or network interface circuitry 1307. For example, processing circuitry 1303 may control network interface circuitry 1307 to transmit communications through network interface circuitry 1307 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 1305, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1303, processing circuitry 1303 performs respective operations.

[0049] In some embodiments, for each PFCP session, a UPF has a list of PDRs that will be evaluated to find the one matched on a per incoming packet basis. The PDR matched will determine which of the applicable enforcement rules (e.g., FAR, QERs, URRs and BAR) are to be applied. In additional or alternative embodiments, in addition to the PDRs and the enforcement rules, the UPF will have some PDRs and enforcement rules that will only be applicable if a criteria is matched. In some examples, if the UPF is provisioned with a PDR that is linked with a criteria, the PDR will only be evaluated if the criteria is matched. In additional or alternative examples, if the UPF is provisioned with a PDR for a particular PFCP session and this PDR has a FAR or QER linked with a criteria, the PDR will be always evaluated (as it does not have a criteria) but both the FAR1 and QER1 rules will be considered only if the criteria is matched. Therefore, a criteria can be linked to a PDR, a FAR, a QER, a URR and/or a BAR and the rule will only be considered if the criteria is matched.

[0050] FIG. 2 is a table of example user plane ("UP") functions that can be used in accordance with some embodiments. In this example, a new UP feature called criteria for rules ("CFRU") is added. The CFRU can be reported during a PFCP association procedure between a UPF and a SMF to allow the SMF to know which UPFs support conditional rules, which can influence UPF selection.

[0051] FIG. 3 is a table of example information elements ("IEs") that can be used in accordance with some embodiments. In some embodiments, a new PFCP node procedure can be used so that the SMF can request the UPF measure a metric associated with the conditional rule so that when the conditional rule is evaluated measurement information is available. In some examples, this is a global metric that includes more than one UPF. For example, a criteria for a conditional rule can indicate that the conditional rule is applicable only if the total UPF throughput is higher than a threshold. Then, when this conditional rule is evaluated, the total UPF throughput may be available so that the applicability of the rule can be confirmed immediately. In additional or alternative embodiments, a new metric activation node procedure can be used. The metric activation node procedure can specify the metric that the UPF has to measure at a node level. In this example, a UPF will reply successfully if it is able to measure the metric or unsuccessfully if it is not able to measure the metric.

[0052] In additional or alternative embodiments, the SMF can indicate if a metric is only applicable on per PFCP session basis. For example, a criteria for a conditional rule can indicate that the conditional rule is applicable only if the packet lost rate for this session is higher than a threshold. Then, when the conditional rule is evaluated, the packet lost rate for this PFCP session may be available, so that the applicability of the rule can be confirmed immediately. In additional or alternative embodiments, this can be specified in a PFCP session establishment procedure and in a PFCP session modification procedure accordingly. In this example, a UPF will reply successfully if it is able to measure that metric or with an error if not able to measure that metric.

[0053] In some embodiments, if a criteria is to be linked to a PDR, a create PDR IE within a PFCP session establishment request can be modified as indicated in the table in FIG. 4. FIG. 4 is a table of an example IE for creating a PDR that can have an associated criteria (making it a conditional PDR). The create PDR IE can include a new Criteria IE. The same modifications can be made to IEs associated with PFCP session modification request procedures. If there are several PDRs with a criteria, the precedence can establish the priority of the evaluation as per normal PDRs.

[0054] In additional or alternative embodiments, if a criteria is to be linked to a QER, a create QER IE within a PFCP session establishment request can be modified as indicated in FIG. 5. FIG. 5 is a table of an example IE for creating a QER that can have an associated criteria (making it a conditional QER). The create QER IE can include a new criteria IE and QER criteria precedence. The same modifications can be made to IEs associated with PFCP session modification request procedures. If there are several QERs with criteria in a PFCP session, the QER criteria precedence can provide the priority in which the different QERs with criteria will be evaluated.

[0055] In additional or alternative embodiments, if a criteria is to be linked to a FAR rule, a create FAR IE within a PFCP session establishment request can be modified as indicated in FIG. 6. FIG. 6 is a table of an example IE for creating a FAR that can have an associated criteria (making it a conditional FAR). The create FAR IE can include a new criteria IE and FAR criteria precedence. The same modifications can be made to IEs associated with PFCP session modification request procedures. In additional or alternative embodiments, a PDR many no longer have only have a unique FAR. In some examples, a PDR can have a unique normal FAR (a FAR without a criteria) and one or more FARs with criteria, and FAR criteria precedence can provide the priority of evaluation. In additional or alternative examples, FARs with criteria may be evaluated prior to the unique and normal FAR. In additional or alternative examples, when any of the FAR criteria is fulfilled, then no more FARs will be evaluated. If none of the FAR with criteria are fulfilled, then the normal FAR will apply.

[0056] In some embodiments, similar to the IEs illustrated in FIGS. 3- 6, criteria (and/or a precedence) can be linked to any of the PCC rules (e.g., URRs or BARs) and also to predefined rules, so that the activation or deactivation of a predefined rule is conditioned to a criteria.

[0057] In additional or alternative embodiments, the new criteria IE can be provided with any of the following information: a metric, metric-value, a relation; and/or a metric-dimension. In some examples, the metric information can indicate what the UPF should measure (e.g., a throughput, a round trip time ("RTT"), a packet loss, a retransmission, and/or a number of active PFCP sessions). The metric-value information can indicate a value of the metric that can be used as a threshold value for considering if the rule should be applied or not. The relation information can indicate if the metric value has to be lower / greater / equal to metric measured in order for the rule to be triggered. The metric-dimension information can indicate if this metric is a node level metric or a PFCP session level metric. [0058] In some examples, a new criteria IE can be part of a conditional PDR. The criteria IE can include a metric of RTT, a metric value of 50 ms, a relation of greater, and a metric-dimension that indicates the metric is a PFCP session metric. In this example, the PDR will only be evaluated if the RTT measured for the payload belonging to that PFCP session is greater than 50ms.

[0059] In another example, a network operator can want to start taking some actions over payload traffic considering different criteria. One of the criteria can indicate that tethering traffic is allowed but, when overpassing a first threshold (on global UPF traffic), no tethering traffic shall be allowed. Another of the criteria can indicate that video streaming videos can be watched at any quality but, when overpassing a second threshold (on global UPF traffic), the traffic will be sent to a Service Chain where there will be a Service Function to achieve ABR shaping, decreasing the bandwidth consumption for ABR videos. Another of the criteria can indicate that gaming traffic needs more than acceptable RTT and if it is detected that this metric is overpassing a third threshold, the traffic shall be routed considering a higher QoS flow identifier ("QFI").

[0060] In this example, several rules may be provided to the UPF. First, a PDR can be provided to the UPF to match all tethering traffic, that will be provisioned. A criteria IE of the PDR can include metric = throughput; metric value = the first threshold; relation = greater; and metric-dimension = node metric. Accordingly, this conditional PDR will only be considered for traffic matching if the criteria is matched, that is, if the throughput traversing the UPF is over the first threshold. This PDR will be linked to a QER to drop the tethering packets and, then, if PDR is matched and criteria fulfilled, the QER will apply.

[0061] Furthermore, a normal PDR can be provided to the UPF to match video streaming videos traffic that will be linked to a FAR. A criteria IE of the FAR can include metric = throughput; metric value = the second threshold; relation = greater; and metric-dimension = node metric. Accordingly, this FAR rule will only be considered if the criteria is matched. When the criteria is matched, the FAR will apply and the FAR will have a forwarding policy identifier that will point to a service chain where an available bit rate ("ABR") shaping SF will be present. As stated above, this PDR to match video streaming videos must have a normal FAR to be applied in case the FAR with the criteria does not apply

[0062] Furthermore, a normal PDR can be provided to the UPF to match gaming traffic that will be linked to a QER. A criteria IE of the QER can include metric = RTT, metric value = the third threshold, relation = greater, and metric-dimension = PFCP session metric. Accordingly, this QER rule will only be considered if the criteria is matched. When the criteria is matched, the QER will apply and a higher QFI will be considered for this kind of traffic.

[0063] FIG. 7 is a signal flow diagram illustrating the example above. Prior to the illustrated operations, at a PCFP association procedure between UPF 190 and SMF 180, the UPF 190 can indicate it supports the new CFRU.

[0064] At operation 705, a UE 702 can trigger a PDU session establishment by transmitting a PDU session establishment request to the AMF 170. The AMF 170 can select SMF 180 from a plurality of SMFs and transmit a signal via an Nsmf interface to the SMF 180 requesting creation of the PDU session. In some embodiments, additional signaling messages may be involved in the PDU session establishment procedure.

[0065] At operation 715, the SMF 180 transmits a signal to the PCF 150 via a Npcf interface including a session management policy control request that triggers a new metric activation node procedure to instruct the UPF 190 that throughput metric at node level needs to be measured.

[0066] At operation 720, the PCF 150 decides to retrieve the subscriber policies from the UDR 110.

[0067] At operation 725, the PCF 150 transmits a data management query to the UDR 110 via a Nudr interface.

[0068] At operation 730, the UDR 110 returns the subscriber PCC rules. The subscriber PCC rules can include both non-conditional (legacy) rules and conditional rules.

[0069] At operation 735, the UDR 110 transmits a data management response to the PCF 150 via the Nudr interface. [0070] At operation 740, the PCF 150 generates the PCC rules for the PDU session including conditional PCC rules (as well as any non-conditional rules).

[0071] At operation 745, the PCF 150 transmits the session management policy control response to the SMF 180 via the Npcf interface.

[0072] At operation 750 the SMF 180 selects the UPF 190 from multiple UPFs and transmit a PFCP session establishment request via a N4 interface. The PFCP session establishment request can include the corresponding PDRs, FARs, QERs and URRs, and the needed criteria linked to relevant conditional rules, according to the example above.

[0073] At operation 755, the UPF 190 responds to the PFCP session establish request by transmitting a PFCP session establishment response to the SMF 180 via the N4 interface. A successful response can indicate that the UPF 190 has accepted all of the rules including the conditional rules.

[0074] Operations 760 and 770 can occur at any time during the PFCP session. At operation 760, a payload for the session is received at the UPF 190 from the UE 702 and the UPF 190 starts measuring the metric it was requested to measure by the SMF 180. In this example, the payload includes application tethered traffic. The UPF 190 may measure the metric either at UPF node level or at a session level based on the metric-level that was provided.

[0075] At operation 765, the UPF 190 measures throughput and applies conditional rules triggered based on measured metrics. In this example, the UPF 190 measures the throughput on a per global UPF basis and if the throughput exceeds 20 Gbps, the UPF 190 drops the tethered traffic.

[0076] At operation 770 a payload for the session is received at the UPF 190 from the UE 702 and the UPF 190 starts measuring the metric it was requested to measure by the SMF 180. In this example, the payload includes application traffic associated with a video streaming provider. The UPF 190 may measure the metric either at UPF node level or at a session level based on the metric-level that was provided.

[0077] At operation 775, the UPF 190 measures throughput and takes action based on a feature (or metric) exceeding a threshold value. In this example, the UPF 190 measures throughput on a per global UPF basis and if the throughput exceeds 10 Gbps, the UPF 190 forces the video streaming provider to adjust quality.

[0078] Accordingly, the example processes illustrated in FIG. 7 allow traffic management in the 5GC network using conditional rules that the UPF 190 is able to apply.

[0079] Operations of a user plane function ("UPF") layer will now be discussed with reference to the flow charts of FIGS. 14-15 according to some embodiments of inventive concepts. FIGS. 14-15 will be described below as being performed by UPF node 1100 (implemented using the structure of the block diagram of FIG. 11). For example, modules may be stored in memory 1105 of FIG. 11, and these modules may provide instructions so that when the instructions of a module are executed by respective UPF processing circuitry 1103, processing circuitry 1103 performs respective operations of the flow charts. However, in some embodiments, the operations of FIGS. 14- 15 could be performed by any suitable layer of a core network node.

[0080] FIG. 14 is a flow chart illustrating an example of process performed by a UPF layer or UPF node for handling conditional PCC rules.

[0081] At block 1410, processing circuitry 1103 transmits, via network interface 1107, a message to a SMF (e.g. an independent SMF or a SMF layer of a core network node). In some embodiments, the message indicates that the UPF 1100 is capable of using conditional PCC rules.

[0082] At block 1420, processing circuitry 1103 receives, via network interface 1107, a message from the SMF requesting the UPF measure a feature (or metric) across multiple PFCP sessions. The feature can include any measurable metric associated with network traffic. Although FIG. 14 illustrates the feature being measured across multiple PFCP sessions including the PFCP session, in some embodiments the feature is measured at the node level. For example, the feature can include a throughput metric at the UPF node level.

[0083] At block 1430, processing circuitry 1103 receives, via network interface 1107, a message from the SMF indicating a conditional PCC rule to be applied by the PCF (e.g. an independent PCF or a PCF layer of a core network node) during a PFCP session. In some embodiments, the conditional PCC rule includes an action to be taken in response to a feature (or metric) exceeding a threshold value. In additional or alternative embodiments, the conditional PCC rule includes a PDR, a FAR, a BAR, a QER, or a URR.

[0084] At block 1440, processing circuitry 1103 stores the conditional PCC rule as part of a PDU session context associated with a user of the PFCP session.

[0085] At block 1450, processing circuitry 1103 performs an action associated with the conditional rule. In some embodiments, the action is performed in response to the determining that the feature exceeds the threshold value. In additional or alternative embodiments, the action includes adjusting traffic during the PFCP session by controlling a resource allocated to the PFCP session.

[0086] FIG. 15 is a flow chart illustrating an example of additional processes performed by a UPF layer or UPF node for handling conditional PCC rules. At block 1510, processing circuitry 1103 receives, via network interface 1107, a PFCP session establishment request message from the SMF. At block 1520, processing circuitry 1103 transmits, via network interface 1107, a PFCP session establishment response message to the SMF. At block 1525, processing circuitry 1103 establishes the PFCP session. At block 1530, processing circuitry 1103 measures a feature associated with the conditional rule. At block 1540, processing circuitry 1103 determines that the feature exceeds a threshold value associated with the conditional PCC rule.

[0087] In some embodiments, the UPF node 1100 is a part of a CN node 1000 that includes a UPF layer and a SMF layer. In additional or alternative embodiments, the telecommunication network is a new radio ("NR") network.

[0088] Various operations of FIGS. 14-15 may be optional with respect to some embodiments of UPF nodes/layers, core network nodes, and related methods. Regarding methods of some embodiments, for example, operations of blocks 1410 and 1420 of FIG. 14 and blocks 1510, 1520, 1525, 1530, and 1540 of FIG. 15 may be optional.

[0089] Operations of a core network will now be discussed with reference to the flow charts of FIGS. 16-18 according to some embodiments of inventive concepts. FIGS. 16-18 will be described below as being performed by a single CN node 1000 (implemented using the structure of the block diagram of FIG. 10). For example, modules may be stored in memory 1005 of FIG. 10, and these modules may provide instructions so that when the instructions of a module are executed by respective CN processing circuitry 1003, processing circuitry 1003 performs respective operations of the flow charts. However, in some embodiments, the operations of FIGS. 16- 18 could be performed by any suitable layers of any number of independent core network nodes.

[0090] FIG.16 is a flow chart illustrating examples of processes for operating a core network node in accordance with some embodiments. At block 1610, processing circuitry 1003 provides, by a UPF, an indication that the UPF is capable of using conditional PCC rules.

[0091] At block 1620, processing circuitry 1003 generates, by a PCF, a conditional PCC rule. In some embodiments, the conditional PCC rule is associated with a PFCP session and includes an action to be taken in response to a feature exceeding a threshold value. In some embodiments, the feature includes a throughput metric at a node level. In additional or alternative embodiments, the feature includes a session metric specific to the PFCP session. In additional or alternative embodiments, the conditional PCC rule includes a PDR, a FAR, a BAR, a QER, or a URR.

[0092] At block 1630, processing circuitry 1003 requests that the UPF measures the feature. In some embodiments, the request is provided by a PCF layer via a SMF layer.

[0093] FIG. 17 is a flow chart illustrating examples of additional processes for operating a core network node in accordance with some embodiments. At block 1740, processing circuitry 1003 measures, by the UPF, the feature. At block 1750, processing circuitry 1003 provides, by the UPF, measurements of the feature to the PCF. At block 1760, processing circuitry 1003 determines, by the PCF, that the feature exceeds the threshold value. At block 1770, processing circuitry 1003 performs, by the PCF, the action. In some embodiments, the action is performed in response to determining that the feature exceeds the threshold value. In additional or alternative embodiments, the action includes adjusting traffic during the PFCP session by controlling a resource allocated to the PFCP session.

[0094] FIG. 18 is a flow chart illustrating examples of additional or alternative processes for operating a core network node in accordance with some embodiments. At block 1840, processing circuitry 1003 provides, by the PCF, the conditional PCC rule to the UPF. At block 1850, processing circuitry 1003 measures, by the UPF, the feature. At block 1860, processing circuitry 1003 determines, by the UPF, that the feature exceeds the threshold value. At block 1870, processing circuitry 1003 performs, by the UPF, the action. In some embodiments, the action is performed in response to determining that the feature exceeds the threshold value. In additional or alternative embodiments, the action includes adjusting traffic during the PFCP session by controlling a resource allocated to the PFCP session.

[0095] In some embodiments, the UPF layer, SMF layer, and PCF layer are part of a single CN node. In additional or alternative embodiments, one or more of the UPF layer, SMF layer, and PCF layer are independent CN nodes of a common core network.

[0096] Various operations of FIGS. 16-18 may be optional with respect to some embodiments of core network nodes and related methods. Regarding method of some embodiments, for example, operations of block 1610 of FIG. 16, blocks 1740, 1750, 1760, and 1770 of FIG. 17, and blocks 1840, 1850, 1860, and 1870 of FIG. 18 may be optional.

[0097] Explanations for abbreviations from the above disclosure are provided below.

Abbreviation Explanation lx RTT CDMA2000 lx Radio Transmission Technology

3GPP 3rd Generation Partnership Project

5G 5th Generation

5GC Fifth Generation Core

ABS Almost Blank Subframe

AMF Access and Mobility Management Function ARQ Automatic Repeat Request

ARR Analytics Reporting Rule

AWGN Additive White Gaussian Noise

BAR Buffering Action Rule

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Control Plane

CPICH Common Pilot Channel

CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CQI Channel Quality information

CUPS Control User Plane Separation

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FAR Forwarding Action Rule

FDD Frequency Division Duplex

FFS For Further Study

GERAN GSM EDGE Radio Access Network gNB Base station in NR

GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

LOS Line of Sight

LPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MBMS Multimedia Broadcast Multicast Services

MBSFN Multimedia Broadcast multicast service Single Frequency

Network MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NEF Network Exposure Function

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

OCNG OFDMA Channel Noise Generator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PCF Policy Control Function

PDR Packet Detection Rule

PFCP Packet Forwarding Control Protocol

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel

PLMN Public Land Mobile Network PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

QER QoS Enforcement Rule

QoE Quality of Experience

RAN Radio Access Network

RAT Radio Access Technology

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR

Reference Signal Received Power

RSRQ Reference Signal Received Quality OR

Reference Symbol Received Quality RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SMF Session Management Function

SNR Signal to Noise Ratio

SON Self Optimized Network

SS Synchronization Signal

SSS Secondary Synchronization Signal

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UDM Unified Data Management

UE User Equipment

UL Uplink

UMTS Universal Mobile Telecommunication System

UPF User Plane Function

URR Usage Reporting Rule

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

UTRA Universal Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

WCDMA Wide CDMA

WLAN Wide Local Area Network [0098] Some references include

3GPP TS 29.244 Interface between the Control Plane and the User Plane nodes

[0099] Additional explanation is provided below.

[0100] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0101] The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

[0102] Further definitions and embodiments are discussed below.

[0103] In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0104] When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" (abbreviated "/") includes any and all combinations of one or more of the associated listed items.

[0105] It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

[0106] As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.

[0107] Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

[0108] These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof.

[0109] It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0110] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims

1. A method of operating a user plane function, UPF, layer of a network node in a core network of a telecommunication network, the method comprising: receiving (1430) a message from a session management function, SMF, layer of the core network indicating a conditional policy control and charging, PCC, rule to be applied by the UPF layer during a packet forwarding control protocol, PFCP, session, the conditional PCC rule comprising an action to be taken in response to a feature exceeding a threshold value; and responsive to determining that the feature exceeds the threshold value, performing (1450) the action.

2. The method of Claim 1, wherein receiving the message comprises receiving (1510) a PFCP session establishment request message, the method further comprising: responsive to receiving the PFCP session establishment request message, transmitting (1520) a PFCP session establishment response message to the SMF layer; responsive to receiving the PFCP session establishment request message, establishing (1525) the PFCP session; responsive to establishing the PFCP session, measuring (1530) the feature; and determining (1540), during the PFCP session, that the feature exceeds the threshold value.

3. The method of any of Claims 1-2, wherein the message is a first message, the method further comprising: receiving (1420) a second message, prior to receiving the first message, from the SMF layer requesting the UPF layer measure the feature across multiple PFCP sessions including the PFCP session.

4. The method of any of Claims 1-3, wherein the feature comprises a throughput metric at a network node level.

5. The method of any of Claims 1-3, wherein the feature comprises a session metric specific to the PFCP session.

6. The method of any of Claims 1-5, further comprising: storing (1440) the conditional PCC rule as part of a protocol data unit, PDU, session context associated with a user of the PFCP session.

7. The method of any of Claims 1-6, wherein the conditional PCC rule comprises at least one of: a packet detection rule, PDR, a forwarding action rule, FAR, a buffering action rule, BAR, a quality of service enforcement rule, QER, or a usage reporting rule, URR.

8. The method of any of Claims 1-7, wherein the message is a first message, the method further comprising: transmitting (1410), prior to receiving the first message, a second message to the SMF layer indicating that the UPF is capable of using conditional PCC rules during a PFCP session.

9. The method of any of Claims 1-8, wherein performing the action comprises adjusting traffic during the PFCP session by controlling a resource allocated to the PFCP session.

10. The method of any of Claims 1-9, wherein the network node is a core network node comprising the UPF layer and the SMF layer, and wherein the telecommunication network is a new radio, NR, network.

11. A user plane function, UPF, layer of a network node (1000, 1100) in a core network of a telecommunication network, the network node comprising: processing circuitry (1003, 1103); and memory (1005, 1105) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the UPF layer of the network node to perform operations, the operations comprising: receiving (1430) a message from a session management function, SMF, layer of the core network indicating a conditional policy control and charging, PCC, rule to be applied by the UPF during a packet forwarding control protocol, PFCP, session, the conditional PCC rule comprising an action to be taken in response to a feature exceeding a threshold value; and responsive to determining that the feature exceeds the threshold value, performing (1450) the action.

12. The UPF layer of Claim 11, wherein receiving the message comprises receiving (1510) a PFCP session establishment request message, the operations further comprising: responsive to receiving the PFCP session establishment request message, transmitting (1520) a PFCP session establishment response message to the SMF layer; responsive to receiving the PFCP session establishment request message, establishing (1525) the PFCP session; responsive to establishing the PFCP session, measuring (1530) the feature; and determining (1540), during the PFCP session, that the feature exceeds the threshold value.

13. The UPF layer of any of Claims 11-12, wherein the message is a first message, the operations further comprising: receiving (1420) a second message, prior to receiving the first message, from the SMF layer requesting the UPF layer measure the feature across multiple PFCP sessions including the PFCP session.

14. The UPF layer of any of Claims 11-13, wherein the feature comprises a throughput metric at a network node level.

15. The UPF layer of any of Claims 11-13, wherein the feature comprises a session metric specific to the PFCP session.

16. The UPF layer of any of Claims 11-15, further comprising: storing (1440) the conditional PCC rule as part of a protocol data unit, PDU, session context associated with a user of the PFCP session.

17. The UPF layer of any of Claims 11-16, wherein the conditional PCC rule comprises at least one of: a packet detection rule, PDR, a forwarding action rule, FAR, a buffering action rule, BAR, a quality of service enforcement rule, QER, or a usage reporting rule, URR.

18. The UPF layer of any of Claims 11-17, wherein the message is a first message, the operations further comprising: transmitting (1410), prior to receiving the first message, a second message to the SMF layer indicating that the UPF is capable of using conditional PCC rules during a PFCP session.

19. The UPF layer of any of Claims 11-18, wherein performing the action comprises adjusting traffic during the PFCP session by controlling a resource allocated to the PFCP session.

20. The UPF layer of any of Claims 11-19, wherein the network node is a core network node comprising the UPF layer and the SMF layer, and wherein the telecommunication network is a new radio, NR, network.

21. A user plane function, UPF, layer of a network node (1000, 1100) in a core network of a telecommunication network, the UPF layer adapted to perform operations, the operations comprising: receiving (1430) a message from a session management function, SMF, layer of the core network indicating a conditional policy control and charging, PCC, rule to be applied by the UPF during a packet forwarding control protocol, PFCP, session, the conditional PCC rule comprising an action to be taken in response to a feature exceeding a threshold value; and responsive to determining that the feature exceeds the threshold value, performing (1450) the action.

22. The UPF layer of the network node of Claim 21 adapted to perform according to any of Claims 2-10.

23. A computer program comprising program code to be executed by processing circuitry (1003, 1103) of a user plane function, UPF, layer of a network node (1000, 1100) in a core network of a telecommunication network, whereby execution of the program code causes the UPF layer of the network node to perform operations, the operations comprising: receiving (1430) a message from a session management function, SMF, layer of the core network indicating a conditional policy control and charging, PCC, rule to be applied by the UPF during a packet forwarding control protocol, PFCP, session, the conditional PCC rule comprising an action to be taken in response to a feature exceeding a threshold value; and responsive to determining that the feature exceeds the threshold value, performing (1450) the action.

24. The computer program of Claim 23 whereby execution of the program code causes the UPF layer of the network node to perform operations according to any of Claims 2-10.

25. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1003, 1103) of a user plane function, UPF, layer of a network node (1000, 1100) in a core network of a telecommunication network, whereby execution of the program code causes the UPF layer of the network node to perform operations, the operations comprising: receiving (1430) a message from a session management function, SMF, layer of the core network indicating a conditional policy control and charging, PCC, rule to be applied by the UPF during a packet forwarding control protocol, PFCP, session, the conditional PCC rule comprising an action to be taken in response to a feature exceeding a threshold value; and responsive to determining that the feature exceeds the threshold value, performing (1450) the action.

26. The computer program product of Claim 25, whereby execution of the program code causes the UPF layer of the network node to perform operations according to any of Claims 2-10.

27. A method of operating a core network node operating in a telecommunication network, the method comprising: generating (1620), by a policy control function, PCF, layer of the core network node, a conditional policy control and charging, PCC, rule associated with a packet forwarding control protocol, PFCP, session, the conditional PCC rule comprising an action to be taken in response to a feature exceeding a threshold value; and providing (1630), by the PCF layer via a session management function, SMF, layer of the core network node, a message to a user plane function, UPF, layer of the core network node, the message requesting the UPF layer measure the feature.

28. The method of Claim 27, further comprising: measuring (1740), by the UPF layer, the feature; providing (1750), by the UPF layer, measurements of the feature to the PCF layer via the SMF layer; determining (1760), by the PCF layer, that the feature exceeds the threshold value; and responsive to determining that the feature exceeds the threshold value, performing (1770), by the PCF layer, the action.

29. The method of Claim 28, further comprising: providing (1840), by the PCF layer via the SMF layer, the conditional PCC rule to the UPF layer; measuring (1850), by the UPF layer, the feature; determining (1860), by the UPF layer, that the feature exceeds the threshold value; and responsive to determining that the feature exceeds the threshold value, performing (1870), by the UPF layer, the action.

30. The method of any of Claims 27-29, wherein the feature comprises a throughput metric at a node level.

31. The method of any of Claims 27-29, wherein the feature comprises a session metric specific to the PFCP session.

32. The method of any of Claims 27-31, wherein the conditional PCC rule comprises at least one of: a packet detection rule, PDR, a forwarding action rule, FAR, a buffering action rule, BAR, a quality of service enforcement rule, QER, or a usage reporting rule, URR.

33. The method of any of Claims 27-32, wherein the message is a first message, the method further comprising: providing (1910), by the UPF layer, a second message to the SMF layer indicating that the UPF is capable of using conditional PCC rules during a PFCP session.

34. The method of any of Claims 27-33, wherein performing the action comprises adjusting traffic during the PFCP session by controlling a resource allocated to the PFCP session.

35. A core network node (1000) in a telecommunication network, the core network node comprising: processing circuitry (1003); and memory (1005) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the core network node to perform operations, the operations comprising: generating (1620), by a policy control function, PCF, layer of the core network node, a conditional policy control and charging, PCC, rule associated with a packet forwarding control protocol, PFCP, session, the conditional PCC rule comprising an action to be taken in response to a feature exceeding a threshold value; and providing (1630), by the PCF layer via a session management function, SMF, layer of the core network node, a message to a user plane function, UPF, layer of the core network node, the message requesting the UPF layer measure the feature.

36. The core network of Claim 35, further comprising: measuring (1740), by the UPF layer, the feature; providing (1750), by the UPF layer, measurements of the feature to the PCF layer via the SMF layer; determining (1760), by the PCF layer, that the feature exceeds the threshold value; and responsive to determining that the feature exceeds the threshold value, performing (1770), by the PCF layer, the action.

37. The core network of Claim 36, further comprising: providing (1840), by the PCF layer via the SMF layer, the conditional PCC rule to the UPF layer; measuring (1850), by the UPF layer, the feature; determining (1860), by the UPF layer, that the feature exceeds the threshold value; and responsive to determining that the feature exceeds the threshold value, performing (1870), by the UPF layer, the action.

38. The core network of any of Claims 35-37, wherein the feature comprises a throughput metric at a node level.

39. The core network of any of Claims 35-37, wherein the feature comprises a session metric specific to the PFCP session.

40. The core network of any of Claims 35-39, wherein the conditional PCC rule comprises at least one of: a packet detection rule, PDR, a forwarding action rule, FAR, a buffering action rule, BAR, a quality of service enforcement rule, QER, or a usage reporting rule, URR.

41. The core network of any of Claims 35-40, wherein the message is a first message, the operations further comprising: providing (1610), by the UPF layer, a second message to the SMF layer indicating that the UPF is capable of using conditional PCC rules during a PFCP session.

42. The core network of any of Claims 35-41, wherein performing the action comprises adjusting traffic during the PFCP session by controlling a resource allocated to the PFCP session.

43. A core network node (1000) in a telecommunication network, the core network node adapted to perform operations, the operations comprising: generating (1620), by a policy control function, PCF, layer of the core network node, a conditional policy control and charging, PCC, rule associated with a packet forwarding control protocol, PFCP, session, the conditional PCC rule comprising an action to be taken in response to a feature exceeding a threshold value; and providing (1630), by the PCF layer via a session management function, SMF, layer of the core network node, a message to a user plane function, UPF, layer of the core network node, the message requesting the UPF layer measure the feature.

44. The core network node of Claim 43 adapted to perform according to any of Claims 28-34.

45. A computer program comprising program code to be executed by processing circuitry (1003) of a core network node (1000) in a telecommunication network, whereby execution of the program code causes the core network node to perform operations, the operations comprising: generating (1620), by a policy control function, PCF, layer of the core network node, a conditional policy control and charging, PCC, rule associated with a packet forwarding control protocol, PFCP, session, the conditional PCC rule comprising an action to be taken in response to a feature exceeding a threshold value; and providing (1630), by the PCF layer via a session management function, SMF, layer of the core network node, a message to a user plane function, UPF, layer of the core network node, the message requesting the UPF layer measure the feature.

46. The computer program of Claim 45 whereby execution of the program code causes the core network node to perform operations according to any of Claims 28-34.

47. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1003) of a core network node (1000) in a telecommunication network, whereby execution of the program code causes the core network node to perform operations, the operations comprising: generating (1620), by a policy control function, PCF, layer of the core network node, a conditional policy control and charging, PCC, rule associated with a packet forwarding control protocol, PFCP, session, the conditional PCC rule comprising an action to be taken in response to a feature exceeding a threshold value; and providing (1630), by the PCF layer via a session management function, SMF, layer of the core network node, a message to a user plane function, UPF, layer of the core network node, the message requesting the UPF layer measure the feature.

48. The computer program product of Claim 47, whereby execution of the program code causes the core network node to perform operations according to any of Claims 28-34.