A home-school communication data synchronization control method

Abstract

This application provides a method for controlling the synchronization of home-school communication data, including: identifying the online login records and read confirmation timestamps of two parents from dual account binding; extracting the text content of offline edited replies from the draft cache of the home-school communication system; verifying the initial merged version number generated by the parents' independent reply drafts based on the parent roles marked in the dual account binding; evaluating the synchronization tightness presented by the read coverage result and the latest read confirmation timestamp; analyzing whether the coverage result meets the consistency requirements of parent read aggregation; outputting the parent read aggregation curve; identifying the long-term evolution trajectory of the parents' independent reply drafts based on the complete parent read aggregation curve; determining the optimization path for merging delay and synchronously updating the judgment conditions for reply conflict inaccuracy; and drawing the parent read aggregation conclusion.

Description

Technical Field

[0001] This invention relates to the field of information technology, and in particular to a method for controlling the synchronization of home-school communication data. Background Technology

[0002] In the field of home-school communication, building an efficient and real-time information synchronization mechanism is particularly important. This area directly relates to the smoothness of communication between schools and families, affects the timely feedback and collaborative management of student education, and is an indispensable part of educational informatization. Especially in the information interaction between parents and schools, ensuring the accurate updating and feedback of message status has become a core requirement for ensuring communication quality. However, many current methods often overlook the complex impact of behavioral differences between accounts when dealing with multi-account binding scenarios. Especially when both parents are bound to the same student account, simply relying on the message read status to judge the parent's response can easily lead to information synchronization deviations. Existing solutions focus more on simple status updates at the technical level, but fail to fully consider the inconsistency of account behavior. For example, one parent may have read the message while the other has not, or may even be editing a reply. This behavioral difference directly interferes with the school's overall judgment of parental feedback. When parents participate in communication with two accounts simultaneously, the operation time and status of the two parents are different, and the system's processing record for the same message will be inconsistent. For example, one party may confirm that the message has been read, while the other party is editing the reply while offline, causing the system to fail to unify the message status in a timely manner. This not only delays the school's assessment of parental responses but can also lead to conflicting replies, preventing the school from accurately understanding the parents' true feedback. Specifically, in a real-world scenario, suppose a teacher posts a comment about a student's performance. The mother quickly views it on her phone and marks it as read, while the father is offline editing a detailed reply. Due to the different times and states of their actions, the system misaligns the message statuses. The school might mistakenly assume that both parents have fully understood and responded, when in fact the father's reply has not yet been submitted. This inconsistency directly impacts the school's accurate evaluation of parental feedback. Summary of the Invention

[0003] This invention provides a method for controlling the synchronization of home-school communication data, mainly comprising:

[0004] Obtain the login records and read confirmation timestamps of the two parents from the dual account binding relationship, extract the draft content of the offline edited reply, and verify the initial merged version number;

[0005] The timing compactness is assessed based on the initial merge version number and the read confirmation timestamp, and the content of reply conflicts and inaccuracies is identified and the message status convergence position is determined.

[0006] Adjust the read aggregation judgment conditions according to the message status convergence position, filter the leading account from the login record and verify the synchronization status of the draft content, and generate a unified merged version view;

[0007] The unified merged version view identifies merging logic inconsistencies, assesses the fallback extent of remaining branch versions, adjusts the importance of parent roles, and determines the read coverage results on the parent side.

[0008] Based on the read coverage results and the latest read confirmation timestamp, a synchronization compactness analysis is performed to generate a parent read aggregation curve;

[0009] Based on the parent read aggregation curve, the evolution trajectory of the parent's independent reply draft is determined, the merging delay path is optimized and the reply conflict inaccuracy judgment condition is updated, and the parent read aggregation conclusion is obtained.

[0010] Furthermore, the login records and read confirmation timestamps of the two parents are obtained from the dual-account binding relationship. The draft content of the offline edited reply is extracted, and the initial merged version number is verified, including:

[0011] For dual-account binding relationships, retrieve the login records of both parents' accounts and filter the time of viewing the read stamp records for the comment entries;

[0012] Locate the offline texts of two parents from the draft cache based on the reply topic clues, obtain the draft number, start editing time and end editing time, calculate the editing time and form a summary entry of parent behavior;

[0013] The reply topics of the mother's account and the father's account are distinguished according to the role tags in the parent behavior summary entries, and the initial merged version number of the independent reply draft is determined for each parent's offline text.

[0014] The draft number, role tag, and editing duration are concatenated in a preset order to form a version field. Based on the version field, the order in which the two parents independently replied to the draft is generated is recorded to obtain an initial merged version number that distinguishes the source of the replies from the two accounts.

[0015] Furthermore, based on the initial merge version number and the read confirmation timestamp, the timing compactness is evaluated, content with conflicting or inaccurate responses is identified, and the message status rendezvous position is determined, including:

[0016] Arrange the initial merged version number and the read confirmation timestamp in the order of their generation according to the event timeline, calculate the time interval between the version number writing time and the read confirmation timestamp, and obtain the time sequence compactness metric.

[0017] The offline texts of the two parents were segmented by sentence to locate the reply points. The conflicting statements in the two drafts under the same comment item were compared to identify the conflicting paragraphs and form the draft difference items.

[0018] Based on the draft difference entries, retrieve the read confirmation entries from the monitoring list, read the draft flag value and the last editing time, and incorporate them into the aggregation judgment field in conjunction with the time series compactness metric value.

[0019] The read aggregation lag is calculated based on the misalignment between the read confirmation timestamp and the last edit time, and the node of the lag on the event timeline is determined as the message status convergence position.

[0020] Furthermore, based on the message status convergence position, the read aggregation judgment conditions are adjusted, and the leading account is filtered from the login records and the synchronization status of the draft content is verified, including:

[0021] For the time-series misalignment at the message status convergence position, retrieve the set of trigger conditions for the read aggregation judgment, and offset and correct the threshold of the number of read accounts and the time window span according to the deviation direction of the misalignment at the attribution point to obtain the matching judgment conditions.

[0022] The session activity count and login terminal type of the two parent accounts are read from the login records. The activity count is compared according to the importance of the role label, and the account with the second highest activity is identified as the dominant account.

[0023] Based on the set of conflicting paragraphs in the draft differences, a copy of the offline edit response paragraphs from the dominant account is retrieved, and the annotation text is segmented by the parent annotation prefix symbol;

[0024] Based on the synchronization status of the read confirmation timestamp and the verification annotation text at the last edit time, texts registered later than the read confirmation timestamp are identified as unsynchronized.

[0025] Furthermore, by identifying contradictory merge logic entries through the unified merged version view, assessing the extent of the decline in remaining branch versions, and adjusting the importance of parent roles, including:

[0026] Scan the source markers of the responses from both accounts and the position of the main topic of the response from the unified merged version view. Register the entries that express mutual exclusion under the same topic position as entries with logical contradictions in the merge.

[0027] Extract the branch points of the version branches that were not included in the main line connection from the aforementioned logical contradiction entries to obtain the remaining branch versions;

[0028] For the version number values ​​of the remaining branch versions, the downward magnitude of the version rollback trajectory is compared along the message version number change record, and divided into large and small rollback levels according to a preset threshold to obtain the rollback magnitude evaluation value.

[0029] Based on the aforementioned pullback magnitude assessment value, retrieve the weight values ​​of both accounts, adjust the weight values ​​according to the gear indicator, and determine the adjusted weight values.

[0030] Furthermore, based on the read coverage results and the latest read confirmation timestamp analysis to determine synchronization tightness, a parent read aggregation curve is generated, including:

[0031] Extract the time period defined by the start and end times of merging from the read coverage results, aggregate the read stamp sequence of comment entries according to the parent account identifier, and retrieve the last entry as the latest stamp;

[0032] Calculate the distance between the latest stamp and the merging stop time, and extract the time interval between adjacent read stamps from the read stamp sequence to form the internal gap position;

[0033] Based on the spacing and the position of the internal gap, the density of the bearing is verified according to the preset consistent threshold value. If the spacing is lower than the upper limit and the width of the gap position is lower than the upper limit, the achievement mark is registered as an achievement value.

[0034] By connecting the endpoints of the covered time periods, the internal gap positions, and the achievement markers along the event timeline according to the issue position, a parent read aggregation curve is generated.

