Method, device and storage medium for managing application downlink data based on bus

Abstract

The present application discloses a method for downlinking data based on a bus management application, comprising: a scheduling application sends a data request packet corresponding to a target device to a bus management application, wherein the data request packet is used to indicate information corresponding to the target device; the bus management application responds to the data request packet and converts the data request packet into a data request frame according to a preset device node information table, wherein the device node information table is used to indicate node information of the target device; the target device responds to the data request frame and generates a data response packet, wherein the data response packet is used to indicate data information of the target device; the bus management application generates a data response frame according to the data response packet and sends the data response frame to a telemetry application; and the telemetry application converts the received data response frame into a data response packet and downlinks the data response packet to a ground system.

Description

Technical Field

[0001] The present application relates to the field of satellite management, and in particular to a method, device and storage medium for bus-based management of application downlink data. Background Art

[0002] Satellite telemetry technology has been widely used in the field of satellite technology. Satellite systems transmit telemetry data in the form of telemetry data frames through telemetry channels to ground systems so that staff can monitor equipment on the satellite system.

[0003] Satellite systems typically send telemetry data corresponding to target devices to ground systems in three ways: conventional telemetry, inspection telemetry, and query telemetry. Regardless of whether conventional telemetry, inspection telemetry, or query telemetry are used, a bus management application is required as a bridge.

[0004] However, since the processor module in the existing satellite system cannot make the process of the scheduling application sending a data information request to the bus management application - the process of the bus management application sending a data information request to the target device - the process of the target device sending the data information to the bus management application - the process of the bus management application sending the data information of the target device to the telemetry application highly unified, the operations in the above process are relatively cumbersome.

[0005] With regard to the technical problem existing in the above-mentioned prior art that the processor module in the existing satellite system cannot make the process of the scheduling application sending a data information request to the bus management application - the process of the bus management application sending a data information request to the target device - the process of the target device sending the data information to the bus management application - the process of the bus management application sending the data information of the target device to the telemetry application highly unified, thus making the operations in the above processes relatively cumbersome, no effective solution has been proposed so far. Summary of the Invention

[0006] The embodiments of the present disclosure provide a method for downlinking data based on a bus management application, so as to at least solve the technical problem in the prior art that the operations in the above processes are relatively cumbersome because the processor module in the existing satellite system cannot make the process of the scheduling application sending a data information request to the bus management application - the process of the bus management application sending a data information request to the target device - the process of the target device sending the data information to the bus management application - the process of the bus management application sending the data information of the target device to the telemetry application highly unified.

[0007] According to one aspect of an embodiment of the present disclosure, a method for downlinking data based on a bus management application is provided, which is applied to a satellite system. The satellite system includes a scheduling application, a bus management application, and a telemetry application, wherein the scheduling application is bidirectionally communicated with the bus management application, and the bus management application is bidirectionally communicated with the telemetry application. The scheduling application is connected to the telemetry application, including: the scheduling application sends a data request packet corresponding to a target device to the bus management application, wherein the data request packet is used to indicate information corresponding to the target device; the bus management application responds to the data request packet and converts the data request packet into a data request frame according to a preset device node information table, wherein the device node information table is used to indicate node information of the target device; the target device responds to the data request frame and generates a data response packet, wherein the data response packet is used to indicate data information of the target device; the bus management application generates a data response frame according to the data response packet and sends the data response frame to the telemetry application; and the telemetry application converts the received data response frame into a data response packet and downlinks the data response packet to the ground system.

[0008] According to another aspect of the embodiments of the present disclosure, a storage medium is further provided, the storage medium including a stored program, wherein when the program is run, a processor executes any one of the above methods.

[0009] According to another aspect of an embodiment of the present disclosure, a method for downlinking data based on a bus management application is also provided, which is applied to a satellite system. The satellite system includes a scheduling application, a bus management application and a telemetry application, wherein the scheduling application is bidirectionally connected to the bus management application for communication, and the bus management application is bidirectionally connected to the telemetry application for communication, and the scheduling application is connected to the telemetry application, including: a data request packet sending module, used to send a data request packet corresponding to a target device to the bus management application, wherein the data request packet is used to indicate information corresponding to the target device; a data frame conversion module, used to respond to the data request packet and convert the data request packet into a data request frame according to a preset device node information table, wherein the device node information table is used to indicate node information of the target device; a response packet generation module, used to respond to the data request frame and generate a data response packet, wherein the data response packet is used to indicate data information of the target device; a response frame generation module, used to generate a data response frame according to the data response packet, and send the data response frame to the telemetry application; and a response packet downlink module, used to convert the received data response frame into a data response packet, and downlink the data response packet to the ground system.

[0010] According to another aspect of an embodiment of the present disclosure, a device based on downlink data of a bus management application is also provided, which is applied to a satellite system. The satellite system includes a scheduling application, a bus management application and a telemetry application, wherein the scheduling application is bidirectionally communicated with the bus management application, and the bus management application is bidirectionally communicated with the telemetry application, and the scheduling application is connected to the telemetry application. The device includes: a processor; and a memory connected to the processor, which is used to provide the processor with instructions for processing the following processing steps: the scheduling application sends a data request packet corresponding to a target device to the bus management application, wherein the data request packet is used to indicate information corresponding to the target device; the bus management application responds to the data request packet and converts the data request packet into a data request frame according to a preset device node information table, wherein the device node information table is used to indicate node information of the target device; the target device responds to the data request frame and generates a data response packet, wherein the data response packet is used to indicate data information of the target device; the bus management application generates a data response frame according to the data response packet and sends the data response frame to the telemetry application; and the telemetry application converts the received data response frame into a data response packet and downlinks the data response packet to the ground system.

[0011] This application discloses a method for downlinking data based on a bus management application. First, a scheduling application sends a data request packet corresponding to a target device to the bus management application. Then, the bus management application responds to the data request packet and converts the data request packet into a data request frame based on a preset device node information table. In addition, the target device responds to the data request frame and generates a data response packet. Furthermore, the bus management application generates a data response frame based on the data response packet and sends the data response frame to the telemetry application. Finally, the telemetry application converts the received data response frame into a data response packet and downlinks the data response packet to the ground system.

