WO2014187477A1

WO2014187477A1 - Conditional pcc rules

Info

Publication number: WO2014187477A1
Application number: PCT/EP2013/060461
Authority: WO
Inventors: Rainer Liebhart; Martin Oettl; Thomas Theimer; Joachim Kross
Original assignee: Nokia Solutions And Networks Oy
Priority date: 2013-05-22
Filing date: 2013-05-22
Publication date: 2014-11-27

Abstract

Methods and apparatuses are provided by which applying at least one conditional policy and charging rule is applied, wherein the at least one conditional policy and charging rule depends on one or more conditions, and it is detected whether a certain condition is met and the at least one conditional policy and charging rule is applied in accordance with whether the certain condition is met or not.

Description

Description Title

Conditional PCC rules

Field of the Invention

The present invention relates to an apparatus, a method and a computer program product for reducing user plane congestion in a radio network.

Related background Art

The following meanings for the abbreviations used in this specification apply:

AAA Authentication, Authorization and Accounting

AS Application Server

CGI Cell Global Identification

CN Core Network

DL Downlink eNB Enhanced NodeB

EPC Evolved Packet Core

EPS Evolved Packet System

GERAN GSM/EDGE Radio Access Network

GGSN GPRS Gateway Serving Node GPRS General packet radio service Home Location Register

HPLMN Home Public Land Mobile Network

HSS Home Subscriber Server

Internet Protocol Connectivity Access Network

Mobility Management Entity

OAM Operation, Administration and Maintenance

PCC Policy and Charging Control

PCEF Policy and Charging Enforcement Function

PCRF Policy and Charging Rules function

PDN Packet data network

PDU Protocol Data Unit

P-GW/PGW Packet Data Network Gateway

QCI QoS Class Identifier

QoS Quality of Service

RAN Radio Access Network

RNC Radio Network Controller

S-GW/SGW Serving Gateway

Serving Packet Gateway

Subscription Profile Repository

User equipment

UL Uplink

UPCON User Plane Congestion Management

UTRAN Universal Terrestrial Radio Access Network Embodiments of the present invention relate to congestion in a mobile radio network, for example in an EPS. EPS is the Evolved Packet System, the successor of GPRS (General Packet Radio System). It provides new radio interface and new packet core network functions for broadband wireless data access. Such EPS core network functions are the Mobility Management Entity (MME), Packet Data Network Gateway (P-GW) and Serving Gateway (S-GW).

Fig. 4 illustrates the Evolved Packet Core architecture. In short, within this architecture, a common packet domain Core Network is used for the Radio Access Networks (RAN) E- UTRAN, GERAN and UTRAN. This common Core Network provides GPRS services.

Fig. 5 illustrates an overall PCC architecture (roaming with home routed access) when SPR is used. The PCC architecture extends the architecture of an EPS core network as shown in Fig. 4, where the Policy and Charging Enforcement Function is a functional entity in the Gateway node implementing the I P access to the Packet Data Network.

It is noted that Fig. 4 can be found in TS 23.401 , Fig.5 in TS 23.203 (e.g., Fig. 5.1 -3 in TS 23.203 V12.0.0 (2013-03)), so that it is referred to these documents for further information.

In 3GPP there is an ongoing study which defines system enhancements for user plane congestion management (UPCON - System Enhancements for User Plane Congestion Management). The normative requirements are defined in 3GPP TS 22.101 . The ongoing study results are captured in 3GPP TR 23.705.

Due to the surge in the mobile data traffic growth (e.g. due to smart phones and laptops equipped with USB dongles or data cards) in the market, operators are faced with user plane congestion issues in the live network and this causes network instability and user dis-satisfaction. To be precise, operators are faced with issues due to user plane congestion in the radio access network (i.e. in the eNB or in the backhaul link between eNB and S-GW i.e. on the S1 -U interface).

User plane congestion scenarios can be categorized as follows: 1. User plane congestion due to full use of cell capacity.

2. User plane congestion due to limited backhaul capacity (at the 3GPP RAN to EPC interface (i.e. S1 -U interface))

