Interactive joint planning method and device and storage medium

Abstract

The invention relates to the technical field of computers, and discloses an interactive joint planning method and device and a storage medium, and the interactive joint planning method comprises the steps: firstly creating a user account and a user role which are independent of each other, and enabling the same user account to be associated with at least one user role; secondly, dividing the planning scheme data into a plurality of independent business data blocks according to business logic; then, when the target business data block is updated at any seat, the identification information of the target business data block is released, so that other seats can obtain the updated content according to the identification information; and finally, obtaining planning results submitted by each seat and performing fitting so as to generate a target planning scheme. According to the invention, flexible collaboration among multiple seats and efficient synchronization of data are realized, and the efficiency and quality of joint planning are improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to interactive joint planning methods, apparatus, and storage media. Background Technology

[0002] In modern complex systems, task planning and collaborative work typically require the participation of multiple departments or personnel. Related technologies often employ a single identity binding model, lacking a flexible role-switching mechanism. Furthermore, during collaborative editing or planning by multiple parties, data synchronization often relies on full data transfer or interface-based synchronization, leading to high network bandwidth consumption and difficulties in maintaining data consistency. In addition, the planning results submitted by each participant are usually fragmented, lacking effective means to integrate these scattered results into a unified target solution.

[0003] Therefore, there is an urgent need for an interactive joint planning method to solve the problems of low collaborative efficiency, high data synchronization delay, and difficulty in unifying planning results in related technologies. Summary of the Invention

[0004] This application provides an interactive joint planning method, apparatus, and storage medium to solve the problems of low collaborative efficiency, high data synchronization delay, and difficulty in unifying planning results in related technologies.

[0005] Firstly, this application provides an interactive joint planning method, which includes: Create independent user accounts and user roles, and associate the same user account with at least one user role; The planning scheme data is divided into multiple independent business data blocks according to business logic; When any seat updates the target business data block, it publishes the identification information of the target business data block so that other seats can obtain the content of the updated target business data block based on the identification information; Obtain the planning results submitted by each seat and fit them to generate the target planning scheme.

[0006] The interactive joint planning method provided in this application firstly, by creating and associating independent user accounts and user roles, supports one account to assume multiple roles, thus improving the flexibility of personnel configuration; secondly, by dividing the planning scheme data into independent business data blocks according to business logic, it avoids the resource waste caused by full data transmission; thirdly, based on the release and acquisition mechanism of business data block identification information, it ensures the consistency of data among various seats, significantly improving collaboration efficiency; and finally, by obtaining the results of each seat and fitting them to generate the target planning scheme, it ensures the integrity and coordination of the final scheme, effectively solving the problem of scattered planning results from multiple parties and difficulty in overall coordination.

[0007] In one alternative implementation, after the step of associating the same user account with at least one user role, the method further includes: Perform vertical permission inheritance so that the basic permissions of a user account cover all user roles associated with that user account; When a user account activates multiple user roles simultaneously, horizontal permission stacking is performed based on the preset principle of least privilege to synthesize the real-time operation scope of the user account.

[0008] In one alternative implementation, the method further includes: For each seat's operational behavior, generate log records with dual identifiers including account identifier and role identifier.

[0009] In one optional implementation, when any seat updates the target service data block, it publishes the identification information of the target service data block so that other seats can obtain the updated content of the target service data block based on the identification information, including: In response to any seat's update operation on the target business data block, update the corresponding target business data block in the database; Update messages containing identification information are published through a message middleware based on a publish-subscribe mechanism, so that other seats can subscribe to and receive update messages through the message middleware. Based on the identification information in the update message, the updated target business data block is read from the database through a preset database access interface.

[0010] In one optional implementation, the database stores planning scheme information and scheme-related element information, and the planning scheme information and scheme-related element information are associated through a planning scheme identifier; The planning scheme data is divided into multiple independent business data blocks based on business logic, including: Based on the planned business logic, the data in the relevant information of the plan is divided into several relatively independent business data blocks, and a unique data block identifier is assigned to each business data block.

[0011] In an optional implementation, when any seat updates the target service data block, the method further includes: Determine whether the update operations of each seat involve the same target business data block. If they involve the same target business data block, retain the data content corresponding to the latest update operation.

