Network entity for routing application data to user equipment

Abstract

The present disclosure relates to a network entity (120) for routing application data (108) to a user equipment, UE, (130) in a mobile communication network (200). The network entity comprises a data store (123) for locally storing the application data associated with at least one service in the communication network. The network entity comprises an API (121) for receiving information relating to an application data configuration (109) from a second network entity (105). The network entity comprises: a configuration controller (124) for controlling the data storage to store the application data based on the application data configuration; and a delivery controller (122) for controlling delivery of the application data to the UE. The delivery controller is configured to provide the application data stored in the data store to the UE; if the application data is not stored in the data store, the application data is retrieved from an application server (409) or another network entity.

Description

Technical Field

[0001] 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 higher-level communication networks. The present disclosure also relates to a network entity for routing application data to at least one user equipment (UE). In particular, the present disclosure relates to an evolved user plane function (UPF) for application execution and caching in a mobile network. Background Art

[0002] 6G systems will enable operators to provide additional services using virtualized computing resources, which is important for demanding applications such as video conferencing, VR, drone control, etc. A major problem is that edge computing nodes are still architecturally outside the mobile network. This makes it difficult to guarantee performance and control edge nodes, and it is impossible to efficiently deliver critical applications from outside the transport network.

[0003] Obviously, the operator network is the best place to deploy services close to the end user. This is due to the proximity to the RAN access point, which enables SLA guarantees. However, there is no specific application delivery architecture for edge nodes. This means that each vendor has a specific edge implementation and cannot use a specific approach to run and execute applications from other use cases / scenarios.

[0004] In current 5G systems, UPF functionality is limited to routing and tunnel processing and cannot handle new types of applications. Non-standard implementations of mobile edge computing lead to incompatibility and performance degradation. Current UPF architecture and interactions cannot reduce latency by bringing application logic execution closer to end users. Specifically, it is impossible to deploy services on UPF due to the lack of these mechanisms. The current approach will lead to rigidity of deep edge technology, as each operator / vendor may create its own ecosystem. Summary of the invention

[0005] The present disclosure provides a solution for improving service delivery of user traffic in a mobile communication network.

[0006] Specifically, a solution for enhancing service-specific functions in a mobile communication network such as a 3GPP network is provided.

[0007] The above and other purposes are achieved by the features of the independent technical solutions. Other implementations are obvious in the dependent technical solutions, the description and the drawings.

[0008] This disclosure proposes a general scenario for mobile networks to achieve improved service delivery for user traffic. In addition, it also proposes integrated deep edge delivery within the 3GPP network to achieve specific service enhancements, such as caching, storage, etc.

[0009] In this scenario, in addition to routing and tunnel processing, UPF functionality is enhanced to handle new types of applications and support non-standard implementations of mobile edge computing without causing incompatibility and performance degradation.

[0010] A novel UPF architecture and interaction is proposed to reduce latency by bringing application logic execution closer to end users (e.g., through caching, storage, etc.).

[0011] Since the low latency between UPF and UE can enhance performance, UPF is selected as the best location to deploy user applications. In addition, the powerful execution platform and storage of UPF can be utilized. The enhanced UPF proposed in this disclosure is a possible evolution to 6G where specific application logic can be deployed. Finally, such UPF can create additional services for operators.

[0012] This disclosure describes mechanisms for how UPF can efficiently deploy user services. Specifically, mechanisms for UPF enhancements such as caching and data storage are proposed. This disclosure describes specific mechanisms for deploying services in UPF. The disclosed mechanisms can prevent the rigidity of deep edge technologies because each operator / vendor can apply these mechanisms in a common ecosystem.

[0013] The basic concept proposed in this disclosure is to introduce an evolved UPF architecture for improving service delivery.

[0014] A solution is proposed, how to enhance and define an evolved UPF, including the possibility to execute specific application and user logic. This enhanced UPF (eUPF) can be used for different types of applications depending on the usage scenario. Depending on the need, the eUPF can be used to run user applications or even cache content for the user. The UPF can be enhanced with the following new modules or features (see Figure 2 ):

[0015] 1) Cache / Storage Module

[0016] 2) Local proxy module

[0017] 3) API open module

[0018] 4) Configure the control module

[0019] In addition to defining specific modules of UPF, it also defines interfaces and APIs that the enhanced UPF can open to other network functions. The main purpose is for SMFs that can interact with UPF.

[0020] To describe the present disclosure in detail, the following terms, abbreviations and symbols will be used:

[0021] 3GPP Third Generation Partnership Project

[0022] UE User Equipment

[0023] AF application function, application function entity

[0024] PCF Policy control function, policy control function entity

[0025] SMF session management function; session management function entity

[0026] AMF access and mobility management function; access and mobility management function entity (access and mobility management function; access and mobility management function entity)

[0027] UPF user plane function; user plane function entity

[0028] eUPF enhanced or evolved UPF

[0029] API application programming interface

[0030] SLA Service Level Agreement

[0031] RAN Radio Access Network

[0032] VR Virtual reality

[0033] PSA PDU session anchor

[0034] AN access network

