Device and method for implementing user plane function

By implementing a bare-metal UPF using a SoC composed of FPGA and processor, the problems of high migration costs and long delivery times of EC platforms are solved, enabling low-cost, rapid deployment and migration-free UPF, thus simplifying the deployment of EC platforms in enterprise IT environments.

CN115244955BActive Publication Date: 2024-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080098312.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-03-13
Publication Date
2024-11-12
Estimated Expiration
2040-03-13

AI Technical Summary

Technical Problem

Migrating the User Plane Function (UPF) of existing edge computing (EC) platforms is costly and time-consuming. Differences between enterprise IT environments and carrier EC platforms make migration difficult, and reliance on virtualization and containerization layers leads to high costs and long lead times.

Method used

The system-on-a-chip (SoC) composed of a field-programmable gate array (FPGA) and a processor directly forwards user plane data between the terminal device and the server. Based on the GTP-U protocol, it eliminates the intermediate layer and realizes a bare-metal UPF.

Benefits of technology

The UPF enables low-cost, rapid deployment, eliminating the need to migrate enterprise IT environments, reducing hardware and management costs of the EC platform, and shortening delivery time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115244955B_ABST
    Figure CN115244955B_ABST
Patent Text Reader

Abstract

The present disclosure provides a device (300) for implementing a user plane function (UPF). The device (300) includes: a field programmable gate array (FPGA) (310) configured to forward user plane data between a terminal device and a server; and a processor (320) connected to the FPGA (310) and configured to receive control information from a core network and transmit the control information to the FPGA (310) to control the forwarding of the user plane data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to communication technology, and more particularly, to an apparatus and method for implementing a User Plane Function (UPF). Background Art

[0002] Edge computing (EC) is an important feature brought by the fifth generation (5G) technology, which is used to provide connectivity between operator networks and enterprise information technology (IT) service networks at the edge of the network via the radio access network (RAN) and close to users. EC aims to reduce latency, ensure a highly efficient and secure network, and provide an improved user experience.

[0003] Figure 1 The general architecture of the EC solution is shown. As shown in the figure, the operator's 5G core control plane includes a network repository function (NRF), a policy control function (PCF), a unified data management (UDM), a network exposure function (NEF), an authentication server function (AUSF), an access and mobility management function (AMF), and a session management function (SMF). The AMF is connected to the user equipment (UE) via the N1 interface and to the access network (AN) via the N2 interface. The user plane function (UPF) is implemented in the EC platform and is connected to the AN via the N3 interface and to the SMF via the N4 interface. The EC platform also includes standard X86 servers, switches and routers, a hypervisor layer (virtual machines (VMs) / containers), (virtualization infrastructure manager) VIM, a firewall, and a mobile edge platform (MEP) connected to the mobile edge platform manager (MEPM). In addition, as Figure 1 As shown by the arrows in , the applications (APPs) in the enterprise server need to be migrated to the EC platform. This migration is a challenging task for both operators and enterprises because the EC platform is developed by the operator, while the APPs are usually customized and / or developed on the enterprise's dedicated operating system (OS). Therefore, due to the various differences between the operator's EC platform and the enterprise's IT environment, the migration of the APP may require great efforts.

[0004] In addition, EC platforms are usually built on top of a virtualization layer (e.g., OpenStack) and a containerization layer (e.g., Kubernetes, also known as K8S). In this case, UPF or containerized network function (CNF) / virtualized network function (VNF) heavily relies on cloud platforms such as OpenStack or K8S. These layers / platforms require 4 or 6 X86 servers, resulting in high costs. In addition, Figure 1The EC solution shown has a relatively long lead time (e.g., more than one month), including two weeks of hardware delivery, as well as time for network function virtualization infrastructure (NFVI) installation, UPF installation, and interconnect troubleshooting. Summary of the invention

[0005] An object of the present disclosure is to provide an apparatus and method for implementing a UPF that can solve at least one of the above problems.

