Intelligent converged terminal and its tagged code management method and medium

Abstract

The application provides a kind of intelligent fusion terminal and its tag code management method, medium, method includes: the intelligent fusion terminal service code is split according to function, obtain code module, respectively allocate function label for each code module;For new custom function demand, query the custom function label of label resource library, if custom function demand and custom function label match, reuse the custom function label and corresponding custom function code module;Otherwise, based on the difference of demand new custom function label and custom function code module;Based on the localization supplement agreement specification of each province, form province-tag mapping matrix;According to the input province parameter locking target adaptive province, load general function code module and custom function code module, compile and generate the exclusive terminal program of target province.For the custom function demand of each province, match and reuse the existing custom function label and corresponding code module, without repeated development.

Description

Technical Field

[0001] This invention belongs to the field of terminal code maintenance technology, and in particular relates to an intelligent converged terminal and its tagged code management method and medium. Background Technology

[0002] Intelligent converged terminals are core edge devices for distribution network operation monitoring, fault handling, and electricity consumption management, playing a crucial role in edge IoT agency and localized computing within the distribution IoT architecture. According to the State Grid's technical management system, intelligent converged terminals must strictly adhere to the technical standards uniformly released by the State Grid to complete type testing and grid access testing. Only after passing the tests can they be included in the State Grid's list of qualified materials, and the State Grid will organize centralized bidding and procurement for them from provincial power companies nationwide. Each provincial power company has formulated localized supplementary protocol specifications, differentiated business specifications, and customized functional requirements based on the State Grid's general standard system. This necessitates that intelligent converged terminal equipment be adapted to the differentiated field delivery scenarios across multiple provinces nationwide. As the number of provinces where companies win bids continues to increase, the multi-province compatibility issue is becoming increasingly prominent.

[0003] Currently, for multi-province adaptation scenarios, some companies in the industry adopt a code maintenance model of "one independent code branch per province." This means that a separate independent code branch is created for each province's localized customization needs, and each branch is responsible for feature development, version iteration, vulnerability fixing, adaptation debugging, and version release. As the number of provinces where companies win bids continues to increase, the number of independent branches in the code repository continues to surge, resulting in a large number of fragmented and independent code versions. This leads to prominent problems such as chaotic branch management, frequent merge conflicts, difficulty in tracing historical versions, and exponentially increasing management costs. At the same time, there are many overlapping and consistent customized functional requirements in the localized supplementary agreement specifications of various provinces across the country. These include common customized scenarios such as special data reporting mechanisms, local specification adaptation, and edge permission control. However, existing technologies cannot achieve cross-province function reuse, and the same customized functions still need to be repeatedly developed and deployed in each province's branch.

[0004] Therefore, the existing technology has the following shortcomings: First, for common updates such as iterations of the State Grid's general underlying functions, vulnerability fixes, and performance optimizations, operations and maintenance personnel need to manually modify, compile, test, and release versions for each of the independent code branches in all provinces, resulting in a huge amount of repetitive work and low R&D and operations efficiency. Second, overlapping customized functions in different provinces cannot be reused, and the same functional code is repeatedly stored and developed in multiple branches, resulting in extremely high code redundancy, a large amount of repetitive work, and a significant waste of R&D and server storage resources. Third, the multi-branch architecture has high code coupling and poor scalability, and the adaptation cycle for adding new provincial requirements or iterating customized functions is long and problem tracing is difficult, failing to meet the State Grid's large-scale, batch, and efficient terminal delivery and operations needs. Summary of the Invention

[0005] To address the problems existing in the prior art, the present invention provides a method for managing tag-based codes in intelligent converged terminals, comprising the following steps: Step S1: Construct a unique global main code branch. In the unique global main code branch, the intelligent fusion terminal business code is split according to function to obtain a general function code module and a customized function code module. Function tags are assigned to each code module, and the customized function tags corresponding to the customized function code module are archived to the tag resource library. Step S2: For the newly added customized function requirements, query the customized function tags in the tag resource library. If the customized function requirements match the customized function tags, reuse the customized function tags and the corresponding customized function code modules; if the customized function requirements do not match the customized function tags, create new customized function tags and customized function code modules based on the differentiated requirements. Step S3: Based on the localized supplementary protocol specifications of each province, configure corresponding customized function tags for each province to form a province-tag mapping matrix; Step S4: Based on the input province parameters, lock the target compatible province, load the general function code module, and filter the customized function code module based on the province-tag mapping matrix to compile and generate the exclusive terminal program for the target province.

