Rocket system and rocket launch method

Abstract

To effectively support avoidance of a collision of a rocket with satellites constituting a satellite constellation, in launching the rocket from a locket-launching site at the northern latitude of 40 degrees or more.SOLUTION: A rocket is launched toward an orbit whose orbital altitude is 300 km or higher and which is in a latitude direction at northern latitudes of 50 degrees or more, from a rocket-launching site positioned at a northern latitude of 40 degrees or more. The rocket is launched from a rocket launching site 201, on the basis of a satellite orbit forecast information 51 in which a position coordinate of the rocket launching site 201 and a forecast value for the orbit of satellites are set. Further the rocket is launched toward a passing region where there is no risk of the rocket collision with satellites constituting a satellite constellation passing through sky above the rocket launching site 201.SELECTED DRAWING: Figure 24

Description

[Technical Field]

[0001] The present invention relates to a rocket and a rocket launch method. [Background technology]

[0002] In recent years, the construction of large-scale satellite constellations, so-called mega-constellations, consisting of hundreds or even thousands of satellites, has begun, increasing the risk of satellite collisions in orbit. In addition, there has been an increase in space debris, such as satellites that have become uncontrollable due to malfunctions and rocket debris. With the rapid increase in space objects such as satellites and space debris in outer space, there is an increasing need for international rules in space traffic management (STM) to avoid collisions of space objects.

[0003] In recent years, mega-constellation operators have emerged that operate mega-constellations. These operators plan to deploy satellites across the entire sky as follows: Orbital altitude approximately 336km: Orbital inclination 42 degrees, approximately 2500 aircraft Orbital altitude approximately 341km: Orbital inclination 48 degrees, approximately 2500 aircraft Orbital altitude approximately 346km: Orbital inclination 53 degrees, approximately 2500 aircraft Orbital altitude approximately 550km: Orbital inclination 53 degrees, approximately 1600 aircraft Orbital altitude approximately 1150km: orbital inclination 53 degrees, approximately 1600 aircraft

[0004] Additionally, another mega-constellation operator has announced plans to deploy a total of 3,236 satellites in orbits with inclinations ranging from 39 degrees to 56 degrees. Orbital altitude approximately 590km: 784 aircraft Orbital altitude approximately 610km: 1296 aircraft Orbital altitude approximately 630km: 1156 aircraft For example, there is a plan to develop a rocket launch site in Taiki Town, Hokkaido, Japan, at 42 degrees north latitude.

[0005] Patent Document 1 discloses a technique for forming a satellite constellation consisting of multiple satellites in the same circular orbit. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-114159 Summary of the Invention [Problem to be solved by the invention]

[0007] As mentioned above, satellites that make up mega-constellations are concentrated in the latitudes above 42 degrees, 48 ​​degrees, and 53 degrees. This makes it extremely difficult for launch operators to avoid collisions with satellites when launching rockets. However, Patent Document 1 does not describe any measures to avoid such collisions.

[0008] The present invention aims to effectively assist in collision avoidance between a rocket and a satellite constellation when the rocket is launched from a rocket launch site at a latitude of 40 degrees north or higher. [Means for solving the problem]

[0009] The rocket according to the present invention comprises: It will be launched from a rocket launch site located at a latitude of 40 degrees north or higher into an orbit at an altitude of 300 km or higher and at a latitude of 50 degrees north or higher. [Effects of the Invention]

[0010] The rocket launch support device according to the present invention has the effect of effectively assisting in collision avoidance between a rocket and a satellite that constitutes a satellite constellation when the rocket is launched from a rocket launch site at a latitude of 40 degrees north or higher. [Brief explanation of the drawings]

