Cable management platform, cable management system and cable management method

Abstract

The application discloses a cable management platform, a cable management system and a cable management method. The cable overview module in the cable management platform can display cable information in response to a selection operation on a cable overview option in a cable management interface. In response to a selection operation on target cable information in the cable information, if the login account belongs to a city-level account, the distribution of the target cable information at the city level is displayed on a map. If the login account belongs to a province-level account, the distribution of the target cable information at the province level is displayed on the map. That is, the cable management platform can display information of the region to which the login account belongs according to the region to which the login account belongs, so that the city-level account and the province-level account can log in to the same cable management platform, thereby improving the flexibility of cable management at the city level and the province level.

Description

Technical Field

[0001] This application relates to the field of computers, specifically to a cable management platform, a cable management system, and a cable management method. Background Technology

[0002] As the primary medium for power transmission and distribution, cables can be laid underground, thus not occupying surface space, and have become the main form of power transmission in modern cities. However, because cables are laid in underground spaces, the environment is complex and prone to generating harmful gases, making it difficult to detect and control accidents in a timely manner. Therefore, cable management is necessary.

[0003] Currently, different cable management platforms are used at the provincial and municipal levels, resulting in low flexibility in cable management. Summary of the Invention

[0004] This application aims to at least partially address one of the technical problems in related technologies. To this end, one objective of this application is to propose a cable management platform, a cable management system, and a cable management method. The cable management platform can display cable information in response to a selection operation of the cable overview option in the cable management interface. Furthermore, in response to a selection operation of target cable information within the cable information, if the logged-in account belongs to a prefecture-level city, the distribution of target cable information at the prefecture-level city level is displayed on a map; if the logged-in account belongs to a provincial-level city, the distribution of target cable information at the provincial-level city is displayed on a map. That is, the cable management platform can display the distribution of target cable information corresponding to the region to which the logged-in account belongs, thereby enabling prefecture-level and provincial-level accounts to log in to the same cable management platform, thus improving the flexibility of cable management at both the prefecture-level and provincial levels.

[0005] On the one hand, a cable management platform is provided, which includes an interface display module and a cable overview module, both of which are microservices;

[0006] The interface display module is used to display the cable management interface corresponding to the login account. The login account can be a city-level account or a provincial-level account. The cable management interface should include at least a cable overview option.

[0007] The cable overview module is used for:

[0008] In response to a selection action for the cable overview option, cable information is displayed, including at least one of equipment information, channel information, line information, and abnormal status.

[0009] In response to the selection operation of target cable information in the cable information, if the login account belongs to the prefecture-level account, the distribution of target cable information in the prefecture-level account will be displayed on the map; if the login account belongs to the provincial account, the distribution of target cable information in the provincial account will be displayed on the map.

[0010] Optional cable overview module, used for:

[0011] In response to a selection operation for the cable overview option, a function layer is displayed, which includes at least one of the following: device layer, channel layer, line layer, and abnormal status layer;

[0012] In response to a selection operation on a target function layer in the function layer, display the cable information in the target function layer;

[0013] The equipment layer includes different types of equipment, the channel layer includes different types of channels, the line layer includes different cable lines, and the abnormal status layer includes different types of abnormal statuses.

[0014] Optionally, there can be multiple target cable information entries. The cable overview module is also used for:

[0015] In response to a selection operation for one of multiple target cable information, basic information of the target cable is displayed.

[0016] The basic information for a target cable includes at least the location of the target cable.

[0017] Optionally, the cable management interface also includes: anomaly status statistics options; the cable management platform also includes: anomaly status statistics module, which is used for:

[0018] In response to the selection of an abnormal status statistics option, the abnormal status information statistics area is displayed;

[0019] Receive target anomaly status, target route, and target time period in the information statistics area;

[0020] In response to statistical commands for target anomalies, if the logged-in account is a prefecture-level account, the trend of target anomalies located on the target route within the prefecture-level city is displayed during the target time period; if the logged-in account is a provincial account, the trend of target anomalies located on the target route within the provincial province is displayed during the target time period.

[0021] Optionally, the cable management interface also includes: cable statistics options; the cable management platform also includes: a cable statistics module, which is a microservice; the cable statistics module is used for:

[0022] In response to the selection of cable statistics options, if the login account belongs to the prefecture-level city level, the statistical information of the first target unit in the prefecture-level city level will be displayed in the cable statistics area; if the login account belongs to the provincial level, the statistical information of the first target unit in the provincial level will be displayed in the cable statistics area.

[0023] The first target unit includes equipment, channels, or lines, and the statistical information includes at least the total number of the first target units.

[0024] Optionally, the cable management interface also includes: visualization options; the cable management platform also includes: a visualization module, which is a microservice; the visualization module is used for:

[0025] In response to a selection action for a visualization function option, the visualization function area is displayed;

[0026] In response to a selection operation for a target historical video received in the visualization function area, the target historical video is played in the visualization function area;

[0027] In response to an adjustment operation on the target camera, at least one of the following is adjusted: light intake, shooting range, and focus of the target camera.

[0028] Optionally, the cable management interface also includes: cable ledger options and cable management options; the cable management platform also includes: cable ledger module and cable management module, both of which are microservices;

[0029] The cable ledger module is used to respond to the selection operation of the cable ledger option. If the login account belongs to the prefecture-level account, the ledger data of the second target unit in the prefecture-level account will be displayed in the ledger function area. If the login account belongs to the provincial account, the ledger data of the second target unit in the provincial account will be displayed in the ledger function area.

[0030] The cable management module is used to respond to the selection operation of cable management options. If the login account belongs to the prefecture-level account, the operation and maintenance data of the third target unit in the prefecture-level account will be displayed in the cable management function area. If the login account belongs to the provincial account, the operation and maintenance data of the third target unit in the provincial account will be displayed in the cable management function area.

[0031] Both the second and third target units include equipment, channels, or lines.

[0032] Optionally, the cable management platform also includes: a data entry module, which is a microservice; the data entry module is used for:

[0033] Receive application data, which includes ledger-type data, operation and maintenance data, or online monitoring data;

[0034] If the application data is detected to be accurate, then the application data is stored.

[0035] If an anomaly is detected in the application data, a notification message will be sent.

[0036] Optionally, the data entry module is also used for:

[0037] Determine the storage template for the application data based on the type of application data and the object to which the application data belongs;

[0038] Application data is stored based on storage templates.

[0039] Optionally, the data entry module is also used for:

[0040] After receiving the application data, the verification rules for the application data are determined based on the type of application data and the object to which the application data belongs.

[0041] If the application data does not conform to the verification rules, it is determined that the application data is abnormal;

[0042] If the application data conforms to the verification rules, then the application data is considered accurate.

[0043] On the other hand, a cable management system is provided, including the cable management platform described above.

[0044] On the other hand, a cable management method is provided for use in a cable management platform, the method including:

[0045] Display the cable management interface corresponding to the logged-in account. The logged-in account can be a city-level account or a provincial-level account. The cable management interface should include at least a cable overview option.

[0046] In response to a selection action for the cable overview option, cable information is displayed, including at least one of equipment information, channel information, line information, and abnormal status.

[0047] In response to the selection operation of target cable information in the cable information, if the login account belongs to the prefecture-level account, the distribution of target cable information in the prefecture-level account will be displayed on the map; if the login account belongs to the provincial account, the distribution of target cable information in the provincial account will be displayed on the map.

[0048] Optionally, in response to a selection action for the cable overview option, display cable information, including:

[0049] In response to a selection operation for the cable overview option, a function layer is displayed, which includes at least one of the following: device layer, channel layer, line layer, and abnormal status layer;

[0050] In response to a selection operation on a target function layer in the function layer, display the cable information in the target function layer;

[0051] The equipment layer includes different types of equipment, the channel layer includes different types of channels, the line layer includes different cable lines, and the abnormal status layer includes different types of abnormal statuses.

[0052] Optionally, there may be multiple target cable information items, and the method may also include:

[0053] In response to a selection operation for one of multiple target cable information, basic information of the target cable is displayed.

[0054] The basic information for a target cable includes at least the location of the target cable.

[0055] Optionally, the cable management interface may also include: anomaly status statistics options; methods may also include:

[0056] In response to the selection of an abnormal status statistics option, the abnormal status information statistics area is displayed;

[0057] Receive target anomaly status, target route, and target time period in the information statistics area;