[0012] Because in the technical solution disclosed herein, when the scheduling application sends a data request packet corresponding to the target device to the bus management application, the bus management application converts the data request packet into a data request frame corresponding to the target device according to the preset device node information table. Therefore, the preset device node information table can combine the process of data information request with the process of bus communication (i.e., the process of the scheduling application sending a data request packet to the bus management application and the process of the bus management application converting the data request packet into a data request frame), thereby making the above-mentioned data request process and data conversion process highly unified. And because when the target device sends a data response packet to the bus management application, the bus management application can convert the data response packet into a data response frame according to the preset device node information table. Therefore, the preset device node information table can combine the process of data information response with the process of bus communication (i.e., the process of the target device sending a data response packet to the bus management application and the process of the bus management application converting the data response packet into a data response frame), thereby making the above-mentioned data response process and data conversion process highly unified. Thus, through the above operations, the process of the scheduling application sending a data information request to the bus management application, the process of the bus management application sending a data information request to the target device, the process of the target device sending data information to the bus management application, and the process of the bus management application sending the data information of the target device to the telemetry application is highly unified, thereby simplifying the operations in the above processes. This further solves the technical problem in the prior art that the processor modules in existing satellite systems cannot highly unify the process of the scheduling application sending a data information request to the bus management application, the process of the bus management application sending a data information request to the target device, the process of the target device sending data information to the bus management application, and the process of the bus management application sending the data information of the target device to the telemetry application, thereby making the operations in the above processes relatively cumbersome. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The drawings described herein are used to provide a further understanding of the present disclosure and constitute a part of this application. The illustrative embodiments of the present disclosure and their descriptions are used to explain the present disclosure and do not constitute an improper limitation of the present disclosure. In the drawings:

[0014] Figure 1 is a schematic diagram of a satellite remote control and telemetry system according to the first aspect of the disclosed embodiment 1;

[0015] Figure 2A is a schematic diagram of the hardware architecture of the satellite system according to the first aspect of Embodiment 1 of the present disclosure;

[0016] Figure 2B is a schematic diagram of the hardware architecture of the ground system according to the first aspect of embodiment 1 of the present disclosure;

[0017] Figure 3 is a schematic diagram of a satellite system downlinking data information of a target device to a ground system according to the first aspect of Embodiment 1 of the present disclosure;

[0018] Figure 4 is a schematic diagram of a first processor module and a target device according to the first aspect of embodiment 1 of the present disclosure;

[0019] Figure 5 This is a schematic diagram of the information flow of the bus management application according to the first aspect of Embodiment 1 of the present disclosure;

[0020] Figure 6 This is a flowchart of a method for managing application downlink data based on a bus according to the first aspect of Embodiment 1 of the present disclosure;

[0021] Figure 7 This is a schematic diagram of the process according to the first aspect of Embodiment 1 of the present disclosure in which a scheduling application sends a data request packet to a bus management application, the bus management application sends a data request frame to a target device, the target device sends a data response packet to the bus management application, and the bus management application sends a data response frame to a telemetry application.

[0022] Figure 8 is a schematic diagram of the data structure of a data request packet according to the first aspect of embodiment 1 of the present disclosure;

[0023] Figure 9 Schematic diagram of a data request packet, a device node information table, and a data request frame according to the first aspect of embodiment 1 of the present disclosure;

[0024] Figure 10 This is a schematic diagram of the data structure of a data response packet sent by a target device to a bus management application according to the first aspect of Embodiment 1 of the present disclosure;

[0025] Figure 11 2 is a schematic diagram of the data structure of a data response frame according to the first aspect of embodiment 1 of the present disclosure;

[0026] Figure 12 This is a schematic diagram of the data structure of a data response packet generated by the telemetry application according to the first aspect of embodiment 1 of the present disclosure based on the data response frame;

[0027] Figure 13 This is a flowchart of a method for a satellite system to downlink a telemetry packet corresponding to a target device to a ground system according to the first aspect of Embodiment 1 of the present disclosure;

[0028] Figure 14This is a flowchart of a method for a satellite system to downlink an inspection packet corresponding to a target device to a ground system according to the first aspect of Embodiment 1 of the present disclosure;

[0029] Figure 15 This is a flowchart of a method for a satellite system to downlink a query packet corresponding to a target device to a ground system according to the first aspect of embodiment 1 of the present disclosure;

[0030] Figure 16 is a schematic diagram of an apparatus for managing application downlink data based on a bus according to the first aspect of embodiment 2 of the present disclosure; and

[0031] Figure 17 It is a schematic diagram of a device for managing application downlink data based on a bus according to the first aspect of embodiment 3 of the present disclosure. DETAILED DESCRIPTION

[0032] In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present disclosure.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0034] Example 1

[0035] According to this embodiment, a method is provided, wherein it should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0036] Figure 1A schematic diagram of a satellite remote control and telemetry system according to this embodiment is shown. The system includes a ground system 20 and a satellite system 10. The ground system 20 transmits remote control application data to the satellite system 10 via a remote control channel between the ground system 20 and the satellite system 10 using packet telemetry. Furthermore, the satellite system 10 receives the remote control application data transmitted by the ground system 20 and transmits telemetry data to the ground system 20 via the telemetry channel between the satellite system 10 and the ground system 20 using packet telemetry.

[0037] Figure 2A It further shows Figure 1 Schematic diagram of the hardware architecture of the satellite system 10. Figure 2A As shown, the satellite system 10 includes an integrated electronic system, which includes: a processor, a memory, a bus management module and a communication interface. The memory is connected to the processor, so that the processor can access the memory, read the program instructions stored in the memory, read data from the memory or write data to the memory. The bus management module is connected to the processor and is also connected to a bus such as a CAN bus. The processor can communicate with the onboard equipment connected to the bus through the bus managed by the bus management module. In addition, the processor is also connected to devices such as cameras, star sensors, measurement and control transponders, and data transmission equipment via the communication interface. It can be understood by those skilled in the art that Figure 2A The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 2A More or fewer components than shown, or with Figure 2A Different configurations shown.

[0038] Figure 2B It further shows Figure 1 Schematic diagram of the hardware architecture of the ground system 20. Figure 2B As shown, the ground system 20 may include one or more processors (the processor may include but is not limited to a microprocessor MCU or a programmable logic device FPGA, etc.), a memory for storing data, a transmission device for communication functions, and an input / output interface. The memory, transmission device, and input / output interface are connected to the processor via a bus. In addition, it may also include: a display, a keyboard, and a cursor control device connected to the input / output interface. It will be understood by those skilled in the art that Figure 2B The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 2B More or fewer components than shown, or with Figure 2B Different configurations shown.

[0039] It should be noted that Figure 2A and Figure 2B The one or more processors and / or other data processing circuits shown in the figure may generally be referred to herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuitry may be a single independent processing module, or may be fully or partially integrated into any of the other components of the computing device. As involved in the embodiments of the present disclosure, the data processing circuitry acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0040] Figure 2A and Figure 2B The memory shown in the figure can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the configuration information-based telemetry method in the embodiment of the present disclosure. The processor executes the software programs and modules stored in the memory to perform various functional applications and data processing, that is, to implement the configuration information-based telemetry method of the above-mentioned application. The memory may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.

