Private network data processing method and system, storage medium and electronic device

Abstract

The embodiment of the invention provides a private network data processing method and system, a storage medium and an electronic device.The method is applied to service unloading primary equipment and comprises the steps that running state detection of a primary link is started according to primary and standby deployment configuration, and the running state of the primary link is determined; determining a target transmission link according to the operation state, wherein the target transmission link is a main link or a standby link; and forwarding the uplink special data of the UE to the special network according to the target transmission link, and forwarding the downlink special data of the special network to the UE, thereby solving the problems of high complexity and high cost of networking by adopting a special UPF sinking scheme for the special network data and to-be-guaranteed service unloading reliability when other special network service unloading equipment is introduced in the related technology, and improving the service unloading reliability of the UE. A reliable transmission channel of data of an existing public network core network is inherited, the sinking deployment cost of the special core network is reduced, main and standby switching between the main link and the standby link is achieved, and high-reliability unloading and forwarding of the data of the special network are guaranteed.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to a private network data processing method, system, storage medium, and electronic device. Background Technology

[0002] Existing 5G toB private network applications employ either User Plane Function (UPF) offloading or dedicated MEC offloading of local network data. The dedicated UPF offloading solution has high network complexity and high investment and deployment costs for industrial field equipment. The dedicated multi-access edge computing (MEC) offloading solution does not forward uplink dedicated data from the base station to the UPF, but instead forwards it to a dedicated MEC connected in series at the N3 interface, and then offloads it to the local network. The base station-MEC interface specification is not within the scope of 3GPP or industry-wide unified standards, and each manufacturer uses its own custom protocol standards. This poses a risk of MEC downtime or related transmission interruptions, making it difficult to meet the high availability requirements of industrial application scenarios.

[0003] There is currently no solution to the problems of high complexity and cost in using dedicated UPF sinking schemes for private network data in related technologies, and the need to ensure the reliability of service offloading when introducing other private network service offloading equipment. Summary of the Invention

[0004] This application provides a private network data processing method, system, storage medium, and electronic device to at least solve the problems in related technologies where the use of a dedicated UPF sinking scheme for private network data is complex and costly, and the reliability of service offloading needs to be guaranteed when other private network service offloading equipment is introduced.

[0005] According to one embodiment of this application, a private network data processing system is provided. The system includes: a base station, a primary service offloading device, a backup service offloading device, and a network forwarding device. The network forwarding device is connected to the private network. The base station is connected to the primary service offloading device and the network forwarding device to form a primary link for service data forwarding. The base station is connected to the backup service offloading device and the network forwarding device to form a backup link for service data forwarding.

[0006] The service offloading primary device is used to initiate the operation status detection of the primary link according to the primary and backup deployment configuration, determine the operation status of the primary link, and determine the target transmission link according to the operation status, wherein the target transmission link is the primary link or the backup link; and forward the uplink dedicated data of the UE to the dedicated network according to the target transmission link, and forward the downlink dedicated data of the dedicated network to the UE.

[0007] According to another embodiment of this application, a private network data processing method is also provided, applied to a service offloading primary device, the method comprising:

[0008] The primary link's operational status is detected and determined according to the primary / backup deployment configuration. The primary link is formed by connecting the base station with the service offloading primary device and the network forwarding device.

[0009] The target transmission link is determined based on the operating status, wherein the target transmission link is the primary link or the backup link, and the backup link is formed by connecting the base station with the service offloading backup equipment and the network forwarding equipment;

[0010] According to the target transmission link, the uplink dedicated data of the UE is forwarded to the dedicated network, and the downlink dedicated data of the dedicated network is forwarded to the UE.

[0011] According to yet another embodiment of this application, a computer program product is also provided, including computer program instructions, wherein the computer program instructions cause a computer to implement the steps in any of the above method embodiments.

[0012] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.

[0013] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0014] The service offloading primary device in this embodiment starts the operation status detection of the primary link according to the primary / backup deployment configuration and determines the operation status of the primary link. The primary link is formed by connecting the base station with the service offloading primary device and the network forwarding device. The target transmission link is determined according to the operation status. The target transmission link is either the primary link or the backup link. The backup link is formed by connecting the base station with the service offloading backup device and the network forwarding device. The uplink dedicated data of the UE is forwarded to the dedicated network according to the target transmission link, and the downlink dedicated data of the dedicated network is forwarded to the UE. This can solve the problems of high complexity and high cost of using a dedicated UPF sinking scheme for dedicated network data in related technologies, and the problem of service offloading reliability not being guaranteed when introducing other dedicated network service offloading devices. It inherits the reliable transmission channel of the existing public core network data, reduces the deployment cost of dedicated core network sinking, and realizes the primary / backup switch between the primary link and the backup link, ensuring high reliability of dedicated network data offloading and forwarding. Attached Figure Description

[0015] Figure 1 This is a hardware structure block diagram of a computer device for a private network data processing method according to an embodiment of this application;

[0016] Figure 2 This is a flowchart of a private network data processing method according to an embodiment of this application;

[0017] Figure 3 This is a block diagram of a private network data processing system according to an embodiment of this application;

[0018] Figure 4 This is the architecture of a service offloading system for 5G MEC and UPF primary / backup deployment according to embodiments of this application. Figure 1 ;

[0019] Figure 5 This is the architecture of a service offloading system for 5G MEC and UPF primary / backup deployment according to embodiments of this application. Figure 2 ;

[0020] Figure 6 This is a flowchart of primary / standby switching according to an embodiment of this application;

[0021] Figure 7 This is a schematic diagram of the service port and local port linkage mapping network of a single service link and a single local link according to this embodiment;

[0022] Figure 8 This is a schematic diagram of the service port and local port linkage mapping network of the multi-service link and multi-local link according to this embodiment;

[0023] Figure 9This is a schematic diagram illustrating the bidirectional forwarding detection linked to general route encapsulation detection or static routing according to this embodiment;

[0024] Figure 10 This is a schematic diagram of MEC local port linkage service port linkage detection according to this embodiment;

[0025] Figure 11 This is a schematic diagram illustrating the MEC service port linkage local port linkage detection according to this embodiment;

[0026] Figure 12 This is a flowchart illustrating the linkage between the local port and service port of the MEC according to an embodiment of this application;

[0027] Figure 13 This is a flowchart of MEC initiating MEC-UPF link primary / backup failover according to an embodiment of this application. Detailed Implementation

[0028] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0030] The methods and embodiments provided in this application can be executed in a computer device or similar computing device. Taking running on a computer device as an example, Figure 1 This is a hardware structure block diagram of the computer device for the private network data processing method according to an embodiment of this application, such as... Figure 1 As shown, a computer device may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor (MCU) or programmable logic device, etc.) and a memory 104 for storing data are also shown. The computer device may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the computer device described above. For example, the computer device may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0031] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the private network data processing method in this embodiment. The processor 102 executes various functional applications and single-board matching by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to computer devices via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0032] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the computer equipment. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0033] This embodiment provides a private network data processing method running on the aforementioned computer equipment. Figure 2 This is a flowchart of a private network data processing method according to an embodiment of this application, such as... Figure 2 As shown, this process, applied to the primary device for business offloading, includes the following steps:

[0034] Step S202: Start the operation status detection of the primary link according to the primary and backup deployment configuration, and determine the operation status of the primary link. The primary link is formed by the connection between the base station and the service offloading primary equipment and network forwarding equipment.