[0058] In response to statistical commands for target anomalies, if the logged-in account is a prefecture-level account, the trend of target anomalies located on the target route within the prefecture-level city is displayed during the target time period; if the logged-in account is a provincial account, the trend of target anomalies located on the target route within the provincial province is displayed during the target time period.

[0059] Optionally, the cable management interface also includes: cable statistics options, and the methods also include:

[0060] In response to the selection of cable statistics options, if the login account belongs to the prefecture-level city level, the statistical information of the first target unit in the prefecture-level city level will be displayed in the cable statistics area; if the login account belongs to the provincial level, the statistical information of the first target unit in the provincial level will be displayed in the cable statistics area.

[0061] The first target unit includes equipment, channels, or lines, and the statistical information includes at least the total number of the first target units.

[0062] Optionally, the cable management interface may also include: visualization options; methods may also include:

[0063] In response to a selection action for a visualization function option, the visualization function area is displayed;

[0064] In response to a selection operation for a target historical video received in the visualization function area, the target historical video is played in the visualization function area;

[0065] In response to an adjustment operation on the target camera, at least one of the following is adjusted: light intake, shooting range, and focus of the target camera.

[0066] Optionally, the cable management interface may also include: cable ledger options and cable management options; methods may also include:

[0067] In response to the selection operation for the cable ledger option, if the login account belongs to the prefecture-level account, the ledger data of the second target unit in the prefecture-level account will be displayed in the ledger function area; if the login account belongs to the provincial account, the ledger data of the second target unit in the provincial account will be displayed in the ledger function area.

[0068] In response to the selection operation for cable management options, if the login account belongs to the prefecture-level account, the operation and maintenance data of the third target unit in the prefecture-level account will be displayed in the cable management function area; if the login account belongs to the provincial account, the operation and maintenance data of the third target unit in the provincial account will be displayed in the cable management function area.

[0069] Both the second and third target units include equipment, channels, or lines.

[0070] Optionally, the method also includes:

[0071] Receive application data, which includes ledger-type data, operation and maintenance data, or online monitoring data;

[0072] If the application data is detected to be accurate, then the application data is stored.

[0073] If an anomaly is detected in the application data, a notification message will be sent.

[0074] Optionally, store application data, including:

[0075] Determine the storage template for the application data based on the type of application data and the object to which the application data belongs;

[0076] Application data is stored based on storage templates.

[0077] Optionally, after receiving application data, the method may also include:

[0078] Determine the validation rules for the application data based on the type of application data and the object to which the application data belongs;

[0079] If the application data does not conform to the verification rules, it is determined that the application data is abnormal;

[0080] If the application data conforms to the verification rules, then the application data is considered accurate.

[0081] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0082] Figure 1 This is a schematic diagram of a cable management platform provided in an embodiment of this application;

[0083] Figure 2 This is a schematic diagram of a cable management platform provided in an embodiment of this application;

[0084] Figure 3 This is a schematic diagram of a cable management interface provided in an embodiment of this application;

[0085] Figure 4 This is a schematic diagram of another cable management interface provided in an embodiment of this application;

[0086] Figure 5 This is a schematic diagram of yet another cable management interface provided in an embodiment of this application;

[0087] Figure 6 This is a schematic diagram of another cable management interface provided in an embodiment of this application;

[0088] Figure 7 This is a schematic diagram of another cable management interface provided in an embodiment of this application;

[0089] Figure 8 This is a schematic diagram of another cable management interface provided in an embodiment of this application;

[0090] Figure 9 This is a schematic diagram of another cable management interface provided in an embodiment of this application;

[0091] Figure 10 This is a schematic diagram of another cable management interface provided in an embodiment of this application;

[0092] Figure 11 This is a schematic diagram of a cable management system provided in an embodiment of this application;

[0093] Figure 12 This is a schematic diagram of another cable management interface provided in an embodiment of this application;

[0094] Figure 13 This is a schematic diagram of another cable management interface provided in an embodiment of this application;

[0095] Figure 14 This is a flowchart of another cable management method provided in the embodiments of this application;

[0096] Figure 15 This is a flowchart illustrating an application method for a cable management platform provided in an embodiment of this application;

[0097] Figure 16 This is a flowchart of another application method of the cable management platform provided in the embodiments of this application. Detailed Implementation

[0098] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0099] Figure 1 This is a schematic diagram of a cable management platform provided in an embodiment of this application, as shown below. Figure 1 As shown, the cable management platform may include an interface display module 100 and a cable overview module 200, both of which are microservices.

[0100] The interface display module 100 is used to display the cable management interface corresponding to the login account.

[0101] Optionally, upon receiving a login request, the cable management platform can display a cable management interface corresponding to the login account. The login request may include the login account, which can be a city-level or provincial-level account. The cable management interface must at least include a cable overview option.

[0102] Cable overview module 200, used for:

[0103] In response to the selection of the cable overview option, cable information is displayed, which may include at least one of equipment information, channel information, line information, and abnormal status.

[0104] In response to the selection operation of target cable information in the cable information, if the login account belongs to the prefecture-level account, the distribution of target cable information at the prefecture-level can be displayed on the map; if the login account belongs to the provincial account, the distribution of target cable information at the provincial level can be displayed on the map.

[0105] In summary, this application provides a cable management platform. The cable overview module within this platform can display cable information in response to the selection of a cable overview option in the cable management interface. Furthermore, it can respond to the selection of target cable information within the cable information. If the logged-in account belongs to a prefecture-level city, the distribution of target cable information at the prefecture-level city level is displayed on the map; if the logged-in account belongs to a provincial-level city, the distribution of target cable information at the provincial level is displayed on the map. That is, the cable management platform can display the distribution of target cable information corresponding to the region to which the logged-in account belongs, thereby allowing prefecture-level and provincial-level accounts to log in to the same cable management platform, thus improving the flexibility of cable management at the prefecture-level city and provincial levels.

[0106] refer to Figure 2 The cable management platform may also include a login module 300 and a verification module 400. The login module 300 can receive a login account and password on the login interface. The login interface can display an account input box, a password input box, and a login button. The login module 300 receives the login account in the account input box and the login password in the password input box. After receiving a selection operation for the login button, it can send a login request to the verification module 400. After successfully verifying the login account and password, the verification module 400 sends a display command to the interface display module 100. Upon receiving the display command, the interface display module 100 displays the cable management interface corresponding to the login account.

[0107] In this embodiment, the cable management interface may include at least a cable overview option. After the interface display module 100 displays the cable management interface, the cable overview module 200 may display a function layer in response to the selection operation of the cable overview option.

[0108] The functional layers can include at least one of the following: device layers, channel layers, line layers, and abnormal status layers. Device layers can include different types of devices, channel layers can include different types of channels, line layers can include different cable lines, and abnormal status layers can include different types of abnormal statuses.

[0109] Optionally, different types of equipment may include cable connectors, cable terminals, and online monitoring devices. For example, online monitoring devices may include temperature sensors, humidity sensors, gas detection sensors, and cameras. Gas detection sensors may include oxygen detection sensors, carbon monoxide detection sensors, methane detection sensors, and hydrogen sulfide detection sensors.

[0110] Different types of channels can include: tunnels, pipes, cable trenches, manholes, cable firewalls, cable bridges, cable terminal stations, and ventilation openings. Different types of abnormal states can include defects, hidden dangers, malfunctions, and alarms. Hidden dangers can include fire hazards, flood hazards, overheating hazards, external damage hazards, abnormal auxiliary equipment hazards, and hazardous gas hazards. Abnormal states can refer to abnormal conditions of equipment, channels, or cable lines.

[0111] refer to Figure 3 The cable management interface may include a cable overview option 10. After receiving a selection operation for the cable overview option 10, the cable overview module 200 may display a cable overview option 11, and then, in response to the selection operation for the cable overview option 11, display a device layer 110, a channel layer 111, an abnormal status layer 112, and a line layer 113.

[0112] In this embodiment of the application, after receiving a selection operation for a target functional layer in the functional layer, the cable overview module 200 can display cable information in the target functional layer in response to the selection operation for the target functional layer.

[0113] If the target function layer includes a device layer, the cable overview module 200 can display multiple different types of devices after receiving a selection operation for the device layer. Optionally, the cable overview module 200 can display the names of multiple different types of devices.

