Component data manual query method and device, equipment and storage medium

Abstract

The application discloses a component data manual query method, device and equipment and a storage medium, and the method comprises the following steps: obtaining a query field input by a user, and obtaining a target component data manual based on the query field; traversing a preset keyword dictionary, and judging whether the query field exists in the preset keyword dictionary; if the query field exists, obtaining a target mark code corresponding to the query field; obtaining and displaying a target data page page code corresponding to a target keyword in the target component data manual based on the target mark code, so that the user can quickly locate a target data page based on the displayed target data page page code. Different from the existing component data manual query method, the application can obtain the target component data manual based on the query field input by the user, and quickly locate the target data page page containing the component attribute required by the user based on the query field and the preset keyword dictionary, so that the efficiency of the user inquiring the component attribute is improved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method, apparatus, device, and storage medium for querying component datasheets. Background Technology

[0002] With the development of the electronics industry, electronic components are constantly being updated and iterated. The number of components has now reached tens of millions. Engineers cannot be fully familiar with the specific properties of all components. Therefore, they generally rely on component datasheets to understand component performance for design purposes. However, each component may have dozens or even hundreds of pages of information. Therefore, when engineers look up the information or attributes of a component they want (such as its package, humidity sensitivity rating, or parameters), they usually have to spend a considerable amount of time and effort searching through the documentation.

[0003] While existing electronic platforms allow users to find corresponding component datasheets by entering the component model, most of these datasheets lack a fixed format, and some don't even have a table of contents. When it's necessary to query specific parameters or functions of a component, it's often necessary to search page by page, which is very inconvenient. Therefore, the efficiency of querying component attributes in existing component datasheet query methods is relatively low.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this invention is to provide a method, apparatus, device, and storage medium for querying component datasheets, aiming to solve the technical problem of low efficiency in querying component attributes in existing component datasheet query methods.

[0006] To achieve the above objectives, the present invention provides a method for querying component datasheets, the method comprising the following steps:

[0007] Obtain the query fields input by the user, and obtain the target component datasheet based on the query fields;

[0008] The preset keyword dictionary is traversed, and it is determined whether the query field exists in the preset keyword dictionary;

[0009] If it exists, obtain the target tag code corresponding to the query field;

[0010] Based on the target tag encoding, the target data page number corresponding to the target keyword in the target component datasheet is obtained and displayed, so that the user can quickly locate the target data page according to the displayed target data page number.

[0011] Optionally, before obtaining the query fields input by the user, the method further includes:

[0012] Preprocess the preset query reference information to obtain keywords;

[0013] Generate a preset keyword dictionary based on the keywords;

[0014] Based on the preset keyword dictionary, a preset tagging program is invoked to tag the data pages of the sample component datasheet;

[0015] Based on the marked content of the sample component datasheet, a browsing interface for the sample component datasheet is generated, which is used to display the marked data pages of the sample component datasheet.

[0016] Optionally, the step of preprocessing the preset query reference information to obtain keywords includes:

[0017] The system iterates through a large number of historical query references and / or sample component datasheets input by different users, and identifies words with a frequency greater than a preset frequency as popular words.

[0018] The popular terms are filtered to obtain keywords.

[0019] Optionally, the step of calling a preset tagging program to tag the data pages of the sample component datasheet based on the preset keyword dictionary includes:

[0020] Extract a keyword from the preset keyword dictionary as the tag keyword;

[0021] Analyze the contents of the sample component datasheet;

[0022] Based on the parsing results, a preset marking program is invoked to mark the data pages in the sample component datasheet containing the marked keywords with the corresponding codes for the marked keywords;

[0023] Return to the step of extracting a keyword from the preset keyword dictionary as a tag keyword, until all keywords in the preset keyword dictionary have been tagged.

[0024] Optionally, the step of returning to the step of extracting a keyword from the preset keyword dictionary as a tag keyword, until all keywords in the preset keyword dictionary have been tagged, further includes:

[0025] The sample component datasheet is traversed, and when the number of tag codes on a certain data page is greater than one, all tag codes on that data page are sorted according to the order of the keywords corresponding to the codes.

