Local offloading method and system for ultra-reliable low-latency communication

By configuring the core network, radio unit and intelligent controller in a 5G private network and establishing the F1 local shunt routing program, the problems of high I-UPF LBO delay and insufficient F1-LBO support are solved, and low-latency communication and security are achieved Improved, suitable for microsecond level application requirements.

CN115379524BActive Publication Date: 2024-12-06WISTRON NEWEB CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110542537.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-05-18
Publication Date
2024-12-06
Estimated Expiration
2041-05-18

AI Technical Summary

Technical Problem

In the prior art, the end-to-end communication delay of the 5G private private network may exceed 1ms for the two terminals, and the standard F1-LBO support is lacking, resulting in insufficient management and security.

Method used

Provide a local shunt method and system for ultra-reliable low-latency communication for next-generation radio access networks, and establish F1 by configuring the core network, radio unit, distribution unit, central unit and near real-time radio access network intelligent controller. The local shunt routing program sets the local shunt dedicated radio bearer, and configures the virtual network function module through the F1-LBO routing program to establish a routing comparison table to achieve low-latency communication.

Benefits of technology

It realizes a mechanism to support microsecond-level application requirements without modifying the original network equipment and user devices, comply with 3GPP NG-RAN and 5G core network standards, establish F1-LBO shortcuts, and maintain the continuous line of UPF PDN sessions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115379524B_ABST
    Figure CN115379524B_ABST
Patent Text Reader

Abstract

A local offload method and system for ultra-reliable low-latency communication for next-generation radio access networks. The local offload method for ultra-reliable low-latency communication includes: configuring a core network to establish a data packet data unit session between a first user device and the core network; configuring the first user device to establish a local ultra-reliable low-latency communication service; configuring a near-real-time radio access network intelligent controller to establish an F1 local offload routing program; configuring an F1 local offload virtual network function module with transmission rules through the F1 local offload routing program to establish a routing comparison table through the F1 local offload virtual network function module; configuring the F1 local offload virtual network function module to establish an F1 local offload session between the first user device and the second user device according to the routing comparison table. The local offload method and system for ultra-reliable low-latency communication for next-generation radio access networks of the present invention can support lower microsecond level application requirements.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a traffic offloading method and system, and in particular to a local traffic offloading method and system for ultra-reliable low-latency communication in a next-generation radio access network. Background Art

[0002] With the rise of 5G private networks, enterprises are meeting their network requirements for enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), massive internet of things (mIOT) and data privacy.

[0003] Among them, URLLC and data privacy are important incentives for enterprises to consider whether to build 5G private networks. Therefore, Multi-access Edge Computing (MEC) with Local Break Out (LBO), also known as Local Business Operation (LBO), has become the most important network module.

[0004] MEC provides a hardware virtualization execution platform that can set up the centralized / distributed units (CU / DU) of the data link layer (L2) / radio resource control layer (L3) under the 5G transmission specification, and even part of the 5G core network (Core Network) virtual network software in the MEC. The enterprise's virtual local operation application server software can also be installed in the MEC.

[0005] By using the LBO connection established by the internal user plane function (I-UPF) of the front-end MEC, the private services within the enterprise are directed to the virtual local operation application server software, which can not only reduce latency but also prevent the leakage of confidential data. The LBO of this architecture is called I-UPF LBO.

[0006] However, this I-UPF LBO may still have a large delay of more than 1ms for the end-to-end communication delay between the two terminals, which is not conducive to high synchronization demand services such as smart factories or smart transportation. Therefore, a lower latency F1 interface (interface between DU and CU) LBO is needed.

[0007] Currently, there is no standard F1-LBO supported in the standard specifications. Generally speaking, it is a vendor-specific proprietary solution. The proposed method does not need to establish the UPF PDN Session through the 3GPP 5GC Control Plane (CP), which may cause the disadvantages of insufficient manageability and security.

[0008] Therefore, it is necessary to provide a local offload method and system for ultra-reliable low-latency communication in a next-generation radio access network to solve the above problems. Summary of the invention

[0009] The technical problem to be solved by the present invention is to provide a URLLC-LBO method and system that complies with the 3GPP 5GC connection process in view of the shortcomings of the prior art.

