Email relationship analysis and viewing method, auxiliary office plug-in and electronic device

Abstract

The present application provides an email relationship analysis and viewing method, an auxiliary office plug-in, and an electronic device, which relate to the field of email data analysis. The method first determines an email relationship tree diagram based on the association relationship between each email obtained, and the tree diagram includes multiple groups of email relationship trees, each group of relationship trees includes one or more emails; then generates and displays an email relationship thumbnail based on the email relationship tree diagram to provide an overview of the overall structure; displays the indicator of the key email relationship tree in the thumbnail to highlight the key points to improve the screening efficiency; by responding to the interactive operation of the target indicator, expands and displays the detailed relationship diagram of the corresponding target email relationship tree, providing a dynamic and interactive browsing mechanism. The above method solves the problems of low user interaction efficiency and weak visualization for complex email interaction scenarios, and achieves the effect of enhancing the interactive experience and improving the efficiency of information screening.

Description

Technical Field

[0001] The present application relates to the field of email data analysis, and in particular to a method for analyzing and viewing email relationships, an auxiliary office plug-in, and an electronic device. Background Art

[0002] As a crucial tool for modern business and personal communication, email usage continues to grow in both frequency and volume. With the advancement of enterprise digital transformation, the number of emails stored in email systems is growing exponentially. Individual users may participate in multiple email threads simultaneously, covering multiple topics and contacts. Traditional email clients typically display emails in chronological order or by folder. This linear display format makes it difficult to intuitively reflect the relationships between emails. When users need to review the complete communication history on a specific topic, they often need to manually search and piece together related emails scattered across different time points, a time-consuming process that can easily miss important information.

[0003] In the existing technology, some email systems provide an email threading function that can group emails with the same subject. However, this simple grouping method based on a single attribute cannot effectively handle complex email interaction scenarios across topics and multiple participants. Summary of the Invention

[0004] The purpose of the embodiments of the present application is to provide an email relationship analysis and viewing method, an auxiliary office plug-in and an electronic device to solve the technical problems existing in the above-mentioned prior art.

[0005] In a first aspect, an embodiment of the present invention provides a method for analyzing and viewing email relationships, the method comprising: obtaining the association relationships between individual emails, and determining an email relationship tree diagram based on the association relationships, wherein the email relationship tree diagram comprises multiple groups of email relationship trees, and each group of email relationship trees comprises one or more emails; based on the email relationship tree diagram, generating and displaying an email relationship thumbnail; wherein the email relationship thumbnail displays an indication mark of a key email relationship tree in multiple groups of email relationship trees; and in response to an interactive operation on a target indication mark, expanding and displaying a detailed relationship diagram of a target email relationship tree corresponding to the target indication mark.

[0006] In some optional implementations, the above-mentioned acquisition of the association relationship between each email includes: extracting metadata of each email, the above-mentioned metadata including at least one of the subject, sender, recipient, timestamp, and referenced email ID; based on the above-mentioned metadata, determining the association relationship between emails through preset association rules, the above-mentioned association rules including any one or more of the following: the keyword similarity of the above-mentioned subject exceeds a threshold; the above-mentioned sender and / or the above-mentioned recipient belong to the same group; the interval of the above-mentioned timestamps is less than a preset time length; the ID of other emails is referenced in the current email content.

[0007] In some optional implementations, the key email relationship tree is determined by: counting characteristic parameters of each group of email relationship trees, where the characteristic parameters include at least one of the number of emails, the number of users involved, the number of attachments included, and the frequency of email interactions; calculating the importance score of each group of email relationship trees based on the characteristic parameters, and selecting the email relationship tree whose importance score is higher than a preset threshold as the key email relationship tree.

[0008] In some optional implementations, the above-mentioned interactive operations include clicking, double-clicking or hovering; the above-mentioned response to the interactive operation on the target indicator identifier expands and displays the detailed relationship diagram of the target email relationship tree corresponding to the above-mentioned target indicator identifier, including: when it is detected that the user performs a click, double-click or hover operation on the above-mentioned target indicator identifier, triggering the expansion action to display the detailed relationship diagram of the target email relationship tree corresponding to the above-mentioned target indicator identifier; the above-mentioned detailed relationship diagram of the target email relationship tree includes: at least one information of the email timeline, the interaction path between the sender and the recipient, and the email attachment relationship.