[0012] In one alternative implementation, before the step of obtaining and fitting the planning results submitted by each seat, the method further includes: The system receives the planning results submitted by each seat and provides feedback on modifications to each seat through the approval suggestion function, so that each seat can iteratively optimize the planning results.

[0013] In one optional implementation, the step of generating the target planning scheme further includes: During the generation of the target planning scheme, if a conflict is detected between the planning results submitted by each seat, the planning result of the higher priority seat will be retained based on the pre-set seat priority; and / or, the planning result of the seat selected by the user will be retained based on the received user selection instruction.

[0014] Secondly, this application provides an interactive joint planning apparatus, the apparatus comprising: The creation module is used to create independent user accounts and user roles, and to associate the same user account with at least one user role; The segmentation module is used to divide the planning scheme data into multiple independent business data blocks according to business logic. The update module is used to publish the identification information of the target business data block when any seat updates the target business data block, so that other seats can obtain the content of the updated target business data block based on the identification information; The generation module is used to obtain the planning results submitted by each seat and fit them to generate the target planning scheme.

[0015] Thirdly, this application provides a computer-readable storage medium storing computer instructions for causing a computer to execute the interactive joint planning method of the first aspect or any corresponding embodiment described above. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the specific embodiments of this application or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0017] Figure 1 This is a schematic diagram illustrating an application scenario according to an embodiment of this application; Figure 2 This is a schematic flowchart of the first type of interactive joint planning method according to an embodiment of this application; Figure 3 This is a schematic diagram of a second type of interactive joint planning method according to an embodiment of this application; Figure 4 This is a schematic diagram of the user account and user role permission control process according to an embodiment of this application; Figure 5This is a structural block diagram of the business modules and associated business data blocks according to an embodiment of this application; Figure 6 This is a schematic diagram of data synchronization between multiple seats according to an embodiment of this application; Figure 7 This is a schematic diagram illustrating the multi-seat data synchronization and interaction relationship according to an embodiment of this application; Figure 8 This is a schematic diagram of the fitting and conflict resolution process of multi-factor planning results according to an embodiment of this application; Figure 9 This is a structural block diagram of an interactive joint planning device according to an embodiment of this application; Figure 10 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0019] It is understood that before using the technical solutions disclosed in the various embodiments of this application, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this application in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0020] As one optional application scenario in the embodiments of this application, such as Figure 1 As shown, this interactive joint planning method can be executed in a system including at least one terminal device and at least one server. Figure 1 The system is illustrated in the example, which includes a computer 101, a mobile terminal 102, and a server 103, and the terminal devices such as the computer 101 and the mobile terminal 102 are connected to the server 103 through a network 110.

[0021] The terminal device, serving as the carrier of the "seat," can be a smartphone, tablet, laptop, PDA, desktop computer, command and control console, smart wearable device, etc. The terminal device is used to display business data block content, receive user update operations, and submit planning results. Server 103 stores user account and role information, business data block content, and handles the publication of identification information and data distribution. Server 103 can be a standalone physical server, a server cluster, a distributed system, or a cloud server providing cloud services. Network 110 can be a wired or wireless network, examples of which include, but are not limited to, the Internet, corporate intranet, local area network, wide area network, mobile communication network, and combinations thereof, used to transmit identification information and data block content between seats and between seats and the server.

[0022] In related technologies, when planning collaborative tasks involving multiple people, technical problems often arise, such as rigid permission allocation, data conflicts or synchronization delays caused by simultaneous operations by multiple people, and the difficulty in quickly integrating the planning results of all parties into a unified solution. To address these problems, this disclosure provides an interactive collaborative planning method to improve the efficiency of multi-element collaboration in complex systems, reduce network load, and ensure the uniformity of the solution.

[0023] According to an embodiment of this application, an interactive joint planning method embodiment is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0024] This embodiment provides an interactive joint planning method, which can be used in the aforementioned terminal devices, such as laptops and desktop computers. Figure 2 This is a flowchart of an interactive joint planning method according to an embodiment of this application, such as... Figure 2 As shown, the process includes the following steps: Step S201: Create independent user accounts and user roles, and associate the same user account with at least one user role.