[0011] [Figure 1] An example of multiple satellites working together to provide communications services across the entire globe. [Figure 2] An example of Earth observation services realized by multiple satellites in a single orbital plane. [Figure 3] An example of a satellite constellation with multiple orbital planes that intersect near the polar regions. [Figure 4] An example of a satellite constellation with multiple intersecting orbital planes outside the polar regions. [Figure 5] A diagram of the satellite constellation formation system. [Figure 6] A diagram of the satellite configuration of the satellite constellation formation system. [Figure 7] A diagram of the ground equipment for the satellite constellation formation system. [Figure 8] An example of the functional configuration of a satellite constellation formation system. [Figure 9] An example of a satellite constellation near 42 degrees north latitude. [Figure 10] 1 is a configuration diagram of a rocket launch support device according to a first embodiment. [Figure 11] FIG. 3 is a diagram showing an example of satellite orbit forecast information according to the first embodiment. [Figure 12] FIG. 2 is an image diagram of a rocket launch according to the first embodiment. [Figure 13] 3 is a flow diagram of rocket launch support processing by the rocket launch support device according to the first embodiment. [Figure 14] FIG. 2 is a diagram showing an example of launching a rocket directly upward according to the first embodiment. [Figure 15] FIG. 2 is a diagram showing an example of launching a rocket in an oblique direction according to the first embodiment. [Figure 16] FIG. 2 is a diagram showing an example of a passable time region in which a prediction error is expected according to the first embodiment. [Figure 17] 5A and 5B are diagrams showing display example 1 and display example 2 of a passable time region according to the first embodiment. [Figure 18] FIG. 10 is a diagram showing a third display example of a passable time region according to the first embodiment. [Figure 19] FIG. 2 is a diagram showing the configuration of a rocket launch support device according to a modified example of the first embodiment. [Figure 20] FIG. 10 is a configuration diagram of a rocket launch support device according to a second embodiment. [Figure 21] FIG. 10 is a flow diagram of rocket launch support processing by the rocket launch support device according to the second embodiment. [Figure 22] Image of a satellite flying at an orbital altitude of approximately 340 km. [Figure 23] A diagram showing an example of a satellite constellation at an orbital altitude of around 340 km. [Figure 24] A diagram showing an example of a rocket launch. [Figure 25] FIG. 10 is a diagram showing an example of a relative distance A between a rocket and another space object, which serves as an index of a flight safety area according to a modification of the first embodiment. [Figure 26] FIG. 10 is a diagram showing an example of a relative distance B between a rocket and another space object, which serves as an indicator of a collision risk area in a modified example of the first embodiment. [Figure 27] FIG. 10 is a diagram showing a state in which a flight safety area is not secured according to a modification of the first embodiment. [Figure 28] FIG. 10 is a diagram showing the state of the launch window depending on the size of the error range according to the modification of the first embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each drawing, identical or corresponding parts are designated by the same reference numerals. In the description of the embodiments, the description of identical or corresponding parts will be omitted or simplified as appropriate. In addition, the size relationships of the components in the drawings may differ from the actual size relationships. In addition, in the description of the embodiments, directions or positions such as "upper," "lower," "left," "right," "front," "rear," "front," and "back" may be indicated. These notations are used merely for the convenience of explanation and do not limit the arrangement or orientation of components such as devices, instruments, or parts.

[0013] Embodiment 1 An example of a satellite constellation that is the premise of the following embodiment will be described.

[0014] FIG. 1 is a diagram showing an example in which multiple satellites cooperate to provide communication services across the globe (Earth 70) to the ground. FIG. 1 shows a satellite constellation 20 that provides communication services across the globe. For multiple satellites flying at the same altitude in the same orbital plane, the communication service area for the ground of each satellite overlaps with the communication service area of ​​the succeeding satellite. Therefore, with such multiple satellites, multiple satellites on the same orbital plane can provide communication services to a specific point on the ground by alternating in a time-division manner. Furthermore, by providing adjacent orbital planes, it becomes possible to provide communication services to the ground between adjacent orbits in a surface-wide manner. Similarly, by distributing multiple orbital planes approximately evenly around the Earth, communication services to the ground can be provided over the entire globe.

[0015] FIG. 2 is a diagram showing an example in which multiple satellites in a single orbital plane provide an Earth observation service. Figure 2 shows a satellite constellation 20 that provides an Earth observation service. In the satellite constellation 20 of Figure 2, satellites equipped with Earth observation equipment, such as optical sensors or radio wave sensors such as synthetic aperture radar, fly in the same orbital plane at the same altitude. In this way, in a satellite group 300 in which the terrestrial imaging range is time-delayed and subsequent satellites overlap, multiple satellites in orbit take turns capturing terrestrial images of a specific point on the ground in a time-division manner, thereby providing an Earth observation service.

[0016] In this way, the satellite constellation 20 is made up of a group of satellites 300 consisting of multiple satellites in each orbital plane. In the satellite constellation 20, the group of satellites 300 work together to provide services. Specifically, the satellite constellation 20 refers to a satellite constellation consisting of one group of satellites provided by a communications service company as shown in FIG. 1 or an observation service company as shown in FIG. 2.

[0017] FIG. 3 is an example of a satellite constellation 20 having multiple 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 outside the polar regions. In the satellite constellation 20 of FIG. 3, the orbital inclination angle of each of the multiple orbital planes 21 is approximately 90 degrees, and each of the multiple orbital planes 21 exists in a different plane from each other. In the satellite constellation 20 of FIG. 4, the orbital inclination angle of each of the multiple orbital planes 21 is not approximately 90 degrees, and each of the multiple orbital planes 21 exists in a different plane from each other.

[0018] 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, there is a possibility that 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. Furthermore, depending on the combination of orbital planes, there is a possibility that the orbital planes may intersect at various positions, including near the equator. This increases the variety of locations where a collision of satellites 30 may occur. Satellites 30 are also called artificial satellites.

