A method for organizing information interaction relationships within a spacecraft

Abstract

The present invention provides a method for organizing information interaction relationships within a spacecraft. An interaction management agent is set on each device participating in information interaction, and there is no central node for managing each agent in the entire spacecraft. Each interaction management agent has an equal status, and there is no need to pre-fix the position and connection relationship of the user. All users are dynamically added after the operation is started. Newly added users do not need to understand the status of the system and other users, and users are allowed to increase or decrease or change their positions. At the same time, the present invention supports users to establish a supply and demand relationship for information content, that is, constructs a user table and an information demand table, and weakens the connection relationship between users, so that when the network and users change dynamically, the relationship between providing and obtaining information is not affected, and the method has flexibility and expansibility.

Description

Technical Field

[0001] The present invention belongs to the field of spacecraft onboard information and data technology, and in particular relates to a method for organizing information interaction relationships within a spacecraft. Background Art

[0002] In traditional spacecraft information systems, the data interaction relationship between two users must often be predetermined, which has three main drawbacks: 1) When the number of users who need to participate in information interaction in the system increases, the difficulty of design and maintenance increases greatly, while reliability decreases, and the development cycle is greatly extended; 2) After the design is finalized, it cannot be updated and expanded, and cannot adapt to dynamic changes in structure or tasks. New spacecraft have a higher degree of informatization, complex internal information interaction relationships, and high dynamics, so flexible and scalable information distribution and interaction organization methods are required. 3) As the information interaction relationship becomes more complex, the amount of user data transmission increases greatly, and it may lead to a large number of repeated data flows between and within devices, consuming a large amount of communication and storage resources, as well as copying and processing time, which is not conducive to spacecraft with limited resources. Summary of the invention

[0003] In order to solve the problem of how to organize complex information exchange relationships among multiple users in a spacecraft, the present invention provides a method for organizing information interaction relationships in a spacecraft, which supports dynamic changes in users and their information needs and has flexibility and scalability.

[0004] A method for organizing information interaction relationships within a spacecraft, comprising the following steps:

[0005] After each device in the spacecraft is started, each device acts as a requester to update its own user table and information requirement table;

[0006] After each user on each activated device is activated, it notifies the interactive management agent of the device where it is located of its own identity ID and communication address, and then the interactive management agent of the device where it is located adds the identity ID and communication address to the user table of the device where it is located, and sends the updated user table to the interactive management agents of the remaining devices to update their respective user tables;

[0007] Each activated user organizes the topic number of the information type that he / she wants to receive or stop receiving into a receiving request and sends it to the interactive management agent of the device to update the local information demand table. The interactive management agent of the device then forwards the receiving request to the interactive management agents of other devices to update their respective information demand tables.

[0008] When a user generates information data, the user obtains the various recipient devices that expect to receive the information data with the subject number from the information demand table of the device according to the subject number corresponding to the information data, and obtains the communication address of each recipient device from the user table of the device according to the identity ID of each recipient device. Finally, the user generates an information transmission data frame and sends it to the user data buffer area of ​​the recipient device.

[0009] Furthermore, the method for the requester to update its own user table and information requirement table is:

[0010] The requester sends a synchronization request to the interaction management agents of other devices in the spacecraft through its own interaction management agent. The devices that can receive the synchronization request return user and demand data frames to the requester respectively. The requester's own interaction management agent then updates its own user table and information demand table according to the user and demand data frames, wherein the user and demand data frames are composed of the user tables and information demand tables of each device that can receive the synchronization request.

[0011] Furthermore, after the requester's own interaction management agent obtains the user and demand data frame, it parses the content of the user and demand data frame and writes the parsing results into the local user table and information demand table respectively. When multiple user and demand data frames are received, duplicate information is excluded when updating the user table and information demand table.

[0012] Furthermore, the information transmission data frame consists of a communication address, a subject number, information data content, and a priority, and a priority of 0 indicates cancellation of reception.

[0013] Furthermore, a method for organizing information interaction relationships within a spacecraft further includes the following steps:

