CN117893679A

CN117893679A - Equipment management and control method and system based on digital twin

Info

Publication number: CN117893679A
Application number: CN202311873759.6A
Authority: CN
Inventors: 杨宏旭; 陈健; 方超; 王浩; 杨冰
Original assignee: Baweitong Technology Co ltd
Current assignee: Baweitong Technology Co ltd
Priority date: 2023-12-29
Filing date: 2023-12-29
Publication date: 2024-04-16

Abstract

The embodiment of the application provides a device management and control method and a system based on digital twinning, wherein the method comprises the following steps: displaying a rendered target room model through a first front-end page, wherein the target room model comprises at least one cabinet model; according to a selection instruction of a target cabinet model in a target room model displayed on a first front-end page, displaying an animation of opening a cabinet door of the target cabinet model on the first front-end page, and displaying at least one equipment model in the target cabinet model; acquiring identification information of a target equipment model according to a selection instruction of the target equipment model in the target equipment cabinet model displayed on a first front-end page; and acquiring information corresponding to the target equipment according to the identification information of the target equipment model, and displaying a detail panel containing the information corresponding to the target equipment on the first front-end page. The embodiment of the application can be applied to the field of the Internet of things, can improve the convenience and efficiency of equipment control and reduce the threshold of equipment control.

Description

Equipment management and control method and system based on digital twin

Technical Field

The application relates to the technical field of software development, in particular to a device management and control method and system based on digital twinning.

Background

With the development of information technology, digital transformation is also required for the management of equipment in the fields of rail transit and the like.

However, in the current scheme, the equipment in the fields of rail transit and the like is still controlled by adopting a traditional database-based mode, so that the operation is complex, the threshold for equipment control is higher, and the control efficiency is low.

Disclosure of Invention

The embodiment of the application provides a device management and control method and a system based on digital twinning, which can improve the convenience and efficiency of device management and control at least to a certain extent and reduce the threshold of device management and control.

Other features and advantages of the application will be apparent from the following detailed description, or may be learned by the practice of the application.

According to an aspect of an embodiment of the present application, there is provided a device management and control method based on digital twinning, the method including: displaying a rendered target room model through a first front-end page, wherein the target room model comprises at least one cabinet model; displaying an animation of opening a cabinet door of the target cabinet model on a first front-end page according to a selection instruction of the target cabinet model in the target room model displayed on the first front-end page, and displaying at least one equipment model in the target cabinet model; acquiring identification information of a target equipment model in the target equipment cabinet model according to a selection instruction of the target equipment model displayed on a first front-end page; and acquiring information corresponding to the target equipment according to the identification information of the target equipment model, and displaying a detail panel containing the information corresponding to the target equipment on the first front-end page.

In some embodiments of the present application, based on the foregoing, before displaying the rendered target room model through the first front-end page, the method further includes: acquiring at least one piece of equipment data monitored by a preset operation and maintenance platform by calling an interface provided by an entity configuration management database of the preset operation and maintenance platform; acquiring equipment numbers in the equipment data; for each equipment number, if it is determined that no equipment information matched with the equipment number exists in a local database, newly adding the equipment information matched with the equipment number into the local database according to equipment data containing the equipment number; the obtaining information corresponding to the target device according to the identification information of the target device model includes: and acquiring information corresponding to the target equipment from the local database according to the identification information of the target equipment model.

In some embodiments of the present application, based on the foregoing, before displaying the rendered target room model through the first front-end page, the method further includes: acquiring equipment information configured by an administrator on equipment through a second front-end page; and storing the equipment information into the local database.

In some embodiments of the present application, based on the foregoing, the device information is configured based on device information newly added in a local database according to device data monitored by a predetermined operation and maintenance platform.

In some embodiments of the present application, based on the foregoing, before displaying the rendered target room model through the first front-end page, the method further includes: acquiring port information configured by an administrator on a port of the equipment through a third front-end page, and storing the port information into a local database; acquiring equipment relation information configured by an administrator through a fourth front-end page, and storing the equipment relation information into a local database; acquiring equipment hierarchy relation information configured by an administrator through a fifth front-end page, and storing the equipment hierarchy relation information into a local database; acquiring inter-port connection information configured by an administrator through a sixth front-end page, and storing the inter-port connection information into a local database; after displaying at least one of the target rack models, the method further comprises: according to a trigger instruction of a target equipment model in the target equipment cabinet model displayed on a first front-end page, equipment information, port information, equipment relation information, equipment hierarchy relation information and inter-port connection information associated with the target equipment model are obtained from the local database, and a topological relation diagram is generated according to the equipment information, the port information, the equipment relation information, the equipment hierarchy relation information and the inter-port connection information associated with the target equipment model; and displaying a topology page in the first front-end page, and displaying the topological relation diagram in the topology page.

In some embodiments of the present application, based on the foregoing solution, before the obtaining, by the sixth front-end page, the inter-port connection information configured by the administrator, the method further includes: acquiring at least one port connection data monitored by a preset operation and maintenance platform by calling an interface provided by an entity configuration management database of the preset operation and maintenance platform; acquiring a device number and a port number in each port connection data; for each port connection data, if it is determined that the inter-port connection information matched with the equipment number and the port number in the port connection data does not exist in the local database, adding the inter-port connection information matched with the equipment number and the port number in the port connection data in the local database according to the equipment data containing the equipment number; the obtaining, by the sixth front-end page, the inter-port connection information configured by the administrator includes: displaying the inter-port connection information in the local database in the sixth front-end page; and acquiring new inter-port connection information obtained by editing the inter-port connection information in the sixth front-end page by an administrator.