[0009] In some optional implementations, the above-mentioned generation of email relationship thumbnails also includes: automatically adjusting the zoom ratio of the thumbnails according to the hierarchical depth of the email relationship tree; or assigning different color labels to different groups of email relationship trees to distinguish the projects, teams or business types to which they belong.

[0010] In some optional implementations, the above-mentioned automatic adjustment of the thumbnail zoom ratio according to the hierarchical depth of the email relationship tree includes: obtaining the maximum hierarchical depth of the current email relationship tree; determining the corresponding target zoom ratio based on the above-mentioned maximum hierarchical depth and a preset hierarchical zoom mapping relationship; wherein the above-mentioned hierarchical zoom mapping relationship is a linear mapping function or a nonlinear mapping function.

[0011] In some optional implementations, the above-mentioned email relationship tree diagram is a multi-level nested structure, including the following three levels: the first level is the email cluster, which is used to represent a group of highly related email collections; the second level is the email node, which is located inside each of the above-mentioned email clusters and is used to represent a single email and the basic attributes of the above-mentioned email; the third level is the interaction path, which connects each of the above-mentioned email nodes in a visual form and is used to represent the interaction relationship between each email.

[0012] In the second aspect, an embodiment of the present invention provides an auxiliary office plug-in for email relationship analysis and viewing, which plug-in includes: an email association relationship identification module, which is used to obtain the association relationship between each email, and determine the email relationship tree diagram based on the above association relationship, wherein the above email relationship tree diagram includes multiple groups of email relationship trees, and each group of email relationship trees includes one or more emails; a thumbnail generation module, which is used to generate and display email relationship thumbnails based on the above email relationship tree diagram; wherein the above email relationship thumbnail displays the indicator logo of the key email relationship tree in the multiple groups of email relationship trees; an interactive response module, which is used to respond to interactive operations on the target indicator logo, expand and display the detailed relationship diagram of the target email relationship tree corresponding to the above target indicator logo; a plug-in integration interface module, which is used to be integrated and installed with the email client, and provide a visual interface for users to call the above modules during the email reading process.

[0013] In a third aspect, an embodiment of the present invention provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the computer program, the steps of the method described in any one of the first aspects are implemented.

[0014] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to execute any method described in the first aspect above.

[0015] The present invention provides a method for analyzing and viewing email relationships, an auxiliary office plug-in, and an electronic device. The method first determines an email relationship tree diagram based on the acquired relationships between individual emails, structuring complex email relationships into an easy-to-understand and more intuitive tree diagram structure for easy classification and display. The tree diagram includes multiple groups of email relationship trees, each group of email relationship trees including one or more emails. Then, based on the email relationship tree diagram, an email relationship thumbnail is generated and displayed to provide an overview of the overall structure. By displaying indicators of key email relationship trees in the thumbnail, key points are highlighted to improve information screening efficiency. By responding to interactive operations on target indicators, the detailed relationship diagram of the corresponding target email relationship tree is expanded and displayed, providing a dynamic and interactive browsing mechanism that enables users to gain in-depth understanding of the details of the email relationships of interest on demand, thereby enhancing the interactive experience and the depth of analysis. In summary, the above method solves the problems of low user interaction efficiency and weak visualization in existing complex email interaction scenarios, achieving the effect of enhancing the interactive experience and improving information screening efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0017] Figure 1 A flowchart of a method for analyzing and viewing email relationships provided in an embodiment of the present application;

[0018] Figure 2 A schematic diagram of the structure of an email relationship tree diagram provided by an embodiment of the present invention;

[0019] Figure 3 A schematic diagram of the structure of an auxiliary office plug-in for analyzing and viewing email relationships provided by an embodiment of the present invention;

[0020] Figure 4 A schematic structural diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0022] With the widespread use of email in corporate office work, project collaboration, and personal communication, email data volume has grown rapidly, and the relationships between emails, such as references, forwarding, and replies, have become increasingly complex. Traditional email clients typically display emails in a linear list or simple tree structure, lacking effective organization and visualization of the overall relationships between emails. This leads to problems such as fragmented information, unclear context, and low search efficiency when users interact with emails.

[0023] Furthermore, in multi-project, multi-team collaborative work scenarios, users often need to quickly identify key communication links and core email threads from massive email volumes. However, existing email systems struggle to provide efficient email relationship analysis mechanisms and lack support for structured display and interactive browsing of email relationship graphs. This limitation is particularly prominent in high-information scenarios such as compliance audits, e-forensics, and project reconsideration. Therefore, there is an urgent need for an analysis method that can efficiently organize and visualize the relationships between emails, improve users' understanding of email interaction paths, and enable rapid identification and in-depth review of key email relationships through optimized interactive design.

