A traffic-based electromechanical equipment management method and system, and a storage medium

Abstract

This invention provides a traffic-based electromechanical equipment management method, system, and storage medium. The method is used in a traffic-based electromechanical equipment management system. The system includes a cloud, edge terminals corresponding to traffic segments, and electromechanical equipment terminals used in the traffic segments. The method includes: the cloud receiving an application deployment instruction and publishing the target application in a preset operating system application library; the edge terminals corresponding to each traffic segment obtaining the target application published by the cloud, performing compatibility testing and pre-deployment of the target application to obtain a target application package; and each edge terminal distributing the target application package to the electromechanical equipment terminals used in each traffic segment for management based on the target application package. This application improves integrated intelligent control capabilities and enhances multi-task collaboration efficiency by utilizing target application packages to manage electromechanical equipment terminals, avoiding the problems of traditional management models in achieving refined management and rapid response.

Description

Technical Field

[0001] This invention relates to the field of equipment management technology, and in particular to a method, system and storage medium for managing electromechanical equipment based on transportation. Background Technology

[0002] In the process of digital and intelligent transformation of transportation infrastructure, both construction and operation face profound systemic challenges. On the one hand, in operational scenarios such as highways, long-standing issues of system fragmentation, complex protocols, and strong coupling between software and hardware have created persistent "information silos," leading to difficulties in data integration, high operation and maintenance costs, and severely restricting the formation of integrated intelligent management and control capabilities. On the other hand, in engineering construction scenarios such as tunnels, there are common problems such as low efficiency in multi-disciplinary collaboration and insufficient support for construction decision-making from multiple data sources. Therefore, traditional management models are unable to achieve refined management and rapid response.

[0003] Therefore, existing technologies have shortcomings and need to be improved and developed. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a traffic-based electromechanical equipment management method, system and storage medium to address the above-mentioned deficiencies of the prior art, and to solve the problem that the traditional management mode in the prior art is difficult to achieve refined management and rapid response.

[0005] The technical solution adopted by this invention to solve the technical problem is as follows: A traffic-based electromechanical equipment management method is provided for a traffic-based electromechanical equipment management system, wherein the system includes a cloud platform, an edge terminal corresponding to a traffic segment, and electromechanical equipment terminals used in the traffic segment; the method includes: The cloud receives the application listing instruction and publishes the target application in the preset operating system application library; Each traffic segment's corresponding edge terminal obtains the target application published in the cloud, performs compatibility testing and pre-deployment on the target application, and obtains the target application package; Each edge device distributes the target application package to the electromechanical equipment used in each traffic segment, so as to manage the electromechanical equipment based on the target application package.

[0006] In one embodiment of this application, the cloud receives an application upload instruction and publishes the target application in a preset operating system application library, including: After receiving the application listing instruction in the cloud, the project is created based on DevEco Studio. Then, using the pre-built configuration templates and visual signature management tools of the Kaihong Super Device Management Platform, the process of signing and certificate management, project configuration modification, development environment and build tool adaptation, atomic service development, and application listing material preparation and uploading is completed. The target application is published in a preset operating system application library, which is the Kaihong operating system application library.

[0007] In one embodiment of this application, the traffic-based electromechanical equipment management method further includes: If the cloud receives an instruction to upload an AI application, it will publish the target AI application in the preset AI model library and perform version management, scenario classification and permission control on the target AI application. Each traffic segment's corresponding edge terminal obtains the target AI application published in the cloud, performs local optimization and testing on the target AI application, encapsulates the target AI application into a downloadable plugin, and uses the deployment function to distribute the downloadable plugin to the electromechanical equipment used in each traffic segment; The electromechanical equipment used in each traffic section receives the downloadable plugin and executes the function corresponding to the target AI application based on the downloadable plugin.

[0008] In one embodiment of this application, the target AI application is a deployable container image; the container image is obtained by using the graphical model conversion tool provided by the Kaihong Super Device Management Platform to convert the model into a format that can run on the target chip, and to perform quantization and accuracy comparison through a visual interface. The converted model is packaged into a standard service through the Python SDK, and the service is built through Docker image, automatically packaging the code that implements the standard service.

[0009] In one embodiment of this application, the traffic-based electromechanical equipment management method further includes: If the cloud receives an instruction to deploy an atomic service application, it provides a metadata configuration interface to obtain the configured metadata and obtain the target atomic service application based on the metadata. The cloud publishes the target atomic service application in the preset atomic service library and generates the atomic service package corresponding to the target atomic service application; Each traffic segment's corresponding edge terminal obtains the atomized service package and distributes the atomized service package to the electromechanical equipment terminals used in each traffic segment; The electromechanical equipment used in each traffic segment performs service flow and cross-device collaboration based on the atomic service package.