[0006] Preferably, the method further includes: Step S5: When any code module is updated, the code module is modified in the unique global main code branch to synchronously complete the update of the corresponding province.

[0007] Based on the above scheme, the compilation of the dedicated terminal program for the target province in step S4 adopts a layered compilation strategy: The first layer loads the general-purpose functional code module; The second layer obtains the customized function tags bound to the target province based on the province-tag mapping matrix, loads the corresponding customized function code modules, and hides the customized function code modules corresponding to those not bound to customized function tags. All code modules loaded in the first and second layers are merged and compiled to generate a dedicated terminal program adapted to the target province.

[0008] Specifically, the general function code module is a basic function module required by the State Grid unified standard, and the general function tag corresponding to the general function code module is activated by default for all provinces; the customized function code module is a differentiated function module required by the localized supplementary protocol specifications of each province, and the customized function tag corresponding to the customized function code module is selectively activated according to the province.

[0009] Based on the above scheme, the province-tag mapping matrix is ​​used to represent the binding relationship between provinces and customized function tags. Specifically, it is a two-dimensional Boolean mapping matrix M, where M(i, j)=1 represents province p. i Activate custom function tags j M(i, j)=0 represents province p i Block custom function tags j .

[0010] Based on the above scheme, step S5 specifically includes: S51: When the general functions of the State Grid need to be updated, modify the general function code module corresponding to the unique global main code branch, and automatically synchronize and adapt to all provinces. S52: When the province customization function needs to be updated, query the province in the province-tag mapping matrix that configures the corresponding customization function tag of the code module, and synchronously update the province bound to the customization function tag.

[0011] Based on the above scheme, step S1 specifically includes: All business code of the intelligent converged terminal is decoupled and split, the basic functions of the State Grid unified standard are encapsulated into general function code modules, a set of general function tags is registered, and the general function code modules are bound to the general function tags; The localized customization functions of each province are broken down into customization function code modules, a set of customization function tags is registered and generated, and the customization function code modules are bound to the customization function tags.

[0012] Based on the above solution, the method for matching customized functional requirements with customized functional tags specifically includes: based on the newly added provincial customized functional requirements, synchronously parsing and extracting the business logic, adaptation protocol, and functional scenarios of the requirements to be matched; The requirements to be matched are compared item by item with the metadata of each customized function tag in the tag resource library. When the business logic, adaptation protocol and functional scenario are all consistent, the match is determined to be successful, and the customized function tag and its code module are directly reused. The metadata of the customized function tag includes the business logic, adaptation protocol and functional scenario description corresponding to the tag. If any item is different, the match is deemed to have failed, and a new custom function tag and custom function code module are created.

[0013] On the other hand, this application also provides an intelligent converged terminal, including a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the intelligent converged terminal tag code management method as described above.

[0014] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the intelligent converged terminal tag code management method described above.

