JP7486295B2 - Space insurance support device, collision insurance execution device, insurance payment system, and space insurance program - Google Patents

Description

The present invention relates to a space insurance support device, a collision insurance execution device, an insurance payment system, and a space insurance program.

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 increasing.
With the rapid increase in space objects such as satellites and space debris in outer space, there is an increasing need for international rules in space traffic control (STM) to avoid collisions of space objects.

Measures are also needed for avoidance actions in the event that a collision is predicted in advance. In manned space stations or geostationary satellites operated by satellite communication operators, avoidance actions are implemented when a collision is predicted. However, in an environment where satellites from multiple operators are densely concentrated in low orbit altitude, with some equipped with evasive action functions and others not, it is difficult to formulate unified rules for avoidance actions. This is because when satellites that take evasive action and those that do not are mixed in a dense area, it creates a new risk of collision between satellites that have taken evasive action.
Traditionally, there has been a business model in which space insurance covers losses in the event of a rocket launch failure due to an accident or a satellite losing functionality due to an accident in orbit.

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

JP 2017-114159 A

Collision accidents that can be easily inferred using current technology can no longer be considered accidental, and a new mechanism for compensating for damages is necessary. Furthermore, a mechanism for covering insurance costs including higher-level damages would result in a surge in insurance rates if the total amount of damages were to become huge, and there is a risk that the space insurance system itself would collapse. At present, there are no established international rules regarding responsibility and compensation obligations for collisions in outer space, and space law is still under discussion.
However, Patent Document 1 does not describe a mechanism for compensating for damages caused by a collision accident in outer space.

The present invention aims to maintain the sustainability of the space insurance system and provide a mechanism for appropriate compensation for damages resulting from collision accidents in outer space.

The space insurance support device according to the present invention is a space insurance support device that supports the operation of space insurance that compensates for damage caused by a collision between multiple space objects flying in space, comprising:
The system is provided with a liability evaluation unit that evaluates accident liability and liability for damages based on the predicted orbit value of each of the plurality of hazardous objects and the actual orbit value of each of the plurality of hazardous objects when a danger warning is not issued, which indicates the presence of hazardous objects, which are multiple space objects whose positional relationships are dangerous at the same time, among the plurality of space objects, and when the hazardous objects collide with each other when a danger warning generated based on orbit forecast information, which is a predicted value of the orbit of each of the plurality of hazardous objects, is not issued.

In the space insurance support device according to the present invention, when a collision occurs between objects that are considered to be dangerous and a danger warning has not been issued, the liability assessment unit assesses accident liability and liability for damages based on the predicted orbit values and actual orbit values of each object that is considered to be dangerous. Therefore, the space insurance support device according to the present invention has the effect of being able to appropriately compensate for damages that accompany a collision accident in space.

An example of multiple satellites working together to provide global communications services. An example of multiple satellites in a single orbital plane providing an Earth observation service. An example of a satellite constellation with multiple intersecting orbital planes near the poles. An example of a satellite constellation with multiple intersecting orbital planes outside of the polar regions. A diagram showing the configuration of a satellite constellation formation system. A diagram showing the configuration of satellites in the satellite constellation formation system. A diagram showing the configuration of the ground equipment for the satellite constellation formation system. An example of the functional configuration of a satellite constellation formation system. 1 is a configuration diagram of a collision avoidance support system according to a first embodiment; FIG. 4 is a flow diagram of a recorder process for setting orbit forecast information according to the first embodiment. FIG. 4 is a diagram showing an example of orbit forecast information according to the first embodiment. FIG. 11 is a flow diagram of a recorder process for setting track performance information according to the first embodiment. FIG. 4 is a diagram showing an example of track performance information according to the first embodiment. FIG. 4 is a flow diagram of an alarm control process performed by an alarm control unit according to the first embodiment. FIG. 4 is a diagram illustrating an image of the intersection of error ranges of two satellites according to the first embodiment. FIG. 13 is a diagram showing a state in which error ranges of two satellites overlap according to the first embodiment. FIG. 4 is a diagram showing a state in which the distance between two satellites is equal to or less than a proximity threshold according to the first embodiment. FIG. 4 is a diagram showing warning issuance information according to the first embodiment. 4 is a flow diagram of a result presentation process performed by a result presentation unit according to the first embodiment; FIG. FIG. 13 is a configuration diagram of a collision avoidance assistance device according to a modification of the first embodiment. FIG. 11 is a configuration diagram of a collision avoidance assistance device according to a second embodiment. FIG. 11 is a flow diagram 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. FIG. 11 is a flow diagram 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. A flow diagram of an avoidance decision process based on a condition such as whether or not a space object is in normal operation in the second embodiment. A flow diagram of an avoidance decision process based on a condition such as whether or not a space object belongs to a megaconstellation in embodiment 2. 13 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. 13 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 in the second embodiment. 13 shows an example of a summary of the avoidance decision process according to the second embodiment. 13 is an example of input information in machine learning processing according to the second embodiment. FIG. 11 is a configuration diagram of a space insurance support system and a space insurance support device according to a third embodiment. FIG. 11 is a flow diagram of space insurance support processing by a space insurance support device according to embodiment 3. 13 shows an example of information disclosure by a management business operator in accordance with embodiment 3 and an example of space insurance corresponding to the management business operator. 13 shows specific examples of insurance premium assessment processing and liability assessment processing relating to embodiment 3. 13 shows specific examples of insurance premium assessment processing and liability assessment processing relating to embodiment 3. An example of the risk of collision between space objects in routine and non-routine operations. An example of the risk of collision between a geostationary satellite undergoing orbital transfer and a space object in routine operation. An example of the risk of collision between a launched rocket and a mega-constellation. FIG. 13 is a configuration diagram of a collision insurance execution system and a collision insurance execution device according to a fourth embodiment. FIG. 13 is a flow diagram of a collision insurance execution process performed by the collision insurance execution device according to the fourth embodiment. FIG. 13 is a diagram showing space collision insurance according to embodiment 4. 13 shows an example of a functional configuration of a satellite constellation forming system according to a fifth embodiment. FIG. 13 is a configuration diagram of an information management system according to a fifth embodiment. FIG. 13 is a flow diagram of an information disclosure process according to the fifth embodiment. FIG. 13 is a flow diagram of a satellite constellation control process according to the fifth embodiment. FIG. 13 is a diagram showing the error range of the rocket launch forecast value and the satellite constellation in the fifth embodiment. FIG. 13 is a diagram showing the error range of the rocket launch forecast value and the satellite constellation in the fifth embodiment. FIG. 13 is a configuration diagram of an information management device according to a modified example of the fifth embodiment. FIG. 11 is a flow diagram showing a process of updating a collision avoidance algorithm based on a machine learning effect according to the second embodiment. FIG. 11 is a flow diagram showing a process of updating a collision avoidance algorithm based on a machine learning effect according to the second embodiment.

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

Embodiment 1.
An example of a satellite constellation that is the premise of the collision avoidance support system according to the following embodiment will be described.

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

FIG. 2 is a diagram showing an example in which multiple satellites in a single orbital plane provide an earth observation service.
Fig. 2 shows a satellite constellation 20 that realizes an earth observation service. In the satellite constellation 20 in Fig. 2, satellites equipped with earth observation equipment, which is a radio wave sensor such as an optical sensor or a synthetic aperture radar, fly in the same orbital plane at the same altitude. In this way, in a satellite group 300 in which the imaging range of the ground is time-delayed and subsequent satellites overlap, multiple satellites in orbit take turns taking ground images of a specific point on the ground in a time-division manner to provide an earth observation service.

In this way, the satellite constellation 20 is composed 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 business service company as shown in FIG. 1, or an observation business service company as shown in FIG. 2.

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

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

In particular, in recent years, the construction of large-scale satellite constellations consisting of hundreds to thousands of satellites has begun, increasing the risk of satellite collisions in orbit. In addition, the amount of debris, such as satellites that have become uncontrollable due to malfunctions or rocket debris, is increasing. Large-scale satellite constellations are also called mega-constellations. Such debris is also called space debris.
Thus, with the increase in space debris and the rapid increase in the number of satellites, including megaconstellations, there is an increasing need for space traffic control (STM).

In addition, to avoid collisions with space objects, there is an increasing need for post-mission disposal (PMD) after the completion of an on-orbit mission, or ADR, which allows failed satellites and floating rocket upper stages to be de-orbited by external means such as debris collection satellites. International discussions on the need for such ADR have begun, known as STM. Here, PMD is an abbreviation for Post Mission Disposal. ADR is an abbreviation for Active Debris Removal. STM is an abbreviation for Space Traffic Management.

In addition, with the strengthening of the Space Situational Awareness (SSA) system, including international cooperation, and the improvement of observation accuracy, it is now possible to monitor even smaller space objects. Also, the total number of space objects that can be monitored is increasing.

The collision avoidance assistance device 100 according to this embodiment assists in avoiding collisions between multiple space objects 60 flying in space. As described above, the risk of collisions between space objects 60 is increasing due to the rapid increase in space objects such as satellites and debris in outer space.

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

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

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.

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

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

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

The satellite control device 31 is a computer that controls the propulsion device 33 and the attitude control device 34, and includes a processing circuit. Specifically, the satellite control device 31 controls the propulsion device 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 propulsive force 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).
The attitude control device 34 is a device for controlling attitude elements such as a satellite attitude sensor, an actuator, and a controller. The attitude control device 34 changes each attitude element to a desired direction. Alternatively, the attitude control device 34 maintains each attitude element in a desired direction. The attitude control device 34 includes an attitude sensor, an actuator, and a controller. The attitude sensor is a device such as a gyroscope, an earth sensor, a sun sensor, a star tracker, a thruster, and a magnetic sensor. The actuator is a device such as an attitude control thruster, a momentum wheel, a reaction wheel, and a control moment gyro. The controller controls the actuator according to measurement data of the attitude sensor or various commands from the ground equipment 700.
The power supply unit 35 includes devices such as a solar cell, a battery, and a power control device, and supplies power to each device mounted on the satellite 30 .

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

FIG. 7 is a configuration diagram of a ground facility 700 provided in the satellite constellation forming system 600.
The ground equipment 700 controls programs of multiple satellites in all orbital planes. The ground equipment 700 is an example of a ground device. 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.

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 support device 100. The ground equipment 700 includes a processor 910 and 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 a signal line and controls the other hardware. The hardware of the ground equipment 700 is similar to the hardware of the collision avoidance support device 100 described later in FIG. 9.

The ground equipment 700 has, as its 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.

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 orbit control 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 realize 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.

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 of the multiple satellites 30 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.

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

The management business device 40 provides information about a space object 60, such as an artificial satellite or debris. The management business device 40 is a computer of an operator that collects information about a space object 60, such as an artificial satellite 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.

The megaconstellation business device 41 is a computer of a megaconstellation business operator that operates a large-scale satellite constellation, i.e., a megaconstellation business.
The LEO constellation business device 42 is a computer of a LEO constellation 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 operator that provides support for the orbital transfer of satellites.
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 operator that carries out the 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 situation monitoring business.

The management business device 40 may be any other device that collects information about space objects such as artificial satellites or debris and provides the collected information to the collision avoidance support device 100. In addition, when the collision avoidance support device 100 is mounted on a public server of the SSA, the collision avoidance support device 100 may be configured to function as the public server of the SSA.
The information provided from the management device 40 to the collision avoidance assistance device 100 will be explained in detail later.

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.

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

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. The storage unit 140 may also be provided separately in the memory 921 and the auxiliary storage device 922.

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 presenting unit 130.
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).

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, a CF, a 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.

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. The input interface 930 may be a port connected to a LAN (Local Area Network).
The output interface 940 is a port to which a cable of a display device such as a display is connected. Specifically, the output interface 940 is a USB terminal or a High Definition Multimedia Interface (HDMI (registered trademark)) terminal. Specifically, the display is a Liquid Crystal Display (LCD).

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.

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 a part or all of the collision avoidance assistance program may be incorporated into the OS.

The collision avoidance assistance device 100 may include multiple processors that replace the processor 910. These multiple processors share the task of executing a program. Each processor is a device that executes a program, just like the processor 910.

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

The "parts" of the collision avoidance support device may be read as "processing,""procedure,""means,""stage," or "step." Also, the "processing" of the recorder process, the alarm control process, and the performance presentation process may be read as "program,""programproduct," or "computer-readable recording medium on which a 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 collision avoidance assistance device is replaced with a "process,""procedure,""means,""stage," or "process." Also, 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. Also, each program may be provided as a program product.