[0114] refer to Figure 3 After receiving a selection operation for device layer 110, cable overview module 200 can display temperature 110a, humidity 110b, oxygen 110c and methane 110d.

[0115] If the target function layer includes a channel layer, the cable overview module can display multiple different types of channels after receiving a selection operation for the channel layer.

[0116] refer to Figure 4 After receiving a selection operation for channel layer 111, the cable overview module 200 can display tunnel 111a, pipe 111b, cable trench 111c and manhole 111d.

[0117] If the target function layer includes an abnormal status layer, the cable overview module 200 can display multiple different types of abnormal statuses after receiving a selection operation for that abnormal status layer.

[0118] refer to Figure 5The cable overview module 200 can display defects 112a, hazards 112b, faults 112c and alarms 112d in response to a selection operation for the abnormal status layer 112.

[0119] If the target function layer includes a line layer, the cable overview module can display multiple different cable lines after receiving a selection operation for the line layer.

[0120] The multiple different cable lines may include new cable lines and old cable lines, where the service life of the old cable lines is greater than the preset service life, and the service life of the new cable lines is less than the preset service life.

[0121] In this embodiment of the application, after displaying cable information, the cable overview module 200 can respond to the selection operation of target cable information in the cable information. If the login account belongs to the city-level account, the distribution of target cable information at the city level can be displayed on the map. If the login account belongs to the provincial-level account, the distribution of target cable information at the provincial level can be displayed on the map.

[0122] Example, reference Figure 5 and Figure 6 After receiving a selection operation for defect 112a, the cable overview module 200 can display the distribution of defect 112a on the map if the logged-in account belongs to the city-level account. Figure 6 The distribution of the four defects 112a at the prefecture-level city level is shown on the map.

[0123] In this embodiment, there can be multiple target cable information. The cable overview module 200 can display the basic information of the target cable information in response to the selection operation of one of the multiple target cable information.

[0124] The basic information for a target cable may include at least its location. If the cable information includes a line or channel, the basic information for a target cable may include at least its start and end points. If the cable information includes abnormal conditions, the basic information for a target cable may include at least the location where the abnormal condition occurs, and may also include the total number and percentage of such abnormal conditions.

[0125] Optionally, after receiving a selection operation for a target cable information, the cable overview module 200 can display basic information options in the details interface. The cable management platform can respond to the selection operation for the basic information options and display the basic information of a target cable.

[0126] refer to Figure 7If a target cable information includes the cable line, the basic data for that target cable information may also include information such as voltage level, phase, maintenance team, cable type, total cable length, and maintenance unit. For example, the voltage level could be 110 kV, the phase could be ABC, the cable type could be cross-linked polyethylene, and the total cable length could be 2790 km.

[0127] If a target cable information includes a tunnel, the basic data of that target cable information may include the tunnel code, tunnel name, city where the tunnel is located, tunnel operation and maintenance unit, tunnel commissioning date, tunnel length, number of conduits, number of manholes, and tunnel status.

[0128] If the target cable information is in an abnormal state, the basic information of the target cable information may at least include the location of the abnormal state. Optionally, the basic information of the target cable information may also include the equipment to which the abnormal state belongs.

[0129] Optionally, the cable overview module 200 can respond to a selection operation for one of a plurality of target cable information and can also display information related to a target cable information.

[0130] If the target cable information includes cable lines, then the information related to a target cable line may include statistical information on the devices located on that target cable line, statistical information on the channels, and statistical information on abnormal states. Specifically, the device statistics may include the total number of devices located on that target cable line. The channel statistics may include the total number of channels located on that target cable line, as well as the number of different channels. The abnormal state statistics may include the total number of abnormal states located on that target cable line, as well as the number of different types of abnormal states.

[0131] refer to Figure 7 The cable overview module 200 can also display options for cable joints, cable terminations, and online monitoring devices. In response to a selection operation for the cable joint option, the cable overview module 200 can display statistical information about the cable joints located on that target cable information (cable line); in response to a selection operation for the cable termination option, it can display statistical information about the cable terminations located on that target cable information (cable line); and in response to a selection operation for the online monitoring device option, it can display statistical information about the online monitoring devices located on that target cable information (cable line).

[0132] The statistics for the cable joints should include at least the total number of cable joints located on the target cable (cable line). The statistics for the cable terminals should include at least the total number of cable terminals located on the target cable (cable line). The statistics for the online monitoring devices should include at least the total number of online monitoring devices located on the target cable (cable line).

[0133] refer to Figure 2 The cable management platform may also include an abnormal status statistics module 500, and the cable management interface may also include an abnormal status statistics option. The abnormal status statistics module 500 may display an abnormal status information statistics area in response to the selection operation of the abnormal status statistics option.

[0134] refer to Figure 8 The cable management interface may also include a cable statistics option 20. After receiving a selection operation for the cable statistics option 20, the abnormal status statistics module 500 can display the abnormal status statistics option 21 and, in response to the selection operation for the abnormal status statistics option 21, display the abnormal status information statistics area.

[0135] After displaying the information statistics area for abnormal status, the abnormal status statistics module 500 can receive the target abnormal status, target line, and target time period in the information statistics area.

[0136] refer to Figure 8 The information statistics area may include a status selection box 210, a line selection box 211, and a time period selection box 212. The abnormal status statistics module 500 can receive the input target abnormal status in the status selection box 210, the target line in the line selection box 211, and the target time period in the time period selection box 212. For example, the target abnormal status may include a fire hazard.

[0137] Optionally, the status selection box 210 may include a drop-down button. After receiving a selection operation for the drop-down button, the abnormal status statistics module 500 may display multiple abnormal statuses, and after receiving a selection operation for a target abnormal status among the multiple abnormal statuses, display the target abnormal status in the display area of ​​the status selection box 210.

[0138] The time period selection box 212 may include a start time selection box and an end time selection box. The abnormal state statistics module 500 can receive the target start time from the start time selection box and the target end time from the end time selection box, thereby obtaining the target time period based on the target start time and the target end time.

[0139] refer to Figure 8The information statistics area may also include a query button 213 for the target abnormal status. After receiving the target abnormal status, target route, and target time period of the target abnormal status from the information statistics area, the abnormal status statistics module 500 can generate a statistical instruction for the target abnormal status if it receives a selection operation for the query button 213. The abnormal status statistics module 500 can then respond to this statistical instruction. If the logged-in account is a city-level account, it can display the changing trend of the target abnormal status located on the target route within the city-level account during the target time period. If the logged-in account is a provincial-level account, it can display the changing trend of the target abnormal status located on the target route within the provincial-level account during the target time period.

[0140] Optionally, the information statistics area may include a trend display area, in which the abnormal status statistics module 500 can display the changing trend of the target abnormal status located on the target line during the target time period.

[0141] The target time period can include multiple times. The abnormal status statistics module 500 can determine the total number of target abnormal statuses located on the target line at each time, and then display the changing trend of the total number of target abnormal statuses located on the target line at multiple times.

[0142] In this embodiment, the abnormal status statistics module 500 can also display relevant information about the target abnormal status located on the target line within a target time period. This relevant information may include the sequence number of the target abnormal status, the line to which it belongs, the discovery time, the type of the target abnormal status, the description of the target abnormal status, and the handling status.

[0143] refer to Figure 8 If the target abnormal state includes a hidden danger, the relevant information may include the hidden danger number, the line to which the hidden danger belongs, the time of discovery of the hidden danger, the type of hidden danger, the description of the hidden danger, and the status of the handling of the hidden danger.

[0144] For example, the hazard number can be 101, the line it belongs to can be line A, the hazard discovery time can be 2021-3-10, the hazard type can be fire, and the hazard handling status can be handled.

[0145] Optionally, the abnormal status statistics module 500 can also display the reason for each target abnormal status in the information statistics area.

[0146] refer to Figure 2 and Figure 9The cable management platform may also include a cable statistics module 600. The cable statistics module 600 can respond to the selection operation of the cable statistics option 20. If the login account belongs to the prefecture-level account, the statistical information of the first target unit in the prefecture-level account can be displayed in the cable statistics area. If the login account belongs to the provincial account, the statistical information of the first target unit in the provincial account can be displayed in the cable statistics area.

[0147] The first target unit may include equipment, channels or lines, and the statistical information of the first target unit may include at least the total number of the first target units.

