Distributed command information assistance system, method and related products based on command relationship

Abstract

The application discloses a distributed command information auxiliary system and method based on a command relationship and related products. The command platform server is configured to establish a command relationship graph according to superior-subordinate relationships, post responsibilities, task groupings and temporary authorization information, and distribute the command relationship graph to each command agent device. The first command agent device is configured to query a graph slice to determine a second command agent device corresponding to a command affair in the case that a subordinate unit reports the command affair and a binding object cannot handle the command affair, and send a command cooperation message to the second command agent device. The second command agent device is configured to verify a relationship basis, an authorization range and a security level in the command cooperation message in the case that the command cooperation message is received, generate a structured response in the case that the verification is passed, and return the structured response to the first command agent device. The application improves the response speed and flow accuracy of a command system.

Description

Technical Field

[0001] This application relates to the field of information technology, specifically to a distributed command information assistance system, method, and related products based on command relationships. Background Technology

[0002] Command information systems are core infrastructure supporting operational command, mission scheduling, and situational coordination, and are widely used in command posts at all levels, operational units, and support positions. These systems, through hardware such as communication terminals, workstations, and command platform servers, realize key functions such as issuing command instructions, reporting situational information, relaying support requests, and transmitting mission status, providing technical support for ensuring the efficient operation of the command system.

[0003] In related technologies, command information systems typically consist of hardware such as communication terminals, position display devices, task management servers, and situation display terminals. Commanders, staff officers, and support personnel at all levels use these devices to perform operations such as sending and receiving information, confirming instructions, tracking tasks, and reporting status. When a command task requires collaborative processing by multiple positions, the on-duty personnel or communications officers usually manually search for the target and forward the task content through a contact list, fixed groups, or preset flow rules. However, when the original handler is unable to process the task in a timely manner due to meetings, duty conflicts, or other reasons, the system lacks the ability to autonomously determine collaborative paths, verify permission boundaries, and complete the task flow. All path selection and processing decisions rely on manual completion, leading to systemic risks such as response delays, task backlogs, incorrect path selection, and unauthorized access, severely restricting the response speed and flow accuracy of the command system. Summary of the Invention

[0004] In view of this, this application provides a distributed command information assistance system, method and related products based on command relationship, which can improve the response speed and flow accuracy of the command system.

[0005] To solve the above problems, the technical solution provided in this application is as follows: In a first aspect of this application, a distributed command information assistance system based on command relationship is provided, comprising: a command platform server, a first command agent device, and a second command agent device; The command platform server is configured to establish a command relationship map based on hierarchical relationships, job responsibilities, task grouping, and temporary authorization information, and then distribute the command relationship map to each command agent device, so that each command agent device has the basic data for local routing queries. The first command agent device is configured to query the map slice to determine the second command agent device corresponding to the command task when a lower-level unit reports a command task and the bound object is unable to handle the command task, and then send a command coordination message to the second command agent device. The second command agent is configured to, upon receiving a command coordination message, verify the relationship basis, authorization scope, and confidentiality level in the command coordination message, generate a structured response if the verification is successful, and return it to the first command agent so that the first command agent can generate a processing result based on the structured response.

[0006] In one possible implementation, the distributed command information assistance system further includes: a first edge command device; The first command agent device is configured to determine the corresponding second command agent device based on the task grouping relationship and authorization relationship when the command affairs involve cross-unit collaboration, and submit a cross-unit routing query to the first edge command device. The first edge command device is configured to respond to cross-unit routing queries, determine whether a command transaction falls within the authorized scope of the unit based on locally cached map slices, and send a command coordination message to the second agent device if the command transaction falls within the authorized scope of the unit.

[0007] In one possible implementation, the distributed command information support system also includes: a second edge command device; The first edge command device is configured to submit cross-unit routing query information to the command platform server when the command task exceeds the authorized scope of its own unit, so that the command platform server can return the query results according to the command relationship graph; process the command task according to the query results and encapsulate the processed content into a command coordination message; and send the command coordination message to the second edge command device. The second edge command device is configured to verify the identity of the sending device, verify the relationship basis, authorization scope and confidentiality level in the command and coordination message, and generate a structured response if the verification is successful. If the verification is successful, the transaction summary and request action carried in the command and coordination message are distributed to the local command terminal box of the corresponding position according to the internal job responsibility allocation rules of the unit, so that the local command terminal box can present the coordination request content to the operator of the bound position, collect response information and return it to the second edge command device.

[0008] In one possible implementation, the first edge command device is configured to, when the communication link between the first edge command device and the command platform server is terminated, process authorized transactions within its own unit or region according to the most recently valid map slice and authorization policy; when communication between the first edge device and the command platform server is restored, deduplicatize and retransmit cached messages according to transaction identifiers and message identifiers, and synchronize audit events, processing basis, map version and policy version generated during the offline period to the command platform server.

[0009] In one possible implementation, the second command agent device is configured to return an access denial message or a downgrade summary message when the collaboration request corresponding to the command collaboration message exceeds the authorization scope of the initiating device or the target position does not have the access qualification of the corresponding security level; wherein the access denial message or downgrade summary message includes the reason for denial, the policy version that was hit, the range of fields that can be returned, and whether manual confirmation is required.