*** Operation Description ***
The collision avoidance assistance process performed by the collision avoidance assistance device 100 according to this embodiment will be described with reference to Figs.

<Recorder processing (trajectory forecast information): S100>
Fig. 10 is a flow diagram of a recorder process for setting the orbit forecast information 51 according to this embodiment. Fig. 11 is a diagram showing an example of the orbit forecast information 51 according to this embodiment.

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 that manages the multiple space objects 60. As described above, the management business is a business that manages space objects 60 flying in space, such as satellite constellations, various satellites, rockets, and debris. Also, as described above, the management business devices 40 used by each management business are computers such as a mega constellation 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.

In step S102, the recorder processing unit 110 sets the forecast origin 512 of the orbits of each of the multiple space objects, the forecast orbit elements 513 that specify the orbits, and the forecast error 514 predicted in the orbits as orbit forecast information 51 based on the acquired flight forecast information 401. 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 orbits of each of the multiple space objects.

Based on the flight forecast information 401, the recorder processing unit 110 may set the forecast of the flight state of each of the multiple space objects as the forecast flight state 515 in the orbit forecast information 51. At this time, the recorder processing unit 110 sets the forecast flight state 515 of each of the multiple space objects to whether each of the multiple space objects is in a normal operation state or a non-normal operation state. The normal operation state is specifically a state in which the satellite is flying in an orbit in a normal operation. The non-normal operation state includes a launch transient state from the launch of each of the multiple space objects until it is inserted into the orbit, and a post-departure transient state from the departure of each of the multiple space objects from the departure of the orbit until it enters the atmosphere or is inserted into a disposal orbit.

An example of orbit forecast information 51 according to the present 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.

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

Forecast epoch 512 is the epoch predicted 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 Fig. 11, six Keplerian orbit elements are set as the predicted orbital elements 513.

The forecast error 514 is an error predicted for each orbit of multiple space objects. The forecast error 514 includes a heading error, an orthogonal error, and the basis for the error. In this way, the forecast error 514 explicitly shows the amount of error contained in the actual value along with the basis. The basis for the amount of error includes the measurement means, the contents of data processing performed as a means for improving the accuracy of position coordinate information, and some or all of the results of statistical evaluation of past data.

The forecast flight state 515 is a forecast of the flight state of each of the multiple space objects. In the forecast flight state 515, it is set whether the forecast of the flight state of each of the multiple space objects is a normal operation state, a launch transient state, or a post-separation transient state. In addition, the forecast flight state 515 may include whether or not avoidance operations will be performed, or whether or not autonomous avoidance operations will be performed.

In the orbit forecast information 51 according to the present embodiment, a forecast origin 512 and forecast orbital elements 513 are set for the space object 60. The forecast origin 512 and the forecast orbital elements 513 can be used to determine the time and position coordinates in the near future of the space object 60. For example, the time and position coordinates in the near future for the space object 60 may be set in the 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 near-future forecast values of the space object 60.

<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.

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.

In step S202, the recorder processing unit 110 sets the actual origin 522 of the orbit of each of the multiple space objects, the actual orbit elements 523 that specify the orbit, and the actual position coordinates 242 of each of the multiple space objects as orbit actual information 52 based on the acquired flight actual information 402. Then, the recorder processing unit 110 includes the orbit actual 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 actual information 52 based on the flight actual information 402. In this case, the recorder processing unit 110 sets whether each of the multiple space objects is in a normal operation state or an unnormal operation state in the actual flight state 525 of each of the multiple space objects. The unnormal operation state includes a launch transient state from launch of each of the multiple space objects to being put into orbit, and a post-departure transient state from leaving the orbit to atmospheric re-entry or being put into a disposal orbit.

An example of the track performance information 52 according to the present embodiment will be described with reference to FIG.
In the orbit performance information 52, a space object ID 521, an actual epoch 522, an actual orbit element 523, a specific performance 524, and an actual flight state 525 are set. In the specific performance 524, a specific time 241 and actual position coordinates 242 are set. That is, in the orbit performance information 52, information on the space object 60 at the specific time 241 is set.

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

Actual epoch 522 is the actual epoch of the orbit of each of the multiple space objects.
The actual orbital elements 523 are orbital elements that specify the orbit of each of the multiple space objects. The actual orbital elements 523 are the actual orbital elements of the orbit of each of the multiple space objects. In FIG. 13, the actual orbital elements 523 are set to six Keplerian orbit elements, similar to the predicted orbital elements 513.

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

Actual flight state 525 is the actual flight state of each of the multiple space objects. In actual flight state 525, whether the actual flight state of each of the multiple space objects is a normal operation state, a launch transient state, or a post-separation transient state is set. In addition, actual flight state 525 may include whether or not avoidance operations can be performed, or whether or not autonomous avoidance operations can be performed. The configuration of actual flight state 525 is similar to forecast flight state 515.

<Warning control process: S300>
FIG. 14 is a flow diagram of the warning control process by the warning control unit 120 according to the present embodiment.

In step S301, the warning control unit 120 determines whether or not there is a space object in a positional relationship that requires an alarm to be issued, based on the orbit forecast information 51. Specifically, the warning control unit 120 determines whether or not there are multiple space objects, among the multiple space objects, whose error ranges 502 overlap at the same time, as collision-predicted objects 601, based on the orbit forecast information 51. The warning control unit 120 also determines whether or not there are multiple space objects, among the multiple space objects, whose approach exceeds the approach threshold at the same time, as approach-predicted objects 602, based on the orbit forecast information 51. The collision-predicted objects 601 and approach-predicted objects 602 are examples of hazard-predicted objects 65, which are multiple space objects, among the multiple space objects, whose positional relationship is dangerous at the same time.

If a collision-predicted object 601 exists, proceed to step S302. If an approach-predicted object 602 exists, proceed to step S303. If neither a collision-predicted object 601 nor an approach-predicted object 602 exists, return to step S301.

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 anticipated object 601.
In step S303, the warning control unit 120 outputs a proximity warning 22 indicating that there is a possibility of the approaching object 602 approaching.

FIG. 15 is a diagram showing an image of the intersection of error ranges 502a, 502b of two satellites 30a, 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 the six orbital 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, 501b and error ranges 502a, 502b for the satellites 30a, 30b based on the orbit forecast information 51. Note that the orbit forecast 501 and the error range 502 are distinguished as to whether they correspond to the satellite 30a or the satellite 30b by the subscripts added to the symbols.

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 a plurality of space objects whose error ranges 502 overlap at the same time exist as collision-prone objects 601, based on the orbit forecast information 51. In FIG. 16, two satellites 30a and 30b are determined to be collision-prone objects 601.

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 approach threshold value.
The warning control unit 120 judges, 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 judging whether to issue a approach warning 22. In Fig. 17, two satellites 30a and 30b are judged to be predicted approach objects 602.

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

FIG. 18 is a diagram showing the warning issuance information 141 according to the present 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 are examples of a danger warning 25 that indicates the presence of multiple space objects 65 that are dangerous objects in terms of their positional relationship at the same time.

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

A specific example of satellite orbital information will be described below.
As shown in Fig. 11 and Fig. 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: Epoch (year and day)
・ Mean Motion (m): Mean Motion (circulation/day) or Semi-major Axis (km)
Eccentricity: Eccentricity (no unit)
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 (M): Mean Anomaly (degrees)

A format called TLE (Two Line Element) may also be used.

The accuracy of positioning satellites is directly affected by the time and position on the orbit and the timing of the positioning signal transmission. For this reason, satellite information such as almanac, ephemeris, or precise orbital ephemeris is used depending on the accuracy, distribution method, or difference between forecast and actual values.
In terms of accuracy, the relationship is: 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 coarse-precision almanac information for all satellites, while fine-precision ephemeris transmits information only from its own satellite.

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 re-enters the atmosphere or reaches a disposal orbit. Also, no orbit predictions for rocket launches have been made public.
At the very least, the location of the launch site, the planned launch time, and the planned flight route will be disclosed, with information accurate enough to verify whether there is any risk of collision with satellites owned by satellite constellation operators at altitudes of less than 600 km.

It is not necessary for the orbit forecast information 51 (public orbit forecast value information) and the orbit performance information 52 (precise orbital ephemeris performance information) to be stored in the same storage location. Orbit performance information 52 only needs to be in a state where it can be used when necessary, such as after a collision accident occurs. For example, when an insurance company uses it for its insurance business, it may be stored in a storage location that is disclosed only to the insurance company by the operator of the collision avoidance support device 100.

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, forecast orbital elements, and forecast error of the space object, and the estimated time or time zone of the collision occurrence when a collision between space object A and space object B included in the multiple space objects is predicted.

The space object information also includes trajectory performance information. The trajectory performance information includes the time of collision that is estimated in a post-mortem verification after a collision accident occurs between space object A and space object B, which are included in multiple space objects, position information of space object A at or immediately before that time, and position information of space object B at or immediately before that time.

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 launch plan time and orbit information of the rocket launch operator.

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

The space object information also includes orbital forecast information, which includes 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 orbit information during the orbital transfer process.

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 regular or non-regular. The orbit forecast information may also include whether or not avoidance operations can be performed. The orbit forecast information may also include whether or not autonomous avoidance operations can be performed.

***Description of Effects of This Embodiment***
According to the collision avoidance support device 100 of this embodiment, the recorder processing unit 110 acquires flight forecast information 401 representing a forecast of the flight of each of the multiple 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 orbit of each space object, which includes a forecast error, as orbit forecast information 51 in the space information recorder 50. Therefore, according to the collision avoidance support device 100 of this embodiment, by using the orbit forecast information 51 that takes into account the expected orbit error for each of the multiple space objects, there is an effect that collision avoidance can be appropriately supported.

Furthermore, according to the collision avoidance support device 100 of this embodiment, 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. 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, according to the collision avoidance support device 100 of this embodiment, there is an effect that the flight performance desired by the management business can be immediately presented.

In the collision avoidance support device 100 according to this embodiment, flight performance information 402 is acquired from the management business device 40. However, the collision avoidance support device may have a measuring means for measuring the flight state of a space object. In other words, the collision avoidance support device may have 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.

The collision avoidance support device 100 according to this embodiment can, for example, disclose predicted orbit information of a satellite at the scheduled launch time to a rocket launching company planning to launch a new rocket. This enables the rocket launching company 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 a comparison and verification of the predicted orbit and the actual orbit history.

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 ephemeris performance.
The satellites constituting the mega-constellation are capable of inter-satellite communication or inter-satellite distance measurement with satellites flying in front of or behind the same orbital plane, or with satellites flying in adjacent orbits. Therefore, by using measurement device information mounted on the satellites in the 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, it is possible to improve accuracy by statistical processing of a large number of satellites.

The collision avoidance support device 100 according to this embodiment is equipped with a space information recorder 50 and is mounted on ground equipment.

Voice recorders are installed in aircraft for the purpose of investigating aircraft accidents, and dashcams are installed in automobiles for the purpose of investigating automobile accidents and as evidentiary documents.
With the emergence of mega-constellation operators, satellite constellations with thousands of satellites built in low orbit altitudes of 600 km or less have a high risk of collision when new rockets are launched. Therefore, a "space information recorder," which should be called a satellite drive recorder, is needed for a purpose similar to the voice recorder or drive recorder mentioned above.
Even if an aircraft accident is an explosive accident, 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. In addition, since there is a pilot in an aircraft, the system is designed to record not only the information of the instruments but also the pilot's voice, so that a voice record remains so that it can be verified after the accident, including whether or not there is an abnormality in the instruments. In contrast, in the case of a satellite collision, the 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 not necessary, and the main purpose is to record the data of the onboard instruments. Therefore, after the flight history is acquired, the 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.

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 themselves. This means that 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 useful as a basis for verifying the accident situation.

In the collision avoidance assistance device 100 according to this embodiment, measurement information of an SSA asset, which is a ground observation device, may be used as a means for measuring flight performance information, i.e., precise orbital performance.
Recently, the development of SSSA assets using ground-based telescopes or radar has progressed, and the measurement accuracy has improved. SSA information providers can also handle satellite orbital history, which has the effect of allowing a third party to objectively verify it.