[0010] In one embodiment of this application, the traffic-based electromechanical equipment management method further includes: If the cloud receives a business orchestration instruction, it will orchestrate the business rules in the preset scenario application plugin library to form a rule package; The edge devices corresponding to each traffic segment obtain the rule package, and after verifying and rehearsing the rule package using the rule engine, deploy it to the electromechanical equipment used in each traffic segment. The electromechanical equipment used in each traffic segment performs closed-loop control based on the rule package.

[0011] In one embodiment of this application, if the cloud receives a business orchestration instruction, it orchestrates business rules in a preset scenario application plugin library to form a rule package, including: If the cloud receives a business orchestration instruction, it uses the business rule editor to drag and drop trigger nodes, processing nodes, and execution nodes from the node library, and connects them to build a complete business logic flow. Each node provides form-based configuration to complete the business rule orchestration in the preset scenario application plugin library and form a rule package.

[0012] In one embodiment of this application, the traffic-based electromechanical equipment management method further includes: If the cloud receives a plugin application upload instruction, it obtains the uploaded protocol plugin package, and based on the preset standard object model library and product template, completes the mapping configuration of device data points and standard object model attributes, events and methods in the graphical interface to obtain the device plugin. The edge terminal corresponding to each traffic segment obtains the device plugin, and automatically adapts to the same type of device according to the device type and application scenario corresponding to the device plugin to determine the target electromechanical equipment terminal, and deploys the device plugin to the target electromechanical equipment terminal; The target electromechanical equipment terminal uses the device plug-in to quickly connect to the device, collect data, and / or issue commands.

[0013] This application provides a traffic-based electromechanical equipment management system, wherein the system includes: a cloud, an edge terminal corresponding to a traffic segment, and an electromechanical equipment terminal used in the traffic segment; The cloud is used to receive application listing instructions and publish the target application in a preset operating system application library; The edge terminals corresponding to each traffic segment are used to obtain the target application published in the cloud, perform compatibility testing and pre-deployment of the target application to obtain the target application package; and distribute the target application package to the electromechanical equipment terminals used in each traffic segment to manage the electromechanical equipment terminals based on the target application package.

[0014] This application also provides a computer-readable storage medium storing a computer program that can be executed to implement the steps of the traffic-based electromechanical equipment management method described above.

[0015] This invention provides a traffic-based electromechanical equipment management method, system, and storage medium. The method is used in a traffic-based electromechanical equipment management system. The system includes a cloud, edge terminals corresponding to traffic segments, and electromechanical equipment terminals used in the traffic segments. The method includes: the cloud receiving an application deployment instruction and publishing a target application in a preset operating system application library; each edge terminal corresponding to a traffic segment obtaining the target application published by the cloud, performing compatibility testing and pre-deployment on the target application to obtain a target application package; and each edge terminal distributing the target application package to the electromechanical equipment terminals used in each traffic segment for management based on the target application package. This application improves integrated intelligent control capabilities and enhances multi-task collaboration efficiency by publishing the target application in the operating system application library in the cloud, enabling edge terminals corresponding to each traffic segment to obtain the target application and then distributing it to the electromechanical equipment terminals used in each traffic segment. The use of the target application package for management of the electromechanical equipment terminals improves integrated intelligent control capabilities and enhances multi-task collaboration efficiency, avoiding the problems of traditional management models in achieving refined management and rapid response. Attached Figure Description

[0016] Figure 1 This is a flowchart of a preferred embodiment of the traffic-based electromechanical equipment management method of the present invention.

[0017] Figure 2 This is the running logic diagram of Jihong AppStore in this invention.

[0018] Figure 3 This is a schematic diagram of the overall process of application distribution and deployment in the Jihong AppStore of this invention.

[0019] Figure 4 This is a schematic diagram of the full-stack application system in this invention.

[0020] Figure 5 This is a functional principle block diagram of a preferred embodiment of the traffic-based electromechanical equipment management system of the present invention. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of this invention clearer and more explicit, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0022] This application addresses the long-standing pain points in the transportation industry, such as the fragmentation of highway electromechanical equipment systems, complex protocols, and strong coupling between hardware and software. Based on KaihongOS and KaihongOS Meta, it deeply integrates a cloud-edge-device collaborative architecture, an atomic service concept, and a low-code development model to construct the Jihong AppStore, a software application store for highway electromechanical equipment. The application systematically elaborates on the overall design, technical implementation, and application advantages of the Jihong AppStore. The Jihong AppStore systematically solves the digitalization challenges of electromechanical systems, becoming a core ecological hub for the implementation of the "Jihong Digital Foundation" strategy and providing powerful momentum for the continuous evolution of intelligent transportation.

[0023] Specifically, the Kaihong AppStore is a unified cloud-based software application store for highway electromechanical equipment, built on KaihongOS and KaihongOS Meta. It showcases and distributes various applications based on the Kaihong OS, enabling flexible uploading, distribution, and sharing of all self-developed Kaihong cloud-edge applications. This facilitates rapid deployment, remote upgrades, and resource visualization for all highway electromechanical equipment. Its aim is to provide users with a secure and convenient channel to access applications, while also providing developers with a platform to showcase and promote their services.

