Collision Avoidance Assistance Program

Abstract

To determine a space object to be avoided to which avoidance behavior should be taken, of objects considered to be dangerous which are foreseen to collide, and identify existence of the object considered to be dangerous before a collision to output danger warning to an insurance project company and a space object management project company.SOLUTION: A collision avoidance support program makes a computer execute a danger warning output process for identifying existence of an object considered to be dangerous on the basis of orbit forecast information to output danger warning, before space objects of a plurality of space objects collide to each other. The danger warning outputting process outputs danger warning to an insurance project company having a space insurance program which pays an insurance from preliminarily collected insurance premiums when a space object A collides with a space object B and to a space object management project company that manages at least any of the plurality of space objects.SELECTED DRAWING: Figure 28

Description

[Technical Field]

[0001] The present invention relates to a satellite constellation formation system, a collision avoidance support program, a collision avoidance support system, a collision avoidance support device, a satellite constellation business device, a rocket launch business device, a debris removal business device, a space insurance management business device, a space object management business device, and a space situation monitoring business device. [Background technology]

[0002] 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. In addition, the amount of space debris, such as satellites that have become uncontrollable due to malfunctions or rocket debris, is also increasing. With the rapid increase in space objects such as satellites and space debris in outer space, there is a growing need for international rules in space traffic management (STM) to avoid collisions of space objects.

[0003] Measures are also needed for avoidance actions in the event that a collision is predicted in advance. Avoidance actions are implemented when a collision is predicted in manned space stations or geostationary satellites operated by satellite communication operators. However, in an environment where satellites from multiple operators are densely concentrated in low orbit and some are equipped with avoidance action functions and others are not, it is difficult to formulate unified rules for avoidance actions. This is because when satellites that take evasive action and satellites that do not take evasive action coexist in a densely populated area, it creates a new risk of collision between satellites that have taken evasive action.

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

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

[0006] In satellite constellations, the orbital altitudes of the different orbital planes are generally the same. In orbital planes with the same orbital altitudes but different angles between their normals, there is a risk of collision at the intersections. The collision risk is very high in satellite constellations with many intersections. In addition, when space debris passes through the orbital plane of a satellite constellation in order to be collected, the risk of collision between the satellite and the space debris also increases. However, Patent Document 1 does not describe any avoidance actions to be taken when a collision is predicted in advance.

[0007] The present invention aims to determine, among the predicted dangerous objects for which collision is predicted, the space objects to be avoided for which evasive action should be taken, and to identify the existence of the predicted dangerous objects before collision and output a danger warning to insurance companies and space object management companies. [Means for solving the problem]

[0008] In the collision avoidance support program of the collision avoidance support device according to the present invention, which supports avoidance of collisions between a plurality of space objects flying in space, the collision avoidance assistance device includes a storage unit that stores orbit prediction information that is a predicted value of the orbit of each of the plurality of space objects; an alarm control process for determining whether or not a plurality of space objects whose positional relationship is dangerous at the same time exist as potential hazardous objects among the plurality of space objects based on the orbit forecast information, and outputting a danger alarm indicating the presence of the potential hazardous objects when it is determined that the potential hazardous objects exist; When the danger warning is output, an avoidance determination process is performed to determine an avoidable space object that is a space object for which an avoidance operation is to be performed, from among the space objects included in the predicted danger objects. A machine learning process that updates an algorithm for an avoidance determination process that determines an avoidable space object by machine learning using the determination result of the avoidable space object. A collision avoidance assistance program that causes a computer to execute the following: The collision avoidance assistance program causing a computer to execute a danger warning output process for identifying the presence of the potential dangerous object based on the orbit forecast information and outputting the danger warning before a collision occurs between the plurality of space objects; The danger warning output process includes: The danger alert is output to an insurance company of a space insurance program that pays insurance money from insurance premiums collected in advance in the event of a collision between space object A and space object B among the plurality of space objects, and to a space object management company that manages at least one of the plurality of space objects. [Effects of the Invention]

[0009] The collision avoidance support program of the present invention causes a computer to execute a danger warning output process that identifies the presence of a potential hazardous object based on orbit forecast information and outputs a danger warning before a collision between multiple space objects. The danger warning output process outputs a danger warning to an insurance company of a space insurance program that pays insurance claims from insurance premiums collected in advance in the event of a collision between space objects A and B, and to a space object management company that manages at least one of the multiple space objects. Therefore, the collision avoidance support program of the present invention has the effect of determining an avoidable space object for which avoidance action should be taken among potential hazardous objects for which a collision is predicted, and identifying the presence of a potential hazardous object before a collision and outputting a danger warning to the insurance company and the space object management company. [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] 1 is a configuration diagram of a collision avoidance assistance system according to a first embodiment. [Figure 10] FIG. 4 is a flowchart of a recorder process for setting orbit forecast information according to the first embodiment. [Figure 11] FIG. 3 is a diagram showing an example of orbit forecast information according to the first embodiment. [Figure 12] FIG. 4 is a flowchart of a recorder process for setting track performance information according to the first embodiment. [Figure 13] FIG. 3 is a diagram showing an example of track performance information according to the first embodiment. [Figure 14] FIG. 4 is a flowchart of an alarm control process performed by an alarm control unit according to the first embodiment. [Figure 15] FIG. 3 is a diagram illustrating an image of the intersection of error ranges of two satellites according to the first embodiment. [Figure 16] FIG. 4 is a diagram showing a state in which error ranges of two satellites overlap according to the first embodiment. [Figure 17] FIG. 4 is a diagram showing a state in which the distance between two satellites is equal to or less than the approach threshold value according to the first embodiment. [Figure 18] FIG. 3 is a diagram showing warning issuance information according to the first embodiment. [Figure 19] 4 is a flowchart of a performance result presentation process performed by a performance result presentation unit according to the first embodiment. FIG. [Figure 20] FIG. 10 is a configuration diagram of a collision avoidance assistance device according to a modification of the first embodiment. [Figure 21] FIG. 10 is a configuration diagram of a collision avoidance assistance device according to a second embodiment. [Figure 22]FIG. 10 is a flowchart showing an example of an avoidance decision process based on a condition such as whether or not a space object is a rocket according to the second embodiment. [Figure 23] FIG. 10 is a flowchart showing an example of an avoidance decision process based on a condition such as whether or not a space object is a rocket according to the second embodiment. [Figure 24] FIG. 10 is a flow diagram of an avoidance decision process based on a condition such as whether or not a space object is in normal operation according to the second embodiment. [Figure 25] FIG. 10 is a flow diagram of an avoidance decision process based on a condition such as whether or not a space object belongs to a megaconstellation according to the second embodiment. [Figure 26] 10 is a flow diagram of an avoidance decision process based on a condition such as whether or not a space object is an orbital transfer satellite according to the second embodiment. [Figure 27] FIG. 10 is a flow diagram of an avoidance decision process based on a condition such as whether or not a space object has a collision avoidance function according to the second embodiment. [Figure 28] 10 shows an example of a summary of the avoidance decision process according to the second embodiment. [Figure 29] 10 shows an example of input information in the machine learning process according to the second embodiment. [Figure 30] FIG. 10 is a configuration diagram of a space insurance support system and a space insurance support device according to a third embodiment. [Figure 31] FIG. 11 is a flow diagram of space insurance support processing by the space insurance support device according to the third embodiment. [Figure 32] 10 shows an example of information disclosure by a management business operator according to the third embodiment and an example of space insurance corresponding to the management business operator. [Figure 33] 10 shows a specific example of insurance premium assessment processing and liability assessment processing according to the third embodiment. [Figure 34] 10 shows a specific example of insurance premium assessment processing and liability assessment processing according to the third embodiment. [Figure 35] An example of the risk of collision between a space object in routine operation and a space object in non-routine operation. [Figure 36] An example of the risk of collision between a geostationary satellite undergoing orbital transfer and a space object in routine operation. [Figure 37]An example of the risk of collision between a launched rocket and a mega-constellation. [Figure 38] FIG. 10 is a configuration diagram of a collision insurance execution system and a collision insurance execution device according to a fourth embodiment. [Figure 39] FIG. 11 is a flowchart of a collision insurance execution process performed by the collision insurance execution device according to the fourth embodiment. [Figure 40] FIG. 10 is a diagram showing space collision insurance according to the fourth embodiment. [Figure 41] 13 shows an example of the functional configuration of a satellite constellation forming system according to a fifth embodiment. [Figure 42] FIG. 13 is a configuration diagram of an information management system according to a fifth embodiment. [Figure 43] FIG. 13 is a flow diagram of information disclosure processing according to the fifth embodiment. [Figure 44] FIG. 13 is a flowchart of a satellite constellation control process according to the fifth embodiment. [Figure 45] FIG. 10 is a diagram showing the error range between the forecast value of a rocket launch and the satellite constellation according to the fifth embodiment. [Figure 46] FIG. 10 is a diagram showing the error range between the forecast value of a rocket launch and the satellite constellation according to the fifth embodiment. [Figure 47] FIG. 13 is a configuration diagram of an information management device according to a modified example of the fifth embodiment. [Figure 48] FIG. 10 is a flowchart showing a process of updating a collision avoidance algorithm based on machine learning effects according to the second embodiment. [Figure 49] FIG. 10 is a flowchart showing a process of updating a collision avoidance algorithm based on machine learning effects according to the second embodiment. [Figure 50] 13 shows an example of the configuration of an SSA business device according to the seventh 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 collision avoidance support 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 of Figure 2, satellites equipped with Earth observation equipment, such as optical sensors or radio wave sensors such as synthetic aperture radar, fly in the same orbital plane at the same altitude. In this way, in a satellite group 300 in which the terrestrial imaging range is time-delayed and subsequent satellites overlap, multiple satellites in orbit take turns capturing terrestrial images of a specific point on the ground in a time-division manner, thereby providing an Earth observation service.

[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 increases the variety of 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, to avoid collisions with space objects, there is an increasing need for post-mission disposal (PMD) after the completion of an orbital mission, or for ADR, which involves deorbiting debris such as failed satellites and floating rocket upper stages using external means such as debris collection satellites. International discussions on the need for such ADR have begun, known as STM. Here, PMD stands for Post Mission Disposal, ADR stands for Active Debris Removal, and STM stands 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 collision avoidance assistance device 100 according to this embodiment assists in avoiding collisions between a plurality of space objects 60 flying in space. As described above, the risk of collisions between space objects 60 is increasing with the rapid increase in space objects such as satellites and debris in outer space.

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

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

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

[0025] The satellite constellation forming system 600 includes a processor 910, as well as other hardware such as a memory 921, an auxiliary storage device 922, an input interface 930, an output interface 940, and a communication device 950. The processor 910 is connected to the other hardware via signal lines and controls this other hardware. The hardware of the satellite constellation forming system 600 is similar to the hardware of the collision avoidance assistance device 100, which will be described later with reference to FIG. 9.

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

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

[0028] The satellite control device 31 is a computer that controls the propulsion devices 33 and the attitude control device 34, and includes a processing circuit. Specifically, the satellite control device 31 controls the propulsion devices 33 and the attitude control device 34 in accordance with various commands transmitted from the ground facility 700. The satellite communication device 32 is a device that communicates with the ground facility 700. Specifically, the satellite communication device 32 transmits various data related to its own satellite to the ground facility 700. In addition, the satellite communication device 32 receives various commands transmitted from the ground facility 700. The propulsion device 33 is a device that provides thrust to the satellite 30 and changes the speed of the satellite 30. Specifically, the propulsion device 33 is an electric propulsion device. Specifically, the propulsion device 33 is an ion engine or a Hall thruster. The attitude control device 34 controls the attitude of the satellite 30, the angular velocity of the satellite 30, and the line of sight (Line Of Sight) direction. The attitude control system 34 is a device for controlling attitude elements such as the attitude sensor, the earth sensor, the sun sensor, the star tracker, the thruster, and the magnetic sensor. The attitude control system 34 changes each attitude element to a desired direction. Alternatively, the attitude control system 34 maintains each attitude element in a desired direction. The attitude control system 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 the measurement data of 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.

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

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

[0031] The ground equipment 700 forms the satellite constellation 20 by communicating with each satellite 30. The ground equipment 700 is provided in the collision avoidance assistance device 100. The ground equipment 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 equipment 700 is similar to the hardware of the collision avoidance assistance device 100, which will be described later with reference to FIG. 9.

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

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

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

[0035] ***Configuration Description*** FIG. 9 is a configuration diagram of a collision avoidance assistance system 500 according to this embodiment. The collision avoidance assistance system 500 includes a management business device 40 and a collision avoidance assistance device 100 that communicates with the management business device 40. The collision avoidance assistance device 100 may be mounted on a ground facility. Alternatively, the collision avoidance assistance device 100 may be mounted on a satellite 30. Furthermore, the collision avoidance assistance device 100 may be mounted on a satellite constellation forming system 600. Alternatively, the collision avoidance assistance device 100 may be mounted on at least one of the management business devices 40.

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

[0037] 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 an orbital transfer business that provides support for satellite orbital transfer. The debris collection business device 45 is a computer of a debris collection business operator that carries out the business of collecting debris. The rocket launch business device 46 is a computer of a rocket launch business that 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.

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

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

[0040] The collision avoidance support device 100 includes, as functional elements, a recorder processing unit 110, an alarm control unit 120, a performance presentation unit 130, and a storage unit 140. The storage unit 140 stores a space information recorder 50 and alarm issuance information 141.

[0041] The functions of the recorder processing unit 110, the alarm control unit 120, and the performance presentation 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. Moreover, the storage unit 140 may be provided separately in the memory 921 and the auxiliary storage device 922.

[0042] The processor 910 is a device that executes a collision avoidance support program. The collision avoidance support program is a program that realizes the functions of the recorder processing unit 110, the warning control unit 120, and the performance presentation unit . The processor 910 is an integrated circuit (IC) that performs arithmetic processing. A specific example of the processor 910 is a central processing unit (CPU). Unit), DSP (Digital Signal Processor), and GPU (Graphics Processing Unit).

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

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

[0045] 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 collision avoidance support device 100 communicates with the management business device 40 via the communication device 950.

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

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

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

[0049] The "part" of each part of the collision avoidance assistance device may be read as "processing," "procedure," "means," "stage," or "step." Also, the "processing" of the recorder processing, warning control processing, and performance presentation processing may be read as "program," "program product," or "computer-readable recording medium on which the program is recorded." The collision avoidance assistance program causes a computer to execute each process, procedure, means, stage, or step of the collision avoidance assistance device, where the "part" of the device is replaced with "process," "procedure," "means," "stage," or "process." The collision avoidance assistance method is a method performed by the collision avoidance assistance device executing the collision avoidance assistance program. The collision avoidance assistance program may be provided by being stored in a computer-readable recording medium, or each program may be provided as a program product.

[0050] ***Explanation of Operation*** The collision avoidance assistance process performed by the collision avoidance assistance device 100 according to this embodiment will be described with reference to FIGS.

[0051] <Recorder processing (orbit forecast information): S100> Fig. 10 is a flow diagram of recorder processing for setting orbit forecast information 51 according to this embodiment, and Fig. 11 is a diagram showing an example of orbit forecast information 51 according to this embodiment.

[0052] In step S101, the recorder processing unit 110 acquires flight forecast information 401 representing a forecast of the flight of each of the multiple space objects 60 from a management business device 40 used by a management business operator that manages the multiple space objects 60. As described above, the management business operator is an operator that manages space objects 60 flying in space, such as satellite constellations, various satellites, rockets, and debris. Also, as described above, the management business device 40 used by each management business operator is a computer such as a megaconstellation business device 41, a LEO constellation business device 42, a satellite business device 43, an orbital transfer business device 44, a debris collection business device 45, a rocket launch business device 46, and an SSA business device 47.

[0053] In step S102, based on the acquired flight forecast information 401, the recorder processing unit 110 sets the forecast origin 512 of the orbit of each of the multiple space objects, the forecast orbit elements 513 that specify the orbit, and the forecast error 514 predicted in the orbit as orbit forecast information 51. Then, the recorder processing unit 110 stores the space information recorder 50 including the orbit forecast information 51 in the memory unit 140. The orbit forecast information 51 is a forecast value of the orbit of each of the multiple space objects.

[0054] Based on the flight forecast information 401, the recorder processing unit 110 may set a forecast of the flight state of each of the multiple space objects as a forecast flight state 515 in the orbit forecast information 51. In this case, the recorder processing unit 110 sets, in the forecast flight state 515 of each of the multiple space objects, whether each of the multiple space objects is in a normal operating state or an unnormal operating state. The normal operating state is, specifically, a state in which a satellite is flying in an orbit in a normal operation. The unnormal operating state includes a launch transient state from the launch of each of the multiple space objects until it is inserted into orbit, and a post-release transient state from the de-orbit of each of the multiple space objects until it enters the atmosphere or is inserted into a disposal orbit.

[0055] An example of orbit forecast information 51 according to this embodiment will be described with reference to FIG. The orbit forecast information 51 includes a space object ID (Identifier) ​​511, a forecast origin 512, forecast orbital elements 513, a forecast error 514, and a forecast flight state 515.

[0056] The space object ID 511 is an identifier that identifies the space object 60. In Fig. 11, a satellite ID and a debris ID are set as the space object ID 511. Specifically, the space object is an object such as a rocket launched into space, an artificial satellite, a space station, a debris collection satellite, a planetary exploration spacecraft, or a satellite or rocket that has become debris after completing its mission.

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

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

[0059] Forecasted flight state 515 is a forecast of the flight state of each of the multiple space objects. Forecasted flight state 515 indicates whether the forecast of the flight state of each of the multiple space objects is a normal operating state, a launch transient state, or a post-release transient state. Forecasted flight state 515 may also include whether or not avoidance operations will be performed or whether or not autonomous avoidance operations will be performed.

