WO2024037719A1 - Entité de réseau pour acheminer des données d'application vers un équipement utilisateur - Google Patents

Entité de réseau pour acheminer des données d'application vers un équipement utilisateur Download PDF

Info

Publication number
WO2024037719A1
WO2024037719A1 PCT/EP2022/072983 EP2022072983W WO2024037719A1 WO 2024037719 A1 WO2024037719 A1 WO 2024037719A1 EP 2022072983 W EP2022072983 W EP 2022072983W WO 2024037719 A1 WO2024037719 A1 WO 2024037719A1
Authority
WO
WIPO (PCT)
Prior art keywords
application data
network entity
application
data
configuration
Prior art date
Application number
PCT/EP2022/072983
Other languages
English (en)
Inventor
Osama Abboud
Zoran Despotovic
Artur Hecker
Xun XIAO
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to PCT/EP2022/072983 priority Critical patent/WO2024037719A1/fr
Publication of WO2024037719A1 publication Critical patent/WO2024037719A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching

Definitions

  • 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).
  • UE User Equipment
  • the disclosure relates to an evolved User Plane Function (UPF) for application execution and caching in mobile networks.
  • UPF evolved User Plane Function
  • 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.
  • 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.
  • 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.
  • Current approach will create ossification of deep edge technologies since every operator/vendor might create its own ecosystem.
  • This disclosure provides a solution for an improved service delivery of user traffic in a mobile communication network.
  • a solution is provided for enhancing service-specific functionalities in a mobile communication network such as a 3GPP network.
  • the disclosure presents a general scenario in which the mobile network achieves an improved service delivery of user traffic.
  • an integrated deep edge delivery inside the 3GPP network is presented to enable specific service enhancing functionalities such as caching, storage, etc.
  • 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.
  • 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.
  • 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):
  • 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.
  • SMF session management function 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
  • a service-level agreement 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • an integrated deep edge delivery inside the 3GPP network can be realized to enable specific service enhancing functionalities such as caching, storage, etc.
  • functionality of the network entity e.g., a UPF
  • 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.
  • the application data comprises cacheable application data and non-cacheable application data, wherein the data storage is 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).
  • 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 is configured to clear the application data based on a clearance mechanism upon request of the delivery controller.
  • 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.
  • 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.
  • 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.
  • 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.
  • a network entity e.g., a UPF
  • another network entity e.g., another UPF
  • the configuration controller is configured to create the application data configuration based on a configuration programming language.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • SMF session management function
  • 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.
  • 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
  • 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.
  • 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
  • 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.).
  • 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.
  • 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.
  • 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.
  • 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;
  • Figure 7 shows an exemplary message flow chart 700 illustrating message flow for the second embodiment shown in Figure 6.
  • 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.
  • 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 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 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).
  • UDR Unified Data Repository
  • 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 .
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 .
  • UE 130 User Equipment
  • 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.
  • 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).
  • cacheable content i.e. , cacheable application data
  • non-cacheable content i.e., dynamic content
  • 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.
  • 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.
  • UPF user plane function
  • 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:
  • 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.
  • 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.
  • the SMF 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.
  • 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.
  • the SMF 105 stores DNS redirection configuration 305 such as hostname > UPF IP.
  • the SMF 105 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.
  • 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.
  • 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.
  • 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.
  • eUPF 120 can send 509 cacheable content from cache, i.e. , a fast delivery can be achieved.
  • FIG. 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.
  • the UPF 120 i.e. , eUPF
  • the 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.
  • session establishment procedures 604 select neweUPF 120a, SMF 105 includes oldUPF 120 information in session establishment procedures.
  • newUPF 120a triggers 605 API call with oldeUPF 120 over N9 interface to retrieve buffered packets.
  • 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.
  • NRF 720 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.
  • 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.
  • 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 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.
  • a WIFI node can be used to cache content and interact with the control plane.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente divulgation concerne une entité de réseau (120) permettant d'acheminer des données d'application (108) vers un équipement utilisateur (UE) (130) dans un réseau de communication mobile (200). L'entité de réseau comprend une mémoire de données (123) permettant de stocker localement les données d'application qui sont associées à au moins un service dans le réseau de communication. L'entité de réseau comprend une API (121) permettant de recevoir, d'une seconde entité de réseau (105), des informations concernant une configuration de données d'application (109). L'entité de réseau comprend : un contrôleur de configuration (124) configuré pour amener la mémoire de données à stocker les données d'application d'après la configuration de données d'application ; et un contrôleur de distribution (122) permettant de commander la distribution des données d'application à l'UE. Le contrôleur de distribution est configuré pour fournir à l'UE les données d'application stockées dans la mémoire de données ; et si les données d'application ne sont pas stockées dans la mémoire de données, pour récupérer les données d'application à partir d'un serveur d'application (409) ou d'une autre entité de réseau.