[0035] In this embodiment, the operation status detection of the primary link can be based on a link state detection protocol. The link detection protocol is not limited to the Generic Routing Encapsulation (GRE) protocol and the Bidirectional Forwarding Detection (BFD) protocol.

[0036] Step S204: Determine the target transmission link based on the operating status. The target transmission link is either the primary link or the backup link. The backup link is formed by connecting the base station with the service offloading backup equipment and the network forwarding equipment.

[0037] In this embodiment of the application, step S204 may specifically include: when the primary link is running normally in the above-mentioned operating state, determining the target transmission link as the primary link; when the primary link is abnormal in the operating state, determining the target transmission link as the backup link.

[0038] Step S206: Forward the UE's uplink dedicated data to the dedicated network according to the target transmission link, and forward the dedicated downlink data of the dedicated network to the UE.

[0039] In this embodiment of the application, step S206 may specifically include:

[0040] S2061, If ​​the target transmission link is the primary link, it receives uplink private network data sent by the base station, sends the uplink private network data to the private network through the primary link, and receives downlink private data from the private network forwarded by the network forwarding device, and forwards the downlink private data to the UE through the base station.

[0041] S2062, if the target transmission link is a backup link, notify the base station to forward the uplink dedicated data to the private network through the backup link, and notify the network forwarding device to forward the downlink dedicated data to the UE through the backup link. Furthermore, if the status of the local interface on the primary link is abnormal, when a link control keep-alive request message is received from the base station, instruct the base station to forward the uplink dedicated data to the private network through the backup link. Specifically, this can be done by stopping sending link control keep-alive response messages to the base station or by actively sending a link control message with the link status field set to blocked to the base station. The local interface is the interface with the network forwarding device.

[0042] S2063, In the event of an abnormal status of the service port, the network forwarding device is notified to forward downlink dedicated data to the UE through the backup link. Specifically, this can be done by: stopping the sending of link control keep-alive messages to the network forwarding device or by actively sending a link control message with the link status field set to blocked to the network forwarding device. Here, the service port is the interface with the base station, and the local port is the interface with the network forwarding device.

[0043] In this embodiment, the primary service offloading device is deployed in the dedicated network transmission link as the primary link's service offloading device, forming a primary and backup dedicated network transmission link with other service offloading devices.

[0044] Through the above steps S202 to S206, the high complexity and cost of using a dedicated UPF sinking scheme for private network data in related technologies can be solved, as well as the problem of unreliability of service offloading when introducing other private network service offloading equipment. It inherits the reliable transmission channel of existing public core network data, reduces the deployment cost of dedicated core network sinking, and realizes the primary and backup switching between the primary and backup links, ensuring high reliability of private network data offloading and forwarding.

[0045] In one embodiment, the status of the service port and the local port on the primary link can also be determined, thereby determining whether the status of the primary link is normal or abnormal. Specifically, this may include:

[0046] S11, detect whether the status of the service port on the primary link is abnormal. The service port is the interface with the base station. Further, if the transmission link with the base station fails, or the service port actively disconnects the transmission link due to a local port failure, or the service port actively disconnects the transmission link due to a failure of other service ports, determine that the status of the service port on the primary link is abnormal; if the transmission link with the base station is restored, or the local port failure is restored, or the failure of other service ports is restored, determine that the status of the service port on the primary link has returned to normal.

[0047] S12, detect whether the status of the local port on the primary link is abnormal. This local port is the interface with the network forwarding device. Further, if the transmission link with the network forwarding device is interrupted, the local port disconnects the transmission link due to a service port failure, or the local port disconnects the transmission link due to another local port failure, determine that the status of the local port on the primary link is abnormal; if the transmission link with the network forwarding device is restored, the service port failure is resolved, or the other local port failure is resolved, determine that the status of the local port on the primary link returns to normal.

[0048] S13: If the status of the service port or local port on the primary link is abnormal, determine that the primary link is abnormal; if the status of the service port and local port on the primary link is normal, determine that the primary link is normal or has recovered to normal.

[0049] In this embodiment, the primary service offloading device can be a MEC or a dedicated MEC, and the backup service offloading device can be a UPF. The MEC and UPF are deployed in a primary and backup configuration and work together to offload services, fully utilizing two transmission links to achieve primary and backup deployment. The MEC is deployed in the base station equipment room, making deployment simple and providing high service offloading capabilities. The UPF offers high transmission reliability and saves the cost of deploying a dedicated UPF. Using the MEC as an independent detection and decision-making device for primary / backup failover allows it to be used with general-purpose UPFs and switches, eliminating the need for primary / backup failover functionality support from the UPF and switches. The primary / backup failover latency is within seconds, meeting the requirements for high network availability.

[0050] In one embodiment, the method can further establish a linkage relationship between the service port and the local port, and link the service port and the local port, or link the state changes of the service port and other service ports, and link the state changes of the local port and the service port, or the local port and other local ports, specifically including:

[0051] S21, Generate the linkage relationship between the service port and the local port on the primary link; if the service offloading primary device is connected to a service port belonging to multiple base stations to a single local port, the linkage relationship includes the linkage relationship between the service port on the primary link and other service ports; if the service offloading primary device is connected to a local port belonging to multiple local networks to a single service port, the linkage relationship includes the linkage relationship between the local port on the primary link and other local ports, where the service port is the interface with the base station and the local port is the interface with the network forwarding device.

[0052] S22, based on the linkage relationship, link the status change of the service port to the status change of the local port or other service ports. Further, obtain the link status between the service port and the local port, determine whether the link status no longer changes. If the determination result is yes, update the link status between the service port and the local port; if the determination result is no, obtain the current link status between the service port and the local port, and sequentially link the link status of the local port to the link status of the service port until the link status between the service port and the local port no longer changes.

[0053] S23, link the status change of the local port to the status change of the service port or other local ports, wherein the port transmission interruption is linked to the port being blocked, and the port transmission recovery is linked to the port being unblocked.