[0026] Optionally, the step of generating a browsing interface for the sample component datasheet based on the marked content of the sample component datasheet includes:

[0027] Based on the marking order of the marking codes, a first number of marking codes and a second number of data page numbers corresponding to the displayed marking codes are displayed on the browsing interface of the sample component datasheet, so that users can quickly locate the corresponding data page according to the displayed data page numbers;

[0028] Accordingly, after obtaining and displaying the target data page number corresponding to the target keyword in the target component datasheet based on the target tag encoding, so that the user can quickly locate the target data page according to the displayed target data page number, the method further includes:

[0029] Obtain the user's browsing heatmap, and perform a secondary sorting of the page numbers of the data pages displayed on the browsing interface based on the browsing heatmap.

[0030] Optionally, before calling the preset tagging program to tag the data pages of the sample component datasheet based on the preset keyword dictionary, the method further includes:

[0031] Convert the sample component datasheet to HTML format.

[0032] Accordingly, the step of calling a preset tagging program to tag the data pages of the sample component datasheet based on the preset keyword dictionary includes:

[0033] Based on the preset keyword dictionary, a preset tagging program is invoked to tag the data pages of the sample component datasheet in HTML format.

[0034] Furthermore, to achieve the above objectives, the present invention also proposes a component datasheet lookup device, the component datasheet lookup device comprising:

[0035] The data acquisition module is used to acquire the datasheet of the target component selected by the user and the query fields entered.

[0036] The data query module is used to traverse the preset keyword dictionary and determine whether the query field exists in the preset keyword dictionary;

[0037] The encoding acquisition module is used to acquire the target tag encoding corresponding to the query field if it exists.

[0038] The page display module is used to obtain and display the target data page number corresponding to the target keyword in the target component data sheet based on the target tag encoding, so that the user can quickly locate the target data page according to the displayed target data page number.

[0039] Furthermore, to achieve the above objectives, the present invention also proposes a component datasheet query device, the device comprising: a memory, a processor, and a component datasheet query program stored in the memory and executable on the processor, the component datasheet query program being configured to implement the steps of the component datasheet query method described above.

[0040] In addition, to achieve the above objectives, the present invention also proposes a storage medium storing a component datasheet lookup program, wherein when the component datasheet lookup program is executed by a processor, it implements the steps of the component datasheet lookup method described above.

[0041] This invention discloses a method, apparatus, device, and storage medium for querying component datasheets. The method includes: acquiring a query field input by a user and acquiring a target component datasheet based on the query field; traversing a preset keyword dictionary and determining whether the query field exists in the preset keyword dictionary; if it exists, acquiring a target tag code corresponding to the query field; and acquiring and displaying the target data page number corresponding to the target keyword in the target component datasheet based on the target tag code, so that the user can quickly locate the target data page based on the displayed target data page number. Unlike existing component datasheet query methods, this invention can acquire the target component datasheet and target tag code corresponding to the query field based on a preset keyword dictionary and the user-input query field, and acquire and display the target data page number corresponding to the query field based on the target tag code, thereby locating the target data page. Therefore, this invention can acquire the target component datasheet based on the user-input query field and quickly locate the target data page containing the component attributes that the user needs to query, thereby improving the efficiency of the user's query for component attributes. Attached Figure Description

[0042] Figure 1 This is a schematic diagram of the structure of the component datasheet query device for the hardware operating environment involved in the embodiments of the present invention;

[0043] Figure 2 This is a flowchart illustrating the first embodiment of the component datasheet lookup method of the present invention;

[0044] Figure 3 This is a schematic diagram of the target data page number display interface in the first embodiment of the component datasheet query method of the present invention;

[0045] Figure 4 This is a flowchart illustrating the second embodiment of the component datasheet lookup method of the present invention;

[0046] Figure 5 This is a flowchart illustrating the third embodiment of the component datasheet lookup method of the present invention;

[0047] Figure 6 This is a structural block diagram of the first embodiment of the component datasheet query device of the present invention.