In some embodiments of the present application, based on the foregoing, after displaying the rendered target room model through the first front-end page, the method further includes: displaying an equipment screening query entry through the first front-end page, wherein the equipment screening query entry comprises an equipment cabinet number pull-down menu and an equipment number pull-down menu, the equipment cabinet number pull-down menu comprises equipment cabinet numbers corresponding to all equipment models in a target room model, and the equipment number pull-down menu comprises equipment numbers corresponding to all equipment models in the target room model; and displaying a cabinet model corresponding to the cabinet number and an equipment model corresponding to the equipment number on the first front-end page according to the cabinet number and the equipment number selected by the user from the cabinet number drop-down menu and the equipment number drop-down menu.

In some embodiments of the application, based on the foregoing, after displaying at least one of the target rack models, the method further comprises: according to a trigger instruction of a first port model in target equipment models in the target equipment models displayed on a first front-end page, popping the target equipment models out of the target equipment models, displaying an opposite-end model of equipment to which a second port model belongs, and displaying a connecting line between the second port model of the opposite-end model and the first port model of the target equipment model; and correspondingly displaying information related to a first port according to the position of the first port model in the first front-end page, and correspondingly displaying information related to a second port according to the position of the second port model.

In some embodiments of the application, based on the foregoing, the method further comprises: and displaying equipment classification summary information corresponding to the target room model through a first front-end page, wherein the equipment classification summary information is obtained by classifying and counting information corresponding to equipment in the target room model in the local database.

According to an aspect of an embodiment of the present application, there is provided a digital twin-based device management and control system, including: one or more processors; and a storage means for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the digital twinning-based device management method as described in the above embodiments.

According to an aspect of an embodiment of the present application, there is provided a computer program product including computer instructions stored in a computer-readable storage medium, from which computer instructions a processor of a computer device reads, the processor executing the computer instructions, causing the computer device to perform a digital twin-based device management method as described in the above embodiments.

In the technical schemes provided by some embodiments of the present application, a rendered target room model is displayed in a first front-end page, and a plurality of cabinet models are displayed in the target room model, then according to a selection instruction of a user for a target cabinet model in the target room model displayed in the first front-end page, the first front-end page displays back an animation of a cabinet door for opening the target cabinet model, and displays at least one equipment model in the target cabinet model; when a selection instruction of the target equipment model is received, the identification information of the target equipment model is acquired, the identification information of the target equipment model acquires the information corresponding to the target equipment, and a detail panel containing the information corresponding to the target equipment is displayed on a first front-end page. Therefore, the embodiment of the application realizes mapping of rooms, cabinets and equipment in the virtual space based on the digital twin technology, so that a user can easily and intuitively understand the layout information of the equipment in the physical space and the information of the equipment, the convenience and the efficiency of equipment management and control are improved, the threshold and the cost of equipment management and control are reduced, and the quality improvement and efficiency improvement effects can be realized in scenes such as rail traffic management and the like.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. It is evident that the drawings in the following description are only some embodiments of the present application and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art. In the drawings:

FIG. 1 illustrates an overall functional architecture diagram according to one embodiment of the present application;

FIG. 2 illustrates a flow chart of a digital twinning-based device management and control method in accordance with one embodiment of the present application;

FIG. 3 shows a flowchart of the details of steps prior to step 240 and step 270 in the embodiment of FIG. 2, according to one embodiment of the application;

FIG. 4 shows a schematic architecture diagram according to one embodiment of the application;

FIG. 5 shows a detailed architectural diagram according to one embodiment of the application;

FIG. 6 illustrates a timing diagram of device synchronization and device querying according to one embodiment of the application;

FIG. 7 illustrates a timing diagram for device management according to one embodiment of the application;

FIG. 8 illustrates a timing diagram for in-cabinet device management according to one embodiment of the application;

FIG. 9 illustrates a timing diagram of operations performed by a front-end management console according to one embodiment of the present application;

FIG. 10 shows a schematic diagram of a second front-end page, according to one embodiment of the application;

FIG. 11 shows a schematic diagram of a device information query page, according to one embodiment of the application;

FIG. 12 shows a schematic diagram of a location configuration page, according to one embodiment of the application;

FIG. 13 shows a schematic diagram of a device page queried according to location according to one embodiment of the application;

FIG. 14 shows an overall flow diagram of device management according to one embodiment of the application.

FIG. 15 shows a schematic diagram of a fourth front-end page, according to one embodiment of the application;

FIG. 16 shows a schematic diagram of a query page for device relationship information, according to one embodiment of the application;

FIG. 17 shows a schematic diagram of a fifth front-end page, according to one embodiment of the application;

FIG. 18 shows a schematic diagram of a device-level relationship information query page, according to one embodiment of the application;

FIG. 19 shows an overall flow diagram of a device relationship configuration in accordance with one embodiment of the application;

FIG. 20 shows a schematic diagram of a third front-end page, according to one embodiment of the application;

FIG. 21 shows an overall flow diagram of a port configuration according to one embodiment of the application;

FIG. 22 shows a schematic diagram of a sixth front-end page, according to one embodiment of the application;

FIG. 23 shows a schematic diagram of a query page for inter-port connection information according to one embodiment of the application;

FIG. 24 shows a timing diagram of relationship management between devices according to one embodiment of the application;

FIG. 25 illustrates a timing diagram of device port connection management according to one embodiment of the application;

FIG. 26 illustrates a timing diagram for a large screen user accessing a front end large screen according to one embodiment of the application;

FIG. 27 shows a timing diagram for interaction with a page model through a front-end large screen, according to one embodiment of the application;

FIG. 28 shows a flowchart of steps followed by rendering a rendered target room model through a first front-end page display, according to one embodiment of the application;

FIG. 29 shows a schematic diagram of a brief information of a switch in a front-end large screen page, according to one embodiment of the application;

FIG. 30 shows a panel schematic of cabinet information according to one embodiment of the application;

FIG. 31 shows a schematic panel of equipment information in a machine room according to one embodiment of the application;

FIG. 32 shows a panel schematic of port connection information according to one embodiment of the application;

Fig. 33 shows a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the application may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.

The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.