[0019] In particular, in recent years, the construction of large-scale satellite constellations consisting of hundreds or even thousands of satellites has begun, increasing the risk of satellite collisions in orbit. Furthermore, there has been an increase in debris, such as satellites that have become uncontrollable due to malfunctions or rocket debris. Large-scale satellite constellations are also called megaconstellations. Such debris is also called space debris. As a result of the increase in space debris and the rapid increase in the number of satellites, including megaconstellations, the need for STM (Space Traffic Management) is growing.

[0020] 5 to 8, 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. For example, the satellite constellation forming system 600 is operated by an operator that operates a satellite constellation business, such as a megaconstellation operator, a LEO constellation operator, or another satellite operator.

[0021] FIG. 5 is a diagram illustrating the configuration of a satellite constellation forming system 600. The satellite constellation forming system 600 includes a computer. While Fig. 5 shows the configuration of one computer, in reality, a computer is provided for each of the multiple satellites 30 that make up the satellite constellation 20 and for each of the ground facilities 700 that communicate with the satellites 30. The computers provided for each of the multiple satellites 30 and for 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.

[0022] The satellite constellation forming system 600 includes a satellite 30 and a ground facility 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, which is one of the components included in the satellite 30.

[0023] The satellite constellation forming system 600 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 this other hardware. The hardware of the satellite constellation forming system 600 is similar to the hardware of the rocket launch support device 100, which will be described later with reference to FIG. 10.

[0024] The satellite constellation forming system 600 includes, as a functional element, a satellite constellation forming unit 11. The functions of the satellite constellation forming unit 11 are 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 .

[0025] FIG. 6 is a diagram showing the configuration 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. 6.

[0026] The satellite control device 31 is a computer that controls the propulsion devices 33 and the attitude control device 34, and includes a processing circuit. Specifically, the satellite control device 31 controls the propulsion devices 33 and the attitude control device 34 in accordance with various commands transmitted from the ground facility 700. The satellite communication device 32 is a device that communicates with the ground facility 700. Specifically, the satellite communication device 32 transmits various data related to its own satellite to the ground facility 700. In addition, the satellite communication device 32 receives various commands transmitted from the ground facility 700. The propulsion device 33 is a device that provides thrust 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 elements such as the attitude of the satellite 30, its angular velocity, and line of sight. The attitude control device 34 changes each attitude element to 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. The attitude sensor is a device such as a gyroscope, an earth sensor, a sun sensor, a star tracker, a thruster, and a magnetic sensor. The actuator is a device such as an attitude control thruster, a momentum wheel, a reaction wheel, and a control moment gyro. The controller controls the actuator according to measurement data from the attitude sensor or various commands from the ground equipment 700. The power supply unit 35 includes devices such as solar cells, batteries, and a power control device, and supplies power to each device mounted on the satellite 30.

[0027] 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 thereof. ASIC stands for Application Specific Integrated Circuit, and FPGA stands for Field Programmable Gate Array.

[0028] FIG. 7 is a configuration diagram of a ground facility 700 provided in the satellite constellation forming system 600. The ground equipment 700 controls programs for multiple satellites in all orbital planes. The ground equipment 700 is an example of ground equipment. The ground equipment is composed of 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. The ground equipment may also include a communication device mounted on a moving object such as an aircraft, a self-propelled vehicle, or a mobile terminal.

[0029] The ground facility 700 forms the satellite constellation 20 by communicating with each satellite 30. The ground facility 700 is provided in the rocket launch support device 100. The ground facility 700 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 this other hardware. The hardware of the ground facility 700 is similar to the hardware of the rocket launch support device 100, which will be described later with reference to FIG. 9.

[0030] The ground facility 700 includes, as functional elements, an orbit control command generation unit 510 and an analysis and prediction unit 520. The functions of the orbit control command generation unit 510 and the analysis and prediction unit 520 are realized by hardware or software.

[0031] The communication device 950 transmits and receives signals for tracking and controlling each satellite 30 of the group of satellites 300 that make up the satellite constellation 20. The communication device 950 also transmits orbital maneuver commands 55 to each satellite 30. The analysis and prediction unit 520 analyzes and predicts the orbit of the satellite 30 . The orbital control command generator 510 generates the orbital control command 55 to be transmitted to the satellite 30 . The orbit control command generation unit 510 and the analysis prediction unit 520 implement the functions of the satellite constellation formation unit 11. That is, the orbit control command generation unit 510 and the analysis prediction unit 520 are an example of the satellite constellation formation unit 11.