[0054] This application embodiment can be applied to industrial applications. In high-reliability industrial application scenarios of 5G toB private networks, the network forwarding device can be a switch or a UPF. A dedicated MEC is deployed on the base station chassis or a separate chassis in the industrial field. The base station is dual-connected to both the dedicated MEC and the UPF. Simultaneously, the campus Packet Data Network (PDN) server is dual-connected to both the dedicated MEC and the UPF through primary and backup switches. The UPF in the MEC+UPF primary / backup deployment can be a public network UPF, connected to the primary and backup switches via a transmission network. In industrial parks such as power grids, large ports, mines, and steel smelting plants, private network UPFs can be configured. Therefore, the UPF in the MEC+UPF primary / backup deployment can also be a private network UPF, connected to the primary and backup switches. The N3 port between the base station and the UPF is connected in series with the dedicated MEC device. Uplink data from the base station can be sent to the UPF or the dedicated MEC. Uplink private network data is offloaded to the local PDN server via the MEC or UPF, while downlink data from the campus PDN server is forwarded to the base station via the MEC or UPF. When the MEC equipment and transmission connection are normal, user uplink data (i.e., the UE's dedicated uplink data mentioned above) is forwarded by the base station to the dedicated MEC and offloaded to the local PDN server. Downlink data sent from the local PDN server to the user (i.e., the downlink private network data mentioned above) is forwarded by the MEC to the base station via the primary route at the switch. In scenarios where the MEC equipment and transmission connection fail, user uplink data is forwarded by the base station to the UPF and offloaded to the local PDN server. Downlink data sent from the local PDN server to the user is forwarded by the UPF to the base station via the backup route at the switch.

[0055] In high-reliability industrial applications, the wireless side implements dual-bearer, dual-channel protection, thus providing high-reliability service transmission and forwarding guarantees simultaneously on both the core network and the wired side. The base station and the campus PDN server connect to the MEC and UPF via dual connectivity. The MEC serves as the primary link, providing low forwarding latency, while the UPF serves as the backup link, providing reliable backup forwarding guarantees. The MEC independently detects and decides on failover, while the base station, switches, and UPF collaborate to control the primary / backup failover latency to within seconds in the event of a fault. This invention proposes a networking scheme with dedicated MEC and core network primary / backup deployment, leveraging the convenience of dedicated MEC deployment and its high-performance service offloading capabilities. Depending on the campus size and service reliability requirements, a dedicated core network or a public core network can be flexibly selected. When using the existing public core network as a backup link, it inherits the reliable data transmission channel of the existing public core network, reducing the deployment cost of the dedicated core network. Simultaneously, primary / backup functionality between different systems can be achieved without signaling interaction between the dedicated MEC and UPF.

[0056] This application also provides a private network data processing system. Figure 3This is a block diagram of a private network data processing system according to an embodiment of this application, such as... Figure 3 As shown, the system includes: a base station, a primary service offloading device, a backup service offloading device, and a network forwarding device. The network forwarding device is connected to a private network. The base station is connected to the primary service offloading device and the network forwarding device to form a primary link for service data forwarding. The base station is connected to the backup service offloading device and the network forwarding device to form a backup link for service data forwarding.

[0057] The service offloads the primary device to initiate the operation status detection of the primary link according to the primary and backup deployment configuration, determine the operation status of the primary link, and determine the target transmission link based on the operation status. The target transmission link is either the primary link or the backup link. Based on the target transmission link, the uplink dedicated data of the UE is forwarded to the dedicated network, and the downlink dedicated data of the dedicated network is forwarded to the UE.

[0058] The primary service offloading device, also known as the private network service offloading device, identifies services, provides network communication and computing resources, and offloads services to the local network. The primary service offloading device can be an MEC, a NodeEngine, or other service offloading devices. This application uses a dedicated MEC, or simply MEC, as an example for illustration. The dedicated MEC serves as the primary link forwarding device for UE access to the campus server, connected in series between the base station and the UPF N3 port, and simultaneously connected to the primary and backup switches. When the MEC primary link is active, UE uplink data can access the local PDN server through the base station-MEC-primary / backup switch; downlink data from the PDN server is sent to the UE through the primary / backup switch-MEC-base station. The dedicated MEC establishes a linkage relationship between the base station-side service port link and the local network-side local port link, and periodically detects the status of the linked network nodes. By blocking / unblocking the linked link nodes, it achieves synchronous switching of uplink and downlink services to the UPF backup link or back to the MEC primary link.

[0059] Service offloading backup equipment, also known as private network service offloading backup equipment, performs service identification, provides network communication resources, and offloads services to the local network. Specifically, it can be a UPF (User-Defined Network). Taking a UPF as an example, the UPF acts as a backup link forwarding device for UEs accessing the campus server. It connects to the base station on port N3 and to the PDN server via the primary / backup switch on port N6, and publishes routing information to the primary / backup switch. The UPF can be a private network UPF within the campus or a public network UPF. When the UPF backup link is activated, the UPF receives uplink data from the base station and forwards it to the local PDN server via the primary / backup switch; downlink data from the PDN server is sent to the UE via the primary / backup switch-UPF-base station.

[0060] In one embodiment, the service offloading primary device is further configured to determine the target transmission link as the primary link when the primary link is in normal or has recovered to normal operation; and to determine the target transmission link as the backup link when the primary link is in abnormal operation.

[0061] In one embodiment, the service offloading primary device is further configured to detect whether the status of the service port on the primary link is abnormal, wherein the service port is the interface between the service offloading primary device and the base station; detect whether the status of the local port on the primary link is abnormal, wherein the local port is the interface between the service offloading primary device and the network forwarding device; if the status of the service port or the local port on the primary link is abnormal, determine that the primary link is abnormal; if the status of the service port and the local port on the primary link is normal, determine that the primary link is normal or has recovered to normal.

[0062] In one embodiment, the service offloading primary device is further configured to: determine that the state of the service port on the primary link is abnormal in the event of a transmission link failure with the base station, a service port actively disconnecting the transmission link due to a local port failure, or a service port actively disconnecting the transmission link due to another service port failure; determine that the state of the service port on the primary link returns to normal in the event of a transmission link failure with the base station being resolved, a local port failure being resolved, or another service port failure being resolved; determine that the state of the local port on the primary link is abnormal in the event of a transmission link interruption with the network forwarding device, a local port disconnecting the transmission link due to a service port failure, or a local port disconnecting the transmission link due to another local port failure; and determine that the state of the local port on the primary link returns to normal in the event of a transmission link interruption being resolved with the network forwarding device being resolved, a service port failure being resolved, or another local port failure being resolved.

[0063] In one embodiment, the service offloading primary device is further configured to generate port linkage relationships between service ports and local ports at both ends of a primary link; when a service port belonging to multiple base stations is connected to one local port, port linkage relationships between service ports and other service ports on the primary link are generated; when a service port belonging to multiple private networks is connected to one service port, port linkage relationships between local ports and other local ports on the primary link are generated; based on the linkage relationships, the state changes of the service port are linked to the state changes of the local port or other service ports, and the state changes of the local port are linked to the state changes of the service port and other local ports, wherein, port transmission interruption linkage is associated with port blocking, and port transmission recovery linkage is associated with port deblocking; the linkage relationship between service ports and local ports on the primary link is generated, wherein the service port is the interface between the service offloading primary device and the base station, and the local port is the interface between the service offloading primary device and the network forwarding device; based on the linkage relationships, the state changes of the service port are linked to the state changes of the local port, and the state changes of the local port are linked to the state changes of the service port.

[0064] In one embodiment, the base station is configured to: if the target transmission link is the primary link, confirm that the target link is the primary link based on the link status of the service offloading primary device, send uplink private network data to the service offloading primary device, and forward downlink private network data forwarded by the service offloading primary device to the UE; if the target transmission link is a backup link, confirm that the target link is a backup link based on the link status of the service offloading primary device, forward uplink private network data to the service offloading backup device, and forward downlink private network data forwarded by the service offloading backup device to the UE.

[0065] The service offload function is used to indicate whether the target transmission link is the primary or backup link by confirming the link status. Specifically, it instructs the base station and network forwarding equipment to know whether the current target transmission link is the primary or backup link. If the target transmission link is the primary link, the uplink private network data forwarded by the base station is forwarded to the network forwarding equipment, and the downlink dedicated data forwarded by the network forwarding equipment is forwarded to the base station. If the target transmission link is the backup link, the base station is instructed to forward the uplink dedicated data to the private network through the backup link, and the network forwarding equipment is instructed to forward the downlink dedicated data to the UE through the backup link.

[0066] The service offloading backup equipment is used to forward uplink dedicated data forwarded by the base station to the network forwarding equipment and downlink dedicated data forwarded by the network forwarding equipment to the base station if the target transmission link is a backup link.

[0067] The network forwarding device is used to: if the target transmission link is the primary link, confirm that the target link is the primary link based on the link status of the service offloading primary device, forward the uplink private network data forwarded by the service offloading primary device to the private network, and forward the downlink private network data to the service offloading primary device; if the target transmission link is a backup link, forward the uplink private network data forwarded by the base station to the service offloading backup device, and confirm that the target link is a backup link based on the link status of the service offloading primary device, forward the downlink private network data to the service offloading backup device.

[0068] The base station connects the MEC and UPF using a dual-connectivity approach, as does the campus PDN. The dedicated MEC serves as the primary service offloading device, performing service identification, resource calculation, and local service offloading. The public or private network UPF serves as the backup service offloading device, providing a backup forwarding channel for service identification and offloading. The MEC achieves node-to-node linkage between the base station-MEC service interface and the MEC-campus PDN local interface. This ensures that when the MEC primary link fails, the UPF backup link is activated. When the MEC primary link recovers, services carried on the UPF backup link automatically switch back to the MEC primary link, while simultaneously ensuring synchronous switching of uplink and downlink data between the UE and the campus PDN between the primary and backup links.

[0069] The base station establishes dual connections with the dedicated MEC and UPF, and decides whether to forward uplink data from the UE to the primary MEC link or the backup UPF link. The base station periodically checks the link connection status with the MEC and UPF. If the base station-MEC link is normal, the uplink data decision is to use the primary MEC link: encapsulating the UE's private network slice data in a tunnel and forwarding it to the MEC. If the base station-MEC link is abnormal, the uplink data decision is to use the backup UPF link: sending the UE's private network slice data to the UPF. In the downlink direction, the base station receives data from either the primary MEC link or the backup UPF link and forwards it to the UE.

[0070] Specifically, the network forwarding equipment can be a primary or backup switch. The campus PDN server is dual-connected to the MEC and UPF through the primary and backup switches. The primary and backup switches are configured with transmission protocols to detect the link status with the MEC or UPF, deciding whether to forward downlink data from the PDN server to the primary link of the MEC or the backup link of the UPF. The primary and backup switches periodically check the link connection status with the MEC and UPF, and perform switching between the primary link of the MEC and the backup link of the UPF based on routing status and priority. If the primary / backup switch-MEC link is normal, downlink data will use the primary link of the MEC: forwarding data from the campus PDN server to the MEC; if the base station-MEC link is abnormal, downlink data will use the backup link of the UPF: sending data from the campus PDN server to the UPF. In the uplink direction, the primary and backup switches receive data from the primary link of the MEC or the backup link of the UPF and forward it to the campus PDN server.

[0071] In one embodiment, the service offloading primary device is further configured to, when the status of the local interface on the primary link is abnormal, stop sending a link control keep-alive response message to the base station or indicate blockage through the status bit field of the protocol message upon receiving a link control keep-alive request message sent by the base station, wherein the local interface is the interface between the service offloading primary device and the network forwarding device; and when the status of the service interface is abnormal, stop sending a link control keep-alive message to the network forwarding device or indicate blockage through the status bit field of the protocol message, wherein the service interface is the interface between the service offloading primary device and the base station, and the local interface is the interface between the service offloading primary device and the network forwarding device;

[0072] The base station is also used to forward uplink dedicated data to the dedicated network via a backup link when it does not receive a link control keep-alive response message or receives a protocol message with the status bit set to block.

[0073] The network forwarding device is also used to forward downlink dedicated data to the UE via a backup link when no link control keep-alive message is received or the status bit of the received protocol message is blocked.

[0074] In one embodiment, the base station is further configured to initiate operation status detection of the primary link and the backup link, select an uplink valid route based on the link status detection results, configure the priority of the primary link to be greater than the priority of the backup link, and forward uplink private network data based on the uplink valid route;

[0075] The network forwarding device is also used to initiate primary link status detection and backup link status detection, select downlink valid routes based on the link status detection results, configure the priority of the primary link to be higher than the priority of the backup link, and forward downlink private network data based on the downlink valid routes.

[0076] In one embodiment, the base station is further configured to determine that the primary link is abnormal in the event of a transmission link failure between the primary service offloading device and the service offloading device, a service port actively disconnecting the transmission link due to a local port failure, or a service port actively disconnecting the transmission link due to other service ports; and to determine that the primary link has returned to normal in the event of a transmission link failure between the primary service offloading device and the service offloading device being resolved, a local port failure being resolved, or other service port failures being resolved; when the primary link is normal, the route of the primary link is selected as the uplink valid route; when the primary link is abnormal, the route of the backup link is selected as the uplink valid route; the service port is the interface between the primary service offloading device and the base station; and the local port is the interface between the primary service offloading device and the network forwarding device.

[0077] The network forwarding device is also used to determine that the primary link is abnormal in the event of a transmission link failure between the primary device for service offloading, a transmission link disconnection of the local port due to a service port failure, or a transmission link disconnection of the local port due to a failure of other local ports; and to determine that the primary link has returned to normal in the event of a transmission link failure between the primary device for service offloading, a service port failure, or a failure of other local ports; when the primary link is normal, the route of the primary link is selected as the effective downlink route; when the primary link is abnormal, the route of the backup link is selected as the effective downlink route.

[0078] The embodiments of this application are described in detail below with examples.

[0079] This application embodiment enables service offloading of 5G MEC and UPF primary / backup deployments. Specifically, on the link where mobile terminal toB users access the local server via service offloading, an additional set of inter-system service offloading equipment is deployed to offload private network services locally. The base station and the local server are both dual-connected to these two sets of service offloading equipment, and in real time, one of the links where the service offloading equipment is located is selected to forward uplink or downlink user data. Figure 4 This is the architecture of a service offloading system for 5G MEC and UPF primary / backup deployment according to embodiments of this application. Figure 1 ,like Figure 4 As shown, the UE accesses the campus server and transmits data streams through the primary link and the private network. Figure 5 This is the architecture of a service offloading system for 5G MEC and UPF primary / backup deployment according to embodiments of this application. Figure 2 ,like Figure 5 As shown, when a UE accesses the campus server, the primary link switches to the backup link, and data flow transmission between the UE and the private network is achieved through the backup link. The service offloading system for the 5G MEC and UPF primary / backup deployment includes:

[0080] The primary service offloading device identifies services, provides network communication and computing resources, and offloads services to the local network. The primary service offloading device for the private network can be an MEC, NodeEngine, or other service offloading devices. The MEC acts as the primary link forwarding device for UE access to the campus server, connected in series between the base station and the UPF N3 port. The MEC can be deployed in the base station chassis or a standalone chassis in the campus equipment room, connecting to the base station and UPF via fiber optic access transmission network. The MEC-base station interface is the service port; multiple service ports are formed when the MEC establishes communication links with multiple external base stations. The MEC also connects to multiple local PDN servers through primary and backup switches. The MEC-primary and backup switch interface is the local port; the MEC can establish multiple local ports with the primary and backup switches. Link detection protocols are configured on both the service port and the local port of the MEC.

[0081] When the primary link is active, UE uplink data can access the local PDN server via base station-MEC-primary / backup switch; downlink data from the PDN server is sent to the UE via primary / backup switch-MEC-base station. The dedicated MEC establishes a linkage relationship between the base station-side service port link and the local network-side local port link, and periodically detects the status of the linked network nodes. By blocking / unblocking the linked link nodes, uplink and downlink services are synchronously switched to the UPF backup link or switched back to the MEC primary link.

[0082] UPF (Service Offloading Backup Device): Performs service identification, provides network communication resources, and offloads services to the local network. As a backup link forwarding device for UE access to the campus server, the UPF connects to the base station via port N3 and to the PDN server via the primary / backup switch via port N6, publishing routing information to the primary / backup switch. The UPF can be a private network UPF within the campus or a public network UPF at the county / city level. When the UPF backup link is active, the UPF receives uplink data from the UE sent by the base station and forwards it to the local PDN server via the primary / backup switch; downlink data from the PDN server is sent to the UE via the primary / backup switch-UPF-base station.

[0083] Base Station: Establishes dual connections with the dedicated MEC and UPF, and decides whether to forward uplink data from the UE to the MEC primary link or the UPF backup link. The base station connects to the transmission network via fiber optic cable from the panel port and can be deployed in the same chassis or equipment room as the MEC. The base station connects to the MEC via an internal switching chip or the transmission network, and to the UPF via the transmission network. The base station periodically checks the link connection status with the MEC and UPF. If the base station-MEC link is normal, the uplink data decision is to use the MEC primary link: encapsulating the UE's private network slice data in a tunnel and forwarding it to the MEC; if the base station-MEC link is abnormal, the uplink data decision is to use the UPF backup link: sending the UE's private network slice data to the UPF. In the downlink direction, the base station receives data from the MEC primary link or the UPF backup link and forwards it to the UE.

[0084] Primary and Backup Switches: The campus PDN server connects to the MEC and UPF via primary and backup switches. The primary and backup switches are configured with transmission protocols to detect the link status with the MEC or UPF and decide whether to forward downlink data from the PDN server to the primary link of the MEC or the backup link of the UPF. For example... Figure 4 and Figure 5In this setup, the primary and backup switches connect to the MEC via Port1, the UPF via Port2, and the campus PDN server via Port3. Link detection protocols, routing, and forwarding decisions are configured on the primary and backup switches. The primary and backup switches periodically check the link connection status with the MEC and UPF, and perform switching between the primary MEC link and the backup UPF link based on routing status and priority. If the primary / backup switch-MEC link is normal, downlink data is routed via the primary MEC link: data from the campus PDN server is forwarded to the MEC. If the base station-MEC link is abnormal, downlink data is routed via the backup UPF link: data from the campus PDN server is sent to the UPF. In the uplink direction, the primary and backup switches receive data from either the primary MEC link or the backup UPF link and forward it to the campus PDN server.

[0085] like Figure 4 As shown, when the primary link in a MEC+UPF primary / backup deployment is activated, the communication link between the MEC and the base station is normal, the eth1 port connected to the local network is activated, and the link communication with the primary / backup switches is normal. Figure 5 As shown, uplink and downlink service data are forwarded from the backup link: At this time, the communication link between MEC and base station is disconnected, the eth1 link of MEC connecting to local network is deactivated, and UE accesses the campus PDN server through UPF-backup switch; downlink data from campus PDN server is forwarded to UPF-base station-UE through the backup switch.

[0086] The primary / backup link switching of the 5G MEC and UPF primary / backup service offloading system can specifically include: Based on the characteristics of 5G network slicing and the reliability requirements of campus network resource deployment, and according to the network slicing reliability networking requirements, a dedicated MEC is orchestrated to generate the linkage relationship between service ports and local ports, and link detection protocols are configured on both service ports and local ports. A peer-to-peer link detection protocol is configured on the interface between the base station and the MEC, along with uplink routing policies. A peer-to-peer link detection protocol is configured on the interface between the primary / backup switch and the MEC, along with downlink routing policies. The MEC periodically detects the link status of the service port and local port, and executes service linkage between the service port and local port to achieve real-time switching of the primary / backup links in the MEC and UPF primary / backup service offloading system. Figure 6 This is a flowchart of primary / standby switchover according to an embodiment of this application, such as... Figure 6 As shown, it includes the following steps:

[0087] Step S610: MEC generates a network linking service ports and local ports.

[0088] Based on the QoS level and reliability requirements of B2B industrial park services, wireless network slicing, base station transmission resources, and local network APP server transmission resources are planned to generate a service linkage network between the MEC's ​​service ports connecting to the base station and the local ports connecting to the park server. The service linkage mechanism of the service ports and local ports is explained as follows: Each linkage line on the MEC contains two ports, namely a service port and a local port. If the state of one port automatically affects the state change of the other port, it actually triggers the synchronization of the packet transmission and reception enable states of the two ports. Multiple service port and local port linkage lines on the MEC form a service linkage network.

[0089] Campus servers APP1 and APP2 have high reliability requirements and are dual-connected to both MEC and UPF. Services on private network slice A and private network slice B access campus servers APP1 and APP2 respectively. Campus server APP3 has low reliability requirements, is single-connected to MEC, and corresponds to other slice services. The IP address of the MEC service port eth0 is IP_MECB, and the IP address of the local port eth1 is IP_MECL. A tunnel is established between the base station and the MEC service port to transmit service data, such as a GRE tunnel. The base station service IP and IP_MECB are the outer IP address of the GRE tunnel. A BFD session is established between the MEC local port and the switch connected to the server APP. The interface IP addresses corresponding to the BFD session are IP_MECL and IP_APP.

[0090] Figure 7 This is a schematic diagram of the service port and local port linkage mapping network according to this embodiment of the single service link and single local link, as shown below. Figure 7 As shown, this primary / backup network configuration is relatively simple, with n base stations establishing n linkage relationships. The private network multi-slice services of each base station are carried on a single service IP address channel (IP_A), and the local interface multi-APP services are mapped to a single BFD session. This example uses three base stations to establish a service linkage network with three service interfaces (gNodeB1, gNodeB2, gNodeB3) and one local interface (APP1+APP2), with linkage relationships L1AB12, L2AB12, and L3AB12. Taking L1AB12 as an example, the letter "L" represents the linkage relationship, the number "1" represents gNodeB1, the letter "AB" represents slice A and slice B, and the number "12" represents APP1 and APP2.

[0091] Local port 12 on the MEC is associated with APP1 and APP2. The linkage relationships corresponding to local port 12 include L1AB12, L2AB12, and L3AB12. If the transmission link between the MEC and APP1 / APP2 fails, the MEC will block the service port links of slice A and slice B on gNodeB1, gNodeB2, and gNodeB3. Therefore, all service data will use the UPF backup channel.

[0092] The linkage relationship corresponding to service port 1 on the MEC is L1AB12. If the transmission link between the MEC and gNodeB1 fails, according to the linkage relationship (L1AB12), the MEC blocks local port link 12 of APP1 / APP2. According to the linkage relationships (L2AB12, L3AB12), the MEC continues to block service port links 2 and 3 of slice A and slice B on gNodeB2 and gNodeB3. Therefore, all service data goes through the UPF backup channel.

[0093] Figure 8 This is a schematic diagram of the service port and local port linkage mapping network of the multi-service link and multi-local link according to this embodiment, as shown below. Figure 8 As shown, the primary / backup deployment is relatively complex, but each slice is independent and does not affect others, resulting in higher reliability. n base stations and m independent applications establish n×m linkage relationships. The private network multi-slice services of the base stations are carried on two service IP addresses, IP_A and IP_B, and the local interface multi-APP services are mapped to two BFD sessions. This embodiment takes 3 base stations and 2 applications as an example. The service interface and local interface service linkage network establishes a total of 6 linkage relationships: L1A1, L2A1, L3A1, L1B2, L2B2, and L3B2. Taking L1A1 as an example, the letter "L" represents the linkage relationship (Linkage), the number "1" represents gNodeB1, the letter "A" represents slice A, and the number "1" represents APP1.

[0094] If the transmission link between MEC and APP1 fails, the impact on local port 1 only includes L1A1, L2A1, and L3A1. In this case, MEC will block service port link 1 of slice A on gNodeB1, gNodeB2, and gNodeB3. Service data of APP1 corresponding to slice A on gNodeB1, gNodeB2, and gNodeB3 will use the UPF backup channel, but service data of APP2 corresponding to slice B on gNodeB1, gNodeB2, and gNodeB3 will still use the MEC primary channel.

[0095] If the transmission link IP_A corresponding to slice A between MEC and gNodeB1 fails, the impact on local interface 1 only includes L1A1, L2A1, and L3A1. Therefore, MEC blocks local interface link 1 between gNodeB1 and APP1. Simultaneously, based on the linkage relationships L2A1 and L3A1, MEC blocks service interface links 2 and 3 of slice A on gNodeB2 and gNodeB3. Thus, service data for slice A on gNodeB1, gNodeB2, and gNodeB3 will use the UPF backup channel, but service data for slice B on gNodeB1, gNodeB2, and gNodeB3 will still use the MEC primary channel.

[0096] Step S620: Configure the link state detection protocol, uplink / downlink routing policy, and forwarding policy.

[0097] Link state detection protocols must be configured on the ports of the base station, MEC, and primary / backup switches. For dual connections between the base station and the MEC and UPF, routing and forwarding policies need to be configured.

[0098] Figure 9 This is a schematic diagram illustrating the linkage between BFD bidirectional forwarding detection and GRE general route encapsulation detection or static routing according to this embodiment, as shown below. Figure 9 As shown, the uplink link primary / backup switchover principle is as follows: Uplink data from the base station's N3 port to the UPF uses ordinary IP routing. A GRE link is configured between the base station and the MEC. Therefore, the base station needs to encapsulate the original N3 port data in a GRE tunnel before sending it to the MEC. The base station's GRE routing priority is configured to be higher than the IP routing priority. When the GRE link fails or the MEC actively disconnects the GRE link due to a local port failure, the uplink data is switched to the UPF backup link. When the GRE link or local port failure is resolved, both GRE and IP routes remain valid. However, because the GRE route has a higher priority, the primary / backup switch switches the uplink data back to the MEC's ​​primary link.

[0099] Downlink primary / backup switchover principle: A BFD session is configured between the switch and the MEC, and the BFD session is linked to static routes. The switch is configured with BGP and receives BGP route advertisements from the UPF. Simultaneously, a forwarding policy is configured on the switch: static routes have higher priority than BGP routes. The MEC configures a peer-to-peer BFD session on the switch side on its local port and implements BFD linked to the service port's GRE. When the transmission link corresponding to the BFD session on the MEC is interrupted, or when the MEC disconnects the BFD session on its local port due to a service port failure, downlink data is switched to the UPF backup link. When the transmission link corresponding to the BFD session on the MEC is restored, or when the MEC service port failure is resolved, because the MEC's ​​primary link has higher routing priority, the primary and backup switches switch the downlink data back to the MEC's ​​primary link.

[0100] Step S630: MEC initiates service port and local port link detection and status linkage.

[0101] Both the service port and the local port have two states: link state and management state. The link state reflects the transmission link status, while the management state is the link blocking (admin down) and link unblocking (admin up) caused by linkage.

[0102] MEC enables peer devices (base stations / primary / backup switches) to detect changes in link status by setting the management state of the local link on a linked link. The method is as follows: when the MEC's ​​uplink is set to admin down, the MEC will no longer respond to keep-alive response messages or actively send control request messages. When the MEC's ​​uplink is set to admin up, the MEC will resume responding to keep-alive response messages or can actively send control request messages.

[0103] MEC synchronizes the states of both ends of a linked link on its own device to achieve a change in the associated state of the local port and service port of a linked link, thereby triggering a synchronous switchover of the uplink and downlink of the services carried on this linked link. MEC traverses the port states of all linked links on the linked network to achieve primary / backup link switching for all services on the linked network. Service linkage execution process: The service port and local port of a linked link are labeled X or Y. Changes in the link state of X or Y require synchronous updates to the management state of all nodes on the entire linked network. The X link state of a linked link triggers a management state update of Y, and a change in the management state of Y triggers updates to the X port management state of other linked links associated with Y. Traversing the link states of all X links on the linked network completes the update of the management state of Y for the entire linked network.

[0104] Figure 10 This is a schematic diagram of MEC local port linkage service port linkage detection according to this embodiment, as shown below. Figure 10 As shown, the linkage sequence of the MEC local port to the service port is as follows: 1. Local port BFD link status change (link up <-> link down) -> 2. Execute BFD link linkage to GRE link status change (admin up <-> admin down) -> 3. Execute GRE link linkage to other BFD link status changes (admin up <-> admin down). Figure 11 This is a schematic diagram of the MEC service port linkage local port linkage detection according to this embodiment, as shown below. Figure 11As shown, the linkage sequence of MEC service port to local port is as follows: 1. Service port GRE link status change (link up <-> link down) -> 2. Execute GRE link linkage BFD link status change (admin up <-> admin down) -> 3. Execute BFD link linkage other GRE link status change (admin up <-> admin down).

[0105] Figure 12 This is a flowchart illustrating the linkage between the local port and service port of the MEC according to an embodiment of this application, such as... Figure 12 As shown, the linkage process between the MEC's ​​local port and service port includes the following steps:

[0106] Step S1200: After the business linkage cycle is over, MEC starts executing the business linkage between the local port and the business port.

[0107] Step S1201: The MEC initializes the link status and management status of all local ports and service ports, and obtains the current link status of the local ports and service ports. Specifically, they can all be initialized to link up and admin up.

[0108] In step S1202, the MEC monitors the link status and management status of the local port and service port to determine if they will no longer change. If the status changes, continue executing S1203, S1204, and S1205 until the status no longer changes. Finally, execute step S1206.

[0109] Step S1203: MEC reads the current local port and service port link status.

[0110] Step S1204: MEC performs a local port link status linkage management status traversal.

[0111] Step S1205: MEC performs a status traversal of the service port link status linkage management.

[0112] Step S1206: MEC updates the management status of local ports and service ports.

[0113] Specifically, step S1204 further includes: if the link status of local port i is down and its management status changes to down, and the management status of the service port j associated with local port i is up, then the management status of service port j is set to down. At the same time, all other local ports k associated with service port j are traversed, and if the link status of local port k is up, then the management status of local port k is set to down.

[0114] Specifically, step S1205 further includes: if the link status or management status of the service port j associated with local port i becomes down, and if the management status of local port i is up, then set the management status of local port i to down.

[0115] Step S640: MEC initiates MEC-UPF link primary / backup switchover.

[0116] Figure 13 This is a flowchart illustrating the MEC-UPF link primary / standby failover process according to an embodiment of this application, such as... Figure 13 As shown, it includes the following steps:

[0117] Step S1300: MEC starts the MEC-UPF link to perform primary / backup switchover.

[0118] In step S1301, after the detection cycle is over, the MEC reads the status of all service port GRE links and local port BFD links, and detects the link status and management status of each link.

[0119] In step S1302, the MEC detects whether the link status and management status of BFD or GRE are down. If so, proceed to step S1303, and then proceed to step S1404.

[0120] Step S1303: Uplink and downlink data are switched from the MEC primary link to the UPF backup link. The sub-steps of S1303 include:

[0121] S1303a, MEC stops sending BFD control messages to the peer switch; when MEC receives a GRE keep-alive request, it stops sending GRE keep-alive responses to the base station.

[0122] In the S1303b, after the primary and backup switches detect a BFD link failure, they switch the downlink to the backup UPF link.

[0123] S1303c: After the base station detects that the GRE link keep-alive has failed, it switches the uplink to the backup UPF link.

[0124] If MEC detects that both BFD and GRE links are updated to "up" in step S1302, then proceed to step S1304.

[0125] Step S1304, uplink and downlink data are switched back from the UPF backup link to the MEC primary link. S1304 may further include:

[0126] S1304a, the MEC resumes sending BFD control messages to the peer switch; when the MEC receives a GRE keep-alive request, it resumes sending a GRE keep-alive response to the base station.

[0127] S1304b: After the primary and backup switches detect and recover from a BFD link outage, they will switch the downlink to the primary MEC link.

[0128] S1304c: After the base station detects that the GRE link has been restored to keep-alive, it will switch the uplink to the primary MEC link.

[0129] In 5G MEC and UPF primary / backup deployment scenarios, when the primary / backup link switches over, the service interruption time can be controlled within seconds.

[0130] This application also provides a computer program product, including computer program instructions, wherein the computer program instructions cause a computer to implement the steps in any of the above method embodiments.

[0131] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0132] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0133] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0134] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0135] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0136] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0137] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A private network data processing method characterized by, The method is applied to a service offloading master device, and the method comprises: starting operation state detection of a master link according to a master / standby deployment configuration, and determining the operation state of the master link, wherein the master link is formed by connection of a base station, the service offloading master device, and a network forwarding device; determining a target transmission link according to the operation state, wherein the target transmission link is the master link or a standby link, and the standby link is formed by connection of the base station, a service offloading standby device, and the network forwarding device; forwarding uplink dedicated data of a user equipment (UE) to a dedicated network and forwarding downlink dedicated data of the dedicated network to the UE according to the target transmission link.

