BACKGROUND Field

The present invention relates to apparatuses, methods, systems, computer programs, computer program products and computer-readable media usable for conducting a policy control of mobile edge applications in a communication network.

Background Art

The following description of background art may include insights, discoveries, understandings or disclosures, or associations, together with disclosures not known to the relevant prior art, to at least some examples of embodiments of the present invention but provided by the invention. Some of such contributions of the invention may be specifically pointed out below, whereas other of such contributions of the invention will be apparent from the related context.

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

3GPP: 3 ^rd Generation Partner Project

ADC: application detection and control

BS: base station

C-DB: centralized database

C-PCRF: centralized PCRF

CN: core network

CPU: central processing unit

DB: database

eNB: evolved node B

EPC: evolved packet core

ETSI European Telecommunications Standards Institute

GW: gateway HSS: home subscriber server

ID: identification, identifier

IMS: IP multimedia subsystem

IP: Internet protocol

L-PCRF: local PCRF

LTE: Long Term Evolution

LTE-A: LTE Advanced

MEC: mobile edge computing

NB: node B

PCC: policy and charging control

PCEF: policy and/or charging enforcement function

PCRF: policy and/or charging rule function

P-CSCF: proxy CSCF

PGW: packet data network gateway

QoS: quality of service

RNIS: radio network information service

SDF: service data flow

SPR: subscription provide repository

UDR: user data repository

UE: user equipment

UMTS: universal mobile telecommunication system

Embodiments of the present invention are related to a mechanism which allows a user to quickly access applications running at mobile edge computing platforms, in particular a mechanism for conducting policy control of mobile edge applications.

SUMMARY

According to an example of an embodiment, there is provided, for example, an apparatus comprising at least one processing circuitry, and at least one memory for storing instructions to be executed by the processing circuitry, wherein the at least one memory and the instructions are configured to, with the at least one processing circuitry, cause the apparatus at least: to receive and process a request for providing, to at least one mobile edge computing server, user related data of at least one user, the user related data are to be used for at least one of attaching a user to a communication network including t e at least one mobile edge computing server and conducting an application session of at least one user via the at least one mobile edge computing server, to check whether or not a usable set of user related data of the at least one user is locally present, wherein in case no usable set of user related data is locally present, a process for requesting a usable set for the user related data from a central policy control element or function is conducted for obtaining a usable set of user related data of the at least one user, to prepare the user related data for providing to the at least one mobile edge computing server, and to forward the prepared user related data to the at least one mobile edge computing server.

Furthermore, according to an example of an embodiment, there is provided, for example, a method comprising receiving and processing a request for providing, to at least one mobile edge computing server, user related data of at least one user, the user related data are to be used for at least one of attaching a user to a communication network including the at least one mobile edge computing server and conducting an application session of at least one user via the at least one mobile edge computing server, checking whether or not a usable set of user related data of the at least one user is locally present, wherein in case no usable set of user related data is locally present, a process for requesting a usable set for the user related data from a central policy control element or function is conducted for obtaining a usable set of user related data of the at least one user, preparing the user related data for providing to the at least one mobile edge computing server, and forwarding the prepared user related data to the at least one mobile edge computing server. According to further refinements, these examples may include one or more of the following features:

- for preparing the user related data for providing to the at least one mobile edge computing server, at least one of storing a set of user related data obtained from a central policy control element or function as a usable set of user related data, modifying parameters of a set of user related data obtained from a central policy control element or function according to local and prevailing conditions, and including the modified parameters in a usable set of user related data, and generating parameters according to local and prevailing conditions and including the generated parameters in a usable set of user related data may be conducted; - from a radio network information system, information regarding local and prevailing conditions in the communication network and using the information for modifying or generating the parameters may be acquired;

- the prepared user related data may be forwarded to the at least one mobile edge computing server in response to a request provided when a user is attaching to the communication network, and the prepared user related data may be forwarded to the at least one mobile edge computing server when a session start via the at least one mobile edge computing server is detected, wherein the prepared user related data may include session related policy and/or charging rules;

- at least one processing of a tracking processing including storing of identification data of the user and determining on the basis of the identification information whether a user is a regular user attaching to the network at least a predetermined number of times, a holding processing for holding the current user related data of the at least one user beyond a current session or attachment of the user, wherein the holding of the current user related data is executed in at least one of a local policy control element or function and the mobile edge computing server, and an updating processing including requesting the central policy control element or function to provide updates for information of the user related data and receiving updates for the information, or receiving updates for information of the user related data without request, processing the updates for the information from the central policy control element or function for preparing an updated set of user related data, wherein the preparing includes at least one of storing the user related data, modifying parameters of the user related data and generating parameters for the user related data, and forwarding the updated user related data to the mobile edge computing server, may be conducted;

- it may be determined that a session of the user with the at least one mobile edge computing server is terminated, it may be decided, when the termination of the session is determined, whether the user related data are to be kept, and in case the decision is negative, the user related data may be deleted, or in case the decision is affirmative, the user related data may be kept;

- the user related data may include at least one of a subscription or user profile of the at least one user, communication related parameters assigned to the at least one user in the communication network, policy and/or charging rules assigned to the at least one user in the communication network, and quality of service settings assigned to the at least one user in the communication network; - the processing may be implemented in a local policy control element or function comprising a local policy and/or charging rule function connected to or included in the mobile edge computing server, wherein the central policy control element or function may include a central policy and/or charging rule function.

Furthermore, according to an example of an embodiment, there is provided, for example, an apparatus comprising at least one processing circuitry, and at least one memory for storing instructions to be executed by the processing circuitry, wherein the at least one memory and the instructions are configured to, with the at least one processing circuitry, cause the apparatus at least: to receive and process a request for providing, to at least one local policy control element or function, user related data of at least one user, the user related data are to be used for at least one of attaching a user to a communication network including at least one mobile edge computing server and conducting an application session of at least one user via the at least one mobile edge computing server, to prepare the user related data for providing to the at least one local policy control element or function, and to forward the prepared user related data to the at least one local policy control element or function.

In addition, according to an example of an embodiment, there is provided, for example, a method comprising receiving and processing a request for providing, to at least one local policy control element or function, user related data of at least one user, the user related data are to be used for at least one of attaching a user to a communication network including at least one mobile edge computing server and conducting an application session of at least one user via the at least one mobile edge computing server, preparing the user related data for providing to the at least one local policy control element or function, and forwarding the prepared user related data to the at least one local policy control element or function.

According to further refinements, these examples may include one or more of the following features:

- it may be instructed that current user related data of the at least one user are held in at least one of the at least one local policy control element or function and the at least one mobile edge computing server beyond a current session or attachment of the at least one user; - an updating processing including receiving and processing a request from at least one local policy control element or function to provide updates for information of the user related data may be conducted, or the at least one local policy control element or function may be informed that updates for information of the user related data are provided and to be processed, wherein updated user related data may be prepared and the updated user related data may be forwarded to the at least one local policy control element or function;

- it may be determined that the at least one user detaches from the communication network, it may be decided, when the at least one user is detached, whether the user related data are to be kept, and in case the decision is negative, the at least one local policy control element or function may be instructed to cause deletion the user related data in the at least one local policy control element or function and the at least one mobile edge computing server, or in case the decision is affirmative, the at least one local policy control element or function may be instructed to keep the user related data in the at least one local policy control element or function and the at least one mobile edge computing server;

- users participating in the same user group may be determined, each user being able to establish an application session via at least one mobile edge computing server, communication related parameters for the user related data being valid for each of the determined users participating in the same user group may be defined, and the defined communication related parameters may be provided in connection with the user related parameters to local policy control elements or functions being in charge of the determined users participating in the same user group;

- information regarding a maximum available quality of service setting for each one among the determined users participating in the same user group may be obtained, a connection processing may be conducted for each user on the basis of the obtained information, the connection processing may include one of rejection of a participation of the user in the user group, acceptance of a participation of the user in the user group, and adaptation of communication related parameters for all users participating in the same user group on the basis of the obtained information;

- the defined communication related parameters may be updated in case a new participant for the user group is accepted or at least one participant of the user group leaves, and the updated communication related parameters may be provided in connection with the user related parameters to the local policy control elements or functions being in charge of the determined users participating in the same user group; - the user related data may include at least one of a subscription or user profile of the at least one user, communication related parameters assigned to the at least one user in the communication network, policy and/or charging rules assigned to the at least one user in the communication network, and quality of service settings assigned to the at least one user in the communication network;

- the processing may be implemented in a central policy control element or function comprising a central policy and/or charging rule function connected to the at least one mobile edge computing server, wherein the local policy control element or function may include a local policy and/or charging rule function.

