Multi-device synchronous campus information management platform

Abstract

The invention relates to the technical field of campus information management, in particular to a multi-device synchronous campus information management platform, which comprises the steps of identifying terminal roles and field permissions, judging field consistency and source differences, analyzing field dependency and upstream and downstream relationships, labeling field sensitivity levels and transmission paths, classifying multi-terminal data and generating a synchronous content set. The method comprises the following steps: dynamically identifying a corresponding relation between field sources and role permissions, determining a writable boundary of a field, positioning conflicts in combination with field coverage frequency and a submission sequence, extracting a field dependency structure to identify upstream and downstream inconsistent items, marking a transmission path and a priority according to field sensitivity and an equipment state, and constructing a field transmission map; ordered transmission and reasonable distribution of fields among multiple devices are achieved, terminal data fragments are merged based on the field affiliation relation, service scene identifiers are unified, and conflict elimination and synchronous release of multi-source data are achieved.

Description

Technical Field

[0001] This invention relates to the field of campus information management technology, and in particular to a campus information management platform that synchronizes multiple devices. Background Technology

[0002] The field of campus information management technology encompasses a technical system for the centralized processing and unified management of various types of information within the school. Its core components include the digital collection, storage, and categorized management of student registration data, academic affairs data, logistical resources, and teaching resources. This is achieved through a networked system that enables the orderly flow of data across multiple roles and access control. It also covers internal campus data security and authentication mechanisms, as well as multi-terminal access methods for administrators, faculty, and students, forming a complete operational framework from information collection and organization to distribution and retrieval. This framework provides data support and a foundation for business collaboration in campus teaching management and logistical services.

[0003] Among them, the multi-device synchronized campus information management platform refers to a centralized campus information management system that can achieve consistent storage and updating of information across multiple terminal devices. The data categories it targets cover student basic files, course schedules, teaching documents, logistics management records, and campus announcements, etc. Specifically, it completes the writing, reading, and synchronization of data across multiple terminals by establishing a unified data center and using local area network and Internet protocols for data exchange. At the same time, it combines user identity authentication and permission settings to complete the data entry, query, and modification for different roles, so that various terminal devices can synchronize and manage data in a unified format when they are connected.

[0004] Existing technologies do not dynamically categorize field operation permissions, which can easily lead to permission mismatch issues in scenarios with concurrent access by multiple roles. Field content lacks fine-grained submission source analysis, making it impossible to identify data overlay conflicts or time anomalies. The dependency structure between fields does not establish a unified reference relationship, resulting in chaotic data binding and the risk of incorrect references. Field sensitivity levels are not matched with device channel status during field transmission, which may lead to transmission delays or congestion. Terminal data synchronization lacks a unified classification and conflict elimination mechanism, resulting in data content redundancy or scene mapping errors. Summary of the Invention

[0005] The purpose of this invention is to address the shortcomings of existing technologies by proposing a multi-device synchronized campus information management platform.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: a campus information management platform with multi-device synchronization, the platform comprising: The identity and permission recognition module obtains the role type and access method of campus user terminals, extracts the source of field operations and identity matching content, identifies the difference in the permission level of roles to field groups, determines whether a field belongs to an allowed write item, and generates a list of permission-compliant fields. The field difference processing module calls the field content in the permission compliance field list, extracts the field content and submission source, determines the coverage frequency and submission sequence of each field, marks the device tag and data submission node corresponding to the conflicting field, and generates a field conflict location set. The context consistency judgment module calls the conflicting field content in the field conflict location set, retrieves the field dependency path and binding relationship, analyzes the consistency between the field value and the reference item item by item, identifies and removes inconsistent data nodes, filters the remaining field content and matches the dependency chain structure, and generates a context conflict field identifier list. The field channel transmission module calls the unmarked fields in the context conflict field identifier list, extracts the field sensitivity and device status, determines the matching relationship between field sensitivity and device channel load, allocates transmission paths, and generates a field channel allocation transmission map.

[0007] As a further aspect of the present invention, the permission compliance field list includes field role tags, a set of writable fields, a terminal access identifier, an identity matching result, and a field permission level. The field conflict location set includes conflict field names, device identifier tags, field coverage frequency, field submission time period, and conflict node number. The context conflict field identifier list includes dependent field nodes, upstream and downstream binding paths, value expression mismatch items, data reference anomalies, and field consistency anomaly identifiers. The field channel allocation transmission map includes field sensitivity level, field type classification, transmission path identifier, device channel number, and channel load information.

[0008] As a further embodiment of the present invention, the identity and permission recognition module includes a role recognition submodule, an access method extraction submodule, and a field permission judgment submodule; The role recognition submodule obtains the account identifier and task operation type of the campus user terminal, matches the corresponding field in the role registration table according to the account identifier, cross-compares the task operation type with the role operation range recorded in the table, filters within the group by the number of intersection fields and the mapping fields in the role binding table, extracts the set of field tags that meet the role definition conditions, and generates a set of role tags. The access method extraction submodule, based on the account identifier and field label in the role label set, calls the communication protocol, device code and access address number recorded in the terminal access log, classifies and marks them according to the combination position of the communication protocol and address number, performs field comparison with the access field group in the terminal registration table through the combination label, filters to obtain identifiable access channel fields, and obtains the terminal access field list; The field permission judgment submodule matches the fields in the permission configuration table with the access field number and role tag field in the terminal access field list and writes them into the permission list. It performs intersection filtering on the written field number and the operation field list, and completes the screening of writable fields according to the field role binding rules to generate a permission compliant field list.

[0009] As a further aspect of the present invention, the process of obtaining the terminal access field list specifically involves: combining the identifier of the communication protocol retrieved from the terminal access log with the access address number according to a preset character concatenation rule to generate a unique combined position index string; Using the combined location index string as the retrieval basis, the access channel field that matches the combined location index string is searched in the preset access type mapping table, wherein the access type mapping table stores a variety of preset mapping relationships between combined location index strings and access channel fields. The found access channel field is used as the combined marker, and the access channel field that matches the combined marker is selected by comparing the combined marker with the access field group in the terminal registration table one by one, thereby generating the terminal access field list.

