Space traffic management systems, space traffic management devices, rocket launch business devices, debris removal business devices, space situation monitoring business devices, risk avoidance support business devices, and space insurance business devices

Abstract

To allow a plurality of management business operators managing space objects flying in space to efficiently share and carry out danger analysis.SOLUTION: A plurality of space traffic management devices 100 each include all of: space traffic management rule information; a space information recorder 101; a danger alarm device 102; and a danger analysis device 103. Further, the plurality of space traffic management devices 100 each include all of: a danger avoidance action assist device 104 for displaying role division of an avoidance action against a space object; a danger avoidance action implementation plan; a measurement error close-inspection device; and a security device 105 for preventing information falsification. The space information recorder 101 includes all of: on-orbit object number management information; and flight safety measure information which is information on an orbital altitude of each orbital plane for ensuring flight safety.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present invention relates to a space traffic management system, a space traffic management device, a satellite business device, a satellite constellation business device, a mega-constellation business device, a rocket launch business device, a debris removal business device, a space situation monitoring business device, a danger avoidance support business device, a space insurance business device, a space information recorder, a danger warning device, a danger analysis device, a danger avoidance action support device, and a security device. [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] Patent Document 1 discloses a technique for forming a satellite constellation consisting of multiple satellites in the same circular orbit.

[0004] Conventionally, the US Combined Space Operations Center (CSpOC) has been monitoring space objects continuously and issuing warnings when it predicts that two space objects may approach or collide with each other. In response to these warnings, manned space stations and commercial communications satellites implement evasive maneuvers if deemed necessary. [Prior art documents] [Patent documents]

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

[0006] With the increase in space debris, the rise in the number of satellites due to the emergence of mega-constellations, and improvements in ground-based surveillance capabilities, it is becoming difficult to continue the traditional warning service provided by the US CSpOC. However, Patent Document 1 does not describe a method for avoiding collisions with space objects that arise with the increase in debris in space, the increase in the number of satellites due to the emergence of megaconstellations, and improvements in ground surveillance capabilities.

[0007] The present invention aims to enable multiple management companies that manage space objects flying in space to efficiently share and carry out risk analysis in response to the increase in debris in space, the increase in the number of satellites due to the emergence of megaconstellations, and improvements in ground monitoring capabilities. [Means for solving the problem]

[0008] The space traffic management system according to the present invention comprises: A space traffic management system is provided which is implemented in a business device that manages space objects flying in space and has a space traffic management device that manages the flight safety of space objects, The space traffic control device comprises: Space traffic management rules information, a space information recorder that records orbital information of a space object; a danger warning device that warns of the danger of approach or collision with a space object; a hazard analysis device for analyzing the trajectory of a space object; a danger avoidance behavior support device that displays the role allocation of avoidance behavior of space objects; Hazard avoidance action plan, a measurement error inspection device; A security device to prevent information tampering; It has all of the above. The space information recorder comprises: Orbital object number management information; Flight safety measure information, which is information on the orbital altitude for each orbital plane to ensure flight safety; It has all of the above. [Effects of the Invention]

[0009] The space traffic management system according to the present invention has the advantage that multiple management companies that manage space objects flying in space can efficiently share and carry out risk analysis. [Brief explanation of the drawings]

[0010] [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] FIG. 1 is a configuration diagram of a space traffic management system according to a first embodiment. [Figure 10] 3 shows an example of orbit forecast information according to the first embodiment. [Figure 11] FIG. 1 is a configuration diagram showing Example 1-2 of a space traffic control device according to the first embodiment. [Figure 12] FIG. 5 shows an example 5-2 of a space traffic management system according to the first embodiment. [Figure 13] FIG. 5 is a configuration diagram showing an example 5-3 of a space traffic management system according to the first embodiment. [Figure 14]FIG. 1 is a diagram showing an example of a space information recorder according to a first embodiment. [Figure 15] FIG. 1 is a diagram showing an example of a danger warning device according to a first embodiment. [Figure 16] FIG. 5 shows an example 5-4 of a space traffic management system according to the first embodiment. [Figure 17] FIG. 5 shows an example 5-5 of a space traffic management system according to the first embodiment. [Figure 18] FIG. 1 is a diagram showing an example of a space information recorder according to a first embodiment. [Figure 19] 3 is a flowchart of a space traffic management process performed by the space traffic management system according to the first embodiment. [Figure 20] 10 shows an example of a predicted orbit of debris passing through a satellite constellation and an intrusion warning according to the first embodiment. [Figure 21] An example of the risk of collision between a satellite constellation and debris when there is no error. [Figure 22] An example of the risk of collision between a satellite constellation and debris when there is an error. [Figure 23] FIG. 10 is a configuration diagram of a space traffic management system according to a modified example of the first embodiment. [Figure 24] FIG. 10 is a diagram showing an example 1-3 of a space traffic control device according to the second embodiment. [Figure 25] FIG. 5 shows an example 5-5 of a space traffic management system according to the second embodiment. [Figure 26] FIG. 10 is a diagram showing an example of dense region identification information according to the second embodiment. [Figure 27] FIG. 10 is a diagram showing an example of danger area identification information according to the second embodiment. [Figure 28] FIG. 10 is a diagram showing an example of danger area identification information according to the second embodiment. [Figure 29] FIG. 10 is a diagram showing an example of danger area identification information according to the second embodiment. [Figure 30] FIG. 10 is a diagram showing an example of danger area identification information according to the second embodiment. [Figure 31] FIG. 10 is a diagram showing an example 1-4 of a space traffic control device according to the third embodiment. [Figure 32] FIG. 5 shows an example 5-7 of a space traffic management system according to the third embodiment. [Figure 33] FIG. 5 shows an example 5-8 of a space traffic management system according to the third embodiment. [Figure 34] FIG. 34 is a diagram showing details of the configuration of each business device in Example 5-8 of the space traffic management system 500 of FIG. 33 according to the third embodiment. [Figure 35] FIG. 34 is a diagram showing details of the configuration of each business device in Example 5-8 of the space traffic management system 500 of FIG. 33 according to the third embodiment. [Figure 36] FIG. 34 is a diagram showing details of the configuration of each business device in Example 5-8 of the space traffic management system 500 of FIG. 33 according to the third embodiment. [Figure 37] FIG. 34 is a diagram showing details of the configuration of each business device in Example 5-8 of the space traffic management system 500 of FIG. 33 according to the third embodiment. [Figure 38] FIG. 10 is a diagram showing the effect of Example 5-8 of the space traffic management system 500 according to the third embodiment. [Figure 39] 10 shows an example of the orbit of debris that enters the satellite orbital region according to the fourth embodiment. [Figure 40] FIG. 10 is a configuration diagram of a debris removal control device according to a fourth embodiment. [Figure 41] FIG. 10 is a diagram showing the configuration of a debris removal satellite according to a fourth embodiment. [Figure 42] 10 shows an example of the orbit of debris that enters the satellite orbital region according to the fourth embodiment. [Figure 43] FIG. 13 is a configuration diagram of an example 5-9 of a space traffic management system 500 according to the sixth embodiment. [Figure 44] FIG. 13 is a configuration diagram of an example 5-10 of a space traffic management system 500 according to the sixth embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] Embodiment 1 An example of a satellite constellation that is the premise of the space traffic management system according to the following embodiment will be described.

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

[0014] 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 in 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.

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

[0016] Fig. 3 is an example of a satellite constellation 20 having multiple orbital planes 21 that intersect near the polar regions, and 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.

[0017] 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 diversifies the locations where a collision of satellites 30 may occur. Satellites 30 are also called artificial satellites.

[0018] 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 space traffic control (STM) is increasing.

[0019] Furthermore, for the orbital transfer of space objects, there is an increasing need for post-mission disposal (PMD) after the end of an on-orbit mission, or for ADR, which uses external means such as debris removal satellites to remove debris such as failed satellites and floating rocket upper stages. International discussions on the need for such ADR have begun, known as STM. Here, PMD is an abbreviation for Post Mission Disposal, ADR is an abbreviation for Active Debris Removal, and STM is an abbreviation for Space Traffic Management.

[0020] Furthermore, with the strengthening of the Space Situational Awareness (SSA) system, including international cooperation, and the improvement of observation accuracy, the size of space objects that can be monitored has become smaller, and the total number of space objects that can be monitored has also increased.

[0021] The dramatic increase in the number of space objects accompanying the construction of mega-constellations is one of the causes of the increased risk of collisions in space. However, even if collisions between artificial space objects can be avoided through human activities such as the STM, the risk of chain collisions triggered by collisions of debris floating in space remains a serious problem. Even if the debris itself is a very small object, if the collision conditions are such that the relative velocity is high, there is a risk that the satellite will be destroyed explosively, and there is a risk that the scattered fragments will cause a chain reaction of higher-level damage. A mega-constellation with several thousand satellites has been announced, with around 2,500 satellites flying at the same altitude. During normal operation, the mainstream approach is to avoid collisions within the system by managing the time position of the previous satellite. However, if a debris collision triggers an anomaly in the orbital attitude control of one satellite, causing it to deviate from the initial time management control, or if debris is scattered, there is a very high risk of it colliding with other satellites flying at the same orbital altitude.

[0022] To avoid such collision risks, it is rational to centrally manage debris orbital information and megaconstellation orbital information and conduct collision prediction analysis. It has been said that in the SSA domain, it is possible to monitor approximately 20,000 basketball-sized pieces of debris. Furthermore, with future improvements to monitoring capabilities, known as the US Space Fence, it is said that it will be possible to monitor 200,000 softball-sized pieces. Even if an SSA operator were to maintain and update information on 200,000 pieces of debris, there would be many challenges in centrally managing the orbital information of more than 10,000 satellites owned by a mega-constellation operator. For example, if the satellites use their own orbital attitude control systems in addition to orbital predictions based on natural phenomena, the effects of these control systems would need to be reflected in the orbital prediction analysis, which would require a huge amount of work. Furthermore, mega-constellation operators may not always provide the SSA operator with the most up-to-date and accurate satellite information. Furthermore, monitoring 200,000 pieces of debris is by no means sufficient. Even tiny pieces of debris smaller than a softball could potentially destroy a satellite. Therefore, in the future, there will be an increasing need to monitor even smaller and larger amounts of debris. On the other hand, it is not realistic for a mega-constellation operator to centrally manage information on as many as 200,000 pieces of debris, given the amount of work involved. Furthermore, it is not easy to centrally consolidate information from multiple mega-constellation operators.

[0023] Under the circumstances described above, it is ideal for SSA operators to provide debris orbital information to mega-constellation operators, who then conduct collision analysis with satellites within their own systems. Mega-constellations have thousands of satellites flying at specific orbital altitudes. Therefore, if debris orbital information includes predicted time, position, and velocity vector information for passing through the specific orbital altitude operated by the mega-constellation, mega-constellation operators will be able to identify satellites at risk of collision and conduct collision prediction analysis.

[0024] 5 to 8, an example of satellites 30 and ground equipment 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 a satellite constellation business operator such as a megaconstellation business equipment 41, a LEO constellation business equipment 42, or a satellite business equipment 43.

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

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

[0027] 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 the other hardware. The hardware of the satellite constellation forming system 600 is similar to the hardware of the space traffic control device 100, which will be described later with reference to FIG. 9.

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