[0048] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0049] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0050] Reference Figure 1 , Figure 1 This is a schematic diagram of the device structure for querying component datasheets in the hardware operating environment involved in the embodiments of the present invention.

[0051] like Figure 1 As shown, the component datasheet query device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wireless-Fidelity (Wi-Fi) interface). The memory 1005 may be high-speed random access memory (RAM) or stable non-volatile memory (NVM), such as a disk drive. The memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001.

[0052] Those skilled in the art will understand that Figure 1The structures shown do not constitute a limitation on the component datasheet lookup device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0053] like Figure 1 As shown, the memory 1005, which serves as a storage medium, may include an operating system, a data storage module, a network communication module, a user interface module, and a component datasheet lookup program.

[0054] exist Figure 1 In the component datasheet query device shown, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the component datasheet query device of the present invention can be set in the component datasheet query device, and the component datasheet query device calls the component datasheet query program stored in the memory 1005 through the processor 1001 and executes the component datasheet query method provided in the embodiment of the present invention.

[0055] This invention provides a method for querying component datasheets, referring to... Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the component datasheet lookup method of the present invention.

[0056] In this embodiment, the component datasheet lookup method includes the following steps:

[0057] Step S10: Obtain the query fields input by the user, and obtain the target component datasheet based on the query fields;

[0058] It should be noted that the executing entity of the method in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer or personal computer, or other electronic devices capable of performing the same or similar functions. Here, the component datasheet lookup device (hereinafter referred to as the lookup device) described above will be used to specifically illustrate the component datasheet lookup methods provided in this embodiment and the following embodiments.

[0059] It should be noted that the query fields entered by the user can be component names, component parameters, such as component package size, capacitance and resistance values, or component functions and classifications. Therefore, the query device can obtain the component that the user needs to query, i.e. the target component, from the query fields. It can be understood that the query device can also obtain the datasheet of the target component based on the query fields.

[0060] Step S20: Traverse the preset keyword dictionary and determine whether the query field exists in the preset keyword dictionary;

[0061] It should be noted that the aforementioned preset keyword dictionary can be a dictionary containing a large number of keywords pre-stored in the aforementioned query device. These keywords can be frequently used query terms extracted from the user's search history, or they can be frequently used query terms for the corresponding product category based on the statistics of component categories. Therefore, the process of determining whether a query field exists can be to search the aforementioned preset keyword dictionary for keywords that are the same as or related to the words in the query field.

[0062] Step S30: If it exists, obtain the target tag code corresponding to the query field;

[0063] It should be noted that the aforementioned keywords have a one-to-one correspondence with a tag code, and the correspondence between keywords and tag codes is stored in a tag code correspondence table, which is also stored in the aforementioned query device. The tag code can be Chinese or English, or it can be numbers or symbols; this embodiment does not limit the specific form of the tag code.

[0064] It's important to understand that one tag code can correspond to multiple keywords. For example, the tag code "Package" can correspond to multiple keywords such as "Outline," "Dimension," and / or "Soldering Footprint." That is, keywords with the same meaning or belonging to the same category may correspond to the same tag code. The target tag code mentioned above is the tag code searched from a pre-defined keyword dictionary based on the user-input query field. It's understandable that the user-input query field may contain more than one word, therefore the number of target tag codes obtained based on the query field may also be more than one.

[0065] Step S40: Based on the target tag encoding, obtain and display the target data page number corresponding to the target keyword in the target component data sheet, so that the user can quickly locate the target data page according to the displayed target data page number.

