Satellite data transmission file upload drag and drop componentization method, system, device and medium

Abstract

The present invention relates to the field of computer vision technology, and provides a satellite data transmission file upload drag componentization method, system, device and medium, which solves the technical problem of how to quickly and efficiently realize spacecraft data transmission operations in the prior art. The method includes: after triggering the configuration requirements for satellite data transmission file upload, receiving newly added endpoint information; displaying a visual operation interface of the data transmission link in the aerospace system; confirming the dragging of components in the public component library area to the drag operation area and the execution order between components in the drag operation area; receiving the configuration information of the data transmission endpoint input in the basic information configuration area during transmission; verifying the configuration information to confirm that the data transmission link is complete; and saving the configured data transmission link to the database.

Description

Technical Field

[0001] The present invention relates to the field of spacecraft data transmission technology, and in particular to a satellite data transmission file upload drag componentization method, system, equipment and medium. Background Art

[0002] With the rapid increase in the number of spacecraft, satellites in orbit and the demand for satellite users, especially after the satellite performs data transmission payload operations, how to quickly and efficiently transmit data transmission files to users has become an industry pain point. Traditional file upload methods usually rely on standard file selection dialog boxes, which are not only inefficient but also provide poor user experience. In order to improve the user experience, drag-and-drop component upload technology came into being. By running program code, each node in the transmission link can be monitored and configured. It allows users to upload satellite data transmission files by dragging and arranging files and creating file transfer processes. Achieve more intuitive and smooth operation.

[0003] The existing technical solutions mainly rely on HTML5's drag-and-drop API and file API. HTML5's drag-and-drop API allows users to drag and drop files to a specified area on a web page, while the file API provides the ability to access, read, and process the dragged and dropped files. These technologies together support the front-end to implement the local drag-and-drop upload function of files, and allow JavaScript to process files, such as previewing, verifying, and uploading.

[0004] The existing technology also has some shortcomings. First, for large file uploads, the performance and stability of the drag component may be affected, especially when the network environment is unstable. Although componentized design improves the maintainability of the code, it may require a large amount of custom configuration to implement complex functions, which increases the difficulty of development and maintenance. In addition, when processing large amounts of satellite data transmission files, the limitations of the front-end browser on memory and processing power may cause performance bottlenecks and affect the user experience. Finally, the existing technology also needs to be strengthened in terms of security, such as preventing malicious file uploads and data leakage.

[0005] Therefore, when selecting and implementing the drag-and-drop upload component, you need to comprehensively consider performance, maintainability, and security to meet the needs of specific application scenarios. Summary of the invention

[0006] The purpose of the present invention is to provide a satellite data transmission file upload drag componentization method, system, device and medium, which are used to solve the technical problem of how to quickly and efficiently realize spacecraft data transmission operations in the prior art.

[0007] To solve the above technical problems, as one aspect of the present invention, a satellite data transmission file upload drag componentization method is provided, comprising the following steps:

[0008] After triggering the configuration requirement of satellite data transmission file upload, receiving the newly added endpoint information;

[0009] A visual operation interface for displaying a data transmission link in an aerospace system; wherein the visual operation interface includes a basic information configuration area and a drawing board area for a satellite data transmission file; the drawing board area includes a public component library area and a drag operation area; the public component library area includes a data transmission task start component, a data transmission task end component and a data transmission node component; the data transmission node component includes a data transmission node component corresponding to the newly added endpoint information;

[0010] Confirming the dragging of components in the public component library area to the drag operation area and the execution order between components in the drag operation area;

[0011] Receiving the configuration information of the data transmission endpoint during transmission inputted in the basic information configuration area;

[0012] Verify configuration information to confirm that the data transmission link is complete;

[0013] Save the configured data transmission link to the database.

[0014] Further, after triggering the configuration requirement of satellite data transmission file upload, receiving the newly added endpoint information includes:

[0015] After triggering the configuration requirements for satellite data transmission file upload, confirm the newly added endpoint server type;

[0016] According to the newly added endpoint server type, the corresponding input page is displayed in the aerospace system for inputting endpoint information;

[0017] Receives input endpoint information.

[0018] Further, the confirming that the component in the public component library area is dragged to the drag operation area includes:

[0019] After a data transmission node component exists in the drag operation area, receiving a signal to trigger an editing endpoint;

[0020] Display the input box of the corresponding data transmission node component to enter the endpoint configuration field;

[0021] Receiving and verifying the endpoint configuration field;

[0022] After passing the verification, close the input box.

[0023] Further, the confirming the execution order between components in the drag operation area includes:

[0024] The execution order of the data transmission node components is confirmed according to the numbers corresponding to the execution order contained in the endpoint configuration field.

[0025] Further, the confirming the execution order between components in the drag operation area includes:

[0026] Confirm that the data transmission task start component, the data transmission task end component and the data transmission node component in the drag operation area are all connected end to end through a single arrow connection line; wherein the arrow of the single arrow connection line points to the next component that performs the data transmission task;

[0027] According to the single-arrow connection lines between the components in the drag operation area, the execution order between the components in the drag operation area is confirmed.

[0028] Furthermore, when the endpoint server type is an FTP server, the endpoint information that needs to be entered on the input page includes at least the endpoint name, protocol type, detection switch, detection source, priority, FTP address information, FTP port, FTP user name, FTP password, FTP connection mode and encoding method, and the input box that needs to be entered as the endpoint configuration field includes at least the file path and transmission type; when the endpoint server type is an OBS server, the endpoint information that needs to be entered on the input page includes at least the endpoint name, protocol type, detection switch, detection source, priority, access key, private key and endpoint address, and the input box that needs to be entered as the endpoint configuration field includes at least the bucket name, upload method, shard size and number of threads.

[0029] Furthermore, the drawing board area also includes a drawing board toolbar; the satellite data transmission file upload drag componentization method also includes:

[0030] When a tool in the drawing board toolbar is selected, the operation corresponding to the tool is executed; wherein the operation corresponding to the tool at least includes reducing the canvas, enlarging the canvas, centering the canvas content on the adaptive canvas, retracting to the previous operation, and jumping to the next operation after retracting the previous operation.

[0031] As a second aspect of the present invention, a satellite data transmission file upload drag componentization system is provided, comprising:

[0032] A first receiving module is used to receive newly added endpoint information after triggering the configuration requirement of satellite data transmission file upload;

[0033] A display module is used to display a visual operation interface of a data transmission link in an aerospace system; wherein the visual operation interface includes a basic information configuration area and a drawing board area of ​​a satellite data transmission file; the drawing board area includes a public component library area and a drag operation area; the public component library area includes a data transmission task start component, a data transmission task end component and a data transmission node component; the data transmission node component includes a data transmission node component corresponding to the newly added endpoint information;

[0034] A confirmation module, used for confirming the dragging of components in the public component library area to the drag operation area and the execution order between components in the drag operation area;

[0035] A second receiving module, used to receive the configuration information of the data transmission endpoint input in the basic information configuration area during transmission;

[0036] A verification module is used to verify the configuration information to confirm that the data transmission link is complete;

[0037] The storage module is used to save the configured data transmission link into the database.

[0038] As a third aspect of the present invention, there is provided an electronic device, comprising:

[0039] one or more processors;

[0040] A storage device for storing one or more programs;

[0041] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in the first aspect above.

[0042] As a fourth aspect of the present invention, a computer-readable medium is provided, on which a computer program is stored, and when the program is executed by a processor, the method described in the first aspect is implemented.

[0043] The beneficial effects of the present invention are:

[0044] The present invention allows users to create data transmission links by dragging and arranging components, thereby componentizing satellite data transmission file transmission configuration links, achieving more intuitive and smooth operation, reducing manual operation and link maintenance costs, solving the technical problem of how to quickly and efficiently realize spacecraft data transmission operations in the prior art, and improving user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 The present invention schematically shows a step diagram of a satellite data transmission file upload drag-and-drop componentization method.