[0010] In one possible implementation, the first command agent is also configured to, upon receiving an authorization denial message or a downgrade summary message, query the superior escalation path, generate pending authorization items, submit them for review by a security auditor or authorized personnel, or generate a limited status response based on returnable fields.

[0011] In one possible implementation, the command proxy device includes: a commander command proxy device, a staff officer command proxy device, a communications support post command proxy device, a logistics support post command proxy device, and a lower-level unit seat command proxy device. The commander's command agent device is configured to, when a subordinate unit reports a support request, parse the key attributes of the support request; obtain the real-time status signal of the bound commander; and, if the real-time status information indicates that the commander is online but has not responded within the timeout period, or that the seat is occupied and cannot be processed in a timely manner, query the map slice or initiate a remote query to the command platform server. Based on the job responsibility relationship and task grouping relationship recorded in the command relationship map, it determines the support post command agent device and the staff command agent device as candidate collaboration objects and sends command collaboration messages to the candidate collaboration objects. The command agent device or staff command agent device corresponding to the support post is configured to, upon receiving a command coordination message, verify the identity of the initiator, the validity of the relationship, whether the requested action falls within the authorized scope of the post, and whether the confidentiality level matches. After the verification is passed, it generates a structured response based on the local support resource database that it can access and the current task status and returns it to the commander's command agent device.

[0012] A second aspect of this application provides a distributed command information assistance method based on command relationships, the method comprising: The command platform server establishes a command relationship map based on hierarchical relationships, job responsibilities, task grouping, and temporary authorization information, and distributes the command relationship map to each command agent device, enabling each command agent device to have the basic data for local routing queries. When a subordinate unit reports a command task and the bound object is unable to handle the command task, the first command agent device queries the map slice to determine the second command agent device corresponding to the command task and sends a command coordination message to the second command agent device. When the second command agent receives a command coordination message, it verifies the relationship basis, authorization scope, and confidentiality level in the command coordination message. If the verification is successful, it generates a structured response and returns it to the first command agent device so that the first command agent device can generate a processing result based on the structured response.

[0013] In a third aspect, this application provides a computer device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements a distributed command information assistance method based on command relationship as described in any embodiment of the first aspect.

[0014] In a fourth aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to perform a distributed command information assistance method based on command relationships as described in any embodiment of the first aspect.

[0015] To improve the response speed and accuracy of the command system, this application provides a distributed command information assistance system based on command relationships, including: a command platform server, a first command agent device, and a second command agent device; the command platform server is configured to establish a command relationship graph based on hierarchical relationships, job responsibilities, task grouping, and temporary authorization information, and distribute the command relationship graph to each command agent device, enabling each command agent device to have basic data for local routing queries; the first command agent device is configured to, when a subordinate unit reports a command task and the bound object cannot handle the command task, query a slice of the graph to determine the second command agent device corresponding to the command task and send a command coordination message to the second command agent device; the second command agent device is configured to, upon receiving the command coordination message, verify the relationship basis, authorization scope, and confidentiality level in the command coordination message, generate a structured response if the verification is successful, and return it to the first command agent device so that the first command agent device can generate a processing result based on the structured response.

[0016] In this embodiment, a closed-loop mechanism is established through graph modeling to enable computability of relationships → the agent device autonomously perceives and triggers collaboration → the target device automatically verifies the authorization boundary. This transforms the three core decision-making stages of "who to collaborate with, whether collaboration is possible, and how to transfer" that relied on manual completion into automated execution processes of the equipment. This systematically solves the risks of response delay, transaction backlog, incorrect path selection, and unauthorized access, and improves the efficiency and accuracy of command and control transactions. Attached Figure Description

[0017] Figure 1 A schematic diagram of a distributed command information assistance system based on command relationships provided in an embodiment of this application; Figure 2 A schematic diagram of a three-level collaborative deployment structure of a local command terminal box, an edge command device, and a command platform server is provided for embodiments of this application. Figure 3 A flowchart of collaborative communication for command affairs based on a command relationship graph is provided for embodiments of this application; Figure 4 A schematic diagram of the flow of command affairs status provided in an embodiment of this application; Figure 5 A flowchart of permission confidentiality verification and field minimization processing provided in this application embodiment; Figure 6 A signaling interaction diagram of command and coordination messages between devices is provided as an embodiment of this application; Figure 7 A schematic diagram of cross-unit cooperative routing and boundary control provided in this application embodiment; Figure 8 This application provides a schematic diagram of an offline collaborative, discontinuous transmission, and audit compensation transmission method as an embodiment of the present application. Figure 9 A flowchart illustrating permission denial, downgrade processing, and manual confirmation is provided for embodiments of this application. Figure 10 A flowchart illustrating a distributed command information assistance method based on command relationships, provided for an embodiment of this application. Detailed Implementation

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

[0019] The terms "first" and "second," etc., used in the specification and claims of this application are used to distinguish different objects, not to describe a specific order of objects. For example, "first operation instruction" and "second operation instruction," etc., are used to distinguish different operation instructions, not to describe a specific order of operation instructions.

[0020] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0021] In the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more, for example, multiple processing units means two or more processing units, multiple elements means two or more elements, etc.

[0022] To facilitate understanding of the technical solution of this application, the technical terms used in this application will be introduced below.

