File checking method and device for intelligent manufacturing

Abstract

The embodiment of the invention provides a file checking method and device for intelligent manufacturing, and the method comprises the steps: obtaining a target checking template in response to a file checking request for a target file, and enabling the target checking template to be constructed based on a target base class template corresponding to the target file, the target checking template comprises content positioning information, and the content positioning information is used for describing the position of the target checking content in the target file; extracting target check content from the target file by utilizing the content positioning information; and checking the target checking content to obtain a target checking result of the target file. Based on the target checking template, automatic extraction and checking of the target checking content are realized, and the checking accuracy and efficiency are improved; the risk of content omission is reduced through the content positioning information; and the target checking template is constructed based on the target base class template, so that the efficiency and the flexibility of constructing the checking template can be improved.

Description

TECHNICAL FIELD

[0001] Embodiments of the present specification relate to the technical field of computer technology, and particularly relate to a file checking method and device for intelligent manufacturing. BACKGROUND

[0002] As the "nerve network" of the spacecraft electronic system, the satellite cable network undertakes the key task of connecting various instruments and devices and transmitting power and signals, and its reliability directly determines the performance and life of the satellite in orbit. In the cable network checking process, any checking error may cause system function abnormalities or even mission failure. Therefore, accurate checking of the cable network is a necessary link to ensure the overall quality and reliability of the satellite.

[0003] However, the current cable network checking work is highly dependent on manual completion. Since the cable network design drawings lack unified standards, it is difficult to form a standardized data expression, resulting in that the checking can only rely on the point-by-point comparison of the drawings and the actual object by technical personnel, which is low in efficiency and prone to misjudgment and omission. Therefore, there is an urgent need for an efficient and accurate checking method. SUMMARY

[0004] Therefore, the embodiments of the present specification provide a file checking method for intelligent manufacturing. One or more embodiments of the present specification also relate to a cable file checking method for intelligent manufacturing, a file checking device for intelligent manufacturing, a computing device, a computer-readable storage medium, and a computer program product to solve the technical defects in the prior art.

[0005] According to a first aspect of the embodiments of the present specification, a file checking method for intelligent manufacturing is provided, including: in response to a file checking request for a target file, obtaining a target checking template, wherein the target checking template is constructed based on a target base class template corresponding to the target file, and the target checking template includes content positioning information, the content positioning information being used to describe the position of target checking content in the target file; using the content positioning information to extract the target checking content from the target file; checking the target checking content to obtain a target checking result of the target file.

[0006] According to a second aspect of the embodiments of the present specification, a cable file checking method for intelligent manufacturing is provided, including: in response to a file checking request for a target cable file, obtaining a target checking template, wherein the target checking template is constructed based on a target base class template corresponding to the target cable file, and the target checking template includes content positioning information, the content positioning information being used to describe the position of target checking content in the target cable file; using the content positioning information to extract the target checking content from the target cable file; checking the target checking content to obtain a target checking result of the target cable file.

[0007] According to a third aspect of the embodiments of the present specification, a file checking device for intelligent manufacturing is provided, comprising: a first acquisition module configured to acquire a target checking template in response to a file checking request for a target file, wherein the target checking template is constructed based on a target base class template corresponding to the target file, and the target checking template comprises content positioning information, the content positioning information being used to describe a position of target checking content in the target file; a first extraction module configured to extract the target checking content from the target file by using the content positioning information; and a first checking module configured to check the target checking content to obtain a target checking result of the target file.

[0008] According to a fourth aspect of the embodiments of the present specification, a computing device is provided, comprising: a memory and a processor; the memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which realize the steps of the above-mentioned file checking method for intelligent manufacturing or the cable file checking method for intelligent manufacturing when executed by the processor.

[0009] According to a fifth aspect of the embodiments of the present specification, a computer readable storage medium is provided, which stores computer programs / instructions, which realize the steps of the above-mentioned file checking method for intelligent manufacturing or the cable file checking method for intelligent manufacturing when executed by a processor.

[0010] According to a sixth aspect of the embodiments of the present specification, a computer program product is provided, comprising computer programs / instructions, which realize the steps of the above-mentioned file checking method for intelligent manufacturing or the cable file checking method for intelligent manufacturing when executed by a processor.

[0011] The file checking method for intelligent manufacturing provided by one embodiment of the present specification, in response to a file checking request for a target file, acquires a target checking template, wherein the target checking template is constructed based on a target base class template corresponding to the target file, and the target checking template comprises content positioning information, the content positioning information being used to describe a position of target checking content in the target file; the target checking content is extracted from the target file by using the content positioning information; and the target checking content is checked to obtain a target checking result of the target file. In this way, based on the target checking template, the target checking content in the target file can be automatically extracted and checked, improving the accuracy and efficiency of the checking; the target checking content can be completely and accurately extracted through the content positioning information, reducing the risk of content omission; and the target checking template can be constructed based on the target base class template, improving the efficiency and flexibility of constructing the checking template. BRIEF DESCRIPTION OF DRAWINGS

[0012] Figure 1is a schematic diagram of a file checking system for intelligent manufacturing according to an embodiment of the present specification;

[0013] Figure 2 is a flow chart of a file checking method for intelligent manufacturing according to an embodiment of the present specification;

[0014] Figure 3 is a flow chart of a cable file checking method for intelligent manufacturing according to an embodiment of the present specification;

[0015] Figure 4 is a flow chart of a process of a cable network design file checking method according to an embodiment of the present specification;

[0016] Figure 5 is a flow chart of a process of a cable network design file checking method according to an embodiment of the present specification;

[0017] Figure 6 is a structural schematic diagram of a file checking device for intelligent manufacturing according to an embodiment of the present specification;

[0018] Figure 7 is a structural schematic diagram of a cable file checking device for intelligent manufacturing according to an embodiment of the present specification;

[0019] Figure 8 is a structural block diagram of a computing device according to an embodiment of the present specification. DETAILED DESCRIPTION

[0020] In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present specification. However, the present specification can be practiced without the specific details, other than in the examples described herein, and it is understood that the scope of the present specification is not limited to the details below.

[0021] The terminology used in one or more embodiments of the present specification is for the purpose of describing particular embodiments only and is not intended to be limiting of one or more embodiments of the present specification. As used in one or more embodiments of the present specification and the accompanying claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in one or more embodiments of the present specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. The term "at least one of" followed by a list of one or more items is intended to mean one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the present specification refers to one or more items from the list of items, but not limited to a single item from the list of items. The term "and / or" as used in one or more embodiments of the present specification refers to one or more of the items, but not limited to a single item from the list of items. The term "at least one of" as used in one or more embodiments of the

[0022] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0023] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0024] First, the terms and concepts used in one or more embodiments of this specification will be explained.

[0025] Satellite cable network: A satellite cable network refers to a collection of cables, connectors, and distribution equipment specifically designed for transmitting satellite-related signals and power. It is a complete signal path system that ensures reliable transmission of data and power between the "signal source" and the "terminal."

[0026] Cable: A cable is an electrical component consisting of one or more insulated conductors (usually copper or aluminum) and a common protective layer (sheath) used to transmit electricity or signals.

[0027] Connectors: Satellite cable network connectors are interface components that enable separable electrical and mechanical connections between cables and equipment, or between cables.

[0028] Cable network design documents: Cable network design documents are a collective term for all technical documents generated during the development of products (such as automobiles, airplanes, satellites, and complex equipment) that describe the physical structure, electrical characteristics, connection relationships, installation methods, and process requirements of the cable network.

[0029] Cloud data servers: Virtualized data storage, management, and processing capabilities provided as a service by cloud service providers via the internet. Users can access and use these remote computing resources on demand without purchasing and maintaining physical hardware.

[0030] Intelligent manufacturing scenarios refer to specific examples of intelligent applications that achieve self-perception of state, self-optimization of decision-making, and self-driven execution in specific links, problems, or processes of industrial manufacturing activities, based on the deep integration of new-generation information technologies (such as the Internet of Things, big data, and artificial intelligence) and manufacturing technologies.