[0148] refer to Figure 9 Cable statistics option 20 may also include cable line statistics option 22. Cable statistics module 600 may include a cable line statistics module, which, in response to a selection operation for cable line statistics option 22, displays statistical information about the cable lines in the cable statistics area. This cable line statistical information may further include the total number of cable lines, the total length of multiple cable lines, the number of overloaded lines, the trend of cable length changes for different voltage levels, a statistical chart of the number of cables set in multiple channels, and a statistical chart of the cable length of multiple cable lines.

[0149] refer to Figure 9 The cable line statistics module can display the total length of cable lines (box 220), the total number of cable lines (box 221), the number of overloaded cable lines (box 222), and a statistical chart (box 223) of the lengths of multiple cable lines in the cable statistics area. Specifically, the total length of cable lines (box 220) can be displayed as 33259 km, the total number of cable lines (box 221) as 9, and the number of overloaded cable lines (box 222) as 0.

[0150] refer to Figure 9 The statistical chart 223 showing the lengths of multiple cable lines can be a bar chart. The horizontal axis of the chart can be the cable lines, which may include three cable lines from A to C. The vertical axis can be the total length of the cable lines.

[0151] refer to Figure 9Cable statistics option 20 may further include online monitoring equipment statistics option 23, and the cable statistics area may further include an online detection equipment statistics area. The cable statistics module 600 may further include an online monitoring equipment statistics module. The online monitoring equipment statistics module can receive online monitoring equipment of a target type from the online monitoring equipment statistics area and can display the statistical information of the online monitoring equipment of that target type. The statistical information of the online monitoring equipment of the target type may also include the operating years of the online monitoring equipment of the target type and the growth trend of the number of online monitoring equipment of that target type.

[0152] If there are multiple online monitoring devices of the target type, the service life of these devices can be the longest service life among them. For example, the online monitoring devices of this target type may include temperature sensors.

[0153] refer to Figure 10 The cable management interface may also include a visualization function option 30, and the cable management platform may also include a visualization function module 700. The visualization function module 700 may display a visualization function area in response to a selection operation for the visualization function option 30, and play the target historical video in the visualization function area in response to a selection operation for the target historical video received in the visualization function area.

[0154] Optionally, the visualization function area may also include a first selection box 310 for the camera and a video selection box 311. After the visualization function module 700 selects a reference camera in the first selection box 310, it displays historical videos taken by the reference camera in multiple historical time periods in the video selection box 311. Then, after selecting a target historical video from the multiple historical videos, the target historical video can be played in the video display area 312 of the visualization function area.

[0155] In this embodiment of the application, the visualization function module 700 can adjust at least one of the light intake, shooting range and focus of the target camera in response to the adjustment operation of the target camera.

[0156] refer to Figure 10The visualization function area can also display a second selection box 313 for the camera, where the cable management platform can select the target camera. Furthermore, the visualization function area can also display an aperture adjustment area 314, a zoom adjustment area 315, and a focus adjustment area 316. Each of the aperture adjustment area 314, zoom adjustment area 315, and focus adjustment area 316 has increase and decrease buttons. The visualization function module 700 can increase the amount of light entering the target camera in response to selecting the increase button in the aperture adjustment area 314, and decrease the amount of light entering the target camera in response to selecting the decrease button in the aperture adjustment area 314.

[0157] The visualization module 700 can expand the shooting range of the target camera in response to the selection operation of the increase button in the zoom adjustment area 315, and reduce the shooting range of the target camera in response to the selection operation of the decrease button in the zoom adjustment area 315.

[0158] The visualization module 700 can magnify the focus of the target camera in response to the selection operation of the increase button in the focus adjustment area 316, and defocus the target camera in response to the selection operation of the increase button in the focus adjustment area 316.

[0159] refer to Figure 2 The cable management platform may also include a data entry module 800, which can receive application data, including ledger-type data, operation and maintenance data, or online monitoring data. If the application data is detected to be accurate, the data entry module 800 can store the application data. If an anomaly is detected in the application data, the data entry module 800 can send a prompt message to indicate that the application data is abnormal.

[0160] The ledger data can include equipment ledger data, channel ledger data, and cable line ledger data. For example, cable line ledger data can include the cable's voltage level, phase, cable number, cable grade, cable type, and total length. Online monitoring equipment ledger data can include the online monitoring equipment's number, installation location, and the data collected by the online monitoring equipment.

[0161] Operation and maintenance data can include inspection records, fault records, defect records, and potential hazard records. Online monitoring data can include data detected by online monitoring equipment, the time of data detection, and the identification number of the online monitoring equipment.

[0162] Optionally, the inspection record may include the inspection number, cable line name, cable voltage level, inspection scope, inspection content, inspection type, maintenance team, maintenance unit, inspection cycle, last inspection completion time, and remarks. The fault record may include the fault number, fault display, fault description, time of fault occurrence, cable voltage level, fault location, fault category, line where the fault occurred, and fault handling results.

[0163] Defect records can include defect number, defect display, cable voltage level, defect description, location of defect, person who discovered the defect, work team that handled the defect, and time of handling the defect.

[0164] Hazard records may include hazard number, the line where the hazard is located, the voltage level of the cable, the method of discovery, the location of the hazard, the city where the hazard is located, the maintenance team to which the hazard belongs, the type of hazard, the level of the hazard, the source of the hazard, the equipment affected by the hazard, a description of the hazard, the person who discovered the hazard, the department of the person who discovered the hazard, the date of discovery of the hazard, and a photo of the hazard.

[0165] refer to Figure 11 The cable management platform 01 can establish communication connections with online monitoring equipment 02, mobile terminal 03, and business system 04, and can receive application data sent by the online monitoring equipment, mobile terminal, and business system. The business system may include a plant management system (PMS), an outage management system (OMS), and an energy management system (EMS).

[0166] The online monitoring device 02 is used to send online monitoring data to the cable management platform 01. The mobile terminal 03 is used to send operation and maintenance data to the cable management platform 01. This business system is used to send online monitoring data, operation and maintenance data, and ledger data to the cable management platform 01.

[0167] In this embodiment of the application, if the data entry module 800 detects that the application data is accurate, it can determine the storage template of the application data based on the type of the application data and the object to which the application data belongs, and store the application data based on the storage template.

[0168] The types of application data can include ledgers, operation and maintenance, and online monitoring, and the objects to which the application data belongs can include equipment, cable lines, and channels.

[0169] The cable management platform may also include a storage module, which can be a database within the application management platform. The storage module can pre-store a first correspondence between data types, the objects to which the data belongs, and storage templates. After confirming the accuracy of the application data, the data entry module 800 can retrieve the first correspondence from the storage module and, based on the application data type and the object to which the application data belongs, determine the storage template corresponding to the application data type and the object to which the application data belongs from the first correspondence, and store the application data based on the storage template.

[0170] Optionally, if the type of application data is ledger type and the object to which the application data belongs is cable line, the storage template of the application data can be as shown in Table 1. The storage template of the application data can include cable number, voltage level, cable type, total cable length, starting position and ending position.

[0171] Table 1

[0172]

[0173] Understandably, referring to Table 1 above, if the application data only includes cable number: 101, voltage level: 35KV, cable type: oil-immersed, then the data entry module 800 stores the application data according to the storage template, with the cable number: 101, voltage level: 35KV, cable type: oil-immersed, and the total cable length, start position, and end position all empty.

[0174] If the application data includes: cable number: 102, voltage level: 110KV, cable type: cross-linked polyethylene, total cable length: 1000, then the data entry module 800 can store the application data according to the storage template: cable number: 102, voltage level: 110KV, cable type: cross-linked polyethylene, total cable length: 1000, with the start and end positions both empty.

[0175] For application data of the same object sent from different cities, the cable management platform can use a unified storage template to store the application data, ensuring the uniformity of application data storage for the same object.

[0176] In this embodiment, after receiving application data, the data entry module 800 can determine the verification rules for the application data based on the type of the application data and the object to which the application data belongs. If the application data does not conform to the verification rules, it can be determined that the application data is abnormal; if the application data conforms to the verification rules, it can be determined that the application data is accurate.

[0177] The storage module can pre-store the second correspondence between the data type, the object to which the data belongs, and the verification rules. After receiving the application data, the data entry module 800 retrieves the second correspondence from the storage module, and determines the verification rules corresponding to the application data type and the object to which the application data belongs from the second correspondence based on the application data type and the object to which the application data belongs, and determines whether the application data is accurate based on the verification rules.