2. The method of claim 1, wherein, Determining a target transmission link according to the operation state comprises: in a case where the operation state is normal operation of the master link, determining that the target transmission link is the master link; in a case where the operation state is abnormality of the master link, determining that the target transmission link is the standby link.

3. The method of claim 2, wherein, The method further comprises: detecting whether a state of a service port on the master link is abnormal, wherein the service port is an interface with the base station; detecting whether a state of a local port on the master link is abnormal, wherein the local port is an interface with the network forwarding device; in a case where the state of the service port or the local port on the master link is abnormal, determining that the master link is abnormal, and in a case where the state of the service port and the local port on the master link is normal, determining that the master link is normal or recovers to normal.

4. The method of claim 3, wherein detecting whether a state of a service port on the master link is abnormal comprises: in a case where a transmission link between the base station is faulty, the service port is actively disconnected from the transmission link due to a fault of the local port, or the service port is actively disconnected from the transmission link due to a fault of another service port, determining that the state of the service port on the master link is abnormal; in a case where the transmission link between the base station is recovered from the fault, the local port is recovered from the fault, or the another service port is recovered from the fault, determining that the state of the service port on the master link recovers to normal; detecting whether a state of a local port on the master link is abnormal comprises: in a case where a transmission link between the network forwarding device is interrupted, the local port is disconnected from the transmission link due to a fault of the service port, or the local port is disconnected from the transmission link due to a fault of another local port, determining that the state of the local port on the master link is abnormal; in a case where the transmission link between the network forwarding device is recovered from the interruption, the service port is recovered from the fault, or the another local port is recovered from the fault, determining that the state of the local port on the master link recovers to normal.

