Communication engineering data processing method and device and electronic equipment

Abstract

The invention discloses a communication engineering data processing method and device and electronic equipment, belongs to the technical field of communication engineering, and is used for improving task processing efficiency and data acquisition accuracy in a communication engineering data processing process. Comprising the steps of obtaining a corresponding target work order template from a communication engineering template center through a communication engineering tool system according to target task information of a to-be-executed task; in response to a filling operation performed by the first user based on the target work order template, submitting the filled service resource data to a communication engineering template center; generating an acquisition result corresponding to the to-be-executed task through the communication engineering template center according to the business resource data and the target work order template; and the communication engineering template center associates the business data with a data field of a corresponding first database entity in a database of the communication engineering template center, dynamically generates a corresponding second database entity according to the information of the resource entity, and associates the second database entity with entity configuration information corresponding to the target work order template.

Description

Technical Field

[0001] This application belongs to the field of communication engineering technology, and specifically relates to a communication engineering data processing method, apparatus and electronic equipment. Background Technology

[0002] In telecommunications network construction projects, the planning, surveying, and design phase, as the preliminary stage, significantly impacts the accuracy and completeness of the data collected. In related technologies, predefined, fixed templates are typically used for data collection. These templates exist statically within the relevant digital systems, containing fixed data fields and formats. Users must follow the template requirements to enter data and generate reports.

[0003] However, this method of processing communication engineering data based on fixed templates lacks flexibility due to the inflexibility of predefined data fields and formats, making it difficult to adapt to the specific needs of different projects or scenarios. In practical applications, this affects the accuracy and completeness of data collection. Furthermore, the increased manual intervention (such as manual processing of results) not only leads to low task processing efficiency but also affects the consistency of task processing. With the continuous expansion and increasing complexity of communication networks, existing communication engineering data processing solutions can no longer meet the actual needs of business development. Summary of the Invention

[0004] This application provides a communication engineering data processing method, apparatus, and electronic device to improve task processing efficiency and data acquisition accuracy in the communication engineering data processing process.

[0005] In a first aspect, embodiments of this application provide a communication engineering data processing method, comprising: obtaining a corresponding target work order template from a communication engineering template center based on target task information of a task to be executed through a communication engineering tool system; the communication engineering template center storing the correspondence between task information and pre-configured work order templates; submitting filled-in business resource data to the communication engineering template center in response to a filling operation performed by a first user based on the target work order template; the business resource data including business data and information of resource entities, the resource entities including communication engineering objects that can be allocated, scheduled, or managed; generating collection results corresponding to the task to be executed through the communication engineering template center based on the business resource data and the target work order template; wherein, the communication engineering template center is used to associate the business data with the data fields of a corresponding first database entity in the database of the communication engineering template center; and is used to dynamically generate a corresponding second database entity based on the information of the resource entity, and associate the second database entity with the entity configuration information corresponding to the target work order template. Secondly, embodiments of this application provide a communication engineering data processing apparatus, comprising: a first acquisition module, configured to acquire a corresponding target work order template from a communication engineering template center based on target task information of a task to be executed through a communication engineering tool system; the communication engineering template center stores a correspondence between task information and pre-configured work order templates; a submission module, configured to submit filled-in business resource data to the communication engineering template center in response to a filling operation performed by a first user based on the target work order template; the business resource data includes business data and information of resource entities, the resource entities including communication engineering objects that can be allocated, scheduled, or managed; and a first generation module, configured to generate the collection results corresponding to the task to be executed based on the business resource data and the target work order template through the communication engineering template center; wherein the communication engineering template center is configured to associate the business data with the data fields of a corresponding first database entity in the database of the communication engineering template center; and to dynamically generate a corresponding second database entity based on the information of the resource entity, and associate the second database entity with the entity configuration information corresponding to the target work order template.

[0006] Thirdly, embodiments of this application provide an electronic device including a processor; and a memory arranged to store computer-executable instructions configured to be executed by the processor to implement the steps of the communication engineering data processing method as described in the first aspect.

[0007] Fourthly, embodiments of this application provide a computer-readable storage medium for storing computer-executable instructions, which, when executed by a processor, implement the steps of the communication engineering data processing method as described in the first aspect.

[0008] Fifthly, embodiments of this application provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the communication engineering data processing method as described in the first aspect.

[0009] In a sixth aspect, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run executable instructions to implement the steps of the communication engineering data processing method as described in the first aspect.

[0010] In the embodiments of this application, the communication engineering template center stores the correspondence between task information and pre-configured work order templates. Therefore, this technical solution enables centralized management and configuration of various work order templates through the communication engineering template center. Compared to existing solutions where each tool system independently manages and configures work order templates, this technical solution simplifies the maintenance and management of work order templates and improves overall operational efficiency. Furthermore, by separating the management and configuration of work order templates from each tool system, the content and structure of work order templates can be dynamically adjusted without affecting communication engineering data processing. This allows for better adaptation to different business lines, regional characteristics, and customer needs, enhancing the dynamism and flexibility of work order templates and providing reliable assurance for the accuracy and completeness of data collection. Based on this, in the communication engineering data processing flow, the communication engineering tool system retrieves the corresponding target work order template from the communication engineering template center based on the target task information of the task to be executed, achieving automatic matching of task information and work order templates, eliminating the need for users to manually filter templates. Thus, for the first user's filling operation based on the target work order template, the filled-in business resource data is submitted to the communication engineering template center. Business resource data encompasses business data and resource entity information, with resource entities including communication engineering objects that can be allocated, scheduled, or managed. By guiding the first user to fill in business resource data using a work order template, not only is the standardization of submitted data ensured, but the operational difficulty for non-professional users is also reduced. Subsequently, the communication engineering template center generates the collection results corresponding to the task to be executed based on the business resource data and the target work order template. Through the synergy between the communication engineering tool system and the communication engineering template center, manual intervention steps (such as manually selecting templates and manually organizing results) are reduced, improving the continuity and efficiency of task processing. Specifically, the communication engineering template center is responsible for associating business data with the data fields of the corresponding first database entity in the database, ensuring that business data accurately corresponds to the corresponding database entity and avoiding data redundancy or format confusion. Simultaneously, based on the resource entity information, a corresponding second database entity is dynamically generated and associated with the entity configuration information corresponding to the target work order template. Compared to existing solutions using fixed templates, this technical solution supports the management of new resources without frequent modifications to the underlying database structure, flexibly adapting to different types of communication engineering objects. Therefore, this technical solution improves the task processing efficiency and data collection accuracy in the communication engineering data processing process. Attached Figure Description

[0011] Figure 1 This is a schematic diagram of a planning, surveying, and design process in related technologies; Figure 2 This is a schematic block diagram of a communication engineering data processing system provided in an embodiment of this application; Figure 3This is a flowchart illustrating a communication engineering data processing method provided in an embodiment of this application; Figure 4 This is a schematic diagram of a work order template provided in an embodiment of this application; Figure 5 This is a display interface diagram of a work order template provided in an embodiment of this application; Figure 6 This is a screenshot of a work order template page provided in an embodiment of this application; Figure 7 This is a parent-child relationship diagram of configurable resources provided in an embodiment of this application; Figure 8 This is a schematic diagram illustrating the specific implementation process of a template configuration method provided in an embodiment of this application; Figure 9 This is a schematic diagram illustrating the process of obtaining a work order template according to an embodiment of this application; Figure 10 This is a flowchart illustrating a communication engineering data processing method according to another embodiment of this application; Figure 11 This is a flowchart illustrating a communication engineering data processing method according to another embodiment of this application; Figure 12 This is a schematic diagram of the structure of a communication engineering data processing device provided in an embodiment of this application; Figure 13 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0012] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0013] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0014] In telecommunications network construction projects, the planning, surveying, and design phase, as the preliminary stage, significantly impacts the overall success or failure of the project due to the accuracy and completeness of the data collected. For example... Figure 1 As shown, the overall planning, surveying and design process mainly involves the scheduling system (such as the communication engineering scheduling center) synchronizing the construction planning project or task information from the group or provincial project management system, and then the relevant digital systems (such as intelligent surveying tools, intelligent mapping tools, intelligent computing tools, intelligent document tools, etc.) collecting or generating relevant business resource data according to different work procedures, and finally transmitting the results back to the provincial system for delivery.

[0015] In related technologies, predefined fixed templates are typically used to complete data collection. These templates exist statically in the relevant digital systems, containing fixed data fields and formats. Users need to enter data and generate reports according to the template requirements. To improve data quality, some digital systems have introduced simple verification rules, such as numerical range checks and field non-null constraints, for basic data verification. Furthermore, data quality verification and control for different work processes are mostly completed independently by each digital system. There is a lack of unified verification rule management and data sharing mechanisms between digital systems, and the review process for collected results is not standardized, leading to inconsistent review standards.

[0016] The aforementioned technologies have several shortcomings in practical applications. First, the use of fixed templates leads to a lack of flexibility in data collection, making it difficult to meet the personalized needs of different projects, regions, or clients. Template adjustments require the redevelopment of the digital system, increasing maintenance difficulty. Second, data verification mechanisms are mostly simple rules and tightly coupled with business implementation, making it difficult to support the effective verification of complex data relationships and logic. Adding new verification rules requires the redevelopment of the digital system, posing a risk of missed or false detections. For example, it is impossible to effectively verify and control complex relationships between data fields, thus failing to ensure data accuracy and consistency, easily leading to frequent low-level errors and low data quality. Third, verification rules between different digital systems cannot be uniformly managed, and data sharing relies on specially developed interfaces, resulting in complex and inefficient management. In addition, a large number of operations during data collection need to be completed manually, including data entry, verification, and review, which is inefficient and prone to errors. Due to the reliance on manual review, which has limited coverage and coarse granularity, it is difficult to detect and correct data problems in a timely manner. Furthermore, there is no unified process for reviewing and verifying the data collected from different digital systems. Instead, reviewers from each system conduct the reviews independently, resulting in inconsistent review standards. This increases the risk of data quality control issues in planning, surveying, and design data collection. Finally, the difficulty in reusing data between templates from different digital systems leads to duplicate data entry and redundancy, further reducing work efficiency and increasing the probability of errors.

[0017] It is evident that the various operational processes in planning, surveying, and design generally suffer from insufficient dynamism and flexibility in data quality control, and the mechanisms for collaboration and data reuse among digital systems urgently need improvement. With the continuous expansion of communication network scale and increasing complexity, existing communication engineering data processing solutions can no longer meet the actual needs of business development.