[0035] Furthermore, based on the parent read aggregation curve, the evolution trajectory of parents' independent reply drafts is determined, the merging delay path is optimized, and the reply conflict inaccuracy judgment conditions are updated, including:

[0036] Extract the draft number and editing time of each parent from the parent read aggregation curve, connect them in chronological order to form a draft item chronological chain, divide the long-term evolution segment and register the transition node as the node revision position to obtain the evolution trajectory;

[0037] By comparing the migration trends of role tag values ​​and importance rankings in the dual account binding history, the entries with falling rankings are identified as rollback triggers, forming change context entries;

[0038] Align the changed context entries with the parent read aggregation curve, use the continuous segments marked with consistency as the steady-state control baseline, and select the node revision bits and rollback trigger bits in the segments that have not achieved the goal as adjustment nodes.

[0039] Based on the adjustment node's synchronous offset drop and the degree of conflict in expression, update the consistency threshold and drop threshold, and refresh the judgment conditions.

[0040] Furthermore, generating a unified merged version view includes:

[0041] Read the paragraph writing time from the offline edit reply paragraph and the read confirmation timestamp, and match the comment item number with the parent account identifier to form a comparison record;

[0042] Extract paragraph copies of the dominant account from the comparison records, and select the sentence / segment links as the main reply items according to the reply topic;

[0043] After filtering out entries from the primary account, extract paragraph copies from the secondary account, segment the annotation text according to the parent annotation prefix symbol, verify the synchronization status based on the read confirmation timestamp and the write time, and record the unsynchronized status.

[0044] A dual-account reply source marker is attached to the main reply entry, and message version number change records are written to the version field to form a unified merged version view.

[0045] Furthermore, determining the read coverage result on the parent's end includes:

[0046] Read the endpoints of the coverage area from the read confirmation timestamps of the two parents, and then weight and merge the endpoints of the coverage area according to the adjusted dual account weight values ​​to generate the merged coverage area.

[0047] Based on the correspondence between the merged coverage area and the issue position of the comment items, the completeness of the coverage area's connection to the issue position is calculated to determine the read coverage result on the parent's end.

[0048] Furthermore, the generation of the parent read aggregation curve includes:

[0049] Extract the coverage period markers of the two parents from the read coverage results according to the parent account identifier, and retrieve the last entry of each parent's read stamp sequence as the latest read confirmation timestamp;

[0050] The absolute value of the difference between the latest read confirmation timestamps of the two parents is used as the synchronization offset difference, which is divided into different levels according to the preset offset threshold.

[0051] By comparing the coverage period markers of the two parents along the event timeline, and comparing the gap width of adjacent read stamps in the read stamp sequence, positions that exceed the preset upper limit are registered as gap positions that have not met the consistency requirements;

[0052] By sequentially connecting the endpoints of the coverage period, the synchronous offset difference, and the gap positions where the consistency requirements have not been met according to the order of the topics, an aggregation consistency mark is attached to generate a parent read aggregation curve.

[0053] The technical solutions provided by the embodiments of the present invention may include the following beneficial effects:

[0054] This invention discloses a method for controlling data synchronization in home-school communication. Addressing the unique business scenario of data synchronization and response conflicts between parent accounts in home-school communication, it integrates key issues such as parent read confirmation timestamps, offline draft editing, merged version views, and role importance offsets, forming a logically interconnected comprehensive challenge: how to achieve data synchronization consistency and precise conflict resolution across multiple parent accounts. This invention extracts read confirmation timestamps and offline draft content, combines them with message version numbers to generate a unified merged view, identifies inaccurate response conflict parts and adjusts triggering conditions, analyzes parent read coverage results and synchronization compactness, optimizes the merge delay path, dynamically updates conflict judgment conditions, and finally outputs a parent read aggregation curve and conclusions. Its core invention lies in ensuring the efficiency and accuracy of dual-account data synchronization through multi-dimensional data fusion and time-series analysis, significantly improving the collaborative efficiency and information consistency of home-school communication. Attached Figure Description

[0055] Figure 1 This is a flowchart of a home-school communication data synchronization control method according to the present invention.

[0056] Figure 2 This is a schematic diagram of a home-school communication data synchronization control method according to the present invention.

[0057] Figure 3 This is another schematic diagram of a home-school communication data synchronization control method according to the present invention. Detailed Implementation

[0058] The technical solutions of the embodiments of the present invention will be clearly and thoroughly described below with reference to the accompanying drawings. The described embodiments are merely some embodiments of the present invention.

[0059] like Figures 1-3 This embodiment of a home-school communication data synchronization control method may specifically include:

[0060] Step S101: Identify the online login records and read confirmation timestamps of the two parents from the dual account binding, extract the text content of the offline edited reply from the draft cache of the home-school communication system, and verify the initial merged version number generated by the parent's independent reply draft based on the parent role marked in the dual account binding.

[0061] For the aforementioned dual-account binding relationship, the login records of the two parents' accounts on the school-home communication platform are retrieved. Read stamps for teacher-issued comments are then extracted, recording the time each parent viewed the comments. For the draft cache on the school-home communication platform, the offline texts saved by each parent are located based on the reply topics of the comments. The draft number, start time, and last time of editing are extracted from the offline texts, resulting in a summary entry of parental behavior including login records, read stamps, draft numbers, and offline texts. The role tags indicating the dual-account binding relationship are retrieved from this summary entry. These role tags distinguish the reply topics of the mother's and father's accounts under the comments. For each parent's offline text, an initial merged version number is determined. This initial merged version number is formed by concatenating the draft number, role tag, and editing time in a preset order to create a version field. Based on this version field, the order in which the two independent reply drafts were generated on the school-home communication platform is recorded, resulting in an initial merged version number that distinguishes the source of the replies from both accounts.

[0062] In one embodiment, the home-school communication terminal is deployed between the school's academic affairs department and the parents' mobile devices, carrying the comments issued by teachers and the parents' responses to the comments. When a homeroom teacher issues a comment on a student's classroom performance, the comment is simultaneously pushed to the mother's and father's accounts, which are linked under a dual-account relationship.

[0063] Specifically, the dual-account binding relationship is recorded in the account binding table of the home-school communication terminal. The account binding table stores the student ID, mother's account identifier, father's account identifier, and corresponding role tag fields. When retrieving the login record entries of the two parents' accounts on the home-school communication terminal, starting from the account binding table, the login entry actions of the two parents' accounts after the time the comment entry was issued are retrieved by the student ID. The login record entries include the login time, login terminal type, and session identifier.

[0064] It should be noted that the process of filtering read stamps relies on the message reading log of the parent-teacher communication terminal. When a parent's account expands or swipes to the reading area within the session containing the comment item, the parent-teacher communication terminal writes a reading log record. This reading log record is associated with the comment item number, the parent's account identifier, and the viewing time. By retrieving the viewing time of the two parent accounts from the reading log by comment item number, the read stamps for the mother's account and the father's account are obtained.

[0065] Specifically, regarding the draft cache area of ​​the parent-teacher communication terminal, this draft cache area is a local storage area used by parents' mobile devices to temporarily store unsubmitted responses when offline. When a parent's account enters text under a comment item but has not yet clicked submit, the text is saved to the draft cache area as offline text, along with a draft number, the corresponding comment item number, and a response topic clue field. The offline text in the draft cache area is matched according to the comment item number, and copies of the offline text from the mother's and father's accounts are retrieved respectively. The start and end editing times are read from the metadata of the offline text, where the editing duration is obtained by subtracting the start editing time from the end editing time, resulting in a summary entry for parent behavior. This summary entry concatenates four types of fields: login record, read stamp, draft number, and offline text.

[0066] In one possible implementation, the role tag field includes values ​​for "mother" and "father." Role tags are retrieved from the parent behavior summary entries by account identifier, and each offline text is categorized into either the mother's or father's reply topic. Furthermore, an initial merged version number for each parent's offline text is determined.

[0067] For example, the initial merged version number uses a preset concatenation order, placing the draft number at the beginning, the role tag value in the middle, and the editing time value at the end, concatenating them with underscores as separators to form the version field. For instance, the version field for the mother's account is a concatenation of the draft number value, the mother's value, and the corresponding editing time value; the father's account forms another version field according to the same rule. Based on the version fields, the version registration ledger is written into the home-school communication terminal, and the two independent reply drafts are arranged according to the order of their initial editing time to obtain the initial merged version number that distinguishes the source of the replies from the two accounts.