[0178] Optionally, if the application data is of the ledger type and the object to which the application data belongs is a cable line, the verification rule for the application data can be that the voltage level is within a preset voltage range. For example, this preset voltage range can be 0KV-2000KV. The data entry module 800 can detect whether the voltage level in the application data is within the preset voltage range. If the voltage level is within the preset voltage range, the application data is considered accurate. If the voltage level in the application data is outside the preset voltage range, the application data is considered abnormal.

[0179] For example, if the voltage level in the application data is 35KV, the preset voltage range can be 0KV-2000KV. Since 35KV is within the range of 0KV-2000KV, the cable management platform can determine that the application data is accurate.

[0180] If the application data type is operation and maintenance type, and the object to which the application data belongs is a cable line, then the verification rule for the application data can be: the voltage level is equal to the preset voltage range.

[0181] If the application data type is online monitoring, and the object to which the application data belongs is an online monitoring device (such as a temperature sensor), then the verification rule for the application data can be that the value detected by the online monitoring device is within a preset value range. The cable management platform can detect whether the value in the application data is within the preset value range. If the value is within the preset value range, the application data can be determined to be accurate. If the value in the application data is equal to or outside the preset value range, the application data can be determined to be abnormal.

[0182] For example, the online monitoring equipment may include a partial discharge detector, a grounding monitor, an oxygen sensor, a hydrogen sulfide sensor, a methane sensor, a carbon monoxide sensor, and a liquid level sensor. The partial discharge detector may detect data including the A-phase discharge quantity and A-phase discharge frequency. The grounding monitor may detect data including the grounding current. The oxygen sensor may detect data including oxygen concentration, and the hydrogen sulfide sensor may detect data including hydrogen sulfide concentration. The methane sensor may detect data including methane concentration, and the carbon monoxide sensor may detect data including carbon monoxide concentration. The liquid level sensor may detect the liquid level value. The upper limit of the preset range corresponding to the carbon monoxide concentration may be 30 mg / m³.

[0183] The cable management interface may also include cable ledger options and cable management options, see reference. Figure 2 The cable management platform may include a cable ledger module 900 and a cable management module 1000. The cable ledger module 900, in response to selection of cable ledger options, can display the ledger data of the second target unit within the city-level account in the ledger function area if the logged-in account is at the prefecture-level; and can display the ledger data of the second target unit within the province-level account in the ledger function area if the logged-in account is at the provincial level. The second target unit may include equipment, channels, or lines.

[0184] refer to Figure 12 The cable ledger option 40 may include cable line ledger option 41, channel ledger option 42, and online monitoring equipment ledger option 43. The cable ledger module 900 responds to the selection operation for cable line ledger option 41. If the login account belongs to the prefecture-level account, the ledger data of cable lines in the prefecture-level account can be displayed in the ledger function area. If the login account belongs to the provincial account, the ledger data of cable lines in the provincial account can be displayed in the ledger function area.

[0185] The cable line ledger data may include cable line ledger data, cable section ledger data, cable joint ledger data, cable terminal ledger data, cable branch box ledger data, and cable cross-connection box ledger data, etc.

[0186] The ledger function area may include cable line option 410, cable segment option 412, cable joint option 413, cable termination option 414, and cable grounding box option 415. (Reference) Figure 11 The cable ledger module 900 can display the ledger data of the cable line in response to the selection operation of the cable line option 410.

[0187] The cable ledger module 900 can display the ledger data for cable segments in response to the selection operation of cable segment option 412. The cable ledger module 900 can display the ledger data for cable joints in response to the selection operation of cable joint option 413. The cable ledger module 900 can display the ledger data for cable terminals in response to the selection operation of cable termination option 414. The cable ledger module 900 can display the ledger data for cable grounding boxes in response to the selection operation of cable grounding box option 415.

[0188] In this embodiment, the cable ledger module 900 responds to the selection operation for the channel ledger option 42. If the logged-in account belongs to a prefecture-level city, the ledger data for prefecture-level channels can be displayed in the ledger function area. If the logged-in account belongs to a provincial-level city, the ledger data for provincial-level channels can be displayed in the ledger function area. The channel ledger data may include tunnel ledger data, pipeline ledger data, and manhole ledger data, etc.

[0189] The cable ledger module 900 responds to the selection operation for the ledger options of online monitoring equipment. If the login account belongs to the prefecture-level account, the ledger data of online monitoring equipment at the prefecture-level account can be displayed in the ledger function area. If the login account belongs to the provincial account, the ledger data of online monitoring equipment at the provincial level can be displayed in the ledger function area.

[0190] refer to Figure 2 and Figure 13 The cable management module 1000 can respond to the selection operation of cable management option 50. If the login account belongs to the prefecture-level account, the operation and maintenance data of the third target unit in the prefecture-level account can be displayed in the cable management function area. If the login account belongs to the provincial account, the operation and maintenance data of the third target unit in the provincial account can be displayed in the cable management function area. The third target unit may include equipment, channels, or lines.

[0191] refer to Figure 13 Cable management option 50 may include cable fault management option 51, cable hazard management option 52, cable defect management option 53, cable alarm management option 54, and cable inspection management option 55.

[0192] The cable management functional area may include a cable operation and maintenance management area, a cable fault management area, a cable hidden danger management area, a cable defect management area, a cable alarm management area, and a cable inspection management area.

[0193] In response to the selection operation for cable fault management option 51, cable management module 1000 displays fault registration option, fault handling option, and fault query option in the cable fault management area.

[0194] The cable management module 1000 can respond to the selection of fault registration options. If the login account belongs to the prefecture-level city level, fault information of the third target unit in the prefecture-level city level can be registered in the cable fault management function area. If the login account belongs to the provincial level, fault information of the third target unit in the provincial level can be registered in the cable fault management function area.

[0195] The cable management module 1000 can respond to the selection of fault handling options. If the login account is a city-level account, the fault handling results of the third target unit at the city level can be uploaded in the cable fault management function area. If the login account is a provincial-level account, the fault handling results of the third target unit at the provincial level can be uploaded in the cable fault management function area.

[0196] The cable management module 1000 can respond to the selection of fault query options. If the login account belongs to the prefecture-level city level, the fault information of the third target unit in the prefecture-level city level can be queried in the cable fault management function area. If the login account belongs to the provincial level, the fault information of the third target unit in the provincial level can be queried in the cable fault management function area.

[0197] refer to Figure 13 In response to the selection operation of cable hazard management option 52, cable management module 1000 displays hazard registration option 520, hazard approval option 521, hazard handling option 522 and hazard query option 523 in the cable hazard management area.

[0198] The cable management module 1000 can respond to the selection operation of the hazard registration option 530. If the login account belongs to the prefecture-level account, the hazard record of the third target unit in the prefecture-level account can be registered in the cable hazard management function area. If the login account belongs to the provincial account, the hazard record of the third target unit in the provincial account can be registered in the cable hazard management function area.

[0199] refer to Figure 13 The hazard record can include the hazard number, hazard ID, line name, channel name, voltage level, city / prefecture, and how the hazard was discovered.

[0200] Optionally, the cable management module 1000 can also receive newly added hazard data in the cable hazard management function area.

[0201] The cable management module 1000 can also respond to the selection operation of the hazard approval option 531. If the login account belongs to the prefecture-level account, the approval option of the hazard of the third target unit in the prefecture-level account can be displayed in the cable hazard management function area. If the login account belongs to the provincial account, the approval option of the hazard of the third target unit in the provincial account can be displayed in the cable hazard management function area, which makes it easier for the reviewer to approve the hazard.

[0202] The cable management module 1000 can respond to the selection operation of the hazard handling option 532. If the login account belongs to the prefecture-level account, the handling status of the hazard in the third target unit of the prefecture-level account can be displayed in the cable hazard management function area. If the login account belongs to the provincial account, the handling status of the hazard in the third target unit of the provincial account can be displayed in the cable hazard management function area.

[0203] The cable management module 1000 can respond to the selection operation of the hidden danger query option 533. If the login account belongs to the prefecture-level account, the hidden dangers of the third target unit in the prefecture-level account can be queried in the cable hidden danger management function area. If the login account belongs to the provincial account, the hidden dangers of the third target unit in the provincial account can be queried in the cable hidden danger management function area.