[0041] It should be noted that, in some optional embodiments, the above Figure 2A and Figure 2B The devices shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of both hardware and software elements. Figure 2A and Figure 2B This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the apparatus described above.

[0042] Figure 3 FIG2 shows a schematic diagram of the satellite system 10 according to an embodiment of the present application downlinking data information of a target device to the ground system 20. Figure 3 As shown, the satellite system 10 transmits data corresponding to a target device to the ground system 20 via telemetry downlink. Furthermore, the satellite system 10 includes a first processor module 110. The first processor module 110 includes a bus management application, a scheduling application, a telemetry application, and multiple devices 1-n. Multiple devices 1-n are bidirectionally connected to the bus management application, which is in turn bidirectionally connected to the scheduling application, and bidirectionally connected to the telemetry application. Furthermore, the scheduling application is in communication with the telemetry application. Furthermore, the telemetry application can downlink data corresponding to the target device to the ground system 20.

[0043] Figure 41 is a schematic diagram of the first processor module 110 and the target device according to an embodiment of the present application. Figure 4 As shown, the first processor module 110 is provided with a first data interface for transmitting data information, a bus management application, a scheduling application, and a telemetry application. The target device is provided with a second data interface for transmitting data information, a second processor module, and multiple applications 1-m. Furthermore, the first data interface in the first processor module 110 is connected to the second data interface in the target device. That is, the first processor module 110 can send data information to the target device via the first and second data interfaces, and the target device can send data information to the first processor module 110 via the second and first data interfaces.

[0044] Figure 5 This is a schematic diagram of the information flow of the bus management application according to the embodiment of the present application. Figure 5 As shown, the bus management application includes an internal bus and an external bus. The internal bus connects devices within satellite system 10, while the external bus connects devices outside of satellite system 10. The internal bus connects to the CPU, while the external bus connects to the FPGA. The CPU and FPGA each have a bidirectional communication connection. For example, the power management module, GNSS module, analog and OC module, power driver module, and motor module within satellite system 10 each have a bidirectional communication connection to the internal bus. The electric propulsion, PCDU, and transponder outside satellite system 10 each have a bidirectional communication connection to the external bus.

[0045] In the above operating environment, according to the first aspect of this embodiment, a method for managing application downlink data based on a bus is provided. For example, Figure 1 and the first processor module 110 in FIG. 2 . Figure 6 A schematic diagram of the process is shown in FIG. Figure 6 As shown, the method includes:

[0046] S602: Reading the temperature values of each thermal sensor corresponding to different calibration moments within the calibration period;

[0047] S604: Determine, based on the temperature values of the thermal sensors corresponding to different calibration moments within the calibration period, a first thermal sensor and a second thermal sensor that meet the requirements at the selected moment among the plurality of thermal sensors;

[0048] S606: Acquire a first measured temperature value of the first thermal sensor and a second measured temperature value of the second thermal sensor corresponding to different measurement moments within a measurement period, and determine a first corrected temperature value corresponding to the first thermal sensor and a second corrected temperature value corresponding to the second thermal sensor based on the first measured temperature value and the second measured temperature value;

[0049] S608: Fusing the first corrected temperature value and the second corrected temperature value to obtain a fused temperature value; and

[0050] S610: Controlling the heater to be turned on and off according to the fusion temperature value.

[0051] Specifically, Figure 7 This is a schematic diagram of the scheduling application sending a data request packet to the bus management application according to an embodiment of the present application - the bus management application sends a data request frame to the target device - the target device sends a data response packet to the bus management application - the bus management application sends a data response frame to the telemetry application. Figure 3 、 Figure 4 and Figure 7 As shown, the first processor module 110 includes a scheduling application, a bus management application, and a telemetry application. The scheduling application is bidirectionally connected to the bus management application, the bus management application is bidirectionally connected to the telemetry application, and the scheduling application and the telemetry application are interconnected.

[0052] Furthermore, each of the multiple devices is provided with a second data interface for transmitting data information, and the first processor module 110 is provided with a first data interface for transmitting data information. The first processor module 110 can send data information to the target device through the first data interface and the second data interface, and the target device can send data information to the first processor module 110 through the second data interface and the first data interface.

[0053] In addition, it is worth noting that the bus management application is also provided with a request processing thread for processing data information requests and a receiving thread for processing response data information.

[0054] Based on the above description, the scheduling application first sends a data request packet corresponding to the target device to the request processing thread in the bus management application (S602). The data request packet corresponding to the target device is used to indicate information corresponding to the target device. The information corresponding to the target device can be, for example, the name of the target device and the name of the application in the requested target device.

[0055] Specifically, Figure 8 This is a schematic diagram of the data structure of the data request packet corresponding to the target device according to the embodiment of the present application. Figure 8As shown in the figure, a complete data request packet includes a header and a data field. The header includes packet identification, packet sequence control, and packet length. The data field includes a sub-header, parameters, and an error field. It is worth noting that the sub-header in the data field is used to indicate the name of the target device, while the parameters in the data field are used to indicate the name of the application in the requested target device. For example, the name of the target device indicated in the sub-header is the GNSS module, and the name of the application in the GNSS module indicated in the parameters is the power management application and the health monitoring application.

[0056] Then, the bus management application responds to the data request packet corresponding to the target device and converts the data request packet into a data request frame according to a preset device node information table (S604), wherein the device node information table is used to indicate the node information of the target device.

[0057] Specifically, a device node information table corresponding to each of the multiple devices is pre-set within the bus management application. This device node information table can be, for example, a configuration file pre-set by a staff member through an upload. The bus management application can convert the data request packet into a data request frame based on the device node information table. Figure 9 1 is a schematic diagram of a data request packet, a device node information table, and a data request frame according to an embodiment of the present application. Table 1 shows the names of the device node information table and the meanings corresponding to each name.

[0058] Table 1

[0059]

[0060]

[0061] refer to Figure 9 As shown in Table 1, the device node information table includes the name information of the target device, and the target device name information in the device node information table corresponds to the target device name information in the data request packet. In addition, the device node information table also includes the A-machine identifier, a request data table, and a telemetry data table. The request data table indicates the number and names of applications in the target device corresponding to requests such as regular telemetry packets, query packets, and inspection packets. For example, Table 2 shows the request data table corresponding to the target device.

[0062] Table 2

[0063] quantity 2 Application Name Power management applications Health monitoring applications Data frame length 16 bits 32 bits