[0068] It is understandable that the initial merged version number carries three types of information in the same field: draft number, role tag, and editing duration, to distinguish the source differences between the mother's account reply topic and the father's account reply topic in the home-school communication terminal.

[0069] Step S102: Evaluate the temporal compactness between the initial merge version number and the read confirmation timestamp, identify the parts of the draft content where there is a reply conflict or inaccuracy between the two parents' drafts, and extract the message status convergence position where the read aggregation lag is based on the read confirmation list of all guardians, the offline draft existence flag and its last edit time.

[0070] For the initial merged version number and read confirmation timestamp, their order of occurrence is arranged according to the event timeline of the home-school communication terminal. The time interval between the version number writing time and the read confirmation timestamp is calculated to obtain the temporal compactness metric. The reply landing points are located by segmenting the offline texts of the two parents. The reply landing points are the corresponding sentences and paragraphs written by the two drafts on the same topic under the same comment item. The conflicting paragraphs are identified by comparing the expressions of the two drafts at the same reply landing point, and the draft difference items carrying the conflicting paragraphs and the temporal compactness metric are obtained. The merge operation log record timestamp in the system database is used as the version number writing time. Starting from the draft difference entries, the guardianship list recorded in the home-school communication terminal is retrieved. The guardianship list registers the read confirmation entries of two parent accounts. For each parent account, the draft flag value in the draft cache is read. The draft flag value indicates whether the offline text is still in the pending submission state. Together with the last edit time and the time sequence compactness metric, it is included in the aggregation judgment field. The read aggregation lag is calculated according to the misalignment between the read confirmation timestamp and the last edit time on the event timeline. The node corresponding to the lag on the event timeline is determined as the message status convergence position.

[0071] In one embodiment, the event timeline is deployed in the server-side log area of ​​the home-school communication terminal, and version number write events and read confirmation events are concatenated in chronological order of event occurrence. When the mother's account and the father's account respectively complete the offline text version field writing and the viewing of the comment item, the event timeline records the timestamps of the two types of events in sequence.

[0072] Specifically, the time-compression metric is calculated based on the difference between the version number write time and the read confirmation timestamp. Let T1 be the version number write time for the mother account and T2 be the read confirmation timestamp, and T3 be the version number write time for the father account and T4 be the read confirmation timestamp. Then, the time interval on the mother's side is the absolute value of the difference between T2 and T1, and the time interval on the father's side is the absolute value of the difference between T4 and T3. The time-compression metric is the sum of the time intervals on both sides. A smaller difference indicates that the version number generation and the read confirmation are closer on the event timeline, while a larger difference indicates that the two events are further apart.

[0073] It should be noted that the location of the response depends on the segmentation of the offline text. The parent-teacher communication terminal segments each parent's offline text into several segments according to Chinese punctuation marks, and labels each segment with an issue category from the list of issues attached to the comment item. The issue list is attached by the teacher when the comment item is distributed and covers several aspects of the student's performance.

[0074] Specifically, for identifying conflicting paragraphs, sentences with the same issue-related tags in the offline text from the mother's account and the father's account are paired to form response endpoint pairs. Within each response endpoint pair, the two sentences are compared based on word overlap and sentiment value. If the attitudes or factual statements expressed by the two sentences point to different sides, the response endpoint pair is marked as contradictory, and the corresponding two sentences are included in the conflicting paragraph set. The draft difference entries are concatenated with the conflicting paragraph set and the temporal compactness metric to form a difference description record for the comment entries. Furthermore, the guardianship list is stored in the parent's account file on the home-school communication terminal, registering read confirmation entries under the comment entries for both the mother's and father's accounts, with each read confirmation entry accompanied by a corresponding read confirmation timestamp.

[0075] In one possible implementation, the draft flag value is written to the draft cache of the parent-teacher communication terminal. The value includes two categories: pending submission and withdrawn submission. The former indicates that the offline text is still in editing but has not yet been submitted, while the latter indicates that the offline text has been actively abandoned by the parent. The draft flag value under each parent's account is read and, along with the last edit time, filled into the aggregation judgment field. This aggregation judgment field concatenates four types of information: the read confirmation timestamp of the monitoring list, the draft flag value, the last edit time, and the aforementioned time-series compactness metric.

[0076] Understandably, the read aggregation lag is calculated based on the misalignment between the read confirmation timestamp and the last edit time on the event timeline in the aggregation judgment field. The misalignment is the directed difference obtained by subtracting the read confirmation timestamp from the last edit time. A positive difference indicates that the parent was still editing offline text after reading, while a negative difference indicates that the parent only completed the read action after editing. The points where the directed differences for each parent occur are scanned along the event timeline, and the point with the largest absolute value of the difference is taken as the node where the read aggregation lag occurs. This node is registered as the message status convergence position, which carries the temporal misalignment attribution point between the read actions and offline editing actions of the two accounts under the comment item.

[0077] Step S103: Adjust the triggering conditions for read aggregation judgment based on the message status of the lag. Filter out the paragraphs of offline edited replies belonging to the dominant account in the conflict of parent role importance identification from the online login records. Combine the read confirmation timestamp to verify whether the draft content contains unsynchronized parent annotation text. Integrate the message version number issued by the home-school communication system to obtain a unified merged version view.

[0078] For the time-series misalignment attribution point carried by the message status convergence position, the original set of trigger conditions for read aggregation judgment in the home-school communication terminal is retrieved. The set of trigger conditions includes two types of configuration items: the threshold for the number of read accounts and the span of the read time window. According to the deviation direction of the time-series misalignment attribution point on the event time axis, the threshold for the number of read accounts and the span of the read time window are offset and corrected to obtain the read aggregation judgment trigger conditions that match the message status convergence position. The session activity count and login terminal type of the two parent accounts after the comment item is issued are read from the online login record. The session activity count is the cumulative value of the number of page dwells within the login session. The activity counts of the two parent accounts are compared with the role importance ranking attached to the role tag value in the dual account binding relationship. The account with the higher ranking and the superior activity count is identified as the dominant account. In the set of conflict paragraphs registered in the draft difference item, the paragraph copy belonging to the offline editing reply is retrieved according to the account identifier of the dominant account to obtain the paragraph item under the dominant account name. For the offline text corresponding to the paragraph entry, the parent annotation text is segmented in the text stream according to the parent annotation prefix symbol, which is the annotation start symbol preset on the parent input terminal; the parent annotation text is verified to see if it falls after the read confirmation timestamp by combining the read confirmation timestamp of the master account and the last edit time, and parent annotation text that is later than the read confirmation timestamp is registered with an unsynchronized mark; the message version number sent by the home-school communication terminal is retrieved, and a unified merged version view is formed by concatenating the fields of message version number, initial merged version number, paragraph entry, and unsynchronized mark in the order of the fields.

[0079] In one embodiment, the message version number Vm sent by the home-school communication terminal is retrieved, and a unified merged version view is formed according to the following concatenation rules: First, the merged version number Vf = Vm + Vi is calculated, where Vi is the initial merged version number of S101; then, Vm, Vf, the belonging paragraph entry, and the unsynchronized identifier are concatenated in order, connected using a vertical bar separator, and the output format is as follows: Vm|Vf|paragraph entry|identifier. The set of triggering conditions for the read aggregation judgment is pre-stored in the judgment rule library on the home-school communication terminal service side. The judgment rule library registers two types of configuration items: the threshold for the number of read accounts and the span of the read time window. The threshold for the number of read accounts refers to the number of parent accounts that need to complete the read stamp writing under the same comment entry, and the span of the read time window refers to the allowable read delay duration from the time the comment entry is sent.

[0080] It should be noted that the deviation direction of the time sequence misalignment attribution point on the event timeline has two orientations: one orientation is that the read confirmation timestamp is earlier than the last edit time, and the other orientation is that the read confirmation timestamp is later than the last edit time.

[0081] Specifically, for the offset correction process, asymmetric adjustments are made according to the deviation direction of the time-series misalignment attribution point.