[0035] A service-level agreement (SLA) is a contract between a service provider and its customers that documents what services the provider will provide and defines the service standards the provider is obligated to meet. Service providers need SLAs to help them manage customer expectations and define severity levels and specific circumstances under which the service provider is not responsible for downtime or performance issues. Customers also benefit from SLAs because the contract describes the performance characteristics of the service (which can be compared to other vendors' SLAs) and specifies how to correct service issues.

[0036] In the present disclosure, edge computing, edge nodes for performing edge computing in a mobile communication system, and service deployment and control in 5G and 6G mobile communication systems are described.

[0037] Edge computing, or the on-demand provision of computing services very close to the end user, will enable 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 the ability to provide services with very low latency and high throughput. This is very important for demanding applications such as video conferencing, virtual reality, and drone control. Since edge nodes are deployed close to the end user, optimal service delivery conditions can be achieved.

[0038] In edge computing scenarios, service providers provide applications and typically deploy these computing instances in a centralized cloud. On the other hand, network operators are responsible for creating and managing mobile networks and handling connections between user devices and service providers. Obviously, the operator network is the best place to deploy services close to end users. This is mainly due to the proximity of RAN access points to the end users they serve. This actually achieves SLA guarantees.

[0039] According to a first aspect, the present disclosure relates to a network entity for routing application data to at least one user equipment (UE) in a mobile communication network, the network entity comprising: a data store for locally storing the application data in the network entity based on an application data configuration, the application data configuration indicating a configuration of the data store for storing the application data, the application data being associated with at least one service in the communication network; an application programmable interface (API) for receiving information related to the application data configuration from a second network entity via the communication network; a configuration controller for controlling the data store to store the application data based on the application data configuration; a delivery controller for controlling the delivery of the application data to the at least one UE via the communication network; wherein the delivery controller is used to provide the application data stored in the data store to the at least one UE based on a request from the at least one UE for the application data associated with the at least one service; if the application data associated with the at least one service is not stored in the data store, retrieving the application data from an application server or another network entity and providing the application data retrieved from the application server to the at least one UE.

[0040] This network entity introduces new capabilities for mobile communication networks, where the mobile network enables improved service delivery for user traffic. In addition, integrated deep edge delivery inside the 3GPP network can be implemented to enable specific service enhancements such as caching, storage, etc. In this scenario, in addition to routing and tunnel processing, the capabilities of the network entity (e.g., UPF) are enhanced to handle new types of applications and support non-standard implementations of mobile edge computing without causing incompatibility and performance degradation. The new capabilities of the network entity can reduce latency by bringing application logic execution closer to the end user (e.g., through caching, storage, etc.).

[0041] The new API may be, for example, an enhanced SMF UPF API. The new API implements new functionality for interaction between SMF and UPF, such as controlling specific configuration settings and application logic creation / instantiation.

[0042] In an exemplary implementation of the network entity, the application data includes cacheable application data and non-cacheable application data, wherein the data storage is used to store the cacheable application data.

[0043] This provides the following advantages: Network entities can deliver both cacheable content (i.e., cacheable application data) and non-cacheable content (i.e., dynamic content). For non-cacheable application data, data stores may not be used, but other entities such as delivery controllers (i.e., proxies), configuration controllers, and APIs may be used.

[0044] In an exemplary implementation of the network entity, the data storage is used to purge the application data based on a purge mechanism according to a request of the delivery controller.

[0045] This provides the advantage that old application data can be efficiently deleted by using this cleanup mechanism to create space for new application data.

[0046] The delivery controller may retrieve the application data configuration from information related to the application data configuration received from the API and store the application data configuration in the network entity.

[0047] In an exemplary implementation of the network entity, the delivery controller is used to store the application data in the data store based on a command indicating the application data to be stored; the delivery controller is used to clear the application data from the data store based on a command indicating the application data to be cleared.

[0048] This offers the advantage that the storage and clearing of application data can be controlled and triggered externally.

[0049] In an exemplary implementation of the network entity, the delivery controller is used to control at least one of the following: the size of the application data stored in the data store; the granularity of the application data stored in the data store; the activation and / or deactivation of the storage of application data for each session, each application, each flow, and each content type; the encoding of the application data stored in the data store; the replication of the application data stored in the data store; the synchronization of the application data with the application data stored in the data store of another network entity, for routing the application data in the mobile communication network.

[0050] This offers the advantage that all relevant characteristics of the application data can be efficiently controlled.

[0051] In an exemplary implementation of the network entity, the API is used to implement at least one of the following: control of the network entity by the second network entity; interaction between the network entity and another network entity for routing application data in the mobile communication network.

[0052] This network entity to network entity interaction provides the advantage of enabling a network entity (eg, a UPF) to retrieve content from another network entity (eg, another UPF) that may be cacheable or useful content to create a high performance network.

[0053] 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.

[0054] This offers the advantage that programming languages ​​are generally available. Therefore, the creation of application data configurations can be easily achieved.

[0055] 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 content to an identity of the at least one UE; a certificate of the deliverable services and / or content.

[0056] This provides the advantage of additional security because the mapping and / or certificates must be available before the application data configuration is created.

[0057] In an exemplary implementation of the network entity, the API is used to send the application data stored in the data store to another network entity to route the application data in the mobile communication network upon requesting content retrieval from the other network entity.

[0058] This provides the advantage that application data may be efficiently provided from the communication network, since the application data may be easily accessed from the network entity or from another network entity of the mobile network by using the above-mentioned routing mechanism.

[0059] In an exemplary implementation of the network entity, the API is used to receive integrity information from the other network entity and send the application data to the other network entity after the integrity information is verified.

[0060] This provides the advantage of increased security, since integrity information from another network entity must be verified before application data is sent to the other network entity.

[0061] 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 after a packet data unit (PDU) session is established.

[0062] This provides the advantage that the initial integrity information may enable the delivery controller to verify the integrity information to ensure the sending of the application data.

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

[0064] This provides the following advantage: when the UE moves from one access network to another access network, roaming can be easily achieved.

[0065] In an exemplary implementation of the network entity, the network entity is based on a user plane function (UPF) entity standardized according to 3GPP, and the UPF entity is enhanced by the functions of the data storage, the API, the configuration controller and the delivery controller.

[0066] This network entity provides the advantages of an enhanced UPF architecture that enables the UPF to host applications and cache content, and goes beyond traditional routing and tunnel processing functions. By providing a host that can cache content close to the end user, the latency between the UPF and the UE can be advantageously reduced. By using 3GPP standardization as the basis for the network entity, a standard method for handling application hosting of the UPF can be applied. This corresponds to a standard approach, without the need to create multiple solutions for each different use case. Therefore, technical complexity can be reduced.

[0067] In an exemplary implementation of the network entity, the second network entity is based on a session management function (SMF) entity standardized according to 3GPP, the SMF entity being enhanced to provide the information about the application data configuration of the data storage for storing the application data.

[0068] By using 3GPP standardization as the basis for the second network entity, a standard method for handling SMF entities can be applied. This corresponds to a standard approach, without the need to create multiple solutions for each different use case. Therefore, technical complexity can be reduced.

[0069] According to a second aspect, the present disclosure relates to a method for routing application data by a network entity in a mobile communication network, the method comprising: storing the application data locally in a data store of the network entity based on an application data configuration, the application data configuration indicating a configuration of the data store for storing the application data, the application data being associated with at least one service in the communication network; an application programmable interface (API) of the network entity receiving information related to the application data configuration from a second network entity via the communication network; a configuration controller of the network entity controlling the data store to store the application data based on the application data configuration; a delivery controller of the network entity controlling the delivery of the application data to at least one user equipment (UE) via the communication network, the control comprising: providing the application data stored in the data store to the at least one UE based on a request from the at least one UE for the application data associated with the at least one service; if the application data associated with the at least one service is not stored in the data store, retrieving the application data from an application server or another network entity and providing the application data retrieved from the application server to the at least one UE.

[0070] This approach introduces new capabilities for mobile communication networks, where mobile networks enable improved service delivery for user traffic. In addition, this approach enables integrated deep edge delivery within the 3GPP network to enable specific service enhancements such as caching, storage, etc. The functionality of network entities (e.g., UPF) is enhanced. In addition to routing and tunneling processing, new types of applications can be processed. Non-standard implementations of mobile edge computing can be implemented without causing incompatibility and performance degradation. This approach can reduce latency by bringing application logic execution closer to the end user (e.g., through caching, storage, etc.).

[0071] According to a third aspect, the present disclosure relates to a computer program product, comprising computer executable code or computer executable instructions, which, when executed, cause at least one computer to perform the method according to the second aspect.

[0072] The computer program product may be run on a controller or processor to control a mobile communication network (e.g. Figure 1 The above service in one of the components of the mobile communication network described in.

[0073] According to a fourth aspect, the present disclosure relates to a computer-readable medium having instructions stored therein, which, when executed by a computer, causes the computer to perform the method according to the second aspect above. Such a computer-readable medium may be a non-transitory readable storage medium. The instructions stored on the computer-readable medium may be executed by a controller or a processor to control a mobile communication network (e.g. Figure 1 The above service in one of the components of the mobile communication network described in. BRIEF DESCRIPTION OF THE DRAWINGS

[0074] Other embodiments of the present disclosure will be described in conjunction with the following drawings, in which:

[0075] Figure 1 A block diagram of a main architecture 100 of the present disclosure having a mobile communication network 200 is shown;

[0076] Figure 2 A schematic diagram of a mobile communication network 200 of the present disclosure having two network entities 120, 120a, in particular enhanced or evolved UPF entities, is shown;

[0077] Figure 3 3a and 3b show two exemplary message flow diagrams 300a and 300b related to the evolved UPF of the present disclosure;

[0078] Figure 4 A block diagram showing a main architecture 400 of an evolved mobile communication network 200 including an evolved UPF entity of a first embodiment, the first embodiment involving using an eUPF as a cache;

[0079] Figure 5 Shows Figure 4 An exemplary message flow diagram 500 showing the message flow of the first embodiment is shown;

[0080] Figure 6 A block diagram showing a main architecture 600 of an evolved mobile communication network 200 including an evolved UPF entity 120, 120a of a second embodiment relating to fast retrieval of buffered packets when a user is moving;

[0081] Figure 7 Shows Figure 6 An exemplary message flow diagram 700 of the message flow of the second embodiment is shown. DETAILED DESCRIPTION

[0082] In the following detailed description, reference is made to the accompanying drawings which form a part of this specification, in which specific aspects of the present disclosure may be practiced are shown by way of illustration. It should be understood that other aspects may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description should not be understood in a restrictive sense, and the scope of the present disclosure is defined by the appended claims.

[0083] It should be understood that comments related to the described methods may also be equally applicable to the corresponding devices or systems for performing the methods, and vice versa. For example, if specific method steps are described, the corresponding devices may include units for performing the described method steps, even if such units are not explicitly described or shown in the drawings. In addition, it should be understood that the features of the various exemplary aspects described herein may be combined with each other unless explicitly stated otherwise.

[0084] Figure 1 A block diagram of a main architecture 100 of the present disclosure with a mobile communication network 200 is shown.

[0085] The mobile communication network 200 may be based on the 3GPP standard, but is not limited thereto. Specifically, the mobile communication network 200 may include the following 5G network functions of the 5G reference point architecture, such as those specified in the 3GPP TS 38.300 and 3GPP TS 23.501 specifications: UPF 120, SMF 105, PCF 104, AMF 106, NEF 102, AF 103, UE 130, UE 130a, AN 112, PSA 110, PSA 111.

[0086] UPF stands for User Plane Function. The functions of the 5G NR UPF node or UPF entity include: Anchor point for intra-RAT / inter-RAT mobility (when applicable); External PDU session point for data network interconnection; Packet routing and forwarding; Packet inspection; User plane part of policy rule enforcement, such as gating, redirection, traffic steering; Lawful interception (UP collection); Traffic usage reporting; QoS processing in the user plane, such as UL / DL rate enforcement, reflective QoS marking in DL; Uplink traffic verification (SDF to QoS flow mapping); Transport level packet marking for uplink and downlink; Downlink packet buffering and downlink data notification triggering; Send and forward one or more "end markers" to the source NG-RAN node.

[0087] SMF stands for Session Management Function. The functions of the 5G NR SMF node or SMF entity include: session management; UE IP address allocation and management; UP function selection and control; configuration of traffic steering at UPF to route traffic to the appropriate destination; control part of policy enforcement and QoS; downlink data notification.

[0088] PCF stands for Policy Control Function. The functions of a 5G NR PCF node or PCF entity include: supporting a unified policy framework to manage network behavior; providing policy rules to control plane functions to enforce these policy rules; and accessing subscription information related to policy decisions in a unified data repository (UDR).

[0089] AMF stands for Access and Mobility Management Function. AMF is part of the 3GPP 5G architecture. The main tasks of AMF include: registration management, connection management, reachability management, mobility management, and various functions related to security, access management, and authorization.

[0090] Edge Cloud 114 Figure 1 denoted outside the mobile communication network 200. The central cloud 113 is also located outside the mobile communication network 200.

[0091] The mobile communication network 200 can be any mobile communication network or system or operator network. It is not limited to Figure 1 3GPP system 200 is shown.

[0092] The concepts presented in this disclosure relate to a scenario of a mobile network 200 with improved service delivery. To reduce latency and improve performance, the network entities of the mobile network 200, especially the UPF 120, can be enhanced with additional user plane functions that can be used to execute application logic. This includes caching, API calls, configuration control, and general application execution. Figure 1 A general scenario is described where the execution of application logic moves from the edge cloud 114 to the mobile network 200 , and in particular to the UPF 120 .

[0093] The solution proposed in this disclosure specifies an evolved UPF architecture for improving service delivery. The solution enhances and defines an evolved network entity, in particular an evolved UPF 120, which includes functions for executing specific application and user logic. This enhanced UPF, hereinafter referred to as eUPF 120, can be used for different types of applications depending on the usage scenario. Depending on the needs, the eUPF 120 can be used to run user applications and even cache content for users.

[0094] In the following, the term eUPF or the term UPF is used depending on the context. UPF refers to the basic functions of the standard UPF according to 3GPP, while eUPF refers to the enhanced functions of the UPF proposed in the present disclosure. The UPF 120 can be Figure 2 The following modules are enhanced as shown in more detail:

[0095] Cache / storage module 123 , local proxy module 122 , API open module 121 and configuration control module 124 .

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

[0097] The local proxy module 122 provides storage and retrieval configuration. It controls and operates the storage, getting commands on what to store and what to evict. The local proxy module 122 provides cache management, such as size, eviction, etc. It also provides object allow list management. The local proxy module 122 controls and activates or deactivates each session cache / proxy at different granularities, i.e., per application, per flow, per session, content type, etc. The local proxy module 122 provides cache replica management, such as cache synchronization between multiple eUPFs to achieve failover, multi-warehouse systems, or encoded content to ensure security.

[0098] The API open module 121 provides an API that supports the controllability of the smart UPF and also provides an API that supports the interaction between different smart UPFs.

[0099] The configuration control module 124 provides a configuration language to track settings and rules about the smart UPF (ie, eUPF). Such a configuration can be stored in YAML or similar format. It includes cache eviction rules, hostname storage, certificates, etc.

[0100] In addition to defining specific modules of UPF 120, it also defines interfaces and APIs that the enhanced UPF 120 can open to other network functions. The main purpose is for SMF 105 that can interact with UPF 120.

[0101] The eUPF 120 opens specific service methods or APIs to other NFs (eg, SMF 105) to achieve controllability of the enhanced UPF 120, as described below.

[0102] a) eUPF-SMF interface: SMF can use this interface to create specific application (such as cache) configuration, control agents, and call storage usage (can extend the N4 interface). This interface can be used to implement: 1) basic 5G UPF processes, such as PDU session processing, traffic shaping, traffic detection, etc.; 2) evolved 6G UPF processes, such as triggering content caching, triggering application instantiation, triggering general command execution or serverless functions.