[0010] As a further embodiment of the present invention, the field difference processing module includes a field consistency judgment submodule, a field difference calculation submodule, and a conflict field marking submodule; The field consistency judgment submodule calls the field content in the permission compliance field list, obtains the field name, field value and field time tag in the data submitted by each terminal, groups the field names, compares the field values ​​in the same group item by item according to the terminal source, identifies whether there are differences in character format and tag source in the field value expression, and records the submission path and terminal type corresponding to the field value, and generates a field consistency field group. The field difference calculation submodule, based on the field content in the field consistency field group, organizes the submission records of each field on different terminals, identifies the changes in the submission order and expression of the same field in different sources, sorts out the distribution of the value expression, time tag and source device of the records in the field submission path, confirms the set of fields with content or order differences, and obtains the field expression difference field group. The conflict field marking submodule retrieves the device tag and data node identifier from the field submission log based on the field list in the field expression difference field group, marks the source of the differences in the field under different devices, associates the field with the source device and submission node with multi-source submission conflicts, and extracts the field identifier, device identifier and node identifier group to form the location information, generating a field conflict location set.

[0011] As a further embodiment of the present invention, the context consistency judgment module includes a dependency path extraction submodule, a field binding relationship identification submodule, and an upstream and downstream field judgment submodule; The dependency path extraction submodule calls the content of conflicting fields in the field conflict location set to obtain the field number, field name and field source terminal. It performs a dependency query operation on each field and filters the node combinations in the field that have upward or downward field dependency records according to the field reference path fields and reference target numbers marked in the field registration structure table to generate a field dependency path set. The field binding relationship identification submodule extracts the field type and value reference method between dependent fields and dependent fields based on the field node combination in the field dependency path set, maps and matches the hierarchical position number, referenced field name and the field table of the module to which the field belongs, identifies field groups in the field binding where the referenced field and the target field are inconsistent, and obtains a list of field reference anomalies. The upstream and downstream field judgment submodule retrieves the expression content of the field value and the referenced field value based on the field name and path number in the field reference anomaly list, performs equivalence judgment and structural field comparison operations on the value expression between field pairs, identifies field groups where the upstream and downstream field values ​​are inconsistent, extracts the conflict identifier number corresponding to the field group, and generates a context conflict field identifier list.

[0012] As a further aspect of the present invention, the process of identifying field groups whose upstream and downstream field values ​​are not consistent specifically involves: obtaining the field value content and the preset data type of the referenced field value; If the preset data type is a basic data type, then the binary content comparison is directly performed between the field value and the referenced field value, and the field group with inconsistent comparison results is determined as the field group whose upstream and downstream field values ​​are inconsistent; If the preset data type is a structured data type, the field value content and the referenced field value are parsed into a preset tree data structure, and the corresponding node values ​​in the tree data structure are compared one by one. Field groups with inconsistent node values ​​are determined as field groups where the upstream and downstream field values ​​are inconsistent.

[0013] As a further embodiment of the present invention, the field channel transmission module includes a field partitioning labeling submodule, a channel adaptation judgment submodule, and a path order allocation submodule; The field partitioning and labeling submodule calls the unlabeled fields in the context conflict field identifier list to obtain the field number and field name. Based on the sensitivity level field and type classification field recorded in the field attribute registration table, it divides the fields into sensitivity levels and groups the classification labels. Each field is assigned to the corresponding partition label to generate a field sensitivity classification partition set. The channel adaptation judgment submodule extracts the device number, status level and current channel occupancy fields from the terminal device status record table based on the field labels in the field sensitivity classification partition set, performs a one-to-one correspondence judgment on the field sensitivity and channel load labels, identifies the range of fields that the device channel can carry, removes field labels that do not conform to the adaptation relationship, and obtains the field channel adaptation matching group. The path order allocation submodule extracts the channel path code and sequence control identifier of the corresponding field in the field path allocation table based on the field label and device number field in the field channel adaptation matching group, performs field path binding operation on the field and channel number, confirms the scheduling order between the channel sequence marker number and the field number, and establishes a field channel allocation transmission map.

[0014] As a further aspect of the present invention, the platform also includes: The synchronous content publishing and integration module calls the identified fields in the field channel allocation transmission map, classifies and collects field data from the teacher end, student end and academic affairs end, removes conflicting and unprocessed fields, merges synchronous data fragments and marks the business scenario to which they belong, and generates a multi-terminal information synchronous publishing content set. The multi-terminal information synchronization content set includes course data from the teacher's end, registration data from the student's end, grade data from the academic affairs end, business field classification tags, synchronized data fragments, and scene identification information.

[0015] As a further embodiment of the present invention, the synchronous content publishing and integration module includes a field extraction and classification submodule, a conflict field removal submodule, and a data scenario integration submodule; The field extraction and classification submodule calls the identifier field in the field channel allocation transmission map to obtain the field number and the identifier field of the end to which it belongs. Based on the field belonging type field in the field registration list, it extracts the course field of the teacher end, the registration field of the student end, and the grade field of the academic affairs end. It then performs tag classification processing on the field belonging field to generate a field belonging classification structure set. The conflict field removal submodule, based on the field classification labels in the field attribution classification structure set, calls the field number in the context conflict field identifier list, filters and compares the fields existing in the conflict field identifier list, removes matching fields from the classification structure, and retains the field's end identifier and attribution label to obtain a list of non-conflicting fields. The data scenario integration submodule extracts the field content field and time identifier field based on the field number and terminal identifier in the conflict-free field aggregation list. It performs data aggregation on the field content under the same business affiliation tag, adds the terminal identifier field and business scenario identifier field to the field aggregation result, and combines and summarizes the aggregation result according to the field affiliation category to generate a multi-terminal information synchronous release content set.