Current discussions in 3GPP SA2 separate between open loop (also called proactive) and closed loop (also called reactive) solutions for user plane congestion.

Open loop means that the core network provides information to RAN about ongoing sessions such as their relative priority so that RAN takes measures once congestion occurs.

Closed loop means that RAN provides congestion information to CN and AS so that CN and AS can take appropriate measures such as limiting the bandwidth for certain bearers or applications. Congestion information such as an overload level (none, low, medium, high) can be provided up to the PGW/GGSN and then further to an AS (e.g. video streaming server) or via Gx interface to the PCRF. Based on subscription information (bronze, silver, gold user) and congestion information, PCRF can adapt the PCC rules (e.g. reduce maximum available bandwidth in UL and DL).

Both scenarios are discussed in 3GPP and need proper solutions. However, as congestion information can change frequently, providing this information via Gx to PCRF could lead to a heavy load at Gx and potentially other interfaces such as Rx. It is noted that the congestion information needs to be provided on a per-Gx session or bearer basis, so a single congested cell can trigger multiple notifications. Summary of the Invention

Embodiments of the present invention address this situation and aim to overcome the above-described problem and to reduce the load on network interfaces caused by exchanging control information between network control elements (such as a PCEF and a PCRF) involved in controlling congestion.

According to a first aspect of the present invention an apparatus is provided which comprises a processor and a memory for storing instructions to be executed by the processor, wherein the processor is configured to apply at least one conditional policy and charging rule, wherein the at least one conditional policy and charging rule depends on one or more conditions, and the processor is configured to detect whether a certain condition is met and to apply the at least one conditional policy and charging rule in accordance with whether the certain condition is met or not.

According to a second aspect of the present invention an apparatus is provided which comprises a processor and a memory for storing instructions to be executed by the processor, wherein the processor is configured to specify at least one conditional policy and charging rule and one or more conditions for applying the at least one conditional policy and charging rule, and to forward the at least one conditional policy and charging rule and the one or more conditions to a network element configured to apply the at least one conditional policy and charging rule based on the one or more conditions.

According to a third aspect of the present invention an apparatus is provided which comprises a processor and a memory for storing instructions to be executed by the processor, wherein the processor is configured to set at least one conditional quality of service profile or part of a quality of service profile for a connection, wherein the at least one conditional quality of service profile or part of a quality of service profile depends on one or more conditions, and the processor is configured to detect whether a certain condition is met and to apply the at least one quality of service profile or part of a quality of service profile in accordance with whether the certain condition is met or not.

According to a fourth aspect of the present invention a method is provided which comprises applying at least one conditional policy and charging rule, wherein the at least one conditional policy and charging rule depends on one or more conditions, and the method further comprises detecting whether a certain condition is met and applying the at least one conditional policy and charging rule in accordance with whether the certain condition is met or not.

According to a fifth aspect of the present invention a method is provided which comprises specifying at least one conditional policy and charging rule and one or more conditions for applying the at least one conditional policy and charging rule, and forwarding the at least one conditional policy and charging rule and the one or more conditions to a network element configured to apply the at least one conditional policy and charging rule based on the one or more conditions.

According to a sixth aspect of the present invention a method is provided which comprises setting at least one conditional quality of service profile or part of a quality of service profile for a connection, wherein the at least one conditional quality of service profile or part of a quality of service profile depends on one or more conditions, and the method further comprises detecting whether a certain condition is met and applying the at least one quality of service profile or part of a quality of service profile in accordance with whether the certain condition is met or not.

According to a seventh aspect of the present invention a computer program product is provided which comprises code means for performing a method according to any one of the above fourth to sixth aspects and/or their modifications when run on a processing means or module. The computer program product may be embodied on a computer- readable medium.

Brief Description of the Drawings

These and other objects, features, details and advantages will become more fully apparent from the following detailed description of embodiments of the present invention which is to be taken in conjunction with the appended drawings, in which:

Fig. 1 shows simplified structures of a PCEF and a PCRF according to an embodiment of the present invention, Fig. 2 shows a simplified structure of an eNB according to another embodiment of the present invention,

Fig. 3 shows a flow chart of a routine for applying conditional policy and charging rules according to an embodiment of the present invention,

Fig. 4 shows an evolved packet core architecture, and

Fig. 5 shows an overall PCC architecture.

Detailed Description of embodiments

In the following, description will be made to embodiments of the present invention. It is to be understood, however, that the description is given by way of example only, and that the described embodiments are by no means to be understood as limiting the present invention thereto.

In the following, a general embodiment of the present invention is described by referring to Fig. 1 .

According to embodiments of the present invention, conditional policy and charging rules in the CN or RAN are applied based on one or more conditions, i.e. once such a rule is installed its activation depends on the fact that certain conditions are met. Figs. 1 and 2 show several elements involved in the procedure according to embodiments of the present invention. In more detail, Fig. 1 shows a PCEF 1 and a PCRF 2. The PCEF 1 is an example for an apparatus by which conditional policy and charging rules (potentially including connection quality related information such as RAN congestion levels) are applied. The apparatus may also be only a part of the corresponding network control element.

The PCEF 1 comprises a processor 1 1 and a memory 12 for storing instructions to be executed by the processor. The processor 12 is configured to apply at least one conditional policy and charging rule on at least one communication session. The at least one conditional policy and charging rule depends on one or more conditions, and the processor is configured to detect whether a certain condition is met and to apply the at least one conditional policy and charging rule in accordance with whether the certain condition is met or not.

Hence, the apparatus 1 itself is enabled to decide which conditional policy and charging rule is to be applied, namely based on certain conditions. Therefore, it is not necessary to receive signaling from another network control element which otherwise would install the corresponding policy rule. For example, it is not necessary for a PCRF to send a command to the PCEF by which a certain policy rule would be installed.

The conditions can be provided internally to the PCEF 1 or received via external interfaces (e.g., a congestion indication from eN B). Based on the condition the corresponding policy and charging rule is activated by the PCEF 1 . Once the condition is no longer valid or after a certain time period the corresponding policy and charging rule is de-activated.

The PCRF 2 is an example for an apparatus which sets/specifies the conditional policy and charging rules and the corresponding conditions. The PCRF 2 may also be only a part of a corresponding network control element.

The PCRF 2 comprises a processor 1 1 and a memory 12 for storing instructions to be executed by the processor. The processor 1 1 is configured to specify at least one conditional policy and charging rule and one or more conditions for applying the at least one conditional policy and charging rule, and to forward the at least one conditional policy and charging rule and the one or more conditions to a network element (e.g., the PCEF 1 ) configured to apply the at least one conditional policy and charging rule based on the one or more conditions.

The PCEF 1 and the PCRF 2 may comprise connection units 13 and 23, respectively, by which a connection to the network can be established.

Another example for the usage of conditional policy and charging rules is in the eNB. In this case, the eNB installs the conditional policy and charging rules, i.e., the conditional QoS profiles, when a bearer is established, for example. The eNB activates a conditional policy and charging rule or QoS profile once the condition is met (e.g. a certain congestion level in the eNB is reached). Fig. 2 shows such an eNB 3, which comprises a processor 31 , a memory 32 and a connection unit 33 similar as the corresponding elements of the PCEF 1 shown in Fig. 1.

In this case, an example for the apparatus which sets/specifies the conditional policy and charging rules and the corresponding conditions is the PCEF 1 .

In the following, a more detailed embodiment of the present invention is described.