[0014] When the user data cache area of ​​each receiver device receives a new information transmission data frame, the respective interaction management agent updates the user data reception index table according to the information demand table. The data reception index table contains the receiver, topic number, storage address, offset, length, priority, and processing flag, so that each user on the receiver device can retrieve the data he wants to receive and then extract it from the common user reception data cache area of ​​the device.

[0015] Beneficial effects:

[0016] 1. The present invention provides a method for organizing information interaction relationships within a spacecraft, wherein an interaction management agent is set on each device participating in information interaction, and there is no central node for managing each agent in the entire spacecraft. Each interaction management agent has an equal status, and there is no need to pre-fix the position and connection relationship of the user. All users are dynamically added after the operation is started, and the newly added user does not need to understand the status of the system and other users, allowing the addition or reduction of users or the change of positions; at the same time, the present invention supports users to establish a supply and demand relationship for information content, that is, constructs a user table and an information demand table, synchronizes management information when the interaction management agent is started, and obtains information of the user table and information demand table from other agents by sending synchronization requests to other agents, thereby synchronizing the local user table and information demand table, and weakening the connection relationship between users, so that when the network and users change dynamically, the relationship between providing and obtaining information is not affected, and the method has flexibility and scalability.

[0017] 2. The present invention provides a method for organizing information interaction relationships within a spacecraft, wherein an interaction management agent maintains a user table and an information demand table, wherein the user table includes the identity IDs and communication addresses of all users within the spacecraft, and the information demand table includes the subject number of the information to be received, the identity ID of the information demander, and the information processing priority. When a user notifies the interaction management agent of the subject number of the information to be received or to be cancelled, a reception request data frame is sent, which includes the user's identity ID, subject number, and priority, and priority 0 indicates cancellation of reception; that is, the present invention organizes the information exchange relationship between multiple users within the entire spacecraft by aggregating, managing, exchanging, and synchronizing user information and user information demand information, and supports intensive distribution of user data, thereby saving resource overhead.

[0018] 3. The present invention provides a method for organizing information interaction relationships within a spacecraft, constructing a user data receiving index table, and sending information data on the same topic produced by each user to each device only once, so that when each user on the device needs information data on any topic, he or she can retrieve the data he or she wants to receive and then extract it from the common user receiving data cache area of ​​the device. This can reduce the transmission and copying of information data of the same type of users and reduce the consumption of spacecraft resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 A schematic diagram of a method for organizing information interaction relationships within a spacecraft provided by the present invention. DETAILED DESCRIPTION

[0020] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0021] The present invention provides a method for organizing information interaction relationships within a spacecraft. The information exchange relationship is not specified in the spacecraft design phase. During the operation phase, users dynamically join and propose and change their needs for certain types of information according to their own functional needs. The interactive management agent on the device maintains the user information and user information demand information in the device and performs interactive synchronization between devices. Certain information generated by the user will be provided to the demander according to the demand for that information. Figure 1 As shown, the steps of the present invention are specifically as follows:

[0022] S1: After each device in the spacecraft is started, each device acts as a requester to update its own user table and information requirement table. Specifically, the requester sends a synchronization request to the interaction management agent of other devices in the spacecraft through its own interaction management agent. The devices that can receive the synchronization request return user and requirement data frames to the requester. After the requester's own interaction management agent obtains the user and requirement data frame, it parses the content of the user and requirement data frame and writes the parsing results into the local user table and information requirement table to update its own user table and information requirement table. The user and requirement data frame is composed of the user table and information requirement table of each device that can receive the synchronization request. At the same time, when multiple user and requirement data frames are received, duplicate information is excluded when updating the user table and information requirement table.

[0023] That is to say, after a device is started, the interactive management agent on it is started, and a synchronization request is sent to all other agents based on a preset known agent list; if the interactive management agent of another device receives the synchronization request, it combines the local user table and information requirement table into a user and requirement data frame, and returns it to the requester; after the interactive management agent requesting synchronization obtains the user and requirement data frame, it parses the content and writes it into the local user table and information requirement table respectively. When multiple user and requirement data frames are received, duplicate information is excluded when updating the user table and information requirement table.