The collision avoidance assistance device 100 of this embodiment is equipped with an artificial space object equipped with an IC tag having a satellite identification ID, time, and location information, and is equipped with 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.
The satellite constellation is designed so that when the satellites approach each other within, for example, 100 km, the IC tags equipped on the satellites transmit radio waves for close-range communication that can be received by a trial-free omni-antenna. This allows the satellites to receive each other's satellite information when they approach each other, and if there are many opportunities for close encounters in a mega-constellation, the amount of orbital performance information that can be shared on orbit increases over time. In particular, when the actual measurement information of the satellite itself is more accurate than that of ground measurement means, the IC tags are effective as a means for acquiring highly accurate on-orbit information.

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 operators, orbit insertion operators, and debris collection operators 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 a highly valued asset, which could become a source of revenue for satellite operators.
There is also a high risk of a satellite colliding with a satellite in the megaconstellation when it de-orbits after completing its mission. Similarly, it may be possible to hold accountable the operators of the de-orbiting satellites or the debris collection operators who neglected to take collision avoidance measures for the orbital information they had made public, which would have the effect of turning satellite orbit information into a source of revenue.
Furthermore, operators who launch geostationary satellites into orbit first launch them into geostationary transfer orbit using a rocket, and then transfer them to geostationary orbit using the satellite's own propulsion system. During this process, there is a risk of collision with mega-constellation satellites, and similar effects are expected.

***Other configurations***
<Modification 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 functions described below.

The space information recorder is equipped with an insurance premium setting means for 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 multiple space objects. The insurance premium setting means sets the insurance premium rate based on the forecast error contained in the orbit forecast information.

The space information recorder also includes an insurance money assessment means for a space insurance program that pays insurance money from pre-collision premiums when space object A and space object B among multiple space objects collide. The insurance money assessment means extracts orbit performance information at the time when the space objects collide from the orbit performance information as a collision performance, and extracts orbit forecast information at the time when the space objects collide from the orbit forecast information as pre-collision forecast information. The insurance money assessment means assesses the insurance money based on a comparison between difference information A between the collision performance and pre-collision forecast information of space object A and difference information B between the collision performance and pre-collision forecast information of space object B.

Forecast errors include either the basis for the forecast error or the verification results of the forecast error, or both.

The space information recorder also has a means for outputting a danger warning to an insurance company and a management company that implement 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 multiple space objects.

The space information recorder also has a means for outputting orbit performance information to an insurance company and a management company that implement 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 multiple space objects.

The space information recorder also includes a means for outputting a danger warning to a debris recovery operator who recovers debris resulting from a collision between space object A and space object B among the multiple space objects, indicating that multiple space objects with dangerous positional relationships exist at the same time.

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, outputs a hazard warning, and determines which space object will undergo avoidance operations before the multiple space objects collide with each other. The space information recorder executes a collision avoidance support program that includes a hazard warning output means that determines whether or not a potential hazardous object exists among the multiple space objects based on orbit forecast information, and outputs a hazard warning if it is determined that a potential hazardous object exists. The space information recorder also executes a collision avoidance support program that includes an avoided space object determination means that determines which space object will undergo avoidance operations among the space objects included in the potential hazardous objects after the hazard warning is output.

The space information recorder also includes a disclosure threshold for determining whether or not to disclose orbit 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.

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

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 is specifically a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation of Gate Array.
The functions of the collision avoidance assistance device 100 may be realized by one electronic circuit, or may be distributed across a plurality of electronic circuits.
As another modification, some of the functions of the collision avoidance assistance device 100 may be realized by electronic circuits, and the remaining functions may be realized by software.

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

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 denoted by the same reference numerals, and the description thereof may be omitted.

In this embodiment, we will explain 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.

***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 the present embodiment includes an avoidance determination unit 150 and a machine learning unit 160 in addition to the functional elements of collision avoidance assistance device 100 according to embodiment 1. Other functional elements and hardware configurations are similar to those of embodiment 1. Furthermore, the collision avoidance assistance program according to the present embodiment is a program that realizes at least the functions of warning control unit 120, avoidance determination unit 150, and machine learning unit 160. That is, the collision avoidance assistance program according to the present embodiment causes a computer to execute at least warning control processing, avoidance determination processing, and machine learning processing.

The warning control unit 120 determines whether or not multiple space objects that are dangerous in terms of their positional relationship at the same time exist as predicted hazard objects 65 among the multiple space objects based on the orbit forecast information 51. If it is determined that a predicted hazard object 65 exists, the warning control unit 120 outputs a danger warning 25 indicating the presence of the predicted hazard object 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.

When the danger warning 25 is output, the avoidance determination unit 150 determines an avoidance space object 69 that is a space object for which avoidance operations are to be performed, among the space objects included in the predicted danger objects 65. The conditions used to determine the avoidance space object 69 are, for example, as follows.
The avoidance determination unit 150 determines the space objects 69 to be avoided based on whether each space object included in the anticipated danger objects 65 is a rocket at launch.
The avoidance determination unit 150 determines the space objects 69 to be avoided based on whether each space object included in the predicted danger objects 65 belongs to a megaconstellation.
The avoidance determination unit 150 determines the space object 69 to be avoided based on whether each space object included in the anticipated danger object 65 is in a normal operating state or a non-normal operating state.
The avoidance determination unit 150 determines the space objects to be avoided 69 based on whether each space object included in the anticipated danger objects 65 is an orbital transfer satellite 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 objects 65 has a collision avoidance function.
The avoidance determination unit 150 determines the space objects 69 to be avoided based on whether each space object included in the predicted danger objects 65 is located in a dense orbit.

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

The machine learning unit 160 updates the algorithm of the avoidance decision process that determines the avoidance space object 69 by machine learning using the result of determining the avoidance space object 69, i.e., the decision result by the avoidance decision unit 150.

*** Operation Description ***
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 multiple potential danger objects 65 that are space objects whose positional relationship is dangerous at the same time.

<Avoidance Decision Processing>
22 and 23 are flow diagrams 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 are examples 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.

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 by 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 the space object. The avoidance decision unit 150 may obtain the type of the space object from the management table by using the space object ID, and determine whether or not the space object is an artificial satellite.
If space object A is an artificial satellite, in step S102, the 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.

If the space object B is not an artificial satellite, in step S103, it is determined whether or not the space object B is a rocket. Specifically, the avoidance determination unit 150 determines whether or not the space object is a rocket 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 the space object. The avoidance determination unit 150 may obtain the type of the space object from the management table using the space object ID and determine whether or not 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 an artificial satellite and space object B is not a rocket, i.e., debris (step S104a), the process proceeds to step S106.
In step S105, if space object A belongs to a megaconstellation, processing proceeds to step S106.
In step S105, if space object A does not belong to a megaconstellation, processing proceeds to step S111.

If it is determined in step S101 that the space object A is not an artificial satellite, in step S107, the avoidance determination unit 150 determines whether or not the space object A is a rocket.
If space object A is a rocket in step S107, then in step S108, the avoidance decision 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, the avoidance determination unit 150 determines whether or not 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, processing proceeds to step S111.

If it is determined in step S108 that the space object B is not an artificial satellite, 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 the application of the avoidance determination process.
If it is determined in step S112 that the space object B is not a rocket, i.e., that the space object B is debris, the space object A is a rocket and the space object B is debris (step S114). In this case, the process proceeds to step S106.

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.

If space object A is not a rocket in step S107, then in step S115, the avoidance decision unit 150 determines whether or not space object A is debris.
If space object A is determined to be 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 the space object B is an artificial satellite, the space object A is debris and the space object B is an artificial satellite (step S117). In this case, the process proceeds to step S111.

If it is determined in step S115 that space object A is not debris, in step S121, the avoidance decision unit 150 performs object definition learning processing and algorithm update processing.

If it is determined in step S116 that the space object B is not an artificial 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). At this time, 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 the application of the avoidance decision process.

FIG. 24 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 this embodiment.
Fig. 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 operation or non-normal operation. The process in Fig. 24 is referred to as M1 process. The normal operation state is specifically a state in which a satellite flies in an orbit in normal operation. The non-normal operation state includes a launch transient state from launch of each of the multiple space objects to being inserted into the orbit, and a post-departure transient state from leaving the orbit of each of the multiple space objects to being inserted into the atmosphere or into a disposal orbit.

In step S201, the avoidance decision unit 150 determines whether the space object A is in a normal operation state or a non-normal operation state. Specifically, the avoidance decision unit 150 determines whether the space object A is in a normal operation state or a non-normal operation state by using the predicted flight state 515 of the orbit forecast information 51 shown in FIG.
In step S201, if space object A is in a normal operating state, in step S202, the avoidance decision unit 150 determines whether space object B is in a normal operating state or a non-normal operating state.
In step S202, when space object B is in a normal operation state, both space object A and space object B are in a normal operation state. At this time, in step S203, the avoidance decision unit 150 determines that space object A and space object B will not collide.

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 operation state, space object A is in an unnormal operation state, and space object B is in a normal operation state. At this time, in step S206, the avoidance determination unit 150 determines that space object A in an unnormal operation state is an avoidance space object 69 that should be avoided.
In step S205, if space object B is in an unsteady operational state, both space objects A and B are in unsteady operational states. In this case, in step S207, the avoidance determination unit 150 does not determine the avoidance space object 69, since this is a case in which individual adjustment is performed.

In step S202, if space object B is in an unsteady operational state, space object A is in a steady operational state and space object B is in an unsteady operational state. At this time, in step S204, the avoidance determination unit 150 determines that space object B, which is in an unsteady operational state, is an avoidance space object 69 that should be avoided.

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.
Fig. 25 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 belongs to a megaconstellation or not. The process in Fig. 25 is referred to as M2 process.

In step S301, the avoidance determination unit 150 determines whether or not the space object A belongs to a mega constellation. Specifically, the avoidance determination unit 150 determines whether or not the space object A belongs to a mega constellation using the space object ID 511 of the orbit forecast information 51 shown in FIG. 11. For example, the collision avoidance support device 100 may have a management table that associates the space object ID with the management operator of the space object. The avoidance determination 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 mega constellation.
In step S301, if space object A belongs to a megaconstellation, 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, the avoidance decision unit 150 determines that space object A and space object B will not collide.

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 in which individual adjustment is performed.

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.

FIG. 26 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 this embodiment.
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 that is in a transition orbit or not. The process in FIG. 26 is referred to as M3 process.

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

If space object A is not an orbital transfer satellite in step S401, the avoidance decision 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, in step S405, the avoidance decision unit 150 determines whether or not the space object B is an orbital transfer satellite.
In step S405, if the space object B is an orbital transfer satellite, the space object A is not an orbital transfer satellite, and the 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 the space object A is an avoidance space object 69 that should be avoided.

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

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

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 in which individual adjustment is performed.

FIG. 27 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 this embodiment.
Fig. 27 shows an example of a process for determining a space object 69 to be avoided based on a condition such as 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.

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 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.

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

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

If it is determined in step S501 that space object A does not have a collision avoidance function, 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, in step S506, the avoidance determination unit 150 determines whether the space object B is in normal operation in a dense orbit.
In step S506, if the space object B is not in normal operation in a dense orbit, in step S507, the avoidance determination unit 150 determines that the space object B having a collision avoidance function is an avoidance space object 69 that should be operated in an avoidance manner.

If it is determined in step S502 that space object B does not have a collision avoidance function, processing proceeds to step S506.
Also, in step S503, if space object A does not enter a dense orbit, processing proceeds to step S507.

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

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 avoidance space object 69 is not determined due to individual adjustment or a determination that it is not applicable, the avoidance determination unit 150 may output the avoidance object notification 403 including a message indicating that the avoidance space object 69 is not determined.

FIG. 28 is an example of a summary of the avoidance decision process according to the present embodiment.
The exemplary basis for the avoidance decision process illustrated in Figures 22-27 is to determine an appropriate avoidance space object 69 while overcoming the following possibilities:
- If a collision occurs in a megaconstellation, there is a risk of a chain reaction.
- Areas such as near LEO sun-synchronous LST 10:30 or the polar regions are densely populated with many satellites from multiple operators, and there is a risk of a chain reaction if a collision occurs.
- High-precision orbit information from mega-constellations is held by the mega-constellation operators and is not necessarily made public as forecast values.
- Rocket launch operators and operators transferring geostationary satellites from the geostationary transfer orbit (GTO) perigee to geostationary orbit are at risk of collision with mega constellations, but they cannot necessarily choose the timing of passing through the danger zone.
-If multiple operators of densely packed tracks take evasive action without coordinating with each other, there is a risk of a collision at the desired destination.
- Dense orbits may include satellites that do not have the ability to take collision avoidance measures.

