Relationship between 3GPP (3rd Generation Partnership Project) UPF (User Plane Function) and Edge Computing Application Server

Abstract

The technology discussed herein can be combined with a 5GC (fifth generation core network) system architecture to facilitate EC (edge ​​computing). Various embodiments can facilitate one or more of the following: (1) providing the location of one or more UPFs (user plane functions) associated with at least one AS (application server) to a non-3GPP (third generation partnership project) EC management system; (2) providing the location of at least one AS associated with one or more UPFs to a 3GPP management system; and / or (3) establishing a relationship between one or more UPFs and at least one AS.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 713,980, filed on August 2, 2018, entitled “ASSOCIATION OF USER PLANE FUNCTION (UPF) AND EDGE COMPUTING APPLICATION SERVER,” the contents of which are incorporated herein by reference in their entirety. Background Art

[0003] The fifth generation (5G) network is designed to support a variety of new services such as the Internet of Things (IoT), cloud-based services, industrial control, autonomous driving, mission-critical communications, etc. based on network slicing technology. For example, some services (e.g., autonomous driving) may have ultra-low latency and high data capacity targets for safety and performance reasons. The 5G Core Network (5GC) system architecture as defined in 3GPP (3rd Generation Partnership Project) TS (Technical Specification) 23.501 supports edge computing to enable such services through applications hosted at attachment access points closer to user equipment (UE) in order to reduce end-to-end latency and the load on the transport network. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Figure 1 is a block diagram illustrating a system that may be employed at a 3GPP (3rd Generation Partnership Project) management system or a non-3GPP EC management system in accordance with various aspects discussed herein, the system facilitating the relationship between a UPF (User Plane Function) and an edge computing AS (Application Server) and the sharing of associated location information.

[0005] Figure 2 is a diagram showing in combination various aspects how a UE (User Equipment) connects to a non-3GPP AS hosting an application via the 3GPP network functions of a gNB (Next Generation Node B) and UPF.

[0006] Figure 3 is a diagram illustrating a 5G edge computing network architecture according to various embodiments, showing how 3GPP network elements work with non-3GPP network elements (such as AF and AS) to provide the services discussed herein.

[0007] Figure 4 is a diagram illustrating an exemplary management architecture according to various embodiments, in which a 3GPP management system and a non-3GPP EC management system can work together to support edge computing.

[0008] Figure 5 is a flow chart illustrating an exemplary method that may be employed by a 3GPP management system and a non-3GPP EC management system in various aspects to facilitate providing UPF location information associated with an AS.

[0009] Figure 6 is a flow chart illustrating an exemplary method that may be employed by a 3GPP management system and a non-3GPP EC management system in various aspects to facilitate providing AS location information associated with a UPF.

[0010] Figure 7 is a diagram illustrating a relationship of a UPF to an AS for a scenario in which one or more UPFs may be connected to an AS according to various embodiments.

[0011] Figure 8 is a flow chart illustrating an example method that may be employed by a 3GPP management system and a non-3GPP EC management system to facilitate configuration of a relationship between one or more UPFs and one or more ASs in accordance with various aspects. DETAILED DESCRIPTION

[0012] The embodiments described herein may be implemented into a system using any suitably configured hardware and / or software. Figure 1, a block diagram of a system 100 that can be employed by a 3GPP (3rd Generation Partnership Project) management system (e.g., system 1001) or a non-3GPP EC (edge ​​computing) management system (e.g., system 1002) according to various aspects described herein, which facilitates establishing a relationship between a UPF (user plane function) and an edge computing AS (application server) and sharing of associated location information. The system 100 may include one or more processors 110 (e.g., each processor may include processing circuits and one or more interfaces for sending / receiving data to / from each other or other circuits, such as a memory interface for sending / receiving data to / from a memory 130, a communication circuit interface for sending / receiving data to / from a communication circuit 120, etc.), a communication circuit 120 (which may facilitate transmitting data via one or more reference points, networks, etc., and may include communication resources, etc.), and a memory 130 (which may include any of a variety of storage media and may store instructions and / or data associated with at least one of the one or more processors 110 or the communication circuit 120, and may include a cache memory of the processor 110 and / or one or more memory / storage devices, etc.). In some aspects, one or more processors 110, communication circuitry 120, and memory 130 may be included in a single device, while in other aspects, they may be included in different devices, such as part of a distributed architecture. As described in more detail below, in various embodiments, a 3GPP management system or a non-3GPP EC management system may employ system 200 to facilitate edge computing based on connecting UPFs and ASs and sharing their location information.