[0031] Satellite cable networks are the "nerves" of spacecraft electronic systems, responsible for connecting various instruments and equipment and transmitting power and signals. Their reliability directly affects the satellite's on-orbit performance. Traditional satellite development is mainly based on small-batch customization, and cable networks are usually verified manually, relying on technicians to compare design drawings with physical components point by point, which is inefficient and prone to errors. With the development of commercial spaceflight and satellite constellation networking, the demand for mass production of satellites has surged, posing a serious challenge to traditional verification methods. At the same time, verification data is difficult to collect and upload in real time, and to update it to production and design personnel.

[0032] (1) The current cable network verification still relies on manual verification, mainly because the cable network design drawings are not standardized and cannot be standardized. Therefore, the verification can only be done by human judgment, which is inefficient and prone to errors and omissions.

[0033] Current verification techniques rely on manual verification, which is inefficient and makes it difficult to achieve high-efficiency verification, especially in the mass production of complete satellite cable networks. This specification's embodiments implement a program-based, fast, and efficient automated verification process.

[0034] Current cable network design data is complex and difficult to process using fixed templates, which poses a significant obstacle to automatic and rapid verification. In the embodiments of this specification, big data methods are used to summarize various types of cable network design data to form a rapid verification database, while achieving efficient and standardized drawing output.

[0035] (2) Currently, the versions of cable network drawings are inconsistent, and information between production personnel, process personnel, management personnel, and designers relies on verbal communication, resulting in low information transmission efficiency and hindering efficient and lean production. Furthermore, inadequate information transmission leads to final production errors and reduces the quality of cable network production.

[0036] Currently, data is isolated, with production personnel, process engineers, managers, and designers not sharing data. Data transmission relies on verbal communication and document distribution, which is inefficient and prone to data omissions and delays. This specification's embodiments utilize cloud-based data collaboration to align the production granularity of production personnel, process engineers, managers, and designers, while simultaneously achieving efficient information transmission and breaking down information barriers between design and manufacturing.

[0037] This specification addresses the challenges of rapid verification and production in the mass production of satellite cable networks, proposing an efficient and automated solution that primarily solves the following core problems:

[0038] (1) Traditional verification is inefficient: Satellite cable networks have complex structures, and traditional manual verification relies on drawing comparison and point-by-point measurement, which is time-consuming and prone to errors. In mass production scenarios, the verification time for a single satellite cable network may reach several person-days, which seriously restricts production efficiency.

[0039] (2) Difficulty in ensuring consistency: In mass production, the consistency of the cable network process directly affects the reliability of the satellite. Manual verification is difficult to accurately identify hidden defects such as misaligned wiring and poor soldering of connectors, which can easily lead to batch quality risks.

[0040] (3) Data collaboration bottleneck: Data of production personnel, process personnel, management personnel and designers are isolated, and changes are difficult to be synchronized and verified in a timely manner, which easily leads to version mismatch problems.

[0041] The embodiments in this specification shorten the verification time to the minute level, increase the defect detection rate to over 99.5%, and support real-time data updates for design changes, providing standardized quality control methods for satellite mass production.

[0042] This specification provides a document verification method for intelligent manufacturing. It also relates to a cable document verification method for intelligent manufacturing, a document verification device for intelligent manufacturing, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.

[0043] It should be noted that the document verification method can be applied to intelligent manufacturing scenarios. These scenarios include intelligent production of satellite cable networks and intelligent manufacturing of vehicle bodies. Taking the intelligent production of satellite cable networks as an example, the document verification method for intelligent manufacturing proposed in the embodiments of this specification can be used to verify the cable network design documents, and intelligent production of the satellite cable network can be carried out based on the verified cable network design documents.

[0044] The document verification method for intelligent manufacturing proposed in the embodiments of this specification can be applied to, for example... Figure 1 The document verification system shown is for smart manufacturing, but it is not limited to this. See also Figure 1 , Figure 1 This specification illustrates an architecture diagram of a document verification system for intelligent manufacturing, provided in one embodiment of the specification. The document verification system for intelligent manufacturing may include a client 100 and a server 200.

[0045] Client 100 is used to send a file verification request for the target file to server 200;

[0046] Server 200 is used to respond to file verification requests for target files, obtain target verification templates, wherein the target verification templates are constructed based on the target base class templates corresponding to the target files, and include content location information, which describes the location of the target verification content in the target files; using the content location information, extract the target verification content from the target files; verify the target verification content to obtain the target verification result of the target files; and send the target verification result to client 100.

[0047] Client 100 is also used to receive the target verification results sent by server 200.

[0048] like Figure 1 As shown, the server 200 can connect to one or more clients 100 via a local area network (LAN), a wide area network (WAN), the Internet, or other types of data networks. Clients 100 may include, but are not limited to, smartphones, tablets, laptops, PDAs, personal computers, smart home devices, and in-vehicle devices. Clients 100 can also interact with users through a graphical user interface to implement the document verification method for intelligent manufacturing provided in the embodiments of this specification.

[0049] Server 200 may include servers providing various services, such as servers providing communication services to multiple clients, servers supporting backend training of models used on clients, and servers processing data sent by clients. It should be noted that server 200 can be implemented as a distributed server cluster composed of multiple servers, or as a single server. The server can also be a server in a distributed system, or a server integrated with blockchain. The server can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.

[0050] It is worth noting that the document verification method for intelligent manufacturing provided in the embodiments of this specification is generally executed by the server. However, in other embodiments of this specification, if the client's operating resources can meet the operating conditions, the client can also have similar functions to the server, thereby executing the document verification method for intelligent manufacturing provided in the embodiments of this specification. In other embodiments, the document verification method for intelligent manufacturing provided in the embodiments of this specification can also be executed jointly by the client and the server.

[0051] See Figure 2 , Figure 2 This specification illustrates a flowchart of a document verification method for smart manufacturing according to an embodiment, which specifically includes the following steps:

[0052] Step 202: In response to the file verification request for the target file, obtain the target verification template. The target verification template is constructed based on the target base class template corresponding to the target file. The target verification template includes content location information, which describes the location of the target verification content in the target file.

[0053] It should be noted that target documents refer to documents that need to be verified. Target documents can be documents from multiple application scenarios, including but not limited to engineering design and manufacturing, legal and government affairs, finance and accounting, scientific research and data analysis, digital content and intellectual property, and personal daily use. In specific scenarios, target documents can be of various types. For example, in the field of satellite cable networks, target documents can be cable network design documents, test details documents, bills of materials documents, and process specifications documents.

[0054] A document verification request (VRP) is an application submitted by one party (individual or team) to another, requesting a systematic review of designated documents to verify their correctness, completeness, consistency, and compliance, and ultimately to provide confirmation or propose modifications. A complete VRP typically includes clearly defined requesting and executing parties, clearly defined verification objects, a clear scope and basis for verification, clearly defined verification objectives and standards, required deliverables and outputs, and deadlines and priorities. For example, a VRP might request the verification of cable network design documents before cable network production.

[0055] A verification template is a templated document used to extract specific content from a file. It's a machine-readable set of rules that precisely describes the logic and methods for locating, identifying, and structurally outputting target data fields from unstructured or semi-structured source files. Verification templates typically include: locators, defining how to find the target content; field definitions, defining how to name and categorize the found data; data processing rules, defining how to clean and transform the original content after extraction; and output structure, defining the final organization of the extracted data.

[0056] In traditional computer data processing, standardized data formats are often required for processing. Currently, cable network connection design documents are complex to input, with numerous formats, making it difficult to create a unified template, which poses a challenge to computer data processing. Therefore, by using verification templates, computers can automatically extract target verification content from object files for verification. Multiple verification templates can form a template database, allowing the selection of a matching template for different target files. The database can be built by learning the formats of a large number of template files, recording file characteristics, and annotating important points.

[0057] A target verification template is a verification template that matches a target file. It is used to extract target verification content from the target file. For example, if the target file is a cable network design document, when a new cable network design document appears, it is necessary to match the optimal design document template. Verification of the cable network design document is achieved through template matching. For instance, cable information can be extracted from the cable network design document based on the target verification template.

[0058] A base class template is a partially completed, abstract template framework that encapsulates a set of common structures, behaviors, configurations, and constraints shared by related templates. It is typically not used directly but serves as a blueprint for creating concrete, usable templates. By extending the base class template, multiple concrete templates can be quickly and consistently derived, inheriting the commonalities of the base class while defining their own unique characteristics.