[0103] b) eUPF-eUPF interface: The eUPF 120 may use this interface to interact with other UPFs and use trigger functions at other UPFs 120a, such as retrieving already cached content at another UPF.

[0104] Figure 2 A schematic diagram of a mobile communication network 200 with network entities 120, 120a, in particular enhanced or evolved UPF entities according to the present disclosure is shown.

[0105] Figure 2 It includes the main architecture proposed in this disclosure. It provides two evolved UPF units 120 and 120a, each of which contains modules: configuration 124, storage 123, agent 122 and API open 121, and also includes interfaces for interaction between SMF 105 and eUPF 120, and between eUPF 120 and eUPF 120a.

[0106] Network entity 120 (may correspond to the above Figure 1 The eUPF 120 described above may be used to route the application data 108 to the mobile communication network 200 (corresponding to the above description of Figure 1 At least one user equipment (UE) 130 in the described mobile communication network 200).

[0107] It should be understood that the enhanced functionality of the network entity described in the present disclosure is preferably represented by the eUPF; however, any other network entity of the mobile communication network 200 may be used to implement the enhanced functionality.

[0108] In the following, the functionality of the network entity 120 will be described in more detail.

[0109] The network entity 120 includes a data store 123 for storing the application data 108 locally in the network entity 120 based on the application data configuration 109. The application data configuration 109 indicates a configuration of the data store 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 store 123 may correspond to the above description regarding Figure 1 The cache / storage module 123 is described.

[0110] The network entity 120 includes an application programming interface API 121, which is used to receive information related to the application data configuration 109 from the second network entity 105 through the communication network 200. The API 121 may correspond to the above-mentioned Figure 1 The second network entity 105 may correspond to the API open module 121 described above. Figure 1 SMF 105 as described.

[0111] The network entity 120 includes a configuration controller 124, which is used 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 above Figure 1 Configuration control module 124 is described.

[0112] The network entity 120 includes a delivery controller 122 for controlling the delivery of application data 108 to at least one UE 130 via the communication network 200. The delivery controller 122 may correspond to the above description of Figure 1 The local proxy module 122 is described.

[0113] The delivery controller 122 is configured to provide the application data 108 stored in the data store 123 to the at least one UE 130 based on a request for the application data associated with the at least one service from the at least one UE 130. If the application data associated with the at least one service is not stored in the data store 123, the delivery controller 122 is configured to obtain the application data 108 stored in the data store 123 from the application server 409 (e.g., Figure 4 The edge application server 409 shown in the figure) or another network entity retrieves the application data 108 and provides the application data 108 retrieved from the application server 409 to at least one UE 130.

[0114] Application data 108 may include cacheable application data and non-cacheable application data. Data storage 123 may be used to store cacheable application data.

[0115] Network entities can deliver both cacheable content (i.e., cacheable application data) and non-cacheable content (i.e., dynamic content). For non-cacheable application data, data stores may not be used, but other entities such as delivery controllers (i.e., proxies), configuration controllers, and APIs may be used.

[0116] The data store 123 may be used to purge the application data 108 based on a purge mechanism upon request of the delivery controller 122 .

[0117] The delivery controller 122 may retrieve the application data configuration 109 from the information related to the application data configuration 109 received from the API 121 and store the application data configuration 109 in the network entity 120 .

[0118] Delivery controller 122 may be operable to store application data 108 in data store 123 based on commands indicating application data 108 to be stored. Delivery controller 122 may be operable to purge application data 108 from data store 123 based on commands indicating application data 108 to be purged.

[0119] The delivery controller 122 may be used to control at least one of the following: the size of the application data 108 stored in the data store 123; the granularity of the application data 108 stored in the data store 123; the activation and / or deactivation of the storage of the application data 108 for each session, each application, each flow, and each content type; the encoding of the application data 108 stored in the data store 123; the replication of the application data 108 stored in the data store 123; the synchronization of the application data 108 with the application data stored in the data store 123 of another network entity 120a, for routing the application data 108 in the mobile communication network 200.

[0120] The API 121 may be used to implement at least one of the following: control of the network entity 120 by the second network entity 105 ; interaction between the network entity 120 and another network entity 120 a for routing the application data 108 in the mobile communication network 200 .

[0121] The configuration controller 124 may be used to create the application data configuration 109 based on a configuration programming language.

[0122] The configuration controller 124 may be operable to create the application data configuration 109 based on at least one of: a mapping of deliverable services and / or content to an identity of at least one UE 130; and a certificate of the deliverable services and / or content.

[0123] The API 121 may be used to send 606 the application data 108 stored in the data store 123 to another network entity 120a to route the application data 108 in the mobile communication network 200 after requesting 605 for content retrieval from another network entity 120a, such as described below with respect to Figure 6 and 7 described.

[0124] The API 121 may be used to receive integrity information 607 from another network entity 120a and send application data 108 to another network entity 120a after the integrity information 607 is verified, such as described below with respect to Figure 6 and 7 described.

[0125] The delivery controller 122 may be configured to verify the integrity information 607 based on the initial integrity information received from the second network entity 105 after the packet data unit PDU session is established 601 .

[0126] The network entity 120 may be connected to at least one UE 130 via an access network 112. Another network entity 120a may be connected to at least one UE 130 via another access network 112, wherein the other network entity 120a may be located within a mobile range 603 of the at least one UE 130, such as described below with respect to Figure 6 and 7 described.

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

[0128] The second network entity 105 may be based on a session management function SMF entity standardized according to 3GPP, which is enhanced to provide information about an application data configuration 109 of a data store 123 for storing application data 108. It should be understood that the functionality of the second network entity 105 described in the present disclosure is not limited to SMF; it may also be based on a session management function SMF entity standardized according to 3GPP, which is enhanced to provide information about an application data configuration 109 of a data store 123 for storing application data 108. Figure 1 Any other network entity implementation of the shown mobile communication network 200.

[0129] Figure 1 and Figure 2 The proposed architecture also provides a method for routing application data 108 in the mobile communication network 200 by the network entity 120 .

[0130] This method includes the following steps:

[0131] - locally storing the application data 108 in a data store 123 of the network entity 120 based on an application data configuration 109 indicating a configuration of the data store 123 for storing application data 108 , the application data 108 being associated with at least one service in the communication network 200 .

[0132] The application programming interface API 121 of the network entity 120 receives information related to the application data configuration 109 from the second network entity 105 via the communication network 200 .

[0133] The configuration controller 124 of the network entity 120 controls the data storage 123 to store the application data 108 based on the application data configuration 109 .

[0134] The delivery controller 122 of the network entity 120 controls the delivery of the application data 108 to at least one user equipment UE 130 over the communication network 200 .

[0135] Such control by the delivery controller 122 includes: providing the application data 108 stored in the data store 123 to the at least one UE 130 based on a request from the at least one UE 130 for the application data associated with the at least one service; if the application data associated with the at least one service is not stored in the data store 123, providing the application data 108 stored in the data store 123 to the at least one UE 130; Figure 4 ) retrieves application data 108 and provides the application data 108 retrieved from the application server 409 to at least one UE 130.

