JP7460824B2 - Rocket launch support device, rocket launch support method, and rocket launch support program - Google Patents

Description

The present invention relates to a rocket launch support device, a rocket launch support method, a rocket launch support program, a rocket, a rocket launch method, and a rocket launch support system.

In recent years, construction of large-scale satellite constellations ranging from hundreds to thousands of satellites, so-called mega-constellations, has begun, increasing the risk of satellite collisions in orbit. In addition, space debris such as satellites that are out of control due to malfunctions or debris from rockets is increasing.
With the rapid increase in the number of space objects such as satellites and space debris in outer space, there is an increasing need to create international rules for space traffic management (STM) to avoid collisions between space objects.

In recent years, mega-constellation operators that operate mega-constellations have appeared. The same mega-constellation operator has a plan to deploy satellites across the sky as shown below.
Orbital altitude of approximately 336km: Orbital inclination of 42 degrees, approximately 2500 aircraft Orbital altitude of approximately 341km: Orbital inclination of 48°, approximately 2500 aircraft Orbital altitude of approximately 346km: Orbital inclination of 53°, approximately 2500 aircraft Orbital altitude of approximately 550km: Orbital inclination 53 degrees, approximately 1,600 aircraft Orbit altitude approximately 1,150 km: Orbital inclination of 53 degrees, approximately 1,600 aircraft

In addition, another mega-constellation operator has announced plans to deploy a total of 3,236 satellites in the following orbits with inclinations ranging from 39 degrees to 56 degrees:
Orbital altitude of approximately 590 km: 784 rockets Orbital altitude of approximately 610 km: 1,296 rockets Orbital altitude of approximately 630 km: 1,156 rockets In addition, for example, there is a plan to develop a rocket launch site in Taiki Town, Hokkaido, Japan, which is at 42 degrees north latitude.

Patent document 1 discloses a technology for forming a satellite constellation consisting of multiple satellites in the same circular orbit.

Japanese Patent Application Publication No. 2017-114159

As mentioned above, the sky above latitudes such as 42 degrees, 48 degrees, or 53 degrees is a latitude zone where satellites forming a mega constellation are concentrated. For this reason, it is extremely difficult for rocket launch operators to avoid collisions with satellites when launching rockets.
However, Patent Document 1 does not describe any measures to avoid such collisions.

An object of the present invention is to effectively support collision avoidance between a rocket and a satellite constituting a satellite constellation during a rocket launch.

The rocket launch support device according to the present invention comprises:
a region calculation unit that calculates a possible passage region in which there is no risk of a rocket launched from the rocket launch site colliding with a satellite constellation passing above the rocket launch site, based on satellite orbit forecast information in which a predicted value of a satellite orbit is set; and
and a region notification unit that outputs the possible pass region.

The rocket launch support device according to the present invention has the effect of effectively supporting collision avoidance between a rocket and a satellite that constitutes a satellite constellation during rocket launch.

An example of multiple satellites working together to provide communication services throughout the Earth. An example of multiple satellites in a single orbit providing Earth observation services. An example of a satellite constellation with multiple orbital planes that intersect near the polar regions. Example of a satellite constellation with multiple orbital planes that intersect outside the polar regions. A diagram showing the configuration of a satellite constellation formation system. A configuration diagram of the satellites of the satellite constellation formation system. A diagram showing the configuration of the ground equipment for the satellite constellation formation system. An example of the functional configuration of a satellite constellation formation system. An example of a satellite constellation near 42 degrees north latitude. FIG. 1 is a configuration diagram of a rocket launch support device according to a first embodiment. FIG. 3 is a diagram showing an example of satellite orbit forecast information according to the first embodiment. FIG. 2 is an image diagram of a rocket launch according to the first embodiment. FIG. 3 is a flowchart of rocket launch support processing by the rocket launch support device according to the first embodiment. FIG. 2 is a diagram showing an example of launching a rocket straight up according to the first embodiment. FIG. 1 is a diagram showing an example of launching a rocket in an oblique direction according to the first embodiment. FIG. 13 is a diagram showing an example of a passable time region in which a prediction error is expected in the first embodiment. 5A and 5B are diagrams showing display example 1 and display example 2 of a passable time region according to the first embodiment. FIG. 11 is a diagram showing a third display example of a passable time region according to the first embodiment. FIG. 3 is a diagram showing the configuration of a rocket launch support device according to a modification of the first embodiment. FIG. 2 is a configuration diagram of a rocket launch support device according to a second embodiment. FIG. 11 is a flow diagram of rocket launch support processing by the rocket launch support device according to the second embodiment. Satellite flight image near orbit altitude 340km. A diagram showing an example of a satellite constellation near an orbit altitude of 340 km. A diagram showing an example of a rocket launch. FIG. 7 is a diagram showing an example of a relative distance A between a rocket and another space object, which is an index of a flight safety area according to a modification of the first embodiment. 7 is a diagram showing an example of a relative distance B between a rocket and another space object, which is an index of a collision risk area according to a modification of the first embodiment. FIG. FIG. 13 is a diagram showing a state in which a flight safety area is not secured in a modified example of the first embodiment. FIG. 13 is a diagram showing the state of the launch window depending on the size of the error range in the modified example of the first embodiment.

The following describes an embodiment of the present invention with reference to the drawings. In each drawing, the same or corresponding parts are given the same reference numerals. In the description of the embodiment, the description of the same or corresponding parts will be omitted or simplified as appropriate. In addition, the size relationship of each component in the drawings may differ from the actual one. In the description of the embodiment, directions or positions such as "upper", "lower", "left", "right", "front", "rear", "front" and "back" may be indicated. These notations are written in this way only for the convenience of explanation and do not limit the arrangement or orientation of components such as devices, instruments, or parts.

Embodiment 1.
An example of a satellite constellation that is a premise for the following embodiments will be described.