[0018] Therefore, this application provides a communication engineering data processing method. The following, in conjunction with the accompanying drawings, will describe in detail the communication engineering data processing method, apparatus, and electronic equipment provided in this application through specific embodiments and application scenarios.

[0019] Figure 2 This is a schematic block diagram of a communication engineering data processing system provided in an embodiment of this application, such as... Figure 2 As shown, the communication engineering data processing system may include a communication engineering dispatch center 10, a communication engineering tool system 20, a communication engineering template center 30, and a communication engineering data center 40.

[0020] In one implementation, the communication engineering template center 30 may include a template library 310, a result generation module 320, a result verification module 330, and a result review module 340.

[0021] In practical implementation, a basic template can be constructed through the communication engineering template center 30 based on the basic information of the communication engineering template. Then, in response to the personalized configuration operation performed by the second user based on the basic template, a corresponding candidate work order template is generated. The personalized configuration operation includes entity configuration operation and / or non-entity configuration operation, and the entity configuration operation includes structured attribute configuration operation and / or unstructured attribute configuration operation. Furthermore, in response to the review operation performed by the third user based on the candidate work order template, a work order template that has passed the review is obtained. The third user has different user permissions than the second user, and the work order template includes at least one of the following: business resource template, file type template, business review template, and job control template. Further, the work order template that has passed the review is stored in the template library 310 of the communication engineering template center 30.

[0022] During the process of configuring entities on the basic template to generate candidate work order templates, a data model can be loaded from the NIM (Network Information Model) of the Communication Engineering Data Center 40 to obtain information on resource entities. At the database level, an entity is the basic unit in the data model. Optionally, the second user can be the template configuration personnel, and the third user can be the template review personnel.

[0023] In practical implementation, after obtaining one or more of the following templates through the communication engineering template center 30: business resource template, document template, business review template, and operation control template, the communication engineering scheduling center 10 can filter out the target communication engineering projects that need to be bound to the work order template according to preset filtering conditions. The target communication engineering projects include multiple of the following: projects, sub-projects, work points, and work procedures. Therefore, for each target communication engineering project, the applicable work order template is determined from the communication engineering template center 30 based on the project attributes of that target communication engineering project. Then, the target communication engineering project is bound to the work order template, and the correspondence between the identification information of the target communication engineering project and the work order template is stored in the communication engineering template center 30. Further, the communication engineering scheduling center 10 generates tasks to be executed based on the identification information and work procedure plan of the target communication engineering project, and dispatches the tasks to be executed to the account of the corresponding first user in the corresponding communication engineering tool system 20.

[0024] Optionally, the communication engineering dispatch center can be used for project work point management. By loading work management templates from the template library of the communication engineering template center into the communication engineering dispatch center, and responding to the filling operations of the fourth user based on the work management templates, it is possible to generate tasks to be executed based on the identification information and work plan of the target communication engineering project, and dispatch the tasks to be executed to the corresponding first user's account in the corresponding communication engineering tool system. Here, the fourth user can be a task manager, and the first user can be a task executor.

[0025] In one implementation, the communication engineering tool system 20 may include a tool-type system and a communication engineering design document generation system. The tool-type system may include intelligent surveying equipment, intelligent pipeline surveying, intelligent mapping of pipelines, intelligent mapping equipment, and intelligent computing. The communication engineering design document generation system may include survey reports, disclosure reports, and design documents. In specific implementations, the communication engineering tool system, tool-type system, and communication engineering design document generation system include, but are not limited to, […]. Figure 2 The examples provided are not intended to limit the scope of this application.

[0026] In practical implementation, within the corresponding communication engineering tool system, a corresponding target work order template can be obtained from the communication engineering template center based on the target task information of the task to be executed. The communication engineering template center stores the correspondence between task information and pre-configured work order templates. Therefore, in response to the first user's filling operation based on the target work order template, the filled-in business resource data is submitted to the communication engineering template center. The business resource data includes business data and resource entity information, and resource entities include communication engineering objects that can be allocated, scheduled, or managed. Furthermore, through the result generation module 320 of the communication engineering template center, the collection results corresponding to the task to be executed are generated based on the business resource data and the target work order template. Specifically, the communication engineering template center is used to associate the business data with the data fields of the corresponding first database entity in its database; and to dynamically generate the corresponding second database entity based on the resource entity information, and associate the second database entity with the entity configuration information corresponding to the target work order template.

[0027] In practical implementation, the result verification module 330 of the communication engineering template center can verify the generated data according to the verification rules corresponding to the target work order template, and obtain the verification result. The verification rules can include several of the following: field non-empty constraints, field value constraints, field cascading constraints, field operation constraints, non-empty rules for unstructured data, and non-empty rules between unstructured data. If the verification result is successful, the data is reviewed; if the verification result is unsuccessful, the verification result is fed back to the communication engineering tool system to guide the first user in data correction.

[0028] In practical implementation, when reviewing the collected results, the target business review template corresponding to the target work order template can be obtained through the results review module 340 of the communication engineering template center. Based on the target business review template, the collected results are then reviewed to obtain the review results. The review process may include at least one of the following: automatic preliminary scoring, item-by-item scoring by reviewers, intelligent problem labeling, and reviewer problem labeling. Furthermore, based on the review results, if the review is deemed successful, the collected results are stored in the communication engineering template center for data reuse; and a review report is generated based on the review results. The review report is used for quality statistics to generate a data quality report. If the review is deemed unsuccessful, the review results are fed back to the communication engineering tool system to guide the first user in data correction.

[0029] By integrating the information collection, chart drawing, table processing, text organization, and project coordination processes of planning, surveying, and design, and by separating the work order template configuration capabilities of existing scheduling systems and related digital systems, a general data model field information template configuration, intelligent data verification, and intelligent review capabilities for collected results are formed. Specifically, by combining various data formats of the data model, it can provide general, customized, and rich template configuration capabilities, realizing data quality control templates for different data types such as enumeration, character, integer, decimal, location, image, audio / video, panoramic, and file types. Furthermore, it can provide different types of verification rule configurations and intelligent data verification capabilities based on different data types. The communication engineering data processing method provided in this application embodiment will be described in detail below.

[0030] Figure 3 This application illustrates a communication engineering data processing method according to an embodiment. This method can be executed by an electronic device, which may include a server and / or a terminal device, such as a vehicle-mounted terminal or a mobile phone terminal. In other words, the method can be executed by software or hardware installed in the electronic device, and the method includes the following steps: Step 302: Using the communication engineering tool system, obtain the corresponding target work order template from the communication engineering template center based on the target task information of the task to be executed.

[0031] The target task information may include the identification information of the communication engineering project and the user information of the first user. The communication engineering project may include multiple of the following: project, sub-project, work point, and work procedure. For example, a communication engineering project may include multiple work procedures of project X, multiple work procedures of sub-project x of project X, multiple work procedures of sub-project y of project X, work procedures of work point x1 of sub-project x of project X, work procedures of work point x2 of sub-project x of project X, and so on. Correspondingly, the identification information of the communication engineering project may include multiple of the following: project identification information, sub-project identification information, work point identification information, and work procedure type.

[0032] The communication engineering template center stores the correspondence between task information and pre-configured work order templates. In specific implementations, the communication engineering template center may store the correspondence between the identification information of communication engineering projects and pre-configured work order templates. Thus, in response to a first user's input in the communication engineering tool system, such as... Figure 4 The filling operation on the display interface can retrieve the corresponding target work order template from the communication engineering template center based on the identification information of the communication engineering project filled in.

[0033] Step 304: In response to the first user's filling operation based on the target work order template, the filled business resource data is submitted to the communication engineering template center.

[0034] The business resource data includes business data and information about resource entities. Resource entities include communication engineering objects that can be allocated, scheduled, or managed. In specific implementations, communication engineering objects can be equipment rooms, equipment, lines, outdoor logic stations, multiple cabinets in the equipment room, antennas, etc.

[0035] Step 306: Through the communication engineering template center, generate the collection results corresponding to the task to be executed based on the business resource data and the target work order template.

[0036] The communication engineering template center is used to associate business data with the data fields of the corresponding first database entity in its database. It also dynamically generates a corresponding second database entity based on the resource entity information and associates this second database entity with the entity configuration information corresponding to the target work order template. In practice, the data collection results generated by the communication engineering template center based on the business resource data and the target work order template can be database tables.

[0037] It is understandable that entities in a database are objectively existing and distinguishable things, such as records in a database table (e.g., server room, antenna). Each entity has a unique identifier (e.g., server room name, antenna model) and a set of attributes. In this embodiment, the first database entity is a resource entity (or business object) pre-configured in the database. By associating business data with the data fields of the business object, each piece of business data can be mapped one-to-one to the data fields, avoiding data confusion and redundancy. The second database entity is a new object dynamically created based on the resource entity information filled in by the first user. After the second database entity is generated, it can respond to the business data filled in by the first user for the second database entity by associating the business data with the data fields of the second database entity.

[0038] The entity configuration information corresponding to the target work order template is used to define the relationships between objects, or in other words, to define entity relationships in the database, such as parent-child relationships. By associating the second database entity with the entity configuration information, the entity relationships between dynamically created new objects and business objects can be clearly defined, thereby making the generated data collection results (such as database tables) more accurate. In practical implementation, foreign key constraints can be used to ensure the data integrity of these relationships, such as setting cascading operations to maintain the consistency of the relationships.

[0039] In practice, based on the information of multiple child resource entities added by the first user, the corresponding second database entities can be dynamically generated. According to the entity relationship predefined in the target work order template, the second database entities are associated with the entity configuration information corresponding to the target work order template to form a one-to-many entity relationship between the corresponding parent database entity (such as data center A) and each second database entity (such as multiple racks in data center A).

[0040] As an example, in the planning and surveying design, the rooftop includes the tower and the antenna feeder equipment it supports. Multiple platforms are installed on the tower, and multiple masts are mounted on these platforms for installing the antenna feeder equipment. The antenna feeder equipment may include AAU (Active Antenna Unit), RRU (Radio Remote Unit), antennas, etc. Figure 5 The display interface shows a template for the target work order. In this interface, the first user can fill in the form in the order of rooftop - tower - platform - mast - antenna feeder equipment, parent to child, or click the preset "navigation" button (not shown in the image). Figure 5 (As shown in the image), it allows for quick navigation between resource entities. Upon first clicking on a resource entity in this display interface, the corresponding database entity will be created, and the user will be redirected to the form entry page. Figure 6 A form submission page is shown. In response to the business data submitted by the first user on this page, the communication engineering template center can associate the business data with the data fields of the corresponding database entity. If a platform, pole, or antenna feeder device needs to add a second resource entity (such as a second-layer platform), it can do so by clicking the "Save" button in the upper right corner of the submission page. After saving the business data corresponding to the current resource entity, it can then click the resource entity to be added. Assuming the user clicks the button for example... Figure 5 In the "Outdoor Logical Station" section, you can select the "Add" option in the pop-up window to add a database entity corresponding to a second outdoor logical station. Understandably, the pop-up window may also include options for viewing the first outdoor logical station.