[0136] Figure 3 3a and 3b show two exemplary message flow diagrams 300a and 300b related to the evolved UPF of the present disclosure.

[0137] Figure 3 a describes the association of UPF with service-specific capabilities such as caching.

[0138] The eUPF 120 sends an association establishment request message 309 to the SMF 105 to inform the SMF 105 about the UPF cache function.

[0139] After receiving this request message 309, the SMF 105 responds with an association establishment response message 310 including service specific information such as host name, origin, keys, etc.

[0140] Figure 3 b describes traffic steering with specific UPF capabilities such as caching.

[0141] The application function (AF) 103 sends an initialization message 301 to the SMF 105 to initialize the UPF with configuration such as cache.

[0142] After receiving the initialization message 301, consider the proximity, delay, load, etc., such as the above Figure 1 and Figure 2 As described, the SMF performs UPF selection 302.

[0143] Then, the SMF 105 sends a message 303 with service specific information like hostname, origin, keys etc. to the eUPF 120. The eUPF 120 acknowledges 304 this message 303. After receiving the acknowledgement 304 from the eUPF 120, the SMF 105 stores the DNS redirection configuration 305, e.g. hostname>UPF IP.

[0144] After receiving the message 306 requesting DNS resolution of the host name from the UE 130, the SMF 105 provides the UE 130 with a DNS response 307 with the UPF IP.

