Road asset digital management method, device, electronic equipment and program product

Abstract

The application relates to the technical field of traffic management, and discloses a road asset digital management method and device, an electronic device and a computer program product. The method comprises the following steps: obtaining accessory business information of a road asset device to be input; binding the accessory business information with a device model of the road asset device; and adding the device model with the bound accessory business information to a target position of a preset monitoring page. The accessory business information of the road asset device is bound with the device model, and the corresponding accessory business information is input together when the device model is added to the monitoring page. This process does not require professional code writing operation of a user, can greatly simplify the operation complexity of adding accessory business information to the road asset device, and reduces limitations.

Description

Technical Field

[0001] This application relates to the field of traffic management technology, and in particular to a method, device, electronic device, and computer program product for digital management of road assets. Background Technology

[0002] Road assets mainly include four categories: structures, electromechanical equipment, traffic safety facilities, and other facilities. Currently, road asset management systems are commonly used to manage these various road assets and equipment. These systems allow data from each road asset and equipment to be added to a monitoring page for real-time monitoring of their location, operational status, and equipment parameters. However, existing road asset management systems lack integration with related ancillary business information. Adding this information to managed road assets often requires specialized developers to write code, resulting in significant operational limitations. Summary of the Invention

[0003] In view of this, embodiments of this application provide a method, apparatus, electronic device, and computer program product for digital management of road assets, which can simplify the operational complexity of adding ancillary business information to road asset equipment and reduce limitations.

[0004] The first aspect of this application provides a method for digital management of road assets, including:

[0005] Obtain the ancillary business information of the road assets and equipment to be entered;

[0006] Link ancillary business information with the equipment model of road assets and equipment;

[0007] Add the device model, after binding the ancillary business information, to the target location on the preset monitoring page.

[0008] In the technical solution of this application embodiment, when it is necessary to input a road asset device, the ancillary business information of the road asset device is obtained, and the ancillary business information is bound to the device model of the road asset device. Then, the device model bound with the ancillary business information is added to the target location of the preset monitoring page. The above process, by binding the ancillary business information of the road asset device to the device model, ensures that the corresponding ancillary business information is entered simultaneously when the device model is added to the monitoring page. This process does not require users to perform professional coding operations, greatly simplifying the operational complexity of adding ancillary business information to road asset devices and reducing limitations.

[0009] In one implementation of this application, before binding the ancillary business information to the equipment model of the road asset equipment, the following steps are also included:

[0010] Obtain information on the type of road asset equipment;

[0011] Find the device model that matches this type of information from the pre-built device model library.

[0012] In one implementation of this application, adding the device model bound with ancillary business information to a target location on a preset monitoring page includes:

[0013] Obtain the station number information of road assets and equipment;

[0014] Convert the station number information into corresponding latitude and longitude coordinates;

[0015] Based on latitude and longitude coordinates, add the device model to the initial position of the preset monitoring page;

[0016] The device model is adjusted from its initial position to the target position by using the position adjustment command detected on the visual operation page.

[0017] In another implementation of this application's embodiments, adding the device model bound with ancillary business information to the target location of a preset monitoring page includes:

[0018] From the preset monitoring page, locate the device placement area associated with the ancillary business information;

[0019] Select the target location from the device placement area, and add the device model with the attached business information to the target location.

[0020] In one implementation of this application, selecting a target location from the device placement area includes:

[0021] Obtain information on the type of road asset equipment;

[0022] From the available locations in the device placement area, find the available location that corresponds to this type of information and use it as the target location.

[0023] In one implementation of this application, after adding the device model bound with ancillary business information to the target location of the preset monitoring page, the method further includes:

[0024] The ancillary business information and the coordinates of the target location are uploaded to the IoT server connected to the road asset equipment, instructing the IoT server to synchronize the ancillary business information and coordinates to the relevant information of the road asset equipment stored in the database.

[0025] In one implementation of this application, after adding the device model bound with ancillary business information to the target location of the preset monitoring page, the method further includes:

[0026] When an operation command to delete a device model in the preset monitoring page is detected, the device model and its associated business information will be deleted together.