[0041] In the embodiments of this application, the communication engineering template center stores the correspondence between task information and pre-configured work order templates. Therefore, this technical solution enables centralized management and configuration of various work order templates through the communication engineering template center. Compared to existing solutions where each tool system independently manages and configures work order templates, this technical solution simplifies the maintenance and management of work order templates and improves overall operational efficiency. Furthermore, by separating the management and configuration of work order templates from each tool system, the content and structure of work order templates can be dynamically adjusted without affecting communication engineering data processing. This allows for better adaptation to different business lines, regional characteristics, and customer needs, enhancing the dynamism and flexibility of work order templates and providing reliable assurance for the accuracy and completeness of data collection. Based on this, in the communication engineering data processing flow, the communication engineering tool system retrieves the corresponding target work order template from the communication engineering template center based on the target task information of the task to be executed, achieving automatic matching of task information and work order templates, eliminating the need for users to manually filter templates. Thus, for the first user's filling operation based on the target work order template, the filled-in business resource data is submitted to the communication engineering template center. Business resource data encompasses business data and resource entity information, with resource entities including communication engineering objects that can be allocated, scheduled, or managed. By guiding the first user to fill in business resource data using a work order template, not only is the standardization of submitted data ensured, but the operational difficulty for non-professional users is also reduced. Subsequently, the communication engineering template center generates the collection results corresponding to the task to be executed based on the business resource data and the target work order template. Through the synergy between the communication engineering tool system and the communication engineering template center, manual intervention steps (such as manually selecting templates and manually organizing results) are reduced, improving the continuity and efficiency of task processing. Specifically, the communication engineering template center is responsible for associating business data with the data fields of the corresponding first database entity in the database, ensuring that business data accurately corresponds to the corresponding database entity and avoiding data redundancy or format confusion. Simultaneously, based on the resource entity information, a corresponding second database entity is dynamically generated and associated with the entity configuration information corresponding to the target work order template. Compared to existing solutions using fixed templates, this technical solution supports the management of new resources without frequent modifications to the underlying database structure, flexibly adapting to different types of communication engineering objects. Therefore, this technical solution improves the task processing efficiency and data collection accuracy in the communication engineering data processing process.

[0042] In one implementation, the work order template can be configured in the communication project template center through steps A1-A4. Optionally, in specific implementations, the backend technology can use Java, employing the Spring Boot framework to build a microservice architecture and provide high-performance RESTful API interfaces. Data storage is handled by Spring Data JPA and a MySQL database. The frontend technology can utilize mainstream frontend frameworks such as Vue.js or React.js, using component libraries such as Ant Design and Element UI to build a user-friendly interface.

[0043] Step A1: Construct a basic template using the Communication Engineering Template Center and the basic information of the Communication Engineering Template.

[0044] The basic information of the communication engineering template includes, but is not limited to: year, template type, full name of template, granularity (project, work point), province, major, project type, work point subcategory, construction type, work process, template format and scope of use.

[0045] Template types are categorized into business resource templates, operation control templates, business approval templates, and document templates. Document templates include design documents, information collection reports, handover reports, and survey record forms. If used for data asset entry (such as for communication engineering tools systems like Smart Survey, Smart Map, and Smart Computing), select the business resource template. If used for document processing (such as for Smart Document), select document templates such as design documents, information collection reports, and handover reports. If used for data quality control, select the business approval template. If used for operation control, select the operation control template.

[0046] The project type is derived from the Communication Engineering Dispatch Center and is used to distinguish the projects to which the template applies. If the project type of the work order template is "All Projects", it means that no project is distinguished and the work order template is a general template.

[0047] The difference between basic templates and personalized templates is that each province may have personalized configurations for the same major and minor professional categories. Therefore, personalized templates have an additional province information compared to basic templates, which is used to mark them as personalized templates from the province. When creating a personalized template, it is necessary to inherit from the basic template and configure other entity or data field information on the basic template.

[0048] Step A2: In response to the personalized configuration operation performed by the second user based on the basic template, a corresponding candidate work order template is generated.

[0049] Personalized configuration operations include entity configuration operations and / or non-entity configuration operations. Entity configuration operations include structured attribute configuration operations and / or unstructured attribute configuration operations. It can be understood that the template content that a second user can personalize includes two categories: entity and non-entity. In planning, surveying, and design, entities can include resource entities with fixed structures such as equipment rooms and antennas; non-entity can include information that does not correspond to resource entities, such as auxiliary information without fixed structures like sites and paragraphs.

[0050] In practice, personalized configuration operations include configuration operations for entities and / or non-entities. Entity configuration operations include configuration operations for structured attributes and / or unstructured attributes. Structured attribute configuration operations include configuring structured attribute fields and corresponding field validation rules. Unstructured attribute configuration operations include configuring unstructured attribute fields and corresponding field validation rules. The configured structured attribute fields are used for the first user to fill in the collected structured data, while the configured unstructured attribute fields are used for the communication engineering tool system to upload survey photos, audio, text files, etc. Field validation rules include, for example, field mandatory fields, format, resolution, and naming rules.

[0051] During personalized configuration, entities and non-entities need to be obtained by calling the Communication Engineering Data Center interface. The Communication Engineering Data Center stores data models and unstructured definitions; data models correspond to entities, and unstructured definitions correspond to non-entities. The Communication Engineering Template Center will intuitively display the obtained entities and non-entities to the second user according to parent-child relationships (such as a hierarchy like "site-equipment room-antenna"), helping the second user clearly understand the structural relationships between configurable resources (i.e., entities and / or non-entities), thereby more accurately selecting the resources to be configured (such as equipment rooms) and their corresponding attribute fields (such as equipment room name, area, etc.). This parent-child relationship is determined by the ParentID field in the JSON data returned by the Communication Engineering Data Center interface. ParentID is used to identify the parent resource of a certain resource, thus constructing the hierarchy. For example, the ParentID value recorded by a "device" is the ID (Identity Document, which refers to the code used to uniquely identify an entity) recorded by its "data center"; and the ParentID recorded by the "data center" points to the ID of its "site", ultimately forming a parent-child relationship such as "site-data center-device". Figure 7 This illustrates a parent-child relationship for configurable resources, where the number next to each resource represents the number of attribute fields that resource contains. For example, a "1" next to "data center" indicates that the data center has one configurable attribute field.

[0052] In practical implementation, after obtaining the entities (such as equipment rooms, antennas, and other business objects) defined in NIM and their corresponding attribute fields (such as equipment room name, area, etc.) through the communication engineering data center interface, the required attribute fields can be selected from these fields according to actual business needs. Entities can be given aliases that conform to business habits for easy identification and use. For example, "equipment room" can be changed to "base station dedicated equipment room". Single-field validation rules can be set. Specifically, for each structured attribute field (such as text or numeric types), separate validation rules can be configured (e.g., requiring the equipment room name to be non-empty, the area to be a positive number, and the phone number to be in the correct format, etc.) to ensure that the input data conforms to the specifications. This makes the template more closely aligned with actual business scenarios.

[0053] For example, for structured attribute fields, the following single-field rules can be formulated according to actual business needs: For manually entered fields, it is supported to configure the beginning and end, include, and exclude; for numeric fields, it is supported to configure the range equal to, not equal to, and number of decimal places; for enumerated fields, it is supported to flexibly select enumerated values, and support multiple selections and default value selection.

[0054] For unstructured attribute fields, the following single-field rules can be defined based on actual business needs: maximum and minimum number of fields, watermark content, resolution, format, naming rules, and whether the field is required can be configured. The watermark content can include: collection latitude and longitude, collection location, collection time, collection orientation, collector, collection unit, work site name, executor, executor's phone number, execution time, design unit, and other information.

[0055] Step A3: In response to the review operation performed by the third user based on the candidate work order template, obtain the work order template that has passed the review.

[0056] The third user has different user permissions than the second user. Work order templates include at least one of the following: business resource templates, document templates, business approval templates, and job control templates.

[0057] In practice, the work order template review and release process can include: after the candidate work order template is configured, template reviewers initiate the review process, involving review operations by quality management personnel, review team leaders, and review experts to ensure the quality and standardization of the template. This process can utilize Java open-source workflow engines such as Activiti or Flowable to implement the work order template review and release workflow. The front-end interface displays the template status and process progress, supporting review operations. The back-end defines the template review process, including nodes, participants, and review conditions. Template reviewers can view the template's review status and history on the front-end interface.

[0058] Step A4: Store the approved work order template in the Communication Engineering Template Center.

[0059] In this embodiment, a basic template is constructed based on the basic information of the communication engineering template through the communication engineering template center. This allows a second user to perform personalized configuration operations based on the basic template, forming candidate work order templates. This overcomes the problems of rigid field formats and difficulty in adapting to different project / region / customer needs inherent in fixed templates. It enables dynamic adjustment of the template structure for diverse business scenarios, meeting the customized needs of different business lines. For candidate work order templates, a third user with differentiated permissions is introduced for review, separating the roles of template configuration personnel and template review personnel. Multi-role verification avoids template configuration errors or non-compliance with business standards, ensuring the standardization and accuracy of template content and laying the foundation for the quality of subsequent data collection. Work order templates that pass review are stored in the communication engineering template center, forming a stable and reusable template resource. This replaces the decentralized mode of independent template management by various digital systems in related technologies, achieving unified template storage, maintenance, and retrieval, improving template management efficiency, and providing a centralized resource pool to support subsequent processes such as template binding to projects and automatic work order dispatch. The standardized template generated in this embodiment provides a unified structural basis for subsequent automatic data transfer, intelligent verification, and result review, reducing manual intervention (such as manual format adjustment and template screening) and improving the consistency and efficiency of the entire communication engineering data processing process.

[0060] Figure 8 The specific implementation process of the template configuration method provided in steps A1-A4 is illustrated. Before performing personalized configuration operations, users can select which type of template to configure based on the basic template, thus enabling different personalized configuration operations to be performed for different types of templates.