[0145] The traffic (between the UE 130 and the eUPF 120 ) may then be processed 308 by the UPF 120 .

[0146] Figure 4A block diagram of a main architecture 400 of an evolved mobile communication network 200 including an evolved UPF entity of a first embodiment is shown, the first embodiment involving using an eUPF as a cache.

[0147] The first embodiment involves using the eUPF 120 as a cache. This enables content caching to be very close to the end user, thereby reducing latency and improving performance. This embodiment can be summarized as follows:

[0148] The Evolved UPF 120 handles caching close to the end user.

[0149] The relevant novel functions of UPF 120 for this embodiment are: storage 123, agent 122, api 121.

[0150] The storage may correspond to the above Figure 2 The agent 122 may correspond to the data store 123 described above. Figure 2 The delivery controller 122 described above. The api 121 may correspond to an application programmable interface (API) 121, as described above with respect to Figure 2 described.

[0151] Static content can be detected using standard http headers.

[0152] The SMF / control entity controls cache deletion as needed.

[0153] If the cache is empty, UPF 120 retrieves the cache from central cloud 113 (see Figure 1 ) or another UPF 120a (see Figure 2 ) to get a copy of the file.

[0154] Figure 5 Shows Figure 4 An exemplary message flow diagram 500 of the message flow of the first embodiment is shown.