[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] <Recorder processing (track performance information): S200> Fig. 12 is a flow diagram of a recorder process for setting the track performance information 52 according to this embodiment. Fig. 13 is a diagram showing an example of the track performance information 52 according to this embodiment.

[0062] In step S201, the recorder processing unit 110 acquires flight performance information 402 representing the flight performance of each of the multiple space objects from at least one of each of the multiple space objects and the management business device 40. Specifically, the recorder processing unit 110 acquires the flight performance information 402 from the management business that manages the space object 60. Alternatively, the recorder processing unit 110 may acquire the flight performance information 402 directly from the space object 60.

[0063] In step S202, based on the acquired flight performance information 402, the recorder processing unit 110 sets the performance origin 522 of the orbit of each of the multiple space objects, the performance orbital elements 523 that specify the orbit, and the performance position coordinates 242 of each of the multiple space objects as orbit performance information 52. Then, the recorder processing unit 110 includes the orbit performance information 52 in the space information recorder 50. The recorder processing unit 110 may set the actual flight state of each of the multiple space objects as the actual flight state 525 in the orbit performance information 52 based on the flight performance information 402. In this case, the recorder processing unit 110 sets the actual flight state 525 of each of the multiple space objects to indicate whether each of the multiple space objects is in a normal operating state or an unsteady operating state. The unsteady operating state includes a launch transient state from launch of each of the multiple space objects to insertion into orbit, and a post-departure transient state from de-orbit of each of the multiple space objects to atmospheric re-entry or insertion into a disposal orbit.

[0064] An example of the track performance information 52 according to this embodiment will be described with reference to FIG. Orbit performance information 52 includes a space object ID 521, an actual epoch 522, actual orbit elements 523, a specific performance 524, and an actual flight state 525. Specific performance 524 includes a specific time 241 and actual position coordinates 242. That is, information about space object 60 at specific time 241 is set in orbit performance information 52.

[0065] The space object ID 521 is an identifier that identifies the space object 60. The structure of the space object ID 521 is the same as that of the space object ID 511.

[0066] Actual epoch 522 is the actual epoch of the orbit of each of the plurality of space objects. Actual orbital elements 523 are orbital elements that specify the orbit of each of the multiple space objects. Actual orbital elements 523 are the actual orbital elements of the orbit of each of the multiple space objects. In Figure 13, like the predicted orbital elements 513, the actual orbital elements 523 are set to the six Keplerian orbital elements.

[0067] In the specific performance 524, a specific time 241 and the position coordinates of the space object 60 corresponding to the specific time 241 are set as actual position coordinates 242. In this way, the orbit performance information 52 includes the actual position coordinates 242, which are the position coordinates of the space object 60 at the specific time 241.

[0068] Actual flight state 525 is the actual flight state of each of the multiple space objects. Actual flight state 525 indicates whether the actual flight state of each of the multiple space objects is a normal operation state, a launch transient state, or a post-release transient state. Actual flight state 525 may also include whether or not avoidance operations are being performed, or whether or not autonomous avoidance operations are being performed. Actual flight state 525 has the same configuration as forecast flight state 515.

[0069] <Alarm control process: S300> FIG. 14 is a flowchart of the warning control process by the warning control unit 120 according to this embodiment.

[0070] In step S301, the warning control unit 120 determines, based on the orbit forecast information 51, whether or not there is a space object in a positional relationship that warrants the issuance of a warning. Specifically, based on the orbit forecast information 51, the warning control unit 120 determines, among the multiple space objects, whether or not multiple space objects whose error ranges 502 overlap at the same time exist as objects predicted to collide 601. Furthermore, based on the orbit forecast information 51, the warning control unit 120 determines, among the multiple space objects, whether or not multiple space objects that approach beyond the approach threshold at the same time exist as objects predicted to approach 602. The objects predicted to collide 601 and the objects predicted to approach 602 are examples of predicted hazardous objects 65, which are multiple space objects among the multiple space objects that are in a dangerous positional relationship at the same time.

[0071] If the collision-predictable object 601 exists, the process proceeds to step S302. If the approach-predictable object 602 exists, the process proceeds to step S303. If neither the collision-predictable object 601 nor the approach-predictable object 602 exists, the process returns to step S301.

[0072] In step S302, the warning control unit 120 outputs a collision warning 23 indicating that there is a possibility of a collision with the collision-predictable object 601. In step S303, the warning control unit 120 outputs a proximity warning 22 indicating that there is a possibility of approaching the object 602 expected to approach.

[0073] FIG. 15 is a diagram showing an image of the intersection of error ranges 502a and 502b of two satellites 30a and 30b according to this embodiment. Orbit forecast 501a for satellite 30a is obtained from the forecast epoch and forecast orbital elements corresponding to satellite 30a in orbit forecast information 51. The forecast epoch is also called an epoch. The forecast orbital elements are also called orbital six elements. Similarly, orbit forecast 501b for satellite 30b is obtained from the forecast epoch and forecast orbital elements corresponding to satellite 30b in orbit forecast information 51. The warning control unit 120 acquires orbit forecasts 501a and 501b and error ranges 502a and 502b for satellites 30a and 30b based on orbit forecast information 51. Note that the orbit forecast 501 and error range 502 correspond to either satellite 30a or satellite 30b, as determined by the subscripts added to the symbols.

[0074] FIG. 16 is a diagram showing a state in which error ranges 502a and 502b of two satellites 30a and 30b according to this embodiment overlap. The warning control unit 120 determines whether or not multiple space objects whose error ranges 502 overlap at the same time exist as potential collision objects 601, based on the orbit forecast information 51. In FIG. 16, two satellites 30a and 30b are determined to be potential collision objects 601.

[0075] FIG. 17 is a diagram showing a state in which the distance between two satellites 30 according to this embodiment is equal to or less than the proximity threshold. The warning control unit 120 determines, based on the orbit forecast information 51, whether or not there are multiple space objects approaching at the same time that exceed the approach threshold as predicted approach objects 602. The approach threshold is a threshold for determining whether to issue a proximity warning 22. In FIG. 17, two satellites 30a and 30b are determined to be predicted approach objects 602.

[0076] In this way, the alarm control unit 120 issues a collision alarm 23 when the analysis results indicate contact or a shared area within the error range 502. Furthermore, when two space objects approach each other below or above the approach threshold, the alarm control unit 120 determines that there is a risk of collision and issues a proximity alarm 22.

[0077] FIG. 18 is a diagram showing the alarm issuance information 141 according to this embodiment. The warning issuance information 141 is transmitted to the management business device 40 and used for collision avoidance operations. The warning issuance information 141 includes the identifier of the space object for which the collision warning 23 or approach warning 22 has been issued, the time, the position coordinates at that time, and the overlap distance or approach distance of the error range. The collision warning 23 or the approach warning 22 is an example of a danger warning 25 that indicates the presence of multiple potential danger objects 65, which are space objects whose positional relationships are dangerous at the same time.

[0078] <Results presentation process> FIG. 19 is a flowchart of the performance result presentation process by the performance result presentation unit 130 according to this embodiment. In step S41, when any of the multiple space objects collide with each other, the performance presentation unit 130 extracts the orbit performance information 52 at the time when the space objects collided from the orbit performance information 52 as the collision performance 131. Then, the performance presentation unit 130 presents the collision performance 131 on an output device. The information that any of the multiple space objects collided with each other is notified, for example, by a management company.

[0079] A specific example of satellite orbital information will be described below. 11 and 13, orbital elements based on Kepler's laws are used as satellite orbital information. The orbital elements based on Kepler's laws are composed of the following elements. Epoch (year and day) Mean Motion (m): Mean Motion (orbits / day) or Semi-major Axis (km) Eccentricity: Eccentricity (unitless) ·Orbital inclination angle (i): Inclination (degrees) Right Ascension of Ascending Node (Ω): RAAN (Right Ascension of Ascending Node) (degrees) Argument of Perigee (ω): Argument of Perigee (degrees) ·Mean Anomaly (degrees)

[0080] Alternatively, a format called TLE (Two Line Element) may be used.

[0081] The accuracy of positioning satellites is directly affected by the time and position on orbit and the timing of their positioning signal transmission. For this reason, different satellite information such as almanac, ephemeris, or precise orbital ephemeris is used depending on factors such as accuracy, distribution method, or discrepancies between forecast and actual values. In terms of accuracy, the relationship is as follows: almanac (accuracy: several hundred meters to several kilometers) > ephemeris (broadcast calendar) (accuracy: several meters) > precise calendar (accuracy: several centimeters). In terms of distribution method, almanac and ephemeris are transmitted directly from the satellite, and are also available via the Internet or mobile phone lines. In positioning satellites that form constellations with multiple satellites, each satellite transmits information from all satellites as a coarse-precision almanac, while the fine-precision ephemeris transmits information from only its own satellite.

[0082] On the other hand, no accurate predictions have been made public for the launch transitional state until the satellite reaches normal operation, or the transitional state after deorbit until it enters the atmosphere or reaches a disposal orbit. Also, orbital predictions for rocket launches have not been made public. At a minimum, the location of the launch site, the planned launch time, and the planned flight route will be disclosed, with sufficient accuracy to verify that there is no risk of collision with satellites owned by satellite constellation operators at altitudes below 600 km.

[0083] It should be noted that the orbit forecast information 51 (public orbit forecast value information) and the orbit performance information 52 (precise orbital ephemeris performance information) do not necessarily have to be stored in the same storage location. The orbit performance information 52 only needs to be available when needed, such as after a collision accident occurs. For example, if an insurance company uses the information for its insurance business, the information may be stored in a storage location that is disclosed only to the insurance company by the company that operates the collision avoidance support device 100.

[0084] In this embodiment, the following space information recorder has been described. The space information recorder records space object information obtained from a management business device used by a management business that manages multiple space objects. The space object information includes orbital forecast information. The orbital forecast information includes the forecast origin, predicted orbital elements, and forecast error of the space object, as well as the estimated time or time period of the collision if a collision between space object A and space object B, which are included in the multiple space objects, is predicted.

[0085] The space object information also includes orbital performance information, which includes the time of collision estimated in a post-mortem verification after a collision between space object A and space object B, which are part of a group of space objects, as well as the positional information of space object A at or just before that time and the positional information of space object B at or just before that time.

[0086] The space object information also includes orbital forecast information including the predicted origin, predicted orbital elements, and forecast error of the space object, as well as the planned launch time and orbital information of the rocket launch operator.

[0087] The space object information also includes orbit forecast information including the space object's forecast origin, forecast orbit elements, and forecast error, as well as the de-orbit planned time and orbit information of the space object operator or debris removal operator in the de-orbit process.

[0088] The space object information also includes orbital forecast information including the forecast origin, forecast orbital elements, and forecast error of the space object, as well as the satellite operator's planned orbital transfer time and orbital information during the orbital transfer process.

[0089] The orbit forecast information includes the basis for calculating the amount of forecast error. The orbit forecast information may also include the verification results that led to the derivation of the forecast error. The orbit forecast information may also include an identification of whether the operation is normal or non-normal. The orbit forecast information may also include whether or not an avoidance operation is possible. The orbit forecast information may also include whether or not an autonomous avoidance operation is possible.

[0090] ***Explanation of the effect of this embodiment*** According to the collision avoidance assistance device 100 of this embodiment, the recorder processing unit 110 acquires flight forecast information 401 representing a forecast of the flight of each of a plurality of space objects from the management business device 40. Then, based on the flight forecast information 401, the recorder processing unit 110 sets a forecast value of the trajectory of each space object, which forecast value includes a forecast error, as trajectory forecast information 51 in the space information recorder 50. Therefore, according to the collision avoidance assistance device 100 of this embodiment, by using the trajectory forecast information 51 that takes into account the predicted trajectory error for each of a plurality of space objects, it has the effect of being able to accurately assist in collision avoidance.

[0091] Furthermore, according to the collision avoidance assistance device 100 of this embodiment, the recorder processing unit 110 acquires flight performance information 402 representing the flight performance of each of the plurality of space objects from at least one of each of the plurality of space objects and the management business device 40. Then, the recorder processing unit 110 sets the flight performance information 402 as orbit performance information 52 in the space information recorder 50 based on the flight performance information 402. Therefore, the collision avoidance assistance device 100 of this embodiment has the effect of being able to immediately present the flight performance desired by the management business.

[0092] The collision avoidance assistance device 100 according to this embodiment acquires flight performance information 402 from the management business device 40. However, the collision avoidance assistance device may also have a measuring means for measuring the flight status of a space object. That is, the collision avoidance assistance device may be equipped with a means for measuring the time and orbital information of a satellite, and may record an orbit history for orbital forecast information that has been previously made public.

[0093] The collision avoidance support device 100 according to this embodiment can, for example, disclose predicted satellite orbit information at the scheduled launch time to a rocket launcher planning to launch a new rocket. This enables the rocket launcher to take measures to avoid collisions. Furthermore, the space information recorder 50 of the collision avoidance support device 100 according to this embodiment has the effect of enabling comparison and verification of the predicted orbit and the actual orbit history.

[0094] In the collision avoidance assistance device 100 according to this embodiment, information from a measurement device mounted on a satellite may be used as the flight performance information 402, that is, a measurement means for measuring the precise orbital performance. The satellites that make up a mega-constellation are capable of inter-satellite communication or inter-satellite ranging with satellites that fly in front of or behind them in the same orbital plane, or satellites that fly in adjacent orbits. Therefore, by using information from measurement devices mounted on the satellites in collision avoidance support device 100 according to this embodiment, it is possible to measure highly accurate orbit information, including information such as measurement information from the GPS receivers equipped on the satellites. In addition, statistical processing of a large number of satellites can improve accuracy.

[0095] The collision avoidance assistance device 100 according to this embodiment includes a space information recorder 50 and is mounted on ground equipment.

[0096] Voice recorders are installed in aircraft to investigate aircraft accidents, and dashcams are installed in automobiles to investigate car accidents and as evidence. With the emergence of mega-constellation operators, satellite constellations with thousands of satellites built in low orbits at altitudes of around 600 km or less are at high risk of collision when new rockets are launched. Therefore, there is a need for "space information recorders," which could also be called satellite drive recorders, with a purpose similar to the voice recorders or drive recorders mentioned above. Even in the case of an aircraft accident involving an explosion, there is a possibility that onboard equipment can be recovered after the accident. For this reason, voice recorders are designed to be robust enough to withstand an explosion. Furthermore, since aircraft have a pilot, not only instrument information but also the pilot's voice is recorded, leaving a voice record that can be verified after the accident, including whether or not there were any abnormalities in the instruments. In contrast, in the case of a satellite collision, onboard equipment is scattered into space after the accident and is difficult to recover, and there is no pilot. For this reason, voice recording is unnecessary, and the main purpose is to record data from onboard instrumentation. Therefore, after flight history is acquired, data must be quickly transmitted to the ground or another satellite, and the data up to just before the collision accident must be stored in another location.

[0097] If a collision occurs in space and a satellite is scattered, it will be difficult to recover the onboard equipment. The satellite constellation concept allows for real-time data communication between the satellite and the ground, or between satellites. Therefore, flight performance information, i.e., satellite orbit history information, can also be transmitted in real time. The orbit performance information stored on ground facilities can be referenced after an accident, which has the advantage of being effective as a basis for verifying the accident situation.

[0098] In the collision avoidance assistance device 100 according to this embodiment, measurement information from an SSA asset, which is a ground observation device, may be used as a means for measuring flight performance information, that is, precise ephemeris performance. Recently, the development of SSSA assets using ground-based telescopes or radar has progressed, and their measurement accuracy has also improved. SSA information providers can also handle satellite orbital history, which has the advantage of allowing objective verification by third parties.

[0099] The collision avoidance assistance device 100 according to this embodiment is provided with an artificial space object equipped with an IC tag that includes a satellite identification ID, time, and location information, and a means for reading the IC tag information of the artificial space object flying at a distance without contact, and updates the content based on the IC tag information. Satellite constellations are designed so that when satellites approach each other within, say, 100 km, their IC tags emit radio waves for proximity communication that can be received by a trial-free omnidirectional antenna. This allows satellites that approach each other to receive each other's satellite information, and if there are many opportunities for satellites to approach each other in a mega-constellation, the amount of orbital performance information that can be shared in orbit will increase over time. In particular, when the in-orbit measurement information of each satellite is more accurate than that obtained by ground measurement means, IC tags are effective as a means of obtaining highly accurate in-orbit information.

[0100] In collision avoidance assistance device 100 according to this embodiment, orbit forecast information, that is, satellite orbit prediction information, may be made available to rocket launch companies, orbit insertion companies, and debris collection companies for a fee. In order for rocket launch operators to fulfill their obligation to ensure flight safety, they need accurate predicted orbit information for the satellites that make up mega-constellations. This has the effect of making satellite orbit prediction information highly valued as an asset and potentially becoming a source of revenue for satellite operators. In addition, there is a high risk of a satellite colliding with a satellite in a megaconstellation when it deorbits after completing its mission. Similarly, it may be possible to hold the operator of a deorbiting satellite or a debris collection company responsible for failing to take collision avoidance measures regarding the orbital information that has been made public, which could result in satellite orbital information becoming a source of revenue. Furthermore, operators who launch geostationary satellites into orbit use rockets to launch them into geostationary transfer orbit, and then transfer them to geostationary orbit using the satellite's own propulsion device. During this process, there is a risk of collision with mega-constellation satellites, and similar effects are expected.

[0101] ***Other Configurations*** <Variation 1> The space information recorder may store the orbit forecast information and the orbit performance information in a memory and may have a processor that executes a program. For example, the space information recorder may have the following functions.

[0102] The space information recorder is equipped with an insurance premium rate setting means for a space insurance program that pays insurance money from pre-collected insurance premiums in the event of a collision between space object A and space object B among multiple space objects. The insurance premium rate setting means sets the insurance premium rate based on the forecast error contained in the orbit forecast information.