[0066] It should be noted that after obtaining the target tag code, the target data page marked with the target tag code in the target component datasheet can be retrieved. This target data page can be a data page containing (or possessing) information related to the component attributes that the user wishes to obtain. Furthermore, since there may be more than one target tag code, and the retrieved target data page may also be more than one page, the query device will display the target tag code and the corresponding target data page number together when retrieving and displaying the target data page number. For ease of understanding, [the following is a simplified explanation]. Figure 3 This example is used for illustration, but it does not limit the scope of this solution. Figure 3 This is a schematic diagram of the target data page number display interface in the first embodiment of the component datasheet query method of the present invention, as shown below. Figure 3 As shown, if the user inputs the query field "STM32F103ZET6", the query device will display the relevant datasheets "STM32F103ZET6 DatasheetPDF", "STM32F103ZET6 Pinout Diagram", "STM32F103ZET6 User Reference ManualGuide", and "STM32F103ZET6 Application Note". Simultaneously, the query device can also display the target tag code and the target data page number. The display format can be that the tag code is displayed first, followed by the corresponding target data page number. For example, in the datasheet "STM32F103ZET6 Datasheet PDF", the target tag code is "Pinout Diagram" and the target data page numbers are "Page25, Page26, Page27, Page28, Page29". The target tag code and the target data page number are connected by "on" to allow the user to locate the specific search content, and the displayed target data page number allows the user to navigate to the target data page where detailed data can be obtained.

[0067] In its implementation, the query device obtains the query fields input by the user and retrieves the datasheets of the target components the user wants to query based on the query fields. Then, the query device searches for the query fields in a preset keyword dictionary. After finding keywords that are the same as or related to the query fields, it retrieves the target tag codes corresponding to the keywords based on the tag code mapping table. Finally, it retrieves the target data page based on the target tag codes and displays the target tag codes and the corresponding target data page numbers together. This allows users to quickly locate the content to be searched based on the target tag codes and quickly locate the target data page containing (or having) the data related to the component attributes that the user wants to obtain based on the target data page numbers after the target tag codes.

[0068] This embodiment obtains the user-input query field and retrieves the target component datasheet based on it. It iterates through a preset keyword dictionary and determines if the query field exists within the dictionary. If it does, it obtains the target tag code corresponding to the query field. Based on the target tag code, it retrieves and displays the target data page number corresponding to the target keyword in the target component datasheet, allowing the user to quickly locate the target data page. Unlike existing component datasheet query methods, this invention obtains the target component datasheet and target tag code corresponding to the query field based on a preset keyword dictionary and the user-input query field. It then retrieves and displays the target data page number corresponding to the query field, thereby locating the target data page. Therefore, this embodiment can retrieve the target component datasheet based on the user-input query field and quickly locate the target data page containing the component attributes the user needs to query, thus improving the efficiency of the user's component attribute query.

[0069] Reference Figure 4 , Figure 4 This is a flowchart illustrating the second embodiment of the component datasheet lookup method of the present invention.

[0070] Understandably, before performing the process of locating the target data page by querying fields, it is necessary to first establish a pre-defined keyword dictionary and the correspondence between keywords and target data pages. Therefore, based on the above... Figure 2 The illustrated embodiment presents a second embodiment of the component datasheet lookup method of the present invention.

[0071] Therefore, in this embodiment, before step S10, the following steps are also included:

[0072] Step S01: Preprocess the preset query reference information to obtain keywords;

[0073] It should be noted that the aforementioned preset query reference information can be a large amount of historical query reference information input by different users, such as search records of query components or component parameters input by different users; it can also be fields existing in sample component datasheets. Therefore, the above process can be: traversing the words existing in the large amount of historical query reference information input by different users and / or sample component datasheets, taking words with a frequency greater than a preset frequency as popular words, filtering popular words, and obtaining keywords.

[0074] It's important to understand that the reason for filtering popular keywords is that the data manual contains some useless words that appear more frequently than the preset frequency, such as conjunctions like "and," "in," and "use." These useless words are irrelevant to the data query and therefore need to be filtered out. The filtering can be done manually or by loading the useless words into a filtering program and then using the configured filtering program to remove the obtained popular words to obtain usable keywords.

[0075] Step S02: Generate a preset keyword dictionary based on the keywords;

[0076] Step S03: Based on the preset keyword dictionary, call the preset tagging program to tag the data pages of the sample component datasheet;