[0204] In response to the selection operation for cable defect option 53, cable management module 1000 displays defect registration options, defect handling options, and defect query options in the cable fault management area.

[0205] The cable management module 1000 can respond to the selection of defect registration options. If the login account belongs to the prefecture-level city level, defect information of the third target unit at the prefecture-level city level can be registered in the cable defect management function area. If the login account belongs to the provincial level, defect information of the third target unit at the provincial level can be registered in the cable defect management function area.

[0206] The cable management module 1000 can respond to the selection of defect handling options. If the login account is a municipal-level account, the defect handling results of the third target unit at the municipal level can be uploaded in the cable defect management function area. If the login account is a provincial-level account, the defect handling results of the third target unit at the provincial level can be uploaded in the cable defect management function area.

[0207] The cable management module 1000 can respond to the selection of defect query options. If the login account belongs to the prefecture-level city level, the defect information of the third target unit at the prefecture-level city level can be queried in the cable defect management function area. If the login account belongs to the provincial level, the defect information of the third target unit at the provincial level can be queried in the cable defect management function area.

[0208] In response to the selection operation for cable alarm option 54, the cable management module 1000 can display alarm records of the third target unit at the city level in the cable alarm management function area if the login account belongs to the city level. If the login account belongs to the provincial level, it can display alarm records of the third target unit at the provincial level in the cable alarm management function area.

[0209] The cable management module 1000 can respond to the cable inspection management option 55 and display the inspection cycle maintenance option, inspection plan option, and inspection task maintenance option in the cable inspection management area.

[0210] The cable management module 1000 can respond to the selection of maintenance options for the inspection cycle. If the logged-in account is a municipal-level account, the inspection cycle maintenance list of the third target unit at the municipal level can be displayed in the cable inspection management interface. If the logged-in account is a provincial-level account, the inspection cycle maintenance list of the third target unit at the provincial level can be displayed in the cable inspection management interface.

[0211] The maintenance list for this inspection cycle may include: order number, voltage level, line name, inspection scope, inspection content, inspection type, maintenance team, maintenance unit, inspection cycle, cycle unit, last inspection completion time and remarks.

[0212] The cable management module 1000 can respond to the selection of inspection plan options. If the logged-in account is a prefecture-level account, it can display the inspection plan list of the third target unit at the prefecture-level in the cable inspection management interface. If the logged-in account is a prefecture-level account, it can display the inspection plan list of the third target unit at the provincial level in the cable inspection management interface.

[0213] The inspection plan list may include inspection order number, overdue reminder, planned inspection time, voltage level, line name, inspection type, inspection scope, maintenance unit, maintenance team, inspection content, plan status, and remarks.

[0214] The cable management module 1000 can respond to the selection of maintenance options for inspection tasks. If the logged-in account is a city-level account, it can display the inspection task maintenance list of the third target unit at the city level in the cable inspection management interface. If the logged-in account is a city-level account, it can display the inspection task maintenance list of the third target unit at the provincial level in the cable inspection management interface. This inspection task maintenance list can include the order number, reminder status, task type, voltage level, line name, inspection type, maintenance team, maintenance unit, planned inspection time, actual inspection time, task status, reason for overdue status, and status.

[0215] In this embodiment, the cable management platform may further include a live-line detection management module, an emergency management module, and a power supply management module.

[0216] In this embodiment, the interface display module 100, cable overview module 200, login module 300, verification module 400, abnormal status statistics module 500, cable statistics module 600, visualization function module 700, data entry module 800, cable ledger module 900, and cable management module 1000 can all be microservices. Any two of these modules can communicate with each other using a lightweight communication mechanism, and each module can be independently deployed in the cable management platform.

[0217] Optionally, any two modules can communicate with each other based on the representational state transfer application programming interface (REST API) of the Hypertext Transfer Protocol (HTTP).

[0218] refer to Figure 14 The interface display module 100 may include an interface display submodule 101 and an interface aggregation submodule 102, and the cable overview module 200 may include a cable overview display submodule 201 and a cable overview aggregation module 202.

[0219] The abnormal status statistics module 500 may include a status statistics display submodule 501 and a status statistics aggregation submodule 502; the cable statistics module 600 may include a cable statistics display submodule 601 and a cable statistics aggregation submodule 602; the visualization function module 700 may include a visualization display submodule 701 and a visualization aggregation submodule 702; the cable ledger module 900 may include a cable ledger display submodule 901 and a cable ledger aggregation submodule 902; and the cable management module 1000 may include a cable management display submodule 10001 and a cable management aggregation submodule 1002.

[0220] This cable management platform may include a presentation layer, a service layer, and a data storage layer. (Reference) Figure 14 The presentation layer may include interface display submodule 101, cable overview display submodule 201, login module 300, status statistics display submodule 501, cable statistics display submodule 601, visualization display submodule 701, cable ledger display submodule 901 and cable management display submodule 10001.

[0221] The service layer may include a data forwarding module 001, an interface aggregation submodule 102, a cable overview aggregation submodule 202, a verification module 400, a status statistics aggregation submodule 502, a cable statistics aggregation submodule 602, a visualization aggregation submodule 702, a cable ledger aggregation submodule 902, and a cable management aggregation submodule 1002.

[0222] The data storage layer may include database 002. The modules included in the presentation layer, service layer, and data storage layer can all be microservices. As a result, the front-end and back-end of the cable management platform can be designed, developed, and deployed separately, enabling adaptive display on both desktop and mobile devices. It can be deployed independently, improving reusability.

[0223] For each of the following submodules: interface display submodule 101, cable overview display submodule 201, login module 300, status statistics display submodule 501, cable statistics display submodule 601, visualization display submodule 701, cable ledger display submodule 901, and cable management display submodule 10001, the submodule can send an interface retrieval request to the corresponding submodule in the service layer through the data forwarding module 001. The submodule in the service layer can retrieve data from the database and generate an interface based on the retrieved data, and then send the interface to the submodule through the data forwarding module 001 so that the submodule can display the interface.

[0224] Optionally, after receiving the display instruction sent by the verification module 400, the interface display submodule 201 can send an interface acquisition request to the interface aggregation module 102 through the data forwarding module 001. After receiving the request sent by the interface display submodule 101, the interface aggregation submodule 102 can retrieve data from the database and generate a cable management interface based on the retrieved data, and then send the cable management interface to the interface display submodule 201 for display through the data forwarding module 001.

[0225] In this embodiment, the data in the database may include structured data, unstructured data, cached data, and microservice runtime logs, which can be stored on different servers. The cached data stores user tokens and login account-related information; the structured data stores the relational data tables required by each module; and the unstructured data stores related images, reports, and standard documents generated from defects, potential problems, faults, and inspection tasks. The microservice runtime logs are stored in an Elasticsearch server, thereby improving retrieval efficiency.

[0226] The cable management platform may also include a process engine module, which is a microservice. This process engine module provides basic services for workflow operations and provides process engine services for each microservice.

[0227] In this embodiment, the cable management platform may further include: a public report module, a standard library retrieval module, and a file operation module. These modules are all microservices. During the interface generation process, the aforementioned aggregation sub-modules can also use the public report module to generate query conditions for tables and dynamically display the tables.

[0228] During the interface generation process, the aforementioned aggregation sub-modules can also utilize the standard library retrieval module to perform functions such as searching and displaying files related to hazard mitigation and defect handling. Furthermore, the file operation module allows for uploading, downloading, and browsing of stored files.

[0229] In this application, each module of the cable management platform is a microservice, thereby mitigating the risks associated with monolithic architectures in large and medium-sized project development. These modules exhibit high cohesion, low coupling, and single responsibility; each module can operate independently while also communicating with other modules, improving the reliability and scalability of the cable management platform and facilitating the processing, integration, and display of cables at the city and provincial levels. Communication between services is achieved through a combination of REST API patterns or RPC frameworks, event streams, and message brokers, realizing a lightweight communication mechanism for inter-service collaboration.

[0230] Furthermore, this microservice offers advantages such as rapid deployment and startup, weak application coupling, strong fault tolerance, convenient management, simple maintenance, and immediate effectiveness without requiring service restarts. The unavailability of a single server or microservice can be quickly handled through disaster recovery without affecting the overall system robustness.

[0231] This application employs distributed log tracing to improve the observability of system logs, facilitating rapid problem location and real-time monitoring of the cable management platform's operation.