[0016] Compared with the prior art, the advantages and positive effects of the present invention are as follows: In this invention, by dynamically identifying the correspondence between the source of field operations and role permissions, the writable boundaries of fields are clarified. By combining the coverage frequency and submission order of field values, source conflicts and differences in field expression are located. The dependency structure and binding rules between fields are extracted, and abnormal data references and inconsistencies between upstream and downstream are identified. Based on the field sensitivity level and device status parameters, the transmission priority and path order are marked, and a field transmission map is constructed to achieve orderly transmission and reasonable distribution of fields among multiple devices. Based on the field ownership relationship, data fragments in multi-role terminals are merged, and business scenario identification is unified to achieve conflict elimination, content integration, and synchronous publishing of multi-source data. Attached Figure Description

[0017] Figure 1 This is a flowchart of the platform system of the present invention; Figure 2 This is a flowchart illustrating the acquisition process of the identity and permission recognition module of the present invention. Figure 3 This is a flowchart illustrating the acquisition process of the field difference processing module of the present invention. Figure 4 This is a flowchart illustrating the acquisition process of the context consistency judgment module of this invention. Figure 5 This is a flowchart illustrating the acquisition process of the field channel transmission module of the present invention. Figure 6 This is a flowchart illustrating the acquisition process of the synchronized content publishing and integration module of this invention. Detailed Implementation

[0018] The technical solution of the present invention will now be described with reference to the accompanying drawings.

[0019] In embodiments of the present invention, words such as "exemplarily," "for example," etc., are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" in the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present the concept in a concrete manner. Furthermore, in embodiments of the present invention, the meaning expressed by "and / or" can be both, or either one.

[0020] In the embodiments of this invention, the terms "image" and "picture" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, they convey the same meaning. Similarly, the terms "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, they convey the same meaning.

[0021] In this embodiment of the invention, sometimes a subscript such as W1 may be written in a non-subscript form such as W1. When the difference is not emphasized, the meaning they express is the same.

[0022] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0023] Please see Figure 1 This invention provides a technical solution: a campus information management platform with multi-device synchronization, the platform comprising: The identity and permission recognition module obtains the role type and associated operation source of campus user terminals, extracts role attribute tags and terminal access methods, matches the source identity information and allowed execution items of field execution operations, identifies the difference in permission level of roles to field groups, determines whether a field belongs to a writable item, and generates a list of permission-compliant fields. The field difference processing module calls the field content in the permission compliance field list, performs consistency judgment and source tracing on the field content submitted by each terminal, compares the expression differences of field values ​​and the order of submission, calculates the coverage frequency and submission time interval of each field in all devices, marks the device tags and data submission nodes corresponding to conflicting fields, and generates a set of field conflict location. The context consistency judgment module calls the conflict field content in the field conflict location set, identifies the field nodes that are referenced in the field dependency path, analyzes the association binding rules and data reference points between upstream and downstream fields, judges whether the numerical expression between the field value and its dependency is consistent, removes inconsistent data pairs between upstream and downstream, and generates a list of context conflict field identifiers. The field channel transmission module calls the unmarked fields in the context conflict field identifier list, classifies the sensitivity level and type of the fields into partitions and labels them, extracts the terminal device status and channel occupancy parameters, determines the transmission correspondence between field sensitivity and device channel load, allocates the transmission path and sequence identifier for each field, and generates a field channel allocation transmission map. The synchronized content publishing and integration module calls the identified fields in the field channel allocation transmission map, extracts the content of the course field from the teacher's side, the registration field from the student's side, and the grade field from the academic affairs side, removes conflicting and unprocessed fields, collects terminal data according to the business field classification, merges synchronized data fragments and marks the business scenario to which they belong, and generates a multi-terminal information synchronized publishing content set.

[0024] The list of compliant fields includes field role tags, writable field set, terminal access identifier, identity matching result, and field permission level. The field conflict location set includes conflicting field name, device identifier tag, field coverage frequency, field submission time, and conflict node number. The context conflict field identifier list includes dependent field nodes, upstream and downstream binding paths, value expression mismatch items, data reference anomaly items, and field consistency anomaly identifier. The field channel allocation and transmission graph includes field sensitivity level, field type classification, transmission path identifier, device channel number, and channel load information. The multi-terminal information synchronization and release content set includes teacher-side course data, student-side registration data, academic affairs-side grade data, business field classification tags, synchronized data fragments, and scenario identifier information.

[0025] Please see Figure 2 The identity and permission recognition module includes a role recognition submodule, an access method extraction submodule, and a field permission judgment submodule. The role recognition submodule obtains the account identifier and task operation type of the campus user terminal, matches the corresponding field in the role registration table according to the account identifier, cross-compares the task operation type with the role operation range recorded in the table, filters within the group by the number of intersection fields and the mapping fields in the role binding table, extracts the set of field tags that meet the role definition conditions, and generates a set of role tags. The system retrieves the account identifier and task operation type of the campus user terminal. Specifically, the account identifier is "student_001," and its corresponding task operation type is "submit course assignments." Based on the account identifier "student_001," a search is performed in the role registration table, as shown in Table 1. This table pre-stores the correspondence between account identifiers, roles, and operation ranges. Two records matching "student_001" are found in Table 1, with corresponding role operation ranges of "{submit course assignments, view course materials, modify personal information}" and "{view course announcements, download courseware}." The retrieved task operation type "submit course assignments" is cross-compared with the role operation ranges of these two records. The first record shows an intersection with the field "submit course assignments," with one intersection field. The second record shows a cross-comparison result. Since the set is empty and the number of intersection fields is 0, the number of mapping fields required for different role definitions is queried in the role binding table. The threshold for mapping fields for the "Student" role is set to 1, and the threshold for mapping fields for the "Teaching Assistant" role is set to 3. This threshold is determined based on the statistical analysis of the minimum number of operation types involved when each role performs core tasks in the historical operation log. The 95th percentile with the highest frequency is selected as the threshold. The number of intersection fields 1 is compared with the threshold of mapping fields 1 for the "Student" role. Since 1 equals 1, the filtering condition is met. The number of intersection fields 0 is compared with the threshold of mapping fields 3 for the "Teaching Assistant" role. Since 0 is less than 3, the filtering condition is not met. Based on this, the fields that meet the definition conditions of the "Student" role are filtered out within the group, and the set of field tags associated with this role is extracted. This set includes {"Student ID", "Name", "Course ID", "Assignment Content"}, generating a set of role tags.