FIG. 1 is a diagram showing an example in which a plurality of satellites cooperate to provide communication services over the entire globe of the Earth 70 .
FIG. 1 shows a satellite constellation 20 that provides global communication services.
The communication service range of each of the multiple satellites flying at the same altitude in the same orbital plane overlaps with the communication service range of the succeeding satellite. Therefore, such multiple satellites can provide communication services to a specific point on the ground by alternating between the multiple satellites on the same orbital plane in a time-division manner. In addition, by providing adjacent orbital planes, it becomes possible to provide communication services to the ground between the adjacent orbits in a planar manner. Similarly, by arranging multiple orbital planes approximately evenly around the earth, communication services to the ground can be provided over the entire globe.

FIG. 2 is a diagram showing an example in which multiple satellites in a single orbit plane realize earth observation services.
FIG. 2 shows a satellite constellation 20 that implements earth observation services. In the satellite constellation 20 of FIG. 2, satellites equipped with earth observation devices that are radio wave sensors such as optical sensors or synthetic aperture radars fly on the same orbital plane at the same altitude. In this way, in the satellite group 300 in which the ground imaging range is time-delayed and subsequent satellites overlap, multiple satellites in orbit take turns in time-sharing to capture ground images at specific points on the ground. provide earth observation services.

In this way, the satellite constellation 20 is composed of a satellite group 300 consisting of a plurality of satellites in each orbital plane. In the satellite constellation 20, a group of satellites 300 cooperate to provide services. Specifically, the satellite constellation 20 refers to a satellite constellation consisting of one satellite group provided by a communication service company as shown in FIG. 1 or an observation service company as shown in FIG.

FIG. 3 is an example of a satellite constellation 20 having a plurality of orbital planes 21 that intersect near the polar regions.
FIG. 4 is an example of a satellite constellation 20 having multiple orbital planes 21 that intersect in non-polar regions.
In the satellite constellation 20 of FIG. 3, the orbital inclination angle of each orbital plane 21 of the plurality of orbital planes is approximately 90 degrees, and each orbital plane 21 of the plurality of orbital planes exists on a different plane.
In the satellite constellation 20 of FIG. 4, the orbital inclination angle of each orbital plane 21 of the plurality of orbital planes is not approximately 90 degrees, and each orbital plane 21 of the plurality of orbital planes exists on a different plane.

In the satellite constellation 20 of FIG. 3, any two orbital planes intersect at a point near the polar regions. In the satellite constellation 20 of FIG. 4, any two orbital planes intersect at a point other than the polar regions. In FIG. 3, a collision of satellites 30 may occur near the polar regions. Also, as shown in FIG. 4, the intersection of multiple orbital planes with an orbital inclination angle of more than 90 degrees moves away from the polar regions depending on the orbital inclination angle. Also, depending on the combination of orbital planes, the orbital planes may intersect at various positions, including near the equator. This diversifies the locations where a collision of satellites 30 may occur. Satellites 30 are also called artificial satellites.

In particular, in recent years, construction of large-scale satellite constellations ranging from hundreds to thousands of satellites has begun, increasing the risk of satellite collisions in orbit. In addition, debris such as satellites that have become uncontrollable due to malfunctions or debris from rockets is increasing. Large-scale satellite constellations are also called mega-constellations. This kind of debris is also called space debris.
As described above, with the increase in debris in outer space and the rapid increase in the number of satellites including mega constellations, the need for STM is increasing. STM is an abbreviation for Space Traffic Management.

Here, an example of a satellite 30 and a ground facility 700 in a satellite constellation forming system 600 that forms a satellite constellation 20 will be described with reference to Figures 5 to 8. For example, the satellite constellation forming system 600 is operated by an operator that conducts a satellite constellation business, such as a megaconstellation operator, a LEO constellation operator, or other satellite operator.

FIG. 5 is a configuration diagram of a satellite constellation forming system 600.
The satellite constellation forming system 600 includes a computer. Although Fig. 5 shows the configuration of one computer, in reality, a computer is provided in each of the multiple satellites 30 that make up the satellite constellation 20 and in each of the ground facilities 700 that communicate with the satellites 30. The computers provided in each of the multiple satellites 30 and in each of the ground facilities 700 that communicate with the satellites 30 work together to realize the functions of the satellite constellation forming system 600. An example of the configuration of a computer that realizes the functions of the satellite constellation forming system 600 will be described below.

Satellite constellation formation system 600 includes satellite 30 and ground equipment 700. The satellite 30 includes a satellite communication device 32 that communicates with a communication device 950 of the ground facility 700. FIG. 5 illustrates the satellite communication device 32 among the components included in the satellite 30.

Satellite constellation formation system 600 includes a processor 910 and other hardware such as memory 921, auxiliary storage 922, input interface 930, output interface 940, and communication device 950. Processor 910 is connected to other hardware via signal lines and controls these other hardware. The hardware of the satellite constellation formation system 600 is similar to the hardware of the rocket launch support device 100, which will be described later in FIG.

The satellite constellation forming system 600 includes, as a functional element, a satellite constellation forming unit 11. The function of the satellite constellation forming unit 11 is realized by hardware or software.
The satellite constellation forming unit 11 controls the formation of the satellite constellation 20 while communicating with the satellites 30 .

FIG. 6 is a configuration diagram of a satellite 30 of a satellite constellation forming system 600.
The satellite 30 comprises a satellite control device 31, a satellite communication device 32, a propulsion device 33, an attitude control device 34, and a power supply device 35. The satellite 30 also comprises other components that realize various functions, but only the satellite control device 31, the satellite communication device 32, the propulsion device 33, the attitude control device 34, and the power supply device 35 will be described in FIG.