[0006] According to a first aspect of the present disclosure, a device for implementing a UPF is provided. The device includes: a field programmable gate array (FPGA), configured to forward user plane data between a terminal device and a server; and a processor, connected to the FPGA, and configured to receive control information from a core network and transmit the control information to the FPGA to control the forwarding of the user plane data.

[0007] In an embodiment, the user plane data may include: first user plane data from the server and to be forwarded to the terminal device, and / or second user plane data from the terminal device and to be forwarded to the server.

[0008] In an embodiment, the FPGA may be configured to forward first user plane data to a terminal device and / or receive second user plane data from a terminal device via a radio access network (RAN) using a general packet radio service (GPRS) tunneling protocol-user plane (GTP-U).

[0009] In an embodiment, the control information may include: first packet data unit (PDU) session information for forwarding first user plane data, including one or more of the following: an Internet Protocol (IP) address of a terminal device, a first tunnel endpoint identifier (TEID) associated with the terminal device, or an IP address of an interface with the RAN; and / or second PDU session information for forwarding second user plane data, comprising one or more of the following: an IP address of the terminal device, or a second TEID associated with the terminal device.

[0010] In an embodiment, the FPGA may include a memory storing a first table including first PDU session information and a second table including second PDU session information.

[0011] In an embodiment, the FPGA may be configured to receive first user plane data from a server and / or forward second user plane data to the server using IP.

[0012] In an embodiment, the FPGA may be further configured to transmit user plane data to the processor, and the processor may be configured to forward the user plane data based on the control information.

[0013] In an embodiment, the processor may be connected to the FPGA via direct memory access (DMA).

[0014] In an embodiment, the FPGA and the processor may share a physical layer port.

[0015] In an embodiment, the processor may be an Advanced Reduced Instruction Set Computing (RISC) Machine (ARM) based processor.

[0016] In an embodiment, the FPGA and the processor may form a system on a chip (SoC).

[0017] In an embodiment, the apparatus may be applied in an EC platform co-located with a server.

[0018] According to a second aspect of the present disclosure, a method for implementing UPF is provided, which includes: receiving control information from a core network by a processor; transmitting the control information to an FPGA by the processor; and forwarding user plane data between a terminal device and a server by the FPGA based on the control information.

[0019] In an embodiment, the user plane data may include: first user plane data from the server and to be forwarded to the terminal device, and / or second user plane data from the terminal device and to be forwarded to the server.

[0020] In an embodiment, first user plane data may be forwarded to the terminal device and / or second user plane data may be received from the terminal device via the RAN using GTP-U.

[0021] In an embodiment, the control information may include: first PDU session information for forwarding first user plane data, including one or more of the following: an IP address of the terminal device, a first TEID associated with the terminal device, or an IP address of an interface with the RAN; and / or second PDU session information for forwarding second user plane data, comprising one or more of the following: an IP address of the terminal device, or a second TEID associated with the terminal device.

[0022] In an embodiment, the method may further include: storing, by the FPGA, a first table including the first PDU session information and a second table including the second PDU session information in a memory.

[0023] In an embodiment, using IP, first user plane data may be received from a server and / or second user plane data may be forwarded to the server.

[0024] In an embodiment, the method may further include: transmitting, by the FPGA, the user plane data to the processor; and forwarding, by the processor, the user plane data based on the control information.

[0025] In an embodiment, the processor may be connected to the FPGA via DMA.

[0026] In an embodiment, the FPGA and the processor may share a physical layer port.

[0027] In an embodiment, the processor may be an ARM based processor.

[0028] In an embodiment, the FPGA and the processor may form a SoC.

[0029] In an embodiment, the method may be applied in an EC platform co-located with a server.