[0232] In summary, this application provides a cable management platform that displays cable information in response to the selection of a cable overview option in the cable management interface. Furthermore, in response to the selection of target cable information within the cable information, if the logged-in account belongs to a prefecture-level city, the platform displays the distribution of target cable information at the prefecture-level city level on a map; if the logged-in account belongs to a provincial-level city, the platform displays the distribution of target cable information at the provincial level on a map. That is, the cable management platform can display the distribution of target cable information corresponding to the region to which the logged-in account belongs, thereby allowing prefecture-level and provincial-level accounts to log in to the same cable management platform, thus improving the flexibility of cable management at both the prefecture-level and provincial levels.

[0233] Figure 15This is a flowchart of an application method for a cable management platform provided in an embodiment of this application, such as... Figure 15 As shown, the method may include:

[0234] Step 1501: Display the cable management interface corresponding to the logged-in account.

[0235] Login accounts can be city-level or provincial-level accounts, and the cable management interface should include at least a cable overview option.

[0236] Step 1502: In response to the selection operation for the cable overview option, display cable information.

[0237] Cable information includes at least one of the following: equipment information, channel information, line information, and abnormal status.

[0238] Step 1503: In response to the selection operation of target cable information in the cable information, if the login account belongs to the prefecture-level account, the distribution of target cable information in the prefecture-level account will be displayed on the map; if the login account belongs to the provincial account, the distribution of target cable information in the provincial account will be displayed on the map.

[0239] In summary, this application provides an application method for a cable management platform. The cable management platform can display cable information in response to the selection of a cable overview option in the cable management interface. Furthermore, in response to the selection of target cable information within the cable information, if the logged-in account belongs to a prefecture-level city, the distribution of target cable information at the prefecture-level city level is displayed on the map; if the logged-in account belongs to a provincial-level city, the distribution of target cable information at the provincial level is displayed on the map. That is, the cable management platform can display the distribution of target cable information corresponding to the region to which the logged-in account belongs, thereby allowing prefecture-level and provincial-level accounts to log in to the same cable management platform, thus improving the flexibility of cable management at both the prefecture-level and provincial levels.

[0240] Figure 16 This is a flowchart of an application method for a cable management platform provided in an embodiment of this application, such as... Figure 16 As shown, the method may include:

[0241] Step 1601: Display the cable management interface corresponding to the logged-in account.

[0242] The cable management platform can display a cable management interface corresponding to the login account, which can be a city-level account or a provincial-level account. The cable management interface should include at least a cable overview option.

[0243] Step 1602: In response to the selection operation for the cable overview option, display the function layer.

[0244] The cable management platform can display functional layers in response to selections made for cable overview options. These functional layers include at least one of the following: equipment layer, channel layer, line layer, and abnormal status layer. Specifically, the equipment layer includes different types of equipment, the channel layer includes different types of channels, the line layer includes different cable lines, and the abnormal status layer includes different types of abnormal statuses.

[0245] Step 1603: In response to the selection operation of the target function layer in the function layer, display the cable information in the target function layer.

[0246] The cable management platform can display cable information in the target functional layer in response to a selection operation of the target functional layer.

[0247] Optionally, there may be multiple target cable information entries. The cable management platform can respond to a selection operation for one of the multiple target cable information entries and display the basic information of that target cable information. The basic information of a target cable information entry includes at least the location of that target cable.

[0248] Step 1604: In response to the selection operation of target cable information in the cable information, if the login account belongs to the prefecture-level account, the distribution of target cable information in the prefecture-level account is displayed on the map; if the login account belongs to the provincial account, the distribution of target cable information in the provincial account is displayed on the map.

[0249] Step 1605: In response to the selection operation for the abnormal status statistics option, display the abnormal status information statistics area.

[0250] Step 1606: Receive the target abnormal status, target route, and target time period in the information statistics area.

[0251] Step 1607: In response to the statistical command for the target abnormal status, if the logged-in account belongs to the prefecture-level city level, the trend of the target abnormal status located on the target route in the prefecture-level city level is displayed during the target time period; if the logged-in account belongs to the provincial level, the trend of the target abnormal status located on the target route in the provincial level is displayed during the target time period.

[0252] Optionally, the cable management interface also includes: cable statistics options. The cable management platform can also respond to the selection operation of the cable statistics options. If the login account belongs to the prefecture-level account, the statistical information of the first target unit in the prefecture-level account will be displayed in the cable statistics area. If the login account belongs to the provincial account, the statistical information of the first target unit in the provincial account will be displayed in the cable statistics area.

[0253] The first target unit includes equipment, channels, or lines, and the statistical information includes at least the total number of the first target units.

[0254] Optionally, the cable management interface also includes: visualization function options; the cable management platform can also display a visualization function area in response to a selection operation for the visualization function options, and play the target historical video in the visualization function area in response to a selection operation for the target historical video received in the visualization function area. In response to an adjustment operation for the target camera, at least one of the target camera's light intake, shooting range, and focus can be adjusted.

[0255] Optionally, the cable management interface also includes: a cable ledger option and a cable management option. In response to the selection of the cable ledger option, if the logged-in account is a city-level account, the ledger data for the second target unit within the city-level account will be displayed in the ledger function area; if the logged-in account is a provincial-level account, the ledger data for the second target unit within the province will be displayed in the ledger function area. Similarly, in response to the selection of the cable management option, if the logged-in account is a city-level account, the operation and maintenance data for the third target unit within the city-level account will be displayed in the cable management function area; if the logged-in account is a provincial-level account, the operation and maintenance data for the third target unit within the province will be displayed in the cable management function area. Both the second and third target units include equipment, channels, or lines.

[0256] Optionally, the cable management platform can also receive application data, including ledger data, operation and maintenance data, or online monitoring data. If the application data is detected to be accurate, it will be stored; if an anomaly is detected, a prompt message will be sent.

[0257] Optionally, the cable management platform can determine the storage template for the application data based on the type of application data and the object to which the application data belongs, and store the application data based on the storage template.

[0258] Optionally, after receiving the application data, the cable management platform can also determine the verification rules for the application data based on its type and the object to which it belongs. If the application data does not conform to the verification rules, it is determined that the application data is abnormal. If the application data conforms to the verification rules, it is determined that the application data is accurate.

[0259] It should be noted that the specific implementation methods of steps 1501 to 1502 and steps 1601 to 1607 above can be referred to the above embodiment of the cable management platform, and will not be repeated here.

[0260] In summary, this application provides an application method for a cable management platform. The cable management platform can display cable information in response to the selection of a cable overview option in the cable management interface. Furthermore, in response to the selection of target cable information within the cable information, if the logged-in account belongs to a prefecture-level city, the distribution of target cable information at the prefecture-level city level is displayed on the map; if the logged-in account belongs to a provincial-level city, the distribution of target cable information at the provincial level is displayed on the map. That is, the cable management platform can display the distribution of target cable information corresponding to the region to which the logged-in account belongs, thereby allowing prefecture-level and provincial-level accounts to log in to the same cable management platform, thus improving the flexibility of cable management at both the prefecture-level and provincial levels.

[0261] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0262] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0263] In the description of this specification, the references to terms such as "optional," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0264] Furthermore, the terms "first," "second," etc., used in the embodiments of this application are for descriptive purposes only and should not be construed as indicating or implying relative importance, or implicitly specifying the number of technical features indicated in this embodiment. Therefore, features defined with terms such as "first" and "second" in the embodiments of this application can explicitly or implicitly indicate that the embodiment includes at least one of those features. In the description of this application, the word "multiple" means at least two or more, such as two, three, four, etc., unless otherwise explicitly and specifically defined in the embodiments.

[0265] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A cable management platform, characterized in that, The cable management platform includes an interface display module and a cable overview module, both of which are microservices. The interface display module is used to display the cable management interface corresponding to the login account. The login account includes a city-level account or a provincial-level account. The cable management interface includes at least a cable overview option. The cable overview module is used for: In response to a selection operation for the cable overview option, cable information is displayed, which includes at least one of equipment information, channel information, line information, and abnormal status. In response to the selection operation of target cable information in the cable information, if the login account belongs to the prefecture-level account, the distribution of the target cable information in the prefecture-level account is displayed on the map; if the login account belongs to the provincial account, the distribution of the target cable information in the provincial account is displayed on the map. The cable management interface also includes an abnormal status statistics option; the cable management platform also includes an abnormal status statistics module, which is a microservice; the abnormal status statistics module is used for: In response to the selection of the abnormal state statistics option, the information statistics area of ​​the abnormal state is displayed; The information statistics area receives the target's abnormal status, target route, and target time period. In response to a statistical command for the target abnormal status, if the login account belongs to the prefecture-level city, the trend of the target abnormal status located on the target route in the prefecture-level city is displayed in the target time period; if the login account belongs to the provincial level, the trend of the target abnormal status located on the target route in the provincial level is displayed in the target time period.