[0061] Personalized configuration of business resource templates can include selecting entities and attribute fields, configuring references, and configuring validation rules. Personalized configuration of job control / business approval templates can include selecting NIM-related entities and attribute fields. Personalized configuration of design documents can include selecting Word as a template. Personalized configuration of information collection reports / disclosure reports can include selecting Excel / Word as a template.

[0062] Through reference configuration, automatic data flow and sharing can be achieved. Specifically, it enables cross-process data flow and data flow when attribute field names or aliases are consistent. Cross-process data flow supports automatic data transfer between different work processes at the same work point. This is achieved through the correspondence of attribute fields, enabling automatic data transfer and reducing duplicate entry. Data flow when attribute field names or aliases are consistent means that data can flow automatically when attribute field names or aliases are the same, without additional configuration. For example, if attribute field aliases are the same between primary and secondary surveys, or between information collection and chart drawing, automatic data flow can be achieved.

[0063] Configuring validation rules can enhance data quality control capabilities. Validation rules can include field NOT NULL constraints, field value constraints, field cascading constraints, field operation constraints, NOT NULL rules for unstructured data, and NOT NULL rules between unstructured data. In practice, these validation rules can be defined by writing rule expressions in a rule engine (such as Drools).

[0064] A NOT NULL constraint specifies which fields must be non-empty if a given field is not empty. For example, if the data center name is not empty, then the data center's detailed address must also be non-empty.

[0065] Field value constraints are used to specify which fields cannot be empty or what values ​​to use for fields when a certain field's data value is a specific value. For example, if the computer room name is "X Building", then the computer room type cannot be empty.

[0066] Cascading constraints are used for validation based on the values ​​of other fields, such as dependency relationships or cross-field validation. For example, if the province is configured as Sichuan and the cities as Chengdu and Yibin, then if a user enters Sichuan as the province and Beijing as the city, the data entry will fail. Another example is if all equipment within a province's design area is from Company A. In the template design, the BBU (Baseband Unit) design status is "New," and the constraint BBU manufacturer enumeration value is "Company A." Alternatively, it can be one-to-many, where the BBU manufacturer enumeration value can be either "Company A" or "Company B." Entering other manufacturers will result in an error.

[0067] Field operation constraints refer to specific operation verifications based on business logic, such as numerical calculations and logical judgments. For example, in an outdoor logical station, a 2.6G site has only one carrier frequency per cell, so a verification rule is set to ensure that the number of cells equals the number of carrier frequencies.

[0068] The "Unstructured Data Not Empty" rule specifies that if a structured attribute field is not empty, the target unstructured attribute field must be uploaded as an attachment. For example, if the data center name is not empty, a panoramic photo of the original data center interior must be uploaded. Similarly, in the "Source Data Center - Switching Power Supply Entity" section, if the design status is not empty, a photo of the newly added switching power supply installation location must be uploaded.

[0069] Non-empty rules between unstructured data specify that if a structured attribute field is not empty, the target unstructured attribute field must be uploaded as an attachment. For example, in a rooftop photo, a new non-empty association can be added between the antenna installation location and the surrounding environment photo.

[0070] In practical implementation, machine learning models, such as decision trees, random forests, or deep learning models, can be introduced when configuring validation rules to automatically discover common error patterns in historical data. Based on the discovered common error patterns, new validation rules are automatically generated or existing validation rules are optimized. Specific implementation steps may include the following steps B1-B5: Step B1, Data Collection and Preprocessing.

[0071] Historical submission data and validation results can be collected and stored in a data warehouse. These data and results can be preprocessed to extract field features and error markers for model training.

[0072] Step B2, model training.

[0073] Extracted field features and error markers can be used to train machine learning models to identify common error patterns. By adjusting model hyperparameters, the model's accuracy and generalization ability can be improved.

[0074] Step B3: Validation rule generation and optimization.

[0075] New validation rules can be generated or existing validation rules can be optimized based on the model's output. The validation rule library can be automatically adjusted and optimized by running the model periodically.

[0076] Step B4, self-learning and feedback.

[0077] It can integrate a self-learning module to continuously adjust the validation rule base by monitoring user corrections and operational feedback in real time. Based on the characteristics of new data, it automatically adjusts the priority and scope of validation rules, improving its intelligence level.

[0078] Step B5: Integration and deployment of the self-learning module.

[0079] The self-learning module can be integrated into the existing verification process to enable dynamic adjustment of verification rules. Optionally, the self-learning module can be deployed in the cloud to ensure efficient real-time data processing and verification rule updates.

[0080] Through steps B1-B5 above, a unified automated and intelligent verification rule system can be realized in the communication engineering template center. Combined with the rule engine and machine learning model, it provides a flexible, automated and efficient data verification mechanism, which significantly improves the data quality control capability.

[0081] In one implementation, during the configuration of work order templates in the communication engineering template center through steps A1-A4 above, data security and standardization can be ensured through role-based access control, data encryption, and other means.

[0082] Role-based access control (RBAC) involves strictly controlling the permissions of each role during template configuration, review, and release to ensure system security and process standardization. The Spring Security framework can be used for authentication and authorization in this process. Permission configuration involves defining each role (e.g., template configurer, template reviewer, task executor) and configuring their respective permission scope. Access control involves the backend performing permission verification at the interface level, and the frontend displaying the corresponding functional modules based on the user's role.

[0083] Data encryption refers to the encrypted storage and transmission of sensitive data to ensure data security. Encryption algorithms such as AES (Advanced Encryption Standard), RSA (an asymmetric encryption algorithm), and Chinese national cryptographic standards SM1-SM4 (including symmetric encryption algorithms SM1 and SM4, asymmetric encryption algorithm SM2, and hash algorithm SM3) can be used to ensure the security of data transmission and storage. Encrypted data storage refers to the encryption of sensitive information stored in a database.

[0084] In one implementation, after configuring the work order template in the communication engineering template center through steps A1-A4 above, the work order template needs to be bound to specific projects, sub-projects, work points, or work procedures for application in actual business. Specifically, this can be achieved through steps C1-C4, binding the communication engineering project to the work order template, generating tasks to be executed based on the communication engineering project's work procedure plan, and dispatching them to the corresponding user's account in the corresponding communication engineering tool system.

[0085] Step C1: Through the communication engineering scheduling center, select the target communication engineering projects that need to be bound to the work order template from the communication engineering projects according to the preset screening conditions.

[0086] The target communication engineering project includes several of the following: project, sub-project, work point, and work procedure. A project is a top-level business unit for planning, surveying, and design, such as the 5G Phase VII project. A sub-project is a specific task module broken down from a project, such as a 5G base station construction sub-project in a certain province. A work point is a specific unit for performing tasks on-site, such as a base station survey point or a data center renovation point. A work procedure is the specific execution step under a work point, such as 13 procedures including information collection and chart drawing. After the work order template is published, it can be bound to the aforementioned communication engineering project through the project and work point in the communication engineering dispatch center, achieving standardization of work procedure-level data collection and verification.

[0087] Optionally, preset screening criteria may include production year, professional category, project type, construction type, and subcategory of work site. Professional categories may include transmission, wireless, power supply, data, switching, construction, building equipment, and planning. Project types may include key provincial projects, external customer service, and 5G Phase VI (4.9G). Construction types may include expansion, new site construction, co-located construction, renovation, and relocation.

[0088] In practice, the communication engineering dispatch center can respond to the information filled in by the task management personnel, such as the production year, professional category, project type, construction type, and work point sub-category, and select the target communication engineering projects that need to be bound to the work order template from the communication engineering projects.

[0089] Step C2: For each target communication project, determine the applicable work order template for the target communication project from the communication project template center based on the project attributes of the target communication project.

[0090] In practical implementation, an intelligent recommendation engine can be introduced. By analyzing the project attributes of the target communication engineering project (such as profession, region, project type, etc.), it can automatically recommend the most suitable work order template, improving the efficiency and accuracy of template binding. The intelligent recommendation engine can be implemented using machine learning algorithms, such as collaborative filtering, content-based recommendation, or hybrid recommendation algorithms. The deployment steps of the intelligent recommendation engine can include the following steps D1-D6: Step D1, Data Preparation.

[0091] It can collect usage data from historical communication engineering projects and work order templates to build training and testing sets. The collected data may include: communication engineering project ID, project attributes (including major, region, and project type), used work order template IDs, usage frequency, and usage feedback.

[0092] Step D2, Model Selection.

[0093] The appropriate machine learning algorithm can be selected to implement the intelligent recommendation engine based on actual business needs. For collaborative filtering recommendation algorithms, user-based or item-based collaborative filtering algorithms can be chosen. For content-based recommendation algorithms, machine learning models such as decision trees and random forests can be selected. Hybrid recommendation algorithms are a method that combines multiple recommendation techniques (such as collaborative filtering, content-based recommendation, etc.) to generate the final recommendation results.

[0094] Step D3, Model Training and Deployment.

[0095] Model training can be performed using Python machine learning libraries such as Scikit-Learn, TensorFlow, and PyTorch.

[0096] Step D4: Design of the Intelligent Recommendation API (Application Programming Interface).

[0097] An API interface can be provided for the intelligent recommendation engine to receive the project attributes of the target communication project and return a list of recommended work order templates.

[0098] Step D5, front-end interface design.

[0099] The template binding interface of the intelligent recommendation engine provides suggestions for recommended templates, and a fifth user can view the recommended work order templates and their reasons. The fifth user can be a task administrator (i.e., the fourth user) or a template binding personnel with different user permissions than the fourth user. In practice, an "Auto Recommend" button can be set on the template binding interface to provide suggestions for recommended templates. In response to the fifth user clicking this "Auto Recommend" button, the intelligent recommendation engine automatically generates a list of recommended work order templates based on the project attributes of the target communication engineering project entered by the fifth user. The fifth user can then directly select a work order template to bind.

[0100] Step D6: Model evaluation and optimization.

[0101] The performance of the intelligent recommendation engine can be evaluated periodically using metrics such as accuracy, precision, recall, and F1 score. The engine can be continuously updated and optimized based on user feedback and new data to improve accuracy and adaptability. The F1 score, a statistical metric used to evaluate the performance of binary classification models, ranges from 0 to 1 and is calculated as the harmonic mean of precision and recall.

[0102] Step C3: Bind the target communication project to the work order template, and store the correspondence between the identification information of the target communication project and the work order template in the communication project template center.