FIG. 1 illustrates an overall functional architecture diagram according to one embodiment of the present application. Referring to fig. 1, the overall functional architecture diagram includes a large visualization screen, a worker Shan Yunwei, a machine room alarm, a data monitoring module, a model building module, a device basic information module, a machine room inspection module and other modules, wherein the large visualization screen module includes building visualization, floor visualization, room visualization, device visualization, port visualization, end connection and other sub-modules, the worker Shan Yunwei module includes an IT asset, abnormal alarm, work order report and other sub-modules, the machine room alarm module includes a movable ring alarm, a network alarm, a service alarm and other sub-modules, the data monitoring module includes an environment monitoring module, a power monitoring module and other sub-modules, and the model building module includes building modeling, 8F floor modeling, 803 machine room modeling, 803 device modeling, device port modeling and other sub-modules.

The embodiment of the application firstly provides a device management and control method based on digital twinning. The device management and control method based on digital twin provided by the embodiment of the application can realize device management and control based on the functional architecture diagram shown in fig. 1.

FIG. 2 illustrates a flow chart of a digital twinning-based device management and control method in accordance with one embodiment of the present application. Referring to fig. 2, the device control method based on digital twin at least includes the following steps:

step 240, displaying the rendered target room model through the first front-end page, wherein the target room model comprises at least one cabinet model.

And 250, displaying animation of opening a cabinet door of the target cabinet model on the first front-end page according to a selection instruction of the target cabinet model in the target room models displayed on the first front-end page, and displaying at least one equipment model in the target cabinet model.

Step 260, obtaining the identification information of the target equipment model according to the selection instruction of the target equipment model in the target equipment cabinet model displayed on the first front-end page.

And step 270, acquiring information corresponding to the target equipment according to the identification information of the target equipment model, and displaying a detail panel containing the information corresponding to the target equipment on the first front-end page.

Before describing the steps shown in fig. 2 in detail, the steps preceding step 240 are described.

Fig. 3 shows a flowchart of the details of steps before step 240 and step 270 in the embodiment of fig. 2, according to one embodiment of the application. Referring to fig. 3, before step 240, the following steps may be included:

In step 210, at least one device data monitored by the predetermined operation and maintenance platform is obtained by calling an interface provided by an entity configuration management database of the predetermined operation and maintenance platform.

The predetermined operation and maintenance platform may be IMOC (INTEGRATED MANAGEMENT Operations Center, integrated management operation center) system, and the entity configuration management database, i.e. eCMDB (Entity Configuration Management Database), is a core component of the IMOC system and is responsible for storing and managing all IT entities (such as hosts, services, interfaces, etc.) and their association relationships, so as to implement management and control of an IT service directory.

Fig. 4 shows a schematic architecture diagram according to an embodiment of the application. Referring to fig. 4, the architecture includes a large screen front end, a management platform front end, a digital twin background and a third party, where the third party includes IMOC systems, and further includes other systems such as a dynamic ring system, and the digital twin background includes a data monitoring module, an operation and maintenance module, an equipment module and a configuration module, where the equipment module is an equipment basic information module shown in fig. 1, and includes an equipment management sub-module, an asset management sub-module and a relationship management sub-module, and the equipment module is a module mainly related to an embodiment of the present application. The digital twin background can access a third party, the large screen front end can send a large screen request to the digital twin background, and the management platform front end can send a management platform request to the digital twin background.

Fig. 5 shows a detailed architectural diagram according to an embodiment of the present application. Referring to fig. 5, the difference between the embodiment of fig. 4 is that the architecture further includes an internet of things platform, that is, the machine room digital twin background actually interacts with the IMOC system, the moving ring system and the elite system through the internet of things platform, the internet of things platform can obtain device data from the IMOC system, obtain device performance index data from the elite system, and obtain environment data and energy consumption data from the moving ring system, and the machine room digital twin background interacts with the internet of things platform by calling device APIs and device index APIs of the internet of things platform; the machine room digital twin background can also interact with IMOC systems for work order information and alarm information.

The interface provided by the entity configuration management database may be, for example, a CI (Configuration Item ) interface, and the configuration item is a basic building block of the entity configuration management database, and represents an item that needs to be configured for management, such as a router, a server, an application program, a virtual machine, a container, and even a logical construct (such as a product combination).

The predetermined operation and maintenance platform can monitor the equipment so as to obtain corresponding equipment data. The device data monitored by the predetermined operation and maintenance platform can be device data of various types of devices such as storage devices, racks, frames, ports, network devices, physical servers, network devices, bare metal servers and the like. The device data may include a device identification (id), a device number, a device name, a device location, and the like. Wherein the device identifier is a table dimension unique id generated for the device inside the system. The device data may be pulled from the predetermined operation and maintenance platform periodically (e.g., every 24 hours).

In step 220, the device number in each device data is acquired.

The device data includes a device number. The device number is a unique number when device data is exchanged between systems.

In step 230, for each device number, if it is determined that there is no device information matching the device number in the local database, device information matching the device number is newly added in the local database according to the device data containing the device number.

One or more pieces of equipment information can be stored in the local database, and one piece of equipment information can be matched with one piece of acquired equipment information or can be not matched with any piece of acquired equipment information.

If a device information matches a device number, the device number may be included in the device information.

FIG. 6 illustrates a timing diagram for device synchronization and device querying according to one embodiment of the application.

Referring to fig. 6, a timing chart of the device synchronization phase includes the following procedures:

1. and sending a trigger signal to the device management submodule through the timing task.

2. The device management sub-module sends a request to the IMOC system to invoke the "query CI" interface of eCMDB.

3. The device management submodule obtains IMOC the device data returned by the system.

4. The device management submodule queries the device information in the local database according to the device number in the device data.

5. The device management sub-module obtains a return result of the local database.

6. If the equipment management sub-module determines that the equipment information matched with the equipment number does not exist in the local database according to the returned result, a request is sent to the local database so as to newly add the corresponding equipment information in the local database.