The satellite control device 31 is a computer that controls the propulsion device 33 and the attitude control device 34, and includes a processing circuit. Specifically, satellite control device 31 controls propulsion device 33 and attitude control device 34 according to various commands transmitted from ground equipment 700.
Satellite communication device 32 is a device that communicates with ground equipment 700. Specifically, satellite communication device 32 transmits various data related to its own satellite to ground equipment 700. Additionally, the satellite communication device 32 receives various commands transmitted from the ground equipment 700.
The propulsion device 33 is a device that provides propulsion to the satellite 30 and changes the speed of the satellite 30. Specifically, the propulsion device 33 is an electric propulsion device. Specifically, the propulsion device 33 is an ion engine or a Hall thruster.
The attitude control device 34 is a device for controlling attitude factors such as the attitude of the satellite 30, the angular velocity of the satellite 30, and the line of sight. The attitude control device 34 changes each attitude element in a desired direction. Alternatively, the attitude control device 34 maintains each attitude element in a desired direction. The attitude control device 34 includes an attitude sensor, an actuator, and a controller. Attitude sensors are devices such as gyroscopes, earth sensors, sun sensors, star trackers, thrusters and magnetic sensors. Actuators are devices such as attitude control thrusters, momentum wheels, reaction wheels and control moment gyros. The controller controls the actuator according to the measurement data of the attitude sensor or various commands from the ground equipment 700.
The power supply device 35 includes devices such as a solar cell, a battery, and a power control device, and supplies power to each device mounted on the satellite 30.

The processing circuitry provided in the satellite control device 31 will now be described.
The processing circuitry may be dedicated hardware or may be a processor that executes a program stored in a memory.
In the processing circuit, some functions may be realized by dedicated hardware and the remaining functions may be realized by software or firmware, i.e., the processing circuit may be realized by hardware, software, firmware, or a combination thereof.
The dedicated hardware may specifically be a single circuit, a complex circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination of these.
ASIC is an abbreviation for Application Specific Integrated Circuit, and FPGA is an abbreviation for Field Programmable Gate Array.

FIG. 7 is a configuration diagram of ground equipment 700 included in satellite constellation formation system 600.
Ground facilities 700 programmatically control multiple satellites in all orbital planes. Ground equipment 700 is an example of ground equipment. The ground equipment includes a ground station such as a ground antenna device, a communication device connected to the ground antenna device, or a computer, and ground equipment as a server or terminal connected to the ground station via a network. Further, the ground device may include a communication device mounted on a mobile object such as an aircraft, a self-propelled vehicle, or a mobile terminal.

Ground equipment 700 forms satellite constellation 20 by communicating with each satellite 30 . Ground equipment 700 is provided in rocket launch support device 100 . Ground equipment 700 includes a processor 910 and other hardware such as memory 921, auxiliary storage 922, input interface 930, output interface 940, and communication device 950. Processor 910 is connected to other hardware via signal lines and controls these other hardware. The hardware of the ground equipment 700 is similar to the hardware of the rocket launch support device 100, which will be described later in FIG.

The ground equipment 700 includes an orbit control command generation section 510 and an analysis prediction section 520 as functional elements. The functions of the orbit control command generation section 510 and the analysis prediction section 520 are realized by hardware or software.

Communication device 950 transmits and receives signals for tracking and controlling each satellite 30 of satellite group 300 that constitutes satellite constellation 20 . Furthermore, the communication device 950 transmits the orbit control command 55 to each satellite 30.
The analysis prediction unit 520 analyzes and predicts the orbit of the satellite 30.
Orbit control command generation section 510 generates orbit control command 55 to be transmitted to satellite 30.
The orbit control command generation unit 510 and the analysis prediction unit 520 realize the functions of the satellite constellation formation unit 11. That is, the orbit control command generation section 510 and the analysis prediction section 520 are examples of the satellite constellation formation section 11.

FIG. 8 is a diagram showing an example of the functional configuration of the satellite constellation formation system 600.
The satellite 30 further includes a satellite constellation forming section 11b that forms the satellite constellation 20. The satellite constellation forming unit 11b of each satellite 30 of the plurality of satellites and the satellite constellation forming unit 11 provided in each of the ground facilities 700 cooperate to realize the functions of the satellite constellation forming system 600. . Note that the satellite constellation forming unit 11b of the satellite 30 may be included in the satellite control device 31.

FIG. 9 is a diagram showing an example of a satellite constellation in the vicinity of 42 degrees north latitude.
There is a plan to develop a new rocket launch site in Taiki-cho, Hokkaido, Japan, which is located at 42 degrees north latitude. However, as shown in Figure 9, the skies above 42 degrees, 48 degrees, and 53 degrees north latitude are latitude zones where satellites that make up megaconstellations are densely concentrated. For this reason, it is extremely difficult for rocket launch operators to avoid collisions with satellites when launching rockets.

***Configuration Description***
FIG. 10 is a configuration diagram of a rocket launch support device 100 according to this embodiment.
The rocket launch support system 500 includes a rocket launch support device 100 .
The rocket launch support device 100 communicates with the management business device 40. The rocket launch support device 100 is mounted on the ground facility 701. The rocket launch support device 100 may also be mounted on the satellite constellation formation system 600. Alternatively, the rocket launch support device 100 may be mounted on at least one of the management business devices 40, such as the rocket launch business device 46. Alternatively, the rocket launch support device 100 may be mounted on a device of another business such as an orbital analysis service business.

The management business device 40 provides information regarding a space object 60 such as an artificial satellite or debris. The management business device 40 is a computer of a business that collects information regarding space objects 60 such as artificial satellites or debris.
The management business equipment 40 includes a mega constellation business equipment 41, a LEO constellation business equipment 42, a satellite business equipment 43, an orbit transition business equipment 44, a debris recovery business equipment 45, a rocket launch business equipment 46, and an SSA business equipment 47. Includes equipment. LEO is an abbreviation for Low Earth Orbit.

The mega-constellation business device 41 is a computer of a mega-constellation business that conducts a mega-constellation business.
The LEO constellation business device 42 is a computer of a LEO constellation business that conducts a low orbit constellation, that is, a LEO constellation business.
The satellite business equipment 43 is a computer of a satellite business that handles one to several satellites.
The orbit transition business device 44 is a computer of an orbit transition business that provides rocket launch support for a satellite.
The debris collection business device 45 is a computer of a debris collection business that carries out a business that collects debris.
The rocket launch business device 46 is a computer of a rocket launch business that conducts a rocket launch business.
The SSA business device 47 is a computer of an SSA business that conducts an SSA business, that is, a space situation monitoring business.

