TECHNICAL FIELD

The present disclosure relates to the field of service delivery and control in communication systems, in particular communication networks such as 5G and 6G systems and beyond. The disclosure further relates to a network entity for routing application data towards at least one User Equipment (UE). In particular, the disclosure relates to an evolved User Plane Function (UPF) for application execution and caching in mobile networks.

BACKGROUND

6G systems will enable operators to use virtual compute resources to offer added services which is important for applications with stringent requirements such as video conferencing, VR, drone control, among others. One major issue is that Edge compute nodes are architecturally still outside of the mobile network. This makes it hard to guarantee performance and control edge nodes and it does not make it efficient to deliver critical applications from outside of the transport network.

Evidently, operator networks are the best place to deploy services near end users. This is due to the proximity to RAN access points, which would enable SLA guarantees. However, Edge nodes do not have specific architecture for application delivery. This means that each vendor has specific edge implementations and cannot use specific approaches for running and executing applications from other use-cases/scenarios.

In current 5G systems, UPF functionality is limited to routing and tunnel handling and cannot handle new types of applications. Nonstandard implementation of mobile edge compute will cause incompatibilities and performance degradation. Current UPF architecture and interaction do not allow to reduce latency by enabling application logic execution closer to the end user. In particular, it is not possible to deploy services at the UPF since the mechanisms are missing. Current approach will create ossification of deep edge technologies since every operator/vendor might create its own ecosystem.

SUMMARY

This disclosure provides a solution for an improved service delivery of user traffic in a mobile communication network. In particular, a solution is provided for enhancing service-specific functionalities in a mobile communication network such as a 3GPP network.

The foregoing and other objects are achieved by the features of the independent claims. Further implementation forms are apparent from the dependent claims, the description and the figures.

The disclosure presents a general scenario in which the mobile network achieves an improved service delivery of user traffic. In addition, an integrated deep edge delivery inside the 3GPP network is presented to enable specific service enhancing functionalities such as caching, storage, etc.

Within this scenario, UPF functionality is enhanced besides routing and tunnel handling to also handle new types of applications and enabling nonstandard implementation of mobile edge compute without causing incompatibilities and performance degradation.

A novel UPF architecture and interaction is presented that allows to reduce latency by enabling application logic execution closer to the end user (e.g., by caching, storage, etc.).

UPF is chosen as the best location to deploy user applications due to the low latency between UPF and UE which allows for an enhanced performance. In addition, powerful execution platform and storage at the UPF can be utilized. An enhanced UPF, as presented in this disclosure, is a possible evolution towards 6Gs where specific application logic can be deployed. Lastly, it allows to create added services for the operator.

The disclosure introduces mechanisms how the UPF can efficiently deploy user services. In particular, mechanisms for the UPF enhanced functions such as caching and data storage are presented. Specific mechanisms for deploying services at the UPF are introduced in this disclosure. The disclosed mechanisms allow to prevent creation of ossification of deep edge technologies since every operator/vendor can apply these mechanisms in a common ecosystem.

A basic concept presented in this disclosure is introduction of an evolved UPF architecture for improved service delivery. A solution is presented how to enhance and define an evolved UPF that includes the possibility to execute specific application and user logic. This enhanced UPF (eUPF) can be used for different types of application as per the usage scenario. Depending on what is needed, the eUPF can be used to run user application or even cache content for the users. The UPF can be enhanced with the following new modules or functionalities (see Figure 2):

1) Cache/Storage module

2) Local Agent module

3) API exposure module

4) Configuration control module

In addition to the definition of the specific modules of the UPF, the interfaces and APIs are defined that can be exposed by the enhanced UPF to other network functions. The main usage is for the SMF which can interact with the UPF.

In order to describe the disclosure in detail, the following terms, abbreviations and notations will be used:

3GPP third generation partnership project

UE user equipment

AF application function, application function entity

PCF policy control function, policy control function entity

SMF session management function; session management function entity AMF access and mobility management function; access and mobility management function entity

UPF user plane function; user plane function entity eUPF enhanced or evolved UPF

API application programming interface

SLA Service Level Agreement

RAN Radio Access Network

VR Virtual reality

PSA PDU session anchor

AN access network

A service-level agreement (SLA) is a contract between a service provider and its customers to document which services the provider will furnish and defines the service standards the provider is obligated to meet. Service providers need SLAs to help them manage customer expectations and define the severity levels and circumstances under which they are not liable for outages or performance issues. Customers can also benefit from SLAs because the contract describes the performance characteristics of the service -- which can be compared with other vendors' SLAs -- and sets forth the means for redressing service issues.