[0015] Compared with the prior art, the present invention has the following beneficial effects: 1. By constructing a unique global main code branch and establishing a one-to-one binding relationship between functional tags and code modules, the decoupling of general basic functions and customized functions for each province is achieved, fundamentally eliminating the fragmented code management mode of "one independent code branch per province" in the existing technology, and greatly reducing code redundancy and storage resource consumption; 2. By setting up a tag resource library and establishing a tag matching mechanism, existing customized function tags and corresponding code modules can be matched and reused for the consistent customized function requirements of each province, eliminating the need for repeated development. This achieves cross-province sharing of customized function modules from the architectural level, significantly reducing the workload of repeated development. 3. By establishing a province-tag mapping matrix, coupled with a unified incremental iteration and version consistency verification mechanism, the iterative updates of State Grid's general functions only need to be modified once in the main code branch to be synchronized to all provinces, avoiding the problems of missed synchronization and incorrect synchronization caused by manual branch-by-branch synchronization; after the customized function is updated, all provinces that reuse the tag will automatically synchronize and take effect, without the need for province-by-province maintenance, which greatly improves the efficiency of R&D and maintenance, and ensures the uniformity of the terminal basic code version and the consistency of equipment operation in all provinces across the country; newly added winning provinces only need to be adapted by configuring the tag mapping relationship, which greatly shortens the delivery cycle and can meet the State Grid's large-scale, batch, and efficient terminal delivery and maintenance needs; 4. This invention modularizes and decouples the general functions of the State Grid and the customized functions of provinces through labeling. The code hierarchy is clear, highly readable and portable, and problem tracing, version rollback and function iteration are more convenient, effectively reducing the difficulty of later operation and maintenance. 5. All terminals across all provinces in China use the same set of national grid general basic code. They are adapted to localized customization needs only through functional tags, which solves the problem of inconsistent versions in the traditional multi-branch architecture, ensures the uniformity of the operation standards of terminal equipment across the network, and effectively reduces the failure rate of field equipment. Attached Figure Description

[0016] Figure 1 This is an overall flowchart of the intelligent fusion terminal tag code management method of the present invention; Figure 2 This is a flowchart illustrating the specific process of the tagged code management method of the present invention. Detailed Implementation

[0017] The invention will be further described below with reference to specific embodiments.

[0018] To address the technical problems of cumbersome operation and maintenance of a single branch in one province, easy omissions in synchronizing common functions across multiple branches, inability to reuse overlapping customized functions across provinces, and high code redundancy, this invention provides a method for managing tagged code in intelligent converged terminals, such as... Figure 1 and Figure 2 As shown, the method includes the following steps: Step S1: First, construct a unique global master code branch. This unique global master code branch serves as the main repository for business code. Within this branch, all business code for the intelligent converged terminal is decoupled and split according to function, resulting in general-purpose function code modules and customized function code modules. Both general-purpose and customized function code modules are stored within this unique global master code branch. The general-purpose function code modules are the basic function modules required by the State Grid's unified standard, while the customized function code modules are the differentiated function modules required by the localization supplementary agreements of each province.

[0019] Furthermore, custom function tags are assigned to custom function code modules, and the custom function tags corresponding to the custom function code modules are archived in the tag resource library, while general function tags are not stored in the tag resource library.