[0023] A distributed command information support system is a collaborative communication system formed by multiple command agent devices corresponding to commanders, staff officers, units, or support positions, connected according to command relationships.

[0024] A command agent device is an electronic device that is bound to a specific commander, post, unit, or command seat. It may include a processor, memory, communication interface, status acquisition interface, and authorization verification unit, and is used to receive, parse, coordinate, transfer, and record command-related matters.

[0025] Local command terminal boxes are small terminal devices deployed near command positions, duty positions, or support posts. They are used for collecting position status, caching local context, sending and receiving messages, and providing manual confirmation prompts.

[0026] Edge command devices are edge devices deployed at command posts, unit nodes, regional communication nodes, or task grouping nodes for local routing, map slice caching, intermittent transmission, and audit buffering.

[0027] Command platform server, a server device or server cluster deployed on the superior command platform or central node, is used to maintain the global command relationship graph, execute cross-device routing, issue policies and aggregate audit logs.

[0028] Command relationship graph is a data structure used to describe relationships such as superior-subordinate command, staff coordination, support coordination, temporary authorization, task grouping, and cross-unit communication.

[0029] Map slices are local relational map data generated by the command platform server or edge command device according to units, task groups, confidential domains and authorized scopes. They are used by terminal boxes or edge devices to complete routing decisions within a limited range locally.

[0030] Command and coordination messages are structured messages transmitted between command agents, used to request situational information, confirm matters, transfer tasks, escalate processing, or return to execution status.

[0031] Command affairs involve information that needs to be handled by relevant personnel or positions within the command system, including situation reporting, task confirmation, instruction feedback, support requests, anomaly reports, and meeting coordination.

[0032] Items pending confirmation are those generated by the command agent device but must be confirmed by authorized personnel before they can be responded to, forwarded, upgraded, or archived.

[0033] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the embodiments of this application will be further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0034] See Figure 1 The figure shows a distributed command information assistance system based on command relationship provided in an embodiment of this application, including: a command platform server 1000, a first command agent device 2000, and a second command agent device 3000; Command platform server 1000 is configured to establish a command relationship map based on hierarchical relationships, job responsibilities, task grouping and temporary authorization information, and distribute the command relationship map to each command agent device, so that each command agent device has the basic data for local routing query. The first command agent device 2000 is configured to query the map slice to determine the second command agent device corresponding to the command task when a lower-level unit reports a command task and the bound object is unable to handle the command task, and then send a command coordination message to the second command agent device. The second command agent device 3000 is configured to, upon receiving a command coordination message, verify the relationship basis, authorization scope, and confidentiality level in the command coordination message, generate a structured response if the verification is successful, and return it to the first command agent device so that the first command agent device can generate a processing result based on the structured response.

[0035] In one possible embodiment, command agent devices are configured for commanders, staff officers, communications support personnel, logistics support personnel, and subordinate unit positions within a combat-oriented command information system. The command platform server establishes a command relationship graph based on hierarchical relationships, job responsibilities, task groupings, and temporary authorization information, and distributes the graph data or index to the memory of the corresponding command agent devices. When a subordinate unit reports a support request and the corresponding commander fails to respond within a preset time, the commander's corresponding command agent device receives the request through a communication interface. The processor then parses the request type, urgency level, response timeframe, and security level. After identifying that the request belongs to the support coordination category, the processor queries the command relationship graph in its local memory or the command platform server to determine the support position command agent devices and relevant staff officer command agent devices as candidate coordination partners.

[0036] The command agent device corresponding to the commander sends a command coordination message to the command agent device at the support post. The message includes a transaction summary, relationship basis, requested action, authorization identifier, security level, and return format.

[0037] After the command agent device at the support post completes verification through the authorization and confidentiality verification unit, it returns a structured response, such as the current support status, the range of available resources, the estimated processing time, and matters requiring confirmation from higher authorities. The command agent device corresponding to the commander generates a processing result based on the structured response. If the matter falls within the authorized scope, the processor generates a status reply or transfer record, and the log audit storage unit records the processing chain; if the matter requires confirmation from the commander, a draft handling suggestion is generated and marked as a matter pending confirmation through the human-machine interface.

[0038] In this embodiment, a closed-loop mechanism is established through graph modeling to enable computable relationships → the agent device autonomously perceives and triggers collaboration → the target device automatically verifies the authorization boundary. This transforms the three core decision-making stages—"who to collaborate with, whether collaboration is possible, and how to transfer"—that relied on manual processing into automated execution processes by the equipment. This systematically solves risks such as response delays, transaction backlogs, incorrect path selection, and unauthorized access, improving the efficiency and accuracy of command and control transactions. Specifically, by modeling personnel, positions, units, and authorization relationships in the combat-oriented command system into a computable command relationship graph, the accuracy of transaction routing is improved. When key personnel or positions cannot handle transactions in a timely manner, transaction blocking and repeated manual forwarding are reduced. Through structured command and control collaboration messages, the standardization of situation requests, task transfers, status acknowledgments, and escalation processing is improved.

[0039] The complete technical solution of this application includes the following ten aspects: First, establish a command relationship map. The command agent device or command platform server acquires data on personnel, positions, units, groups, tasks, authorizations, and communication relationships, and stores this data in a memory or map storage device to generate a command relationship map. Relationships include hierarchical command relationships, staff coordination relationships, support coordination relationships, temporary authorization relationships, task grouping relationships, and cross-unit communication relationships.