According to the embodiment, the interactions between the PCEF, which is implemented in PGW/GGSN, and the PCRF is minimized by defining PCC rules that depend totally or partly on one or more conditions and potentially on subscription information such as the subscriber category. These conditional PCC rules can be pre-installed in the PCEF during connection/bearer establishment and modification but are not active unless the defined conditions are met (alternatively the rules can be pre-configured in the PCEF and enabled later on by the PCRF at any time). In the present description activating e.g. a PCC rule is to be understood such that this PCC rule is becoming active (i.e., an action/profile part is executed) when a condition is met. On the other hand enabling a PCC rule means that the corresponding network element (e.g., PCEF) starts evaluating its conditions and then the rule can become active based on the condition being met, resulting again in execution of an action/profile. That is, "activation" means that a condition is met and the corresponding action/profile is executed, whereas "enablement" means that PCRF puts a conditional PCC rule in the PCEF in a state that its conditions are being evaluated and potentially the rule can be activated. Note in this context as well that in case a rule is installed in one element (e.g. PCEF) by another element (e.g. PCRF) as part of protocol operation, the corresponding rule is implicitly enabled according to the above description. On the other hand, rules that are pre-installed in an element (e.g. PCEF) by means other than protocol operation (e.g. OAM would be such means), the rule would need to be activated separately via protocol operation e.g. from the PCRF, or based on internal logic in the concerned network element (e.g. in PCEF, a rule pre-installed via OAM can be enabled if the PCEF is configured to enable it upon session establishment for specific users).

The conditions can be met due to an external or internal event in the PGW/GGSN. In the context of the 3GPP UPCON feature an external condition could be the RAN congestion level notification sent from RAN (eNB, RNC) up to the PGW/GGSN via signaling messages. Once the PGW/GGSN, and, thus, the PCEF, receives notification about a certain congestion level, it can activate the pre-installed PCC rule corresponding to the particular congestion level. For simplicity, in the following description it is referred to the case where the particular external condition is specified by RAN congestion levels.

An example for the corresponding procedure carried out by the PCEF (e.g., PCEF 1 shown in Fig. 1 ) is illustrated in Fig. 3.

In S1 , the PCEF detects a certain congestion level. This may be achieved by simply receiving congestion level notification from the RAN (e.g., eNB, RNC), as described above, but alternatively based on measurements or the like carried out by the PCEF 1 or an associated network element.

In S2, it is evaluated whether the received congestion level meets a first condition (condition 1 ). This condition 1 could be a specific congestion level, such as a low congestion level, for example. If this condition is met, a policy rule 1 corresponding to condition 1 is applied.

If the condition 1 is not met in S2, it is evaluated in S4 whether the congestion level meets a second condition (condition 2). This condition 2 could be another specific congestion level, such as a high congestion level, for example. If this condition is met, a policy rule 2 corresponding to condition 3 is applied.

If condition 2 is not met in S4, a policy rule 3 is applied in S6. This policy rule 3 may be a default policy rule, which may be applied in case there is no congestion at all, for example.

The procedure shown in Fig. 3 is only an example, and there are other ways of determining which conditions are fulfilled so that the corresponding policy rules are to be applied. In particular, more than just two conditions can be applied.

Pre-installation of PCC rules can be done via OAM or via the PCRF once a PDN connection or dedicated bearer is established or modified. A pre-installed PCC rule for a certain congestion level is activated autonomously by the PGW/GGSN once this congestion level is received and de-activated either when another congestion level (or explicitly no congestion or a lower level) is received or a defined duration of time has expired.

Based on subscription information received from the HSS/SPR such as bronze, silver, gold user (defining different categories of users which, e.g., are permitted to use different bit rates, data volumes etc.) and dependent on the congestion levels that can be provided by RAN (usually these will only be a limited number of values such as no, low, medium, high congestion, but in principle every granularity is possible) the PCRF can provide a set of PCC rules in advance to the PCEF, i.e. PCRF provides the rules during PDN connection or dedicated bearer establishment and modification. Alternatively, the rules can be pre-configured in the PCEF via OAM or downloaded from the AAA server during authentication phase and enabled by the PCRF at any time.

Fully specified PCC rules can be installed in advance in the PCEF per congestion level.