[0020] In this embodiment, step S1 specifically includes: All business code of the intelligent converged terminal is decoupled and split, and the basic functions of the State Grid's unified standard are encapsulated into general function code modules, which are then registered to form a general function tag set G={g1,g2,...,g m The general function tags are bound to the general function code modules; the general function tag set corresponds to the basic functions of the State Grid's unified standard, such as basic data collection, communication transmission, protocol adaptation, and equipment management. The general function tag is activated globally by default and is effective for terminals in all provinces. The localized customization functions for each province are broken down into the smallest granularity of customization function code modules that can be used independently in business operations, can be enabled or disabled individually, and cannot be further divided. A set of customization function tag S={s1,s2,...,s...} is then registered and generated. n The system binds custom function tags to custom function code modules. The minimum granularity is defined by the business function. Each minimum granularity module corresponds to an independent localized business and cannot be further divided into multiple independently runnable sub-businesses. Custom function tags correspond to the differentiated and customized functions required by the localized supplementary protocol specifications of each province. Each tag uniquely corresponds to a set of independently encapsulated custom function code modules, which can be freely reused in multiple provinces. Initialize the province identifier set P = {p1, p2, ..., p k This is a unique identification code assigned to each winning province nationwide, used to accurately locate the target province and achieve targeted function filtering.

[0021] Step S1 breaks down all business functions of the intelligent converged terminal into two categories: general basic functions of the State Grid and customized functions of each province. All functions are bound to a unique function tag, and all provinces in the country share a complete set of main code, thus solving the pain points of multi-branch operation and maintenance from an architectural perspective.

[0022] Step S2: For newly added customized function requirements, query the customized function tags in the tag resource library. If the customized function requirement matches the customized function tag, reuse the customized function tag and the corresponding customized function code module. If the customized function requirement does not match the customized function tag, create a new customized function tag and customized function code module based on the differentiated requirements, and include the new customized function tag in the tag resource library.

[0023] Each customized function tag stored in the tag resource library comes with its own metadata, which includes the corresponding business logic, adaptation protocol, and functional scenario description. The specific methods for matching customized function requirements with customized function tags include: Based on the newly added province-specific functional requirements, the business logic, adaptation protocols, and functional scenarios of the requirements to be matched are simultaneously parsed and extracted. The requirements to be matched are compared item by item with the metadata of each customized function tag in the tag resource library. When the business logic, adaptation protocol and functional scenario are all consistent, the match is determined to be successful and the customized function tag and its code module can be directly reused. If any item is different, the match is deemed to have failed, and a new custom function tag and code module need to be created.

[0024] Iterate through the custom function tags in the tag resource library and compare the consistency of business logic, adaptation protocol and functional scenario.

[0025] In step S2, if an existing customized function tag is matched in the tag resource library, the tag and the corresponding customized function module code are directly reused without repeated development; if no match is found, a new customized function code module is developed and a new customized function tag is registered and managed uniformly through the tag resource library. This existing tag matching and reuse mechanism reduces the cross-province repeated development work from the source.

[0026] Step S3: Based on the localized supplementary protocol specifications of each province, configure corresponding customized function tags for each province to form a province-tag mapping matrix; Specifically, the province-tag mapping matrix is ​​used to bind provinces to customized function tags. With provinces as rows and customized function tags as columns, the province-tag mapping matrix M(k×n) is initialized and updated, where k is the total number of winning provinces in the country and n is the total number of customized function tags. In this embodiment, the province-tag mapping matrix is ​​used to represent the binding relationship between provinces and customized function tags. Specifically, it is a two-dimensional Boolean mapping matrix M, where M(i, j) being 1 indicates that province p i Activate custom function tags j M(i, j) being 0 indicates that province p i Block custom function tags j .

[0027] Through step S3, the province-tag matrix mapping enables the same customized function tag to be bound to multiple provinces with overlapping needs, thus realizing the sharing and reuse of a single function module across multiple provinces.

[0028] Step S4: During the code compilation stage, the target province is locked based on the input province parameter, and the customized function code module is filtered based on the province-tag mapping matrix to compile and generate the exclusive terminal program for the target province. The province parameter is the province identifier parameter passed in the compilation execution command, which is used to specify the target province to be adapted in this compilation.

[0029] In step S4, the compilation of the dedicated terminal program for the target province adopts a layered compilation strategy: The first layer loads all common function code modules; among them, the common function code modules are labeled with common function tags, which serve as module identity identifiers; The second layer obtains the custom function tags bound to the target province based on the province-tag mapping matrix, loads the corresponding custom function code modules, and hides the custom function code modules corresponding to those not bound to custom function tags. All code modules loaded in the first and second layers are merged and compiled to generate a dedicated terminal program adapted to the target province. It's important to note that general function tags and customized function tags are only used for identification and filtering logic; the tags themselves do not participate in the compilation process. The compilation target is the code module.

[0030] According to step S4, the province-tag mapping matrix only contains customized function tags and does not contain general function tags. The general function code modules corresponding to the general function tags are forcibly loaded during the compilation stage and are not controlled by this matrix. The set of customized functions that need to be enabled by each province terminal is determined only through the province-tag mapping matrix.

[0031] The compiled version obtained in step S4 only contains general functions of the State Grid and customized functions that are specific to or reused in the target province. There is no redundant code, and it supports batch rapid compilation and on-site deployment in multiple provinces.

[0032] Preferably, the tagged code management method further includes: Step S5: When any code module is updated, modify the code module in the unique global main code branch to synchronously complete the update of the corresponding province.

[0033] In this embodiment, step S5 specifically includes: S51: When the general functions of the State Grid need to be updated, such as when there are update requirements for vulnerability repair, version iteration, performance optimization, etc., modify the general function code module corresponding to the unique global main code branch and automatically synchronize and adapt to all provinces. S52: When the province customization function needs to be updated, query the province in the province-tag mapping matrix that configures the corresponding customization function tag of the code module, and update the province bound to the customization function tag synchronously.

[0034] Step S5: Iterative repairs and performance optimizations of general functions of China.com only require updating the main code branch, and all provincial terminals across the network will automatically synchronize and take effect. After the customized function code module is iterated and upgraded, all provinces that reuse the customized function tag will complete the update synchronously, without the need for province-by-province maintenance.

[0035] In this embodiment, the present invention also performs version consistency verification and source tracing management, including: The common basic code for terminals in each province is taken from a single global main code branch to ensure that the common basic code versions are naturally from the same source and consistent. Based on the province-tag mapping matrix, obtain the list of customized function tags bound to each province. Combined with the lifecycle record chain indexed by the function tags, compare the code module versions corresponding to the same customized function tag in different provinces to complete the version consistency verification of customized functions.

[0036] A complete lifecycle record chain indexed by function tags is formed by recording the following information: In response to the creation of any new custom function tag, record the creation time of the custom function tag, the code module identifier it is bound to, and the source of the provincial requirements on which the creation is based; In response to the activation of a customized feature tag in any province, record the establishment time and operation log of the binding relationship; In response to a version update of any code module, record the version change history and change descriptions for that code module.

[0037] Through the above version verification and traceability management, the terminal version can be traced, the adaptation status can be controlled, and version anomalies can be detected and warned in a timely manner.

[0038] According to a specific embodiment of the present invention, when a new winning province is added, it is not necessary to create a new code branch, as follows: The localized customization requirements of the province are broken down, and the existing customized function tags in the tag resource library are traversed through the tag reuse matching module. For existing function tags that match, reuse them directly; for custom function requirements that cannot match, develop new custom function code modules and register new function tags. Update the province-tag mapping matrix M and activate the customized function tag corresponding to the province. By inputting the province parameter of the newly added province, layered compilation is performed to quickly generate a dedicated terminal program adapted to that province and then deploy it on-site.

[0039] This invention accurately identifies homogeneous customization needs across multiple provinces through tag comparison and reuse. Existing functional tags can be directly reused across provinces without the need for repeated development of functional code modules, thereby reducing redundant R&D work from the source, simplifying the code repository architecture, and reducing server storage resource consumption.

[0040] Based on the same technical concept, the present invention also provides an intelligent converged terminal, including a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the intelligent converged terminal tag code management method as described above.

[0041] A processor can perform various actions and processes according to a program stored in memory. Specifically, a processor can be an integrated circuit chip with signal processing capabilities. The aforementioned processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor, and can be based on an x86 architecture or an ARM architecture.

[0042] The memory stores computer-executable instructions that, when executed by a processor, implement the aforementioned intelligent converged terminal tag code management method. The memory can be volatile or non-volatile, or may include both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). It should be noted that the memory used in the methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0043] Furthermore, the intelligent converged terminal tagging code management method according to the present invention can be recorded in a computer-readable recording medium. Specifically, according to the present invention, a computer-readable recording medium storing computer-executable instructions can be provided, which, when executed by a processor, causes the processor to execute the intelligent converged terminal tagging code management method as described above.