The management business device 40 may be any other device as long as it is a device that collects information about space objects such as artificial satellites or debris and provides the collected information to the rocket launch support device 100. Furthermore, when the rocket launch support device 100 is installed on the SSA public server, the rocket launch support device 100 may be configured to function as the SSA public server.
Note that the information provided from the management business device 40 to the rocket launch support device 100 will be explained in detail later.

The rocket launch support device 100 includes a processor 910, as well as other hardware such as a memory 921, an auxiliary storage device 922, an input interface 930, an output interface 940, and a communication device 950. The processor 910 is connected to the other hardware via signal lines and controls the other hardware.

The rocket launch support device 100 has, as its functional elements, an area calculation unit 110, an area notification unit 120, and a memory unit 130. The memory unit 130 stores satellite orbit forecast information 51.

The functions of the area calculation section 110 and the area notification section 120 are realized by software. The storage unit 130 is included in the memory 921. Alternatively, the storage unit 130 may be included in the auxiliary storage device 922. Further, the storage unit 130 may be divided into a memory 921 and an auxiliary storage device 922.

Processor 910 is a device that executes a rocket launch support program. The rocket launch support program is a program that realizes the functions of the area calculation section 110 and the area notification section 120.
The processor 910 is an IC (Integrated Circuit) that performs arithmetic processing. Specific examples of the processor 910 are a CPU (Central Processing Unit), a DSP (Digital Signal Processor), and a GPU (Graphics Processing Unit).

Memory 921 is a storage device that temporarily stores data. A specific example of the memory 921 is SRAM (Static Random Access Memory) or DRAM (Dynamic Random Access Memory).
Auxiliary storage device 922 is a storage device that stores data. A specific example of the auxiliary storage device 922 is an HDD. Further, the auxiliary storage device 922 may be a portable storage medium such as an SD (registered trademark) memory card, CF, NAND flash, flexible disk, optical disk, compact disc, Blu-ray (registered trademark) disc, or DVD. Note that HDD is an abbreviation for Hard Disk Drive. SD (registered trademark) is an abbreviation for Secure Digital. CF is an abbreviation for CompactFlash®. DVD is an abbreviation for Digital Versatile Disk.

The input interface 930 is a port connected to an input device such as a mouse, keyboard, or touch panel. Specifically, the input interface 930 is a USB (Universal Serial Bus) terminal. Note that the input interface 930 may be a port connected to a LAN (Local Area Network).
The output interface 940 is a port to which a cable of a display device 941 such as a display is connected. The output interface 940 is specifically a USB terminal or an HDMI (registered trademark) (High Definition Multimedia Interface) terminal. Specifically, the display is an LCD (Liquid Crystal Display).

Communication device 950 has a receiver and a transmitter. The communication device 950 is specifically a communication chip or NIC (Network Interface Card). The rocket launch support device 100 communicates with the management business device 40 via the communication device 950.

The rocket launch support program is read into the processor 910 and executed by the processor 910. The memory 921 stores not only the rocket launch support program but also an OS (Operating System). The processor 910 executes the rocket launch support program while executing the OS. The rocket launch support program and the OS may be stored in the auxiliary storage device 922. The rocket launch support program and the OS stored in the auxiliary storage device 922 are loaded into the memory 921 and executed by the processor 910. Note that a part or all of the rocket launch support program may be incorporated into the OS.

The rocket launch support device 100 may be equipped with multiple processors that replace the processor 910. These multiple processors share the task of executing a program. Each processor is a device that executes a program, just like the processor 910.

Data, information, signal values and variable values used, processed or output by the program are stored in memory 921, auxiliary storage device 922, or in a register or cache memory within processor 910.

The "parts" of the rocket launch support system may be read as "processing,""procedure,""means,""stage," or "step." Also, the "processing" of the area calculation process and area notification process may be read as "program,""programproduct," or "computer-readable recording medium on which a program is recorded."
The rocket launch support program causes a computer to execute each process, each procedure, each means, each stage, or each step of the rocket launch support system, where the "part" of each part is interpreted as a "process,""procedure,""means,""stage," or "process." Also, the rocket launch support method is a method performed by the rocket launch support device 100 executing the rocket launch support program.
The rocket launch support program may be provided by being stored in a computer-readable recording medium. Also, each program may be provided as a program product.

*** Operation Description ***
FIG. 11 is a diagram showing an example of satellite orbit forecast information 51 according to the present embodiment.
The rocket launch support device 100 stores satellite orbit forecast information 51 in which a forecast value of the orbit of the space object 60 is set in the memory unit 130. The rocket launch support device 100 may obtain forecast values of the orbits of each of the multiple space objects 60 from a management business device 40 used by a management business operator that manages the multiple space objects 60, for example, and store the forecast values as the satellite orbit forecast information 51. Alternatively, the rocket launch support device 100 may obtain the satellite orbit forecast information 51 in which a forecast value of the orbit of each of the multiple space objects 60 is set from the management business operator, and store the satellite orbit forecast information 51 in the memory unit 130.
The management company is a company that manages space objects 60 flying in space, such as satellite constellations, various satellites, rockets, and debris. As described above, the management business devices 40 used by each management company are computers such as a megaconstellation business device 41, a LEO constellation business device 42, a satellite business device 43, an orbital transfer business device 44, a debris retrieval business device 45, a rocket launch business device 46, and an SSA business device 47.

In the satellite orbit forecast information 51, for example, information such as a space object ID (Identifier) 511, a forecast era 512, a forecast orbit element 513, and a forecast error 514 is set.

The space object ID 511 is an identifier that identifies the space object 60. In FIG. 11, a satellite ID and a debris ID are set as the space object ID 511. Specifically, space objects include objects such as rockets launched into outer space, artificial satellites, space bases, debris collection satellites, planetary exploration spacecraft, and satellites or rockets that become debris after their missions are completed.