Alternatively, only one PCC rule is installed that contains different parameters dependent on the congestion level, e.g. different values for the maximum bit rate in UL and DL dependent on the congestion levels 'no congestion', 'low', 'medium' and 'high'. As long as no congestion level is received from RAN the default PCC rule or default rule parameters (i.e. the values correlated with 'no congestion') are active in the PCEF. Once a certain congestion level is received from RAN, PCEF activates the rule or rule parameters dedicated to this congestion level. For example, in case of high RAN congestion the maximum bit rate in DL for bronze and silver users can be decreased to 64 kBit/sec. Once RAN resets the congestion level to 'no congestion' or a pre-defined duration of time (dependent on the congestion level and potentially subscriber category) has expired PCEF can activate the default PCC rule again.

As long as the conditional (e.g., congestion dependent) PCC rules have no impact to RAN (e.g., only bit rates in DL are affected), PCEF can avoid updating QoS profiles per bearer in RAN. If this is not the case and to avoid frequent signaling between PCEF and RAN when PCC rules change due to changes of RAN load, PCEF can provide in advance different QoS profiles or parts of QoS profiles (e.g. different maximum bit rate in UL and DL) to the RAN.

RAN, e.g. the eNB 3 shown in Fig. 2, activates the QoS profile for the particular bearer and dependent on the congestion level once it determines that this congestion level is met. This procedure may be similar as that shown in Fig. 3 described above. Hence, according to embodiments of the present invention, a solution to optimize the information exchange between GGSN/PGW and PCRF (and optionally also between GGSN/PGW and RAN) by reducing signalling traffic is achieved.

That is, according to embodiments of the present invention, the benefit is achieved that a way to significantly reduce the number of signaling messages between PGW/GGSN and PCRF (and optionally also between PGW/GGSN and RAN) is provided, but that on the other hand it is possible to take RAN congestion information into account for PCC decisions.

It is noted that the embodiments and the present invention in general is not limited to the specific examples given above.

For example, the measure of some embodiments of the invention, namely installing conditional PCC rules in the PCEF that are activated once certain conditions are met, can not only be used in the context of RAN user plane congestion, but potentially in all use cases where specified PCEF external or internal conditions trigger the activation of pre- installed rules in the PCEF.

Other examples could be policies triggered by application detection events. That is, the conditions may comprise a specific application flow, or a group of application flows detected in the user plane traffic. That is, the PCEF may be configured to detect such application flows and/or groups of application flows in the user plane traffic.

Furthermore, the network elements involved are not limited to PCEF, PCRF and eNB as shown in Figs. 1 and 2, but can be any suitable network elements by which the corresponding functions can be realized. Moreover, according to some embodiments described above, EPS and E-UTRAN were considered. However, the invention is not limited to these, and can be applied to other architectures such as GPRS and UTRAN/GERAN access as well.

According to a another aspect of embodiments of the present invention an apparatus is provided which comprises means for applying at least one conditional policy and charging rule, wherein the at least one conditional policy and charging rule depends on one or more conditions, the apparatus further comprising means for detecting whether a certain condition is met and means for applying the at least one conditional policy and charging rule in accordance with whether the certain condition is met or not.

According to a further aspect of embodiments of the present invention an apparatus is provided which comprises means for specifying at least one conditional policy and charging rule and one or more conditions for applying the at least one conditional policy and charging rule, and means for forwarding the at least one conditional policy and charging rule and the one or more conditions to a network element for applying the at least one conditional policy and charging rule based on the one or more conditions.

According to a still further aspect of embodiments of the present invention an apparatus is provided which comprises means for setting at least one conditional quality of service profile or part of a quality of service profile for a connection, wherein the at least one conditional quality of service profile or part of a quality of service profile depends on one or more conditions, and the apparatus further comprises means for detecting whether a certain condition is met and means for applying the at least one quality of service profile or part of a quality of service profile in accordance with whether the certain condition is met or not.

It is to be understood that any of the above modifications can be applied singly or in combination to the respective aspects and/or embodiments to which they refer, unless they are explicitly stated as excluding alternatives.

For the purpose of the present invention as described herein above, it should be noted that