[0046] Figure 2A schematic diagram of an endpoint information input page is shown schematically.

[0047] Figure 3 Another schematic diagram of an endpoint information input page is shown schematically.

[0048] Figure 4 A schematic diagram of a visual operation interface is shown schematically.

[0049] Figure 5 for Figure 4 Diagram of the input endpoint configuration fields in .

[0050] Figure 6 for Figure 4 Schematic diagram of the connected components.

[0051] Figure 7 A block diagram of a satellite data transmission file upload drag-and-drop componentized system is schematically shown.

[0052] Figure 8 A block diagram of an electronic device is schematically shown.

[0053] Fig. 9 A block diagram of a computer-readable medium is schematically shown. DETAILED DESCRIPTION

[0054] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this application will be comprehensive and complete and will fully convey the concepts of the example embodiments to those skilled in the art. The same reference numerals in the figures represent the same or similar parts, and thus their repeated description will be omitted.

[0055] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0056] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0057] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0058] It should be understood that although the terms first, second, third, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another component. Therefore, the first component discussed below can be referred to as the second component without departing from the teachings of the concepts of the present application. As used herein, the term "and / or" includes any one of the associated listed items and all combinations of one or more.

[0059] Those skilled in the art will appreciate that the drawings are merely schematic diagrams of example embodiments, and the modules or processes in the drawings are not necessarily necessary for implementing the present application, and therefore cannot be used to limit the scope of protection of the present application.

[0060] According to the first specific embodiment of the present invention, Figure 1 As shown, the present invention provides a satellite data transmission file upload drag componentization method, comprising the following steps:

[0061] S11, after triggering the configuration requirement of satellite data transmission file upload, receiving the newly added endpoint information.

[0062] This application can configure components in the web page according to user needs, presenting the overall process of satellite data transmission file upload for more intuitive display and maintenance. The configuration requirement for satellite data transmission file upload can be triggered by the user selecting the option to start configuration requirements for different satellites and different satellite parties in the web page of the high-speed data transmission system of the space transportation management system. After the user selects the option to start configuration requirements, the configuration requirement for satellite data transmission file upload is triggered.

[0063] Specifically, step S11 may include the following steps:

[0064] S111, after triggering the configuration requirement of satellite data transmission file upload, confirm the newly added endpoint server type.

[0065] S112, according to the newly added endpoint server type, a corresponding input page is displayed in the aerospace system for inputting endpoint information.

[0066] S113, receiving input endpoint information.

[0067] After the user selects the option to start configuring the requirements, he can select the newly added endpoint server type. It should be noted that the data transmission node components mentioned in the following are divided into two types of data transmission node components according to the different endpoint server types, namely FTP type data transmission endpoint components and OBS type data transmission endpoint components.

[0068] Please refer to the following Figure 2 and Figure 3 , Figure 2 A schematic diagram of an endpoint information input page is shown schematically. Figure 3 Another schematic diagram of an endpoint information input page is shown schematically. Figure 2 As shown, when the endpoint server type is an FTP server, the endpoint information that needs to be entered on the input page may include endpoint name, protocol type, detection switch, detection source, priority, FTP address information, FTP port, FTP user name, FTP password, FTP connection mode, encoding method and endpoint description.

[0069] like Figure 3 As shown, when the endpoint server type is an OBS server, the endpoint information that needs to be entered on the input page may include endpoint name, protocol type, detection switch, detection source, priority, access key, private key, endpoint address, non-accelerated endpoint address and endpoint description.

[0070] After the user inputs the endpoint information, step S12 is executed.

[0071] S12, a visual operation interface for displaying data transmission links within the aerospace system.