2. The cable management platform according to claim 1, characterized in that, The cable overview module is used for: In response to a selection operation for a cable overview option, a functional layer is displayed, the functional layer including at least one of a device layer, a channel layer, a line layer, and an abnormal status layer; In response to a selection operation for a target function layer in the function layers, the cable information in the target function layer is displayed; The device layer includes different types of devices, the channel layer includes different types of channels, the line layer includes different cable lines, and the abnormal status layer includes different types of abnormal statuses.

3. The cable management platform according to claim 1, characterized in that, The target cable information includes multiple cables, and the cable overview module is also used for: In response to a selection operation for one of the multiple target cable information, basic information of the target cable is displayed. The basic information of a target cable includes at least the location of the target cable.

4. The cable management platform according to any one of claims 1 to 3, characterized in that, The cable management interface also includes a cable statistics option, and the cable management platform also includes a cable statistics module, which is a microservice; the cable statistics module is used for: In response to the selection operation for the cable statistics option, if the login account belongs to the prefecture-level account, the statistical information of the first target unit in the prefecture-level account is displayed in the cable statistics area; if the login account belongs to the provincial account, the statistical information of the first target unit in the provincial account is displayed in the cable statistics area. The first target unit includes a device, channel, or line, and the statistical information includes at least the total number of the first target units.

5. The cable management platform according to any one of claims 1 to 3, characterized in that, The cable management interface also includes: a visualization function option; the cable management platform also includes: a visualization function module, which is a microservice; the visualization function module is used for: In response to a selection operation for the visualization function options, the visualization function area is displayed; In response to a selection operation for a target historical video received in the visualization function area, the target historical video is played in the visualization function area; In response to an adjustment operation on the target camera, at least one of the light intake, shooting range, and focus of the target camera is adjusted.

6. The cable management platform according to any one of claims 1 to 3, characterized in that, The cable management interface also includes: cable ledger options and cable management options; the cable management platform also includes: cable ledger module and cable management module, both of which are microservices; The cable ledger module is used to respond to the selection operation of the cable ledger option. If the login account belongs to the prefecture-level account, the ledger data of the second target unit in the prefecture-level account is displayed in the ledger function area. If the login account belongs to the provincial account, the ledger data of the second target unit in the provincial account is displayed in the ledger function area. The cable management module is used to respond to the selection operation of the cable management option. If the login account belongs to the prefecture-level account, the operation and maintenance data of the third target unit in the prefecture-level account is displayed in the cable management function area. If the login account belongs to the provincial account, the operation and maintenance data of the third target unit in the provincial account is displayed in the cable management function area. Both the second target unit and the third target unit include equipment, channels, or lines.

7. The cable management platform according to any one of claims 1 to 3, characterized in that, The cable management platform further includes: a data entry module, which is a microservice; the data entry module is used for: Receive application data, which includes ledger-type data, operation and maintenance data, or online monitoring data; If the application data is detected to be accurate, then the application data is stored; If an anomaly is detected in the application data, a notification message will be sent.

8. The cable management platform according to claim 7, characterized in that, The data entry module is also used for: Based on the type of the application data and the object to which the application data belongs, determine the storage template of the application data; The application data is stored based on the storage template.

9. The cable management platform according to claim 7, characterized in that, The data entry module is also used for: After receiving the application data, the verification rules for the application data are determined based on the type of the application data and the object to which the application data belongs. If the application data does not conform to the verification rules, then the application data is determined to be abnormal; If the application data conforms to the verification rules, then the application data is determined to be accurate.

10. A cable management system, characterized in that, Includes the cable management platform as described in any one of claims 1 to 9.

11. A cable management method, characterized in that, Applied to any one of the cable management platforms of claims 1 to 9, the method comprises: The cable management interface is displayed corresponding to the login account, which may be a city-level account or a provincial-level account. The cable management interface includes at least a cable overview option. In response to a selection operation for the cable overview option, cable information is displayed, which includes at least one of equipment information, channel information, line information, and abnormal status. In response to the selection operation of target cable information in the cable information, if the login account belongs to the prefecture-level account, the distribution of the target cable information in the prefecture-level account is displayed on the map; if the login account belongs to the provincial account, the distribution of the target cable information in the provincial account is displayed on the map. The cable management interface also includes: an abnormal status statistics option; the method also includes: In response to the selection of the abnormal state statistics option, the information statistics area of ​​the abnormal state is displayed; The information statistics area receives the target's abnormal status, target route, and target time period. In response to a statistical command for the target abnormal status, if the login account belongs to the prefecture-level city, the trend of the target abnormal status located on the target route in the prefecture-level city is displayed in the target time period; if the login account belongs to the provincial level, the trend of the target abnormal status located on the target route in the provincial level is displayed in the target time period.

12. The method according to claim 11, characterized in that, The response to selecting the cable overview option, displaying cable information, includes: In response to a selection operation for a cable overview option, a functional layer is displayed, the functional layer including at least one of a device layer, a channel layer, a line layer, and an abnormal status layer; In response to a selection operation for a target function layer in the function layers, the cable information in the target function layer is displayed; The device layer includes different types of devices, the channel layer includes different types of channels, the line layer includes different cable lines, and the abnormal status layer includes different types of abnormal statuses.

13. The method according to claim 11, characterized in that, The target cable information includes multiple parameters, and the method further includes: In response to a selection operation for one of the multiple target cable information, basic information of the target cable is displayed. The basic information of a target cable includes at least the location of the target cable.

14. The method according to any one of claims 11 to 13, characterized in that, The cable management interface also includes a cable statistics option, and the method further includes: In response to the selection operation for the cable statistics option, if the login account belongs to the prefecture-level account, the statistical information of the first target unit in the prefecture-level account is displayed in the cable statistics area; if the login account belongs to the provincial account, the statistical information of the first target unit in the provincial account is displayed in the cable statistics area. The first target unit includes a device, channel, or line, and the statistical information includes at least the total number of the first target units.

15. The method according to any one of claims 11 to 13, characterized in that, The cable management interface also includes: a visualization function option; the method also includes: In response to a selection operation for the visualization function options, the visualization function area is displayed; In response to a selection operation for a target historical video received in the visualization function area, the target historical video is played in the visualization function area; In response to an adjustment operation on the target camera, at least one of the light intake, shooting range, and focus of the target camera is adjusted.

16. The method according to any one of claims 11 to 13, characterized in that, The cable management interface also includes: cable ledger options and cable management options; the method also includes: In response to the selection operation of the cable ledger option, if the login account belongs to the prefecture-level account, the ledger data of the second target unit in the prefecture-level account is displayed in the ledger function area; if the login account belongs to the provincial account, the ledger data of the second target unit in the provincial account is displayed in the ledger function area. In response to the selection operation of the cable management option, if the login account belongs to the city-level account, the operation and maintenance data of the third target unit in the city-level account will be displayed in the cable management function area; if the login account belongs to the provincial-level account, the operation and maintenance data of the third target unit in the provincial-level account will be displayed in the cable management function area. Both the second target unit and the third target unit include equipment, channels, or lines.

17. The method according to any one of claims 11 to 13, characterized in that, The method further includes: Receive application data, which includes ledger-type data, operation and maintenance data, or online monitoring data; If the application data is detected to be accurate, then the application data is stored; If an anomaly is detected in the application data, a notification message will be sent.

18. The method according to claim 17, characterized in that, The storage of the application data includes: Based on the type of the application data and the object to which the application data belongs, determine the storage template of the application data; The application data is stored based on the storage template.

19. The method according to claim 17, characterized in that, After receiving the application data, the method further includes: Based on the type of the application data and the object to which the application data belongs, determine the verification rules for the application data; If the application data does not conform to the verification rules, then the application data is determined to be abnormal; If the application data conforms to the verification rules, then the application data is determined to be accurate.

Images