[0024] The application types in the Kaihong App Store include: 1. Kaihong Operating System Applications: These applications are developed using Kaihong's UI framework and APIs. They can be front-end applications with a graphical user interface or back-end services running in the background without a user interface. Specifically, this includes front-end and back-end KaihongOS applications, as well as AI applications that provide AI capabilities in the form of containerized services; 2. Kaihong Atomic Service Applications: Atomic service applications provide users with a convenient service experience due to their lightweight, plug-and-play, and installation-free characteristics, and their ability to easily transfer between different Kaihong devices. Specifically, this includes atomic service applications; 3. Kaihong Platform Atomic Applications: These applications support rapid customization and can quickly adapt to specific business scenarios based on user needs and roles, such as the automation of inspection processes and the intelligent orchestration of emergency plans. Specifically, this includes business rule applications that allow for rapid customization of scenario-based business applications through visual orchestration, and device plugin applications that provide basic device access capabilities. See Table 1.

[0025] Table 1

[0026] Jihong AppStore provides comprehensive end-to-end cloud services, including application listing, management, signing, and distribution. This process ensures application security and availability, and simplifies the user acquisition and usage process, as shown in Table 2.

[0027] Table 2

[0028] Therefore, this application, based on the distributed collaboration capabilities of KaihongOS and the low-code development model of the KaihongOSMeta platform, deeply integrates cloud-edge-device collaboration and atomic service concepts to construct a transportation-based electromechanical equipment management and distribution platform—Jihong AppStore, which has significant practical implications. This platform aims to systematically solve the challenges of digitizing electromechanical systems, becoming a core ecological hub for the implementation of the "Jihong Digital Foundation" strategy, and providing strong and sustainable momentum for the continuous evolution of intelligent transportation.

[0029] The following description, with reference to the accompanying drawings, describes a traffic-based electromechanical equipment management method, system, and storage medium according to embodiments of this application. Addressing the problem mentioned in the background art that traditional management models struggle to achieve refined management and rapid response, this application provides a traffic-based electromechanical equipment management method for a traffic-based electromechanical equipment management system. The system includes a cloud, edge terminals corresponding to traffic segments, and electromechanical equipment terminals used in the traffic segments. In this method, the cloud receives an application deployment instruction and publishes a target application in a preset operating system application library. Each edge terminal corresponding to a traffic segment obtains the target application published by the cloud, performs compatibility testing and pre-deployment of the target application, and obtains a target application package. Each edge terminal distributes the target application package to the electromechanical equipment terminals used in each traffic segment to manage the electromechanical equipment terminals based on the target application package. This application publishes the target application in the cloud-based operating system application library, enabling the edge devices corresponding to each traffic segment to obtain the target application, which is then distributed to the electromechanical equipment used in each traffic segment. The target application package is used to manage the electromechanical equipment, thereby improving the integrated intelligent control capability and the efficiency of multi-task collaboration. This avoids the problem that traditional management models are unable to achieve refined management and rapid response.

[0030] Please see Figure 1 , Figure 1 This is a flowchart of the traffic-based electromechanical equipment management method in this invention. For example... Figure 1 As shown in the embodiment of the present invention, the traffic-based electromechanical equipment management method includes: Step S100: Receive the application listing instruction from the cloud and publish the target application in the preset operating system application library.

[0031] Jihong App Store's operating logic is as follows: Figure 2As shown, application developers (individuals / enterprises) access the application workbench through the developer portal of the Kaihong Cloud Service Platform to complete application development, debugging, integration, and deployment, as well as business rule editing and publishing. The submitted content flows to the Kaihong Operations Management Platform, where platform operators review, categorize, operate, and distribute the applications. Approved applications then enter the industry application marketplace for private clients to search, subscribe to, and download. Simultaneously, all operations within the entire business layer are technically supported by the infrastructure layer's environment services, middleware services, and third-party services.

[0032] For example, the application store in this application is implemented based on the low-code application development technology of KaihongOS Meta. Specifically, based on KaihongOS Meta, Jihong AppStore implements low-code development of KaihongOS applications, AI applications, atomic service applications, business rule applications, and device plugin applications. The specific development process is shown in the following pseudocode block: Algorithm: Unified Low-Code Development Input: AT ∈ {KAIHONG_OS, AI, ATOMIC, RULE, PLUGIN}, CP Output: DA, DS function lowCodeDevelopment(AT, CP): switch AT: KAIHONG_OS: return Algorithm1(CP.requirements, CP.certificateInfo) AI: return Algorithm2(CP.modelFile, CP.chipSpecification) ATOMIC: return Algorithm3(CP.serviceRequirements, CP.metadataSpec) RULE: return Algorithm4(CP.businessLogic, CP.ruleParameters) PLUGIN: return Algorithm5(CP.protocolFile, CP.deviceSpec) function automatedSubmission(app, AT): VR ← validateApplicationSpecification(app, AT) if not VR.passed: return {status: "failed", error: VR.errorMessage} AP ← packageApplication(app, AT) SP ← automatedSigning(AP, AT) SSR ← JiHongAppStore.submitApplication(SP, AT) if SSR.success: configureDistributionPolicy(app, SSR.applicationId) return {status: SSR.status, applicationId: SSR.applicationId} This application is based on a cloud-edge-device collaborative architecture, and the Jihong operating system provides a unified, secure, and efficient distribution and deployment mechanism for various applications.