[0029] 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. It also comprises other components that realize various functions, but Fig. 6 will explain 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. The satellite 30 is an example of a space object 60.

[0030] 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 apogee kick motor, a chemical propulsion device, or an electric propulsion device. The apogee kick motor (AKM) is an upper stage propulsion device used to put an artificial satellite into orbit, and is also called an apogee motor (when a solid rocket motor is used) or an apogee engine (when a liquid engine is used). Chemical propulsion systems are thrusters that use monopropellant or bipropellant fuels. Electric propulsion systems include ion engines and Hall thrusters. An apogee kick motor is a device used for orbital transfer and can also be a type of chemical propulsion system. 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.

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

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

[0033] The ground facility 700 forms the satellite constellation 20 by communicating with each satellite 30. The ground facility 700 is provided in the space traffic control 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 space traffic control device 100, which will be described later in FIG. 9.

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

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

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

[0037] ***Configuration Description*** The space traffic management system 500 includes a space traffic management device 100. The space traffic management system 500 is also called a space object intrusion warning system. The space traffic management device 100 is also called a space object intrusion warning device.

[0038] The space traffic management system 500 comprises a plurality of space traffic management devices 100, each installed in the business equipment of a plurality of management operators that manage space objects flying in space. The space traffic management devices 100 each perform flight safety management for space objects. The plurality of space traffic management devices 100 are connected to each other via communication lines.

[0039] FIG. 9 is a configuration diagram showing Example 5-1 of a space traffic management system 500 and Example 1-1 of a space traffic control device 100 according to this embodiment. The space traffic control device 100 communicates with other management business devices 40. The space traffic control device 100 may be mounted on a ground facility 701. The space traffic control device 100 may also be mounted on a satellite constellation forming system 600.

[0040] 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 megaconstellation business equipment 41, LEO constellation business equipment 42, satellite business equipment 43, orbital transfer business equipment 44, debris removal business equipment 45, rocket launch business equipment 46, and SSA business equipment 47. LEO is an abbreviation for Low Earth Orbit.

[0041] The megaconstellation business device 41 is a computer of a megaconstellation business operator that operates a large-scale satellite constellation, that is, 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 the orbital transfer business that issues space object intrusion warnings to satellites. The debris removal business device 45 is a computer of a debris removal 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 carries out 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.

[0042] 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 space traffic management system 500. In addition, when space traffic management device 100 is mounted on a public server of SSA, space traffic management device 100 may be configured to function as the public server of SSA. The information provided from the management business device 40 to the space traffic control device 100 will be explained in detail later.

[0043] Space traffic control 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. Processor 910 is connected to the other hardware via signal lines and controls the other hardware.

[0044] The space traffic control device 100 includes, as examples of functional elements, a passage determination unit 110, an alarm generation unit 120, an alarm notification unit 130, and a storage unit 140. The storage unit 140 stores orbit forecast information 51.

[0045] The functions of the passage determination unit 110, the warning generation unit 120, and the warning notification unit 130 are realized by software. The storage unit 140 is provided in the memory 921. Alternatively, the storage unit 140 may be provided in the auxiliary storage device 922. Furthermore, the storage unit 140 may be provided separately in the memory 921 and the auxiliary storage device 922. 9, the space traffic control device 100 is described as realizing the space object intrusion warning function. However, as will be described later, the space traffic control device 100 has various functions other than the space object intrusion warning function.

[0046] The processor 910 is a device that executes a space traffic management program. The space traffic management program is a program that realizes the functions of each component of the space traffic control device 100 and the space traffic management system 500. 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).

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

[0048] 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).

[0049] 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 space traffic control device 100 communicates with the management business device 40 via the communication device 950.

[0050] The space traffic management program is loaded into processor 910 and executed by processor 910. Memory 921 stores not only the space traffic management program but also an OS (Operating System). Processor 910 executes the space traffic management program while executing the OS. The space traffic management program and the OS may be stored in auxiliary storage device 922. The space traffic management program and the OS stored in auxiliary storage device 922 are loaded into memory 921 and executed by processor 910. Note that part or all of the space traffic management program may be incorporated into the OS.

[0051] Space traffic control device 100 may include multiple processors that replace processor 910. These multiple processors share the task of executing a program. Each processor is a device that executes a program, just like processor 910.

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

[0053] The "parts" of each part of the space traffic control device may be read as "processing," "procedure," "means," "stage," or "step." Also, the "processing" of the passage determination process, warning generation process, and warning notification process may be read as "program," "program product," or "computer-readable recording medium on which a program is recorded." "Processing," "procedure," "means," "stage," or "step" may be read as interchangeable with each other. The space traffic management program causes a computer to execute each process, procedure, means, stage, or step of the space traffic management system, where "part" is replaced with "process," "procedure," "means," "stage," or "process." The space traffic management method is a method carried out by the space traffic management device 100 executing the space traffic management program. The space traffic management program may be provided in a form stored on a computer-readable recording medium, or each program may be provided as a program product.

[0054] FIG. 10 is a diagram showing an example of orbit forecast information 51 according to this embodiment. The space traffic management device 100 stores in the memory unit 140 orbit forecast information 51 in which forecast values ​​for the orbits of the space objects 60 are set. The space traffic management device 100 may, for example, acquire forecast values ​​for the orbits of each of the multiple space objects 60 from a management business device 40 used by a management company that manages multiple space objects 60, and store the acquired orbit forecast information 51. Alternatively, the space traffic management device 100 may acquire from the management company orbit forecast information 51 in which forecast values ​​for the orbits of each of the multiple space objects 60 are set, and store the acquired orbit forecast information 51 in the memory unit 140. 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 removal business device 45, a rocket launch business device 46, and an SSA business device 47.

[0055] The orbit forecast information 51 includes satellite orbit forecast information 52 and debris orbit forecast information 53. The satellite orbit forecast information 52 includes forecast values ​​for satellite orbits. The debris orbit forecast information 53 includes forecast values ​​for debris orbits. In this embodiment, the satellite orbit forecast information 52 and the debris orbit forecast information 53 are included in the orbit forecast information 51, but the satellite orbit forecast information 52 and the debris orbit forecast information 53 may also be stored in the storage unit 140 as individual pieces of information.

[0056] In the 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.

[0057] The space object ID 511 is an identifier that identifies the space object 60. In Fig. 10, 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 removal satellite, a planetary exploration spacecraft, or a satellite or rocket that has become debris after completing its mission.

[0058] 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 10, six Keplerian orbital elements are set as the predicted orbital elements 513.

[0059] 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, a cross-directional error, and the basis for the error. In this way, the forecast error 514 explicitly indicates the amount of error contained in the actual value along with the basis. The basis for the amount of error includes some or all of the measurement means, the details of data processing performed as a means for improving the accuracy of position coordinate information, and the results of statistical evaluation of past data.

[0060] In the 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 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 orbit forecast information 51. In this way, the 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 indicates the predicted values ​​of the space object 60 in the near future.

[0061] Next, a description will be given of another example of the space traffic control device 100 and the space traffic management system 500. The hardware configuration of the space traffic control device 100 is as described above.

[0062] FIG. 11 is a configuration diagram showing Example 1-2 of the space traffic control device 100 according to this embodiment. FIG. 12 is a diagram showing an example 5-2 of a space traffic management system 500 according to this embodiment. The space traffic management system 500 includes multiple space traffic control devices 100, which are connected to each other via communication lines. A space traffic control device 100 is provided in each of the multiple management business devices 40. Hereinafter, the management business device 40 may be simply referred to as a business device.

[0063] The space traffic control device 100 includes a space information recorder 101 , a danger warning device 102 , a danger analysis device 103 that analyzes the orbit of space objects, a danger avoidance action support device 104 , and a security device 105 . The space information recorder 101 records orbital information of a space object. A specific example of the space information recorder 101 is orbital forecast information 51 in FIG. The danger warning device 102 warns of the danger of approaching or colliding with a space object. The risk analysis device 103 performs trajectory analysis of space objects. The danger avoidance behavior support device 104 displays the role allocation of the avoidance behavior of the space object. The security device 105 prevents information from being tampered with.

[0064] The space information recorder 101 includes a space object ID for identifying a space object, orbital information, and disclosure condition information, as well as a business device ID for identifying a business device and disclosure condition information. The multiple space traffic control devices 100 have compatible data formats, share space object IDs and business device IDs, and share orbit information corresponding to the space object IDs between business devices that comply with the disclosure condition information.

[0065] There was a system in place where a single operator centrally managed all information on monitorable space objects and issued an alert if a collision risk was predicted. However, with the increase in the total number of objects in space and the increase in the number of identifiable objects in SSA, it has become difficult to realize a space traffic management system in which a single operator updates the orbital information of all space objects in real time, and a system for decentralized management of orbital information is required. In addition, with the emergence of mega-constellation operators, it has become difficult to share operator management information for real-time orbital control of constellations of over 1,000 satellites with other operators, making it difficult for operators other than mega-constellation operators to conduct collision analysis of space objects, including mega-constellation satellites. On the other hand, it is difficult for megaconstellation operators to conduct collision analysis that includes orbital information for all space objects, so a new mechanism for realizing collision analysis is needed. Furthermore, it is reasonable to handle orbital information for space objects with different accuracy and update frequency depending on the purpose, such as real-time high-precision orbital information for tracking and controlling one's own space object in real time and orbital control, and coarse-precision orbital information for disclosure to other operators. Therefore, there is a long-awaited mechanism that allows for compatibility of data formats and sharing of identification IDs, and allows for the selection of operators with whom to share information depending on the purpose, and for the content of the information to be shared to be scrutinized. Furthermore, if an approach that poses a risk of collision in orbit or an intrusion into a dangerous area is predicted, information must be shared quickly and with minimal effort. Furthermore, to avoid the risk of collision, it is effective to take action to avoid collisions by manually controlling the trajectory, but it is necessary to clarify the division of roles as to which object will take action to avoid collisions when a collision is predicted.

[0066] According to the space traffic management system 500 shown in Figures 11 and 12, orbital information is managed in a decentralized manner, and if other operators report the intrusion of a space object into the danger zone where the megaconstellation satellites are flying, the megaconstellation operators themselves can perform collision analysis. In addition to being able to share necessary information during peacetime, it can also provide an environment where risk analysis can be performed using only the ID of a space object that is predicted to pose a risk. This has the effect of enabling information sharing to be achieved quickly and with minimal effort, and enabling early risk avoidance actions to be taken. Furthermore, by providing risk avoidance behavior support that provides rational options for risk avoidance behavior in advance, countermeasures can be taken early, which has the effect of greatly reducing risk.

[0067] FIG. 13 is a configuration diagram showing an example 5-3 of a space traffic management system 500 according to this embodiment.

[0068] In FIG. 13, the business equipment in the space traffic management system 500 is composed of all or some of the following business equipment: ·Government business equipment that manages domestic and international government satellites. Space agency business unit that manages satellites owned by domestic and international space agencies. Mega-constellation business unit that manages satellite constellations consisting of more than 100 satellites. Constellation business equipment that manages satellite constellations consisting of 10 or more satellites. · Satellite business constellations consisting of a single satellite or a small number of satellites (less than 10). Rocket launch equipment. · SSA business equipment for managing naturally occurring space object information. -SSA business equipment that manages artificial space object information. Debris removal equipment that captures and removes space debris. - A risk avoidance support business device that manages support information to prevent collision accidents involving space objects. ·Space insurance business unit that operates space insurance.