<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 result of the avoidance decision unit 150 will be described.

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 results of the M1 process to the M4 process are inconsistent, the machine learning unit 160 adjusts them individually.

FIG. 29 is 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 the M1 process to the M4 process, add new judgment criteria, and, in order to make it a judgment process that should be added when modifying the flowchart in the future, depending on the content of the individual adjustment that will occur in the future, the judgment process, and the judgment result.
Perform processes such as optimizing the flow of flowcharts.

<Avoidance action 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 support 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.

Here, an example of an algorithm when a collision warning or approach warning is issued to a mega-constellation is shown below, which is an algorithm of a satellite constellation forming unit that generates an orbital control command.
Set the following information as input conditions.
- Whether the orbital altitude at which the constellation is in operation has been passed - The angle of incidence at that orbital altitude - Information on the object to be collided with or approached By setting the above information as input conditions, the system will output the judgment result of whether or not evasive action should be taken based on the following judgment criteria, and the entity that should take evasive action.

The grounds for judgment on individual items are as follows:
- It is predicted that a huge number of warnings will be issued in mega-constellations, making it difficult to take evasive action in response to all warnings.
- If some of the satellites in a megaconstellation take evasive action, there is a risk of colliding with other satellites.
- It is necessary to compare the risks of taking evasive action with the risks of not taking evasive action to determine whether or not to take evasive action.
- Only mega constellation operators have high-precision orbital information forecast values, and if they keep these values confidential, only the mega constellation operators will be able to perform highly accurate collision prediction analysis.
- Mega constellation operators need to share the results of their risk analysis and their policies on whether or not to take evasive action with stakeholders who are subject to collisions.
- There is a possibility that the algorithm will overturn its initial judgment and make alternative suggestions.

48 and 49 are flow diagrams showing the process of updating the collision avoidance algorithm according to this embodiment through the machine learning effect.
In the collision avoidance assistance device 100a, the collision avoidance algorithm is updated by the machine learning effect.

Until the process is established, it will be necessary for stakeholders to reconcile their opinions, so the algorithm to be implemented on the computer will be part of this. Machine learning will be used to create a decision-making process that should be added when modifying the flowchart in the future, depending on the content of future stakeholder response policy adjustments, as well as the decision-making process and results. 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.

In a situation where mega constellation operators are faced with so many collision warnings that they cannot handle them all on a daily basis, they may conclude that "even if there is a risk of collision, we will not take evasive action." From the perspective of the other party in the collision, the mega constellation operator may be adamant that evasive action should be taken. In this case, it is highly likely that a decision will be reached after reconciling opinions through a consensus system each time. 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 machine learning new patterns of such decision-making processes, it is possible to modify or add to the processing flow.

In this embodiment, the collision avoidance assistance program that realizes the following functions has been described.
The collision avoidance support program causes the computer to execute a danger warning output process for identifying the presence of a potential dangerous object based on orbit forecast information and outputting a danger warning before a collision occurs between the 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 when space object A and space object B among the multiple space objects collide, and to a space object management company that manages at least one of the multiple space objects.

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 dangerous object exists based on the orbit prediction information provided by the space information recorder, and outputs a danger warning if it is determined that a dangerous object exists.

When a danger warning is output, the collision avoidance assistance program causes the computer to execute a space object to be avoided determination process that determines a space object to be avoided. The space object to be avoided determination process determines a space object to be avoided that is included in the predicted danger objects, based on the orbit forecast information provided by the space information recorder.

***Description of Effects of This Embodiment***
The collision avoidance support device according to the present embodiment can show the grounds and results of identifying the space objects for which avoidance action should be taken to the respective jurisdiction holders of multiple space objects that are predicted to be dangerous objects, and can request and support the avoidance action. Therefore, the collision avoidance support device according to the present embodiment has the effect of being able to appropriately avoid collisions with space objects.

***Other configurations***
<Modification>
The collision avoidance support system acquires space object information from a space information recorder that records space object information acquired from a management business device used by a management business that manages multiple space objects, and supports collision avoidance between the multiple space objects.
The collision avoidance support system according to this embodiment may include a database for storing space object information acquired by the space information recorder, and a server having an 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) by 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.

The server comprises the following stages:
- A stage in which a notification is received from the space information recorder that a collision between space object A and space object B, which are included in the 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 of space object A, and the orbital forecast information of space object B from the space information recorder.
- A step of reporting a danger alert, which is 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.
- A stage of requesting collision avoidance action from the selected collision avoidance operator.

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 whether the space object is a routinely operated object or a non-routine space object as an evaluation index.
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 whether or not the space object is a mega constellation satellite as an evaluation index for selection.
In addition, the avoidance operator determination means selects a debris removal operator as the collision avoidance operator when both space object A and space object B are not equipped with a collision avoidance function.

The space object information includes the history of past space collision incidents.
The collision avoidance operator determination means adds an evaluation index in the process of determining collision avoidance operators in past space collision accidents to the selection evaluation index, and selects a collision avoidance operator.

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 warning, which is a collision warning or an approach warning, 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.

The database acquires from the space information recorder the scheduled launch time and launch forecast information of space object C obtained from the rocket launch operator by the space information recorder.
The server comprises the following stages:
- A step of reporting the launch forecast information for the scheduled launch time information to a mega-constellation operator that manages a mega-constellation satellite that is at risk of collision with space object C.
- A stage where the avoidance operator determination means requests mega constellation operators to take collision avoidance actions or to provide information necessary to avoid collisions during rocket launches.
A step of reporting space object information of a mega-constellation satellite with which space object C is at risk of collision to the rocket launch operator.

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 orbital transfer time to the mega-constellation operator that manages the mega-constellation satellites with which there is a risk of collision with space object D.
A step in which the avoidance operator determination means requests the megaconstellation operator to take collision avoidance action or to provide information necessary for collision avoidance during orbital transfer.
A step 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.

The database obtains from the space information recorder the scheduled de-orbit time and de-orbit forecast information for space object E obtained from the satellite operator performing the de-orbit using the space information recorder or from the debris collection operator.
The server comprises the following stages:
- A step of reporting de-orbit forecast information at the scheduled de-orbit time to a mega-constellation operator that manages a mega-constellation satellite with which there is a risk of collision with space object E.
A stage in which the avoidance operator determination means requests the mega constellation operators to take collision avoidance action or to provide information necessary for collision avoidance at the time of deorbiting.
A step of reporting space object information of mega-constellation satellites that are at risk of collision with space object E to a deorbiting satellite operator or a debris recovery operator.

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 has 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 has 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 when a space object de-orbits.
This will have the effect of encouraging stakeholders to make efforts to reduce accident liability and avoid collisions.

The server also includes a step of providing the launch time information that can ensure flight safety during rocket launch.
The server also includes a step of providing the transfer time information that can ensure flight safety during orbit transfer.
The server also includes a step of providing the de-orbit time information that can ensure flight safety during de-orbit.

Embodiment 3.
In this embodiment, the following will mainly describe the differences from the first and second embodiments. Note that the same components as those in the first and second embodiments are given the same reference numerals, and the description thereof may be omitted.

In this embodiment, we will explain a space insurance support system 550 and a space insurance support device 200 that support the operation of space insurance that compensates for damage caused by collisions between multiple space objects flying in space.

***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.

The functions of the responsibility 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. The storage unit 230 may also be provided separately in the memory 921 and the auxiliary storage device 922.

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 of this embodiment is a program that realizes the functions of the liability assessment unit 210 and the insurance premium assessment unit 220. In other words, the space insurance support program of this embodiment causes a computer to execute a liability assessment process and an insurance premium assessment process.

*** Operation Description ***
The space insurance support process performed by the space insurance support device 200 according to this embodiment will be described with reference to FIG.

<Space insurance support processing: S200>
In step S21, the responsibility assessment unit 210 assesses accident liability and liability for damages in the case where the hazard anticipated objects 65 collide with each other when the hazard 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 of the hazard anticipated objects 65 and the actual trajectory values of each of the hazard anticipated objects 65.
Specifically, the liability 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 liability assessment unit 210 assesses the accident liability and damages liability based on the space information recorder 50 that includes the orbit forecast information 51 and the orbit performance information 52 in which the orbit performance value is set.

In step S22, the insurance premium assessment unit 220 assesses the insurance premiums for 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 for the management company so that the smaller the forecast error 514, the lower the insurance premium rate.

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

Below is a description of a specific example of space insurance support processing.

<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 value of the orbit of a space object is made public as orbital forecast information 51 and it is possible to foresee that a collision will not occur.

FIG. 32 is a diagram showing an example of information disclosure by a management business operator and an example of space insurance corresponding to the management business operator.
As stakeholders in space operations, 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 higher, while others plan to deploy a few satellites at orbital altitudes of 300 to 600 km.
There are also LEO constellation operators that operate multiple Earth observation satellites in a specific orbital plane in low Earth orbit. There are also satellite operators that operate commercially with single satellites. In addition, debris collection operators are scheduled to appear for the purpose of debris collection.
Space objects owned by these management companies are at risk of colliding with each other. The risk of collision is particularly high during non-routine operations, such as during the orbit insertion stage or when leaving the orbit after the mission is completed. In addition, operators who insert geostationary satellites into geostationary orbit transfer their satellites to geostationary orbit using their own propulsion devices after rocket launch, and so there is a risk of collision with satellites in other orbits during this process.

It would be effective as a collision avoidance measure if these operators could publicly disclose the time and orbital information forecasts they hold in advance, and predict that collisions would not occur. On the other hand, if a collision accident were to occur, it would be effective in clarifying the occurrence of the accident and responsibility for damages if it were possible to clearly show evidence that one of the objects deviated from the forecast value and collided with an object that was operated according to the initial forecast, using the actual orbital ephemeris performance as the basis for judgment against the forecast value. As a means of covering the costs of damages, it would be effective to cover the costs with space insurance premiums.

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

For the purpose of investigating aircraft accidents, aircraft are equipped with voice recorders, and for the purpose of investigating and providing evidentiary documentation for automobile accidents, automobiles are equipped with drive recorders.
A satellite constellation with thousands of satellites constructed in a low orbit altitude of 600 km or less has a high risk of collision when a new rocket is launched. For this reason, it is thought that a "space information recorder," which should be called a satellite drive recorder, will be needed for a purpose similar to that of a voice recorder and a drive recorder.

The difference between aircraft accidents and satellite collisions is that in aircraft accidents, even if the accident is explosive, 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. Also, since there is a pilot in an aircraft, not only information from the measuring instruments but also the pilot's voice is recorded, so that a voice record remains that can be verified after the accident, including whether or not there were any abnormalities in the instruments. In contrast, in a satellite collision, the 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 not necessary, and the main purpose is to record the data from the onboard measuring instruments, and after acquisition, the data must be transmitted to the ground or another satellite as quickly as possible, and the data up to just before the collision accident must be stored in another location.

The difference between car accidents and satellite collisions is that the main purpose of a car's dashcam is to record the vehicle's operating conditions and the surrounding conditions at the time of the accident in order to verify or provide evidence of who is responsible for the accident. If the location information of the accident is recorded in the event of a head-on collision, the lane in which the accident occurred can be verified, and it is easy to clarify who is responsible for the accident. On the other hand, it does not have the purpose of transmitting its own future forecast information in advance. Also, since the concept of driver negligence exists, it is highly effective in clarifying who is responsible and as evidence for damages. In contrast, in the case of satellite collisions, there is currently no concept equivalent to a lane, and there are no drivers, so negligence liability for satellite collisions is not held, and the concept of perpetrator and victim has not existed.

At present, there are no established international rules regarding who is responsible and who is liable for damages in the event of a collision accident. However, as a means of avoiding future collision accidents, it is reasonable for stakeholders related to space objects to share the orbital forecast values of space objects in advance and take avoidance measures if a collision risk is foreseen. An effective avoidance measure is for one of the parties that foresees a collision to take evasive action, and if both parties take evasive action, mutual cooperation is essential. As a result of both parties carrying out autonomous collision avoidance operations, the risk of collision should be avoided. It is also important to avoid the risk of collision with another satellite when collision avoidance operations are carried out.
If a collision occurs despite measures to avoid collisions being taken, 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.

Figures 33 and 34 show some specific examples of the insurance premium assessment process and the liability assessment process according to this embodiment.

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

