WO2018206844A1

WO2018206844A1 - Routing and policy management at network edge

Info

Publication number: WO2018206844A1
Application number: PCT/FI2018/050333
Authority: WO
Inventors: John RÄSÄNEN
Original assignee: Nokia Technologies Oy
Priority date: 2017-05-08
Filing date: 2018-05-07
Publication date: 2018-11-15
Also published as: EP3622733A4; EP3622733A1

Abstract

Embodiments of the present invention generally relate to routing and policy management in wireless networks.In particular, embodiments described herein relate to routing and policymanagement in radio access networks (for example, 5G or the like) and other, for example, existing or future generations of wireless/mobile networks and, specifically to a method, apparatus, and computer program product for routing and policy management at the network edge.

Description

ROUTING AND POLICY MANAGEMENT AT NETWORK EDGE

TECHNOLOGICAL FIELD Embodiments described herein generally relate to routing and policy management in wireless networks. In particular, embodiments described herein relate to routing and policy management in radio access networks (for example, 5G or the like) and other, for example, existing or future generations of wireless/mobile networks and, specifically to a method, apparatus, and computer program product for routing and policy management at the network edge.

BACKGROUND

Two standardization organizations, European telecommunications standards institute (ETSI) and 3^rd generation partnership project (3GPP), are working on Multi-access Edge Computing (MEC). ETSI Industry specification group (ISG) MEC has so far concentrated mainly on the MEC system infrastructure and MEC application enablement. The MEC system is assumed to be transparent to the 3GPP 4G specifications, the MEC data plane being transparently connected to the mobile network user plane.

3 GPP is currently in an early phase in integrating MEC in the forthcoming 5G architecture. One current working assumption is that a local gateway / user plane function (UPF) at the (radio) access network edge ((R)AN) routes MEC related traffic to a ME Host (MEH). Figure 3, an excerpt from 3 GPP TS 23.501 / version 0.3.1 (Fig. 4.2.3-4), describes the proposed architectural principle (in a non-roaming case). UPFs 306 and 310 appear on two levels, local (at the access network / ((R)AN) edge) and central. The local UPF 306 is assumed to route data flows/packets either further towards the core network, i.e. to the central UPF 310 (and further to the data network DN 312), or to the local data network DN 308. ME Hosts are assumed to be connected to/via the local data network. However, no further details on possible interworking and/or integration of the MEC System and 5G network are available for the time being.

3GPP TR 23.799 (a study report completed before the currently ongoing normative standardization) describes the role of MEC in 5G in the following way: For the efficient delivery of certain operator/3rd party content related services, as well as for the provision of services over long distances in a cost-effective way, there is a need to deploy services in the operator trust domain close to the UE's access point of attachment to reduce latency and reduce the load on the transport network. The design of NextGen System should enable access to services deployed close to the UE's point of attachment from the very beginning, so that this functionality could be deployed in a flexible manner, leveraging also Network Function Virtualization (NFV).

The necessary functionality to support this is addressed as part of a number of key issues, including: QoS framework, session management, enabling (re)selection of efficient user plane paths, 3 GPP architecture impacts to support network capability exposure, and charging.

PROBLEM

It has not yet been defined how the MEC system fits into the 3GPP 5G architecture. The current specification states that the local UPF routes the non-MEC-related traffic to/from the central UPF (and related DN) and the MEC related traffic to/from the local data network / DN. This leads to architectural questions, such as how to map the MEC concept defined by ETSI ISG MEC to the 5G architecture being defined by 3 GPP.

How or on which grounds the local UPF gets the information, and which information, to make the routing decisions to route the MEC related data traffic to the local DN, is vaguely defined in the current specifications (3GPP TS 23.501). More generally the question is, how or on which grounds the local UPF gets the information, and which information, to make policy decisions (e.g., Policy and charging control (PCC), Quality of service (QoS) and/or charging control) concerning the data flows to be routed to the local DN. Related to this, the current version of TS 23.501 states that PCF "provides policy rules to control plane function(s) to enforce them" (Session Management Function (SMF) is one of the control plane functions), Policy control function (PCF) accesses "subscription information relevant for policy decisions", SMF "configures traffic steering at User plane function (UPF) to route traffic to proper destination", the functionalities of UPF include, for example, "packet routing & forwarding" and "packet inspection and user plane part of policy rule enforcement". This leaves the process of getting the information to make routing decisions pretty open, pretty much based on more or less semi-permanent configurations in the PCF and subscription data base.

A further complication, not yet addressed in the specifications either, is caused by data flows that need to go via a ME Host, the ME Host acting only as an intermediate data flow manipulator (called a "via MEC" flow/case later in the text). The peer entity information typically used for routing, for example, IP address, does not really help in making the routing decision in a "via MEC" case. The "via MEC" flows may also need special attention for policy and charging control (PCC) / policy control due to possibly different data flows on the two different legs caused by the data flow manipulation by an application on the ME Host.

In this regard, areas for improving known and existing conventional and/or existing systems have been identified. Through applied effort, ingenuity, and innovation, solutions to improve such systems have been realized and are described in connection with embodiments of the present invention.

BRIEF SUMMARY