[0103] The space information recorder also includes an insurance claim assessment means for a space insurance program that pays insurance claims from pre-collision premiums in the event of a collision between space object A and space object B among multiple space objects. The insurance claim assessment means extracts, from the orbital result information, orbital result information at the time the space objects collide as a collision result, and extracts, from the orbital forecast information, orbital forecast information at the time the space objects collide as pre-collision forecast information. The insurance claim assessment means assesses insurance claims based on a comparison of difference information A between the collision result and pre-collision forecast information for space object A and difference information B between the collision result and pre-collision forecast information for space object B.

[0104] The forecast error includes either the basis of the forecast error or the verification results of the forecast error, or both.

[0105] The space information recorder also has a means for outputting a danger alert to an insurance company and a management company that implement a space insurance program that pays insurance claims from insurance premiums collected in advance in the event of a collision between space object A and space object B among multiple space objects.

[0106] The space information recorder also has a means for outputting orbital performance information to an insurance company and a management company that implement a space insurance program that pays insurance claims from insurance premiums collected in advance in the event of a collision between space object A and space object B among multiple space objects.

[0107] The space information recorder also has a means for outputting a danger alert to a debris collection operator who collects debris resulting from a collision between space objects A and B among the multiple space objects, indicating that multiple space objects with dangerous positional relationships exist at the same time.

[0108] The space information recorder also executes a collision avoidance support program that identifies the presence of a potential hazardous object based on orbit forecast information before a collision occurs between multiple space objects, outputs a danger alert, and determines which space objects should undergo avoidance operations. The space information recorder executes the collision avoidance support program, which includes a danger alert output means that determines whether or not a potential hazardous object exists among the multiple space objects based on the orbit forecast information, and outputs a danger alert if it is determined that a potential hazardous object exists. The space information recorder also executes the collision avoidance support program, which includes an avoidable space object determination means that determines which space objects included in the potential hazardous objects should undergo avoidance operations after the danger alert is output.

[0109] The space information recorder also has a disclosure threshold for determining whether or not to disclose orbital forecast information to different management business devices when it is predicted that multiple space objects will approach each other at a specific time, and an information disclosure means for determining whether or not to disclose the information.

[0110] <Variation 2> In this embodiment, the functions of the collision avoidance assistance device 100 are realized by software. As a modification, the functions of the collision avoidance assistance device 100 may be realized by hardware.

[0111] FIG. 20 is a diagram showing the configuration of a collision avoidance assistance device 100 according to a modified example of this embodiment. The collision avoidance assistance device 100 includes an electronic circuit in place of the processor 910 . The electronic circuit is a dedicated electronic circuit that realizes the functions of the collision avoidance assistance device 100 . The electronic circuit may be a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array. The functions of the collision avoidance assist device 100 may be realized by one electronic circuit, or may be realized by distributing the functions across multiple electronic circuits. As another modification, some of the functions of the collision avoidance assist device 100 may be realized by electronic circuits, and the remaining functions may be realized by software.

[0112] Each of the processor and the electronic circuit is also called a processing circuitry. That is, the functions of the collision avoidance assistance device 100 are realized by the processing circuitry.

[0113] Embodiment 2 In this embodiment, the differences from embodiment 1 will be mainly described. Note that the same components as those in embodiment 1 are given the same reference numerals, and the description thereof may be omitted.

[0114] In this embodiment, we will describe a collision avoidance support device 100a that appropriately determines which space object among the predicted hazard objects 65 should take evasive action when a danger warning 25 is issued based on orbit forecast information 51.

[0115] ***Configuration Description*** FIG. 21 is a configuration diagram of a collision avoidance assistance device 100a of a collision avoidance assistance system 500 according to this embodiment. Collision avoidance assistance device 100a according to this embodiment includes an avoidance decision unit 150 and a machine learning unit 160 in addition to the functional elements of collision avoidance assistance device 100 according to embodiment 1. The other functional elements and hardware configuration are the same as those of embodiment 1. Furthermore, the collision avoidance assistance program according to this embodiment is a program that realizes at least the functions of warning control unit 120, avoidance decision unit 150, and machine learning unit 160. In other words, the collision avoidance assistance program according to this embodiment causes a computer to execute at least warning control processing, avoidance decision processing, and machine learning processing.

[0116] The warning control unit 120 determines, based on the orbit forecast information 51, whether or not there are multiple space objects among the multiple space objects whose positional relationship is dangerous at the same time as the potential hazard objects 65. If it is determined that the potential hazard objects 65 exist, the warning control unit 120 outputs a danger warning 25 indicating the presence of the potential hazard objects 65. The method of outputting the danger warning 25 by the warning control unit 120 is the same as that described in the first embodiment.

[0117] When a danger alert 25 is output, the avoidance determination unit 150 determines an avoidable space object 69, which is a space object for which avoidance operations are to be performed, from among the space objects included in the anticipated danger objects 65. The conditions used to determine the avoidable space object 69 are, for example, as follows: The avoidance determination unit 150 determines the space object to be avoided 69 based on whether each space object included in the anticipated danger object 65 is a rocket at launch or not. The avoidance determination unit 150 determines the space object 69 to be avoided based on whether each space object included in the predicted danger object 65 belongs to a megaconstellation. The avoidance determination unit 150 determines the space object to be avoided 69 based on whether each space object included in the anticipated danger object 65 is in a normal operating state or an unnormal operating state. The avoidance determination unit 150 determines the space object to be avoided 69 based on whether each space object included in the predicted danger object 65 is an orbital transfer satellite currently undergoing orbital transfer. The avoidance determination unit 150 determines the space object to be avoided 69 based on whether each space object included in the anticipated danger object 65 has a collision avoidance function. The avoidance determination unit 150 determines the space object to be avoided 69 based on whether each space object included in the anticipated danger object 65 is located in a dense orbit.

[0118] The avoidance determination unit 150 determines the space object to be avoided 69 from the anticipated danger object 65 using any one of the above conditions or a combination of multiple conditions.

[0119] The machine learning unit 160 updates the algorithm of the avoidance determination process that determines the space object 69 to be avoided by machine learning using the result of determining the space object 69 to be avoided, i.e., the result of determination by the avoidance determination unit 150.

[0120] ***Explanation of Operation*** The collision avoidance assistance process performed by the collision avoidance assistance device 100a according to this embodiment will be described with reference to FIGS. Here, it is assumed that there are space objects A and B as potential danger objects 65, which are multiple space objects whose positional relationship is dangerous at the same time.

[0121] <Avoidance decision processing> 22 and 23 are flow charts showing an example of an avoidance decision process based on a condition such as whether or not a space object is a rocket according to this embodiment. Figures 22 and 23 show an example of a process for determining an avoidable space object 69 based on conditions such as whether the space object is a rocket, whether the space object is a satellite belonging to a megaconstellation, and whether the space object is debris.

[0122] In step S101, the avoidance decision unit 150 determines whether or not the space object A is an artificial satellite. Specifically, the avoidance decision unit 150 determines whether or not the space object is an artificial satellite using the space object ID 511 of the orbit forecast information 51 shown in FIG. 11. For example, the collision avoidance assistance device 100 may have a management table that associates the space object ID with the type of space object. The avoidance decision unit 150 may use the space object ID to obtain the type of space object from the management table and determine whether or not the space object is an artificial satellite. If space object A is an artificial satellite, in step S102, avoidance determination unit 150 determines whether space object B is an artificial satellite or not. If space object A and space object B are both artificial satellites (YES in step S102), proceed to at least one of M1 to M4.

[0123] If space object B is not a satellite, in step S103, it is determined whether space object B is a rocket. Specifically, avoidance decision unit 150 determines whether the space object is a rocket using space object ID 511 of orbit forecast information 51 shown in FIG. 11. For example, collision avoidance assistance device 100 may have a management table that associates space object IDs with space object types. Avoidance decision unit 150 may use the space object ID to obtain the type of space object from the management table and determine whether the space object is a rocket. If space object A is an artificial satellite and space object B is a rocket (step S104), in step S105, the avoidance determination unit 150 determines whether or not space object A belongs to a megaconstellation. If space object A is not a satellite and space object B is not a rocket, ie, it is debris (step S104a), the process proceeds to step S106. In step S105, if space object A belongs to a megaconstellation, the process proceeds to step S106. In step S105, if space object A does not belong to a megaconstellation, the process proceeds to step S111.

[0124] If it is determined in step S101 that the space object A is not a satellite, then in step S107 the avoidance determination unit 150 determines whether or not the space object A is a rocket. If space object A is determined to be a rocket in step S107, then in step S108, the avoidance determination unit 150 determines whether space object B is an artificial satellite. If space object A is a rocket and space object B is an artificial satellite (step S109), in step S110, avoidance determination unit 150 determines whether space object B belongs to a megaconstellation. If, in step S110, space object B does not belong to a megaconstellation, processing proceeds to step S106. In step S110, if space object B belongs to a megaconstellation, the process proceeds to step S111.

[0125] If it is determined in step S108 that the space object B is not a satellite, then in step S112 the avoidance determination unit 150 determines whether or not the space object B is a rocket. In step S112, if space object B is a rocket, both space objects A and B are rockets. In this case, in step S113, the avoidance determination unit 150 excludes the anticipated danger object 65 from application of the avoidance determination process. In step S112, if space object B is not a rocket, that is, if space object B is debris, space object A is a rocket and space object B is debris (step S114). In this case, the process proceeds to step S106.

[0126] In step S106, the avoidance determination unit 150 determines space object A, among the space objects included in the anticipated danger objects 65, as the avoidance space object 69 that should be avoided. In step S111, the avoidance determination unit 150 determines space object B, among the space objects included in the anticipated danger objects 65, as the avoidance space object 69 that should be avoided.

[0127] If it is determined in step S107 that the space object A is not a rocket, then in step S115 the avoidance decision unit 150 determines whether the space object A is debris or not. If space object A is debris in step S115, then in step S116, the avoidance decision unit 150 determines whether space object B is an artificial satellite. In step S116, if space object B is an artificial satellite, space object A is debris and space object B is an artificial satellite (step S117). In this case, the process proceeds to step S111.

[0128] If it is determined in step S115 that the space object A is not debris, then in step S121 the avoidance determination unit 150 performs a learning process for the object definition and an update process for the algorithm.

[0129] If it is determined in step S116 that the space object B is not a satellite, it is determined in step S118 whether or not the space object B is a rocket. In step S118, if space object B is a rocket, space object A is debris and space object B is the rocket (step S120). In this case, the process proceeds to step S111. In step S118, if space object B is not a rocket, both space objects A and B become debris. In this case, in step S119, the avoidance decision unit 150 excludes the anticipated danger object 65 from application of the avoidance decision process.

[0130] FIG. 24 is a flow diagram of the avoidance decision process based on the condition of whether or not the space object is in normal operation according to this embodiment. Figure 24 shows an example of a process for determining a space object 69 to be avoided depending on whether the space object is in normal or non-normal operation. The process in Figure 24 is referred to as M1 process. The normal operation state is specifically a state in which a satellite is flying in orbit in normal operation. The non-normal operation state includes a launch transient state from the launch of each of the multiple space objects until they are injected into orbit, and a post-departure transient state from the de-orbit of each of the multiple space objects until they enter the atmosphere or are injected into a disposal orbit.

[0131] In step S201, the avoidance decision unit 150 determines whether the space object A is in a normal operating state or an unnormal operating state. Specifically, the avoidance decision unit 150 determines whether the space object A is in a normal operating state or an unnormal operating state using the predicted flight state 515 of the orbit forecast information 51 shown in FIG. 11 . If space object A is in a normal operating state in step S201, then in step S202 the avoidance decision unit 150 determines whether space object B is in a normal operating state or an unnormal operating state. In step S202, if space object B is in a normal operating state, both space object A and space object B are in a normal operating state. In this case, in step S203, the avoidance decision unit 150 determines that space object A and space object B will not collide.

[0132] If space object A is in an unsteady operating state in step S201, then in step S205 the avoidance decision unit 150 determines whether space object B is in a steady operating state or an unsteady operating state. In step S205, if space object B is in a normal operating state, space object A is in an unsteady operating state, and space object B is in a normal operating state. In this case, in step S206, the avoidance determination unit 150 determines that space object A, which is in an unsteady operating state, is an avoidance space object 69 that should be subjected to avoidance operation. In step S205, if space object B is in an unsteady operating state, both space objects A and B are in unsteady operating states. In this case, in step S207, the avoidance determination unit 150 does not determine the avoiding space object 69, since this is a case where individual adjustment is performed.

[0133] In step S202, if space object B is in an unsteady operating state, space object A is in a steady operating state and space object B is in an unsteady operating state. In this case, in step S204, the avoidance determination unit 150 determines that space object B, which is in an unsteady operating state, is an avoidance space object 69 that should be subjected to avoidance operation.

[0134] FIG. 25 is a flow diagram of an avoidance decision process based on a condition such as whether or not a space object belongs to a megaconstellation according to this embodiment. 25 shows an example of a process for determining a space object 69 to be avoided based on the condition of whether or not the space object belongs to a megaconstellation. The process in FIG. 25 is referred to as M2 process.

[0135] In step S301, the avoidance decision unit 150 determines whether or not the space object A belongs to a megaconstellation. Specifically, the avoidance decision unit 150 determines whether or not the space object A belongs to a megaconstellation using the space object ID 511 of the orbit forecast information 51 shown in FIG. 11. For example, the collision avoidance assistance device 100 may have a management table that associates the space object ID with the management operator of the space object. The avoidance decision unit 150 may use the space object ID to obtain the management operator of the space object from the management table and determine whether or not the space object belongs to a megaconstellation. If space object A belongs to a megaconstellation in step S301, then in step S302 the avoidance decision unit 150 determines whether space object B belongs to a megaconstellation. In step S302, if space object B belongs to the megaconstellation, both space object A and space object B belong to the megaconstellation. In this case, in step S303, avoidance decision unit 150 determines that space object A and space object B will not collide.

[0136] If space object A does not belong to a megaconstellation in step S301, then in step S305, the avoidance decision unit 150 determines whether space object B belongs to a megaconstellation. In step S305, if space object B belongs to a megaconstellation, space object A does not belong to a megaconstellation and space object B belongs to a megaconstellation. In this case, in step S306, the avoidance determination unit 150 determines that space object B belonging to the megaconstellation is an avoidance space object 69 that should be avoided. In step S305, if space object B does not belong to the megaconstellation, then neither space object A nor space object B belongs to the megaconstellation. In this case, in step S307, the avoidance determination unit 150 does not determine the avoidance space object 69, since this is a case where individual adjustment is performed.

[0137] In step S302, if space object B does not belong to the megaconstellation, space object A belongs to the megaconstellation and space object B does not belong to the megaconstellation. In this case, in step S304, the avoidance determination unit 150 determines that space object A belonging to the megaconstellation is an avoidance space object 69 that should be avoided.

[0138] FIG. 26 is a flow diagram of the avoidance decision process according to this embodiment based on the condition of whether or not the space object is an orbital transfer satellite. 26 shows an example of a process for determining a space object 69 to be avoided based on a condition such as whether the space object is an orbital transfer satellite currently transferring orbit. The process in FIG. 26 is referred to as M3 process.

[0139] In step S401, the avoidance decision unit 150 determines whether or not the space object A is an orbital transfer satellite. Specifically, the avoidance decision unit 150 determines whether or not the space object A is an orbital transfer satellite by using the predicted flight state 515 of the orbit forecast information 51 shown in FIG. If space object A is an orbital transfer satellite in step S401, the avoidance determination unit 150 determines in step S402 whether space object B belongs to a megaconstellation. If it is determined in step S402 that the space object B belongs to a megaconstellation, then in step S403 the avoidance determination unit 150 determines that the space object B belonging to the megaconstellation is an avoidance space object 69 that should be subjected to avoidance operations.

[0140] If space object A is not an orbital transfer satellite in step S401, the avoidance determination unit 150 determines in step S404 whether space object B belongs to a megaconstellation. If it is determined in step S404 that the space object B belongs to a megaconstellation, then in step S405 the avoidance determination unit 150 determines whether or not the space object B is an orbital transfer satellite. In step S405, if space object B is an orbital transfer satellite, space object A is not an orbital transfer satellite, and space object B is an orbital transfer satellite belonging to a megaconstellation. In this case, in step S406, the avoidance determination unit 150 determines that space object A is an avoidance space object 69 that should be avoided.

[0141] In step S402, if space object B does not belong to the megaconstellation, space object A is an orbital transfer satellite and space object B does not belong to the megaconstellation. In this case, in step S407, the avoidance determination unit 150 does not determine the avoidance space object 69 because this is a case where individual adjustment is performed.

[0142] In step S404, if space object B does not belong to the megaconstellation, space object A is not an orbital transfer satellite, and space object B does not belong to the megaconstellation. In this case, in step S407, the avoidance determination unit 150 does not determine the avoidance space object 69 because this is a case where individual adjustment is performed.

[0143] In step S405, space object B belongs to a megaconstellation but is not an orbital transfer satellite, and space object A is not an orbital transfer satellite. In this case, in step S407, the avoidance determination unit 150 does not determine an avoidance space object 69 because this is a case where individual adjustment is performed.

[0144] FIG. 27 is a flow diagram of the avoidance decision process according to this embodiment, which is based on the condition of whether or not the space object has a collision avoidance function. 27 shows an example of a process for determining an avoidable space object 69 based on the condition of whether or not the space object has a collision avoidance function while transitioning its orbit. The process in FIG. 27 is referred to as M4 process.

[0145] In step S501, the avoidance determination unit 150 determines whether or not the space object A has a collision avoidance function. Specifically, the avoidance determination unit 150 determines whether or not the space object A has a collision avoidance function using the space object ID 511 of the orbit forecast information 51 shown in FIG. 11. For example, the collision avoidance assistance device 100 may have a management table that associates the space object ID with the function of the space object. The avoidance determination unit 150 may use the space object ID to obtain the function of the space object from the management table and determine whether or not the space object has a collision avoidance function.