In this disclosure, edge computing, edge nodes in mobile communication systems for performing edge computing and deployment and control of services in 5G and 6G mobile communication systems are described.

Edge computing, or on demand provisioning of compute services very close to end-users, enables next generation applications especially in 6G mobile communication systems. The main advantage of deep (meaning as close to the user as possible) edge computing is its ability to offer services with very low latencies and high throughput. Which is very important for applications with stringent requirements such as: video conferencing, virtual reality, and drone control. Since the edge nodes are deployed close to end users it is possible to realize the best service delivery conditions.

In an edge computing scenario, the service provider provides the applications and usually deploys those compute instances in centralized clouds. The network operators on the other hand are responsible for creating and managing the mobile network as well as handling the connectivity between the user devices and the service providers. Evidently, the operator networks are the best place to deploy services near end users. This is mainly due to the proximity of RAN access points to the end users they are serving. This actually enables SLA guarantees.

According to a first aspect, the disclosure relates to a network entity for routing application data towards at least one User Equipment, UE, in a mobile communication network, the network entity comprising: a data storage for locally storing the application data in the network entity based on an application data configuration, the application data configuration being indicative of a configuration of the data storage for storing the application data, the application data being associated with at least one service in the communication network; an application programmable interface, API, configured to receive information about the application data configuration from a second network entity over the communication network; a configuration controller configured to control the data storage to store the application data based on the application data configuration; and a delivery controller for controlling delivery of the application data to the at least one UE over the communication network, wherein the delivery controller is configured, based on a request from the at least one UE for application data associated with the at least one service, to provide the at least one UE with the application data stored in the data storage; and if the application data associated with the at least one service is not stored in the data storage, to retrieve the application data from an application server or another network entity and provide the at least one UE with the application data retrieved from the application server.

Such network entity introduces a new functionality of the mobile communication network in which the mobile network achieves an improved service delivery of user traffic. In addition, an integrated deep edge delivery inside the 3GPP network can be realized to enable specific service enhancing functionalities such as caching, storage, etc. Within this scenario, functionality of the network entity (e.g., a UPF) is enhanced besides routing and tunnel handling to also handle new types of applications and enabling nonstandard implementation of mobile edge compute without causing incompatibilities and performance degradation. The novel functions of the network entity allow to reduce latency by enabling application logic execution closer to the end user (e.g., by caching, storage, etc.).

The new API can be for example an enhanced SMF UPF API. The new API enables new functions of interactions between SMF and UPF for example controlling specific configuration setup and application logic creation/instantiation.

In an exemplary implementation of the network entity, the application data comprises cacheable application data and non-cacheable application data, wherein the data storage is configured to store the cacheable application data.

This provides the advantage that the network entity can deliver both, cacheable content (i.e., cacheable application data) and non-cacheable content (i.e., dynamic content). For the noncacheable application data, the data storage may not be used, but the other entities such as the delivery controller (i.e., agent), the configuration controller and API may be used.

In an exemplary implementation of the network entity, the data storage is configured to clear the application data based on a clearance mechanism upon request of the delivery controller.

This provides the advantage that older application data can be efficiently deleted by using this clearance mechanism in order to create space for new application data.

The delivery controller may retrieve the application data configuration from the information about the application data configuration received from the API and store the application data configuration in the network entity. In an exemplary implementation of the network entity, the delivery controller is configured to store the application data in the data storage based on a command indicating the application data to be stored; and the delivery controller is configured to clear the application data from the data storage based on a command indicating the application data to be cleared.

This provides the advantage that storing and clearing the application data can be controlled and triggered from external.

In an exemplary implementation of the network entity, the delivery controller is configured to control at least one of: a size of the application data stored in the data storage, a granularity of the application data stored in the data storage, activating and/or deactivating the storing of application data per session, per application, per flow, per content-type, an encoding of the application data stored in the data storage, a replication of the application data stored in the data storage, a synchronization of the application data with application data stored in a data storage of another network entity for routing application data in the mobile communication network.

This provides the advantage that all relevant characteristics of the application data can be efficiently controlled.

In an exemplary implementation of the network entity, the API is configured to enable at least one of: control of the network entity from the second network entity, interaction of the network entity with another network entity for routing application data in the mobile communication network.

This network entity to network entity interaction provides the advantage of enabling the network entity (e.g., a UPF) to retrieve content from another network entity (e.g., another UPF), which can be cacheable or useful content creating a performant network.