[0064] As shown in Reference Table 2, the number of applications in the target device requested in the data request table is 2, the names of the applications in the target device requested are power management application and health monitoring application, the data frame length of the requested power management application is 16 bits, and the data frame length of the requested health monitoring application is 32 bits.

[0065] Further, refer to Figure 9 As shown, the data structure of the data request frame includes a frame start, an arbitration segment, a control segment, a data segment, an ORC segment, an ACK segment, and a frame end. Among them, the A machine identifier in the device node information table corresponds to the arbitration segment ID in the data request frame. The arbitration segment ID is used to indicate the name information of the target device. And wherein, different arbitration segment IDs also have different priority information. For example, when the scheduling application sends a data request packet corresponding to the GNSS module and a data request packet corresponding to the motor module to the bus management application at the same time. And the priority of the arbitration segment ID for the GNSS module is greater than the priority of the arbitration segment ID for the motor module. Then, the bus management application first responds to the data request packet corresponding to the GNSS module, and converts the data request packet corresponding to the GNSS module into a data request frame corresponding to the GNSS module. Then, the bus management application responds to the data request packet corresponding to the motor module, and converts the data request packet corresponding to the motor module into a data request frame corresponding to the motor module.

[0066] In addition, the data segment of the data request frame is used to indicate the name information of the application in the requested target device, and the name information used to indicate the application in the requested target device in the data request frame corresponds to the name information used to indicate the application in the requested target device in the data request packet.

[0067] The bus management application then broadcasts a data request frame corresponding to the target device to multiple devices. However, because the data request frame includes an arbitration segment ID, which indicates the name of the corresponding target device, the target device among the multiple devices receives the data request frame corresponding to the arbitration segment ID. While other devices receive the data request frame, because the arbitration segment ID indicates the name of the corresponding target device, they do not respond to the data request frame.

[0068] Furthermore, the target device responds to the data request frame corresponding to the target device sent by the bus management application and generates a data response packet (S606). The data response packet is used to indicate the data information corresponding to the target device, that is, the data information of the application in the target device requested by the data request packet. Figure 10This is a schematic diagram of the data structure of a data response packet sent by a target device to a bus management application according to an embodiment of the present application. Figure 10 As shown in the figure, a data response packet consists of a header and a data field. The header includes packet identification, packet sequence control, and packet length. The data field contains data and an error field. The data in the data field includes the name information corresponding to the application. It is also worth noting that the data in the data field is n × 16 bits long. This provides the necessary foundation for the bus management application to generate a data response frame based on the data response packet.

[0069] In addition, the bus management application generates a data response frame according to the data response packet, and sends the data response frame to the telemetry application (S608). Figure 11 Schematic diagram of the data structure of the data response frame according to the embodiment of the present application. Figure 11 As shown, the data response frame includes a frame start, arbitration segment, control segment, data segment, ORC segment, ACK segment, and frame end. The arbitration segment ID in the data response frame corresponds to the arbitration segment ID in the data request frame. It is also worth noting that the data segment in the data request frame is 64 bits, of which the first 16 bits are the data length of the application name information. The name information of the application requested in the data request frame corresponds to the name information of the application in the data response frame. The last 48 bits are the data length of the application in the requested target device.

[0070] Finally, the telemetry application converts the received data response frame into a data response packet, and transmits the data response packet downlink to the ground system 20 ( S610 ). Figure 12 Schematic diagram of the data structure of a data response packet generated by a telemetry application according to an embodiment of the present application based on a data response frame. Figure 12 As shown, the data structure of a data response packet includes a header and a data field. The header includes packet identification, packet sequence control, and packet length. The data field includes a sub-header, parameters, and an error field. The sub-header indicates the name of the target device, and the parameters include the name of the application in the requested target device and the data corresponding to the application (i.e., the first 16 bits are the data length of the application name information, and the last 48 bits are the data length of the application in the requested target device).

[0071] As described in the background technology, since the processor module in the existing satellite system cannot make the process of the scheduling application sending a data information request to the bus management application - the process of the bus management application sending a data information request to the target device - the process of the target device sending the data information to the bus management application - the process of the bus management application sending the data information of the target device to the telemetry application highly unified, the operations in the above process are relatively cumbersome.

[0072] In view of this, in the technical solution disclosed herein, when the scheduling application sends a data request packet corresponding to the target device to the bus management application, the bus management application converts the data request packet into a data request frame corresponding to the target device according to the preset device node information table. Therefore, the preset device node information table can combine the process of data information request with the process of bus communication (i.e., the process of the scheduling application sending a data request packet to the bus management application and the process of the bus management application converting the data request packet into a data request frame), thereby making the above-mentioned data request process and data conversion process highly unified. And because when the target device sends a data response packet to the bus management application, the bus management application can convert the data response packet into a data response frame according to the preset device node information table. Therefore, the preset device node information table can combine the process of data information response with the process of bus communication (i.e., the process of the target device sending a data response packet to the bus management application and the process of the bus management application converting the data response packet into a data response frame), thereby making the above-mentioned data response process and data conversion process highly unified. Thus, through the above operations, the process of the scheduling application sending a data information request to the bus management application, the process of the bus management application sending a data information request to the target device, the process of the target device sending data information to the bus management application, and the process of the bus management application sending the data information of the target device to the telemetry application is highly unified, thereby simplifying the operations in the above processes. This further solves the technical problem in the prior art that the processor modules in existing satellite systems cannot highly unify the process of the scheduling application sending a data information request to the bus management application, the process of the bus management application sending a data information request to the target device, the process of the target device sending data information to the bus management application, and the process of the bus management application sending the data information of the target device to the telemetry application, thereby making the operations in the above processes relatively cumbersome.

[0073] Optionally, the bus management application responds to the data request packet and converts the data request packet into a data request frame according to a preset device node information table, including: the bus management application parses the data request packet, and obtains the name information of the target device, and determines the device node information table corresponding to the target device according to the name of the target device; the bus management application determines a first message frame identifier according to the name of the target device and the device node information table, wherein the first message frame identifier corresponds to the name of the target device; and the bus management application parses the data request packet, obtains the first application identifier, and generates a corresponding data request frame according to the first message frame identifier and the first application identifier, wherein the first application identifier is used to indicate the name information of the application in the target device to be requested.

[0074] Specifically, first, the bus management application parses the data request packet corresponding to the target device and parses out the name information of the target device. For example, the bus management application parses out the name information of the target device as a GNSS module. Then, the bus management application determines the corresponding device node information table based on the parsed name information of the target device. For example, refer to Figure 9 As shown, the "target device name" is set in the target device node information table.