[0069] The example 5-3 of the space traffic management system 500 shown in FIG. 13 has the advantage that all operators of artificial space objects can share information, regardless of whether they are public or private. It also has the effect of enabling operators of various space objects, such as mega-constellation satellites, small and medium-sized constellations, individual satellites, rockets, and debris removal satellites, to share information. Another benefit is that information can be shared with SSA operators who collect information on objects in space using ground-based radar or telescopes and manage the information in a database. Furthermore, by sharing information with space insurance companies, it will be possible to rationally prepare for peacetime situations in response to the prediction of collisions with space objects, and to rationally respond to emergencies by providing compensation for damages after a collision accident occurs.

[0070] In addition, flight safety management of space objects consists of all or part of the following management: - Orbital management of space objects. -Manage rocket launch timing. Deorbit trajectory management of space objects. - Collision prediction and management between multiple space objects. · Space object surveillance and management. - Collision prevention management of multiple space objects. - Information management after a collision occurs. - Managing damage compensation after a collision accident.

[0071] As described above, by configuring flight safety management for space objects, it is possible to ensure flight safety in mega-constellation projects in which several thousand satellites fly at the same nominal orbital altitude. Furthermore, this has the effect of ensuring flight safety not only for satellites in regular operation, but also for rockets in the middle of launch, space objects in the middle of orbital transfer, space objects in the middle of deorbit, and debris removal satellites. Furthermore, danger warnings can be sent and received quickly and with minimal effort from SSA operators and analysis companies that collect and manage information on objects in space using ground-based radar or telescopes, which has the effect of enabling rational risk avoidance. In addition, establishing a contractual relationship with an insurance company will have the effect of increasing the sense of ownership and motivation to ensure flight safety.

[0072] In addition, the compatible space object ID provided by the space information recorder 101 is composed of all or part of a satellite ID that identifies an individual satellite and a satellite group ID that identifies a satellite group in which multiple satellites work together to perform a single function or performance. The orbital information of an individual satellite includes the orbital origin, orbital elements, and prediction error of the individual satellite. The orbit information of the satellite constellation includes upper and lower limit values ​​of the orbit altitude and upper and lower limit values ​​of the orbital inclination angle of the constituent satellites. For mega-constellation satellites, for which it is difficult to exchange real-time, high-precision orbital information, information on the area in which the satellites fly is shared. This information sharing has the effect of enabling other operators to issue intrusion warnings for the area in which the satellites fly, without having to perform collision analysis for each individual satellite. It is also possible to manage groups of space objects operated by multiple operators flying in dangerous areas such as near LST 10:30 in sun-synchronous orbits, or in the polar regions where many polar-orbiting satellites fly, which has the effect of enabling information sharing quickly and with minimal effort.

[0073] FIG. 14 is a diagram showing an example of a space information recorder 101 according to this embodiment.

[0074] The disclosure condition information possessed by the space information recorder 101 includes a business device ID and a business device group ID for identifying a business device group consisting of a plurality of business devices. The disclosure conditions are made up of all or part of the conditions for whether or not disclosure is permitted, the conditions for paying costs, and the information update conditions that indicate the frequency of information updates or the events that act as triggers.

[0075] The space information recorder 101 in Figure 14 can manage information disclosure conditions for individual businesses, as well as for a group of business devices. This allows for simultaneous operation for multiple SSA businesses, multiple space insurance businesses, or multiple debris removal businesses. This has the effect of enabling information sharing quickly and with minimal effort. It is also possible to manage multiple operators flying in dangerous areas such as near LST 10:30 on a sun-synchronous orbit or in the polar regions where many polar orbiting satellites fly, which has the effect of enabling information sharing quickly and with minimal effort.

[0076] FIG. 15 is a diagram showing an example of a danger warning device 102 according to this embodiment.

[0077] The danger warning device 102 comprises all or some of the following information: - Collision warning that is displayed when a collision between space object A and space object B is predicted. - Approach warning that is displayed when space object A and space object B are predicted to approach within a dangerous distance. - An intrusion alert is displayed when space object A is predicted to intrude into the flight area of ​​satellite group C. Space object ID of Space object A. Space object ID of Space object B. - The constellation ID of constellation C where intrusion is predicted.

[0078] The danger warning device 102 of FIG. 15 has the advantage that, when any one of multiple businesses foresees a danger, information can be shared among the related businesses quickly and with minimal effort. Furthermore, by only reporting the space object ID or the satellite group ID, the orbital information can be shared by the space object recorder, which has the advantage of enabling information to be shared quickly and with minimal effort.

[0079] FIG. 16 is a diagram showing an example 5-4 of a space traffic management system 500 according to this embodiment.

[0080] The risk analysis device 103 installed in each of the multiple business devices has a common algorithm. When the space object ID of space object A and the space object ID of space object B included in the risk warning device 102 are input, the risk analysis device 103 can reproduce the analysis results of the risk analysis device 103 owned by the business that issued the risk warning. When the danger analysis device 103 obtains the space object ID of space object A and the space object ID of space object B from the danger warning device 102 of another business device, it uses the space information recorder 101 to output the collision time and collision position coordinates using a common algorithm.

[0081] 16, information such as the time period and approach distance when dangerous approach or collision is predicted can be reproduced simply by exchanging space object IDs. This has the effect of enabling risk information to be grasped and shared quickly and with minimal effort.

[0082] FIG. 17 is a diagram showing an example 5-5 of a space traffic management system 500 according to this embodiment.

[0083] When an alarm is displayed that space object A is entering a dangerous area, and the dangerous area is an area where a megaconstellation or constellation satellite group C is flying, the danger analysis device 103 can perform the following processing. Under the above conditions, the space object ID of space object A and the satellite group ID of satellite group C included in the danger warning device 102 are input to the danger analysis device 103. Then, the megaconstellation business device or the constellation business device performs a danger analysis using the precise orbit information of the satellite group from the space information recorder 101 installed in the device. The megaconstellation business device or the constellation business device then predicts a collision between individual satellites and outputs the time of collision and the coordinates of the collision location.

[0084] This has the effect of enabling operators who do not have real-time, high-precision information from mega-constellation satellites to issue danger warnings to mega-constellation operators. Furthermore, mega-constellation operators will be able to use the real-time precise orbit information they manage to analyze whether there is a collision risk for individual satellites, and if a risk is predicted, to analyze the satellite ID, collision time, and location coordinates. As a result, it will be possible to decentralize the management of orbital information and realize a new mechanism for predicting danger.

[0085] The danger avoidance action support device 104 displays all or part of the following displays for the space object A, the space object B, or the satellite group C for which danger has been reported by the danger warning device 102. -Indication that the business equipment of space object A will take action to avoid danger. -Indication that the business equipment of space object B will take action to avoid danger. -Indication that the business equipment of satellite constellation C will take action to avoid danger. -Indication that debris removal equipment is taking hazard avoidance action. -Indicates that neither space object A nor space object B will take any action to avoid danger. -Indicates that neither space object A nor satellite group C will take any action to avoid danger. -Display of rocket launch equipment taking risk avoidance action. -Indication that the space object's business equipment is taking evasive action during orbital transfer. -Indication that the space object's equipment is taking evasive action during deorbit. -Display indicating that all parties have agreed. - A notice indicating that the parties involved have not yet reached an agreement and adjustments are required.

[0086] If a collision between space objects is predicted and multiple operators simultaneously take uncoordinated action to avoid the collision, another risk of collision will arise at the destination where the collision was avoided. Furthermore, in dangerous areas where satellites with avoidance capabilities coexist with satellites that do not even have propulsion systems, such as near the sun-synchronous orbit LST10:30, there are situations where collision avoidance actions cannot be taken even if multiple operators are in control. Therefore, it is effective to categorize the role of taking avoidance actions according to the status of the space object related to the danger alert and set options in advance. Furthermore, with mega-constellation satellites, situations may arise where danger warnings continue to be issued frequently, so there may be economic benefits to not taking evasive action in response to individual danger warnings. Setting these as options has the effect of enabling a course of action to avoid danger to be set quickly and with minimal effort. Furthermore, although it is necessary to reach a consensus among multiple businesses where a collision is predicted, it is possible to reach a consensus by making a quick decision using the danger avoidance action support device 104. Furthermore, if an agreement cannot be reached, it has the effect of enabling early start of adjustment work.

[0087] The security device 105 is comprised of all or part of an encryption device, a password system, and a biometric authentication system to prevent unauthorized users from changing information.

[0088] FIG. 18 is a diagram showing an example of a space information recorder 101 according to this embodiment.

[0089] The space information recorder 101 is configured to store, for each space object ID, all or part of a plurality of pieces of orbit information from different business devices that provide the information and a plurality of pieces of orbit information with different information update dates.

[0090] Each information provider has different prediction and measurement errors. For example, the orbital information used by satellite operators to track and control their own satellites has smaller prediction and measurement errors than the orbital information measured by SSA operators using ground-based radar or telescopes. According to the space information recorder 101 of this embodiment, when prediction errors or measurement errors are used as calculation criteria for space insurance premium rates and insurance claims assessment, it has the effect of being able to select more accurate information.

[0091] The space traffic control device 100 functions as a portal site. The business equipment and the space traffic management equipment installed on the business equipment have information processing functions, and can be realized even as virtual devices in the virtual space of the cloud. Therefore, it is also effective to set up a portal by renting the server display function of the SSA operator, which has the effect of making it easier to centrally manage public information.

[0092] ***Explanation of Operation*** FIG. 19 is a flow chart showing a space object intrusion warning process S100, which is an example of a space traffic control process of the space traffic control device 100 according to this embodiment. FIG. 20 is a diagram showing an example of a predicted orbit of debris passing through the satellite constellation 20 and an intrusion warning 111 according to this embodiment.

[0093] <Operation of Space Object Intrusion Alarm Processing S100> In step S101, the passage determination unit 110 determines whether or not debris will pass through a satellite orbital region 301, which is the orbit or region through which multiple satellites forming the satellite constellation 20 fly, based on the satellite orbit forecast information 52 and the debris orbit forecast information 53. Specifically, the satellite orbital region 301 is the orbit in which the satellite constellation 20 is formed. If it is determined that debris will pass through the satellite orbital region 301, the process proceeds to step S102. If it is not determined that debris will pass through the satellite orbital region, the process of step S101 is repeated.

[0094] In step S102, the warning generation unit 120 generates an intrusion warning 111 including the predicted time, predicted position coordinates, and predicted velocity vector information of the debris passing through. Figure 20 shows how debris passes through satellite orbital region 301, which includes satellite constellation A at an orbital altitude of A km and satellite constellation B at an orbital altitude of B km. Passage determination unit 110 determines whether the predicted orbit of the debris will pass through the satellite constellation, based on satellite orbit forecast information 52 and debris orbit forecast information 53. In Figure 20, the entrance and exit of satellite constellation A and the entrance and exit of satellite constellation B are the passing points of satellite constellation 20. The alarm generation unit 120 generates an intrusion alarm 111 including predicted time, coordinates, and velocity vector at the time of passing through each of these four passing points.