[0146] In step S501, if space object A has a collision avoidance function, in step S502, the avoidance determination unit 150 determines whether space object B has a collision avoidance function. If it is determined in step S502 that space object B has a collision avoidance function, then in step S503, the avoidance determination unit 150 determines whether space object A will enter a dense orbit. Specifically, the avoidance determination unit 150 determines whether the space object has a collision avoidance function using the predicted flight state 515 of the orbit forecast information 51 shown in Figure 11.

[0147] In step S503, if space object A enters the dense orbit, the space object A has a collision avoidance function and enters the dense orbit. Therefore, in step S504, the avoidance determination unit 150 determines that the space object A, which has a collision avoidance function and enters the dense orbit, is an avoidance space object 69 that should be operated to avoid the collision.

[0148] If it is determined in step S501 that space object A does not have a collision avoidance function, then in step S505, the avoidance determination unit 150 determines whether or not space object B has a collision avoidance function. If it is determined in step S505 that the space object B has a collision avoidance function, then in step S506 the avoidance determination unit 150 determines whether the space object B is in regular operation on a dense orbit. If the space object B is not in normal operation in a dense orbit in step S506, the avoidance determination unit 150 determines in step S507 that the space object B having a collision avoidance function is an avoidance space object 69 that should be subjected to avoidance operation.

[0149] In step S502, if space object B does not have a collision avoidance function, the process proceeds to step S506. Also, in step S503, if space object A does not enter a dense orbit, the process proceeds to step S507.

[0150] If it is determined in step S505 that space object B does not have a collision avoidance function, then in step S509, the avoidance determination unit 150 determines whether or not to request removal from the debris removal business. If a request for removal is not made to the debris removal business in step S509, the avoidance determination unit 150 determines to leave it alone in step S510 and does not determine the space object 69 to be avoided. In step S509, if a removal request is made to a debris removal business, in step S508 the avoidance determination unit 150 does not determine an avoidable space object 69 because individual adjustment is required. In step S506, if space object B is in normal operation in a dense orbit, the process proceeds to step S508.

[0151] The avoidance determination unit 150 outputs an avoidance object notification 403 notifying the avoidance space object 69. Specifically, when the avoidance space object 69 is determined, the avoidance determination unit 150 outputs an avoidance object notification 403 notifying the avoidance space object 69. In addition, the avoidance determination unit 150 may transmit the avoidance object notification 403 to the management business device 40 of the management business corresponding to the avoidance space object 69. In addition, when the space object 69 to be avoided is not determined due to individual adjustment or determination that it is not applicable, the avoidance determination unit 150 may output the object to be avoided notification 403 including a message that the space object 69 to be avoided has not been determined.

[0152] FIG. 28 is an example of a summary of the avoidance decision process according to this embodiment. The basis for the exemplary avoidance decision process shown in Figures 22-27 is to determine an appropriate avoidance space object 69 while overcoming the following possibilities: - Collisions occurring in mega-constellations pose a risk of chain reactions. Areas such as near LEO sun-synchronous LST 10:30 or the polar regions are areas where many satellites from multiple operators are concentrated, and there is a risk of a chain reaction if a collision occurs. High-precision orbital information from megaconstellations is held by megaconstellation operators and may not be made public as forecast values. Rocket launch operators and operators transferring geostationary satellites from the perigee of the geostationary transfer orbit (GTO) to geostationary orbit are at risk of collision with megaconstellations, but they are not necessarily able to arbitrarily choose the timing of their passage through the danger zone. If multiple operators of a densely packed track take evasive action without coordinating with each other, there is a risk of collision at the destination. -Dense orbits may contain satellites that do not have the capability to avoid collisions.

[0153] <Machine learning processing> Next, a machine learning process in which the machine learning unit 160 updates the algorithm of the avoidance decision unit 150 through machine learning using the decision results of the avoidance decision unit 150 will be described.

[0154] A specific example of the machine learning process by the machine learning unit 160 is as follows. If the results of the M1 process to the M4 process are the same, the machine learning unit 160 confirms the algorithm. If the processing results of the M1 process to the M4 process are inconsistent, the machine learning unit 160 adjusts them individually.

[0155] FIG. 29 shows an example of input information in the machine learning process according to this embodiment. The machine learning unit 160 performs AI machine learning to optimize the execution order of M1 processing to M4 processing, add new judgment criteria, and create a judgment process that should be added when modifying the flowchart in the future, depending on the content of individual adjustments that will occur in the future, the judgment process, and the judgment results. Perform processes such as optimizing the flow of flowcharts.

[0156] <Evasive Maneuver Processing by Satellite Constellation Formation System> Here, the satellite constellation forming system 600 will be described when it receives the object to be avoided notification 403 output from the collision avoidance support device 100a. The satellite constellation forming system 600 forms, for example, a mega-constellation. The satellite constellation forming system 600 performs an avoidance action for the avoidance space object 69 when the avoidance space object 69 is a satellite included in the mega-constellation based on the avoidance object notification 403 output from the collision avoidance assistance device 100a. 5, 7, and 8 generates an orbital maneuver command 55 for a satellite notified as an avoidable space object 69 to perform an avoidance action. Then, the satellite constellation forming unit transmits the orbital maneuver command 55 to the satellite.

[0157] Here, an example of an algorithm when a collision warning or approach warning is issued for a mega-constellation is shown below: For example, this is an algorithm of a satellite constellation formation unit that generates an orbital maneuver command. Set the following information as input conditions. - Whether or not the constellation is passing through the orbital altitude during operation - Incidence angle relative to the orbital altitude Information on the other party in a collision or approach By setting the above information as input conditions, the system outputs the judgment results of whether or not avoidance action should be taken based on the following judgment criteria, and the entity that should take the avoidance action.

[0158] The basis for determining individual items is as follows: It is predicted that a huge number of warnings will be issued in mega-constellations, and it will be difficult to take evasive action in response to all warnings. -If some satellites in a megaconstellation take evasive action, there is a risk of them colliding with other satellites. - It is necessary to compare the risks of taking evasive action with the risks of not taking evasive action and decide whether or not to take evasive action. - Only mega-constellation operators have high-precision orbital information forecast values, and if they are kept secret, only mega-constellation operators can perform highly accurate collision prediction analysis. Mega-constellation operators must share the results of their risk analysis and their policy on whether or not to take evasive action with stakeholders who are subject to collisions. -The algorithm may overturn the initial decision and make an alternative suggestion.

[0159] 48 and 49 are flow charts showing the process of updating the collision avoidance algorithm based on the machine learning effect according to this embodiment. The collision avoidance support device 100a updates the collision avoidance algorithm through machine learning effects.

[0160] Until the process is established, coordination between stakeholders will be necessary, and so the algorithm implemented in the computer will be part of this. Machine learning will be used to determine the content of future coordination of response policies between stakeholders, as well as the decision-making process and results, and to create a decision-making process that should be added when modifying the flowchart in the future. Machine learning will be used to optimize the execution order of processes M1 to M4, add new decision criteria, and optimize the flow of the flowchart.

[0161] In a situation where mega-constellation operators are faced with an overwhelming number of collision warnings issued daily, they may conclude that they will not take evasive action even if there is a risk of collision. From the perspective of the opposing party in the collision, the mega-constellation operator may also be adamant that evasive action should be taken. In this case, it is highly likely that a decision will be reached by reconciling opinions through a consensus system on each occasion. By accumulating many examples of the results of reconciling such conflicting opinions, new patterns may emerge in the decision-making process leading to a conclusion. By learning new patterns of such decision-making processes through machine learning, it is possible to modify or add to the processing flow.

[0162] In this embodiment, the collision avoidance assistance program that realizes the following functions has been described. The collision avoidance support program causes a computer to execute a danger warning output process that identifies the presence of a potential hazardous object based on orbital forecast information and outputs a danger warning before a collision occurs between multiple space objects. The danger warning output process outputs a danger warning to an insurance company of a space insurance program that pays insurance money from insurance premiums collected in advance in the event of a collision between space objects A and B among the multiple space objects, and to a space object management company that manages at least one of the multiple space objects.

[0163] The collision avoidance assistance device includes a space information recorder that includes orbital forecast information. The danger warning output process determines whether or not a potential dangerous object exists based on the orbit forecast information provided by the space information recorder, and outputs a danger warning if it is determined that a potential dangerous object exists.

[0164] The collision avoidance assistance program causes the computer to execute a space object to be avoided determination process when a danger alert is output. The space object to be avoided determination process determines a space object to be avoided from among the space objects included in the predicted danger objects based on the orbital forecast information provided by the space information recorder.

[0165] ***Explanation of the effect of this embodiment*** The collision avoidance assistance device according to this embodiment can request and assist in avoidance actions by presenting the grounds and results for identifying the space objects for which avoidance actions should be taken to the respective jurisdiction holders of multiple space objects that are predicted to be dangerous. Therefore, the collision avoidance assistance device according to this embodiment has the effect of being able to appropriately avoid collisions with space objects.

[0166] ***Other Configurations*** <Modification> The collision avoidance assistance system acquires space object information from a space information recorder that records space object information acquired from a management business device used by a management business that manages multiple space objects, and assists in avoiding collisions between the multiple space objects. The collision avoidance assistance system according to this embodiment may include a database for storing space object information acquired by the space information recorder, and a server equipped with avoidance operator determination means for determining a collision avoidance operator who will carry out collision avoidance. The server realizes the following steps (also referred to as means or units) using processing circuitry such as a processor or electronic circuit. Specifically, the database may be a memory, an auxiliary storage device, or a file server. Specifically, the server is a collision avoidance assistance device. Also, a specific example of the avoidance operator determination means is an avoidance determination unit. The database may be provided in the server, or may be a device separate from the server.

[0167] The server comprises the following stages: The stage where a notification is received from the space information recorder that a collision between space object A and space object B, which are included in multiple space objects, has been predicted. A step of obtaining the estimated time or time period when the collision is predicted, the orbital forecast information for space object A, and the orbital forecast information for space object B from the space information recorder. A stage of issuing a danger alert, such as a collision alert or approach alert, at the estimated time or time period to all or some of the operators of space object A, the operators of space object B, and the debris removal operators. - The stage of selecting a collision avoidance company. The stage of requesting collision avoidance actions from the selected collision avoidance business.

[0168] The space object information includes information indicating whether or not the space object has a collision avoidance function. When either space object A or space object B is equipped with a collision avoidance function, the avoidance operator determination means selects a management operator that manages the space object equipped with the collision avoidance function as the collision avoidance operator. In addition, when both space object A and space object B are equipped with a collision avoidance function, the avoidance operator determination means selects a collision avoidance operator using as an evaluation index whether the space object is a regular operation object or a non-regular space object. In addition, when both space object A and space object B have collision avoidance functions, the avoidance operator determination means selects a collision avoidance operator using whether or not the space object is a mega-constellation satellite as an evaluation index for selection. Furthermore, the avoidance operator determination means selects a debris removal operator as the collision avoidance operator when neither space object A nor space object B is equipped with a collision avoidance function.

[0169] The space object information includes a history of past space collision incidents. The collision avoidance operator determination means adds evaluation indicators used in the process of determining collision avoidance operators in past space collision accidents to the evaluation indicators for selection, and selects a collision avoidance operator.

[0170] The space information recorder includes trajectory forecast information and trajectory performance information indicating the performance values ​​of the flight of the space object. The server includes a step of reporting a danger alert, such as a collision alert or an approach alert, to a space insurance company that applies an insurance payment system that assesses accident liability and insurance claims according to the difference between the orbit forecast information and the orbit performance information. This has the effect of encouraging stakeholders to make efforts to reduce accident liability and avoid collisions.

[0171] The database acquires from the space information recorder the scheduled launch time and launch forecast information of space object C, which are acquired from the rocket launch operator by the space information recorder. The server comprises the following stages: A step in which the launch forecast information for the scheduled launch time information is reported to the mega-constellation operator that manages the mega-constellation satellites that are at risk of collision with space object C. A step in which the avoidance operator determination means requests the mega-constellation operator to take collision avoidance action or to provide information necessary for collision avoidance during the rocket launch. A step of notifying the launch vehicle operator of space object information of the mega-constellation satellite that is at risk of collision with space object C.

[0172] The database acquires from the space information recorder the scheduled time of orbital transfer of space object D and transfer forecast information obtained from the orbital transfer satellite operator by the space information recorder. The server comprises the following stages: A step of reporting the transfer forecast information at the scheduled time of the orbital transfer to the mega-constellation operator that manages the mega-constellation satellites that are at risk of collision with space object D. The avoidance operator determination means requests the mega-constellation operator to take collision avoidance action or to provide information necessary for collision avoidance during orbital transfer. The stage of reporting space object information of mega-constellation satellites that are at risk of collision with space object D to the orbital transfer satellite operator.

[0173] The database acquires from the space information recorder the scheduled de-orbit time and de-orbit forecast information for space object E, which are acquired from the satellite operator that will de-orbit using the space information recorder or the debris recovery operator. The server comprises the following stages: A step of reporting the de-orbit forecast information at the scheduled de-orbit time to the mega-constellation operator that manages the mega-constellation satellites that are at risk of collision with space object E. The avoidance operator determination means requests the mega-constellation operators to take collision avoidance actions or to provide information necessary for collision avoidance during de-orbiting. The stage where space object information of mega-constellation satellites that are at risk of collision with space object E is reported to the satellite operator that will deorbit them or to the debris collection operator.

[0174] The server includes a step of reporting launch forecast information to a space insurance company that operates an insurance payment system that allows contracts to be made when a collision risk during a rocket launch is predicted. The server also includes a step of reporting the transition forecast information to a space insurance company that operates an insurance payment system that allows contracts to be made when a collision risk during orbital transfer is predicted. The server also includes a step of reporting the de-orbit forecast information to a space insurance company that operates an insurance payment system that allows insurance contracts to be made when a collision risk is predicted during de-orbit of a space object. This will encourage stakeholders to make efforts to reduce accident liability and help avoid collisions.

[0175] The server also provides the launch time information that can ensure flight safety during rocket launch. The server also includes a step of providing the transfer forecast information (transfer time information) that can ensure flight safety during orbital transfer. The server also includes a step of providing the de-orbit forecast information (de-orbit time information) that can ensure flight safety during de-orbit.

[0176] Embodiment 3 In this embodiment, the differences from embodiments 1 and 2 will be mainly described. Note that the same components as those in embodiments 1 and 2 are denoted by the same reference numerals, and the description thereof may be omitted.

[0177] In this embodiment, a space insurance support system 550 and a space insurance support device 200 that support the operation of space insurance that compensates for damages caused by collisions between multiple space objects flying in space will be described.

[0178] ***Configuration Description*** FIG. 30 is a configuration diagram of a space insurance support system 550 and a space insurance support device 200 according to this embodiment. The space insurance support device 200 includes, as functional elements, a responsibility assessment unit 210, an insurance premium assessment unit 220, and a storage unit 230. The storage unit 230 stores the space information recorder 50 and the warning issuance information 141.

[0179] The functions of the liability assessment unit 210 and the insurance premium assessment unit 220 are realized by software. The storage unit 230 is provided in the memory 921. Alternatively, the storage unit 230 may be provided in the auxiliary storage device 922. Moreover, the storage unit 230 may be provided separately in the memory 921 and the auxiliary storage device 922.

[0180] The hardware configuration of the space insurance support device 200 is the same as that of the collision avoidance support device 100 of embodiment 1. The space insurance support program according to this embodiment is a program that realizes the functions of the liability assessment unit 210 and the insurance premium assessment unit 220. That is, the space insurance support program according to this embodiment causes a computer to execute a liability assessment process and an insurance premium assessment process.

[0181] ***Explanation of Operation*** The space insurance support process performed by the space insurance support device 200 according to this embodiment will be described with reference to FIG.

[0182] <Space Insurance Support Processing: S200> In step S21, the responsibility assessment unit 210 assesses accident liability and liability for damages in the event that two potential hazardous objects 65 collide with each other when a danger warning 25 generated based on the trajectory forecast information 51 has not been issued. The responsibility assessment unit 210 assesses accident liability and liability for damages based on the predicted trajectory values ​​of each potential hazardous object 65 and the actual trajectory values ​​of each potential hazardous object 65. Specifically, the responsibility assessment unit 210 assesses the accident liability and damages liability of the management company that owns each of the space objects of the predicted hazardous objects 65. The responsibility assessment unit 210 assesses the accident liability and damages liability based on the space information recorder 50 that includes orbit forecast information 51 and orbit performance information 52 in which orbit performance values ​​are set.

[0183] In step S22, the insurance premium assessment unit 220 assesses the insurance premiums of the management company that manages each of the multiple space objects based on the forecast error 514. Specifically, the insurance premium assessment unit 220 assesses the insurance premiums of the management company so that the smaller the forecast error 514, the lower the insurance premium rate.

[0184] The order of steps S21 and S22 does not matter, and steps S21 and S22 may be reversed, or steps S21 and S22 may be performed in parallel.

[0185] A specific example of the space insurance support process will be described below.

[0186] <About Space Insurance 201> The space insurance 201 supported by the space insurance support device 200 according to this embodiment is an insurance that determines the responsibility for the occurrence of an accident and the responsibility for compensation for damages based on the orbital performance of a colliding space object, and covers the damages with insurance premiums. In particular, the space insurance 201 is an insurance that determines the responsibility for the occurrence of an accident and the responsibility for compensation for damages, and covers the damages with insurance premiums, when a collision accident occurs even though the predicted values ​​of the orbits of space objects are made public as orbital forecast information 51 and it is possible to foresee that a collision will not occur.