[0075] Furthermore, after the bus management application finds the device node information table corresponding to the target device, it determines the arbitration segment ID (i.e., the first message frame identifier). Figure 9 As shown, the bus management application determines the corresponding device node information table according to the name information of the target device. The device node information table includes the A machine identifier, which is the name information of the target device.

[0076] Furthermore, after parsing the data request packet, the bus management application obtains the name information of the application in the requested target device. The name information of the application in the requested target device is set in the parameters of the data request packet. For example, the name information of the application in the requested target device parsed by the bus management application is the power management application and the health monitoring application.

[0077] The bus management application then generates a corresponding data request frame based on the target device's name information (i.e., the first message frame identifier) and the name information of the application in the requested target device (i.e., the first application identifier). Specifically, the bus management application generates an arbitration segment ID based on the target device's name information and a data segment based on the name information of the application in the requested target device.

[0078] Thus, the bus management application converts the data request packet corresponding to the target device into the data request frame corresponding to the target device according to the preset device node information table, thereby achieving the technical effect of being able to combine the process of the scheduling application sending the data request packet to the bus management application with the process of the bus management application generating the data request frame based on the data request packet, thereby providing the necessary basis for the bus management application to send the data request frame to the target device.

[0079] Optionally, the bus management application generates a data response frame based on the data response packet and sends the data response frame to the telemetry application, including: the bus management application parses the second message frame identifier in the data response frame and determines whether the second message frame identifier exists in the device node information table, wherein the first message frame identifier corresponds to the second message frame identifier; if the second message frame identifier exists in the device node information table, determines whether the second application identifier exists in the device node information table; and if the second message frame identifier does not exist in the device node information table, stops sending the data response frame. Further optionally, if the second message frame identifier exists in the device node information table, the operation of determining whether the second application identifier exists in the device node information table includes: if the second application identifier exists in the device node information table, sends the data response frame to the telemetry application; and if the second application identifier does not exist in the device node information table, stops sending the data response frame.

[0080] Specifically, because the bus management application broadcasts the data request frame to the target device, each of the multiple devices can actually receive the data request frame. However, because the data request frame contains the name information corresponding to the target device and the name information corresponding to the application in the requested target device, only the target device and its corresponding application will respond to the data request frame. However, to prevent response failures from devices other than the target device (i.e., non-target devices also responding to the data request frame), the bus management application needs to further determine whether the data response frame sent to the telemetry application is the data response frame corresponding to the target device.

[0081] In addition, in order to prevent response failures of other applications except the application in the requested target device (that is, non-requested applications also respond to the data request frame), the bus management application needs to further determine whether the data response frame sent to the telemetry application is a data response frame corresponding to the application in the requested target device.

[0082] First, after receiving a data response packet sent by the target device, the bus management application generates a corresponding data response frame based on the data response packet. The bus management application then needs to further determine whether the target device's name information (i.e., the second message frame identifier) exists in the device node information table. If the target device's name information exists in the device node information table (i.e., the data response frame is consistent with the data response packet sent by the target device), the bus management application further determines whether the name information of the application in the requested target device exists in the device node information table. If the target device's name information does not exist in the device node information table, the bus management application stops sending the data response frame.

[0083] For example, the bus management application sends a data request frame to the target device containing the GNSS module as the target device name. However, after converting the data response packet into a data response frame and evaluating the response frame, the bus management application discovers that the device name in the response frame is a motor module. The bus management application determines that the responding device name does not exist in the device node information table and therefore stops sending the data response frame.

[0084] Furthermore, after the bus management application determines that the device name information in the data response frame exists in the device node information table, it further determines whether the name information of the application in the requested target device exists in the device node information table. If the name information of the application in the requested target device exists in the device node information table, the data response frame is sent to the telemetry application; if the name information of the application in the requested target device does not exist in the device node information table, the sending of the data response frame is stopped.

[0085] For example, the bus management application sends a data request frame to the target device containing the target device's name as a GNSS module, and the applications in the target device being requested are a power management application and a health monitoring application. However, the bus management application converts the data response packet into a data response frame and, after verifying the data response frame, discovers that the device name in the data response frame is a GNSS module, but the application name in the data response frame is a time management application. The bus management application determines that the responding application's name does not exist in the device node information table, and therefore stops sending the data response frame.

[0086] Thus, the bus management application achieves the technical effect of ensuring that the ground system 20 receives accurate data information by determining whether the name information of the device in the data response frame exists in the device node information table (that is, whether the name information of the device in the data response frame is consistent with the name information of the target device), and determining whether the name information of the application in the data response frame exists in the device node information table (that is, whether the name information of the application in the data response frame is consistent with the name information of the requested application).

[0087] Optionally, it also includes: the scheduling application sends a regular telemetry request packet corresponding to the target device to the bus management application, wherein the regular telemetry request packet is used to indicate the regular telemetry information corresponding to the target device; the bus management application responds to the regular telemetry request packet and converts the regular telemetry request packet into a regular telemetry request frame according to the device node information table; the target device responds to the regular telemetry request frame and generates a regular telemetry response packet, wherein the regular telemetry response packet is used to indicate the regular telemetry data information of the target device; the bus management application generates a regular telemetry response frame based on the regular telemetry response packet and sends the regular telemetry response frame to the telemetry application; and the telemetry application converts the received regular telemetry response frame into a regular telemetry response packet and downlinks the regular telemetry response packet to the ground system.

[0088] Specifically, Figure 13 1 is a flow chart of a method for the satellite system 10 to downlink a telemetry packet corresponding to a target device to the ground system 20 according to an embodiment of the present application. Figure 13 As shown, the scheduling application periodically sends a regular telemetry request packet corresponding to the target device to the request processing thread in the bus management application. Then, the request processing thread in the bus management application converts the regular telemetry request packet into a regular telemetry request frame according to the device node information table.

[0089] Furthermore, the request processing thread in the bus management application sends a regular telemetry request frame corresponding to the target device to the target device. The target device responds to the regular telemetry request frame by generating a regular telemetry response packet. The regular telemetry response packet includes regular telemetry data information of the application in the target device requested by the scheduling application.

[0090] In addition, the receiving thread in the bus management application generates a regular telemetry response frame according to the regular telemetry response packet, and sends the regular telemetry response frame to the telemetry application.

[0091] Finally, the telemetry application converts the received conventional telemetry response frame into a conventional telemetry response packet, and transmits the conventional telemetry response packet downlink to the ground system 20 .

[0092] Thus, through the above operations, the satellite system 10 can periodically downlink the data information of the application in the requested target device to the ground system 20.