[0010] In order to solve the above technical problems, one of the technical solutions adopted by the present invention is to provide an ultra-reliable and low latency communications local breakout (URLLC-LBO) method for a next generation radio access network (NG-RAN), which includes: configuring a core network to establish a data packet data unit (PDU) session between a first user equipment (UE) and the core network, and the PDU session is via a radio unit (RU), a first distributed unit (DU) and a central unit (CU) arranged between the first UE and the core network; configuring the first UE to establish a local ultra-reliable and low latency communications (URLLC) service; configuring a near real-time radio access network intelligent controller (Near Real-Time Radio Access Network Intelligence Controller, Near-RT RIC) to establish an F1 local breakout (F1-Local A Local Breakout (F1-LBO) routing program is used to set a Local Breakout Dedicated Radio Bearer (LBO DRB) for the URLLC service; an F1 local breakout virtual network function (VNF) module is configured with a transmission rule through the F1-LBO routing program to establish a routing comparison table through the F1 local breakout VNF ​​module, wherein a correspondence between a first position and a second position of the DRB is defined in the routing comparison table, wherein the first position is a first tunnel endpoint identifier (TEID) of the first UE, and the second position is a second TEID of a second UE or an Internet Protocol (IP) address of a multi-access edge computing (MEC) device;And configuring the F1 local offload VNF module to establish an F1 local offload session between the first UE and the second UE according to the routing comparison table, or to establish the F1 local offload session between the first UE and a virtual central unit (vCU) user plane (UP) executed by the MEC device. ;

[0011] In order to solve the above technical problems, another technical solution adopted by the present invention is to provide an ultra-reliable and low latency communications (URLLC) local breakout (LBO) system for the next generation radio access network (NG-RAN), which includes a first user equipment (UE), a core network, a radio unit (RU), a first distributed unit (DU), a central unit (CU), a near real-time radio access network intelligent controller (Near Real-Time Radio Access Network Intelligence Controller, Near-RT RIC) and an F1 local breakout virtual network function (VNF) module. The first UE is configured to establish a local ultra-reliable and low latency communications (URLLC) service. The core network is configured to establish a first data packet data unit (PDU) session between the first UE and the core network. The RU is connected between the first UE and the core network. The first DU is connected between the RU and the core network. The CU is connected between the first DU and the core network. The Near-RT RIC is configured to establish an F1-Local Breakout (F1-LBO) routing program to set up a local breakout dedicated radio bearer (Local Breakout Dedicated Radio Bearer, LBO DRB) for the URLLC service. The F1 VNF module is connected between the first DU and the CU. The F1-LBO routing program is executed to configure the F1 local breakout VNF ​​module with transmission rules to establish a routing comparison table, wherein the routing comparison table defines a correspondence between a first position and a second position related to the DRB. The first position is the first tunnel endpoint identifier (TEID) of the first UE, and the second position is the second TEID of the second UE or the Internet Protocol (IP) address of the multi-access edge computing (MEC) device.The F1 local offload VNF module is also configured to establish an F1 local offload session for the LBO DRB between the first UE and the second UE according to the pair of routing tables, or to establish the F1 local offload session between the first UE and a virtual central unit (vCU) user plane (UP) executed by the MEC device.

[0012] One of the beneficial effects of the present invention is that the URLLC-LBO method and system for NG-RAN provided by the present invention is suitable for the F1 interface between CU and DU, can support lower microsecond level application requirements, and comply with 3GPP NG-RAN and 5G core network (5GC) standards. Therefore, it can comply with the management interface standard of the Near Real-Time RAN Intelligent Controller (Near-RT RIC) of the Open Radio Access Network (O-RAN) Working Group 3 without modifying the original network equipment and user equipment (UE) to establish an F1-LBO shortcut, and can also maintain a mechanism for maintaining an uninterrupted UPF PDN session.

[0013] To further understand the features and technical contents of the present invention, please refer to the following detailed description and drawings of the present invention. However, the drawings provided are only for reference and description and are not intended to limit the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 It is a functional block diagram of a local distribution system provided according to a first embodiment of the present invention.

[0015] Figure 2 FIG. 1 is a schematic diagram of an O-RAN architecture according to a first embodiment of the present invention.

[0016] Figure 3 Flow chart of the URLLC-LBO method according to an embodiment of the present invention.

[0017] Figure 4 FIG. 1 is a flow chart of a disconnection mechanism according to a first embodiment of the present invention.

[0018] Figure 5 It is a functional block diagram of a local distribution system provided according to a second embodiment of the present invention.

[0019] Figure 6 FIG. 4 is a flow chart of a disconnection mechanism according to a second embodiment of the present invention.

[0020] Figure 7 FIG. 4 is a flow chart of establishing a DRB through Near-RT RIC according to the third embodiment of the present invention.

[0021] Main component symbols:

[0022] 10 First UE

[0023] 11 Second UE

[0024] 12 RU

[0025] 13-1 First DU

[0026] 13-2 Second DU

[0027] 14 CU

[0028] 15 Near-RT RIC

[0029] 150 F1-LBO Routing Procedure

[0030] 16 F1 Gateway

[0031] 160 F1-LBO VNF

[0032] 17 MEC equipment

[0033] 170 vCU-UP

[0034] 5GC CP 5G core control plane

[0035] 5GC UPF 5G core user plane function

[0036] CN Core Network

[0037] LAN interface Local Area Network

[0038] MSO MECMSO MEC Multi-system operator multi-access edge computing

[0039] UPF Multi-system operator multi-access edge computing user plane function

[0040] Non-RT RIC Non-real-time radio access network intelligent controller

[0041] P0 Public Server

[0042] P1 Public Services

[0043] UDM Unified Data Management

[0044] SMO Service Management and Orchestration

[0045] O-CU-CP Control plane of O-CU

[0046] O-CU-UP O-CU user interface

[0047] O-Cloud

[0048] RAN Radio Access Network

[0049] E2, F1-C / U, A1, O1, O2, F1-c, F1-u, OFH CUS-Plane, OFH M-Plane interface DETAILED DESCRIPTION

[0050] The following is an explanation of the implementation methods of the "local offloading method and system for ultra-reliable low-latency communication for the next generation radio access network" disclosed in the present invention through specific embodiments. Those skilled in the art can understand the advantages and effects of the present invention from the contents disclosed in this specification. The present invention can be implemented or applied through other different specific embodiments, and the details in this specification can also be modified and changed in various ways based on different viewpoints and applications without departing from the concept of the present invention. In addition, the drawings of the present invention are only simple schematic illustrations and are not depicted in actual size. It is stated in advance. The following embodiments will further explain the relevant technical contents of the present invention in detail, but the disclosed contents are not intended to limit the scope of protection of the present invention. In addition, the term "or" used in this article may include any one or more combinations of the associated listed items depending on the actual situation.

[0051] Figure 1 FIG. 1 is a functional block diagram of a local distribution system according to a first embodiment of the present invention. Figure 1As shown, the first embodiment of the present invention provides an ultra-reliable and low latency communications (URLLC) local breakout (LBO) system 1 for a next generation radio access network (NG-RAN), which includes a first user equipment (UE) 10, a core network CN, a radio unit (RU) 12, a first distributed unit (DU) 13-1, a central unit (CU) 14, a near real-time radio access network intelligence controller (Near-RT RIC) 15, an F1 gateway 16 and a multi-access edge computing (MEC) device 17.

[0052] Please refer to Figure 2 , which is a schematic diagram of the O-RAN architecture according to the first embodiment of the present invention. In short, the system and method provided by the present invention are mainly based on the 5G open radio access network (Open-Radio Access Network, O-RAN) architecture. In the past, the access network technology difficulty of 2G / 3G was relatively low, and it was usually integrated and built on the same architecture. In 5G, it is divided into a three-layer architecture of RU, DU, and CU, and the O-RAN Alliance standardized this three-layer architecture as O-CU, O-DU, and O-RU. Figure 2 In the 3GPP architecture, the prefix "O-" is added to each component (CU, DU, RU) to represent the interfaces and functions newly added to support O-RAN.

[0053] It should be noted that the devices, units, networks, modules and gateways mentioned in the present invention can be implemented in the form of hardware, software or firmware. When implemented in hardware, they may include the memory, processor and network interface included in a general computer system. When implemented in software or firmware, they may be stored in the memory of the aforementioned computer system and their functions may be performed by the processor.

[0054] Among them, O-CU is responsible for the packet data convergence protocol (PDCP) layer of the protocol, O-DU is responsible for all baseband processing, scheduling, radio link control (RLC), media access control (MAC) and physical layer (PHY), and O-RU is responsible for the components of physical layer processing, including analog components of wireless transmitters and receivers.

[0055] exist Figure 1 In the architecture, RU12, the first DU13-1 and CU14 are connected between the first UE10 and the core network CN. The core network CN may include MSO MEC and MSO MEC user plane function (UPF) under the edge cloud of the multi-system operator (MSO), 5G core (5GC for short) UPF, 5GC control plane (CP), unified data management (UDM) and non-real-time radio access network intelligent controller (Non Real-Time Radio Access Network Intelligent Controller, Non-RT RIC) under the cloud center, and public service P1 provided by the public server P0.

[0056] Before explaining Near-RT RIC 15, we need to first explain the service management and orchestration framework (SMO). Figure 2 The system architecture proposed by O-RAN is based on the 3GPP radio access network (RAN) architecture, adding SMO, non-real-time radio access network intelligent controller (Non-RealTime RAN Intelligent Controller, Non-RT RIC) and near-real-time network intelligent controller (Near-RT RAN Intelligent Controller, Near-RT RIC) and other functional components, as well as O1, O2, A1, E2 interfaces, to support intelligent control mechanisms. Among them, O-DU is also connected to the control plane (Control Plane, CP) of O-CU through the F1-c interface, and connected to the user plane (User Plane, UP) of O-CU through the F1-u interface.

[0057] SMO is set up in the cloud center and is the management center of the 5G network. SMO provides management services for network facilities. Its management interfaces and management contents include O1 interface, O2 interface and Open Fronthaul M-Plane interface. O1 interface is used for fault, configuration, accounting, performance, and security (FCAPS) management, and O2 interface is used for resource and load management of the cloud platform (O-Cloud). The Open Fronthaul (OFH) M-Plane interface and OFH CUS-Plane interface are used for the management of O-RU.

[0058] On the other hand, Non-RT RIC is located in SMO, and its functions include data analysis, training machine learning models, providing additional information (Enrichment Information), and setting policies (Policies). The data analysis and training machine learning model functions of Non-RT RIC can obtain RAN-related data from SMO and user-related data from the application server, apply machine learning methods, and train recognition or prediction models in an offline manner for individual purposes. The machine learning model is deployed in the near-real-time network intelligent controller (Near-RT RIC), which can actively / preemptively adjust network resource configuration in response to changes in traffic and environment. The A1 interface can be used to set guidelines for individual or a group of users, such as QoE targets, preferred cells or frequency bands. The guideline setting or adjustment cycle of the A1 interface has a response time or interval of more than 1 second, so it is called non-real-time.

[0059] In addition, Near-RT RIC is located in the RAN, receiving and analyzing real-time information from the RAN, combining it with additional information provided by the Non-RT RIC, and using the machine learning model deployed by the Non-RT RIC to monitor or predict changes in user connection conditions. Once it is found that the policy set by the Non-RT RIC may not be achieved, the RAN parameters need to be adjusted, such as adjusting resource allocation, transmission rate, transmission priority, switching connection points, handovers, etc., so that each user can continue to maintain the established policy goals.

[0060] Near-RT RIC can adjust RAN through the E2 interface. Because it can monitor the network status in near real time, the response time and cycle of E2 interface control are within 1 second. Figure 2As shown, in the Near-RT RIC, an executable application (xApp) can be used to monitor data and adjust parameters of RAN functions according to different application scenarios. The present invention implements the LBO function of the F1 interface by executing the F1-LBO routing program (xApp) 150 through the Near-RT RIC.

[0061] In the first embodiment, the F1 local offload VNF module 160 is executed through the F1 gateway 16. The F1 gateway 16 is connected to the first DU13-1, CU 16 and MEC device 17 through the F1-C / U interface, and is connected to the Near-RTRIC 15 through an E2 interface. The Near-RT RIC 15 and the MEC device 17 can be connected through a local area network (LAN). In this embodiment, the F1 gateway 16 can be connected to multiple distribution units through the F1-C / U interface, for example, connected to the second DU13-2, and the second UE11 can also be connected to the second DU13-2, so the F1 gateway 16 can be used to implement F1-LBO between multiple distribution units.

[0062] The MEC device 17 can provide a hardware virtualized execution platform to set the CU / DU of the data link layer (L2) / radio resource control layer (L3) under the 5G transmission specification, and even part of the 5G core network (Core Network) virtual network software in the MEC, and can also install the enterprise's virtual local operation application server software in the MEC. The MEC device 17 can provide a virtual central unit user plane (Virtual Central Unit User Plane, vCU-UP) 170, which is a virtual CU provided by the MEC device 17, which only executes the user plane (User plane, UP), and this virtual CU does not execute any actions of the control plane (Control plane, CP).

[0063] Under this framework, the URLLC-LBO method provided by the present invention is further described. Figure 3 , which is a flow chart of the URLLC-LBO method according to an embodiment of the present invention. As shown in the figure, the URLLC-LBO method includes:

[0064] Step S30: configuring the core network CN to establish a packet data unit (PDU) session between the first UE 10 and the core network CN.

[0065] The following first describes the PDU session. In the 5G network, the data sent and received between the user equipment and the external network are transmitted in the form of data packets, and these data packets are usually called PDUs. The 5G network calls the path established between the user equipment and the external network a PDU session, and the PDU session will pass through RU12, the first DU13-1 and CU 14.

[0066] Step S31: Configure the first UE10 to establish a URLLC service. In short, this URLLC service is set as a request that can be completed within a delay range of less than 1ms. Its applicable scenario can be, for example, a service for transmitting information between multiple user devices under the same RU under the 5G architecture, or a service initiated by the first UE10 and hoped to be processed by the MEC device 17.

[0067] Step S32: Configure Near-RT RIC to establish F1-LBO routing xAPP to set up a local breakout dedicated radio bearer (LBO DRB) for the URLLC service. In detail, under the 5G architecture, there will be a corresponding DRB for each service.

[0068] In the 3GPP-compliant PDU session management steps, it is specified that the gNB-DU is responsible for allocating the tunnel endpoint identifier (TEID) (TS38.470) of the GPRS Tunnelling Protocol (GTP) of the F1-U interface downlink (DL) for each DRB, and the gNB-CU is responsible for allocating the DU uplink (UL) GTP TEID (TS38.473) for each DRB. The transport bearer can be identified by the GTP-U TEID (TS29.281) and the IP address, for example, the source TEID, the target TEID, the source IP address, and the target IP address.

[0069] In addition, the GTP for User Plane (GTP-U) TEID for the user plane can be used to identify the transport bearer (user plane PDU session), including not only the core network session but also the dedicated radio bearer (DRB) session, and the present invention performs F1-LBO in the DRB session. In addition, in order to comply with the 3GPP standard, the GTP-U (TS 29.281) protocol must be used on the F1 interface between the gNB-DU and the gNB-CU.

[0070] Step S33: Configure the F1-LBO VNF module with the transmission rules through the F1-LBO routing xAPP to establish a routing comparison table. As mentioned above, in order to comply with the 3GPP standard, the correspondence between the first position and the second position of the LBO DRB needs to be defined in the routing comparison table. Since the URLLC service initiator is the first UE10, the first position can be the first TEID of the first UE10, and the second position can be set according to the target of the URLLC service, for example, it can be the second TEID of the second UE11, or it can be the IP address of the MEC device 17.

[0071] Step S34: Configure the F1 local offload VNF module to establish an F1 local offload session between the first UE 10 and the second UE 11 according to the routing comparison table, or to establish an F1 local offload session between the first UE 10 and the vCU-UP 170 executed by the MEC device 17. It should be noted that the vCU-UP 170 only passively recognizes the routing comparison table.

[0072] In addition, in this step, if the target of the LBO DRB is the second UE11, and the second UE11 is connected to the second DU13-2, the F1 local offload VNF module 160 establishes an F1 local offload session between the first UE10 and the second UE11 through the first DU13-1 and the second DU13-2. Therefore, as mentioned above, the F1 gateway 16 can be used to implement LBO between multiple DUs.

[0073] Therefore, under the original 5G architecture, there is no support for standard F1-LBO, and the above-mentioned DRBs need to be transmitted to the core network CN through RU, DU, and CU, and then returned to CU and DU to finally reach the target location. However, the present invention can support lower microsecond level application requirements, and at the same time comply with the 3GPP NG-RAN and 5G core network (5GC) standards and the management interface standard of the Open Radio Access Network (O-RAN) working group 3Near-RT RIC to establish an F1-LBO shortcut.

[0074] In addition, the present invention can also maintain the original PDN session when providing the F1-LBO mechanism. Figure 4 , which is a flow chart of the disconnection mechanism according to the first embodiment of the present invention.

[0075] like Figure 4 As shown, the disconnection mechanism can perform the following steps after the F1 gateway 16 executes the F1 local offload VNF module 160 to establish the F1 local offload session:

[0076] Step S40: configure the F1 gateway to transmit a keep-alive signal to the CU via the F1-U interface.

[0077] In response to the CU receiving the keep-alive signal, the process proceeds to step S41: configuring the CU to transmit the keep-alive signal to the core network to keep the PDU session connected. It should be noted that in order to comply with the GTP-U protocol and be compatible with 3GPP, the frequency of sending the keep-alive signal on each path should not exceed 60s.

[0078] Please refer to Figure 5 , which is a functional block diagram of a local diversion system provided according to a second embodiment of the present invention. In the second embodiment, the same elements are marked with the same element symbols, and repeated descriptions are omitted. The difference is that the LBO system 1 of the second embodiment removes the F1 gateway, and the first DU13-1 executes the F1 local diversion VNF module 160 instead. In addition, in this embodiment, the first DU13-1 is connected to the CU 14 and the MEC device 17 respectively through multiple F1-C / U interfaces, and is connected to the Near-RT RIC 15 through the E2 interface.

[0079] In the second embodiment, although the scalability of the F1 gateway 16 to implement F1-LBO between multiple distribution units is lacking, the first DU 13 - 1 can still be used to implement the F1-LBO shortcut provided by the F1 local diversion VNF module 160 in the first embodiment.

[0080] Therefore, the second embodiment of the present invention can comply with the management interface standard of the O-RAN Working Group 3Near-RT RIC without modifying the original network device and UE.

[0081] In addition, the second embodiment can also maintain the original PDN session when the F1-LBO mechanism is provided. Figure 6 , which is a flow chart of the disconnection mechanism according to the second embodiment of the present invention.

[0082] like Figure 6 As shown, the disconnection mechanism may perform the following steps after the first DU 13 - 1 executes the F1 local offload VNF module 160 to establish the F1 local offload session:

[0083] Step S60: configure the first DU 13 to transmit a keep-alive signal to the CU through the F1-U interface.

[0084] In response to the CU receiving the keep-alive signal, the process proceeds to step S61: configuring the CU to transmit the keep-alive signal to the core network to keep the PDU session connected. Similarly, in order to comply with the GTP-U protocol and be compatible with 3GPP, the frequency of sending the keep-alive signal on each path should not exceed 60s.

[0085] Please refer to further Figure 2 and Figure 7 . Figure 7 FIG. 1 is a flow chart of establishing a routing comparison table of a DRB through a Near-RT RIC according to a third embodiment of the present invention. Figure 2 and Figure 7 As shown, the detailed process of establishing the routing comparison table of LBO DRB will be further described below, including the following steps:

[0086] Step S70: Configure the Non-RT RIC under the SMO device to transmit the local diversion strategy including the first location and the second location to the Near-RT RIC. As previously mentioned, depending on the needs of the URLLC service, the first location can be the first TEID of the first UE10, and the second location can be set according to the target of the URLLC service, for example, it can be the second TEID of the second UE11, or it can be the IP address of the MEC device 17, and the local diversion strategy can plan a local diversion path from the first location to the second location.

[0087] In response to receiving the local offload policy, proceed to step S71: configure the Near-RT RIC to execute the F1-LBO routing program to convert the local offload policy into E2 information and transmit it to the F1 local offload VNF module.

[0088] In response to receiving the E2 information, enter step S72: configure the F1 local diversion VNF module to detect the second TEID of the second UE11 or the IP address of the MEC device based on the E2 information, and detect the PDU session corresponding to the first location to obtain the first TEID of the first UE.

[0089] Step S73: Configure the F1 local diversion VNF module to establish a routing comparison table based on the detected second TEID or the IP address of the MEC device and the detected first TEID.

[0090] In the third embodiment, since the core network CN itself does not have the ability to establish an F1-LBO session, the present invention adopts the virtual network function of the Near-RT RIC that complies with the O-RAN architecture to configure the transmission rules of the F1 local diversion VNF module according to the local diversion strategy through the Near-RT RIC. Therefore, LBO DRB can be set for the URLLC service, and a routing comparison table for LBO DRB can be established.

[0091] [Beneficial Effects of Embodiments]

[0092] One of the beneficial effects of the present invention is that the URLLC-LBO method and system for NG-RAN provided by the present invention is suitable for the F1 interface between CU and DU, can support lower microsecond level application requirements, and comply with 3GPP NG-RAN and 5G core network (5GC) standards. Therefore, it can comply with the management interface standard of the Near Real-Time RAN Intelligent Controller (Near-RT RIC) of the Open Radio Access Network (O-RAN) Working Group 3 without modifying the original network equipment and user equipment (UE) to establish an F1-LBO shortcut, and can also maintain a mechanism for maintaining an uninterrupted UPF PDN session.

[0093] The contents disclosed above are only preferred feasible embodiments of the present invention, and are not intended to limit the scope of the claims of the present invention. Therefore, all equivalent technical changes made using the contents of the present invention description and drawings are included in the scope of the claims of the present invention.

Claims

1. A local offload method for ultra-reliable low-latency communication in a next-generation radio access network, the local offload method for ultra-reliable low-latency communication include: configuring a core network to establish a packet data unit session between a first user equipment and the core network, wherein the packet data unit session is via a radio unit, a first distribution unit and a central unit disposed between the first user equipment and the core network; configuring the first user equipment to establish a local ultra-reliable low-latency communication service; configuring a near real-time radio access network intelligent controller to establish an F1 local offload routing procedure to set up a local offload dedicated radio bearer for the local ultra-reliable low-latency communication service; configuring an F1 local offload virtual network function module with a transmission rule through the F1 local offload routing program, so as to establish a routing comparison table through the F1 local offload virtual network function module, wherein the routing comparison table defines a correspondence between a first position and a second position of a dedicated radio bearer, wherein the first position is a first tunnel endpoint identifier of the first user equipment, and the second position is a second tunnel endpoint identifier of a second user equipment or an Internet Protocol address of a multi-access edge computing device; and The F1 local offload virtual network function module is configured to establish an F1 local offload session between the first user device and the second user device according to the routing comparison table, or to establish the F1 local offload session between the first user device and a virtual central unit user layer executed by the multi-access edge computing device.

2. The local offloading method for ultra-reliable low-latency communication according to claim 1, wherein the local offloading method for ultra-reliable low-latency communication further comprises: include: An F1 gateway is configured to execute the F1 local traffic distribution virtual network function module, wherein the F1 gateway is respectively connected to the first distribution unit, the central unit and the multi-access edge computing device through multiple F1-C / U interfaces, and is connected to the near real-time radio access network intelligent controller through an E2 interface.

3. The local offload method for ultra-reliable low-latency communication as described in claim 2, wherein the F1 gateway is also connected to a second distribution unit via one of the F1-C / U interfaces, and in response to the second user device being connected to the second distribution unit, the F1 local offload virtual network function module establishes the F1 local offload session between the first user device and the second user device via the first distribution unit and the second distribution unit.

4. The local offloading method for ultra-reliable low-latency communication according to claim 2, wherein the local offloading method for ultra-reliable low-latency communication further comprises: include: In response to the F1 gateway executing the F1 local offload virtual network function module to establish the F1 local offload session, configuring the F1 gateway to transmit a keep-alive signal to the central unit through an F1-U interface; and In response to receiving the keep-alive signal, the central unit is configured to transmit the keep-alive signal to the core network to keep the PDU session connected.

5. The local offloading method for ultra-reliable low-latency communication according to claim 1, wherein the local offloading method for ultra-reliable low-latency communication further comprises: include: The first distribution unit is configured to execute the F1 local offload virtual network function module, wherein the first distribution unit is connected to the central unit and the multi-access edge computing device respectively through multiple F1-C / U interfaces, and is connected to the near real-time radio access network intelligent controller through an E2 interface.

6. The local offloading method for ultra-reliable low-latency communication according to claim 5, wherein the local offloading method for ultra-reliable low-latency communication further comprises: include: In response to the first distribution unit executing the F1 local offload virtual network function module to establish the F1 local offload session, configuring the first distribution unit to transmit a keep-alive signal to the central unit through an F1-U interface; and In response to receiving the keep-alive signal, the central unit is configured to transmit the keep-alive signal to the core network to keep the PDU session connected.

7. The local offloading method for ultra-reliable low-latency communication according to claim 1, wherein the local offloading method for ultra-reliable low-latency communication further comprises: include: A non-real-time radio access network intelligent controller under a service management and orchestration device of the core network is configured to transmit a local offload strategy including the first location and the second location to the near real-time radio access network intelligent controller; In response to receiving the local offload strategy, configuring the near real-time radio access network intelligent controller to execute the F1 local offload routing program to convert the local offload strategy into an E2 message and transmit it to the F1 local offload virtual network function module; In response to receiving the E2 message, configuring the F1 local offload virtual network function module to detect the second tunnel endpoint identifier of the second user equipment or the Internet Protocol address of the multi-access edge computing device according to the E2 message, and detecting the data packet data unit session corresponding to the first position to obtain the first tunnel endpoint identifier of the first user equipment; as well as The F1 local offload virtual network function module is configured to establish the routing comparison table according to the detected second tunnel endpoint identifier or the Internet Protocol address of the multi-access edge computing device and the detected first tunnel endpoint identifier.

8. A local offload system for ultra-reliable low-latency communication for next-generation radio access networks, the local offload system for ultra-reliable low-latency communication include: a first user equipment configured to establish a local ultra-reliable low-latency communication service; a core network configured to establish a data packet data unit session between the first user equipment and the core network; a radio unit connected between the first user equipment and the core network; a first distribution unit connected between the radio unit and the core network; a central unit connected between the first distribution unit and the core network; a near real-time radio access network intelligent controller configured to establish an F1 local offload routing procedure to set up a local offload dedicated radio bearer for the local ultra-reliable low-delay communication service; as well as an F1 local traffic distribution virtual network function module, the F1 local traffic distribution virtual network function module is connected between the first distribution unit and the central unit, wherein the F1 local offload routing program is executed to configure the F1 local offload virtual network function module with a transmission rule to establish a routing comparison table, wherein the routing comparison table defines a correspondence between a first position and a second position associated with a dedicated radio bearer, The first location is a first tunnel endpoint identifier of the first user equipment, and the second location is a second tunnel endpoint identifier of a second user equipment or an Internet Protocol address of a multi-access edge computing device; and The F1 local offload virtual network function module is also configured to establish an F1 local offload session for the local offload dedicated radio bearer between the first user equipment and the second user equipment according to the routing comparison table, or to establish the F1 local offload session between the first user equipment and a virtual central unit user layer executed by the multi-access edge computing device.

9. The local distribution system for ultra-reliable low-latency communication as claimed in claim 8, wherein the local distribution system for ultra-reliable low-latency communication further include: An F1 gateway, which is configured to execute the F1 local offload virtual network function module, wherein the F1 gateway is respectively connected to the first distribution unit, the central unit and the multi-access edge computing device through multiple F1-C / U interfaces, and is connected to the near real-time radio access network intelligent controller through an E2 interface.

10. The local offload system for ultra-reliable low-latency communication as described in claim 9, wherein the F1 gateway is also connected to a second distribution unit via one of the F1-C / U interfaces, and in response to the second user equipment being connected to the second distribution unit, the F1 local offload virtual network function module establishes the F1 local offload session between the first user equipment and the second user equipment via the first distribution unit and the second distribution unit.

11. The local offloading system for ultra-reliable low-latency communication as claimed in claim 10, in, In response to the F1 gateway being configured to execute the F1 local offload virtual network function module to establish the F1 local offload session, the F1 gateway is further configured to transmit a keep-alive signal to the central unit through an F1-U interface, In response to the central unit receiving the keep-alive signal, the central unit is configured to transmit the keep-alive signal to the core network to keep the data packet data unit session connected.

12. The local offload system for ultra-reliable low-latency communication as described in claim 8, wherein the first distribution unit is configured to execute the F1 local offload virtual network function module, and the first distribution unit is connected to the central unit and the multi-access edge computing device respectively through multiple F1-C / U interfaces, and is connected to the near real-time radio access network intelligent controller through an E2 interface.

13. The local offloading system for ultra-reliable low-latency communication as claimed in claim 12, in, In response to the first distribution unit being configured to execute the F1 local offload virtual network function module to establish the F1 local offload session, the first distribution unit is further configured to transmit a keep-alive signal to the central unit through an F1-U interface, In response to the central unit receiving the keep-alive signal, the central unit is configured to transmit the keep-alive signal to the core network to keep the data packet data unit session connected.

14. The local offload system for ultra-reliable low-latency communication as claimed in claim 8, wherein the core network comprises a service management and orchestration device configured to transmit a local offload strategy including the first location and the second location to the near real-time radio access network intelligent controller through a non-real-time radio access network intelligent controller, in, In response to receiving the local offload strategy, the near real-time radio access network intelligent controller is configured to execute the F1 local offload routing program to convert the local offload strategy into an E2 message and transmit it to the F1 local offload virtual network function module; In response to receiving the E2 message, the F1 local offload virtual network function module is configured to detect the second tunnel endpoint identifier of the second user equipment or the Internet Protocol address of the multi-access edge computing device according to the E2 message, and detect the data packet data unit session corresponding to the first position to obtain the first tunnel endpoint identifier of the first user equipment. The F1 local traffic distribution virtual network function module is also configured to establish the routing comparison table based on the detected second tunnel endpoint identifier or the Internet Protocol address of the multi-access edge computing device and the detected first tunnel endpoint identifier.