[0077] It should be noted that the keywords in the aforementioned preset keyword dictionary are arranged in a specific order, which can be based on alphabetical order or on the frequency of keyword occurrence. The tagging process can be as follows: extract a keyword from the preset keyword dictionary as the tagging keyword; then parse the sample component datasheet; based on the parsing results, call the preset tagging program to tag the data pages in the sample component datasheet containing the tagging keyword with the corresponding code; finally, return to the step of extracting a keyword from the preset keyword dictionary as the tagging keyword, until all keywords in the preset keyword dictionary are tagged.

[0078] It is understandable that the aforementioned preset tagging program will call the aforementioned tag code correspondence table. When the preset tagging program detects that a certain keyword exists in a certain data page, it will call the tag code correspondence table to obtain the tag code corresponding to the keyword, and then tag the data page with the tag code.

[0079] It is important to understand that a single data page may contain multiple keywords. Therefore, a single data page may be marked with multiple tag codes. To prevent data disorder, this embodiment, after marking all keywords in the preset keyword dictionary, can traverse the sample component datasheet. When it is detected that the number of tag codes on a certain data page is greater than one, all tag codes on that data page are sorted according to the order of the keywords corresponding to the codes.

[0080] Step S04: Based on the marked content of the sample component datasheet, generate a browsing interface for the sample component datasheet. The browsing interface is used to display the marked data page of the sample component datasheet.

[0081] It should be noted that the process of generating the browsing interface can be based on the marking order of the marking codes in the sample component datasheet, displaying a first number of marking codes and a second number of data page numbers corresponding to the displayed marking codes, so that users can quickly locate the corresponding data page based on the displayed data page numbers. The specific display is as follows: Figure 3 As shown, the first quantity can be determined by the existing marker codes in the sample component datasheet, and the second quantity can be determined by the number of data pages corresponding to the marker codes. The browsing interface of the sample component datasheet is the page that displays the target marker codes and target data page numbers, and the marked data pages of the sample component datasheet correspond to the target data pages of the target component datasheet in the specific query process.

[0082] This embodiment obtains keywords by preprocessing preset query reference information; generates a preset keyword dictionary based on the keywords; uses a preset tagging program to tag the data pages of the sample component datasheet based on the preset keyword dictionary; and generates the sample component datasheet interface based on the tagged content of the sample component datasheet. The browsing interface is used to display the tagged data pages of the sample component datasheet. This embodiment analyzes the preset query reference information to construct a preset keyword dictionary, then encodes and tags the sample component datasheet based on the preset keyword dictionary and the preset tagging program, thereby constructing the browsing interface for the sample component datasheet. This allows users to quickly locate the target data page in the component datasheet through the tagged encoding when searching for components through the pre-constructed browsing interface, thus improving the browsing efficiency of the component datasheet.

[0083] Reference Figure 5 , Figure 5 This is a flowchart illustrating the third embodiment of the component datasheet lookup method of the present invention, based on the above. Figure 2 Alternatively, as shown in embodiment 4, a third embodiment of the component datasheet lookup method of the present invention is proposed. Figure 5 Based on Figure 1 The embodiments shown are examples of the proposed embodiments.

[0084] It's important to understand that component datasheets are typically stored in text formats such as PDF or Word. Current technologies usually convert these formats to text files before data analysis. However, text files are generally in formats similar to TXT files; their content is plain text without headings, fonts, font sizes, or other textual structures. Therefore, converting PDF or Word datasheets to text files results in the loss of structured information. In contrast, converting PDF or Word datasheets to HTML not only preserves the original content and structure (such as headings and tables), but also provides richer content. For example, a page with the keyword "parameter information" in the title is more likely to contain "parameter information" than a page where it appears in a section of the page. Therefore, in a pre-defined keyword dictionary, the former ("parameter information") will have higher priority than the latter. Therefore, converting component datasheets in PDF or Word format to HTML format can effectively utilize information such as keyword positions (titles) and styles (bold / enlarged) in the component datasheets, thereby improving the accuracy of hitting the target data pages.

[0085] Therefore, as a possible implementation, this embodiment further includes the following step before step S03:

[0086] Step S022: Convert the sample component datasheet to HTML format to obtain the sample component datasheet.

[0087] It should be understood that the above format conversion process can be achieved through format conversion software or a pre-written format conversion program.

[0088] Accordingly, step S03 includes:

[0089] Step S031: Based on the preset keyword dictionary, call the preset tagging program to tag the data pages of the HTML format sample component datasheet.

[0090] Understandably, the tagging steps for HTML format sample component datasheets are the same as those for other text format sample component datasheets. However, the keyword selection and positioning in HTML format sample component datasheets can target document titles, table column headers, or font changes (such as whether the font is bold or enlarged), thus making the content of HTML format component datasheets richer.

[0091] Furthermore, in this embodiment, after step S40, the following steps are also included:

[0092] Step S50: Obtain the user's browsing heatmap, and perform a secondary sorting of the page numbers of the data pages displayed on the browsing interface based on the browsing heatmap.

[0093] Understandably, in order to further facilitate user browsing and improve user browsing efficiency, this embodiment can also rearrange the page number order of the data pages displayed on the interface based on the browsing heatmap formed by the number of times the user stays on each data page, the duration of stay, and / or the click situation.

[0094] This embodiment converts the sample component datasheet into an HTML format; it acquires the user's browsing heatmap and re-sorts the page numbers of the data pages displayed on the browsing interface based on the heatmap. Therefore, compared to existing methods that directly extract text from component datasheets, this embodiment preserves the document structure information of the component datasheet by converting it to HTML, thus making the identification and location of target data pages more accurate. Furthermore, this embodiment can re-sort the page numbers of the target data pages displayed on the browsing interface based on the user's browsing heatmap, further improving the browsing efficiency of the component datasheet.

[0095] Furthermore, this embodiment of the invention also proposes a storage medium storing a component datasheet lookup program, wherein when the component datasheet lookup program is executed by a processor, it implements the steps of the component datasheet lookup method described above.

[0096] refer to Figure 6 , Figure 6 This is a structural block diagram of the first embodiment of the component datasheet query device of the present invention.

[0097] like Figure 6 As shown, the component datasheet lookup device proposed in this embodiment of the invention includes:

[0098] The data acquisition module 601 is used to acquire the datasheet of the target component selected by the user and the input query fields;

[0099] The data query module 602 is used to traverse the preset keyword dictionary and determine whether the query field exists in the preset keyword dictionary;

[0100] The encoding acquisition module 603 is used to acquire the target tag encoding corresponding to the query field if it exists.

[0101] The page display module 604 is used to obtain and display the target data page number corresponding to the target keyword in the target component data manual based on the target mark encoding, so that the user can quickly locate the target data page according to the displayed target data page number.

[0102] This embodiment obtains the user-input query field and retrieves the target component datasheet based on it. It iterates through a preset keyword dictionary and determines if the query field exists within the dictionary. If it does, it obtains the target tag code corresponding to the query field. Based on the target tag code, it retrieves and displays the target data page number corresponding to the target keyword in the target component datasheet, allowing the user to quickly locate the target data page. Unlike existing component datasheet query methods, this embodiment can obtain the target component datasheet and target tag code corresponding to the query field based on a preset keyword dictionary and the user-input query field, and then retrieve and display the target data page number corresponding to the query field, thereby locating the target data page. Therefore, this embodiment can quickly locate the target data page containing the component attributes the user needs to query based on the user-input query field, thus improving the efficiency of the user's component attribute query.

[0103] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0104] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

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