Furthermore, according to an example of an embodiment, there is provided, for example, an apparatus comprising at least one processing circuitry, and at least one memory for storing instructions to be executed by the processing circuitry, wherein the at least one memory and the instructions are configured to, with the at least one processing circuitry, cause the apparatus at least: to receive and process a request for attaching at least one user to a communication network including at least one mobile edge computing server or conducting an application session of at least one user via at least one mobile edge computing server, to check whether or not a usable set of user related data of the at least one user is present, wherein in case no usable set of user related data is present, a process for requesting a usable set of the user related data from a local policy control element or function is conducted for obtaining a usable set of user related data of the at least one user, and to apply the usable user related data for conducting an application session of the at least one user via the at least one mobile edge computing server. In addition, according to an example of an embodiment, there is provided, for example, a method comprising receiving and processing a request for attaching at least one user to a communication network including at least one mobile edge computing server or conducting an application session of at least one user via at least one mobile edge computing server, checking whether or not a usable set of user related data of the at least one user is present, wherein in case no usable set of user related data is present, a process for requesting a usable set of the user related data from a local policy control element or function is conducted for obtaining a usable set of user related data of the at least one user, and applying the usable user related data for conducting an application session of the at least one user via the at least one mobile edge computing server. According to further refinements, these examples may include one or more of the following features:

- it may be instructed that current user related data of the at least one user are held in at least one of the at least one local policy control element or function and the at least one mobile edge computing server beyond a current session or attachment of the at least one user;

- an instruction for holding current user related data of the at least one user beyond a current session or attachment of the user may be received and processed, and an updating processing including receiving and processing updated user related data from the local policy control element or function replacing or supplementing the held user related data may be conducted;

- it may be determined that a session of the user with the at least one mobile edge computing server is terminated, it may be decided, on the basis of an instruction received from the local policy control element or function, whether the user related data are to be kept when the termination of the session is determined, and in case the decision is negative, the user related data may be deleted, or in case the decision is affirmative, the user related data may be kept;

- the user related data may include at least one of a subscription or user profile of the at least one user, communication related parameters assigned to the at least one user in the communication network, policy and/or charging rules assigned to the at least one user in the communication network, and quality of service settings assigned to the at least one user in the communication network;

- the processing may be implemented in at least one of a mobile edge computing server and a policy and/or charging enforcement element or function, wherein the central policy control element or function may comprise a central policy and/or charging rule function connected to the mobile edge computing server, wherein the local policy control element or function may include a local policy and/or charging rule function connected to or incorporated in the mobile edge computing server. In addition, according to embodiments, there is provided, for example, a computer program product for a computer, including software code portions for performing the steps of the above defined methods, when said product is run on the computer. The computer program product may include a computer-readable medium on which said software code portions are stored. Furthermore, the computer program product may be directly loadable into t e internal memory of the computer and/or transmittable via a network by means of at least one of upload, download and push procedures.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments of the present invention are described below, by way of example only, with reference to the accompanying drawings, in which:

Fig. 1 shows a diagram illustrating a configuration of communication network environment where some examples of embodiments are implementable;

Fig. 2 shows a signaling diagram illustrating policy control processing according to some examples of embodiments; Fig. 3 shows a signaling diagram illustrating policy control processing according to some examples of embodiments;

Fig. 4 shows a signaling diagram illustrating policy control processing according to some examples of embodiments;

Fig. 5 shows a signaling diagram illustrating policy control processing according to some examples of embodiments;

Fig. 6 shows a flow chart of a processing conducted in a local policy control element or function according to some examples of embodiments;

Fig. 7 shows a flow chart of a processing conducted in a centralized policy control element or function according to some examples of embodiments; Fig. 8 shows a flow chart of a processing conducted in a MEC server and/or a policy and/or charging enforcement function according to some examples of embodiments;

Fig. 9 shows a diagram of a network element or function acting as a local policy control element or function according to some examples of embodiments; Fig. 10 shows a diagram of a network element or function acting as a centralized policy control element or function according to some examples of embodiments; and

Fig. 1 1 shows a diagram of a network element or function acting as a MEC server and/or a policy and/or charging enforcement function according to some examples of embodiments.

DESCRIPTION OF EMBODIMENTS

In the last years, an increasing extension of communication networks, e.g. of wire based communication networks, such as the Integrated Services Digital Network (ISDN), DSL, or wireless communication networks, such as the cdma2000 (code division multiple access) system, cellular 3 ^rd generation (3G) like the Universal Mobile Telecommunications System (UMTS), fourth generation (4G) communication networks or enhanced communication networks based e.g. on LTE or LTE-A, fifth generation (5G) communication networks, cellular 2 ^nd generation (2G) communication networks like the Global System for Mobile communications (GSM), the General Packet Radio System (GPRS), the Enhanced Data Rates for Global Evolution (EDGE), or other wireless communication system, such as the Wireless Local Area Network (WLAN), Bluetooth or Worldwide Interoperability for Microwave Access (WiMAX), took place all over the world. Various organizations, such as the European Telecommunications Standards Institute (ETSI), the 3 ^rd Generation Partnership Project (3GPP), Telecoms & Internet converged Services & Protocols for Advanced Networks (TISPAN), the International Telecommunication Union (ITU), 3 ^rd Generation Partnership Project 2 (3GPP2), Internet Engineering Task Force (IETF), the IEEE (Institute of Electrical and Electronics Engineers), the WiMAX Forum and the like are working on standards or specifications for telecommunication network and access environments.

Generally, for properly establishing and handling a communication connection between two or more end points (e.g. communication stations or elements, such as terminal devices, user equipments (UEs), or other communication network elements, a database, a server, host etc.), one or more network elements such as communication network control elements, for example access network elements like access points, radio base stations, eNBs etc., and core network elements or functions, for example control nodes, support nodes, service nodes, gateways etc., may be involved, which may belong to one communication network system or different communication network systems.

One research field in the telecommunication field is mobile edge computing (MEC). MEC provides IT and cloud-computing capabilities within a radio access network in close proximity to mobile subscribers. For application developers and content providers, the access network edge offers a service environment with low latency and high-bandwidth as well as direct access to real-time radio network information (such as subscriber location, cell load, etc.) that can be used by applications and services to offer, for example, context-related services. Furthermore, applications and services offered by a

MEC server may be provided by different service providers. Applications and services offered by a MEC server may be used by network users/subscribers either in sessions between a communication element such as a UE and a server element, also referred to as a MEC server, or as intermediate data flow manipulators in sessions between a UE and e.g. the Internet.

The key element of MEC is the MEC server. The MEC server is, for example, integrated at a radio access network element, e.g. in an eNB site, or at a radio network controller element or a multi-technology (e.g. 3G/LTE) cell aggregation site. The MEC server provides computing resources, storage capacity, connectivity, and access to user traffic and radio and network information. For this purpose, a MEC server platform consists of several parts including a hosting infrastructure and an application platform. The MEC hosting infrastructure consists, for example, of hardware resources and a virtualization layer. The MEC application platform provides the capabilities for hosting applications and consists of the application's virtualization manager and application platform services.

These MEC application-platform services provide middleware services to the applications which are hosted on the MEC server, such as an infrastructure service, communication services, service registry, radio network information services (RNIS) and traffic offload function.

Since MEC allows cloud application services to be hosted alongside mobile network elements and also facilitates leveraging of the available real-time network and radio information, RNIS provides authorized applications with low-level radio and network information, which can be used by applications to calculate and present e.g. a cell-ID, location of the user/subscriber, cell load and throughput guidance. Furthermore, the RNIS may deliver information from t e radio network relating to users and cells, and provides indications relating to the activation of a UE on a specific mobile network element. These include parameters on the UE context and the established radio access bearer, such as QoS, cell ID for the radio access bearer, ID of the UE-associated logical signaling connection, etc.

On the other hand, in communication networks implementing MEC, policy and charging control (PCC) is an issue that is to be addressed. For example, policy management, charging, billing and accounting are to be considered.

Basically, in a PCC architecture, a policy control element or function, such as a policy and/or charging rule function (PCRF) is used as a central entity that makes policy and charging decisions, based on input from different sources, including mobile operator configuration, user subscription information, services information, and the like.

The PCRF may be a software node designated to determine policy rules in a communication network. The PCRF is the part of the network architecture that aggregates information to and from the network, operational support systems, and other sources (such as portals) in real time, supporting the creation of rules and then automatically making policy decisions for each user/subscriber being active on the network. The network may offer multiple services, QoS levels, and charging rules.

The PCC decisions are then communicated to a policy and/or charging enforcement function (PCEF) in the form of user related data including PCC rules. The PCEF enforces policy decisions that are received from the PCRF and provides the PCRF with subscriber and access information.