[0025] A user account is the identity credential used by an operator to log in to the system, and typically includes a unique account ID, password, and basic personal information. For example, two accounts named "User_A" and "User_B" can be created.

[0026] User roles refer to the specific functions or division of labor undertaken in planning activities, and are usually associated with specific operational permissions. For example, roles such as "intelligence analyst," "resource coordinator," or "chief planner" can be set.

[0027] Association refers to establishing a mapping relationship between accounts and roles in a database or system configuration. For example, administrators can configure the system in the backend management interface to associate the account "User_A" with both the "Intelligence Analyst" and "Resource Scheduler" roles. This means that when an operator logs in using "User_A," they can perform intelligence analysis operations as well as handle resource scheduling tasks. This step, by decoupling and flexibly binding "people" (accounts) and "tasks" (roles), enables the system to adapt to complex and ever-changing personnel division of labor needs.

[0028] Step S202: Divide the planning scheme data into multiple independent business data blocks according to business logic.

[0029] Planning scheme data refers to a complete set of plan information developed to complete a certain task, which may include a large amount of data such as map plots, resource lists, and time schedules.

[0030] Business logic refers to the inherent functional relationships or classification rules between data. For example, data can be categorized by functional modules or by geographical regions.

[0031] A business data block refers to the smallest unit of data that has been divided and can be stored and transmitted independently.

[0032] For example, suppose a large logistics planning scheme includes a "transportation route map," a "vehicle list," and a "driver schedule." Based on business logic, the "transportation route map" data is packaged into a separate business data block (denoted as Block_Map), and the "vehicle list" is packaged into another business data block (denoted as Block_Vehicle). The purpose of this is to break down a large scheme file into several smaller blocks, facilitating subsequent fine-grained management and transmission, rather than reprocessing the entire scheme for every minor modification.

[0033] Step S203: When any seat updates the target business data block, the identification information of the target business data block is published so that other seats can obtain the content of the updated target business data block based on the identification information.

[0034] A seat refers to a client terminal or operating node involved in the planning process. A target business data block refers to the specific data block currently being modified. An update includes adding, deleting, or modifying data. A publication refers to the action of the system sending a notification to the network or message bus. Identification information refers to the ID or code that uniquely identifies the data block.

[0035] For example, suppose an operator at seat A modifies the status of a vehicle in the "Vehicle List," updating the target business data block "Block_Vehicle." Once saved, a message is automatically published to the collaborative network containing the unique identifier of that data block (e.g., "ID: Block_Vehicle_001"). Other seats monitoring this scheme (such as seats B and C) will then receive this message containing the identifier. The software systems at seats B and C, based on this ID, automatically request and download the latest "Block_Vehicle" content from the server and refresh the display. In this way, precise data synchronization is achieved between seats, transmitting only the changed parts, significantly saving bandwidth and improving real-time performance.

[0036] Step S204: Obtain the planning results submitted by each seat and fit them to generate the target planning scheme.

[0037] The planning results refer to the partial plans or sub-projects completed by each seat in its respective area of ​​responsibility.

[0038] Fitting refers to the process of logically combining, conflict-detecting, and fusing multiple local and scattered data or schemes to form a whole.

[0039] The target planning scheme refers to the final, unified overall plan.

[0040] For example, towards the end of the planning process, seat A submits its assigned "transportation route planning results," and seat B submits its "material allocation results." The main control system retrieves all these submissions and initiates a matching process. This process checks the routes against the materials (e.g., checking for routes that have been planned but materials not allocated). After a series of integrations and verifications, these disparate results are merged into a complete "Annual Logistics Overall Guarantee Plan" (i.e., the target planning plan). This step ensures that the results of multiple people's collaborative work can be effectively coordinated to form an executable overall plan.

[0041] In summary, the interactive joint planning method provided in this embodiment firstly, by creating and associating independent user accounts and user roles, supports one account to assume multiple roles, thus improving the flexibility of personnel configuration; secondly, by dividing the planning scheme data into independent business data blocks according to business logic, it avoids the resource waste caused by full data transmission; thirdly, based on the release and acquisition mechanism of business data block identification information, it ensures the consistency of data among various seats, significantly improving collaborative efficiency; and finally, by acquiring the results of each seat and fitting them to generate the target planning scheme, it ensures the integrity and coordination of the final scheme, effectively solving the problem of scattered planning results from multiple parties and difficulty in overall coordination.