[0024] Based on this, the embodiment of the present invention provides an email relationship analysis and viewing method, an auxiliary office plug-in and an electronic device to solve the above problems. To facilitate understanding of this embodiment, first, a detailed description of the email relationship analysis and viewing method disclosed in the embodiment of the present invention is given. Figure 1 The flowchart of a method for analyzing and viewing email relationships is shown, and the method mainly includes the following steps S110 to S130:

[0025] S110: Acquire association relationships between the respective emails, and determine an email relationship tree diagram based on the association relationships, wherein the email relationship tree diagram includes multiple groups of email relationship trees, and each group of email relationship trees includes one or more emails;

[0026] In one embodiment, the association relationship between the above-mentioned emails can be determined by first extracting metadata of each email and then determining the association relationship based on the metadata of each email using a preset association rule.

[0027] The metadata may include at least one of the following: subject, sender, recipient, timestamp, and reference email ID; and the association rules may include any one or more of the following:

[0028] (1) The keyword similarity of the topic exceeds the threshold;

[0029] For example, if the subject of Email A is "Project A Progress Report" and the subject of Email B is "Project A Update - Wednesday Meeting Minutes," you can use a text similarity algorithm (such as cosine similarity or Jaccard similarity coefficient) to calculate the similarity between the keywords in the subjects of the two emails. If the similarity exceeds a threshold (such as 0.65), the two emails are considered to have a related subject.

[0030] (2) The sender and / or recipient belong to the same group;

[0031] For example, if email C is sent by "wang@company.com" and email D is sent to "li@company.com," and the system records organizational structure information: "wang and li both belong to the marketing department," we can determine whether the senders and / or recipients of the two emails belong to the same predefined group, such as department, team, or project group. If so, the two emails are considered to have a personal relationship.

[0032] (3) The timestamp interval is less than the preset duration;

[0033] For example, if email E's timestamp is 2025-07-09 09:45:00, and email F's timestamp is 2025-07-09 09:55:00, emails E and F were sent close together and may have been part of the same communication round or incident response. This can be determined by determining whether the timestamp interval between the two emails is less than a set time window (e.g., 30 minutes). If so, they are considered to be temporally proximate.

[0034] (4) The ID of other emails referenced in the current email content;

[0035] For example, if email G contains the ID "808" of email H, it can be determined that there is an interaction between the two emails. Furthermore, the specific type of interaction can be determined by referencing the position of the ID in the email, such as quoting, replying, or forwarding.

[0036] It should be noted that any two or more of the above association rules may be combined to perform a joint judgment, thereby improving the accuracy of the association judgment and facilitating the determination of the strength of the association between emails.

[0037] As a specific example, the association rules of the above four dimensions are assigned corresponding weights (the weight of the topic relevance association is a, the weight of the person relationship association is b, the weight of the time proximity association is c, and the weight of the interactive behavior association is d). Then, the judgment results of the above four dimensions and their corresponding weights are linearly weighted and summed to obtain the total association score. If the total score exceeds the set comprehensive judgment threshold (for example, 0.7), these emails are judged to have a strong correlation.

[0038] In a preferred example, if an email M and another email N meet the following conditions:

[0039] The subject keyword similarity is 0.72 (>0.65), indicating a subject relevance association, with a weight of 0.3. The senders belong to the same "Project Team X," indicating a personnel relationship association, with a weight of 0.2. The time interval is 18 minutes (<30 minutes), indicating a temporal proximity association, with a weight of 0.25. The body of email N references the ID of email M, indicating an interactive behavior association, with a weight of 0.25. The total score is 0.3 + 0.2 + 0.25 + 0.25 = 1.0, which is much higher than the judgment threshold of 0.7. Therefore, it can be determined that the two emails belong to the same conversation thread or are highly correlated.

[0040] Furthermore, in another embodiment, a machine learning model can be used to dynamically adjust the weights of each rule, and the optimal weight combination can be trained based on historical data to further improve the judgment accuracy.

[0041] In summary, this step, by capturing the relationships between individual emails, establishes a logical connection between them, forming a foundational data structure for subsequent visual analysis. By integrating multidimensional rules and introducing a weighting mechanism, this solution can more accurately identify relationships between emails in complex email environments, enhancing the intelligent management capabilities of email analysis and review methods.