The predicted orbit of a space object includes time error and position estimation error. Since a satellite flies at a speed of about 7 to 10 km per second, the distance associated with the time error in the satellite's direction of travel becomes large. Expressed geometrically, this results in a space on an elliptical cone with the space object at its center, which is called an error bubble. The 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 provided by the satellite itself, or distance measurement data from ground-based telescopes, and the amount of error is also diverse. Usually, satellite operators have highly accurate orbit forecast values and orbit performance values for their own satellites. However, the accuracy of orbit forecast values owned by external operators and SSA operators who distribute measurement information from the ground has a large error.
When predicting the risk of collision based on the orbit forecast value, there is a high possibility that large error bubbles with large amounts of error will come into contact with each other, so the collision risk is high. Also, as shown in the upper part of Figure 33, the smaller the amount of error, the smaller the collision risk. Also, the smaller the amount of error, the smaller the difference between the orbit forecast value and the orbital ephemeris performance. Also, in the unlikely event that the orbit performance value of an operator with a small estimated error amount deviates from this, the insurance operator may be exempt from liability.
For this reason, it is reasonable for insurance companies to set lower insurance rates for companies with smaller estimation errors, since the risk of causing an accident is lower for such companies.

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

The forecast error 514 is a self-reported value by the management company. Since multiple management companies use different evaluation criteria, other means of evaluating the objective validity of the insurance premium rate 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.

<Specific example 3 of insurance premium assessment processing>
The insurance premium assessment unit 220 assesses the insurance premium so that the smaller the difference between the predicted track value and the track actual value, the higher the insurance premium to be paid.

When 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. In cases where it is not possible to determine 100% responsibility between the assailant and the victim, and although both parties bear some responsibility, contingency cannot be completely denied, and insurance needs to be paid, it is reasonable that the smaller the difference between the predicted value and the actual orbital ephemeris, the higher the insurance payout will be.

<Specific example 1 of responsibility evaluation processing>
The liability evaluation unit 210 evaluates the liability for accidents and the liability for damages so that the smaller the difference between the orbit forecast value and the orbit actual value, the less the liability for accidents and the liability for damages in the event of a collision. In other words, in the space insurance 201, the smaller the difference between the space information recorder forecast value and the orbital ephemeris actual value, the less the basis for determining the liability for accidents and the liability for damages in the event of a collision accident.

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.

<Specific example 2 of responsibility evaluation processing>
The liability assessment unit 210 assesses liability for accidents and liability for damages so as to provide an exemption clause for accidents that occurred despite being foreseeable based on the predicted values of the trajectory.

In terms of predicting collision accidents, in addition to the efforts of each operator, it is also effective for SSA operators to issue collision warnings.
An operator who fails to avoid a foreseeable collision is in breach of the 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 maneuvers 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.

<Specific example 3 of responsibility evaluation processing>
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 carries out a rocket launch business 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.

In mega-constellations consisting of several thousand satellites at altitudes of 600 km or less, it is easy to imagine that debris scattered in a collision accident will 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 the occurrence of a chain reaction is accidental. In addition, there is a risk that the total amount of damage will be unlimited, so it is appropriate to exempt high-level damage from launch third-party liability insurance, and since the total scale of damage is kept within a predictable scale, it is effective in ensuring the sustainability of the space insurance system.

Here, we assume a constellation of 2,400 satellites, with 40 orbital planes at an altitude of about 340 km that pass through the polar regions, and 60 satellites deployed in each orbital plane. Since all satellites pass through the polar regions, extremely strict timing management is required for all satellites in order to prevent collisions in a time-division manner. The number of satellite orbits at an altitude of 340 km is about 15.7, with one orbit taking about 90 minutes and the satellite speed being about 7.7 km/sec. The distance between satellites in one orbital plane is about 700 km, so the waiting time from when a satellite in a specific orbital plane passes until the subsequent satellite returns is about 90 seconds. In order to pass 40 satellites during this time, it takes about 2 seconds for 90 seconds/40 planes. This is an extremely strict management requirement in terms of the technological level of satellite development, and there is a good possibility of collisions due to unexpected orbital malfunctions due to error factors.

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

<Specific example 4 of responsibility evaluation processing>
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.

For satellites that are routinely operated in roughly circular orbits, rockets or debris collection satellites that irregularly enter the same orbital plane under orbital conditions with different circularity, such as elliptical orbits, pose a risk of collision. Although they bear a proportionate share of responsibility when a collision occurs, in the case of high-level damage caused by scattered debris, if the cause is a crowded situation such as a mega-constellation, it is difficult to say that it is reasonable to cover damages with launch insurance or launch third-party liability insurance. Therefore, it is reasonable to cover high-level damage with the satellite's life insurance or orbit third-party liability insurance.

<Specific example 5 of responsibility evaluation processing>
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 groups of satellites.

In mega-constellations, the risk of a chain reaction of collisions is anticipated, so it is unreasonable to attribute compensation for higher-level damage entirely to the initial collision.
And in some cases, it makes more sense to insure a constellation of satellites rather than insuring thousands of them individually.
If megaconstellation operators were to recognize the risk of chain collisions in advance, pay insurance premiums, and cover damages with insurance in the event of an accident, insurance rates could be set according to the probability of accidents occurring, high-level damage predictions, and the total amount of insurance premiums to be paid. This would have the effect of allowing the construction of an insurance system without adversely affecting the entire space insurance system.

<Specific 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 accident liability and damages liability so as to give a heavier liability for the accident and damages liability to the management company of the space object undergoing non-routine operation in the event of a collision between a space object undergoing routine operation and a space object undergoing non-routine operation.

The operation of a satellite that continues in orbit for several years to more than 10 years until the end of its life is called routine operation. The satellite orbit in routine operation maintains a certain degree of reproducibility based on physical phenomena. In addition, long-term operation is often performed in an approximately circular orbit. A group of satellites that are routinely operated in an approximately circular orbit, maintaining a constant phase interval at the same altitude, will not collide even if dozens of them fly simultaneously in the same orbital plane.
On the other hand, in a transitional orbit leading up to orbit insertion, or in non-routine operations such as rocket launches, there is a risk of collisions occurring due to non-routine intrusions into the same orbital plane under orbital conditions with different circular values, such as elliptical orbits. In particular, if an intrusion into an orbital plane at a shallow relative angle carries a risk of collisions with multiple satellites. For this reason, it is reasonable to consider setting heavy liability for accidents and compensation.

<Specific example 7 of responsibility evaluation processing>
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 accident liability and damages liability so as to give a greater weight to the accident liability and damages liability of the management company of the space object in regular operation in the event of a collision between a satellite in the middle of an orbital transfer from a geostationary satellite and a space object in regular operation.

A geostationary satellite is usually launched to a geostationary transfer orbit (GTO) by a rocket, and then the propulsion device equipped on the geostationary satellite is operated to transfer the satellite to a geostationary orbit. In this case, for example, in a method of operating a chemical propulsion device called an apogee kick motor at the apogee (apogee), it is difficult for the geostationary orbit launch operator to avoid collisions because the timing of operation cannot be arbitrarily selected. Also, unlike rocket launch operators, it is difficult to avoid collisions by looking at all the satellite information of the megaconstellation, including the uncertainty after the time has passed since launch.
For mega-constellation operators, it is self-evident that satellites launched into geostationary orbit will undergo orbital transfer above the equator, and since the feasibility of autonomous collision avoidance functions has also been touted, it is reasonable to attribute responsibility to collision avoidance.

<Specific example 8 of responsibility evaluation processing>
FIG. 37 is a diagram showing the collision risk between a launched rocket and a megaconstellation.
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.

There is a concept of a mega-constellation, with around 2,500 satellites deployed at three different altitudes around 340 km above sea level. However, there are significant constraints on collision avoidance during rocket launch, which could pose excessive risks to insurance companies.
For example, if we assume that there are about 40 orbital planes at an altitude of 340 km, and about 60 satellites per orbital plane, the distance between satellites in the same orbital plane is about 700 km, and the satellite speed is about 7.7 km, the satellites will revisit the orbital plane at intervals of about 90 seconds. Also, it takes about 18 minutes from the time an adjacent orbital plane passes until the next orbital plane revisits. Also, if there are three different altitudes in the vicinity, the orbital planes will gradually move in the longitude direction without synchronization. Under these circumstances, a rocket launched from Guiana near the equator must launch in the gap between the time the three orbital planes pass and the time the next orbital plane revisits, and there is only a few minutes of time to spare.
Even if a collision occurs under these circumstances, it is difficult to call it an accidental accident, so it is reasonable to exempt them from liability.
As a result, it will be possible to avoid an increase in the scale of insurance payments due to the frequent risk of collision accidents between low-orbit mega-constellations, thereby ensuring the sustainability of space insurance.

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

In space stations or geostationary orbit satellites, collision avoidance operations are often performed based on danger warnings. On the other hand, in low-earth orbit satellites, the distance between satellites is much shorter than in geostationary orbit, and some satellites, such as CubeSats, do not have the function of collision avoidance operations. Therefore, when a danger warning is issued in a specific dense orbital plane of low-earth orbit satellites, if some satellites perform collision avoidance operations without coordination with surrounding satellites, there is a risk of collision with other nearby satellites.
In addition, some management operators have declared that they will be equipped with autonomous collision avoidance operation means. 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 positions as a result of the avoidance.
Therefore, according to specific example 8 of the liability evaluation 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 of the reasonable measures.
If exemptions are not granted, international rules will need to be created to facilitate collision avoidance operations in dense orbits.

Embodiment 4.
In this embodiment, the following mainly describes the differences from the first to third embodiments. Note that the same components as those in the first to third embodiments are given the same reference numerals, and the description thereof may be omitted.

In this embodiment, a collision insurance execution device that executes the operation of space collision insurance 202 that compensates for damage caused by collisions between multiple space objects flying in space will be described.
With the emergence of mega-constellation operators, the possibility of collision accidents of space objects occurring not by accident but due to a dominant occurrence rate or human misjudgment is increasing. Space insurance assumes accidental accidents, but insurance is needed for accidents with a significantly higher occurrence risk compared to the statistical probability of accidental failure, that is, collision accidents that cannot be called accidental. For example, just as there is a one-time insurance that applies only to the flight when boarding an aircraft, space collision insurance 202 that can be purchased as a one-time insurance after a satellite collision is predicted is a promising business model. Space collision insurance 202 is also called space object collision insurance.

***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.

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. The storage unit 262 may also be provided separately in the memory 921 and the auxiliary storage device 922.

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. The collision insurance execution program according to this embodiment is a program that realizes the functions of the insurance processing unit 261. In other words, the collision insurance execution program according to this embodiment causes a computer to execute insurance processing by the insurance processing unit 261.

*** Operation Description ***
The collision insurance execution process performed by the collision insurance execution device 260 according to this embodiment will be described with reference to FIG.

<Collision Insurance Execution Process: S300>
In step S61, the insurance processing unit 261 executes the operation of the space collision insurance 202.
Space collision insurance 202 is purchased by a management company that owns a space object for which a collision is predicted based on orbit forecast information 51. Space collision insurance 202 pays insurance money when a predicted collision accident actually occurs, and the contract ends when a 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 executes the operation of space collision insurance that the management company can subscribe to after the issuance of a danger warning. The insurance processing unit 261 executes the operation of space collision insurance 202 that megaconstellation companies that own megaconstellations, which are large-scale satellite constellations, can subscribe to on a satellite group basis and can receive insurance money when a collision accident occurs. The insurance processing unit 261 also executes the operation of space collision insurance 202, which covers high-level damages associated with a collision chain caused by a predicted collision accident. In the space collision insurance 202, the insurance premium and the insurance rate change depending on the past record of similar collision accidents.

Below, we explain a specific example of space collision insurance 202 that is executed in the collision insurance execution process.

<Specific example 1 of Space Collision Insurance 202>
Space collision insurance 202 is 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 money when the predicted collision accident actually occurs, and the contract ends when the danger time period during which the warning was issued has passed without an accident.

Space collision insurance 202 can be purchased after a collision warning is issued by a stakeholder who owns a space object for which a collision is predicted based on public information and the space object orbit information forecast value in the launch insurance, life insurance, launch third party liability insurance, and orbit 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 is terminated if the danger time period during which the warning was issued has passed without an accident.
Danger warnings such as collision warnings may be issued by SSA operators based on publicly available orbital forecast information, or may be issued by a separate operator whose specialty is 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 error between the predicted and actual values is small.
If a collision warning is issued but neither party takes evasive action, the insurance company will not be liable and no insurance payments will be made.