[0042] This embodiment provides an interactive joint planning method, which can be used in the aforementioned terminal devices, such as laptops and desktop computers. Figure 3 This is a flowchart of an interactive joint planning method according to an embodiment of this application, such as... Figure 3 As shown, the process includes the following steps: Step S301: Create independent user accounts and user roles, and associate the same user account with at least one user role.

[0043] In this step, the user account is the entity used for system login and authentication (e.g., UserID_001), and the user role is a set of attributes that define business functions and operational boundaries (e.g., "Materials Support Officer"). The system administrator can configure this flexibly, for example, associating the account UserID_001 with both the "Materials Support Officer" and "Transportation Coordinator" roles simultaneously.

[0044] Based on this, further access control is implemented, including: First, vertical permission inheritance is performed to ensure that the basic permissions of a user account cover all user roles associated with that account. This means that the account's basic permissions (such as system login and password modification) are automatically assigned to all roles under it, eliminating the need for repeated configuration. Second, when the account logs in and simultaneously activates both roles, horizontal permission stacking is performed based on the principle of least privilege. For example, if a "Materials Support Officer" can read and write the materials table and a "Transportation Coordinator" can read and write the vehicle table, after stacking, the account can read and write these two tables but cannot access other unauthorized data, thus creating a unified real-time operational scope.

[0045] In addition, logs are automatically generated whenever a user performs any action. These logs record dual identifiers (e.g., Account ID: UserID_001 + Role ID: Role_Transport) to accurately distinguish which role the user is using to perform the action.

[0046] Step S302: Divide the planning scheme data into multiple independent business data blocks according to business logic.

[0047] In this step, a planning scheme information table (storing the overall description of the scheme) and a scheme-related element information table (storing specific details) are pre-established in the database, and the two are linked by a unique planning scheme identifier. Based on business logic (such as by functional department, by time phase, etc.), the massive amount of data in the scheme-related element information is physically or logically divided into several business data blocks. For example, all data related to fuel replenishment is divided into a "fuel data block," and data related to vehicle maintenance is divided into a "maintenance data block." A unique data block identifier (Block_ID) is assigned to each segmented block, such as "Block_001" and "Block_002" respectively, for subsequent accurate indexing.

[0048] Step S303: When any seat updates the target business data block, the identification information of the target business data block is published so that other seats can obtain the content of the updated target business data block based on the identification information.

[0049] In this step, the data synchronization is implemented as follows: Step S3031: In response to any seat's update operation on the target business data block, update the corresponding target business data block in the database.

[0050] An update operation refers to the act of a user modifying data. Updating the corresponding target business data block in the database involves writing the new data modified by the user into the database.

[0051] Step S3032: Publish an update message containing identification information through a message middleware based on a publish-subscribe mechanism, so that other seats can subscribe to and receive the update message through the message middleware. Based on the identification information in the update message, read the updated target business data block from the database through a preset database access interface.

[0052] A message queue is a software component responsible for transmitting messages. For example, seat A modifies the data in "Block_001". First, the new data is written to the database, and then a message is broadcast through the message queue: "Block_001 has been updated". After receiving this message, seat B uses the ID "Block_001" to actively retrieve the latest data from the database and display it on the interface.

[0053] In addition, to handle concurrent conflicts, the system also includes: determining whether the update operations of each seat involve the same target business data block. If they do, the data content corresponding to the latest update operation is retained. For example, if seat A and seat B modify "Block_001" almost simultaneously, comparing their timestamps, if seat B's operation is slightly later, the database ultimately retains seat B's data, ensuring the determinism of the data state.

[0054] Step S304: Obtain the planning results submitted by each seat and fit them to generate the target planning scheme.

[0055] Prior to this step, iterative optimization is supported, including: receiving the planning results submitted by each seat and providing feedback on modifications to each seat through the approval suggestion function, so that each seat can iteratively optimize the planning results.

[0056] The approval and suggestion function is a tool for the chairperson to comment on subordinate plans. For example, if the chairperson finds a flaw in seat A's plan, they can send a suggestion to modify the route, and seat A can then revise and resubmit.