[0093] Optionally, it also includes: the scheduling application sends a patrol request packet corresponding to the target device to the bus management application, wherein the patrol request packet is used to indicate the patrol information corresponding to the target device; the bus management application responds to the patrol request packet and converts the patrol request packet into a patrol request frame according to the device node information table; the target device responds to the patrol request frame and generates a patrol response packet, wherein the patrol response packet is used to indicate the patrol data information of the target device; the bus management application generates a patrol response frame based on the patrol response packet; and the bus management application performs health diagnosis on the patrol response frame.

[0094] Specifically, Figure 14 1 is a flow chart of a method for the satellite system 10 to transmit an inspection packet corresponding to a target device to the ground system 20 according to an embodiment of the present application. Figure 14 As shown, the scheduling application periodically sends a patrol request packet corresponding to the target device to the request processing thread in the bus management application. Then, the request processing thread in the bus management application converts the patrol request packet into a patrol request frame according to the device node information table.

[0095] Furthermore, the request processing thread in the bus management application sends a patrol request frame corresponding to the target device to the target device, and the target device generates a patrol response packet in response to the patrol request frame, wherein the patrol response packet includes the patrol data information of the application in the target device requested by the scheduling application.

[0096] In addition, the receiving thread in the bus management application generates a patrol response frame based on the patrol response packet, and performs health diagnosis on the target device based on the patrol response frame.

[0097] Therefore, the above operation achieves the technical effect of being able to timely determine whether the target device has a fault and ensure that the target device can be used normally.

[0098] Optionally, it also includes: the telemetry application sends a query request packet corresponding to the target device to the bus management application, wherein the query request packet is used to indicate the query telemetry information corresponding to the target device; the bus management application responds to the query request packet and converts the query request packet into a query request frame according to the device node information table; the target device responds to the query request frame and generates a query response packet, wherein the query response packet is used to indicate the query telemetry data information of the target device; the bus management application generates a query response frame based on the query response packet and sends the query response frame to the telemetry application; and the telemetry application converts the received query response frame into a query response packet and downlinks the query response packet to the ground system.

[0099] Specifically, Figure 15 FIG. 1 is a flow chart of a method for the satellite system 10 to downlink a query packet corresponding to a target device to the ground system 20 according to an embodiment of the present application. Figure 15 As shown, the scheduling application sends a query request packet corresponding to the target device to the request processing thread in the bus management application. Then, the request processing thread in the bus management application converts the query request packet into a query request frame according to the device node information table.

[0100] Furthermore, the request processing thread in the bus management application sends a query request frame corresponding to the target device to the target device, and the target device generates a query response packet in response to the query request frame, wherein the query response packet includes the query data information of the application in the target device requested by the scheduling application.

[0101] In addition, the receiving thread in the bus management application generates a query response frame according to the query response packet, and sends the query response frame to the telemetry application.

[0102] Finally, the telemetry application converts the received query response frame into a query response packet and transmits the query response packet downlink to the ground system 20 .

[0103] Thus, through the above operations, the technical effect is achieved that the satellite system 10 can downlink the data information of the application in the target device requested by the ground system 20 to the ground system 20.

[0104] In the technical solution disclosed herein, when the scheduling application sends a data request packet corresponding to the target device to the bus management application, the bus management application converts the data request packet into a data request frame corresponding to the target device according to the preset device node information table. Therefore, the preset device node information table can combine the process of data information request with the process of bus communication (i.e., the process of the scheduling application sending a data request packet to the bus management application and the process of the bus management application converting the data request packet into a data request frame), thereby making the above-mentioned data request process and data conversion process highly unified. Furthermore, since when the target device sends a data response packet to the bus management application, the bus management application can convert the data response packet into a data response frame according to the preset device node information table. Therefore, the preset device node information table can combine the process of data information response with the process of bus communication (i.e., the process of the target device sending a data response packet to the bus management application and the process of the bus management application converting the data response packet into a data response frame), thereby making the above-mentioned data response process and data conversion process highly unified. Thus, through the above operations, the process of the scheduling application sending a data information request to the bus management application, the process of the bus management application sending a data information request to the target device, the process of the target device sending data information to the bus management application, and the process of the bus management application sending the data information of the target device to the telemetry application is highly unified, thereby simplifying the operations in the above processes. This further solves the technical problem in the prior art that the processor modules in existing satellite systems cannot highly unify the process of the scheduling application sending a data information request to the bus management application, the process of the bus management application sending a data information request to the target device, the process of the target device sending data information to the bus management application, and the process of the bus management application sending the data information of the target device to the telemetry application, thereby making the operations in the above processes relatively cumbersome.

[0105] Furthermore, according to a third aspect of this embodiment, a storage medium is provided, wherein the storage medium includes a stored program, wherein when the program is run, a processor executes any one of the above methods.

[0106] Thus, according to this embodiment, the process of the scheduling application sending a data information request to the bus management application, the bus management application sending a data information request to the target device, the target device sending data information to the bus management application, and the bus management application sending the target device's data information to the telemetry application is highly unified, thereby simplifying the operations in the above processes. This further solves the technical problem in the prior art that the processor modules in existing satellite systems cannot highly unify the process of the scheduling application sending a data information request to the bus management application, the bus management application sending a data information request to the target device, the target device sending data information to the bus management application, and the bus management application sending the target device's data information to the telemetry application, thereby making the operations in the above processes relatively cumbersome.

[0107] It should be noted that for the aforementioned method embodiments, for simplicity of description, they are all expressed as a series of action combinations. However, those skilled in the art should be aware that the present invention is not limited by the order of the actions described, because according to the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

[0108] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0109] Example 2

[0110] Figure 16 FIG1 shows an apparatus 1600 for managing application downlink data based on a bus according to the first aspect of this embodiment. The apparatus 1600 corresponds to the method according to the first aspect of embodiment 1. Figure 16As shown, the device 1600 includes: a data request packet sending module 1610, used to send a data request packet corresponding to the target device to the bus management application, wherein the data request packet is used to indicate information corresponding to the target device; a data frame conversion module 1620, used to respond to the data request packet and convert the data request packet into a data request frame according to a preset device node information table, wherein the device node information table is used to indicate the node information of the target device; a response packet generation module 1630, used to respond to the data request frame and generate a data response packet, wherein the data response packet is used to indicate the data information of the target device; a response frame generation module 1640, used to generate a data response frame according to the data response packet, and send the data response frame to the telemetry application; and a response packet downlink module 1650, used to convert the received data response frame into a data response packet, and downlink the data response packet to the ground system.