7. And the equipment management submodule receives response information returned by the database.

8. The device management sub-module returns corresponding response information to the timing task.

In one embodiment of the present application, before displaying the rendered target room model via the first front-end page, the method further comprises: acquiring equipment information configured by an administrator on equipment through a second front-end page; the device information is stored in a local database.

The second front-end page is the page provided by the management desk front-end.

Referring to fig. 4, a manager request may be sent to the digital twin backend through the manager front end, so that the manager manually configures the device.

Specifically, the management desk front end may provide a device management portal, a device relationship management portal, and a port configuration management portal, through which an administrator may perform configuration of device information through the device management portal.

Fig. 7 shows a timing diagram of device management according to one embodiment of the application. Referring to fig. 7, the timing chart includes the following steps:

1. the front end of the management desk calls the new, deleted, modified and inquired interfaces of the equipment provided by the equipment management module, so that corresponding equipment information is sent to the equipment management module or inquiry is requested to be carried out on a certain equipment.

2. The device management module sends instructions such as device addition, deletion, modification, inquiry and the like to the local database.

3. The local database returns corresponding response information to the device management module.

4. And the equipment management module returns corresponding response information to the front end of the management platform.

The administrator can also configure the equipment information of the equipment in one cabinet, so that only the equipment associated with one cabinet can be configured and queried, and the efficiency is improved; before the management of the equipment in the cabinet, the front end of the management platform needs to be used for configuring the corresponding cabinet information. FIG. 8 illustrates a timing diagram for in-cabinet device management according to one embodiment of the application. Referring to fig. 8, the timing chart includes the following steps:

1. The front end of the management desk calls an in-cabinet device new adding, deleting, modifying and inquiring interface provided by the in-cabinet device management module, so that corresponding device information is sent to the in-cabinet device management module or a certain device is requested to be inquired.

The in-cabinet device management module may be a sub-module of the device management module.

2. The in-cabinet device management module sends instructions such as adding, deleting, modifying, inquiring and the like to the local database.

3. And the local database returns corresponding response information to the in-cabinet device management module.

4. And the equipment management module in the cabinet returns corresponding response information to the front end of the management platform.

In one embodiment of the application, the device information is configured based on device information that is newly added to the local database based on device data monitored by the predefined operation and maintenance platform.

The administrator can configure the device information in the local database on the basis of the existing device information, such as editing the device information and adding new data items, so that the configuration efficiency and the configuration flexibility are improved, the device information can be checked secondarily, and errors are reduced.

FIG. 9 illustrates a timing diagram for operation by a front-end management console according to one embodiment of the present application. Referring to fig. 9, a manager user may perform operations such as inputting device, querying device, inputting relationship, querying relationship, etc. through the front-end manager, and it is easy to understand that inputting device and querying device are actually inputting device information and querying device information, and the inputting and querying of relationship will be described below. When the management platform user performs each operation through the front-end management platform, the front-end management platform needs to access the relevant page provided by the front-end management platform, the front-end management platform can call the corresponding interface provided by the equipment module, the equipment module can return the input or inquiry result to the front-end management platform, and finally the front-end management platform returns the result to the management platform user.

FIG. 10 shows a schematic diagram of a second front-end page, according to one embodiment of the application. Referring to fig. 10, the device information includes a plurality of information items, including a plurality of necessary information items, such as a device id, a service type, a device name, a device number, a device type, and the like; an administrator typically needs to configure each of the necessary information items; of course, the necessary information items can also be synchronized by a preset operation and maintenance platform, and the user only needs to edit part of the information items needing to be modified. The plurality of information items also comprise optional filling information items such as equipment height, maximum power, port number and the like, and a user can fill in according to requirements.

FIG. 11 shows a schematic diagram of a device information query page, according to one embodiment of the application. Referring to fig. 11, after completing the configuration of the device information, the administrator may also query the device information based on the information items such as the device type, the device name, the device number, and the like.

In one embodiment of the present application, before displaying the rendered target room model via the first front-end page, the method further comprises: and acquiring the position information configured by the administrator for the target equipment through the position configuration page.

FIG. 12 shows a schematic diagram of a location configuration page, according to one embodiment of the application. Referring to fig. 12, in the location configuration page, the device may be screened by the device type, name, model and number, then the information of the cabinet to which the device belongs is set, the cabinet number is selected, and finally the location of the cabinet to which the device belongs is set, including a start U bit and an end U bit. U-bit, a standard size inside the cabinet, is used to identify the vertical space inside the cabinet. A U (also referred to as a "unit") has a height of 1.75 inches (44.45 millimeters), which is the basic unit of measure of the vertical space inside the cabinet.

After the administrator configures the location of the device, the query of the device information may be performed according to the location. FIG. 13 shows a schematic diagram of a device page queried according to location according to one embodiment of the application. Referring to fig. 13, an administrator may input a cabinet number as a device location through the page, and then query location information of devices in the corresponding cabinets.

Next, a flow of device management is generally described. Referring to fig. 14, when an administrator requests to query a device (information) management list, a list shown in the page of fig. 11 is obtained; then, the system screens according to the conditions provided by the administrator, and if no request is successful, the system returns to the original step; if the request is successful, judging whether the acquired data number is more than 0; if not, displaying the empty list and ending; if yes, displaying a page of the equipment information list; when the administrator clicks an editing button or a new button in the page, an editing popup window is displayed, and when the administrator fills information in the editing popup window and clicks to determine, the system judges whether a value exists in a necessary filling item; if not, popping up a corresponding prompt, and enabling the administrator to continue filling in the information; if yes, requesting a corresponding interface, and ending after refreshing the device information list; if the administrator clicks a delete button in the page, the system pop-up window prompts the administrator whether to confirm deletion, if so, a corresponding delete interface is requested, and the process is finished after the equipment information list is refreshed; if the administrator does not delete, closing the prompt popup window and ending; when the administrator clicks a view button in the page, a device information popup window is displayed in the page, and the process is ended.