[0057] Finally, the fitting process is performed. During the fitting process, if a conflict is detected between the planning results submitted by each seat, the planning result of the higher-priority seat is retained based on the pre-set seat priority; and / or, the planning result of the user-selected seat is retained based on the received user selection instruction.

[0058] Fitting involves assembling the plans from each subsystem into a master plan. If seat A and seat B plan to use the same track at the same time (i.e., conflict), the system can automatically determine: seat A has higher priority and its plan should be retained; or a pop-up window can prompt the user to select which plan to retain, and the user can then choose to retain seat B's plan. Ultimately, a conflict-free target planning scheme is generated.

[0059] In summary, the interactive joint planning method provided in this embodiment firstly solves the problems of flexible grouping and security control of personnel and functions in complex systems through dynamic mapping of accounts and roles and permission synthesis mechanisms; secondly, it establishes a highly real-time data synchronization link by utilizing the segmentation of business data blocks and an identifier-based publish-subscribe mechanism, combined with real-time database access, ensuring real-time consistency of the situation among all positions; and finally, it achieves effective coordination of multi-factor planning results through iterative feedback optimization and multi-mode conflict resolution fitting. This method solves the technical problems of low collaboration efficiency, delayed data synchronization, and difficulty in scheme integration in related technologies, enabling efficient, accurate, and flexible joint planning in complex environments.

[0060] To better illustrate the interactive joint planning method of the embodiments, a preferred embodiment will be provided below. This embodiment is intended to describe the implementation process of this disclosure in detail, but is not intended to limit the scope of protection of this disclosure.

[0061] Before providing a detailed description of this embodiment, some of the nouns and terms used in this embodiment will be explained.

[0062] Complex systems refer to organic wholes with specific functions, composed of numerous interrelated and interacting elements. Examples include large-scale mission systems requiring multi-element collaborative planning, such as joint command systems and large-scale engineering management systems.

[0063] Multi-element collaboration: refers to a work mode in which functional units (elements) with different functions and fields in the system achieve consistent and complementary cooperation through information exchange and resource allocation.

[0064] User account: refers to the main container in the system, used to bind the basic information of a natural person (such as name and contact information), and is a static identity identifier for users to log in to the system.

[0065] User roles: These are functional instances attached to user accounts, corresponding to specific business elements. Roles define independent data access permissions and operational scopes, and are the smallest logical unit of access control.

[0066] Vertical permission inheritance: This means that the basic general permissions (such as system login and basic settings) of a user account will be automatically passed on and override all user roles associated with it, without having to repeatedly configure basic permissions for each role.

[0067] Horizontal permission stacking: When a user account activates multiple user roles at the same time, the system dynamically synthesizes the union or intersection of the permissions of these roles according to preset rules to form the user's current real-time operation scope.

[0068] Business data block: refers to several relatively independent data units into which a large amount of planning data is divided according to business logic.

[0069] Publish-subscribe mechanism: a messaging pattern. Message senders (publishers) do not send messages directly to specific receivers, but instead publish messages in categories; message receivers (subscribers) subscribe to specific categories of messages, thus achieving asynchronous information distribution.

[0070] Scheme fitting: refers to the process of collecting, logically verifying, splicing and integrating the local planning results scattered across various positions to form a complete overall planning scheme.

[0071] Conflict resolution: refers to the process of eliminating contradictions by using specific algorithms or manual intervention when logically mutually exclusive planning results of different positions are found during the scheme fitting process (such as resource contention or time conflict).

[0072] This embodiment provides an interactive joint planning method for multi-element collaboration in complex systems. This method addresses the problems of element fragmentation, static rigidity, and insufficient information support inherent in traditional planning models by constructing a flexible permission system, a real-time synchronization mechanism based on data blocks, and a closed-loop scheme fitting process.

[0073] This embodiment first establishes a set of access control mechanisms that can adapt to complex organizational structures. Figure 4This is a diagram illustrating the user account and user role access control process, such as... Figure 4 As shown, the process includes the following: The first step is the creation and association of accounts and roles.