[0032] FIG. 8 is a diagram showing an example of the functional configuration of the satellite constellation forming system 600. The satellite 30 further includes a satellite constellation forming unit 11b that forms the satellite constellation 20. The satellite constellation forming unit 11b of each satellite 30 of the multiple satellites and the satellite constellation forming unit 11 provided in each of the ground facilities 700 work together to realize the functions of the satellite constellation forming system 600. The satellite constellation forming unit 11b of the satellite 30 may be provided in the satellite control device 31.

[0033] FIG. 9 is a diagram showing an example of a satellite constellation near 42 degrees north latitude. There is a plan to develop a new rocket launch site in Taiki Town, Hokkaido, Japan, at 42 degrees north latitude. However, as shown in Figure 9, the sky above 42 degrees, 48 ​​degrees, and 53 degrees north latitude is a latitude zone where satellites that make up megaconstellations are densely concentrated. This makes it extremely difficult for launch operators to avoid collisions with satellites when launching rockets.

[0034] ***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 system 100 communicates with the management business device 40. The rocket launch support system 100 is mounted on the ground facility 701. The rocket launch support system 100 may also be mounted on the satellite constellation formation system 600. Alternatively, the rocket launch support system 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 system 100 may be mounted on a device of another business operator, such as an orbital analysis service provider.

[0035] The management business device 40 provides information about space objects 60, such as satellites or debris. The management business device 40 is a computer of an operator that collects information about space objects 60, such as satellites or debris. The management business equipment 40 includes equipment such as a megaconstellation business equipment 41, a LEO constellation business equipment 42, a satellite business equipment 43, an orbital transfer business equipment 44, a debris retrieval business equipment 45, a rocket launch business equipment 46, and an SSA business equipment 47. LEO is an abbreviation for Low Earth Orbit.

[0036] The megaconstellation business device 41 is a computer of a megaconstellation business operator that operates a megaconstellation business. The LEO constellation business equipment 42 is a computer of a LEO constellation business operator that operates a low earth orbit constellation, i.e., a LEO constellation business. The satellite business device 43 is a computer of a satellite operator that handles one to several satellites. The orbital transfer business device 44 is a computer of an orbital transfer business that provides support for the rocket launch of a satellite. The debris collection business device 45 is a computer of a debris collection business operator that carries out the business of collecting debris. The rocket launch business device 46 is a computer of a rocket launch business that operates a rocket launch business. The SSA business device 47 is a computer of an SSA business operator that performs the SSA business, i.e., the space situational awareness business.

[0037] The management business device 40 may be any other 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. In addition, if the rocket launch support device 100 is mounted on a public server of the SSA, the rocket launch support device 100 may be configured to function as the public server of the SSA. The information provided from the management business device 40 to the rocket launch support device 100 will be explained in detail later.

[0038] 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.

[0039] The rocket launch support device 100 includes, as functional elements, an area calculation unit 110, an area notification unit 120, and a storage unit 130. The storage unit 130 stores satellite orbit forecast information 51.

[0040] The functions of the area calculation unit 110 and the area notification unit 120 are realized by software. The storage unit 130 is provided in the memory 921. Alternatively, the storage unit 130 may be provided in the auxiliary storage device 922. Furthermore, the storage unit 130 may be divided into the memory 921 and the auxiliary storage device 922.

[0041] The 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 unit 110 and the area notification unit 120. The processor 910 is an integrated circuit (IC) that performs arithmetic processing. Specific examples of the processor 910 include a central processing unit (CPU), a digital signal processor (DSP), and a graphics processing unit (GPU).

[0042] The memory 921 is a storage device that temporarily stores data. Specific examples of the memory 921 include a static random access memory (SRAM) and a dynamic random access memory (DRAM). The auxiliary storage device 922 is a storage device that stores data. A specific example of the auxiliary storage device 922 is a HDD. The auxiliary storage device 922 may also be a portable storage medium such as an SD (registered trademark) memory card, CF, NAND flash, a flexible disk, an optical disk, a compact disk, a Blu-ray (registered trademark) disk, or a 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 (registered trademark). DVD is an abbreviation for Digital Versatile Disk.

[0043] The input interface 930 is a port connected to an input device such as a mouse, a keyboard, or a touch panel. Specifically, the input interface 930 is a USB (Universal Serial Bus) terminal. Note that the input interface 930 may also 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. Specifically, the output interface 940 is a USB terminal or an HDMI (registered trademark) (High Definition Multimedia Interface) terminal. Specifically, the display is an LCD (Liquid Crystal Display).

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

[0045] 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 an 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 part or all of the rocket launch support program may be incorporated into the OS.

[0046] The rocket launch support device 100 may include 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.

[0047] Data, information, signal values ​​and variable values ​​used, processed or output by the program are stored in memory 921, secondary storage device 922, or registers or cache memory within processor 910.