[0026] Table 1: Role Registration Form As shown in Table 1, this table records the set of operations that are allowed to be performed by different account identifiers, providing basic matching data for role identification.

[0027] The access method extraction submodule, based on the account identifier and field label in the role label set, calls the communication protocol, device code and access address number recorded in the terminal access log, classifies and marks them according to the combination position of the communication protocol and address number, performs field comparison with the access field group in the terminal registration table through the combination label, filters out the identifiable access channel fields, and obtains the terminal access field list; Based on the account identifier "student_001" and field labels {"student ID", "name", "course number", "assignment content"} from the role label set, the terminal access log is accessed. From the entry associated with the login record of account identifier "student_001" at timestamp "T22:10:05", the following are extracted: communication protocol "HTTPS", device code "PC_Lab_0315", and access address number "192.168.1.108". The entries are then categorized and labeled according to the combination of the communication protocol and the address number. Specifically, the communication protocol identifier "HTTPS" and the access address number "192.168.1.108" retrieved from the terminal access log are combined according to a preset character concatenation rule: "protocol identifier" + "_" + "address number" to generate a unique group. The location index string "HTTPS_192.168.1.108" is used as the retrieval basis to search for the matching access channel field in the preset access type mapping table, as shown in Table 2. The access channel field corresponding to the index "HTTPS_192.168.1.108" is found to be "Campus Network Wired Access". The found "Campus Network Wired Access" is used as a combination tag, and the combination tag is compared with the access field group recorded in the terminal registration table. The access field group associated with the device code "PC_Lab_0315" in the terminal registration table is {"Campus Network Wired Access", "Education Private Network VPN Access"}. "Campus Network Wired Access" is compared with each field in this field group one by one, and the consistent access channel field "Campus Network Wired Access" is selected to obtain the terminal access field list.

[0028] Table 2: Access Type Mapping Table See Table 2, which pre-stores various combinations of location index strings and preset mapping relationships with access channel fields.

[0029] The field permission judgment submodule matches the fields in the permission configuration table with the access field number and role tag field in the terminal access field list and writes them into the permission list. It performs intersection filtering on the written field number and the operation field list, and completes the screening of writable fields according to the field role binding rules to generate a permission compliant field list. Based on the access channel field "Campus Network Wired Access" in the terminal access field list, its corresponding access field number "CH_01" is extracted. This is then combined with the role tag fields in the role tag set, such as "Student," and matched against the permission configuration table. This permission configuration table (as shown in Table 3) pre-stores the write permissions for different roles on different access channels. The list of field write permissions for the "Student" role under the "CH_01" channel is found to be {"Assignment Content", "Submission Time"}, with corresponding field numbers {F004, F005}. Simultaneously, in the actual task operation initiated by the user, the list of operation fields requested for writing is {"Course Number", "Assignment Content"}, with corresponding... The operation field number is {F003, F004}. An intersection filtering operation is performed on the number set {F004, F005} of the field write permission list and the number set {F003, F004} of the operation field list, resulting in {F004}. This number corresponds to the field "Assignment Content". Based on the field role binding rules, writable fields are determined. These rules require that the final writable fields must be necessary fields for the core business of the role. Checking the rule base, the necessary field bound to the core business "Submit Assignment" of the "Student" role is "Assignment Content". The number F004 of the field "Assignment Content" exists in the intersection result {F004}, therefore it is confirmed as a writable field, and a list of permission-compliant fields is generated.

[0030] Table 3: Permission Configuration Table Table 3 lists the field write permissions that different roles have under a specific access channel, which is the direct basis for field permission judgment.

[0031] Please see Figure 3 The field difference processing module includes a field consistency judgment submodule, a field difference calculation submodule, and a conflict field marking submodule; The field consistency judgment submodule calls the field content in the permission compliance field list, obtains the field name, field value and field timestamp in the data submitted by each terminal, groups the field names, compares the field values ​​in the same group item by item according to the terminal source, identifies whether there are differences in character format and tag source in the field value expression, records the submission path and terminal type corresponding to the field value, and generates a field consistency field group. The system retrieves field content from the permission compliance field list, which includes the field {"Job Content", ID F004}. It then obtains the field name, field value, and field timestamp from the data submitted by each terminal. For example, the submitted data from terminal "PC_Lab_0315" is {Field Name: "Job Content", Field Value: "[Text Content]", Field Timestamp: "T22:15:10"}, while the submitted data from the same user from another terminal "Laptop_Personal_02" is {Field Name: "Job Content", Field Value: "[Text Content in Different Formats]", Field Timestamp: "T22:18:30"}. The system groups the field names, grouping data with the same name "Job Content" together. Finally, it compares the field values ​​within each group according to the terminal source. The comparison process involves comparing the binary representation of the field value from "PC_Lab_0315" with the binary representation of the field value from "Laptop_Personal_02" to identify character format differences caused by different newline character encodings (CRLF and LF). Simultaneously, the metadata tags attached to the two field values ​​are checked to identify their origins as "Online Editor Submission Channel" and "File Upload Channel," respectively. This difference in tag origin is recorded. The submission path for the field value "[Text Content]" is " / api / upload / text," and the terminal type is "Public Computer." The submission path for the field value "[Different Format Text Content]" is " / api / upload / file," and the terminal type is "Personal Laptop." A field consistency group is then generated.