[0187] FIG. 32 is a diagram showing an example of information disclosure by a management company and an example of space insurance corresponding to the management company. As stakeholders in space business, management operators can be broadly divided into satellite operators and rocket operators. Mega-constellation operators deploy satellites across the entire sky. Some mega-constellation operators plan to deploy hundreds to thousands of satellites at altitudes of 1,000 km or more, while others plan to deploy a few satellites at orbital altitudes of around 300 to 600 km. There are also LEO constellation operators that operate multiple Earth observation satellites in specific low-earth orbit planes, satellite operators that operate commercial operations with single satellites, and debris collection operators that aim to collect debris are also expected to appear. Space objects owned by these operators are at risk of collision with each other. This risk is particularly high during non-routine operations, such as during orbit insertion or deorbit after the mission is completed. Furthermore, operators who launch geostationary satellites into geostationary orbits must use their own propulsion systems to transfer their satellites to geostationary orbit after launch, which means there is a risk of collision with satellites in other orbits during this process.

[0188] These operators could publish the time and orbital information forecasts they hold in advance, which would be an effective collision avoidance measure. On the other hand, if a collision does occur, it would be effective to clarify the occurrence of the accident and liability for damages if they could use the actual orbital ephemeris performance against the forecast to show evidence that one of the two vehicles deviated from the forecast and collided with an object that was operating according to the initial forecast. Space insurance premiums would be an effective way to cover the costs of damages.

[0189] <About Space Information Recorder 50> In the space insurance 201, the space information recorder 50 containing orbit forecast information 51, which is public information about the time and predicted values ​​of orbit information of a space object, and orbit performance information 52, is used as evidence for the application of the space insurance.

[0190] For the purpose of investigating aircraft accidents, aircraft are equipped with voice recorders, and for the purpose of investigating car accidents and as evidence, cars are equipped with dashcams. Satellite constellations with thousands of satellites built in low orbits at altitudes of around 600 km or less are at high risk of collision when new rockets are launched. For this reason, it is thought that "space information recorders," which could be called satellite drive recorders, will be needed, as they serve a purpose similar to voice recorders and drive recorders.

[0191] The difference between aircraft accidents and satellite collisions is that in aircraft accidents, even if the accident involves an explosion, there is a possibility that onboard equipment can be recovered after the accident, so voice recorders are designed to be robust enough to withstand an explosion. Furthermore, since aircraft have pilots, they record not only instrument information but also the pilot's voice, leaving a voice record that can be verified after the accident, including whether or not there were any abnormalities in the instruments. In contrast, in a satellite collision, onboard equipment is scattered into space after the accident and is difficult to recover, and there is no pilot. For this reason, voice recording is unnecessary; the main purpose is to record data from onboard instruments, and after acquisition, the data must be quickly transmitted to the ground or another satellite, and the data up to just before the collision must be stored in a separate location.

[0192] The difference between car accidents and satellite collisions is that car dashcams are primarily intended to record the vehicle's operating conditions and surrounding circumstances at the time of the accident in order to verify or provide evidence of responsibility for the accident. If a head-on collision occurs, recording the accident location information makes it possible to verify the lane in which the accident occurred and clarify responsibility for the accident. However, dashcams are not intended to transmit their own future forecast information in advance. Furthermore, because the concept of driver negligence exists, dashcams are highly effective in clarifying responsibility and as evidence for damage compensation. In contrast, with satellite collisions, there is currently no concept equivalent to lanes, and there are no drivers, so negligence responsibility for satellite collisions cannot be held, and the concept of perpetrator and victim has also not existed.

[0193] At present, there are no established international rules regarding who is responsible and who will be liable for damages in the event of a collision. However, as a means of avoiding future collisions, it would be reasonable for stakeholders involved in space objects to share orbital forecasts of space objects in advance and to take avoidance measures if a collision risk is foreseen. An effective avoidance measure would be for one of the parties foreseeing a collision to take evasive action, and if both parties take evasive action, mutual cooperation is essential. The risk of a collision should be avoided as a result of both parties carrying out autonomous collision avoidance operations. It is also important to avoid the risk of a collision with another satellite if collision avoidance operations are carried out. If a collision occurs despite measures to avoid it, it is important to determine whether the cause was a deviation from the predicted orbit published by the satellite. Therefore, the orbit history information from the space data recorder is important as objective evidence.

[0194] 33 and 34 are diagrams showing some specific examples of the insurance premium assessment process and the liability assessment process according to this embodiment.

[0195] <Specific example of insurance premium assessment processing 1> The insurance premium assessment unit 220 assesses the insurance premiums at the management business operator so that the smaller the forecast error 514, the lower the insurance premium rate.

[0196] The predicted orbit of a space object includes time errors and position estimation errors. Since satellites fly at approximately 7 to 10 km per second, the distance increases due to the time error in the satellite's direction of travel. Expressed geometrically, this results in a space on an elliptical cone with the space object at the center, which is called an error bubble. Error range 502 in Figure 15 is an example of an error bubble. Position estimation errors have various causes, such as measurement data such as GPS reception on the satellite itself, or ranging data from ground-based telescopes, and the amount of error varies. Satellite operators usually have highly accurate forecasts and orbital ephemeris records for their own satellites. However, the accuracy of orbital information held by external operators and SSA operators that distribute measurement information from the ground has large errors. When predicting collision risk using orbit forecast values, there is a high possibility that bubbles with large error amounts will come into contact with each other, resulting in a high collision risk. Also, as shown in the top part of Figure 33, the smaller the error amount, the lower the collision risk. Also, the smaller the error amount, the smaller the difference between the orbit forecast value and the actual orbital ephemeris. Furthermore, if the actual orbital ephemeris of an operator with a small estimated error amount deviates from this, the insurance company may be exempt from liability. Therefore, it is reasonable for insurance companies to set lower insurance rates for companies with smaller estimation errors, since they have a lower risk of causing an accident.

[0197] <Specific example of insurance premium assessment processing 2> The insurance premium assessment unit 220 assesses the insurance premium based on the trajectory forecast information 51 and the trajectory performance information 52 including the trajectory performance values ​​of each of the predicted hazardous objects 65 so that the insurance premium rate is lower the smaller the difference between the trajectory forecast value and the trajectory performance value.

[0198] Forecast error 514 is a self-reported value by the management company. Because evaluation standards are used by multiple management companies, other means of objectively evaluating the appropriateness of insurance premium rates are also effective. If the difference between the forecast value and the actual orbital ephemeris is statistically analyzed based on past results, it is possible to objectively evaluate the amount of error contained in the forecast value, which is effective in ensuring fairness in setting insurance premium rates.

[0199] <Specific example of insurance premium assessment processing 3> The insurance premium assessment unit 220 assesses the insurance amount so that the smaller the difference between the predicted orbit value and the actual orbit value, the larger the insurance amount to be paid.

[0200] If a space object collides with a predicted value that posed no risk of collision, there will be a difference between the predicted value and the actual orbital ephemeris. However, it is reasonable to judge that the smaller this difference is, the less responsibility for the collision accident. If it is not possible to determine 100% responsibility between the assailant and the victim, and although both parties bear some responsibility, the possibility of accidental accidents cannot be completely ruled out, and insurance payments are required, it is reasonable to expect that the smaller the difference between the predicted value and the actual orbital ephemeris, the higher the insurance payments will be.

[0201] <Example 1 of responsibility evaluation processing> The liability assessment unit 210 assesses liability for accidents and liability for damages so that the smaller the difference between the predicted orbit value and the actual orbit value, the lower the liability for accidents and liability for damages in the event of a collision. In other words, in the space insurance 201, the smaller the difference between the predicted value of the space information recorder and the actual orbital ephemeris, the lower the basis for determining the lower the liability for accidents and liability for damages in the event of a collision accident.

[0202] It is useful as an objective indicator when it is necessary to clarify accident liability and compensation liability in a situation where international STM rules have not yet been established.

[0203] <Specific example of responsibility evaluation process 2> The liability assessment unit 210 assesses liability for the accident and liability for damages so that an accident that occurred despite being foreseeable based on the predicted values ​​of the trajectory is exempt from liability.

[0204] In addition to the efforts of each operator, it is also effective for SSA operators to issue collision warnings in order to predict collision accidents. An operator who fails to avoid a foreseeable collision is in breach of their duty to ensure safety, and it is reasonable for insurance companies to exempt them from liability. If an operator with a large estimated error in forecast values ​​owns many satellites, collision warnings will be issued frequently, and if no evasive operations are taken, no insurance will be paid in the event of a collision. This system has the effect of encouraging operators to make efforts to improve the accuracy of forecast values, and as a result, it has the effect of reducing collision warnings.

[0205] <Specific example of responsibility evaluation processing 3> The liability assessment unit 210 assesses accident liability and liability for damages in a third-party liability insurance policy with a rocket launch company that conducts rocket launch operations as the insured so that only the parties involved in the collision accident are subject to compensation for damages and higher-level damages are exempt from liability.

[0206] In mega-constellations consisting of several thousand satellites at altitudes below 600 km, it is easy to imagine that debris from a collision accident could collide with other satellites flying in the same orbital plane, at a nearby altitude, or in a nearby orbital plane. Therefore, it cannot be said with certainty that the high-level damage caused by a chain reaction is accidental. Furthermore, there is a risk that the total amount of damage could be unlimited, so it is appropriate to exempt high-level damage from launch third-party liability insurance, and since the total amount of damage would be within a predictable range, it is effective in ensuring the sustainability of the space insurance system.

[0207] Here, we assume a constellation of 2,400 satellites, each with 40 orbital planes at an altitude of approximately 340 km passing through the polar regions, with 60 satellites deployed in each orbital plane. Because all satellites pass through the polar regions, extremely strict timing control is required for all satellites to avoid collisions in a time-sharing manner. At an altitude of 340 km, a satellite orbits approximately 15.7 times, taking approximately 90 minutes per orbit. The satellite speed is approximately 7.7 km / sec. The distance between satellites in one orbital plane is approximately 700 km, meaning a waiting time of approximately 90 seconds between the passing of a satellite in a particular orbital plane and its return. To allow 40 satellites to pass within this time frame requires a 90-second / 40-plane ratio of approximately 2 seconds. This represents an extremely stringent control requirement given the technological level of satellite development, and there is ample opportunity for collisions due to unforeseen orbital malfunctions caused by error factors.

[0208] The above is an example of a polar orbit, i.e., an orbital inclination of 90 degrees, and in reality, concentration in the polar regions can be avoided by setting the orbital inclination to a value other than 90 degrees. However, if the orbital inclination is, for example, around 50 degrees, there will be many intersections between orbital planes not only at high latitudes but also at mid-latitudes, and if the timing of passage at all of these intersections is off, there is a risk of collision. In mega-constellations that require such strict operational timing management, if a collision causes orbital errors, the possibility of a chain reaction of collisions is quite high. Furthermore, because debris scattered by a collision will scatter at various speeds and in various directions, it is easy to imagine that a collision accident in an area where thousands of satellites are densely packed together will cause extensive damage.

[0209] <Specific example of responsibility evaluation process 4> The liability assessment unit 210 assesses accident liability and liability for damages so that high-level damage caused by debris scattered due to the collision is covered by life insurance or on-orbit liability insurance.

[0210] For satellites operating regularly in roughly circular orbits, rockets or debris collection satellites that irregularly enter the same orbital plane in an elliptical orbit or other orbital conditions with different circularity factors run the risk of collision. While liability is shared in the event of a collision, it is difficult to say that it is reasonable to cover damages caused by scattered debris through launch insurance or launch third-party liability insurance if the cause is a densely packed environment such as a mega-constellation. Therefore, it is more reasonable to cover damages through the satellite's life insurance or in-orbit third-party liability insurance.

[0211] <Specific example of responsibility evaluation processing 5> The liability assessment unit 210 assesses liability for accidents and damages so as to exempt parties other than those paying life insurance for individual satellites or satellite groups.

[0212] In mega-constellations, the risk of chain collisions is anticipated, so it is unreasonable to attribute compensation for higher-level damage entirely to the initial collision. In addition, it may make more sense to treat a constellation of satellites rather than insuring thousands of satellites individually. If mega-constellation operators were to recognize the risk of chain collisions in advance, pay insurance premiums, and use insurance to cover damages in the event of an accident, they could set insurance rates according to the probability of an accident occurring, the prediction of high-level damage, and the total amount of insurance premiums to be paid. This would have the effect of allowing the establishment of an insurance system without adversely affecting the entire space insurance system.

[0213] <Example 6 of responsibility evaluation processing> FIG. 35 is a diagram showing the collision risk between a space object in routine operation and a space object in non-routine operation. The liability assessment unit 210 assesses the liability for the accident and the liability for damages so as to increase the liability for the accident and the liability for damages of the management company of the space object operating non-routinely in the event of a collision between a space object operating in a routine manner and a space object operating in a non-routine manner.

[0214] The operation of a satellite that continues in orbit for several years to over 10 years until the end of its lifespan is called steady-state operation. In steady-state operation, the satellite orbit maintains a certain degree of reproducibility based on physical phenomena. Furthermore, long-term operation is often carried out in approximately circular orbits. A group of satellites in steady-state operation, maintaining a constant phase interval at the same altitude in an approximately circular orbit, will not collide even if dozens of them fly in the same orbital plane at the same time. On the other hand, in transient orbits leading up to orbital insertion, or in non-routine operations such as rocket launches, satellites enter the same orbital plane non-routinely under orbital conditions with different circular values, such as elliptical orbits, which pose a risk of collisions. Entering the orbital plane at a particularly shallow relative angle poses a risk of collisions with multiple satellites. For this reason, it is reasonable to consider setting heavy liability for accidents and compensation.

[0215] <Specific example of responsibility evaluation processing 7> FIG. 36 is a diagram showing the risk of collision between a geostationary satellite undergoing orbital transfer and a space object in regular operation. The liability assessment unit 210 assesses the liability for the accident and the liability for damages so as to place a heavier burden on the management company of the regularly operating space object when a satellite in the middle of an orbital transfer from a geostationary satellite collides with the regularly operating space object.

[0216] Geostationary satellites are usually launched by rockets to a geostationary transfer orbit (GTO), and then their propulsion devices are activated to transfer them to geostationary orbit. For example, if a chemical propulsion device called an apogee kick motor is activated at the apogee, the timing of activation cannot be chosen arbitrarily, making it difficult for geostationary orbit launch operators to avoid collisions. Furthermore, unlike rocket launch operators, it is difficult to avoid collisions by considering all satellite information in a megaconstellation, including the uncertainty that exists after launch. For mega-constellation operators, it is obvious that satellites launched into geostationary orbit will undergo orbital transfer above the equator, and given that the feasibility of autonomous collision avoidance functions is also being touted, it is reasonable to attribute responsibility to collision avoidance.

[0217] <Specific example of responsibility evaluation process 8> Figure 37 shows the risk of collision between a launched rocket and a mega-constellation. The liability assessment unit 210 assesses liability for accidents and liability for damages so as to exempt from liability for collisions with megaconstellations, which are large-scale satellite constellations formed at orbital altitudes of 600 km or less.

[0218] There is a mega-constellation concept in place that would deploy approximately 2,500 satellites at three different altitudes around 340 km, but there are significant constraints on collision avoidance during rocket launch, which could pose excessive risks to insurance companies. For example, if we assume approximately 40 orbital planes at an altitude of approximately 340 km, with approximately 60 satellites per orbital plane, and the distance between satellites in the same orbital plane is approximately 700 km, and the satellite speed is approximately 7.7 km, then the satellites will revisit the orbital plane at approximately 90-second intervals. Furthermore, it takes approximately 18 minutes for the next orbital plane to revisit after passing an adjacent orbital plane. Furthermore, if there are three orbital planes at different altitudes nearby, the orbital planes will gradually shift in the longitude direction without synchronization. Under these circumstances, a rocket launched from Guiana, near the equator, would need to launch between the three orbital planes and the next one, giving it only a few minutes of time to wait between the time it passes each of the three orbital planes and the time it revisits the next one. Even if a collision occurs under these circumstances, it is difficult to call it an accidental accident, so it is reasonable to exempt the driver from liability. As a result, it will be possible to avoid an increase in the scale of insurance payments due to collision accidents involving low-orbit mega-constellations, which are a frequent risk, and it will be possible to ensure the sustainability of space insurance.

[0219] <Specific example of responsibility evaluation process 8> The liability assessment unit 220 assesses liability for the accident and liability for damages so as to exempt from liability if collision avoidance operational measures are taken without prior notice in the event of a collision between space objects equipped with the function of performing collision avoidance operations.

[0220] Space stations and geostationary orbit satellites often perform collision avoidance operations based on danger warnings. Meanwhile, in low-earth orbit satellites, the distance between satellites is much shorter than in geostationary orbit, and some satellites, like cubesats, lack the capability to perform collision avoidance operations. Therefore, when a danger warning is issued for a low-earth orbit satellite in a specific dense orbital plane, if some satellites perform collision avoidance operations without coordinating with surrounding satellites, there is a risk of collision with other nearby satellites. In addition, some operators have declared that they will be equipped with autonomous collision avoidance operations. If multiple operators' satellites carry out autonomous collision avoidance operations without coordination with surrounding satellites, there is a risk that collisions will occur at different orbital locations as a result of the avoidance. Therefore, according to Example 8 of the liability assessment process, the purpose is to include the risk countermeasures as a premise of the insurance company's contract, and making it a disclaimer is one reasonable measure. If exemptions are not granted, international rules will need to be created to facilitate collision avoidance operations in dense orbits.

[0221] Embodiment 4 In this embodiment, the differences from embodiments 1 to 3 will be mainly described. Note that the same components as those in embodiments 1 to 3 are given the same reference numerals, and the description thereof may be omitted.