[0024] Furthermore, the composition of the user table is shown in Table 1.

[0025] Table 1

[0026]

[0027] Data design description:

[0028] (1) APID: The user's application process identifier, which is determined by the upper-layer application.

[0029] (2) Device ID: the device ID.

[0030] (3) User ID: An identifier assigned to a user within this device, unique within each device.

[0031] (4) Group ID: The group or role attribute of a user task, which can be used to distinguish the user's business category or permissions.

[0032] (5) Registration status: indicates whether the unit is occupied and whether the node has been registered. The values ​​include: blank, applying for registration, and registered.

[0033] (6) Request message address type: indicates the type of the lower-layer communication interface address used to transmit the request message. The highest bit indicates the address storage method: 0 indicates that the address is directly stored in the subsequent "Request message address" field; 1 indicates that the string pointer address representing the address is stored in the subsequent "Request message address" field; the last 7 bits indicate the specific type of transport layer service: 1 indicates the operating system message queue, and the address type is the message queue ID.

[0034] (7) Request message address: The lower-layer communication interface address used to transmit request message messages.

[0035] (8) User data address type: indicates the type of lower-layer interface address used to transmit user data messages. The highest bit indicates the address storage method: 0 indicates that the address is directly stored in the subsequent "user data address" field; 1 indicates that the string pointer address representing the address is stored in the subsequent "user data address" field; the last 7 bits indicate the specific type of transport layer service: 0 indicates that the transport layer uses the space packet service, and the address type is APID.

[0036] (9) User data address: The lower-layer communication interface address used to transmit user data. If the address type is APID, APID is stored in the lowest 11 bits.

[0037] It should be noted that in a specific implementation, the "user data address" is not necessarily used, because it may be possible to support the lower-layer communication addressing based on the device ID.

[0038] Furthermore, the composition of the information requirement table is shown in Table 2.

[0039] Table 2

[0040]

[0041] Data design description:

[0042] (1) Subject number: The subject of the data type.

[0043] (2) Demander APID: indicates the specific user who wants to obtain the topic.

[0044] (3) Requirement type: divided into "invite" and "publish". "Invite" means that only specified users can provide data on the topic, and "publish" means users with specified group IDs. Group ID 0 means any user.

[0045] (4) Invitee APID / Publisher Group ID: Based on the previous field "Requirement Type", indicate the specific invitee APID or publisher group ID.

[0046] (5) Priority: Priority determines the order of processing and indicates the importance of data. It can also be used in combination with other mechanisms.

[0047] S2: After each user on each activated device is activated, he / she informs the interactive management agent of the device where he / she is located of his / her own identity ID and communication address. The interactive management agent of the device then adds the identity ID and communication address to the user table of the device where he / she is located, and sends the updated user table to the interactive management agents of the remaining devices to update their respective user tables.

[0048] That is to say, there are one or more users on the device. After the interaction management agent is initialized, the user starts and joins, notifies the interaction management agent of the device of its own identity ID and communication address. When the interaction management agent receives the identity ID and communication address notified by the user, it adds the content to the user table and sends it to all other agents. Other interaction management agents update their own user tables after receiving the forwarded user information.

[0049] S3: Each activated user organizes the topic number of the information type that he / she expects to receive or stop receiving into a receiving request and sends it to the interaction management agent of the device to update the local information demand table. The interaction management agent of the device then forwards the receiving request to the interaction management agents of other devices to update their respective information demand tables.

[0050] That is to say, during operation, the user organizes the topic number of the information type that he wants to receive or stop receiving into a receiving request according to his own function and sends it to the interactive management agent of the device where he is located. The interactive management agent updates the local information demand table and forwards the receiving request to the interactive management agents of all other devices. After receiving the receiving request, other interactive management agents also update the information demand table they maintain.