[0059] The target base class template corresponds to the target file, and the target verification template can be constructed based on the target base class template. Target files have different categories, and each category of target file can correspond to a target base class template. The classification criteria can be design stage and document purpose, cable network system or function, physical location and hierarchy, and file format and creation software. For the design stage and document purpose, they can be divided into system design and definition documents, detailed design documents, production and manufacturing documents, inspection and testing documents, and installation and integration documents; for cable network system or function, they can be divided into power cable network files, radio frequency cable network files, data bus cable network files, telemetry and remote control cable network files, and grounding cable network files; for physical location and hierarchy, they can be divided into inter-compartment cable network files, intra-compartment trunk cable network files, equipment branch cable network files, and component-level cable files; for file format and creation software, they can be divided into computer-aided design (CAD) model files, drawing files, data table files, and document files.

[0060] Content location information consists of one or more rules embedded in a template. It enables automatic data discovery and capture by identifying and describing the unique or characteristic location of target data within the source file. Content location information is used to describe the location of the target verification content within the target file.

[0061] Different types of files have different structures and require different content location information. For structured / markup language files (e.g., Hypertext Markup Language (HTML)), content location information can be tag hierarchy structures (e.g., XML Path Language (XPath)); for semi-structured text files (e.g., logs, reports), content location information can be regular expressions and delimiters; for binary documents (e.g., PDF, Word, Excel), content location information can be coordinates / regions / bounding boxes, keywords, styles / bookmarks. For example, if the target verification template is an Excel file, the content location information could be keywords.

[0062] The target verification content refers to the content that needs to be verified in the target document. For example, if the target document is a cable network design document, the target verification content could be the cables and connectors in the cable network. A connector is a component that enables a separable electrical connection between a cable and equipment, or between cables.

[0063] In practical applications, there are multiple ways to obtain the target verification template in response to a file verification request for the target file. The specific method chosen depends on the actual situation, and the embodiments in this specification do not impose any limitations on this. In one possible implementation of this specification, there is a one-to-one correspondence between the target file and the target verification template, and the corresponding target verification template can be directly determined based on the target file.

[0064] In another possible implementation of this specification, the document verification request carries the identifier of the target verification template. Based on the document verification request, the identifier of the target verification template can be obtained, and based on the identifier, the corresponding target verification template can be determined.

[0065] In another possible implementation of this specification, obtaining the target verification template includes: obtaining candidate verification templates; matching the target file and the candidate verification templates to obtain matching indicators, wherein the matching indicators are used to describe the degree of content matching between the target file and the candidate verification templates, and the matching indicators correspond one-to-one with the candidate verification templates; and determining the target verification template based on the matching indicators and the candidate verification templates.

[0066] It should be noted that a candidate verification template refers to the template(s) among a series of alternative, pre-designed verification templates that are likely applicable to the current specific task or data source. There can be one or more candidate verification templates.

[0067] Matching metrics refer to the degree of conformity between a candidate object (such as a template, solution, or result) and a target requirement or standard, measured using a predefined algorithm or rule set. In different contexts, it is also called similarity score, matching degree, or confidence score. Matching metrics describe the degree of content matching between the target file and the candidate verification template; there is a one-to-one correspondence between matching metrics and candidate verification templates. Content matching degree is a quantitative metric used to evaluate the level of agreement between a piece of content (such as a document, webpage, or answer) and a specific query request, topic, or another piece of content in terms of information relevance, topic coverage, and semantic consistency. Matching metrics can be a quantitative value (e.g., a number between 0 and 1) or a non-quantitative value (e.g., high matching degree, relatively high matching degree, moderate matching degree, low matching degree, poor matching degree).

[0068] In practical applications, there are multiple ways to obtain candidate verification templates, and the specific method should be selected according to the actual situation. This specification does not limit the specific methods used in this embodiment. In one possible implementation of this specification, the template database contains multiple verification templates, and the usage frequency of different verification templates is different. Based on the usage frequency of the verification templates, the top N verification templates with the highest (highest) usage frequency are selected from the template database as candidate verification templates.

[0069] In another possible implementation of this specification, the template database contains multiple verification templates, each with different template information. The target file also contains file information. After obtaining the target file, a verification template whose template information matches the file information is selected as a candidate verification template. The template information / file information can include the file creator, file format, and file size. For example, if the target file is a cable network design file, and different verification templates are created by different designers, a verification template created by the same designer is selected as a candidate verification template based on the designer's profile in the target file.

[0070] In another possible implementation of this specification, obtaining the candidate verification template includes: obtaining a reference file of the same category as the target file; and using the reference file to update the target base class template to obtain the candidate verification template.

[0071] It should be noted that the verification template is built upon the base class template. The base class template can be updated based on reference files to obtain the verification template. The reference files contain new information, structures, or patterns that the base class template cannot currently process. They serve as the data source for updating the base class template. Different target files correspond to different categories, and each category has one or more corresponding reference files.

[0072] In practical applications, after obtaining the target file, its category can be determined. Based on the target file's category, reference files of the same category can be identified. For example, if the target file is a power cable network file and its category is power supply, the reference files could be various power cable network files.

[0073] The target base class template can be updated using reference files to obtain candidate verification templates. This can be done by adding new fields; if new data items appear in the reference file, the target base class template needs to add corresponding extraction rules accordingly. Alternatively, the content location information can be corrected; if the structure or position of a field in the reference file changes, the content location information in the template needs to be updated according to the reference file. Another method is to expand the processing rules; if a new data format appears, corresponding processing logic needs to be added to the data cleaning rules of the template.

[0074] For example, the target base class template includes a table with multiple fields. If a reference file contains fields that are different from those in the table of the target base class template, then new fields need to be added to the target base class template based on the new fields in the reference file to obtain a candidate verification template.

[0075] By applying the scheme of the embodiments in this specification, a reference file of the same category as the target file is obtained; using the reference file, the target base class template is updated to obtain candidate verification templates. In this way, multiple verification templates can be obtained by expanding the base class template, which can improve the efficiency of template construction; template expansion based on the reference file can realize data-driven objective decision-making and optimization, and improve the generalization ability of the template.

[0076] In one optional embodiment of this specification, multiple reference files are divided into different categories based on their matching degree. For example, if the matching degree between two reference files is greater than a threshold, the two reference files are grouped into one category. For each category, there is at least one reference file. A base class template corresponding to the category is determined based on the reference file corresponding to the category, and the base class template is updated based on the reference file to obtain at least one verification template corresponding to the category. The base class template can be constructed based on common features in multiple reference files.

[0077] For example, the reference document is a cable network design document. Based on the company's cable network design documents, data integration is performed to obtain multiple categories of cable network design documents. For each category of cable network design documents, a design classification is performed. A minimum base class of design documents is established through common standards. At the same time, the base class is extended for different cable network design documents to obtain the design document template corresponding to the category.

[0078] In practical applications, there are multiple ways to match target files and candidate verification templates to obtain matching indicators. The specific method chosen depends on the actual situation, and this specification does not limit this approach. In one possible implementation, the positions of the data to be matched in the target file correspond one-to-one with the positions of the data to be matched in the candidate verification template. Based on the data to be matched in the target file, the data to be matched in the candidate verification template is determined. The data to be matched in the target file and the data to be matched in the candidate verification template are then matched to obtain the matching indicators.

[0079] In another possible implementation of this specification, the target file and candidate verification templates are matched to obtain matching indicators, including: parsing the target file to obtain the target file content; determining the template content to be matched of the candidate verification template based on the target area of ​​the target file content; and matching the target file content and the template content to be matched to obtain matching indicators.

[0080] It should be noted that the target file content refers to the content in the target file that needs to be matched. It can be some keywords in the target file (e.g., title, paragraph start word, paragraph end word) or some data fields in the target file (e.g., cable model, cable specification).

[0081] The target region refers to the location of the target file content within the target file. For example, the target region can be the line containing the target file content, the column containing the target file content, or a predefined area surrounding the target file content (e.g., including the area containing several adjacent lines of the line containing the target file content).

[0082] The content to be matched in the template refers to the content in the candidate verification template that needs to be matched. The content to be matched in the template corresponds one-to-one with the content in the target file.