[0040] Second, configure command agent devices. Each command agent device is bound to a commander, staff officer, unit position, or support position, and receives command tasks, parses task types, determines the status of bound objects, communicates with other command agent devices, and generates processing results within the authorized scope through processors, communication interfaces, and status acquisition interfaces.

[0041] Third, a multi-level hardware deployment approach is adopted. The command agent device can form a local command terminal box, an edge command device, a command post server, or a command platform server. The local command terminal box is used to obtain the post status, local task context, and terminal events; the edge command device is used to perform local routing, caching, and interrupted / continuous transmission; the command platform server is used to maintain the command relationship graph, perform cross-device routing, record logs, and issue control policies.

[0042] Fourth, receive and parse command and control transactions. When the command and control agent receives situation reports, task confirmations, instruction receipts, support requests, anomaly reports, or meeting coordination matters through the communication interface, the processor parses the transaction source, associated unit, task stage, required actions, urgency level, access requirements, security level, and response time.

[0043] Fifth, determine whether the bound object can handle the task in a timely manner. The status acquisition interface outputs status signals to the processor based on online status, seat occupancy status, meeting status, on-duty status, terminal activity status, or timeout failure events. The processor then determines whether the corresponding personnel or positions can handle the task in a timely manner.

[0044] Sixth, determine the collaborative path. The collaborative routing processing unit queries the command relationship graph and selects one or more target command agent devices based on transaction type, command relationship, job responsibilities, authorization scope, task grouping, communication reachability, and response time.

[0045] Seventh, send command and coordination messages. Command and coordination messages include message identifier, transaction identifier, initiating device identifier, target device identifier, command relationship basis, transaction type, requested action, context summary, authorization identifier, security level, response period, return format, and processing status.

[0046] Eighth, the target command agent device processes the coordination request. After receiving the command coordination message, the target device verifies the basis of the command relationship, the permission identifier, and the security level through the permission and security verification unit; after the verification is successful, it returns a structured response based on its accessible data, the status of the bound object, and the local authorization rules.

[0047] Ninth, generate command and control task processing results. Based on the original task, command relationship diagram, coordinated response results, and authorization strategy, the initiating command agent device generates status responses, summary reports, task handover records, escalation notices, draft handling suggestions, or items awaiting commander confirmation.

[0048] Tenth, record and synchronize the processing. The log audit storage unit records transaction input, triggering conditions, participating devices, relationship basis, permission verification results, message digest, generation results, execution actions, and final status for post-event backtracking, permission auditing, and anomaly tracking.

[0049] In one possible implementation, such as Figure 2As shown, the distributed command information support system adopts a three-tiered hardware collaborative structure consisting of local command terminal boxes, edge command devices, and a command platform server. Local command terminal boxes are bound to specific seats or positions; edge command devices serve a unit node, command post node, or task group node; and the command platform server maintains the global map, policies, and audit data. The three levels of devices communicate with each other through controlled communication interfaces, transmitting transactions, routing queries, collaborative messages, policy versions, and log summaries.

[0050]

[0051] In one possible implementation, the command relationship graph in this application embodiment may include a node set, a relationship set, version information, and scope of application. The node set includes at least personnel nodes, position nodes, unit nodes, device nodes, task group nodes, authorization nodes, communication channel nodes, and strategy version nodes. The relationship set includes at least hierarchical command relationships, staff coordination relationships, support coordination relationships, device binding relationships, task group member relationships, authorization relationships, communication channel relationships, and cross-unit communication relationships.

[0052]

[0053] The map version is maintained by the command platform server. Edge command devices and local command terminal boxes receive map slices that match their unit, task group, security domain, and authorized scope. Each command transaction records the map version and policy version used during routing, verification, and result generation so that the processing basis can still be traced back after the relationship changes.

[0054]

[0055] The map version is maintained by the command platform server. Edge command devices and local command terminal boxes receive map slices that match their unit, task group, security domain, and authorized scope. Each command transaction records the map version and policy version used during routing, verification, and result generation so that the processing basis can still be traced back after the relationship changes.

[0056] The map version is maintained by the command platform server. Edge command devices and local command terminal boxes receive map slices that match their unit, task group, security domain, and authorized scope. Each command transaction records the map version and policy version used during routing, verification, and result generation so that the processing basis can still be traced back after the relationship changes.

[0057] Regarding the command and control transaction state machine, the command and control transaction processing in this embodiment can be constrained using a state machine approach to avoid duplicate processing of transactions across multiple devices or unaudited jumps. The state machine may include states such as receiving, parsing, binding object status judgment, routing, permission verification, coordination, response aggregation, result generation, manual confirmation, escalation, completion, rejection, and archiving.

[0058]

[0059] Once a transaction enters the collaborative state, if the target device fails to return a collaborative response within the response period, the initiating agent can mark the transaction as having a collaborative timeout and trigger a retry or alternative path based on the map slice, backup position relationships, and communication reachability. If the retry is successful, the transaction re-enters the collaborative or response convergence state; if the retry fails or the alternative path remains unreachable, it enters the escalation or manual confirmation state, and the timeout count, alternative path, escalation target, and final processing result are written to the log audit storage unit.