[0106] The above are merely preferred embodiments of the present invention and do not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for querying component datasheets, characterized in that, The methods for querying component datasheets include: Obtain the query fields input by the user, and obtain the target component datasheet based on the query fields; The preset keyword dictionary is traversed, and it is determined whether the query field exists in the preset keyword dictionary; If it exists, obtain the target tag code corresponding to the query field; Based on the target tag encoding, the page number of the target data page corresponding to the target keyword in the target component data manual is obtained and displayed, so that the user can quickly locate the target data page according to the displayed target data page number; the target data page is a data page containing component attribute information; Before obtaining the query fields input by the user, the process also includes: Preprocess the preset query reference information to obtain keywords; Generate a preset keyword dictionary based on the keywords; Based on the preset keyword dictionary, a preset tagging program is called to tag the data pages of the sample component datasheet. Keywords of the same category correspond to the same tag code. Based on the marked content of the sample component datasheet, a browsing interface for the sample component datasheet is generated, and the browsing interface is used to display the marked data page of the sample component datasheet. The step of generating a browsing interface for the sample component datasheet based on the marked content of the sample component datasheet includes: Based on the marking order of the marking codes, a first number of marking codes and a second number of data page numbers corresponding to the displayed marking codes are displayed on the browsing interface of the sample component datasheet, so that users can quickly locate the corresponding data page according to the displayed data page numbers; Accordingly, after obtaining and displaying the target data page number corresponding to the target keyword in the target component datasheet based on the target tag encoding, so that the user can quickly locate the target data page according to the displayed target data page number, the method further includes: Obtain the user's browsing heatmap, and perform a secondary sorting of the page numbers of the data pages displayed on the browsing interface based on the browsing heatmap.

2. The component datasheet lookup method as described in claim 1, characterized in that, The step of preprocessing the preset query reference information to obtain keywords includes: The system iterates through a large number of historical query references and / or sample component datasheets input by different users, and identifies words with a frequency greater than a preset frequency as popular words. The popular terms are filtered to obtain keywords.

3. The component datasheet lookup method as described in claim 1, characterized in that, The step of calling a preset tagging program to tag the data pages of the sample component datasheet based on the preset keyword dictionary includes: Extract a keyword from the preset keyword dictionary as the tag keyword; Analyze the contents of the sample component datasheet; Based on the parsing results, a preset marking program is invoked to mark the data pages in the sample component datasheet containing the marked keywords with the corresponding codes for the marked keywords; Return to the step of extracting a keyword from the preset keyword dictionary as a tag keyword, until all keywords in the preset keyword dictionary have been tagged.

4. The component datasheet lookup method as described in claim 3, characterized in that, The step of returning to the step of extracting a keyword from the preset keyword dictionary as a tag keyword, until all keywords in the preset keyword dictionary have been tagged, further includes: The sample component datasheet is traversed, and when the number of tag codes on a certain data page is greater than one, all tag codes on that data page are sorted according to the order of the keywords corresponding to the codes.

5. The component datasheet lookup method as described in claim 1, characterized in that, Before calling the preset tagging program to tag the data pages of the sample component datasheet based on the preset keyword dictionary, the process also includes: Convert the sample component datasheet to HTML format. Accordingly, the step of calling a preset tagging program to tag the data pages of the sample component datasheet based on the preset keyword dictionary includes: Based on the preset keyword dictionary, a preset tagging program is invoked to tag the data pages of the sample component datasheet in HTML format.

6. A component datasheet lookup device, characterized in that, The component datasheet lookup device is used to execute the component datasheet lookup method as described in any one of claims 1 to 5, and the device includes: The data acquisition module is used to acquire the datasheet of the target component selected by the user and the query fields entered. The data query module is used to traverse the preset keyword dictionary and determine whether the query field exists in the preset keyword dictionary; The encoding acquisition module is used to acquire the target tag encoding corresponding to the query field if it exists. The page display module is used to obtain and display the target data page number corresponding to the target keyword in the target component data manual based on the target tag encoding, so that the user can quickly locate the target data page according to the displayed target data page number; the target data page is a data page containing component attribute information.

7. A component datasheet lookup device, characterized in that, The device includes: a memory, a processor, and a component datasheet lookup program stored in the memory and executable on the processor, the component datasheet lookup program being configured to implement the steps of the component datasheet lookup method as described in any one of claims 1 to 5.

8. A storage medium, characterized in that, The storage medium stores a component datasheet lookup program, which, when executed by a processor, implements the steps of the component datasheet lookup method as described in any one of claims 1 to 5.

Images