[0072] Among them, the visual operation interface includes the basic information configuration area and the drawing board area of ​​the satellite data transmission file; the drawing board area includes the public component library area and the drag operation area; the public component library area includes the data transmission task start component, the data transmission task end component and the data transmission node component; the data transmission node component includes the data transmission node component corresponding to the newly added endpoint information. As the name implies, the data transmission task start component and the data transmission task end component respectively control the start and end operations of the data transmission task; the data transmission task starts the execution of the link process through the data transmission task start component; at the same time, the data transmission task calls the end transmission command in the database through the data transmission task end component to control the end of the data transmission task.

[0073] The specific data transmission node component that the data transmission task starts the component to flow to. The data transmission node component is divided into two types of data transmission node components according to the different server types, namely FTP type data transmission endpoint components and OBS type data transmission endpoint components. The distinction of server types is determined by the endpoint type related fields in the database.

[0074] Figure 4 A schematic diagram of a visual operation interface is shown schematically. Figure 4 As shown, the main structure of the visual operation interface is mainly divided into the following four area modules.

[0075] The upper layer of the visual operation interface is the basic information configuration area, and the basic data information configuration area is the configuration information of the satellite data transmission file when the data transmission endpoint is transmitted. The configuration information during the data transmission endpoint transmission includes: the name of the satellite data transmission file link configuration; the specified Python script used to process the satellite data transmission file; the type of site during the data transmission process, the site type includes two formats of site types, namely domestic sites and foreign sites; the device type of the monitoring site server, the device type includes measurement and control baseband, data transmission baseband and ACU; the enabled state of the satellite data transmission file link, the enabled state includes enabled and disabled states; the data transmission file file identifier, the meaning of the file identifier is to retrieve the corresponding data transmission macro file in the database according to the configured file identifier to process the file transfer. In addition, there are some other non-mandatory options, such as site name.

[0076] like Figure 4 As shown, the middle and lower layers of the visual operation interface are the drawing board area, in which you can drag and customize the data transmission components. The left side of the drawing board is the public component library area, which provides three types of components, namely, the data transmission task start component, the data transmission task end component, and the data transmission node component. Optionally, the upper layer of the public component library has a component search function box, which can fuzzily retrieve the specific component content based on the component name. The area with a light gray background in the middle of the canvas is the drag operation area, and the operator can arbitrarily drag and edit the component content in the public component area in the drag operation area.

[0077] The upper right side of the artboard area is the artboard toolbar, which includes the following five tools: shrink the canvas, enlarge the canvas, center the canvas content on the adaptive canvas, retract to the previous operation, and jump to the next operation after retracting the previous operation.

[0078] S13, confirming the dragging of components in the public component library area to the drag operation area and the execution order between components in the drag operation area.

[0079] Optionally, in step S13, confirming that the component in the public component library area is dragged to the drag operation area may include the following steps:

[0080] S131, after a data transmission node component exists in the drag operation area, receiving a signal for triggering an editing endpoint.

[0081] S132, displaying an input box corresponding to the data transmission node component to input an endpoint configuration field.

[0082] S133, receiving and verifying the endpoint configuration field.

[0083] S134, after passing the verification, close the input box.

[0084] Please refer to Figure 5 , Figure 5 for Figure 4 A diagram showing the input endpoint configuration fields in . Figure 5 As shown in the figure, the user can use the mouse to drag the data transmission node component in the public component library area of ​​the canvas to the right side of the drawing board area. Then, the user can double-click the data transmission node component to trigger the signal of editing the endpoint. After receiving the signal to trigger the editing endpoint, the system displays the input box of the corresponding data transmission node component to enter the endpoint configuration field. Figure 5 What is shown in the figure is the input box corresponding to the OBS type data transmission endpoint component. The OBS type data transmission endpoint component needs to enter the following fields in the input box: Bucket name, which means the name of the bucket registered by the OBS server; Upload method, which means the upload method of uploading files to the target endpoint OBS server. Currently, there are three upload methods to choose from, namely file streaming upload, file segment upload and file migration; segment size (bytes), which means that after selecting segment upload in the pre-upload method operation, the size of each file segment needs to be entered; and the number of threads.