[0155] The process related to the first embodiment is as follows Figure 5 shown and described below.

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

[0157] Flowchart 500 begins with initial traffic setup and creation 501 of an end-to-end path from UE 130 and EAS 409 .

[0158] Another SMF 105a sends a message 502 to the eUPF 120 to create a cache configuration.

[0159] UE 130 sends a request 503 for cacheable content to eUPF 120. eUPF 120 forwards this request 503 as a request 504 for cacheable content to EAS 409. Edge application server (EAS) 409 sends a message 505 to eUPF 120 to receive cacheable content, and eUPF 120 stores 506 the content according to the configuration. eUPF 120 sends 507 the content to UE 130.

[0160] When the second UE 130a requests 508 the cacheable content from the eUPF 120, the eUPF 120 may send 509 the cacheable content from the cache, ie, fast delivery may be achieved.

[0161] Although this embodiment is described in terms of cacheable content and cache configuration, it should be understood that this embodiment is not limited to cacheable data. Figure 2 The described application data 108 and application data configuration 109 can also be implemented via this message diagram 500 .

[0162] Figure 6 A block diagram of a main architecture 600 of an evolved mobile communication network 200 including an evolved UPF entity 120, 120a of a second embodiment is shown, the second embodiment involving fast retrieval of buffered packets when a user is moving.