[0074] The system administrator first creates user accounts within the system. These user accounts serve as the primary container, storing basic information such as the name and contact details of specific individuals. Subsequently, the administrator creates user roles based on the specific business elements of the complex system (e.g., reconnaissance, attack, logistics). Each user role is assigned strictly independent data access permissions and operational scope, mandating that each role can only view and operate data within its authorized scope, thereby ensuring data security. A user role, as a functional instance attached to a user account, carries the specific business logic.

[0075] In the association process, flexible one-to-many mapping is supported. Administrators can associate a user account with multiple user roles. For example, a senior commander account can be associated with both the intelligence analyst and operations commander roles simultaneously, thereby giving the account the ability to handle cross-domain tasks.

[0076] Next is the generation and management of dynamic permissions. When a user logs into the system, the permission control mechanism will perform calculations in two dimensions, as follows: Vertical inheritance: The basic permissions of a user account (such as system login rights and personal settings rights) will be automatically overridden and inherited by all the roles associated with it.

[0077] Horizontal stacking: When a user activates multiple roles simultaneously during a task, the system does not simply accumulate all permissions. Instead, it dynamically synthesizes permissions according to the principle of least privilege, generating a real-time scope of operations. This ensures that users can complete collaborative tasks with multiple roles without incurring security risks due to excessive permissions.

[0078] In addition, to support multi-task collaboration, it allows multiple seats with the same user role to be online at the same time (e.g., multiple "logistics staff" online at the same time), and supports the establishment of workflow dependencies between different user roles to form a closed-loop collaboration chain.

[0079] Finally, there is the audit and tracing of the source.

[0080] All business operations are strictly logged. In particular, the logging employs a dual-identification mechanism, where each log entry records both the account ID and the role ID. This mechanism ensures that during post-event review, it is possible to trace back to which person (account) performed the operation and to identify their role at the time, achieving precise source tracing.

[0081] To achieve efficient collaboration among multiple seats, this embodiment abandons the traditional full synchronization or UI screen synchronization and constructs a fine-grained synchronization mechanism based on business data blocks. The specific process is as follows: First, based on the planned business logic, the massive solution data is divided into several relatively independent business data blocks. Figure 5 It is a structural diagram of the business module and several associated business data blocks, such as... Figure 5 As shown, each business module is associated with a specific business data block, and a unique data block identifier is assigned to each data block. These data blocks constitute the smallest unit of a single synchronization.

[0082] At the storage level, this embodiment establishes a standardized database structure, which includes a planning scheme information table (storing overall scheme information) and a scheme-related element information table (storing details of each element), and the two are linked by the planning scheme ID.

[0083] The specific execution of the synchronization process relies on the collaborative work of a unified database access interface and message middleware. Figure 6 This is a schematic diagram of the data synchronization process between multiple seats, such as... Figure 6 As shown, the specific process is as follows: When seat A (as the publisher) performs an operation on its business module that results in data changes, it is determined that the associated business data block has been updated.

[0084] First, Seat A writes the updated data to the corresponding business data block in the database via the database interface. Then, Seat A publishes a data update message via a message broker. It's important to note that this message does not contain large amounts of data; it only includes the business data block ID and the associated planning scheme ID.

[0085] Seat B (as a subscriber) subscribes to the relevant messages. When Seat B receives the update message through the message middleware, it automatically triggers the database interface based on the business data block ID in the message, actively reads the latest content of the data block from the database, and refreshes the user interface.

[0086] When multiple seats operate simultaneously Figure 7 This is a diagram illustrating the data synchronization and interaction relationship among multiple seats, such as... Figure 7 As shown, the following guidelines should be followed: If the operations of each seat involve different business data blocks, the system processes them in parallel without interfering with each other.

[0087] If the operations of each seat involve the same business data block, the system follows the principle of "last update as the standard" to ensure the eventual consistency of the data status.

[0088] This business data block-level synchronization method reduces system coupling compared to UI synchronization; compared to full data synchronization, it avoids network congestion and achieves efficient and stable isolated updates.

[0089] After each element has completed its respective task, the core stage of joint planning begins, namely, fitting and resolving. Figure 8 This is a schematic diagram illustrating the process of fitting and resolving conflicts in multi-factor planning results, such as... Figure 8 As shown, the process includes the following: First, each element position (such as the reconnaissance position, the strike position) completes the planning work within its respective authority, stores the partial results in the relevant element information table of the plan, and submits the planning status to the chairman position (commander-in-chief).