[0032] The field difference calculation submodule, based on the field content in the field consistency field group, organizes the submission records of each field on different terminals, identifies the changes in the submission order and expression of the same field in different sources, sorts out the distribution of the value expression, time tag and source device of the records in the field submission path, confirms the set of fields with content or order differences, and obtains the field group with field expression differences. Based on the field content in the field consistency field group, which includes the field name "Job Content" and its submission records from two different terminals, the submission records of each field on different terminals were sorted out. It was identified that on terminal "PC_Lab_0315", the field "Job Content" was encapsulated into the data packet before the field "Submission Time", while on terminal "Laptop_Personal_02", the field "Submission Time" was encapsulated before "Job Content". This is a change in submission order. At the same time, the differences in the expression of the aforementioned field values ​​due to different newline character encoding were also identified. The value expression, time stamp, and source device of the records in the field submission path were analyzed. The distribution analysis specifically revealed that, in the past 24 hours, 15 records for the "Job Content" field were submitted via the path " / api / upload / text", and 8 records were submitted via the path " / api / upload / file". Their time tags ranged from "T22:15:00" to "T22:20:00", and the source devices were mainly the "PC_Lab" series and "Laptop_Personal" series. This analysis confirmed that there were differences in the value representation and submission order of the "Job Content" field. These differences were then added to the set of fields with content or order discrepancies to obtain the field group with the most significant differences in expression.

[0033] The conflict field marking submodule retrieves the device tag and data node identifier from the field submission log based on the field list in the field expression difference field group. It marks the differences in the field under different devices, associates the field with the source device and submission node with multi-source submission conflicts, and extracts the field identifier, device identifier and node identifier group to form the location information and generates the field conflict location set. Based on the field list in the field expression difference field group, extract the field "Job Content" that shows differences, and retrieve the field submission logs to find the device tag and data node identifier associated with this field in different submission records. For example, for the submission record from "PC_Lab_0315", the associated device tag in the log is "Win10_Chrome_v105" and the data node identifier is "DataNode_A". For the submission record from "Laptop_Personal_02", the associated device tag is "MacOS_Safari_v16" and the data node identifier is "DataNode_B". Trace and mark the differences of this field appearing on the two devices, "Win10_Chrome_v105" and "MacOS_Safari_v16". Specifically, the marking process involves generating structured data to record conflicting fields. The identifier “F004”, the source device identifier “Win10_Chrome_v105” and the submitting node “DataNode_A” of the difference content A are recorded. At the same time, the source device identifier “MacOS_Safari_v16” and the submitting node “DataNode_B” of the difference content B are recorded. The field “Job Content” with multi-source submission conflicts is associated with its source devices “PC_Lab_0315”, “Laptop_Personal_02” and submitting nodes “DataNode_A”, “DataNode_B”. The field identifier “F004”, device identifiers {“Win10_Chrome_v105”, “MacOS_Safari_v16”} and node identifiers {“DataNode_A”, “DataNode_B”} are extracted to form the location information, and a field conflict location set is generated.

[0034] Please see Figure 4 The context consistency judgment module includes a dependency path extraction submodule, a field binding relationship identification submodule, and an upstream and downstream field judgment submodule; The dependency path extraction submodule calls the conflict field content in the field conflict location set, obtains the field number, field name and field source terminal, performs a dependency query operation on each field, and filters the node combinations in the field that have upward or downward field dependency records according to the field reference path fields and reference target numbers marked in the field registration structure table, and generates a field dependency path set. The system retrieves the conflicting field content from the field conflict location set, obtaining the field number "F004", field name "Assignment Content", and field source terminal {"PC_Lab_0315", "Laptop_Personal_02"}. It then performs a dependency query operation on field "F004". This operation is achieved by searching the field registration structure table for records that start or end with "F004". This table indicates the reference relationships between fields. For example, if a record is found with the reference path field "F010" (field name "Assignment Score"), the reference destination... The label "F004" (field name "Assignment Content") indicates that "Assignment Score" depends on "Assignment Content". Filter out the node combination {F010, F004} that has a downward field dependency. Simultaneously, find another record with "F004" as its reference path field and "F002" (field name "Course Number") as its reference target number, indicating that "Assignment Content" depends on "Course Number". Filter out the node combination {F004, F002} that has an upward field dependency. Combine these two node combinations to generate a set of field dependency paths.

[0035] The field binding relationship identification submodule extracts the field type and value reference method between dependent fields and the fields they depend on based on the combination of field nodes in the field dependency path set. It maps and matches the hierarchical position number between fields, the referenced field name and the field table of the module to which they belong, identifies field groups in the field binding where the referenced field and the target field are inconsistent, and obtains a list of field reference anomalies. Based on the field node combinations {F010,F004} and {F004,F002} in the field dependency path set, for the combination {F010,F004}, the field type and value reference method between the dependent field "Homework Score" and the dependent field "Homework Content" are extracted. Looking up the table, it is found that the field type of "Homework Score" is "Numerical" and the value reference method is "Indirect Reference". A mapping and matching is performed between the hierarchical position number, the referenced field name, and the field table of the module to which the field belongs. Specifically, the hierarchical position number "L3" of "Homework Score" is compared with the hierarchical position number "L2" of "Homework Content". It is confirmed that their hierarchical relationship conforms to the preset rules. However, it is found that in the field table of the "Grade Management Module" to which "Homework Score" belongs, the referenced field name generated by its value is recorded as "Post-Grading Content" instead of "Homework Content". This identifies a situation where the referenced field and the target field are inconsistent in this binding. The field group {F010,F004} is recorded, and a field reference anomaly list is obtained.