[0042] In one embodiment, the key email relationship tree may be determined in the following manner:

[0043] (1) Counting characteristic parameters of each group of email relationship trees, where the characteristic parameters may include at least one of the number of emails, the number of users involved, the number of attachments included, and the frequency of email interactions;

[0044] Among them, the total number of emails contained in each email relationship tree can reflect the length and continuity of the conversation; the number of different users participating in the email interaction in the email relationship tree (i.e., the number of users involved) can reflect the breadth of the discussion and the degree of multi-party participation; the total number of attachments carried by all emails in the email relationship tree (i.e., the number of attachments included) can be used to measure the intensity of information transmission; the above three characteristic parameters can all be obtained by counting the emails contained in the email relationship tree, and the email interaction frequency can be calculated based on parameters such as the number of emails contained in the email relationship tree and the analysis time period, which is used to reflect the activeness of the discussion.

[0045] As a specific example, methods for obtaining email interaction frequency include determining email interaction frequency based on time intervals. This process involves first determining the analysis time period (for example, a single day), then counting the number of emails sent and received within that time period, and finally calculating the average number of email interactions per day, week, or month as the email interaction frequency. This method helps understand the intensity of communication between users and trends over time.

[0046] As another specific example, determining email interaction frequency based on email response time can include calculating the time difference between the receipt and the sending of each reply email in the email relationship tree, calculating the average response time based on the obtained time difference, or calculating the distribution of emails within different response time intervals as the email interaction frequency. This method can be used to assess response speed and interaction enthusiasm, and is suitable for analyzing user response habits and service levels.

[0047] As another specific example, methods for determining email interaction frequency include: determining email interaction frequency based on the hierarchical depth of the email relationship tree. This can include analyzing the length of reply chains under each email subject and counting the number of emails in each length range, or simply using the longest chain length as an indicator of interaction frequency. This method uses the depth of the email thread—that is, the number of subsequent reply levels triggered by the original email—to measure the complexity and duration of the interaction, reflecting the depth of the discussion and the appeal of the topic.

[0048] The depth of an email relationship tree refers to the maximum number of nested levels of references formed by subsequent replies and forwards after an initial email (the root node) is sent. This depth can be used to measure the complexity of an email thread: deeper levels indicate a more continuous and progressive email conversation; shallower levels may indicate a simpler discussion or frequent interruptions.

[0049] (2) Calculate the importance score of each group of email relationship trees based on the above characteristic parameters, and select the email relationship trees with importance scores higher than the preset threshold as the key email relationship trees.

[0050] In this embodiment, the importance score of each email relationship tree can be determined based on the characteristic parameters and their assigned weights. For example, first, the characteristic parameters are assigned corresponding weights (weight w1 for email volume, weight w2 for number of users involved, weight w3 for number of attachments included, and weight w4 for email interaction frequency). Each parameter is then normalized, and the importance score of each email relationship tree is calculated using a weighted formula. In some other embodiments, a machine learning model can be introduced to automatically optimize the weight assignment strategy based on historical data.

[0051] The calculated importance score is compared with a preset threshold (e.g., 0.7). If the importance score of the email relationship tree exceeds the threshold, it is marked as a "critical email relationship tree." This critical email relationship tree can be used in advanced application scenarios such as subsequent prioritization, intelligent summary generation, risk auditing, and knowledge graph construction.

[0052] In a preferred example, it is assumed that the email relationship tree contains the following characteristic parameters: 25 emails, 6 users involved, 8 attachments, and an average interaction frequency of 1.2 emails per hour; the weight of the number of emails w1=0.25, the weight of the number of users involved w2=0.3, the weight of the number of attachments w3=0.2, and the weight of the email interaction frequency w4=0.25; after normalization and substitution into the above weight calculation, its importance score is 0.81, which exceeds the judgment threshold of 0.7, and is therefore identified as a critical email relationship tree.

[0053] Furthermore, in another embodiment, the selection of characteristic parameters and their corresponding weight configurations may be adjusted according to the user's customized needs to adapt to key email identification requirements in different business scenarios.

[0054] In summary, through the statistics and weighted scoring mechanism of multi-dimensional feature parameters, the present invention can efficiently and accurately identify the key email relationship tree in the email system, which helps to improve the intelligence level of enterprise information management and decision support capabilities.

[0055] S120: Generate and display an email relationship thumbnail based on the email relationship tree diagram; wherein the email relationship thumbnail displays an indicator of a key email relationship tree in the plurality of email relationship trees;