[0095] In step S103, the alarm notification unit 130 notifies the intrusion alarm 111 to the management business device 40 used by the management operator that manages the satellites flying in the satellite orbital region 301. Specifically, the alarm notification unit notifies the intrusion alarm to a satellite constellation business device used by the satellite constellation operator that operates the satellite constellation. The satellite constellation business device is an operator that conducts a satellite constellation business, such as a mega constellation business device 41, a LEO constellation business device 42, or a satellite business device 43.

[0096] FIG. 21 is a diagram showing an example of the risk of collision between the satellite constellation 20 and debris when there is no error. FIG. 22 is a diagram showing an example of the risk of collision between the satellite constellation 20 and debris according to this embodiment.

[0097] When issuing a debris intrusion alert for a megaconstellation of satellites, it is difficult for the alert issuing party to distinguish between an approach alert and a collision alert. Below, we will explain the concepts of collision risk and approach risk in megaconstellations. The risk of collision is limited to two points: the entrance and exit, which pass through specific altitudes. However, the satellites that could collide are the many satellites flying in nearby orbits. If the predicted trajectory of the debris does not include any error and there is no variation in the orbital altitudes at which the megaconstellation satellites fly, the points at which there is a risk of collision can be identified and limited to two points: the entrance and exit. However, in reality, there are errors in the predicted orbits of debris, and there are also variations or errors in the orbital altitudes of megaconstellation satellites. As a result, the collision risk is not a point, but rather a spatial spread as an area. Furthermore, the time error in the debris's flight direction is reduced to a spatial error relative to the flight direction. Furthermore, on the megaconstellation side, the flight distance expands depending on the time error, and the number of satellites at risk of collision increases.

[0098] A proximity warning may be issued when the relative distance approaches 100 km or less. The area equivalent to the prediction error plus an expansion of 100 km becomes the "area at risk of approach," and the number of target satellites on the megaconstellation side will increase even further. Low-earth orbit satellites generally fly at speeds of around 7 to 10 km / sec, so a time error of 10 seconds would result in an area expansion equivalent to 100 km.

[0099] Furthermore, position coordinates can be uniquely identified by using a coordinate system such as the Earth-fixed coordinate system WGS84. However, the orbital plane of a mega-constellation satellite moves relative to the Earth from moment to moment. Therefore, strictly speaking, only the mega-constellation operator can know the position of the orbital plane at a specific time. Furthermore, only the mega-constellation operator can accurately know where the satellite is flying in that orbital plane. Therefore, if an SSA operator takes over the warning service of the US CSpOC, it will be sufficient for the SSA operator to issue an "warning" to the mega-constellation operator, including the predicted time of passage at the relevant orbital altitude, predicted position coordinates, and predicted velocity vector. In this embodiment, this "warning" is called an intrusion warning 111. It is then the role of the satellite constellation operator, such as the mega-constellation operator, to take evasive action upon receiving the intrusion warning 111.

[0100] <Collision Avoidance Using Satellite Constellation Formation Systems> The satellite constellation forming system 600 described in FIGS. 5 to 8 controls the satellite constellation 20 to avoid debris invading the satellite constellation 20 based on the intrusion warning 111 from the space traffic control device 100. 5 to 8, the satellite constellation forming system 600 may be mounted on a ground facility 700. In this case, the ground facility 700 controls avoidance actions to avoid collisions between debris entering the satellite orbital region 301 and the satellites that make up the satellite constellation 20, based on an intrusion alarm 111 from the space traffic control device 100.

[0101] The satellite constellation operator can avoid collisions without significantly disrupting the relative positions of all the satellites by simultaneously accelerating or decelerating the speed of at least all the satellites using the satellite constellation forming system 600. Therefore, the satellite constellation forming system 600 can avoid debris collisions using the intrusion alarm 111 according to this embodiment.

[0102] ***Explanation of the effect of this embodiment*** When the space traffic control device 100 according to this embodiment determines that debris is about to enter a satellite constellation, it can issue an intrusion warning including predicted time, predicted position coordinates, and predicted velocity vector information. Thus, the space traffic control device 100 according to this embodiment can determine whether debris will enter the orbital region of the satellite constellation and issue an appropriate intrusion warning. Furthermore, the satellite constellation forming system or ground facility that receives the intrusion warning according to this embodiment can take appropriate evasive action.

[0103] ***Other Configurations*** In this embodiment, the functions of the space traffic control device 100 are realized by software. As a modification, the functions of the space traffic control device 100 may be realized by hardware.

[0104] FIG. 23 is a diagram showing the configuration of a space traffic control device 100 according to a modified example of this embodiment. The space traffic control device 100 includes an electronic circuit 909 instead of a processor 910 . The electronic circuit 909 is a dedicated electronic circuit that realizes the functions of the space traffic control 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 space traffic control device 100 may be realized by a single electronic circuit, or may be distributed across multiple electronic circuits. As another variation, some of the functions of the space traffic control device 100 may be implemented by electronic circuits, and the remaining functions may be implemented by software.

[0105] Each of the processor and electronic circuitry is also referred to as processing circuitry, i.e., the functions of the space traffic control device 100 are realized by the processing circuitry.

[0106] Embodiment 2 In this embodiment, differences from or additions to embodiment 1 will be mainly described. In this embodiment, the same components as those in embodiment 1 will be assigned the same reference numerals, and the description thereof may be omitted.

[0107] There are dense areas where many Earth observation satellites fly in sun-synchronous orbits around LST 10:30, 13:00, 06:00, and 18:00. In the polar regions, the intersections of all the orbital planes of the sun-synchronous orbit satellites mentioned above are concentrated, and there are dense areas where all the satellites pass through.

[0108] Meanwhile, the following plans have been announced by mega-constellation operators: The plan is for approximately 7,500 satellites to fly in an inclined orbit at an altitude of around 340 km. The plan is for approximately 2,500 satellites to fly as an inclined orbit constellation at an altitude of approximately 550 km. The plan is for approximately 3,200 satellites to fly as an inclined orbit constellation at an altitude of approximately 610 km. -Several plans call for constellations of hundreds to over 1,000 satellites to fly at orbits above 1,000 km. These plans involve densely packed satellites flying across the entire sky at specific altitudes.

[0109] The area where these dense regions intersect is a dangerous area where the risk of a space object collision is extremely high. Moreover, once a space object collision occurs, the risk of a chain reaction of collisions is also extremely high, and this is the area where the risk of falling into the Kessler syndrome is highest. In formulating international rules for space traffic management (STM), determining traffic rules for areas where densely populated areas intersect is one of the most urgent and important issues. However, due to the wide range of stakeholders involved, it is difficult to consolidate discussions at forums such as international conferences.

[0110] Therefore, the present embodiment aims to prevent catastrophic space object collision accidents, alert stakeholders, and establish de facto rules for rapid and effective collision avoidance. Furthermore, the present invention proposes a space traffic management device as an information sharing tool for related businesses. It presents traffic rules for areas where multiple densely populated areas intersect, a means for raising awareness of dangerous areas, and a means for promoting the establishment of de facto rules for collision avoidance. The effect of this is to avoid collisions between space objects and prevent the Kessler syndrome.

[0111] ***Configuration Description*** In this embodiment, the configurations of satellite constellation forming system 600, space traffic management system 500, and space traffic control device 100 are the same as those described in FIG. 5 to FIG. 9 in the first embodiment.

[0112] FIG. 24 is a diagram showing Example 1-3 of the space traffic control device 100 according to this embodiment. FIG. 25 is a diagram showing an example 5-5 of a space traffic management system 500 according to this embodiment. In FIG. 25, the detailed configuration of the space traffic control device 100 is omitted.

[0113] Each of the plurality of space traffic control devices 100 includes space traffic control rule information 106 , a danger warning device 102 , and danger avoidance action plan information 107 . The space traffic control rules information 106 includes international rules 61 that are internationally recognized in accordance with space law, and trial phase rules 62 that have not yet been internationally recognized. The trial stage rules 62 include all or some of the following: congested area identification information 621 for identifying congested areas; danger area identification information 622 for identifying danger areas where congested areas intersect; and traffic management rule information 623 for the danger areas.

[0114] In this embodiment, space traffic management rule information is shared based on the effect of information sharing between space object management companies described in embodiment 1. This information sharing ensures flight safety in peacetime design and operation. In addition, by establishing rules for reporting when danger is foreseen and sharing information on risk avoidance action plans, danger can be avoided and space traffic safety can be achieved.

[0115] <About the dense area identification information 621> FIG. 26 is a diagram showing an example of the dense area identification information 621 according to this embodiment.

[0116] The dense area identification information 621 includes the following areas: - Sun-synchronous orbit near LST10:30, orbital altitude between 500km and 1000km. - Sun-synchronous orbit near LST13:30, orbital altitude between 500km and 1000km. Sun-synchronous orbit near LST06:00, orbital altitude between 500km and 1000km. Sun-synchronous orbit near LST18:00, orbital altitude between 500km and 1000km. -Areas above 80 degrees north latitude and with an orbital altitude of between 500km and 1000km. -Areas above 80 degrees south latitude and with an orbital altitude of between 500km and 1000km. - Each orbital altitude region in which mega-constellation satellites fly, with the same nominal orbital altitude, and satellites flying at an orbital altitude of 100km or more but less than 2000km, and with a constellation of 500 or more satellites that provides unique services.

[0117] <Regarding the danger area identification information 622> 27, 28, 29, and 30 are diagrams showing examples of the danger area identification information 622 according to this embodiment.

[0118] The risk area identification information 622 is an area where dense areas intersect. The risk area identification information 622 includes an area where any of the following areas intersects with each orbital altitude area where megaconstellation satellites fly, with satellites that fly at orbital altitudes between 500 km and 1000 km and that provide unique services with a group of 1000 or more satellites, and have the same nominal orbital altitude. - Sun-synchronous orbit near LST10:30, orbital altitude between 500km and 1000km. - Sun-synchronous orbit near LST13:30, orbital altitude between 500km and 1000km. Sun-synchronous orbit near LST06:00, orbital altitude between 500km and 1000km. Sun-synchronous orbit near LST18:00, orbital altitude between 500km and 1000km.

[0119] <About Example 1 of Traffic Management Rule Information 623> Example 1 of the traffic management rule information 623 in dangerous areas includes the following rules: A rule that requires all mega-constellation satellites that realize specific services to maintain their orbital altitudes at a nominal orbital altitude of Ha±ΔHa km during normal operation. - A rule that prohibits sun-synchronous orbit satellites from entering the above nominal orbital altitude Ha±ΔHakm during normal operation. In addition, ΔHa is 2 or more and 10 or less.

[0120] The nominal orbital altitude Hakm at which mega-constellation satellites fly is an area of ​​approximately 0±40 degrees, with the central latitude above the equator, that is, an area where the satellites fly in all directions from roughly 40 degrees north latitude to 40 degrees south latitude. The risk of collision is high for sun-synchronous satellites to enter this area, which is dangerous. Therefore, taking into account fluctuations from the nominal orbital altitude Hakm and the distribution of the satellites, ±ΔHakm is designated as an area where the mega-constellation is responsible for maintaining its orbital altitude, and sun-synchronous satellites are prohibited from entering. This rule eliminates areas where densely packed areas intersect, allowing for safe flight.