5. The method of claim 1, wherein, Forwarding uplink dedicated data of a UE to a dedicated network and forwarding downlink dedicated data of the dedicated network to the UE according to the target transmission link comprises: if the target transmission link is the primary link, receiving uplink private network data sent by a base station, sending the uplink private network data to a private network through the primary link, and receiving downlink private network data forwarded by the network forwarding device, and forwarding the downlink private network data to the UE through the base station; if the target transmission link is the backup link, notifying the base station to forward the uplink private network data to the private network through the backup link, and notifying the network forwarding device to forward the downlink private network data to the UE through the backup link.

6. The method of claim 5, wherein, notifying the base station to forward the uplink private network data to the private network through the backup link; notifying the network forwarding device to forward the downlink private network data to the UE through the backup link includes: in the case of abnormal state of a local port on the primary link, when a link control keep-alive request packet sent by the base station is received, the base station is instructed to forward the uplink private network data to the private network through the backup link by stopping sending a link control keep-alive response packet to the base station or actively sending a link control packet carrying a link state field of occlusion to the base station, wherein the local port is an interface with the network forwarding device; in the case of abnormal state of a service port, the network forwarding device is notified to forward the downlink private network data to the UE through the backup link by stopping sending a link control keep-alive packet to the network forwarding device or actively sending a link control packet carrying a link state field of occlusion to the network forwarding device, wherein the service port is an interface with the base station, and the local port is an interface with the network forwarding device.