In one embodiment of the present application, before displaying the rendered target room model via the first front-end page, the method further comprises: acquiring port information configured by an administrator on a port of the equipment through a third front-end page, and storing the port information into a local database; acquiring equipment relation information configured by an administrator through a fourth front-end page, and storing the equipment relation information into a local database; acquiring equipment hierarchy relation information configured by an administrator through a fifth front-end page, and storing the equipment hierarchy relation information into a local database; and acquiring the inter-port connection information configured by the administrator through a sixth front-end page, and storing the inter-port connection information into a local database.

The device relationship information may be a connection relationship between switches, between switches and a firewall, between switches and a server, between switches and a storage device, and the like, for example, the connection relationship between switches may be cascade, stack, cluster, M-LAG, upstream and downstream, and the like, and the connection relationship between switches and a firewall may be interconnection.

FIG. 15 shows a schematic diagram of a fourth front-end page, according to one embodiment of the application. Referring to fig. 15, through the fourth front page, the administrator selects the relationship between devices, selects the devices having the relationship according to the device type, and then clicks the save to complete the configuration.

FIG. 16 shows a schematic diagram of a query page for device relationship information, according to one embodiment of the application. Referring to fig. 16, which shows a device relationship list in effect, an administrator may perform a query for device relationships by inputting device types, device relationships, and device names.

FIG. 17 shows a schematic diagram of a fifth front-end page, according to one embodiment of the application. Referring to fig. 17, a target switch needs to be configured for configuring a device hierarchy, and a switch device at the same level as the target switch and a device at a lower level of the target switch, where one of the devices at the same level or at the lower level may be empty. There may be a plurality of peer devices and subordinate devices. When a target switch is configured, its peer device and its subordinate device cannot be the same device.

FIG. 18 shows a schematic diagram of a device-level relationship information query page, according to one embodiment of the application. Referring to fig. 18, a list of device hierarchy information is actually shown, and an administrator may perform a query of the device hierarchy by inputting a device name, a device id, and the like.

FIG. 19 shows an overall flow diagram of a device relationship configuration in accordance with one embodiment of the application. Referring to fig. 19, the overall flow of the device relationship configuration is as follows: firstly, an administrator selects a relationship, wherein the relationship can be cascade, stack, cluster, M-LAG, uplink and downlink, interconnection and the like; then, selecting the corresponding device, adding or deleting the device, re-selecting the device type and the device after adding or deleting the device, and then clicking a save button by an administrator to complete the configuration of the device relation when the selection or deletion of the device is completed; then, the system judges whether all options in all pages have contents, if not, the system prompts corresponding information; if yes, requesting the corresponding interface to save; then, judging whether the interface responds successfully, if so, refreshing the list and ending, otherwise ending after prompting the error information.

The above operation process of selecting, deleting and adding the device type may specifically be: the host and the standby machines with the main-standby relation are respectively selected, the host equipment type is selected firstly, then the host is selected, then the standby machine equipment type is selected, the standby machine can be added or deleted, the standby machine equipment type and the standby machine are required to be selected again, and when the selection or deletion of the standby machine is completed, an administrator can click a storage button to complete equipment relation configuration.

FIG. 20 shows a schematic diagram of a third front-end page, according to one embodiment of the application. Referring to fig. 20, in the embodiment of the present application, the port of the device is an independent device, information such as a port number, a port id, etc. needs to be configured, when the information configuration of the port is performed through the third front-end page, the device needing to configure the port needs to be selected first, then the port id is selected by pulling down, and the port type and the port number are carried out after the selection; when the ports are configured, the number of the ports can be set in a self-defined mode, and the number of the ports, which is set by the equipment corresponding to the ports when the equipment is newly added, is not in forced association.

FIG. 21 shows an overall flow diagram of a port configuration according to one embodiment of the application. Referring to fig. 21, the overall flow of port configuration may be as follows, first, selecting a device type; then, selecting equipment, at the moment, acquiring a corresponding port list through a request interface, judging whether the interface is successful in response or not by the system, if so, prompting error information, and otherwise, displaying the port list corresponding to the equipment; then, the administrator performs data filling or selection at the port needing to be configured, and clicks a save button; the system can traverse and check whether the information corresponding to the filled configuration relation is perfect, if so, the corresponding information is prompted, otherwise, the interface is requested to store the information, and the process is finished.

FIG. 22 shows a schematic diagram of a sixth front-end page, according to one embodiment of the application. Referring to fig. 22, a sixth front-end page is used to perform port connection, that is, configuration of connection information between ports, specifically, a device type and a device name of a local device need to be selected, then, configuration of a local device port is performed by selecting a local device port number, and for each local device port, a peer device and a peer port number, a traffic type and a connection type are sequentially selected, where the traffic type may select interconnection, downlink, DAD, uplink, stacking, service, management, service/management, L3, peerlink, storage, BMC, etc., and the connection type may select 10GE optical fiber, 40GE optical fiber, 100GE optical fiber, RJ45, etc.

FIG. 23 shows a schematic diagram of a query page for inter-port connection information according to one embodiment of the application. Referring to fig. 23, what is actually shown is a list of port connections, and an administrator may query port connection information according to a port number, a device name, and a device id.

FIG. 24 shows a timing diagram of relationship management between devices according to one embodiment of the application. Referring to fig. 24, the flow of the management station operation is as follows:

1. the front end of the management desk calls configuration interfaces for adding, deleting, modifying and inquiring the relationships between the devices provided by the relationship management module between the devices.

The device-to-device relationship management module may belong to a device module.

2. The device relationship management module requests to add, delete and modify the device relationship to the local database.

3. And the inter-device relation management module receives response information returned by the local database.

4. And the inter-equipment relationship management module returns the received response information to the front end of the management platform.