[0056] In one embodiment, the generating of the email relationship thumbnail may further include: automatically adjusting the scaling of the thumbnail according to the hierarchical depth of the email relationship tree;

[0057] Alternatively, assign different color labels to the email relationship trees of different groups to distinguish the projects, teams, or business types they belong to.

[0058] As a specific example, automatically adjusting the thumbnail zoom ratio based on the hierarchical depth of the email relationship tree can include: obtaining the maximum hierarchical depth of the current email relationship tree; determining a corresponding target zoom ratio based on the maximum hierarchical depth and a preset hierarchical zoom mapping relationship; wherein the hierarchical zoom mapping relationship is a linear mapping function or a nonlinear mapping function. In this embodiment, mathematical modeling is used to clarify the logical relationship between zoom ratio and hierarchical depth, which can improve the algorithm's feasibility and predictability.

[0059] As a specific example, the automatic adjustment of thumbnail scale based on the hierarchical depth of the email relationship tree can also include: when the hierarchical depth exceeds a first preset level, reducing the overall display scale of the thumbnails and highlighting key email clusters to guide user attention; when the hierarchical depth is less than a second preset level, increasing the display scale of the thumbnails and highlighting the interaction paths between email nodes. These examples can distinguish between email structures of varying complexity, adopting differentiated visual strategies, and optimizing the user experience.

[0060] In addition, the scaling ratio of thumbnails can be dynamically adjusted based on the user's screen resolution, display area size, and the complexity of the thumbnail itself. External environmental parameters (such as device information) can be introduced as the basis for scaling decisions to improve adaptability.

[0061] In another embodiment, after adjusting the thumbnail zoom ratio, the method may further include: rearranging the positions of key email nodes in the thumbnail to avoid visual overlap; and, if multiple key email relationship trees exist, sorting them by importance score and assigning priority display areas to enhance visibility. In this embodiment, not only is the overall zoom ratio controlled, but local layout optimization is also considered to improve visual clarity.

[0062] S130: In response to the interactive operation on the target indicator, expand and display a detailed relationship diagram of the target email relationship tree corresponding to the target indicator.

[0063] In one embodiment, the interactive operation includes clicking, double-clicking, or hovering; and the step of expanding and displaying a detailed relationship diagram of the target email relationship tree corresponding to the target indicator in response to the interactive operation on the target indicator may include:

[0064] When it is detected that the user clicks, double-clicks or hovers the target indicator, the expansion action is triggered and the detailed relationship diagram of the target email relationship tree corresponding to the target indicator is displayed to present the email interaction path and context information in the target email relationship tree.

[0065] The target email relationship tree detailed relationship diagram may include at least one of the following information: the timeline of the email, the interaction path between the sender and the recipient, and the relationship between the email attachments.

[0066] In one embodiment, the above-mentioned email relationship tree diagram may be a multi-level nested structure, see Figure 2 As shown, the multi-level nested structure may include the following three levels:

[0067] The first level is the email cluster, which represents a group of highly related emails. The second level is the email node, located within each email cluster, representing a single email and its basic attributes. Basic email attributes can include at least one of the sender, recipient, timestamp, subject summary, and attachment flags. By default, only key fields are displayed, expanding to reveal detailed content upon user interaction. The third level is the interaction path, which visually connects the email nodes and represents the interaction relationships between emails. These interactions can be actions such as quoting, replying, and forwarding.

[0068] In this embodiment, each email cluster represents a set of highly related emails (e.g., emails related to a project discussion, a case communication, or a meeting). There can be multiple email clusters, which can be distinguished by different background colors or borders ( Figure 2 Only one is shown).

[0069] When displayed on the visual interface, each email cluster can include a brief information label, such as "120 emails total, involving 5 people." Within the corresponding email cluster, email nodes, each icon representing a specific email, display basic attributes, including sender's profile picture / name, recipient, timestamp, subject summary, and whether there are attachments. However, by default, only key fields (such as sender + subject) are displayed. Hovering the mouse will open a brief preview window, which can be clicked to expand the details.

[0070] The interaction path is represented in the diagram by lines or curves with arrows connecting email nodes, which are used to represent behaviors such as quoting, replying, and forwarding between emails. The direction of the line can indicate the flow of the email. A brief interaction type identifier (such as "Re:", "Forwarded") can also be added to the path line, or different colors and line types can be used to represent different types of interactions (such as solid lines for direct replies and dotted lines for forwarding).