7. The method of claim 1, wherein, The method further includes: generating a linkage relationship between a service port and a local port on the primary link; if the service offloading primary device is connected to one local port through the service port belonging to multiple base stations, the linkage relationship includes a linkage relationship between the service port and other service ports on the primary link; if the service offloading primary device is connected to one service port through the local port belonging to multiple local networks, the linkage relationship includes a linkage relationship between the local port and other local ports on the primary link, wherein the service port is an interface with the base station, and the local port is an interface with the network forwarding device; according to the linkage relationship, the state change of the service port is linked to the state change of the local port or the other service ports, and the state change of the local port is linked to the state change of the service port or the other local ports, wherein the transmission interruption of the port is linked to the occlusion of the port, and the transmission recovery of the port is linked to the un-occlusion of the port.

8. The method of claim 7, wherein, According to the linkage relationship, the state change of the service port is linked to the state change of the local port includes: obtaining the link state of the service port and the local port; determining whether the link state of the link no longer changes; in the case of yes, updating the link state of the service port and the local port; If the determination result is negative, the current link state of the service port and the local port is acquired, and the link state of the local port is sequentially linked to the link state of the service port until the link state of the service port and the local port no longer changes.

9. A private network data processing system, characterized by The system comprises a base station, a service offloading primary device, a service offloading backup device, and a network forwarding device, wherein the network forwarding device is connected with a private network, the base station is connected with the service offloading primary device and the network forwarding device to form a primary link for service data forwarding, and the base station is connected with the service offloading backup device and the network forwarding device to form a backup link for service data forwarding. The service offloading primary device is configured to start operation state detection of the primary link according to a primary / backup deployment configuration, determine an operation state of the primary link, determine a target transmission link according to the operation state, wherein the target transmission link is the primary link or the backup link, forward uplink private data of a user equipment (UE) to the private network according to the target transmission link, and forward downlink private data of the private network to the UE.