[0033] The application distribution and deployment process of Jihong AppStore is as follows: 1. Cloud: Jihong AppStore serves as a unified entry point, providing functions such as application listing, review, version management, and authorized distribution; 2. Edge: Jihong edge components are responsible for receiving cloud distribution instructions, performing application pre-testing, policy distribution, and local management; 3. Device: Jihong OS components run on devices such as Jihong controllers and adapters, executing applications, plugins, and rules, and supporting near-field operation and maintenance and device-side closed-loop. Figure 3 As shown.

[0034] The distribution or deployment process for KaihongOS applications, AI applications, atomic service applications, business rule applications, and device plug-in applications is as follows: Figure 4 As shown.

[0035] In this embodiment of the application, step S100 specifically includes: Step S110: Receive the application listing instruction from the cloud. After creating a project based on DevEco Studio, use the pre-built configuration templates and visual signature management tools of the Kaihong Super Device Management Platform to complete the process of signature and certificate management, project configuration modification, development environment and build tool adaptation, atomic service development, and application listing material preparation and uploading. Step S120: Publish the target application in a preset operating system application library, wherein the operating system application library is the Kaihong operating system application library.

[0036] The target application of this application is the KaihongOS application. The core of low-code development for KaihongOS applications lies in its standardized templates and visual configuration. After creating a project based on DevEco Studio, developers can use the pre-built configuration templates and visual signature management tools in KaihongOSMeta to complete the process of signing and certificate management, modifying project configurations, adapting development environments and build tools, developing atomic services, and preparing and uploading application submission materials. This completes the application configuration and submission process without the need to manually write submission scripts or handle distribution logic.

[0037] like Figure 1 As shown in the embodiments of the present invention, the traffic-based electromechanical equipment management method further includes: Step S200: The edge terminal corresponding to each traffic segment obtains the target application published in the cloud, performs compatibility testing and pre-deployment on the target application, and obtains the target application package.

[0038] Step S300: Each edge terminal sends the target application package to the electromechanical equipment terminals used in each traffic segment, so as to manage the electromechanical equipment terminals based on the target application package.

[0039] For example, when distributing KaihongOS applications, developers list their applications in the KaihongOS application library in the cloud, and release them after review and signing. At the edge, the application and service modules of the edge Meta platform subscribe to applications from the Jihong App Store for compatibility testing and pre-deployment. At the electromechanical equipment end, the application is distributed to the terminal application market through the edge platform, and users can install, update, and uninstall the target application on the device.

[0040] This application publishes the target application in the cloud-based operating system application library, enabling the edge devices corresponding to each traffic segment to obtain the target application, which is then distributed to the electromechanical equipment used in each traffic segment. The target application package is used to manage the electromechanical equipment, thereby improving the integrated intelligent control capability and the efficiency of multi-task collaboration. This avoids the problem that traditional management models are unable to achieve refined management and rapid response.

[0041] In one embodiment of this application, the traffic-based electromechanical equipment management method further includes: If the cloud receives an instruction to upload an AI application, it will publish the target AI application in the preset AI model library and perform version management, scenario classification and permission control on the target AI application. Each traffic segment's corresponding edge terminal obtains the target AI application published in the cloud, performs local optimization and testing on the target AI application, encapsulates the target AI application into a downloadable plugin, and uses the deployment function to distribute the downloadable plugin to the electromechanical equipment used in each traffic segment; The electromechanical equipment used in each traffic section receives the downloadable plugin and executes the function corresponding to the target AI application based on the downloadable plugin.

[0042] For example, when deploying AI applications, models are uploaded to the AI ​​model library in the cloud for version management, scene classification, and access control; the edge AI module at the edge receives the models, performs local optimization and testing, and encapsulates them into a downloadable plugin; the AI ​​model plugin is then deployed to the Jihong controller or adapter at the electromechanical equipment end through the deployment function to perform functions (such as video analysis and event recognition) on the edge side.

[0043] In this embodiment of the application, the target AI application is a deployable container image; the container image is obtained by using the graphical model conversion tool provided by the Kaihong Super Device Management Platform to convert the model into a format that can run on the target chip, and to perform quantization and accuracy comparison through a visual interface. The converted model is packaged into a standard service through the Python SDK, and the service is built through Docker image, automatically packaging the code that implements the standard service.