MEC is regarded as an essential and integral part of the 5G network concept, and embodiments described herein are directed to solving routing and network policy related problems within the 5G network concept with MEC.

In particular, embodiments described herein include a method, apparatus, computer readable medium, and system for routing and policy management at network edge in a communication system. A control interface is defined between the Mobile edge computing (MEC) System and policy control function (PCF) of the core network (e.g., 'N-new'). N- new may be a new interface between the MEC System and PCF or, in some embodiments, depending on the functional entities of the core network or the MEC System the interface may be based on some existing ETSI ISG MEC or 3GPP interface. The N-new interface may more generally be considered as an interface or reference point between an entity that manages applications available on a certain platform and an entity that controls routing and/or policy operations on the (local) User plane function (UPF) in the core network.

Embodiments described herein may include functions configured to: 1.keep the core network policy control (PCF) aware of the applications / services that are available at the ME Host; 2. provide the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows (including "via MEC" flows) to or via the ME Host; 3. provide the PCF with application specific policy information to enable the PCF for example to create QoS or Policy and/or charging control (PCC) rules to be enforced by the local UPF on the MEC application specific data flows, such that in an instance of 'via MEC application, the application specific policy information may have separate requirements for the UE leg and far end leg of a data flow due to the flow manipulation performed by the MEC application, which may produce different PCC rules for those two legs; 4. provide PCF with application identification information that enables the above described operations, such that the application identification information may comprise just an application ID, or more detailed information like protocols or protocol stacks and/or protocol related detection pattern(s); and 5. provide PCF with information that enables PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host. For example, keeping the ME Host / System as agnostic on the core network topology as possible, the ME Host can identify itself and the PCF and/or SMF can have the topology information to be able to address the correct UPF(s). Or alternatively, the ME Host / System is aware enough of the topology to identify the UPF(s) to be addressed and sends the identifier(s) of the UPF(s) to PCF. The MEC System / ME Host / ME Platform provides the core network PCF with the application specific (identification, routing, PCC, etc.) information. PCF creates application specific routing and/or PCC rules, heeding also possible operator policies. PCF may also deduce / determine which UPF(s) to address. PCF sends the rules and information to SMF. The SMF identifies or determines the UPF(s) to be addressed and sends the rules and related information to the UPF(s). UPF applies the Routing Rules to route the data flow(s)/packets of the application to/via MEH. UPF applies the QoS/PCC rule(s) to the data flow(s)/packets of the application.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein: Fig. 1 is block diagram of a system that may be specifically configured in accordance with an example embodiment of the present invention;

Fig. 2 is a block diagram of an apparatus that may be specifically configured in accordance with an example embodiment of the present invention;

Fig. 3 is block diagram, from draft 3GPP TS 23.501 of a system that may be specifically configured in accordance with an example embodiment of the present invention, specifically showing the application of non-roaming 5G System architecture for concurrent access to two (e.g., local and central) data networks (single PDU session option) in reference point representation;

Fig. 4 is block diagram of a system that may be specifically configured in accordance with an example embodiment of the present invention, specifically showing 5G architecture with a ME Host at the edge of the access network (R)A and a management/control interface between the core network PCF and MEC System;

Fig. 5 is a flowchart showing an exemplary method of operating an example apparatus in accordance with an embodiment of the present invention; and

Fig. 6 is a data flow diagram showing an exemplary operation of an example system in an instance in which an application is introduced/on-boarded or updated on a ME Host, in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

Some example embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments are shown. Indeed, the example embodiments may take many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. The terms "data," "content," "information," and similar terms may be used interchangeably, according to some example embodiments, to refer to data capable of being transmitted, received, operated on, and/or stored. Moreover, the term "exemplary", as may be used herein, is not provided to convey any qualitative assessment, but instead merely to convey an illustration of an example. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.