[0060] Access control and confidentiality verification, along with field minimization, are implemented. Before initiating a collaboration request and before the target device processes it, both the access control and confidentiality verification units verify the message. Verification includes checking the sending device's identity, the target device's identity, message integrity, transaction identifier, graph relationship basis, whether the requested action falls within the authorized scope, whether the target object possesses the corresponding security level access qualifications, and whether the returned fields meet the minimum necessary principle.

[0061] When permissions or security levels do not meet requirements, the system does not silently discard transactions. Instead, it outputs results such as rejection, downgraded processing, need for manual confirmation, or escalation, and records the corresponding audit events. For example, when the target device does not have permission to access the original attachment, the system may only transmit a context summary or attachment reference; when the requested action exceeds the local authorization scope, the system generates a pending confirmation item and submits it to the commander, duty officer, or authorized superior for confirmation.

[0062] The offline collaboration and intermittent transmission mechanism allows the edge command device to continue processing authorized transactions within its unit or region when it is temporarily disconnected from the command platform server, based on the most recent valid map slice and authorization policy. Transactions involving multiple units, multiple security domains, policy conflicts, or expired map versions are placed in a waiting queue or a manual confirmation queue, without expanding the scope of automatic processing.

[0063] Local command terminal boxes or edge command devices write unsent messages, unconfirmed results, and audit events to a persistent cache. After the network is restored, the device performs deduplication and retransmission based on message identifiers and transaction identifiers, and synchronizes the map version, policy version, and processing basis used during the offline period to the platform audit service.

[0064] The command and coordination message fields are shown in the table below:

[0065]

[0066] Command and coordination messages can be further divided into message types such as transaction commit, route query, route return, coordination request, coordination response, permission denial, manual confirmation request, manual confirmation result, status heartbeat, audit append, and policy synchronization. Different message types are associated with a unified message identifier, transaction identifier, device identifier, map version, and policy version.

[0067]

[0068] The device and related product forms described in the embodiments of this application can be shown in the following table:

[0069]

[0070] Based on the content introduced above, such as Figure 3 As shown in the figure, this application embodiment provides a flowchart of command transaction collaborative communication based on a command relationship graph. First, the local command terminal box receives the original command transaction. Second, the processor parses the type and urgency of the transaction; then, the system queries the command relationship graph to determine the collaborative path. Next, the initiating device sends a command collaboration message to the target device; third, the target device returns a structured response after completing the permission verification; finally, the initiating device generates a final processing status based on the response result and writes the entire process to the log.

[0071] like Figure 4 As shown in the figure, this application embodiment provides a schematic diagram of the state transition of a command transaction, which illustrates the state transition process of a command transaction under the definition of a state machine. The transaction starts from the "RECEIVED" state; after parsing, it enters the "PARSED" state; depending on the state of the bound object, it transitions to "ROUTING" or "REJECTED"; after successful routing, it enters "AUTH_CHECKING"; if the verification passes, it enters "COLLABORATING"; after collaboration is completed, if manual confirmation is required, it transitions to "HUMAN_CONFIRM_REQUIRED", otherwise it directly enters "COMPLETED"; finally, all ending branches transition to the final state of "ARCHIVED".

[0072] like Figure 5As shown in the figure, this application embodiment provides a flowchart of permission confidentiality verification and field minimization processing. The flowchart describes the processing details of the permission verification unit for collaborative messages. First, the verification unit verifies the device identities of the sender and the target; second, it verifies message integrity to prevent tampering; then, it checks whether the requested action is within the authorized scope and confirms that the target has the corresponding confidentiality level; if the verification passes, only fields that meet the minimum necessary principle are transmitted to the target device; if the verification fails, a rejection message or downgrade summary is output, and an audit log is triggered.

[0073] like Figure 6 As shown in the illustration, this application provides a signaling interaction diagram for command and coordination messages between devices to demonstrate the timing signaling interaction process between the initiating device and the target device. The initiator first submits a transaction commit (TRANSACTION_SUBMIT) message to the edge device or platform; the platform returns a routing query (ROUTE_QUERY) result; the initiator then sends a coordination request (COLLAB_REQUEST) to the target; the target verifies the request and returns a coordination response (COLLAB_RESPONSE). If permissions are insufficient, the target returns an authorization denial (AUTH_DENIED) message; finally, the initiator sends an audit append (AUDIT_APPEND) message to the audit storage.

[0074] like Figure 7 As shown in the illustration, this application provides a cross-unit collaborative routing and boundary control diagram, describing the boundary control process for cross-unit transactions. The initiating terminal box submits the cross-unit request to the edge command device of its own unit; the edge device of the unit determines whether it exceeds the local authorization scope, and if so, initiates a routing query to the command platform server; the platform server returns the address and field pruning requirements of the target unit's edge device; after receiving the message, the target edge device re-verifies the identity and authorization scope of the initiator, and after successful verification, distributes the message to the specific terminal boxes of its subordinate positions.

[0075] like Figure 8 As shown in the figure, this application embodiment provides a flowchart of offline collaboration, interrupted and continuous transmission, and audit retransmission, describing the processing mechanism during network interruption and recovery. When the edge device detects a disconnection from the platform server, the system uses the most recently valid map slice to continue processing local transactions within the authorized scope; all messages and audit events generated during this period are written to a persistent cache; when the network is restored, the edge device initiates a deduplication retransmission request to the platform server based on the message identifier; the platform server performs integrity verification on the retransmitted data, and archives the offline audit records after confirming that there are no errors.