- an access technology via which signaling is transferred to and from a network element may be any technology by means of which a network element or sensor node can access another network element or node (e.g. via a base station or generally an access node). Any present or future technology, such as WLAN (Wireless Local Access Network), WiMAX (Worldwide Interoperability for Microwave Access), LTE, LTE-A, Bluetooth, Infrared, and the like may be used; although the above technologies are mostly wireless access technologies, e.g. in different radio spectra, access technology in the sense of the present invention implies also wired technologies, e.g. IP based access technologies like cable networks or fixed lines but also circuit switched access technologies; access technologies may be distinguishable in at least two categories or access domains such as packet switched and circuit switched, but the existence of more than two access domains does not impede the invention being applied thereto,

- usable communication networks, stations and transmission nodes may be or comprise any device, apparatus, unit or means by which a station, entity or other user equipment may connect to and/or utilize services offered by the access network; such services include, among others, data and/or (audio-) visual communication, data download etc.;

- a user equipment or communication network element (station) may be any device, apparatus, unit or means by which a system user or subscriber may experience services from an access network, such as a mobile phone or smart phone, a personal digital assistant PDA, or computer, or a device having a corresponding functionality, such as a modem chipset, a chip, a module etc., which can also be part of a UE or attached as a separate element to a UE, or the like;

- method steps likely to be implemented as software code portions and being run using a processor at a network element or terminal (as examples of devices, apparatuses and/or modules thereof, or as examples of entities including apparatuses and/or modules therefore), are software code independent and can be specified using any known or future developed programming language as long as the functionality defined by the method steps is preserved;

- generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the invention in terms of the functionality implemented;

- method steps and/or devices, units or means likely to be implemented as hardware components at the above-defined apparatuses, or any module(s) thereof, (e.g., devices carrying out the functions of the apparatuses according to the embodiments as described above, eNode-B etc. as described above) are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components;

- devices, units or means (e.g. the above-defined apparatuses, or any one of their respective means) can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;

- an apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;

- a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.

It is noted that the embodiments and examples described above are provided for illustrative purposes only and are in no way intended that the present invention is restricted thereto. Rather, it is the intention that all variations and modifications be included which fall within the spirit and scope of the appended claims.

Claims

1. An apparatus comprising a processor and a memory for storing instructions to be executed by the processor, wherein the processor is configured to apply at least one conditional policy and charging rule, wherein the at least one conditional policy and charging rule depends on one or more conditions, and the processor is configured to detect whether a certain condition is met and to apply the at least one conditional policy and charging rule in accordance with whether the certain condition is met or not.

2. The apparatus according to claim 1 , wherein a plurality of conditions are defined and for each condition a conditional policy and charging rule is specified, wherein the processor is configured to apply a conditional policy and charging rule which is specified for the condition, which is detected to be met.

3. The apparatus according to claim 1 , wherein a plurality of parameters with respect to one conditional policy and charging rule is specified and for each condition, a parameter of the conditional policy and charging rule is defined, wherein the processor is configured to apply a parameter of the conditional policy and charging rule which is specified for the condition which is detected to be met.

4. The apparatus according to any one of the claims 1 to 3, wherein the at least one conditional policy and charging rule and the one or more conditions are preconfigured and stored in the memory.

5. The apparatus according to claim 4, wherein the processor is configured to receive an enable command from a network control element, and to enable the at least one conditional policy and charging rule based on the received enable command.

6. The apparatus according to any one of the claims 1 to 3, wherein the processor is configured to receive at least one conditional policy and charging rule and the one or more conditions from a network control element , and to store the received conditional policy and charging rule and the one or more conditions in the memory.

7. The apparatus according to claim 6, wherein the processor is configured to receive at least one conditional policy and charging rule and the one or more conditions from the network control element during connection/bearer establishment regarding the communication session, and to store the received conditional policy and charging rule and the one or more conditions in the memory.

8. The apparatus according to claim 6 or 7, wherein the processor is configured to receive an enable command from the network control element, and to enable the at least one conditional policy and charging rule based on the received enable command.

9. The apparatus according to any one of the claims 1 to 7, wherein the processor is configured to apply the at least one conditional policy and charging rule by taking into account subscription information.