PCT/EP2022/072983 2022-08-17 2022-08-17 Entité de réseau pour acheminer des données d'application vers un équipement utilisateur WO2024037719A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/072983 WO2024037719A1 (fr) 2022-08-17 2022-08-17 Entité de réseau pour acheminer des données d'application vers un équipement utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/072983 WO2024037719A1 (fr) 2022-08-17 2022-08-17 Entité de réseau pour acheminer des données d'application vers un équipement utilisateur

Publications (1)

Publication Number Publication Date
WO2024037719A1 true WO2024037719A1 (fr) 2024-02-22

Family

ID=83271524

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/072983 WO2024037719A1 (fr) 2022-08-17 2022-08-17 Entité de réseau pour acheminer des données d'application vers un équipement utilisateur

Country Status (1)

Country Link
WO (1) WO2024037719A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113259498A (zh) * 2020-02-11 2021-08-13 大唐移动通信设备有限公司 一种本地业务分流方法、装置、电子设备及存储介质
KR20220121045A (ko) * 2021-02-24 2022-08-31 주식회사 케이티 에지 컴퓨팅 시스템 그리고 이의 네트워크 접근 제어 방법

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113259498A (zh) * 2020-02-11 2021-08-13 大唐移动通信设备有限公司 一种本地业务分流方法、装置、电子设备及存储介质
KR20220121045A (ko) * 2021-02-24 2022-08-31 주식회사 케이티 에지 컴퓨팅 시스템 그리고 이의 네트워크 접근 제어 방법

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.501
3GPP TS 38.300
ARTUÑEDO GUILLEN DAVID ET AL: "Edge computing for 5G networks - white paper", 29 January 2021 (2021-01-29), XP093003475, Retrieved from the Internet <URL:https://bscw.5g-ppp.eu/pub/bscw.cgi/d397473/EdgeComputingFor5GNetworks.pdf> [retrieved on 20221130], DOI: 10.5281/zenodo.3698117 *
PAPER WHITE ET AL: "Edge Computing: from standard to actual infrastructure deployment and software development Authors", 1 October 2019 (2019-10-01), XP055883211, Retrieved from the Internet <URL:https://www.martechcube.com/resources/intel_q1_nt/where_is_the_edge/edge-computing-from-standard-to-actual-infrastructure-deployment-and-software-development.pdf> [retrieved on 20220125] *

Similar Documents

Publication Publication Date Title
US11825335B2 (en) Always-on packet data unit session indication
US11134410B2 (en) Quality of service (QoS) control in mobile edge computing (MEC)
CN110049070B (zh) 事件通知方法及相关设备
KR102469191B1 (ko) 정보 전송방법 및 장치, 컴퓨터 판독가능 저장 매체
WO2018161803A1 (fr) Procédé et dispositif pour sélectionner des tranches de réseau
CN114868435A (zh) 针对多址接入的策略控制
CN111935738B (zh) 一种用于多运营商核心网对接mec的方法及系统
EP2883384B1 (fr) Réduction de trafic de signalisation dans des systèmes de communications mobiles
KR20230152838A (ko) 이벤트 통지 방법, 장치 및 저장매체
EP3954098B1 (fr) Optimisation des services appliqués à des sessions de paquets de données
EP3656089B1 (fr) Procédés, systèmes et supports lisibles par ordinateur pour faire fonctionner un réseau de télécommunications à l&#39;aide d&#39;un système informatique sur site et d&#39;un système informatique en nuage hors site
CN111406437B (zh) 多路径数据通信
EP3777464B1 (fr) Procédés, dispositifs, système et programme informatique permettant d&#39;accéder à un service à l&#39;extérieur d&#39;un réseau de communication mobile dans une connexion par trajets multiples
WO2024037719A1 (fr) Entité de réseau pour acheminer des données d&#39;application vers un équipement utilisateur
Amadeo et al. Empowering 5G network softwarization through information centric networking
US9674844B2 (en) Device and method for distributing WLAN user policy
US20220386087A1 (en) Communications Network Architecture
CN114143185A (zh) 一种网络通信的方法及装置、电子设备、存储介质
Takatama et al. Intelligent SIP system for mobile Internet
WO2024034446A1 (fr) Dispositif de réseau central, serveur d&#39;application et procédé de communication
US20230327997A1 (en) Methods and Apparatuses for Providing Quality of Service Handling of User Traffic Transmitted by a Content Provider
US20240187374A1 (en) Method and apparatus for improving a server discovery handling procedure
WO2022217376A1 (fr) Procédé et appareil permettant d&#39;améliorer une procédure de gestion de découverte de serveur

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22768286

Country of ref document: EP

Kind code of ref document: A1