As used herein, the term "circuitry" refers to all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry); (b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.

This definition of "circuitry" applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term 'circuitry' would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware. The term 'circuitry' would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or application specific integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or other network device.

System Architecture

Referring now to Figure 1, which illustrates an example system that supports communications between a plurality of stations 10 and one or more radio base stations / access points 12 (for example, a high density system scenario where a plurality of radio base stations / access points may be deployed to a geographical area and may be operating on the same frequency channel), each radio base station / access point may communicate with one or more stations and, in one embodiment, may communicate with a large number of stations. The radio base stations / access points may, in turn, communicate with a network 14. While the radio base stations / access points may communicate via 5G, an Long Term Evolution (LTE) or LTE-Advanced (LTE-A) network, other networks may support communications between the access points including those configured in accordance with wideband code division multiple access (W-CDMA), CDMA2000, global system for mobile communications (GSM), general packet radio service (GPRS), the IEEE 802.11 standard including, for example, the IEEE 802.11 ah or 802.11 ac standard or other newer amendments of the standard, wireless local access network (WLAN), Worldwide Interoperability for Microwave Access (WiMAX) protocols, universal mobile telecommunications systems (UMTS) terrestrial radio access network (UTRAN) and/or the like, as well as other standards, for example, with respect to multi-domain networks, that may include, industrial wireless communication networks such as WirelessHART, Bluetooth, ZigBee etc. and/or the like.

The radio base stations / access points 12 and the stations 10 may communicate via wireline communications, but most commonly communicate via wireless communications. For example, the radio base stations / access points and the stations may communicate in a sub 1 GHz band as defined by IEEE 802.11 ah standard or in a 5GHz band, which may be defined by, for example, IEEE 802.1 lac standard. The radio base station / access point may be embodied by any of a variety of network entities, such as an access point, a base station, a Node B, an evolved Node B (eNB), a radio network controller (RNC), a mobile device / a station (for example, mobile telephones, smart phones, portable digital assistants (PDAs), pagers, laptop computers, tablet computers or any of numerous other hand held or portable communication devices, computation devices, content generation devices, content consumption devices, or combinations thereof), or the like. The stations may also be embodied by a variety of devices, such as sensors, meters or the like. The sensors and meters may be deployed in a variety of different applications including in utility applications to serve as a gas meter, a water meter, a power meter or the like, in environmental and/or agricultural monitoring applications, in industrial process automation applications, vehicular or transportation automation application, in healthcare and fitness applications, in building automation and control applications and/or in temperature sensing applications. Stations that are embodied by sensors or meters may be utilized in some embodiments to backhaul sensor and meter data. Alternatively, the stations may be embodied by mobile terminals or user equipment(s) (UE), such as mobile communication devices, for example, mobile telephones, smart phones, portable digital assistants (PDAs), pagers, laptop computers, tablet computers or any of numerous other hand held or portable communication devices, computation devices, content generation devices, content consumption devices, or combinations thereof. In an embodiment in which the station is embodied by a mobile terminal, the communication between an access point and the station may serve to extend the range of Wi-Fi or another wireless local area network (WLAN), such as by extending the range of a hotspot, and to offload traffic that otherwise would be carried by a cellular or other network.

The radio base station / access point 12 and/or the station 10 may be embodied as or otherwise include an apparatus 20 that is specifically configured to perform the functions of the respective device, as generically represented by the block diagram of Figure 2. While the apparatus may be employed, for example, by a radio base station / access point or a station, it should be noted that the components, devices or elements described below may not be mandatory and thus some may be omitted in certain embodiments. Additionally, some embodiments may include further or different components, devices or elements beyond those shown and described herein.

Apparatus Architecture

Regardless of the type of device that embodies the radio base station / access point

12 and/or the station 10, the radio base station / access point 12 and/or the station 10 may include or be associated with an apparatus 20 as shown in Figure 2. In this regard, the apparatus may include or otherwise be in communication with a processor 22, a memory device 24, a communication interface 26 and a user interface 28. As such, in some embodiments, although devices or elements are shown as being in communication with each other, hereinafter such devices or elements should be considered to be capable of being embodied within the same device or element and thus, devices or elements shown in communication should be understood to alternatively be portions of the same device or element.

In some embodiments, the processor 22 (and/or co-processors or any other processing circuitry assisting or otherwise associated with the processor) may be in communication with the memory device 24 via a bus for passing information among components of the apparatus. The memory device may include, for example, one or more volatile and/or non-volatile memories. In other words, for example, the memory device may be an electronic storage device (for example, a computer readable storage medium) comprising gates configured to store data (for example, bits) that may be retrievable by a machine (for example, a computing device like the processor). The memory device may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus 20 to carry out various functions in accordance with an example embodiment of the present invention. For example, the memory device could be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device could be configured to store instructions for execution by the processor.

As noted above, the apparatus 20 may be embodied by a computing device 10 configured to employ an example embodiment of the present invention. However, in some embodiments, the apparatus may be embodied as a chip or chip set. In other words, the apparatus may comprise one or more physical packages (for example, chips) including materials, components and/or wires on a structural assembly (for example, a baseboard). The structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus may therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single "system on a chip." As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.

The processor 22 may be embodied in a number of different ways. For example, the processor may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other processing circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processor may include one or more processing cores configured to perform independently. A multi-core processor may enable multiprocessing within a single physical package. Additionally or alternatively, the processor may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.

In an example embodiment, the processor 22 may be configured to execute instructions stored in the memory device 24 or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor may represent an entity (for example, physically embodied in circuitry) capable of performing operations according to an embodiment of the present invention while configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a specific device configured to employ an embodiment of the present invention by further configuration of the processor by instructions for performing the algorithms and/or operations described herein. The processor may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor. In one embodiment, the processor may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface 28.

Meanwhile, the communication interface 26 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data between the computing device 10 and a server 12. In this regard, the communication interface 26 may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications wirelessly. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). For example, the communications interface may be configured to communicate wirelessly with the head mounted displays 10, such as via Wi-Fi, Bluetooth or other wireless communications techniques. In some instances, the communication interface may alternatively or also support wired communication. As such, for example, the communication interface may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms. For example, the communication interface may be configured to communicate via wired communication with other components of the computing device.

The user interface 28 may be in communication with the processor 22, such as the user interface circuitry, to receive an indication of a user input and/or to provide an audible, visual, mechanical, or other output to a user. As such, the user interface may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, and/or other input/output mechanisms. In some embodiments, a display may refer to display on a screen, on a wall, on glasses (for example, near-eye-display), in the air, etc. The user interface may also be in communication with the memory 24 and/or the communication interface 26, such as via a bus.

