Urban rail transit network cloud edge collaborative network architecture system

Abstract

The invention provides a cloud edge collaborative network architecture system of an urban rail transit network. The cloud edge collaborative network architecture system comprises at least one central station and a plurality of non-central stations. The central station comprises a transfer station, a line starting station and a line terminal station which are provided with edge cloud nodes, and is provided with a main cloud resource cluster, a first standby cloud resource cluster and a second standby cloud resource cluster. And the non-central station is not provided with the edge cloud node, is connected with the central station through the main link and the standby link, and is also provided with the main and standby cloud resource clusters. A network operation command center NOCC and a line operation control center OCC are deployed at a central station, and edge computing management center nodes are deployed at the NOCC and the OCC and are used for processing scheduling of network data traffic. According to the invention, in combination with the business characteristics of the urban rail transit industry, the networking mode of the communication line network and the latest development trend of the cloud-side cooperation technology, a network architecture scheme which is suitable for really realizing cloud-side cooperation in the urban rail transit line network so as to significantly improve the overall operation reliability is designed.

Description

Technical Field

[0001] The present invention relates to the field of urban rail transit technology, and in particular to an urban rail transit line network cloud-edge collaborative network architecture system, an electronic device and a readable storage medium. Background Art

[0002] In recent years, newly built urban rail transit lines at home and abroad have gradually introduced private cloud computing platforms to provide computing power and storage resources for various professional application systems of urban rail transit. However, how to layout the resource pool of the cloud platform to meet the high reliability and low response delay requirements of the urban rail transit industry for systems and equipment, and to achieve intensive use and management of resources, has always been a difficult problem.

[0003] Since some professional systems in the urban rail transit industry have high requirements for reliability and response delay, the industry currently generally adopts the method of deploying edge cloud nodes in all stations. Compared with the deployment method before the introduction of the cloud platform, this method has no obvious improvement effect in terms of intensive use of resources, intensive management and control, and reducing operating costs, and it is difficult to truly achieve cloud-edge collaboration (cloud-edge collaboration is a general term for various technologies that realize dynamic resource sharing between the central node and edge nodes of the cloud platform). Summary of the invention

[0004] In view of the above problems, the present invention is proposed to provide an urban rail transit network cloud-edge collaborative network architecture system, an electronic device and a readable storage medium that overcome the above problems or at least partially solve the above problems.

[0005] The present invention provides an urban rail transit network cloud-edge collaborative network architecture system, comprising:

[0006] At least one central station, which is a transfer station, a line starting station, and a line terminal station where edge cloud nodes are deployed, is configured with a primary cloud resource cluster, a first backup cloud resource cluster, and a second backup cloud resource cluster;

[0007] A plurality of non-central stations, which are stations where edge cloud nodes are not deployed, are connected to the central station via a primary link and a backup link, and are configured with a primary cloud resource cluster, a first backup cloud resource cluster, and a second backup cloud resource cluster;

[0008] The network operation command center NOCC and the line operation control center OCC are deployed at the central station and / or non-central station;

[0009] The edge computing management center node deploys the online network operation command center NOCC and the line operation control center OCC to handle network data traffic scheduling.

[0010] Optionally, the main link is composed of a trunk optical fiber line accompanying the urban rail transit line, and the backup link is composed of a bypassing series connection of the trunk optical fiber line.

[0011] Optionally,

[0012] The main cloud resource cluster of the non-central station is deployed on the edge cloud node of the central station which is closest to the non-central station network and closer to the line operation control center OCC;

[0013] The first backup cloud resource cluster of the non-central station is deployed on the edge cloud node of the central station in the opposite direction of the same line;

[0014] The second backup cloud resource cluster of the non-central station is deployed on the edge cloud node where the line operation control center OCC is located.

[0015] Optionally,

[0016] The main cloud resource cluster of the central station is deployed on the edge cloud node of the central station itself;

[0017] The first backup cloud resource cluster of the central station is deployed on an edge cloud node of the central station which is closest to the central station network and closer to the line operation control center OCC;

[0018] The second backup cloud resource cluster of the central station is deployed on the edge cloud node where the line operation control center OCC is located.

[0019] Optionally,

[0020] The backup cloud resource cluster at the station where the line operation control center OCC is located is deployed on the central node of the cloud platform where the online network operation command center NOCC is located;

[0021] The backup cloud resource cluster at the station where the NOCC is located is deployed on the active-active central node or backup central node of the cloud platform.