10. The system of claim 9, wherein The service offloading primary device is further configured to determine that the target transmission link is the primary link when the operation state is normal or recovered, and determine that the target transmission link is the backup link when the operation state is abnormal.

11. The system of claim 10, wherein The service offloading primary device is further configured to detect whether a state of a service port on the primary link is abnormal, wherein the service port is an interface between the service offloading primary device and the base station, detect whether a state of a local port on the primary link is abnormal, wherein the local port is an interface between the service offloading primary device and the network forwarding device, determine that the primary link is abnormal when the state of the service port or the local port on the primary link is abnormal, and determine that the primary link is normal or recovered when the state of the service port and the local port on the primary link is normal.

12. The system of claim 11, wherein The service offloading primary device is further configured to determine that the state of the service port on the primary link is abnormal when a transmission link between the service offloading primary device and the base station is faulty, the transmission link is actively disconnected due to a fault of the local port, or the transmission link is actively disconnected due to a fault of another service port. In the case of transmission link fault recovery between the base station, the local port fault recovery or the other service port fault recovery, the state of the service port on the primary link is determined to be normal; in the case of transmission link interruption between the network forwarding device, the local port disconnection of the transmission link due to the service port fault linkage or the local port disconnection of the transmission link due to the other local port fault linkage, the state of the local port on the primary link is determined to be abnormal; in the case of transmission link interruption recovery between the network forwarding device, the service port fault recovery or the other local port fault recovery, the state of the local port on the primary link is determined to be normal.