[0036] The upstream and downstream field judgment submodule retrieves the expression of field value content and referenced field value based on the field name and path number in the field reference exception list. It performs equivalence judgment and structural field comparison operations on the value expression between field pairs, identifies field groups where upstream and downstream field values ​​are inconsistent, extracts the conflict identifier number corresponding to the field group, and generates a context conflict field identifier list. Based on the field name "Homework Score" and path number in the field reference anomaly list, which is generated by the dependency {F010->F004}, the value of the "Homework Score" field is retrieved, which is "85". Simultaneously, the value of its referenced field "Homework Content" is retrieved, which is "[Text Content]". The content of these two field values ​​is compared. Specifically, the preset data types of the field value "85" and the referenced field value "[Text Content]" are obtained. The former is a numeric basic data type, and the latter is a text basic data type. Because the data types do not match, it is directly determined that the upstream and downstream field values ​​are inconsistent, and this field group is added to the list. For example, for another field pair "Course Average Score" (structured data)... The data structure is divided into two types: "Type" and "Assignment Score" (basic data type). The "Course Average Score" field value is obtained as {"Midterm Percentage": 0.3, "Final Percentage": 0.5, "Assignment Score": 80}, where the referenced field "Assignment Score" has a value of "85". The "Course Average Score" data structure is parsed into a tree structure, and the node value "80" named "Assignment Score" in the tree structure is compared one by one with the referenced field value "85". Since 80 is not equal to 85, there is a node value inconsistency. This field group is determined to be a field group where the upstream and downstream field values ​​are inconsistent, and the previously generated conflict identifier number corresponding to this field group is extracted, for example, "Conflict_ID_007", generating a context conflict field identifier list.

[0037] Please see Figure 5 The field channel transmission module includes a field partitioning and labeling submodule, a channel adaptation and judgment submodule, and a path order allocation submodule. The field partitioning and labeling submodule calls the unlabeled fields in the context conflict field identifier list to obtain the field number and field name. Based on the sensitivity level field and type classification field recorded in the field attribute registration table, it divides the fields into sensitivity levels and groups them into classification labels. Each field is assigned to the corresponding partition label to generate a field sensitivity classification partition set. The unmarked fields in the context conflict field identifier list are retrieved, and the field number "F010" and field name "Homework Score" are obtained. Based on the records associated with "F010" in the field attribute registration table, the sensitivity level field value is found to be "3", and the type classification field is "Grade". The sensitivity level of this field is then divided into preset ranges: [0-1] for public, [2-4] for internal, and [5-7] for confidential. This range is based on an impact assessment experiment on the leakage of sensitive information from 10,000 historical data sets. Data with a leakage impact factor below 0.2 is classified as public, data between 0.2 and 0.7 as internal, and data above 0.7 as confidential. Experimental results show that this classification method can cover 98% of scenarios. Since the sensitivity level value of "homework score" is 3, which is within the range [2-4], it is classified as "internal". Based on the type classification field "grade", it is classified into the "teaching evaluation" category label group. The field "F010" is classified into the partition label {"internal", "teaching evaluation"}, generating a field sensitivity classification partition set.

[0038] The channel adaptation judgment submodule extracts the device number, status level and current channel occupancy fields from the terminal device status record table based on the field labels in the field sensitivity classification partition set. It performs a one-to-one correspondence judgment on the field sensitivity and channel load label, identifies the range of fields that the device channel can carry, removes field labels that do not conform to the adaptation relationship, and obtains the field channel adaptation matching group. Based on the field labels {"Internal Level", "Teaching Assessment"} in the field sensitivity classification partition set, extract the terminal device status record table related to field submission, and retrieve the record associated with the device code "PC_Lab_0315". This record contains the device number "PC_Lab_0315", the status level "Normal", and the current channel occupancy field "Light Load". Perform a one-to-one correspondence determination between the field sensitivity "Internal Level" and the channel load label "Light Load". This determination is based on a preset adaptation matrix, which specifies the sensitivity words of "Internal Level". The segment can only be transmitted through the "light load" or "medium load" channel, while the "confidential level" field must be transmitted through the "light load" channel. Since the current channel is "light load", it meets the transmission requirements of the "internal level" field, so the adaptation relationship is established. Then, another device "Mobile_Student_01" is judged. Its channel occupation field is "heavy load", which does not meet the transmission requirements of the "internal level" field. The adaptation relationship between this device and the field is eliminated. The combination of field tags and devices that meet the adaptation relationship is retained to obtain the field channel adaptation matching group.

[0039] The path order allocation submodule extracts the channel path code and sequence control identifier of the corresponding field in the field path allocation table based on the field label and device number field in the field channel adaptation matching group, performs field path binding operation on the field and channel number, confirms the scheduling order between the channel sequence marker number and the field number, and establishes the field channel allocation transmission map. Based on the field label "Internal Level" and the device number field "PC_Lab_0315" in the field channel adaptation matching group, the channel path code corresponding to the field "Homework Score" (F010) and the device "PC_Lab_0315" is extracted from the field path allocation table. The code is found to be "Path_Encrypt_02", and the sequence control identifier is "Seq_Grade_Sync". Field path binding operation is performed on the field "Homework Score" and the channel number "Path_Encrypt_02", that is, the transmission request of the field is routed to the encrypted channel. At the same time, the scheduling order between the channel sequence marker number "Seq_Grade_Sync" and the field number "F010" is confirmed. This order stipulates that the field marked "Seq_Grade_Sync" must be scheduled after the field marked "Seq_Info_Update" (such as "Student Personal Information Update") has completed transmission. By setting the above binding and sequence rules, a field channel allocation transmission map is established.

[0040] Please see Figure 6 The synchronized content publishing and integration module includes a field extraction and classification submodule, a conflict field removal submodule, and a data scenario integration submodule. The field extraction and classification submodule calls the identifier field in the field channel allocation transmission map to obtain the field number and the identifier field of the end to which it belongs. Based on the field belonging type field in the field registration list, it extracts the course field of the teacher end, the registration field of the student end, and the grade field of the academic affairs end. It then performs tag classification processing on the field belonging field to generate a field belonging classification structure set. The system calls the fields identified in the field channel allocation transmission map to obtain field numbers, such as "F011" (course name), "F012" (student name), and "F010" (homework score), as well as their respective end-identification fields, such as "teacher end", "student end", and "academic affairs end". It then extracts and classifies the belonging type fields of each field in the field registration list. Specifically, it extracts the field "F011" belonging to the "course" category and assigns it to the teacher end course field set; it extracts the field "F012" belonging to the "student status" category and assigns it to the student end registration field set; and it extracts the field "F010" belonging to the "grade" category and assigns it to the academic affairs end grade field set. Finally, it performs label classification processing according to its belonging field to generate a field belonging classification structure set.