In one embodiment of the present application, before the inter-port connection information configured by the administrator is acquired through the sixth front-end page, the method further includes: acquiring at least one port connection data monitored by a preset operation and maintenance platform by calling an interface provided by an entity configuration management database of the preset operation and maintenance platform; acquiring a device number and a port number in connection data of each port; for each port connection data, if it is determined that the inter-port connection information matched with the equipment number and the port number in the port connection data does not exist in the local database, the inter-port connection information matched with the equipment number and the port number in the port connection data is newly added in the local database according to the equipment data containing the equipment number; the obtaining, through the sixth front-end page, the inter-port connection information configured by the administrator includes: displaying the inter-port connection information in the local database in a sixth front-end page; and acquiring new inter-port connection information obtained by editing the inter-port connection information in the sixth front-end page by an administrator.

Fig. 25 shows a timing diagram of device port connection management according to one embodiment of the application. Referring to fig. 25, the flow of the port connection synchronization phase in the device port connection is as follows:

1. And sending a trigger signal to the port connection management module through the timing task.

The port connection management module may be part of the device module.

2. The port connection management module sends a request to IMOC systems to invoke the "query CI" interface of eCMDB.

3. The port connection management module obtains IMOC port connection data returned by the system.

4. And the port connection management module queries the port connection information in the local database according to the equipment number and the port number in the port connection data.

5. The port connection management module obtains a return result of the local database.

6. If the port connection management module determines that the port connection information matched with the equipment number and the port number does not exist in the local database according to the returned result, a request is sent to the local database so as to newly add the corresponding port connection information in the local database.

7. And the port connection management module receives response information returned by the database.

8. The port connection management module returns corresponding response information to the timing task.

With continued reference to fig. 25, the following phase of the port connection synchronization phase in the device port connection is as follows:

1. The front end of the management platform calls the port connection adding, deleting, modifying and inquiring interfaces provided by the port connection management module.

2. The port connection management module sends a request to the local database to perform operations such as adding, deleting, modifying, inquiring and the like of port connection.

3. And the port connection management module receives response information returned by the local database.

4. And the port connection management module returns corresponding response information to the front end of the management platform.

The following describes in detail the steps shown in fig. 2:

As shown in fig. 1, building, floor, machine room, equipment, ports and the like need to be modeled in advance, so that an administrator can be allowed to upload model files to the system, and dynamic configuration of the model is realized. The user of the large screen at the front end requests to log in the system, a first front end page is displayed, and the first front end page executes the following procedures:

1. Logging in the system.

2. A machine room building model appears.

3. Building animation transitions, enters the 8 th floor of the machine room, and positions the view angle to 803 rooms.

4. The mouse is moved to the rack (cabinet), and the rack model is highlighted and selected.

5. Clicking the rack (cabinet), highlighting the front view angle of the selected rack model, and automatically opening the cabinet door.

6. The frame model can be pulled up, pulled away and rotated.

7. The cursor is moved to the device on the rack, and the device model is highlighted.

8. Clicking on the device on the rack, the device is highlighted enlarged in the form of a drawer pop-up.

9. Clicking other devices, returning the last device to the original position, and popping up and amplifying the clicking device.

In an embodiment of the present application, after displaying at least one equipment model in the target cabinet model, the method further includes: according to a trigger instruction of a target equipment model in a target equipment cabinet model displayed on a first front-end page, acquiring equipment information, port information, equipment relation information, equipment hierarchy relation information and inter-port connection information associated with the target equipment model from a local database, and generating a topological relation diagram according to the equipment information, the port information, the equipment relation information, the equipment hierarchy relation information and the inter-port connection information associated with the target equipment model; and displaying the topological page in the first front-end page, and displaying the topological relation diagram in the topological page.

By displaying the topological relation diagram, a user can intuitively see the topological relation among the devices.

With continued reference to fig. 24, the front-end topology display phase is as follows:

1. the front end large screen calls an inter-device relationship query interface provided by the inter-device relationship management module.

2. The inter-device relationship management module queries the detail relationship among the devices in the local database.

3. The inter-device relationship management module receives the inter-device detailed relationship data returned by the local database.

4. And the inter-device relation management module returns the received inter-device detail relation data to the front-end large screen.

5. And the front-end large screen draws a topological graph according to the detail relation data among the devices.

When clicking the target equipment model, the target equipment model is enlarged, and the target equipment model is emphasized when the target equipment model is placed on the top layer of the screen and other models in the screen are all hidden or weakened.

With continued reference to fig. 3, step 270 may specifically include:

and 270', acquiring information corresponding to the target equipment from a local database according to the identification information of the target equipment model.

FIG. 26 illustrates a timing diagram for a large screen user accessing a front-end large screen according to one embodiment of the application. Referring to fig. 26, first, a large screen user requests an equipment module to query equipment related information and corresponding relation information of equipment by accessing a front end large screen, wherein the equipment related information includes information such as equipment information, equipment layout and the like, and the corresponding relation information of equipment is equipment port connection information; then, the equipment module returns a result to the front end large screen; and finally, displaying corresponding configuration information by the front-end large screen according to the returned result.

FIG. 27 shows a timing diagram for interaction with a page model through a front-end large screen, according to one embodiment of the application. Referring to fig. 27, when a user opens a large screen page, the large screen page requests a model component to render a model, and starts loading of the model; then, when the rendering of the model component is completed, the large screen page is instructed to cancel the loading of the model; next, the user selects the cabinet by means of mouse hovering (Hover); the model component triggers the cabinet highlighting operation in the large screen page and returns the ID of the selected cabinet to the large screen page; the large screen page acquires cabinet details according to the cabinet ID and displays a corresponding detail panel to a user; then, when a user clicks a cabinet rendered by the model component, the model component triggers the large screen page to switch the scene to a single cabinet, and returns an ID of the cabinet selected by clicking to the large screen page; the large screen page can hide charts positioned on the left side and the right side, and show chart panels of the selected cabinets to a user; when a user clicks equipment in a cabinet rendered by the model component, the large screen page can highlight the equipment in a pulling way, and an ID of the equipment selected by clicking is returned to the large screen page; and finally, displaying a corresponding equipment detail panel by the large screen page according to the ID of the equipment.