[0022] Optionally,

[0023] The edge computing management center nodes are deployed in two levels:

[0024] The primary node is responsible for the network data traffic scheduling between the secondary nodes;

[0025] The secondary node is responsible for the network data traffic scheduling between the central stations.

[0026] Optionally,

[0027] The primary cloud resource cluster, the first backup cloud resource cluster, and the second backup cloud resource cluster of each station are deployed in the same container cluster;

[0028] A DNS server is deployed at each station; the DNS server is controlled by an edge computing management center node deployed in the line operation control center OCC to realize the scheduling of network data traffic.

[0029] Optionally,

[0030] When the edge computing management center node deployed in the line operation control center OCC is available, the edge computing management center node deployed in the line operation control center OCC is used to monitor the operation status of each edge cloud node; when the primary edge cloud node where the primary cloud resource cluster is located is operating normally, the network data traffic from each station is directed to the primary edge cloud node; when the load of the primary edge cloud node exceeds the load threshold or partially fails, part or all of the network data traffic of the station is directed to the backup edge cloud node where the backup cloud resource cluster is located;

[0031] When the edge computing management center node deployed in the line operation control center OCC is unavailable, the main edge cloud node is used to maintain operation in an edge self-sustaining manner.

[0032] The present invention also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the electronic device executes the computer program, it loads the transportation line network cloud-edge collaborative network architecture system as described in any one of the embodiments of the present invention.

[0033] The present invention also provides a readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the transportation line network cloud-edge collaborative network architecture system as described in any one of the embodiments of the present invention is loaded.

[0034] The present invention includes the following advantages:

[0035] The transportation network cloud-edge collaborative network architecture system of the present invention includes at least one central station and multiple non-central stations. The central station is a transfer station, a line starting station, and a line terminal station where edge cloud nodes are deployed, and is configured with a primary cloud resource cluster, a first backup cloud resource cluster, and a second backup cloud resource cluster. The non-central station does not deploy edge cloud nodes, is connected to the central station through a primary link and a backup link, and is also configured with a primary and backup cloud resource cluster. The network operation command center NOCC and the line operation control center OCC are deployed at the central station and / or non-central station, and edge computing management center nodes are deployed at the network operation command center NOCC and the line operation control center OCC to be responsible for processing the scheduling of network data traffic. The present invention combines the business characteristics of the urban rail transit industry, the networking mode of the communication network, and the latest development trend of cloud-edge collaborative technology, and provides a network architecture solution suitable for truly realizing cloud-edge collaboration in the urban rail transit network, thereby significantly improving the overall operation reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 It is a structural block diagram of a cloud-edge collaborative network architecture system for an urban rail transit network provided by an embodiment of the present invention;

[0037] Figure 2 It is a schematic diagram of the site selection of the central station and the non-central station provided by the present invention;

[0038] Figure 3 It is a schematic diagram of the deployment method of two types of site cloud resource clusters provided in an embodiment of the present invention;

[0039] Figure 4 It is a schematic diagram of a high-availability link from each site to an edge cloud node provided by an embodiment of the present invention;

[0040] Figure 5 It is a schematic diagram of a two-level scheduling system for network data traffic provided by an embodiment of the present invention;

[0041] Figure 6 It is a schematic diagram provided by an embodiment of the present invention that describes the connection relationship, division of labor, and network data flow within the cloud among a station, active and standby edge cloud nodes, and an edge computing management center node of an OCC in a normal working mode;

[0042] Figure 7 It is a schematic diagram of the time required for a cloud platform to switch from a normal operation mode to a fault operation mode in the event of an edge application failure or a full edge failure provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0043] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0044] Reference Figure 1 , shows a structural block diagram of a cloud-edge collaborative network architecture system for an urban rail transit network provided in an embodiment of the present invention, which may specifically include the following modules:

[0045] At least one central station, which is a transfer station, a line starting station, and a line terminal station where edge cloud nodes are deployed, is configured with a primary cloud resource cluster, a first backup cloud resource cluster, and a second backup cloud resource cluster;

[0046] A plurality of non-central stations, which are stations where edge cloud nodes are not deployed, are connected to the central station via a primary link and a backup link, and are configured with a primary cloud resource cluster, a first backup cloud resource cluster, and a second backup cloud resource cluster;