[0111] Optionally, the data frame conversion module 1620 includes: a device node information table determination module, used to parse the data request packet, parse out the name information of the target device, and determine the device node information table corresponding to the target device based on the name information of the target device; a first message frame identifier determination module, used to determine the first message frame identifier based on the name information of the target device and the device node information table, wherein the first message frame identifier corresponds to the name information of the target device; and a data request frame generation submodule, used to parse the data request packet, parse out the first application identifier, and generate a corresponding data request frame based on the first message frame identifier and the first application identifier, wherein the first application identifier is used to indicate the name information of the application in the requested target device.

[0112] Optionally, the response frame generation module 1640 includes: a first determination module, used to parse out the second message frame identifier in the data response frame, and determine whether the second message frame identifier exists in the device node information table, wherein the first message frame identifier corresponds to the second message frame identifier; a second determination module, used to determine whether the second application identifier exists in the device node information table when the second message frame identifier exists in the device node information table; and a first stop sending module, used to stop sending the data response frame when the second message frame identifier does not exist in the device node information table.

[0113] Optionally, the second determination module includes: a data response frame sending module, used to send the data response frame to the telemetry application when the second application identifier exists in the device node information table; and a second stop module, used to stop sending the data response frame when the second application identifier does not exist in the device node information table.

[0114] Optionally, the device 1600 also includes: a conventional telemetry packet request module, which is used to send a conventional telemetry request packet corresponding to the target device to the bus management application, wherein the conventional telemetry request packet is used to indicate conventional telemetry information corresponding to the target device; a first conversion module, which is used to respond to the conventional telemetry request packet and convert the conventional telemetry request packet into a conventional telemetry request frame according to the device node information table; a conventional telemetry response packet generation module, which is used to respond to the conventional telemetry request frame and generate a conventional telemetry response packet, wherein the conventional telemetry response packet is used to indicate conventional telemetry data information of the target device; a conventional telemetry response frame generation module, which is used for the bus management application to generate a conventional telemetry response frame according to the conventional telemetry response packet, and send the conventional telemetry response frame to the telemetry application; and a first downlink module, which is used to convert the received conventional telemetry response frame into a conventional telemetry response packet, and downlink the conventional telemetry response packet to the ground system.

[0115] Optionally, the device 1600 also includes: a patrol report request module, which is used to send a patrol request packet corresponding to the target device to the bus management application, wherein the patrol request packet is used to indicate the patrol information corresponding to the target device; a second conversion module, which is used for the bus management application to respond to the patrol request packet and convert the patrol request packet into a patrol request frame according to the device node information table; a patrol response packet generation module, which is used to respond to the patrol request frame and generate a patrol response packet, wherein the patrol response packet is used to indicate the patrol data information of the target device; a patrol response frame generation module, which is used to generate a patrol response frame based on the patrol response packet; and a health diagnosis module, which is used to perform health diagnosis on the patrol response frame.

[0116] Optionally, the device 1600 also includes: a query packet request module, which is used to send a query request packet corresponding to the target device to the bus management application, wherein the query request packet is used to indicate the query information corresponding to the target device; a third conversion module, which is used to apply the response to the query request packet and convert the query request packet into a query request frame according to the device node information table; a query response packet generation module, which is used to respond to the query request frame and generate a query response packet, wherein the query response packet is used to indicate the query data information of the target device; a query response frame generation module, which is used to generate a query response frame based on the query response packet and send the query response frame to the telemetry application; and a second downlink module, which is used to convert the received query response frame into a query response packet and downlink the query response packet to the ground system.

[0117] Thus, according to this embodiment, the process of the scheduling application sending a data information request to the bus management application, the bus management application sending a data information request to the target device, the target device sending data information to the bus management application, and the bus management application sending the target device's data information to the telemetry application is highly unified, thereby simplifying the operations in the above processes. This further solves the technical problem in the prior art that the processor modules in existing satellite systems cannot highly unify the process of the scheduling application sending a data information request to the bus management application, the bus management application sending a data information request to the target device, the target device sending data information to the bus management application, and the bus management application sending the target device's data information to the telemetry application, thereby making the operations in the above processes relatively cumbersome.

[0118] Example 3

[0119] Figure 17 FIG1 shows an apparatus 1700 for managing application downlink data based on a bus according to the first aspect of this embodiment. The apparatus 1700 corresponds to the method according to the first aspect of embodiment 1. Figure 17 As shown, the device 1700 includes: a processor 1710; and a memory 1720, which is connected to the processor 1710 and is used to provide instructions for the processor 1710 to process the following processing steps: sending a data request packet corresponding to the target device to the bus management application, wherein the data request packet is used to indicate information corresponding to the target device; responding to the data request packet and converting the data request packet into a data request frame according to a preset device node information table, wherein the device node information table is used to indicate node information of the target device; responding to the data request frame and generating a data response packet, wherein the data response packet is used to indicate data information of the target device; generating a data response frame according to the data response packet, and sending the data response frame to the telemetry application; and converting the received data response frame into a data response packet, and downlinking the data response packet to the ground system.

[0120] Thus, according to this embodiment, the process of the scheduling application sending a data information request to the bus management application, the bus management application sending a data information request to the target device, the target device sending data information to the bus management application, and the bus management application sending the target device's data information to the telemetry application is highly unified, thereby simplifying the operations in the above processes. This further solves the technical problem in the prior art that the processor modules in existing satellite systems cannot highly unify the process of the scheduling application sending a data information request to the bus management application, the bus management application sending a data information request to the target device, the target device sending data information to the bus management application, and the bus management application sending the target device's data information to the telemetry application, thereby making the operations in the above processes relatively cumbersome.

[0121] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0122] In the above embodiments of the present invention, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0123] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0124] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0125] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0126] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc. Various media that can store program codes.

[0127] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. A method for downlinking data based on a bus management application, applied to a satellite system, wherein the satellite system includes a scheduling application, a bus management application, and a telemetry application, wherein the scheduling application is bidirectionally connected to the bus management application, the bus management application is bidirectionally connected to the telemetry application, and the scheduling application is connected to the telemetry application, characterized in that: include: The scheduling application sends a data request packet corresponding to the target device to the bus management application, wherein the data request packet is used to indicate information corresponding to the target device; The bus management application responds to the data request packet and converts the data request packet into a data request frame according to a preset device node information table, wherein the device node information table is used to indicate the node information of the target device. The bus management application responds to the data request packet and converts the data request packet into a data request frame according to the preset device node information table, including: The bus management application parses the data request packet to obtain the name information of the target device, and determines a device node information table corresponding to the target device according to the name information of the target device; The bus management application determines a first message frame identifier according to the name information of the target device and the device node information table, wherein the first message frame identifier corresponds to the name information of the target device; and The bus management application parses the data request packet to obtain a first application identifier, and generates a corresponding data request frame according to the first message frame identifier and the first application identifier, wherein the first application identifier is used to indicate name information of an application in the requested target device; The target device responds to the data request frame and generates a data response packet, wherein the data response packet is used to indicate data information of the target device; The bus management application generates a data response frame according to the data response packet, and sends the data response frame to the telemetry application; and The telemetry application converts the received data response frame into the data response packet and transmits the data response packet downlink to the ground system.