[0044] The core of this application's low-code AI application development lies in the standardized encapsulation of model conversion and services. Developers do not need to write low-level chip adaptation code; they only need to use the graphical model conversion tool provided by KaihongOS Meta to convert the ONNX model into the RKNN format that can run on RK35x8 series chips, and complete quantization and accuracy comparison through a visual interface. The converted model is encapsulated into a standard service through the Python SDK, and KaihongOS Meta provides a Docker image building service to automatically package the Python code into a deployable container image.

[0045] In one embodiment of this application, the traffic-based electromechanical equipment management method further includes: If the cloud receives an instruction to deploy an atomic service application, it provides a metadata configuration interface to obtain the configured metadata and obtain the target atomic service application based on the metadata. The cloud publishes the target atomic service application in the preset atomic service library and generates the atomic service package corresponding to the target atomic service application; Each traffic segment's corresponding edge terminal obtains the atomized service package and distributes the atomized service package to the electromechanical equipment terminals used in each traffic segment; The electromechanical equipment used in each traffic segment performs service flow and cross-device collaboration based on the atomic service package.

[0046] For example, when distributing atomic service applications, lightweight, installation-free atomic service applications are listed in the atomic service library in the cloud; the edge device receives the atomic service package (ZIP / HAP format) and distributes it to the electromechanical equipment; users on the electromechanical equipment can download and use it directly through the Jihong App Store, supporting service flow and cross-device collaboration.

[0047] The core of the low-code development of atomic service applications in this application lies in the rapid implementation of the "installation-free" and "direct service access" features. After developers create atomic service projects in DevEco Studio, KaihongOS Meta ensures that the services comply with the installation-free specification through pre-defined configuration rules and automated build processes. Although service cards require front-end coding, card templates and standardized interfaces make card development modular. During the deployment process, KaihongOS Meta provides a complete metadata configuration interface. Developers do not need to write installation package deployment logic; the system automatically handles service subscription, distribution, and client-side launch mechanisms, enabling lightweight services to be quickly deployed and streamlined.

[0048] In this embodiment of the application, the traffic-based electromechanical equipment management method further includes: If the cloud receives a business orchestration instruction, it will orchestrate the business rules in the preset scenario application plugin library to form a rule package; The edge devices corresponding to each traffic segment obtain the rule package, and after verifying and rehearsing the rule package using the rule engine, deploy it to the electromechanical equipment used in each traffic segment. The electromechanical equipment used in each traffic segment performs closed-loop control based on the rule package.

[0049] For example, when deploying business rule applications, business rules (such as linkage control and energy-saving strategies) are arranged in the scenario application plugin library in the cloud to form rule templates; at the edge, the edge rule engine receives rule packages and performs verification and rehearsal; the rules are distributed to the Jihong OS on the electromechanical equipment through the deployment function, and closed-loop control such as device linkage and event response is executed on the edge.

[0050] In this embodiment of the application, the step "If the cloud receives a business orchestration instruction, then orchestrate business rules in the preset scenario application plugin library to form a rule package" specifically includes: If the cloud receives a business orchestration instruction, then use the business rule editor to drag and drop trigger nodes, processing nodes and execution nodes from the node library, and build a complete business logic flow by connecting them. Each node provides form-based configuration to complete the orchestration of business rules in the preset scenario application plugin library to form a rule package.

[0051] The development of the business rules in this application is a purely visual orchestration process, truly code-free development. Developers use the business rule editor in KaihongOS Meta to drag and drop "trigger nodes" (such as timers and event reporting), "processing nodes" (such as conditional judgments and data calculations), and "execution nodes" (such as device control and message pushes) from the left-hand node library, connecting them to build a complete business logic flow. Each node provides form-based configuration, such as setting timeouts, selecting device attributes, and writing judgment conditions. Developers can achieve cross-device linkage and automation scenarios without writing any control logic code.

[0052] In this embodiment of the application, the traffic-based electromechanical equipment management method further includes: If the cloud receives a plugin application upload instruction, it obtains the uploaded protocol plugin package, and based on the preset standard object model library and product template, completes the mapping configuration of device data points and standard object model attributes, events and methods in the graphical interface to obtain the device plugin. The edge terminal corresponding to each traffic segment obtains the device plugin, and automatically adapts to the same type of device according to the device type and application scenario corresponding to the device plugin to determine the target electromechanical equipment terminal, and deploys the device plugin to the target electromechanical equipment terminal; The target electromechanical equipment terminal uses the device plug-in to quickly connect to the device, collect data, and / or issue commands.

[0053] For example, when deploying device plug-in applications, various electromechanical device plug-ins (protocol parsing, drivers, etc.) are managed in the device access plug-in library in the cloud; at the edge, appropriate plug-ins are selected and deployed to the controller of the corresponding electromechanical device according to the device type and scenario; at the electromechanical device, the plug-ins run on Jihong OS to realize rapid device access, data collection, and command issuance.