[0083] In practical applications, the methods for parsing a target file to obtain its content can be either based on the target file's corresponding format, or by calling a parsing tool specific to the target file.

[0084] Based on the target area in the target file, determine the template content to be matched for the candidate verification template. This can be done by determining the corresponding target area in the candidate verification template based on the target area in the target file, and then reading the template content to be matched for the target area in the candidate verification template.

[0085] The matching method involves matching the content of the target file with the content of the template to obtain matching metrics. This can be done by comparing the two strings character-by-character to see if they are completely equal, or by splitting the text into words / tokens and checking if all tokens in one text appear exactly in the other. This matching method focuses on whether the two contents are completely identical.

[0086] Matching the content of the target file with the content of the template to obtain a matching metric can be achieved by calculating the minimum number of single-character editing operations (insertion, deletion, replacement) required to convert one string into another; the fewer the number of operations, the higher the similarity. Alternatively, the text can be converted into vectors (numerical arrays) in a high-dimensional space, and then the cosine of the angle between the two vectors can be calculated; the larger the cosine value, the higher the similarity. This matching method focuses on the degree of similarity between the two contents.

[0087] For example, the target file is a cable network design document. Parsing the target file, the content of the target file is "Cable Information Table". The target area is the three adjacent lines containing the words "Cable Information Table". In the candidate verification template, the corresponding three lines contain the words "Table about cable connection information". Therefore, the "Cable Information Table" and "Table about cable connection information" are matched, and the matching index is 95%, indicating that the matching degree between the two is 95%, and the target file matches the candidate verification template to a high degree.

[0088] The scheme described in this specification involves parsing the target file to obtain its content; determining the template content to be matched for candidate verification templates based on the target area of ​​the target file content; and matching the target file content with the template content to be matched to obtain matching indicators. This matching based on the target file content and the template content to be matched improves matching efficiency and speed compared to matching the entire target file and candidate verification templates. Furthermore, searching for the template content to be matched within a target area improves the accuracy of the search compared to searching at fixed locations.

[0089] In practical applications, there are multiple ways to determine the target verification template based on matching indicators and candidate verification templates. The specific method should be selected according to the actual situation, and the embodiments in this specification do not impose any limitations on this. In one possible implementation of this specification, if there is only one candidate verification template, then the candidate verification template is directly determined as the target verification template; if there are multiple candidate verification templates, then the multiple candidate verification templates are sorted according to the matching indicators, and the candidate verification template with the highest matching indicator is determined as the target verification template.

[0090] In another possible implementation of this specification, the target verification template is determined based on the matching indicators and the candidate verification templates, including: if the candidate verification template does not meet the template determination conditions based on the matching indicators, the candidate verification template is updated based on the target file to obtain the updated candidate verification template; the process of matching the target file and the candidate verification template to obtain the matching indicators is repeated until the candidate verification template meets the template determination conditions, thereby determining the target verification template.

[0091] It should be noted that the template determination condition refers to the conditions that the target verification template must meet. For example, for quantitative matching indicators, the template determination condition may be that the matching indicator is greater than a threshold; for non-quantitative matching indicators, the template determination condition may be that the matching indicator reaches "a high degree of matching or above".

[0092] In practical applications, after obtaining the matching indicators, it is determined whether the candidate verification template meets the template determination conditions based on the matching indicators. If it is determined that the candidate verification template meets the template determination conditions, the candidate verification template is determined as the target verification template. If there are multiple candidate verification templates that meet the template determination conditions, the target verification template can be any one of the candidate verification templates that meets the template determination conditions.

[0093] If the candidate verification template does not meet the template determination conditions based on the matching index, the candidate verification template needs to be updated to obtain the updated candidate verification template; return to the step of matching the target file and the candidate verification template to obtain the matching index, until the candidate verification template meets the template determination conditions, and then determine the updated candidate verification template as the target verification template.

[0094] Based on the target file, the candidate verification templates are updated. This can be done by updating all candidate verification templates based on the target file, or by updating only the candidate verification template with the highest matching index. When updating all candidate verification templates based on the target file, if any updated candidate verification template meets the template determination criteria, that template can be designated as the target verification template. If an updated candidate verification template does not meet the template determination criteria, it needs to be updated again.

[0095] Specifically, the candidate verification template can be updated based on the differences between the target file and the candidate verification template during the matching process to obtain the updated candidate verification template.

[0096] In another optional embodiment of this specification, the target base class template can be updated based on the target file to obtain the updated candidate verification template, and then the updated candidate verification template and the target file can be matched until the candidate verification template meets the template determination conditions.

[0097] For example, cable network design documents are matched with design document templates. If mismatches are found, new extended design document templates can be implemented based on the corresponding base templates, and then the cable network design documents are matched with the design document templates again for verification. During the verification of target documents, a self-learning method is used to add the design documents for this model to the database, further optimizing the design document database and conducting a new round of data iteration for the next efficient verification. Based on classification and recognition algorithms, design document templates are divided into multiple categories. Through further self-learning, efficient data matching is achieved, identifying non-standard cable network design drawings, and simultaneously managing the verified cable network design drawings for batch production.

[0098] It should be noted that, due to the creation of a design document database, optimal matching of information in cable network design documents can be achieved by matching template files within the database. When a task for this model is issued, the task is quickly decomposed by comparing it with existing design document templates in the database, enabling efficient verification and rapid decomposition of production and processes. Traditionally, verifying 200 cables requires approximately 3 person-days; through template matching and identification verification, this is reduced to 20 minutes, increasing efficiency by over 90% and significantly reducing labor costs.

[0099] Applying the scheme of the embodiments in this specification, when a candidate verification template does not meet the template determination conditions based on matching indicators, the candidate verification template is updated based on the target file to obtain an updated candidate verification template. This process continues until the updated candidate verification template meets the template determination conditions, thus determining the target verification template. In this way, when a candidate verification template does not meet the template determination conditions, it can be updated based on the target file. This self-learning approach enables the updating and expansion of candidate verification templates, improving their diversity and completeness, further optimizing them, obtaining an accurate target verification template, and increasing the probability of successful matching in the next attempt.

[0100] In another optional embodiment of this specification, the template database includes candidate verification templates and remaining templates. If a candidate verification template does not meet the template determination conditions based on matching indicators, the target file and the remaining templates are matched to obtain remaining matching indicators. If the remaining templates do not meet the template determination conditions based on remaining matching indicators, the candidate verification templates or remaining templates are updated based on the target file to obtain updated candidate verification templates. The process of matching the target file and candidate verification templates to obtain matching indicators is repeated until a candidate verification template meets the template determination conditions, thus determining the target verification template. If the remaining templates meet the template determination conditions based on remaining matching indicators, the remaining templates are determined as the target verification templates.

[0101] By applying the scheme of the embodiments in this specification, candidate verification templates are obtained; the target file and candidate verification templates are matched to obtain matching indicators; and the target verification template is determined based on the matching indicators and candidate verification templates. In this way, by matching the target file with candidate verification templates to determine the target verification template, it is possible to select a target verification template with a high degree of matching from multiple candidate verification templates, thereby improving the accuracy and selectability of the target verification template.

[0102] Step 204: Use content location information to extract the target verification content from the target file.

[0103] In practical applications, there are various ways to extract target verification content from a target file using content location information. The specific method chosen depends on the actual situation, and this specification does not limit this approach. In one possible implementation, the content location information is the region / boundary box / coordinates where the target verification content is located. After obtaining the target verification template, the location of the target verification content in the target file can be determined based on the content location information in the template, and the target verification content at the corresponding location can be extracted from the target file. For example, the target verification content is the content of the region corresponding to the coordinates of the content location information in the target file.

[0104] In another possible implementation of this specification, the content location information includes start position information and end position information; using the content location information, the target verification content is extracted from the target file, including: extracting the target verification content from the target file based on the start position information and end position information.

[0105] It should be noted that the start position information describes the starting position of the target verification content within the target file, while the end position information describes the ending position. The content location information in the target verification template corresponds one-to-one with the content location information in the target file. The start and end position information can be in any format; for example, they can be strings, specific fields, or keywords.