[0085] If the user double-clicks an FTP type data transmission endpoint component, the following fields need to be entered in the pop-up input box: file path, which means the specific path address of the data transmission file uploaded to the FTP service; transmission type, which means the type of file upload to the target FTP server, which is fixed as streaming upload; execution order, which means the order in which the components are executed.

[0086] Double-click the data transmission node component to enter the input box. Figure 5 As shown, fill in the required fields and click the Confirm button. The input box will close automatically after verification.

[0087] There are multiple ways to confirm the execution order between components in the drag operation area in step S13, two of which are described in detail below:

[0088] The first method is to confirm the execution order of the data transmission node components according to the numbers corresponding to the execution order contained in the endpoint configuration field.

[0089] The second way is to connect the components with single arrow lines to determine the order in which the components are executed. Figure 6 , Figure 6 for Figure 4 Schematic diagram of connecting components. Figure 6 As shown, the single arrow connection line can be an auxiliary component of the data transmission component, which is used to control and record the connection sequence of the data transmission component, so as to provide feedback code to execute the execution sequence of components in the data transmission link. If the data transmission task start component, the data transmission task end component, and the data transmission node component are connected by an arrow connection line, after the component connected by the tail of the arrow completes the execution action, it will directly jump to the component pointed by the arrow and continue to execute the next component.

[0090] Confirming the execution order of the data transmission node components in a second manner may include the following steps:

[0091] S135, the data transmission task start component, the data transmission task end component and the data transmission node component in the drag operation area are connected end to end through a single arrow connection line; wherein the arrow of the single arrow connection line points to the next component that executes the data transmission task.

[0092] S136: confirming the execution order between the components in the drag operation area according to the single-arrow connection lines between the components in the drag operation area.

[0093] The logic connected by the single arrow connection line is strictly executed according to the following weights. The link execution must start from the data transmission task start component, so the execution order of the data transmission task start component is 0, and it does not need to be automatically filled; the data transmission node components (FTP type data transmission endpoint components, OBS type data transmission endpoint components) are all executed in order, and the execution order field is reserved in the component configuration item. The execution order must be greater than 1. The code recognizes that the execution order filled in the component configuration has a strong weight execution logic; if the execution order field of one of the data transmission node components is filled in empty, the arrow component connection logic with a weaker weight is executed, and the execution order of the data transmission component is determined based on the head and tail connection of the arrow components. Among them, when the execution order of the data transmission node components in the same link is consistent, the data transmission node components are executed in parallel by default. The link execution ends at the data transmission task end component, and the execution order of the data transmission task end component is n+1 (where n is the total number of data transmission components).

[0094] Use step lines to connect the components of each node, from the start component to each node, and from each node to the end component. Make sure that the connections between components are consistent with the user input configuration, and fill in all the required configurations in the configuration information area. Figure 6 shown.

[0095] After adding the data transmission task start component in the visual operation interface, the corresponding action control instructions are formed, specifically including: if the data transmission task start component appears in the current satellite data transmission link, the data transmission start receiving action control is executed at the start of the data transmission task, and the data transmission task start component executes other data transmission components in sequence thereafter until the data transmission process is completed; if the data transmission task start component does not appear in the current satellite data transmission link, this data transmission link will not be executed at the start of the data transmission task.

[0096] After adding the data transmission task end component in the visual operation interface, the corresponding action control instructions are formed, specifically including: if the data transmission task end component appears in the current satellite data transmission link, the data transmission termination action control instruction is executed at the end of the data transmission task, and the data transmission task end component terminates the data transmission operation from its completion; if the data transmission task start component does not appear in the current satellite data transmission link, this data transmission link will not be executed when the data transmission task starts.