[0163] The second embodiment involves quickly retrieving buffered packets when the user moves. In the case of user movement, the UPF 120 (ie, eUPF) can be triggered to retrieve buffered packets from another UPF 120a (ie, eUPF). The process is as follows.

[0164] SMF 105 enables fast transfer of buffered packets from one UPF 120 to another UPF 120a.

[0165] (1) SMF establishes a 601 PDU session on the old eUPF 120 (oldeUPF 120).

[0166] (2) PDU session establishment 602.

[0167] (3) Moving 603 to the new AN triggers PDU session modification.

[0168] (4) The session establishment process 604 selects the new eUPF 120 (neweUPF 120a), and the SMF 105 includes the oldUPF 120 information in the session establishment process.

[0169] (5) The newUPF 120a triggers 605 an API call to the oldeUPF 120 through the N9 interface to retrieve the buffered packets.

[0170] (6) oldeUPF 120 sends 606 the buffered packet.

[0171] (7) The neweUPF 120a verifies 607 the data integrity information.

[0172] Figure 7 Shows Figure 6 An exemplary message flow diagram 700 of the message flow of the second embodiment is shown.

[0173] The process related to the second embodiment is as follows Figure 7 shown.

[0174] Messages are sent between the following entities: NRF 720, SMF 105, NEWeUPF 120a and OLDeUPF 120.

[0175] The NRF 720 maintains an updated repository of all 5G elements available in the operator's network and the services provided by each element in the 5G core, which are expected to be instantiated, extended, and terminated with no or minimal human intervention. In addition to being a repository of services, the NRF also supports a discovery mechanism that allows 5G elements to discover each other and obtain updated status of required elements.

[0176] Flowchart 500 begins with the SMF 105 triggering 701 to create a PDU session.

[0177] The SMF 105 then retrieves 702 the evolved UPF list from the NRF 720. The NRF 720 sends 703 this eUPF list to the SMF 105.

[0178] SMF 105 checks whether the existing eUPF for this UE is active. In this example, the answer is yes.

[0179] SMF 105 sends a message 601 to NEWeUPF 120a to establish a PDU session including the identity and integrity information of OLDeUPF 120. This message 601 may correspond to the above Figure 6 The described message 601. The NEWeUPF 120a responds 601a to the message 601.

[0180] Then, NEWeUPF 120a sends a message 605 to OLDeUPF 120 to call the remote eUPF API for content retrieval, buffering packets, etc. Message 605 includes integrity information. This message 605 may correspond to the above description of Figure 6 Message 605 is described.

[0181] OLDeUPF 120 verifies 607 the integrity information and sends a response 605a to NEWeUPF 120a, such as described above with respect to Figure 6 described.

[0182] The above article about Figure 3 , 5 The messages described in 7 may be implemented as computer executable codes or computer executable instructions or computer programs executed on a computer.

[0183] A computer program may be run on a controller or processor to control a mobile communication network (e.g. Figure 1 or Figure 2 The above service in one of the components of the mobile communication network described in.

[0184] The solution proposed in the present 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 a control plane.

[0185] Although specific features or aspects of the present disclosure may have been disclosed with respect to only one of several implementations, such features or aspects may be advantageously combined with one or more other features or aspects of other implementations as desired and for any given or specific application. In addition, to the extent that the terms "include," "have," "have," or other variations of these words are used in the specific embodiments or claims, such terms are similar to the term "comprise," and are both intended to represent the meaning of inclusion. Similarly, the terms "exemplary," "for example," and "such as" are only intended to be examples, not the best or optimal. The terms "coupled" and "connected," as well as derivatives, may have been used. It should be understood that these terms may be used to indicate that two elements cooperate or interact with each other, regardless of whether they are in direct physical or electrical contact, or whether they are not in direct contact with each other.

[0186] Although specific aspects have been illustrated and described herein, it will be appreciated by those skilled in the art that various alternative and / or equivalent implementations may be used to replace the specific aspects shown and described without departing from the scope of the present disclosure. This application is intended to cover any modifications or changes to the specific aspects discussed herein.

[0187] Although elements in the claims are listed in a specific order with corresponding labels, these elements are not necessarily limited to being implemented in this specific order unless the recitation of the claims otherwise implies a specific order for implementing some or all of these elements.

[0188] According to the above teachings, many substitutions, modifications and changes are obvious to those skilled in the art. Of course, it is easy for those skilled in the art to recognize that, in addition to the applications described herein, there are many other applications of the present disclosure. Although the present disclosure has been described with reference to one or more specific embodiments, it is recognized by those skilled in the art that many changes can be made to the present disclosure without departing from the scope of the present disclosure. Therefore, it should be understood that the present disclosure can be practiced in a manner different from that specifically described herein, as long as it is within the scope of the attached claims and their equivalents.

Claims

1. A network entity (120) for routing application data (108) to at least one user equipment UE (130) in a mobile communication network (200), the network entity (120) comprising: a data storage (123) for storing the application data (108) locally in the network entity (120) based on an application data configuration (109), the application data configuration (109) indicating 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); An application programming interface API (121) for receiving information related to the application data configuration (109) from a second network entity (105) via the communication network (200); a configuration controller (124) configured to control the data storage (123) to store the application data (108) based on the application data configuration (109); a delivery controller (122) for controlling the delivery of the application data (108) to the at least one UE (130) via the communication network (200); The delivery controller (122) is configured to provide the application data (108) stored in the data storage (123) to the at least one UE (130) based on a request from the at least one UE (130) for the application data associated with the at least one service; if the application data associated with the at least one service is not stored in the data storage (123), retrieve the application data (108) from an application server (409) or another network entity and provide the application data (108) retrieved from the application server (409) to the at least one UE (130).