[0054] The core of this application's low-code development of device plugins lies in the configurable protocol parsing and object model mapping. Developers do not need to write communication protocol parsing code; instead, they upload protocol plugin packages (such as JAR or SO files) through KaihongOS Meta and complete the mapping configuration between device data points and standard object model attributes, events, and methods in a graphical interface. KaihongOS Meta provides a standard object model library and product templates; developers can simply drag and drop to define device capabilities. After the plugin is uploaded, it can be associated with a specific product model, automatically adapting to similar devices during deployment, enabling plug-and-play and rapid integration of third-party devices, and shielding the coding complexity caused by protocol differences.

[0055] The Jihong AppStore proposed in this application is not a traditional application distribution channel, but rather an integrated application ecosystem hub and empowerment platform tailored for the digital upgrade of highway electromechanical systems. It deeply integrates HarmonyOS native technology, industry knowledge, and ecosystem operation thinking, aiming to systematically solve the long-standing core pain points in the transportation electromechanical field, such as fragmentation, silos, and strong coupling between software and hardware, through unified standards, reliable processes, and an open architecture. This application systematically analyzes how it constructs a sustainable, secure, efficient, and deeply industry-adapted digital application ecosystem from six dimensions: purpose and objectives, application system, core functions, operating logic, development model, and distribution deployment system, thereby providing core software support and innovative impetus for the Jihong digital foundation.

[0056] First, the purpose and function of vertical focus. The unique feature of Jihong AppStore lies in its deep vertical industry empowerment platform. It is not a general store for the consumer market, but rather specifically designed to solve the persistent problems of "siloed systems and strong hardware-software coupling" in highway electromechanical systems. Its core objective is to build a unified cloud-edge-device ecosystem integrating development, distribution, and management, enabling rapid deployment, remote upgrades, and unified control of all electromechanical equipment. This transforms dispersed electromechanical equipment into flexibly schedulable and continuously evolving digital assets, driving business from "single-point intelligence" to "system intelligence."

[0057] Second, a full-stack application system. Jihong AppStore has built a comprehensive application system covering the entire digital chain, such as... Figure 4 As shown, it not only provides traditional operating system applications and AI applications as basic computing power and interaction capabilities, but also innovatively integrates solution components for different scenarios: "use-and-go" atomic services meet flexible and lightweight interaction needs; while device plug-in applications are the cornerstone of realizing "Internet of Everything" in this system. Through standardized and configurable methods, it quickly abstracts and connects various heterogeneous electromechanical devices to a unified digital base, shielding them from the complex differences in underlying protocols; combined with business rule applications that can be quickly customized through visual orchestration, business personnel can combine device capabilities and business processes like building blocks without coding, quickly constructing scenario-based solutions such as inspection and emergency response. This system achieves full-stack coverage from "bottom-level device access" to "top-level business intelligence," perfectly matching the fragmented and ever-changing characteristics of industry businesses.

[0058] Third, the platform offers trusted and automated application lifecycle management. Jihong AppStore's core advantage lies in its end-to-end automated management and integrated control capabilities based on trusted mechanisms. Through standardized application signing and automated distribution and deployment toolchains, the platform seamlessly connects the entire application process from development and listing, version management to multi-platform deployment, achieving a highly efficient "one-time release, full-domain synchronization" operation and maintenance model. This not only greatly simplifies the complexity of software management for massive, distributed electromechanical equipment, but also ensures the accuracy of application distribution, the consistency of deployment, and the traceability of operation and maintenance through a unified control interface and automated strategies, thus providing solid technical support for the large-scale, highly reliable operation of highway electromechanical systems.

[0059] Fourth, the collaborative operational logic. Jihong AppStore has built a clear, open, and sustainable "production-operation-application" collaborative ecosystem model. Built on the mature Kaihong platform, it forms a closed loop of "developer innovation - operator review and quality control - end-user subscription and use." This logic not only ensures the reliability and quality of application sources but also supports private deployment through an industry application marketplace, balancing the needs of unified group management with the flexible customization requirements of various business units, providing a solid framework for the continued prosperity of the ecosystem and the iterative evolution of technology.

[0060] Fifth, Low-code Development Mode. Based on the low-code development mode of KaihongOS Meta, Jihong AppStore significantly reduces the development threshold and improves efficiency through standardized templates, visual orchestration, and full-process automation. Developers can complete AI model conversion, device protocol mapping, business rule orchestration, and atomic service configuration through a graphical interface without writing complex code, greatly shortening the development cycle. The platform's built-in signature management, object model library, and containerized construction tools ensure application security and standardization. This mode not only accelerates the digital implementation of smart transportation scenarios but also provides efficient and reliable technical support for the ecological co-construction of Jihong's digital foundation. Table 3 shows the comparative advantages of the low-code development mode based on KaihongOSMeta compared to the high-code development mode.

[0061] Table 3