[0082] In one possible implementation, if the time-series misalignment point exhibits an advanced read confirmation timestamp orientation, the read time window span is extended backward by a compensation period to accommodate offline text still being edited by the parent account, while maintaining the read account threshold at the value where both accounts have read the text; if the time-series misalignment point exhibits a delayed read confirmation timestamp orientation, the read account threshold is broadened from the value where both accounts have read the text to the value where a single account has read the text and triggers the event, while simultaneously tightening the read time window span forward. The compensation period is determined based on the offset of the message status convergence position relative to the time of comment item issuance on the event timeline; the larger the offset, the longer the compensation period. After completing the above asymmetric adjustment, a read aggregation determination trigger condition matching the message status convergence position is obtained. Furthermore, the online login record is carried in the conversation ledger of the home-school communication terminal, and the conversation ledger records the login conversation identifier, login time, logout time, login terminal type, and the number of page dwells within the conversation.

[0083] Specifically, the session activity count is the cumulative number of page dwells within all login sessions initiated by the parent account after the comment item is issued. The login terminal type includes both mobile and desktop values. Session activity counts for the mother and father accounts are retrieved from the session log, filtered by parent account identifier and the time the comment item was issued. The importance ranking of roles is pre-stored in a ranking field attached to the role marker value within the dual-account binding relationship. The ranking field value is determined based on the priority sequence of legal guardians registered in the student's academic record; for example, the ranking field corresponding to the parent account registered as the head of household on the first page of the household registration book, or the guardian frequently responsible for the student's education, is ranked higher. During the comparison process, the conversation activity counts of parent accounts with higher rankings are compared item by item with those with lower rankings. If the conversation activity count of the higher-ranked account is also higher than that of the lower-ranked account, then the higher-ranked account is identified as the dominant account. If the conversation activity count of the higher-ranked account is lower than that of the lower-ranked account, then the higher-ranked account is still identified as the dominant account according to the principle of prioritizing the importance of the role, and the dominant account identifier is obtained.

[0084] In one embodiment, the ownership of the set of conflicting paragraphs in the draft difference entries is determined by the dominant account identifier. Each sentence in the set of conflicting paragraphs is accompanied by a written account identifier field. The corresponding sentences are filtered out according to the condition that the written account identifier field is equal to the dominant account identifier, so as to obtain the ownership paragraph entries under the dominant account name.

[0085] It is understandable that the parent annotation prefix symbol is a preset annotation start symbol on the parent input terminal, which serves to distinguish the main text reply from the parent annotation text in the offline text stream.

[0086] For example, the parent input terminal provides a comment insertion button in the reply editing interface under the comment item. After pressing the comment insertion button, the characters entered are written to the draft buffer as a fixed symbol string opened with double hash marks or square brackets. The positions of the prefix symbols are scanned character by character along the offline text stream, and the character sequence from the position of the prefix symbol to the next paragraph separator is read as the parent comment text, along with the writing time corresponding to the parent comment text.

[0087] Specifically, regarding the verification process of parent annotation text, the read confirmation timestamp of the primary account is denoted as Ta, and the writing time of the parent annotation text is denoted as Tb. The order of Tb and Ta is compared. If Tb is later than Ta, the parent annotation text is written to the draft cache only after the primary account completes the read action, and is not fed back to the home-school communication server side through the synchronization channel after the comment item is issued. The parent annotation text is registered as unsynchronized. If Tb is earlier than Ta, the parent annotation text already exists before the read action, and the value of the unsynchronized flag is left blank. The unsynchronized flag includes the character sequence of the parent annotation text and the writing time. Further, the message version number attached when the comment item is issued by the home-school communication terminal is retrieved. The message version number is assigned by the server side in ascending order according to the issuance sequence. A unified merged version view is formed by concatenating the fields of message version number, initial merged version number, belonging paragraph entry, and unsynchronized flag in that order. This unified merged version view consists of four fields that sequentially contain the service-side message version number, the initial merged version number carrying the difference in response sources between the two accounts, the belonging paragraph entry under the dominant account name, and an unsynchronized flag indicating the write time. This unified merged version view carries the version evolution of the comment entries from teacher issuance to offline editing and response by both accounts, as well as the attribution point of unsynchronized parent annotation text, allowing the home-school communication terminal to make a unified version judgment in cases where the response sources from the two accounts are inconsistent.

[0088] Another way to determine the unified merged version view is to retrieve the comparison records of offline edited reply paragraphs and online read confirmation timestamps, extract the main reply entries of the dominant account in the merged version view, identify the parent annotation text submitted by the other parent account and mark the unsynchronized status, and obtain a unified merged version view that includes the source markers of the replies from both accounts, message version number changes and synchronization status flags.

[0089] For the offline edited reply paragraphs and online read confirmation timestamps stored on the home-school communication terminal, the paragraph writing time is read from the metadata of the offline edited reply paragraphs. Records are matched according to two types of index items: comment item number and parent account identifier, to obtain a comparison record with parallel fields carrying paragraph writing time and read confirmation timestamp. The paragraph copy to which the dominant account identifier belongs is read from the comparison record. According to the reply topic of the paragraph copy, the sentence links connected in the order of the comment item topics are selected in the merged version view as the main reply item.

[0090] In one embodiment, the paragraph copy to which the dominant account identifier belongs is read from the comparison record. The TF-IDF algorithm is used to calculate the similarity between the paragraph copy's reply topic and the comment item's issue. The input is the paragraph text and issue keywords. The output is a similarity score. If the score is greater than 0.7, it is a match. The issue position is generated by sorting the matched issues in ascending order of the comment item number. In the merged version view, the sentence links connected along the issue position are selected as the main reply items. After filtering out entries corresponding to the primary account identifier from the comparison records, a copy of the paragraph to which the secondary account identifier belongs is retained. The secondary account is another parent account that is not the primary account within the dual account binding relationship. Parent annotation text is extracted from the offline text of the secondary account according to the parent annotation prefix symbol. The synchronization status of the parent annotation text is verified according to the order of the secondary account's read confirmation timestamp and the paragraph writing time. Parent annotation text that is later than the secondary account's read confirmation timestamp is registered as a synchronization status flag and taken as an unsynchronized value. Dual account reply source tags are attached to the reply main line entries according to the two types of sources: primary account and secondary account. Then, the change record of the message version number issued by the home-school communication terminal on the old and new values ​​is written to the version field of the merged version view to obtain a unified merged version view that connects the dual account reply source tags, message version number changes and synchronization status flags.

[0091] For offline edited reply paragraphs stored on the parent-teacher communication platform, each paragraph copy is accompanied by a metadata field. This metadata field registers the paragraph's writing time, the corresponding comment item number, the writing account identifier, and the reply topic. The paragraph's writing time is the value recorded on the parent-teacher communication platform when the parent's input device fetches the paragraph copy from the draft cache.

[0092] Specifically, the paragraph writing time is read from the metadata field, and the online read confirmation timestamp is read from the reading log of the home-school communication terminal; all paragraph copies and read confirmation entries under the same comment entry are matched by the comment entry number; and the paragraph copy is matched with the read confirmation timestamp of the parent account as the secondary index item to obtain a comparison record. Each row of the comparison record carries four types of fields: comment entry number, parent account identifier, paragraph writing time, and read confirmation timestamp.

[0093] Specifically, the paragraph copies belonging to the leading account are retrieved from the comparison records by the leading account identifier, which comes from the leading account identifier registered in the aforementioned merged version view. Within the merged version view, the topic attribution field of the reply to the paragraph copy of the leading account is matched with the topic position in the topic list under the comment item. The paragraph copies of the leading account are then linked one by one along the topic position from small to large, resulting in a sentence link connected in the order of the topic of the comment item. This sentence link serves as the main reply line item under the leading account name in the merged version view, carrying the continuous expression of the leading account under the comment item.

[0094] In one possible implementation, the comparison records are filtered out according to the dominant account identifier, and the parent account identifier to which the remaining entries belong is the secondary account identifier. The secondary account is another parent account that is not the dominant account in the dual account binding relationship.

[0095] It should be noted that the parent annotation prefix symbol is scanned character by character along the offline text stream under the sub-account name. The character sequence from the prefix symbol position to the next paragraph separator is taken as the parent annotation text of the sub-account, along with the corresponding write time of the parent annotation text. The read confirmation timestamp of the sub-account is denoted as Tc, and the write time of the parent annotation text of the sub-account is denoted as Td. The order of Td and Tc is compared. If Td is later than Tc, the parent annotation text falls into the draft buffer after the sub-account completes the read action, and is not transmitted back to the server side through the synchronization channel of the home-school communication terminal. The synchronization status flag attached to the parent annotation text is registered as unsynchronized. If Td is earlier than or equal to Tc, the synchronization status flag is registered as synchronized. Furthermore, a dual-account reply source mark is attached to the aforementioned reply main line entry. The dual-account reply source mark has two types of values: the main account value and the sub-account value. These are attached to the paragraph copy of the main account and the parent annotation text of the sub-account, respectively.