[0027] A second aspect of this application provides a digital management device for road assets, comprising:

[0028] The information acquisition module is used to acquire ancillary business information of road asset equipment to be entered;

[0029] The information binding module is used to bind ancillary business information to the equipment model of road asset equipment;

[0030] The model adding module is used to add device models, after binding with ancillary business information, to the target location on the preset monitoring page.

[0031] A third aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the road asset digital management method provided in the first aspect of this application.

[0032] A fourth aspect of this application provides a computer program product that, when run on an electronic device, causes the electronic device to perform the road asset digital management method provided in the first aspect of this application.

[0033] The fifth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the road asset digital management method provided in the first aspect of this application.

[0034] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0035] Figure 1 This is a schematic diagram of a digital management system for road assets provided in an embodiment of this application;

[0036] Figure 2 This is a flowchart of a method for digital management of road assets provided in an embodiment of this application;

[0037] Figure 3 This is a schematic diagram of a monitoring page of a road asset management system provided in an embodiment of this application;

[0038] Figure 4 This is a schematic diagram illustrating the operational principle of device model placement and real-time synchronization of business data provided in this application embodiment;

[0039] Figure 5 This is a schematic diagram of the structure of a digital management device for road assets provided in an embodiment of this application;

[0040] Figure 6 This is a schematic diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0041] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application can also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail. Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0042] Road assets mainly include four categories: structures, electromechanical equipment, traffic safety facilities, and other facilities. Structures mainly include roadbeds, pavements, bridges, tunnels, culverts, interchanges, and retaining walls. Electromechanical equipment mainly includes various monitoring equipment, communication equipment, information dissemination equipment, lighting equipment, and power equipment. Traffic safety facilities mainly include traffic signs, traffic markings, guardrails, isolation fences, delineators, guide signs, and anti-glare facilities. Other facilities mainly include operating equipment, building facilities, other management facilities, other service facilities, and greening and environmental protection facilities.

[0043] Existing road asset management systems can add data from various road asset devices to a monitoring page for display, enabling real-time monitoring of their location, operating status, and device parameters. However, these systems lack integration with related ancillary business information. Adding such information to managed road asset devices often requires specialized developers to write code, resulting in significant operational limitations.

[0044] In view of this, embodiments of this application provide a method, apparatus, electronic device, and computer program product for digital management of road assets. By binding the ancillary business information of road asset equipment to the equipment model, the operational complexity of adding ancillary business information to road asset equipment can be simplified, reducing limitations. For more specific technical implementation details of the embodiments of this application, please refer to the various embodiments described below.

[0045] The following describes a digital management system for road assets provided in an embodiment of this application, such as... Figure 1As shown, the system includes an IoT server, electronic devices, and various road asset devices, with no restrictions on the specific type or quantity of each device. Each road asset device can connect to the IoT server via a network, and the electronic devices can also connect via the same means. Each road asset device can upload its operating status and equipment parameters to the IoT server, which then distributes this information to the electronic devices. These operating statuses and parameters are displayed on the electronic devices' monitoring pages, thus achieving digital management of road assets. Alternatively, each road asset device can also connect to the electronic devices via a network, directly sending its operating status and equipment parameters for display. It should be noted that the road asset devices with data transmission capabilities primarily refer to electromechanical equipment within the road assets. For structures, traffic safety facilities, and other facilities that do not have data transmission capabilities, their relevant data can be collected separately and added to the monitoring pages of the electronic devices for display. Regarding... Figure 1 For details on the specific technical implementation of the system shown, please refer to the various method embodiments described below.

[0046] It should be understood that the implementing entity of the various method embodiments proposed in this application may be... Figure 1 The electronic device of the system shown can be a mobile phone, tablet computer, wearable device, roadside equipment, vehicle terminal, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), large screen TV, etc. The embodiments of this application do not limit the specific type of the electronic device.

[0047] Please see Figure 2 This application illustrates a method for digital management of road assets, comprising:

[0048] 201. Obtain the ancillary business information of the road assets and equipment to be entered;