2. The network entity (120) according to claim 1, wherein: The application data (108) includes cacheable application data and non-cacheable application data, and the data storage (123) is used to store the cacheable application data.

3. The network entity (120) according to claim 1 or 2, wherein: The data storage (123) is used to clear the application data (108) based on a clearing mechanism according to a request of the delivery controller (122).

4. The network entity (120) according to any of the preceding claims, wherein The delivery controller (122) is configured to store the application data (108) in the data storage (123) based on a command indicating that the application data (108) is to be stored; The delivery controller (122) is configured to clear the application data (108) from the data storage (123) based on a command indicating that the application data (108) is to be cleared.

5. The network entity (120) according to any of the preceding claims, wherein The delivery controller (122) is used to control at least one of the following: the size of the application data (108) stored in the data storage (123), the granularity of the application data (108) stored in the data store (123), activation and / or deactivation of said storage of application data (108) per session, per application, per flow, per content type, an encoding of said application data (108) stored in said data storage (123), a copy of said application data (108) stored in said data storage (123), Synchronisation of the application data (108) with application data stored in a data store (123) of another network entity (120a) for routing the application data (108) in the mobile communication network (200).

6. The network entity (120) according to any of the preceding claims, wherein The API (121) is used to implement at least one of the following: the second network entity (105) controlling the network entity (120), Interaction of the network entity (120) with another network entity (120a) for routing application data (108) in the mobile communication network (200).

7. The network entity (120) according to any of the preceding claims, wherein The configuration controller (124) is used to create the application data configuration (109) based on a configuration programming language.

8. The network entity (120) according to any of the preceding claims, wherein The configuration controller (124) is used to create the application data configuration (109) based on at least one of the following: a mapping of deliverable services and / or content to an identity of the at least one UE (130), The certificate for the deliverable services and / or content.

9. The network entity (120) according to any of the preceding claims, wherein The API (121) is used to send (606) the application data (108) stored in the data storage (123) to another network entity (120a) to route the application data (108) in the mobile communication network (200) after requesting (605) for content retrieval from the other network entity (120a).

10. The network entity (120) according to claim 9, wherein: The API (121) is used to receive integrity information (607) from the other network entity (120a), and send the application data (108) to the other network entity (120a) after the integrity information (607) is verified.

11. The network entity (120) according to claim 10, wherein: The delivery controller (122) is configured to verify the integrity information (607) based on initial integrity information received from the second network entity (105) after a packet data unit (PDU) session (601) is established.

12. The network entity (120) according to any one of claims 9 to 11, wherein: The network entity (120) is connected to the at least one UE (130) via an access network (112); The other network entity (120a) is connected to the at least one UE (130) via another access network (112), and the other network entity (120a) is located within a moving range (603) of the at least one UE (130).

13. The network entity (120) according to any of the preceding claims, wherein The network entity (120) is based on a user plane function (UPF) entity standardized according to 3GPP, and the UPF entity is enhanced by the functions of the data storage (123), the API (121), the configuration controller (124) and the delivery controller (122).

14. The network entity (120) according to any of the preceding claims, wherein The second network entity (105) is based on a Session Management Function (SMF) entity standardized according to 3GPP, the SMF entity being enhanced to provide the information about the application data configuration (109) of the data storage (123) for storing the application data (108).

15. A method for routing application data (108) in a mobile communication network (200) by a network entity (120), the method comprising: storing application data (108) locally in a data store (123) of the network entity (120) based on an application data configuration (109), the application data configuration (109) indicating a configuration of the data store (123) for storing the application data (108), the application data (108) being associated with at least one service in the communication network (200); An application programming interface API (121) of the network entity (120) receives information related to the application data configuration (109) from a second network entity (105) via the communication network (200); The configuration controller (124) of the network entity (120) controls the data storage (123) to store the application data (108) based on the application data configuration (109); The delivery controller (122) of the network entity (120) controls the delivery of the application data (108) to at least one user equipment UE (130) via the communication network (200), wherein the control comprises: Based on a request from the at least one UE (130) for application data associated with the at least one service, providing the at least one UE (130) with the application data (108) stored in the data store (123); if the application data associated with the at least one service is not stored in the data store (123), retrieving the application data (108) from an application server (409) or another network entity and providing the at least one UE (130) with the application data (108) retrieved from the application server (409).

Images