[0071] Users can click on the corresponding location (e.g., the expansion icon) of an email cluster to expand and view all email nodes and their interaction paths. Typically, the thumbnail view only displays the email cluster level, with indicators indicating key email relationship trees (e.g., red dots, stars, or color-coded highlights). Clicking on a specific email cluster opens a detailed relationship diagram for that cluster.

[0072] The above-described embodiment can improve user browsing efficiency by filtering key email relationship trees through email clusters; reduce information overload by utilizing email node thumbnails and interactive expansion mechanisms; and enhance context recognition capabilities through visual connections of interaction paths. The nested structure between each level is achieved through visual layout and user interaction mechanisms, allowing users to quickly understand the overall structure of email interactions at different levels of detail.

[0073] This embodiment provides a method for analyzing and viewing email relationships. First, by determining an email relationship tree diagram based on the acquired relationships between the various emails, the complex email relationship relationships are structured into an easy-to-understand and more intuitive tree diagram structure for easy classification and display. The tree diagram includes multiple groups of email relationship trees, each group of email relationship trees includes one or more emails. Then, based on the email relationship tree diagram, an email relationship thumbnail is generated and displayed to provide an overview of the overall structure. By displaying indicators of key email relationship trees in the thumbnail, key points are highlighted to improve information screening efficiency. By responding to interactive operations on target indicators, the detailed relationship diagram of the corresponding target email relationship tree is expanded and displayed, providing a dynamic and interactive browsing mechanism that allows users to deeply understand the details of the email relationships of interest on demand, thereby enhancing the interactive experience and the depth of analysis. In summary, the above method solves the problems of low user interaction efficiency and weak visualization in existing complex email interaction scenarios, and achieves the effect of enhancing the interactive experience and improving information screening efficiency.

[0074] Based on the same inventive concept, the embodiment of the present application also provides an auxiliary office plug-in for email relationship analysis and viewing, which can be used to implement the steps of the email relationship analysis and viewing method provided in any of the above embodiments, see Figure 3 As shown, the plugin includes:

[0075] The email association relationship identification module 310 is configured to obtain association relationships between emails and determine an email relationship tree diagram based on the association relationships, wherein the email relationship tree diagram includes multiple groups of email relationship trees, each group of email relationship trees includes one or more emails;

[0076] The thumbnail generation module 320 is configured to generate and display an email relationship thumbnail based on the email relationship tree diagram; wherein the email relationship thumbnail displays an indicator of a key email relationship tree in a plurality of email relationship trees;

[0077] The interactive response module 330 is configured to respond to the interactive operation on the target indicator, expand and display the detailed relationship diagram of the target email relationship tree corresponding to the target indicator;

[0078] The plug-in integration interface module 340 is used for integration installation with the email client and provides a visual interface for users to call the above functional modules during email reading.

[0079] This embodiment provides an auxiliary office plug-in for analyzing and viewing email relationships, which is suitable for enterprise mailbox systems, desktop email clients or web email platforms, and is particularly suitable for mainstream email environments such as Outlook, Exchange Server, and Webmail.

[0080] In one embodiment, the plug-in includes multiple functional modules, each of which implements the structured organization and visual presentation of email information. The email association identification module is used to obtain user email data from the local or server side and, by parsing email metadata (such as sender, recipient, timestamp, reference ID, etc.), construct a tree diagram of email associations. This tree diagram organizes email interaction paths in a hierarchical structure, facilitating subsequent visualization.

[0081] The thumbnail generation module generates an email relationship thumbnail based on the email relationship tree diagram and displays it on the display interface. The thumbnail contains multiple indicators, each representing a key email relationship tree. The thumbnail generation may be based on characteristic parameters such as the number of emails, the number of users involved, the density of attachments, and the frequency of interaction. Key email relationship trees are selected using a pre-defined importance scoring mechanism to ensure that only the most noteworthy email threads are highlighted.

[0082] The interaction response module detects user interactions with specific indicators in the thumbnail (e.g., clicks, double-clicks, hovering), and expands the corresponding email relationship tree into a detailed view. This detailed view includes the email timeline, the communication path between sender and recipient, and the relationships between email attachments, helping users gain a deeper understanding of the email interaction context.

[0083] Furthermore, these plug-ins can also include a plug-in integration interface module that supports seamless integration with various email clients. This module provides a standard API interface, compatible with multiple operating systems and browser environments, and allows users to install and activate the plug-in with a single click through a graphical interface, without having to change their existing email usage habits.