In an exemplary implementation of the network entity, the configuration controller is configured to create the application data configuration based on a configuration programming language.

This provides the advantage that programming languages are generally available. Thus, creation of the application data configuration can be easily achieved.

In an exemplary implementation of the network entity, the configuration controller is configured to create the application data configuration based on at least one of: a mapping of deliverable services and/or contents to an identification of the at least one UE, a certificate of the deliverable services and/or contents.

This provides the advantage of additional security since a mapping and/or certificate must be available before creating the application data configuration.

In an exemplary implementation of the network entity, the API is configured to send the application data stored in the data storage to another network entity for routing application data in the mobile communication network upon request for content retrieval from the other network entity.

This provides the advantage that application data can be efficiently provided from the communication network since the application data can be easily accessed from the network entity or from another network entity of the mobile network by using the above routing mechanism.

In an exemplary implementation of the network entity, the API is configured to receive integrity information from the other network entity and to send the application data to the other network entity upon verification of the integrity information.

This provides the advantage of improved security since the integrity information from another network entity must be validated before sending application data to the other network entity.

In an exemplary implementation of the network entity, the delivery controller is configured to verify the integrity information based on initial integrity information received from the second network entity upon establishment of a packet data unit, PDU, session.

This provides the advantage that the initial integrity information allows the delivery controller to verify the integrity information in order to secure the sending of application data.

In an exemplary implementation of the network entity, the network entity is connected via an access network to the at least one UE; and the other network entity is connected via another access network to the at least one UE, the other network entity being located within a mobility range of the at least one UE.

This provides the advantage that roaming can be easily implemented when the UE moves from one access network to another access network. In an exemplary implementation of the network entity, the network entity is based on a user plane function, UPF, entity according to 3GPP standardization which is enhanced by functionalities of the data storage, the API, the configuration controller and the delivery controller.

Such network entity provides the advantage of an enhanced UPF architecture which enables the UPF to host application and cache content and go beyond classical routing and tunnel handling functionalities. By providing host cacheable content close to end users, latency between UPF and UE can be advantageously reduced. By using the 3GPP standardization as basis for the network entity, the standard method for handling application hosting of the UPF can be applied. This corresponds to the standard way without creating multiple solutions for each different use case. Technical complexity can thus be reduced.

In an exemplary implementation of the network entity, the second network entity is based on a session management function, SMF, entity according to 3GPP standardization enhanced for providing the information about the application data configuration of the data storage for storing the application data.

By using the 3GPP standardization as basis for the second network entity, the standard method for handling the SMF entity can be applied. This corresponds to the standard way without creating multiple solutions for each different use case. Technical complexity can thus be reduced.

According to a second aspect, the disclosure relates to a method for routing application data by a network entity in a mobile communication network, the method comprising: locally storing application data in a data storage of the network entity based on an application data configuration, the application data configuration being indicative of a configuration of the data storage for storing the application data, the application data being associated with at least one service in the communication network; receiving, by an application programmable interface, API, of the network entity, information about the application data configuration from a second network entity over the communication network; controlling, by a configuration controller of the network entity, the data storage to store the application data based on the application data configuration; and controlling, by a delivery controller of the network entity, delivery of the application data to at least one User Equipment, UE over the communication network, the controlling comprising: providing the at least one UE with the application data stored in the data storage based on a request from the at least one UE for application data associated with the at least one service; and if no application data associated with the at least one service is stored in the data storage, retrieving the application data from an application server or another network entity and providing the at least one UE with the application data retrieved from the application server.

Such a method introduces a new functionality of the mobile communication network in which the mobile network achieves an improved service delivery of user traffic. In addition, the method allows to implement an integrated deep edge delivery inside the 3GPP network to enable specific service enhancing functionalities such as caching, storage, etc. Functionality of the network entity (e.g., a UPF) is enhanced. Besides routing and tunnel handling also new types of applications can be handled. Nonstandard implementation of mobile edge compute can be implemented without causing incompatibilities and performance degradation. The method allows to reduce latency by enabling application logic execution closer to the end user (e.g., by caching, storage, etc.).

According to a third aspect, the disclosure relates to a computer program product including computer executable code or computer executable instructions that, when executed, causes at least one computer to execute the method according to the second aspect described above.

The computer program product may run on a controller or processor for controlling the abovedescribed service in a mobile communication network, e.g., one of the components of the mobile communication network described in Figure 1.