[0090] Then, the chairperson reviews the submissions from each seat using the system's approval and suggestion function. The chairperson is not only a recipient but also a guide, able to send specific feedback to each element seat. Each seat then modifies and iteratively optimizes the plan based on this feedback. This process incorporates human cognitive wisdom, initially mitigating obvious logical errors or tactical conflicts.

[0091] Finally, after the iteration is complete, the chairperson initiates the scheme fitting function. The planning results from each seat are automatically extracted and logically integrated. If a conflict is detected during the fitting process (e.g., resource preemption within the same time period), two mechanisms are provided for resolution: One method is automatic decision-making based on priority. It reads a pre-set list of seat priorities (e.g., setting the main attack direction to have a higher priority than the assist direction) and automatically determines the result based on the seat with the higher priority.

[0092] Another approach is manual adjudication based on user selection. A conflict prompt will pop up, and the chairperson will manually choose which side's result to retain based on the current situation.

[0093] Through the above mechanism, this embodiment successfully breaks down the barriers of single elements, realizes the integration and optimization of resources and the improvement of collaborative efficiency, enabling complex systems to flexibly respond to emergencies in a modular and dynamic manner, and significantly reduces the trial and error costs in actual combat.

[0094] This embodiment also provides an interactive joint planning device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0095] This embodiment provides an interactive joint planning device, such as... Figure 9As shown, it includes: Create module 901, which is used to create independent user accounts and user roles, and associate the same user account with at least one user role; The segmentation module 902 is used to segment the planning scheme data into multiple independent business data blocks according to business logic. The update module 903 is used to publish the identification information of the target business data block when any seat updates the target business data block, so that other seats can obtain the content of the updated target business data block based on the identification information; The generation module 904 is used to obtain the planning results submitted by each seat and fit them to generate the target planning scheme.

[0096] In one alternative implementation, creation module 901 is further configured to: Perform vertical permission inheritance so that the basic permissions of a user account cover all user roles associated with that user account; When a user account activates multiple user roles simultaneously, horizontal permission stacking is performed based on the preset principle of least privilege to synthesize the real-time operation scope of the user account.

[0097] In one alternative implementation, creation module 901 is further configured to: For each seat's operational behavior, generate log records with dual identifiers including account identifier and role identifier.

[0098] In one alternative implementation, the update module 903 is used to: In response to any seat's update operation on the target business data block, update the corresponding target business data block in the database; Update messages containing identification information are published through a message middleware based on a publish-subscribe mechanism, so that other seats can subscribe to and receive update messages through the message middleware. Based on the identification information in the update message, the updated target business data block is read from the database through a preset database access interface.

[0099] In one optional implementation, the database stores planning scheme information and scheme-related element information, and the planning scheme information and scheme-related element information are associated through a planning scheme identifier; Segmentation module 902, used for: Based on the planned business logic, the data in the relevant information of the plan is divided into several relatively independent business data blocks, and a unique data block identifier is assigned to each business data block.

[0100] In an alternative implementation, the update module 903 is further configured to: Determine whether the update operations of each seat involve the same target business data block. If they involve the same target business data block, retain the data content corresponding to the latest update operation.

[0101] In an optional implementation, the generation module 904 is further configured to: The system receives the planning results submitted by each seat and provides feedback on modifications to each seat through the approval suggestion function, so that each seat can iteratively optimize the planning results.

[0102] In an optional implementation, the generation module 904 is further configured to: During the generation of the target planning scheme, if a conflict is detected between the planning results submitted by each seat, the planning result of the higher priority seat will be retained based on the pre-set seat priority; and / or, the planning result of the seat selected by the user will be retained based on the received user selection instruction.

[0103] The interactive joint planning apparatus provided in this application can execute the interactive joint planning method provided in any embodiment of this application, and has the corresponding functional modules and beneficial effects for executing the method. Further functional descriptions of the various modules and units described above are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0104] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0105] The following is a detailed reference. Figure 10 The diagram illustrates a structural schematic suitable for implementing the electronic device described in the embodiments of this application. The electronic device may include a processor (e.g., a central processing unit, graphics processor, etc.) 1001, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 1002 or a program loaded from memory 1008 into random access memory (RAM) 1003. The RAM 1003 also stores various programs and data required for the operation of the electronic device. The processor 1001, ROM 1002, and RAM 1003 are interconnected via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0106] Typically, the following devices can be connected to the I / O interface 1005: input devices 1006 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 1007 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; memory devices 1008 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows electronic devices to exchange data via wireless or wired communication with other devices. Although Figure 10Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown, and more or fewer devices may be implemented or have instead.