Invention System Architecture

Figure 4 shows the principles of the 5G architecture in the current draft 3GPP specifications, enhanced with a ME Host 404 concept defined by ETSI ISG MEC. As suggested by 3GPP, the local UPF 306 routes the MEC related data traffic to the ME Host 404 through the N6 interface.

A control interface may be defined between the MEC System 402 and policy control function / PCF 322 of the core network, known as N-new in figure 4. N-new could be a totally new interface between the MEC System 402 and PCF 322, in some embodiments, depending on the functional entities of the core network (e.g. PCF 322) and the MEC System 402 (e.g. ME Host 404 / Platform 410 or ME orchestrator (MEO)), the interface may be based on some existing ETSI ISG MEC or 3 GPP interface. For example the interface may be based on or be an extension of the Mp3 interface introduced by ETSI MEC (currently for control purposes between two ME Hosts), assuming that the ME Host / Platform exchanges information with the core network (e.g. with PCF). In some embodiments, the interface may be based on or be an extension of the Mm3 interface introduced by ETSI MEC (currently for control purposes between MEO and ME Platform manager), assuming that the MEO exchanges information with the core network (e.g. with PCF). In some embodiments, the interface may be based on or be an extension of the N5 interface introduced by 3GPP (currently for session control purposes between AF and PCF), assuming that the MEC System exchanges information with the core network PCF. In the long run some of the core network and MEC System functionalities may, at least to some extent, be integrated, rather than having a strictly separate core network (defined by 3GPP) and MEC System (defined by ETSI). Consequently, the N-new interface may more generally be understood as an interface or reference point between an entity that manages applications available on a certain platform and an entity that controls routing and/or policy operations on the (local) UPF in the core network.

Figure 5 shows a flowchart of the exemplary operations performed by a method, apparatus and computer program product in accordance with an embodiment of the present invention. In some example embodiments, a method, apparatus and computer program product may be configured for providing and/or defining a control interface between the MEC System 402 and policy control function / PCF 322 of the core network. Figure 5 is a flowchart showing an exemplary method of operating an example apparatus in accordance with an embodiment of the present invention.

As shown in block 505 of Figure 5, an apparatus, for example, apparatus 20 embodied by the computing device 10, or the like, may be configured to provide an interface between a first entity configured for managing applications available on a specific platform and a second entity configured for controlling routing or policy operations on a local UPF in a core network. The apparatus, for example, embodied by the computing device 10, or the like may therefore include means, such as the processor 22, the communication interface 26 or the like, for providing an interface between a first entity configured for managing applications available on a specific platform and a second entity configured for controlling routing or policy operations on a UPF in a core network.

In some embodiments, the interface, (e.g., the N-new interface) may be configured to keep the core network policy control (PCF) aware of the applications / services that are available at the ME Host.

As shown in block 510 of Figure 5, an apparatus, for example, apparatus 20 embodied by the computing device 10, or the like, may be configured to keep the core network policy control (PCF) aware of the applications / services that are available at the ME Host. The apparatus, for example, embodied by the computing device 10, or the like may therefore include means, such as the processor 22, the communication interface 26 or the like, for keeping the core network policy control (PCF) aware of the applications / services that are available at the ME Host.

In some embodiments, the interface, (e.g., the N-new interface) may be configured to provide the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows (including "via MEC" flows) to or via the ME Host.

As shown in block 515 of Figure 5, an apparatus, for example, apparatus 20 embodied by the computing device 10, or the like, may be configured to provide the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows (including "via MEC" flows) to or via the ME Host. The apparatus, for example, embodied by the computing device 10, or the like may therefore include means, such as the processor 22, the communication interface 26 or the like, for providing the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows to or via the ME Host.

In some embodiments, the interface, (e.g., the N-new interface) may be configured to provide the PCF with application specific policy information to enable the PCF for example to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows. In case of "via MEC" application, the application specific policy information may have separate requirements for the UE leg and far end leg of a data flow due to the flow manipulation performed by the MEC application, which may produce different PCC rules for those two legs.

As shown in block 520 of Figure 5, an apparatus, for example, apparatus 20 embodied by the computing device 10, or the like, may be configured to provide the PCF with application specific policy information to enable the PCF for example to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows. The apparatus, for example, embodied by the computing device 10, or the like may therefore include means, such as the processor 22, the communication interface 26 or the like, for providing the PCF with application specific policy information to enable the PCF for example to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows. In some embodiments, the interface, (e.g., the N-new interface) may be configured to provide PCF with application identification information that enables the above described operations. The application identification information may comprise just an application ID, or more detailed information like e.g. protocols or protocol stacks and/or protocol related detection pattern(s).

As shown in block 525 of Figure 5, an apparatus, for example, apparatus 20 embodied by the computing device 10, or the like, may be configured to provide PCF with application identification information that enables the above described operations The apparatus, for example, embodied by the computing device 10, or the like may therefore include means, such as the processor 22, the communication interface 26 or the like, for providing PCF with application identification information that enables the above described operations.