[0076] like Figure 9As shown in the figure, this application embodiment provides a flowchart for permission denial, degradation processing, and manual confirmation, illustrating the branch processing path after verification failure. First, the system determines the failure type (such as invalid relationship, insufficient level, etc.); if it is a degradeable type, the system generates a degradation summary and returns it; if manual intervention is required, the system generates a confirmation item and submits it to the superior or authorized personnel; if the confirmation is successful, the transaction continues. If the confirmation is rejected, the transaction is marked as rejected; all failure types, degradation content, confirmation results, and final status are forcibly written to the log audit unit.

[0077] In one possible implementation, if a transaction involves cross-unit collaboration, the initiating command agent device can locate the corresponding unit's command agent device based on the task grouping relationship and temporary authorization relationship, and complete information supplementation, status confirmation, or upgrade processing through command collaboration messages.

[0078] When collaborating across units, the initiating unit's local command terminal does not directly broadcast the request to any target unit. Instead, it submits a cross-unit routing query to its own edge command device. The edge command device determines whether the request falls within its authorized scope based on the geographic map slices. If a global relationship determination is required, the routing query is submitted to the command platform server. The command platform server returns the target edge devices allowed to contact, the relationship criteria, field pruning requirements, and the policy version.

[0079] After receiving a cross-unit collaborative message, the target unit's edge command device verifies the sender's identity, relationship basis, authorization scope, and security level again. If the verification passes, the target unit's edge command device distributes the message to the local command terminal box of the corresponding position within its unit; if the verification fails, the target unit's edge command device returns a rejection, downgrade summary, or a result requiring manual confirmation.

[0080] In one possible implementation, the relevant products can be deployed collaboratively using local command terminal boxes, edge command devices, and a command platform server. The local command terminal box is responsible for seat status awareness and local context acquisition, the edge command device is responsible for local routing, caching, and intermittent transmission, and the command platform server is responsible for maintaining the global relationship graph, issuing policies, and auditing logs.

[0081] When the communication link between the edge command device and the command platform server is temporarily interrupted, the edge command device continues to process authorized transactions within its unit or region using the most recent valid map slice and authorization policy. For transactions involving multiple units, multiple security domains, conflicting map relationships, or expired policy versions, the edge command device writes the transaction to a waiting queue or a manual confirmation queue and generates a status message indicating that it cannot be automatically closed.

[0082] After communication is restored, the edge command device deduplicates and retransmits cached messages according to transaction and message identifiers, and synchronizes the audit events, processing basis, map version, and policy version generated during the offline period to the command platform server. The command platform server performs integrity checks on the retransmitted data based on the chained summary and timestamp in the audit log.

[0083] In one possible implementation, after receiving a coordination request, the target command agent device discovers that the requested action exceeds the authorization scope of the initiating device or the target position does not have the access qualifications for the corresponding security level. In this case, the target command agent device does not process the original transaction content, but instead returns an access denial message or a downgrade summary message, which includes the reason for denial, the policy version that was hit, the range of fields that can be returned, and whether manual confirmation is required.

[0084] After receiving a permission denial or downgrade summary, the initiating agent can query the superior escalation path, generate pending authorization items, submit them for review by a security auditor or authorized personnel, or generate a limited status response based on returnable fields. All of the above denial, downgrade, escalation, and manual confirmation processes are written to the log audit storage unit.

[0085] In the authorization denial, downgrade processing, and manual confirmation process, the system can first determine the failure type, including invalid relationship basis, insufficient authorization scope, mismatched security level, unreachable target device, or map version conflict. For different failure types, the processor generates a denial receipt, downgrade summary, manual confirmation item, or escalation processing request, respectively. The escalation processing request can query the superior path or authorized approval object according to the command relationship map, and write the confirmation result, rejection reason, policy version, and final status to the log audit storage unit.

[0086] In one possible implementation, the collaborative routing processing unit can be implemented by a processor executing a rule table, a relationship graph query program, a workflow sequence, a knowledge retrieval program, a model reasoning program, or a combination thereof. Regardless of the processing method used, the command agent device completes communication and transaction flow based on the command relationship graph, authorization policy, and command coordination messages, and generates pending confirmation items for matters exceeding the authorization scope.

[0087] The local command terminal box can be deployed separately from the existing seat terminal, or it can be integrated into the seat terminal, mobile command terminal, or dedicated communication terminal; the edge command device can adopt embedded server, ruggedized computing device, communication board combination device, or virtualized edge node; the command platform server can adopt centralized server, primary and backup server, or server cluster.