[0048] The "part" of each part of the rocket launch support system may be read as "processing," "procedure," "means," "stage," or "step." Also, the "processing" of the area calculation processing and area notification processing may be read as "program," "program product," or "computer-readable recording medium on which the program is recorded." The rocket launch support program causes a computer to execute each process, procedure, means, stage, or step of the rocket launch support system, where the "part" of each part is read 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, or each program may be provided as a program product.

[0049] ***Explanation of Operation*** FIG. 11 is a diagram showing an example of satellite orbit forecast information 51 according to this embodiment. The rocket launch support device 100 stores satellite orbit forecast information 51 in which forecast values ​​for the orbit of the space object 60 are set in the memory unit 130. The rocket launch support device 100 may, for example, acquire forecast values ​​for the orbit of each of the multiple space objects 60 from a management business device 40 used by a management business operator that manages multiple space objects 60, and store the information as satellite orbit forecast information 51. Alternatively, the rocket launch support device 100 may acquire satellite orbit forecast information 51 in which forecast values ​​for the orbit of each of the multiple space objects 60 are set from the management business operator, and store the information in the memory unit 130. The management operators are operators that manage 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 operator 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 collection business device 45, a rocket launch business device 46, and an SSA business device 47.

[0050] In the satellite orbit forecast information 51, information such as a space object ID (Identifier) ​​511, a forecast origin 512, forecast orbital elements 513, and a forecast error 514 is set, for example.

[0051] 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, the space object is an object such as a rocket launched into space, an artificial satellite, a space station, a debris collection satellite, a planetary exploration spacecraft, or a satellite or rocket that has become debris after completing its mission.

[0052] Predicted epoch 512 is the predicted epoch for the orbit of each of the plurality of space objects. The predicted orbital elements 513 are orbital elements that specify the orbit of each of the multiple space objects. The predicted orbital elements 513 are orbital elements that are predicted for the orbit of each of the multiple space objects. In Figure 11, the six Keplerian orbital elements are set as the predicted orbital elements 513.

[0053] The forecast error 514 is an error predicted for each orbit of a plurality of 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.

[0054] In the satellite orbit forecast information 51 according to this 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 orbital information of the space object, including the epoch and orbital elements, or the time and position coordinates, and explicitly shows the predicted values ​​of the space object 60 in the near future. The satellite orbit forecast information 51 may have a configuration other than that shown in FIG. 11, as long as it is information that explicitly indicates the near-future forecast values ​​of the space object 60.

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

[0056] FIG. 13 is a flow diagram of rocket launch support processing S100 by the rocket launch support device 100 according to this embodiment. In step S101, the region calculation unit 110 calculates a passable time region 111 based on the position coordinates of the rocket launch site 201 and the satellite orbit forecast information 51 in which the forecast values ​​of the satellite orbit are set. The passable time region 111 is a time region 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 other words, the passable time region 111 is a time region in which there is no risk of a rocket 202 launched from the rocket launch site 201, whose position coordinates are fixed and known, colliding with a satellite 30 constituting the satellite constellation 20 formed at a specific altitude.

[0057] FIG. 14 is a diagram showing an example in which a rocket 202 according to this embodiment is launched straight up. For example, assume that there exists a mega-constellation A consisting of approximately 2,500 satellites, formed at an orbital altitude of approximately 336 km and an orbital inclination of 42 degrees. Then, assume that a rocket 202 is launched directly overhead from a rocket launch site 201 established in Taiki Town, 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 a satellite 30 constituting the mega-constellation A at an altitude of 336 km. However, satellites flying in the same orbital plane are generally operated at intervals of 100 km or more. Therefore, there is a revisit waiting time of 10 seconds or more between the time one satellite passes overhead and the time the subsequent satellite passes. Satellites in adjacent orbital planes are also operated at a similar interval, but in order to avoid collisions with satellites in different orbital planes near 42 degrees north latitude, the satellites are controlled to pass through 42 degrees north latitude at a time that fills the gaps between them.

[0058] The region 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 during which a satellite happens to pass overhead as a "time period with collision risk." For example, the region calculation unit 110 may calculate the time period obtained by excluding the "time period with collision risk" from the time periods of a day as the passable time region 111. Alternatively, the region calculation unit 110 may calculate the time period obtained by excluding the "time period with collision risk" from the time period specified by the user as the passable time region 111. In this way, by excluding the "time period with collision risk" of a satellite in an orbital plane passing near the rocket launch site 201 from the time period, the "time period without collision risk," i.e., the passable time region 111, remains. If this information is disclosed to the rocket launch operator at the rocket launch site as an additional condition of the time period from launch until the rocket reaches a specific altitude, rockets can be launched without collision risk.

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