In some embodiments, the interface, (e.g., the N-new interface) may be configured to provide PCF with information that enables PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host. For example, keeping the ME Host / System as agnostic on the core network topology as possible, the ME Host can identify itself and the PCF and/or SMF can have the topology information to be able to address the correct UPF(s). Or alternatively, the ME Host / System is aware enough of the topology to identify the UPF(s) to be addressed and sends the identifier(s) of the UPF(s) to PCF.

As shown in block 530 of Figure 5, an apparatus, for example, apparatus 20 embodied by the computing device 10, or the like, may be configured to provide PCF with information that enables PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host. The apparatus, for example, embodied by the computing device 10, or the like may therefore include means, such as the processor 22, the communication interface 26 or the like, for providing the PCF with information that enables the PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host.

Data Flow Diagram

Figure 6 comprises a data flow / signal flow diagram describing an exemplary embodiment. As shown in step 605, an application is introduced/on-boarded (or updated) on a ME Host. As shown in step 610, the MEC System / ME Host / ME Platform provides the core network PCF with the application specific (identification, routing, PCC, etc.) information. As shown in step 615, PCF creates application specific routing and/or PCC rules, heeding also possible operator policies. As shown in step 620, PCF may also deduce / determine which UPF(s) to address. PCF sends the rules and information to SMF. As shown in step 625, the SMF identifies or determines the UPF(s) to be addressed. As shown in step 630, SMF sends the rules and related information to the UPF(s). As shown in step 635, UPF applies the Routing Rules to route the data flow(s)/packets of the application to/via MEH. As shown in step 635, UPF applies the QoS/PCC rule(s) to the data flow(s)/packets of the application.

Implementation and Advantages

Advantage, as described herein, include enabling the routing and/or policy information exchange between the MEC System and core network PCF to dynamically keep the core network PCF and UPF aware of which applications are available on the MEC System, how/where they are available and which policies shall be applied to related data flows. A minimum implementation extends an existing ETSI MEC or 3GPP interface / reference point and defines it to be used between the ME Host and PCF to cover the suggested issues.

There is no interface like the suggested N-new between the MEC System and core network PCF. The N5 interface between AF and PCF in the current 3 GPP architecture is meant for session information exchange between the AF and PCF, whereas the N-new is a management interface to be used for exchanging application specific, non-session-related, information.

The interface between the ME Host / Platform and PCF may keep the MEC System independent and agnostic on the core network and may have no impact, for example, on MEO.

An important use case is the integration of the MEC concept defined by ETSI into the 3GPP 5G network architecture (as part of the ongoing 5G standardization work in 3GPP and ETSI ISG MEC phase 2 work). Operation

Figure 5, described above, shows a flowchart of the exemplary operations performed by a method, apparatus and computer program product in accordance with an embodiment of the present invention. It will be understood that each block of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by various means, such as hardware, firmware, processor, circuitry and/or other device associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory 26 of an apparatus employing an embodiment of the present invention and executed by a processor 24 in the apparatus. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (for example, hardware) to produce a machine, such that the resulting computer or other programmable apparatus provides for implementation of the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer-readable storage memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage memory produce an article of manufacture, the execution of which implements the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart block(s). As such, the operations of Figure 5 when executed, converts a computer or processing circuitry into a particular machine configured to perform an example embodiment of the present invention. Accordingly, the operations of Figure 5 defines an algorithm for configuring a computer or processing to perform an example embodiment. In some cases, a general purpose computer may be provided with an instance of the processor which performs the algorithms of Figure 5 to transform the general purpose computer into a particular machine configured to perform an example embodiment. Accordingly, blocks of the flowchart support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware- based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.

In some embodiments, certain ones of the operations herein may be modified or further amplified. It should be appreciated that each of the modifications, optional additions or amplifications may be included with the operations above either alone or in combination with any others among the features described herein.

Exemplary Embodiments

In some embodiments, a method may be provided, the method comprising providing an interface between a first entity configured for managing applications available on a specific platform and a second entity configured for controlling routing or policy operations on a local user plane function (UPF) in a core network.

In some embodiments, the first entity is a multi-access edge computing (MEC) system. In some embodiments, the second entity is a core network policy control function (PCF) entity. In some embodiments, the method may further comprise keeping the second entity, the core network policy control (PCF), aware of the applications and services that are available at a ME Host. In some embodiments, the method may further comprise providing the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows, including "via MEC" flows, to or via the ME Host.

In some embodiments, the method may further comprise providing the PCF with application specific policy information to enable the PCF to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows. In some embodiments, the method may further comprise providing the PCF with application identification information that enables the above described operations. In some embodiments, the method may further comprise providing PCF with information that enables PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host. In some embodiments, the method may further comprise causing awareness of the ME Host / System of the topology to identify the UPF(s) to be addressed and causing transmission of the identifier(s) of the UPF(s) to PCF.

In some embodiments, a method may be provided, the method comprising causing introduction of an application on a ME Host, providing, via the MEC System, ME Host, or ME Platform, the core network PCF with the application specific information, and causing PCF to create application specific routing or PCC rules, heeding operator policies.