The PCC rules contain also service data flow (SDF) information that allows identification of IP traffic, charging parameters that are used to charge this traffic, and QoS parameters to be applied to the IP traffic that SDF filters identify.

When considering MEC in new communication network environments, it has to be expected that PCC and QoS framework will be closely related. That is, when a user (i.e. the UE) uses an application running on a MEC server connected e.g. to an eNB, an application session is to be established between the UE and the application on the MEC server. For this purpose, as a conceivable policy control mechanism, a policy and/or charging enforcement (e.g. by PCEF) is arranged/supported in the network between the UE and MEC server. For example, such an element or function is included in or connected to the involved MEC server. This is because the data flow(s) of the application session are not visible to the core network PCC entities.

As indicated above, one goal of MEC is to provide low latency services by MEC applications. Thus, an immediate availability of services for a user when the user/UE requests the service or when an ongoing session is modified can be provided.

It is desirable to provide a mechanism which allows policy control in such a manner that also low latency services in a MEC environment can be provided to a user without unnecessary delays. Specifically, it is desirable to provide a mechanism which allows a user to quickly access applications running at MEC platforms, wherein a policy control of mobile edge applications is provided.

In the following, different exemplifying embodiments will be described using, as an example of a communication network to which the embodiments may be applied, a communication network architecture based on 3GPP standards, such as LTE or LTE-A communication networks, without restricting the embodiments to such architectures, however. It is obvious for a person skilled in the art that the embodiments may also be applied to other kinds of communication networks having suitable means by adjusting parameters and procedures appropriately, e.g. 5G networks, WiFi, worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, mobile ad-hoc networks (MANETs), wired access, etc.. Furthermore, without loss of generality, description of some examples of embodiments is related to a mobile edge computing (MEC) environment, but principles of the invention can be extended and applied to any other type of combinations of radio access networks and IT computing configurations being similar or comparable to MEC principles. The following examples and embodiments are to be understood only as illustrative examples. Although the specification may refer to "an", "one", or "some" example(s) or embodiment(s) in several locations, this does not necessarily mean that each such reference is related to the same example(s) or embodiment(s), or that the feature only applies to a single example or embodiment. Single features of different embodiments may also be combined to provide other embodiments. Furthermore, terms like "comprising" and "including" should be understood as not limiting the described embodiments to consist of only those features that have been mentioned; such examples and embodiments may also contain features, structures, units, modules etc. that have not been specifically mentioned.

A basic system architecture of a (tele)communication network including a communication system where some examples of embodiments are applicable may include an architecture of one or more communication networks including a wired or wireless access network subsystem and a core network. Such an architecture may include one or more communication network control elements, access network elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station (BS), an access point (AP), a NodeB (NB) or an eNB, which control a respective coverage area or cell(s) and with which one or more communication stations such as communication elements, user devices or terminal devices, like a UE or a vehicle, or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a station, an element, a function or an application capable of conducting a communication, such as a UE, an element or function usable in a machine-to-machine communication architecture, or attached as a separate element to such an element, function or application capable of conducting a communication, or the like, are capable to communicate via one or more channels for transmitting several types of data in a plurality of access domains, such as a PS domain and a CS domain. Furthermore, core network elements such as gateway network elements, mobility management entities, a mobile switching center, servers, databases and the like may be included.

The general functions and interconnections of the described elements, which also depend on the actual network type, are known to those skilled in the art and described in corresponding specifications, so that a detailed description thereof is omitted herein. However, it is to be noted that several additional network elements and signaling links may be employed for a communication to or from an element, function or application, like a communication endpoint, a communication network control element, such as a server, a radio network controller, and other elements of the same or other communication networks besides those described in detail herein below.

A communication network as being considered in examples of embodiments may also be able to communicate with other networks, such as a public switched telephone network or the Internet. The communication network may also be able to support the usage of cloud services for virtual network elements or functions thereof, wherein it is to be noted that the virtual network part of the telecommunication network can also be provided by non-cloud resources, e.g. an internal network or the like. It should be appreciated that network elements of an access system, of a core network etc., and/or respective functionalities may be implemented by using any node, host, server, access node or entity etc. being suitable for such a usage.

Furthermore, a network element, such as communication elements, like a UE, access network elements, like a base station, an eNB, a radio network controller, other network elements, like a core network element, a server, etc., as well as corresponding functions as described herein, and other elements, functions or applications may be implemented by software, e.g. by a computer program product for a computer, and/or by hardware.

For executing their respective functions, correspondingly used devices, nodes, functions or network elements may include several means, modules, units, components, etc. (not shown) which are required for control, processing and/or communication/signaling functionality. Such means, modules, units and components may include, for example, one or more processors or processor units including one or more processing portions for executing instructions and/or programs and/or for processing data, storage or memory units or means for storing instructions, programs and/or data, for serving as a work area of the processor or processing portion and the like (e.g. ROM, RAM, EEPROM, and the like), input or interface means for inputting data and instructions by software (e.g. floppy disc, CD-ROM, EEPROM, and the like), a user interface for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), other interface or means for establishing links and/or connections under the control of the processor unit or portion (e.g. wired and wireless interface means, radio interface means including e.g. an antenna unit or the like, means for forming a radio communication part etc.) and the like, wherein respective means forming an interface, such as a radio communication part, can be also located on a remote site (e.g. a radio head or a radio station etc.). It is to be noted that in the present specification processing portions should not be only considered to represent physical portions of one or more processors, but may also be considered as a logical division of the referred processing tasks performed by one or more processors.

It should be appreciated that according to some examples, a so-called "liquid" or flexible network concept may be employed where the operations and functionalities of a network element, a network function, or of another entity of the network, may be performed in different entities or functions, such as in a node, host or server, in a flexible manner. In other words, a "division of labor" between involved network elements, functions or entities may vary case by case.

Generally, for providing policy control (and/or charging control, which is summarized in the following as "policy control"), it is necessary to obtain corresponding policy information (to be used by the PCEF), wherein corresponding information is provided from a policy control function (PCRF). However, when a UE uses an application running on an MEC server connected to an eNB, policy and charging enforcement is arranged between the UE and the MEC server, by a policy and/or charging enforcement function (PCEF), e.g. in or at the MEC server.

Therefore, policy information (to be used by the PCEF) are to be obtained e.g. from a (core network) policy and charging rules function (PCRF). However, there may be situations where a conventional way of obtaining the required data (e.g. when low latency is required) by requesting the information from a centralized entity are not fast enough.

Therefore, according to examples of embodiments of the invention, a configuration of a communication network is implemented where besides a centralized policy control element or function (or a plurality of centralized policy control elements or functions) the mobile edge computing platforms (e.g. the MEC servers) are each provided with or connected to a local policy control element or function. That is, a configuration is provided where a centralized policy control element or function is in (general) charge of a plurality of MEC platforms (MEC servers), wherein for each MEC server an own local policy control element or function is provided, which are connected to the centralized policy control element or function. With regard to Fig. 1 , a diagram illustrating a configuration of communication network environment where some examples of embodiments are implementable. It is to be noted that the structure indicated in Fig. 1 shows only those parts which are useful for understanding principles underlying some examples of embodiments of the invention. As also known by those skilled in the art there may be several other network elements or devices involved e.g. in a communication which are omitted here for the sake of simplicity. Furthermore, it is to be noted that links indicated in Fig. 1 are intended to show only principle examples of connections between respective network parts. It is possible that also additional or alternative links than those indicated in Fig. 1 are provided in a corresponding network, and/or that respective network elements or functions communicate with other network elements or functions by using intermediate nodes shown or not shown in Fig. 1 . It is to be noted that examples of embodiments are not limited to the number of communication stations, elements, functions, and links as indicated in Fig. 1 , i.e. there may be implemented or present less of or more of the corresponding stations, elements, functions, and links than those shown in Fig. 1 .

Fig. 1 shows an architecture where a centralized policy and/or charging control element or function, such as a PCRF (i.e. C-PCRF 70) is provided. The C-PCRF 70 may be a PCRF of one or more PCRFs provided in the core network of the communication network. Alternatively, the C-PCRF 70 may be a policy control element or function provided for a mobile edge computing environment, e.g. for or within a group of MEC servers (described later). It is to be noted that the centralized policy control element may be used for policy control and/or charging control. According to some examples of embodiments, the C-PCRF 70 is connected to a subscription database (C-DB), e.g. a HSS or SPR, or may have an integrated subscription database.