2. The method according to claim 1, characterized in that The bus management application generates a data response frame according to the data response packet and sends the data response frame to the telemetry application, including: The bus management application parses the second message frame identifier in the data response frame and determines whether the second message frame identifier exists in the device node information table, wherein the first message frame identifier corresponds to the second message frame identifier; If the second message frame identifier exists in the device node information table, determining whether the second application identifier exists in the device node information table; and If the second message frame identifier does not exist in the device node information table, then the sending of the data response frame is stopped.

3. The method according to claim 2, characterized in that When the second message frame identifier exists in the device node information table, the operation of determining whether the second application identifier exists in the device node information table includes: If the second application identifier exists in the device node information table, sending the data response frame to the telemetry application; and If the second application identifier does not exist in the device node information table, then the sending of the data response frame is stopped.

4. The method according to claim 1, wherein Also includes: The scheduling application sends a regular telemetry request packet corresponding to the target device to the bus management application, wherein the regular telemetry request packet is used to indicate regular telemetry information corresponding to the target device; The bus management application responds to the conventional telemetry request packet and converts the conventional telemetry request packet into a conventional telemetry request frame according to the device node information table; The target device responds to the conventional telemetry request frame and generates a conventional telemetry response packet, wherein the conventional telemetry response packet is used to indicate conventional telemetry data information of the target device; The bus management application generates a conventional telemetry response frame according to the conventional telemetry response packet, and sends the conventional telemetry response frame to the telemetry application; as well as The telemetry application converts the received conventional telemetry response frame into the conventional telemetry response packet, and transmits the conventional telemetry response packet downlink to the ground system.

5. The method according to claim 1, wherein Also includes: The scheduling application sends a patrol request packet corresponding to the target device to the bus management application, wherein the patrol request packet is used to indicate patrol information corresponding to the target device; The bus management application responds to the patrol request packet and converts the patrol request packet into a patrol request frame according to the device node information table; The target device responds to the inspection request frame and generates an inspection response packet, wherein the inspection response packet is used to indicate the inspection data information of the target device; The bus management application generates a patrol response frame according to the patrol response packet; as well as The bus management application performs health diagnosis on the patrol response frame.

6. The method according to claim 1, characterized in that Also includes: The telemetry application sends a query request packet corresponding to the target device to the bus management application, wherein the query request packet is used to indicate query information corresponding to the target device; The bus management application responds to the query request packet and converts the query request packet into a query request frame according to the device node information table; The target device responds to the query request frame and generates a query response packet, wherein the query response packet is used to indicate the query data information of the target device; The bus management application generates a query response frame according to the query response packet, and sends the query response frame to the telemetry application; as well as The telemetry application converts the received query response frame into the query response packet, and transmits the query response packet downlink to the ground system.

7. A storage medium, characterized in that: The storage medium includes a stored program, wherein when the program is run, the processor executes the method according to any one of claims 1 to 6.

8. A device for downlinking data based on a bus management application, applied to a satellite system, the satellite system comprising a scheduling application, a bus management application, and a telemetry application, wherein the scheduling application is bidirectionally connected to the bus management application, the bus management application is bidirectionally connected to the telemetry application, and the scheduling application is connected to the telemetry application, characterized in that: include: a data request packet sending module, configured to send a data request packet corresponding to a target device to a bus management application, wherein the data request packet is used to indicate information corresponding to the target device; a data frame conversion module, configured to respond to the data request packet and convert the data request packet into a data request frame according to a preset device node information table, wherein the device node information table is used to indicate the node information of the target device, wherein the data frame conversion module includes: a device node information table determination module, configured to parse the data request packet, parse out the name information of the target device, and determine the device node information table corresponding to the target device according to the name information of the target device; a first message frame identifier determining module, configured to determine a first message frame identifier according to the name information of the target device and the device node information table, wherein the first message frame identifier corresponds to the name information of the target device; and a data request frame generating submodule, configured to parse the data request packet to obtain a first application identifier, and generate a corresponding data request frame according to the first message frame identifier and the first application identifier, wherein the first application identifier is used to indicate name information of an application in the requested target device; a response packet generating module, configured to respond to the data request frame and generate a data response packet, wherein the data response packet is used to indicate data information of the target device; a response frame generation module, configured to generate a data response frame according to the data response packet, and send the data response frame to the telemetry application; and The response packet downlink module is used to convert the received data response frame into the data response packet and downlink the data response packet to the ground system.

9. A device for downlinking data based on a bus management application, applied to a satellite system, the satellite system comprising a scheduling application, a bus management application, and a telemetry application, wherein the scheduling application is bidirectionally connected to the bus management application, the bus management application is bidirectionally connected to the telemetry application, and the scheduling application is connected to the telemetry application, characterized in that: include: processor; as well as A memory, connected to the processor, configured to provide the processor with instructions for processing the following processing steps: The scheduling application sends a data request packet corresponding to the target device to the bus management application, wherein the data request packet is used to indicate information corresponding to the target device; The bus management application responds to the data request packet and converts the data request packet into a data request frame according to a preset device node information table, wherein the device node information table is used to indicate the node information of the target device. The bus management application responds to the data request packet and converts the data request packet into a data request frame according to the preset device node information table, including: The bus management application parses the data request packet to obtain the name information of the target device, and determines a device node information table corresponding to the target device according to the name information of the target device; The bus management application determines a first message frame identifier according to the name information of the target device and the device node information table, wherein the first message frame identifier corresponds to the name information of the target device; and The bus management application parses the data request packet to obtain a first application identifier, and generates a corresponding data request frame according to the first message frame identifier and the first application identifier, wherein the first application identifier is used to indicate name information of an application in the requested target device; The target device responds to the data request frame and generates a data response packet, wherein the data response packet is used to indicate data information of the target device; The bus management application generates a data response frame according to the data response packet, and sends the data response frame to the telemetry application; and The telemetry application converts the received data response frame into the data response packet and transmits the data response packet downlink to the ground system.

Images