[0103] In practice, the target communication engineering project may use one or more work order templates. The communication engineering dispatch center supports binding multiple applicable work order templates to a target communication engineering project at one time to meet complex business needs.

[0104] In this embodiment, by storing the binding relationship between the work order template and the project, sub-project, work point or work procedure in the communication engineering template center, it can be ensured that in subsequent procedures, each communication engineering tool system can obtain the corresponding work order template according to the binding relationship.

[0105] Optionally, the communication engineering dispatch center can provide functions for querying and managing template binding status. A fifth user can view the binding status of work order templates and perform operations such as unbinding and rebinding. Furthermore, to ensure data security and process standardization, during the template binding process, the communication engineering dispatch center restricts users' binding operations on templates and communication engineering projects based on their roles and permissions.

[0106] Step C4: Based on the identification information and process plan of the target communication engineering project, generate tasks to be executed and dispatch the tasks to be executed to the corresponding first user's account in the corresponding communication engineering tool system.

[0107] In practical implementation, the planning, surveying, and design process can be divided into 13 operational steps: project management, project research, project plan, project standards, project review, project support, information collection, on-site coordination, support services, chart drawing, text processing, table processing, and document publication. The planning and design management or surveying work for each operational step is implemented using different communication engineering tool systems. Furthermore, the same operational step may involve different communication engineering tool systems to complete its tasks due to different specializations. As an example, the correspondence between operational steps and communication engineering tool systems is as follows: Project Management - Communication Engineering Dispatch Center, Information Collection - Intelligent Surveying Equipment (Wireless Specialty), Information Collection - Intelligent Surveying Pipeline (Transmission Specialty), Information Collection - Intelligent Text, Chart Drawing - Intelligent Mapping Equipment (Wireless), Chart Drawing - Intelligent Mapping Pipeline (Transmission), On-site Coordination - Intelligent Text, Text Processing - Intelligent Text, Table Processing - Intelligent Calculation, Document Publication - Intelligent Text, etc.

[0108] In practice, after completing the template binding, the project, sub-project, or task point needs to be assigned to the specific executor (i.e., the first user). Detailed implementation steps are as follows: Steps E1-E5. Step E1, Pre-dispatch verification. The communication engineering dispatch center automatically verifies the template binding status before dispatching work orders to ensure that all required work order templates are correctly bound, avoiding operational anomalies caused by missing work order templates and ensuring the standardized execution of operations.

[0109] Step E2: Generating Tasks to be Performed. Based on the work plan of the communication engineering project, corresponding tasks to be performed are generated. The task information for each task to be performed may include project ID, sub-project ID, work point ID, work process type, and executor.

[0110] Step E3, Task Assignment. Task managers assign tasks to suitable personnel based on factors such as workload and skills. Optionally, Java scheduling frameworks such as Quartz can be used to automate task assignment and notification.

[0111] Step E4, Task Notification. The communication engineering dispatch center can notify the executor of the tasks to be executed via message center, SMS, or email to ensure that the executor receives the task information in a timely manner. Optionally, task notifications can be sent via WebSocket, SMS gateway, or mail server.

[0112] Step E5: Order Dispatch Status Tracking. Task managers can view the execution status of tasks in real time within the communication engineering tool system corresponding to different work processes. Execution status can include dispatched, in progress, completed, etc.

[0113] In this embodiment, the communication engineering scheduling center filters target communication engineering projects that need to be bound to work order templates based on preset screening criteria. These projects include a multi-level structure encompassing projects, sub-projects, work points, and work procedures. For each target communication engineering project, a suitable work order template is determined from the communication engineering template center based on its project attributes. The binding management of communication engineering projects and work order templates is then completed, and the corresponding relationship is stored. This achieves dynamic matching and binding of project attributes and work order templates. Subsequently, the communication engineering scheduling center generates tasks to be executed and dispatches these tasks to the corresponding user accounts in the relevant communication engineering tool systems. This ensures the standardization and relevance of task formation, achieves accurate task allocation and efficient execution, and improves the scientific nature and efficiency of project management.

[0114] In one implementation, the target task information includes the identification information of the communication engineering project. For example... Figure 9 As shown, using the communication engineering tool system, based on the target task information of the task to be executed, the corresponding target work order template is obtained from the communication engineering template center (i.e., step 302), which can be executed as follows: steps 3022-3026: Step 3022: Using the communication engineering tool system, query the corresponding target work order template from the communication engineering template center based on the identification information of the communication engineering project.

[0115] Step 3024: Through the communication engineering template center, for the target work order template found in the query, obtain reusable data according to the preset data reuse rules and fill it into the target work order template.

[0116] The preset data reuse rules include: for work order templates corresponding to different work processes under the same project, sub-project or work point, data reuse is performed based on data field mapping and / or field alias consistency rules.

[0117] Step 3026: Send the filled target work order template to the communication engineering tool system.

[0118] In this embodiment, the communication engineering tool system queries the work order template from the communication engineering template center based on the identification information of the communication engineering project. Then, according to preset data reuse rules, it obtains and fills in reusable data, significantly reducing repetitive data entry and improving data processing efficiency and accuracy. The filled work order template is then sent to the communication engineering tool system, enabling users to efficiently complete data entry and task execution.

[0119] In practical implementation, when executing specific work procedures, the communication engineering tool system needs to load the corresponding work order template to guide data collection and entry. Technically, the backend can provide a unified API interface for querying and retrieving work order templates, and use JWT for authentication. JWT (JSON Web Token) is an open standard for authentication that ensures secure information transmission through digital signatures. Page components can be dynamically generated on the frontend based on the work order template configuration, enabling dynamic frontend rendering. Detailed implementation steps are as follows: Steps F1-F3: Step F1, API call. Using communication engineering tools (such as Smart Survey, Smart Map, Smart Calculation, Smart Documentation, etc.), based on information such as project ID, work point ID, and professional category, call the API interface provided by the communication engineering template center to obtain the bound work order template.

[0120] Before sending the bound work order template to the communication engineering tool system, the communication engineering template center will, for the work order template with data references, obtain reusable data and fill it according to the preset data reuse rules. For automatically generated data fields, it will automatically fill them to reduce manual input and improve efficiency.

[0121] For communication engineering tool systems that need to work in a network-free environment, offline caching of work order templates is supported to ensure the continuity of operations.

[0122] When loading the work order template, the corresponding language version can be provided according to the language settings of the first user to meet the needs of different regions.

[0123] Step F2, Template Parsing. The obtained work order template is parsed using a communication engineering tool system to obtain basic information, entity and field configurations, validation rules, etc.

[0124] Step F3: Interface Generation. Using the communication engineering tool system, a front-end interface is dynamically generated based on the work order template configuration, displaying the fields to be filled in and the attachments to be uploaded. It supports the display of different data types, such as text boxes, drop-down lists, checkboxes, and image upload controls.

[0125] In this embodiment, the communication engineering tool system of each work process calls the unified template configuration information API interface service provided by the communication engineering template center according to information such as project ID, work point ID, and professional category to obtain the business resource data that needs to be processed at the current work point, and renders the resource model according to the front-end style of each communication engineering tool system, providing a foundation for users to efficiently complete data entry and task execution.

[0126] In one implementation, the detailed steps for submitting the filled-in business resource data to the communication engineering template center (i.e., step 304) in response to the first user's filling-in operation based on the target work order template can be as follows: steps G1-G6: In terms of technical implementation, the front-end can perform real-time validation during the first user input, while the back-end performs secondary validation upon data submission. HTTPS protocol can be used to ensure the security of data transmission.

[0127] Step G1: Data Entry. The first user fills in the data and uploads attachments according to the work order template. The communication engineering tool system performs real-time validation of required fields and format requirements, and displays error messages.

[0128] Step G2, Data Reference and Automatic Generation. For fields configured with data references, the Communication Engineering Template Center retrieves data from existing data sources and automatically populates it. For example, it retrieves a list of standard equipment models referenced by work order templates under the same work process from the results library. The results library can store collected results that have been approved by the results review module.

[0129] Step G3, Local Validation. Before data submission, the communication engineering tool system performs local validation based on the single-field validation rules of the work order template to avoid submitting non-compliant data.

[0130] Step G4: Data Encryption and Compression. During the data submission process, the Communication Engineering Template Center encrypts and compresses sensitive data to ensure secure and efficient transmission.

[0131] Step G5, Data Submission. After the first user confirms that the data is correct, they click the "Submit" button. The communication engineering tool system then submits the data to the results generation module of the communication engineering template center via the API interface.

[0132] Step G6: Submit Feedback. The Communication Engineering Template Center will provide feedback on the submission result. The feedback will include information such as successful submission or reason for failure, to guide the first user to the next step.

[0133] In one implementation, after generating the data collection results corresponding to the task to be executed (i.e., step 306) through the communication engineering template center based on business resource data and the target work order template, if the target work order template is configured with field validation rules, the generated data collection results can be validated according to the configured validation rules, such as... Figure 10 As shown, the specific steps can be executed as follows: Steps 308-312: Step 308: Through the communication engineering template center, the collected results are verified according to the verification rules corresponding to the target work order template to obtain the verification result.

[0134] Validation rules can include several of the following: field NOT NULL constraints, field value constraints, field cascading constraints, field operation constraints, and unstructured data validation. Unstructured data validation can include unstructured data NOT NULL rules and unstructured data inter-data NOT NULL rules, etc.

[0135] Step 310: If the verification result is successful, the collected results will be reviewed.

[0136] Step 312: If the verification result is that the verification failed, the verification result is fed back to the communication engineering tool system to guide the first user to perform data correction processing.

[0137] In this embodiment, to ensure data quality, the communication engineering template center performs a comprehensive verification of the collected results according to the verification rules corresponding to the target work order template. If the verification passes, the collected results undergo further review; if the verification fails, the verification result is fed back to the communication engineering tool system to guide the first user to correct the data. The review process is based on the target business review template and supports multiple review methods, including automatic preliminary scoring, manual item-by-item scoring, and intelligent problem labeling. The review result determines the data storage and report generation. This mechanism achieves a comprehensive and in-depth data quality control, improving the accuracy and reliability of the data, and ensuring the consistency and traceability of data quality through a unified review process.