<Specific example 2 of Space Collision Insurance 202>
The 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. The space collision insurance 202 pays out insurance money when a predicted collision accident actually occurs, and the contract ends when the danger time period when the warning was issued has passed without an accident.

When a rocket is launched, there is a risk that space objects that have left their orbit and are in the process of deorbiting, or that are flying in an elliptical orbit during orbital transfer, may collide with mega-constellation satellites flying across the entire sky. However, if forecast values are not made public, or even if they are made public, there is a possibility that the SSA operator or orbit analysis service provider will not be able to issue a collision warning at the appropriate time. In this case, it is reasonable for the operator to decide to take out ad-hoc insurance even if there is no collision warning. The contract will end once the object has safely passed the dangerous orbit.

<Specific 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 megaconstellation operators on a satellite group basis, and insurance money can be received in the event of a collision accident caused by a collision warning or ad hoc collision risk.

Megaconstellation operators can foresee many collision risks in the future, and can choose to fund their insurance with life insurance or third-party liability insurance, or with 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 cooperates to provide a series of services as a lump sum, and to make insurance payments for each of the constituent satellites.
In addition, when funding ad hoc space collision insurance 202, it is reasonable for the contract for a rocket or a space object in the deorbiting process to terminate after passing through a danger zone, but it is reasonable for megaconstellation operators to have a mechanism for taking out insurance in one go, including the risk of ad hoc collisions that occur one after another.
Premiums should be set according to the size of the constellation, the expected frequency of ad-hoc collision risks, and the term of the contract.

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

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 is a concern for mega-constellation operators.
If these high-level damages that can be foreseen in advance were to be the subject of insurance, it may be possible to establish space collision insurance 202 by having megaconstellation operators pay high insurance premiums.

<Specific example 5 of Space Collision Insurance 202>
Space collision insurance 202 does not cover higher-level damages caused by a chain of collisions resulting from ad-hoc collision accidents that are predicted in advance.

This is space collision insurance 202, which insures only the one satellite that has collided when the party receiving the collision warning is a constellation operator, and does not take into account damages resulting from chain accidents.
In the space collision insurance 202 of specific 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 of the sustainability of the insurance business itself being at risk. In a situation where the megaconstellation operator does not respond to the necessary and sufficient payment of insurance premiums, it is reasonable to exclude high-level damage that can be foreseen in advance from the insurance payment target as an exemption.

<Specific example 6 of Space Collision Insurance 202>
For space collision insurance 202, the insurance premium and insurance rate vary depending on the past record of similar collision accidents.

In space collision insurance 202, insurance premiums and insurance rates vary 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 orbit forecast information 51 and orbit performance information 52 from the space information recorder 50, the history of compensation and litigation in the accident, the frequency of similar accidents, and the results of an analysis of past information on insurance payment performance.

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

***Other configurations***
<Modification>
Here, modifications of the third and fourth embodiments will be described.
The space insurance support system and the 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 operation device. The space insurance support device and the collision insurance operation device may work together to realize the functions of the server. The server realizes the following steps (also called means or units) by processing circuitry such as a processor or electronic circuit.
An example of the insurance premium rate setting means is a premium evaluation section, and an example of the insurance payment assessment means is an insurance processing section.

The contract information includes insurance premium rates, accident liability assessments, and insurance claim assessment amounts.
The space object information includes trajectory forecast information for space object A and space object B in which a collision accident occurred, and actual trajectory information for space object A and space object B in the time period in which the collision occurred.
The server includes the following stages:
A stage in which, after a collision accident has occurred, the responsibility of colliding space objects A and B is assessed based on the difference between actual orbit information and predicted orbit information.
- A stage in which the amount of insurance payable is assessed based on the difference between the actual orbit information and the forecast orbit information.
・The stage of paying the insurance money.

The space object information includes space object collision warnings obtained from satellite information management companies.
The server also includes the following steps:
A stage in which, after a collision accident has occurred, the responsibility of colliding space objects A and B is assessed based on the difference between actual orbit information and predicted orbit information.
- A stage in which the amount of insurance payable is assessed based on the difference between the actual orbit information and the forecast orbit information.
・The stage of paying the insurance money.

The server also includes the following steps:
- The stage where contracts are accepted after receiving a space object collision warning.
- Determining insurance rates based on the forecast error of the orbital forecast information recorded in the space object information.
- A stage in which, after a collision accident has occurred, the responsibility of the colliding space objects A and B is assessed based on the difference between the actual orbit values and the predicted orbit values .
- Assessing the amount of insurance payable based on the difference between the actual orbit values and the predicted orbit values .
・The stage of paying the insurance money.
- The stage at which the contract is terminated after completing payment, the stage at which the contract is terminated due to a release of liability, or the stage at which the contract is terminated without a collision accident occurring due to a space object collision warning.

The server also includes the following steps:
- The stage where contracts are accepted after obtaining forecasts of the rocket launch, satellite orbital transfer, or satellite pass during de-orbit.
- Determining insurance rates based on the forecast error of the orbital forecast information recorded in the space object information.
- A stage in which, after a collision accident has occurred, the responsibility of the colliding space object A and the colliding space object B is assessed based on the difference between the actual orbit values and the predicted orbit values .
- Assessing the amount of insurance payable based on the difference between the actual orbit values and the predicted orbit values .
・The stage of paying the insurance money.
- The stage at which the contract is terminated after completing payment, the stage at which the contract is terminated due to a release of liability, or the stage at which the contract is terminated without a collision accident occurring due to a space object collision warning.

In the insurance payment system, after a collision accident occurs, at the stage of assessing the liability of colliding space objects A and B 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.

In the insurance payment system, at the stage of 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.

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

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

In the insurance payment system, insurance payments will only be made in the case of collision accidents involving space objects identified by space object collision warnings obtained from satellite information management companies, and the contract information will include information that exempts insurance from liability for higher-level damage caused by chain reactions.

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 cover damages for higher-level damage caused by chain reactions.

In the insurance payment system, when assessing the insurance payout for space objects A and B that collided after a collision accident occurred based on the difference between actual orbit information and predicted orbit information, the insurance payout is subject to compensation for damages for higher-level damage caused by the chain collision accident.

In the insurance payment system, the contract information will include information that waives liability for extensive damage caused by debris scattered due to collisions during rocket launches or collisions with debris removal satellites.

In the insurance payment system, the contract information will include information that will exempt the operator from liability if the party involved in the space object collision is a megaconstellation operator and has not paid insurance premiums for individual satellites or satellite groups.

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 accident liability of colliding space objects A and B is assessed based on the difference between actual orbit information and predicted orbit information, the accident liability of the non-routine operation side is assessed more heavily.

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

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 colliding space objects A and 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.

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

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

In the insurance payment system, the contract information includes information that waives liability in the event of a collision between space objects equipped with a collision avoidance function taking collision avoidance measures without prior notice.

The insurance payment system allows mega-constellation operators to subscribe to the system on a satellite-by-satellite basis, and to receive insurance payments in the event of a collision accident caused by collision warnings or ad-hoc collision risks.

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

In the insurance payment system, the forecast error included in the orbit forecast information includes a verification record, and the more extensive the verification record, the lower the insurance premium rate is set.

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

In the insurance payment system, the assessment of accident liability and insurance payment fluctuates depending on the track record of similar collision accidents in the past.

The server also comprises the following steps:
- The stage where contracts are accepted after receiving a space object collision warning.
- A step of determining insurance premium rates based on the forecast error of the orbit forecast information recorded in the space object information, and - A step of assessing the accident liability of the colliding space objects A and B based on the difference between the actual orbit values and the predicted orbit values after the collision accident occurs.
- The stage of assessing the insurance payment amount.
- The stage where the contract is terminated when the insurance payment has been completed or no collision accident has occurred due to the space object collision warning.

The space insurance program causes a computer to execute a process for paying insurance money from insurance premiums collected in advance when space object A and space object B among a plurality of space objects collide.
The space insurance program includes a danger warning output means for identifying the presence of a potentially 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 subscribed to by a management company that owns a space object for which a collision is predicted after a danger warning is issued by the collision avoidance assistance program.The insurance payment is made when the predicted collision accident actually occurs, and the contract is terminated if the danger time period during which the danger warning notifying of the risk of collision is issued has passed without an accident.It is an ad hoc space collision insurance.

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, allowing them to receive insurance benefits in the event of a collision accident.

Space collision insurance under the Space Insurance Program does not cover higher damages caused by a chain of collisions resulting from a foreseeable collision accident.

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

For space collision insurance under the Space Insurance Program, the premium rate setting method and insurance claim assessment method vary depending on the past record of similar collision accidents.

Embodiment 5.
In this embodiment, the following will mainly describe the differences from the first to fourth embodiments. Note that the same components as those in the first to fourth embodiments are given the same reference numerals, and the description thereof may be omitted.

***Configuration Description***
FIG. 41 is a diagram showing an example of the functional configuration of the satellite constellation forming system 600.
The difference between FIG. 41 and FIG. 8 is that communication with a rocket launch business device 46 is illustrated.

FIG. 42 is a configuration diagram of an information management system 500 according to the present 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 performs a management business for 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 device 40 refers to another management business device that does not have the information management device 1000 mounted thereon. Specifically, the other management business device 40 is a rocket launch business device 46, an orbital transfer business device 44, or a debris collection business device 45 used by a debris collection business operator. Note that even if the information management device 1000 is mounted on the satellite constellation business device 451, the other management business device 40 may include another satellite constellation business device.
In addition, the information management device 1000 may be a device that centrally manages satellite constellation business equipment used by a satellite constellation operator that forms a satellite constellation consisting of multiple satellites, and rocket launch business equipment used by a rocket launch operator.

The management business device 40 performs a management business of a space object 60 such as an artificial satellite or debris. The management business device 40 is a computer of a business operator that collects information on the space object 60 such as an artificial satellite 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.

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.

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.

The information management device 1000 has, 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.

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. The storage unit 1400 may also be provided separately in the memory 921 and the auxiliary storage device 922.

The hardware configuration of the space insurance support device 200 is the same as that of the collision avoidance support device 100 in embodiment 1.

*** Operation Description ***
<Information disclosure process: 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.

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

In step S1002, the information disclosure unit 1100 extracts the disclosed forecast information 552 from the multiple orbit forecast information corresponding to the multiple space objects included in the orbit forecast information 51. For example, the information disclosure unit 1100 may extract the orbit forecast information whose forecast error 514 is equal to or greater than the disclosure threshold value 141 as the disclosed forecast information 552 from the multiple orbit forecast information corresponding to the multiple space objects included in the orbit forecast information 51. The information disclosure unit 1100 may also extract the disclosed forecast information 552 by other methods. The information disclosure unit 1100 outputs the disclosed forecast information 552 to another management business device. At this time, when the information disclosure unit 1100 accepts the information disclosure request 551, it may transmit the disclosed 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.

<Satellite constellation control process: 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 forming 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.

In step S2001, the satellite constellation formation unit 11 acquires rocket launch information 503 from the rocket launch business device 46, the rocket launch information including the launch point of the rocket for the rocket launch and the scheduled launch time of the rocket at the launch point.

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 the flight path at the scheduled time when the rocket will fly along the 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 to raise or lower the orbital altitude 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.

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

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 a 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 allowable 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.

FIG. 46 is a diagram showing the error range of the rocket launch forecast values 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.

As shown in the upper part of Figure 46, it may be possible for a satellite constellation operator to reduce the error range within its own system by using techniques such as differential evaluation of inter-satellite ranging data and GPS measurement values, or statistical data evaluation.
If satellite constellation operators do not disclose the margin of error, launch vehicle operators will have to rely on external measurement information, such as SSA operators, for information on the satellite orbit forecast values. This could result in launch vehicle operators only being able to grasp forecast values with a large margin of error.
In this way, by configuring the disclosure of orbit forecast information within a specified 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.

Note that the orbit forecast information used by rocket launch operators when launching a rocket has been described here. However, this embodiment can also be applied in 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.