[0044] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functions, and operations that may be implemented by methods, terminals, and computer-readable recording media according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or portion of code containing at least one executable instruction for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutively represented blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0045] In general, various exemplary embodiments of the present invention can be implemented in hardware or dedicated circuitry, software, firmware, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. When aspects of embodiments of the present invention are illustrated or described as block diagrams, flowcharts, or represented using certain other images, it will be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented as non-limiting examples in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or certain combinations thereof.

[0046] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

[0047] While the specific embodiments of the present invention have been described above, they are not intended to limit the scope of protection of the present invention. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art without creative effort based on the technical solutions of the present invention are still within the scope of protection of the present invention.

Claims

1. A method for managing tag-based codes in intelligent converged terminals, characterized in that, The method includes the following steps: Step S1: Construct a unique global main code branch. In the unique global main code branch, the intelligent fusion terminal business code is split according to function to obtain a general function code module and a customized function code module. Function tags are assigned to each code module, and the customized function tags corresponding to the customized function code module are archived to the tag resource library. Step S2: For the newly added customized function requirements, query the customized function tags in the tag resource library. If the customized function requirements match the customized function tags, reuse the customized function tags and the corresponding customized function code modules; if the customized function requirements do not match the customized function tags, create new customized function tags and customized function code modules based on the differentiated requirements. Step S3: Based on the localized supplementary protocol specifications of each province, configure corresponding customized function tags for each province to form a province-tag mapping matrix; Step S4: Based on the input province parameters, lock the target compatible province, load the general function code module, and filter the customized function code module based on the province-tag mapping matrix to compile and generate the exclusive terminal program for the target province.