According to a fourth aspect, the disclosure relates to a computer-readable medium, storing instructions that, when executed by a computer, cause the computer to execute the method according to the second aspect described above. Such a computer readable medium may be a non-transient readable storage medium. The instructions stored on the computer-readable medium may be executed by a controller or processor for controlling the above-described service in a mobile communication network, e.g., one of the components of the mobile communication network described in Figure 1.

BRIEF DESCRIPTION OF THE DRAWINGS

Further embodiments of the disclosure will be described with respect to the following figures, in which:

Figure 1 shows a block diagram illustrating the main architecture 100 with a mobile communication network 200 according to the disclosure; Figure 2 shows a schematic diagram illustrating a mobile communication network 200 with two network entities 120, 120a, in particular enhanced or evolved UPF entities, according to the disclosure;

Figures 3a and 3b show two exemplary message flow charts 300a, 300b related to an evolved UPF according to the disclosure;

Figure 4 shows a block diagram illustrating the main architecture 400 of an evolved mobile communication network 200 including an evolved UPF entity according to a first embodiment related to using the eUPF as a cache;

Figure 5 shows an exemplary message flow chart 500 illustrating message flow for the first embodiment shown in Figure 4;

Figure 6 shows a block diagram illustrating the main architecture 600 of an evolved mobile communication network 200 including evolved UPF entities 120, 120a according to a second embodiment related to fast retrieval of buffered packets upon user mobility; and

Figure 7 shows an exemplary message flow chart 700 illustrating message flow for the second embodiment shown in Figure 6.

DETAILED DESCRIPTION OF EMBODIMENTS

In the following detailed description, reference is made to the accompanying drawings, which form a part thereof, and in which is shown by way of illustration specific aspects in which the disclosure may be practiced. It is understood that other aspects may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

It is understood that comments made in connection with a described method may also hold true for a corresponding device or system configured to perform the method and vice versa. For example, if a specific method step is described, a corresponding device may include a unit to perform the described method step, even if such unit is not explicitly described or illustrated in the figures. Further, it is understood that the features of the various exemplary aspects described herein may be combined with each other, unless specifically noted otherwise.

Figure 1 shows a block diagram illustrating the main architecture 100 with a mobile communication network 200 according to the disclosure.

The mobile communication network 200 may be based on 3GPP standardization but is not restricted to that. In particular, the mobile communication network 200 may comprise the following 5G network functions of the 5G reference point architecture, e.g., as specified in 3GPP TS 38.300 and 3GPP TS 23.501 specifications: UPF 120, SMF 105, PCF 104, AMF 106, NEF 102, AF 103, UE 130, 130a, AN 112, PSA 110, 111.

UPF stands for User plane function. The functions of 5G NR UPF node or UPF entity are: Anchor point for lntra-/lnter-RAT mobility (when applicable); External PDU Session point of interconnect to Data Network; Packet routing & forwarding; Packet inspection; User Plane part of policy rule enforcement, e.g. Gating, Redirection, Traffic steering; Lawful intercept (UP collection); Traffic usage reporting; QoS handling for user plane, e.g. UL/DL rate enforcement, Reflective QoS marking in DL; Uplink Traffic verification (SDF to QoS Flow mapping); Transport level packet marking in the uplink and downlink; Downlink packet buffering and downlink data notification triggering; Sending and forwarding of one or more "end marker" to the source NG-RAN node.

SMF stands for Session Management Function. The functions of 5G NR SMF node or SMF entity are: Session Management; UE IP address allocation and management; Selection and control of UP function; Configures traffic steering at UPF to route traffic to proper destination; Control part of policy enforcement and QoS; Downlink Data Notification.

PCF stands for Policy Control Function. The functions of 5G NR PCF node or PCF entity are: Support of unified policy framework to govern network behavior; Providing policy rules to Control Plane function(s) to enforce them; Accessing subscription information relevant for policy decisions in a Unified Data Repository (UDR).

AMF stands for Access and Mobility Management Function. AMF is part of the 3GPP 5G Architecture. Its primary tasks include: Registration Management, Connection Management, Reachability Management, Mobility Management and various function relating to security and access management and authorization.

The edge cloud 114 is represented in Figure 1 outside the mobile communication network 200. A central cloud 113 is also located outside the mobile communication network 200.

The mobile communication network 200 can be any mobile communication network or system or operator network. It is not restricted to the 3GPP system 200 as shown in Figure 1 .