[0060] As described above, the region calculation unit 110 acquires the rocket launch prediction value Ox for the rocket 202 launched from the rocket launch site 201 to pass through the orbit of the satellite constellation 20. The region calculation unit 110 may calculate the passable time region 111 using the rocket launch prediction value Ox acquired from the rocket launch operator.

[0061] FIG. 16 is a diagram showing an example of a passable time region 111 in which a prediction error is expected according to this embodiment. For example, the rocket launch operator may have a significant prediction error in the position coordinates when passing at an altitude of 336 km. Alternatively, the megaconstellation operator may have a significant prediction error in the satellite pass time and position coordinates. Figure 16 shows that if such a prediction error exists, there is a concern that there will be no time region without collision risk, i.e., the passable time region 111, and suggests that a safe rocket launch will not be possible unless accuracy is improved.

[0062] 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.

[0063] 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 specific mega-constellation operator. The region calculation unit 110 calculates a passable time region 111 for each of the plurality of orbital altitudes. The region notification unit 120 displays, on a display device, a time region that combines the plurality of passable time regions 111 calculated for each of the plurality of orbital altitudes.

[0064] FIG. 17 is a diagram showing display example 1 and display example 2 of 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.

[0065] 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 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 only a necessary condition for the "time region without collision risk in all orbits," and is not a sufficient condition.

[0066] For example, assume that the following satellite constellation 20 exists: Orbital altitude approximately 336km: Orbital inclination 42 degrees, approximately 2500 aircraft Orbital altitude approximately 341km: Orbital inclination 48 degrees, approximately 2500 aircraft Orbital altitude approximately 346km: Orbital inclination 53 degrees, approximately 2500 aircraft

[0067] The rocket launch support device 100 according to this embodiment integrates the "time region without risk of collision," i.e., the passable time region 111, for the above three altitudes and for multiple or all orbital altitudes operated by the same megaconstellation operator. Then, as shown in display example 2 of Fig. 17, the "time region without risk of collision in multiple orbits" is displayed as the passable time region 111. As a result, the rocket launch operator can launch all satellites operated by the megaconstellation operator safely without collisions.

[0068] Alternatively, the satellite constellation 20 may be a plurality of satellite constellations operated by a plurality of different satellite constellation operators. In this case, the region calculation unit 110 calculates the passable time region 111 for each of the plurality of satellite constellations. The region notification unit 120 then displays the passable time region 111 for each of the plurality of satellite constellations.

[0069] FIG. 18 is a diagram showing a display example 3 of the passable time region 111 according to the present embodiment. In FIG. 18, a transit time region 111 for a plurality of megaconstellation operators A and B is displayed. High-precision forecast values ​​for the satellites that make up a mega-constellation are usually held exclusively by the mega-constellation operator, making it difficult for a third party to share high-precision forecast values ​​from multiple mega-constellation operators. Furthermore, at this stage, if SPACE-X can pass through the orbital plane it plans to establish for its Starlink concept without a collision, the risk of a collision with satellites from another megaconstellation during launch is actually sufficiently small. However, there is a possibility that in the future, a different megaconstellation operator may build another megaconstellation at an altitude of, for example, around 400 km. For this reason, display example 3 in Figure 18 is suitable for achieving a launch without a collision with any megaconstellation. When mega-constellation operators, rocket launch operators, and operators providing support services using rocket launch support equipment span multiple countries, it would be desirable to establish international rules for the disclosure of high-precision forecast values ​​in international coordination to avoid space collisions and in the development of space laws.

[0070] The display examples of the passable time region 111 in FIGS. 17 and 18 are merely examples, and any display format may be used as long as the passable time region 111 can be notified.

[0071] ***Explanation of the effect of this embodiment*** The rocket launch support device according to this embodiment can notify the rocket launch operator of the time range over which a rocket launched from a rocket launch site can pass. In this way, by disclosing the time range over which a rocket can pass to the rocket launch operator at the rocket launch site, with the time it takes for the rocket to reach a specific altitude after launch as an additional condition, the rocket can be launched without the risk of collision.

[0072] ***Other Configurations*** <Variation 1> The rocket launch support system acquires space object information from a space information recorder that records space object information acquired from a management business device used by a management business that manages multiple space objects. The rocket launch support system then assists in avoiding collisions between rockets and space objects during launch. The rocket launch support system of this embodiment includes a database that stores space object information obtained from a space information recorder, and a server that supports avoidance of collisions between rockets and space objects during launch.

[0073] Specifically, the database may be a memory, an auxiliary storage device, 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 be equipped with the space information recorder. The space information recorder may also include satellite orbit forecast information.

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

[0075] The database acquires and stores rocket space object information and satellite orbit forecast information for mega-constellation satellites from a space information recorder. The rocket space object information is information acquired by the space information recorder from the rocket launch operator's management business device. The mega-constellation satellite orbit forecast information is information acquired by the space information recorder from the mega-constellation management business device with which there is a risk of rocket collision. The rocket space object information includes the location coordinates of the rocket launch site, rocket launch schedule time information, and forecast orbit information.