[0222] In this embodiment, a collision insurance execution device that implements space collision insurance 202 that compensates for damages caused by collisions between a plurality of space objects flying in space will be described. With the emergence of mega-constellation operators, the likelihood of space object collisions occurring not by accident, but due to a significant incidence rate or human error in judgment, is increasing. While space insurance assumes accidental accidents, there is a need for insurance that covers collisions that cannot be called accidental, i.e., accidents with a significantly higher risk of occurrence compared to the statistical probability of random failure. For example, just as there is term insurance that applies only to the flight when boarding an aircraft, space collision insurance 202, which can be purchased on a term basis once a satellite collision is predicted, is a promising business model. Space collision insurance 202 is also called space object collision insurance.

[0223] ***Configuration Description*** FIG. 38 is a configuration diagram of a collision insurance execution system 560 and a collision insurance execution device 260 according to this embodiment. The collision insurance execution device 260 includes, as functional elements, an insurance processing unit 261 and a storage unit 262. The storage unit 262 stores the space information recorder 50 and the warning issuance information 141.

[0224] The functions of the insurance processing unit 261 are realized by software. The storage unit 262 is provided in the memory 921. Alternatively, the storage unit 262 may be provided in the auxiliary storage device 922. Moreover, the storage unit 262 may be provided separately in the memory 921 and the auxiliary storage device 922.

[0225] The hardware configuration of the collision insurance execution device 260 is the same as that of the collision avoidance support device 100 of embodiment 1. Furthermore, the collision insurance execution program according to this embodiment is a program that realizes the function of the insurance processing unit 261. That is, the collision insurance execution program according to this embodiment causes a computer to execute insurance processing by the insurance processing unit 261.

[0226] ***Explanation of Operation*** The collision insurance execution process by the collision insurance execution device 260 according to this embodiment will be described with reference to FIG.

[0227] <Collision insurance execution process: S300> In step S61, the insurance processing unit 261 executes the space collision insurance 202. Space collision insurance 202 is purchased by management companies that own space objects for which a collision is predicted based on orbital forecast information 51. Space collision insurance 202 pays insurance money when the predicted collision accident actually occurs, and the contract ends when the danger time period during which a danger warning is issued to notify of the risk of collision has passed without an accident. The insurance processing unit 261 manages space collision insurance that can be subscribed to by management operators after a danger alert is issued. The insurance processing unit 261 manages space collision insurance 202 that can be subscribed to by megaconstellation operators who own large-scale satellite constellations, on a satellite-by-satellite basis, and that allows them to receive insurance money in the event of a collision accident. The insurance processing unit 261 also manages space collision insurance 202, which covers high-level damages caused by a chain reaction of collisions resulting from a predicted collision accident. In space collision insurance 202, insurance premiums and insurance rates fluctuate depending on the past record of similar collision accidents.

[0228] A specific example of the space collision insurance 202 executed in the collision insurance execution process will be described below.

[0229] <Example 1 of Space Collision Insurance 202> Space Collision Insurance 202 is a space insurance that stakeholders who own space objects for which a collision is predicted based on publicly available information on space object orbital information forecast values ​​can subscribe to after a collision warning is issued. Space Collision Insurance 202 pays insurance benefits when the predicted collision accident actually occurs, and the contract ends when the danger time period for which the warning was issued has passed without any accident.

[0230] Space collision insurance 202 can be purchased by stakeholders who own a space object for which a collision is predicted based on publicly available information on the space object orbital information forecast value, after a collision warning is issued, in the launch insurance, life insurance, launch third-party liability insurance, and orbital third-party liability insurance described in embodiment 3. Space collision insurance 202 pays insurance money when the predicted collision accident actually occurs, and the contract terminates if the danger time period for which the warning was issued has passed without any accident. Danger warnings such as collision warnings may be issued by SSA operators based on publicly available orbital forecast information, or by a separate operator that specializes in providing advice on avoiding collisions with space objects. The insurance payout after a collision is based on the precise orbital history of the Space Information Recorder, and is set so that the insurance payout is higher if the difference between the predicted value and the actual value is small. If neither party takes evasive action despite a collision warning being issued, the insurance company will be exempt from liability and no insurance payments will be made.

[0231] <Example 2 of Space Collision Insurance 202> Space Collision Insurance 202 is a space insurance that can be purchased ad hoc when a collision accident is predicted, even if a collision warning is not issued. Space Collision Insurance 202 pays out when the predicted collision accident actually occurs, and the contract ends when the danger time period when the warning was issued has passed without any accident.

[0232] During rocket launch, space objects that have deorbited and are in the process of deorbiting, or space objects flying in elliptical orbits during orbital transfer, are at risk of colliding with mega-constellation satellites flying across the sky. However, if forecast values ​​are not made public, or even if they are, there is a possibility that SSA operators or orbital analysis service providers will not be able to issue collision warnings in a timely manner. In such cases, it is reasonable for operators to be able to purchase ad hoc insurance at their discretion, even if no collision warnings are issued. The contract ends once the object has safely passed through the dangerous orbit.

[0233] <Example 3 of Space Collision Insurance 202> FIG. 40 is a diagram showing space collision insurance 202 according to this embodiment. Space Collision Insurance 202 can be purchased by mega-constellation operators on a satellite group basis, and insurance payments can be received in the event of a collision accident caused by a collision warning or ad hoc collision risk.

[0234] Megaconstellation operators can foresee numerous collision risks in the future, and can choose to fund their insurance through life insurance or third-party liability insurance, or through ad hoc space collision insurance. 202 In addition, since it is irrational to purchase insurance for each individual satellite in a constellation of several thousand satellites, it is rational to insure a constellation of satellites at a specific altitude that cooperate to provide a series of services collectively, and to have insurance payments made for each individual satellite that constitutes it. Furthermore, when funding ad hoc space collision insurance202, it is reasonable for the contract to terminate for rockets or space objects undergoing deorbiting after they pass through the danger zone, but it is reasonable for megaconstellation operators to have a system in place to subscribe to insurance for all ad hoc collision risks that arise one after another. Premiums should be set according to the size of the constellation, the expected frequency of ad hoc collision risks, and the contract period.

[0235] <Example 4 of Space Collision Insurance 202> Space collision insurance 202 covers high-level damages caused by a chain reaction of collisions resulting from ad-hoc collision accidents that are predicted in advance.

[0236] In the case of a mega-constellation satellite group, if a single component satellite is destroyed explosively or malfunctions and loses its orbital control capability, there is a risk of a chain reaction collision with another satellite flying in the same orbital plane or another satellite flying in a nearby orbit. If a large amount of debris is scattered, there is a risk that it will spread over a long period of time and violate the entire nearby orbital altitude, which could cause significant damage to mega-constellation operators. If these high-level damages that can be foreseen in advance are covered by insurance, it may be possible to establish space collision insurance202 ​​by having megaconstellation operators pay high insurance premiums.

[0237] <Example 5 of Space Collision Insurance 202> Space collision insurance 202 does not cover higher damages caused by a chain of collisions resulting from ad hoc collision accidents that are predicted in advance.

[0238] Space Collision Insurance 202 provides insurance coverage for only the one aircraft involved in the collision when the party issuing the collision warning is a constellation operator, and does not take into account damages resulting from chain reactions. In the case of space collision insurance 202 in Example 4, which covers high-level damage, it is difficult to estimate the scale of high-level damage, and there is a risk of insurance rates rising after an accident occurs, or there is concern that this could pose a risk to the sustainability of the insurance business itself. In a situation where megaconstellation operators are unwilling to pay sufficient insurance premiums, it is reasonable to exclude foreseeable high-level damage from the scope of insurance payments as an exemption.

[0239] <Example 6 of Space Collision Insurance 202> The insurance premium and premium rate for space collision insurance 202 vary depending on the past record of similar collision accidents.

[0240] In space collision insurance 202, insurance premiums and insurance rates fluctuate based on information on similar space object collision accidents that have occurred in the past. Information on similar space object collision accidents that have occurred in the past includes orbital forecast information 51 and orbital performance information 52 from the space information recorder 50, details of compensation for damages and lawsuits in the accident, frequency of similar accidents, and analysis results of past information on insurance payment results.

[0241] In the above first to fourth embodiments, the collision avoidance support device, the space insurance support device, and the collision insurance management device have been described as independent functional blocks. However, the configurations of the collision avoidance support device, the space insurance support device, and the collision insurance management device do not have to be as in the above-described embodiments. The functional blocks of the collision avoidance support device, the space insurance support device, and the collision insurance management device may have any configuration as long as they can realize the functions described in the above-described embodiments. Furthermore, each of the collision avoidance support device, the space insurance support device, and the collision insurance management device may be a single device or a system made up of multiple devices.

[0242] ***Other Configurations*** <Modification> Here, modifications of the third and fourth embodiments will be described. The space insurance support system and collision insurance execution system are also referred to as insurance payment systems. The insurance payment system includes a server having a database that records insurance payment contract information for each individual insurance contract, and a database that records space object information. Specifically, the database is a memory or an auxiliary storage device. Specifically, the server is a space insurance support device or a collision insurance management device. The space insurance support device and the collision insurance management device may work together to realize the functions of the server. The server realizes the following steps (also called means or units) using processing circuitry such as a processor or electronic circuit. A specific example of the insurance premium rate setting means is an insurance premium evaluation section, and a specific example of the insurance payment assessment means is an insurance processing section.

[0243] The contract information includes insurance premium rates, accident liability assessments, and insurance claim assessment amounts. The space object information includes orbit forecast information for each of space objects A and B where the collision accident occurred, and orbit performance information for each of space objects A and B during the time period when the collision occurred. The server includes the following stages: After a collision occurs, the responsibility of colliding space objects A and B is assessed based on the difference between actual orbit information and predicted orbit information. The stage where insurance payment is assessed based on the difference between the actual orbit information and the forecast orbit information. -The stage of paying insurance claims.

[0244] The space object information includes space object collision warnings obtained from satellite information management companies. The server also includes the following steps: After a collision occurs, the responsibility of colliding space objects A and B is assessed based on the difference between actual orbit information and predicted orbit information. The stage where insurance payment is assessed based on the difference between the actual orbit information and the forecast orbit information. -The stage of paying insurance claims.

[0245] The server also includes the following steps: The stage where contracts are accepted after receiving a space object collision warning. The stage of determining insurance rates based on error information from the predicted orbit information recorded in the space object information. After a collision occurs, the responsibility of colliding space objects A and B is assessed based on the difference between actual orbit information and predicted orbit information. The stage where insurance payment is assessed based on the difference between the actual orbit information and the forecast orbit information. -The stage of paying insurance claims. The stage where the contract is terminated after payment is completed, the stage where the contract is terminated due to a release of liability, or the stage where the contract is terminated without a collision occurring due to a space object collision warning.

[0246] The server also includes the following steps: This is the stage where contracts are accepted after obtaining forecasts of rocket launches, satellite orbital transfers, or satellite passes during deorbit. The stage of determining insurance rates based on error information from the predicted orbit information recorded in the space object information. After a collision occurs, the responsibility of colliding space objects A and B is assessed based on the difference between actual orbit information and predicted orbit information. The stage where insurance payment is assessed based on the difference between the actual orbit information and the forecast orbit information. -The stage of paying insurance claims. The stage where the contract is terminated after payment is completed, the stage where the contract is terminated due to a release of liability, or the stage where the contract is terminated without a collision occurring due to a space object collision warning.

[0247] In the insurance payment system, after a collision accident occurs, when the liability of colliding space objects A and B is assessed based on the difference between actual orbit information and predicted orbit information, the greater the difference between the actual orbit information and the predicted orbit information, the heavier the assessment of liability for the accident.

[0248] In the insurance payment system, when assessing the insurance payout for colliding space objects A and B based on the difference between actual orbit information and predicted orbit information after a collision accident occurs, the smaller the difference between the actual orbit information and the predicted orbit information, the higher the assessed insurance payout.

[0249] In the insurance payment system, at the stage where insurance rates are determined based on error information of the predicted orbit information recorded in the space object information, the smaller the estimated error amount, the lower the insurance rate will be.

[0250] The insurance payment system provides an exemption clause for collision accidents in which a collision occurs when neither the management company of space object A nor the management company of space object B takes any action to avoid the collision, despite receiving a space object collision warning from a satellite information management company and receiving orbital forecast information for each of space object A and space object B, which are predicted to collide.

[0251] The insurance payment system will include in the contract information information that insurance payments will only be made for collision accidents involving space objects identified by space object collision alerts obtained from satellite information management companies, and that liability will be exempt for severe damage caused by chain reactions.

[0252] In the insurance payment system, the contract information will include information stating that in addition to collision accidents involving space objects identified by space object collision warnings obtained from satellite information management companies, insurance payments will also be made for damages caused by chain reactions.

[0253] In the insurance payment system, when assessing the insurance payout for space objects A and B that collided after a collision accident based on the difference between actual orbit information and predicted orbit information, the insurance payout will be subject to compensation for damages caused by the chain reaction accident.

[0254] The insurance payment system will include in the contract information information that exempts liability for extensive damage caused by debris scattered due to collisions during rocket launches or collisions with debris removal satellites.

[0255] In the insurance payment system, the contract information includes information that exempts liability if the party involved in a space object collision is a megaconstellation operator and has not paid insurance premiums for individual satellites or satellite groups.

[0256] In the insurance payment system, after a collision accident occurs between a space object in routine operation and a space object in non-routine operation, when assessing the liability of the colliding space object A and space object B based on the difference between actual orbit information and predicted orbit information, the liability of the non-routine operation side is assessed more heavily.

[0257] In the insurance payment system, when a collision accident occurs between a space object in routine operation and a space object in non-routine operation, the insurance payment for the space object A and space object B that collided based on the difference between actual orbit information and predicted orbit information is assessed, the insurance payment for the space object in routine operation is assessed at a higher amount.

[0258] In the insurance payment system, after a collision occurs between a satellite in orbital transfer and a space object in regular operation, the liability of the colliding space object A and space object B is assessed based on the difference between actual orbital information and predicted orbital information, and the liability of the satellite in orbital transfer is assessed lightly.

[0259] In the insurance payment system, when a collision accident occurs between a satellite in orbital transfer and a space object in regular operation, the insurance payment for the colliding space object A and space object B is assessed based on the difference between actual orbit information and predicted orbit information, and the insurance payment for the space object in regular operation is assessed at a higher amount.

[0260] The insurance payment system will include information in the contract information that waives liability for collisions with mega-constellation operators formed at altitudes of 600 km or less.

[0261] In the insurance payment system, the contract information includes information that exempts the insurance company from liability if collision avoidance measures are taken without notice in the event of a collision between space objects equipped with a function to perform collision avoidance operations.

[0262] The insurance payment system allows mega-constellation operators to subscribe to each satellite group and receive insurance payments in the event of a collision accident caused by collision warnings or ad hoc collision risks.

[0263] In the insurance payment system, the error information included in the orbit forecast information includes the basis for calculating the amount of error, and the clearer the basis, the lower the insurance premium rate is set.

[0264] In the insurance payment system, the error information included in the orbit prediction information includes verification results, and the more extensive the verification results, the lower the insurance premium rate is set.

[0265] In the insurance payment system, insurance rates fluctuate depending on the past record of similar collision accidents.

[0266] In the insurance payment system, the assessment of accident liability and insurance payment varies depending on the past record of similar collision accidents.

[0267] The server also comprises the following steps: The stage where contracts are accepted after receiving a space object collision warning. A stage of determining insurance rates based on error information of the predicted orbit information recorded in the space object information, and a stage of assessing the liability of the colliding space object A and space object B based on the difference between the actual orbit information and the predicted orbit information after the collision accident occurs. The stage of assessing insurance claims. The stage where the contract is terminated when the insurance payment is completed or no collision accident occurs due to the space object collision warning.

[0268] The space insurance program causes a computer to execute a process to pay insurance money from insurance premiums collected in advance in the event that space object A and space object B among multiple space objects collide. The space insurance program includes a danger warning output means for identifying the presence of a potential dangerous object based on orbital forecast information provided by a space information recorder and outputting a danger warning before a collision occurs between multiple space objects flying in space. Space collision insurance under the Space Insurance Program is space collision insurance that is taken out by management companies that own space objects for which a collision is predicted after a danger warning is issued by the Collision Avoidance Assistance Program.It is an ad hoc space collision insurance in which insurance payments are made when the predicted collision accident actually occurs, and the contract terminates if the danger time period during which the danger warning notifying of the risk of collision is issued passes without any accident.

[0269] Space collision insurance under the Space Insurance Program can be purchased by megaconstellation operators who own large-scale satellite constellations on a satellite-by-satellite basis, and insurance payments can be received in the event of a collision accident.

[0270] Space collision insurance under the Space Insurance Program does not cover higher-level damage caused by a chain of collisions resulting from a foreseeable collision accident.

[0271] Space collision insurance under the Space Insurance Program covers high-level damage caused by a chain of collisions resulting from a foreseeable collision accident.

[0272] The space collision insurance provided by the Space Insurance Program has variable premium rate setting methods and insurance claim assessment methods depending on the past performance of similar collision accidents.

[0273] Embodiment 5 In this embodiment, the differences from embodiments 1 to 4 will be mainly described. Note that the same components as those in embodiments 1 to 4 are given the same reference numerals, and the description thereof may be omitted.

[0274] ***Configuration Description*** FIG. 41 is a diagram showing an example of the functional configuration of a satellite constellation forming system 600. 41 differs from FIG. 8 in that communication with a rocket launch business device 46 is illustrated.