In some embodiments, the method may further comprise causing deduction or determination, by the PCF, of which UPF(s) to address, and causing transmission, by the PCF, of the rules and information to SMF. In some embodiments, the method may further comprise causing identification or determination, by the SMF, of the UPF(s) to be addressed, and causing transmission of the rules and related information to the UPF(s). In some embodiments, the method may further comprise causing application, by the UPF, of the routing rules to route the data flow(s)/packets of the application to/via MEH. In some embodiments, the method may further comprise causing application, by the UPF, QoS/PCC rule(s) to the data flow(s)/packets of the application.

In some embodiments an apparatus may be provided, the apparatus comprising means for providing an interface between a first entity configured for managing applications available on a specific platform and a second entity configured for controlling routing or policy operations on a local user plane function (UPF) in a core network. In some embodiments, the first entity is a multi-access edge computing (MEC) system. In some embodiments, the second entity is a core network policy control function (PCF) entity.

In some embodiments, the apparatus may further comprise means for keeping the second entity, the core network policy control (PCF), aware of the applications and services that are available at a ME Host. In some embodiments, the apparatus may further comprise means for providing the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows, including "via MEC" flows, to or via the ME Host. In some embodiments, the apparatus may further comprise means for providing the PCF with application specific policy information to enable the PCF to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows. In some embodiments, the apparatus may further comprise means for providing the PCF with application identification information that enables the above described operations. In some embodiments, the apparatus may further comprise means for providing PCF with information that enables PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host. In some embodiments, the apparatus may further comprise means for causing awareness of the ME Host / System of the topology to identify the UPF(s) to be addressed and causing transmission of the identifier(s) of the UPF(s) to PCF.

In some embodiments, an apparatus may be provided, the apparatus comprising means for causing introduction of an application on a ME Host, means for providing, via the MEC System, ME Host, or ME Platform, the core network PCF with the application specific information, and means for causing PCF to create application specific routing or PCC rules, heeding operator policies..

In some embodiments, the apparatus may further comprise means for causing deduction or determination, by the PCF, of which UPF(s) to address, and means for causing transmission, by the PCF, of the rules and information to SMF. In some embodiments, the apparatus may further comprise means for causing identification or determination, by the SMF, of the UPF(s) to be addressed, and means for causing transmission of the rules and related information to the UPF(s). In some embodiments, the apparatus may further comprise means for causing application, by the UPF, of the routing rules to route the data flow(s)/packets of the application to/via MEH. In some embodiments, the apparatus may further comprise means for causing application, by the UPF, QoS/PCC rule(s) to the data flow(s)/packets of the application.

In some embodiments, a computer program product may be provided, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer- executable program code instructions comprising program code instructions for providing an interface between a first entity configured for managing applications available on a specific platform and a second entity configured for controlling routing or policy operations on a local user plane function (UPF) in a core network. In some embodiments, the first entity is a multi-access edge computing (MEC) system. In some embodiments, the second entity is a core network policy control function (PCF) entity. In some embodiments, the computer-executable program code instructions further comprise program code instructions for keeping the second entity, the core network policy control (PCF), aware of the applications and services that are available at a ME Host. In some embodiments, the computer-executable program code instructions further comprise program code instructions for providing the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows, including "via MEC" flows, to or via the ME Host. In some embodiments, the computer-executable program code instructions further comprise program code instructions for providing the PCF with application specific policy information to enable the PCF to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows.

In some embodiments, the computer-executable program code instructions further comprise program code instructions for providing the PCF with application identification information that enables the above described operations. In some embodiments, the computer-executable program code instructions further comprise program code instructions for providing the PCF with application specific policy information to enable the PCF to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows. In some embodiments, the computer-executable program code instructions further comprise program code instructions for providing PCF with information that enables PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host. In some embodiments, the computer-executable program code instructions further comprise program code instructions for causing awareness of the ME Host / System of the topology to identify the UPF(s) to be addressed and causing transmission of the identifier(s) of the UPF(s) to PCF.

In some embodiments, a computer program product may be provided, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer- executable program code instructions comprising program code instructions for causing introduction of an application on a ME Host, providing, via the MEC System, ME Host, or ME Platform, the core network PCF with the application specific information, and causing PCF to create application specific routing or PCC rules, heeding operator policies. In some embodiments, the computer-executable program code instructions further comprise program code instructions for causing deduction or determination, by the PCF, of which UPF(s) to address, and causing transmission, by the PCF, of the rules and information to SMF. In some embodiments, the computer-executable program code instructions further comprise program code instructions for causing identification or determination, by the SMF, of the UPF(s) to be addressed, and causing transmission of the rules and related information to the UPF(s).

In some embodiments, the computer-executable program code instructions further comprise program code instructions for causing application, by the UPF, of the routing rules to route the data flow(s)/packets of the application to/via MEH. In some embodiments, the computer-executable program code instructions further comprise program code instructions for causing application, by the UPF, QoS/PCC rule(s) to the data flow(s)/packets of the application.

In some embodiments, an apparatus may be provided, the apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the processor, cause the apparatus to at least provide an interface between a first entity configured for managing applications available on a specific platform and a second entity configured for controlling routing or policy operations on a local user plane function (UPF) in a core network. In some embodiments, the first entity is a multi-access edge computing (MEC) system. In some embodiments, the second entity is a core network policy control function (PCF) entity.