***Description of Effects of This Embodiment***
According to the information management device 1000 of this embodiment, a satellite constellation operator that forms a mega constellation can disclose the predicted values of the orbital information of its own satellite to a rocket launch operator, a geostationary satellite orbit insertion operator, or a debris collection operator for a fee.
In order for rocket launch operators to fulfill their obligation to ensure flight safety, accurate predicted orbit information of satellites that constitute a mega-constellation is necessary. Therefore, according to the information management device 1000 of the present embodiment, it is possible to increase the asset value of the satellite orbit prediction information, and it is possible for it to become a source of revenue for the satellite operator.

In addition, there is a high risk of a collision with a satellite in a megaconstellation when the satellite leaves its orbit after completing its mission and is deorbited. Similarly, it may be possible to hold accountable the operator of a deorbit satellite that failed to take collision avoidance measures for the orbit information it disclosed, or the debris collection operator, and this has the effect of making satellite orbit information a source of revenue.
Furthermore, operators who launch geostationary satellites into orbit first launch them into geostationary transfer orbit using a rocket, 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.

According to the information management device 1000 of the present embodiment, a rocket launching company can share the satellite orbit information forecast value of a mega-constellation company in a low orbit altitude. Therefore, the rocket launching company can develop a rocket launching business in which launching without collision risk without using the disclosure information of the satellite's predicted orbit information is a source of competitiveness.
If the satellite predictive 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 operator.

According to the satellite constellation forming 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 from that launch point.
In a planetary exploration spacecraft for rendezvous with a planet flying in a specific orbit, the launch window during which it can be launched appropriately from the launch point may be limited to a short time of several seconds. On the other hand, since the Earth rotates with respect to the orbital plane of a satellite flying in inertial space according to the laws of nature, there is a risk that a satellite will happen to fly on the launch flight path and collide with it. In a mega-constellation, the interval between satellites flying on the same orbital plane may be only several tens of seconds, so it is difficult to sufficiently avoid collisions unless measures are taken to prevent the orbital plane from being located in the sky. According to the satellite constellation forming system 600 of this embodiment, the satellite mega-constellation side operates the propulsion devices equipped on all satellites in advance so that the orbital plane is not located in the sky at a specific time of a specific launch point. Then, the orbital altitude of the satellite is raised or lowered, and the relative relationship between the orbital plane and the rotation of the Earth is adjusted, so that the orbital plane is not located in the sky at a specific time of a specific launch point, thereby avoiding collisions. In megaconstellations, it is important to synchronize and adjust all satellites, because adjusting only individual satellites would run the risk of them colliding with other satellites.

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

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 based on the orbit forecast information that a satellite forming the satellite constellation and a space object about which the orbit forecast information is obtained from another management business device will approach each other at a specific time.

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

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 includes 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 performs collision analysis 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.
A satellite constellation management business device does 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 the space object information A and the space object information B to perform collision analysis, derives conditions for ensuring flight safety during rocket launch, and avoids collision.

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 business operator can use the space object information A and the space object information B free of charge to perform collision analysis, derive conditions for ensuring flight safety during rocket launch, and avoid collision.

A satellite constellation management business device does not disclose space object information B to space information recorder A and space information recorder C owned by other businesses.
Then, the satellite constellation operator performs a collision analysis using the space object information A and the space object information B, and if a collision is predicted, the satellite constellation operator takes evasive action to ensure flight safety.

***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.

FIG. 47 is a diagram showing a configuration of an information management device 1000 according to a modification of the present 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 is specifically a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation of Gate Array.
The functions of the information management device 1000 may be realized by a single electronic circuit, or may be distributed 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.

Each of the processor and electronic circuit is also called processing circuitry. In other words, the functions of the information management device 1000 are realized by the processing circuitry.

In the above first to fifth embodiments, each part 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 as in the above-mentioned 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-mentioned embodiments. Furthermore, each device and each system may be composed of one device or multiple devices.

In the above embodiments 1 to 5, the terms "part," "process," "procedure," "stage," "process," and "means" in the components of each device and each system can be interchanged or rewritten. For example, the "stage for paying insurance money" in the server described in the modified examples of embodiments 3 and 4 can be interchanged as the "means for paying insurance money" or "part for paying insurance money." Also, the information disclosure part of the information management device 1000 described in embodiment 5 can be interchanged as the information disclosure process, information disclosure stage, information disclosure processing, or information disclosure means.

In addition, a combination of multiple parts of the first to fifth embodiments may be implemented. Alternatively, one part of these embodiments may be implemented. In addition, any combination of these embodiments may be implemented, either as a whole or in part.
In the first to fifth embodiments, any combination of the first to fifth embodiments may be used. In the first to fifth embodiments, the components may be modified in any way. Alternatively, in the first to fifth embodiments, the components may be omitted.

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

20 Satellite constellation, 21 Orbital plane, 22 Approach warning, 23 Collision warning, 25 Danger warning, 30, 30a, 30b Satellite, 31 Satellite control device, 32 Satellite communication device, 33 Propulsion device, 34 Attitude control device, 35 Power supply device, 40 Management business device, 41 Mega constellation business device, 42 LEO constellation business device, 43 Satellite business device, 44 Orbit transfer business device, 45 Debris collection business device, 46 Rocket launch business device, 47 SSA business device, 50 Space information recorder, 51 Orbit forecast information, 511, 521 Space object ID, 512 Forecast origin, 513 Forecast orbital elements, 514 Forecast error, 515 Forecast flight state, 52 Orbit performance information, 522 Actual origin, 523 Actual orbital elements, 524 Specific performance, 525 Actual flight state, 241 Specific time, 242 Actual position coordinates, 515 Forecasted flight state, 60 Space object, 65 Predicted dangerous object, 69 Avoided space object, 70 Earth, 100, 100a Collision avoidance support device, 110 Recorder processing unit, 120 Warning control unit, 130 Results presentation unit, 131 Collision results, 140 Memory unit, 141 Warning issuance information, 150 Avoidance decision unit, 160 Machine learning unit, 401 Flight forecast information, 402 Flight results 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 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 storage unit, 503 rocket launch information.

Claims (54)