[0047] The network operation command center (NOCC) and line operation control center (OCC) are deployed at the central station and / or non-central station;

[0048] The edge computing management center node is deployed in the online network operation command center (NOCC) and the line operation control center (OCC) to handle network data traffic scheduling.

[0049] The present invention designs a cloud-edge collaborative network architecture system suitable for urban rail transit networks. The core of the system lies in its efficient cloud resource deployment and scheduling strategy, aiming to improve the reliability and efficiency of the overall operation. Specifically, the system includes at least one central station and multiple non-central stations. Figure 2 The central station is a transfer station, a line starting station or a line terminal station where edge cloud nodes are deployed. These stations are selected as edge cloud node deployment points due to their important transportation node status, and multiple cloud resource clusters are configured to ensure high availability and reliability. Non-central stations do not deploy edge cloud nodes, but are connected to the central station through primary and backup links to ensure the stability and redundancy of data transmission.

[0050] Furthermore, the network operation command center (NOCC) and the line operation control center (OCC) can be deployed at the central station to make full use of their own network resources to improve the reliability of their network connections. Of course, based on physical space, land prices, power supply and other considerations, the network operation command center (NOCC) and the line operation control center (OCC) can also be deployed at other sites. At the same time, the edge computing management center nodes are deployed in the NOCC and OCC, which are responsible for handling the scheduling of network data traffic and optimizing the transmission and processing of data between the cloud and the edge. This design not only improves the response speed and reliability of the system, but also makes the overall resource allocation of the network cloud platform more convenient, flexible and intelligent.

[0051] The embodiments of the present invention realize the intensive deployment and high-availability configuration of cloud resources. By deploying edge cloud nodes only at transfer stations and line terminal stations, the utilization efficiency of information resources used by the station is greatly increased, the operation and maintenance costs of resources are greatly reduced, and the operation and maintenance efficiency is improved. At the same time, the configuration of multiple cloud resource clusters and the high-availability cloud platform supporting network topology further improve the overall reliability and security of the system. The design of the edge computing management center node enables the system to quickly respond to various emergencies and prioritize the continuous operation of key application systems, thereby ensuring the safe and stable operation of the line network.

[0052] In one embodiment of the present invention,

[0053] The main cloud resource cluster of the non-central station is deployed on the edge cloud node of the central station which is closest to the non-central station network and closer to the line operation control center (OCC);

[0054] The first backup cloud resource cluster of the non-central station is deployed on the edge cloud node of the central station in the opposite direction of the same line;

[0055] The second backup cloud resource cluster of the non-central station is deployed on the edge cloud node where the line operation control center (OCC) is located.

[0056] In one embodiment of the present invention,

[0057] The main cloud resource cluster of the central station is deployed on the edge cloud node of the central station itself;

[0058] The first backup cloud resource cluster of the central station is deployed on an edge cloud node of the central station that is closest to the central station network and closer to the line operation control center (OCC);

[0059] The second backup cloud resource cluster of the central station is deployed on the edge cloud node where the line operation control center (OCC) is located.

[0060] In one embodiment of the present invention,

[0061] The backup cloud resource cluster at the station where the line operation control center (OCC) is located is deployed on the central node of the cloud platform where the line network operation command center (NOCC) is located;

[0062] The backup cloud resource cluster at the station where the network operation command center (NOCC) is located is deployed on the active-active central node or backup central node of the cloud platform.

[0063] Reference Figure 3 , the main cloud resource cluster of the non-central station is deployed at the edge cloud node of the central station with the closest network distance and closer to the OCC, the (first) backup cloud resource cluster is deployed at the edge cloud node of the central station in the opposite direction of the same line (deployed in a hot standby manner, the same below), and the second backup cloud resource cluster is deployed at the edge cloud node where the OCC is located (deployed in a cold standby manner, the same below). The main cloud resource cluster of the central station is deployed at the edge cloud node of this station, the (first) backup cloud resource cluster is deployed at the edge cloud node with the closest network distance and closer to the OCC, and the second backup cloud resource cluster is also deployed at the edge cloud node where the OCC is located. The backup cluster of the site where the OCC is located is recommended to be deployed at the cloud platform central node where the NOCC is located, and the backup cluster of the site where the NOCC is located is recommended to be deployed at the active-active central node or backup central node of the cloud platform. Among them, the cloud platform central node, active-active central node or backup central node can be deployed at the central station, and can also be deployed at other sites based on physical space, land price, power supply and other considerations. By designing these cloud resources for each station, the high-availability deployment of cloud resources is fully realized, which can improve the overall availability of the computing and storage resources used by the station by at least one order of magnitude.