Reference signs 30 and 31 denote a respective MEC server. Each MEC server 30/31 has one or more applications 40/41 accessible by a user, control functions 60/61 including gateway functions, ADC, RNIS and a policy and charging enforcement function (PCEF), and a local policy control function (L-PCRF) 50/51 . It is to be noted that the local policy control element may be a used for policy control and/or charging control. The L-PCRF 50/51 may be provided for one MEC server (as shown in Fig. 1 ) or more than one MEC server. Furthermore, the L-PCRF and/or the PCEF may also reside outside of the MEC server (not shown in the figure). Reference signs 20 and 21 denote a respective access point to an access network subsystem, such as an eNB representing an access point to an LTE network part. As described above, the MEC servers 30 and 31 may be connected to or included in a corresponding eNB. Furthermore, a MEC server may be connected to more than one eNB.

Reference sign 10 denotes a UE (i.e. user) representing an example of a communication element configured to communicate with the MEC server for setting up and conducting an application session using one of the applications 40/41 . It is assumed that the UE 10 is capable of communicating with at least one of the eNBs 20/21 and with at least one MEC server. The UE 10 is movable within the network area.

Even though Fig. 1 shows an example of one UE 10, a plurality of eNBs 20/21 , two MEC servers 30/31 and one C-PCRF 70, it is to be noted that examples of embodiments are not limited to these numbers. More or less elements or functions can be involved in a control procedure according to examples of embodiments. For example, a group of users including a plurality of UEs may be connected to one or more MEC servers, wherein each of the MEC servers is running an application used by the respective UEs.

Furthermore, Fig. 1 shows also links or connections (such as interfaces etc.) between the respective network elements or functions. Details of these links, interfaces and connections may be implementation specific and generally known to those skilled in the art, so that a detailed description of each interface or link between the elements and functions according to an example as shown in Fig. 1 is omitted. However, it is to be noted that according to some examples of embodiments, links between elements or functions like the L-PCRFs 50 or 51 and the C-PCRF 70 (which is referred to, for example, as Pel interface) are used for a signaling being related to examples of embodiments. Next, examples of embodiments of a policy control procedure will be described with reference to the figures. First, a general concept of examples of the invention is discussed in connection with Fig. 1 . When UE 10 attaches to the network via eNB 20, wherein e.g. MEC server 30 is on the path and/or connected to the eNB 20 which is used by the UE 10, this means that the services offered by the MEC server 30 (e.g. by applications 40) can be accessed by the user (UE 10). When no user related data are available, which is e.g. the case when the UE 10 attaches for the first time, the MEC server 30 requests the user related data, such as PCC rules and/or subscription profile / parameters of the user, from a PCRF.

Specifically, the MEC server 30 uses its local policy and/or charging control function (L- PCRF 50).

It is to be noted that the attachment of the UE 10 at the eNB 20 may be noticed by the MEC server 30 by means of the RNIS which monitors corresponding events. Here, the user/UE 10 is identified and bound to the information in the database e.g. by a user ID or an IP address.

Now, the L-PCRF 50 checks whether it can provide the required user related data. When the L-PCRF 50 does not have usable (e.g. up-to-date) data, like PCC rule(s) and/or subscription profile for the user, the L-PCRF 50 requests these data (i.e. PCC rules and/or subscription profile / parameters) from the centralized policy control element or function, i.e. the C-PCRF 70. According to some examples of embodiments, the L-PCRF 50 stores the user ID or IP address of the attaching user. This ID is used for monitoring/checking, e.g. when the user attaches/detaches later on, whether the user in question is a "regular" visitor. This means, for example, that the user is determined to attach a predetermined number of times, e.g. in a certain period of time, or is attached to the network for at least a specified time or longer. This is used, for example, for deciding whether user related data of the user in question, such as the PCC rules and/or a user profile, is to be locally stored and to be kept up-to-date even if the UE 10 has no active application session or is detached from / out of the area of the MEC server 30. For example, if t e user ID or IP address, possibly with status information, already is present, L-PCRF 50 decides to request for an update of the status information. The status information may further indicate, for example, whether the user related parameters, like the PCC rules and/or user profile, are to be held only as long as the UE 10 has an active application session with the MEC server 30, or is attached to the area of the MEC server 30. Furthermore, it may be indicated whether the PCC rules and/or user profile may be removed after the termination of the last application session or after the UE 10 detaches from / is moving away from the area of the MEC server 30. Alternatively or additionally, the status information indicates whether updates of the user related data (e.g. PCC rules and/or subscription profile / parameters) are to be conducted. For example, the L-PCRF 50 can subscribe at the C-PCRF 70 for updating (i.e. request updates, when available at the C-PCRF 70). Furthermore, other conditions for the updates can be specified, e.g. an expiration time or an event after which no further updating is needed.

When the L-PCRF 50 receives a response from the C-PCRF 70 including e.g. PCC rules and/or the user profile / parameters, the L-PCRF 50 stores the PCC rules and/or user profile / parameters. Alternatively (or additionally), the L-PCRF 50 generates or creates own PCC rule(s), e.g. for a (default) context of the user/UE 10. The generation of own PCC rules is done, for example, in case no PCC rules are sent by C-PCRF 70 or if the received rules are not suitable or optimal for the local conditions. Furthermore, the received parameters of the user related data, such as PCC rules, can also be modified by the L-PCRF 50 according to prevailing and local conditions, if required.

It is to be noted that the RNIS (radio network information service) as a part of the MEC server 30/31 is configured to locally obtain information from the radio network, which can be used by applications running on the MEC server. Hence, according to some examples of embodiments, locally obtained RNIS based information, either general radio network information/conditions and/or user/UE related information and/or user session related information, are used by the L-PCRF 50 as input for creating/modifying the PCC rules.

When the MEC server 30 detects at any time an application session establishment by/for the user/UE 10, e.g. when a MEC application session related start of a session packet is detected, the MEC server 30 is now able to quickly get the required user related data; for example, it requests the PCC rules for service data flow(s) (SDF) of the session from the L-PCRF 50, or the data / PCC rules are already available at the PCEF (i.e. stored therein).

It is to be noted that according to some examples of embodiments, when generating/creating new PCC rules or when selecting PCC rules for the SDF(s) of the session, the L-PCRF 50 also takes into account, in addition to the profile and parameters received earlier from C-PCRF 70, prevailing and local conditions, e.g. a loading status and/or capabilities of the access network and/or neighboring MEC servers (e.g. considered for a possible handover etc.), and adjusts the PCC rules accordingly.

The policy and charging enforcement function (PCEF) in/at the MEC server 30 now applies the PCC rules to the SDF(s) of the user/UE's session as long as the session is alive or the rules are updated by L-PCRF 50. On the other hand, according to some examples of embodiments, when the user/UE's application session is terminated, the MEC server (the PCEF) holds the user related parameters (e.g. PCC rules), for a possible later use on a similar session established by the user/UE 10. This is done, for example, when the user is deemed to be a regular user (based on the corresponding determination as indicated above). Hence, an application session establishment can be accelerated.

According to some examples of embodiments, holding of the PCC rules is controlled by the L-PCRF 50, which itself is configured to decide to subscribe to updates of the user related parameters (PCC rules and or subscription profile / parameters) received from the C-PCRF 70 (as described above). Furthermore, according to some examples of embodiments, an updating processing may be conducted for keeping the PCC rules etc. up-to-date. Hence, when the subscription profile / parameters of the user changes, this is updated in the L-PCRF and also in the MEC server (PCEF) (i.e. meaning an update from the C-PCRF 70 to the L-PCRF 50 and further to the PCEF). Furthermore, when prevailing or local conditions change, a corresponding update can be considered by generating/modifying parameters of the user related data being currently present (i.e. the PCC rules are updated accordingly).

According to some further examples of embodiments, it is to be noted that at least some actions related to holding/updating user related data, such as user/UE related policy information in t e L-PCRF 50 and/or the PCEF 60 are controlled by the C-PCRF 70. For example, the C-PCRF 70 sends a corresponding instruction to the L-PCRF 50 (and the MEC server 30 (PCEF 60)). For example, when a UE 10 detaches from the network and the IP address of the UE 10 is released, this is regarded as a point after which there is no reason for preserving the PCC rule and/or subscription profile information of a user/UE 10 in the L-PCRF 50 and/or the PCEF 60. Consequently, the C-PCRF 70 sends a request to the L-PCRF 50 to delete the related information. Accordingly, the L-PCRF 50 can be triggered by the event to send a request to the PCEF to delete the related information.

According to some further examples of embodiments, the policy control processing is used in connection with the following. Specifically, for end-to-end mobility situations where communication partners (plural UEs) are served by different MEC servers, the centralized policy control element or function manages and compares e.g. the QoS levels of the respective users. For example, when using a gaming application (e.g. multiplayer game), all parties (being located e.g. in different MEC servers) shall have (approximately) the same conditions, e.g. the same latency and/or bit rate and/or quality class. According to examples of embodiments, this is achieved by using the C-PCRF 70 for comparing the characteristics and transmitting respective rules to all L-PCRFs.