[0106] In practical applications, based on the start and end position information in the target verification template, the corresponding start and end position information is searched in the target file. Then, the target verification content is extracted from the target file based on this information. For example, the content between the start and end position information in the target file is determined as the target verification content.

[0107] Specifically, when determining the start and end position information of the target file, the search can be performed within the entire content area of ​​the target file, or within a small area (e.g., including the adjacent lines of information of the start position information) that corresponds to the start and end position information in the target verification template.

[0108] The search for corresponding start and end position information in the target file based on the start and end position information in the target verification template can be done in two ways: First, by searching the target file for information that is completely identical to the start and end position information in the target verification template. If the search is successful, the start and end position information of the target file is obtained. Second, by performing a fuzzy match between the content found in the target file and the start and end position information in the target verification template. If the fuzzy match is successful, the start and end position information of the target file is obtained.

[0109] One method for fuzzy matching is to calculate the minimum number of single-character editing operations (insertion, deletion, replacement) required to convert one string into another. If the number of operations is less than the corresponding threshold, the fuzzy match is considered successful. Alternatively, the text can be converted into a vector (numerical array) in a high-dimensional space, and then the cosine value of the angle between the two vectors can be calculated. If the cosine value is greater than the corresponding threshold, the fuzzy match is considered successful.

[0110] For example, the starting position information in the target verification template is "data start position" and the ending position information is "data end position". The corresponding starting position information found in the target file is "data start point" and the ending position information is "data end point". Therefore, the target verification content is the content between "data start point" and "data end point" in the target file.

[0111] The scheme implemented in this specification includes start position information and end position information in the target verification template. Based on the start position information and end position information, the target verification content is extracted from the target file, which can achieve precise positioning of the target verification content and thus extract accurate target verification content.

[0112] In one optional embodiment of this specification, after extracting the target verification content from the target file using content location information, the method further includes: obtaining file adjustment information for the target file; and adjusting the target file according to the file adjustment information and the target verification content to obtain the adjusted target file.

[0113] It should be noted that file adjustment information is used to adjust the target file. This can include standardizing field names, normalizing value formats, unifying units, and hierarchizing the structure of the target file. It can also include content modification and updates, structural reorganization and reconstruction, content enhancement and enrichment, customization of views and presentation, and unification of semantics and standards. File adjustment information can be used to adjust the target verification content in the target file, or it can be used to adjust the entire target file.

[0114] File adjustment information can be about methods / rules for making adjustments, or it can be a specific standard format.

[0115] Adjustments to the target file can be made at any point in time, during, before, or after the verification process.

[0116] In practical applications, the target file is adjusted based on the file adjustment information and the target verification content to obtain the adjusted target file. This can be done by systematically replacing specific words, phrases, or patterns in the target verification content according to the file adjustment information, by modularly splitting the target file or merging multiple related target files into a complete system-level file according to the file adjustment information, or by outputting the target verification content according to the format corresponding to the file adjustment information.

[0117] By applying the scheme of the embodiments in this specification, the target file is adjusted according to the file adjustment information and the target verification content to obtain the adjusted target file. In this way, the adjusted target file can be output according to the file adjustment information, realizing the data recombination and standardized output of target files with various non-standard and inconsistent formats, resulting in a target file with a standardized format, thereby improving the readability and operability of the target file.

[0118] Step 206: Verify the target verification content to obtain the target verification result of the target document.

[0119] It should be noted that the target verification result is a summary report or output generated after the target document verification process is completed. It usually includes overall conclusions, a detailed list of findings, quantitative statistics, and the verification environment.

[0120] In practical applications, there are various ways to verify the target content and obtain the target file's verification result. The specific method chosen depends on the actual situation, and this specification does not impose any limitations on these methods. In one possible implementation, after extracting the target content, the target content is directly verified according to the corresponding verification criteria to obtain the target file's verification result. The target content is stored in memory in a distributed or unstructured format.

[0121] For example, the target file is a cable network design file. For a certain batch of cable network design files, the verification goal can be to verify the entire cable network design file, and complete the output of cable specifications, models, wire gauges, bill of materials (BOM), and standardized production drawings (verified cable network design files). The specific verification process can be as follows: First, check whether the cable markings conform to the standardized markings; only cables that conform to the item + number are considered qualified cables. Second, check whether the conductor diameter conforms to the connector specifications; only when the connector matches the appropriate conductor diameter are the products considered qualified. Third, check whether the cable network design file is a standardized format file: if so, output the standardized format file; if not, output the cable network design file in a standardized format. Finally, combine the standardized production drawings to create the material BOM, and add information such as production auxiliary materials to the standardized production drawings. When the verification is completed, output the standardized production drawings and the material BOM.

[0122] In another possible implementation of this specification, the target verification content is verified to obtain the target verification result of the target file, including: constructing a content verification graph based on the target verification content, wherein the content verification graph uses key information in the target verification content as nodes and the relationships between key information as edges; and verifying the content verification graph to obtain the target verification result of the target file.

[0123] It's important to note that a content verification graph can be understood as a knowledge graph specifically built for understanding and organizing content (such as documents, web pages, videos, and product information). It aims to transform unstructured, disorganized content into a structured, interconnected, and machine-understandable "knowledge network." A content verification graph is a data model organized in a graph structure (composed of "nodes" and "edges") that clearly defines: core entities (nodes), the key concepts, topics, things, or people involved in the content; and relationships between entities (edges), how these entities are interconnected. For example, a content verification graph can be a directed graph.

[0124] Key information refers to fragments extracted from the target verification content that uniquely represent a core concept or entity and are of significant importance for realizing the application value of the graph. For example, key information could be connectors in a cable network design document, which are responsible for connecting cables to equipment.

[0125] An association is an explicit, semantic connection that precisely describes a specific type of relationship between any two "key pieces of information" (entities). For example, an association could be a cable in a cable network design document, with both ends of the cable connected to connectors.

[0126] In practical applications, after extracting the target verification content, it can be decomposed according to content decomposition criteria to obtain key information and the relationships between key information. A content verification graph is then constructed using key information within the target verification content as nodes and the relationships between key information as edges.

[0127] For example, after determining the target verification template, the target verification data of the cable network design document can be extracted according to the target verification template. The extracted data is then decomposed into the smallest unit and imported into the computer memory. A unified data format will be formed in the computer memory. At this time, cable identification, numbering, and location identification are performed, and finally, location information is corrected.

[0128] It should be noted that the batch production of the cable network involved a total of over 200 cables. Traditional cable network verification processes rely on manual verification, primarily checking cable specifications, models, wire gauges, and BOM (Bill of Materials) information. However, the satellite network mainly consists of complex cables with many-to-many node relationships and intricate topologies. Manual verification often struggles to clarify these topological relationships, leading to data verification errors. To address the difficulties of manual verification, a directed graph of node relationships is stored on a computer, forming a structured node information system that improves verification efficiency. Storing the node information from the cable network design documents on the computer requires identifying cable identifiers, corresponding connector start-point numbers, connector start-point models, connector end-point numbers, connector end-point models, connector start-point location information, connector end-point location information, and cable wire gauge information.

[0129] In practical applications, after constructing the content verification map, the content verification map can be verified to obtain the target verification result of the target file. After the verification is completed, the structured data (content verification map) can be output according to the standard template (standard format) to realize the verification of standardized cable network design documents.

[0130] For example, the target verification content includes cables and connectors. A directed graph is constructed with connectors as nodes and cables as relationships. The directed graph is then verified to determine the target verification result.

[0131] By applying the scheme of the embodiments in this specification, a content verification graph is constructed based on the target verification content. The content verification graph is then verified to obtain the target verification result of the target file. In this way, verifying the target verification content in the form of a graph can uncover contradictions and inconsistencies that cannot be detected by isolated verification, achieving global consistency and logical closed-loop verification. The graph forms well-organized node information, making information processing structured and improving verification efficiency.

[0132] The scheme implemented in this specification, in response to a file verification request for a target file, obtains a target verification template. This target verification template is constructed based on the target base class template corresponding to the target file. The target verification template includes content location information, which describes the location of the target verification content within the target file. Using the content location information, the target verification content is extracted from the target file. The target verification content is then verified to obtain the target verification result for the target file. Thus, based on the target verification template, the extraction and verification of target verification content in a target file can be automated, improving the accuracy and efficiency of the verification. The content location information enables complete and accurate extraction of the target verification content, reducing the risk of content omission. Constructing the target verification template based on the target base class template improves the efficiency and flexibility of template construction.