[0030] Through the embodiments of the present disclosure, a UPF having an FPGA for user plane functions (e.g., forwarding based on GTP-U) and a processor for control plane functions (e.g., control of forwarding) can be implemented. The UPF is based on a "bare metal" and relies only on an FPGA and a processor, with no intermediate layer between the application and the hardware. The UPF can be implemented at a much lower cost and is faster and easier to deploy, for example, in a plug-and-play manner. In addition, enterprises or operators do not need to perform migration work because the UPF is implemented without any operating system, so that the enterprise IT environment can remain as it is when running using the EC platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The above and other objects, features and advantages will become more apparent from the following description of the embodiments with reference to the accompanying drawings, in which:

[0032] Figure 1 is a schematic diagram showing a general architecture of an EC solution;

[0033] Figure 2 is a schematic diagram showing an exemplary architecture of an EC solution according to an embodiment of the present disclosure;

[0034] Figure 3 is a block diagram of an apparatus for implementing UPF according to an embodiment of the present disclosure and a network scenario in which the apparatus is deployed;

[0035] Figure 4 It shows Figure 3 A schematic diagram of a specific structure of the device;

[0036] Figure 5 It shows Figure 3 A schematic diagram of another specific structure of the device in; and

[0037] Figure 6 is a flowchart illustrating a method for implementing UPF according to an embodiment of the present disclosure. Specific embodiments

[0038] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0039] Figure 2 is a schematic diagram showing an exemplary architecture of an EC solution according to an embodiment of the present disclosure. As shown in the figure, the UPF can be moved to be co-located with an enterprise server (e.g., in an enterprise IT environment). For example, the UPF can be directly connected to a router or switch in the enterprise IT environment, or directly plugged into a service computer in the enterprise IT environment as a peripheral component interconnect express (PCIe) card. The UPF can be deployed within a day, a few hours, or even a few minutes. When combined with Figure 1 Compared with the architecture shown in the figure, in this architecture, the savings can be as follows Figure 1 The cost of the hypervisor layer, hardware and VIM is shown. More importantly, there is no need to migrate the APP from the enterprise IT environment to the operator's EC platform.

[0040] Figure 3 1 is a block diagram of an apparatus 300 for implementing UPF according to an embodiment of the present disclosure and a network scenario in which the apparatus 300 is deployed. As shown in the figure, the apparatus 300 can be set in an EC platform co-located with a server 400 (for example, in an enterprise IT environment). The server 400 can be an enterprise server, a cloud server, or any suitable device that hosts, for example, an enterprise APP.

[0041] The device 300 includes an FPGA 310 and a processor 320. The processor 320 may be an ARM-based processor (or alternatively, an X86-based processor). The FPGA 310 and the processor 320 may be integrated in a system on a chip (SoC) and may communicate with each other using DMA. The DMA channel may be used to transmit control information and packet data at high speed. Alternatively, the FPGA 310 and the processor 320 may be separated and may be connected via an inter-integrated circuit (I2C) bus to work as a system.

[0042] FPGA 310 is configured to forward user plane data between terminal device (or UE) 200 and server 400. As shown, FPGA 310 can communicate with RAN 150 (which serves UE 200 via an air interface) via N3 interface using, for example, GTP-U, and communicate with server 400 via N6 interface using, for example, IP. Processor 320 is connected to FPGA 310, for example, via DMA, and is configured to receive control information from core network (e.g., 5G core network) 100 and transmit the control information to FPGA 310 to control the forwarding of user plane data. Processor 320 can communicate with core network 100 via N4 interface using, for example, packet forwarding control protocol (PFCP).

[0043] Here, the user plane data may include: user plane data from the server 400 and to be forwarded to the UE 200 (hereinafter, referred to as downlink data), and / or user plane data from the UE 200 and to be forwarded to the server 400 (hereinafter, referred to as uplink data). The FPGA 310 may be configured to forward the downlink data to the UE 200 via the RAN 150 using GTP-U (through the N3 interface), and / or receive uplink data from the UE 200. The FPGA 310 may be configured to receive downlink data from the server 400 using IP (through the N6 interface), and / or forward uplink data to the server 400.