13. The system of claim 12, wherein, The service offloading primary device is further configured to generate a port linkage relationship between the service port and the local port at both ends of the primary link; in the case of connection of the service port belonging to a plurality of base stations to one local port, generate a port linkage relationship between the service port and other service ports on the primary link; in the case of connection of the local port belonging to a plurality of private networks to one service port, generate a port linkage relationship between the local port and other local ports on the primary link; according to the linkage relationship, link the state change of the service port to the state change of the local port or other service ports, and link the state change of the local port to the state change of the service port and other local ports, wherein the linkage associated port in the case of port transmission interruption is port blocking, and the linkage associated port in the case of port transmission recovery is port unblocking; generate a linkage relationship between the service port and the local port on the primary link, wherein the service port is the interface of the service offloading primary device and the base station, and the local port is the interface of the service offloading primary device and the network forwarding device; according to the linkage relationship, link the state change of the service port to the state change of the local port, and link the state change of the local port to the state change of the service port.

14. The system of claim 9, wherein, The base station is configured to, if the target transmission link is the primary link, confirm the target link as the primary link according to the link state of the service offloading primary device, send the uplink private network data to the service offloading primary device, and forward the downlink private network data forwarded by the service offloading primary device to the UE; if the target transmission link is the backup link, confirm the target link as the backup link according to the link state of the service offloading primary device, forward the uplink private network data to the service offloading backup device, and forward the downlink private network data forwarded by the service offloading backup device to the UE. The service offloading primary device is further configured to instruct the base station and the network forwarding device that the target transmission link is the primary link or the backup link through link state confirmation respectively; if the target transmission link is the primary link, forward the uplink private network data forwarded by the base station to the network forwarding device, and forward the downlink private network data forwarded by the network forwarding device to the base station; if the target transmission link is the backup link, instruct the base station to forward the uplink private network data to the private network through the backup link; instruct the network forwarding device to forward the downlink private network data to the UE through the backup link; The service offloading backup device is configured to, if the target transmission link is the backup link, forward the uplink private network data forwarded by the base station to the network forwarding device, and forward the downlink private network data forwarded by the network forwarding device to the base station; The network forwarding device is configured to, if the target transmission link is the primary link, according to the link state confirmation of the service offloading primary device that the target link is the primary link, forward the uplink private network data forwarded by the service offloading primary device to the private network, and forward the downlink private network data to the service offloading primary device; if the target transmission link is the backup link, forward the uplink private network data forwarded by the base station to the service offloading backup device, and according to the link state confirmation of the service offloading primary device that the target link is the backup link, forward the downlink private network data to the service offloading backup device.

15. The system of claim 14, wherein The service offloading primary device is further configured to, in the case of abnormal state of a local interface between the service offloading primary device and the network forwarding device, stop sending a link control keep-alive response message to the base station or instructing occlusion through a protocol message state bit field when receiving a link control keep-alive request message sent by the base station, and in the case of abnormal state of a service interface between the service offloading primary device and the base station, stop sending a link control keep-alive message to the network forwarding device or instructing occlusion through a protocol message state bit field, wherein the local interface is the interface between the service offloading primary device and the network forwarding device, and the service interface is the interface between the service offloading primary device and the base station; The base station is further configured to, in the case of not receiving the link control keep-alive response message or receiving a protocol message state bit field indicating occlusion, forward the uplink private network data to the private network through the backup link; The network forwarding device is further configured to, in the case of not receiving the link control keep-alive message or receiving a protocol message state bit field indicating occlusion, forward the downlink private network data to the UE through the backup link.

16. The system of claim 9, wherein The base station is further configured to start the operation state detection of the primary link and the operation state detection of the backup link, select an uplink effective route according to the link state detection result, configure the priority of the primary link to be higher than the priority of the backup link, and forward the uplink private network data based on the uplink effective route. The network forwarding device is further configured to start the primary link state detection and the backup link state detection, select a downlink effective route according to the link state detection result, configure the priority of the primary link to be higher than the priority of the backup link, and forward the downlink private network data based on the downlink effective route.

17. The system of claim 16, wherein The base station is further configured to determine that the primary link is abnormal in a case that a transmission link between the base station and the service offloading primary device fails, the transmission link is actively disconnected due to a local port failure or the transmission link is actively disconnected due to another service port, and determine that the primary link is normal in a case that the transmission link between the base station and the service offloading primary device recovers, the local port recovers or the another service port recovers. The route of the primary link is selected as the uplink effective route when the primary link is normal, and the route of the backup link is selected as the uplink effective route when the primary link is abnormal, wherein the service port is an interface between the service offloading primary device and the base station, and the local port is an interface between the service offloading primary device and the network forwarding device. The network forwarding device is further configured to determine that the primary link is abnormal in a case that a transmission link between the network forwarding device and the service offloading primary device fails, the transmission link is actively disconnected due to a service port failure or the transmission link is actively disconnected due to another local port, and determine that the primary link is normal in a case that the transmission link between the network forwarding device and the service offloading primary device recovers, the service port recovers or the another local port recovers, and select the route of the primary link as the downlink effective route when the primary link is normal, and select the route of the backup link as the downlink effective route when the primary link is abnormal.

18. A computer readable storage medium, characterized in that, The storage medium has a computer program stored therein, and the computer program is configured to execute the method in any one of claims 1 to 8 when running.

19. An electronic device, comprising: The system comprises a memory and a processor, the memory has a computer program stored therein, and the processor is configured to execute the computer program to execute the method in any one of claims 1 to 8.

Images