[0121] The currently known megaconstellation construction plans alone will involve hundreds of satellites at each of the following orbital altitudes: ·Nominal orbit altitude 335.9km 2493 aircraft. ·Nominal orbit altitude 340.8km 2478 aircraft. ·Nominal orbit altitude 345.6km 2547 aircraft. ·Nominal orbit altitude 591km 784 aircraft. ·Nominal orbit altitude 610km 1296 aircraft. ·Nominal orbit altitude 629km 1156 aircraft.

[0122] If ΔHa is 10 km, the two regions from 345.9 to 355.6 km and from 581 to 639 km will be occupied by mega-constellation satellites. This has the disadvantage that a wide range of areas that have been frequently used by Earth observation satellites and are in high demand will become no-go areas. On the other hand, if ΔHa is 2 km, it is considered technically feasible to achieve orbital altitude control of ±2 km for mega-constellation satellites if orbital control is performed with high precision and frequency. As a flight safety measure for mega-constellation satellites, there is a passive safety measure that reduces the basic collision probability to zero by dispersing the orbital altitudes, even in the unlikely event of an artificial loss of control due to a collision with foreign debris. However, it is difficult to achieve a method of dispersing orbital altitudes within a ΔHa range of ±2 km. For this reason, the adoption of a time-division method is considered to be a necessary condition for flight safety measures to prevent collisions within the mega-constellation's own system, which has the disadvantage of exposing the risk of collisions in the event of an artificial loss of control. Although there are such restrictions, example 1 of the traffic management rule information 623 has the effect of being able to avoid collisions between mega-constellation satellites and sun-synchronous satellites in a normal operation state.

[0123] <About Example 2 of Traffic Management Rule Information 623> Example 2 of the traffic management rule information 623 in dangerous areas includes the following rules: A rule that requires that the orbital altitude of all mega-constellation satellites that realize specific services during normal operation must be maintained within ±2 km of the nominal orbital altitude Ha when the nominal orbital altitude Ha is between 500 km and 1,000 km. - A rule that prohibits sun-synchronous orbit satellites from entering the nominal orbital altitude range of Ha ±2km during normal operation.

[0124] The orbital altitude range between 500km and 1000km is the altitude range where most sun-synchronous satellites fly. Meanwhile, among the currently known mega-constellation construction plans, the plans with nominal orbital altitudes between 500km and 1000km are as follows: ·Nominal orbit altitude 550km 1600 aircraft. ·Nominal orbit altitude 591km 784 aircraft. ·Nominal orbit altitude 610km 1296 aircraft. ·Nominal orbit altitude 629km 1156 aircraft.

[0125] When the rule according to Example 1 of the traffic management rule information 623 above is applied, the orbital altitude occupied by the megaconstellation is as follows: 548~552km (550±2 km). 589~593km (591±2 km). 608~612km (610±2 km). 627~631km (629±2 km).

[0126] If orbital control is carried out with high precision and frequency, it is believed that orbital altitude control of ±2 km is technically feasible. As a result, the orbital altitudes at which sun-synchronous satellites can be used at orbital altitudes above 500 km and below 1000 km, which are frequently used by sun-synchronous satellites, are as follows: 500 to 548 km (524 ± 24 km). 552~589km (571±19 km). 593~608km (600.5±7.5 km). 612~627km (619.5±7.5 km). ·631~1000km (815.5±184.5 km).

[0127] According to example 2 of the traffic management rule information 623, it is possible to avoid collisions between mega-constellation satellites and sun-synchronous satellites in a normal operation state.

[0128] <About Example 3 of Traffic Management Rule Information 623> Example 3 of traffic management rule information in dangerous areas includes the following rules: -Rules stipulating that operators of space objects that are expected to pass through an area with a nominal orbital altitude of Ha±ΔHa km must publish information on danger zone intrusion warnings on danger warning devices. - Rules stipulating that business entities that manage satellites at the above-mentioned nominal orbital altitude Ha must publish collision avoidance action plan information.

[0129] Even just the currently known megaconstellation construction plans will place hundreds of satellites at each of the following orbital altitudes: Therefore, rockets launched to orbits above 340 km, or satellites in the process of deorbiting from orbits above 340 km, will necessarily pass through the orbital altitudes at which megaconstellation satellites fly. ·Nominal orbit altitude 335.9 km 2493 aircraft. ·Nominal orbit altitude 340.8 km 2478 aircraft. ·Nominal orbit altitude 345.6 km 2547 aircraft. ·Nominal orbit altitude 550 km 1600 aircraft. ·Nominal orbit altitude 591km 784 aircraft. ·Nominal orbit altitude 610km 1296 aircraft. ·Nominal orbit altitude 629km 1156 aircraft. ·Nominal orbit altitude 1030~1080 2956 aircraft. ·Nominal orbit altitude 1150 km 2808 aircraft. ·Nominal orbit altitude approximately 1200 km, approximately 600 aircraft.

[0130] Similarly, geostationary orbit satellites that transfer from the perigee to the apogee of a geotransfer orbit, or quasi-zenith orbit satellites that have a similar orbital injection process, may also pass through the orbital altitude at which megaconstellation satellites fly during the orbital transfer process. According to Example 3 of the traffic management rule information 623, a rule that requires danger warning devices to publish information about danger zone intrusion warnings and mega-constellation operators to publish information about collision avoidance action plans is applied. This has the effect of ensuring information sharing and ensuring flight safety.

[0131] Embodiment 3 In this embodiment, the following mainly describes the differences from or additions to embodiments 1 and 2. In this embodiment, the same components as those in embodiments 1 and 2 are denoted by the same reference numerals, and the description thereof may be omitted.

[0132] In international discussions on STM, the need for information sharing, as well as ensuring transparency and third-party verification, is beginning to be emphasized. The incident began with India's ASAT (anti-satellite weapon) test on March 27, 2019 (the destruction of a satellite using an anti-satellite missile in outer space). Regarding debris resulting from the ASAT test, India claimed that it was an explosive test conducted in low orbit, and that it would re-enter the atmosphere in 45 days. However, even now, six months later, debris can still be seen flying, indicating the need for third-party monitoring. In the space traffic management system according to this embodiment, flight safety-related information is shared among multiple business devices, and a space traffic management device with standardized algorithms that contribute to risk analysis and error information scrutiny is defined. Based on this, a space traffic management system is formed in which the space traffic management devices that are compatible as standard equipment of multiple business devices are connected via communication lines. As a result, the sharing of orbital information on space objects, as well as information on danger warnings and danger avoidance action plans, will be quicker and more labor-saving. Furthermore, by creating an environment in which third parties can compare and evaluate information from multiple sources, it will be possible to ensure transparency and ensure reliable flight safety management.

[0133] ***Configuration Description*** In this embodiment, the configurations of satellite constellation forming system 600, space traffic management system 500, and space traffic control device 100 are the same as those described in FIG. 5 to FIG. 9 in the first embodiment.

[0134] FIG. 31 is a diagram showing Example 1-4 of the space traffic control device 100 according to this embodiment.

[0135] The space traffic management device includes all or some of the following: space traffic management rule information 106, space information recorder 101, danger warning device 102, danger analysis device 103, danger avoidance action support device 104, danger avoidance action implementation plan information 107, measurement error inspection device 108, and security device 105.

[0136] The space information recorder 101 records orbital information of space objects. The space information recorder 101 also includes all or part of orbital object number management information 121 and flight safety measure information 112.

[0137] The danger warning device 102 warns of the danger of approaching or colliding with a space object. The risk analysis device 103 performs trajectory analysis of space objects. The danger avoidance behavior support device 104 displays the role allocation of the avoidance behavior of the space object. The security device 105 prevents information from being tampered with.

[0138] In order to mitigate the risk of space object collisions due to the rapid increase in the number of space objects and ensure flight safety, it is necessary to take measures to ensure flight safety in peacetime, to predict danger early, to share information quickly, and to take rational countermeasures. The space traffic management rule information 106, the space information recorder 101, the danger warning device 102, the danger analysis device 103, the danger avoidance action support device 104, the danger avoidance action implementation plan information 107, and the security device 105 are effective information and tools for ensuring flight safety. By having these contents in common by the business devices that manage space objects, and by having the space information recorder 101 also have the orbital object number management information 121, the number of space objects can be managed appropriately. Furthermore, by providing flight safety countermeasure information 112, flight safety can be ensured even in normal times. Furthermore, the measurement error inspecting device 108 inspects the measurement errors of the orbit information acquired by a plurality of measuring means, which has the effect of enabling safety management using more accurate orbit information.

[0139] Orbital information managed by satellite operators, rocket operators, and debris removal companies to track and control space objects and ensure flight safety is essential for each operator and is essential information for space information recorders. In addition, there are danger warning devices that warn of danger when other space objects or debris approach, and if the time period and location information of the collision risk can be predicted, it is expected that collisions can be avoided by taking risk avoidance actions. Security devices are also necessary to prevent intentional tampering by third parties. Therefore, it is reasonable to equip business equipment with the configuration of Example 1-4 of the space traffic management device 100 in Figure 31.

[0140] FIG. 32 is a diagram showing an example 5-7 of a space traffic management system 500 according to this embodiment. In FIG. 32, the detailed configuration of Example 1-4 of the space traffic control device 100 in FIG. 31 is omitted.

[0141] The space traffic management system 500 includes a plurality of space traffic control devices 100 installed in the business devices of a plurality of management businesses. The plurality of space traffic management devices 100 are connected to each other via communication lines. The plurality of space information recorders 101 are provided with a space object ID for identifying a space object, orbit information, and disclosure condition information, as well as a business device ID for identifying a business device and disclosure condition information. The multiple space traffic control devices 100 have mutual data format compatibility. The multiple space traffic control devices 100 share a space object ID and a business device ID. Furthermore, the multiple space traffic control devices 100 share space information corresponding to the space object ID among business devices that comply with the disclosure condition information, and the risk analysis device 103 and the measurement error inspection device 108 have a common algorithm among different business devices.

[0142] The plurality of space traffic control devices 100 have compatibility in satellite ID and orbit information, and the risk analysis devices 103 have a common algorithm among different business devices. For example, a business device that predicts a collision between space objects A and B using the risk analysis device 103 transmits the IDs of space objects A and B using the risk warning device 102. This has the effect of allowing another business device to obtain orbital information using the space information recorder 101 and reproduce the collision prediction using the risk analysis device 103 that has a common algorithm.

[0143] Furthermore, the plurality of space traffic control devices 100 have compatibility in satellite ID and orbit information, and the measurement error inspection devices 108 are provided with a common algorithm among different business devices. This allows the orbit information of the same space object C measured by two different space situation monitoring operators, SSA operator A and SSA operator B, to be updated by combining components with small measurement errors. Furthermore, there is an advantage that orbit information can be acquired by a space information recorder in another business device, and the updated content of the measurement information can be reproduced by a measurement error inspection device 108 having a common algorithm. As a result, it becomes possible for a third party to verify the information, which has the effect of ensuring the transparency of the information.

[0144] FIG. 33 is a diagram showing an example 5-8 of a space traffic management system 500 according to this embodiment. 34, 35, 36, and 37 are diagrams showing the detailed configuration of each business device in Example 5-8 of the space traffic management system 500 in FIG.