[0275] FIG. 42 is a configuration diagram of an information management system 500 according to this embodiment. The information management system 500 includes a management business device 40 and an information management device 1000. The information management device 1000 is mounted on at least one of a plurality of management business devices 40, each of which manages a plurality of space objects 60 flying in space. Specifically, the information management device 1000 is a satellite constellation business device 451 used by a satellite constellation operator that forms a satellite constellation consisting of a plurality of satellites. The mega constellation business device 41 or the LEO constellation business device 42 are examples of the satellite constellation business device 451. The information management device 1000 discloses information about multiple space objects flying in space, for example, information about satellite constellations, to other management business devices 40. The other management business devices 40 refer to other management business devices that do not have the information management device 1000 installed. Specifically, the other management business devices 40 are rocket launch business devices 46, orbital transfer business devices 44, or debris collection business devices 45 used by debris collection businesses. Note that even when the information management device 1000 is installed in a satellite constellation business device 451, the other management business devices 40 may include other satellite constellation business devices. In addition, the information management device 1000 may be a device that centrally manages satellite constellation business equipment used by satellite constellation operators that form satellite constellations consisting of multiple satellites, and rocket launch business equipment used by rocket launch operators.

[0276] The management business device 40 performs the management business of space objects 60 such as artificial satellites or debris. The management business device 40 is a computer of a business operator that collects information on space objects 60 such as artificial satellites or debris. The management business equipment 40 includes equipment such as a megaconstellation business equipment 41, a LEO constellation business equipment 42, a satellite business equipment 43, an orbital transfer business equipment 44, a debris retrieval business equipment 45, a rocket launch business equipment 46, and an SSA business equipment 47.

[0277] The management business device 40 may collect information about space objects such as artificial satellites or debris, and provide the collected information to the information management device 1000. In addition, when the information management device 1000 is mounted on a public server of the SSA, the information management device 1000 may be configured to function as the public server of the SSA.

[0278] The information management device 1000 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.

[0279] The information management device 1000 includes, as functional elements, an information disclosure unit 1100 and a storage unit 1400. The storage unit 1400 stores a space information recorder 50 and a disclosure threshold 141. The disclosure threshold 141 is a threshold for determining whether or not to disclose the orbit forecast information 51.

[0280] The functions of the information disclosure unit 1100 are realized by software. The storage unit 1400 is provided in the memory 921. Alternatively, the storage unit 1400 may be provided in the auxiliary storage device 922. Furthermore, the storage unit 1400 may be divided into the memory 921 and the auxiliary storage device 922.

[0281] The hardware configuration of the space insurance support device 200 is the same as that of the collision avoidance support device 100 of the first embodiment.

[0282] ***Explanation of Operation*** <Information disclosure processing: S1000> FIG. 43 is a flow diagram of the information disclosure process S1000 according to this embodiment. In the information disclosure process, the information disclosure unit 1100 determines whether or not to disclose the orbit forecast information 51 to other management business devices 40 based on a disclosure threshold 141 for determining whether or not to disclose the orbit forecast information 51 and a forecast error 514. For example, the information disclosure unit 1100 discloses the orbit forecast information 51 to other management business devices when the forecast error 514 is equal to or greater than the disclosure threshold 141. Also, for example, when the forecast error 514 is smaller than the disclosure threshold 141, the information disclosure unit 1100 does not disclose the orbit forecast information 51 to other management business devices. Note that the determination of whether to disclose or not disclose information may use a determination method other than the above.

[0283] In step S1001, the information disclosure unit 1100 receives an information disclosure request 551 requesting disclosure of the orbit forecast information 51 from another management business device.

[0284] In step S1002, the information disclosure unit 1100 extracts disclosure forecast information 552 from multiple pieces of orbit forecast information corresponding to multiple space objects included in the orbit forecast information 51. For example, the information disclosure unit 1100 may extract, as the disclosure forecast information 552, orbit forecast information whose forecast error 514 is equal to or greater than the disclosure threshold 141 from multiple pieces of orbit forecast information corresponding to multiple space objects included in the orbit forecast information 51. The information disclosure unit 1100 may also extract the disclosure forecast information 552 using other methods. The information disclosure unit 1100 outputs the disclosure forecast information 552 to another management business device. At this time, when the information disclosure unit 1100 receives the information disclosure request 551, it may transmit the disclosure forecast information 552 to the other management business device for a fee. For example, the rocket launch business device 46 transmits an information disclosure request 551 requesting the disclosure of the orbit forecast information 51 to the information management device 1000. In response to the disclosure forecast information 552, the rocket launch business device 46 receives the disclosure forecast information 552 from the information management device 1000.

[0285] <Satellite constellation control processing: S2000> FIG. 44 is a flow diagram of the satellite constellation control process S2000 according to this embodiment. Next, using Figures 41 and 44, we will explain the satellite constellation control processing S2000 when the satellite constellation formation system 600 acquires rocket launch information 503 from the rocket launch business device 46 that has received the disclosed forecast information 552. The satellite constellation control process S2000 is a process for controlling the orbit of the satellite constellation 20 when a space object such as a rocket passes through the satellite constellation 20.

[0286] In step S2001, the satellite constellation formation unit 11 acquires, from the rocket launch business equipment 46, rocket launch information 503 including the launch point of the rocket in the rocket launch and the scheduled launch time of the rocket at the launch point.

[0287] In step S2002, the satellite constellation forming unit 11 controls the orbit of each of the multiple satellites based on the rocket launch information 503 so that each of the multiple satellites does not fly along its flight path at the scheduled time for the rocket to fly along its flight path after launch. Specifically, the satellite constellation forming unit 11 controls the orbit of each of the multiple satellites so that the orbital plane of the multiple satellites deviates from the sky above the launch point by operating the propulsion device 33 of each of the multiple satellites. For example, the satellite constellation forming unit 11 generates an orbit control command 55 for performing the above-mentioned orbit control and transmits it to the satellite 30.

[0288] Below, specific examples and effects of the information disclosure process and satellite constellation control process will be described. 45 is a diagram showing the error range between the rocket launch forecast value and the satellite constellation 20. The satellite constellation 20 is a large-scale satellite constellation, that is, a megaconstellation, for example, ranging from several hundred to several thousand satellites.

[0289] The upper part of Fig. 45 is a conceptual diagram of a two-dimensional model of the satellite constellation 20. The lower part of Fig. 45 is a conceptual diagram of the launch window for a rocket launch when the satellite constellation 20 in the upper part of Fig. 45 is located in the sky. As shown in the lower part of Figure 45, when the error range of each satellite in the satellite constellation 20 is taken into consideration, the launch window that is permissible for a rocket launch is limited. Therefore, the satellite constellation forming system 600 needs to control the orbit of the satellite constellation 20 based on the rocket launch information 503.

[0290] FIG. 46 is a diagram showing the error range between the rocket launch forecast value and the satellite constellation 20. The upper part of Fig. 46 is a conceptual diagram showing a satellite constellation 20 with a small error range, and the lower part of Fig. 46 is a conceptual diagram showing a satellite constellation 20 with a large error range.

[0291] As shown in the upper part of Figure 46, within the satellite constellation operator's own system, it may be possible to reduce the error range by using methods such as differential evaluation of inter-satellite ranging data and GPS measurement values, or statistical data evaluation. If satellite constellation operators do not disclose their error ranges, launch vehicle operators will have to rely on external measurement information, such as SSA operators, for information on satellite orbit forecasts, which could result in launch vehicle operators only being able to see forecasts with large error ranges. In this way, by providing orbit forecast information within a predetermined error range for a fee, it is possible to contribute to the business of providing precise orbit forecast values ​​that are useful to rocket launch operators.

[0292] Although the orbit forecast information described here is used by rocket launch operators when launching a rocket, the present embodiment can also be applied to various other situations, such as the passage of a satellite constellation when a satellite is launched, the passage of a satellite constellation when debris is collected, or the investigation of the orbit of a space object.

[0293] ***Explanation of the effect of this embodiment*** According to the information management device 1000 of this embodiment, a satellite constellation operator that forms a megaconstellation can disclose the predicted values ​​of the orbital information of its own satellite to a rocket launch operator, a geostationary satellite orbit injection operator, or a debris collection operator for a fee. In order for rocket launch operators to fulfill their obligation to ensure flight safety, they need accurate predicted orbit information for the satellites that make up the mega-constellation. Therefore, the information management device 1000 according to this embodiment has the effect of increasing the asset value of the satellite orbit prediction information, which can become a source of revenue for satellite operators.

[0294] In addition, there is a high risk of a collision with a satellite in a megaconstellation when a satellite leaves its orbit and de-orbits after completing its mission. Similarly, it may be possible to hold accountable the operator of a de-orbiting satellite or a debris collection company that neglected to take collision avoidance measures for the orbital information that they disclosed, which has the effect of making satellite orbital information a source of revenue. Furthermore, operators who launch geostationary satellites into orbit use rockets to launch them into geostationary transfer orbit, and then transfer them to geostationary orbit using the satellite's own propulsion device. During this process, there is a risk of collision with mega-constellation satellites, and similar effects are expected.

[0295] The information management device 1000 according to this embodiment allows rocket launch operators to share the satellite orbit information forecast values ​​of mega-constellation operators in low orbit altitudes. This allows rocket launch operators to develop a rocket launch business in which launches without using disclosed information on satellite predicted orbit information and without collision risk are a source of competitiveness. If the satellite predicted orbit information itself becomes worth paying for, being able to launch a rocket without using the paid information will have the effect of reducing costs and becoming a source of competitiveness for the business.

[0296] According to the satellite constellation formation system 600 of this embodiment, in a rocket launch where the launch time available at a launch point is limited, the satellite's orbit can be changed in advance so that the satellite does not fly on the flight path at the scheduled launch time at that launch point. For a planetary exploration spacecraft intended to rendezvous with a planet traveling in a specific orbit, the launch window during which it can be launched appropriately from the launch site may be limited to a short time of several seconds. Meanwhile, because the Earth rotates relative to the orbital plane of a satellite traveling in inertial space according to the laws of nature, there is a risk of a satellite accidentally landing on the launch path and colliding with it. In a megaconstellation, the interval between satellites traveling in the same orbital plane may be only a few tens of seconds, making sufficient collision avoidance difficult without measures to prevent the orbital plane from being positioned in the sky. According to the satellite constellation formation system 600 of this embodiment, the satellite megaconstellation side activates the propulsion devices of all satellites in advance so that the orbital plane is not positioned in the sky at a specific time and a specific launch site. Then, by raising or lowering the satellite's orbital altitude and adjusting the relative relationship between the orbital plane and the Earth's rotation, the orbital plane is shifted so that it is not positioned in the sky at a specific time and a specific launch site, thereby avoiding collisions. In megaconstellations, adjusting only individual satellites poses the risk of collision with other satellites, so it is important to synchronize and adjust all satellites.

[0297] In this embodiment, the following information management method for the information management device has been described.

[0298] The information management device manages orbital forecast information stored in a management business device that manages satellites that form a satellite constellation. The processor of the information management device includes a disclosure threshold and an information disclosure determination means for determining whether to disclose the information. The disclosure threshold is information for determining whether to disclose the orbit forecast information of the satellite constellation management business device when it is predicted that a satellite forming the satellite constellation and a space object whose orbit forecast information has been obtained from another management business device will approach each other at a specific time based on the orbit forecast information.

[0299] The other management business equipment is a rocket launch business equipment, an orbital transfer business equipment, or a debris collection business equipment.

[0300] The management business device A for managing rocket launches is equipped with a space information recorder A for recording space object information A including launch time information and orbit forecast information for rocket launches. A management business device B that manages satellites that form a satellite constellation is equipped with a space information recorder B that records space object information B including forecast origins, forecast orbit information, and forecast errors of multiple satellites that form the satellite constellation. A management business device C, which is used by an analysis company that analyzes collisions between space objects to manage space object information, is equipped with a space information recorder C that records various space object information obtained from a management business device used by a management company that manages multiple space objects. The satellite constellation management business device will not disclose space object information B to space information recorder A and space information recorder C owned by other businesses. A single operator then exclusively uses space object information A and space object information B to perform collision analysis, derive conditions that ensure flight safety during rocket launch, and avoid collisions.

[0301] A satellite constellation management business device discloses space object information B to space information recorder A and space information recorder C owned by other businesses for a fee. Then, only a single operator can use space object information A and space object information B free of charge to perform collision analysis, derive conditions that ensure flight safety during rocket launch, and avoid collisions.

[0302] The satellite constellation management business device will not disclose space object information B to space information recorder A and space information recorder C owned by other businesses. The satellite constellation operator then uses space object information A and space object information B to conduct a collision analysis, and if a collision is predicted, the satellite constellation operator will take evasive action to ensure flight safety.

[0303] ***Other Configurations*** In this embodiment, the functions of the information management device 1000 are realized by software. As a modification, the functions of the information management device 1000 may be realized by hardware.

[0304] FIG. 47 is a diagram showing the configuration of an information management device 1000 according to a modification of this embodiment. The information management device 1000 includes an electronic circuit in place of the processor 910 . The electronic circuit is a dedicated electronic circuit that realizes the functions of the information management device 1000 . The electronic circuit may be a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array. The functions of the information management device 1000 may be realized by one electronic circuit, or may be realized by distributing the functions across multiple electronic circuits. As another modification, some of the functions of the information management device 1000 may be realized by electronic circuits, and the remaining functions may be realized by software.

[0305] Each of the processor and the electronic circuit is also called processing circuitry. That is, the functions of the information management device 1000 are realized by the processing circuitry.

[0306] Embodiment 6 In this embodiment, the following description will be mainly focused on the points added to the embodiments 1 to 5. Note that the same components as those in the embodiments 1 to 5 are given the same reference numerals, and the description thereof may be omitted.

[0307] In this embodiment, a variation of the management business device 40 using the collision avoidance support device 100 described in the first to fifth embodiments will be described.

[0308] The SSA business device 47 described in the first embodiment is a computer of an SSA business operator that conducts an SSA business, i.e., a space situation awareness business. The SSA business operator manages space object information. The SSA business device 47 is used by an SSA business operator that manages space object information that indicates the status of space objects flying in space. For example, the SSA business operator makes at least a portion of the space object information collected through the SSA business available on a server. The SSA business device 47 is also called a space situation awareness business device. SSA is an abbreviation for Space Situation Awareness. Furthermore, the management business device 40 described in the first to fifth embodiments may be simply called a business device.

[0309] The mega-constellation business device 41 is a computer of a mega-constellation business operator that operates a large-scale satellite constellation, i.e., a mega-constellation business. The mega-constellation business device 41 is a business device that manages a satellite constellation consisting of, for example, 100 or more satellites. The LEO constellation business device 42 is a computer of a LEO constellation business operator that operates a low earth orbit constellation, i.e., a LEO constellation business. The LEO constellation business device 42 is, for example, a business device that manages a constellation of 10 or more satellites. The satellite business device 43 is, for example, a computer of a satellite business operator that handles one to several satellites. Mega-constellation business equipment 41, LEO constellation business equipment 42, and satellite business equipment 43 are examples of satellite constellation business equipment. A satellite constellation business equipment is a business equipment that manages a constellation of 100 or more satellites, a constellation of 10 or more but less than 100 satellites, or a constellation of less than 10 satellites.

[0310] In this embodiment, the SSA business device 47 includes a collision avoidance assistance device 100 and executes a collision avoidance assistance method or a collision avoidance assistance program. The SSA business device 47 also executes the functions of a collision avoidance assistance system 500.

[0311] The satellite constellation business device manages a constellation of 100 or more satellites, a constellation of 10 or more but less than 100 satellites, or a constellation of less than 10 satellites. The satellite constellation business device discloses satellite orbit information to the collision avoidance assistance device 100.

[0312] The satellite constellation business device manages a constellation of 100 or more satellites, or a constellation of 10 or more satellites but less than 100. The satellite constellation business device performs the functions of the satellite constellation forming system 600.

[0313] In this embodiment, the rocket launch business device 46 discloses rocket trajectory information to the collision avoidance support device 100.

[0314] In this embodiment, the debris removal business device manages a debris removal satellite equipped with means for capturing space objects. The debris removal business device is an example of a debris collection business device 45 that collects debris. The debris removal business device discloses orbital information of the debris removal satellite to the collision avoidance assistance device 100. In addition, the debris removal business device acquires orbital information of space objects from the collision avoidance support device 100. The debris removal business device may also be a business device that includes the collision avoidance assistance device 100 and executes the collision avoidance assistance method or the collision avoidance assistance program. Alternatively, the debris removal business device may be a business device that executes the functions of the collision avoidance assistance system 500.

[0315] The space insurance management business device is a business device used by a space insurance company that manages space insurance. The space insurance management business device acquires orbital information of space objects from the collision avoidance support device 100.

[0316] The space object management business device is a business device that manages space object information of space objects other than satellites or rockets, including space stations, space transport vehicles, and spacecraft. In other words, the space object management business device manages space object information of space objects other than satellites and rockets, including at least one of space stations, space transport vehicles, and spacecraft. The space object management business device discloses the orbital information of the space objects to the collision avoidance assistance device 100.

[0317] The space traffic management enterprise is an enterprise that manages space traffic and includes a spacecraft control device or a collision avoidance assistance device 100. The space traffic management enterprise is equipped with the collision avoidance assistance device 100 and executes a collision avoidance assistance method or a collision avoidance assistance program. The space traffic management enterprise also executes the functions of the collision avoidance assistance system 500.

[0318] Embodiment 7 In this embodiment, the following description will be mainly focused on the points added to the embodiments 1 to 6. Note that the same components as those in the embodiments 1 to 6 are given the same reference numerals, and the description thereof may be omitted.

[0319] In this embodiment, a variation of the SSA business device 47 described in the first to sixth embodiments will be described.

[0320] In this embodiment, the SSA business device 47 is used by an SSA business operator equipped with a monitoring device to manage space object information. The SSA project equipment 47 measures space object A multiple times using a monitoring device to calculate initial estimates of the orbital elements, which consist of an epoch and six orbital elements. The SSA project equipment 47 acquires orbital information of space object A four or more times, calculates updated estimates of the orbital elements, and if there is a significant change that exceeds the measurement error and estimation error, determines that space object A is accelerating or decelerating.