[0064] In one embodiment of the present invention,

[0065] The main link is composed of a trunk optical fiber line accompanying the urban rail transit line, and the backup link is composed of a bypass and series connection of the trunk optical fiber line.

[0066] In the embodiment of the present invention, refer to Figure 4 , the network connection method from each station to the edge cloud node: the trunk optical fiber line accompanying the urban rail transit line is used as the main link, and the interconnection and interoperability between the trunk optical fiber lines are realized at each transfer station (it is recommended to adopt a dual-link backup method to ensure its reliability), and a backup link is established between each station and the edge cloud node through the detour of the trunk optical fiber line. The remote central station of the line network should rent the line of the telecommunications operator to connect to the OCC, and use the external line as part of the backup link, so as to ensure that any station can be routed to the cloud node where its main and backup cloud resources are located through two independent networks, and fully realize the high-availability architecture of the cloud platform network layer. The network connection method from each station to the edge cloud node designed by the embodiment of the present invention realizes the high availability of the supporting network topology of the cloud platform, and can improve the availability of the network connection from the station to the cloud resource pools at all levels by at least one order of magnitude.

[0067] In one embodiment of the present invention,

[0068] The edge computing management center nodes are deployed in two levels:

[0069] The primary node is responsible for the network data traffic scheduling between the secondary nodes;

[0070] The secondary node is responsible for the network data traffic scheduling between the central stations.

[0071] In this embodiment, refer to Figure 5, deploy edge computing management center nodes in two levels in NOCC and OCC. The first-level node is responsible for the network data traffic scheduling between the second-level nodes, and the second-level node is responsible for the network data traffic scheduling between the central stations. In addition to accessing the edge cloud node (primary node) of its corresponding central station, each non-central station can also access the cloud resources of two backup edge cloud nodes (backup nodes). The non-central station can access its primary node and backup node through two independent lines, and the line resources used by the non-central station to access these nodes are also independent of each other. This high-availability design of the overall network, coupled with the resource backup of each central station by OCC and the resource backup of OCC by NOCC, enables NOCC and OCC to grasp the overall situation of the cloud platform network and conduct effective command and dispatch in various fault situations. Even in the extreme case where a serious fault occurs in part of the network, resulting in a serious shortage of network bandwidth, NOCC is still able to allocate the cloud resources of each node in real time to OCC according to the overall network load and the load of cloud nodes at all levels, giving priority to ensuring that key applications that need to synchronize data in the entire network, such as the dispatching command system, AFC, etc., can work normally, and overall improve the overall availability of cloud network resources by one to two orders of magnitude. By deploying edge computing management center nodes at two levels, namely NOCC and OCC, the overall resource allocation of the line network cloud platform is more convenient, flexible and intelligent. It can respond quickly to various emergencies, give priority to the continuous operation of key application systems, and ensure the safe and stable operation of the line network.

[0072] In one embodiment of the present invention,

[0073] The primary cloud resource cluster, the first backup cloud resource cluster, and the second backup cloud resource cluster of each station are deployed in the same container cluster;

[0074] A DNS server is deployed at each station; the DNS server is controlled by an edge computing management center node deployed in the line operation control center (OCC) to realize the scheduling of network data traffic.

[0075] In one embodiment of the present invention,

[0076] When the edge computing management center node deployed in the line operation control center (OCC) is available, the edge computing management center node deployed in the line operation control center (OCC) is used to monitor the operation status of each edge cloud node; when the primary edge cloud node where the primary cloud resource cluster is located is operating normally, the network data traffic from each station is directed to the primary edge cloud node; when the load of the primary edge cloud node exceeds the load threshold or partially fails, part or all of the network data traffic of the station is directed to the backup edge cloud node where the backup cloud resource cluster is located;

[0077] When the edge computing management center node deployed in the line operation control center (OCC) is unavailable, the primary edge cloud node is used to maintain operation in an edge self-sustaining manner.

[0078] The deployment method of the cloud platform central node and edge node can adopt various mainstream cloud computing technologies currently on the market, such as the open source OpenStack technology.