[0096] It is understandable that the message version number change record records the migration trajectory of the message version number attached to the comment item issued by the home-school communication terminal between the old and new values. Each time the service side redistributes the message version number value attached to the comment item, the old value and the new value are written side by side into the version field of the merged version view. The unified merged version view is composed of three types of fields: dual account reply source marker, message version number change, and synchronization status flag, connected together.

[0097] Step S104: Identify the remaining branch versions left over from the merged logical contradiction entries in the unified merged version view, evaluate the decline of the remaining branch version number, adjust the offset of the parent role importance between the two parents, and verify the read coverage result of the parent end by combining the coverage of the read confirmation timestamps of the two parents.

[0098] From the unified merged version view, scan the dual-account reply source markers and the topic positions attached to the reply main line entries by field position. For entries where dual-account reply source markers coexist under the same topic position and the statements within the reply main line entries point to mutually exclusive terms, register them as merged logical contradiction entries. The process of determining mutual exclusivity is as follows: input two statement texts, calculate the similarity S, and S less than 0.5 is considered as exclusivity, where S=(A·B) / (|A||B|), and A and B are the TF-IDF vectors of the statements. Extract the version branch branch points that are not included in the main line concatenation from the message version number change records attached to the merged logical contradiction entries to obtain the remaining branch versions that remain at the edge of the merged version view. For the version number value corresponding to the remaining branch version, the difference magnitude of the version branch trajectory is compared with the migration trajectory of the old and new values ​​in the message version number change record. The difference magnitude is the absolute value of the difference between the high position of the main line and the low position of the branch during the version number migration process. The difference magnitude is divided into two levels, large difference and small difference, according to a preset threshold, to obtain the difference magnitude evaluation value of the carrying level identifier. Starting from the assessed value of the decline, the dual-account weight value attached to the importance ranking of the roles within the dual-account binding relationship is retrieved. The dual-account weight value is determined according to the importance ranking of the roles based on a pre-registered weight lookup table. The dual-account weight value is adjusted between the two parents according to the tier identifier, so that the dual-account weight value of the secondary account increases under a large decline tier, and maintains the original tier value under a small decline tier. The coverage interval endpoints are read from the read confirmation timestamps of the two parents. The coverage interval endpoints are taken as the start and end times of the read confirmation timestamps. The coverage interval endpoints of the two parents are weighted and merged according to the adjusted dual-account weight values ​​to verify the read coverage result of the parents.

[0099] In one embodiment, the unified merged version view is divided into four categories based on field positions: dual-account reply source marker field position, message version number change field position, synchronization status flag field position, and reply mainline entry field position. The entries in the merged version view are scanned one by one along the field positions, and the entries are grouped and aggregated according to the topic position value.

[0100] It should be noted that the issue ranking value is contained in the metadata attached to the main reply entry. When each paragraph copy is attached to the merged version view, its issue ranking is written according to the order number of the issue in the comment entry's issue list. Under each issue ranking, the attribution value of the dual-account reply source markers (mother account and father account) is registered.

[0101] Specifically, the registration process for merging logically contradictory entries relies on a dual-judgment approach. Under the same issue position, if the source marker field of both accounts' responses simultaneously carries values ​​from both the mother's and father's accounts, and the sentiment values ​​or factual statements attached to the corresponding two paragraph copies point to mutually exclusive sides, then the two paragraph copies under that issue position are jointly registered as merged logically contradictory entries. The sentiment values ​​are derived from the markers already attached during the aforementioned conflict paragraph identification process, and the factual statement values ​​are obtained by the text comparison interface of the home-school communication terminal through a positive-negative comparison of the keyword sets of the two paragraph copies.

[0102] In one possible implementation, for the "homework completion" issue position under a comment item, if the paragraph copy from the mother's account expresses approval and the paragraph copy from the father's account expresses disapproval, then the two paragraph copies under that issue position are registered as merged logically contradictory entries. Further, the version number migration trajectory is read from the message version number change record attached to the merged logically contradictory entry, and the migration trajectory is concatenated with the previous old and new values ​​in chronological order.

[0103] Specifically, by comparing the high and low digits of two adjacent version number values ​​along the migration trajectory, any version number node that branches off from the main path is registered as a version branch fork point.

[0104] In one embodiment, the main line concatenation path is taken from the sequence of version number nodes that have been included in the main line of response in the merged version view. Any version number node that does not appear in the sequence falls into the set of remaining branch versions, thereby extracting the remaining branch versions that are stuck at the edge of the merged version view.

[0105] It is understood that the downlink magnitude calculation object of the version rollback trajectory is the version number value corresponding to the remaining branch versions. Let the higher-order version number value at a certain moment on the migration trajectory be denoted as Vh, and the immediately following lower-order version number value be denoted as Vl. Then the downlink magnitude at that moment is the absolute value of the difference between Vh and Vl. By accumulating the downlink magnitude values ​​at each moment along the migration trajectory, the total downlink magnitude value corresponding to the remaining branch versions is obtained.

[0106] In one embodiment, the total downlink amplitude is categorized into two levels—a large drop level and a small drop level—based on a preset threshold Th. Values ​​with a total downlink amplitude greater than Th are classified as large drop levels, and vice versa, resulting in an assessment value for the drop amplitude of the carrying level. The preset threshold Th is pre-stored in the decision rule base of the home-school communication terminal service side.

[0107] It should be noted that the weight values ​​of the dual accounts are determined according to the importance of the roles and are based on a pre-registered weight lookup table.

[0108] Specifically, the weighted reference table is registered in the parent attribute files on the home-school communication terminal service side. Based on the priority order of legal guardians in the student record, the weight value corresponding to the higher-ranking parent is taken as the larger value, and the weight value corresponding to the lower-ranking parent is taken as the smaller value. The sum of the weight values ​​of the two parents is normalized to a single unit. Furthermore, regarding the adjustment process of offset elements, the weight values ​​of the two accounts are asymmetrically redistributed between the two parents according to the aforementioned rank identifier.

[0109] In one possible implementation, if the gear indicator is a significant drop gear, the weight values ​​of the secondary account are increased by a preset increase, and the weight value of the primary account is correspondingly compressed according to the constraint that the sum of the weight values ​​is normalized to a unit value, so that the secondary account obtains a higher reflective component in the read coverage results; if the gear indicator is a slight drop gear, the weight values ​​of the dual accounts are maintained at their original values, and no redistribution is made. The preset increase is determined by the proportion of the total downlink amplitude of the significant drop gear relative to a preset threshold Th; the larger the proportion, the larger the increase. After completing the above asymmetric redistribution, the adjusted weight values ​​of the dual accounts are obtained.

[0110] In one embodiment, the coverage interval endpoints are read from the read confirmation timestamps of each of the two parents. The coverage interval endpoints are the start and end times of the read confirmation timestamps. The start time corresponds to the time when the parent's account first writes a read confirmation, and the end time corresponds to the time when the parent's account last writes a read confirmation. The coverage interval endpoints of the two parents are weighted and merged according to the adjusted dual-account weight values. The weighted merge is the sum of the products of each parent's start time and corresponding weight value, and the sum of the products of the end time and corresponding weight value is the merge end time. The time period defined by the merge start time and merge end time is used as the read coverage result on the parent's end. The read coverage result on the parent's end carries the weighted aggregated time period of the dual-account read confirmation timestamps under the comment item, reflecting the overall read time period attribution for the two parents in the case of logically contradictory items during merging.

[0111] Step S105: Evaluate the synchronization tightness between the read coverage results and the latest read confirmation timestamp, analyze whether the coverage results meet the consistency requirements of parent read aggregation, and output the parent read aggregation curve.