[0051] S4: When the user who starts to generate information data, the user obtains the various receiver devices that are expected to receive the information data of the subject number in the information demand table of the device according to the subject number corresponding to the information data, and obtains the communication address of each receiver device in the user table of the device according to the identity ID of each receiver device, and finally generates an information transmission data frame and sends it to the user data buffer of the receiver device. The information transmission data frame is composed of the communication address, subject number, information data content, and priority, and the priority of 0 indicates cancellation of reception. At the same time, the information transmission data frame is sent to the user data buffer of the receiver device directly by the user or by the sending function module in the device where the user is.

[0052] That is to say, when a user generates a certain type of information data (a certain topic number) during operation, he consults the information demand table, searches according to the topic number, and obtains the communication address of all recipients who expect to receive the topic number according to their identity ID in the user table, and organizes the information transmission data frame composed of the communication address, information topic number, information data content, and priority. The information transmission data frame can be sent to the user data buffer area of ​​the recipient device directly by the user or by a special sending function module in the device. At the same time, the user data of the same topic sent to multiple users of the same device is only sent once.

[0053] S5: When the user data buffer of each receiver device receives a new information transmission data frame, the respective interaction management agent updates the user data reception index table according to the information demand table, so that each user on the receiver device can retrieve the data he or she wants to receive and then extract it from the common user reception data buffer of the device.

[0054] That is, when the user data receiving buffer receives new data, the agent updates the user data receiving index table according to the information demand table, so that the user can retrieve his own data and then extract it from the public user receiving data buffer of this device.

[0055] Furthermore, the composition of the user data receiving index table is shown in Table 3.

[0056] Table 3

[0057]

[0058] Data design description:

[0059] (1) Receiver APID: same as above.

[0060] (2) Topic number: The topic of the received data type.

[0061] (3) Storage address: the starting address where the message entity is stored.

[0062] (4) Offset: Indicates the number of bytes from the storage address to the start of the user data. For interactive messages within the device, the offset is 0. For data from other devices, the offset is related to the lower-layer communication format and the packet header length should be skipped.

[0063] (5) Length: The number of bytes of user data length.

[0064] (6) Priority: Priority determines the order of processing and indicates the importance of data. It can also be used in combination with other mechanisms.

[0065] (7) Processing flag: used to manage the message cache. The values ​​include: blank (same as read), updating, and waiting to be read.

[0066] The following takes the example of N devices in a spacecraft to explain in detail the information interaction relationship organization method of the present invention.

[0067] Suppose there are N devices E1, E2, ...En in the spacecraft, each with M 1 、M 2 ……M n Each user participates in information interaction. The specific implementation method is mainly divided into the following four steps:

[0068] Step 1: Proxy initialization

[0069] The interactive management agent is started earlier than all users participating in information interaction on the device. During the initialization of the agent, according to the preset known agent list, it sends synchronization requests to other N-1 agents in the spacecraft. For example, device E1 sends a synchronization request to devices E2~En. The devices in E2~En that are started earlier than E1 will form a user and demand data frame with the local user table and information demand table and return it to E1. After the interactive management agent of E1 obtains the user and demand data frame from the agents on other devices, it parses the content and writes it into the local user table and information demand table respectively. If multiple agents in E2~En return the user and demand data frame, the interactive management agent of E1 will exclude duplicate information when updating the user table and information demand table. When devices E2~En are started, the agents on them also perform the same initialization work.

[0070] Step 2: User Joining

[0071] E1 on the device has M 1 Users A1(1)~A1(m 1 ), after the interaction management agent is initialized, each user starts and notifies the interaction management agent of his / her identity information and communication address. When the interaction management agent receives the identity information and communication address notified by each user, it adds the content to the user table and sends it to all other agents. The interaction management agents of other devices update their own user tables after receiving the forwarded user information.

[0072] Step 3: Organize user needs

[0073] Users A1(1) and A1(m 1 ), under certain working conditions, it is necessary to obtain information with subject number S1, and send the production receiving request to the interactive management agent. The interactive management agent records the receiving request information in the information requirement table of device E1, and then forwards the receiving request to the interactive management agents of devices E2~En. The interactive management agents of each device also update the local information requirement table.

[0074] Step 4: Determine the recipient of the information