[0084] In actual deployment, the plug-in can run on local clients, cloud servers, or in a hybrid architecture, offering excellent scalability and cross-platform adaptability. For example, in an Outlook environment, the plug-in can be integrated through the VSTO framework; in a webmail system, it can be embedded in the page through a JavaScript extension mechanism and call backend interfaces to obtain data.

[0085] In summary, this office assistant plug-in effectively solves the problems of scattered email information, unclear context, and difficulty in finding in traditional email systems. Through structured organization and visual display, it significantly improves the user's understanding efficiency and operational convenience of the email interaction path.

[0086] The implementation principles and technical effects of the auxiliary office plug-in provided in the embodiments of this application are the same as those of the aforementioned method embodiments. For the sake of brevity, any details not mentioned in the auxiliary office plug-in embodiments are referred to the corresponding content in the aforementioned method embodiments. The auxiliary office plug-in for analyzing and viewing email relationships provided in the embodiments of this application shares the same technical features as the email relationship analysis and viewing method provided in the aforementioned embodiments, and therefore solves the same technical problems and achieves the same technical effects.

[0087] An embodiment of the present application further provides an electronic device. Specifically, the electronic device includes a processor and a storage device; the storage device stores a computer program, and when the computer program is run by the processor, it executes the method described in any one of the above-mentioned embodiments.

[0088] Figure 4 A structural diagram of an electronic device provided in an embodiment of the present application, the electronic device 400 includes: a processor 40, a memory 41, a bus 42 and a communication interface 43, wherein the processor 40, the communication interface 43 and the memory 41 are connected via the bus 42; the processor 40 is used to execute an executable module stored in the memory 41, such as a computer program.

[0089] Memory 41 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Communication between the system network element and at least one other network element is achieved through at least one communication interface 43 (which may be wired or wireless), and may utilize the Internet, a wide area network, a local area network, a metropolitan area network, or the like.

[0090] The bus 42 may be an ISA bus, a PCI bus, or an EISA bus. The bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, Figure 4 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0091] Among them, the memory 41 is used to store programs, and the processor 40 executes the program after receiving the execution instruction. The method executed by the process definition device disclosed in any embodiment of the above-mentioned embodiment of the present invention can be applied to the processor 40 or implemented by the processor 40.

[0092] Processor 40 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method may be completed by hardware integrated logic circuits or software instructions in processor 40. The above processor 40 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present invention may be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or the like. The storage medium is located in the memory 41 , and the processor 40 reads the information in the memory 41 and completes the steps of the above method in combination with its hardware.

[0093] Corresponding to the above method, an embodiment of the present application also provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are called and executed by the processor, the computer-executable instructions prompt the processor to execute the steps of the above method.

[0094] In the embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interface, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0095] In addition, the units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0096] Furthermore, the functional modules in each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0097] It should be noted that if the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the existing technology, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program code.

[0098] In this document, relational terms such as first and second, etc. are used merely to distinguish one entity or operation from another entity or operation, but do not necessarily require or imply any actual relationship or order between these entities or operations.

[0099] The above description is merely an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, various modifications and variations of the present application are possible. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for analyzing and viewing email relationships, characterized in that: include: Obtaining association relationships between the respective emails, and determining an email relationship tree diagram based on the association relationships, wherein the email relationship tree diagram includes multiple groups of email relationship trees, and each group of email relationship trees includes one or more emails; Counting characteristic parameters of each group of email relationship trees, the characteristic parameters including at least one of the number of emails, the number of users involved, the number of attachments included, and the frequency of email interactions; calculating an importance score for each group of email relationship trees based on the characteristic parameters, and selecting an email relationship tree with an importance score higher than a preset threshold as a key email relationship tree; The importance score is determined based on each feature parameter and the corresponding weight assigned to each feature parameter; Based on the email relationship tree diagram, generate and display an email relationship thumbnail; wherein the email relationship thumbnail displays an indicator mark of a key email relationship tree in a plurality of email relationship trees; In response to an interactive operation on a target indicator, unfold and display a detailed relationship diagram of a target email relationship tree corresponding to the target indicator; The email relationship tree diagram includes three levels corresponding to email clusters, email nodes, and interaction paths; when displayed on the visual interface, each email cluster contains a brief information label to represent a group of highly related emails; The email node is located inside each email cluster and is used to represent a single email and its basic attributes. By default, only the key fields of the basic attributes are displayed. A brief preview window pops up in response to a user's hover operation, and a click operation expands to display detailed content. The interaction path connects each of the email nodes in a visual form to represent the interaction relationship between the emails; the interaction relationship includes quoting, replying and forwarding behaviors between emails; the visualization form includes arrowed lines and / or interaction type identifiers connecting the email nodes; the direction of the line is used to indicate the direction of the email flow, and the color or line type of the line is used to represent different types of interactions.