[0079] It is recommended to use containerization technology or Kubernetes container scheduling technology to deploy application loads in containers and realize flexible scheduling of cloud resources through container scheduling. In actual deployment, it is recommended to deploy the cloud resources used by each station in the same container cluster. Deploy a DNS server at each station, which is controlled by the edge computing management center node deployed in OCC to realize the scheduling of network data traffic.

[0080] Reference Figure 6 , describes the connection relationship and respective division of labor among the station, active edge cloud node, backup edge cloud node and OCC edge computing management center in normal working mode, as well as the data flow in the cloud network under normal circumstances.

[0081] Detailed description of the operation scenario:

[0082] The network connection from the station to the primary edge cloud node is normal, and the primary edge cloud node is working normally.

[0083] The network connection from the station to OCC is normal.

[0084] The network connection from the station to the backup edge cloud node is normal, and the backup edge cloud node is working properly.

[0085] Technical highlights of this scenario:

[0086] 1. Traffic from each station is directed to the primary edge cloud node.

[0087] OCC's edge computing management center monitors the operation of each edge cloud node and can import part or all of the station's traffic to a backup edge cloud node when necessary.

[0088] 2. Under normal circumstances, the container cluster of the primary edge cloud node will process all traffic data from the station. If the container clusters of the primary edge cloud node are overloaded, the access layer of the cloud edge node can divert part of the traffic to the client cluster of the backup edge cloud node.

[0089] 3. Each application service deployed on the primary edge cloud node writes business data to the database deployed locally. Each application service deployed on the backup edge cloud node also writes data to the database deployed on the primary edge cloud node.

[0090] 4. Various databases deployed on the active edge cloud node synchronize data to the database of the standby edge cloud node through a one-way data synchronization mechanism.

[0091] The second backup cloud resource cluster of each station is deployed in the OCC of the line to which the station belongs. Under normal circumstances, the database of this cluster synchronizes data from the database of the first backup edge cloud node. When the (first) backup cloud resource cluster of the station is unavailable, the edge computing management center of the OCC activates the second backup cloud resource cluster deployed in this OCC to provide backup cloud resources for the station. Its working mode is similar to Figure 6 When the (first) standby cloud resource cluster of the station is restored to an available state, the database of the second standby cloud resource cluster synchronizes its stored incremental data to the database in the (first) standby cloud resource cluster, and then switches back to the normal working mode.

[0092] When the edge computing management center of the OCC is unavailable, the primary edge cloud node deployed at the central station will maintain operation in an edge self-sustaining manner. When the primary edge cloud node of the central station partially fails, the traffic will be switched to the backup edge cloud node under the scheduling of the edge computing management center. Figure 7 The time required for the cloud platform to switch from normal operation mode to fault operation mode under these two types of fault conditions is shown. Figure 7 The reliability indicators shown in the figure are calculated with only one backup cluster. However, this solution actually designs a second (different-site) backup cluster, which can further increase the overall availability of the system by an order of magnitude.

[0093] If a network contains enough lines, and the redundancy of network connections is guaranteed, the number of edge cloud nodes can be further reduced. For example, the line terminal stations and transfer stations do not necessarily need to be set as central stations (that is, they are not necessarily edge cloud nodes).

[0094] Based on the same inventive concept, another embodiment of the present invention provides an electronic device, including a memory, a processor, and a computer program stored on the memory, wherein the processor executes the computer program to load the transportation line network cloud-edge collaborative network architecture system as described in any one of the embodiments of the present invention.

[0095] Specifically, the electronic device includes: a memory and a processor. The memory and the processor are connected via a bus communication. A computer program is stored in the memory. The computer program can be run on the processor, and then the transportation line network cloud-edge collaborative network architecture system described in any one of the first aspects of the embodiments of the present invention is loaded.

[0096] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0097] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0098] Based on the same inventive concept, another embodiment of the present invention provides a computer-readable storage medium on which a computer program / instruction is stored. When the computer program / instruction is executed by a processor, it loads the transportation line network cloud-edge collaborative network architecture system as described in any one of the first aspects of the embodiments of the present invention.

[0099] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0100] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, devices, electronic devices, storage media or computer program products. Therefore, embodiments of the present invention may take the form of complete hardware embodiments, complete software embodiments, or embodiments combining software and hardware. Moreover, embodiments of the present invention may take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CDROM, optical storage, etc.) containing computer-usable program codes.

[0101] Although the embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

