# A Heterogeneous Battlefield Situation Information Sharing Method Based on Content
## 5 Information Sharing Mechanism Based on Content  
Based on UBSIS, an implementation mechanism of information sharing was designed, which is shown in Figure 10.  
Suppose both system **A** and system **B** contain the description information of entity \(e_{i}\), and the description information in **A** or **B** merely reflect a certain aspect of it. Besides, the entity class set describing \(e_{i}\) is {\(EC_{i}\), \(EC_{i+1}\),..., \(EC_{i+n}\)}(\(n\in\textbf{N}\)), in which \(EC_{i}\) is a first level class. By organizing this information contained in the messages according to the information description model proposed above, bit oriented information can be transformed into content oriented structured information, so that the potential correlation between heterogeneous information can be expressed explicitly. After that, integrate the information describing the same entity on content and semantics. Then, update the UBSIS, and broadcast the newly received information to all systems except the one from which the information comes. In addition, when someone needs to get some information about specific entities, this can be done by a centralized query in UBSIS. Thus, information sharing among systems can be realized. When considering the process of information sharing based on the UBSIS, it can be divided into two types: information broadcasting and information query. Among them, information broadcasting is easy to realize, e.g., when **A** finds something new and important, you just need to transport it to **B** through UBSIS. The process of querying and searching for the actual entity description information in UBSIS can be viewed as the process of searching for the required entity description information based on specific attributes and semantic relationships between entities; where the searching based on specific attributes is used to find the specific entities that meet the attribute requirements in the query conditions, while it can be easily realized based on the robust operational mechanism of XML; besides, the searching based on semantic relationships between entities is used to judge whether the entities found meet the semantic requirements in the query conditions; for example, when querying the information of entities with attribute \(a_{i}=a_{1}\) and that possess relationship \(r_{a}\) to \(e_{i}\), while relationship \(r_{b}\) to \(e_{j}\). Firstly, entities with attribute \(a_{i}=a_{1}\) are found through Algorithm 1, and then, we judge whether they possess \(r_{a}\) to \(e_{i}\) and relationship \(r_{b}\) to \(e_{j}\) through Algorithm 2. Figure 9: Structure of the entity class classification tree. ```
0: The value \(v_{a}\) of attribute \(a\)
0: The description information of \(e_{i}\) with \(a\)==\(v_{a}\) \(\underline{EFind}(a)\) in \(T_{\text{LEC}}(V_{\text{EC}})\) If true, then ERecord EC\({}_{a}\), Level\({}_{a}\), and \(LNun_{a}\) For each document \(Doc_{i}\) describing \(e_{i}\) in UIS If \(EC_{i}\)=\(EC_{a}\), then Match(\(v_{a}\)) with the value of \(a_{i}\) in \(T(e_{i})\) that satisfies Level\({}_{a_{i}}\)==Level\({}_{a}\), and \(LNun_{a_{i}}\)==\(LNun_{a}\) If true, return \(Doc_{i}\) Else return \"There is no attribute \(a\) found\"
```  
**Algorithm 1** Query of entity description information in UIS. ```
0: Entity \(e_{f}\) and the specific semantic relationship \(r_{f}\)
0: Information of entities that possess \(r_{f}\) to \(e_{f}\) CoFind (\(e_{f}\)) in SRM If true, then CoRecord \(c_{f}\) For each element \(r_{ic_{f}}\) in the column \(c_{f}\) of SRM If \(r_{ic_{f}}\)=\(r_{f}\), then return \(Doc_{i}\) Else return null Else return There are no semantic links directed to \(e_{f}\) found in SRM
```  
**Algorithm 2** Judgment of specific semantic relationships between entities. Figure 10: Implementation progress of information sharing. The _Efind_ function is used to find whether there is an attribute \(a\) in \(T_{LEC}(V_{EC})\).