[0321] In addition, after determining that space object A is accelerating or decelerating, the SSA business device 47 generates orbit prediction information for space object A after acceleration or deceleration, and points the monitoring device at space object A using the orbit prediction information to measure space object A and track and monitor space object A.

[0322] In addition, the SSA business device 47 issues an alert to the management company of space object B when it predicts a risk of approach or collision with space object B, taking into account the future acceleration / deceleration of space object A.

[0323] Incidentally, when the collision avoidance assistance device 100 predicts a risk of approach or collision with space object B, taking into account the future acceleration / deceleration of space object A, it may issue an alert to the management company of space object B. The collision avoidance assistance device 100 executes such a collision avoidance assistance method or collision avoidance assistance program. In addition, the collision avoidance assistance device 100 performs the function of a collision avoidance assistance system 500, which issues an alert to the management company of space object B when a risk of approach or collision with space object B is predicted, taking into account the future acceleration / deceleration of space object A.

[0324] FIG. 50 shows an example of the configuration of the SSA business device 47 according to this embodiment. The SSA business device 47 includes a first monitoring device 810a flying near geostationary orbit, a second monitoring device 840 installed on the ground, and a catalog that records orbital information of multiple space objects. The space object information 501 includes orbital information of space objects collected from other management business devices 40. For example, the space object information 501 includes a catalog in which orbital information of space objects is pre-recorded. The catalog is collected from a management company that manages space objects. The SSA business equipment 47 also includes a measurement error inspection device 471 and an accelerating / decelerating object tracking device 472. A specific example of the first monitoring device 810a is an observation satellite 812. A specific example of the second monitoring device 840 is an observation device included in the ground equipment 700 of the SSA business equipment 47.

[0325] <Operation Example 1 of this Embodiment> The catalog records public orbit information obtained from publicly available information, first orbit information obtained by the first monitoring device 810a, and second orbit information obtained by the second monitoring device 840. Based on the public orbital information of the specific space object, the SSA business device 47 acquires monitoring information of the specific space object by the first monitoring device 810a and the second monitoring device 840. The SSA business device 47 acquires first monitoring information by the first monitoring device 810a and acquires second monitoring information by the second monitoring device 840. The monitoring information includes the first monitoring information and the second monitoring information. The measurement error inspecting device 471 selects highly reliable orbital information based on the public orbital information, the first orbital information, and the second orbital information for the specific space object, and generates third orbital information, which is updated information.

[0326] The orbit information from public information has the problem of low accuracy of position information. Furthermore, in the first and second monitoring devices, the object information acquired by the optical monitoring means has the problem of high accuracy in measuring the azimuth angle as seen from the monitoring device, but large errors in the distance direction. Furthermore, the object information acquired by the radar or laser monitoring means has the problem of high accuracy in measuring the distance as seen from the monitoring device, but large errors in the azimuth angle.

[0327] Therefore, by acquiring monitoring information of a specific monitoring target based on public orbit information using the first monitoring device and the second monitoring device, it becomes possible to update the catalog with reduced errors in the public information. Furthermore, by selecting highly reliable information as the position information that constitutes the orbit information according to the position of the monitoring device and the monitoring means, it is possible to improve the accuracy of the orbit information. For stars in inertial space or space objects flying near geostationary orbits that rely solely on natural phenomena and do not involve the operation of artificial propulsion devices, it is easy to estimate their positions after a certain time has passed. However, if there is a large error in the public orbital information, there is a risk that the object will deviate from the field of view of the first or second monitoring device and become impossible to monitor.

[0328] According to the first operational example of this embodiment, there is an effect that the inherent error of the trajectory information can be reduced, so that the first monitoring device or the second monitoring device can reliably capture the object within the field of view.

[0329] <Operation Example 2 of this Embodiment> Based on the third orbital information, the SSA business device 47 again acquires monitoring information of the specific space object from both or either of the first monitoring device 810 and the second monitoring device 840. The measurement error inspection device 471 updates the third orbit information based on the third orbit information, the updated first orbit information, and the updated second orbit information. The measurement error inspection device 471 compares and evaluates the third orbit information before and after the update to identify whether or not the specific space object has artificially accelerated or decelerated motion. Then, the measurement error inspection device 471 records information about the space object having artificially accelerated or decelerated motion in the accelerating / decelerating object tracking device 472 as the initial value of the tracking information.

[0330] Space objects flying near geostationary orbit may be accompanied by the operation of artificial propulsion devices. Compared to space objects whose flight relies solely on natural phenomena, if the position after acceleration and deceleration over time is significantly different from the estimated position, it can be identified as a space object with artificial acceleration and deceleration. In operation example 2 of this embodiment, a space object exhibiting artificial acceleration / deceleration in geostationary orbit is identified. For space objects for which non-regular movement plans for orbit insertion, deorbit, or orbital transfer have been published in advance, consideration has been given to ensuring that even if artificial acceleration / deceleration is identified, there will be no adverse effects or danger to other satellites. However, space objects for which non-regular movement plans have not been published must be tracked as suspicious objects.

[0331] <Operation Example 3 of this Embodiment> The accelerating / decelerating object tracking device 472 acquires monitoring information of the specific space object again using both or either of the first monitoring device 810 and the second monitoring device 840 based on the updated third orbit information. The measurement error inspection device 471 re-updates the third orbit information based on the updated third orbit information, the re-updated first orbit information, and the re-updated second orbit information.The measurement error inspection device 471 then compares and evaluates the third orbit information before the update, after the update, and after the re-update, obtains acceleration and deceleration information of the specific space object, and records the updated value of the orbit information of the specific space object as tracking information.

[0332] According to operation example 3 of this embodiment, by tracking the passage of time regarding the third orbit information, the offset error contained in the position measurement error can be eliminated, and it becomes possible to grasp the intentional direction of movement of the space object.

[0333] <Operation Example 4 of this Embodiment> The accelerating / decelerating object tracking device 472 repeatedly updates the monitoring information by both or one of the first monitoring device 810 and the second monitoring device 840 based on the third orbit information, and records the updated value of the orbit information of the specific space object as tracking information.

[0334] By tracking the third orbital information over time, it becomes possible to determine the direction of intentional space object movement and predict its approach to other space objects in geostationary orbit. In particular, if the direction and magnitude of acceleration / deceleration change over time, the movement history of a specific space object can provide clues for inferring human intentions.

[0335] ***Description of the functions and effects of this embodiment*** If a space object A other than a publicly known space object is detected by an SSA operator's monitoring device, there is a risk that it may be unknown debris or a space object behaving suspiciously. For this reason, it is necessary to quickly identify the orbital elements of the space object A and generate orbit prediction information. In order to understand the orbital elements of space object A for which there is no prior information, it is essential to make multiple measurements using the monitoring equipment of an SSA operator. In order to obtain highly accurate orbital information with minimal measurement error, it is reasonable to use a large number of monitoring devices distributed over a wide area to collect monitoring information using various monitoring methods, such as optical monitoring and radar monitoring, and calculate initial estimates of the orbital elements. If a single operator does not possess monitoring equipment using a variety of monitoring methods deployed over a wide area, it may be possible to obtain these from another operator. Furthermore, if publicly available orbital elements such as TLE (Two Line Element) already exist, the publicly available information may be used as the initial estimate.

[0336] The amount of measurement error varies depending on the monitoring method or performance, and the positional relationship with space object A. In addition, estimation errors are included depending on the algorithm used to calculate the orbital elements from the measurement results. Therefore, by repeating measurements after calculating the initial estimated values ​​of the orbital elements, it is possible to reduce measurement or estimation errors and calculate orbital elements with high accuracy. For the orbital elements of objects that move naturally without acceleration or deceleration, such as naturally occurring debris or man-made objects that have lost their function, it is possible to estimate the orbital elements with high accuracy by reducing longitude errors through multiple measurements.

[0337] However, if the propulsion device is operated artificially to accelerate or decelerate, the updated estimated values ​​of the orbital elements will exceed the range of measurement error or estimation error and will manifest as significant changes in the orbital elements, making it possible to identify objects that are accelerating or decelerating.

[0338] For naturally occurring debris or man-made objects that have lost their function, it is possible to predict their future trajectories based on physical phenomena. In contrast, for space objects with propulsion functions, the acceleration or deceleration effect contributes to the difficulty of predicting their future trajectories, leading to large prediction errors. This increases the relative distance that must be maintained to avoid close encounters or collisions, raising the risk of collisions.

[0339] Space objects that undergo artificial acceleration and deceleration include rockets that are continuing to fire during launch, or satellites or transport vehicles that are continuing to operate their propulsion systems for orbital transfer or orbital control. Other space objects include spacecraft traveling long distances for lunar or planetary exploration, and suborbital planes that accelerate and decelerate before and after ballistic flight. Another example is a space object that is leaking propellant from a propulsion system tank due to an in-orbit malfunction.

[0340] Among space objects that have acceleration and deceleration components, by disclosing the acceleration and deceleration vectors of space objects whose acceleration and deceleration vectors are known, such as rockets or suborbital transport vehicles, the effect is that it will be possible to improve the accuracy of future orbit predictions. In addition, for satellites in normal operation, while acceleration and deceleration are performed for orbital attitude control, the acceleration and deceleration vector averaged over a certain period to maintain a normal operating orbit may become zero, which can be used as a reference for predicting future orbits.

[0341] On the other hand, if a space object has malfunctioned and is leaking propellant from its tank, and is rotating, the acceleration / deceleration vector will change from moment to moment, making it difficult to predict its future orbit. Repeating measurements after the initial estimated values ​​of the orbital elements have been calculated has the effect of reducing measurement or estimation errors. Furthermore, repeating measurements two or more times makes it possible to determine whether acceleration or deceleration is occurring. Repeating measurements three or more times makes it possible to estimate the acceleration / deceleration vector. Repeating measurements four or more times makes it possible to estimate the time change in acceleration or deceleration.

[0342] Furthermore, by disclosing the time difference between orbital information updates and changes in acceleration / deceleration vectors as a change history for acceleration / deceleration vectors, it becomes possible to determine the uncertainty of future orbital information. Therefore, when a risk of approach or collision is predicted, it is possible to contribute to measures such as ensuring a large distance necessary to ensure flight safety.

[0343] In addition, when the acceleration / deceleration vector changes frequently, by frequently updating and re-measuring the predicted orbit, it is possible to repeatedly re-measure and track the space object A without losing sight of it.

[0344] SSA operators who monitor the same space object multiple times can assess whether the object is accelerating or decelerating by evaluating the fluctuations in updated orbital information relative to the predicted orbit. This has the effect of enabling appropriate future orbital information to be used to issue an appropriate warning to the management equipment of space object B when an abnormal approach or collision is predicted. Furthermore, if a space object moving artificially in space shows suspicious behavior that has not been made public, it will be possible to predict its future movement range and track it.

[0345] In the above first to seventh embodiments, each unit of each device and each system has been described as an independent functional block. However, the configuration of each device and each system does not have to be the same as that of the above-described embodiments. The functional blocks of each device and each system may have any configuration as long as they can realize the functions described in the above-described embodiments. Furthermore, each device and each system may be composed of one device or multiple devices.

[0346] In the above-described first to seventh embodiments, the terms "unit," "process," "procedure," "stage," "process," and "means" in the components of each device and each system can be interchanged or rewritten. For example, the "stage of paying insurance money" in the server described in the modified examples of the third and fourth embodiments can be interchanged as the "means of paying insurance money" or the "unit of paying insurance money." Furthermore, the information disclosure unit of the information management device 1000 described in the fifth embodiment can be interchanged as the information disclosure process, information disclosure stage, information disclosure processing, or information disclosure means.

[0347] Furthermore, it is possible to combine two or more parts of the first to seventh 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. In the first to seventh embodiments, any combination of the first to seventh embodiments may be used. In addition, in the first to seventh embodiments, any modification of the constituent elements may be used. Alternatively, in the first to seventh embodiments, any constituent element may be omitted.

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

[0349] 20 Satellite constellation, 21 Orbital plane, 22 Approach warning, 23 Collision warning, 25 Danger warning, 30, 30a, 30b Satellite, 31 Satellite control unit, 32 Satellite communication equipment, 33 Propulsion unit, 34 Attitude control unit, 35 Power supply unit, 40 Management business equipment, 41 Mega constellation business equipment, 42 LEO constellation business equipment, 43 Satellite business equipment, 44 Orbital transfer business equipment, 45 Debris collection business equipment, 46 Rocket launch business equipment, 47 SSA business equipment, 50 Space information recorder, 51 Orbital forecast information, 511, 521 Space object ID, 512 Forecast origin, 513 Forecast orbital elements, 514 Forecast error, 515 Forecast flight status, 52 Orbital performance information, 522 Actual origin, 523 Actual orbital elements, 524 Specific performance, 525 Actual flight status, 241 specific time, 242 actual position coordinates, 515 predicted flight status, 60 space object, 65 predicted dangerous object, 69 avoided space object, 70 Earth, 100, 100a collision avoidance support device, 110 recorder processing unit, 120 alarm control unit, 130 performance presentation unit, 131 collision record, 140 memory unit, 141 alarm issuance information, 150 avoidance decision unit, 160 machine learning unit, 401 flight forecast information, 402 flight performance information, 403 avoided object notification, 500 collision avoidance support system, 55 orbit control command, 501, 501a, 501b orbit forecast, 502, 502a, 502b error range, 600 satellite constellation formation system, 601 predicted collision object, 602 predicted approach object, 65 predicted dangerous object, 11, 11b Satellite constellation formation unit, 300 satellite group, 700 ground equipment, 510 orbit control command generation unit, 520 analysis and prediction unit, 910 processor, 921 memory, 922 auxiliary storage device, 930 input interface, 940 output interface, 950 communication device, 1000 information management device, 1100 information disclosure unit, 1400 memory unit, 503 rocket launch information, 810a first monitoring device, 840 second monitoring device, 710 space traffic management unit, 471 measurement error inspection device, 472 acceleration / decrease measurement object tracking device.

Claims

1. A collision avoidance support program for a collision avoidance support device that supports avoidance of collisions between multiple space objects flying in space, the collision avoidance assistance device includes a storage unit that stores orbit prediction information that is a predicted value of the orbit of each of the plurality of space objects; an alarm control process for determining whether or not a plurality of space objects whose positional relationship is dangerous at the same time exist as potential hazardous objects among the plurality of space objects based on the orbit forecast information, and outputting a danger alarm indicating the presence of the potential hazardous objects when it is determined that the potential hazardous objects exist; When the danger warning is output, an avoidance determination process is performed to determine an avoidable space object that is a space object for which an avoidance operation is to be performed, from among the space objects included in the predicted danger objects. A machine learning process that updates an algorithm for an avoidance determination process that determines an avoidable space object by machine learning using the determination result of the avoidable space object. A collision avoidance assistance program that causes a computer to execute the following: The collision avoidance assistance program causing a computer to execute a danger warning output process for identifying the presence of the potential dangerous object based on the orbit forecast information and outputting the danger warning before a collision occurs between the plurality of space objects; The danger warning output process includes: outputting the danger warning to an insurance company of a space insurance program that pays insurance money from insurance premiums collected in advance in the event of a collision between space object A and space object B among the plurality of space objects, and to a space object management company that manages at least one of the plurality of space objects; The collision avoidance assistance device The system acquires flight forecast information representing a forecast of the flight of each of the plurality of space objects from a management business device used by a management business that manages space objects, and sets, based on the acquired flight forecast information, a forecast origin of the orbit of each of the plurality of space objects, forecast orbital elements that specify the orbit, and forecast errors that are predicted in the orbit, as orbit forecast information; and includes a space information recorder that includes the orbit forecast information; The danger warning output process includes: A collision avoidance assistance program that determines whether or not the potential hazardous object exists based on the orbital forecast information provided by the space information recorder, and outputs the danger warning if it is determined that the potential hazardous object exists.

2. A collision avoidance support program for a collision avoidance support device that supports avoidance of collisions between multiple space objects flying in space, the collision avoidance assistance device includes a storage unit that stores orbit prediction information that is a predicted value of the orbit of each of the plurality of space objects; an alarm control process for determining whether or not a plurality of space objects whose positional relationship is dangerous at the same time exist as potential hazardous objects among the plurality of space objects based on the orbit forecast information, and outputting a danger alarm indicating the presence of the potential hazardous objects when it is determined that the potential hazardous objects exist; When the danger warning is output, an avoidance determination process is performed to determine an avoidable space object that is a space object for which an avoidance operation is to be performed, from among the space objects included in the predicted danger objects. A machine learning process that updates an algorithm for an avoidance determination process that determines an avoidable space object by machine learning using the determination result of the avoidable space object. A collision avoidance assistance program that causes a computer to execute the following: The collision avoidance assistance program causing a computer to execute a danger warning output process for identifying the presence of the potential dangerous object based on the orbit forecast information and outputting the danger warning before a collision occurs between the plurality of space objects; The danger warning output process includes: outputting the danger warning to an insurance company of a space insurance program that pays insurance money from insurance premiums collected in advance in the event of a collision between space object A and space object B among the plurality of space objects, and to a space object management company that manages at least one of the plurality of space objects; The collision avoidance assistance device The system acquires flight forecast information representing a forecast of the flight of each of the plurality of space objects from a management business device used by a management business that manages space objects, and sets, based on the acquired flight forecast information, a forecast origin of the orbit of each of the plurality of space objects, forecast orbital elements that specify the orbit, and forecast errors that are predicted in the orbit, as orbit forecast information; and includes a space information recorder that includes the orbit forecast information; The collision avoidance assistance program When the danger warning is output, the computer is caused to execute a space object to be avoided determination process for determining the space object to be avoided; The space object to be avoided determination process includes: A collision avoidance support program that determines the space objects to be avoided among the space objects included in the predicted hazard objects based on the orbit forecast information provided by the space information recorder.

Images