[0112] For the time period defined by the start and end times of merging in the read coverage results on the parent's end, all read stamps for each parent's comments are collected from the reading flow of the home-school communication terminal according to the parent account identifier and arranged in chronological order to form a read stamp sequence. The last item in the read stamp sequence is taken as the latest stamp, which carries the time value of the last confirmation action of the parent account under the comment item. The distance between the latest stamp and the end time of merging on the event time axis is calculated to obtain a compactness metric. The time interval between two adjacent read stamps is extracted from the read stamp sequence to form the internal gap position of the coverage period, and the maximum value of these intervals is calculated as the gap position width. Starting from the compactness metric and the internal gap position of the coverage period, the density of the read coverage results in relation to the issue position of the comment item is verified according to a pre-registered consistency threshold. The consistency threshold includes two configuration items: an upper limit for the compactness metric and an upper limit for the gap position width. If the compactness metric is lower than the upper limit and the internal gap position width is lower than the upper limit, an achievement marker is registered under the issue position to which the read coverage result belongs, indicating an achieved value; otherwise, it is registered as an unachieved value. The issue position refers to the sequential position of the comment item in the communication topic, such as the upper limit of the compactness metric. The value is 24 hours, and the upper limit of the gap position width is 12 hours. The endpoints of the coverage period, the internal gap position and the achievement mark in the read coverage results are concatenated along the event timeline according to the issue position to obtain the parent read aggregation curve. The specific concatenation method is as follows: First, sort the results according to the issue position, and then connect the endpoints of each position, such as the start time t1, the end time t2, the gap position, such as the interval d1=5 hours and the achievement mark, such as 1 to indicate that it has been achieved, linearly along the timeline. For example, the input sequence is [t1, t2, d1, 1], and the output is the curve segment from t1 to t2 labeled with the gap d1 and the mark 1.

[0113] In one embodiment, the home-school communication terminal's reading log collects all read stamps written by each parent after a comment item is issued, using two types of indexes: parent account identifier and comment item number. Each read stamp entry records the parent account identifier, comment item number, viewing time, and session identifier.

[0114] Specifically, the system retrieves read stamp entries belonging to the mother's and father's accounts from the reading log by combining the parent's account identifier and the comment entry number. These read stamp entries are then sorted in ascending order of viewing time, forming separate read stamp sequences for the mother's and father's accounts. The last entry from each sequence is selected, and the entry with the later viewing time is designated as the latest stamp. This latest stamp carries the time value of the parent's last confirmation action for the comment entry.

[0115] It should be noted that the compactness metric is calculated based on the interval between the latest stamp and the merging end time. Let the latest stamp time be denoted as Tn, and the merging end time in the parent's read coverage result be denoted as Te. Then, the compactness metric is the absolute value of the difference between Tn and Te. The smaller the difference, the closer the parent's last confirmation action is to the end of the coverage period; the larger the difference, the farther the last confirmation action is from the end of the coverage period.

[0116] In one possible implementation, for a scenario where both accounts have written several read stamps under a comment entry, the compactness metric is calculated by the judgment module on the home-school communication terminal server side according to the above difference and filled into the compactness field of the read coverage result.

[0117] Specifically, two adjacent read stamps are taken out one by one from the two read stamp sequences in chronological order of viewing time. The viewing time of the latter read stamp is subtracted from the viewing time of the former read stamp to obtain the time interval value. All time interval values ​​are used as the internal gap positions of the coverage period.

[0118] It is understood that the consistency threshold value is pre-registered in the judgment rule base of the home-school communication terminal service side, including two types of configuration items: the upper limit value of compactness measurement and the upper limit value of gap position width.

[0119] In one embodiment, the upper limit of the compactness metric is determined by the urgency level of the issue attached to the comment item when it is issued; the higher the urgency level, the smaller the upper limit of the compactness metric. The upper limit of the gap position width is determined by the historical response pace of the parent's account on the school-home communication terminal. For each internal gap position, the gap position width is compared with the upper limit of the gap position width, and the compactness metric is compared with the upper limit of the compactness metric. If the compactness metric is lower than the upper limit of the compactness metric and the width of all internal gap positions is lower than the upper limit of the gap position width, then an achievement mark is registered as an achieved value under the issue position to which the read coverage result belongs; if any item exceeds the corresponding upper limit value, then an achievement mark is registered as an unachieved value. Further, the coverage period endpoints, internal gap positions, and achievement marks in the read coverage result are concatenated along the event timeline in chronological order of issue position, and the concatenated result is the parent read aggregation curve. The parent read aggregation curve presents the extension of the coverage period, the distribution of gap positions, and the value distribution of achievement marks segment by segment along the issue position axis.

[0120] It is understandable that the parent read aggregation curve carries the dense evolution trajectory of the dual account read confirmation actions under the comment items as the issue position progresses, reflecting the trend of the two parents' read aggregation for each issue position.

[0121] Another way to determine the parent read aggregation curve is to extract the coverage period markers and the latest read confirmation timestamps of the two parents from the read coverage results, analyze the synchronization offset difference between the confirmation times of the two parents, identify the gap positions where the coverage period does not meet the aggregation consistency requirements, and obtain the parent read aggregation curve.

[0122] Based on the read coverage results carried by the parent read aggregation curve, the coverage period markers under the mother's account and the father's account are extracted according to the parent account identifier. The coverage period markers record the start and end times of each parent's comment item. The last item of each of the two read stamp sequences is retrieved as the latest read confirmation timestamp of the mother's account and the latest read confirmation timestamp of the father's account. The absolute value of the difference between the two latest read confirmation timestamps is determined as the synchronization offset difference. According to the preset difference threshold of 5 minutes, the synchronization offset difference is divided into two difference levels: close and far. The threshold is calculated based on the empirical statistics of typical parent reading response time as T=avg(R)-min(R), where T is the threshold, avg(R) is the average response time, and min(R) is the minimum response time. If the difference is less than or equal to T, it is the close level; otherwise, it is the far level. For the gap position associated with the synchronization offset drop, the coverage period markers of the mother's account and father's account are compared along the event timeline. A single-point comparison is made between the gap positions formed by two adjacent read stamps in the read stamp sequence of each parent. The position where the gap position width exceeds the pre-registered upper limit value of the gap position width is registered as the gap position that has not achieved the aggregation consistency requirement. The coverage period endpoints of the two parents, the synchronization offset drop and the gap position that has not achieved the aggregation consistency requirement are concatenated according to the issue position. An aggregation consistency mark is attached to the corresponding issue position on the concatenation result to obtain the parent read aggregation curve that carries the coverage period, offset drop and aggregation consistency mark of the two people.

[0123] In one embodiment, the coverage period markers under the mother's account name and the father's account name are extracted from the read coverage results according to the parent's account identifier. The coverage period marker consists of two time values, namely the start time when the parent first writes the read stamp under the comment item and the end time when the parent last writes the read stamp.

[0124] Specifically, the last entry in each of the two read stamp sequences formed from the reading logs on the home-school communication terminal is taken. The viewing time of the last entry in the mother's account is determined as the latest read confirmation timestamp for the mother's account, and the viewing time of the last entry in the father's account is determined as the latest read confirmation timestamp for the father's account.

[0125] It should be noted that the synchronization offset difference is determined by the absolute value of the difference between the two latest read confirmation timestamps. Let Tm be the latest read confirmation timestamp of the mother's account and Tf be the latest read confirmation timestamp of the father's account, then the synchronization offset difference is the absolute value of the difference between Tm and Tf.

[0126] In one possible implementation, a threshold value Tg is pre-registered in the rule base of the home-school communication server. The system is then categorized into different tiers based on the relationship between the synchronization offset and the threshold value Tg: if the synchronization offset does not exceed the threshold value Tg, the children are placed in the "closely adjacent" tier, indicating that the final confirmation actions of the two parents are close to each other on the event timeline; if the synchronization offset exceeds the threshold value Tg, the children are placed in the "staggered" tier, indicating that the final confirmation actions of the two parents are staggered. The threshold value Tg is pre-determined based on the urgency level of the issue attached to the comment item; the higher the urgency level, the smaller the threshold value Tg.

[0127] It is understood that the upper limit value of the gap position width is taken from the upper limit value configuration item of the gap position width in the aforementioned consistency threshold value, and is registered in the judgment rule library of the home-school communication terminal service side.

[0128] Specifically, for each parent's read stamp sequence, two adjacent read stamps are taken out in order of viewing time. The viewing time of the next read stamp is subtracted from the viewing time of the previous read stamp to obtain the time interval value. The time interval value is used as the gap position width under the parent's name.