10. The apparatus according to any one of the claims 1 to 9, wherein the conditions comprise different congestion levels and/or different network loads.

1 1 . The apparatus according to claim 3, wherein the conditions comprise different congestion levels and/or different network loads, and the parameters comprise different bit rates to be applied for the communication session.

12. The apparatus according to any one of the claims 1 to 1 1 , wherein the conditions comprise one or more specific application flows and/or one or more groups of application flows, and the processor is configured to detect application flows and/or groups of application flows in the user plane traffic.

13. The apparatus according to claim 3, wherein the conditions comprise one or more specific application flows and/or one or more groups of application flows and the parameters comprise different bit rates to be applied for the communication session, and the processor is configured to detect application flows and/or groups of application flows in the user plane traffic.

14. The apparatus according to any one of the claims 1 to 13, wherein the processor is configured to provide a plurality of different quality of service profiles or parts of quality of service profiles based on the one or more conditions to an access network control element.

15. The apparatus according to any one of the claims 1 to 14, wherein the at least one conditional policy and charging rule determines a quality of service profile or a part of a quality of service profile.

16. An apparatus comprising a processor and a memory for storing instructions to be executed by the processor, wherein the processor is configured to specify at least one conditional policy and charging rule and one or more conditions for applying the at least one conditional policy and charging rule, and to forward the at least one conditional policy and charging rule and the one or more conditions to a network element configured to apply the at least one conditional policy and charging rule based on the one or more conditions.

17. The apparatus according to claim 16, wherein a plurality of conditions are specified and for each condition a conditional policy and charging rule is specified, or a plurality of parameters with respect to one conditional policy and charging rule is specified, and for each condition, a parameter of the conditional policy and charging rule is defined.

18. The apparatus according to claim 16 or 17, wherein the processor is configured to forward the at least one conditional policy and charging rule and the one or more conditions to the network element during connection/bearer establishment.

19. The apparatus according to any one of the claim 16 to 18, wherein the processor is configured to send an enable command for enabling the at least one conditional policy and charging rule to the network element.

20. The apparatus according to any one of the claims 16 to 19, wherein the conditions comprise different congestion levels and/or different network loads, and/or one or more specific application flows and/or one or more groups of application flows.

21 . The apparatus according to claim 17, wherein the conditions comprise different congestion levels and/or different network loads, and/or one or more specific application flows and/or one or more groups of application flows, and the parameters comprise different bit rates to be applied for the communication session.

22. The apparatus according to any one of the claims 16 to 20, wherein the at least one conditional policy and charging rule determines a quality of service profile or a part of a quality of service profile.

An apparatus comprising a processor and a memory for storing instructions to be executed by the processor, wherein the processor is configured to set at least one conditional quality of service profile or part of a quality of service profile for a connection, wherein the at least one conditional quality of service profile or part of a quality of service profile depends on one or more conditions, and the processor is configured to detect whether a certain condition is met and to apply the at least one quality of service profile or part of a quality of service profile in accordance with whether the certain condition is met or not.

24. The apparatus according to claim 23, wherein the processor is configured to receive the at least one conditional quality of service profile or part of a quality of service profile and the on or more conditions from a network control element.

25. A method comprising applying at least one conditional policy and charging rule, wherein the at least one conditional policy and charging rule depends on one or more conditions, and the method further comprises detecting whether a certain condition is met and applying the at least one conditional policy and charging rule in accordance with whether the certain condition is met or not.

26. The method according to claim 25, wherein a plurality of conditions are defined and for each condition a conditional policy and charging rule is specified, and the method further comprises applying a conditional policy and charging rule which is specified for the condition, which is detected to be met.

27. The method according to claim 25, wherein a plurality of parameters with respect to one conditional policy and charging rule is specified and for each condition, a parameter of the conditional policy and charging rule is defined, and the method further comprises applying a parameter of the conditional policy and charging rule which is specified for the condition which is detected to be met.