[0088] In this embodiment, personnel, positions, units, and authorization relationships in the combat-oriented command system are modeled as a computable command relationship graph, improving the accuracy of transaction routing. When key personnel or positions cannot handle transactions in a timely manner, transaction blocking and redundant manual forwarding are reduced. Structured command collaboration messages improve the standardization of situational requests, task transfers, status acknowledgments, and escalation processing. Permission identification and security level verification reduce the risks of incorrect routing, unauthorized processing, and information dissemination. A log auditing mechanism enhances the traceability of the command transaction processing chain. Hierarchical deployment of local terminal boxes, edge command devices, and platform servers enables local transactions to be routed and cached within a limited scope at the edge, reducing reliance on the continuous online status of the central platform. Graph slicing, message queues, transaction identification, and idempotent retransmission mechanisms reduce the risk of message omissions and duplicate processing during weak network or network outage recovery. Recording graph versions, policy versions, relationship bases, permission verification results, and manual confirmation results allows for the retrospective processing of historical transactions even after changes in organizational or authorization relationships. Field minimization and summary transmission mechanisms ensure that collaborative messages meet the information requirements of transaction processing while reducing the scope of sensitive information dissemination.

[0089] Based on the distributed command information assistance system based on command relationships described in the foregoing embodiments, this application also provides a distributed command information assistance method based on command relationships, the flowchart of which is shown below. Figure 10 As shown: The methods include: S1000: The command platform server establishes a command relationship map based on hierarchical relationships, job responsibilities, task grouping, and temporary authorization information, and distributes the command relationship map to each command agent device, enabling each command agent device to have the basic data for local routing queries. S2000: When a subordinate unit reports a command task and the bound object is unable to handle the command task, the first command agent device queries the map slice to determine the second command agent device corresponding to the command task and sends a command coordination message to the second command agent device. S3000: When the second command agent receives the command coordination message, it verifies the relationship basis, authorization scope and confidentiality level in the command coordination message. If the verification is successful, it generates a structured response and returns it to the first command agent device so that the first command agent device can generate a processing result based on the structured response.

[0090] In one possible implementation, the method also includes: When command affairs involve cross-unit collaboration, the first command agent device determines the corresponding second command agent device based on task grouping and authorization relationships, and submits a cross-unit routing query to the first edge command device. The first edge command device responds to cross-unit routing queries and determines whether the command task falls within the authorized scope of its unit based on the locally cached map slices. If the command task falls within the authorized scope of its unit, it sends a command coordination message to the second agent device.

[0091] In one possible implementation, the method also includes: When a command task exceeds the authorized scope of its own unit, the first edge command device submits cross-unit routing query information to the command platform server, so that the command platform server can return query results based on the command relationship graph; it processes the command task according to the query results and encapsulates the processed content into a command coordination message; and sends the command coordination message to the second edge command device. The second edge command device verifies the identity of the sending device, and verifies the relationship basis, authorization scope and confidentiality level in the command and coordination message. If the verification is successful, it generates a structured response. If the verification is successful, it distributes the transaction summary and request action carried in the command and coordination message to the local command terminal box of the corresponding position according to the internal job responsibility allocation rules of the unit. The local command terminal box then presents the coordination request content to the operator of the bound position, collects response information and returns it to the second edge command device.

[0092] In one possible implementation, when the communication link between the first edge command device and the command platform server is terminated, the first edge command device processes authorized transactions within its unit or region based on the most recently valid map slice and authorization policy; when communication between the first edge device and the command platform server is restored, the cached messages are deduplicated and retransmitted according to the transaction identifier and message identifier, and the audit events, processing basis, map version and policy version generated during the offline period are synchronized to the command platform server.

[0093] In one possible implementation, if the coordination request corresponding to the command coordination message exceeds the authorization scope of the initiating device or the target position does not have the access qualification of the corresponding security level, the second command agent device returns an access denial message or a downgrade summary message; wherein the access denial message or downgrade summary message includes the reason for denial, the policy version that was hit, the range of fields that can be returned, and whether manual confirmation is required.

[0094] In one possible implementation, upon receiving a permission denial message or a downgrade summary message, the first command agent device queries the superior escalation path, generates pending authorization items, submits them for review by a security auditor or authorized personnel, or generates a limited status response based on returnable fields.

[0095] In one possible implementation, the commander's command agent device is configured to, upon receiving a support request from a subordinate unit, parse the key attributes of the support request; obtain the real-time status signal of the bound commander; and, if the real-time status information indicates that the commander is online but has not responded within the timeout period, or that the seat is occupied and cannot be processed in a timely manner, query the command map slice or initiate a remote query to the command platform server. Based on the job responsibility relationships and task grouping relationships recorded in the command relationship map, it determines the support post command agent device and the staff command agent device as candidate collaboration objects and sends command collaboration messages to the candidate collaboration objects. The command agent device or staff command agent device corresponding to the support post is configured to, upon receiving the command collaboration message, verify the identity of the initiator, the validity of the relationship basis, whether the request action falls within the authorized scope of the post, and whether the confidentiality level matches. After the verification is passed, it generates a structured response based on its accessible local support resource database and the current task status and returns it to the commander's command agent device.

[0096] In this embodiment, a closed-loop mechanism is established through graph modeling to enable computability of relationships → the agent device autonomously perceives and triggers collaboration → the target device automatically verifies the authorization boundary. This transforms the three core decision-making stages of "who to collaborate with, whether collaboration is possible, and how to transfer" that relied on manual completion into automated execution processes of the equipment. This systematically solves the risks of response delay, transaction backlog, incorrect path selection, and unauthorized access, and improves the efficiency and accuracy of command and control transactions.

[0097] In addition, embodiments of this application provide a computer device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements a distributed command information assistance method based on command relationships as described in any embodiment.