[0107] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 1009, or installed from memory 1008, or installed from ROM 1002. When the computer program is executed by processor 1001, it performs the functions defined in the interactive joint planning method of embodiments of this application.

[0108] Figure 10 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0109] This application also provides a computer-readable storage medium. The methods described in this application can be implemented in hardware or firmware, or implemented as recordable on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and subsequently stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code. When the software or computer code is accessed and executed by the computer, processor, or hardware, the interactive joint planning method shown in the above embodiments is implemented.

[0110] A portion of this application can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to this application through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

[0111] Although embodiments of this application have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of this application, and all such modifications and variations fall within the scope defined by the appended claims.

Claims

1. An interactive joint planning method, characterized in that, The method includes: Create independent user accounts and user roles, and associate the same user account with at least one user role; The planning scheme data is divided into multiple independent business data blocks according to business logic; When any seat updates the target business data block, it publishes the identification information of the target business data block so that other seats can obtain the content of the updated target business data block based on the identification information; Obtain the planning results submitted by each seat and fit them to generate the target planning scheme.

2. The method according to claim 1, characterized in that, Following the step of associating the same user account with at least one user role, the method further includes: Perform vertical permission inheritance so that the basic permissions of the user account cover all user roles associated with the user account; When a user account activates multiple user roles simultaneously, horizontal permission stacking is performed based on the preset principle of least privilege to synthesize the real-time operation scope of the user account.

3. The method according to claim 1, characterized in that, The method further includes: For each seat's operational behavior, generate log records with dual identifiers including account identifier and role identifier.

4. The method according to claim 1, characterized in that, When any seat updates the target service data block, the step of publishing the identification information of the target service data block so that other seats can obtain the updated content of the target service data block based on the identification information includes: In response to any seat's update operation on the target business data block, update the corresponding target business data block in the database; An update message containing the identification information is published through a message middleware based on a publish-subscribe mechanism, so that other seats can subscribe to and receive the update message through the message middleware. Based on the identification information in the update message, the updated target business data block is read from the database through a preset database access interface.

5. The method according to claim 4, characterized in that, The database stores planning scheme information and scheme-related element information, and the planning scheme information and the scheme-related element information are associated through a planning scheme identifier; The process of dividing the planning scheme data into multiple independent business data blocks based on business logic includes: Based on the planned business logic, the data in the relevant element information of the scheme is divided into several relatively independent business data blocks, and a unique data block identifier is assigned to each business data block.

6. The method according to claim 1, characterized in that, When any seat updates the target business data block, the method further includes: Determine whether the update operations of each seat involve the same target business data block. If they involve the same target business data block, retain the data content corresponding to the latest update operation.

7. The method according to claim 1, characterized in that, Before the step of obtaining and fitting the planning results submitted by each seat, the method further includes: The system receives the planning results submitted by each seat and provides feedback on modifications to each seat through the approval suggestion function, so that each seat can iteratively optimize the planning results.

8. The method according to claim 1 or 7, characterized in that, The step of generating the target planning scheme further includes: During the process of generating the target planning scheme, if a conflict is detected between the planning results submitted by each seat, the planning result of the higher priority seat is retained based on the pre-set seat priority; and / or, the planning result of the seat selected by the user is retained based on the received user selection instruction.

9. An interactive joint planning device, characterized in that, The device includes: The creation module is used to create independent user accounts and user roles, and to associate the same user account with at least one user role; The segmentation module is used to divide the planning scheme data into multiple independent business data blocks according to business logic. The update module is used to publish the identification information of the target business data block when any seat updates the target business data block, so that other seats can obtain the content of the updated target business data block based on the identification information; The generation module is used to obtain the planning results submitted by each seat and fit them to generate the target planning scheme.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to execute the interactive joint planning method according to any one of claims 1 to 8.

Images