[0133] In one optional embodiment of this specification, after verifying the target verification content and obtaining the target verification result of the target file, the method further includes: if the target verification result indicates that the target file has passed the verification, uploading the target file to a shared database.

[0134] It should be noted that passing the verification means that the target document has been confirmed to meet all predefined, mandatory standards, specifications and requirements after a series of systematic checks.

[0135] A shared database is a data management strategy that treats data as a shared asset across an entire organization or specific business scope, rather than the private property of a particular department or application. It enables multiple users, applications, or business units to concurrently and consistently access and manipulate the same data by establishing a unified, centralized, and standardized database. For example, a shared database can be a cloud data server, a local data server, a distributed database cluster, or an edge computing node.

[0136] In practical applications, if the target file passes the verification, it can be uploaded to a shared database so that different users can obtain it and perform further processing.

[0137] For example, the target file is a cable network design document, and the shared database is a cloud data server. The cloud data server enables version tracking and data iteration of the cable network design document. Simultaneously, it connects the data of designers, process engineers, managers, and inspectors, reducing communication costs and improving efficiency. Currently, cable network design documents lack version management and control. By connecting the information of production personnel, designers, process engineers, managers, and inspectors through the cloud data server, and enabling efficient document distribution and updates through data iteration, efficient and lean production can be achieved.

[0138] Applying the solution described in the embodiments of this specification, when the target file passes the target verification result, the target file is uploaded to the shared database. This allows the target file to be shared among different personnel via the shared database, facilitating data exchange between them, reducing communication costs, and improving communication efficiency.

[0139] In one optional embodiment of this specification, if the target verification result indicates that the target file has failed the verification, a confirmation operation is performed on the target verification result to obtain a confirmation result. Based on the confirmation result, it is determined whether to modify the target file. If modification of the target file is required, the modification is performed, and the modified target file is verified. If the verification passes, the modified target file is uploaded to the shared database; if no modification of the target file is required, the unmodified target file is uploaded to the target database.

[0140] For example, during the verification process of cable network design documents, if the target verification result indicates that the cable network design documents have failed the verification, the target verification result needs to be sent to the designer of the cable network design documents for confirmation, and the designer determines whether the cable network design documents need to be modified.

[0141] In one optional embodiment of this specification, after uploading the target file to the shared database, the method further includes: in response to a modification request for the target file, extracting the target file from the shared database, modifying the target file to obtain a modified target file; and, if the modified target file passes verification, replacing the target file in the shared database with the modified target file.

[0142] It should be noted that a modification request is a formal, structured process used to propose, review, approve, and implement changes to a controlled document (such as design drawings, source code, contracts, standard operating procedures, etc.). Here, a modification request is used to modify the target document. A modification request can include the specific changes made to the target document; for example, a modification request could be for a cable network modification document, primarily containing information on changes to the cable network design documents.

[0143] The target modified file refers to the file obtained after modifying the target file according to the modification request.

[0144] In practical applications, when modifying a target file based on a modification request, the target file needs to be extracted from the shared database first, and then modified according to the modification request to obtain the target modified file. The target modified file undergoes the above verification process. If the target modified file passes the verification, it can be uploaded to the shared database and used to replace the target file in the shared database.

[0145] If the target modified file fails the verification, a confirmation operation is performed on the target modified file to obtain a confirmation result. Based on the confirmation result, it is determined whether the target modified file needs to be modified again. If the target modified file needs to be modified, the modification is performed, and the modified target modified file is verified. If the verification passes, the modified target modified file is uploaded to the shared database; if the target modified file does not need to be modified, it is uploaded to the shared database.

[0146] The solution described in this specification involves modifying target files in a shared database based on modification requests. Once the modified target file passes verification, it replaces the original target file in the shared database. This allows for updating the target files in the shared database, ensuring that the database stores the latest and most accurate versions while maintaining the accuracy of the target files within it.

[0147] In one optional embodiment of this specification, a corresponding local database copy is set up for the shared database, wherein the local database copy can synchronize update operations in the shared database. Permission management can also be set up for the shared database, with different users having different permissions. The shared database can also perform version management on uploaded target files.

[0148] It should be noted that in traditional production, cable network production drawings (design documents) are often disorganized. Designers and process engineers can only update design documents verbally, and process engineers and production personnel can only update the latest data verbally. Finally, there is no communication between inspection personnel and production personnel, leading to situations where production is carried out according to incorrect drawings, resulting in production errors and affecting the overall progress. However, objectively speaking, cable network production drawings are numerous and tasks are complex, making it difficult to synchronize various types of information among production personnel, process engineers, managers, and designers. Therefore, achieving efficient, fast, and accurate information synchronization, and synchronizing production and design information, is the only way to fundamentally solve the problem of production based on incorrect drawings.

[0149] To address the aforementioned issues, this specification's embodiments design a cloud-based data service method. This method controls the permissions of production personnel, process engineers, managers, and designers, enabling distributed task management for cloud-based data services and controlling iterative updates of tasks through cloud services. First, master node information is published, with production information published through master nodes such as design and process engineers, establishing the latest initial design information on the cloud server. Second, production personnel, acting as distributed nodes, receive the information and begin production. When designers make changes, the cloud server locks the design production files, updates the master node on the latest files, quickly notifies production personnel to update their information, and simultaneously synchronizes the modified information to inspection personnel. The system also records the design file version. Sometimes, designers may revoke modifications; in such cases, the design file can be rolled back to its original version, achieving efficient information processing. This method has been thoroughly verified across multiple projects. It establishes seamless information flow between production and design personnel, ensuring no production information synchronization errors occurred during the production of over 900 cables across four different models. Especially for experimental satellites, there are many modifications during the production process. Traditional information exchange is chaotic, and process personnel need to communicate with production personnel, management personnel, and design personnel at the same time. The amount of information exchanged is large and prone to errors. This method reduces the traditional communication time from one person communicating three times to one person communicating one piece of information, which greatly shortens the communication time, reduces the production error rate, and also effectively improves the production progress and quality.

[0150] Because there are many cable network drawings, a cloud database is established to unify the cable network data versions in the cloud database. At the same time, production personnel, process personnel, managers, designers, etc. can all create an identical copy of the cloud database locally. When the cloud database is updated, it will prompt you to update the copy database.

[0151] When erroneous drawings are found, process engineers will update the drawings and issue an update notice. When production and inspection personnel discover that the data has been updated, they will also update their local copy database. During the update, they will obtain the latest change information and can then proceed with production according to the latest cable network drawings.

[0152] Cloud database permissions include CRUD (Create, Read, Update, Delete) permissions. Because cloud databases have version rollback functionality, to standardize the job responsibilities of production personnel, process engineers, managers, and designers, and to facilitate management, production personnel are initially granted only view permissions, not CRUD permissions. Managers, primarily concerned with production information, also only have view permissions. Designers, being the ones who require the tasks, do not directly possess these permissions; instead, they communicate information to process engineers through process integration. The corresponding process engineers will then have the highest permissions, meaning they will have full CRUD permissions. Version logging ensures that the database can be rolled back, preventing irrecoverable damage to the cloud database due to accidental operations.

[0153] Figure 3 The flowchart illustrates a cable document verification method for smart manufacturing according to an embodiment of this specification, specifically including the following steps:

[0154] Step 302: In response to the file verification request for the target cable file, obtain the target verification template. The target verification template is constructed based on the target base class template corresponding to the target cable file. The target verification template includes content location information, which describes the location of the target verification content in the target cable file.

[0155] It should be noted that the target cable file refers to the target file containing cable information. During the design and production process of satellite cable networks, the target cable file needs to be verified. For example, the target cable file may be the cable network design document.

[0156] Step 304: Use content location information to extract the target verification content from the target cable file.

[0157] Step 306: Verify the target verification content to obtain the target verification result of the target cable file.