[0098] In addition, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to perform a distributed command information assistance method based on command relationships as described in any embodiment.

[0099] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A distributed command information support system based on command relationships, characterized in that, include: Command platform server, first command agent device, and second command agent device; The command platform server is configured to establish a command relationship map based on hierarchical relationships, job responsibilities, task grouping, and temporary authorization information, and to distribute the command relationship map to each command agent device, so that each command agent device has the basic data for local routing queries. The first command agent device is configured to, when a lower-level unit reports a command task and the bound object is unable to handle the command task, query the map slice to determine the second command agent device corresponding to the command task and send a command coordination message to the second command agent device. The second command agent is configured to, upon receiving the command coordination message, verify the relationship basis, authorization scope, and confidentiality level in the command coordination message; if the verification is successful, generate a structured response and return it to the first command agent so that the first command agent can generate a processing result based on the structured response.

2. The system according to claim 1, characterized in that, The distributed command information assistance system also includes: a first edge command device; The first command agent device is configured to determine the corresponding second command agent device based on the task grouping relationship and authorization relationship when the command affairs involve cross-unit collaboration, and submit a cross-unit routing query to the first edge command device; The first edge command device is configured to, in response to the cross-unit routing query, determine whether the command transaction falls within the authorized scope of its own unit based on locally cached map slices; and if the command transaction falls within the authorized scope of its own unit, send the command coordination message to the second agent device.

3. The system according to claim 2, characterized in that, The distributed command information support system also includes: a second edge command device; The first edge command device is configured to, when the command task exceeds the authorized scope of its own unit, submit the cross-unit routing query information to the command platform server, so that the command platform server returns the query result according to the command relationship graph; process the command task according to the query result and encapsulate the processed content into a command coordination message; and send the command coordination message to the second edge command device. The second edge command device is configured to verify the identity of the sending device, verify the relationship basis, authorization scope and confidentiality level in the command and coordination message, and generate a structured response if the verification is successful. If the verification is successful, the transaction summary and request action carried in the command and coordination message are distributed to the local command terminal box of the corresponding position according to the internal job responsibility allocation rules of the unit, so that the local command terminal box can present the coordination request content to the operator of the bound position, collect response information and return it to the second edge command device.

4. The system according to claim 3, characterized in that, The first edge command device is configured to, when the communication link between the first edge command device and the command platform server is terminated, process authorized transactions within its own unit or region based on the most recently valid map slice and authorization policy; when communication between the first edge device and the command platform server is restored, deduplicate and retransmit cached messages according to transaction identifiers and message identifiers, and synchronize audit events, processing basis, map version and policy version generated during the offline period to the command platform server.

5. The system according to claim 1, characterized in that, The second command agent device is configured to return an access denial message or a downgrade summary message when the collaboration request corresponding to the command collaboration message exceeds the authorization scope of the initiating device or the target position does not have the access qualification of the corresponding security level; wherein the access denial message or the downgrade summary message includes the reason for denial, the hit policy version, the range of returnable fields, and whether manual confirmation is required.

6. The system according to claim 6, characterized in that, The first command agent device is further configured to, upon receiving the permission denial message or the downgrade summary message, query the superior upgrade path, generate pending authorization items, submit them for review by a security auditor or authorized personnel, or generate a limited status response based on returnable fields.

7. The system according to claim 1, characterized in that, The command proxy device includes: a commander command proxy device, a staff officer command proxy device, a communications support post command proxy device, a logistics support post command proxy device, and a lower-level unit seat command proxy device. The commander's command proxy device is configured to, when a subordinate unit reports a support request, parse the key attributes of the support request; obtain the real-time status signal of the bound commander; and, if the real-time status information indicates that the commander is online but has not responded within the timeout period, or that the seat is occupied and cannot be processed in a timely manner, query the map slice or initiate a remote query to the command platform server; and, based on the job responsibility relationship and task grouping relationship recorded in the command relationship map, determine the support post command proxy device and the staff command proxy device as candidate collaboration objects and send command collaboration messages to the candidate collaboration objects. The command agent device corresponding to the support post or the staff command agent device is configured to, upon receiving the command coordination message, verify the identity of the initiator, the validity of the relationship, whether the requested action falls within the authorized scope of the post, and whether the confidentiality level matches. After the verification is passed, it generates a structured response based on the local support resource database that it can access and the current task status and returns it to the commander command agent device.

8. A distributed command information assistance method based on command relationships, characterized in that, The method includes: The command platform server establishes a command relationship map based on hierarchical relationships, job responsibilities, task grouping, and temporary authorization information, and distributes the command relationship map to each command agent device, so that each command agent device has the basic data for local routing queries. When a subordinate unit reports a command task and the bound object is unable to handle the command task, the first command agent device queries the map slice to determine the second command agent device corresponding to the command task and sends a command coordination message to the second command agent device. When the second command agent receives the command coordination message, it verifies the relationship basis, authorization scope, and confidentiality level in the command coordination message. If the verification is successful, it generates a structured response and returns it to the first command agent device so that the first command agent device can generate a processing result based on the structured response.

9. A computer device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements the distributed command information assistance method based on command relationship as described in claim 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a terminal device, cause the terminal device to perform the distributed command information assistance method based on command relationships as described in claim 8.

Images