[0062] Sixth, a cloud-edge-device collaborative application distribution and deployment system. Jihong AppStore has built an integrated cloud-edge-device application distribution and deployment system with the following advantages: It achieves centralized and standardized management of all self-developed and ecosystem applications through a unified entry point, unified permissions, and unified updates; it maximizes resource utilization efficiency by relying on a collaborative mechanism of cloud storage, edge preprocessing, and device-side execution; it supports closed-loop device-side business, real-time edge collaboration, and intelligent cloud-based coordination, ensuring rapid response and high reliability for critical businesses; it supports independent upgrades, canary releases, and version rollbacks, achieving flexible and smooth system updates; and it is highly secure and controllable, ensuring trustworthy distribution across the entire chain through application signing, device authentication, communication encryption, and hierarchical permissions. Based on this system, Jihong AppStore continuously promotes the listing and iteration of applications, plugins, models, and business rules, building a constantly growing open ecosystem and providing strong application support and evolution capabilities for the "Jihong Digital Foundation."

[0063] In summary, the Jihong AppStore of this application, based on a cloud-edge-device collaborative architecture, constructs an integrated process covering application listing, review, distribution, and management. It achieves unified management and efficient collaboration of software across the group's cloud, roadside edges, and field equipment, providing a framework for the digital management and control of massive amounts of electromechanical equipment. In terms of technical implementation, Jihong AppStore possesses two core capabilities: first, it provides low-code development support based on KaihongOS Meta, significantly reducing the development threshold; second, it constructs an application distribution and deployment system based on a cloud-edge-device collaborative architecture, achieving reliable and efficient end-to-end software delivery. Regarding application advantages, Jihong AppStore demonstrates six core values: vertically focused uses and purposes, a full-stack application system, reliable and automated application lifecycle management, collaboratively driven operational logic, a low-code development model, and a cloud-edge-device collaborative application distribution and deployment system. Based on this design, technology and advantages, Jihong AppStore systematically solved the digitalization problem of electromechanical systems, driving the evolution of highway electromechanical systems from single-point function automation to intelligent, service-oriented and low-carbon systems across the entire road section and life cycle, and propelling highway electromechanical systems into a new development stage centered on "software-defined and ecosystem-driven".

[0064] In one embodiment, such as Figure 5 As shown, based on the above-mentioned traffic-based electromechanical equipment management method, the present invention also provides a traffic-based electromechanical equipment management system, the system comprising: a cloud 100, an edge terminal 200 corresponding to a traffic segment, and an electromechanical equipment terminal 300 used in the traffic segment; The cloud 100 is used to receive application listing instructions and publish the target application in the preset operating system application library; The edge terminal 200 corresponding to each traffic segment is used to obtain the target application published in the cloud, perform compatibility testing and pre-deployment of the target application to obtain the target application package; and distribute the target application package to the electromechanical equipment terminal 300 used in each traffic segment to manage the electromechanical equipment terminal based on the target application package.

[0065] It should be noted that the foregoing explanation of the embodiment of the traffic-based electromechanical equipment management method also applies to the traffic-based electromechanical equipment management system of this embodiment, and will not be repeated here.

[0066] This invention discloses a traffic-based electromechanical equipment management system. The system receives application deployment instructions from the cloud and publishes the target application in a pre-defined operating system application library. Edge devices corresponding to each traffic segment obtain the published target application, perform compatibility testing and pre-deployment, and obtain a target application package. Each edge device then distributes the target application package to the electromechanical equipment used in each traffic segment for management. This application improves integrated intelligent control capabilities and enhances multi-task collaboration efficiency by publishing the target application in the cloud's operating system application library, enabling edge devices corresponding to each traffic segment to obtain the target application and distribute it to the electromechanical equipment used in each segment. The use of the target application package for equipment management improves integrated intelligent control capabilities and enhances multi-task collaboration efficiency, avoiding the problems of traditional management models in achieving refined management and rapid response.

[0067] This embodiment also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described traffic-based electromechanical equipment management method.

[0068] In the description of this specification, the references to terms such as "one embodiment," "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. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0069] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0070] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0071] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a ordered list of executable instructions for implementing logical functions, and can be embodied 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 read and execute instructions from or in conjunction with such 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). In addition, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically by optically scanning paper or other media, then editing, interpreting or otherwise processing them as necessary, and then storing them in computer memory.

[0072] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. 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.

[0073] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by a program instructing related hardware, and the program can be stored in a computer-readable storage medium. When executed, the program includes one or a combination of the steps of the method embodiments.

[0074] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0075] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. 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 traffic-based electromechanical equipment management method, used in a traffic-based electromechanical equipment management system, characterized in that, The system includes a cloud platform, an edge terminal corresponding to a traffic segment, and electromechanical equipment terminals used in the traffic segment; the method includes: The cloud receives the application listing instruction and publishes the target application in the preset operating system application library; Each traffic segment's corresponding edge terminal obtains the target application published in the cloud, performs compatibility testing and pre-deployment on the target application, and obtains the target application package; Each edge device distributes the target application package to the electromechanical equipment used in each traffic segment, so as to manage the electromechanical equipment based on the target application package.