[0145] The space information recorder 101 obtains orbital object number management information obtained from the business device that manages the space object in question, and orbital object number management information obtained by a different measurement means from another business device, and can compare and evaluate the disclosed information of the business device that manages the space object in question to perform third-party verification.

[0146] Space Information Recorder 101 is As for orbital information relating to a specific space object ID, orbital information obtained from the business device that manages the space object and orbital information obtained by a different means can be obtained from another business device, and then compared and evaluated with the disclosed information of the business device that manages the space object for third-party verification.

[0147] The space information recorder 101 can obtain measurement errors contained in orbital information, including measurement errors obtained from the business device that manages the space object and measurement errors obtained by different means from another business device, and compare and evaluate them with the disclosed information of the business device that manages the space object for third-party verification.

[0148] In space collision insurance, which covers damages caused by collisions with space objects with insurance premiums, the business entity that manages the space insurance business obtains orbital information of the insured space object from the business entity that manages the space object in question, as well as from the business entity of the SSA operator, and compares and evaluates it. This allows the space insurance business, as a third party, to verify the validity of the disclosed information of the business entity that manages the space object in question. It is also possible to obtain and evaluate orbital information for the same space object from multiple space situation monitoring business devices. In space collision insurance, when premiums are assessed based on the difference between predicted orbit information and actual orbit information, third-party verification becomes possible by comparing and evaluating orbit information obtained from the business equipment of the colliding space object with orbit information obtained by other means, thereby ensuring the reliability and fairness of the information.

[0149] FIG. 38 is a diagram showing the effect of Example 5-8 of the space traffic management system 500 according to this embodiment.

[0150] In the case of an insurance system in which the smaller the measurement error, the higher the insurance payout, it is possible to adopt the more accurate component of orbital information obtained from multiple SSA providers. For example, information measured by ground-based radar equipment has excellent ranging performance, so it has high measurement accuracy for orbital altitude (elliptical bubble 801). Also, information measured by ground-based optical telescopes has excellent angle measurement performance, so it has high measurement accuracy for orbital position (elliptical bubble 802). Because of these characteristics, it is reasonable to obtain orbital altitude from SSA equipment using radar measurement, and position information from an SSA provider using optical telescope measurement, and then merge the orbital information (elliptical bubble 803). However, ensuring transparency and objectivity is essential when updating information obtained from different sources. Therefore, by equipping not only business equipment for space objects that take out space insurance but also insurance business equipment with a measurement error inspection device equipped with a common data processing algorithm, a system will be created that allows third-party verification of the validity of updated orbital information. The effect of this is that it becomes possible to update information and improve its accuracy while ensuring transparency and objectivity.

[0151] Embodiment 4 In this embodiment, the differences from or additions to embodiments 1 to 3 will be mainly described. In this embodiment, the same components as those in embodiments 1 to 3 will be assigned the same reference numerals, and the description thereof may be omitted.

[0152] ***Configuration Description*** In this embodiment, the configurations of satellite constellation forming system 600, space traffic management system 500, and space traffic control device 100 are the same as those described in FIG. 5 to FIG. 9 in the first embodiment.

[0153] In this embodiment, an example of a process will be described in which a space traffic management device 100 installed in a debris removal operator issues an intrusion alarm 111 to warn of the intrusion of debris into a dense orbit. The space traffic management device 100 may have the following functions of a debris removal control device 190.

[0154] In this embodiment, the satellite orbital region 301 includes an orbit in a sun-synchronous orbit LST (Local Sun Time) of approximately 10:30 and at an altitude of approximately 500 km to 800 km. The alarm notification unit 130 issues an intrusion alarm 111 to warn the debris removal business device 45, which is used by a debris removal business operator that removes debris, that debris is entering an orbit in a sun-synchronous orbit LST of approximately 10:30 and at an altitude of approximately 500 km to 800 km.

[0155] FIG. 39 is a diagram showing an example of the orbit of debris entering the satellite orbital region 301 according to this embodiment. Currently, satellites from multiple countries and numerous operators fly in sun-synchronous orbits at altitudes of around 500km to 800km near LST 10:30, which are commonly used by Earth observation optical satellites. In the future, it is expected that orbits will become congested, with satellites from multiple stakeholders operating in a chain-like fashion. If debris enters the plane of this congested orbit, many satellites will be subject to proximity or collision warnings. Furthermore, in this orbit, satellites that do not have the means to take evasive action on their own, such as small satellites called CubeSats, cannot take evasive action even if a collision warning is issued. If a dense orbit contains a mixture of satellites that take evasive action and those that do not, there is a risk of a secondary collision, where one satellite may collide with another satellite even though it was thought to have avoided a collision, so taking evasive action in a dense orbit is not necessarily rational. Furthermore, if there is an error in the predicted time of debris arrival, and the direction of the satellite's flight is close to the direction of the debris' flight, the distance will be large, exposing many satellites to the risk of collision. A low-earth orbit satellite makes one orbit approximately every 90 to 100 minutes, so if there is an uncertainty of about ±50 minutes regarding the arrival of debris, there is a risk of collision with all satellites in that orbital plane. Another problem is that if a collision occurs on a dense orbit, the chances of a chain reaction of collisions are very high. Therefore, if a predicted trajectory of debris entering a dense orbit is discovered, it is reasonable to issue an alert to debris removal companies as soon as possible and remove the debris.

[0156] FIG. 40 is a diagram showing an example of the configuration of a debris removal control device 190 according to this embodiment. FIG. 41 is a diagram showing an example of the configuration of a debris removal satellite 30a according to this embodiment. The debris removal satellite 30a is equipped with a capture device 36 that captures debris in addition to the configuration of the satellite 30 described in Figures 5 to 8. The debris removal satellite 30a captures debris in response to control commands 56 from the debris removal control device 190, and performs active orbit control operation during orbit descent to avoid areas with a high risk of collision with space objects during the de-orbit process leading up to atmospheric re-entry. Active orbit control operation during orbit descent is also called active de-orbit operation. The debris removal control device 190 may be mounted on the ground facility 702. The debris removal control device 190 may also be mounted on the debris removal business device 45, or on another device that communicates with the debris removal business device 45.

[0157] The control unit 191 of the debris removal control device 190 generates control commands 56 to be sent to the debris removal satellite 30a. The control commands 56 include a capture command 57 and an orbit control command 55. The control unit 191 generates a capture command 57 to capture the debris using the capture device 36. The control unit 191 also generates an orbit control command 55 to perform active de-orbit operation on the debris removal satellite 30a that has captured the debris. The debris removal satellite 30a captures debris and performs active de-orbit operations based on control commands 56.

[0158] The satellite orbital region 301 may also include high-latitude regions, including polar regions. The warning notification unit 130 issues an intrusion warning 111 to a debris removal business device 45 used by a debris removal business operator that removes debris, to warn that debris is entering high-latitude regions, including polar regions.

[0159] FIG. 42 is a diagram showing an example of the orbit of debris that enters the satellite orbital region 301 according to this embodiment. In a polar-orbiting satellite constellation, all orbital planes pass through the polar regions, making the polar regions denser. If the predicted time of debris arrival is ±50 minutes, there is a possibility that all satellites in all orbital planes will be at risk of collision. Furthermore, even if evasive action is desired, the only evasive action that a normal satellite can contribute is to change the orbital altitude, which may not be an effective means of risk aversion, and situations may arise where taking evasive action is practically impossible. Therefore, if a predicted trajectory of debris entering the airspace above high latitude regions, including the polar regions, is discovered, it is reasonable to issue an alert to debris removal companies as soon as possible and remove the debris.

[0160] In the first embodiment, an example of an intrusion alert to a satellite constellation operator, such as a mega-constellation operator, was described. An intrusion alert to a satellite constellation operator is similar to, for example, an intrusion alert being sent to the management organization of a huge apartment building when a suspicious person is discovered. In the second embodiment, an example of an intrusion alert to a debris removal operator was described. An intrusion alert to a debris removal operator is similar to an intrusion alert being sent to a security service organization.

[0161] The space traffic management system may include a space information recorder that records space object information obtained from a management business device used by a management company that manages multiple space objects, and a server. The space traffic management system may also include a database that stores the space object information obtained from the space information recorder. The server sends an intrusion alert to the management business device to help avoid collisions with space objects.

[0162] Specifically, the server is a space traffic management system. The database may be provided on the server or may be a separate device from the server. The server realizes the following steps (also called means or units) using processing circuitry such as a processor or electronic circuit.

[0163] 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. A space traffic management system may be equipped with the space information recorder. The space information recorder may also include orbital forecast information.

[0164] The server comprises the following stages: A stage of defining and registering dense areas where many space objects fly. A step of identifying a space object A that is predicted to intrude into one of the densely populated areas from the space object information recorded in the space information recorder, and a step of transmitting an intrusion alarm to the management business device of the space object A. A step of transmitting an intrusion alert to a management business device that manages space objects flying in a dense area.

[0165] The space object information includes the forecast epoch, forecast orbital elements, and forecast error of the space object.

[0166] The dense area is generally in the range of orbital altitudes from 300 km to 1000 km, where a constellation of satellites in sun-synchronous orbits from 10:00 to 11:00 LST exists. The densely populated area is generally above 80 degrees north latitude or above 80 degrees south latitude, where polar orbiting satellites fly, and is in the range of orbital altitudes from 300 km to 1000 km.

[0167] The dense area includes the altitude range and latitude range of the constellation satellites that fly at the same nominal altitude and work together to accomplish the same mission, obtained from the management business device of the satellites that make up the megaconstellation.

[0168] The server includes a step of analyzing the predicted time period and predicted orbit information from when the space object A enters the dense area until when it leaves.

[0169] The server also includes a step of transmitting the predicted time period and predicted trajectory information from when space object A enters the densely populated area until it leaves to the management business device for space object A and the management business device for space objects flying in the densely populated area.

[0170] The server also has a step of transmitting an intrusion alert predicting that space object A will enter the densely populated area, as well as the predicted time period from when space object A enters the densely populated area until when it leaves, and predicted orbit information to a management business device of a debris removal operator that manages the debris removal satellite.

[0171] The server also includes a step of transmitting an intrusion alert predicting that space object A will intrude into the densely populated area, as well as the predicted time period from when space object A enters the densely populated area until when it leaves and predicted orbit information to a management business device of a space insurance company that operates the space insurance.

[0172] The management business device of the megaconstellation operator is equipped with means for performing collision analysis using space object information of the satellites of the megaconstellation and space object information of space object A. The server includes a step of transmitting an intrusion alert to a management business device of a mega-constellation operator in a collision avoidance method in which satellites of the mega-constellation avoid collisions when a collision is predicted by the collision analysis.

[0173] The management business device of the debris removal company, which is equipped with debris removal means, performs a collision avoidance method to avoid intrusion by capturing space object A at the predicted orbital position using the debris removal means before the predicted intrusion time based on the space object information of space object A. In the collision avoidance method, the server sends an intrusion alert to the management business device of the debris removal company.

[0174] The space insurance company operates an insurance payment system that covers damages caused by collisions with space objects by paying insurance claims using insurance premiums collected and saved in advance. The insurance payment system is a system that starts a contract after a collision with a space object is predicted. In the insurance payment system, a server sends an intrusion alarm to the space insurance company's management business device.