The concept presented in this disclosure relates to the scenario of a mobile network 200 with an improved service delivery. In order to reduce latency and improve performance, a network entity of the mobile network 200, in particular the UPF 120, can be enhanced with additional user plane functionality that can be used to execute application logics. This includes caching, APIs calls, configuration control, as well as generic application execution. Figure 1 depicts a generic scenario in which the execution of application logic is moved from the edge cloud 114 into the mobile network 200 and specifically into the UPF 120.

The solution presented in this disclosure specifies an evolved UPF architecture for improved service delivery. The solution enhances and defines an evolved network entity, in particular an evolved UPF 120, that includes the functionality to execute specific application and user logic. This enhanced UPF, referred to as eUPF 120 hereinafter, can be used for different types of application as per the usage scenario. Depending on what is needed, the eUPF 120 can be used to run user application or even cache content for the users.

In the following, depending on the context, the term eUPF or the term UPF is used. UPF relates to the basic functionality of the standard UPF according to 3GPP while eUPF relates to the enhanced functionality of the UPF as presented in this disclosure. The UPF 120 can be enhanced with the following modules as shown in Figure 2 in more detail:

Cache/Storage module 123, Local Agent module 122, API exposure module 121 , and Configuration control module 124.

The cache/storage module 123 supports local storage of cacheable content and implements a cache eviction mechanism controlled by the agent 122.

The Local agent module 122 provides storage and retrieves configuration. It controls and manipulates that storage, gets commands what to store and what to evict. The Local agent module 122 provides cache management such as size, eviction, etc. It also provides object allow list management. The Local agent module 122 controls and activates or deactivates per session caching/proxying at different granularities, i.e., per app, per flow, per session, contenttype, etc. The Local agent module 122 provides cache replica management, e.g. cache synchronization between multiple eUPF to realize failover, multi-bin systems, or encoded content for security.

The API Exposure module 121 provides an API supporting controllability of smart UPF. It further provides an API supporting interaction between different smart UPFs. The Configuration control module 124 provides configuration language to keep track of settings and rules around the smart UPF (i.e., ellPF). Such configuration can be stored in YAML or similar. It includes cache eviction rules, hostname store, certificates, etc.

In addition to the definition of the specific modules of the UPF 120, the interfaces and APIs are defined that can be exposed by the enhanced UPF 120 to other network functions. The main usage is for the SMF 105 which can interact with the UPF 120.

The eUPF 120 exposes specific service methods or APIs to the other NFs (e.g., SMF 105) to enable controllability of the enhanced UPF 120 as described in the following. a) eUPF-SMF interface: This interface can be used by the SMF to create specific application (e.g. caching) configurations, control the agent, invoke usage of storage (extension of the N4 interface is possible). Such interface can be used to realize: 1) basic 5G UPF procedures such as PDU session handling, traffic shaping, traffic inspection, etc. 2) Evolved 6G UPF procedures such as trigger content caching, trigger application instantiation, trigger a generic command execution or serverless functions. b) eUPF-eUPF interface: This interface can be used by the eUPF 120 to interact with other UPFs and to use trigger functions at other UPFs 120a, e.g., retrieve already cached content at another UPF.

Figure 2 shows a schematic diagram illustrating a mobile communication network 200 with network entities 120, 120a, in particular enhanced or evolved UPF entities, according to the disclosure.

Figure 2 includes the main architecture presented in this disclosure. It provides the two evolved UPF units 120, 120a that each contain the modules: configuration 124, storage 123, agent 122, and API exposure 121 as well as includes the interfaces used for the interaction between the SMF 105 and the eUPF 120 and eUPF 120 and eUPF 120a.

The network entity 120 that may correspond to the eUPF 120 described above with respect to Figure 1 , can be used for routing application data 108 towards at least one User Equipment, UE 130, in the mobile communication network 200 corresponding to the mobile communication network 200 described above with respect to Figure 1 . It understands that the enhanced functionality of the network entity as described in this disclosure is preferably represented by the ell PF; however, any other network entity of the mobile communication network 200 can be used for implementing this enhanced functionality.

In the following, the functionality of the network entity 120 is described in more detail.

The network entity 120 comprises a data storage 123 for locally storing the application data 108 in the network entity 120 based on an application data configuration 109. The application data configuration 109 is indicating a configuration of the data storage 123 for storing the application data 108. The application data 108 is associated with at least one service in the communication network 200. The data storage 123 may correspond to the cache/storage module 123 described above with respect to Figure 1.

The network entity 120 comprises an application programmable interface, API 121 , configured to receive information about the application data configuration 109 from a second network entity 105 over the communication network 200. The API 121 may correspond to the API Exposure module 121 described above with respect to Figure 1. The second network entity 105 may correspond to the SMF 105 described above with respect to Figure 1.