[0075] When user A2(1) on device E2 generates information with subject number S1 during its own function operation, it consults the information demand table on device E2 and searches according to subject number S1 to find recipients A1(1) and A1(m 1 ), find out its device ID and communication address according to the user table on E2. Organize the information transmission data frame composed of communication address, information subject number S1, information data content and priority, and submit it to the external sending module of device E2 for processing, and then send it to device E1.

[0076] Step 5: Receive data from users

[0077] After receiving the data frame, the communication receiving module of the E1 device stores it in the receiving buffer area and notifies the E1 agent. The agent updates the user data receiving index table according to the information demand table, which is provided to users A1(1) and A1(m 1 ) retrieves its own data and extracts it from the public user receive data buffer area of ​​this device.

[0078] It can be seen that the present invention proposes a method and device for organizing information interaction relationships within a spacecraft, which does not require pre-fixing the positions and connection relationships of each user participating in information exchange within the spacecraft, and allows users to dynamically increase or decrease or change positions. By supporting users to establish supply and demand relationships based on information content, the connection relationship between users themselves is weakened, so that when the internal equipment or network connection structure of the spacecraft and the user change dynamically, the relationship between the provision and acquisition of information is not affected. By aggregating, managing, exchanging and synchronizing user information and user information demand information, the information exchange relationship between multiple users in the entire spacecraft is organized, and it is also possible to merge and distribute data intensively, reduce the transmission and replication of similar user information data, and reduce spacecraft resource consumption.

[0079] Of course, the present invention may have many other embodiments. Without departing from the spirit and essence of the present invention, those skilled in the art may certainly make various corresponding changes and modifications based on the present invention, but these corresponding changes and modifications should all fall within the scope of protection of the claims attached to the present invention.

Claims

1. A method for organizing information interaction relationships within a spacecraft, characterized in that: The following steps are involved: After each device in the spacecraft is started, each device acts as a requester to update its own user table and information requirement table; After each user on each activated device is activated, it notifies the interactive management agent of the device where it is located of its own identity ID and communication address, and then the interactive management agent of the device where it is located adds the identity ID and communication address to the user table of the device where it is located, and sends the updated user table to the interactive management agents of the remaining devices to update their respective user tables; Each activated user organizes the topic number of the information type that he / she wants to receive or stop receiving into a receiving request and sends it to the interactive management agent of the device to update the local information demand table. The interactive management agent of the device then forwards the receiving request to the interactive management agents of other devices to update their respective information demand tables. When a user generates information data, the user obtains each receiver device that expects to receive the information data of the subject number from the information demand table of the device where the user is located according to the subject number corresponding to the information data, and obtains the communication address of each receiver device from the user table of the device where the user is located according to the identity ID of each receiver device, and finally generates an information transmission data frame and sends it to the user data buffer area of ​​the receiver device; The method for the requester to update its own user table and information requirement table is: The requester sends a synchronization request to the interaction management agents of other devices in the spacecraft through its own interaction management agent, and the devices that can receive the synchronization request return user and demand data frames to the requester respectively, and the requester's own interaction management agent then updates its own user table and information demand table according to the user and demand data frames, wherein the user and demand data frames are composed of the user tables and information demand tables of each device that can receive the synchronization request; After the requester's own interactive management agent obtains the user and demand data frame, it parses the content of the user and demand data frame and writes the parsing results into the local user table and information demand table respectively. When multiple user and demand data frames are received, duplicate information is excluded when updating the user table and information demand table. The following steps are also included: When the user data cache area of ​​each receiver device receives a new information transmission data frame, the respective interaction management agent updates the user data reception index table according to the information demand table. The data reception index table contains the receiver, topic number, storage address, offset, length, priority, and processing flag, so that each user on the receiver device can retrieve the data he wants to receive and then extract it from the common user reception data cache area of ​​the device.

2. A method for organizing information interaction relationships within a spacecraft as claimed in claim 1, characterized in that: The information transmission data frame consists of a communication address, a subject number, information data content, and a priority level, and a priority level of 0 indicates cancellation of reception.

Images