[0041] The conflict field removal submodule, based on the field classification labels in the field attribution classification structure set, calls the field number in the context conflict field identifier list, filters and compares the fields existing in the conflict field identifier list, removes matching fields from the classification structure, and retains the field's end identifier and attribution label to obtain a list of non-conflicting fields. Based on the field category labels in the field classification structure set, such as the "Grade" label, the context conflict field identifier list is retrieved. This list contains previously generated conflict field numbers, such as "F010" (assignment score). Fields existing in the conflict field identifier list are filtered and compared. The field number "F010" under the "Grade" category in the classification structure set is compared with "F010" in the conflict list. Since a match is found, the field "F010" is removed from the "Grade" category structure. At the same time, its end identifier "Academic Affairs End", the belonging label "Grade", and a status bit marked as "Conflict Pending" are retained under this category. For other non-conflicting fields, such as "F011" (course name), since they are not in the conflict list, they are retained. Through this operation, a list of non-conflicting fields is obtained.

[0042] The data scenario integration submodule extracts the field content field and time identifier field based on the field number and terminal identifier in the conflict-free field collection list. It performs data aggregation on the field content under the same business affiliation tag, adds the terminal identifier field and business scenario identifier field to the field aggregation result, and combines and summarizes the aggregation result according to the field affiliation category to generate a multi-terminal information synchronous release content set. Based on the field numbers and terminal identifiers in the conflict-free field aggregation list, extract the field content fields and time identifier fields. For example, extract the "Course Name" (F011) from the teacher's side, whose content is "Data Structure" and time identifier is "T09:00:00", and the "Student ID" (F001) from the student's side, whose content is "student_001" and time identifier is "T09:01:00". Perform data aggregation on the field content under the same business affiliation tag, such as "Course Registration Information", and aggregate "Course Name" and "Student ID" into a JSON object: {"Course Name":"Data Structure","Student ID":"student_001"}. Append terminal identifier fields to this aggregation result, namely "Teacher's Side" and "Student's Side", and append the business scenario identifier field "New Student Course Selection Confirmation". Combine and summarize the aggregation results under all business affiliation tags according to field affiliation categories to form a complete, multi-level JSON structure, and generate a multi-terminal information synchronous publishing content set.

[0043] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A campus information management platform that synchronizes multiple devices, characterized in that, The platform includes: The identity and permission recognition module obtains the role type and access method of campus user terminals, extracts the source of field operations and identity matching content, identifies the difference in the permission level of roles to field groups, determines whether a field belongs to an allowed write item, and generates a list of permission-compliant fields. The field difference processing module calls the field content in the permission compliance field list, extracts the field content and submission source, determines the coverage frequency and submission sequence of each field, marks the device tag and data submission node corresponding to the conflicting field, and generates a field conflict location set. The context consistency judgment module calls the conflict field content in the field conflict location set, retrieves the field dependency path and binding relationship, analyzes the consistency between the field value and the reference item item by item, identifies and removes inconsistent data nodes, filters the remaining field content and matches the dependency chain structure, and generates a context conflict field identifier list. The field channel transmission module calls the unmarked fields in the context conflict field identifier list, extracts the field sensitivity and device status, determines the matching relationship between field sensitivity and device channel load, allocates transmission paths, and generates a field channel allocation transmission map.

2. The campus information management platform with multi-device synchronization according to claim 1, characterized in that: The permission compliance field list includes field role tags, writable field set, terminal access identifier, identity matching result, and field permission level. The field conflict location set includes conflict field name, device identifier tag, field coverage frequency, field submission time period, and conflict node number. The context conflict field identifier list includes dependent field nodes, upstream and downstream binding paths, value expression mismatch items, data reference anomaly items, and field consistency anomaly identifiers. The field channel allocation transmission map includes field sensitivity level, field type classification, transmission path identifier, device channel number, and channel load information.

3. The campus information management platform with multi-device synchronization according to claim 1, characterized in that, The identity and permission recognition module includes a role recognition submodule, an access method extraction submodule, and a field permission judgment submodule; The role recognition submodule obtains the account identifier and task operation type of the campus user terminal, matches the corresponding field in the role registration table according to the account identifier, cross-compares the task operation type with the role operation range recorded in the table, filters within the group by the number of intersection fields and the mapping fields in the role binding table, extracts the set of field tags that meet the role definition conditions, and generates a set of role tags. The access method extraction submodule, based on the account identifier and field label in the role label set, calls the communication protocol, device code and access address number recorded in the terminal access log, classifies and marks them according to the combination position of the communication protocol and address number, performs field comparison with the access field group in the terminal registration table through the combination label, filters to obtain identifiable access channel fields, and obtains the terminal access field list; The field permission judgment submodule matches the fields in the permission configuration table with the access field number and role tag field in the terminal access field list and writes them into the permission list. It performs intersection filtering on the written field number and the operation field list, and completes the screening of writable fields according to the field role binding rules to generate a permission compliant field list.

4. The campus information management platform with multi-device synchronization according to claim 3, characterized in that: The process of obtaining the terminal access field list is as follows: the identifier of the communication protocol and the access address number retrieved from the terminal access log are combined according to a preset character concatenation rule to generate a unique combined position index string; Using the combined location index string as the retrieval basis, the access channel field that matches the combined location index string is searched in the preset access type mapping table, wherein the access type mapping table stores a variety of preset mapping relationships between combined location index strings and access channel fields. The found access channel field is used as the combined marker, and the access channel field that matches the combined marker is selected by comparing the combined marker with the access field group in the terminal registration table one by one, thereby generating the terminal access field list.