[0076] The server comprises the following stages: The stage where the delay time and orbital position of the rocket, launched at the scheduled launch time, is analyzed from the coordinates of the rocket launch site to arrive near the satellite constellation. - The stage of determining the relative distance A between the rocket and other space objects, which serves as an indicator of the flight safety zone. -Determining the relative distance B between the rocket and other space objects, which is an indicator of the collision risk zone. The stage where satellites in the satellite constellation that may approach closer than relative distance B are extracted and identified as satellites requiring attention. The stage where a safe time region is extracted in which all of the satellites of concern fly simultaneously at a distance greater than relative distance A. - Displaying the safe time area. A step of displaying a safety confirmation message if the scheduled launch time of the rocket is within the safety time range. When the scheduled launch time of the rocket is not included in the safe time range, a recommended launch time from within the safe time range is displayed as a message recommending a change to the launch time. This is the stage where a safety confirmation message or a message recommending a change in the launch time is sent to the launch vehicle operator.

[0077] A safe time region is an example of a time region where there is no risk of collision.

[0078] FIG. 25 is a diagram showing an example of a relative distance A between a rocket and another space object, which serves as an index of a flight safety area according to a modification of this embodiment. FIG. 26 is a diagram showing an example of a relative distance B between a rocket and another space object, which serves as an indicator of a collision risk area according to a modification of this embodiment. As shown in Figure 25, when the server determines the relative distance A between the rocket and another space object, which serves as an indicator of the flight safety area, it is necessary to consider the size of the space object to include an error range. Also, as shown in Figure 26, when the server determines the relative distance B between the rocket and another space object, which is an indicator of the collision risk area, the actual relative distance when the relative distance is considered to be the size of the space object, including the error range, and is less than or equal to 0, becomes the relative distance B.

[0079] FIG. 27 is a diagram showing a state in which the flight safety area is not secured according to a modification of this embodiment. The top part of Figure 27 is a diagram of a megaconstellation modeled in two-dimensional space. The bottom part of Figure 27 shows a state in which the relative distance between the rocket and the space object is almost 0 (because the object dimensions are considered to include errors), and although a collision does not occur, the flight safety area has not been secured.

[0080] 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 Figure 28 is a diagram showing a state in which a flight safety area according to this embodiment is secured. Specifically, the upper part of Figure 28 shows a state in which a flight safety area for a rocket is secured within the mega-constellation operator's own system. Within the mega-constellation operator's own system, there is a possibility that the amount of error can be reduced by using techniques 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.

[0081] On the other hand, the bottom panel of Figure 28 shows a case where the precise forecast values ​​of megaconstellations are not made public and have large errors. If megaconstellation operators do not disclose the amount of error, the megaconstellation forecast values ​​will have to rely on external measurement information from SSA operators. If launch vehicle operators only have access to forecast values ​​with large errors, there is a concern that the launch window will not be secured. In other words, if launch vehicle operators and megaconstellation operators monopolize precise orbit forecast values, there is a concern that the launch business will be monopolized.

[0082] <Variation 2> In this embodiment, the functions of the rocket launch support device 100 are realized by software. As a modification, the functions of the rocket launch support device 100 may be realized by hardware.

[0083] FIG. 19 is a diagram showing the configuration of a rocket launch support device 100 according to a modified example of this 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. The 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, where GA is an abbreviation for Gate Array. The functions of the rocket launch support device 100 may be realized by a single electronic circuit, or may be realized by distributing the functions across multiple 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.

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

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

[0086] ***Configuration Description*** FIG. 20 is a diagram showing the configuration of a rocket launch support device 100 according to this embodiment. In this embodiment, the region calculation unit 110 calculates the feasible pass region 112. Then, the region notification unit 120 outputs the feasible pass region 112 calculated by the region calculation unit 110. Other configurations are the same as those in the first embodiment.

[0087] ***Explanation of Operation*** FIG. 21 is a flow diagram of the 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 the possible pass area 112 based on the position coordinates of the rocket launch site 201 and the satellite orbit forecast information 51 in which the predicted values ​​of the satellite orbit are set. The possible pass area 112 is a pass 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.

[0088] In step S102a, the area notification unit 120 outputs the possible passing area 112. For example, the area notification unit 120 displays the possible passing 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 passing area 112 via the communication device 950. This allows the launch control device 200 to launch the rocket 202 while avoiding collisions using the feasible passage area 112.

[0089] Figure 22 shows an image of the satellite flying at an orbital altitude of around 340 km. FIG. 23 is a diagram showing an example of a satellite constellation at an orbital altitude of about 340 km. FIG. 24 is a diagram showing an example of a rocket launch. A specific example of a rocket launch will be described with reference to FIGS.

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