FIG. 28 shows a flowchart of steps followed by rendering the rendered target room model through the first front-end page display, according to one embodiment of the application. Referring to fig. 28, after the target room model rendered by the first front-end page display, the method further includes:

in step 2810, a device screening query entry is displayed through a first front-end page, the device screening query entry includes a cabinet number drop-down menu and a device number drop-down menu, the cabinet number drop-down menu includes cabinet numbers corresponding to each cabinet model in the target room model, and the device number drop-down menu includes device numbers corresponding to each device model in the target room model.

Step 2820, displaying the cabinet model corresponding to the cabinet number and the equipment model corresponding to the cabinet model and the equipment number on the first front-end page according to the cabinet number and the equipment number selected by the user in the cabinet number drop-down menu and the equipment number drop-down menu.

In the embodiment of the application, when the models of a room, a cabinet and the like are displayed on the first front-end page, a corresponding query entry can be directly provided for a front-end large-screen user, and the user can query by inputting corresponding information.

With continued reference to fig. 6, the timing diagram of the device query phase includes the following steps:

1. the front end invokes the device query interface provided by the device management sub-module.

2. The device management sub-module sends a request to the local database to query the local database for corresponding device data.

3. The device management sub-module obtains the device data returned by the local database.

4. The device management sub-module returns the device data to the front end.

Fig. 29 shows a schematic diagram of brief information of a switch in a front-end large screen page according to one embodiment of the application. The user can see the corresponding brief information without operating the device model. For example, referring to fig. 29, the front-end large screen page may show brief information of the switch.

In one embodiment of the application, after displaying at least one of the target rack models, the method further comprises: according to a trigger instruction for a first port model in target equipment models displayed on a first front-end page, popping the target equipment models from the target equipment models, displaying opposite-end models of equipment to which a second port model belongs, and displaying connecting lines between the second port model of the opposite-end models and the first port model of the target equipment models; and correspondingly displaying information related to the first port according to the position of the first port model in the first front-end page, and correspondingly displaying information related to the second port according to the position of the second port model.

The information related to the first port or the second port may include a port number, a port name, a port ID, a device name to which the port belongs, a cabinet number to which the device belongs, a port state, a port IP, a port type, and the like of the first port or the second port. The connection line is displayed, and meanwhile, the connection line types among ports such as 10GE optical fiber, 40GE optical fiber, 100GE optical fiber, RJ45 and the like and the traffic types among ports such as interconnection, downlink, DAD, uplink, stacking, service, management, service/management, L3, peerlink, storage, BMC and the like can be displayed.

In one embodiment of the application, the method further comprises: and displaying equipment classification summary information corresponding to the target room model through the first front-end page, wherein the equipment classification summary information is obtained by classifying and counting according to information corresponding to equipment in the target room model in a local database.

Fig. 30 shows a panel schematic of cabinet information according to one embodiment of the application. The panel shown in fig. 30 may be displayed next to the page when the user views the cabinet model of the front-end large screen display. A cabinet device layout table can be maintained to establish the relationship between cabinet devices and devices, and a device table is maintained to establish the relationship between devices and attributes. And finding the associated equipment ID from the equipment layout table through the equipment ID of the equipment, and analyzing and accumulating statistics from the equipment attribute field in the equipment table through the associated equipment ID so as to obtain the information shown in fig. 30.

Fig. 31 shows a schematic diagram of a panel of equipment information in a machine room according to an embodiment of the application. When the user views the machine room model displayed on the front-end large screen, the panel shown in fig. 31 may be displayed beside the page. The equipment table can be used for inquiring the equipment of each type according to the room number, and then the quantity of the equipment of each type is obtained by summarizing; the U bit number can be obtained by calculating the 'device occupied U bit/frame device total U bit', and the power can be obtained by calculating the 'device occupied power/frame device total power'.

FIG. 32 shows a panel schematic of port connection information according to one embodiment of the application. Referring to fig. 32, when the user clicks on a model of a certain port of the front-end large screen display, the panel may be displayed. The information in the panel can be obtained by querying a device port connection table, a port network index hour table and the like in a local database, and the configuration of the information in the device port connection table is described above and is not repeated here.

The digital twin-based equipment management and control system provided by the embodiment of the application is borne on the electronic equipment during operation.

It should be noted that, the computer system 3300 of the electronic device shown in fig. 33 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.

As shown in fig. 33, the computer system 3300 includes a central processing unit (Central Processing Unit, CPU) 3301, which can perform various appropriate actions and processes, such as performing the methods described in the above embodiments, according to a program stored in a read-only memory (ROM) 3302 or a program loaded from a storage section 3308 into a random access memory (Random Access Memory, RAM) 3303. In the RAM 3303, various programs and data required for system operation are also stored. The CPU 3301, ROM 3302, and RAM 3303 are connected to each other via a bus 3304. An Input/Output (I/O) interface 3305 is also connected to bus 3304.

The following components are connected to the I/O interface 3305: an input section 3306 including a keyboard, a mouse, and the like; an output section 3307 including a Cathode Ray Tube (CRT), a Liquid crystal display (Liquid CRYSTAL DISPLAY, LCD), and a speaker, etc.; a storage section 3308 including a hard disk or the like; and a communication section 3309 including a network interface card such as a LAN (Local Area Network ) card, a modem, or the like. The communication section 3309 performs communication processing via a network such as the internet. The drives 3310 are also connected to the I/O interface 3305 as required. A removable medium 3311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed in the drive 3310 so that a computer program read out therefrom is installed into the storage section 3308 as needed.

In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such embodiments, the computer program may be downloaded and installed from a network via the communications portion 3309, and/or installed from the removable media 3311. When executed by a Central Processing Unit (CPU) 3301, the computer programs perform the various functions defined in the system of the present application.