The network entity 120 comprises a configuration controller 124 configured to control the data storage 123 to store the application data 108 based on the application data configuration 109. The configuration controller 124 may correspond to the Configuration control module 124 described above with respect to Figure 1.

The network entity 120 comprises a delivery controller 122 for controlling delivery of the application data 108 to the at least one UE 130 over the communication network 200. The delivery controller 122 may correspond to the Local agent module 122 described above with respect to Figure 1 .

The delivery controller 122 is configured, based on a request from the at least one UE 130 for application data associated with the at least one service, to provide the at least one UE 130 with the application data 108 stored in the data storage 123. If the application data associated with the at least one service is not stored in the data storage 123, the delivery controller 122 is configured to retrieve the application data 108 from an application server 409, e.g., an edge application server as shown in Figure 4, or another network entity and provide the at least one UE 130 with the application data 108 retrieved from the application server 409. The application data 108 may comprise cacheable application data and non-cacheable application data. The data storage 123 may be configured to store the cacheable application data.

The network entity can deliver both, cacheable content (i.e. , cacheable application data) and non-cacheable content (i.e., dynamic content). For the non-cacheable application data, the data storage may not be used, but the other entities such as the delivery controller (i.e., agent), the configuration controller and API may be used.

The data storage 123 may be configured to clear the application data 108 based on a clearance mechanism upon request of the delivery controller 122.

The delivery controller 122 may retrieve the application data configuration 109 from the information about the application data configuration 109 received from the API 121 and store the application data configuration 109 in the network entity 120.

The delivery controller 122 may be configured to store the application data 108 in the data storage 123 based on a command indicating the application data 108 to be stored. The delivery controller 122 may be configured to clear the application data 108 from the data storage 123 based on a command indicating the application data 108 to be cleared.

The delivery controller 122 may be configured to control at least one of: a size of the application data 108 stored in the data storage 123, a granularity of the application data 108 stored in the data storage 123, activating and/or deactivating the storing of application data 108 per session, per application, per flow, per content-type, an encoding of the application data 108 stored in the data storage 123, a replication of the application data 108 stored in the data storage 123, a synchronization of the application data 108 with application data stored in a data storage 123 of another network entity 120a for routing application data 108 in the mobile communication network 200.

The API 121 may be configured to enable at least one of: control of the network entity 120 from the second network entity 105, interaction of the network entity 120 with another network entity 120a for routing application data 108 in the mobile communication network 200.

The configuration controller 124 may be configured to create the application data configuration 109 based on a configuration programming language. The configuration controller 124 may be configured to create the application data configuration 109 based on at least one of: a mapping of deliverable services and/or contents to an identification of the at least one UE 130, a certificate of the deliverable services and/or contents.

The AP1 121 may be configured to send 606 the application data 108 stored in the data storage 123 to another network entity 120a for routing application data 108 in the mobile communication network 200 upon request 605 for content retrieval from the other network entity 120a, e.g., as described below with respect to Figures 6 and 7.

The API 121 may be configured to receive integrity information 607 from the other network entity 120a and to send the application data 108 to the other network entity 120a upon verification of the integrity information 607, e.g., as described below with respect to Figures 6 and 7.

The delivery controller 122 may be configured to verify the integrity information 607 based on initial integrity information received from the second network entity 105 upon establishment of a packet data unit, PDU, session 601.

The network entity 120 may be connected via an access network 112 to the at least one UE 130. The other network entity 120a may be connected via another access network 112 to the at least one UE 130, where the other network entity 120a may be located within a mobility range 603 of the at least one UE 130, e.g., as described below with respect to Figures 6 and 7.

As described above, the network entity 120 may be based on a user plane function, UPF, entity according to 3GPP standardization which is enhanced by functionalities of the data storage 123, the API 121 , the configuration controller 124 and the delivery controller 122 as described in this disclosure.

The second network entity 105 may be based on a session management function, SMF, entity according to 3GPP standardization enhanced for providing the information about the application data configuration 109 of the data storage 123 for storing the application data 108. It understands that the functionality of the second network entity 105 as described in this disclosure is not restricted to a SMF; it can also be implemented by any other network entity of the mobile communication network 200 shown in Figure 1. The architecture presented in Figures 1 and 2 also provide a method for routing application data 108 by a network entity 120 in a mobile communication network 200.

Such a method comprises the following:

Locally storing application data 108 in a data storage 123 of the network entity 120 based on an application data configuration 109, the application data configuration 109 being indicative of a configuration of the data storage 123 for storing the application data 108, the application data 108 being associated with at least one service in the communication network 200.

Receiving, by an application programmable interface, API, 121 of the network entity 120, information about the application data configuration 109 from a second network entity 105 over the communication network 200.

Controlling, by a configuration controller 124 of the network entity 120, the data storage 123 to store the application data 108 based on the application data configuration 109.

Controlling, by a delivery controller 122 of the network entity 120, delivery of the application data 108 to at least one User Equipment, UE 130 over the communication network 200.

Such controlling by the delivery controller 122 comprises: providing the at least one UE 130 with the application data 108 stored in the data storage 123 based on a request from the at least one UE 130 for application data associated with the at least one service; and if no application data associated with the at least one service is stored in the data storage 123, retrieving the application data 108 from an application server 409 or another network entity, e.g., as shown in Figure 4, and providing the at least one UE 130 with the application data 108 retrieved from the application server 409.

Figures 3a and 3b show two exemplary message flow charts 300a, 300b related to an evolved UPF according to the disclosure.

Figure 3a depicts UPF association with service specific capability, e.g., caching.

The eUPF 120 transmits an association setup request message 309 to the SMF 105 to inform the SMF 105 about UPF caching functionality.

Upon receiving this request message 309, the SMF 105 responds with association setup response message 310 including service-specific information such as hostnames, origin, keys, etc. Figure 3b depicts traffic steering with specific UPF capabilities, e.g., caching.

An application function (AF) 103 transmits an initialization message 301 to the SMF 105 to initialize the UPF with configuration such as cache, etc.

Upon receiving the initialization message 301 , the SMF performs UPF selection 302 considering proximity, latency, load etc, e.g., as described above with respect to Figures 1 and 2.

Then, the SMF 105 send a message 303 with service-specific information such as hostnames, origin, keys, etc. to the eUPF 120. The eUPF 120 acknowledges 304 this message 303. Upon receiving the acknowledgement 304 from eUPF 120, the SMF 105 stores DNS redirection configuration 305 such as hostname > UPF IP.

Upon receiving a message 306 from the UE 130 requesting DNS resolution for hostname, the SMF 105 provides a DNS response 307 with UPF IP to the UE 130.

Then, traffic (between UE 130 and eUPF 120) can be handled 308 by the UPF 120.

Figure 4 shows a block diagram illustrating the main architecture 400 of an evolved mobile communication network 200 including an evolved UPF entity according to a first embodiment related to using the eUPF as a cache.

The first embodiment is related to using an eUPF 120 as a cache. This enables caching of content very close to the end users thereby reducing the latency and improving performance. This embodiment can be summarized as follows:

The Evolved UPF 120 handles caching near end users.

The related novel functions of the UPF 120 used for the embodiment are: Storage 123, agent 122, api 121.

The storage may correspond to the data storage 123 as described above with respect to Figure 2. The agent 122 may correspond to the delivery controller 122 as described above with respect to Figure 2. The api 121 may correspond to the application programmable interface, API 121 , as described above with respect to Figure 2. Static content may be detected using standard http headers.

SMF/control entities control cache deletion if needed.

If cache is empty, the UPF 120 gets a copy of the file from the central cloud 113 (see Figure 1) or another UPF 120a (see Figure 2).

Figure 5 shows an exemplary message flow chart 500 illustrating message flow for the first embodiment shown in Figure 4.

The procedures related to the first embodiment are shown in Figure 5 and described in the following.

Messages are transmitted between the following entities: UE 130, UE2 130a, eUPF 120, EAS 409, SMF 105, AF 103 and other SMF 105a.

The flow chart 500 begins with initial traffic setup and creation 501 of end-to-end path from UE 130 and EAS 409.

The other SMF105a transmits a message 502 to the eUPF 120 to create a caching configuration.

UE 130 transmits a request 503 for cacheable content to the eUPF 120. The eUPF 120 forwards this request 503 as request 504 for cacheable content to the EAS 409. Edge application server, EAS 409 transmits message 505 to receive cacheable content to eUPF 120 and eUPF 120 stores 506 content as per configuration. eUPF 120 sends content 507 to UE 130.

When second UE 130a requests 508 cacheable content form eUPF 120, eUPF 120 can send 509 cacheable content from cache, i.e. , a fast delivery can be achieved.