The forecast epoch 512 is an epoch in which the orbits of each of a plurality of space objects are predicted.
The predicted orbit element 513 is an orbit element that specifies the orbit of each of a plurality of space objects. The predicted orbit element 513 is an orbit element predicted for each orbit of a plurality of space objects. In FIG. 11, six Keplerian orbit elements are set as the forecast orbit elements 513.

The forecast error 514 is an error predicted for each orbit of multiple space objects. The forecast error 514 includes a heading error and an orthogonal error. The forecast error 514 explicitly indicates the amount of error contained in the actual value.

In the satellite orbit forecast information 51 according to the present embodiment, a forecast origin 512 and forecast orbital elements 513 are set for the space object 60. The forecast origin 512 and the forecast orbital elements 513 can be used to determine the time and position coordinates in the near future of the space object 60. For example, the time and position coordinates in the near future for the space object 60 may be set in the satellite orbit forecast information 51.
In this way, the satellite orbit forecast information 51 includes orbit information of the space object, including the epoch and orbital elements, or the time and position coordinates, and explicitly shows the near-future forecast values of the space object 60.
Note that the satellite orbit forecast information 51 may have a configuration other than that shown in FIG. 11 as long as the information explicitly indicates the near-future forecast values of the space object 60.

FIG. 12 is an image diagram of a rocket launch according to this embodiment.
The rocket 202 is launched from the rocket launch site 201 under the control of the launch control device 200. The launch control device 200 is mounted on, for example, ground equipment 702.
The rocket launch support device 100 according to the present embodiment supports the launch of the rocket 202 so that the rocket 202 can be launched without colliding with the satellites 30 of the satellite constellation 20 flying above the rocket launch site 201.

FIG. 13 is a flowchart of rocket launch support processing S100 by the rocket launch support device 100 according to the present embodiment.
In step S101, the area calculation unit 110 calculates the passable time area 111 based on the position coordinates of the rocket launch site 201 and the satellite orbit forecast information 51 in which the predicted value of the satellite's orbit is set. The passable time region 111 is a time region in which there is no risk that the rocket 202 launched from the rocket launch site 201 will collide with the satellites 30 forming the satellite constellation 20 passing over the rocket launch site 201. In other words, the passable time area 111 is a time period during which there is no risk of a rocket 202 launched from a rocket launch site 201 whose position coordinates are fixed and known colliding with a satellite 30 forming a satellite constellation 20 formed at a specific altitude. It is an area.

FIG. 14 is a diagram showing an example of launching the rocket 202 according to the present embodiment directly upward.
For example, it is assumed that there is a mega-constellation A formed with an orbital altitude of about 336 km and an orbital inclination of 42 degrees, and composed of about 2,500 satellites. Assume that a rocket 202 is launched directly overhead from a rocket launch site 201 established in Taiki-cho, Hokkaido, located at 42 degrees north latitude and 143 degrees east longitude. At this time, there is a risk that the rocket 202 will collide with the satellites 30 forming the mega constellation A at an altitude of 336 km. However, satellites flying in the same orbit are generally spaced apart by more than 100 km. Therefore, there is a return waiting time of 10 seconds or more after one satellite passes over the sky until the subsequent satellite passes.
Satellites in adjacent orbit planes are operated at intervals in the same way, and in order to avoid collisions with satellites in different orbit planes near 42 degrees north latitude, the satellites operate at 42 degrees north latitude at a timing that closes the gap between the satellites. The operation is controlled so that it passes through.

The area calculation unit 110 takes into account the time it takes for the rocket to reach an altitude of 336 km after launch, and excludes the time period in which the satellite happens to pass over the sky as a "time period with a risk of collision." The area calculation unit 110 may calculate, for example, a time period obtained by excluding the "time period with a risk of collision" from the time period of the day as the passable time area 111. Alternatively, the area calculation unit 110 may calculate the passable time area 111 by excluding the "time period with a risk of collision" from the time period specified by the user. In this way, if we exclude from the time period the "time period where there is a risk of collision" of the satellite in the orbit passing near the rocket launch site 201, we will end up with a "time period where there is no risk of collision", i.e. A passable time area 111 remains. If this information is disclosed to the rocket launch operator at the rocket launch site with the additional condition of the time required to reach a specific altitude after launch, it will be possible to launch the rocket without the risk of collision.

FIG. 15 is a diagram showing an example of launching the rocket 202 in an oblique direction according to this embodiment.
The rocket 202 is not necessarily launched directly overhead. For example, the area calculation unit 110 may obtain a rocket launch prediction value Ox, which is a predicted rocket launch trajectory, from a rocket launch operator in advance. The area calculation unit 110 calculates a passable time area 111 based on the rocket launch prediction value Ox and the satellite orbit forecast information 51. Specifically, the predicted rocket launch value Ox is the desired passing time and passing position coordinates at a specific altitude, for example, an altitude of 336 km. The reason why it is desired to pass is that the launch control device 200 needs to correct the launch timing according to the "time region without risk of collision."

As described above, the area calculation unit 110 obtains the rocket launch prediction value Ox at which the rocket 202 launched from the rocket launch site 201 passes through the orbit of the satellite constellation 20. The area calculation unit 110 may calculate the passable time area 111 using the predicted rocket launch value Ox obtained from the rocket launch operator.

FIG. 16 is a diagram illustrating an example of the passable time region 111 in which prediction errors are expected according to the present embodiment.
On the rocket launch operator's side, for example, there may be a significant prediction error in the position coordinates when the rocket passes through an altitude of 336 km. Alternatively, there may be a significant prediction error in the satellite passage time and position coordinates of the mega-constellation operator. In Fig. 16, if such a prediction error exists, there is a concern that there is no collision risk-free time region, that is, the passable time region 111, and this suggests that a safe rocket launch will not be possible unless accuracy is improved. ing.