[0102] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0103] The above is a detailed introduction to the cloud-edge collaborative network architecture system for an urban rail transit network provided by the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and its core idea of ​​the present application; at the same time, for those of ordinary skill in the art, according to the idea of ​​the present application, there will be changes in the specific implementation methods and scope of application. In summary, the content of this specification should not be understood as a limitation on the present application. The above embodiments are only preferred embodiments cited to fully illustrate the present invention, and the scope of protection of the present invention is not limited to this. Equivalent substitutions or changes made by those skilled in the art on the basis of the present invention are all within the scope of protection of the present invention.

Claims

1. A cloud-edge collaborative network architecture system for urban rail transit network, characterized in that: include: At least one central station, which is a transfer station, a line starting station, and a line terminal station where edge cloud nodes are deployed, is configured with a primary cloud resource cluster, a first backup cloud resource cluster, and a second backup cloud resource cluster; A plurality of non-central stations, which are stations where edge cloud nodes are not deployed, are connected to the central station via a primary link and a backup link, and are configured with a primary cloud resource cluster, a first backup cloud resource cluster, and a second backup cloud resource cluster; The network operation command center NOCC and the line operation control center OCC are deployed at the central station and / or non-central station; The edge computing management center node deploys the online network operation command center NOCC and the line operation control center OCC to handle network data traffic scheduling.

2. The urban rail transit network cloud-edge collaborative network architecture system according to claim 1 is characterized in that: The main link is composed of a trunk optical fiber line accompanying the urban rail transit line, and the backup link is composed of a bypass and series connection of the trunk optical fiber line.

3. The traffic line network cloud-edge collaborative network architecture system according to claim 1 is characterized in that: The main cloud resource cluster of the non-central station is deployed on the edge cloud node of the central station which is closest to the non-central station network and closer to the line operation control center OCC; The first backup cloud resource cluster of the non-central station is deployed on the edge cloud node of the central station in the opposite direction of the same line; The second backup cloud resource cluster of the non-central station is deployed on the edge cloud node where the line operation control center OCC is located.

4. The traffic line network cloud-edge collaborative network architecture system according to claim 1 is characterized in that: The main cloud resource cluster of the central station is deployed on the edge cloud node of the central station itself; The first backup cloud resource cluster of the central station is deployed on an edge cloud node of the central station which is closest to the central station network and closer to the line operation control center OCC; The second backup cloud resource cluster of the central station is deployed on the edge cloud node where the line operation control center OCC is located.

5. The traffic line network cloud-edge collaborative network architecture system according to claim 1 is characterized in that: The backup cloud resource cluster at the station where the line operation control center OCC is located is deployed on the central node of the cloud platform where the online network operation command center NOCC is located; The backup cloud resource cluster at the station where the NOCC is located is deployed on the active-active central node or backup central node of the cloud platform.

6. The traffic line network cloud-edge collaborative network architecture system according to claim 1 is characterized in that: The edge computing management center nodes are deployed in two levels: The primary node is responsible for the network data traffic scheduling between the secondary nodes; The secondary node is responsible for the network data traffic scheduling between the central stations.

7. The urban rail transit network cloud-edge collaborative network architecture system according to claim 1 is characterized in that: The primary cloud resource cluster, the first backup cloud resource cluster, and the second backup cloud resource cluster of each station are deployed in the same container cluster; A DNS server is deployed at each station; the DNS server is controlled by the edge computing management center node deployed in the line operation control center OCC to realize the scheduling of network data traffic.

8. The urban rail transit network cloud-edge collaborative network architecture system according to claim 1 is characterized in that: When the edge computing management center node deployed in the line operation control center OCC is available, the edge computing management center node deployed in the line operation control center OCC is used to monitor the operation status of each edge cloud node; when the primary edge cloud node where the primary cloud resource cluster is located operates normally, the network data traffic from each station is directed to the primary edge cloud node; When the load of the active edge cloud node exceeds the load threshold or partially fails, part or all of the station's network data traffic is directed to the standby edge cloud node where the standby cloud resource cluster is located; When the edge computing management center node deployed in the line operation control center OCC is unavailable, the main edge cloud node is used to maintain operation in an edge self-sustaining manner.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the electronic device executes the computer program, it loads the urban rail transit network cloud-edge collaborative network architecture system as described in any one of claims 1 to 8.

10. A readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by the processor, the urban rail transit network cloud-edge collaborative network architecture system as described in any one of claims 1 to 8 is loaded.

Images