[0049] If it is necessary to input a road asset device into an electronic device for digital management, the basic information and ancillary business information of the road asset device can be entered into the electronic device first. The basic information may include device ID, device name, type information, station number information, and direction and location information, etc. The ancillary business information may include the device IP address, port number, URL address, brand information, and other business information related to the business.

[0050] As an example, a preliminary equipment list can be prepared, containing basic and ancillary business information for all road asset equipment to be entered. This preliminary equipment list can then be input into an electronic device for processing. As another example, a data input interface can be displayed on the screen of the electronic device, allowing the user to manually input the basic and ancillary business information for each road asset device. In practice, both input methods can coexist. For instance, the prepared preliminary equipment list might only contain basic information for each road asset device; after inputting this list into the electronic device, the user would need to manually input the corresponding ancillary business information for each road asset device through the data input interface.

[0051] 202. Bind the ancillary business information to the equipment model of road assets and equipment;

[0052] After acquiring the ancillary business information of the road asset equipment to be entered, the electronic device binds this ancillary business information to the equipment model of that road asset equipment. To enable monitoring of different road asset equipment on the monitoring page, the electronic device assigns a corresponding equipment model to each road asset equipment. After assigning the equipment model, the corresponding ancillary business information is bound. For example, assuming the road asset equipment to be entered includes equipment A and equipment B, after assigning equipment model A to equipment A, equipment model A is bound to the ancillary business information A of equipment A. Similarly, after assigning equipment model B to equipment B, equipment model B is bound to the ancillary business information B of equipment B, and so on.

[0053] In one implementation of this application, before binding the ancillary business information to the equipment model of the road asset equipment, the following steps are also included:

[0054] (1) Obtain information on the type of road assets and equipment;

[0055] (2) Search for a device model that matches the type of information from a pre-built device model library.

[0056] Electronic devices can be pre-built and maintained within a device model library, containing a large number of lightweight, high-precision textured devices of various types and formats. Furthermore, device models can be customized based on the actual road environment and added to this library. This effectively supports model mapping for different road asset types, facilitating the digital operation and maintenance management of road assets. The stored device models can be 2D or 3D, and their types include, but are not limited to: traffic safety equipment models, general management models, monitoring equipment models, power supply and distribution equipment models, lighting equipment models, ventilation equipment models, fire protection facility models, building models, vegetation models, and traffic participant models, etc. The high-definition textures used in the models can include, but are not limited to: stone, tiles, metal, glass, windows, doors, roofs, fences, wood grain, billboards, and natural elements, etc. When assigning a device model to a road asset device to be entered, the type information is first obtained from the basic information of the road asset device, and then a device model matching that type information is searched and assigned from the device model library. For example, for a LiDAR device to be entered, a device model of the LiDAR type can be found in the device model library and assigned; for a camera device to be entered, a device model of the camera type can be found in the device model library and assigned, and so on.

[0057] 203. Add the device model after binding the auxiliary business information to the target location on the preset monitoring page.

[0058] Once the device model is bound to ancillary business information, it will be added to the target location on the preset monitoring page of the electronic device. This preset monitoring page can be developed based on a high-precision map and can be a 2D or 3D page. As an example, a high-precision 3D monitoring page can be constructed using a 3D twin engine. This 3D twin engine can include a twin platform navigation framework, a weather day / night twin controller, page effects, operation and maintenance components, platform configuration and settings, coordinate system transformation plugins, login page, device list statistics, device objectification, individual device animation effects, information board twins, device objectification effects, 3D roaming, and viewpoint jumps, among other functional components. These functional components can be combined according to actual business needs. Using these components, it is possible to achieve refined restoration of static elements at the component level, high-precision image quality and dynamic lighting effects, large-scene high-frame-rate digital base, real-time twinning of multiple types of traffic information, multi-angle monitoring modes and interactive operations, high-smoothness perception data smoothing optimization, multiple different interactive perspectives, and loop playback of the full details of the 3D scene.

[0059] When adding device models to the monitoring page, you can first perform a preliminary placement and then a fine placement. The position of the device model after fine placement is the target position. Please refer to the following text for specific device model placement steps.