In step S102, the area notification unit 120 outputs the passable time area 111. Specifically, the area notification unit 120 displays the passable time area 111 on the display device 941 via the output interface 940. Alternatively, the area notification unit 120 may transmit the passable time area 111 to the management business device 40 via the communication device 950.

The satellite constellation 20 may also be a plurality of satellite constellations formed at a plurality of different orbital altitudes. For example, the plurality of satellite constellations may belong to a particular mega-constellation operator. The area calculation unit 110 calculates a passable time area 111 for each of the plurality of orbital altitudes. The area notification unit 120 displays on a display device a time area that is an aggregate of the plurality of passable time areas 111 calculated for each of the plurality of orbital altitudes.

FIG. 17 is a diagram showing display example 1 and display example 2 of the passable time region 111 according to the present embodiment.
As shown in display example 1 of FIG. 17, a passable time region 111, which is a time region without risk of collision, may be displayed for each of a plurality of orbital altitudes operated by a specific megaconstellation operator.

For example, three types of mega-constellations formed around an orbital altitude of 340 km operate asynchronously with each other. Therefore, the movement of the orbital plane as viewed from the position coordinates of a specific rocket launch site, or the flight position of the satellite, is uncorrelated for each orbital altitude. Therefore, even if the rocket launch support device 100 displays the passable time region 111 for each orbital altitude, this is merely a necessary condition for "a time region without risk of collision in all orbits," and is not a sufficient condition.

For example, assume that the following satellite constellation 20 exists:
Orbital altitude: approx. 336 km; orbital inclination: 42 degrees; approx. 2,500 units Orbital altitude: approx. 341 km; orbital inclination: 48 degrees; approx. 2,500 units Orbital altitude: approx. 346 km; orbital inclination: 53 degrees; approx. 2,500 units

In the rocket launch support device 100 according to the present embodiment, the above-mentioned three altitudes and multiple or all orbital altitudes operated by the same mega constellation operator are set in a "time domain without risk of collision", that is, a passing The possible time areas 111 are integrated. Then, as shown in display example 2 in FIG. 17, "a time region in which there is no risk of collision in a plurality of trajectories" is displayed as a passable time region 111. As a result, rocket launch operators will be able to safely launch all the satellites operated by the mega constellation operator without any collisions.

Further, the satellite constellation 20 may be a plurality of satellite constellations operated by a plurality of mutually different satellite constellation operators. At this time, the area calculation unit 110 calculates the passable time area 111 for each of the plurality of satellite constellations. Then, the area notification unit 120 displays the passable time area 111 for each of the plurality of satellite constellations.

FIG. 18 is a diagram showing a third display example of the passable time area 111 according to the present embodiment.
In FIG. 18, passable time areas 111 for a plurality of mega-constellation operators A and B are displayed.
High-precision forecast values for the satellites that make up a mega-constellation are usually held only by the relevant mega-constellation operator, so it is difficult for third parties to share the high-precision forecast values of multiple mega-constellation operators.
Furthermore, the current outlook is that if SPACE-X can pass through the orbital plane that it plans to develop under the Starlink concept without collision, the risk of collision with a satellite from another mega constellation during launch is sufficiently small. However, in the future, for example, there is a possibility that a different mega-constellation operator will construct another mega-constellation near an altitude of 400 km. Therefore, in order to achieve a launch without colliding with any mega-constellation, the display of display example 3 in FIG. 18 is suitable.
When mega constellation operators, rocket launch operators, and operators providing support services using rocket launch support equipment span multiple countries, high-precision It is preferable to establish international rules for disclosing information on forecast values.

Note that the display examples of the passable time area 111 in FIGS. 17 and 18 are merely examples, and any display format may be used as long as the passable time area 111 can be notified.

***Description of Effects of This Embodiment***
According to the rocket launch support device of the present embodiment, the rocket launch operator can be notified of the time range over which the rocket can pass after being launched from the rocket launch site. In this way, by disclosing the time range over which the rocket can pass to the rocket launch operator at the rocket launch site with the time required to reach a specific altitude after the rocket is launched as an additional condition, the rocket can be launched without the risk of collision.

***Other configurations***
<Modification 1>
The rocket launch support system acquires space object information from a space information recorder that records space object information obtained from a management business device used by a management business operator that manages multiple space objects. The rocket launch support system helps avoid collisions between the rocket and space objects during launch.
The rocket launch support system according to this embodiment includes a database that stores space object information acquired from a space information recorder, and a server that supports avoidance of collision between the rocket and the space object during launch.

Specifically, the database may be memory, auxiliary storage, or a file server. The space information recorder records space object information obtained from a management business device used by a management business that manages multiple space objects. The rocket launch support device may include a space information recorder. The space information recorder may include satellite orbit forecast information.

Specifically, the server is a rocket launch support device. The database may be provided in the server or may be a separate device from the server. A server implements the following steps (also referred to as means or units) using processing circuitry such as a processor or an electronic circuit.

The database acquires and stores rocket space object information and satellite orbit forecast information for the mega constellation satellite group from the space information recorder. The rocket's space object information is information obtained from the rocket launch operator's management business equipment using the space information recorder. Satellite orbit forecast information for a group of satellites in a mega constellation is information obtained by a space information recorder from the management business equipment of a mega constellation that is at risk of being hit by a rocket. The rocket space object information includes the position coordinates of the rocket launch site, the rocket's scheduled launch time information, and the predicted trajectory information.

The server comprises the following stages:
- A stage in which, based on the position coordinates of the rocket launch site, the delay time and orbital position until the rocket launched at the scheduled launch time arrives in the vicinity of the satellite constellation are analyzed.
- A stage of determining the relative distance A between the rocket and other space objects, which serves as an indicator of the flight safety area.
- A stage for determining the relative distance B between the rocket and other space objects, which is an indication of the collision danger zone.
A step of extracting satellites from the satellite constellation that are likely to approach closer than the relative distance B and identifying them as satellites requiring attention.
A step of extracting a safe time region in which all of the satellites of concern fly simultaneously at a distance greater than the relative distance A.
- Displaying the safe time zone.
A step of displaying a safety confirmation message if the scheduled launch time of the rocket is included in the safety time region.
A step of displaying a recommended launch time from within the safe time range as a launch time change recommendation message when the scheduled rocket launch time is not included in the safe time range.
- The stage where a safety confirmation message or a message recommending a change in the launch time is sent to the rocket launch operator.