[0158] The scheme implemented in this specification, in response to a file verification request for a target cable file, obtains a target verification template. This target verification template is constructed based on a target base class template corresponding to the target cable file. The target verification template includes content location information, which describes the location of the target verification content within the target cable file. Using the content location information, the target verification content is extracted from the target cable file. The target verification content is then verified to obtain the target verification result for the target cable file. Thus, based on the target verification template, the extraction and verification of target verification content in the target cable file can be automated, improving the accuracy and efficiency of the verification. The content location information enables complete and accurate extraction of the target verification content, reducing the risk of content omission. Constructing the target verification template based on the target base class template improves the efficiency and flexibility of template construction.

[0159] The above is an illustrative scheme of a cable document verification method for intelligent manufacturing according to this embodiment. It should be noted that the technical solution of this cable document verification method for intelligent manufacturing belongs to the same concept as the technical solution of the document verification method for intelligent manufacturing described above. Details not described in detail in the technical solution of the cable document verification method for intelligent manufacturing can be found in the description of the technical solution of the document verification method for intelligent manufacturing described above.

[0160] The following is in conjunction with the appendix Figure 4 Taking the application of the document verification method for intelligent manufacturing provided in this manual to satellite cable networks as an example, this paper further explains the document verification method for intelligent manufacturing. Figure 4 This specification illustrates a flowchart of a cable network design document verification method according to an embodiment, which specifically includes the following steps:

[0161] Step 402: Obtain the base class template corresponding to the category and the cable network reference file corresponding to the category;

[0162] The cable network reference document corresponds to the reference document in the above embodiments.

[0163] Step 404: Update the base class template using the cable network reference file to obtain the cable network verification template corresponding to the category;

[0164] Among them, the cable network verification template corresponds to the verification template in the above embodiment, and multiple categories of cable network verification templates can constitute a template database.

[0165] Step 406: Based on the cable network design documents, determine the candidate verification templates from the cable network verification templates;

[0166] The cable network design document corresponds to the target document in the above embodiments.

[0167] Step 408: Match the cable network design documents and candidate verification templates to determine the target verification template;

[0168] Step 410: Use the content location information of the target verification template to extract the target verification content from the cable network design documents;

[0169] Step 412: Construct a content verification map based on the target verification content, verify the content verification map, obtain the verification results of the cable network design document, and generate the adjusted cable network design document according to the target format and the content verification map;

[0170] The target format corresponds to the file adjustment information in the above embodiments.

[0171] Step 414: If the verification result indicates that the cable network design document has passed the verification, upload the adjusted cable network design document to the shared database;

[0172] Step 416: Modify the latest cable network design documents in the shared database according to the cable network renovation information to obtain the target modified document; if the target modified document passes the verification, upload the target modified document to the shared database.

[0173] The cable network modification information corresponds to the modification request in the above embodiments.

[0174] In this embodiment, a template database is constructed using a large number of cable network design documents. Template matching and verification are then performed through this database, standardizing a large number of non-standard cable network design documents for output and achieving automated verification. Compared to traditional methods where verification data largely relies on manual processing and cannot effectively organize large amounts of non-standard design data, this embodiment constructs a template database for categorized management, resulting in efficiency improvements of tens of times compared to traditional manual verification.

[0175] See Figure 5 , Figure 5 This specification illustrates a flowchart of a rapid verification production process for cable networks according to one embodiment. Figure 5 As shown, at the beginning, the designers issue cable network design documents, and the process engineers use the data rapid verification engine to verify the cable network design documents. During the verification process, the existing template database is used for batch verification, which reduces the traditional manual verification from several days to a few minutes. At the same time, the cable network data with different specifications can be standardized and output, and the verified data is uploaded to the cloud data server.

[0176] Secondly, the designers issue the cable network modification documents, the process engineers confirm them, and at the same time, they obtain the latest cable network design information from the cloud data server, compare and confirm it, quickly verify it, and upload the latest cable network design information to the cloud data server.

[0177] Production personnel access cable network design information (corresponding to standardized production documents) from the cloud data server in real time, updating it when modifications occur to ensure production uses the latest standardized production documents. Simultaneously, production data (corresponding to the physical cable network production) is also uploaded to the cloud data server for data traceability.

[0178] Inspectors obtain cable network design information from the cloud data server in real time and inspect the actual cable network production using the latest cable network design information, ensuring information exchange between production and inspection personnel and achieving efficient inspection; at the same time, inspectors upload inspection data to the cloud data server to ensure that it can be traced later through the cloud data server.

[0179] Managers can access production and design data in real time by connecting to a cloud data server, understand the current progress of cable network design and production, and provide guidance for cable network production through the cloud data server.

[0180] The cloud-based data server performs version management, recording every addition, deletion, modification, and query, while also keeping version records. This allows for tracing and reviewing previous versions and performing version comparison management.

[0181] The data fast verification engine uses intelligent pattern recognition to classify and manage data, forming a template database. It then performs database matching verification using verification data (corresponding to cable network design documents) to achieve data template verification. At the same time, it compares the verified data with the cloud data server to enable CRUD operations and version management on the cloud data server.

[0182] Corresponding to the above method embodiments, this specification also provides embodiments of a document verification device for intelligent manufacturing. Figure 6 A schematic diagram of a document verification device for intelligent manufacturing, provided in one embodiment of this specification, is shown. Figure 6 As shown, the device includes:

[0183] The first acquisition module 610 is configured to acquire a target verification template in response to a file verification request for a target file. The target verification template is constructed based on the target base class template corresponding to the target file. The target verification template includes content location information, which describes the position of the target verification content in the target file.

[0184] The first extraction module 620 is configured to extract the target verification content from the target file using content location information;

[0185] The first verification module 630 is configured to verify the target verification content and obtain the target verification result of the target file.

[0186] Optionally, the first acquisition module 610 is further configured to acquire candidate verification templates; match the target file and the candidate verification templates to obtain matching indicators, wherein the matching indicators are used to describe the degree of content matching between the target file and the candidate verification templates, and the matching indicators correspond one-to-one with the candidate verification templates; and determine the target verification template based on the matching indicators and the candidate verification templates.

[0187] Optionally, the first acquisition module 610 is further configured to parse the target file to obtain the content of the target file; determine the content of the candidate verification template to be matched based on the target area of ​​the target file content; and match the content of the target file and the content of the template to be matched to obtain the matching index.

[0188] Optionally, the first acquisition module 610 is further configured to, if the candidate verification template does not meet the template determination conditions based on the matching index, update the candidate verification template based on the target file to obtain the updated candidate verification template; return to execute the step of matching the target file and the candidate verification template to obtain the matching index, until the candidate verification template meets the template determination conditions and the target verification template is determined.

[0189] Optionally, the first acquisition module 610 is also configured to acquire a reference file of the same type as the target file; and to update the target base class template using the reference file to obtain a candidate verification template.

[0190] Optionally, the content location information includes start position information and end position information; the first extraction module 620 is also configured to extract the target verification content from the target file based on the start position information and end position information.

[0191] Optionally, the first verification module 630 is further configured to construct a content verification graph based on the target verification content, wherein the content verification graph uses key information in the target verification content as nodes and the relationships between key information as edges; and to verify the content verification graph to obtain the target verification result of the target file.

[0192] Optionally, the first extraction module 620 is further configured to obtain file adjustment information for the target file; and to adjust the target file according to the file adjustment information and the target verification content to obtain the adjusted target file.

[0193] Optionally, the first verification module 630 is also configured to upload the target file to the shared database if the target verification result indicates that the target file has passed the verification.

[0194] Optionally, the first verification module 630 is further configured to, in response to a modification request for the target file, extract the target file from the shared database, modify the target file to obtain a modified target file; and, if the modified target file passes verification, replace the target file in the shared database with the modified target file.

[0195] The scheme implemented in this specification, in response to a file verification request for a target file, obtains a target verification template. This target verification template is constructed based on the target base class template corresponding to the target file. The target verification template includes content location information, which describes the location of the target verification content within the target file. Using the content location information, the target verification content is extracted from the target file. The target verification content is then verified to obtain the target verification result for the target file. Thus, based on the target verification template, the extraction and verification of target verification content in a target file can be automated, improving the accuracy and efficiency of the verification. The content location information enables complete and accurate extraction of the target verification content, reducing the risk of content omission. Constructing the target verification template based on the target base class template improves the efficiency and flexibility of template construction.