[0060] In one implementation of this application, adding the device model bound with ancillary business information to a target location on a preset monitoring page includes:

[0061] (1) Obtain the station number information of road assets and equipment;

[0062] (2) Convert the station number information into corresponding latitude and longitude coordinates;

[0063] (3) Add the device model to the initial position of the preset monitoring page according to the latitude and longitude coordinates;

[0064] (4) Adjust the device model from the initial position to the target position by the position adjustment command detected by the visual operation page.

[0065] A monitoring page can be generated based on a high-precision map and by loading a digital base package. It retrieves the station number information of road asset equipment from its basic information, converts this station number information into corresponding latitude and longitude coordinates, and quickly places the equipment model on the monitoring page to the initial position corresponding to these coordinates, thus completing the initial placement of the equipment model. In practice, a plugin for converting kilometer markers to latitude and longitude can be designed. This plugin can convert the station number information of multiple road asset equipment into latitude and longitude coordinates, and then quickly place the corresponding equipment models of multiple road asset equipment to their approximate positions on the monitoring page based on these coordinates, thus achieving rapid automatic positioning of batch equipment models. Alternatively, the approximate location of road asset equipment can be determined manually based on image data, and equipment models can be directly dragged and dropped from the equipment model library to the monitoring page and placed to their approximate initial positions. After the initial placement of the equipment model is completed, the fine-tuning operation can begin. The electronic device displays a visual operation page, through which the user can perform various positional adjustments on the equipment model (such as dragging or rotating it). The electronic device will finely adjust the position of the equipment model based on the detected positional adjustment commands, ultimately moving the equipment model from its initial position to the target position. After the fine-tuning is completed, the corresponding scene information can be saved and the monitoring page updated. The user can then view the corresponding equipment model on the monitoring page.

[0066] In another implementation of this application's embodiments, adding the device model bound with ancillary business information to the target location of a preset monitoring page includes:

[0067] (1) Locate the device placement area associated with the ancillary business information from the preset monitoring page;

[0068] (2) Select the target location from the equipment placement area and add the equipment model after binding the ancillary business information to the target location.

[0069] In another implementation, the monitoring page can be pre-divided into multiple device placement areas based on different ancillary business information. When adding a device model to the monitoring page, the associated device placement area is first found based on its bound ancillary business information. Then, a suitable model placement location is selected from that device placement area and recorded as the target location. Finally, the device model is placed at the target location. For example, the monitoring page can be divided into N device placement areas based on IP addresses, with each device placement area corresponding to a specific IP address prefix. When adding a device model A to the monitoring page, the target IP address from the ancillary business information bound to device model A is obtained. Based on the prefix of the target IP address, the corresponding device placement area is found from the N device placement areas. Then, a target location is selected from that device placement area, and device model A is placed at the target location. For example, the monitoring page can be divided into M device placement areas based on the brand, with each area corresponding to a specific device brand. When a device model B is added to the monitoring page, the target device brand is retrieved from the associated business information. Based on the target device brand, the corresponding device placement area is selected from the M areas, and a target location is chosen within that area to place device model B. This setup standardizes the placement of device models on the monitoring page according to their associated business information, thereby improving the rationality and convenience of road asset equipment management.

[0070] In one implementation of this application, selecting a target location from the device placement area includes:

[0071] (1) Obtain information on the type of road assets and equipment;

[0072] (2) From the available locations in the equipment placement area, find an available location that corresponds to this type of information as the target location.

[0073] When selecting a target location from the equipment placement area associated with ancillary business information, the type information of the road asset equipment can be obtained from its basic information. Then, from the available locations within that equipment placement area, a vacant location corresponding to that type information can be found as the target location. For example, based on the target equipment brand in the ancillary business information bound to equipment model B, after finding a corresponding equipment placement area from the aforementioned M equipment placement areas, the type information of the road asset equipment corresponding to equipment model B can be obtained. Assuming it is a LiDAR type, a vacant location for placing a LiDAR type device can be found within that equipment placement area as the target location. Through this setup, after determining the placement area of ​​the equipment model on the monitoring page based on the ancillary business information, the corresponding specific placement location can be found within that placement area based on the equipment type. This achieves refined placement by equipment type, further improving the standardization and rationality of equipment model placement.