A safe time domain is an example of a time domain where there is no risk of collision.

FIG. 25 is a diagram showing an example of the relative distance A between the rocket and another space object, which is an index of the flight safety area, according to a modification of the present embodiment.
FIG. 26 is a diagram showing an example of the relative distance B between the rocket and another space object, which is an index of the collision risk area according to a modification of the present embodiment.
As shown in FIG. 25, when the server determines the relative distance A between the rocket and another space object, which is an indicator of the flight safety area, it needs to consider the size of the space object including the error range.
In addition, as shown in Figure 26, when the server determines the relative distance B between the rocket and other space objects, which is an indicator of the collision risk area, the server considers the size of the space object including the error range. The actual relative distance when the relative distance is less than or equal to 0 is the relative distance B.

FIG. 27 is a diagram showing a state in which a flight safety area cannot be secured according to a modified example of the present embodiment.
The top part of Fig. 27 is a model of a mega-constellation in two-dimensional space. The bottom part of Fig. 27 shows a state where the relative distance between the rocket and the space object is almost 0 (because the object dimensions are considered to include errors), and a collision is barely avoided, but the flight safety area is not secured.

FIG. 28 is a diagram showing the state of the launch window depending on the size of the error range according to the modified example of the present embodiment.
The upper part of FIG. 28 is a diagram showing a state in which a flight safety area according to the present embodiment is secured. Specifically, the upper part of FIG. 28 shows a state in which a flight safety area of a rocket is secured within the mega constellation operator's own system. In the mega constellation operator's own system, there is a possibility that the amount of error can be reduced by a method such as differential evaluation of inter-satellite ranging data or GPS measurement values, and statistical data evaluation. Therefore, there is a high possibility that a flight safety area can be secured within the mega constellation operator's own system.

On the other hand, the lower part of FIG. 28 shows a case where the precise forecast value of the mega-constellation is not disclosed and the error is large. If the mega-constellation operator does not disclose the amount of error, the forecast value of the mega-constellation will depend on external measurement information such as the SSA operator. If a rocket launch company only knows forecast values with a large amount of error, there is a concern that the launch window may not be secured. In other words, if rocket launch operators and megaconstellation operators monopolize precise trajectory forecast values, there is a concern that the launch business will become monopolized.

<Modification 2>
In this embodiment, the functions of the rocket launch support device 100 are realized by software. As a modified example, the functions of the rocket launch support device 100 may be realized by hardware.

FIG. 19 is a diagram showing the configuration of a rocket launch support device 100 according to a modification of the present embodiment.
The rocket launch support device 100 includes an electronic circuit 909 instead of the processor 910.
The electronic circuit 909 is a dedicated electronic circuit that realizes the functions of the rocket launch support device 100.
Electronic circuit 909 is specifically a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array.
The functions of the rocket launch support device 100 may be realized by one electronic circuit, or may be realized by being distributed among a plurality of electronic circuits.
As another modification, some of the functions of the rocket launch support device 100 may be realized by electronic circuits, and the remaining functions may be realized by software.

Each of the processor and electronic circuitry is also called a processing circuitry. In other words, the functions of the rocket launch support device 100 are realized by the processing circuitry.

Embodiment 2.
In this embodiment, the differences from embodiment 1 will be mainly described. Configurations having the same functions as those in embodiment 1 are given the same reference numerals, and descriptions thereof will be omitted.

***Explanation of configuration***
FIG. 20 is a diagram showing the configuration of rocket launch support device 100 according to this embodiment.
In this embodiment, the area calculation unit 110 calculates the possible passage area 112. Then, the area notification unit 120 outputs the possible passage area 112 calculated by the area calculation unit 110. The other configurations are the same as in the first embodiment.

*** Operation Description ***
FIG. 21 is a flow diagram of rocket launch support processing S100a by the rocket launch support device 100 according to this embodiment.
In step S101a, the area calculation unit 110 calculates a possible passage area 112 based on the position coordinates of the rocket launch site 201 and the satellite orbit forecast information 51 in which the forecast value of the satellite orbit is set. The possible passage area 112 is a passage area in which there is no risk of a rocket 202 launched from the rocket launch site 201 colliding with a satellite 30 constituting the satellite constellation 20 passing above the rocket launch site 201.

In step S102a, the area notification unit 120 outputs the possible pass area 112. For example, the area notification unit 120 displays the possible pass area 112 on the display device 941 via the output interface 940. Alternatively, the area notification unit 120 notifies the management business device 40 or the launch control device 200 of the possible pass area 112 via the communication device 950.
This allows the launch control device 200 to launch the rocket 202 while avoiding collisions using the possible passing area 112.

FIG. 22 is a satellite flight image near an orbit altitude of 340 km.
FIG. 23 is a diagram showing an example of a satellite constellation near an orbit altitude of 340 km.
FIG. 24 is a diagram showing an example of a rocket launch.
A specific example of rocket launch will be described using FIGS. 22 to 24.

For example, the rocket 202 is launched from a rocket launch site 201 located at a latitude of 40 degrees north or higher to an orbit at an altitude of 300 km or more and in a latitude direction of a latitude of 50 degrees north or higher. That is, the launch control device 200 launches a rocket 202 from a rocket launch site 201 located at a latitude of 40 degrees or more north to an orbit in a latitude direction of an altitude of 300 km or more and a latitude of 50 degrees or more north.