In some embodiments, the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to keep the second entity, the core network policy control (PCF), aware of the applications and services that are available at a ME Host. In some embodiments, the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to provide the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows, including "via MEC" flows, to or via the ME Host. In some embodiments, the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to provide the PCF with application specific policy information to enable the PCF to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows.

In some embodiments, the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to provide the PCF with application identification information that enables the above described operations. In some embodiments, the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to provide PCF with information that enables PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host. In some embodiments, the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to causing awareness of the ME Host / System of the topology to identify the UPF(s) to be addressed and causing transmission of the identifier(s) of the UPF(s) to PCF.

In some embodiments, an apparatus may be provided, the apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the processor, cause the apparatus to at least cause introduction of an application on a ME Host, provide, via the MEC System, ME Host, or ME Platform, the core network PCF with the application specific information, and cause PCF to create application specific routing or PCC rules, heeding operator policies.

In some embodiments, the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to cause deduction or determination, by the PCF, of which UPF(s) to address, and cause transmission, by the PCF, of the rules and information to SMF. In some embodiments, the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to cause identification or determination, by the SMF, of the UPF(s) to be addressed, and cause transmission of the rules and related information to the UPF(s). In some embodiments, the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to cause application, by the UPF, of the routing rules to route the data flow(s)/packets of the application to/via MEH. In some embodiments, the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to cause application, by the UPF, QoS/PCC rule(s) to the data flow(s)/packets of the application.

Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

What is claimed is:

1. A method comprising:

providing an interface between a first entity configured for managing applications available on a specific platform and a second entity configured for controlling routing or policy operations on a local user plane function (UPF) in a core network.

2. The method according to Claim 1, wherein the first entity is a multi-access edge computing (MEC) system.

3. The method according to Claim 2, wherein the second entity is a core network policy control function (PCF) entity.

4. The method according to any of Claim 1 to 3, further comprising:

keeping the second entity, the core network policy control (PCF), aware of the applications and services that are available at a ME Host.

5. The method according to any of Claim 1 to 4, further comprising:

providing the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows, including "via MEC" flows, to or via the ME Host.

6. The method according to any of Claim 1 to 5, further comprising:

providing the PCF with application specific policy information to enable the PCF to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows.

7. The method according to any of Claim 1 to 6, further comprising:

providing the PCF with application identification information that enables the above described operations.

8. The method according to any of Claim 1 to 7, the method further comprising:

providing PCF with information that enables PCF or SMF to find the correct UPF or

UPFs connected to the particular ME Host.

9. The method according to any of Claim 1 to 7, the method further comprising:

causing awareness of the ME Host / System of the topology to identify the UPF(s) to be addressed and causing transmission of the identifier(s) of the UPF(s) to PCF.

10. A method, the method comprising:

causing introduction of an application on a ME Host;

providing, via the MEC System, ME Host, or ME Platform, the core network PCF with the application specific information; and

causing PCF to create application specific routing or PCC rules, heeding operator policies.

11. The method according to Claim 10, the method further comprising:

causing deduction or determination, by the PCF, of which UPF(s) to address; and causing transmission, by the PCF, of the rules and information to SMF.

12. The method according to Claim 11, the method further comprising:

causing identification or determination, by the SMF, of the UPF(s) to be addressed; and

causing transmission of the rules and related information to the UPF(s).

13. The method according to Claim 12, the method further comprising:

causing application, by the UPF, of the routing rules to route the data flow(s)/packets of the application to/via MEH.

14. The method according to Claim 13, the method further comprising:

causing application, by the UPF, QoS/PCC rule(s) to the data flow(s)/packets of the application.

15. An apparatus comprising: means for providing an interface between a first entity configured for managing applications available on a specific platform and a second entity configured for controlling routing or policy operations on a local user plane function (UPF) in a core network.

16. The apparatus according to Claim 15, wherein the first entity is a multi-access edge computing (MEC) system.

17. The apparatus according to Claim 15 or 16, wherein the second entity is a core network policy control function (PCF) entity.

18. The apparatus according to any of Claim 15 to 17, further comprising:

means for keeping the second entity, the core network policy control (PCF), aware of the applications and services that are available at a ME Host.

19. The apparatus according to any of Claim 15 to 18, further comprising:

means for providing the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows, including "via MEC" flows, to or via the ME Host.

20. The apparatus according to any of Claim 15 to 19, further comprising:

means for providing the PCF with application specific policy information to enable the PCF to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows.

21. The apparatus according to one of Claims 15 or 20, the apparatus further comprising: means for providing the PCF with application identification information that enables the above described operations.

22. The apparatus according to any of Claim 15 to 21, further comprising means for providing PCF with information that enables PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host.

23. The apparatus according to any of Claim 15 to 21, the apparatus further comprising: means for causing awareness of the ME Host / System of the topology to identify the UPF(s) to be addressed and causing transmission of the identifier(s) of the UPF(s) to PCF.

24. An apparatus, the apparatus comprising:

means for causing introduction of an application on a ME Host;

means for providing, via the MEC System, ME Host, or ME Platform, the core network PCF with the application specific information; and

means for causing PCF to create application specific routing or PCC rules, heeding operator policies..

25. The apparatus according to Claim 24, further comprising:

means for causing deduction or determination, by the PCF, of which UPF(s) to address; and

means for causing transmission, by the PCF, of the rules and information to SMF.

26. The apparatus according to claim 24 or claim 25, further comprising:

means for causing identification or determination, by the SMF, of the UPF(s) to be addressed; and

means for causing transmission of the rules and related information to the UPF(s).

27. The apparatus according to any of claims 24 to 26, further comprising:

means for causing application, by the UPF, of the routing rules to route the data flow(s)/packets of the application to/via MEH.

28. The apparatus according to any of claims 24 to 27, further comprising:

means for causing application, by the UPF, QoS/PCC rule(s) to the data flow(s)/packets of the application.

29. A computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising program code instructions for: providing an interface between a first entity configured for managing applications available on a specific platform and a second entity configured for controlling routing or policy operations on a local user plane function (UPF) in a core network.

30. The computer program product according to Claim 29,

wherein the first entity is a multi-access edge computing (MEC) system.

31. The computer program product according to Claim 29 or 30, wherein the second entity is a core network policy control function (PCF) entity.

32. The computer program product according to any of Claims 29 to 31, wherein the computer-executable program code instructions further comprise program code instructions for:

33. The computer program product according to Claim 32, wherein the computer-executable program code instructions further comprise program code instructions for:

34. The computer program product according to any of Claims 29 to 33, wherein the computer-executable program code instructions further comprise program code instructions for: providing the PCF with application specific policy information to enable the PCF to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows.

35. The computer program product according to any of Claims 29 or 34, wherein the computer-executable program code instructions further comprise program code instructions for:

providing the PCF with application identification information that enables the above described operations, providing the PCF with application specific policy information to enable the PCF to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows.

36. The computer program product according to any of Claims 29 to 35, wherein the computer-executable program code instructions further comprise program code instructions for:

providing PCF with information that enables PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host.

37. The computer program product according to any of Claims 29 to 35, wherein the computer-executable program code instructions further comprise program code instructions for:

38. A computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising program code instructions for: causing introduction of an application on a ME Host;

providing, via the MEC System, ME Host, or ME Platform, the core network PCF with the application specific information; and causing PCF to create application specific routing or PCC rules, heeding operator policies.

39. The computer program product according to Claim 38, wherein the computer-executable program code instructions further comprise program code instructions for:

40. The computer program product according to any of Claims 38 or 39, wherein the computer-executable program code instructions further comprise program code instructions for:

causing transmission of the rules and related information to the UPF(s).

41. The computer program product according to any of Claims 38 to 40, wherein the computer-executable program code instructions further comprise program code instructions for:

42. The computer program product according to any of Claims 38 to 41, wherein the computer-executable program code instructions further comprise program code instructions for:

43. An apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the processor, cause the apparatus to at least: provide an interface between a first entity configured for managing applications available on a specific platform and a second entity configured for controlling routing or policy operations on a local user plane function (UPF) in a core network.

44. The apparatus according to Claim 43,

wherein the first entity is a multi-access edge computing (MEC) system.

45. The apparatus according to any of Claim 43 to 44,

wherein the second entity is a core network policy control function (PCF) entity.

46. The apparatus according to any of Claim 43 to 45, wherein the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to:

keep the second entity, the core network policy control (PCF), aware of the applications and services that are available at a ME Host.

47. The apparatus according to any of Claim 43 to 46, wherein the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to:

provide the PCF with application specific routing information to enable the PCF to create routing rules for the local UPF to route MEC specific data flows, including "via MEC" flows, to or via the ME Host.

48. The apparatus according to any of Claim 43 to 47, wherein the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to:

provide the PCF with application specific policy information to enable the PCF to create QoS or PCC rules to be enforced by the local UPF on the MEC application specific data flows.

49. The apparatus according to any of Claim 43 to 48, wherein the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to:

provide the PCF with application identification information that enables the above described operations.

50. The apparatus according to any of Claim 43 to 49, wherein the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to:

provide PCF with information that enables PCF or SMF to find the correct UPF or UPFs connected to the particular ME Host.

51. The apparatus according to any of Claim 43 to 49, wherein the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to:

52. An apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the processor, cause the apparatus to at least:

cause introduction of an application on a ME Host;

provide, via the MEC System, ME Host, or ME Platform, the core network PCF with the application specific information; and

cause PCF to create application specific routing or PCC rules, heeding operator policies.

53. The apparatus according to any of Claim 52, wherein the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to: cause deduction or determination, by the PCF, of which UPF(s) to address; and cause transmission, by the PCF, of the rules and information to SMF.

54. The apparatus according to any of Claims 52 to 53, wherein the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to:

cause identification or determination, by the SMF, of the UPF(s) to be addressed; and

cause transmission of the rules and related information to the UPF(s).

55. The apparatus according to any of Claims 52 to 54, wherein the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to:

cause application, by the UPF, of the routing rules to route the data flow(s)/packets of the application to/via MEH.

56. The apparatus according to any of Claims 52 to 55, wherein the at least one memory and the computer program code are further configured to, with the processor, cause the apparatus to:

cause application, by the UPF, QoS/PCC rule(s) to the data flow(s)/packets of the application.