[0138] In practical implementation, large-scale models or machine learning algorithms can be used to enable the communication engineering template center to more intelligently validate submitted data, especially in complex scenarios, anomaly detection, and unstructured data processing, thereby improving overall efficiency and accuracy. In terms of technical implementation, the backend validation service can be written in Java and calls the rule engine to execute validation rules. Simultaneously, large-scale models are used to assist validation. Specifically, natural language processing models (such as the GPT series) can dynamically generate validation rules or perform intelligent auxiliary validation based on business needs and data types. Large-scale models can quickly understand business logic and provide recommended rule optimization solutions without requiring manual definition of complex rules. Furthermore, multithreading or asynchronous tasks can be used to achieve asynchronous processing, improving validation efficiency. Detailed implementation steps are as follows: Steps H1-H7: Step H1: Loading Validation Rules. The Communication Engineering Template Center loads relevant validation rules based on the work order template, including field NOT NULL constraints, field value constraints, field cascading constraints, field operation constraints, and unstructured data validation.

[0139] Step H2: Dynamic validation rule generation. Based on historical data and common business scenarios, basic validation rules are generated or recommended by the large model, such as common validation rules like field NOT NULL constraints and field value constraints, reducing manual intervention.

[0140] Step H3: Verification Execution. The Communication Engineering Template Center verifies each submitted data item by item according to the verification rules. For unstructured data, such as the format, size, and naming rules of attachments, corresponding verification is also performed. Basic natural language processing functions are introduced to quickly parse the text and verify the format.

[0141] Step H4: Record the verification results. Record the verification results in the database, including items that passed, items that failed, and the reasons for the errors, for reference in subsequent review and processing stages.

[0142] Step H5, Error Handling. For data that fails validation, the Communication Engineering Template Center will send the result back to the first user, indicating the fields that need to be modified and the reason. The first user can then correct the data according to the prompts and resubmit.

[0143] Optionally, the validation results can be provided through natural language descriptions generated by the large model, making it easier for the first user to understand and modify the data. The large model can directly generate user-friendly error messages without the need for complex error classification and attribution algorithms.

[0144] Step H6: Automatic Notification. For data that passes verification, the Communication Engineering Template Center will automatically notify the reviewers to proceed to the next review and processing stage.

[0145] Step H7, Visual Display. The Communication Engineering Template Center can provide a visual display of the verification results, including error distribution, common problems, etc., to help auditors identify data quality issues.

[0146] In one implementation, if the target work order template is configured with a business review template, the verified data collection results can be reviewed according to the configured business review template, such as... Figure 11 As shown, the specific steps can be executed as follows: Steps 3102-3108: The difference between verification processing and audit processing lies in the format verification of field information, while audit processing verifies whether the collected results meet the quality control requirements of project management. This is a higher level of auditing, where auditors score based on audit criteria or the communication engineering template center performs intelligent scoring. For example, audit processing might include: scoring whether sketches and photos match the actual site; scoring whether client management personnel have signed off on any instances where the rooftop couldn't be reached due to objective reasons (e.g., building roof); scoring whether the key on-site information in the joint survey confirmation form is complete, whether the construction plan is reasonable, and whether signatures are complete; and so on.

[0147] Step 3102: Obtain the target business approval template corresponding to the target work order template.

[0148] Step 3104: Based on the target business review template, review the collected results to obtain the review results.

[0149] The review process may include at least one of the following: automatic preliminary scoring, reviewer item-by-item scoring, intelligent issue labeling, and reviewer issue labeling.

[0150] Step 3106: Based on the review results, if the review is approved, the collected results will be stored in the Communication Engineering Template Center for data reuse; and a review report will be generated based on the review results.

[0151] The audit report is used for quality statistics to generate a data quality report.

[0152] Step 3108: If the review is determined to be unsuccessful, the review result will be fed back to the communication engineering tool system to guide the first user in data correction.

[0153] In terms of technical implementation, an intuitive review interface can be provided through the front-end review interface, supporting multiple viewing and annotation methods. Within this interface, the Communication Engineering Template Center can utilize large models (such as GPT-like language models) to implement an intelligent review assistant, providing intelligent review suggestions, including automatically identifying problem areas and generating correction suggestions to help reviewers improve review speed. Furthermore, it can achieve visual annotation based on AI (Artificial Intelligence) image processing technologies (such as OCR) to automatically identify and annotate problem areas in attachments, allowing reviewers to quickly view potential issues in the data. In the back-end review process, a workflow engine can be used to manage the review process and status. Regarding automatic scoring and suggestion generation, a machine learning model can be used through the Communication Engineering Template Center to automatically perform preliminary scoring based on historical review records and provide review opinions for reviewers' reference, reducing the workload of manual scoring. Detailed implementation steps are as follows: Steps I1-I8. Step I1: Task Assignment. The Communication Engineering Template Center assigns review tasks to the appropriate reviewers according to the review process. This supports both single-person and multi-person collaborative review.

[0154] Step I2: The review interface loads. Reviewers view the collected results in the Communication Engineering Template Center. The Communication Engineering Template Center loads the configuration information of the business review template, displaying the key points to be reviewed and the scoring criteria.

[0155] Optionally, the review interface can automatically extract key review content based on the data collected from the large model analysis, display high-risk data items, and load personalized scoring criteria based on the business review template.

[0156] Step I3, Intelligent Review Process: Step I31: The Communication Engineering Template Center automatically performs a preliminary score. Based on historical review data and scoring criteria, the Communication Engineering Template Center automatically performs a preliminary score on some fields or data items and generates suggested scores for reviewers' reference. Reviewers can quickly confirm or modify the scores.

[0157] Step I32: Reviewers score each item. Reviewers score each field or data item according to the review criteria. Features include scoring, comment submission, and attachment viewing.

[0158] Step I33, Intelligent Problem Annotation. The Communication Engineering Template Center automatically analyzes and reviews the data, annotates potential problems, and generates rectification suggestions.

[0159] Optionally, reviewers may further refine their comments or provide additional feedback based on this information.

[0160] Step I34: Auditor marking issues. For data items with problems, auditors can mark them, specifying the problem description and rectification suggestions.

[0161] Step 14: Submit Review Results. After the review is completed, the reviewers submit the review results. The Communications Engineering Template Center summarizes the scores and review comments to form a review report.

[0162] Step I5: Result Feedback. The Communication Engineering Template Center will provide the review results to the first user. For those requiring rectification, the first user will modify the data according to the review comments and resubmit it.

[0163] Step I6: Archive Audit Records. All audit records and results are archived in the Communication Engineering Template Center, supporting subsequent queries and statistical analysis.

[0164] Step I7, Quality Statistics and Analysis. The Communication Engineering Template Center compiles the audit results and generates a data quality report, including pass rate, problem classification, number of rectifications, etc., to provide a basis for management decisions.

[0165] Optionally, Apache Spark or Flink can be used for big data analysis to generate statistical reports. Then, libraries such as ECharts and D3.js can be used on the front end to display charts and reports, achieving data visualization.

[0166] Optionally, the statistical analysis may include: (1) Template usage statistics. Based on production year, unit, project type and profession, the proportion of sub-projects bound to work order templates and the execution rate of work points are statistically analyzed to understand the application of work order templates.

[0167] Regarding data collection, the backend regularly extracts usage data for work order templates from the database and results repository of the communication engineering template center. In terms of report generation, various statistical reports are generated, such as work order template binding ratios and execution rates.

[0168] (2) Verification Rate Monitoring. Statistics on the verification rate distribution of each work order template are compiled to monitor data quality. Support for displaying binding and execution status by province, and provides chart display and data download functions.

[0169] For real-time monitoring, submitted data is validated in real time, and the pass rate and reasons for failure are recorded. For displaying data by province, data is aggregated based on dimensions such as province and organization, and the front end provides filtering functionality.

[0170] (3) Batch review and data import. Supports batch download of review data and batch upload of review comments to improve review efficiency. Provides review record query function for easy tracking and management.

[0171] In implementation, Excel processing is used. Specifically, the front-end supports importing and exporting Excel files and uses libraries such as SheetJS to parse the data. The back-end provides a batch approval interface to support batch operations and improve approval efficiency.

[0172] (4) Anomaly Detection. Anomaly detection algorithms are used to monitor data input in real time, identify abnormal data, and provide an early warning mechanism. Optionally, machine learning algorithms such as Isolation Forest and One-Class SVM can be used for anomaly detection to identify potentially abnormal data. Anomaly analysis is performed on the real-time input data, and real-time data stream monitoring is conducted in conjunction with Flink.

[0173] In this embodiment, an early warning mechanism can be provided. By setting an early warning threshold, once abnormal data is detected, the communication engineering template center automatically triggers an early warning, notifying relevant personnel via email, SMS, system notifications, etc. Furthermore, a visual abnormal data monitoring dashboard can be provided to display the status and historical records of abnormal detections in real time.

[0174] In this embodiment, abnormal data can be processed. Specifically, an abnormal data processing interface is provided on the front end, allowing users to view abnormal data details, mark the cause of the abnormality, correct the data, and provide supplementary explanations. Automatic learning and optimization of abnormal data are supported; the detection rules are adaptively adjusted by the model to improve the accuracy of anomaly detection.

[0175] Step I8, Access Control and Security. Data and records generated during the audit process can only be accessed by personnel with the appropriate permissions, ensuring data security and confidentiality.

[0176] This application implements a multi-dimensional data acquisition and intelligent verification scheme based on dynamic template configuration. By establishing a communication engineering template center, it achieves unified dynamic template management and configuration, supports template inheritance and personalized customization, and dynamically adds entities and fields. Through automatic data flow and sharing, it reduces repetitive data entry and improves data reuse rate. By forming unified intelligent verification rules, including field non-empty constraints, field value constraints, field cascading constraints, field operation constraints, and unstructured data verification, it enhances data quality control capabilities. Simultaneously, it improves template execution and management, security and access control, and the quality monitoring and statistics of collected results, solving problems such as insufficient template flexibility, low data reuse rate, cumbersome manual operation, and weak data quality control capabilities in related technologies, thereby improving the data management efficiency and accuracy of communication engineering network construction.