As shown in Figures 22 and 23, there is a plan to build a constellation of about 7,500 satellites at an altitude of about 340 km and an orbital inclination of 50 degrees or less. After this plan is completed, there is a possibility that there will be no launch window when launching directly above or southward from a rocket launch site developed in Hokkaido, for example.
Rockets launched from rocket launch sites at latitudes above 40 degrees north and passing through high-latitude orbits at orbital altitudes of 300 km or more and latitudes of 50 degrees north or more pass through areas near the poles where there are no mega-constellations, allowing for safe launches without the risk of collision.
Currently, there is a plan to develop a rocket launch site in Taiki-cho, Hokkaido, at approximately 42 degrees north latitude. In addition, there is a plan to operate approximately 2,500 satellites in an orbit at an altitude of approximately 340 km and an inclination angle of 42 degrees as part of the mega-constellation plan. Since 42 degrees north latitude is a dense area where satellites turn around, it is difficult to secure a launch window directly above. There are also plans for an orbit with an inclination of 50 degrees, and it is extremely difficult to launch in the south and avoid colliding with these constellations.
On the other hand, since the above-mentioned constellation satellites do not exist above 50 degrees north latitude, this has the advantage of making it possible to launch the satellite while avoiding collisions.

As shown in Figure 24, if launching from Taiki Town at 42 degrees north latitude, an orbit that passes north through an altitude of 336 km at 42 degrees north latitude, an altitude of 346 km at 53 degrees north latitude, and an altitude of 590 km at 56 degrees north latitude will allow launch without the risk of collision with the mega-constellation.

***Description of Effects of the Present Embodiment***
In the rocket launch support device according to the present embodiment, a passage area in which there is no risk of a rocket launched from a rocket launch site with fixed and known position coordinates colliding with a satellite constellation formed at a specific altitude is displayed as a possible passage area. This has the effect that the rocket launch operator can launch the rocket while avoiding collisions.

In the first and second embodiments above, each part of the rocket launch support device has been described as an independent functional block. However, the configuration of the rocket launch support device does not have to be the configuration of the above-described embodiment. The functional blocks of the rocket launch support device may have any configuration as long as they can realize the functions described in the embodiments described above. Further, the rocket launch support device may be a single device or a system composed of a plurality of devices.

In addition, a combination of multiple parts of the first and second embodiments may be implemented. Alternatively, one part of these embodiments may be implemented. In addition, any combination of these embodiments may be implemented, either as a whole or in part.
That is, the first and second embodiments may be partially combined freely. Alternatively, the components of the first and second embodiments may be modified in any way. That is, the components of the first and second embodiments may be added or omitted.

The above-described embodiment is essentially a preferred example, and is not intended to limit the scope of the present invention, the scope of the application of the present invention, or the scope of use of the present invention. The above-described embodiment can be modified in various ways as necessary.

20 Satellite constellation, 21 Orbital surface, 30 Satellite, 31 Satellite control device, 32 Satellite communication device, 33 Propulsion device, 34 Attitude control device, 35 Power supply device, 40 Management business device, 41 Mega constellation business device, 42 LEO constellation device ration business equipment, 43 Satellite business equipment, 44 Orbit transition business equipment, 45 Debris recovery business equipment, 46 Rocket launch business equipment, 47 SSA business equipment, 51 Satellite orbit forecast information, 511,521 Space object ID, 512 Forecast epoch, 513 Forecast orbit element, 514 Forecast error, 60 Space object, 70 Earth, 100 Rocket launch support device, 110 Area calculation unit, 111 Passable time area, 112 Possible passage area, 120 Area notification unit, 130 Storage unit, 55 Orbit control Command, 200 Launch control device, 201 Rocket launch site, 202 Rocket, 600 Satellite constellation formation system, 11, 11b Satellite constellation formation unit, 300 Satellite group, 700, 701, 702 Ground equipment, 500 Rocket launch support system, 510 Orbit control command generation section, 520 analysis prediction section, 909 electronic circuit, 910 processor, 921 memory, 922 auxiliary storage device, 930 input interface, 940 output interface, 941 display device, 950 communication device, Ox rocket launch predicted value.

Claims (5)

a region calculation unit that calculates, based on the position coordinates of a rocket launch site and satellite orbit forecast information in which a forecast value of a satellite orbit is set, a possible passage region in which a rocket launched from the rocket launch site located at a latitude of 40 degrees north or higher into an orbit at an orbital altitude of 300 km or higher and in a latitudinal direction of a latitude of 50 degrees north or higher does not risk colliding with a satellite constellation passing above the rocket launch site;
A rocket launch support device comprising an area notification unit that outputs the possible passing area. the area calculation unit calculates, based on the position coordinates of the rocket launch site and the satellite orbit forecast information in which a forecast value of a satellite orbit is set, a possible passing area in which there is no risk of a rocket launched from the rocket launch site located at a latitude of 40 degrees north or higher into an orbit at an orbital altitude of 300 km or higher and a latitude direction of a latitude of 50 degrees north or higher colliding with a satellite constellation passing above the rocket launch site;
A rocket launch support method in which an area notification unit outputs the possible passing area. Based on the position coordinates of the rocket launch site and the satellite orbit forecast information in which the predicted value of the satellite's orbit is set, the rocket launched from the rocket launch site is located at a latitude of 40 degrees or more north. , a rocket launched into an orbit with an orbital altitude of 300 km or more and a latitude of 50 degrees north or more can pass through a transit area without the risk of colliding with a satellite constituting a satellite constellation passing over the rocket launch site. Area calculation processing to calculate as an area,
A rocket launch support program that causes a computer to execute an area notification process for outputting the possible passage area. Based on the position coordinates of the rocket launch site and the satellite orbit forecast information in which the predicted value of the satellite's orbit is set, the rocket launched from the rocket launch site is set to a satellite constellation that passes over the rocket launch site. an area calculation unit that calculates, as a possible passage area, a passage area without the risk of colliding with a satellite constituting a satellite constellation formed with an orbital inclination of 39 degrees to 56 degrees;
an area notification unit that outputs the possible passage area;
A rocket launch support system equipped with a 5. The rocket launch support system according to claim 4, wherein the satellite constellation is a satellite mega-constellation, which is a large-scale satellite constellation.

Images