[0175] Space object A is a newly launched rocket. Alternatively, space object A is a geostationary satellite or quasi-zenith satellite in the middle of orbital transfer. Alternatively, space object A is a space object in the middle of orbital descent in the de-orbit process.

[0176] Embodiment 5. In this embodiment, an example of a device and a system configured by combining the embodiments 1 to 4 will be mainly described. In this embodiment, the same components as those in the embodiments 1 to 4 are denoted by the same reference numerals, and the description thereof may be omitted.

[0177] The satellite business device 43 includes the space traffic control device 100 of the first embodiment, and is provided in the space traffic management system 500 described in the first embodiment.

[0178] The satellite constellation business device includes the space traffic control device 100 of the first embodiment, and is provided in the space traffic management system 500 described in the first embodiment.

[0179] The megaconstellation business device 41 includes the space traffic control device 100 of the first embodiment, and is provided in the space traffic management system 500 described in the first embodiment.

[0180] The rocket launch business equipment 46 includes the space traffic control device 100 of the first embodiment, and is provided in the space traffic management system 500 described in the first embodiment.

[0181] The debris removal business device 45 includes the space traffic control device 100 of the first embodiment, and is provided in the space traffic management system 500 described in the first embodiment.

[0182] The space situation monitoring business device (SSA business device 47) includes the space traffic control device 100 of the first embodiment, and is provided in the space traffic management system 500 described in the first embodiment.

[0183] The danger avoidance support business device includes the space traffic control device 100 of the first embodiment, and is provided in the space traffic management system 500 described in the first embodiment. The danger avoidance support business device is a management business device 40 that manages support information for preventing collision accidents involving space objects.

[0184] The space insurance business device includes the space traffic control device 100 of the first embodiment, and is provided in the space traffic management system 500 described in the first embodiment. The space insurance business device is a management business device 40 that manages space insurance.

[0185] The satellite business device 43 includes the space traffic control device 100 of the second embodiment, and is provided in the space traffic management system 500 described in the second embodiment.

[0186] The satellite constellation business device includes the space traffic control device 100 of the second embodiment, and is provided in the space traffic management system 500 described in the second embodiment.

[0187] The megaconstellation business device 41 includes the space traffic control device 100 of the second embodiment, and is provided in the space traffic management system 500 described in the second embodiment.

[0188] The rocket launch business equipment 46 includes the space traffic control device 100 of the second embodiment, and is provided in the space traffic management system 500 described in the second embodiment.

[0189] The debris removal business device 45 includes the space traffic control device 100 of the second embodiment, and is provided in the space traffic management system 500 described in the second embodiment.

[0190] The space situation monitoring business device (SSA business device 47) includes the space traffic control device 100 of the second embodiment, and is provided in the space traffic management system 500 described in the second embodiment.

[0191] The danger avoidance support business device includes the space traffic control device 100 of the second embodiment, and is provided in the space traffic management system 500 described in the second embodiment. The danger avoidance support business device is a management business device 40 that manages support information for preventing collision accidents involving space objects.

[0192] The space insurance business device includes the space traffic control device 100 of the second embodiment, and is provided in the space traffic management system 500 described in the second embodiment. The space insurance business device is a management business device 40 that manages space insurance.

[0193] The rocket launch business equipment 46 includes the space traffic control device 100 of the third embodiment, and is provided in the space traffic management system 500 described in the third embodiment.

[0194] The debris removal business device 45 includes the space traffic control device 100 of the third embodiment, and is provided in the space traffic management system 500 described in the third embodiment.

[0195] The space situation monitoring business device (SSA business device 47) includes the space traffic control device 100 of the third embodiment, and is provided in the space traffic management system 500 described in the third embodiment.

[0196] The danger avoidance support business device includes the space traffic control device 100 of the third embodiment, and is provided in the space traffic management system 500 described in the third embodiment. The danger avoidance support business device is a management business device 40 that manages support information for preventing collision accidents involving space objects.

[0197] The space insurance business device includes the space traffic management device 100 of the third embodiment, and is provided in the space traffic management system 500 described in the third embodiment. The space insurance business device is a management business device 40 that manages space insurance.

[0198] The space information recorder 101 is provided in the space traffic management device 100 described in embodiment 1, 2, or 3, and is also provided in the space traffic management system 500 described in embodiment 1, 2, or 3. The space information recorder 101 has a space object ID, orbit information, and disclosure condition information that identify a space object, as well as a business device ID and disclosure condition information that identify a business device.

[0199] The danger warning device 102 is provided in the space traffic control device 100 described in embodiment 1, 2, or 3, and is also provided in the space traffic management system 500 described in embodiment 1, 2, or 3. The danger warning device 102 is provided with all or some of the following information: a collision warning to be displayed when a collision between space object A and space object B is predicted, an approach warning to be displayed when space object A and space object B are predicted to approach within a dangerous distance, an intrusion warning to be displayed when space object A is predicted to intrude into the flight area of ​​satellite group C, the space object ID of space object A, the space object ID of space object B, and the satellite group ID of satellite group C whose intrusion is predicted.

[0200] The risk analysis device 103 is provided in the space traffic management device 100 described in embodiment 1, 2, or 3, and is also provided in the space traffic management system 500 described in embodiment 1, 2, or 3. The risk analysis device 103 has an algorithm common to multiple business devices, and when the space object ID of space object A and the space object ID of space object B contained in the risk warning device 102 are input, the analysis results of the risk analysis device owned by the business that issued the risk warning can be reproduced.

[0201] The risk analysis device 103 is provided in the space traffic control device 100 described in embodiment 1, 2, or 3, and also in the space traffic management system 500 described in embodiment 1, 2, or 3. When the risk analysis device 103 displays an intrusion warning of space object A into a danger area, and if the danger area is an area where a megaconstellation or constellation satellite group C flies, and the space object ID of space object A and the satellite group ID of satellite group C contained in the risk warning device are input, the megaconstellation business device or constellation business device performs a risk analysis using precise orbit information of the satellite group from a space information recorder implemented in the device, predicts a collision of individual satellites, and outputs the collision time and position coordinates.

[0202] The danger avoidance action support device 104 is provided in the space traffic control device 100 described in the first, second, or third embodiment, and is also provided in the space traffic management system 500 described in the first, second, or third embodiment. The danger avoidance action support device 104 displays all or some of the following for space objects A and B or satellite group C for which danger has been reported by the danger warning device: an indication that the business equipment of space object A will take danger avoidance action; an indication that the business equipment of space object B will take danger avoidance action; an indication that the business equipment of satellite group C will take danger avoidance action; an indication that the business equipment for debris removal will take danger avoidance action; an indication that neither space object A nor space object B will take danger avoidance action; an indication that neither space object A nor satellite group C will take danger avoidance action; an indication that the business equipment for rocket launch will take danger avoidance action; an indication that the business equipment of a space object in the middle of orbital transfer will take danger avoidance action; an indication that the business equipment of a space object in the middle of de-orbit will take danger avoidance action; an indication that the parties involved have reached agreement; and an indication that the parties involved have not reached agreement and adjustment is required.

[0203] The security device 105 is provided in the space traffic control device 100 described in embodiment 1, 2, or 3, and is also provided in the space traffic management system 500 described in embodiment 1, 2, or 3. The security device 105 is composed of all or part of an encryption device, a password system, and a biometric authentication system to prohibit unauthorized users from changing information.

[0204] The space information recorder 101 is provided in the space traffic control device 100 described in embodiment 1, 2, or 3, and is also provided in the space traffic management system 500 described in embodiment 1, 2, or 3. The space information recorder 101 is provided in the space traffic control device 100 provided in each business device (management business device 40) described in embodiments 1 to 4.

[0205] The danger warning device 102 is provided in the space traffic control device 100 described in embodiment 1, 2, or 3, and is also provided in the space traffic management system 500 described in embodiment 1, 2, or 3. The danger warning device 102 is provided in the space traffic management device 100 provided in each business device (management business device 40) described in embodiments 1 to 4.

[0206] The risk analysis device 103 is provided in the space traffic control device 100 described in embodiment 1, 2, or 3, and is also provided in the space traffic management system 500 described in embodiment 1, 2, or 3. The risk analysis device 103 is provided in the space traffic management device 100 provided in each business device (management business device 40) described in embodiments 1 to 4.

[0207] The danger avoidance action support device 104 is provided in the space traffic control device 100 described in embodiment 1, 2, or 3, and is also provided in the space traffic management system 500 described in embodiment 1, 2, or 3. The danger avoidance action support device 104 is provided in the space traffic control device 100 provided in each business device (management business device 40) described in embodiments 1 to 4.

[0208] Embodiment 6 In this embodiment, differences from or additions to embodiments 1 to 5 will be mainly described. In this embodiment, the same components as those in embodiments 1 to 5 will be assigned the same reference numerals, and the description thereof may be omitted.

[0209] In this embodiment, a space traffic management system 500 is described that includes business devices (management business devices 40) for various businesses as well as a terminal 481 or a mobile terminal 482. The terminal 481 is, for example, a personal computer and is also called a terminal device. The mobile terminal 482 is, for example, a computer such as a portable personal computer, a smartphone, or a mobile phone and is also called a mobile terminal device.

[0210] FIG. 43 is a configuration diagram of Example 5-9 of a space traffic management system 500 according to this embodiment. In example 5-9 of the space traffic management system 500, in addition to business equipment for various businesses, a terminal 481 is provided. In Figure 43, examples of business equipment for various businesses include business equipment for various satellites, debris removal business equipment 45, SSA business equipment 47, rocket launch business equipment 46, space insurance business equipment, and space traffic management business equipment. Business equipment for other businesses may also be used.

[0211] The space information recorder 101 includes a space object ID and orbit information for identifying a space object, as well as a group ID and orbit information for space objects flying at the same nominal altitude. The multiple space traffic management devices 100 in Example 5-9 of the space traffic management system 500 have compatible data formats, share space object IDs, and share orbit information corresponding to the space object IDs between business devices that comply with the disclosure condition information. The risk analysis device 103 of each business device is provided with a common or compatible algorithm.

[0212] The terminal 481 also includes a space traffic control device 100 that includes a space information recorder 101, a danger warning device 102, and a danger analysis device 103, and an interface 109 with each business device. In the example 5-9 of the space traffic management system 500, each of the multiple terminals 481 is connected to a corresponding business device.

[0213] In the future, space traffic management operators may take over the information disclosure work, such as collision warnings for private space objects, which has been carried out by the U.S. CSpOC. In this case, the space traffic management operators' space traffic management business equipment will perform risk analysis on the space object information they have independently collected and provide risk warnings as public information. Specifically, risk warnings will be provided as public information when a dangerous approach, a collision between space objects, or the intrusion of a space object into a dense area of ​​multiple satellites with the same nominal altitude, such as a megaconstellation, is predicted.

[0214] This public information can be obtained by each business device, and at the same time, the information can be instantly shared on individual terminals owned by each business operator. When a danger alert is issued late at night and an emergency response is required, there is a problem that the response will be delayed if information is shared only with business devices owned by the corporation. Therefore, we will create a system that allows danger warnings to be shared instantly on the devices of individuals who have responsibility and authority for the operation of business equipment, and if necessary, we will realize a space traffic management system that allows individuals to issue operational instructions to business equipment for which they have responsibility and authority from their personal devices.