[0196] The above is a schematic scheme of a document verification device for intelligent manufacturing according to this embodiment. It should be noted that the technical solution of this document verification device for intelligent manufacturing and the technical solution of the document verification method for intelligent manufacturing described above belong to the same concept. For details not described in detail in the technical solution of the document verification device for intelligent manufacturing, please refer to the description of the technical solution of the document verification method for intelligent manufacturing described above.

[0197] Corresponding to the above method embodiments, this specification also provides an embodiment of a cable document verification device for intelligent manufacturing. Figure 7 A schematic diagram of a cable document verification device for smart manufacturing, provided in one embodiment of this specification, is shown. Figure 7 As shown, the device includes:

[0198] The second acquisition module 710 is configured to acquire a target verification template in response to a file verification request for a target cable file. The target verification template is constructed based on a target base class template corresponding to the target cable file. The target verification template includes content positioning information, which describes the position of the target verification content in the target cable file.

[0199] The second extraction module 720 is configured to extract the target verification content from the target cable file using the content location information;

[0200] The second verification module 730 is configured to verify the target verification content and obtain the target verification result of the target cable file.

[0201] The scheme implemented in this specification, in response to a file verification request for a target cable file, obtains a target verification template. This target verification template is constructed based on a target base class template corresponding to the target cable file. The target verification template includes content location information, which describes the location of the target verification content within the target cable file. Using the content location information, the target verification content is extracted from the target cable file. The target verification content is then verified to obtain the target verification result for the target cable file. Thus, based on the target verification template, the extraction and verification of target verification content in the target cable file can be automated, improving the accuracy and efficiency of the verification. The content location information enables complete and accurate extraction of the target verification content, reducing the risk of content omission. Constructing the target verification template based on the target base class template improves the efficiency and flexibility of template construction.

[0202] The above is a schematic scheme of a cable document verification device for intelligent manufacturing according to this embodiment. It should be noted that the technical solution of this cable document verification device for intelligent manufacturing and the technical solution of the cable document verification method for intelligent manufacturing described above belong to the same concept. For details not described in detail in the technical solution of the cable document verification device for intelligent manufacturing, please refer to the description of the technical solution of the cable document verification method for intelligent manufacturing described above.

[0203] Figure 8 This specification illustrates a structural block diagram of a computing device according to one embodiment. The components of the computing device 800 include, but are not limited to, a memory 810 and a processor 820. The processor 820 is connected to the memory 810 via a bus 830, and a database 850 is used to store data.

[0204] The computing device 800 also includes an access device 840, which enables the computing device 800 to communicate via one or more networks 860. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 840 may include one or more of any type of wired or wireless network interface (e.g., Network Interface Card (NIC)), such as an IEEE 802.11 Wireless Local Area Networks (WLAN) interface, a Wi-MAX (World Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0205] In one embodiment of this specification, the above-described components of the computing device 800 and Figure 8 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 8 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0206] The computing device 800 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 800 can also be a mobile or stationary server.

[0207] The processor 820 is used to execute computer programs / instructions, which, when executed by the processor, implement the steps of the document verification method for intelligent manufacturing or the cable document verification method for intelligent manufacturing.

[0208] The above is a schematic scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device belongs to the same concept as the technical solutions of the document verification method for intelligent manufacturing and the cable document verification method for intelligent manufacturing described above. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solutions of the document verification method for intelligent manufacturing or the cable document verification method for intelligent manufacturing described above.

[0209] An embodiment of this specification also provides a computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the above-described document verification method for smart manufacturing or cable document verification method for smart manufacturing.

[0210] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium belongs to the same concept as the technical solutions of the document verification method for intelligent manufacturing and the cable document verification method for intelligent manufacturing described above. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solutions of the document verification method for intelligent manufacturing or the cable document verification method for intelligent manufacturing described above.

[0211] An embodiment of this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described document verification method for smart manufacturing or cable document verification method for smart manufacturing.

[0212] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product belongs to the same concept as the technical solutions of the document verification method for intelligent manufacturing and the cable document verification method for intelligent manufacturing described above. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solutions of the document verification method for intelligent manufacturing or the cable document verification method for intelligent manufacturing described above.

[0213] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0214] Computer instructions include computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. Computer-readable media can include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in computer-readable media can be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.

[0215] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.

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

[0217] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. A document verification method for intelligent manufacturing, characterized in that, include: In response to a file verification request for a target file, a target verification template is obtained, wherein the target verification template is constructed based on the target base class template corresponding to the target file, and the target verification template includes content location information, which describes the position of the target verification content in the target file; Using the content location information, the target verification content is extracted from the target file; The target verification content is verified to obtain the target verification result of the target file.

2. The method according to claim 1, characterized in that, The process of obtaining the target verification template includes: Obtain candidate verification templates; The target file and the candidate verification template are matched to obtain a matching index, wherein the matching index is used to describe the degree of content matching between the target file and the candidate verification template, and the matching index corresponds one-to-one with the candidate verification template; The target verification template is determined based on the matching index and the candidate verification template.

3. The method according to claim 2, characterized in that, The process of matching the target file and the candidate verification template to obtain matching metrics includes: The target file is parsed to obtain its content; Based on the target area in the target file, determine the template content to be matched for the candidate verification template; The content of the target file is matched with the content of the template to be matched to obtain the matching index.

4. The method according to claim 2, characterized in that, The step of determining the target verification template based on the matching index and the candidate verification template includes: If the candidate verification template does not meet the template determination conditions based on the matching index, the candidate verification template is updated based on the target file to obtain the updated candidate verification template. Return to the step of matching the target file and the candidate verification template to obtain matching indicators, until the candidate verification template meets the template determination conditions, and determine the target verification template.

5. The method according to claim 2, characterized in that, The process of obtaining candidate verification templates includes: Obtain a reference file of the same type as the target file; Using the reference file, the target base class template is updated to obtain the candidate verification template.

6. The method according to claim 1, characterized in that, The content location information includes start location information and end location information; The step of extracting the target verification content from the target file using the content location information includes: Based on the start position information and the end position information, the target verification content is extracted from the target file.

7. The method according to claim 1, characterized in that, The step of verifying the target content to obtain the target verification result of the target file includes: Based on the target verification content, a content verification graph is constructed, wherein the content verification graph uses key information in the target verification content as nodes and the relationships between the key information as edges; The content verification map is verified to obtain the target verification result of the target file.

8. The method according to any one of claims 1 to 7, characterized in that, After extracting the target verification content from the target file using the content location information, the process further includes: Obtain file adjustment information for the target file; Based on the file adjustment information and the target verification content, the target file is adjusted to obtain the adjusted target file.

9. The method according to any one of claims 1 to 7, characterized in that, After verifying the target verification content and obtaining the target verification result of the target file, the process further includes: If the target file passes the verification, the target file will be uploaded to the shared database.

10. The method according to claim 9, characterized in that, After uploading the target file to the shared database, the process also includes: In response to a modification request for the target file, the target file is extracted from the shared database and modified to obtain a modified target file; If the target modified file passes the verification, the target file in the shared database is replaced with the target modified file.

11. A method for verifying cable documents in intelligent manufacturing, characterized in that, include: In response to a file verification request for a target cable file, a target verification template is obtained, wherein the target verification template is constructed based on the target base class template corresponding to the target cable file, and the target verification template includes content location information, which describes the position of the target verification content in the target cable file; Using the content location information, the target verification content is extracted from the target cable file; The target verification content is verified to obtain the target verification result of the target cable file.

12. A document verification device for intelligent manufacturing, characterized in that, include: The first acquisition module is configured to acquire a target verification template in response to a file verification request for a target file. The target verification template is constructed based on the target base class template corresponding to the target file. The target verification template includes content positioning information, which describes the position of the target verification content in the target file. The first extraction module is configured to extract the target verification content from the target file using the content location information; The first verification module is configured to verify the target verification content and obtain the target verification result of the target file.

13. A computing device, characterized in that, include: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that, It stores a computer program / instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 11.

15. A computer program product, characterized in that, Includes a computer program / instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 11.

Images