While this embodiment is described in terms of cacheable content and caching configuration, it understands that the embodiment is not restricted to cacheable data. Instead, application data 108 and application data configuration 109 as described above with respect to Figure 2 can be implemented as well by this message chart 500. Figure 6 shows a block diagram illustrating the main architecture 600 of an evolved mobile communication network 200 including evolved UPF entities 120, 120a according to a second embodiment related to fast retrieval of buffered packets upon user mobility.

The second embodiment is related to fast retrieval of buffered packets upon user mobility. In case of user mobility, the UPF 120 (i.e. , eUPF) can be triggered to retrieve buffered packets from another UPF 120a (i.e., eUPF). The procedures are as follows.

SMF 105 enables fast transfer of buffer packets from one UPF 120 to another UPF 120a.

(1) SMF establishes 601 PDU session at oldeUPF 120.

(2) PDU session is established 602.

(3) mobility 603 to new AN triggers PDU session modification.

(4) session establishment procedures 604 select neweUPF 120a, SMF 105 includes oldUPF 120 information in session establishment procedures.

(5) newUPF 120a triggers 605 API call with oldeUPF 120 over N9 interface to retrieve buffered packets.

(6) oldeUPF 120 sends 606 buffered packets.

(7) neweUPF 120a validates 607 data integrity information.

Figure 7 shows an exemplary message flow chart 700 illustrating message flow for the second embodiment shown in Figure 6.

The procedures related to the second embodiment are shown in Figure 7.

Messages are transmitted between the following entities: NRF 720, SMF 105, NEWeUPF 120a and OLDeUPF 120.

The NRF 720 maintains an updated repository of all the 5G elements available in the operator's network along with the services provided by each of the elements in the 5G core that are expected to be instantiated, scaled and terminated without or minimal manual intervention. In addition to serving as a repository of the services, the NRF also supports discovery mechanisms that allows 5G elements to discover each other and get updated status of the desired elements.

The flow chart 500 begins with SMF 105 trigger 701 to create PDU session. Then SMF 105 retrieves 702 a list of evolved UPFs from NRF 720. NRF 720 sends 703 this list of eUPFs to SMF 105.

SMF 105 checks if existing ell PF was active for this UE. In this example, the answer is yes.

SMF 105 sends message 601 to NEWeUPF 120a for PDU session establishment including OLDeUPF 120 identity and integrity information. This message 601 may correspond to message 601 described above with respect to Figure 6. NEWeUPF 120a reponds 601a to message 601.

Then NEWeUPF 120a sends message 605 to OLDeUPF 120 to invoke remote eUPF API for content retrieval, buffer packets, etc. The message 605 includes integrity information. This message 605 may correspond to message 605 described above with respect to Figure 6.

OLDeUPF 120 verifies 607 the integrity information and sends response 605a to NEWeUPF 120a, e.g., as describe above with respect to Figure 6.

The messages described above with respect to Figures 3, 5 and 7 can be implemented as computer executable code or computer executable instructions or computer program for execution on a computer.

The computer program may run on a controller or processor for controlling the abovedescribed service in a mobile communication network, e.g., one of the components of the mobile communication network described in Figure 1 or Figure 2.

The solution presented in this disclosure can also be used for specific WIFI and fixed networks. For example, a WIFI node can be used to cache content and interact with the control plane.

While a particular feature or aspect of the disclosure may have been disclosed with respect to only one of several implementations, such feature or aspect may be combined with one or more other features or aspects of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms "include", "have", "with", or other variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term "comprise". Also, the terms "exemplary", "for example" and "e.g." are merely meant as an example, rather than the best or optimal. The terms “coupled” and “connected”, along with derivatives may have been used. It should be understood that these terms may have been used to indicate that two elements cooperate or interact with each other, regardless whether they are in direct physical or electrical contact, or they are not in direct contact with each other.

Although specific aspects have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and/or equivalent implementations may be substituted for the specific aspects shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the specific aspects discussed herein.

Although the elements in the following claims are recited in a particular sequence with corresponding labeling, unless the claim recitations otherwise imply a particular sequence for implementing some or all of those elements, those elements are not necessarily intended to be limited to being implemented in that particular sequence.

Many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the above teachings. Of course, those skilled in the art readily recognize that there are numerous applications of the disclosure beyond those described herein. While the present disclosure has been described with reference to one or more particular embodiments, those skilled in the art recognize that many changes may be made thereto without departing from the scope of the present disclosure. It is therefore to be understood that within the scope of the appended claims and their equivalents, the disclosure may be practiced otherwise than as specifically described herein.