[0091] As shown in Figures 22 and 23, there are plans to build a constellation of approximately 7,500 satellites at an altitude of around 340 km and an orbital inclination of less than 50 degrees. After this plan is completed, there is a possibility that a launch window will not exist if a rocket is launched directly overhead or southward from a rocket launch site in Hokkaido, for example. Rockets launched from launch sites at latitudes above 40 degrees north and passing through high-latitude orbits at altitudes of 300 km or more and latitudes above 50 degrees north will pass through areas near the poles where there are no megaconstellations, allowing for safe launches without the risk of collision. Currently, there are plans to develop a rocket launch site in Taiki, Hokkaido, at approximately 42 degrees north latitude. Additionally, there are plans within the mega-constellation concept to operate approximately 2,500 satellites in an orbit at an altitude of approximately 340 km and an inclination of 42 degrees. Because 42 degrees north latitude is a densely packed area where satellites turn around, it is difficult to secure a launch window directly overhead. Furthermore, there are plans for an orbit with an inclination of 50 degrees, and it would be extremely difficult to launch southward without colliding with these constellations. On the other hand, since the above constellation satellites do not exist above 50 degrees north latitude, this has the advantage of allowing launches to avoid collisions.

[0092] As shown in Figure 24, if the launch is from Taiki Town at 42 degrees north latitude, the orbit should pass through the northern part of the latitude of 336 km at 42 degrees north latitude, 346 km at 53 degrees north latitude, and 590 km at 56 degrees north latitude, making it possible to launch without the risk of collision with the megaconstellation.

[0093] ***Explanation of the Effects of the Present Embodiment*** The rocket launch support device according to this embodiment displays a possible passage area where a rocket launched from a rocket launch site with fixed and known position coordinates does not risk colliding with a satellite constellation formed at a specific altitude, thereby enabling the rocket launch operator to launch while avoiding collisions.

[0094] In the above first and second embodiments, 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 same as that of the above-described embodiments. The functional blocks of the rocket launch support device may have any configuration as long as they can realize the functions described in the above-described embodiments. Furthermore, the rocket launch support device may be a single device or a system composed of multiple devices.

[0095] Furthermore, it is possible to combine multiple parts of the first and second embodiments. Alternatively, it is possible to implement only one part of these embodiments. In addition, it is possible to implement any combination of these embodiments, 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.

[0096] It should be noted that the above-described embodiment is essentially a preferred example and is not intended to limit the scope of the present invention, the scope of 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. [Explanation of symbols]

[0097] 20 Satellite constellation, 21 Orbital plane, 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 Megaconstellation business device, 42 LEO constellation business device, 43 Satellite business device, 44 Orbital transfer business device, 45 Debris collection business device, 46 Rocket launch business device, 47 SSA business device, 51 Satellite orbit forecast information, 511, 521 Space object ID, 512 Forecast origin, 513 Forecast orbital elements, 514 Forecast error, 60 Space object, 70 Earth, 100 Rocket launch support device, 110 Area calculation unit, 111 Possible passage time area, 112 Possible passage area, 120 Area notification unit, 130 Memory 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 unit, 520 analysis prediction unit, 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 prediction value.

Claims

1. A rocket that is launched from a rocket launch site located at a latitude of 40 degrees north or higher below the latitude band where satellites constituting a mega-constellation fly densely in the sky, into an orbit at an altitude of 300 km or higher and in a latitude direction of 50 degrees north or higher; a rocket launch support device that supports the launch of the rocket so as to avoid collision between the rocket and the satellites that constitute the megaconstellation; Equipped with The rocket launch support device is Calculate the feasible transit area, which is the transit area passing through the megaconstellation-free area near the pole, The rocket is A rocket system launched into an orbit that includes the feasible passage region.

2. A rocket launch method in which a rocket is launched from a rocket launch site located at a latitude of 40 degrees north or higher, below the latitude band where satellites constituting a mega-constellation fly densely in the sky, into an orbit at an altitude of 300 km or higher and in a latitudinal direction at a latitude of 50 degrees north or higher, the orbit including a possible passage area, which is a passage area calculated to pass through an area near the pole where no mega-constellation is present.

3. The rocket launch support device 2. The rocket system according to claim 1, wherein the feasible passage area is calculated based on the position coordinates of the rocket launch site and satellite orbit forecast information in which predicted values ​​of the orbits of the satellites that make up the megaconstellation are set.

4. 3. A rocket launch method according to claim 2, wherein the feasible passage area is calculated based on the position coordinates of the rocket launch site and satellite orbit forecast information in which predicted values ​​of the orbits of the satellites that make up the megaconstellation are set.

Images