It should be noted that, the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (Erasable Programmable Read Only Memory, EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.

As an aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer-readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to implement the methods described in the above embodiments.

It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a touch terminal, or a network device, etc.) to perform the method according to the embodiments of the present application.

It will be appreciated that in particular embodiments of the present application, where data relating to image processing is involved, user approval or consent is required when the above embodiments of the present application are applied to particular products or technologies, and the collection, use and processing of the relevant data is required to comply with relevant legal regulations and standards in the relevant countries and regions.

Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains.

It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A digital twinning-based device management and control method, the method comprising:

Displaying a rendered target room model through a first front-end page, wherein the target room model comprises at least one cabinet model;

displaying an animation of opening a cabinet door of the target cabinet model on a first front-end page according to a selection instruction of the target cabinet model in the target room model displayed on the first front-end page, and displaying at least one equipment model in the target cabinet model;

Acquiring identification information of a target equipment model in the target equipment cabinet model according to a selection instruction of the target equipment model displayed on a first front-end page;

and acquiring information corresponding to the target equipment according to the identification information of the target equipment model, and displaying a detail panel containing the information corresponding to the target equipment on the first front-end page.

2. The digital twinning-based device management method of claim 1, wherein prior to displaying the rendered target room model via the first front-end page, the method further comprises:

Acquiring at least one piece of equipment data monitored by a preset operation and maintenance platform by calling an interface provided by an entity configuration management database of the preset operation and maintenance platform;

acquiring equipment numbers in the equipment data;

for each equipment number, if it is determined that no equipment information matched with the equipment number exists in a local database, newly adding the equipment information matched with the equipment number into the local database according to equipment data containing the equipment number;

The obtaining information corresponding to the target device according to the identification information of the target device model includes:

And acquiring information corresponding to the target equipment from the local database according to the identification information of the target equipment model.

3. The digital twinning-based device management method of claim 2, wherein prior to displaying the rendered target room model via the first front-end page, the method further comprises:

Acquiring equipment information configured by an administrator on equipment through a second front-end page;

and storing the equipment information into the local database.

4. The digital twinning-based device management method of claim 3, wherein the device information is configured based on device information newly added in a local database based on device data monitored by a predetermined operation and maintenance platform.

5. A digital twinning-based device management method in accordance with claim 3, wherein prior to displaying the rendered target room model via the first front-end page, the method further comprises:

Acquiring port information configured by an administrator on a port of the equipment through a third front-end page, and storing the port information into a local database;

Acquiring equipment relation information configured by an administrator through a fourth front-end page, and storing the equipment relation information into a local database;

Acquiring equipment hierarchy relation information configured by an administrator through a fifth front-end page, and storing the equipment hierarchy relation information into a local database;

acquiring inter-port connection information configured by an administrator through a sixth front-end page, and storing the inter-port connection information into a local database;

after displaying at least one of the target rack models, the method further comprises:

According to a trigger instruction of a target equipment model in the target equipment cabinet model displayed on a first front-end page, equipment information, port information, equipment relation information, equipment hierarchy relation information and inter-port connection information associated with the target equipment model are obtained from the local database, and a topological relation diagram is generated according to the equipment information, the port information, the equipment relation information, the equipment hierarchy relation information and the inter-port connection information associated with the target equipment model;

and displaying a topology page in the first front-end page, and displaying the topological relation diagram in the topology page.

6. The digital twinning-based device management method of claim 5, wherein before obtaining the inter-port connection information configured by the administrator through the sixth front-end page, the method further comprises:

Acquiring at least one port connection data monitored by a preset operation and maintenance platform by calling an interface provided by an entity configuration management database of the preset operation and maintenance platform;

Acquiring a device number and a port number in each port connection data;

for each port connection data, if it is determined that the inter-port connection information matched with the equipment number and the port number in the port connection data does not exist in the local database, adding the inter-port connection information matched with the equipment number and the port number in the port connection data in the local database according to the equipment data containing the equipment number;

the obtaining, by the sixth front-end page, the inter-port connection information configured by the administrator includes:

displaying the inter-port connection information in the local database in the sixth front-end page;

And acquiring new inter-port connection information obtained by editing the inter-port connection information in the sixth front-end page by an administrator.

7. The digital twinning-based device management method of claim 1, wherein after displaying the rendered target room model via the first front-end page, the method further comprises:

displaying an equipment screening query entry through the first front-end page, wherein the equipment screening query entry comprises an equipment cabinet number pull-down menu and an equipment number pull-down menu, the equipment cabinet number pull-down menu comprises equipment cabinet numbers corresponding to all equipment models in a target room model, and the equipment number pull-down menu comprises equipment numbers corresponding to all equipment models in the target room model;

and displaying a cabinet model corresponding to the cabinet number and an equipment model corresponding to the equipment number on the first front-end page according to the cabinet number and the equipment number selected by the user from the cabinet number drop-down menu and the equipment number drop-down menu.

8. The digital twinning-based equipment management method of claim 5, wherein after displaying at least one of the target rack models, the method further comprises:

according to a trigger instruction of a first port model in target equipment models in the target equipment models displayed on a first front-end page, popping the target equipment models out of the target equipment models, displaying an opposite-end model of equipment to which a second port model belongs, and displaying a connecting line between the second port model of the opposite-end model and the first port model of the target equipment model;

and correspondingly displaying information related to a first port according to the position of the first port model in the first front-end page, and correspondingly displaying information related to a second port according to the position of the second port model.

9. The digital twinning-based device management method of claim 2, further comprising:

and displaying equipment classification summary information corresponding to the target room model through a first front-end page, wherein the equipment classification summary information is obtained by classifying and counting information corresponding to equipment in the target room model in the local database.

10. A digital twinning-based device management and control system, comprising:

one or more processors;

Storage means for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the digital twinning-based device management method of any one of claims 1 to 8.