[0215] It is difficult to perform risk analysis of any two objects on a mobile device due to the huge number of space objects. However, if the identification IDs of two objects predicted to pose a risk are made public, the risk analysis can be reproduced on a device such as a personal computer. Furthermore, if the algorithm is the same, it has the advantage of being possible to reproduce the same analysis results as the operator that issued the risk alert. Furthermore, there are cases where businesses have their own risk analysis devices with higher performance than the published algorithms, and in such cases, it is possible to perform high-precision risk analysis unique to the business device by issuing detailed analysis instructions via the interface with the individual business device provided by the terminal.

[0216] If an individual working in the SSA business has a device, they can issue instructions to their own space situation monitoring device to independently remeasure the orbital information of a space object reported in a danger alert.The measured orbital information can then be provided to the public information from the SSA business device, which has the effect of enabling highly accurate SSA measurement information to be shared among stakeholders. A personal device used by a service provider using mega-constellation satellites may receive an intrusion warning about an intrusion into the altitude range where the satellites they manage fly. In such cases, they can use real-time, high-precision orbital information from the mega-constellation satellites they manage to instruct their business equipment to perform collision analysis for individual satellites and take evasive action if necessary. The public information on the space traffic management system is sometimes called the Open Architecture Data Repository (OADR).

[0217] FIG. 44 is a configuration diagram of Example 5-10 of a space traffic management system 500 according to this embodiment. In the example 5-10 of the space traffic management system 500, a mobile terminal 482 and business devices of various businesses are connected. Also, a space information recorder 101 and a risk analysis device 103 are provided in the cloud environment.

[0218] The mobile terminal 482 is equipped with a space traffic management portal 821 that functions as a portal site for the space traffic management device 100, a danger warning tool 822 that communicates danger through screen display, sound, or vibration, and an interface 823 with individual business devices.

[0219] The space traffic management portal 821 has a means for viewing the space information recorder 101 and a means for operating the risk analysis tool. The space traffic management portal 821 has, for example, an operation screen that is compatible with the terminal 481 and that operates the space information recorder 101, which allows viewing of the public information of the space traffic management system 500. In addition, the mobile terminal 482 has an operation screen that operates the risk analysis tool that is common or compatible with the risk analysis device 103 that the terminal 481 has.

[0220] The danger warning tool 822 is a tool that obtains danger information from the public information of the space traffic management system 500, which is reported by the danger warning device 102 that warns of approach or collision of a space object or intrusion into a danger area, and transmits the warning visually, audibly, or tactilely.

[0221] In the mobile terminal 482, the danger warning tool obtains, as danger information, the IDs of two space objects predicted to pose a danger, or the ID of a space object predicted to enter a danger area and the IDs of a group of space objects flying in the danger area, from the public information of the space traffic management system 500. Then, the space traffic management portal 821 obtains the trajectory information of the space object with the ID from the public information, and operates the danger analysis tool to display the time of occurrence and location information of the predicted danger.

[0222] The mobile terminal 482 is, for example, a portable personal computer, a smartphone, a mobile phone, etc. In the mobile terminal 482, if data or applications are stored in a cloud environment and the mobile terminal is provided with only a human transmission function related to vision, hearing, or touch, it is possible to realize the same operation as the terminal 481. The interface 823 with the individual business device may be provided with a function for direct remote control, or may be a means of communication such as email or telephone. According to the portable terminal 482, even a portable terminal with limited memory area can perform the same operations as the terminal 481, so there is an advantage that the space traffic control portal 821 can be carried around with great portability.

[0223] The SSA business device 47 according to this embodiment includes a space situation monitoring device. The SSA business device 47 acquires a space object ID and an orbit information acquisition command from a terminal 481 or a mobile terminal 482 via an interface with the business device included in the terminal 481 or the mobile terminal 482. The SSA business device 47 then acquires the orbit information of the ID from the space situation monitoring device.

[0224] The mega-constellation business device 41 according to this embodiment acquires, from the terminal 481 or the mobile terminal 482, the ID of a space object predicted to intrude into the orbital altitude band in which the constellation of satellites it manages flies, the time period and location information for the predicted intrusion, and a detailed analysis command, via an interface with the business device provided in the terminal 481 or the mobile terminal 482. The mega-constellation business device 41 then performs a risk analysis using the real-time high-precision orbit information.

[0225] The debris removal business equipment 45 of this embodiment obtains the space object ID, time information when danger is predicted, location information, and a debris removal satellite operation command from the terminal 481 or mobile terminal 482 via an interface with the business equipment equipped on the terminal 481 or mobile terminal 482, and operates the debris removal satellite.

[0226] The rocket launch business equipment 46 of this embodiment obtains instructions to change the rocket launch time from the terminal 481 or the mobile terminal 482 via an interface with the business equipment equipped on the terminal 481 or the mobile terminal 482, and changes the rocket launch plan.

[0227] The space insurance business device according to this embodiment manages space insurance that compensates for damages caused by collisions between multiple space objects flying in space. The space insurance business device acquires space insurance brokerage instructions from a terminal 481 or a mobile terminal 482 to business devices related to foreseen risks via an interface with the business devices equipped in the terminal 481 or the mobile terminal 482, and solicits space insurance.

[0228] In the above first to sixth embodiments, each part of the space traffic management system and the space traffic control device has been described as an independent functional block. However, the configuration of the space traffic management system and the space traffic control device does not have to be as in the above-described embodiments. The functional blocks of the space traffic management system and the space traffic control device may have any configuration as long as they can realize the functions described in the above-described embodiments. Furthermore, the space traffic management system and the space traffic control device may be a single device or a system composed of multiple devices.

[0229] Furthermore, it is possible to combine two or more parts of the first to sixth 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, in the first to sixth embodiments, the parts of the first to sixth embodiments can be freely combined, or any of the components can be modified, or any of the components in the first to sixth embodiments can be omitted.

[0230] 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]

[0231] 20 Satellite constellation, 21 Orbital plane, 30 Satellite, 30a Debris removal satellite, 31 Satellite control device, 32 Satellite communication device, 33 Propulsion device, 34 Attitude control device, 35 Power supply device, 36 Capture device, 40 Management business device, 41 Mega constellation business device, 42 LEO constellation business device, 43 Satellite business device, 44 Orbital transfer business device, 45 Debris removal business device, 46 Rocket launch business device, 47 SSA business device, 51 Orbital forecast information, 52 Satellite orbit forecast information, 53 Debris orbit forecast information, 511 Space object ID, 512 Forecast origin, 513 Forecast orbital elements, 514 Forecast error, 60 Space object, 70 Earth, 100 Space traffic management device, 110 Passage determination unit, 111 Intrusion warning, 120 Warning generation unit, 130 Warning notification unit, 140 Memory unit, 190 debris removal control device, 191 control unit, 55 orbital control command, 56 control command, 57 capture command, 301 satellite orbital region, 500 space traffic management system, 600 satellite constellation formation system, 11, 11b satellite constellation formation unit, 300 satellite group, 700, 701, 702 ground equipment, 510 orbital control command generation unit, 520 analysis and 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, 101 space information recorder, 102 danger warning device, 103 danger analysis device, 104 danger avoidance action support device, 105 security device, 106 space traffic management rule information, 107 danger avoidance action implementation plan information, 61 international rules, 62 Trial phase rules, 621 Congested area identification information, 622 Dangerous area identification information, 623 Traffic management rule information, 121 Orbital object number management information, 112 Flight safety measures information, 113 Orbit information, 801, 802, 803 Elliptical bubble, 481 Terminal, 482 Mobile terminal, 109, 823 Interface, 821 Space traffic management portal, 822 Danger warning tool.

Claims

1. A space traffic management system is provided which is implemented in a business device that manages space objects flying in space and has a space traffic management device that manages the flight safety of space objects, The space traffic control device comprises: Space traffic management rules information, a space information recorder that records orbital information of a space object; a danger warning device that warns of the danger of approach or collision with a space object; a hazard analysis device for analyzing the trajectory of a space object; a danger avoidance behavior support device that displays the role allocation of avoidance behavior of space objects; Hazard avoidance action plan, a measurement error inspection device; A security device to prevent information tampering; It has all of the above. The space information recorder comprises: Orbital object number management information; Flight safety measure information, which is information on the orbital altitude for each orbital plane to ensure flight safety; A space traffic management system that has all of the above.

2. The space traffic management system includes: A plurality of space traffic management devices are provided, each of which is installed in the business equipment of a plurality of management operators; The multiple space traffic control devices are connected to each other via communication lines, Multiple space information recorders The information includes a space object ID (Identifier) ​​for identifying a space object, orbital information, and disclosure condition information, and a business device ID for identifying a business device and disclosure condition information, the plurality of space traffic control devices; A space traffic management system as described in claim 1, which has compatible data formats, shares space object IDs and business device IDs, shares space information corresponding to space object IDs between business devices that comply with the disclosure condition information, and has a common algorithm between different business devices in the risk analysis device and measurement error inspection device.

3. The space information recorder comprises: As the on-orbit object number management information, orbital object number management information acquired from the business device that manages the space object; A space traffic management system as described in claim 2, which can obtain orbital object number management information obtained by different measurement means from another business device, and compare and evaluate the disclosed information of the business device that manages the space object to perform third-party verification.

4. The space information recorder comprises: Orbital information for a specific space object ID: Orbital information obtained from a business device that manages the space object; A space traffic management system as described in claim 2, which can obtain orbital information obtained by different means from another business device and compare and evaluate it with the disclosed information of the business device that manages the space object for third-party verification.

5. The space information recorder comprises: Measurement errors contained in orbit information include: Measurement errors obtained from the business equipment that manages the space object; and A space traffic management system as described in claim 2, in which measurement errors obtained by different means can be obtained from another business device and compared with the disclosed information of the business device that manages the space object for third-party verification.

6. A space traffic management device that is implemented in a business device that manages space objects flying in space and manages the flight safety of space objects, The space traffic control device comprises: Space traffic management rules information, a space information recorder that records orbital information of a space object; a danger warning device that warns of the danger of approach or collision with a space object; a hazard analysis device for analyzing the trajectory of a space object; a danger avoidance behavior support device that displays the role allocation of avoidance behavior of space objects; Hazard avoidance action plan, a measurement error inspection device; A security device to prevent information tampering; It has all of the above. The space information recorder comprises: Orbital object number management information; Flight safety measure information, which is information on the orbital altitude for each orbital plane to ensure flight safety; A space traffic control device that has all of the above.

7. A space traffic control device according to claim 6, A rocket launch business device provided in the space traffic management system according to any one of claims 1 to 5.

8. A space traffic control device according to claim 6, A debris removal business device provided in the space traffic management system according to any one of claims 1 to 5.

9. A space traffic control device according to claim 6, A space situation monitoring business device provided in the space traffic management system according to any one of claims 1 to 5.

10. A space traffic control device according to claim 6, A danger avoidance support business device provided in the space traffic management system according to any one of claims 1 to 5.

11. A space traffic control device according to claim 6, A space insurance business device provided in the space traffic management system according to any one of claims 1 to 5.

Images