Space target orbit prediction data retrieval method, device, equipment and medium
Through the Lucene toolkit, the space target ephemeris data is created, and the target number and time are used as the search keywords, the problem of inefficient search of spatial target orbit prediction results in the existing technology is solved, and efficient data retrieval is achieved.
Patent Information
- Application Number
- CN202210611821.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-05-31
- Publication Date
- 2025-02-21
- Estimated Expiration
- 2042-05-31
AI Technical Summary
When predicting spatial target tracks, the efficiency of retrieving massive track forecast results is very inefficient, and all files need to be traversed and meaninglessly compared.
Through the open source full-text search engine toolkit Lucene, a toolkit for open source, create an index of the file content of the target ephemeris data, and search data in the file content with the target number and time as the search keywords.
It realizes no need to traverse all files and meaningless comparison operations, which reduces the retrieval complexity, improves the running speed, and greatly improves the retrieval efficiency.
Smart Images

Figure CN114936263B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer technology and can be used in the field of aerospace technology, and in particular to a method, device, equipment and medium for retrieving space target orbit prediction data. Background Art
[0002] According to the statistical model, there are about 34,000 fragments larger than 10 cm in orbit, about 900,000 fragments between 1 cm and 10 cm, and more than 120 million fragments between 1 mm and 1 cm. When predicting the orbit of a space target, it is necessary to calculate the ephemeris data of the space target at the specified forecast time interval within the forecast period according to the orbital parameters of the space target. The ephemeris data of the space target mainly includes: time, position and speed, etc. Since the total amount of data is proportional to the number of targets, the forecast time interval and the number of forecast time intervals, if the ephemeris data for a large number of space targets is calculated within a period of time, a large amount of results will be generated. In the prior art, multiple "loops" are nested to retrieve the orbit prediction results of space targets. Each retrieval operation requires traversing all files, and there are multiple loops and meaningless comparison operations, which is very inefficient. Therefore, how to scientifically manage and quickly retrieve the massive orbit prediction results of a large number of space targets is a problem that technicians in this field need to solve urgently. Summary of the invention
[0003] In view of the above technical problems, the first aspect of the present disclosure provides a method for retrieving space target orbit prediction data, comprising: predicting the space target ephemeris data within a specified time period according to the orbital parameters of the space target; extracting the file content of the space target ephemeris data; creating an index for the file content through the open source full-text search engine toolkit Lucene; based on the index, using the target number and time as search keywords, performing data retrieval in the file content to obtain the ephemeris data of the specified target number at the specified time.
[0004] According to an embodiment of the present disclosure, extracting the file content of the space target ephemeris data specifically includes: calling a parse() method to parse the space target ephemeris data to extract the file content.
[0005] According to an embodiment of the present disclosure, an index is created for file content through the open source full-text search engine toolkit Lucene, specifically including: constructing an entity class and setting a first member variable and a second member variable for the entity class, wherein the first member variable is used to store a title corresponding to the file content, and the first member variable is used to store the file content; constructing a Java class, adding a first static method and a second static method to the Java class, wherein the first static method is used to list all files under the indexed directory, and the second static method is used to use the file content corresponding to all files.
[0006] According to an embodiment of the present disclosure, data retrieval is performed in the file content based on the index with the target number and time as search keywords, specifically including: using multiMatchQuery and calling the first static method to search in the file content according to the target number and time, and finding the ephemeris data of the specified target number at the specified time; calling the second static method to place the ephemeris data of the specified target number at the specified time in the request scope.
[0007] According to an embodiment of the present disclosure, obtaining the ephemeris data of the specified target number at the specified time includes: calling a getAttribute() method to obtain the ephemeris data of the specified target number at the specified time from a request scope.
[0008] According to an embodiment of the present disclosure, the method further includes: creating an index for the file content through a search engine server Solr or a search engine server ElasticSearch.
[0009] According to an embodiment of the present disclosure, the first member variable and the second member variable are member variables of String type.
[0010] The second aspect of the present disclosure provides a retrieval device for space target orbit prediction data, including: a prediction module, used to predict the space target ephemeris data within a specified time period according to the orbital parameters of the space target; an extraction module, used to extract the file content of the space target ephemeris data; a creation module, used to create an index for the file content through the open source full-text search engine toolkit Lucene; a retrieval module, used to perform data retrieval in the file content based on the index, using the target number and time as retrieval keywords, and obtain the ephemeris data of the specified target number at the specified time.
[0011] A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the above method.
[0012] A fourth aspect of the present disclosure provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enables the processor to implement the above method.
[0013] The space target orbit prediction data retrieval method, device, equipment and medium provided by the embodiments of the present disclosure can at least achieve the following technical effects:
[0014] By using Lucene to index the data, data can be retrieved from the file content based on the index and using the target number and time as search keywords. There is no need to traverse all files or perform meaningless comparison operations. The retrieval complexity is low and the running speed is fast, which greatly improves the retrieval efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:
[0016] Figure 1 The flowchart of the method for retrieving orbit prediction data of a space target according to an embodiment of the present disclosure is schematically shown.
[0017] Figure 2 A block diagram of a device for retrieving orbit prediction data of a space target according to an embodiment of the present invention is schematically shown.
[0018] Figure 3 A block diagram of an electronic device suitable for implementing the method described above according to an embodiment of the present invention is schematically shown. DETAILED DESCRIPTION
[0019] In order to make the purpose, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present disclosure.
[0020] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.
[0021] In the present disclosure, unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", "fixed" and the like should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection, an electrical connection, or can communicate with each other; it can be a direct connection, or it can be indirectly connected through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present disclosure can be understood according to specific circumstances.
[0022] In the description of the present disclosure, it is necessary to understand that the terms "longitudinal", "length", "circumferential", "front", "rear", "left", "right", "top", "bottom", "inside", "outside", etc., indicating the orientation or positional relationship, are based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing the present disclosure and simplifying the description, and do not indicate or imply that the subsystem or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present disclosure.
[0023] Throughout the drawings, the same elements are represented by the same or similar reference numerals. Conventional structures or configurations will be omitted when they may cause confusion in the understanding of the present disclosure. The shapes, sizes, and positional relationships of the components in the drawings do not reflect the actual size, proportion, and actual positional relationship. In addition, in the present disclosure, any reference symbol between brackets should not be constructed as a limitation to the present disclosure.
[0024] Similarly, in order to simplify the present disclosure and help understand one or more of the various disclosed aspects, in the above description of the exemplary embodiments of the present disclosure, the various features of the present disclosure are sometimes grouped together into a single embodiment, figure, or description thereof. The description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" and the like means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.
[0025] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the feature. In the description of the present disclosure, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.
[0026] In view of the problem in the prior art that the ephemeris data of each space target needs to be cyclically compared, which is extremely inefficient and time-consuming, the disclosed embodiment provides a method for retrieving space target orbit forecast data, including: forecasting the space target ephemeris data within a specified time period based on the orbital parameters of the space target. Extracting the file content of the space target ephemeris data. Creating an index for the file content through the open source full-text search engine toolkit Lucene. Based on the index, using the target number and time as search keywords, perform data retrieval in the file content to obtain the ephemeris data of the specified target number at the specified time. The following is a detailed introduction in conjunction with specific embodiments.
[0027] Figure 1 The flowchart of the method for retrieving orbit prediction data of a space target according to an embodiment of the present disclosure is schematically shown.
[0028] like Figure 1 As shown, the method for retrieving space target orbit prediction data may include, for example, operations S101 to S104.
[0029] In operation S101, ephemeris data of a space target within a specified time period is predicted according to the orbital parameters of the space target.
[0030] In one embodiment of the present disclosure, the space target ephemeris data is predicted, and the two-line orbit data (Two-Line Element, TLE) which is the most widely used space target catalog element release form is used, which can be downloaded from websites such as Space Track and CelesTrak. In order to ensure the calculation accuracy, the models and software such as SGP4, SDP4, GP4, SGP8, PPT2, PPT3, HANDE, SALT, SP and SST released by the North American Aerospace Defense Command (NORAD) are usually used to calculate the position and velocity vector of the space target and obtain the orbit parameters of the space target.
[0031] In operation S102, the file content of the space object ephemeris data is extracted.
[0032] In an embodiment of the present disclosure, Tika can be used to extract the content of the space target ephemeris data file. Specifically, the parse() method is called to parse the space target ephemeris data and traverse the space target ephemeris data file content.
[0033] In operation S103, an index is created for the file content using the open source full-text search engine toolkit Lucene.
[0034] In an embodiment of the present disclosure, the process of creating an index may include, for example:
[0035] Construct an entity class, and set a first member variable and a second member variable for the entity class, wherein the first member variable is used to store the title corresponding to the file content, and the second member variable is used to store the file content. In addition, a setter method and a getter method are provided for the entity class. The first member variable and the second member variable can be member variables of the String type. For example, the title can be generated using the target number and time.
[0036] Construct a Java class, and add a first static method and a second static method in the Java class, wherein the first static method is used to list all files under the indexed directory, and the second static method is used to extract the file contents corresponding to all files using Tika.
[0037] It should be noted that the embodiments of the present disclosure can also create indexes for file contents through the search engine server Solr or the search engine server ElasticSearch. The search engine server Solr or the search engine server ElasticSearch is an index creation technology similar to the full-text search engine toolkit Lucene. The core of both is based on the full-text search engine toolkit Lucene, but they are optimized and packaged in a targeted manner according to different application scenarios, and both can achieve similar effects as the full-text search engine toolkit Lucene. Therefore, in actual applications, the method of creating an index can be selected according to the actual application scenario, and the present disclosure does not limit it.
[0038] In operation S104, based on the index, the target number and time are used as search keywords to perform data search in the file content to obtain the ephemeris data of the specified target number at the specified time.
[0039] In an embodiment of the present disclosure, based on the index, with the target number and time as search keywords, data retrieval in the file content may include, for example: first, using multiMatchQuery and calling the first static method to search in the file content according to the fields corresponding to the target number and time, and find the ephemeris data of the specified target number at the specified time. Then, calling the second static method to place the ephemeris data of the specified target number at the specified time in the request scope.
[0040] In an embodiment of the present disclosure, obtaining the ephemeris data of the specified target number at the specified time may include, for example: calling a getAttribute() method to obtain the ephemeris data of the specified target number at the specified time from a request scope.
[0041] According to the data retrieval method provided by the embodiment of the present disclosure, by using Lucene to index the data, based on the index, using the target number and time as the search keywords, data retrieval is performed in the file content, and there is no need to traverse all files, as well as meaningless comparison operations. The retrieval complexity is low, the running speed is fast, and the retrieval efficiency is greatly improved. Especially in the space target simulation scenario, when it is necessary to retrieve the massive data generated by tens of thousands of targets per second, the high efficiency advantage of the data retrieval method provided by the embodiment of the present disclosure is more prominent. In addition, the data retrieval method has good compatibility, simple operation, and easy engineering implementation, and can be better applied to the field of aerospace technology.
[0042] Figure 2 A block diagram of a device for retrieving orbit prediction data of a space target according to an embodiment of the present invention is schematically shown.
[0043] like Figure 2 As shown, the device 200 for retrieving space target orbit prediction data may include a prediction module 210 , an extraction module 220 , a creation module 230 and a retrieval module 240 .
[0044] The prediction module 210 is used to predict the ephemeris data of the space target within a specified time period according to the orbital parameters of the space target.
[0045] The extraction module 220 is used to extract the file content of the space target ephemeris data.
[0046] The creation module 230 is used to create an index for the file content through the open source full-text search engine toolkit Lucene.
[0047] The search module 240 is used to search for data in the file content based on the index, using the target number and time as search keywords, and obtain the ephemeris data of the specified target number at the specified time.
[0048] According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits, or at least part of the functions of any one of them can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be at least partially implemented as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, systems on packages, application specific integrated circuits (ASICs), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging the circuit, or by any one of the three implementation methods of software, hardware, and firmware, or by a suitable combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, submodules, units, and subunits can be at least partially implemented as computer program modules, and when the computer program modules are run, the corresponding functions can be performed.
[0049] For example, any multiple of the forecast module 210, the extraction module 220, the creation module 230 and the retrieval module 240 can be combined in one module / unit / subunit for implementation, or any one of the modules / units / subunits can be split into multiple modules / units / subunits. Alternatively, at least part of the functions of one or more of these modules / units / subunits can be combined with at least part of the functions of other modules / units / subunits and implemented in one module / unit / subunit. According to an embodiment of the present invention, at least one of the forecast module 210, the extraction module 220, the creation module 230 and the retrieval module 240 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation modes of software, hardware and firmware or in a suitable combination of any of them. Alternatively, at least one of the forecasting module 210 , the extracting module 220 , the creating module 230 , and the retrieving module 240 may be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function may be performed.
[0050] It should be noted that the retrieval device part of the space target orbit prediction data in the embodiment of the present invention corresponds to the retrieval method part of the space target orbit prediction data in the embodiment of the present invention, and their specific implementation details and the technical effects brought about are also the same, which will not be repeated here.
[0051] Figure 3A block diagram of an electronic device suitable for implementing the method described above according to an embodiment of the present invention is schematically shown. Figure 3 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.
[0052] like Figure 3 As shown, the electronic device 300 according to an embodiment of the present invention includes a processor 301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 302 or a program loaded from a storage part 308 into a random access memory (RAM) 303. The processor 301 may, for example, include a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 301 may also include an onboard memory for caching purposes. The processor 301 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present invention.
[0053] In RAM 303, various programs and data required for the operation of electronic device 300 are stored. Processor 301, ROM 302 and RAM 303 are connected to each other via bus 304. Processor 301 performs various operations of the method flow according to an embodiment of the present invention by executing the programs in ROM 302 and / or RAM 303. It should be noted that the program can also be stored in one or more memories other than ROM 302 and RAM 303. Processor 301 can also perform various operations of the method flow according to an embodiment of the present invention by executing the programs stored in the one or more memories.
[0054] According to an embodiment of the present invention, the electronic device 300 may further include an input / output (I / O) interface 305, which is also connected to the bus 304. The electronic device 300 may further include one or more of the following components connected to the I / O interface 305: an input portion 306 including a keyboard, a mouse, etc.; an output portion 307 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 308 including a hard disk, etc.; and a communication portion 309 including a network interface card such as a LAN card, a modem, etc. The communication portion 309 performs communication processing via a network such as the Internet. A drive 310 is also connected to the I / O interface 305 as needed. A removable medium 311, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 310 as needed, so that a computer program read therefrom is installed into the storage portion 308 as needed.
[0055] According to an embodiment of the present invention, the method flow according to an embodiment of the present invention can be implemented as a computer software program. For example, an embodiment of the present invention includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 309, and / or installed from the removable medium 311. When the computer program is executed by the processor 301, the above-mentioned functions defined in the system of the embodiment of the present invention are executed. According to an embodiment of the present invention, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.
[0056] The present invention also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiment; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present invention is implemented.
[0057] According to an embodiment of the present invention, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device.
[0058] For example, according to an embodiment of the present invention, the computer-readable storage medium may include the ROM 302 and / or the RAM 303 described above and / or one or more memories other than the ROM 302 and the RAM 303 .
[0059] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present invention. In this regard, each box in the flowchart or block diagram may represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box may also occur in an order different from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions. It can be understood by those skilled in the art that the features recorded in the various embodiments of the present invention can be combined and / or combined in various ways, even if such a combination or combination is not explicitly recorded in the present invention. In particular, without departing from the spirit and teachings of the present invention, the features recorded in the various embodiments of the present invention can be combined and / or combined in various ways. All these combinations and / or combinations fall within the scope of the present invention.
Claims
1. A method for retrieving space target orbit prediction data, characterized in that: include: According to the orbital parameters of the space target, the ephemeris data of the space target within the specified time period is predicted; Extracting the file content of the space target ephemeris data; The file content is indexed by using an open source full-text search engine toolkit Lucene, including: constructing an entity class and setting a first member variable and a second member variable for the entity class, wherein the first member variable is used to store a title corresponding to the file content, and the first member variable is used to store the file content; constructing a Java class, and adding a first static method and a second static method to the Java class, wherein the first static method is used to list all files under the index directory, and the second static method is used to use the file content corresponding to all files; Based on the index, using the target number and time as search keywords, data retrieval is performed in the file content, including: using multiMatchQuery and calling the first static method to search the file content according to the target number and time, and find the ephemeris data of the specified target number at the specified time; calling the second static method to place the ephemeris data of the specified target number at the specified time in the request scope; Obtaining the ephemeris data of the specified target number at the specified time includes: calling a getAttribute() method to obtain the ephemeris data of the specified target number at the specified time from the request scope.
2. The search method according to claim 1, characterized in that: The extracting of the file content of the space target ephemeris data specifically includes: The parse() method is called to parse the space target ephemeris data to extract the file content.
3. The search method according to claim 1, characterized in that: The method further comprises: An index is created for the file content through a search engine server Solr or a search engine server ElasticSearch.
4. The search method according to claim 1, characterized in that: The first member variable and the second member variable are member variables of String type.
5. A device for retrieving space target orbit prediction data, used to execute the method according to any one of claims 1 to 4, characterized in that: include: A prediction module is used to predict the ephemeris data of the space target within a specified time period according to the orbital parameters of the space target; An extraction module, used to extract the file content of the space target ephemeris data; Creating a module for creating an index for the file content through an open source full-text search engine toolkit Lucene; The retrieval module is used to perform data retrieval in the file content based on the index, using the target number and time as retrieval keywords, and obtain the ephemeris data of the specified target number at the specified time.
6. An electronic device, characterized in that: include: one or more processors; a memory 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 4.
7. A computer-readable storage medium, characterized in that: Executable instructions are stored thereon, and when the instructions are executed by a processor, the processor implements the method according to any one of claims 1 to 4.
Citation Information
Patent Citations
Optical disk library full-text retrieval system based on Lucene
CN106055546A
Full-text retrieval method and system
CN108255972A