A Visualization and Arrangement System and Method for Urban Rail Cloud Simulation Test Resources
By using a visual orchestration system and methodology, the problem of resource interconnection in rail transit cloud simulation testing was solved, enabling efficient scenario building and management, and improving the convenience and efficiency of simulation testing.
Patent Information
- Application Number
- CN202411628464.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-14
- Publication Date
- 2025-12-02
- Estimated Expiration
- 2044-11-14
AI Technical Summary
In the cloud simulation test of rail transit, traditional public cloud orchestration services lack compatibility with the rail transit industry, making it difficult to achieve effective interconnection of cloud and on-premises resources. Furthermore, the limited test environment resources lead to complex and repetitive setup and destruction processes, affecting the efficiency of simulation testing.
This paper provides a visual orchestration system and method for urban rail cloud simulation test resources, including a visual editing module, a template management module, a scheduling engine module, and a storage management module. Resources are created by dragging and dropping, templates are generated, and template parameters are parsed to automate the construction and management of cloud and on-premises resources.
It enables convenient and efficient orchestration of simulation test scenarios, improves the convenience and efficiency of building cloud simulation environment scenarios, solves the problem of limited resources, supports template reuse and flexible calling, and simplifies the process of building and destroying test environments.
Smart Images

Figure CN119583347B_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of cloud computing application technology for rail transit, specifically relating to a visualization and arrangement system and method for urban rail cloud simulation test resources. Background Technology
[0002] With the rapid development and maturation of cloud computing and big data technologies, cloud platforms have been widely applied in the rail transit industry, offering multiple advantages such as resource sharing, data centralization, efficient operation and maintenance, energy conservation and environmental protection, personalized customization, and cost reduction and efficiency improvement. As of June 2021, among the 44 cities with operational urban rail transit systems, 29 cities had built, planned, or were conducting cloud technology research. The deep integration of cloud computing technology and the rail industry has become an inevitable trend, serving as the foundation and driving force for the industry's digital transformation and innovation. Currently, the application of cloud computing technology in rail industry production systems is still in its early stages. Several metro systems in China are exploring product development models that deeply integrate urban rail transit expertise with cloud computing technology by building testing and verification platforms.
[0003] Due to the unique nature of the rail transit industry, very few rail transit business systems are deployed on public clouds; they are typically hosted on private clouds. Therefore, traditional public cloud orchestration services lack the on-premises and cloud-based interconnectivity capabilities required for the rail transit industry, making them difficult to integrate with its needs. Currently, most rail transit cloud platforms primarily provide IaaS-level infrastructure services, lacking focus and support for the architecture and performance of cloud-based business systems. Especially given the diverse specializations and complex system architectures within the rail transit sector, situations often arise where data acquisition front-ends are on-premises while management systems reside in the cloud. Therefore, setting up simulation testing environments requires allocating cloud resources as well as building supporting on-premises environments, involving multiple aspects such as hosts, networks, storage, and security, making environment setup quite challenging. Furthermore, rail transit systems often have testing requirements for interconnecting multiple professional interfaces. Due to limited testing environment resources, complex scheduling is necessary during testing to minimize the problem of redundant environment setups for business systems with numerous interconnections. In urban rail cloud simulation testing, there is a lack of functionality for repeatedly creating, destroying, and restoring different cloud simulation environment scenarios based on limited simulation resources. Summary of the Invention
[0004] To address the shortcomings of the existing technologies, this application provides a visualization and arrangement system and method for urban rail cloud simulation test resources.
[0005] In the first aspect, this application proposes a visual arrangement system for urban rail cloud simulation test resources, including a visual editing module, a template management module, a scheduling engine module, a storage management module, a cloud platform, on-premises equipment, and a simulation interface;
[0006] The visual editing module is used to create or edit different types of resources by dragging and dropping, visually represent various resource types and set attributes at the same time, thereby completing the visual arrangement of business scenarios. Based on the arranged business scenarios, a template is generated. The template is a text description file used to create or update scenario instances in resource arrangement, which describes the required cloud resources and service information.
[0007] The template management module is used to save the templates created or edited by the visual editing module to the database, and to connect to the corresponding devices and configure parameters according to the resource type of the template;
[0008] The scheduling engine module is used to parse the template to obtain template parameters, and build corresponding types of business scenarios with the cloud platform, on-premises devices and simulation interfaces according to the parsed template parameters. At the same time, the storage management module queries and verifies the type of business scenario construction and marks the construction status.
[0009] The storage management module is used for data storage, including system management data, template data, resource data, and log data. The resource data is sent to the scheduling engine module for business scenario query and verification.
[0010] In some optional implementations of some embodiments, the visual editing module includes a visual editing interface, a resource bar operation unit, an attribute bar operation unit, and a toolbar operation unit;
[0011] The visual editing interface is used to drag and drop resource items in the resource bar operation unit, while displaying the attribute fields of the resource item. It constructs the architecture diagram of the arrangement template through the interactive connection between resource items, and performs arrangement, association and inclusion operations on the position of resource items.
[0012] The resource bar operation unit is used to display the programmable resource items in the resource bar and classify them according to business type. The resource items come from resource items of different resource types configured by the system.
[0013] The attribute bar operation unit is used to display the attribute content of resource items. When any resource item is selected in the visual editing interface, the attribute bar operation unit displays the name and type of the resource item, and lists the attribute fields of the resource item according to the resource item configuration. The attributes of the resource item are set, and the set attribute values will be automatically generated into the template script content.
[0014] The toolbar operation unit includes basic operation tools required in the visual arrangement process. The toolbar operation unit is used to perform operations including file management, template saving, point selection, box selection, undo, and redo via shortcut keys.
[0015] In some optional implementations of some embodiments, the resource types configured in the resource bar operation unit include cloud resources, simulation types, and on-premises resources;
[0016] When the system configures resource items of the resource type as cloud resources, the resource items include virtual computing resources, virtual network resources, virtual storage resources, and virtual security resources;
[0017] When the system is configured with resource items of the type of on-premises resource, the resource items include cloud boundary network devices, cloud boundary security devices, cloud boundary interface devices, and on-premises devices of the subject to be tested or related subjects.
[0018] When the system configures resource items of the simulation type, the resource items include virtual interfaces or virtual systems of simulation tools.
[0019] In some optional implementations of some embodiments, the template management module includes a cloud resource docking unit, an on-premises resource docking unit, a cloud platform simulation docking unit, and a parameter configuration unit;
[0020] The cloud resource docking unit is used to dock with devices whose resource type is cloud resources, including cloud hosts, cloud disks, VPCs, subnets, routers, virtual firewalls, and security networks.
[0021] The cloud-based resource docking unit is used to dock with devices whose resource type is cloud-based resources, including border firewalls, border switches, rail transit professional front-end equipment, servers, terminals, network equipment, security equipment and storage devices;
[0022] The cloud platform simulation docking unit is used to dock with simulation testing tools whose resource type is simulation, including professional system interface simulation service and professional system data simulation service;
[0023] The parameter configuration unit is used to separate sensitive information and configuration parameters from the template code and perform dynamic parameter configuration when applying the template.
[0024] In some optional implementations of some embodiments, the scheduling engine module includes a cloud resource scheduling unit, an on-premises resource scheduling unit, and a simulation device scheduling unit;
[0025] The cloud resource scheduling unit is used to call the cloud platform's API interface to create a new virtual machine when the resource type in the parsed template parameters is a cloud resource and the resource item's setup status is a new type; when the resource item's setup status is an existing type, it schedules the existing virtual machine environment; and finally, it configures the corresponding network and security parameters according to the resource item's network and security status.
[0026] The on-premises resource scheduling unit is used to schedule the boundary network devices and boundary security devices at the cloud edge to perform API docking when the resource type in the parsed template parameters is an on-premises resource, thereby connecting the cloud and on-premises networks and security links and enabling the interface connectivity between the business systems in the cloud virtual machines and the on-premises systems.
[0027] The simulation equipment scheduling unit is used to schedule the simulation system and the corresponding network and security devices when the resource type in the parsed template parameters is simulation type, so as to provide simulated business interfaces or data interfaces for the business systems in the cloud virtual machine.
[0028] In some optional implementations of some embodiments, the storage management module includes a system data management unit, a template data management unit, a resource data management unit, and a log data management unit;
[0029] The system data management unit is used to manage data related to cloud environment management, line management, professional management, user management, role management, and organization management.
[0030] The template data management unit is used to record templates, template history information, and status information data;
[0031] The resource data management unit is used to record resource item configuration data, including resource item configuration information of cloud platform, on-premises device, and simulation interface. When resources change, the resource data record also needs to be updated synchronously. The resource data is finally stored in the database and provided to the visualization editing module for display, as well as sent to the scheduling engine module for query and verification.
[0032] The log data management unit is used to record system logs, operation logs, and running logs.
[0033] Secondly, this application proposes a visualization arrangement method for urban rail cloud simulation test resources, including scene creation steps, template creation steps, and template definition steps;
[0034] The scene creation steps are as follows:
[0035] Through the visual editing interface, users can drag and drop resource items to arrange their positions and relationships, configure the required attribute information for each resource item, and automatically generate and update template management data through the template management module after configuration. This data is then cached in the storage management module. Once the user has completed the arrangement, the deployment process is executed through the visual editing interface. At this point, the scheduling engine module reads the template data, parses out the resource data information for each life in the template, verifies the status of the resources, lists the status of resources to be created, modified, or scheduled, and creates scenarios based on different resource statuses and resource types.
[0036] The template creation steps are as follows:
[0037] Templates are created on the visual editing interface. The visual editing interface reads the resource item configuration content, displays the dragged resource items according to the resource item classification and definition, obtains the metadata information of the resource item attributes according to the resource item configuration, dynamically loads the attributes and corresponding attribute configurations, handles the dependencies between attributes, ensures that the combination of attribute values is logical, provides a detailed description of the attributes and fill-in prompts, configures attributes as variables, and separates sensitive information and fixed values from the template code to ensure the template security and flexibility.
[0038] After the resource item configuration and attribute configuration are completed, the resource items are connected to determine the dependencies between them, which guides the execution engine to analyze the order of resource creation and connect them appropriately.
[0039] After the integration is completed, the template content is serialized in JSON format and sent to the template management module for template saving. Different templates are created according to business distinctions, or different versions are created under one template to realize template creation.
[0040] The template definition steps are as follows:
[0041] Define the configuration declarations, resource declarations, variable declarations, and output declarations according to the template structure.
[0042] Define configuration declaration: Specify the cloud service provider or infrastructure platform to be used, including configuration connection parameters, authentication information and region;
[0043] Define variable declarations: Introduce external inputs into the template to increase its flexibility and reusability, including custom configurations when applying the template;
[0044] Define output declaration: used to obtain resource information from other templates or user-created resources;
[0045] Define resource declarations: Create infrastructure resources in the template, each resource has a unique type, name and other configuration properties;
[0046] The scene destruction steps are as follows:
[0047] The scene module to be destroyed is read through the visual editing module, and the scene destruction process is initiated. After initiation, the scheduling engine module first reads the resource status involved in the storage management module and lists the resources to be destroyed. Then, the cloud platform API is called to perform the cloud resource destruction operation, the corresponding network security interface is called to restore the original settings, the on-premises system is shut down, and the simulation interface service is activated. During the destruction process, the scheduling engine module captures the results in real time and synchronously updates the resource status in the storage management module.
[0048] In some optional implementations of certain embodiments, the system also includes using a scheduling engine module to coordinate the dependencies and execution order between various resources, capture API return results, update resource status files, perform logging, and provide early warnings about issues with resource operation interfaces.
[0049] Thirdly, this application proposes an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method described above.
[0050] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described above.
[0051] The beneficial effects of this invention are:
[0052] This method assists users in conveniently and efficiently orchestrating simulation test business scenarios and converting these scenarios into templates—reusable business scenario architecture scripts. The scheduling engine then uses the template data to interface with cloud platforms, on-premises systems, and simulation interfaces to build simulation test scenario instances for the business system from cloud to on-premises. Users can perform business system simulation tests on these instance instances. This method allows users to save the entire visually orchestrated simulation scenario as a template, or select a specific resource as a template. When needed during subsequent simulation testing, the template file can be flexibly invoked, and the scheduling engine can launch and deploy the environment, solving the problem of limited test environment resources and improving the convenience and efficiency of building cloud simulation environment scenarios. Attached Figure Description
[0053] Figure 1 This is a system schematic diagram of the present invention. Detailed Implementation
[0054] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
[0055] Firstly, this application proposes a visualization and arrangement system for urban rail cloud simulation test resources, such as... Figure 1 As shown, it includes a visual editing module, a template management module, a scheduling engine module, a storage management module, a cloud platform, on-premises devices, and a simulation interface;
[0056] The visual editing module is used to create or edit different types of resources by dragging and dropping, visually represent various resource types and set attributes at the same time, thereby completing the visual arrangement of business scenarios. Based on the arranged business scenarios, a template is generated. The template is a text description file used to create or update scenario instances in resource arrangement, which describes the required cloud resources and service information.
[0057] In some optional implementations of some embodiments, the visual editing module includes a visual editing interface, a resource bar operation unit, an attribute bar operation unit, and a toolbar operation unit;
[0058] The visual editing interface is used to drag and drop resource items in the resource bar operation unit, while displaying the attribute fields of the resource item. It constructs the architecture diagram of the arrangement template through the interactive connection between resource items, and performs arrangement, association and inclusion operations on the position of resource items.
[0059] The resource bar operation unit is used to display the programmable resource items in the resource bar and classify them according to business type. The resource items come from resource items of different resource types configured by the system.
[0060] In some optional implementations of some embodiments, the resource types configured in the resource bar operation unit include cloud resources, simulation types, and on-premises resources;
[0061] When the system configures resource items of the resource type as cloud resources, the resource items include virtual computing resources, virtual network resources, virtual storage resources, and virtual security resources;
[0062] When the system is configured with resource items of the type of on-premises resource, the resource items include cloud boundary network devices, cloud boundary security devices, cloud boundary interface devices, and on-premises devices of the subject to be tested or related subjects.
[0063] When the system configures resource items of the simulation type, the resource items include virtual interfaces or virtual systems of simulation tools.
[0064] The attribute bar operation unit is used to display the attribute content of resource items. When any resource item is selected in the visual editing interface, the attribute bar operation unit displays the name and type of the resource item, and lists the attribute fields of the resource item according to the resource item configuration. The attributes of the resource item are set, and the set attribute values will be automatically generated into the template script content.
[0065] The toolbar operation unit includes basic operation tools required in the visual arrangement process. The toolbar operation unit is used to perform operations including file management, template saving, point selection, box selection, undo, and redo via shortcut keys.
[0066] Furthermore, the ultimate goal of the visual editing module is to assist users in arranging business scenarios. Compared to traditional manual editing, it provides an intuitive interface that allows users to create or edit different types of resources through drag-and-drop. It supports visual representation and attribute settings for various resource types and generates templates for the business scenario, which can then be used as reusable business scenario architecture scripts.
[0067] The main design includes a resource bar, a visual editing interface, a resource bar, a property bar, and a toolbar. Users can arrange simulation test scene resources by dragging and dropping on the visual editing page.
[0068] The resource bar operation unit is the resource bar itself, which displays resource items available for arrangement. These resource items originate from the system's configured display resource items and are categorized by business type. Resource items include cloud resources, such as virtual computing resources, virtual network resources, virtual storage resources, and virtual security resources; cloud edge resources, such as cloud boundary network devices, cloud boundary security devices, and cloud boundary interface devices; on-premises supporting systems or equipment, including on-premises equipment or systems of the discipline under test or related disciplines; virtual interfaces or virtual systems of simulation tools; and test scenarios for other disciplines, including interface-connected systems, devices, or services.
[0069] The visual editing interface is the main work area for orchestrating scenes. It supports drag-and-drop placement of resource items in the resource bar and displays the architecture diagram of the orchestration template through the interactive connections between resource items. It supports operations such as orchestrating, associating, and including resource items. Clicking on a resource item in the visual editing interface displays the attribute fields of that resource item in the attribute panel on the right.
[0070] The attribute bar is the operation unit that displays the attribute content of resource items in the visual editing interface. When a resource item is selected in the visual editing interface, the attribute bar displays the name and type of the resource item, and lists the attribute fields of the resource item according to the resource item configuration. It supports setting the attributes of the resource item, and the entered attribute values will be automatically generated into the template script content.
[0071] The toolbar operation unit is the toolbar itself, which contains the basic operation tools needed in the visual layout process, and should also have shortcut key operation methods, such as file management, template saving, point selection / box selection, undo / redo, etc.
[0072] The visual editing interface is implemented by a vector graphics editing engine based on HTML5 Canvas and SVG. From bottom to top, it includes a base layer (providing basic functions such as graphic drawing, event handling, and style settings), a component layer (various graphic components, such as nodes, lines, and text, as well as the layout and interaction logic of components), a data layer (interacting with data, parsing and processing data, and mapping it onto graphics), a rendering layer (using efficient rendering algorithms to achieve real-time drawing and animation effects of graphics), and an interaction layer (enabling user interaction with graphics).
[0073] The visual editing module can read historical template parameters from the template management module, visually restore and display historical template scenes, and publish new simulation test scenarios and update template data through visual editing. The visual editing interface provided by this invention offers users a custom drag-and-drop arrangement and building function for simulation test scenarios. It provides custom drag-and-drop arrangement and editing functions for cloud platform resources, including parameter configurations for nodes such as cloud computing, storage, network, and security; custom drag-and-drop arrangement and editing for cloud edge and on-premises systems, including network and security configurations at the edge and interface configurations for on-premises systems; and custom drag-and-drop arrangement and editing for simulation interfaces / systems, including related interface configurations.
[0074] The template management module is used to save the templates created or edited by the visual editing module to the database, and to connect to the corresponding devices and configure parameters according to the resource type of the template;
[0075] In some optional implementations of some embodiments, the template management module includes a cloud resource docking unit, an on-premises resource docking unit, a cloud platform simulation docking unit, and a parameter configuration unit;
[0076] The cloud resource docking unit is used to dock with devices whose resource type is cloud resources, including cloud hosts, cloud disks, VPCs, subnets, routers, virtual firewalls, and security networks.
[0077] The cloud-based resource docking unit is used to dock with devices whose resource type is cloud-based resources, including border firewalls, border switches, rail transit professional front-end equipment, servers, terminals, network equipment, security equipment and storage devices;
[0078] The cloud platform simulation docking unit is used to dock with simulation testing tools whose resource type is simulation, including professional system interface simulation service and professional system data simulation service;
[0079] The parameter configuration unit is used to separate sensitive information and configuration parameters from the template code and perform dynamic parameter configuration when applying the template.
[0080] Furthermore, the template management module is responsible for saving the templates created and edited by the visual editing module to the database, and providing users with template retrieval, version control, professional classification, sharing, and permission setting functions. A template is a text description file used in resource orchestration to create and update scene instances, and is used to describe the required cloud resources and service information.
[0081] The template supports cloud resource types, including but not limited to: cloud computing resources (cloud hosts, bare metal), cloud storage resources (cloud disks, object storage), cloud network resources (classic networks, VPCs, subnets, routers), and cloud security resources (virtual firewalls, security groups).
[0082] The template supports on-premises resource types, including but not limited to: border firewalls, border switches, rail transit professional front-end equipment, servers, terminals, network equipment, security equipment, or storage devices.
[0083] The template supports cloud platform simulation testing tools, including but not limited to professional system interface simulation services and professional system data simulation services.
[0084] Templates support configuration variables, which can separate sensitive information (such as passwords) and configuration parameters (such as specifications) from the template code. When applying the template, variables can be dynamically configured, improving the template's flexibility and security.
[0085] The template management function based on rail transit simulation test scenarios provided by this invention allows template parameters to declare the required cloud platform resource types, specifications, and relationships between resources; to declare the required cloud edge / on-premises system resource types, parameter configurations, interface configurations, and relationships between resources; and to declare the simulation tool's interface / system resource types, parameter configurations, interface configurations, and relationships between resources. The template parameters also include network and security configuration information required for the rail transit simulation test scenario. The template management module provides multi-version template management to facilitate elastic scaling of scenario instances.
[0086] The scheduling engine module is used to parse the template to obtain template parameters, and build corresponding types of business scenarios with the cloud platform, on-premises devices and simulation interfaces according to the parsed template parameters. At the same time, the storage management module queries and verifies the type of business scenario construction and marks the construction status.
[0087] In some optional implementations of some embodiments, the scheduling engine module includes a cloud resource scheduling unit, an on-premises resource scheduling unit, and a simulation device scheduling unit;
[0088] The cloud resource scheduling unit is used to call the cloud platform's API interface to create a new virtual machine when the resource type in the parsed template parameters is a cloud resource and the resource item's setup status is a new type; when the resource item's setup status is an existing type, it schedules the existing virtual machine environment; and finally, it configures the corresponding network and security parameters according to the resource item's network and security status.
[0089] The on-premises resource scheduling unit is used to schedule the boundary network devices and boundary security devices at the cloud edge to perform API docking when the resource type in the parsed template parameters is an on-premises resource, thereby connecting the cloud and on-premises networks and security links and enabling the interface connectivity between the business systems in the cloud virtual machines and the on-premises systems.
[0090] The simulation equipment scheduling unit is used to schedule the simulation system and the corresponding network and security devices when the resource type in the parsed template parameters is simulation type, so as to provide simulated business interfaces or data interfaces for the business systems in the cloud virtual machine.
[0091] Furthermore, the scheduling engine module can parse template parameters and classify scene construction based on the parsed template parameters. It also queries the storage management module to verify whether the construction type in the template already exists and marks the construction status.
[0092] 1) When the resource type in the template parameters parsed by the cloud resource scheduling unit is cloud resource, and the resource item's setup status is "new", the scheduling engine module calls the cloud platform's API interface to create a new virtual machine; when the resource item's setup status is "existing", the existing virtual machine environment is scheduled. Finally, the corresponding network and security parameters are configured according to the resource item's network and security status.
[0093] 2) When the resource type in the template parameters parsed by the on-premises resource scheduling unit is on-premises resource, the boundary network devices and boundary security devices at the cloud edge are scheduled to perform API docking scheduling, connect the cloud and on-premises networks and security links, and realize the interface connection between the business system in the cloud virtual machine and the on-premises system.
[0094] 3) When the resource type in the template parameters parsed by the simulation equipment scheduling unit is simulation type, the simulation system and the corresponding network and security equipment are scheduled to provide simulated business interfaces or data interfaces for the business systems in the cloud virtual machine.
[0095] The scheduling function based on the rail transit simulation test scenario template provided by this invention can be used to create scenario instances. The scheduling engine module can parse template parameters and perform scenario construction and scheduling based on the parsed template parameters. It can interface with cloud platforms via API to create new virtual machine environments or schedule existing virtual machine environments, including but not limited to virtualized computing resources, storage resources, network resources, and security resources of the cloud platform. It can interface with boundary network devices and boundary security devices at the cloud edge via API to connect cloud and on-premises networks and security links, enabling interface connectivity between business systems in cloud virtual machines and on-premises systems. It can interface with simulation tools to provide simulated business interfaces or data interfaces for business systems in cloud virtual machines.
[0096] The storage management module is used for data storage, including system management data, template data, resource data, and log data. The resource data is sent to the scheduling engine module for business scenario query and verification.
[0097] In some optional implementations of some embodiments, the storage management module includes a system data management unit, a template data management unit, a resource data management unit, and a log data management unit;
[0098] The system data management unit is used to manage data related to cloud environment management, line management, professional management, user management, role management, and organization management.
[0099] The template data management unit is used to record templates, template history information, and status information data;
[0100] The resource data management unit is used to record resource item configuration data, including resource item configuration information of cloud platform, on-premises device, and simulation interface. When resources change, the resource data record also needs to be updated synchronously. The resource data is finally stored in the database and provided to the visualization editing module for display, as well as sent to the scheduling engine module for query and verification.
[0101] The log data management unit is used to record system logs, operation logs, and running logs.
[0102] Secondly, this application proposes a visualization arrangement method for urban rail cloud simulation test resources, including scene creation steps, template creation steps, and template definition steps;
[0103] The scene creation steps are as follows:
[0104] Through the visual editing interface, users can drag and drop resource items to arrange their positions and relationships, configure the required attribute information for each resource item, and automatically generate and update template management data through the template management module after configuration. This data is then cached in the storage management module. Once the user has completed the arrangement, the deployment process is executed through the visual editing interface. At this point, the scheduling engine module reads the template data, parses out the resource data information for each life in the template, verifies the status of the resources, lists the status of resources to be created, modified, or scheduled, and creates scenarios based on different resource statuses and resource types.
[0105] Furthermore, users can drag and drop resource items through a visual editing interface to arrange their positions, relationships, and other aspects, and configure the required attribute information for each resource item.
[0106] The template management module automatically generates and updates template management data based on user operations and caches it in the storage management module.
[0107] Once the user has completed the orchestration, the deployment work can be performed through the visual editing interface. At this time, the scheduling engine module reads the template data, parses out the resource data information of each life in the template, verifies the status of the resources, and lists the status of the resources to be created, modified or scheduled.
[0108] When a cloud resource is in a new state, the scheduling engine module calls the cloud platform API to create a new virtual machine; when a resource is in an existing state, it schedules the existing virtual machine environment. Finally, it configures the corresponding network and security parameters based on the resource's network and security status.
[0109] When the on-premises resource type is newly created, the scheduling engine module calls the API interfaces of the cloud edge boundary network device and boundary security device to connect the cloud and on-premises network and security links, and realize the interface connection between the business system in the cloud virtual machine and the on-premises system.
[0110] For simulation interfaces or system types, schedule the simulation system and responding network and security devices to provide simulated business interfaces or data interfaces for business systems in cloud virtual machines.
[0111] The template creation steps are as follows:
[0112] Templates are created on the visual editing interface. The visual editing interface reads the resource item configuration content, displays the dragged resource items according to the resource item classification and definition, obtains the metadata information of the resource item attributes according to the resource item configuration, dynamically loads the attributes and corresponding attribute configurations, handles the dependencies between attributes, ensures that the combination of attribute values is logical, provides a detailed description of the attributes and fill-in prompts, configures attributes as variables, and separates sensitive information and fixed values from the template code to ensure the template security and flexibility.
[0113] After the resource item configuration and attribute configuration are completed, the resource items are connected to determine the dependencies between them, which guides the execution engine to analyze the order of resource creation and connect them appropriately.
[0114] After the integration is completed, the template content is serialized in JSON format and sent to the template management module for template saving. Different templates are created according to business distinctions, or different versions are created under one template to realize template creation.
[0115] Furthermore, users can create templates on the visual editing interface. The visual editor reads the resource item configuration content and displays the draggable resource items according to their categories and definitions. Resource items include cloud resources, such as virtual computing resources, virtual network resources, virtual storage resources, and virtual security resources; on-premises resources, such as cloud boundary network devices, cloud boundary security devices, cloud boundary interface devices, and on-premises devices or systems of the subject under test or related fields; virtual interfaces or virtual systems of simulation tools; and test scenarios of other fields, including interface connection systems, devices, or services.
[0116] Based on the resource item configuration, the visual editor can obtain metadata information about the resource item attributes, including field types, parameter ranges, and whether they are required. It dynamically loads attributes and their corresponding configurations, handles dependencies between attributes, ensures logical combinations of attribute values, and provides detailed descriptions and input hints to help users understand the meaning of each attribute. Users can configure attributes as variables, separating sensitive information and fixed values from the template code, thus improving template security and flexibility.
[0117] Users can connect resources to determine their dependencies. This guides the execution engine in analyzing the order in which resources are created and ensuring proper integration.
[0118] The visual editor reads available values of resource attributes, such as specifications, image, and availability zone, through the storage management module to ensure the validity of attribute values.
[0119] After the visual editor finishes editing the template, it serializes the template content in JSON format and hands it over to the template management module for saving.
[0120] Users can create different templates according to business needs, or create different versions under one template to modify and upgrade a business environment.
[0121] The template definition steps are as follows:
[0122] Define the configuration declarations, resource declarations, variable declarations, and output declarations according to the template structure.
[0123] Define configuration declaration: Specify the cloud service provider or infrastructure platform to be used, including configuration connection parameters, authentication information and region;
[0124] Define variable declarations: Introduce external inputs into the template to increase its flexibility and reusability, including custom configurations when applying the template;
[0125] Define output declaration: used to obtain resource information from other templates or user-created resources;
[0126] Define resource declarations: Create infrastructure resources in the template, each resource has a unique type, name and other configuration properties;
[0127] Furthermore, the template structure consists of four parts, in order: configuration declaration, resource declaration, variable declaration, and output declaration.
[0128] The configuration declaration is used to specify the cloud service provider or infrastructure platform to be used. This includes configuring connection parameters, authentication information, region, etc.
[0129] Variable declarations are used to introduce external input into templates to increase template flexibility and reusability, allowing users to customize configurations when applying templates.
[0130] The output declaration is used by other templates or users to obtain information about the resources created.
[0131] The resource declaration in the template defines the infrastructure resources to be created, such as virtual machines, buckets, database instances, network rules, etc. Each resource has a unique type and name, as well as other configuration attributes.
[0132] The specific configuration attributes are as follows:
[0133] 1. The cloud server type name in the template is compute_instance, which includes, but is not limited to, the following attributes. The cloud server attribute descriptions are shown in Table 1:
[0134] Table 1
[0135]
[0136] 2. In the template, the disk type is named "disk" and includes, but is not limited to, the following attributes. Disk attribute descriptions are shown in Table 2:
[0137] Table 2
[0138] Attribute Name Attribute Description type name Disk Name String region_id Store available domain IDs String storage_type Storage type String volume_type Hard drive type, such as SSD, HDD, SSHD String size Size, unit GB Int description describe String multi_attach Multiple mounts Boolean snapshot_id Snapshot ID String image_id Mirror ID String location Storage pool name String
[0139] 3. In the template, the classic network type is named "network" and includes the following attributes. The attribute descriptions for the classic network are shown in Table 3:
[0140] Table 3
[0141] Attribute Name Attribute Description type name The name of a classic network String tenant_id Organization ID String description describe String cidr network segment String
[0142] 4. In the template, the classic network subnet is named "subnet" and includes the following attributes. The attribute descriptions for classic network subnets are shown in Table 4:
[0143] Table 4
[0144]
[0145] 5. The firewall in the template is named "firewall" and includes the following attributes, as described in Table 5:
[0146] Table 5
[0147] Attribute Name Attribute Description type name Firewall name String tenant_id Organization ID String description describe String enable_audit Audit Boolean route_ids Router ID List
[0148] 6. A firewall can be associated with multiple firewall rules. In the template, the type name is firewall_rule, and the firewall rule attributes are described in Table 6.
[0149] Table 6
[0150]
[0151] 7. In the template, the security group type is named security_group and includes the following attributes. The security group attributes are described in Table 7:
[0152] Table 7
[0153] Attribute Name Attribute Description type name Security group name String tenant_id Organization ID String description describe String
[0154] 8. Multiple security group rules can be associated with a security group. In the template, the type name is security_group_rule, which includes the following attributes. The attributes of security group rules are described in Table 8:
[0155] Table 8
[0156]
[0157] 9. In the template, the router type is named "route" and includes the following attributes. Router attribute descriptions are shown in Table 9:
[0158] Table 9
[0159]
[0160] The scene destruction steps are as follows:
[0161] The scene module to be destroyed is read through the visual editing module, and the scene destruction process is initiated. After initiation, the scheduling engine module first reads the resource status involved in the storage management module and lists the resources to be destroyed. Then, the cloud platform API is called to perform the cloud resource destruction operation, the corresponding network security interface is called to restore the original settings, the on-premises system is shut down, and the simulation interface service is activated. During the destruction process, the scheduling engine module captures the results in real time and synchronously updates the resource status in the storage management module.
[0162] After the test is completed, users can undo the built scene through the visual editing module interface. At this time, the scheduling engine module will execute the user's command to reclaim the corresponding resources and restore the initial configuration. Users can also save the template as needed, in which case the template management module will store the template data in the storage management module.
[0163] In some optional implementations of certain embodiments, the system also includes using a scheduling engine module to coordinate the dependencies and execution order between various resources, capture API return results, update resource status files, perform logging, and provide early warnings about issues with resource operation interfaces.
[0164] Thirdly, this application proposes an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method described above.
[0165] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described above.
[0166] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.
[0167] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0168] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.
[0169] In the embodiments provided in this disclosure, it should be understood that the disclosed apparatus / computer devices and methods can be implemented in other ways. For example, the apparatus / computer device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. Multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0170] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0171] Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0172] If an integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program may include computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. A computer-readable medium may include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in a computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in a jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.
[0173] The above are merely preferred embodiments of the present invention. It should be noted that any modifications and improvements made by those skilled in the art without departing from the present technical solution should also be considered to fall within the scope of protection claimed in this claim.
Claims
1. A visualization and arrangement system for urban rail cloud simulation test resources, characterized in that: It includes a visual editing module, a template management module, a scheduling engine module, a storage management module, a cloud platform, on-premises devices, and a simulation interface; The visual editing module is used to create or edit different types of resources by dragging and dropping, visually represent various resource types and set attributes at the same time, thereby completing the visual arrangement of business scenarios. Based on the arranged business scenarios, a template is generated. The template is a text description file used to create or update scenario instances in resource arrangement, which describes the required cloud resources and service information. The template management module is used to save the templates created or edited by the visual editing module to the database, connect to the corresponding devices according to the resource type of the template and configure the parameters. The template management module includes a cloud resource connection unit, a cloud-based resource connection unit, a cloud platform simulation connection unit and a parameter configuration unit. The cloud resource docking unit is used to dock with devices whose resource type is cloud resources, including cloud hosts, cloud disks, VPCs, subnets, routers, virtual firewalls, and security networks. The cloud-based resource docking unit is used to dock with devices whose resource type is cloud-based resources, including border firewalls, border switches, rail transit professional front-end equipment, servers, terminals, network equipment, security equipment and storage devices; The cloud platform simulation docking unit is used to dock with simulation testing tools whose resource type is simulation, including professional system interface simulation service and professional system data simulation service; The parameter configuration unit is used to separate sensitive information and configuration parameters from the template code and perform dynamic parameter configuration when applying the template. The scheduling engine module is used to parse the template to obtain template parameters, and build corresponding types of business scenarios with the cloud platform, on-premises devices and simulation interfaces according to the parsed template parameters. At the same time, the storage management module queries and verifies the type of business scenario construction and marks the construction status. The scheduling engine module includes a cloud resource scheduling unit, an on-premises resource scheduling unit and a simulation device scheduling unit. The cloud resource scheduling unit is used to call the cloud platform's API interface to create a new virtual machine when the resource type in the parsed template parameters is a cloud resource and the resource item's setup status is a new type; when the resource item's setup status is an existing type, it schedules the existing virtual machine environment; and finally, it configures the corresponding network and security parameters according to the resource item's network and security status. The on-premises resource scheduling unit is used to schedule the boundary network devices and boundary security devices at the cloud edge to perform API docking when the resource type in the parsed template parameters is an on-premises resource, thereby connecting the cloud and on-premises networks and security links and enabling the interface connectivity between the business systems in the cloud virtual machines and the on-premises systems. The simulation equipment scheduling unit is used to schedule the simulation system and the corresponding network and security devices when the resource type in the parsed template parameters is simulation type, so as to provide simulated business interfaces or data interfaces for the business systems in the cloud virtual machine. The storage management module is used for data storage, including system management data, template data, resource data, and log data. The resource data is sent to the scheduling engine module for business scenario query and verification.
2. The system according to claim 1, characterized in that: The visual editing module includes a visual editing interface, a resource bar operation unit, a property bar operation unit, and a toolbar operation unit; The visual editing interface is used to drag and drop resource items in the resource bar operation unit, while displaying the attribute fields of the resource item. It constructs the architecture diagram of the arrangement template through the interactive connection between resource items, and performs arrangement, association and inclusion operations on the position of resource items. The resource bar operation unit is used to display the programmable resource items in the resource bar and classify them according to business type. The resource items come from resource items of different resource types configured by the system. The attribute bar operation unit is used to display the attribute content of resource items. When any resource item is selected in the visual editing interface, the attribute bar operation unit displays the name and type of the resource item, and lists the attribute fields of the resource item according to the resource item configuration. The attributes of the resource item are set, and the set attribute values will be automatically generated into the template script content. The toolbar operation unit includes basic operation tools required in the visual arrangement process. The toolbar operation unit is used to perform operations including file management, template saving, point selection, box selection, undo, and redo via shortcut keys.
3. The system according to claim 2, characterized in that: The resource types configured in the resource bar operation unit include cloud resources, simulation types, and on-premises resources; When the system configures resource items of the resource type as cloud resources, the resource items include virtual computing resources, virtual network resources, virtual storage resources, and virtual security resources; When the system is configured with resource items of the type of on-premises resource, the resource items include cloud boundary network devices, cloud boundary security devices, cloud boundary interface devices, and on-premises devices of the subject to be tested or related subjects. When the system configures resource items of the simulation type, the resource items include virtual interfaces or virtual systems of simulation tools.
4. The system according to claim 3, characterized in that: The storage management module includes a system data management unit, a template data management unit, a resource data management unit, and a log data management unit; The system data management unit is used to manage data related to cloud environment management, line management, professional management, user management, role management, and organization management. The template data management unit is used to record templates, template history information, and status information data; The resource data management unit is used to record resource item configuration data, including resource item configuration information of cloud platform, on-premises device, and simulation interface. When resources change, the resource data record also needs to be updated synchronously. The resource data is finally stored in the database and provided to the visualization editing module for display, as well as sent to the scheduling engine module for query and verification. The log data management unit is used to record system logs, operation logs, and running logs.
5. A method for visualizing and arranging urban rail cloud simulation test resources, characterized in that: This includes the steps for scene creation, template creation, template definition, and scene destruction. The scene creation steps are as follows: Through the visual editing interface, users can drag and drop resource items to arrange their positions and relationships, configure the required attribute information for each resource item, and automatically generate and update template management data through the template management module after configuration. This data is then cached in the storage management module. Once the user has completed the arrangement, the deployment process is executed through the visual editing interface. At this point, the scheduling engine module reads the template data, parses out the resource data information for each life in the template, verifies the status of the resources, lists the status of resources to be created, modified, or scheduled, and creates scenarios based on different resource statuses and resource types. The template creation steps are as follows: Templates are created on the visual editing interface. The visual editing interface reads the resource item configuration content, displays the dragged resource items according to the resource item classification and definition, obtains the metadata information of the resource item attributes according to the resource item configuration, dynamically loads the attributes and corresponding attribute configurations, handles the dependencies between attributes, ensures that the combination of attribute values is logical, provides a detailed description of the attributes and fill-in prompts, configures attributes as variables, and separates sensitive information and fixed values from the template code to ensure the template security and flexibility. After the resource item configuration and attribute configuration are completed, the resource items are connected to determine the dependencies between them, which guides the execution engine to analyze the order of resource creation and connect them appropriately. After the integration is completed, the template content is serialized in JSON format and sent to the template management module for template saving. Different templates are created according to business distinctions, or different versions are created under one template to realize template creation. The template definition steps are as follows: Define the configuration declarations, resource declarations, variable declarations, and output declarations according to the template structure. Define configuration declaration: Specify the cloud service provider or infrastructure platform to be used, including configuration connection parameters, authentication information and region; Define variable declarations: Introduce external inputs into the template to increase its flexibility and reusability, including custom configurations when applying the template; Define output declaration: used to obtain resource information from other templates or user-created resources; Define resource declarations: Create infrastructure resources in the template, each resource has a unique type, name and other configuration properties; The scene destruction steps are as follows: The scene module to be destroyed is read through the visual editing module, and the scene destruction work is started. After the start, the scheduling engine module first reads the resource status involved in the storage management module and lists the resources to be destroyed. Then, it calls the cloud platform API to perform the destruction operation of the cloud resources, calls the corresponding network security interface to restore the original settings, shuts down the on-premises system, and simulates the service. During the destruction process, the scheduling engine module captures the results in real time and updates the resource status in the storage management module synchronously.
6. The method according to claim 5, characterized in that: It also includes coordinating the dependencies and execution order between various resources through the scheduling engine module, capturing API return results, updating resource status files, logging, and alerting on problems in calling resource operation interfaces.
7. 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 processor executes the computer program, it implements the steps of the method as described in any one of claims 5-6.
8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 5-6.
Citation Information
Patent Citations
Resource management system based on cloud native platform technology and elastic construction method thereof
CN115733754A
Resource allocation method and device based on cloud native, equipment and medium
CN117648191A