[0074] As an example, Figure 3 This is a schematic diagram of the monitoring page of a road asset management system provided in an embodiment of this application. Figure 3 The monitoring page shown contains multiple different device models, each corresponding to a road asset device and bound to its own associated business information. For example, device model 1 is bound to associated business information 1 for road asset device 1, device model 2 is bound to associated business information 2 for road asset device 2, and so on. Each device model is placed in its corresponding position on the monitoring page according to its location information. When a user clicks on a device model on the monitoring page, a window will pop up displaying the real-time operating status and device parameters of the corresponding road asset device, thus realizing single-page road asset operation and maintenance management.

[0075] In one implementation of this application, after adding the device model bound with ancillary business information to the target location of the preset monitoring page, the method further includes:

[0076] The ancillary business information and the coordinates of the target location are uploaded to the IoT server connected to the road asset equipment, instructing the IoT server to synchronize the ancillary business information and coordinates to the relevant information of the road asset equipment stored in the database.

[0077] After placing the device model at the target location on the monitoring page using the methods described above, the electronic device saves the corresponding scene information and updates the monitoring page. Additionally, the corresponding road asset equipment data can be synchronized to [the relevant information] in real time. Figure 1The system shown is an IoT server. Specifically, after an electronic device completes the placement of a device model, it can upload its associated business information and the coordinates of the target location to the IoT server. The IoT server then synchronizes this associated business information and coordinates to the relevant information of the corresponding road asset device stored in the database, thereby achieving real-time synchronization and updating of relevant business data across multiple devices.

[0078] As an example, Figure 4 This is a schematic diagram illustrating the operational principle of device model placement and real-time synchronization of business data provided in this application embodiment. Figure 4In this context, the IoT platform refers to the Internet of Things server, and the road asset editor is an editing tool provided by the road asset management system running on electronic devices. After loading the digital base package and generating the monitoring page, the initial placement of equipment models can be completed manually or automatically. Manual placement refers to the user manually observing and determining the approximate location of the equipment based on image data, and then dragging and dropping the equipment model directly from the equipment model library to the initial position on the monitoring page. Automatic positioning refers to inputting the road asset equipment list and using kilometer markers to convert latitude and longitude to complete the low-precision automatic positioning of batch equipment models. After the initial placement is completed, the equipment model is added to the initial position on the monitoring page. At this time, the user can enter the associated ancillary business information for the equipment model. It should be noted that the operation of entering ancillary business information can occur before or after the initial placement of the equipment model; this embodiment does not impose any restrictions on this. Next, the system performs a fine-grained placement of the equipment model, displaying a visual operation page through which the user can drag and move the equipment model to ultimately complete the fine-grained placement of the equipment model. The added device models can automatically match the corresponding device protocols based on their respective device types, enabling simultaneous completion of model addition and device integration development, as well as effective integration of device models with ancillary business information. Specifically, after customizing and developing device protocols for various types of road asset equipment, a dynamic protocol mounting service can be run to automatically complete the matching and mounting operation between device models and corresponding device protocols. Afterwards, users can click "Save Scene," and the system saves the updated monitoring page, allowing users to monitor various road asset equipment in a comprehensive overview. The system will synchronize the relevant business data to the IoT platform in real time. After receiving the business data through the device data interface, the IoT platform will update and store the business data in the IoT database, achieving persistent storage of business data. In addition to business data interaction, electronic devices and the IoT platform can also interact on device models. Taking the device model library described earlier as an example, electronic devices can maintain a device model library A, and the IoT platform can maintain another device model library B. Electronic devices can download various device models saved in device model library B to device model library A through the IoT platform, or upload customized device models from device model library A to device model library B on the IoT platform for storage. In addition, third-party mobile, client, or web applications can also query and perform other operations on the data stored on the IoT platform through the device data interface.

[0079] In one implementation of this application, after adding the device model bound with ancillary business information to the target location of the preset monitoring page, the method further includes:

[0080] When an operation command to delete a device model in the preset monitoring page is detected, the device model and its associated business information will be deleted together.

[0081] In the technical solution of this application embodiment, the device model and its associated business information have a strongly bound symbiotic relationship. When a device model is added, the bound associated business information is also added; similarly, when a device model is deleted, the bound associated business information is also deleted. Specifically, users can select one or more device models to delete on the monitoring page. Deleting these device models will also delete the bound associated business information, thereby improving the completeness and comprehensiveness of the data deletion operation.

[0082] After electronic devices have entered the data for each road asset device according to the steps described above, they can obtain real-time data from the device via an IoT server, such as operating status and equipment parameters. This real-time data enables the operation and maintenance management of the road asset device. Specifically, a road asset management system can be deployed on the electronic devices. After the road asset device is entered into the system, it can perform functions such as equipment status monitoring, equipment fault analysis, online inspection, electromechanical maintenance work order processing, and equipment operation and maintenance evaluation. Based on the acquired real-time data, the system performs statistical analysis, including system health status analysis, fault cause analysis, equipment performance analysis, personnel efficiency analysis, service quality analysis, and cost-benefit analysis. This enables proactive early warning of operational status, prevention of recurring faults, reminders for replacing obsolete inventory, optimization of personnel organizational structure, improvement of the evaluation system, cost reduction, and increased revenue.

[0083] In the technical solution of this application embodiment, when it is necessary to input a road asset device, the ancillary business information of the road asset device is obtained, and the ancillary business information is bound to the device model of the road asset device. Then, the device model bound with the ancillary business information is added to the target location of the preset monitoring page. The above process, by binding the ancillary business information of the road asset device to the device model, ensures that the corresponding ancillary business information is entered simultaneously when the device model is added to the monitoring page. This process does not require users to perform professional coding operations, greatly simplifying the operational complexity of adding ancillary business information to road asset devices and reducing limitations.

[0084] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0085] The above mainly describes a method for digital management of road assets. The following will describe a device for digital management of road assets.

[0086] Please see Figure 5 One embodiment of a road asset digital management device in this application includes:

[0087] Information acquisition module 501 is used to acquire ancillary business information of road asset equipment to be entered;

[0088] Information binding module 502 is used to bind ancillary business information to the equipment model of road asset equipment;

[0089] The model addition module 503 is used to add the device model after binding the auxiliary business information to the target location of the preset monitoring page.

[0090] In one implementation of this application, the road asset digital management device further includes:

[0091] The equipment type acquisition module is used to acquire the type information of road asset equipment;

[0092] The model matching module is used to find device models that match this type of information from a pre-built device model library.

[0093] In one implementation of this application, the model adding module includes:

[0094] The stationing acquisition unit is used to acquire stationing information of road assets and equipment;

[0095] The latitude and longitude conversion unit is used to convert station information into corresponding latitude and longitude coordinates;

[0096] The coarse placement unit is used to add the device model to the initial position of the preset monitoring page based on latitude and longitude coordinates;

[0097] The fine placement unit is used to adjust the device model from its initial position to the target position based on the position adjustment commands detected by the visual operation page.

[0098] In another implementation of this application's embodiments, the model adding module includes:

[0099] The area search unit is used to find the device placement area associated with the ancillary business information from the preset monitoring page;

[0100] The location selection unit is used to select a target location from the device placement area and add the device model with the attached business information to the target location.

[0101] In one implementation of this application, the location selection unit includes:

[0102] The type acquisition subunit is used to acquire type information of road asset equipment;

[0103] The location lookup subunit is used to find a free location corresponding to this type of information from among the various free locations in the device placement area as the target location.

[0104] In one implementation of this application, the road asset digital management device further includes:

[0105] The information upload module is used to upload ancillary business information and target location coordinates to an IoT server connected to the road asset equipment, so as to instruct the IoT server to synchronize the ancillary business information and coordinates to the relevant information of the road asset equipment stored in the database.

[0106] In one implementation of this application, the road asset digital management device further includes:

[0107] The information deletion module is used to delete the device model and its associated business information together when an operation command to delete the device model in the preset monitoring page is detected.