[0129] In one embodiment, a single-point comparison is performed on the width of each gap position in the mother's account against the upper limit of the gap position width. Gaps exceeding the upper limit of the gap position width are registered as gap positions under the mother's account that have not met the aggregation consistency requirement. The same comparison is performed on the width of each gap position in the father's account to obtain gap positions under the father's account that have not met the aggregation consistency requirement. The gap positions under both parents that have not met the aggregation consistency requirement are jointly filled into the gap field of the aggregation curve. Further, for the issue positions in the issue list under the comment item, the coverage time endpoints, synchronization offset differences, and gap positions that have not met the aggregation consistency requirement of the two parents are concatenated in order of issue position. The concatenation result is expanded segment by segment along the issue position axis. An aggregation consistency mark is attached to the concatenation node of each issue position. The aggregation consistency mark value includes two categories: achieved value and unachieved value. The value is jointly verified based on the verification results of the adjacent position, the separated position, and the gap position width under the issue position.

[0130] Understandably, the resulting concatenated records serve as the parent read aggregation curve, carrying the coverage time period, offset difference, and aggregation consistency markers for both individuals. Along the issue position axis, it presents the gradual evolution of the synchronization and coverage completeness of the dual account read confirmation actions.

[0131] Step S106: Based on the complete parent read aggregation curve, identify the long-term evolution trajectory of parents' independent reply drafts, determine the optimization path for merging delays, and simultaneously update the judgment conditions for reply conflict inaccuracy, and draw the parent read aggregation conclusion.

[0132] For the complete parent read aggregation curve, extract the draft number and editing duration fields of each parent's offline edited reply along the topic position axis. Concatenate these fields according to the order in which the draft numbers were written to the home-school communication terminal to form a draft item timeline chain. Divide the draft item timeline chain into long-term evolution segments based on increasing and decreasing editing duration segments. Register the transition nodes between adjacent long-term evolution segments as node revision positions to obtain the evolution trajectory of the parent's independent reply drafts carrying the draft item timeline chain and node revision positions. Extend this evolution trajectory to the dual-account bound history records the writing time of each role tag value and role importance position. Compare the migration trend of the position field values ​​one by one according to the writing time order to identify entries where the position field value falls from a high position to a low position, registering them as rollback trigger positions. Concatenate these rollback trigger positions to form a change context entry for the parent's role importance. Optionally, the change context entry is a time-sorted position change sequence data structure derived from the history log file. Align the changed context entries with the parent read aggregation curve on the event timeline, and use the continuous segment with the achieved value as the steady-state control baseline. For the segment with the unachieved value outside the steady-state control baseline, select two types of entries that both fall within the segment from the node revision position and the rollback trigger position as adjustment nodes for merging delay. Concatenate the adjustment nodes to form the optimized path for merging delay. Optionally, the node revision position originates from the draft editing evolution, and the rollback trigger position originates from the historical change of role position. Collect the measured value of the synchronization offset drop from the adjustment node and the character span of the conflicting sentence segment in the conflict paragraph as the expression conflict amplitude. Replace the original values ​​of the aforementioned consistency threshold and drop threshold with the measured value, refresh the judgment condition for replying to the conflict inaccuracy, and obtain the parent read aggregation conclusion that carries the evolution trajectory, changed context entries, and refreshed judgment conditions.

[0133] In one embodiment, each node on the parent read aggregation curve is traversed along the issue position axis, and for each node, two fields are extracted: the draft number and the editing duration of the offline edited reply under the parent's name for the comment item to which the node belongs. The draft number is taken from the incrementing number value assigned by the draft cache when it is written to disk, and the editing duration is taken from the difference between the start time and the last time of editing.

[0134] Specifically, following the chronological order of the comments items, the draft numbers of the two parents under each comment item are strung together according to the position of the time they are written into the parent-teacher communication terminal to form a draft item chronological chain, with each link including the editing time value of that comment item.

[0135] It should be noted that the division of the long-term evolution segment is based on the trend of editing time along the time sequence chain of draft entries. By comparing the difference in editing time between adjacent links along the chain, if the difference in editing time for several consecutive links is a positive value, then the consecutive segment is registered as an increasing segment, indicating that the time parents spend on replying and editing under this time sequence is continuously increasing; if the difference in editing time for several consecutive links is a negative value, then the consecutive segment is registered as a decreasing segment, indicating that the time parents spend on replying and editing under this time sequence is continuously decreasing.

[0136] In one possible implementation, the junction between adjacent increasing and decreasing paragraphs is registered as a node revision bit, which includes a chain number and the corresponding comment item number. The node revision bit represents the inflection point where parental editing input shifts from expansion to contraction or from contraction to expansion. After completing the above concatenation, the evolution trajectory of the parent's independent response draft, carrying the draft item sequence chain and node revision bits, is obtained. Furthermore, the historical record of the dual-account binding is stored in the version archive branch of the account binding table on the home-school communication terminal service side.

[0137] Specifically, the version archive branch of the account binding table records each revision of the role flag value and role importance ranking value in chronological order of writing time. Following the chronological order of writing time, the ranking field value is compared with the previous writing entry. If the current value is lower than the previous value, the writing entry is registered as a rollback trigger bit, which includes the account identifier and the writing time.

[0138] In one embodiment, for a scenario where the ranking field in a student's academic record is rewritten due to a change in the priority order of legal guardians, the write entry corresponding to the parent account with the lower ranking after the rewrite falls into the rollback trigger bit set. The link formed by concatenating the rollback trigger bits serves as the change path entry for the importance of the parent's role.

[0139] It is understandable that the change context entries and the parent read aggregation curve are aligned on the event timeline. The alignment method is to project the write timelines of both in parallel, so that each back trigger bit of the change context entry is paired with the issue position node at the same time on the aggregation curve.

[0140] Specifically, the aggregation consistency marker values ​​are scanned along the aligned event timeline. Any segment where the aggregation consistency marker has continuously reached a value is registered as a steady-state control baseline segment. The steady-state control baseline serves as a reference for the stable state of read aggregation on the parent's end, carrying the set of time periods where the read confirmation actions of both accounts under the comment item are stably aligned.

[0141] In one possible implementation, for the segment outside the steady-state baseline where the aggregation consistency marker has not reached a value, the node revision bit and rollback trigger bit that simultaneously fall within the segment are retrieved along the aligned event timeline. Items where both types of entries are located within the segment are used as adjustment nodes for merging delay. The adjustment nodes carry the correlation points where the draft editing inflection point and the role importance ranking fall back concurrently within the same time period. The adjustment nodes are strung together along the event timeline to form an optimized path for merging delay.

[0142] It should be noted that, for each adjustment node on the optimization path, the difference between the latest read confirmation timestamps of the two accounts is taken from the corresponding position on the event timeline as the measured value of the synchronization offset difference, denoted as Dn; the character span of the conflicting sentence segment is taken from the corresponding position in the conflicting segment set as the measured value of the conflict amplitude, denoted as Wn, where the character span is determined by the difference between the starting and ending character positions of the conflict. The Dn and Wn values ​​at all adjustment nodes are collected cumulatively along the optimization path. Further, for the refresh process, the original value of the aforementioned offset threshold Tg is replaced with the Dn value collected at the adjustment node, and the original value of the upper limit of the gap width in the aforementioned consistency threshold is replaced with the Wn value collected at the adjustment node, thus obtaining the judgment condition for the refreshed response conflict inaccuracy.

[0143] Specifically, the updated judgment criteria, the evolution of parents' independent draft replies, and the changes in the importance of parents' roles are all linked together and fall into the judgment rule library on the home-school communication terminal service side. As the carrier of the aggregated conclusion of parents' read status, it reflects the overall trend of the achievement of aggregated parent read status under the dual account binding relationship as the issue position progresses and the position of role importance shifts.

[0144] The above embodiments are merely one of the preferred embodiments of the present invention and should not be used to limit the scope of protection of the present invention. Any modifications or refinements made to the main design concept and spirit of the present invention that are not of substantial significance, but solve the same technical problem as the present invention, should be included within the scope of protection of the present invention.

Claims