A space insurance support device that supports the operation of space insurance that compensates for damage caused by a collision between a plurality of space objects flying in space, comprising:
A space insurance support device that is equipped with a liability evaluation unit that evaluates accident liability and liability for damages based on the predicted value of the orbit of each of the plurality of hazardous objects at any time and orbit performance information including the actual orbit value of each of the plurality of hazardous objects at the time, when a danger warning is issued to indicate the presence of hazardous objects, which are multiple space objects among the plurality of space objects whose positional relationship is dangerous at the same time, and when the hazardous objects collide when a danger warning generated based on orbit forecast information which is a predicted value of the orbit of each of the plurality of space objects is not issued. the orbit forecast information includes a forecast error predicted in the orbit,
The space insurance support device includes:
2. A space insurance support device as described in claim 1, further comprising an insurance premium evaluation unit that evaluates insurance premiums for a management company that manages each of the plurality of space objects based on the forecast error. The insurance premium assessment unit includes:
3. A space insurance support device as described in claim 2, wherein insurance premiums are assessed based on the orbit forecast information and orbit performance information including the orbit performance values of each of the predicted hazard objects, so that the insurance premium rate is lower the smaller the difference between the predicted value of the orbit and the orbit performance value. The insurance premium assessment unit includes:
4. A space insurance support device according to claim 2 or 3, wherein the insurance premium is evaluated such that the smaller the difference between the predicted value of the orbit and the actual value of the orbit, the higher the insurance premium to be paid. The responsibility assessment unit:
A space insurance support device as described in any one of claims 1 to 4, in which accident liability and liability for damages are evaluated so that the smaller the difference between the predicted value of the orbit and the actual orbit value, the lower the accident liability and liability for damages in the event of a collision. The responsibility assessment unit:
A space insurance support device as described in any one of claims 1 to 5, which evaluates accident liability and liability for damages so that an accident that occurs despite being foreseeable in advance based on the predicted orbit value is treated as an exemption clause. The responsibility assessment unit:
A space insurance support device as described in any one of claims 1 to 6, in which accident liability and liability for damages are evaluated in a third-party liability insurance policy with a rocket launch company that operates a rocket launch business as the insured, so that only the parties involved in a collision accident are subject to compensation for damages and higher-level damages are exempt from liability. The responsibility assessment unit:
8. A space insurance support device according to claim 1, which assesses accident liability and liability for damages so that high-level damage caused by debris scattered due to a collision is covered by life insurance or orbital liability insurance. The responsibility assessment unit:
9. A space insurance support device according to any one of claims 1 to 8, which assesses liability for accidents and liability for damages so as to exempt parties other than those paying life insurance for individual satellites or groups of satellites. The responsibility assessment unit:
A space insurance support device as described in any one of claims 1 to 9, which evaluates accident liability and damages liability so as to give a heavier liability to the management company of the space object in non-routine operation in the event of a collision between a space object in routine operation and a space object in non-routine operation. The responsibility assessment unit:
A space insurance support device as described in any one of claims 1 to 10, which evaluates accident liability and damages liability so as to give a heavier responsibility for the accident and damages liability of the management company of the space object in regular operation in the event of a collision between a satellite in the orbital transfer of a geostationary satellite and a space object in regular operation. The responsibility assessment unit:
12. A space insurance support device as claimed in any one of claims 1 to 11, which 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. The responsibility assessment unit:
A space insurance support device as described in any one of claims 1 to 12, which evaluates accident liability and liability for damages so as to exempt from liability in the event of a collision accident between space objects equipped with the function of performing collision avoidance operations, in which collision avoidance operational measures are taken without notice. The responsibility assessment unit:
A space insurance support device as described in any one of claims 1 to 13, which evaluates accident liability and liability for damages based on a space information recorder including the orbit forecast information and orbit performance information in which the orbit performance value is set. A collision insurance execution device that executes a space collision insurance that compensates for damage caused by a collision between a plurality of space objects flying in space, comprising:
A collision insurance execution device equipped with an insurance processing unit that executes the operation of the space collision insurance, in which a management company that owns a space object for which a collision is predicted takes out subscribes to the space collision insurance based on orbit forecast information, which is a predicted value of the orbit of each of the multiple space objects, and in which, when a predicted collision accident actually occurs, an insurance premium is paid that is set to be high when the difference between the predicted orbit value and the actual orbit value is small, and the contract is terminated 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:
The collision insurance execution device according to claim 15, which executes the operation of the space collision insurance that the management company can subscribe to after the issuance of the danger warning. The insurance processing unit:
The collision insurance execution device according to claim 15 or 16, wherein a megaconstellation operator who owns a megaconstellation, which is a large-scale satellite constellation, operates the space collision insurance, which can be subscribed to on a satellite group basis and can receive insurance money in the event of a collision accident. The insurance processing unit:
18. The collision insurance execution device according to claim 15, which executes the space collision insurance that covers higher damages associated with a collision chain caused by a predicted collision accident. The insurance processing unit:
19. The collision insurance execution device according to claim 15, which executes the space collision insurance in which the insurance premium and the insurance rate vary depending on the results of past similar collision accidents. A database that records insurance payment contract information for each individual insurance contract;
A server having a database that records space object information,
The contract information is
The space object information includes insurance rates, accident liability assessments, and insurance claim assessment amounts.
Orbit forecast information, which is the orbit forecast value of each of space objects A and B where a collision accident occurred;
The orbit performance information includes orbit performance values of each of the space object A and the space object B during the time period in which the collision occurred,
The server,
After the collision occurs, assessing the responsibility of the space object A and the space object B in the collision based on the difference between the actual orbit value and the predicted orbit value;
assessing an insurance payment based on a difference between the actual track value and the predicted track value;
and paying the payment insurance claim. A database that records insurance payment contract information for each individual insurance contract;
A server having a database that records space object information,
The contract information is
The space object information includes insurance rates, accident liability assessments, and insurance claim assessment amounts.
Space object collision warnings obtained from satellite information management companies,
Orbit prediction information is a predicted orbit value of each of space objects A and B, which are predicted to collide;
Orbit performance information including orbit performance values of each of the space object A and the space object B during a time period in which a collision is predicted;
Including,
The server,
After a collision occurs, assessing the responsibility of the collided space object A and the collided space object B based on the difference between the actual orbit value and the predicted orbit value;
assessing a payment amount based on a difference between the actual track value and the predicted track value;
and paying the payment insurance claim. A database that records insurance payment contract information for each individual insurance contract;
A server having a database that records space object information,
The contract information is
The space object information includes insurance rates, accident liability assessments, and insurance claim assessment amounts.
Space object collision warnings obtained from satellite information management companies,
Orbit prediction information including predicted values and prediction errors of the orbits of space objects A and B, which are predicted to collide with each other;
Orbit performance information including orbit performance values of each of the space object A and the space object B during a time period in which a collision is predicted;
Including,
The server,
receiving the space object collision warning and then accepting a contract;
determining an insurance premium rate based on the forecast error recorded in the space object information;
After a collision occurs, assessing the responsibility of the collided space object A and the collided space object B based on the difference between the actual orbit value and the predicted orbit value;
assessing insurance payout based on a difference between the actual track value and the predicted track value;
paying the payment claim;
a step of completing payment and terminating the contract, a step of terminating the contract due to exemption from liability, or a step of terminating the contract without occurrence of a collision accident due to the space object collision warning;
An insurance payment system with A database that records insurance payment contract information for each individual insurance contract;
A server having a database that records space object information,
The contract information is
The space object information includes insurance rates, accident liability assessments, and insurance claim assessment amounts.
Space object collision warnings obtained from satellite information management companies,
Orbit prediction information including predicted values and prediction errors of the orbits of space objects A and B, which are predicted to collide with each other;
Orbit performance information including orbit performance values of each of the space object A and the space object B during a time period in which a collision is predicted;
Including,
The server,
accepting a contract after obtaining a forecast of the launch of the rocket, or the orbital transfer of the satellite, or the satellite passing during de-orbit;
determining an insurance rate based on the predicted value of the orbit and the predicted error recorded in the space object information;
After a collision occurs, assessing the responsibility of the collided space object A and the collided space object B based on the difference between the actual orbit value and the predicted orbit value;
assessing a payment amount based on a difference between the actual track value and the predicted track value;
paying the payment claim;
a step of completing payment and terminating the contract, a step of terminating the contract due to exemption from liability, or a step of terminating the contract without occurrence of a collision accident due to the space object collision warning;
An insurance payment system with In a step of assessing the responsibility of the space object A and the space object B that collided based on the difference between the actual orbit value and the predicted orbit value after the collision accident occurs,
23. The insurance payment system according to claim 20, wherein the larger the difference between the track record value and the track forecast value, the heavier the assessment of the accident liability. In a step of assessing the insurance payout amount of the space object A and the space object B that collided based on the difference between the actual orbit value and the predicted orbit value after the collision accident occurs,
23. The insurance payment system according to claim 20, wherein the insurance payout amount is assessed to be higher as the difference between the actual track value and the predicted track value is smaller. The insurance payment system according to claim 21, wherein in the step of determining the insurance premium rate based on the forecast error contained in the orbit forecast information recorded in the space object information, the smaller the estimated error amount, the lower the insurance premium rate. The space object collision warning obtained from the satellite information management company; and
Orbit forecast information for each of the space objects A and B, which are predicted to collide with each other;
Despite having obtained
An insurance payment system as described in claim 21 or claim 22, which has an exemption clause for a collision accident in which a collision occurs when neither the management operator of space object A nor the management operator of space object B takes any action to avoid a collision. The insurance payment system according to claim 21 or claim 22, in which the contract information includes information that only collision accidents involving space objects identified by the space object collision warning obtained from the satellite information management company are covered by insurance payments, and that high-level damages due to chain reactions are exempt from liability. The insurance payment system according to claim 21 or claim 22, in which the contract information includes information indicating that the insurance payment covers damages for higher damages caused by chain reactions in addition to collision accidents involving space objects identified by the space object collision warning obtained from the satellite information management company. In a step of assessing the insurance payout for the space object A and the space object B that collided based on the difference between the actual orbit value and the predicted orbit value after the collision accident occurs,
30. The insurance payment system according to claim 29, wherein compensation for higher damages caused by a chain reaction accident is the subject of insurance assessment. The insurance payment system according to claim 20 or claim 21, in which the contract information includes information exempting from liability for high-level damage caused by debris scattered due to a collision during rocket launch or a collision of a debris removal satellite. The insurance payment system according to any one of claims 20 to 22, in which the contract information includes information that provides exemption from liability when the party involved in the space object collision is a megaconstellation operator and has not paid insurance premiums for individual satellites or satellite groups. The insurance payment system according to any one of claims 20 to 22, in which the accident liability of the non-routine operating side is assessed more heavily in the stage of assessing the accident liability of the space object A and the space object B that collided based on the difference between the orbit actual value and the orbit forecast value after a collision accident occurs between a space object in routine operation and a space object in non-routine operation. The insurance payment system according to any one of claims 20 to 22, in which the insurance payment for the space object A and the space object B that collided based on the difference between the actual orbit value and the predicted orbit value after a collision accident occurs between a space object in regular operation and a space object in non-regular operation is assessed at a higher amount. The insurance payment system according to any one of claims 20 to 22, in which the liability of the colliding space object A and the colliding space object B is assessed based on the difference between the actual orbit value and the predicted orbit value after a collision accident occurs between a satellite in orbit transfer and a space object in regular operation, and the liability of the satellite in orbit transfer is assessed lightly. The insurance payment system according to any one of claims 20 to 22, in which the insurance payment for the space object A and the space object B that collided based on the difference between the actual orbit value and the predicted orbit value after a collision accident occurs between a satellite in orbit transfer and a space object in regular operation is assessed to be high for the space object in regular operation. The insurance payment system according to claim 20, in which the contract information includes information exempting operators from liability for collisions with mega-constellation operators formed at altitudes of 600 km or less. The insurance payment system according to claim 21 or claim 22, in which the contract information includes information exempting the user from liability in the event of a collision between space objects equipped with a function for implementing collision avoidance operations, in which the collision avoidance operation is implemented without prior notice. An insurance payment system as described in claim 22 or claim 23, in which mega-constellation operators can subscribe on a satellite group basis and receive insurance money in the event of a collision accident caused by a collision warning or ad-hoc collision risk. The insurance payment system according to claim 22 or 23, in which the forecast error included in the orbit forecast information includes a basis for calculating the amount of error, and the insurance premium rate is set lower the clearer the basis is. The insurance payment system according to claim 22 or 23, in which the forecast error included in the orbit forecast information includes a verification record, and the more extensive the verification record, the lower the insurance premium rate is set. An insurance payment system as described in claim 22 or claim 23, in which the assessment of insurance premium rates varies depending on the past record of similar collision accidents. An insurance payment system according to any one of claims 20 to 23, in which the assessment of accident liability and the assessment of insurance money vary depending on the track record of similar collision accidents in the past. A database that records insurance payment contract information for each individual insurance contract;
A server having a database that records space object information,
The contract information is
The space object information includes insurance rates, accident liability assessments, and insurance claim assessment amounts.
Space object collision warnings obtained from satellite information management companies,
Orbit forecast information is a forecast value of the orbits of space objects A and B, which are predicted to collide with each other;
Trajectory performance information including a trajectory performance value during a time period in which a collision is predicted;
The server,
receiving the space object collision warning and then accepting a contract;
determining an insurance rate based on a forecast error included in the orbit forecast information recorded in the space object information;
After a collision occurs, assessing the responsibility of the collided space object A and the collided space object B based on the difference between the actual orbit value and the predicted orbit value;
assessing the claim to be paid;
terminating the contract when the insurance payment is completed or when the collision accident caused by the space object collision warning does not occur;
An insurance payment system. A space insurance program that causes a computer to execute a process for paying insurance money from insurance premiums collected in advance when a space object A and a space object B among a plurality of space objects collide, comprising:
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 a plurality of space objects flying in space, after a danger warning is issued by a collision avoidance support program,
This is an ad-hoc space collision insurance program in which a management company that owns a space object with which a collision is predicted can subscribe to the insurance. When a predicted collision accident actually occurs, the insurance payout is set to be higher if the difference between the predicted orbital value and the actual orbital value is small, and the contract is terminated if the danger time period during which a danger warning is issued to notify of the risk of collision has passed without an accident. A space insurance program as described in claim 45, which allows megaconstellation operators who own large-scale satellite constellations to subscribe to the program on a satellite-by-satellite basis and receive insurance benefits in the event of a collision accident. A space insurance program as described in claim 45 or claim 46, which does not cover higher damages due to a chain reaction of collisions caused by a foreseeable collision accident. A space insurance program as set forth in any one of claims 45 to 47, which insures against high-level damages caused by a chain of collisions resulting from a predicted collision accident. A space insurance program according to any one of claims 45 to 48, in which the contents of the insurance premium rate setting means and the insurance payment assessment means vary depending on the past record of similar collision accidents. A space insurance program that causes a computer to execute a process for paying insurance money from insurance premiums collected in advance when a space object A and a space object B among a plurality of space objects collide, comprising:
A space insurance program comprising: a management business device used by a management company that manages a plurality of space objects flying in space, which acquires flight forecast information representing a forecast of the flight of each of the plurality of space objects; based on the acquired flight forecast information, sets a forecast origin of the orbit of each of the plurality of space objects, forecast orbital elements that specify the orbit, and forecast errors predicted in the orbit as orbit forecast information; and a space information recorder that includes the orbit forecast information has a means for setting insurance premium rates based on the forecast errors contained in the orbit forecast information. A space insurance program that causes a computer to execute a process for paying insurance money from insurance premiums collected in advance when a space object A and a space object B among a plurality of space objects collide, comprising:
As a means of insurance assessment,
Acquire flight performance information representing the flight performance of each of a plurality of space objects flying in space from at least one of each of the plurality of space objects and a management business device that manages the space objects, set the actual epoch of the orbit of each of the plurality of space objects, actual orbital elements that specify the orbit, and actual position coordinates of each of the plurality of space objects as orbit performance information based on the acquired flight performance information, extract the orbit performance information at the time when the space objects collide with each other from the orbit performance information possessed by a space information recorder that includes the orbit performance information as a collision performance, and extract the orbit forecast information at the time when the space objects collide with each other from the orbit forecast information as pre-collision forecast information,
Difference information A between the collision record and the pre-collision forecast information of the space object A. Difference information B between the collision record and the pre-collision forecast information of the space object B.
A space insurance program that includes a means of assessing insurance claims by comparison with the actual amount of the insurance premium. The insurance premium rate setting means:
51. A space insurance program as described in claim 50, wherein the insurance premium rate is changed according to the reasons and verification results included in the forecast error of the space information recorder. A space insurance support device that supports the operation of space insurance that compensates for damage caused by collisions between multiple space objects flying in space, comprising:
a space information recorder that sets, based on flight performance information representing the flight performance of each of the plurality of space objects, a performance origin of the orbit of each of the plurality of space objects, performance orbital elements that specify the orbit, and performance position coordinates of each of the plurality of space objects as orbit performance information;
A danger warning indicating the presence of a plurality of space objects that are dangerous in terms of their positional relationship at the same time among the plurality of space objects, in which the danger warning is generated based on orbit forecast information that is the time and orbit forecast value of each of the plurality of space objects, when the danger warning is not issued and the danger warning is generated based on the time and orbit forecast information of each of the plurality of space objects, the danger warning is generated when the danger warning is generated based on the orbit forecast information of the plurality of space objects, the orbit forecast value of the plurality of space objects, and the danger warning is generated when the danger warning is generated based on the orbit forecast information of the plurality of space objects, the orbit forecast value of the plurality of space objects,
a liability evaluation unit that extracts, from the orbit performance information possessed by the space information recorder, the orbit performance information at the time when the space objects collide with each other as a collision performance, and extracts, from the orbit forecast information, the orbit forecast information at the time when the space objects collide with each other as pre-collision forecast information, and evaluates accident liability and liability for damages based on the pre-collision forecast information and the collision performance;
Space insurance support equipment equipped with A database that records insurance payment contract information for each individual insurance contract;
A server having a database that records space object information,
The contract information is
The space object information includes insurance rates, accident liability assessments, and insurance claim assessment amounts.
Orbit forecast information, which is the orbit forecast value of each of space objects A and B where a collision accident occurred;
The orbit performance information includes orbit performance values of each of the space object A and the space object B during the time period in which the collision occurred,
The server,
After the collision occurs, assessing the responsibility of the space object A and the space object B in the collision based on the difference between the actual orbit value and the predicted orbit value;
assessing an insurance payment based on a difference between the actual track value and the predicted track value;
A step of paying the payment insurance claim,
Space object collision warnings obtained from satellite information management companies,
Orbit forecast information for each of the space objects A and B, which are predicted to collide with each other;
Despite having obtained
An insurance payment system with an exemption clause for a collision accident 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 a collision.

Images