2. The traffic-based electromechanical equipment management method according to claim 1, characterized in that, The cloud receives the application deployment instruction and publishes the target application in the preset operating system application library, including: After receiving the application listing instruction in the cloud, the project is created based on DevEco Studio. Then, using the pre-built configuration templates and visual signature management tools of the Kaihong Super Device Management Platform, the process of signing and certificate management, project configuration modification, development environment and build tool adaptation, atomic service development, and application listing material preparation and uploading is completed. The target application is published in a preset operating system application library, which is the Kaihong operating system application library.

3. The traffic-based electromechanical equipment management method according to claim 1, characterized in that, The traffic-based electromechanical equipment management method also includes: If the cloud receives an instruction to upload an AI application, it will publish the target AI application in the preset AI model library and perform version management, scenario classification and permission control on the target AI application. Each traffic segment's corresponding edge terminal obtains the target AI application published in the cloud, performs local optimization and testing on the target AI application, encapsulates the target AI application into a downloadable plugin, and uses the deployment function to distribute the downloadable plugin to the electromechanical equipment used in each traffic segment; The electromechanical equipment used in each traffic section receives the downloadable plugin and executes the function corresponding to the target AI application based on the downloadable plugin.

4. The traffic-based electromechanical equipment management method according to claim 3, characterized in that, The target AI application is a deployable container image. The container image is obtained by using the graphical model conversion tool provided by the Kaihong Super Device Management Platform to convert the model into a format that can run on the target chip, and to perform quantization and accuracy comparison through a visual interface. The converted model is packaged into a standard service through the Python SDK, and the service is built through Docker image, which automatically packages the code that implements the standard service.

5. The traffic-based electromechanical equipment management method according to claim 1, characterized in that, The traffic-based electromechanical equipment management method also includes: If the cloud receives an instruction to deploy an atomic service application, it provides a metadata configuration interface to obtain the configured metadata and obtain the target atomic service application based on the metadata. The cloud publishes the target atomic service application in the preset atomic service library and generates the atomic service package corresponding to the target atomic service application; Each traffic segment's corresponding edge terminal obtains the atomized service package and distributes the atomized service package to the electromechanical equipment terminals used in each traffic segment; The electromechanical equipment used in each traffic segment performs service flow and cross-device collaboration based on the atomic service package.

6. The traffic-based electromechanical equipment management method according to claim 1, characterized in that, The traffic-based electromechanical equipment management method also includes: If the cloud receives a business orchestration instruction, it will orchestrate the business rules in the preset scenario application plugin library to form a rule package; The edge devices corresponding to each traffic segment obtain the rule package, and after verifying and rehearsing the rule package using the rule engine, deploy it to the electromechanical equipment used in each traffic segment. The electromechanical equipment used in each traffic segment performs closed-loop control based on the rule package.

7. The traffic-based electromechanical equipment management method according to claim 6, characterized in that, If the cloud receives a business orchestration instruction, it will orchestrate business rules in a pre-defined scenario application plugin library to form a rule package, including: If the cloud receives a business orchestration instruction, it uses the business rule editor to drag and drop trigger nodes, processing nodes, and execution nodes from the node library, and connects them to build a complete business logic flow. Each node provides form-based configuration to complete the business rule orchestration in the preset scenario application plugin library and form a rule package.

8. The traffic-based electromechanical equipment management method according to claim 1, characterized in that, The traffic-based electromechanical equipment management method also includes: If the cloud receives a plugin application upload instruction, it obtains the uploaded protocol plugin package, and based on the preset standard object model library and product template, completes the mapping configuration of device data points and standard object model attributes, events and methods in the graphical interface to obtain the device plugin. The edge terminal corresponding to each traffic segment obtains the device plugin, and automatically adapts to the same type of device according to the device type and application scenario corresponding to the device plugin to determine the target electromechanical equipment terminal, and deploys the device plugin to the target electromechanical equipment terminal; The target electromechanical equipment terminal uses the device plug-in to quickly connect to the device, collect data, and / or issue commands.

9. A traffic-based electromechanical equipment management system, characterized in that, The system includes: a cloud platform, an edge terminal corresponding to a traffic segment, and electromechanical equipment terminals used in the traffic segment; The cloud is used to receive application listing instructions and publish the target application in a preset operating system application library; The edge terminals corresponding to each traffic segment are used to obtain the target application published in the cloud, perform compatibility testing and pre-deployment of the target application to obtain the target application package; and distribute the target application package to the electromechanical equipment terminals used in each traffic segment to manage the electromechanical equipment terminals based on the target application package.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that can be executed to implement the steps of the traffic-based electromechanical equipment management method as described in any one of claims 1 to 8.

Images