1. A method for controlling the synchronization of home-school communication data, characterized in that, include: Obtain the login records and read confirmation timestamps of the two parents from the dual account binding relationship, extract the draft content of the offline edited reply, and verify the initial merged version number; The timing compactness is assessed based on the initial merge version number and the read confirmation timestamp, and the content of reply conflicts and inaccuracies is identified and the message status convergence position is determined. Adjust the read aggregation judgment conditions according to the message status convergence position, filter the leading account from the login record and verify the synchronization status of the draft content, and generate a unified merged version view; The unified merged version view identifies merging logic inconsistencies, assesses the fallback extent of remaining branch versions, adjusts the importance of parent roles, and determines the read coverage results on the parent side. Based on the read coverage results and the latest read confirmation timestamp, a synchronization compactness analysis is performed to generate a parent read aggregation curve; Based on the parent read aggregation curve, the evolution trajectory of the parent's independent reply draft is determined, the merging delay path is optimized and the reply conflict inaccuracy judgment condition is updated, and the parent read aggregation conclusion is obtained.

2. The home-school communication data synchronization control method as described in claim 1, characterized in that, The process of retrieving the login records and read confirmation timestamps of the two parents from the dual-account binding relationship, extracting the draft content of the offline edited reply, and verifying the initial merged version number includes: For dual-account binding relationships, retrieve the login records of both parents' accounts and filter the time of viewing the read stamp records for the comment entries; Locate the offline texts of two parents from the draft cache based on the reply topic clues, obtain the draft number, start editing time and end editing time, calculate the editing time and form a summary entry of parent behavior; The reply topics of the mother's account and the father's account are distinguished according to the role tags in the parent behavior summary entries, and the initial merged version number of the independent reply draft is determined for each parent's offline text. The draft number, role tag, and editing duration are concatenated in a preset order to form a version field. Based on the version field, the order in which the two parents independently replied to the draft is generated is recorded to obtain an initial merged version number that distinguishes the source of the replies from the two accounts.

3. The home-school communication data synchronization control method as described in claim 1, characterized in that, The step of assessing the timing compactness based on the initial merge version number and the read confirmation timestamp, identifying content with conflicting or inaccurate responses, and determining the message status rendezvous position includes: Arrange the initial merged version number and the read confirmation timestamp in the order of their generation according to the event timeline, calculate the time interval between the version number writing time and the read confirmation timestamp, and obtain the time sequence compactness metric. The offline texts of the two parents were segmented by sentence to locate the reply points. The conflicting statements in the two drafts under the same comment item were compared to identify the conflicting paragraphs and form the draft difference items. Based on the draft difference entries, retrieve the read confirmation entries from the monitoring list, read the draft flag value and the last editing time, and incorporate them into the aggregation judgment field in conjunction with the time series compactness metric value. The read aggregation lag is calculated based on the misalignment between the read confirmation timestamp and the last edit time, and the node of the lag on the event timeline is determined as the message status convergence position.

4. The home-school communication data synchronization control method as described in claim 1, characterized in that, The step of adjusting the read aggregation judgment condition based on the message status convergence position, filtering the leading account from the login record and verifying the synchronization status of the draft content includes: For the time-series misalignment at the message status convergence position, retrieve the set of trigger conditions for the read aggregation judgment, and offset and correct the threshold of the number of read accounts and the time window span according to the deviation direction of the misalignment at the attribution point to obtain the matching judgment conditions. The session activity count and login terminal type of the two parent accounts are read from the login records. The activity count is compared according to the importance of the role label, and the account with the second highest activity is identified as the dominant account. Based on the set of conflicting paragraphs in the draft differences, a copy of the offline edit response paragraphs from the dominant account is retrieved, and the annotation text is segmented by the parent annotation prefix symbol; Based on the synchronization status of the read confirmation timestamp and the verification annotation text at the last edit time, texts registered later than the read confirmation timestamp are identified as unsynchronized.

5. The home-school communication data synchronization control method as described in claim 1, characterized in that, The process of identifying contradictory merge logic entries through the unified merged version view, assessing the decline in remaining branch versions, and adjusting the importance of parent roles includes: Scan the source markers of the responses from both accounts and the position of the main topic of the response from the unified merged version view. Register the entries that express mutual exclusion under the same topic position as entries with logical contradictions in the merge. Extract the branch points of the version branches that were not included in the main line connection from the aforementioned logical contradiction entries to obtain the remaining branch versions; For the version number values ​​of the remaining branch versions, the downward magnitude of the version rollback trajectory is compared along the message version number change record, and divided into large and small rollback levels according to a preset threshold to obtain the rollback magnitude evaluation value. Based on the aforementioned pullback magnitude assessment value, retrieve the weight values ​​of both accounts, adjust the weight values ​​according to the gear indicator, and determine the adjusted weight values.

6. The home-school communication data synchronization control method as described in claim 1, characterized in that, The step of analyzing the synchronization tightness based on the read coverage results and the latest read confirmation timestamp to generate a parent read aggregation curve includes: Extract the time period defined by the start and end times of merging from the read coverage results, aggregate the read stamp sequence of comment entries according to the parent account identifier, and retrieve the last entry as the latest stamp; Calculate the distance between the latest stamp and the merging stop time, and extract the time interval between adjacent read stamps from the read stamp sequence to form the internal gap position; Based on the spacing and the position of the internal gap, the density of the bearing is verified according to the preset consistent threshold value. If the spacing is lower than the upper limit and the width of the gap position is lower than the upper limit, the achievement mark is registered as an achievement value. By connecting the endpoints of the covered time periods, the internal gap positions, and the achievement markers along the event timeline according to the issue position, a parent read aggregation curve is generated.

7. The home-school communication data synchronization control method as described in claim 1, characterized in that, The process of determining the evolution trajectory of parents' independent reply drafts based on the parent read aggregation curve, optimizing the merging delay path, and updating the reply conflict inaccuracy judgment conditions includes: Extract the draft number and editing time of each parent from the parent read aggregation curve, connect them in chronological order to form a draft item chronological chain, divide the long-term evolution segment and register the transition node as the node revision position to obtain the evolution trajectory; By comparing the migration trend of role tag values ​​and importance ranking in the dual account binding history, the entries with falling ranking were identified as rollback triggers, forming change context entries; Align the changed context entries with the parent read aggregation curve, use the continuous segments marked with consistency as the steady-state control baseline, and select the node revision bits and rollback trigger bits in the segments that have not achieved the goal as adjustment nodes. Based on the adjustment node's synchronous offset drop and the degree of conflict with the description, update the consistency threshold value and the drop threshold, and refresh the judgment conditions.

8. The home-school communication data synchronization control method as described in claim 1, characterized in that, The generation of a unified merged version view includes: Read the paragraph writing time from the offline edit reply paragraph and the read confirmation timestamp, and match the comment item number with the parent account identifier to form a comparison record; Extract paragraph copies of the dominant account from the comparison records, and select the sentence / segment links as the main reply items according to the reply topic; After filtering out entries from the primary account, extract paragraph copies from the secondary account, segment the annotation text according to the parent annotation prefix symbol, verify the synchronization status based on the read confirmation timestamp and the write time, and record the unsynchronized status. A dual-account reply source marker is attached to the main reply entry, and message version number change records are written to the version field to form a unified merged version view.

9. The home-school communication data synchronization control method as described in claim 1, characterized in that, The determination of the read coverage result on the parent's end includes: Read the endpoints of the coverage area from the read confirmation timestamps of the two parents, and then weight and merge the endpoints of the coverage area according to the adjusted dual account weight values ​​to generate the merged coverage area. Based on the correspondence between the merged coverage area and the issue position of the comment items, the completeness of the coverage area's connection to the issue position is calculated to determine the read coverage result on the parent's end.

10. The home-school communication data synchronization control method as described in claim 1, characterized in that, The generation of the parent read aggregation curve includes: Extract the coverage period markers of the two parents from the read coverage results according to the parent account identifier, and retrieve the last entry of each parent's read stamp sequence as the latest read confirmation timestamp; The absolute value of the difference between the latest read confirmation timestamps of the two parents is used as the synchronization offset difference, which is divided into different levels according to the preset offset threshold. By comparing the coverage period markers of the two parents along the event timeline, and comparing the gap width between adjacent read stamps in the read stamp sequence, positions exceeding the preset upper limit are registered as gap positions where consistency requirements have not been met. By sequentially connecting the endpoints of the coverage period, the synchronization offset, and the gaps where consistency requirements were not met according to the order of the topics, an aggregation consistency marker is attached to generate a parent read aggregation curve.

Images