2. The email relationship analysis and viewing method according to claim 1, characterized in that: The obtaining of the association relationship between the emails includes: Extracting metadata of each email, wherein the metadata includes at least one of a subject, a sender, a recipient, a timestamp, and a reference email ID; Based on the metadata, the association relationship between the emails is determined using preset association rules, where the association rules include any one or more of the following: The keyword similarity of the topic exceeds a threshold; The sender and / or the recipient belong to the same group; The time interval of the timestamps is less than a preset time length; The ID of other emails referenced in the current email content.

3. The email relationship analysis and viewing method according to claim 1, characterized in that: The interactive operation includes clicking, double-clicking or hovering; The step of responding to the interactive operation on the target indicator identifier and expanding and displaying a detailed relationship diagram of the target email relationship tree corresponding to the target indicator identifier includes: When it is detected that the user performs a click, double-click or hover operation on the target indicator, an expansion action is triggered to display a detailed relationship diagram of the target email relationship tree corresponding to the target indicator; The target email relationship tree detailed relationship diagram includes at least one of: a timeline of the email, an interaction path between the sender and the recipient, and a relationship between email attachments.

4. The email relationship analysis and viewing method according to claim 1, characterized in that: Generating the email relationship thumbnail further includes: Automatically adjust the scale of thumbnails according to the depth of the email relationship tree; Alternatively, assign different color labels to the email relationship trees of different groups to distinguish the projects, teams, or business types they belong to.

5. The email relationship analysis and viewing method according to claim 4, characterized in that: The automatic adjustment of the thumbnail scaling ratio according to the hierarchical depth of the email relationship tree includes: Get the maximum level depth of the current email relationship tree; Based on the maximum hierarchical depth and a preset hierarchical scaling mapping relationship, a corresponding target scaling ratio is determined; wherein the hierarchical scaling mapping relationship is a linear mapping function or a nonlinear mapping function.

6. An auxiliary office plug-in for analyzing and viewing email relationships, characterized in that: The plug-ins include: An email association relationship identification module, configured to obtain association relationships between emails and determine an email relationship tree diagram based on the association relationships, wherein the email relationship tree diagram includes multiple groups of email relationship trees, each group of email relationship trees includes one or more emails; A thumbnail generation module is configured to generate and display an email relationship thumbnail based on the email relationship tree diagram; wherein the email relationship thumbnail displays an indicator of a key email relationship tree in a plurality of email relationship trees; the key email relationship tree is determined by: counting characteristic parameters of each email relationship tree, the characteristic parameters including at least one of the number of emails, the number of users involved, the number of attachments included, and the frequency of email interactions; calculating an importance score for each email relationship tree based on the characteristic parameters, and selecting an email relationship tree having an importance score greater than a preset threshold as a key email relationship tree; the importance score is determined based on each characteristic parameter and the corresponding weight assigned to each characteristic parameter; An interactive response module, configured to respond to an interactive operation on a target indicator, and expand and display a detailed relationship diagram of a target email relationship tree corresponding to the target indicator; The email relationship tree diagram includes three levels corresponding to email clusters, email nodes, and interaction paths; when displayed on a visual interface, each email cluster contains a thumbnail information label for representing a set of highly related emails; the email node is located inside each email cluster and is used to represent a single email and its basic attributes; the basic attributes include: at least one of: sender, recipient, timestamp, subject summary, and attachment mark; by default, only key fields are displayed, a brief preview window pops up in response to a user's hover operation, and detailed content is expanded in response to a user's click operation; the interaction path connects each of the email nodes in a visual form to represent the interaction relationship between each email; the interaction relationship includes quoting, replying, and forwarding behaviors between emails; the visual form includes arrowed lines and / or interaction type identifiers connecting the email nodes; the direction of the line is used to indicate the email flow direction, and the color or line type of the line is used to represent different types of interactions; The plug-in integration interface module is used for integrated installation with the email client and provides a visual interface for users to call the above modules during email reading.

7. An electronic device comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 5 are implemented.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to execute the method according to any one of claims 1 to 5.

Images