[0108] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the road asset digital management method as described in any of the above embodiments.

[0109] This application also provides a computer program product that, when run on an electronic device, causes the electronic device to execute the road asset digital management method as shown in any of the above embodiments.

[0110] Figure 6 This is a schematic diagram of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device 6 in this embodiment includes: a processor 60, a memory 61, and a computer program 62 stored in the memory 61 and executable on the processor 60. When the processor 60 executes the computer program 62, it implements the steps in the embodiments of the various road asset digital management methods described above, for example... Figure 2 Steps 201 to 203 are shown. Alternatively, when the processor 60 executes the computer program 62, it implements the functions of each module / unit in the above-described device embodiments, for example... Figure 5 The functions of modules 501 to 503 are shown.

[0111] The computer program 62 can be divided into one or more modules / units, which are stored in the memory 61 and executed by the processor 60 to complete this application. The one or more modules / units can be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program 62 in the electronic device 6.

[0112] The processor 60 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0113] The memory 61 can be an internal storage unit of the electronic device 6, such as a hard disk or memory. The memory 61 can also be an external storage device of the electronic device 6, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card. Furthermore, the memory 61 can include both internal and external storage units of the electronic device 6. The memory 61 is used to store the computer program and other programs and data required by the electronic device. The memory 61 can also be used to temporarily store data that has been output or will be output.

[0114] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0115] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0116] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0117] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0118] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or units through some interfaces, and may be electrical, mechanical, or other forms.

[0119] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0120] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0121] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.

[0122] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for digital management of road assets, characterized in that, include: Obtain the ancillary business information of the road assets and equipment to be entered; Bind the ancillary business information to the equipment model of the road asset equipment; Add the device model, after binding the associated business information, to the target location on the preset monitoring page.

2. The method as described in claim 1, characterized in that, Before binding the ancillary business information to the equipment model of the road asset equipment, the process also includes: Obtain the type information of the road asset equipment; From a pre-built library of device models, find the device model that matches the type information.

3. The method as described in claim 1, characterized in that, Adding the device model, after binding the ancillary business information, to the target location on the preset monitoring page includes: Obtain the station number information of the road asset equipment; Convert the station number information into corresponding latitude and longitude coordinates; Based on the latitude and longitude coordinates, the device model is added to the initial position of the preset monitoring page; The device model is adjusted from the initial position to the target position by the position adjustment command detected by the visual operation page.

4. The method as described in claim 1, characterized in that, Adding the device model, after binding the ancillary business information, to the target location on the preset monitoring page includes: From the preset monitoring page, locate the device placement area associated with the ancillary service information; Select the target location from the device placement area, and add the device model after binding the ancillary business information to the target location.

5. The method as described in claim 4, characterized in that, Selecting the target location from the device placement area includes: Obtain the type information of the road asset equipment; From the available locations in the device placement area, find an available location that corresponds to the type information and use it as the target location.

6. The method as described in claim 1, characterized in that, After adding the device model, which has been bound to the associated business information, to the target location on the preset monitoring page, the process also includes: The ancillary business information and the coordinate information of the target location are uploaded to an IoT server connected to the road asset equipment, so as to instruct the IoT server to synchronize the ancillary business information and the coordinate information to the relevant information of the road asset equipment stored in the database.

7. The method according to any one of claims 1 to 6, characterized in that, After adding the device model, which has been bound to the associated business information, to the target location on the preset monitoring page, the process also includes: When an operation command to delete the device model in the preset monitoring page is detected, the device model and the ancillary business information are deleted together.

8. A digital management device for road assets, characterized in that, include: The information acquisition module is used to acquire ancillary business information of road asset equipment to be entered; The information binding module is used to bind the ancillary business information to the equipment model of the road asset equipment; The model adding module is used to add the device model, after binding the ancillary business information, to the target location on the preset monitoring page.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the road asset digital management method as described in any one of claims 1 to 7.

10. A computer program product, characterized in that, When the computer program product is run on an electronic device, the electronic device performs the road asset digital management method as described in any one of claims 1 to 7.

Images