[0044] Therefore, the control information may include first PDU session information (downlink PDU session information) for forwarding downlink data, the first PDU session information including one or more of the following: an IP address of UE 200, a first TEID associated with UE 200 (TEID for downlink), or an IP address of an interface with RAN 150. Additionally or alternatively, the control information may include second PDU session information (uplink PDU session information) for forwarding uplink data, the second PDU session information including one or more of the following: an IP address of UE 200, or a second TEID associated with UE 200 (TEID for uplink).

[0045] In an example, the FPGA 310 may include a memory that stores a first table (eg, a hash table for a downlink) containing first PDU session information and a second table (eg, a hash table for an uplink) containing second PDU session information.

[0046] Optionally, FPGA 310 may also be configured to transmit user plane data to processor 320, and processor 320 may be configured to forward user plane data based on control information. FPGA 310 may process GTP-U-based forwarding in real time. When features such as packet detection rules (PDR), forwarding action rules (FAR), quality of service (QoS) enhancement rules (QER), buffer action rules (BAR), or any combination thereof are to be supported, user plane data may be transmitted to processor 320 for forwarding.

[0047] Figure 4 It shows Figure 3 Schematic diagram of the specific structure of the device 300 in FIG. As shown in the figure, the processor (e.g., an ARM processor) 320 may include an application module 321 and an OS / kernel 322. The application module 321 may include: a UPF function 701 having a PFCP endpoint connected to a network interface controller (NIC) and configured to communicate with the core network 100 to receive control information (downlink (DL) PDU session information and / or uplink (UL) PDU session information); and an FPGA management module configured to transmit the control information to a DMA interface 702. The FPGA management module is used to provide and update control information to the FPGA 310 and to collect FPGA service statistics and counts. The control information is then transmitted to a DMA driver 703 in the OS / kernel 322 through an application programming interface (API) call, and then transmitted to a DMA IP core 704 in the FPGA 310 through DMA. The control information is stored in a hash table 705, for example, DL PDU session information is stored in a hash table for DL, and UL PDU session information is stored in a hash table for UL.