[0013] See also Figure 2 , shows an exemplary diagram 200 that illustrates how a UE (user equipment) 210 connects to a non-3GPP AS (application server) 240 where an application is hosted (e.g., at a local data network 250) via 3GPP network functions of a gNB (next generation Node B) 220 and a UPF (user plane function) (uplink classifier 2301 and PDU (protocol data unit) session anchor 2302 in example 200), in conjunction with various aspects discussed herein. The end-to-end latency between the UE and the AS can be reduced by bringing the UPF and the AS geographically close to each other.

[0014] Therefore, various embodiments may solve one or more of the following problems: (1) providing the UPF location (if deployed) to the edge computing (EC) management system so that the EC management system can deploy the AS at the location that can meet the end-to-end delay target (or QoS (quality of service) requirements, etc.); (2) providing the AS location (if deployed) to the 3GPP management system so that the GPP management system can deploy the UPF at the location that can meet the end-to-end delay target; and (3) providing a relationship between the UPF and the AS, where one or more UPFs can be connected to the AS (for example, when the UE moves, for example from a first UPF (UPF#1) to a second UPF (UPF#2), the relationship between the UPF and the AS can indicate which AS UPF#2 is connected to. If the AS is not the AS to which the UE was previously connected, it can redirect the UE traffic to the new AS).

[0015] Various implementations may employ a 5G edge computing network architecture to facilitate non-3GPP edge computing functions (such as AF (application function), AS, etc.) that interact with 3GPP network functions. The exemplary use cases and capabilities discussed below involve the following three scenarios: (1) UPF location retrieval; (2) AS location retrieval; and (3) UPF-AS relationship.

[0016] Edge computing concepts / technology

[0017] As mentioned above, 5G networks are designed to support a variety of new services such as IoT (Internet of Things), cloud-based services, industrial control, autonomous driving, mission-critical communications, and more based on network slicing technology. For example, some services (e.g., autonomous driving) may have ultra-low latency and high data capacity targets for safety and performance reasons. The 5GC system architecture supports edge computing to enable such services through applications hosted at attachment access points closer to the UE in order to reduce end-to-end latency and the load on the transport network.

[0018] See also Figure 3 , a diagram of a 5G edge computing network architecture 300 according to various embodiments discussed herein, showing how 3GPP network elements work with non-3GPP network elements such as AF (application function) and AS (application server) to provide EC services. Elements 210 to 250 are similar to those described above in conjunction with Figure 2Those discussed. AF 330 may send a request to SMF (Session Management Function) 310 via PCF (Policy Control Function) 320 or NEF (Network Exposure Function) (not shown) to influence UPF (User Plane Function) selection / reselection and / or traffic routing. SMF 310 may insert an uplink classifier in UPF (e.g., 2301, 2302, etc.) to transfer some user plane traffic from UE 210 to local AS 240 in order to meet the ultra-low latency target imposed by the service.

[0019] The end-to-end delay of traffic traveling from the UE to the AS includes delays both inside and outside the 3GPP network. The delay inside the 3GPP network is related to the QoS (quality of service) goals / objectives / requirements in the 5G network, while the delay outside the 3GPP network is related to the geographic location of the UPF and the AS. Therefore, various implementations may facilitate the deployment of the AS and UPF in a way that meets the end-to-end delay target for the service.

[0020] The deployment of edge computing in 3GPP networks may involve collaboration with other SDOs (Standard Definition Organizations) because AF and AS are not 3GPP defined nodes. Therefore, to support edge computing deployment, the 3GPP management system may communicate with a non-3GPP edge computing (EC) management system, for example, as described in ETSI (European Telecommunications Standards Institute) GS (Group Specification) MEC (Multi-Access Edge Computing) 003 or another non-3GPP EC management system.

[0021] See also Figure 4 , a diagram illustrating an exemplary management architecture 400 according to various embodiments is shown, in which a 3GPP management system (e.g., employing a first device 1001) and a non-3GPP EC management system (e.g., employing a second device 1002) can work together to support edge computing.

[0022] The following are examples of use cases and conditions or characteristics of various implementations and associated architectures.

[0023] Example use cases :

[0024] UPF location retrieval

[0025] question : The operator decides to deploy one or more ASs to support the UPFs already deployed in the 3GPP network. Information about the location of the UPF can help the operator determine where the AS should be deployed in order to meet the end-to-end objectives of the service.

[0026] Prerequisites : Deploy the UPF to connect to the AS.

[0027] describe : See Figure 5 , a flow chart of an exemplary method 500 that can be employed by a 3GPP management system (e.g., using apparatus 1001) and a non-3GPP EC management system (e.g., using apparatus 1002) according to various aspects is shown, which facilitates providing UPF location information associated with an AS. The exemplary method 500 illustrates a method that can be employed by a 3GPP management system to perform Figure 5 and discussed below, and may be employed at a non-3GPP EC management system to perform Figure 5 In other aspects, a machine-readable medium may store instructions associated with either or both of these methods, which when executed may cause a 3GPP management system and / or a non-3GPP EC management system to perform the actions of its associated method.

[0028] At 510, the non-3GPP EC management system may request the 3GPP management system to provide the location of the UPF intended to connect to the AS (e.g., where a signal from the non-3GPP EC management system to the 3GPP management system may be generated via processor 1102, sent by communication circuit 1202 over a relevant interface or reference point, received by communication circuit 1201, and processed by processor 1101). In various aspects, the request may indicate the location of the AS and / or a data center / local data network hosting the AS.

[0029] At 520, the 3GPP management system may respond to the non-3GPP EC management system with a list of UPF locations (e.g., where a signal from the 3GPP management system to the non-3GPP EC management system may be generated via processor 1101, sent by communication circuit 1201 via a relevant interface or reference point, received by communication circuit 1202, and processed by processor 1102).

[0030] At 530, the non-3GPP EC management system may confirm that the UPF location information has been received.

[0031] Postcondition : At 540, non-3GPP EC management may deploy the AS in a location that meets the end-to-end objectives of the service.

[0032] AS location retrieval

[0033] question : The operator decides to add a new UPF to the 5GC or change the existing UPF to connect to one or more ASs already deployed in the non-3GPP network. Information about the AS location can help the operator determine where the UPF should be deployed in order to meet the end-to-end objectives of the service.

[0034] Prerequisites : Deploy the AS to which the new UPF is connected.

[0035] describe : See Figure 6 , in various aspects, a flow chart of an exemplary method that may be employed by a 3GPP management system and a non-3GPP EC management system to facilitate providing AS location information associated with one or more UPFs. Exemplary method 600 illustrates an exemplary method that may be employed by a 3GPP management system to perform Figure 6 and discussed below, and may be employed at a non-3GPP EC management system to perform Figure 6 In other aspects, a machine-readable medium may store instructions associated with either or both of these methods, which when executed may cause a 3GPP management system and / or a non-3GPP EC management system to perform the actions of its associated method.

[0036] At 610, the 3GPP management system may request the non-3GPP EC management system to provide the location of the AS to which the UPF is to connect. In various aspects, the request may indicate the location of the UPF and / or a data center hosting the UPF.

[0037] At 620, the non-3GPP EC management system may respond to the 3GPP management system with the location of the AS.

[0038] At 630, the 3GPP management system may confirm that the AS location information has been received.

[0039] Postcondition : At 640, the 3GPP management system may select an AS that is closer to the UPF, and at 650, the 3GPP management system may deploy the UPF at a location where the traffic delay from the AS to the UE meets the end-to-end delay target.

[0040] Relationship between UPF and AS

[0041] question : See Figure 7 , shows an exemplary graph 700, which in an embodiment shows a method for one or more UPF 230 i-j Connectable to an associated local data network 250 i AS 240 i When UE 210 moves from the first gNB 2201 to the AS via UPF 230 i-jWhen connecting to a second gNB 2202 or a third gNB 2203 of the same or different AS 2401 (hosted at the first local data network 2501) or AS 2402 (hosted at the second local data network 2502). If the target gNB 2202 or 2203 is connected to an AS 2402 different from the AS 2401 to which the source gNB 2201 is connected, traffic from the UE 210 may be redirected to the new AS 2402. Therefore, both 3GPP management and non-3GPP EC management systems may facilitate the management of the relationship between the UPF and the AS.

[0042] Prerequisites : UPF and AS have been deployed.

[0043] describe : See Figure 8 , in various aspects, a flow chart of an exemplary method that may be employed by a 3GPP management system and a non-3GPP EC management system to facilitate configuration of a relationship between one or more UPFs and one or more ASs. Exemplary method 800 illustrates an exemplary method that may be employed by a 3GPP management system to perform Figure 8 and discussed below, and may be employed at a non-3GPP EC management system to perform Figure 8 In other aspects, a machine-readable medium may store instructions associated with either or both of these methods, which when executed may cause a 3GPP management system and / or a non-3GPP EC management system to perform the actions of its associated method.

[0044] The 3GPP management system may request one or more UPFs to establish connections with one or more ASs at 810. Connection establishment between the UPFs and the ASs may be facilitated via communication with the non-3GPP EC management system.

[0045] At 620, the 3GPP management system may configure the relationship between the UPF and the AS after the connection has been established.

[0046] Postcondition : The relationship between UPF and AS is available.

[0047] Potential conditions

[0048] The following are potential conditions or characteristics of a system employing the embodiments discussed herein, which may facilitate the various embodiments discussed herein.

[0049] REQ-ECM_CON-1 : The 3GPP Management System shall have the capability to allow a non-3GPP EC Management System to retrieve the UPF location.

[0050] REQ-ECM_CON-2 : The 3GPP management system should have the ability to request the non-3GPP EC management system to provide the AS location.

[0051] REQ-ECM_CON-3 : The 3GPP management system should have the ability to request the establishment of a connection between the UPF and the AS.

[0052] REQ-ECM_CON-4 : The 3GPP management system should have the ability to configure the relationship between UPF and AS.

[0053] Additional Implementation

[0054] The examples herein may include subject matter, such as a method, components for performing actions or blocks of the method, and at least one machine-readable medium including executable instructions that, when executed by a machine (e.g., a processor with memory, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), cause the machine to perform actions of a method or apparatus or system for concurrent communication using multiple communication technologies according to the described embodiments and examples.

[0055] Embodiment 1 is a device configured to be adopted in a 3GPP (Third Generation Partnership Project) management system, comprising: one or more processors, wherein the one or more processors are configured to: receive a first request from an EC (edge ​​computing) management system for providing information associated with one or more UPFs (user plane functions) to which EC resources in a local data network are to be connected; and provide the information associated with the one or more UPFs to the EC management system.

[0056] Embodiment 2 includes the subject matter of any variation of any one of Embodiment 1, wherein the information associated with the one or more UPFs includes location information of the one or more UPFs.

[0057] Embodiment 3 includes the subject matter of any variation of any one of Embodiments 1-2, wherein the one or more processors are further configured to receive a first confirmation from the EC management system that the information associated with the one or more UPFs has been received.

[0058] Embodiment 4 includes the subject matter of any variation of any one of Embodiments 1 to 3, wherein the EC resource includes at least one AS (Application Server).

[0059] Embodiment 5 includes the subject matter of any variation of any one of Embodiment 4, wherein the one or more processors are further configured to: send a second request to the EC management system to provide information associated with the at least one AS; and receive the information associated with the at least one AS from the EC management system.

[0060] Embodiment 6 includes the subject matter of any variation of any one of Embodiment 5, wherein the information associated with the at least one AS includes location information of the at least one AS.

[0061] Embodiment 7 includes the subject matter of any variation of any one of Embodiments 5 to 6, wherein the one or more processors are further configured to send a second confirmation to the EC management system that the information associated with the at least one AS has been received.

[0062] Embodiment 8 includes the subject matter of any variation of any one of Embodiments 5 to 7, wherein the one or more processors are further configured to select a first AS of the at least one AS based on a delay target.

[0063] Embodiment 9 includes the subject matter of any variation of any of Embodiment 8, wherein the one or more processors are further configured to deploy the one or more UPFs at a location sufficiently close to the first AS to meet the latency target.

[0064] Embodiment 10 includes the subject matter of any variation of any one of Embodiments 1 to 9, wherein the EC management system is a non-3GPP EC management system.

[0065] Embodiment 11 is a device configured to be employed in an EC (edge ​​computing) management system, comprising: one or more processors, wherein the one or more processors are configured to: send a request to a 3GPP management system for providing information associated with one or more UPFs (user plane functions) to which EC resources in a local data network are to be connected; and receive the information associated with the one or more UPFs from the 3GPP management system.

[0066] Embodiment 12 includes the subject matter of any variation of any of Embodiment 11, wherein the information associated with the one or more UPFs includes location information of the one or more UPFs.

[0067] Embodiment 13 includes the subject matter of any variation of any one of Embodiment 12, wherein the one or more processors are further configured to deploy at least one AS (application server) based on the location information and latency target of the one or more UPFs.

[0068] Embodiment 14 includes the subject matter of any variation of any one of Embodiments 11 to 13, wherein the one or more processors are further configured to send a first acknowledgement to the 3GPP management system that the information associated with the one or more UPFs has been received.

[0069] Embodiment 15 includes the subject matter of any variation of any one of Embodiments 11 to 14, wherein the EC resource includes at least one AS (Application Server).

[0070] Embodiment 16 includes the subject matter of any variation of any one of Embodiment 15, wherein the one or more processors are further configured to: receive a second request for providing information associated with the at least one AS from the 3GPP management system; and send the information associated with the at least one AS to the 3GPP management system.

[0071] Embodiment 17 includes the subject matter of any variation of any one of Embodiment 16, wherein the information associated with the at least one AS includes location information of the at least one AS.

[0072] Embodiment 18 includes the subject matter of any variation of any one of Embodiments 16 to 17, wherein the one or more processors are further configured to receive a second confirmation from the 3GPP management system that the information associated with the at least one AS has been received.

[0073] Embodiment 19 includes the subject matter of any variation of any one of Embodiments 11 to 18, wherein the EC management system is a non-3GPP EC management system.

[0074] Embodiment 20 is a device configured to be adopted in a 3GPP (Third Generation Partnership Project) management system, comprising: one or more processors, wherein the one or more processors are configured to: send a request to an EC (edge ​​computing) management system to establish a connection between one or more UPFs (user plane functions) and at least one AS (application server).

[0075] Embodiment 21 includes the subject matter of any variation of any of Embodiment 20, wherein the EC management system is a non-3GPPEC management system.

[0076] Embodiment 22 includes the subject matter of any variation of any one of Embodiments 20 to 21, wherein the one or more processors are further configured to configure a relationship between the one or more UPFs and the at least one AS after the connection has been established.

[0077] Embodiment 23 includes the subject matter of any variation of any one of Embodiments 20 to 22, wherein the at least one AS is a single AS.

[0078] Embodiment 24 includes the subject matter of any variation of any of Embodiments 20 to 23, wherein the one or more processors are further configured to redirect traffic from a first AS in the at least one AS to a different second AS in the at least one AS in response to a UE (user equipment) associated with the one or more UPFs moving from a first gNB (next generation Node B) to a different second gNB.

[0079] Embodiment 25 includes the subject matter of any variation of any one of Embodiments 1 to 24, wherein the one or more UPFs include one or more of an uplink classifier or a PDU (Protocol Data Unit) session anchor.

[0080] Embodiment 26 includes an apparatus comprising means for performing any of the described operations of embodiments 1-25.

[0081] Embodiment 27 includes a machine-readable medium storing instructions for execution by a processor to perform any of the described operations of Embodiments 1 to 25.

[0082] Embodiment 28 includes an apparatus comprising: a memory interface; and a processing circuit configured to: perform any one of the described operations of embodiments 1 to 25.

[0083] The above description of the exemplary embodiments of the disclosed subject matter, including the contents described in the abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. Although specific embodiments and examples are described herein for illustrative purposes, various modifications can be considered within the scope of such embodiments and examples as can be appreciated by those skilled in the relevant art.

[0084] In particular, with respect to the various functions performed by the above-described components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise specified, the terms used to describe such components (including references to "members") are intended to correspond to any component or structure that performs the specified functions of the components (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structures that perform the functions in the exemplary implementations shown herein. In addition, while particular features have been disclosed with respect to only one of a plurality of implementations, for any given or particular application, such features may be combined with one or more other features of other implementations, which may be desirable and advantageous.

Claims

1. An apparatus configured to be employed in a 3rd Generation Partnership Project 3GPP management system, the apparatus comprising: One or more processors configured to: receiving, from an edge computing EC management system, a first request to provide information associated with one or more user plane functions (UPFs) to which EC resources in a local data network are to connect; and Information associated with the one or more UPFs is provided to the EC management system, wherein the information associated with the one or more UPFs includes location information of the one or more UPFs, wherein one or more application servers AS are deployed based on the location information and latency targets of the one or more UPFs.

2. The apparatus of claim 1, wherein the one or more processors are further configured to receive a first confirmation from the EC management system that the information associated with the one or more UPFs has been received. 3 . The apparatus according to claim 1 , wherein the EC resource comprises at least one application server (AS). 4 .

4. The apparatus of claim 3, wherein the one or more processors are further configured to: sending a second request to the EC management system to provide information associated with the at least one AS; and Information associated with the at least one AS is received from the EC management system. The apparatus of claim 4 , wherein the information associated with the at least one AS comprises location information of the at least one AS. 6 . The apparatus of claim 4 , wherein the one or more processors are further configured to send a second acknowledgement to the EC management system that the information associated with the at least one AS has been received. 7 . The apparatus of claim 4 , wherein the one or more processors are further configured to select a first AS of the at least one AS based on a delay target.

8. The apparatus of claim 7, wherein the one or more processors are further configured to deploy the one or more UPFs at a location sufficiently close to the first AS to meet the latency target.

9. The apparatus according to any one of claims 1 to 2, wherein the EC management system is a non-3GPP EC management system.

10. A device configured to be employed in an edge computing EC management system, the device comprising: One or more processors configured to: sending a request to a 3GPP management system for providing information associated with one or more user plane functions (UPFs) to which EC resources in a local data network are to be connected; receiving information associated with the one or more UPFs from the 3GPP management system, wherein the information associated with the one or more UPFs includes location information of the one or more UPFs; as well as One or more application servers AS are deployed based on the location information and latency targets of the one or more UPFs.

11. The apparatus of claim 10, wherein the one or more processors are further configured to send a first acknowledgement to the 3GPP management system that the information associated with the one or more UPFs has been received.

12. The apparatus according to claim 10, wherein the EC resource comprises at least one application server (AS).

13. The apparatus of claim 12, wherein the one or more processors are further configured to: receiving, from the 3GPP management system, a second request to provide information associated with the at least one AS; and Information associated with the at least one AS is sent to the 3GPP management system.

14. The apparatus of claim 13, wherein the information associated with the at least one AS comprises location information of the at least one AS.

15. The apparatus of claim 13, wherein the one or more processors are further configured to receive a second acknowledgment from the 3GPP management system that the information associated with the at least one AS has been received.

16. The apparatus of claim 10, wherein the EC management system is a non-3GPP EC management system.

17. An apparatus configured to be employed in a 3rd Generation Partnership Project (3GPP) management system, the apparatus comprising: One or more processors configured to: Sending a request to the edge computing EC management system for establishing a connection between one or more user plane functions UPF and at least one application server AS; as well as In response to a user equipment UE associated with the one or more UPFs moving from a first next-generation node B gNB to a different second gNB, traffic is redirected from a first AS in the at least one AS to a different second AS in the at least one AS.

18. The apparatus of claim 17, wherein the EC management system is a non-3GPP EC management system.

19. The apparatus of claim 17 or 18, wherein the one or more processors are further configured to configure a relationship between the one or more UPFs and the at least one AS after the connection has been established.

20. The apparatus according to claim 17 or 18, wherein the at least one AS is a single AS.

21. The apparatus of claim 17 or 18, wherein the one or more UPFs include one or more of an uplink classifier or a protocol data unit (PDU) session anchor.

Images