Specifically, according to examples of embodiments, when a group activity, e.g. a game with several players is started, the group of the involved players (users) is identified, for example by using an ID that ties the players and the particular game instance(s). The ID may be established by the MEC entity or application that is involved when the game starts. It is to be noted that Users/UEs belonging to a group can be connected to the same MEC server or to different MEC servers, wherein each MEC server being involved is running the group application. For example, each user/UE uses an own MEC server.

In order to manage such a situation, i.e. where more than one MEC server is involved in the game session, a centralized entity (for example the C-PCRF 70 or another centralized entity, such as a database, a control entity, etc.) is made aware of the participants of a given game (identified by the ID). It is to be noted that the centralized entity is not limited to be the C-PCRF or a DB thereof, but may be one of the MEC entities or applications (e.g. the one that was involved at the start of the game). In t e control processing, the centralized entity (e.g. the C-PCRF 70) defines the same, application dependent, QoS rule(s) to be used by the participants of the given group. Then, the centralized entity (C-PCRF 70) sends the thus defined QoS rule(s) to all MEC servers, i.e. to all L-PCRFs, that are involved through a user/UE in the group. Hence, all MEC servers are provided with the same parameters.

According to some further examples of embodiments, in the management/control of the user group described above, when e.g. a new participant is trying to join the group (or when the first participant starts the group), the participant/UE or the involved access indicates the maximum QoS level being available to it. This information is then used for the following processing: the attempt to join the group is rejected, e.g. because the QoS level is determined to be not sufficient or acceptable to the group (for example, the others participants are operating on a higher QoS level; the attempt to join the group is accepted; or settings for the other participants of the group are adapted in accordance with the QoS information, i.e. the C-PCRF 70 updates the QoS setting for the other MEC servers accordingly by preparing and sending an update regarding the corresponding user related data to all involved MEC servers / L-PCRFs.

Furthermore, according to some further examples of embodiments, it is also possible that in case a participant leaves the group, the QoS level is evaluated again. For example, in case the leaving user has the lowest maximum QoS level available in the group, the C-PCRF 70 can now update the QoS level to match the (now present) lowest maximum QoS level amongst the still involved/active participants, i.e. send a corresponding update to the remaining (still involved) MEC servers / L-PCRFs.

In connection with Figures 2 to 5, further examples of embodiments for implementing the above described measures are described wherein elements being used in these examples correspond to elements shown in Fig. 1 . It is to be noted that the signaling flows indicated in Figs. 2 to 5 may be forwarded between a starting point and an end point via one or more additional nodes or function, which are not illustrated for the sake of simplicity.

Fig. 2 shows a signaling diagram illustrating policy control processing according to some examples of embodiments. Specifically, Fig. 2 is related to a processing when an unknown user/UE is attached and an application session is setup. ln S10, a request, e.g. an attach request, is sent from an unknown UE entering the area of the MEC server for attaching to the network, wherein the MEC server receives a corresponding indication, e.g. via the RNIS. Since the MEC server determines that the user/UE is unknown and hence there are no previously saved/stored and up-to-date PCC rules or other parameters present in the PCEF at the MEC server, it requests corresponding user related data from the L-PCRF in S20.

The L-PCRF determines in S30 that it does also not have any previously saved/stored and/or up-to-date (i.e. usable) user related data (user profile etc.) in a local storage/DB for the user/UE. In the present example, it is to be noted that the L-PCRF stores the user ID in order to be able to monitor/check upon later attaches/detaches of the user/UE, i.e. if the user/UE is a regular visitor (tracking processing) and/or if the user profile should be locally stored and kept up-to-date e.g. even if the UE has no active application session(s) or is out of the area of the MEC server.

In S40, the L-PCRF requests corresponding user related data (the subscription profile / parameters) from the C-PCRF and receives corresponding information in S50. For example, the user ID or an IP address is used as a key.

In S60, the L-PCRF stores the subscription profile / parameters for possible further (e.g. application session specific) use. In addition, the L-PCRF modifies parameters and/or generates new PCC rules for the (default) context of the user/UE, e.g. for the communication between the UE and the MEC server.

In S70, the L-PCRF responds to the request in S20 and sends information, e.g. PCC rules, to the PCEF. Furthermore, in S80, a response regarding the attachment request of the UE is sent to the UE. In S90, the UE sets up a MEC application session with the MEC server. In S100, the

MEC server (e.g. the ADC function in the MEC server) detects a MEC application session related packet, e.g. a start of a session message.

In S1 10, the MEC server (PCEF) requests from the L-PCRF required user related parameters, such as PCC rules. In S120, the L-PCRF fetches, caused by the request of PCEF / MEC server, t e user profile / parameters for the user/UE from the local storage/DB and selects/modifies/creates PCC rule(s) for the SDF(s) of the application.

In S130, the parameters (e.g. PC rules) are returned to the MEC server / PCEF.

In S140, the PCEF in the MEC server applies the received PCC rules to the SDFs of the user/UE application session. Hence, in S150, user data packets are exchanged between the UE and the MEC server. In S160 and S165, the signaling regarding an updating processing is illustrated, e.g. updating the user profile and related PCC rules, for example when the user profile of a user/UE is updated (e.g. by the operator) in a central UDR / database. Specifically, the C-PCRF sends in S160 update information to the L-PCRF, which uses the update for preparing corresponding information for the MEC server / PCEF. This update is sent to the PCEF in S165, for example.

Fig. 3 shows a signaling diagram illustrating policy control processing according to some examples of embodiments. Specifically, Fig. 3 is related to a processing when a known/regular user/UE (re-)attaches and application session is set up.

In S210, a request, e.g. an attach request, is sent from the known UE entering the area of the MEC server for attaching to the network, wherein the MEC server receives a corresponding indication, e.g. via the RNIS. Here, it is assumed that the MEC server determines that user related data of the attaching user/UE are not stored or up-to-date (e.g. PCC rules or other parameters) in the PCEF at the MEC server. Hence, it requests corresponding user related data from the L-PCRF in S220.

The L-PCRF determines in S30 that it has previously saved/stored and/or up-to-date (i.e. usable) user related data (user profile etc.) in a local storage/DB for the user/UE. In the present example, it is to be noted that the L-PCRF has stored the user ID for the tracking processing, and consequently updates a regular visitor status of the user/UE. Also holding/updating processing for holding the user profile locally stored and keeping it up- to-date e.g. even if the UE has no active application session(s) or is out of the area of the MEC server is conducted. It is to be noted that the L-PCRF can modify parameters and/or generates new PCC rules for t e (default) context of the user/UE, e.g. for the communication between the UE and the MEC server.

In S270, the L-PCRF responds to the request in S220 and sends information, e.g. PCC rules, to the PCEF. Furthermore, in S280, a response regarding the attachment request of the UE is sent to the UE.

In S290, the UE sets up a MEC application session with the MEC server. In S300, the MEC server (e.g. the ADC function in the MEC server) detects a MEC application session related packet, e.g. a start of a session message.

In S310, the MEC server (PCEF) requests from the L-PCRF required user related parameters, such as PCC rules. In S320, the L-PCRF fetches, caused by the request of PCEF / MEC server, the user profile / parameters for the user/UE from the local storage/DB and selects/modifies/creates PCC rule(s) for the SDF(s) of the application.

In S330, the parameters (e.g. PC rules) are returned to the MEC server / PCEF.

In S340, the PCEF in the MEC server applies the received PCC rules to the SDFs of the user/UE application session. Hence, in S350, user data packets are exchanged between the UE and the MEC server.

In S360 and S365, the signaling regarding an updating processing is illustrated, e.g. updating the user profile and related PCC rules, for example when the user profile of a user/UE is updated (e.g. by the operator) in a central UPR / database. Specifically, the C-PCRF sends in S360 update information to the L-PCRF, which uses the update for preparing corresponding information for the MEC server / PCEF. This update is sent to the PCEF in S365, for example.

Fig. 4 shows a signaling diagram illustrating policy control processing according to some examples of embodiments. Specifically, Fig. 4 is related to a termination of the last MEC application session of a user/UE at a MEC server, and to an update of the locally stored user related data (e.g. a user profile etc.). In S400, t e last user data packet is sent from the UE to the MEC server. Consequently, the MEC server detects in S410 the termination of the application session (last) MEC application session of the user/UE. In S420, the MEC server sends an information to the L-PCRF, for example a corresponding request to terminate the session.

In S430, L-PCRF decides on the further processing (e.g. tracking/holding/updating). For example, the L-PCRF deduces whether the user/UE is a regular visitor, wherein in this case L-PCRF decides to keep the user profile up-to-date in the local storage/DB. If not already requested earlier, or if an update to an earlier request is needed, the L-PCRF sends a corresponding request in S440 to the C-PCRF in order to keep the user profile at the L-PCRF up-to-date (see also S480 and S490 described below). S450 denotes a response to the requests in S440.

On the other hand, in case the L-PCRF deduces in S430 that the user/UE is not a regular visitor, the L-PCRF delete the user profile or declares it obsolete or not being up-to-date (so that in case of a new attachment of the UE a corresponding request to the C-PCRF is sent).

In S460, the L-PCRF informs the MEC server about the further processing, i.e. informs about whether a holding/updating processing is to be conducted. Hence, in S470, depending on the response from the L-PCRF, the PCEF / MEC server either keeps the existing PCC rules of the user/UE for possible further/later use or declares/makes the PCC rules obsolete.

In S480, the updating of user/UE's parameters at the L-PCRF and the PCEF in/at the MEC server is initiated, e.g. when the user profile is updated at the central SPR / database and when there has been the decision to keep the user/UE's parameters and PCC rules up-to-date (despite terminating the last MEC application session). Specifically, for example, the user profile or information stored in C-PCRF is updated (e.g. by the operator) in S480. The C-PCRF detects that the update has to be sent to the L-PCRF, e.g. as per the earlier received updating request in S440.

In S490, the updated information is provided to the L-PCRF. Here, in S500, the locally stored user related data (user profile etc.) are updated in accordance with the received updated information (user profile etc.). Furthermore, information, e.g. PCC rules, to be provided to the MEC server are prepared (if required). It is to be noted that this further update may be requested (instructed) by the C-PCRF in S490, if not being previously set.

In S510, the prepared updated information, e.g. PCC rules, for the MEC server (PCEF) is sent from the L-PCRF. Then, in S520, the PCEF in/at the MEC server updates the locally stored user related data (e.g. PCC rules) in accordance with the updated information received from L-PCRF in S510.

Fig. 5 shows a signaling diagram illustrating policy control processing according to some examples of embodiments. Specifically, Fig. 5 is related to an application session setup when usable user related data (i.e. up-to-date PCC rules) exist in the MEC server / PCEF.

Figure 5 steps 1 - 3 describe a case where a known/regular user/UE, i.e. a user/UE for whom/which previously saved/stored and up-to-date PCC rules exist in PCEF in/at MEC server, set up a MEC application session with a MEC server.

In S600, the MEC server (e.g. the ADC function in the MEC server) detects a MEC application session related packet, e.g. a start of a session message. The MEC server now determines that usable user related data (i.e. up-to-date PCC rules) related to the requested application/service exist for the user/UE. Consequently, the MEC server / PCEF determines that there is no need to request PCC rules from the L-PCRF; instead, an immediate session establishment is possible. Hence, the PCEF in the MEC server applies the existing PCC rules to the application session and the session establishment can start (S620).

In S630 and S635, the signaling regarding an updating processing is illustrated, e.g. updating the user profile and related PCC rules, for example when the user profile of a user/UE is updated (e.g. by the operator) in a central UPR / database. Specifically, the C-PCRF sends in S630 update information to the L-PCRF, which uses the update for preparing corresponding information for the MEC server / PCEF. This update is sent to the PCEF in S635, for example. Fig. 6 shows a flow chart of a processing conducted in a local policy control element or function according to some examples of embodiments. Specifically, the example according to Fig. 6 is related to a procedure conducted by a L-PCRF connected to or included in the MEC server and involved in a policy control processing, such as that shown in connection with Figs. 2 to 5.

In S700, a request for providing, to at least one network element or function acting as a MEC server, user related data of at least one user is received and processed. According to examples of embodiments, the user related data are to be used for one or more of the following processes: attaching a user to a communication network (e.g. the access network where the MEC server in question is located), and conducting an application session of user via the at least one MEC server. For example, the user related data includes at least one of the following parameters or information: a subscription or user profile of the at least one user, communication related parameters assigned to the at least one user in the communication network, policy and charging rules assigned to the at least one user in the communication network, and QoS settings assigned to the at least one user in the communication network.

In S710 and S720, it is checked whether or not a usable set of user related data of the at least one user is locally present. "Usable" means in this context that a corresponding set of data is present (e.g. stored) and also up-to-date (e.g. received/stored within a predetermined period of time allowing to assume that the data are actually valid for the user). In S720, in case no usable set of user related data is locally present (e.g. no data at all or data from which it is assumed that they are not up-to-date), the processing proceeds to S730, where a process for requesting a usable set for the user related data from a central policy control element or function (e.g. the C-PCRF) is conducted for obtaining a usable set of user related data of the at least one user.

In S740, either from S720 (a usable set of data is present) or from S730 (a usable set of data is received from the C-PCRF), user related data are prepared for providing them to the at least one MEC server. According to some examples of embodiments, when preparing the user related data for providing to the at least one MEC server, at least one of the following is executed. A set of user related data obtained from a C-PCRF is locally stored as a usable set of user related data. Additionally or alternatively, parameters of a set of user related data obtained from the C-PCRF are modified according to local and prevailing conditions, e.g. according to load conditions, local preferences, or the like, wherein the modified parameters are then included in a usable set of user related data. Furthermore, as another option, parameters according to local and prevailing conditions are generated by the L-PCRF itself, for example in case no or insufficient user related data are received from the C-PCRF, wherein the generated parameters are stored as or added to a usable set of user related data. According to some examples of embodiments, necessary information to be used in the modification or generation of parameters of the user related data is acquired from a RNIS in the (local) MEC server. In S750, the prepared user related data (of S740) are forwarded to the at least one MEC server (e.g. to a PCEF in the MEC server). The forwarding of the prepared user related data to the at least one MEC server is done, for example, in response to a request of the MEC server provided when a user is attaching to the communication network. Alternatively or additionally, the forwarding of the prepared user related data to the at least one MEC server is executed when a session start via the at least one MEC server is detected (e.g. when a MEC application is used by the user). In this case, the prepared user related data includes e.g. session related policy and/or charging rules.

According to some further examples of embodiments, at least one of the following processing is conducted. For example, a tracking processing is executed in which identification data of the user are stored (e.g. already in the processing of S700). On the basis of the identification information, it can then be determined whether the user is a regular user attaching to the network at least a predetermined number of times. Furthermore, as indicated in S760 a holding processing for holding the current user related data of the at least one user beyond a current session or attachment of the user is executed. The holding of the current user related data is executed in the L-PCRF and/or in the MEC server (e.g. in the PCEF). Furthermore, according to some examples of embodiments, in addition to the holding processing, also an updating processing can be executed. In the updating processing, the L-PCRF requests the C-PCRF to provide updates for information of t e user related data, and receives the requested updates for the information. Alternatively, the updates for information of the user related data are received at the L-PCRF without a dedicated request (i.e. automatically, in intervals, event-triggered, etc.). Irrespective of the way how the updated information is received, the updates for the information from the C-PCRF are processed for conducting (again) a preparing processing (see e.g. S740) for obtaining an updated set of user related data. That is, the preparing processing may include (again) at least one of storing the user related data, modifying parameters of the user related data and generating parameters for the user related data. Then, the updated user related data are forwarded to the MEC server (corresponding to S750).

Moreover, as indicated in S770, it is determined that a session of the user with the at least one MEC server is terminated (or the user detaches from the network). Then, it is decided, when the termination of the session is determined, whether the user related data are to be kept (e.g. based on S760 or based on a corresponding instruction, e.g. from the C-PCRF). In case the decision is negative (the user related data are not to be held), the user related data can be deleted or labelled as obsolete. Otherwise, in case the user related data are to be held (or even to be updated), the user related data are kept.

Fig. 7 shows a flow chart of a processing conducted in a centralized policy control element or function according to some examples of embodiments. Specifically, the example according to Fig. 7 is related to a procedure conducted by a C-PCRF connected to a plurality of MEC servers (and including an L-PCRF, for example) and involved in a policy control processing, such as that shown in connection with Figs. 2 to 5.

In S800 a request for providing, to at least one local policy control element or function such as a corresponding L-PCRF connected to or included in a corresponding MEC server, user related data of at least one user is received and processed. The user related data are to be used for one or more of the following processes: attaching a user to a communication network (e.g. the access network where the MEC server in question is located), and conducting an application session of user via the at least one MEC server. For example, the user related data includes at least one of the following parameters or information: a subscription or user profile of the at least one user, communication related parameters assigned to the at least one user in the communication network, policy and/or charging rules assigned to the at least one user in the communication network, and QoS settings assigned to the at least one user in the communication network.

In S810, the user related data are prepared for being provided to the at least one L- PCRF, and in S820, the prepared user related data are forwarded to the at least one L- PCRF.

According to some examples of embodiments, it is instructed that current user related data of the at least one user are held in at least one of the at least one L-PCRF and the at least one MEC server beyond a current session or attachment of the at least one user (i.e. a holding processing is instructed). The holding of the current user related data is instructed to be executed in the L-PCRF and/or in the MEC server (e.g. in the PCEF). Furthermore, according to some examples of embodiments, in addition to the holding processing, also an updating processing can be executed. In the updating processing, a request from at least one L-PCRF to provide updates for information of the user related data is received and processed. Alternatively, the at least one L-PCRF is informed (instructed) that updates for information of the user related data are provided and to be processed (i.e. stored and/or forwarded to the MEC server, etc.). Then, when updates for parameters of the user related data are available (e.g. due to an entry of an operator or the like) updated user related data are prepared and forwarded to the at least one L- PCRF.

In S830, it is determined that the at least one user detaches from the communication network or from the realm of the MEC server. In this context, it is decided whether the user related data are to be kept, when the at least one user is detached. In case the decision is negative, the at least one L-PCRF is instructed to cause deletion of the user related data in the at least one L-PCRF and the at least one MEC server. Otherwise, in case the decision is affirmative (i.e. the data are to be kept), the at least one L-PCRF is instructed to keep the user related data in the at least one L-PCRF and the at least one MEC server.

According to some further examples of embodiments, in connection with the above described processing for controlling policy for a MEC application, also the following processing is executed. For example, the following processing is conducted in connection with S810, i.e. when preparing the user related date. First, users participating in the same user group are determined, wherein each user is able to establish an application session via at least one mobile edge computing server. Then, communication related parameters for the user related data being valid for each of the determined users participating in the same user group are defined. For example, a (minimal) required QoS level for an application session in the user group, or the like, is defined. Then, the defined communication related parameters are provided in connection with the user related parameters to the L-PCRFs being in charge of the determined users participating in the same user group (i.e. to the MEC servers thereof).

According to some examples of embodiments, information regarding a maximum available QoS setting for each one among the determined users participating in the same user group are obtained. Based on this information (i.e. the knowledge about the maximum available QoS setting) a connection processing is conducted in which a rejection of a participation of the user in the user group, an acceptance of a participation of the user in the user group, or an adaptation of communication related parameters for all users (e.g. QoS setting) participating in the same user group on the basis of the obtained information is conducted.

Furthermore, according to some examples of embodiments, also an updating processing regarding the defined communication related parameters is conducted, for example in case a new participant for the user group is accepted or at least one participant of the user group leaves. For example, a QoS setting can be changed in accordance with the entry or exit of a user (and thus of its QoS setting). In this context, the updated communication related parameters are provided in connection with the user related parameters to the L-PCRFs being in charge of the determined users participating in the same user group.

Fig. 8 shows a flow chart of a processing conducted in a MEC server and/or a policy and/or charging enforcement function according to some examples of embodiments. Specifically, the example according to Fig. 8 is related to a procedure conducted by a MEC server including a policy and/or charging enforcement element or function, such as a PCEF, and being involved in a policy control processing, such as that shown in connection with Figs. 2 to 5. ln S900, a request for attaching at least one user to a communication network including at least one MEC server or for conducting an application session of at least one user via at least one MEC server is received and processed. In S910 and S920, it is checked whether or not a usable set of user related data of the at least one user is locally present. "Usable" means in this context that a corresponding set of data is present (e.g. stored) and also up-to-date (e.g. received/stored within a predetermined period of time allowing to assume that the data are actually valid for the user). According to examples of embodiments, the user related data are to be used for one or more of the following processes: attaching the user to the communication network

(e.g. the access network where the MEC server in question is located), and conducting an application session of the user via the at least one MEC server. For example, the user related data includes at least one of the following parameters or information: a subscription or user profile of the at least one user, communication related parameters assigned to the at least one user in the communication network, policy and/or charging rules assigned to the at least one user in the communication network, and QoS settings assigned to the at least one user in the communication network.

In S920, in case no usable set of user related data is locally present (e.g. no data at all or data from which it is assumed that they are not up-to-date), the processing proceeds to S930, where a process for requesting a usable set for the user related data from a local policy control element or function (e.g. the L-PCRF) is conducted for obtaining a usable set of user related data of the at least one user. In S940, either from S920 (a usable set of data is present) or from S930 (a usable set of data is received from the L-PCRF), the user related data are applied for an application session of the user with the at least one MEC server.

According to some further examples of embodiments, in S950, a holding process is conducted. For example, an instruction may be issued that current user related data of the at least one user are to be held in at least one of the at least one L-PCRF and the at least one MEC server beyond a current session or attachment of the at least one user. Alternatively or additionally, a corresponding instruction for holding the current user related data of the at least one user beyond a current session or attachment of the user is received and processed. In addition, an updating processing including receiving and processing updated user related data from t e L-PCRF (which replace or supplement the held user related data) is conducted.

In S960, it is determined that a session of the user with the at least one MEC server is terminated. Then, it is decided, on the basis of an instruction received from the local policy control element or function, whether the user related data are to be kept when the termination of the session is determined. In case the decision is negative (the user related data are not to be held), the user related data can be deleted or labelled as obsolete. Otherwise, in case the user related data are to be held (or even to be updated), the user related data are kept.

Fig. 9 shows a diagram of a network element or function acting as a local policy control element or function according to some examples of embodiments, e.g. as L-PCRF, which is configured to implement a procedure for policy control processing as described in connection with some of the examples of embodiments. It is to be noted that the network element or function, like the L-PCRF 50 of Fig. 1 , may include further elements or functions besides those described herein below. Furthermore, even though reference is made to a network element or function, the element or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry. The L-PCRF 50 shown in Fig. 9 may include a processing circuitry, a processing function, a control unit or a processor 5001 , such as a CPU or the like, which is suitable for executing instructions given by programs or the like related to the control procedure. The processor 5001 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference sign 5002 denotes input/output (I/O) units or functions (interfaces) connected to the processor or processing function 5001 . The I/O units 5002 may be used for communicating with the communication network and/or other entities or functions, as described in connection with Fig. 1 , for example. The I/O units 5002 may be a combined unit including communication equipment towards several entities, or may include a distributed structure with a plurality of different interfaces for different entities. Reference sign 5004 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 5001 and/or as a working storage of the processor or processing function 5001 . It is to be noted that the memory 5004 may be implemented by using one or more memory portions of the same or different type of memory.

The processor or processing function 5001 is configured to execute processing related to the above described procedure for policy control processing. In particular, the processor or processing circuitry or function 5001 includes one or more of the following sub-portions. Sub-portion 5005 is a processing portion which is usable as a portion for checking whether usable user related data are available. The portion 5005 may be configured to perform processing according to S710 and S720 of Fig. 6. Furthermore, the processor or processing circuitry or function 5001 may include a sub-portion 5006 usable as a portion for requesting user related data. The portion 5006 may be configured to perform a processing according to S730 of Fig. 6. In addition, the processor or processing circuitry or function 5001 may include a sub-portion 5007 usable as a portion for preparing and forwarding user related data. The portion 5007 may be configured to perform a processing according to S740 and S750 of Fig. 6. Moreover, the processor or processing circuitry or function 5001 may include a sub-portion 5008 usable as a portion for conducting an updating processing. The portion 5008 may be configured to perform a processing according to S760 of Fig. 6.

Fig. 10 shows a diagram of a network element or function acting as a centralized policy control element or function according to some examples of embodiments, e.g. as C- PCRF, which is configured to implement a procedure for policy control processing as described in connection with some of the examples of embodiments. It is to be noted that the network element or function, like the C-PCRF 70 of Fig. 1 , may include further elements or functions besides those described herein below. Furthermore, even though reference is made to a network element or function, the element or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or t e like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry. The C-PCRF 70 shown in Fig. 10 may include a processing circuitry, a processing function, a control unit or a processor 7001 , such as a CPU or the like, which is suitable for executing instructions given by programs or the like related to the control procedure. The processor 7001 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference sign 7002 denotes input/output (I/O) units or functions (interfaces) connected to the processor or processing function 7001 . The I/O units 7002 may be used for communicating with the communication network and/or other entities or functions, as described in connection with Fig. 1 , for example. The I/O units 7002 may be a combined unit including communication equipment towards several entities, or may include a distributed structure with a plurality of different interfaces for different entities. Reference sign 7004 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 7001 and/or as a working storage of the processor or processing function 7001 . It is to be noted that the memory 7004 may be implemented by using one or more memory portions of the same or different type of memory.

The processor or processing function 7001 is configured to execute processing related to the above described procedure for policy control processing. In particular, the processor or processing circuitry or function 7001 includes one or more of the following sub-portions. Sub-portion 7006 is a processing portion which is usable as a portion for processing a request for user related data. The portion 7006 may be configured to perform processing according to S800 of Fig. 7. Furthermore, the processor or processing circuitry or function 7001 may include a sub-portion 7007 usable as a portion for preparing and forwarding user related data. The portion 7007 may be configured to perform a processing according to S810 of Fig. 7. In addition, the processor or processing circuitry or function 7001 may include a sub-portion 7008 usable as a portion for conducting an updating processing. The portion 7008 may be configured to perform a processing according to S820 of Fig. 7.

Fig. 11 shows a diagram of a network element or function acting as a mobile edge computing server (including a policy and/or charging enforcement element or function) according to some examples of embodiments, e.g. as MEC server with PCEF, which is configured to implement a procedure for policy control and/or enforcement processing as described in connection with some of the examples of embodiments. It is to be noted that the network element or function, like the MEC server 30 of Fig. 1 , may include further elements or functions besides those described herein below. Furthermore, even though reference is made to a network element or function, the element or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.

The MEC server 30 shown in Fig. 1 1 may include a processing circuitry, a processing function, a control unit or a processor 3001 , such as a CPU or the like, which is suitable for executing instructions given by programs or the like related to the control procedure.

The processor 3001 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a

CPU or in one or more physical or virtual entities, for example. Reference sign 3002 denotes input/output (I/O) units or functions (interfaces) connected to the processor or processing function 3001 . The I/O units 3002 may be used for communicating with the communication network and/or other entities or functions, as described in connection with Fig. 1 , for example. The I/O units 3002 may be a combined unit including communication equipment towards several entities, or may include a distributed structure with a plurality of different interfaces for different entities. Reference sign 3004 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 3001 and/or as a working storage of the processor or processing function 3001 . It is to be noted that the memory 3004 may be implemented by using one or more memory portions of the same or different type of memory.

The processor or processing function 3001 is configured to execute processing related to the above described procedure for policy control and/or enforcement processing. In particular, the processor or processing circuitry or function 3001 includes one or more of the following sub-portions. Sub-portion 3005 is a processing portion which is usable as a portion for checking whether usable user related data are available. The portion 3005 may be configured to perform processing according to S910 and S920 of Fig. 8. Furthermore, the processor or processing circuitry or function 3001 may include a sub- portion 3006 usable as a portion for requesting user related data. The portion 3006 may be configured to perform a processing according to S930 of Fig. 8. In addition, the processor or processing circuitry or function 3001 may include a sub-portion 3007 usable as a portion for applying user related data. The portion 3007 may be configured to perform a processing according to S940 of Fig. 8.

As described above, according to examples of embodiments, procedures are described allowing to conduct a policy control and/or enforcement in such a manner that also low latency services in a MEC environment can be provided to a user without unnecessary delays. That is, a mechanism is provided which allows a user to quickly access applications running at MEC platforms, wherein a policy control and/or enforcement of mobile edge applications is provided.

It is to be noted that the measures described in the present specification can be executed on top of common/general measures or communication procedures. Some of the measures described in the present specification can be applied separately, some in various combinations, or all measures can be combined in one procedure.

By means of the proposed procedures described above, it is possible, for example, to enable a fast / low latency (QoS and/or charging) policy control and management for MEC application sessions and to optimize and/or reduce overall policy handling related message exchange in the network. Thus, it is possible to provide a solution for policy and/or charging control and management to be addressed in MEC standardization, e.g. policy management, charging, billing and accounting. By allowing t e local policy control element or function to adapt or even generate parameters of the user related data, such as of PCC rules or QoS settings, according to local and prevailing conditions, the policy control of an application session with a MEC server can be flexible and adapted to current requirements/conditions.

Furthermore, by keeping the parameters, such as PCC rules and/or subscription profile/parameters up-to-date at the MEC server, a faster establishment and modification of MEC application sessions is possible. Hence, a further reduction of PCC related messaging between the MEC environment and core network and in the core network is possible. Moreover, user experience can be improved.

The centralized policy control and management for user groups by the centralized policy control element or function discussed above enables a flexible adaptation of the communication or application session between the users in the user group and the network. Furthermore, in case a plurality of MEC servers with L-PCRF are involved in the communication path, the setting and configuration of the application session in the user group is facilitated, and user experience can be improved.

According to a further example of embodiments, there is provided, for example, an apparatus comprising means configured to receive and process a request for providing, to at least one mobile edge computing server, user related data of at least one user, the user related data are to be used for at least one of attaching a user to a communication network including the at least one mobile edge computing server and conducting an application session of at least one user via the at least one mobile edge computing server, means configured to check whether or not a usable set of user related data of the at least one user is locally present, wherein in case no usable set of user related data is locally present, a process for requesting a usable set for the user related data from a central policy control element or function is conducted for obtaining a usable set of user related data of the at least one user, means configured to prepare the user related data for providing to the at least one mobile edge computing server, and means configured to forward the prepared user related data to the at least one mobile edge computing server.

Furthermore, according to some other examples of embodiments, the above defined apparatus may further comprise means for conducting at least one of the processing defined in the above described methods, for example a method according that described in connection with Fig 6.

According to a further example of embodiments, there is provided, for example, an apparatus comprising means configured to receive and process a request for providing, to at least one local policy control element or function, user related data of at least one user, the user related data are to be used for at least one of attaching a user to a communication network including at least one mobile edge computing server and conducting an application session of at least one user via the at least one mobile edge computing server, means configured to prepare the user related data for providing to the at least one local policy control element or function, and means configured to forward the prepared user related data to the at least one local policy control element or function.

Furthermore, according to some other examples of embodiments, the above defined apparatus may further comprise means for conducting at least one of the processing defined in the above described methods, for example a method according that described in connection with Fig 7.

According to a further example of embodiments, there is provided, for example, an apparatus comprising means configured to receive and process a request for attaching at least one user to a communication network including at least one mobile edge computing server or conducting an application session of at least one user via at least one mobile edge computing server, means configured to check whether or not a usable set of user related data of the at least one user is present, wherein in case no usable set of user related data is present, a process for requesting a usable set of the user related data from a local policy control element or function is conducted for obtaining a usable set of user related data of the at least one user, and means configured to apply the usable user related data for conducting an application session of the at least one user via the at least one mobile edge computing server.

Furthermore, according to some other examples of embodiments, the above defined apparatus may further comprise means for conducting at least one of the processing defined in the above described methods, for example a method according that described in connection with Fig 8. It should be appreciated that

- an access technology via which traffic is transferred to and from an entity in the communication network may be any suitable present or future technology, such as WLAN (Wireless Local Access Network), WiMAX (Worldwide Interoperability for Microwave Access), LTE, LTE-A, 5G, Bluetooth, Infrared, and the like may be used; additionally, embodiments may also apply wired technologies, e.g. IP based access technologies like cable networks or fixed lines.

- embodiments suitable to be implemented as software code or portions of it and being run using a processor or processing function are software code independent and can be specified using any known or future developed programming language, such as a high- level programming language, such as objective-C, C, C++, C#, Java, Python, Javascript, other scripting languages etc., or a low-level programming language, such as a machine language, or an assembler.

- implementation of embodiments is hardware independent and may be implemented using any known or future developed hardware technology or any hybrids of these, such as a microprocessor or CPU (Central Processing Unit), MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), and/or TTL (Transistor-Transistor Logic).

- embodiments may be implemented as individual devices, apparatuses, units, means or functions, or in a distributed fashion, for example, one or more processors or processing functions may be used or shared in the processing, or one or more processing sections or processing portions may be used and shared in the processing, wherein one physical processor or more than one physical processor may be used for implementing one or more processing portions dedicated to specific processing as described,

- an apparatus may be implemented by a semiconductor chip, a chipset, or a (hardware) module including such chip or chipset;

- embodiments may also be implemented as any combination of hardware and software, such as ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field- programmable Gate Arrays) or CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components.

- embodiments may also be implemented as computer program products, including a computer usable medium having a computer readable program code embodied therein, the computer readable program code adapted to execute a process as described in embodiments, wherein the computer usable medium may be a non-transitory medium. Although t e present invention has been described herein before with reference to particular embodiments thereof, the present invention is not limited thereto and various modifications can be made thereto.