[0048] For UL forwarding, FPGA 310 may use a physical layer (PHY) port (e.g., Ethernet PHY port) 706 (via N3 interface) to forward data via RAN (e.g., Figure 3 RAN 150 in the UE (eg, Figure 3UE 200 in Receives UL data. The UL data then undergoes media access control (MAC) frame decoding and cyclic redundancy check (CRC) at the Ethernet MAC module 707, and undergoes IP packet decoding and IP address matching for the N3 interface at the IP (e.g., IP version 4 or IPv4) module 708. The UL data also undergoes multiplexing and packet filtering with respect to protocol type, checksum, IP address, and User Datagram Protocol (UDP) port. The GTP-U decapsulation module 709 extracts the TEID from the UL data and queries the UL PDU session information (including, for example, the IP address of the UE and the UL TEID of the UE) from the hash table 705. The UL data / packet will be processed based on the query result from the hash table 705. The GTP-U decapsulation module 709 removes the GTP-U header of the packet with the valid TEID, and transmits the decoded GTP-U inner packet to the IPv4 module 708 to be forwarded (via the N6 interface) to the server (e.g., Figure 3 FPGA 310 may also include an address resolution protocol (ARP) cache 710 for address resolution.

[0049] For DL ​​forwarding, FPGA 310 can use Ethernet PHY port 706 (through N6 interface) to receive data from a server (e.g., Figure 3 The DL data is then subjected to MAC frame decoding and CRC at the Ethernet MAC module 707, and IP packet decoding and IP checksum verification at the IPv4 module 708. The GTP-U encapsulation module 711 queries the DL PDU session information (including, for example, the IP address of the UE, the DL TEID of the UE, and the RAN (for example, Figure 3 The DL data / packet will be processed based on the query result from the hash table 705. The GTP-U encapsulation module 711 constructs a GTP-U packet header based on the DL PDU session information, recalculates the IP checksum and forwards the resulting GTP-U packet to the UE (e.g., Figure 3 Optionally, the GTP-U encapsulation module 711 may transmit the GTP-U packet to the processor 320 to be forwarded to the UE 200.

[0050] Figure 5 It shows Figure 3 Schematic diagram of another specific structure of the device 300 in FIG. Figure 4The difference of the structure shown is that the FPGA 310 and the processor 320 share a physical layer (PHY) port (e.g., an Ethernet PHY port) 706. In other words, the Ethernet PHY port 706 can be shared by the N3 interface, the N4 interface, and the N6 interface. In this case, the FPGA 310 and the processor 320 can use different IP addresses. The processor 320 can have its own ARP module, which can be implemented in the OS / kernel 322. The FPGA 310 can include a multiplexer / arbiter 712 for directing data / traffic to the FPGA 310 or the processor 320. For example, the multiplexer / arbiter 712 can be configured to receive an IP packet with a MAC address from the IPv4 module 708 and forward it to the MAC module 707, or receive a MAC frame with an Ethernet payload and a MAC address and forward it to the MAC module 707.

[0051] Figure 6 6 is a flow chart showing a method 600 according to an embodiment of the present disclosure. The method 600 may be executed by the apparatus 300 as described above.

[0052] At block 610, a processor (e.g., Figure 3 The processor 320 in receives control information from the core network.

[0053] At block 620, the processor transmits control information to the FPGA (e.g., Figure 3 FPGA 310 in.

[0054] At block 630 , the FPGA forwards user plane data between the terminal device and the server based on the control information.

[0055] In an embodiment, the user plane data may include: first user plane data from the server and to be forwarded to the terminal device, and / or second user plane data from the terminal device and to be forwarded to the server.

[0056] In an embodiment, first user plane data may be forwarded to the terminal device and / or second user plane data may be received from the terminal device via the RAN using GTP-U.

[0057] In an embodiment, the control information may include: first PDU session information for forwarding first user plane data, including one or more of the following: an IP address of the terminal device, a first TEID associated with the terminal device, or an IP address of an interface with the RAN; and / or second PDU session information for forwarding second user plane data, comprising one or more of the following: an IP address of the terminal device, or a second TEID associated with the terminal device.

[0058] In an embodiment, the method 600 may further include: storing, by the FPGA, a first table including the first PDU session information and a second table including the second PDU session information in a memory.

[0059] In an embodiment, using IP, first user plane data may be received from a server and / or second user plane data may be forwarded to the server.

[0060] In an embodiment, the method 600 may further include: transmitting, by the FPGA, the user plane data to the processor; and forwarding, by the processor, the user plane data based on the control information.

[0061] In an embodiment, the processor may be connected to the FPGA via DMA.

[0062] In an embodiment, the FPGA and the processor may share a physical layer port.

[0063] In an embodiment, the processor may be an ARM based processor.

[0064] In an embodiment, the FPGA and the processor may form a SoC.

[0065] In an embodiment, the method 600 may be applied in an EC platform co-located with a server.

[0066] The present disclosure has been described above with reference to its embodiments. It should be understood that various modifications, substitutions and additions may be made by those skilled in the art without departing from the spirit and scope of the present disclosure. Therefore, the scope of the present disclosure is not limited to the above specific embodiments, but is only limited by the appended claims.

Claims

1. A device (300) for implementing a user plane function UPF, comprising: A field programmable gate array FPGA (310) configured to forward user plane data between the terminal device and the server; as well as a processor (320) connected to the FPGA (310) and configured to receive control information from a core network and transmit the control information to the FPGA (310) to control forwarding of the user plane data; The FPGA (310) is further configured to transmit the user plane data to the processor (320) in real time, and the processor (320) is configured to forward the user plane data based on the control information; The FPGA (310) supports one or more of a packet detection rule PDR, a forwarding action rule FAR, a quality of service QoS enhancement rule QER, a buffer action rule BAR or any combination thereof; The processor (320) is an Advanced Reduced Instruction Set Computing (RISC) machine (ARM) based processor.

2. The device (300) according to claim 1, wherein: The user plane data includes: first user plane data from the server to be forwarded to the terminal device, and / or second user plane data from the terminal device to be forwarded to the server.

3. The device (300) according to claim 2, wherein: The FPGA (310) is configured to forward the first user plane data to the terminal device and / or receive the second user plane data from the terminal device via a radio access network RAN ​​using a general packet radio service GPRS tunneling protocol-user plane GTP-U.

4. The device (300) according to claim 3, wherein: The control information includes: first packet data unit (PDU) session information for forwarding the first user plane data, comprising one or more of the following: an Internet Protocol (IP) address of the terminal device, a first tunnel endpoint identifier (TEID) associated with the terminal device, or an IP address of an interface with the RAN, and / or The second PDU session information used to forward the second user plane data includes one or more of the following: the IP address of the terminal device, or a second TEID associated with the terminal device.

5. The device (300) according to claim 4, wherein: The FPGA (310) includes a memory storing a first table including the first PDU session information and a second table including the second PDU session information.

6. The device (300) according to any one of claims 2 to 5, wherein: The FPGA (310) is configured to receive the first user plane data from the server and / or forward the second user plane data to the server using IP.

7. The device (300) according to any one of claims 1 to 6, wherein: The processor (320) is connected to the FPGA (310) via direct memory access (DMA).

8. The device (300) according to any one of claims 1 to 7, wherein: The FPGA (310) and the processor (320) share a physical layer port.

9. The device (300) according to any one of claims 1 to 8, wherein: The FPGA (310) and the processor (320) form a system on chip (SoC).

10. The device (300) according to any one of claims 1 to 9, wherein: The device (300) is applied in an edge computing EC platform co-located with the server.

11. A method (600) for implementing a user plane function UPF, comprising: Receiving (610) control information from a core network by a processor; The processor transmits (620) the control information to a field programmable gate array (FPGA); as well as The FPGA forwards (630) user plane data between the terminal device and the server based on the control information; wherein the FPGA transmits the user plane data to the processor in real time, and the processor forwards the user plane data based on the control information; The FPGA supports one or more of a packet detection rule PDR, a forwarding action rule FAR, a quality of service QoS enhancement rule QER, a buffer action rule BAR or any combination thereof; The processor is an Advanced Reduced Instruction Set Computing (RISC) Machine (ARM) processor.

12. The method (600) of claim 11, wherein: The user plane data includes: first user plane data from the server to be forwarded to the terminal device, and / or second user plane data from the terminal device to be forwarded to the server.

13. The method (600) of claim 12, wherein: The first user plane data is forwarded to the terminal device and / or the second user plane data is received from the terminal device via a radio access network RAN ​​using a General Packet Radio Service "GPRS" Tunneling Protocol-User Plane GTP-U.

14. The method (600) of claim 13, wherein: The control information includes: first packet data unit (PDU) session information for forwarding the first user plane data, comprising one or more of the following: an Internet Protocol (IP) address of the terminal device, a first tunnel endpoint identifier (TEID) associated with the terminal device, or an IP address of an interface with the RAN, and / or The second PDU session information used to forward the second user plane data includes one or more of the following: the IP address of the terminal device, or a second TEID associated with the terminal device.

15. The method (600) of claim 14, further comprising: The FPGA stores a first table including the first PDU session information and a second table including the second PDU session information in a memory.

16. The method (600) according to any one of claims 12 to 15, wherein: The first user plane data is received from the server using IP and / or the second user plane data is forwarded to the server using IP.

17. The method (600) according to any one of claims 11 to 16, wherein: The processor is connected to the FPGA via direct memory access (DMA).

18. The method (600) according to any one of claims 11 to 17, wherein: The FPGA and the processor share a physical layer port.

19. The method (600) according to any one of claims 11 to 18, wherein: The FPGA and the processor form a system on chip SoC.

20. The method (600) according to any one of claims 11 to 19, wherein: The method is applied in an edge computing EC platform co-located with the server.