[0097] After adding the data transmission node component in the visual operation interface, the corresponding action control instructions are formed, including: the FTP type data transmission node component executes the corresponding file transfer action through the file upload path configured by the endpoint, and executes the corresponding file upload method transmission action through the transmission type configured by the endpoint; the OBS type data transmission node component executes the file transfer action of the corresponding file upload bucket through the bucket name configured by the endpoint, and executes the corresponding file upload method transmission action through the transmission type configured by the endpoint; if the data transmission node components are connected through arrow connecting lines, after the upload action is completed according to the above type of component operation, the sequence execution operation is performed through the arrow pointing.

[0098] After confirming that the components in the common component library area are dragged to the drag operation area and the execution order between the components in the drag operation area, step S14 is executed.

[0099] S14, receiving the configuration information of the data transmission endpoint input in the basic information configuration area during transmission.

[0100] After the configuration information of the data transmission endpoint is filled in, it can be Figure 6 shown.

[0101] S15, verifying the configuration information to confirm that the data transmission link is complete.

[0102] After completing the configuration information for the user data transmission endpoint transmission, you can click the confirmation button to verify whether the data transmission link is complete. Among them, the data structure of the satellite data transmission file upload drag component can be as follows:

[0103] {"transferStrategyId":123,"transferStrategyName":"xxxx Domestic Transmission Link","fileMatchMark":"SV03-01,GJ1E,GJ1F,GJ1G,GJ1H","scriptId":21,"scriptName":"High-Speed Data Transmission - xx - File Processing","stationType":1,"nodeCode":null,"transferStrategyInfo":"[{\"endpointName\":\"YuXing Beijing Node OBS\",\"linkId\":199,\"transferStrategyId\":123,\"endpointId\":83,\"dirBucket\":\"data-distribute\",\"uploadType\":2,\"orderNum\":1,\"partSize\":1073741824,\"threadNum\":100},{\"endpointName\":\"xx0102 Star FTP\",\"linkId\":178,\"transferStrategyId\":123,\"endpointId\":65,\"dirBucket\":\" / \",\"uploadType\":1,\"orderNum\":2}]","graphData":"\"{}\"","status":1}, the transferStrategyId is the ID (i.e., the unique key) configured for the satellite data transmission file upload and drag-and-drop component, the transferStrategyName is the configuration name, the fileMatchMark is the file identifier, the scriptId is the Python script ID, the scriptName is the script name, the stationType is the station type, the nodeCode is the station code, the transferStrategyInfo is the content of the data transmission configuration link, the graphData is the set of size and position information of the component on the canvas, and the status is the configuration status.

[0104] S16, save the configured data transmission link to the database.

[0105] After the configuration is completed, this information will be saved to the database. If this configuration scheme is in the enabled state, then in subsequent file uploads, the satellite data transmission files will be uploaded through this configured link.

[0106] This application allows users to create data transmission links by dragging and arranging components, thereby componentizing satellite data transmission file transmission configuration links, achieving more intuitive and smooth operation, reducing manual operation and maintenance link costs, solving the technical problem of how to quickly and efficiently realize spacecraft data transmission operations in the prior art, and improving user experience.

[0107] According to a second specific embodiment of the present invention, the present invention provides a satellite data transmission file upload drag component system, using the method of the first specific embodiment, such as Figure 7 As shown, the satellite data transmission file upload drag component system 400 includes:

[0108] The first receiving module 410 is used to receive the newly added endpoint information after triggering the configuration requirement of satellite data transmission file upload;

[0109] Display module 420, used to display a visual operation interface of the data transmission link in the aerospace system; wherein the visual operation interface includes a basic information configuration area and a drawing board area of ​​the satellite data transmission file; the drawing board area includes a public component library area and a drag operation area; the public component library area includes a data transmission task start component, a data transmission task end component and a data transmission node component; the data transmission node component includes a data transmission node component corresponding to the newly added endpoint information;