2. The intelligent converged terminal tag code management method according to claim 1, characterized in that, The method further includes: Step S5: When any code module is updated, the code module is modified in the unique global main code branch to synchronously complete the update of the corresponding province.

3. The intelligent converged terminal tag code management method according to claim 1, characterized in that, In step S4, the compilation of the dedicated terminal program for the target province adopts a layered compilation strategy: The first layer loads the general-purpose functional code module; The second layer obtains the customized function tags bound to the target province based on the province-tag mapping matrix, loads the corresponding customized function code modules, and hides the customized function code modules corresponding to those not bound to customized function tags. All code modules loaded in the first and second layers are merged and compiled to generate a dedicated terminal program adapted to the target province.

4. The intelligent converged terminal tag code management method according to claim 1, characterized in that, The general function code module is a basic function module required by the State Grid's unified standard, and the general function tag corresponding to the general function code module is activated by default for all provinces; the customized function code module is a differentiated function module required by the localized supplementary protocol specifications of each province, and the customized function tag corresponding to the customized function code module is selectively activated according to the province.

5. The intelligent converged terminal tag code management method according to claim 1, characterized in that, The province-tag mapping matrix is ​​used to represent the binding relationship between provinces and customized function tags. Specifically, it is a two-dimensional Boolean mapping matrix M, where M(i,j)=1 represents province p. i Activate custom function tags j M(i, j)=0 represents province p i Block custom function tags j .

6. The intelligent converged terminal tag code management method according to claim 2, characterized in that, Step S5 specifically includes: S51: When the general functions of the State Grid need to be updated, modify the general function code module corresponding to the unique global main code branch, and automatically synchronize and adapt to all provinces. S52: When the province customization function needs to be updated, query the province in the province-tag mapping matrix that configures the corresponding customization function tag of the code module, and synchronously update the province bound to the customization function tag.

7. The intelligent converged terminal tag code management method according to claim 1, characterized in that, Step S1 specifically includes: All business code of the intelligent converged terminal is decoupled and split, the basic functions of the State Grid unified standard are encapsulated into general function code modules, a set of general function tags is registered, and the general function code modules are bound to the general function tags; The localized customization functions of each province are broken down into customization function code modules, a set of customization function tags is registered and generated, and the customization function code modules are bound to the customization function tags.

8. The intelligent converged terminal tag code management method according to claim 1, characterized in that, The method for matching customized feature requirements with customized feature tags specifically includes: Based on the newly added province-specific functional requirements, the business logic, adaptation protocols, and functional scenarios of the requirements to be matched are simultaneously parsed and extracted. The requirements to be matched are compared item by item with the metadata of each customized function tag in the tag resource library. When the business logic, adaptation protocol and functional scenario are all consistent, the match is determined to be successful, and the customized function tag and its code module are directly reused. The metadata of the customized function tag includes the business logic, adaptation protocol and functional scenario description corresponding to the tag. If any item is different, the match is deemed to have failed, and a new custom function tag and custom function code module are created.

9. A smart converged terminal, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the intelligent converged terminal tag code management method as described in any one of claims 1-8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the intelligent converged terminal tag code management method as described in any one of claims 1-8.

Images