5. The campus information management platform with multi-device synchronization according to claim 1, characterized in that, The field difference processing module includes a field consistency judgment submodule, a field difference calculation submodule, and a conflict field marking submodule; The field consistency judgment submodule calls the field content in the permission compliance field list, obtains the field name, field value and field time tag in the data submitted by each terminal, groups the field names, compares the field values ​​in the same group item by item according to the terminal source, identifies whether there are differences in character format and tag source in the field value expression, and records the submission path and terminal type corresponding to the field value, and generates a field consistency field group. The field difference calculation submodule, based on the field content in the field consistency field group, organizes the submission records of each field on different terminals, identifies the changes in the submission order and expression of the same field in different sources, sorts out the distribution of the value expression, time tag and source device of the records in the field submission path, confirms the set of fields with content or order differences, and obtains the field expression difference field group. The conflict field marking submodule retrieves the device tag and data node identifier from the field submission log based on the field list in the field expression difference field group, marks the source of the differences in the field under different devices, associates the field with the source device and submission node with multi-source submission conflicts, and extracts the field identifier, device identifier and node identifier group to form the location information, generating a field conflict location set.

6. The campus information management platform with multi-device synchronization according to claim 1, characterized in that, The context consistency judgment module includes a dependency path extraction submodule, a field binding relationship identification submodule, and an upstream and downstream field judgment submodule; The dependency path extraction submodule calls the content of conflicting fields in the field conflict location set to obtain the field number, field name and field source terminal. It performs a dependency query operation on each field and filters the node combinations in the field that have upward or downward field dependency records according to the field reference path fields and reference target numbers marked in the field registration structure table to generate a field dependency path set. The field binding relationship identification submodule extracts the field type and value reference method between dependent fields and dependent fields based on the field node combination in the field dependency path set, maps and matches the hierarchical position number, referenced field name and the field table of the module to which the field belongs, identifies field groups in the field binding where the referenced field and the target field are inconsistent, and obtains a list of field reference anomalies. The upstream and downstream field judgment submodule retrieves the expression content of the field value and the referenced field value based on the field name and path number in the field reference anomaly list, performs equivalence judgment and structural field comparison operations on the value expression between field pairs, identifies field groups where the upstream and downstream field values ​​are inconsistent, extracts the conflict identifier number corresponding to the field group, and generates a context conflict field identifier list.

7. The campus information management platform with multi-device synchronization according to claim 6, characterized in that: The process of identifying field groups where upstream and downstream field values ​​are inconsistent specifically involves: obtaining the field value content and the preset data type of the referenced field value; If the preset data type is a basic data type, then the binary content comparison is directly performed between the field value and the referenced field value, and the field group with inconsistent comparison results is determined as the field group whose upstream and downstream field values ​​are inconsistent; If the preset data type is a structured data type, the field value content and the referenced field value are parsed into a preset tree data structure, and the corresponding node values ​​in the tree data structure are compared one by one. Field groups with inconsistent node values ​​are determined as field groups where the upstream and downstream field values ​​are inconsistent.

8. The campus information management platform with multi-device synchronization according to claim 1, characterized in that, The field channel transmission module includes a field partitioning labeling submodule, a channel adaptation judgment submodule, and a path order allocation submodule. The field partitioning and labeling submodule calls the unlabeled fields in the context conflict field identifier list to obtain the field number and field name. Based on the sensitivity level field and type classification field recorded in the field attribute registration table, it divides the fields into sensitivity levels and groups the classification labels. Each field is assigned to the corresponding partition label to generate a field sensitivity classification partition set. The channel adaptation judgment submodule extracts the device number, status level and current channel occupancy fields from the terminal device status record table based on the field labels in the field sensitivity classification partition set, performs a one-to-one correspondence judgment on the field sensitivity and channel load labels, identifies the range of fields that the device channel can carry, removes field labels that do not conform to the adaptation relationship, and obtains the field channel adaptation matching group. The path order allocation submodule extracts the channel path code and sequence control identifier of the corresponding field in the field path allocation table based on the field label and device number field in the field channel adaptation matching group, performs field path binding operation on the field and channel number, confirms the scheduling order between the channel sequence marker number and the field number, and establishes a field channel allocation transmission map.

9. The campus information management platform with multi-device synchronization according to claim 1, characterized in that, The platform also includes: The synchronous content publishing and integration module calls the identified fields in the field channel allocation transmission map, classifies and collects field data from the teacher end, student end and academic affairs end, removes conflicting and unprocessed fields, merges synchronous data fragments and marks the business scenario to which they belong, and generates a multi-terminal information synchronous publishing content set. The multi-terminal information synchronization content set includes course data from the teacher's end, registration data from the student's end, grade data from the academic affairs end, business field classification tags, synchronized data fragments, and scene identification information.

10. The campus information management platform with multi-device synchronization according to claim 9, characterized in that, The synchronous content publishing and integration module includes a field extraction and classification submodule, a conflict field removal submodule, and a data scenario integration submodule. The field extraction and classification submodule calls the identifier field in the field channel allocation transmission map to obtain the field number and the identifier field of the end to which it belongs. Based on the field belonging type field in the field registration list, it extracts the course field of the teacher end, the registration field of the student end, and the grade field of the academic affairs end. It then performs tag classification processing on the field belonging field to generate a field belonging classification structure set. The conflict field removal submodule, based on the field classification labels in the field attribution classification structure set, calls the field number in the context conflict field identifier list, filters and compares the fields existing in the conflict field identifier list, removes matching fields from the classification structure, and retains the field's end identifier and attribution label to obtain a list of non-conflicting fields. The data scenario integration submodule extracts the field content field and time identifier field based on the field number and terminal identifier in the conflict-free field aggregation list. It performs data aggregation on the field content under the same business affiliation tag, adds the terminal identifier field and business scenario identifier field to the field aggregation result, and combines and summarizes the aggregation result according to the field affiliation category to generate a multi-terminal information synchronous release content set.

Images