[0110] A confirmation module 430, used to confirm the dragging of components in the public component library area to the drag operation area and the execution order between components in the drag operation area;

[0111] The second receiving module 440 is used to receive the configuration information of the data transmission endpoint input in the basic information configuration area during transmission;

[0112] Verification module 450, used to verify configuration information to confirm that the data transmission link is complete;

[0113] The storage module 460 is used to save the configured data transmission link into a database.

[0114] According to a third specific embodiment of the present invention, the present invention provides an electronic device, such as Figure 8 As shown, Figure 8 It is a block diagram of an electronic device according to an exemplary embodiment.

[0115] Refer to the following Figure 8 The electronic device 200 according to this embodiment of the present application is described. Figure 8 The electronic device 200 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0116] like Figure 8As shown, the electronic device 200 is in the form of a general computing device. The components of the electronic device 200 may include, but are not limited to: at least one processing unit 210, at least one storage unit 220, a bus 230 connecting different system components (including the storage unit 220 and the processing unit 210), a display unit 240, etc.

[0117] The storage unit stores a program code, which can be executed by the processing unit 210, so that the processing unit 210 performs the steps described in this specification according to various exemplary embodiments of the present application. For example, the processing unit 210 can perform the following steps: Figure 1 Follow the steps shown in .

[0118] The storage unit 220 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 2201 and / or a cache memory unit 2202 , and may further include a read-only memory unit (ROM) 2203 .

[0119] The storage unit 220 may also include a program / utility 2204 having a set (at least one) of program modules 2205, such program modules 2205 including but not limited to: an operating system, one or more application programs, other program modules and program data, each of which or some combination may include the implementation of a network environment.

[0120] Bus 230 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0121] The electronic device 200 may also communicate with one or more external devices 200' (e.g., keyboards, pointing devices, Bluetooth devices, etc.) so that a user can communicate with the device that interacts with the electronic device 200, and / or the electronic device 200 can communicate with any device (e.g., routers, modems, etc.) that communicates with one or more other computing devices. Such communication may be performed through an input / output (I / O) interface 250. In addition, the electronic device 200 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) through a network adapter 260. The network adapter 260 may communicate with other modules of the electronic device 200 through a bus 230. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0122] Through the description of the above implementations, those skilled in the art can easily understand that the example implementations described here can be implemented by software, or by combining software with necessary hardware.

[0123] Therefore, according to a fourth specific embodiment of the present invention, the present invention provides a computer readable medium. Fig. 9 As shown, the technical solution according to the embodiment of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes a number of instructions to enable a computing device (which can be a personal computer, a server, or a network device, etc.) to execute the above method according to the embodiment of the present invention.

[0124] The software product may be any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, a system, device or component of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0125] The computer readable storage medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The readable storage medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by an instruction execution system, an apparatus, or a device or used in combination with it. The program code contained on the readable storage medium may be transmitted with any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the above.

[0126] Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0127] The computer-readable medium carries one or more programs. When the one or more programs are executed by a device, the computer-readable medium implements the functions of the first embodiment.

[0128] Those skilled in the art will appreciate that the above modules can be distributed in the device according to the description of the embodiment, or can be changed accordingly and only used in one or more devices different from the embodiment. The modules of the above embodiments can be combined into one module, or further divided into multiple sub-modules.

[0129] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the exemplary embodiments described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the embodiment of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiment of the present invention.

[0130] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A satellite data transmission file upload drag and drop componentization method, characterized in that: The following steps are involved: After triggering the configuration requirement of satellite data transmission file upload, receiving the newly added endpoint information; A visual operation interface for displaying a data transmission link in an aerospace system; wherein the visual operation interface includes a basic information configuration area and a drawing board area for a satellite data transmission file; the drawing board area includes a public component library area and a drag operation area; the public component library area includes a data transmission task start component, a data transmission task end component and a data transmission node component; the data transmission node component includes a data transmission node component corresponding to the newly added endpoint information; Confirming the dragging of components in the public component library area to the drag operation area and the execution order between components in the drag operation area; Receiving the configuration information of the data transmission endpoint during transmission inputted in the basic information configuration area; Verify configuration information to confirm that the data transmission link is complete; Save the configured data transmission link to the database.