28. The method according to any one of the claims 25 to 27, wherein the at least one conditional policy and charging rule and the one or more conditions are preconfigured and stored in the memory.

29. The method according to claim 28, further comprising receiving an enable command from a network control element, and enabling the at least one conditional policy and charging rule based on the received enable command.

30. The method according to any one of the claims 25 to 27, further comprising receiving at least one conditional policy and charging rule and the one or more conditions from a network control element, and storing the received conditional policy and charging rule and the one or more conditions in the memory.

31 . The method according to claim 30, further comprising receiving at least one conditional policy and charging rule and the one or more conditions from the network control element during connection/bearer establishment regarding the communication session, and to store the received conditional policy and charging rule and the one or more conditions in the memory.

32. The method according to claim 30 or 31 , further comprising receiving an enable command from the network control element, and enabling the at least one conditional policy and charging rule based on the received enable command.

33. The method according to any one of the claims 25 to 32, further comprising applying the at least one conditional policy and charging rule by taking into account subscription information.

34. The method according to any one of the claims 25 to 33, wherein the conditions comprise different congestion levels and/or different network loads.

35. The method according to claim 27, wherein the conditions comprise different congestion levels and/or different network loads, and the parameters comprise different bit rates to be applied for the communication session.

36. The method according to any one of the claims 25 to 35, wherein the conditions comprise one or more specific application flows and/or one or more groups of application flows, and the method further comprises detecting application flows and/or groups of application flows in the user plane traffic.

37. The apparatus according to claim 27, wherein the conditions comprise one or more specific application flows and/or one or more groups of application flows and the parameters comprise different bit rates to be applied for the communication session, and the method further comprises detecting application flows and/or groups of application flows in the user plane traffic.

38. The method according to any one of the claims 25 to 37, further comprising providing a plurality of different quality of service profiles or parts of quality of service profiles based on the one or more conditions to an access network control element.

39. The method according to any one of the claims 25 to 38, wherein the at least one conditional policy and charging rule determines a quality of service profile or a part of a quality of service profile.

40. A method comprising specifying at least one conditional policy and charging rule and one or more conditions for applying the at least one conditional policy and charging rule, and forwarding the at least one conditional policy and charging rule and the one or more conditions to a network element configured to apply the at least one conditional policy and charging rule based on the one or more conditions.

41 . The method according to claim 40, wherein a plurality of conditions are specified and for each condition a conditional policy and charging rule is specified, or a plurality of parameters with respect to one conditional policy and charging rule is specified, and for each condition, a parameter of the conditional policy and charging rule is defined.

42. The method according to claim 40 or 41 , further comprising forwarding the at least one conditional policy and charging rule and the one or more conditions to the network element during connection/bearer establishment.

43. The method according to any one of the claim 40 to 42, further comprising sending an enable command for enabling the at least one conditional policy and charging rule to the network element.

44. The method according to any one of the claims 40 to 43, wherein the conditions comprise different congestion levels and/or different network loads, and/or one or more specific application flows and/or one or more groups of application flows.

45. The method according to claim 41 , wherein the conditions comprise different congestion levels and/or different network loads, and/or one or more specific application flows and/or one or more groups of application flows, and the parameters comprise different bit rates to be applied for the communication session.

46. The apparatus according to any one of the claims 40 to 45, wherein the at least one conditional policy and charging rule determines a quality of service profile or a part of a quality of service profile.

47. A method comprising setting at least one conditional quality of service profile or part of a quality of service profile for a connection, wherein the at least one conditional quality of service profile or part of a quality of service profile depends on one or more conditions, and the method further comprises detecting whether a certain condition is met and applying the at least one quality of service profile or part of a quality of service profile in accordance with whether the certain condition is met or not.

48. The apparatus according to claim 47, further comprising receiving the at least one conditional quality of service profile or part of a quality of service profile and the on or more conditions from a network control element.

49. A computer program product comprising code means for performing a method according to any one of claims 25 to 48 when run on a processing means or module.

50. The computer program product according to claim 49, wherein the computer program product is embodied on a computer-readable medium.