[0177] Furthermore, the planning, surveying, and design work order template serves as a highly leveraged carrier of business knowledge in the early planning and design phase of communication engineering network construction projects, embodying expert experience. The widespread application of this template is crucial for the rapid transfer and universal application of expert experience. This application, based on accumulated experience in planning, surveying, and design within communication engineering network construction projects, and combined with digital and intelligent methods, explores and considers various approaches, which will have a positive impact on the communication engineering network construction industry. By using automated and intelligent methods to control operational standards and quality, relying on the NIM model, it positions, configures, maps, and manages rules, further controls the scope of data outputs, supports quality control from data entry to data output, and enables the implementation and management of review capabilities based on collected results. It is adaptable to multiple disciplines in communication engineering and can be further expanded to other surveying and design industries, possessing extremely broad application prospects. Specifically, this is reflected in: 1. Reduced Costs. Reduced Development and Maintenance Costs: A unified communication engineering template center centrally manages and dynamically configures various templates, avoiding the high costs associated with frequent template adjustments and redevelopment in existing systems. Dynamic configuration capabilities allow templates to quickly respond to changes in business needs, reducing system maintenance and development costs. Reduced Manual Operation and Review Costs: Automated data collection, flow, and intelligent verification reduce the workload of manual intervention and review, lowering labor costs. Simultaneously, automated processes reduce human error, further minimizing additional rework and correction costs due to data errors.

[0178] 2. Improved Operational Efficiency. Increased data collection and processing efficiency: Dynamic template configuration and automated data flow functions make data collection and processing more efficient, reducing redundant data entry and data silos, and improving data reuse and sharing. Data can flow and be reused quickly between different business processes, significantly improving overall operational efficiency. Accelerated Project Delivery: Intelligent verification rules and automated review processes speed up data verification and review, reducing the time and error probability of manual review, thereby shortening project delivery cycles and improving customer satisfaction and market competitiveness.

[0179] 3. Improve data quality and decision support capabilities. Enhanced data accuracy and consistency: Through rich validation rules and an intelligent rule self-learning optimization mechanism, data accuracy and consistency can be effectively improved, reducing the occurrence of low-quality data and ensuring the quality of project deliverables. Support for efficient business decision-making: Through unified data quality monitoring and statistical analysis functions, data problems and trends can be identified in a timely manner, providing management with real-time and accurate decision support, optimizing resource allocation and business processes, and enhancing the enterprise's decision-making efficiency and flexibility.

[0180] 4. Enhanced the flexibility and adaptability of the communication engineering tool system. Improved adaptability and scalability: Through a unified communication engineering template center and dynamic template configuration, the communication engineering tool system can quickly respond to changes and expansions in business needs without requiring extensive system reconstruction. The increased flexibility and scalability of the communication engineering tool system better copes with future business growth and diversified needs. Meets diverse customer needs. Dynamic template configuration supports personalized customization: It can be flexibly adjusted according to the specific needs of different customers and projects, meeting the personalized needs of various customers and enhancing customer stickiness and satisfaction.

[0181] 5. Enhance market competitiveness. Improved service quality and customer satisfaction: By responding quickly to customer needs, increasing project delivery speed, and ensuring data quality, service quality and customer satisfaction can be significantly improved, helping enterprises gain a favorable position in a highly competitive market. Establish a differentiated competitive advantage: Through innovative technologies and intelligent capabilities, enterprises can provide differentiated and efficient solutions in communication engineering network construction, establishing a unique competitive advantage and exploring new market opportunities and partnerships.

[0182] 6. Support digital transformation and strategic upgrades. Drive enterprise digital transformation: Through intelligent data management and automated processes, help enterprises achieve comprehensive digital transformation of business processes, optimize resource allocation and management models, and promote the upgrading of enterprises from traditional operating models to digital and intelligent ones. Enhance overall enterprise competitiveness: By adopting the technical solutions provided in the embodiments of this application, enterprises can significantly improve internal operational efficiency, data quality, and customer service capabilities, thereby enhancing overall market competitiveness and expanding market share and profitability.

[0183] It should be noted that the communication engineering data processing method provided in this application embodiment can be executed by a communication engineering data processing device, or a control module within that device for executing the communication engineering data processing method. This application embodiment uses the execution of the communication engineering data processing method by a communication engineering data processing device as an example to illustrate the communication engineering data processing device provided in this application embodiment.

[0184] Figure 12 This is a schematic diagram of the structure of a communication engineering data processing device provided in an embodiment of this application. Figure 12 As shown, the communication engineering data processing device includes: a first acquisition module 1210, a submission module 1220, and a first generation module 1230.

[0185] The first acquisition module 1210 is used to acquire the corresponding target work order template from the communication engineering template center based on the target task information of the task to be executed through the communication engineering tool system; the communication engineering template center stores the correspondence between task information and pre-configured work order templates; the submission module 1220 is used to submit the filled-in business resource data to the communication engineering template center in response to the first user's filling operation based on the target work order template; the business resource data includes business data and resource entity information, and the resource entity includes communication engineering objects that can be allocated, scheduled, or managed; the first generation module 1230 is used to generate the collection results corresponding to the task to be executed through the communication engineering template center based on the business resource data and the target work order template; wherein, the communication engineering template center is used to associate the business data with the data fields of the corresponding first database entity in the database of the communication engineering template center; and is used to dynamically generate the corresponding second database entity based on the information of the resource entity, and associate the second database entity with the entity configuration information corresponding to the target work order template.

[0186] In one implementation, the communication engineering data processing device further includes: a construction module, a second generation module, a second acquisition module, and a storage module.

[0187] The system comprises the following modules: a construction module for building a basic template based on the basic information of the communication engineering template center; a second generation module for generating corresponding candidate work order templates in response to personalized configuration operations performed by a second user based on the basic template; wherein personalized configuration operations include entity configuration operations and / or non-entity configuration operations, and entity configuration operations include structured attribute configuration operations and / or unstructured attribute configuration operations; a second acquisition module for acquiring approved work order templates in response to review operations performed by a third user based on the candidate work order templates; wherein the third user has different user permissions than the second user; and work order templates include at least one of the following: business resource templates, file templates, business review templates, and job control templates; and a storage module for storing approved work order templates in the communication engineering template center.

[0188] In one implementation, the communication engineering data processing device further includes: a filtering module, a determining module, a binding and storage module, and a generating and distributing module.

[0189] The filtering module, through the communication engineering scheduling center, filters out target communication engineering projects that need to be bound to work order templates based on preset filtering conditions. Target communication engineering projects include multiple of the following: projects, sub-projects, work points, and work procedures. The determination module, for each target communication engineering project, determines the applicable work order template from the communication engineering template center based on the project attributes of the target communication engineering project. The binding and storage module binds the target communication engineering project to the work order template and stores the correspondence between the identification information of the target communication engineering project and the work order template in the communication engineering template center. The generation and dispatch module generates tasks to be executed based on the identification information and work procedure plan of the target communication engineering project and dispatches the tasks to be executed to the account of the corresponding first user in the corresponding communication engineering tool system.

[0190] In one implementation, the target task information includes the identification information of the communication engineering project; The first acquisition module 1210 includes: a query unit, used to query the corresponding target work order template from the communication engineering template center based on the identification information of the communication engineering project through the communication engineering tool system; an acquisition and filling unit, used to acquire reusable data and fill it into the target work order template according to preset data reuse rules through the communication engineering template center; the preset data reuse rules include: for work order templates corresponding to different work procedures under the same project, sub-project or work point, data reuse is performed based on data field mapping and / or field alias consistency rules; and a sending unit, used to send the filled target work order template to the communication engineering tool system.

[0191] In one implementation, the communication engineering data processing device further includes: a verification module, an audit processing module, and a feedback module.

[0192] The verification module is used to verify the collected results through the communication engineering template center according to the verification rules corresponding to the target work order template, and obtain the verification results. The verification rules include multiple items of the following: field non-empty constraints, field value constraints, field cascading constraints, field operation constraints, and unstructured data verification. The review processing module is used to review the collected results if the verification result is successful. The feedback module is used to feed back the verification result to the communication engineering tool system if the verification result is unsuccessful, so as to guide the first user to perform data correction processing.

[0193] In one implementation, the review processing module includes: an acquisition unit for acquiring the target business review template corresponding to the target work order template; an review processing unit for reviewing the collected results based on the target business review template to obtain the review result; the review processing includes at least one of the following: automatic preliminary scoring, reviewer item-by-item scoring, intelligent problem labeling, and reviewer problem labeling; a storage and generation unit for storing the collected results in the communication engineering template center for data reuse if the review is deemed successful, and generating a review report based on the review result; the review report is used for quality statistics to generate a data quality report; and a feedback unit for feeding back the review result to the communication engineering tool system if the review is deemed unsuccessful, to guide the first user to perform data correction processing.

[0194] In the embodiments of this application, the communication engineering template center stores the correspondence between task information and pre-configured work order templates. Therefore, this technical solution enables centralized management and configuration of various work order templates through the communication engineering template center. Compared to existing solutions where each tool system independently manages and configures work order templates, this technical solution simplifies the maintenance and management of work order templates and improves overall operational efficiency. Furthermore, by separating the management and configuration of work order templates from each tool system, the content and structure of work order templates can be dynamically adjusted without affecting communication engineering data processing. This allows for better adaptation to different business lines, regional characteristics, and customer needs, enhancing the dynamism and flexibility of work order templates and providing reliable assurance for the accuracy and completeness of data collection. Based on this, in the communication engineering data processing flow, the communication engineering tool system retrieves the corresponding target work order template from the communication engineering template center based on the target task information of the task to be executed, achieving automatic matching of task information and work order templates, eliminating the need for users to manually filter templates. Thus, for the first user's filling operation based on the target work order template, the filled-in business resource data is submitted to the communication engineering template center. Business resource data encompasses business data and resource entity information, with resource entities including communication engineering objects that can be allocated, scheduled, or managed. By guiding the first user to fill in business resource data using a work order template, not only is the standardization of submitted data ensured, but the operational difficulty for non-professional users is also reduced. Subsequently, the communication engineering template center generates the collection results corresponding to the task to be executed based on the business resource data and the target work order template. Through the synergy between the communication engineering tool system and the communication engineering template center, manual intervention steps (such as manually selecting templates and manually organizing results) are reduced, improving the continuity and efficiency of task processing. Specifically, the communication engineering template center is responsible for associating business data with the data fields of the corresponding first database entity in the database, ensuring that business data accurately corresponds to the corresponding database entity and avoiding data redundancy or format confusion. Simultaneously, based on the resource entity information, a corresponding second database entity is dynamically generated and associated with the entity configuration information corresponding to the target work order template. Compared to existing solutions using fixed templates, this technical solution supports the management of new resources without frequent modifications to the underlying database structure, flexibly adapting to different types of communication engineering objects. Therefore, this technical solution improves the task processing efficiency and data collection accuracy in the communication engineering data processing process.