2. The satellite data transmission file upload drag and drop componentization method according to claim 1, characterized in that: After triggering the configuration requirement of satellite data transmission file upload, receiving the newly added endpoint information includes: After triggering the configuration requirements for satellite data transmission file upload, confirm the newly added endpoint server type; According to the newly added endpoint server type, the corresponding input page is displayed in the aerospace system for inputting endpoint information; Receives input endpoint information.

3. The satellite data transmission file upload drag and drop componentization method according to claim 2, characterized in that: The step of confirming that the component in the public component library area is dragged to the drag operation area includes: After a data transmission node component exists in the drag operation area, receiving a signal to trigger an editing endpoint; Display the input box of the corresponding data transmission node component to enter the endpoint configuration field; Receiving and verifying the endpoint configuration field; After passing the verification, close the input box.

4. The satellite data transmission file upload drag and drop componentization method according to claim 3, characterized in that: The determining the execution order between components in the drag operation area includes: The execution order of the data transmission node components is confirmed according to the numbers corresponding to the execution order contained in the endpoint configuration field.

5. The satellite data transmission file upload drag and drop componentization method according to claim 3, characterized in that: The determining the execution order between components in the drag operation area includes: Confirm that the data transmission task start component, the data transmission task end component and the data transmission node component in the drag operation area are all connected end to end through a single-arrow connecting line; wherein the arrow of the single-arrow connecting line points to the next component that performs the data transmission task; According to the single-arrow connection lines between the components in the drag operation area, the execution order between the components in the drag operation area is confirmed.

6. The satellite data transmission file upload drag and drop componentization method according to claim 3, characterized in that: When the endpoint server type is an FTP server, the endpoint information that needs to be entered on the input page includes at least the endpoint name, protocol type, detection switch, detection source, priority, FTP address information, FTP port, FTP user name, FTP password, FTP connection mode and encoding method, and the input box needs to enter the endpoint configuration field that includes at least the file path and transmission type; When the endpoint server type is an OBS server, the endpoint information that needs to be entered on the input page includes at least the endpoint name, protocol type, detection switch, detection source, priority, access key, private key and endpoint address, and the input box requires input of the endpoint configuration field that includes at least the bucket name, upload method, shard size and number of threads.

7. The satellite data transmission file upload drag-and-drop componentization method according to any one of claims 1 to 6, characterized in that: The drawing board area also includes a drawing board toolbar; the satellite data transmission file upload drag componentization method also includes: When a tool in the drawing board toolbar is selected, the operation corresponding to the tool is executed; wherein the operation corresponding to the tool at least includes reducing the canvas, enlarging the canvas, centering the canvas content on the adaptive canvas, retracting to the previous operation, and jumping to the next operation after retracting the previous operation.

8. A satellite data transmission file upload drag and drop component system, characterized in that: include: A first receiving module, used to receive newly added endpoint information after triggering the configuration requirement of satellite data transmission file upload; A display module is used to display a visual operation interface of a data transmission link in an aerospace system; wherein the visual operation interface includes a basic information configuration area and a drawing board area of ​​a satellite data transmission file; the drawing board area includes a public component library area and a drag operation area; the public component library area includes a data transmission task start component, a data transmission task end component and a data transmission node component; the data transmission node component includes a data transmission node component corresponding to the newly added endpoint information; A confirmation module, used for confirming the dragging of components in the public component library area to the drag operation area and the execution order between components in the drag operation area; A second receiving module, used to receive the configuration information of the data transmission endpoint input in the basic information configuration area during transmission; A verification module is used to verify the configuration information to confirm that the data transmission link is complete; The storage module is used to save the configured data transmission link into the database.

9. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 7.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images