[0195] The communication engineering data processing device in this application embodiment can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. For example, mobile electronic devices can be mobile phones, tablets, laptops, PDAs, in-vehicle electronic devices, wearable devices, ultra-mobile personal computers (UMPCs), netbooks, or personal digital assistants (PDAs), etc., while non-mobile electronic devices can be servers, network attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service machines, etc. This application embodiment does not impose specific limitations.

[0196] The communication engineering data processing device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system used.

[0197] The communication engineering data processing device provided in this application embodiment can achieve... Figures 3 to 11 The various processes implemented in the method embodiments are not described in detail here to avoid repetition.

[0198] Based on the same technical concept, embodiments of this application also provide an electronic device for performing the above-described communication engineering data processing method. Figure 13 This is a schematic diagram of the structure of an electronic device to implement various embodiments of this application. The electronic device can vary significantly due to differences in configuration or performance, and may include a processor 1310, a communications interface 1320, a memory 1330, and a communication bus 1340. The processor 1310, communications interface 1320, and memory 1330 communicate with each other via the communication bus 1340. The processor 1310 can call a computer program stored in the memory 1330 and executable on the processor 1310 to perform the following steps: The communication engineering tool system retrieves the corresponding target work order template from the communication engineering template center based on the target task information of the task to be executed. The communication engineering template center stores the correspondence between task information and pre-configured work order templates. In response to the first user's filling operation based on the target work order template, the filled-in business resource data is submitted to the communication engineering template center. The business resource data includes business data and resource entity information, and the resource entity includes communication engineering objects that can be allocated, scheduled, or managed. Through the communication engineering template center, the collection results corresponding to the task to be executed are generated based on the business resource data and the target work order template. The communication engineering template center is used to associate the business data with the data fields of the corresponding first database entity in the database of the communication engineering template center; and to dynamically generate the corresponding second database entity based on the information of the resource entity, and associate the second database entity with the entity configuration information corresponding to the target work order template.

[0199] In the embodiments of this application, the communication engineering template center stores the correspondence between task information and pre-configured work order templates. Therefore, this technical solution enables centralized management and configuration of various work order templates through the communication engineering template center. Compared to existing solutions where each tool system independently manages and configures work order templates, this technical solution simplifies the maintenance and management of work order templates and improves overall operational efficiency. Furthermore, by separating the management and configuration of work order templates from each tool system, the content and structure of work order templates can be dynamically adjusted without affecting communication engineering data processing. This allows for better adaptation to different business lines, regional characteristics, and customer needs, enhancing the dynamism and flexibility of work order templates and providing reliable assurance for the accuracy and completeness of data collection. Based on this, in the communication engineering data processing flow, the communication engineering tool system retrieves the corresponding target work order template from the communication engineering template center based on the target task information of the task to be executed, achieving automatic matching of task information and work order templates, eliminating the need for users to manually filter templates. Thus, for the first user's filling operation based on the target work order template, the filled-in business resource data is submitted to the communication engineering template center. Business resource data encompasses business data and resource entity information, with resource entities including communication engineering objects that can be allocated, scheduled, or managed. By guiding the first user to fill in business resource data using a work order template, not only is the standardization of submitted data ensured, but the operational difficulty for non-professional users is also reduced. Subsequently, the communication engineering template center generates the collection results corresponding to the task to be executed based on the business resource data and the target work order template. Through the synergy between the communication engineering tool system and the communication engineering template center, manual intervention steps (such as manually selecting templates and manually organizing results) are reduced, improving the continuity and efficiency of task processing. Specifically, the communication engineering template center is responsible for associating business data with the data fields of the corresponding first database entity in the database, ensuring that business data accurately corresponds to the corresponding database entity and avoiding data redundancy or format confusion. Simultaneously, based on the resource entity information, a corresponding second database entity is dynamically generated and associated with the entity configuration information corresponding to the target work order template. Compared to existing solutions using fixed templates, this technical solution supports the management of new resources without frequent modifications to the underlying database structure, flexibly adapting to different types of communication engineering objects. Therefore, this technical solution improves the task processing efficiency and data collection accuracy in the communication engineering data processing process.

[0200] The specific execution steps can be found in the various steps of the above-described communication engineering data processing method embodiment, and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0201] It should be noted that the electronic devices in the embodiments of this application include: servers, terminals, or other devices besides terminals.

[0202] The above electronic device structure does not constitute a limitation on the electronic device. An electronic device may include more or fewer components than illustrated, or combine certain components, or arrange them differently. For example, an input unit may include a Graphics Processing Unit (GPU) and a microphone, and a display unit may use a liquid crystal display (LCD), organic light-emitting diode (OLED), or other similar display panels. User input units include at least one of a touch panel and other input devices. A touch panel is also called a touchscreen. Other input devices may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be elaborated further here.

[0203] Memory can be used to store software programs and various data. Memory can primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area can store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, memory can include volatile memory or non-volatile memory, or 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), 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 (Synchlink DRAM, SLDRAM), and direct memory bus RAM (DRRAM).

[0204] The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor, wherein the application processor mainly handles operations related to the operating system, user interface, and applications, while the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into the processor.

[0205] This application also provides a computer-readable storage medium for storing computer-executable instructions. When these computer-executable instructions are executed by a processor, they implement the various processes of the above-described communication engineering data processing method embodiments and achieve the same technical effects. To avoid repetition, these will not be described again here.

[0206] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0207] This application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described communication engineering data processing method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0208] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described communication engineering data processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0209] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0210] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0211] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0212] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for processing communication engineering data, characterized in that, include: Using the communication engineering tool system, the corresponding target work order template is obtained from the communication engineering template center based on the target task information of the task to be executed; The communication engineering template center stores the correspondence between task information and pre-configured work order templates; In response to the first user's filling operation based on the target work order template, the filled business resource data is submitted to the communication engineering template center; the business resource data includes business data and information about resource entities, and the resource entities include communication engineering objects that can be allocated, scheduled, or managed; Through the communication engineering template center, the collection results corresponding to the task to be executed are generated based on the business resource data and the target work order template; The communication engineering template center is used to associate the business data with the data fields of the corresponding first database entity in the database of the communication engineering template center; In addition, it is used to dynamically generate a corresponding second database entity based on the information of the resource entity, and associate the second database entity with the entity configuration information corresponding to the target work order template.

2. The method according to claim 1, characterized in that, The method further includes: A basic template is constructed based on the basic information of the communication engineering template through the communication engineering template center; In response to the personalized configuration operation performed by the second user based on the basic template, a corresponding candidate work order template is generated; wherein, the personalized configuration operation includes entity configuration operation and / or non-entity configuration operation, and the entity configuration operation includes structured attribute configuration operation and / or unstructured attribute configuration operation; In response to a review operation performed by a third user based on the candidate work order template, a work order template that has passed the review is obtained; wherein, the third user has different user permissions than the second user; the work order template includes at least one of the following: business resource template, file template, business review template, and job control template; The approved work order templates are stored in the Communication Engineering Template Center.

3. The method according to claim 2, characterized in that, The method further includes: Through the communication engineering scheduling center, target communication engineering projects that need to be bound to work order templates are selected from the communication engineering projects according to preset screening conditions; the target communication engineering projects include multiple of the following: projects, sub-projects, work points, and work procedures. For each target communication project, a work order template applicable to the target communication project is determined from the communication project template center based on the project attributes of the target communication project. The target communication project is bound to the work order template, and the correspondence between the identification information of the target communication project and the work order template is stored in the communication project template center; Based on the identification information and process plan of the target communication engineering project, tasks to be executed are generated and dispatched to the account of the corresponding first user in the corresponding communication engineering tool system.

4. The method according to claim 1, characterized in that, The target task information includes the identification information of the communication engineering project; The process of obtaining the corresponding target work order template from the communication engineering template center through the communication engineering tool system, based on the target task information of the task to be executed, includes: Using the communication engineering tool system, the corresponding target work order template can be queried from the communication engineering template center based on the identification information of the communication engineering project; Through the communication engineering template center, for the target work order template queried, reusable data is obtained and populated into the target work order template according to the preset data reuse rules; the preset data reuse rules include: for work order templates corresponding to different work procedures under the same project, sub-project or work point, data reuse is performed based on data field mapping and / or field alias consistency rules; The filled-in target work order template is sent to the communication engineering tool system.

5. The method according to claim 1, characterized in that, The method further includes: Through the communication engineering template center, the collected results are verified according to the verification rules corresponding to the target work order template to obtain the verification results; the verification rules include multiple items of the following: field non-empty constraints, field value constraints, field cascading constraints, field operation constraints, and unstructured data verification; If the verification result is successful, the collected results will be reviewed and processed. If the verification result is that the verification fails, the verification result is fed back to the communication engineering tool system to guide the first user to perform data correction processing.

6. The method according to claim 5, characterized in that, The review and processing of the collected results includes: Obtain the target business approval template corresponding to the target work order template; Based on the target business review template, the collected results are reviewed to obtain the review results; the review process includes at least one of the following: automatic preliminary scoring, reviewer item-by-item scoring, intelligent problem annotation, and reviewer problem annotation. Based on the audit results, if the audit is deemed successful, the collected data will be stored in the communication engineering template center for data reuse; and an audit report will be generated based on the audit results; the audit report will be used for quality statistics to generate a data quality report. If the review is deemed unsuccessful, the review result will be fed back to the communication engineering tool system to guide the first user in data correction.

7. A communication engineering data processing device, characterized in that, include: The first acquisition module is used to obtain the corresponding target work order template from the communication engineering template center based on the target task information of the task to be executed through the communication engineering tool system. The communication engineering template center stores the correspondence between task information and pre-configured work order templates; The submission module is used to respond to the first user's filling operation based on the target work order template and submit the filled business resource data to the communication engineering template center; the business resource data includes business data and information of resource entities, and the resource entities include communication engineering objects that can be allocated, scheduled or managed; The first generation module is used to generate the collection results corresponding to the task to be executed by the communication engineering template center, based on the business resource data and the target work order template. The communication engineering template center is used to associate the business data with the data fields of the corresponding first database entity in the database of the communication engineering template center; In addition, it is used to dynamically generate a corresponding second database entity based on the information of the resource entity, and associate the second database entity with the entity configuration information corresponding to the target work order template.

8. An electronic device, characterized in that, include: processor; as well as A memory configured to store computer-executable instructions configured to be executed by the processor to implement the communication engineering data processing method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store computer-executable instructions, which, when executed by a processor, implement the communication engineering data processing method as described in any one of claims 1-6.

10. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the communication engineering data processing method as described in any one of claims 1-6.

Images