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

Abstract

To provide a system capable of appropriately compensating for damage caused by a collision in outer space.SOLUTION: A space insurance support device 200 supports the operation of space insurance for compensating for damage caused by collisions between space objects. In spite of no risk warning is issued which indicates that there is a hazardous object, which is one of the multiple space objects with a dangerous positional relationship at the same time, when a hazardous object collides, a responsibility evaluation unit 210 evaluates the accident liability and the damage liability based on a forecast value of the orbits in each of the hazardous objects and orbital performance value of each of the hazardous objects.SELECTED DRAWING: Figure 30

Description

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

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

In addition, it is necessary to take measures for avoidance behavior when a collision is predicted in advance. Manned space stations or geostationary satellites of satellite carriers take evasive action when a collision is foreseen. However, it is difficult to formulate a unified rule for avoidance behavior in an environment where satellites of multiple operators are densely packed at low orbit altitude and some have and do not have the function of avoidance behavior. This is to create a new risk of collision between evasive satellites when evasive satellites and non-evasive satellites coexist in a dense area.
Conventionally, there is a business model in which space insurance covers damages caused by a rocket launch failure due to an accidental accident or a loss of function due to an orbital accident of a satellite.

Patent Document 1 discloses a technique for forming a satellite constellation composed of a plurality of satellites in the same circular orbit.

JP-A-2017-114159

Collision accidents that can be easily inferred by current technology are no longer accidental accidents, and a new mechanism for compensating for damage is needed. In addition, the mechanism to cover insurance including higher-order damage has the risk of inducing a rise in the insurance premium rate as a result when the total amount of damage becomes huge, leading to the collapse of the space insurance system itself. At present, there are no established international rules regarding the responsibility and liability 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.

An object of the present invention is to provide a mechanism for maintaining the sustainability of a space insurance system and appropriately compensating for damages caused by a collision 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 collisions between space objects in a plurality of space objects flying in space.
It is a danger warning indicating that there is a danger prediction object which is a plurality of space objects whose positional relationship is dangerous at the same time among the plurality of space objects, and is a predicted value of the orbit of each of the plurality of space objects. When the danger prediction object collides with the danger warning generated based on a certain orbit forecast information, the forecast value of the orbit in each of the danger prediction objects and each of the danger prediction objects It has a liability evaluation department that evaluates accident liability and liability for damages based on actual track values.

In the space insurance support device according to the present invention, the responsibility evaluation unit is based on the predicted value and the actual orbit value of the orbit of each of the danger-predicted objects when the danger-predicted object collides with the danger-predicted object when the danger warning is not issued. Evaluate accident liability and liability for damages. Therefore, according to the space insurance support device according to the present invention, there is an effect that damages caused by a collision accident in outer space can be appropriately compensated.

An example in which multiple satellites work together to realize communication services throughout the globe. An example in which multiple satellites with a single orbital plane realize earth observation services. An example of a satellite constellation with multiple orbital planes that intersect near the polar regions. An example of a satellite constellation with multiple orbital planes that intersect outside the polar regions. A block diagram of a satellite constellation formation system. The block diagram of the satellite of the satellite constellation formation system. A block diagram of the ground equipment of the satellite constellation formation system. Functional configuration example of satellite constellation formation system. The block diagram of the collision avoidance support system which concerns on Embodiment 1. FIG. The flow chart of the recorder processing which sets the orbit forecast information which concerns on Embodiment 1. FIG. The figure which shows the example of the orbit forecast information which concerns on Embodiment 1. FIG. FIG. 5 is a flow chart of a recorder process for setting track record information according to the first embodiment. The figure which shows the example of the orbit record information which concerns on Embodiment 1. FIG. FIG. 5 is a flow chart of alarm control processing by the alarm control unit according to the first embodiment. The figure which shows the crossing image of the error range of two satellites which concerns on Embodiment 1. FIG. The figure which shows the state which overlapped the error range of two satellites which concerns on Embodiment 1. FIG. The figure which shows the state which the distance of two satellites which concerns on Embodiment 1 became equal to or less than an approach threshold value. The figure which shows the warning issuance information which concerns on Embodiment 1. FIG. 5 is a flow chart of a performance presentation process by the performance presentation unit according to the first embodiment. FIG. 3 is a configuration diagram of a collision avoidance support device according to a modified example of the first embodiment. The block diagram of the collision avoidance support device which concerns on Embodiment 2. FIG. FIG. 5 is a flow chart showing an example of avoidance decision processing based on conditions such as whether or not the space object according to the second embodiment is a rocket. FIG. 5 is a flow chart showing an example of avoidance decision processing based on conditions such as whether or not the space object according to the second embodiment is a rocket. FIG. 5 is a flow chart of avoidance decision processing based on conditions such as whether or not the space object according to the second embodiment is in steady operation. The flow chart of the avoidance decision processing based on the condition such as whether or not the space object which concerns on Embodiment 2 belongs to a mega constellation. FIG. 5 is a flow chart of avoidance decision processing based on conditions such as whether or not the space object according to the second embodiment is an orbital transition satellite. FIG. 5 is a flow chart of avoidance determination processing based on conditions such as whether or not the space object according to the second embodiment has a collision avoidance function. An example of a summary of the avoidance decision process according to the second embodiment. An example of input information in the machine learning process according to the second embodiment. The block diagram of the space insurance support system and the space insurance support device which concerns on Embodiment 3. FIG. 5 is a flow chart of space insurance support processing by the space insurance support device according to the third embodiment. An example of information disclosure of a management company and an example of space insurance corresponding to a management company according to the third embodiment. Specific examples of insurance premium evaluation processing and liability evaluation processing according to the third embodiment. Specific examples of insurance premium evaluation processing and liability evaluation processing according to the third embodiment. An example of the risk of collision between a space object in steady operation and a space object in unsteady operation. An example of the risk of collision between a satellite in the middle of a geostationary satellite orbit transition and a space object in steady operation. An example of the risk of collision between a launched rocket and a mega constellation. The block diagram of the collision insurance execution system and the collision insurance execution device which concerns on Embodiment 4. FIG. 5 is a flow chart of a collision insurance execution process by the collision insurance execution device according to the fourth embodiment. The figure which shows the space collision insurance which concerns on Embodiment 4. An example of the functional configuration of the satellite constellation formation system according to the fifth embodiment. The block diagram of the information management system which concerns on Embodiment 5. FIG. 5 is a flow chart of information disclosure processing according to the fifth embodiment. FIG. 5 is a flow chart of satellite constellation control processing according to the fifth embodiment. The figure which shows the forecast value of the rocket launch and the error range of a satellite constellation which concerns on Embodiment 5. The figure which shows the forecast value of the rocket launch and the error range of a satellite constellation which concerns on Embodiment 5. The block diagram of the information management apparatus which concerns on the modification which concerns on Embodiment 5. FIG. 5 is a flow chart showing a process of updating the collision avoidance algorithm according to the second embodiment by a machine learning effect. FIG. 5 is a flow chart showing a process of updating the collision avoidance algorithm according to the second embodiment by a machine learning effect.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each figure, the same or corresponding parts are designated by the same reference numerals. In the description of the embodiment, the description will be omitted or simplified as appropriate for the same or corresponding parts. Further, in the drawings below, the relationship between the sizes of each configuration may differ from the actual one. Further, in the description of the embodiment, when the direction or position such as "top", "bottom", "left", "right", "front", "rear", "front", "back" is indicated. There is. These notations are merely described as such for convenience of explanation, and do not limit the arrangement and orientation of configurations such as devices, appliances, or parts.

Embodiment 1.
An example of a satellite constellation that is a prerequisite for 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 with each other to realize a communication service over the entire globe of the earth 70.
FIG. 1 shows a satellite constellation 20 that realizes a communication service all over the world.
For each satellite of a plurality of satellites flying on the same orbital plane at the same altitude, the communication service range for the ground overlaps with the communication service range of the succeeding satellite. Therefore, according to such a plurality of satellites, it is possible to provide a communication service to a specific point on the ground while a plurality of satellites on the same orbital plane alternate with each other in a time-division manner. Further, by providing the adjacent track surface, it is possible to cover the communication service between the adjacent tracks on the ground. Similarly, if a large number of orbital planes are arranged approximately evenly around the earth, communication services to the ground can be provided all over the globe.

FIG. 2 is a diagram showing an example in which a plurality of satellites having a single orbital plane realize an earth observation service.
FIG. 2 shows a satellite constellation 20 that realizes an earth observation service. In the satellite constellation 20 of FIG. 2, a satellite equipped with an earth observation device, which is a radio wave sensor such as an optical sensor or a synthetic aperture radar, flies on the same orbital surface at the same altitude. In this way, in the satellite group 300 in which the subsequent satellites overlap with each other due to a time delay in the imaging range on the ground, a plurality of satellites in orbit alternately alternate with each other at a specific point on the ground to capture a ground image. By providing earth observation services.

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

FIG. 3 is an example of a satellite constellation 20 having a plurality of orbital surfaces 21 intersecting in the vicinity of the polar region. Further, FIG. 4 is an example of a satellite constellation 20 having a plurality of orbital surfaces 21 that intersect outside the polar region.
In the satellite constellation 20 of FIG. 3, the orbital inclination angles of the orbital surfaces 21 of the plurality of orbital surfaces are about 90 degrees, and the orbital surfaces 21 of the plurality of orbital surfaces are present on different surfaces.
In the satellite constellation 20 of FIG. 4, the orbital inclination angles of the orbital planes 21 of the plurality of orbital planes are not about 90 degrees, and the orbital planes 21 of the plurality of orbital planes are present on different planes.

In the satellite constellation 20 of FIG. 3, any two orbital planes intersect at a point near the polar region. Further, in the satellite constellation 20 of FIG. 4, any two orbital planes intersect at points other than the polar region. In FIG. 3, a collision of the satellite 30 may occur in the vicinity of the polar region. Further, as shown in FIG. 4, the intersections of a plurality of orbital surfaces whose orbit inclination angles are inclined more than 90 degrees depart from the polar region according to the orbit inclination angles. In addition, depending on the combination of orbital surfaces, the orbital surfaces may intersect at various positions including the vicinity of the equator. Therefore, the places where the collision of the satellite 30 may occur are diversified. Satellite 30 is also called an artificial satellite.

In particular, in recent years, the construction of hundreds to thousands of large-scale satellite constellations has begun, increasing the risk of satellite collisions in orbit. In addition, debris such as artificial satellites that have become uncontrollable due to breakdowns 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 debris in outer space and the rapid increase in the number of satellites including mega constellations, the need for space traffic control (STM) is increasing.

In addition, in order to avoid collisions with space objects, ADR that debris debris such as debris such as the upper stage of a floating rocket and debris that has left orbit (PMD) or failed after the mission in orbit is completed by external means such as a debris recovery satellite. The need is increasing. International discussions have begun as STM on the need for such ADR. 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, the size of space objects that can be grasped can be monitored even smaller due to the strengthening of the system including international cooperation of space situation monitoring (SSA) and the improvement of observation accuracy. Also, the total number of space objects that can be monitored is increasing.

The collision avoidance support device 100 according to the present embodiment supports avoidance of collisions between space objects in a plurality of space objects 60 flying in space. As described above, the risk of collision of the space object 60 is increasing with the rapid increase of space objects such as satellites and debris in outer space.

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

FIG. 5 is a block diagram of the satellite constellation formation system 600.
The satellite constellation formation system 600 includes a computer. Although FIG. 5 shows the configuration of one computer, in reality, each satellite 30 of the plurality of satellites constituting the satellite constellation 20 and the ground equipment 700 communicating with the satellite 30 are equipped with a computer. Be done. Then, the computers provided in each of the satellites 30 of the plurality of satellites and the ground equipment 700 communicating with the satellites 30 cooperate to realize the function of the satellite constellation formation system 600. Hereinafter, an example of a computer configuration that realizes the functions of the satellite constellation formation system 600 will be described.

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

The satellite constellation forming system 600 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 other hardware via a signal line and controls these other hardware. The hardware of the satellite constellation formation system 600 is the same as the hardware of the collision avoidance support device 100, which will be described later in FIG.

The satellite constellation forming system 600 includes a satellite constellation forming unit 11 as a functional element. 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 satellite 30.

FIG. 6 is a block diagram of the satellite 30 of the satellite constellation formation system 600.
The satellite 30 includes 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. In addition, although it includes components that realize various functions, FIG. 6 describes 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 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 according to various commands transmitted from the ground equipment 700.
The satellite communication device 32 is a device that communicates with the ground equipment 700. Specifically, the satellite communication device 32 transmits various data related to its own satellite to the ground equipment 700. Further, the satellite communication device 32 receives various commands transmitted from the ground equipment 700.
The propulsion device 33 is a device that gives a 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 uses the attitude of the satellite 30, the angular velocity of the satellite 30, and the line-of-sight direction (Line Of).
It is a device for controlling a posture element such as Sign). The attitude control device 34 changes each attitude element in a desired direction. Alternatively, the attitude control device 34 maintains each attitude element in a desired direction. The attitude control device 34 includes an attitude sensor, an actuator, and a controller. Attitude sensors are devices such as gyroscopes, earth sensors, sun sensors, star trackers, thrusters and magnetic sensors. Actuators are devices such as attitude control thrusters, momentum wheels, reaction wheels and control moment gyros. The controller controls the actuator according to the measurement data of the attitude sensor or various commands from the ground equipment 700.
The power supply device 35 includes devices such as a solar cell, a battery, and a power control device, and supplies power to each device mounted on the satellite 30.

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

FIG. 7 is a configuration diagram of the ground equipment 700 included in the satellite constellation formation system 600.
The ground equipment 700 programmatically controls a large number of satellites in all orbital planes. The ground equipment 700 is an example of a ground device. The ground device 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 a terminal connected to the ground station via a network. Further, the ground device may include a communication device mounted on a moving body such as an aircraft, a self-propelled vehicle, or a mobile terminal.

The ground equipment 700 forms a 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 other hardware via a signal line and controls these other hardware. The hardware of the ground equipment 700 is the same as the hardware of the collision avoidance support device 100 described later in FIG.

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

The communication device 950 transmits / receives a signal for tracking and controlling each satellite 30 of the satellite group 300 constituting the satellite constellation 20. Further, the communication device 950 transmits an orbit control command 55 to each satellite 30.
The analysis prediction unit 520 analyzes and predicts the orbit of the satellite 30.
The orbit control command generation unit 510 generates an orbit 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 examples of the satellite constellation formation unit 11.

FIG. 8 is a diagram showing a functional configuration example of the satellite constellation formation system 600.
The satellite 30 further includes a satellite constellation forming unit 11b that forms the satellite constellation 20. Then, the satellite constellation forming unit 11b of each satellite 30 of the plurality of satellites and the satellite constellation forming unit 11 provided in each of the ground equipment 700 cooperate to realize the function 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.

*** Explanation of configuration ***
FIG. 9 is a configuration diagram of the collision avoidance support system 500 according to the present 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 the ground equipment. Alternatively, the collision avoidance support device 100 may be mounted on the satellite 30. Further, the collision avoidance support device 100 may be mounted on the satellite constellation formation 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 apparatus 40 provides information on 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 about a space object 60 such as an artificial satellite or debris.
The management business device 40 includes a mega constellation business device 41, a LEO constellation business device 42, a satellite business device 43, an orbit transition business device 44, a debris recovery business device 45, a rocket launch business device 46, and an SSA business device 47. Equipment is included. LEO is an abbreviation for Low Earth Orbit.

The mega constellation business device 41 is a computer of a large-scale satellite constellation, that is, a mega constellation business operator that carries out a mega constellation business.
The LEO constellation business apparatus 42 is a computer of a low-earth orbit constellation, that is, a computer of a LEO constellation business operator that carries out a LEO constellation business.
The satellite operator 43 is a computer of a satellite operator that handles one to several satellites.
The orbit transition business device 44 is a computer of the orbit transition business operator that supports the orbit transition of the satellite.
The debris collection business device 45 is a computer of a debris collection business operator that conducts a business of collecting debris.
The rocket launch business device 46 is a computer of a rocket launch business that carries out a rocket launch business.
The SSA business device 47 is a computer of an SSA business operator that carries out an SSA business, that is, a space condition monitoring business.

The management business device 40 may be any other device as long as it is a device that collects information about a space object such as an artificial satellite or debris and provides the collected information to the collision avoidance support device 100. When the collision avoidance support device 100 is mounted on the public server of the SSA, the collision avoidance support device 100 may function as the public server of the SSA.
The information provided from the management business device 40 to the collision avoidance support device 100 will be described in detail later.

The collision avoidance support device 100 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 other hardware via a signal line and controls these other hardware.

The collision avoidance support device 100 includes a recorder processing unit 110, an alarm control unit 120, a result presentation unit 130, and a storage unit 140 as functional elements. The space information recorder 50 and the alarm issuance information 141 are stored in the storage unit 140.

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. Further, the storage unit 140 may be provided separately as a memory 921 and an 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 alarm control unit 120, and the result presentation unit 130.
The processor 910 is an IC (Integrated Circuit) that performs arithmetic processing. A specific example of the processor 910 is a CPU (Central Processing).
Unit), DSP (Digital Signal Processor), GPU (Graphics Processing Unit).

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

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

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 support program is read into the processor 910 and executed by the processor 910. In the memory 921, not only the collision avoidance support program but also the OS (Operating System) is stored. The processor 910 executes a collision avoidance support program while executing the OS. The collision avoidance support program and the OS may be stored in the auxiliary storage device 922. The collision avoidance support program and the OS stored in the auxiliary storage device 922 are loaded into the memory 921 and executed by the processor 910. A part or all of the collision avoidance support program may be incorporated in the OS.

The collision avoidance support device 100 may include a plurality of processors that replace the processor 910. These multiple processors share the execution of the program. Each processor, like the processor 910, is a device that executes a program.

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

The "part" of each part of the collision avoidance support device may be read as "processing", "procedure", "means", "step" or "process". Further, the "process" of the recorder process, the alarm control process, and the result presentation process may be read as "program", "program product", or "computer-readable recording medium on which the program is recorded".
In the collision avoidance support program, each process, each procedure, each means, each stage in which the "part" of each part of the collision avoidance support device is read as "process", "procedure", "means", "step" or "process". Alternatively, let the computer execute each process. The collision avoidance support method is a method performed by the collision avoidance support device executing a collision avoidance support program.
The collision avoidance support program may be provided stored in a computer-readable recording medium. In addition, each program may be provided as a program product.

*** Explanation of operation ***
The collision avoidance support process by the collision avoidance support device 100 according to the present embodiment will be described with reference to FIGS. 10 to 19.

<Recorder processing (orbit forecast information): S100>
FIG. 10 is a flow chart of a recorder process for setting the orbit forecast information 51 according to the present embodiment. Further, FIG. 11 is a diagram showing an example of the orbit forecast information 51 according to the present embodiment.

In step S101, the recorder processing unit 110 acquires flight forecast information 401 representing the flight forecast of each of the plurality of space objects 60 from the management business device 40 used by the management company that manages the plurality of space objects 60. To do. As described above, the management company is a company that manages space objects 60 flying in space such as satellite constellations, various satellites, rockets, and debris. Further, as described above, the management business equipment 40 used by each management business operator is a mega constellation business equipment 41, a LEO constellation business equipment 42, a satellite business equipment 43, an orbit transition business equipment 44, and a debris collection business equipment. Computers such as 45, rocket launch business equipment 46, and SSA business equipment 47.

In step S102, the recorder processing unit 110 makes a forecast in the orbit with the forecast source period 512 of each orbit of the plurality of space objects, the forecast orbit element 513 that specifies the orbit, and the forecast orbit element 513 that specifies the orbit, based on the acquired flight forecast information 401. The forecast error 514 is set as the orbit forecast information 51. Then, the recorder processing unit 110 stores the space information recorder 50 including the orbit forecast information 51 in the storage unit 140. The orbit forecast information 51 is a forecast value of each orbit of a plurality of space objects.

The recorder processing unit 110 may set the forecast of the flight state of each of the plurality of space objects as the forecast flight state 515 in the orbit forecast information 51 based on the flight forecast information 401. At this time, the recorder processing unit 110 sets the forecast flight state 515 of each of the plurality of space objects to be in the steady operation state or the unsteady operation state of each of the plurality of space objects. The steady operation state is specifically a state in which the satellite is flying in orbit in steady operation. In the unsteady operation state, the launch transient state from the launch of each of the multiple space objects to the time they are put into orbit, and the state after each of the multiple space objects leaves the orbit until they are put into the atmosphere or abandoned orbit. A state such as a transient state after leaving the universe is included.

An example of the orbit forecast information 51 according to the present embodiment will be described with reference to FIG.
Space object ID (Identifier) 511, forecast epoch 512, forecast orbital element 513, forecast error 514, and forecast flight state 515 are set in the orbit forecast information 51.

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 recovery satellites, planetary exploration spacecraft, and satellites or rockets that have become debris after the mission is completed.

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

The forecast error 514 is an error predicted in each orbit of a plurality of space objects. The forecast error 514 is set with a traveling direction error, an orthogonal direction error, and a basis for the error. In this way, the forecast error 514 explicitly indicates the amount of error included in the actual value together with the grounds. The basis of the amount of error includes the measurement means, the content of the data processing performed as the means for improving the accuracy of the position coordinate information, and a part or all of the statistical evaluation result of the past data.

The forecast flight state 515 is a forecast of the flight state of each of the plurality of space objects. In the forecast flight state 515, it is set whether the forecast of the flight state of each of the plurality of space objects is the steady operation state, the launch transient state, or the transient state after departure. Further, the forecast flight state 515 may include whether or not the avoidance operation can be carried out or whether or not the autonomous avoidance operation can be carried out.

In the orbit forecast information 51 according to the present embodiment, the forecast epoch 512 and the forecast orbit element 513 are set for the space object 60. The time and position coordinates of the space object 60 in the near future can be obtained from the forecast epoch 512 and the forecast orbital element 513. For example, the near future time and position coordinates of the space object 60 may be set in the orbit forecast information 51.
As described above, the orbit forecast information 51 includes the orbit information of the space object including the original period and the orbit elements, or the time and position coordinates, and the near future forecast value of the space object 60 is explicitly shown. There is.

<Recorder processing (orbit record information): S200>
FIG. 12 is a flow chart of a recorder process for setting the track record information 52 according to the present embodiment. Further, FIG. 13 is a diagram showing an example of the track record information 52 according to the present embodiment.

In step S201, the recorder processing unit 110 acquires flight record information 402 representing the flight record of each of the plurality of space objects from at least one of each of the plurality of space objects and the management business apparatus 40. Specifically, the recorder processing unit 110 acquires flight record information 402 from the management company that manages the space object 60. Alternatively, the recorder processing unit 110 may acquire the flight record information 402 directly from the space object 60.

In step S202, the recorder processing unit 110 determines the actual original period 522 of each orbit of the plurality of space objects, the actual orbital element 523 that specifies the orbit, and the plurality of space objects based on the acquired flight record information 402. Each actual position coordinate 242 is set as the orbit actual information 52. Then, the recorder processing unit 110 includes the orbital record information 52 in the space information recorder 50.
The recorder processing unit 110 may set the actual flight state of each of the plurality of space objects as the actual flight state 525 in the orbit record information 52 based on the flight record information 402. At this time, the recorder processing unit 110 sets, in the actual flight state 525 of each of the plurality of space objects, whether each of the plurality of space objects is in the steady operation state or the unsteady operation state. In the unsteady operation state, the launch transient state from the launch of each of the multiple space objects to the time they are put into orbit, and the state after each of the multiple space objects leaves the orbit until they are put into the atmosphere or abandoned orbit. Includes a transient state after withdrawal.

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

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

The actual epoch 522 is the actual epoch of each orbit of a plurality of cosmic objects.
The actual orbital element 523 is an orbital element that specifies the orbit of each of a plurality of space objects. The actual orbital element 523 is the actual orbital element of each orbit of a plurality of space objects. In FIG. 13, six Kepler orbital elements are set in the actual orbital element 523, similarly to the forecast orbital element 513.

In the specific actual 524, the specific time 241 and the position coordinates of the space object 60 corresponding to the specific time 241 are set as the actual position coordinates 242. As described above, the orbital actual information 52 includes the actual position coordinates 242 which are the position coordinates of the space object 60 at the specific time 241.

The actual flight state 525 is the actual flight state of each of the plurality of space objects. In the actual flight state 525, whether the actual flight state of each of the plurality of space objects is a steady operation state, a launch transient state, or a transient state after departure is set. Further, the actual flight state 525 may include whether or not the avoidance operation can be carried out or whether or not the autonomous avoidance operation can be carried out. The configuration of the actual flight state 525 is the same as that of the forecast flight state 515.

<Alarm control processing: S300>
FIG. 14 is a flow chart of an alarm control process by the alarm control unit 120 according to the present embodiment.

In step S301, the alarm control unit 120 determines the existence or nonexistence of a space object having a positional relationship in which an alarm should be issued, based on the orbit forecast information 51. Specifically, the warning control unit 120 determines whether or not, among the plurality of space objects, a plurality of space objects having overlapping error ranges 502 at the same time exist as the collision prediction object 601 based on the orbit forecast information 51. judge. Further, the warning control unit 120 determines, based on the orbital forecast information 51, whether or not, among the plurality of space objects, a plurality of space objects approaching beyond the approach threshold value at the same time exist as approach prediction objects 602. To do. The collision prediction object 601 and the approach prediction object 602 are examples of the danger prediction object 65, which is a plurality of space objects whose positional relationship is dangerous at the same time among the plurality of space objects.

If the collision prediction object 601 is present, the process proceeds to step S302. If the approach prediction object 602 is present, the process proceeds to step S303. If neither the collision prediction object 601 nor the approach prediction object 602 exists, the process returns to step S301.

In step S302, the warning control unit 120 outputs a collision warning 23 indicating that there is a possibility of collision with respect to the collision prediction object 601.
In step S303, the warning control unit 120 outputs an approach warning 22 indicating that there is a possibility of approaching the approach prediction object 602.

FIG. 15 is a diagram showing a cross image of the error ranges 502a and 502b of the two satellites 30a and 30b according to the present embodiment.
The orbit forecast 501a of the satellite 30a is obtained from the forecast epoch and the forecast orbit element corresponding to the satellite 30a in the orbit forecast information 51. The epoch of the forecast is also called epoch. The forecast orbital element is also referred to as an orbital 6 element. Similarly, the orbit forecast 501b of the satellite 30b is obtained from the forecast epoch and the forecast orbit element corresponding to the satellite 30b in the orbit forecast information 51.
The alarm control unit 120 acquires the orbit forecasts 501a and 501b and the error ranges 502a and 502b of the satellites 30a and 30b based on the orbit forecast information 51. It should be noted that the orbit forecast 501 and the error range 502 shall distinguish whether they correspond to the satellite 30a or the satellite 30b by the subscripts given to the symbols.

FIG. 16 is a diagram showing a state in which the error ranges 502a and 502b of the two satellites 30a and 30b according to the present embodiment overlap.
Based on the orbit forecast information 51, the alarm control unit 120 determines whether or not a plurality of space objects having overlapping error ranges 502 exist as the collision prediction object 601 at the same time. In FIG. 16, the two satellites 30a and 30b are determined to be collision prediction objects 601.

FIG. 17 is a diagram showing a state in which the distance between the two satellites 30 according to the present embodiment is equal to or less than the approach threshold value.
Based on the orbit forecast information 51, the alarm control unit 120 determines whether or not a plurality of space objects approaching beyond the approach threshold value at the same time exist as approach prediction objects 602. The approach threshold is a threshold for determining that the approach alarm 22 is issued. In FIG. 17, the two satellites 30a and 30b are determined to be approach prediction objects 602.

In this way, the alarm control unit 120 issues the collision alarm 23 when the contact or shared area of the error range 502 occurs in the analysis result. Further, when the two space objects approach each other below the approach threshold value or exceed the approach threshold value, the warning control unit 120 determines that there is a risk of collision and issues an approach warning 22.

FIG. 18 is a diagram showing alarm issuance information 141 according to the present embodiment.
The warning issuance information 141 is transmitted to the management business apparatus 40 and used for collision avoidance operation.
In the warning issuance information 141, the identifier of the space object for which the collision warning 23 or the approach warning 22 is issued, the time, the position coordinates at that time, and the overlapping distance or the approaching distance of the error range are set.
The collision warning 23 or the approach warning 22 is an example of the danger warning 25 indicating that there are a plurality of space objects whose positional relationship is dangerous at the same time.

<Result presentation processing>
FIG. 19 is a flow chart of the result presentation process by the result presentation unit 130 according to the present embodiment.
In step S41, when any of the space objects of the plurality of space objects collides with each other, the result presentation unit 130 extracts the orbit record information 52 at the time when the space objects collide with each other as the collision record 131 from the orbit record information 52. To do. Then, the result presentation unit 130 presents the collision result 131 to the output device. For example, the management company notifies the information that one of the plurality of space objects has collided with each other.

Hereinafter, specific examples of satellite orbit information will be described.
As shown in FIGS. 11 and 13, the orbital elements (Keplerian Elements) based on Kepler's law are used as the orbital information of the satellite. Orbital elements based on Kepler's law are composed of the following elements.
・ Epoch: Epoch (year and day)
-Average exercise (m): Mean Motion (circulation / day) or semi-major axis Semi-major Axis (km)
・ Eccentricity: Eccentricity (no unit)
-Orbital inclination (i): Inclination (degrees)
-Right ascension (Ω): RAAN (Right Ascension of Ascending Node) (degree)
-Argument of periapsis (ω): Argument of Perigee (degree)
-Mean anomaly (M): Mean Anomaly (degrees)

Further, a format called TLE (Two Line Element) may be used.

In positioning satellites, the time and position in orbit and the timing of transmitting positioning signals directly affect the positioning accuracy. Therefore, satellite information such as almanac, ephemeris, or precision orbital calendar is used properly according to the accuracy, distribution method, or the difference between the forecast value and the actual value.
Focusing on accuracy, there is a relationship of almanac (accuracy: several hundred meters to several kilometers)> ephemeris (broadcasting calendar) (accuracy: several meters)> precision calendar (accuracy: several centimeters). Focusing on delivery methods, almanacs and ephemeris are transmitted directly from satellites and are also available via the Internet or mobile phone lines. In the positioning satellites that form a constellation with a large number of satellites, the coarse-precision ephemeris transmits information on all satellites, and the precise ephemeris transmits only information on its own satellite.

On the other hand, forecast values of accuracy effective for collision avoidance have not been released for the transient state of launch until the satellite reaches steady operation, and the transient state of entering the atmosphere or reaching the disposal orbit after leaving the orbit. Also, the orbit forecast value for rocket launch is not public information.
At a minimum, the location of the launch point, the scheduled launch time, and the scheduled flight route will be disclosed, and accurate information that can verify whether there is a risk of collision with a satellite owned by a satellite constellation operator at an altitude of 600 km or less will be disclosed.

The orbit forecast information 51 (orbit forecast value disclosure information) and the orbit record information 52 (precision orbit calendar record) do not necessarily exist in the same storage location. The track record information 52 may be in a state where it can be handled when necessary, such as after a collision accident occurs. For example, when the insurance company uses it in the insurance business, it may be a storage location disclosed only to the insurance company by the business 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 acquired from a management business device used by a management business operator that manages a plurality of space objects. Space object information includes orbit forecast information. The orbital forecast information includes the forecasting period of the space object, the forecasted orbital element, the forecast error, and the estimated time or time of the collision occurrence when the collision between the space object A and the space object B included in the plurality of space objects is predicted. Bands and are included.

In addition, the space object information includes orbital record information. The orbital record information includes the collision occurrence time estimated by the ex-post verification after the collision accident between the space object A and the space object B included in the plurality of space objects, and the position information of the space object A at or immediately before the collision occurrence time. , The position information of the space object B at or immediately before that time.

In addition, the space object information includes orbit forecast information including the forecast source period of the space object, the forecast orbital element, the forecast error, and the launch plan time and orbit information of the rocket launcher.

In addition, the space object information includes the orbit forecast information including the forecast source period of the space object, the forecast orbit element, the forecast error, and the deorbit planning time and orbit information of the space object operator or the debris removal operator in the deorbit process. Is included.

In addition, the space object information includes orbit forecast information including the forecast source period of the space object, the forecast orbit element, the forecast error, the orbit transition planned time and the orbit information of the satellite operator in the orbit transition process.

The orbit forecast information includes a basis for calculating the error amount of the forecast error. In addition, the orbit forecast information may include the verification results that led to the derivation of the forecast error. In addition, the orbit forecast information may include identification of regular operation or non-steady operation. In addition, the orbit forecast information may include whether or not avoidance operation can be performed. In addition, the orbit forecast information may include whether or not autonomous avoidance operation can be carried out.

*** Explanation of the effect of this embodiment ***
According to the collision avoidance support device 100 according to the present embodiment, the recorder processing unit 110 acquires flight forecast information 401 representing the flight forecast of each of the plurality of space objects from the management business device 40. Then, the recorder processing unit 110 sets the forecast value of the orbit of each space object and the forecast value including the forecast error as the orbit forecast information 51 in the space information recorder 50 based on the flight forecast information 401. Therefore, according to the collision avoidance support device 100 according to the present embodiment, collision avoidance can be accurately avoided by using the orbit forecast information 51 that takes into account the expected orbital error for each of the plurality of space objects. It has the effect of being able to support.

Further, according to the collision avoidance support device 100 according to the present embodiment, the recorder processing unit 110 has a flight record of each of the plurality of space objects from at least one of each of the plurality of space objects and the management business device 40. The flight record information 402 representing the above is acquired. Then, the recorder processing unit 110 sets the space information recorder 50 as the orbital record information 52 based on the flight record information 402. Therefore, according to the collision avoidance support device 100 according to the present embodiment, there is an effect that the flight record desired by the management operator can be immediately presented.

In the collision avoidance support device 100 according to the present embodiment, flight record information 402 was 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. That is, the collision avoidance support device may include means for measuring the time and orbit information of the satellite, and may record the orbit history with respect to the orbit forecast information published in advance.

In the collision avoidance support device 100 according to the present embodiment, for example, the predicted orbit information of the satellite at the scheduled launch time can be disclosed to the rocket launcher who is planning to launch a new rocket. This will allow rocket launchers to take measures to avoid collisions. Further, the space information recorder 50 of the collision avoidance support device 100 according to the present embodiment has an effect that the predicted orbit and the actual orbit history can be compared and verified.

In the collision avoidance support device 100 according to the present embodiment, the flight record information 402, that is, the measurement device information mounted on the satellite may be used as the measuring means of the precision orbit calendar record.
The satellites that make up the mega constellation are capable of inter-satellite communication or inter-satellite distance measurement with satellites that fly before and after the same orbital plane or satellites that fly in adjacent orbits. Therefore, by using the measurement device information mounted on the satellite by the collision avoidance support device 100 according to the present embodiment, it is possible to measure the orbit information with high accuracy including the measurement information of the GPS receiver provided by the satellite. effective. In addition, there is an effect that the accuracy can be improved by statistical processing of many satellites.

The collision avoidance support device 100 according to the present embodiment includes a space information recorder 50 and is mounted on a ground facility.

The aircraft will be equipped with a voice recorder for the purpose of verifying aircraft accidents. In addition, automobiles will be equipped with drive recorders for the purpose of verifying and providing evidence of automobile accidents.
With the advent of mega constellation operators, satellite constellations with thousands of satellites constructed at low orbit altitudes of about 600 km or less have a high risk of collision when launching a new rocket. Therefore, a "space information recorder" that should be called a satellite drive recorder is required for the same purpose as the above voice recorder or drive recorder.
Even if an aircraft accident is an explosive accident, there is a possibility that the onboard equipment can be recovered after the accident. For this reason, voice recorders are designed to be robust enough to withstand explosions. In addition, since there is a driver in the aircraft, by recording not only the information of the measuring instruments but also the voice of the operator, the voice recording is left so that it can be verified after the accident, including the presence or absence of abnormalities in the instruments. It has become. On the other hand, in a satellite collision, it is difficult for the onboard equipment to dissipate into outer space and be recovered after the accident, and there is no operator. Therefore, voice recording is not required, and the main purpose is to record the data of the on-board measuring instruments. Therefore, after the flight record is acquired, it is necessary to quickly transmit the data to the ground or another satellite, and the data up to immediately before the collision accident is stored in another place.

If a collision accident occurs in outer space and the satellite is scattered, it will be difficult to recover the onboard equipment. The satellite constellation concept enables real-time data communication between satellites and the ground or between satellites. Therefore, flight record information, that is, satellite orbit history information can also be transmitted in real time. The track record information placed on the ground equipment can be referred to after the accident, which has the effect of being effective as a basis for verifying the accident situation.

In the collision avoidance support device 100 according to the present embodiment, the flight record information, that is, the measurement information of the SSA asset, which is a ground observation device, may be used as a means for measuring the precision track calendar record.
Recently, the maintenance of SSSA assets using ground-mounted telescopes or radar has progressed, and the measurement accuracy has also improved. The SSA information provider can also handle the satellite orbit history, which has the effect of being able to be objectively verified by a third party.

The collision avoidance support device 100 according to the present embodiment reads IC tag information of an artificial space object having an IC tag having a satellite identification ID, time, and position information, and an artificial space object flying far away without contact. A means is provided, and the content is updated based on the IC tag information.
The satellite constellation is designed so that when the satellites approach each other within 100 km, for example, the IC tag provided on the satellite emits radio waves for near-field communication that can be received by the non-trial omni-antenna. As a result, close satellites can receive each other's satellite information, and if there are many opportunities for approaching in a mega constellation, the orbital record information that can be shared in orbit over time will increase. In particular, when the orbital measurement information of the own satellite is more accurate than the ground measurement means, the IC tag is effective as a means for acquiring the high-precision orbital information.

In the collision avoidance support device 100 according to the present embodiment, the orbit forecast information, that is, the satellite orbit prediction information may be disclosed to the rocket launcher, the orbit insertion operator, and the debris collection operator for a fee.
In order for rocket launchers to fulfill their flight safety obligations, the predicted orbit information of satellites that make up an accurate mega constellation is required, and the asset value of the satellite orbit prediction information is highly evaluated, and the satellite operator's profits. It has the effect of being a source.
In addition, there is a high risk of collision with the mega constellation satellite in the process of the satellite leaving orbit and debris after the mission, and the operator of the debris satellite who neglected the collision avoidance measures for the orbit information that was also released, Or there is a possibility that the responsibility of the debris collection company can be pursued, and satellite orbit information has the effect of becoming a source of revenue.
Furthermore, the operator who inserts the geostationary satellite into orbit will make a transition to the geostationary orbit with the propulsion device provided by the satellite after launching it to the geostationary transfer orbit with a rocket, so there is a risk of collision with the mega constellation satellite in the process. Similar effects are expected.

*** Other configurations ***
<Modification example 1>
The space information recorder may have a processor that stores the orbital forecast information and the orbital record information in the memory and executes the program. For example, the space information recorder may have the functions described below.

The space information recorder is provided with a means for setting a premium rate of a space insurance program that pays insurance money from a premium collected in advance when a space object A and a space object B collide with each other among a plurality of space objects. The insurance premium rate setting means sets the insurance premium rate based on the forecast error included in the track forecast information.

Further, the space information recorder is provided with an insurance claim assessment means of a space insurance program that pays insurance money from a premium collected in advance when a space object A and a space object B collide with each other among a plurality of space objects. The insurance money assessment means extracts the orbit record information at the time when the space objects collide with each other as the collision record from the orbit record information, and extracts the orbit forecast information at the time when the space objects collide with each other as the pre-collision forecast information from the orbit forecast information. To do. Then, the insurance money assessment means obtains the insurance money based on the comparison between the difference information A between the collision record of the space object A and the pre-collision forecast information and the difference information B between the collision record of the space object B and the pre-collision forecast information. Assess.

The forecast error includes one or both of the basis of the forecast error and the verification result of the forecast error.

In addition, the space information recorder is used by insurance companies and management companies that implement space insurance programs that pay insurance money from insurance premiums collected in advance when space object A and space object B collide with each other. , Provide means to output a danger alarm.

In addition, the space information recorder is used by insurance companies and management companies that implement space insurance programs that pay insurance money from the premiums collected in advance when space object A and space object B collide with each other. , Provide means to output track record information.

In addition, the space information recorder has a plurality of space objects whose positional relationship is dangerous at the same time in the debris collection company that collects the debris generated when the space object A and the space object B collide with each other. Provide a means for outputting a danger alarm indicating that the universe is to be used.

In addition, the space information recorder identifies the existence of the danger prediction object based on the orbit forecast information and outputs a danger warning before the space objects in multiple space objects collide with each other, and determines the space object to be avoided. Execute the collision avoidance support program. The space information recorder determines whether or not a danger prediction object exists among a plurality of space objects based on the orbit forecast information, and if it is determined that a danger prediction object exists, a danger warning is output. Execute a collision avoidance support program provided with output means. Further, after the danger warning is output, the space information recorder executes a collision avoidance support program provided with an avoidance space object determination means for determining a space object to be avoided among the space objects included in the danger prediction object.

In addition, the space information recorder is a disclosure threshold value for determining whether or not to disclose orbit forecast information to different management business devices when it is predicted that space objects in a plurality of space objects will approach each other at a specific time. And an information disclosure means for determining whether or not to disclose.

<Modification 2>
In the present embodiment, the function of the collision avoidance support device 100 is realized by software. As a modification, the function of the collision avoidance support device 100 may be realized by hardware.

FIG. 20 is a diagram showing a configuration of a collision avoidance support device 100 according to a modified example of the present embodiment.
The collision avoidance support device 100 includes an electronic circuit instead of the processor 910.
The electronic circuit is a dedicated electronic circuit that realizes the function of the collision avoidance support 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 for Gate Array.
The function of the collision avoidance support device 100 may be realized by one electronic circuit, or may be realized by being distributed in a plurality of electronic circuits.
As another modification, some functions of the collision avoidance support device 100 may be realized by an electronic circuit, and the remaining functions may be realized by software.

Each of the processor and the electronic circuit is also called a processing circuit. That is, the function of the collision avoidance support device 100 is realized by the processing circuit.

Embodiment 2.
In this embodiment, the points different from those in the first embodiment will be mainly described. The same components as those in the first embodiment may be designated by the same reference numerals, and the description thereof may be omitted.

In the present embodiment, when the danger warning 25 is issued based on the orbit forecast information 51, the collision avoidance support device 100a for appropriately determining which of the danger prediction objects 65 should perform the avoidance action will be described. To do.

*** Explanation of configuration ***
FIG. 21 is a configuration diagram of the collision avoidance support device 100a of the collision avoidance support system 500 according to the present embodiment.
The collision avoidance support 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 the collision avoidance support device 100 of the first embodiment. Other functional elements and hardware configurations are the same as those in the first embodiment. Further, the collision avoidance support program according to the present embodiment is a program that realizes at least the functions of the alarm control unit 120, the avoidance determination unit 150, and the machine learning unit 160. That is, the collision avoidance support program according to the present embodiment causes the computer to execute at least the alarm control process, the avoidance decision process, and the machine learning process.

Based on the orbital forecast information 51, the alarm control unit 120 determines whether or not, among the plurality of space objects, a plurality of space objects whose positional relationship is dangerous at the same time exists as the danger prediction object 65. When it is determined that the danger prediction object 65 exists, the alarm control unit 120 outputs a danger alarm 25 indicating that the danger prediction object 65 exists. The method of outputting the danger alarm 25 by the alarm 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 the avoidance space object 69, which is a space object that performs avoidance operation, among the space objects included in the danger prediction object 65. The conditions used for determining the avoidance space object 69 are as follows, for example.
The avoidance determination unit 150 determines the avoidance space object 69 based on whether or not each space object included in the danger prediction object 65 is a rocket at the time of launch.
The avoidance determination unit 150 determines the avoidance space object 69 based on whether or not each space object included in the danger prediction object 65 belongs to the mega constellation.
The avoidance determination unit 150 determines the avoidance space object 69 based on whether each space object included in the danger prediction object 65 is in the steady operation state or the unsteady operation state.
The avoidance determination unit 150 determines the avoidance space object 69 based on whether or not each space object included in the danger prediction object 65 is an orbit transition satellite performing the orbit transition.
The avoidance determination unit 150 determines the avoidance space object 69 based on whether or not each space object included in the danger prediction object 65 has a collision avoidance function.
The avoidance determination unit 150 determines the avoidance space object 69 based on whether or not each space object included in the danger prediction object 65 is located in a dense orbit.

The avoidance determination unit 150 determines the avoidance space object 69 from the danger prediction object 65 by using any of the above conditions or a plurality of combinations of the above conditions.

The machine learning unit 160 updates the algorithm of the avoidance determination process for determining the avoidance space object 69 by machine learning using the result of determining the avoidance space object 69, that is, the determination result by the avoidance determination unit 150.

*** Explanation of operation ***
The collision avoidance support process by the collision avoidance support device 100a according to the present embodiment will be described with reference to FIGS. 22 to 25.
Here, it is assumed that the space object A and the space object B exist as the danger prediction object 65 which is a plurality of space objects whose positional relationship is dangerous at the same time.

<Avoidance decision processing>
22 and 23 are flow charts showing an example of avoidance determination processing based on conditions such as whether or not the space object according to the present embodiment is a rocket.
22 and 23 show the avoidance universe depending on the conditions such as whether the space object is a rocket, whether the space object is an artificial satellite belonging to a mega constellation, and whether the space object is debris. This is an example of a process for determining the object 69.

In step S101, the avoidance determination unit 150 determines whether or not the space object A is an artificial satellite. Specifically, the avoidance determination 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. For example, the collision avoidance support device 100 may have a management table in which the space object ID and the type of the space object are associated with each other. The avoidance determination unit 150 may acquire 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.
When the space object A is an artificial satellite, in step S102, the avoidance determination unit 150 determines whether or not the space object B is an artificial satellite.
When both the space object A and the space object B are artificial satellites (YES in step S102), the process proceeds to at least one of M1 to M4.

When 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 by using the space object ID 511 of the orbit forecast information 51 shown in FIG. For example, the collision avoidance support device 100 may have a management table in which the space object ID and the type of the space object are associated with each other. The avoidance determination unit 150 may acquire 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 a rocket.
When the space object A is an artificial satellite and the space object B is a rocket (step S104), in step S105, the avoidance determination unit 150 determines whether or not the space object A belongs to the mega constellation.
When the space object A is an artificial satellite and the space object B is not a rocket, that is, debris (step S104a), the process proceeds to step S106.
In step S105, if the space object A belongs to the mega constellation, the process proceeds to step S106.
In step S105, if the space object A does not belong to the mega constellation, the process proceeds to step S111.

In step S101, when 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.
In step S107, when the space object A is a rocket, in step S108, the avoidance determination unit 150 determines whether or not the space object B is an artificial satellite.
When the space object A is a rocket and the space object B is an artificial satellite (step S109), in step S110, the avoidance determination unit 150 determines whether or not the space object B belongs to the mega constellation.
If the space object B does not belong to the mega constellation in step S110, the process proceeds to step S106.
If the space object B belongs to the mega constellation in step S110, the process proceeds to step S111.

In step S108, when 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, when the space object B is a rocket, both the space object A and the space object B are rockets. At this time, in step S113, the avoidance determination unit 150 excludes the danger prediction object 65 from the avoidance determination process.
In step S112, when the space object B is not a rocket, that is, the space object B is debris, the space object A is a rocket and the space object B is debris (step S114). At this time, the process proceeds to step S106.

In step S106, the avoidance determination unit 150 determines the space object A as the avoidance space object 69 to be avoided and operated among the space objects included in the danger prediction object 65.
In step S111, the avoidance determination unit 150 determines the space object B as the avoidance space object 69 to be avoided and operated among the space objects included in the danger prediction object 65.

In step S107, when the space object A is not a rocket, in step S115, the avoidance determination unit 150 determines whether or not the space object A is debris.
In step S115, when the space object A is debris, in step S116, the avoidance determination unit 150 determines whether or not the space object B is an artificial satellite.
In step S116, when 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). At this time, the process proceeds to step S111.

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

If the space object B is not an artificial satellite in step S116, it is determined in step S118 whether the space object B is a rocket or not.
In step S118, when the space object B is a rocket, the space object A is debris and the space object B is a rocket (step S120). At this time, the process proceeds to step S111.
In step S118, if the space object B is not a rocket, both the space object A and the space object B become debris. At this time, in step S119, the avoidance determination unit 150 excludes the danger prediction object 65 from the avoidance determination process.

FIG. 24 is a flow chart of avoidance decision processing based on conditions such as whether or not the space object according to the present embodiment is in steady operation.
FIG. 24 is an example of a process of determining the avoidance space object 69 depending on the conditions such as whether the space object is in steady operation or unsteady operation. The process of FIG. 24 is referred to as M1 process. The steady operation state is specifically a state in which the satellite is flying in orbit in steady operation. In the unsteady operation state, the launch transient state from the launch of each of the multiple space objects to the time they are put into orbit, and the state after each of the multiple space objects leaves the orbit until they are put into the atmosphere or abandoned orbit. A state such as a transient state after leaving the universe is included.

In step S201, the avoidance determination unit 150 determines whether the space object A is in the steady operation state or the unsteady operation state. Specifically, the avoidance determination unit 150 determines whether the space object is in the steady operation state or the unsteady operation state by using the forecast flight state 515 of the orbit forecast information 51 shown in FIG.
In step S201, when the space object A is in the steady operation state, in step S202, the avoidance determination unit 150 determines whether the space object B is in the steady operation state or the unsteady operation state.
In step S202, when the space object B is in the steady operation state, both the space object A and the space object B are in the steady operation state. At this time, in step S203, the avoidance determination unit 150 determines that the space object A and the space object B do not collide.

In step S201, when the space object A is in the unsteady operation state, in step S205, the avoidance determination unit 150 determines whether the space object B is in the steady operation state or the unsteady operation state.
In step S205, when the space object B is in the steady operation state, the space object A is in the unsteady operation state and the space object B is in the steady operation state. At this time, in step S206, the avoidance determination unit 150 determines that the space object A in the unsteady operation state is the avoidance space object 69 to be avoided.
In step S205, when the space object B is in the unsteady operation state, both the space object A and the space object B are in the unsteady operation state. At this time, in step S207, the avoidance determination unit 150 does not determine the avoidance space object 69 because it is an example of performing individual adjustment.

In step S202, when the space object B is in the unsteady operation state, the space object A is in the steady operation state and the space object B is in the unsteady operation state. At this time, in step S204, the avoidance determination unit 150 determines that the space object B in the unsteady operation state is the avoidance space object 69 to be avoided.

FIG. 25 is a flow chart of avoidance decision processing based on conditions such as whether or not the space object according to the present embodiment belongs to a mega constellation.
FIG. 25 is an example of a process of determining the avoidance space object 69 based on conditions such as whether or not the space object belongs to the mega constellation. The process of 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 the mega constellation. Specifically, the avoidance determination unit 150 determines whether or not the space object belongs to the mega constellation by using the space object ID 511 of the orbit forecast information 51 shown in FIG. For example, the collision avoidance support device 100 may have a management table in which the space object ID and the space object management company are associated with each other. The avoidance determination unit 150 may acquire the management company of the space object from the management table by using the space object ID, and determine whether or not the space object belongs to the mega constellation.
In step S301, when the space object A belongs to the mega constellation, in step S302, the avoidance determination unit 150 determines whether or not the space object B belongs to the mega constellation.
In step S302, when the space object B belongs to the mega constellation, both the space object A and the space object B belong to the mega constellation. At this time, in step S303, the avoidance determination unit 150 determines that the space object A and the space object B do not collide.

In step S301, when the space object A does not belong to the mega constellation, in step S305, the avoidance determination unit 150 determines whether or not the space object B belongs to the mega constellation.
In step S305, when the space object B belongs to the mega constellation, the space object A does not belong to the mega constellation and the space object B belongs to the mega constellation. At this time, in step S306, the avoidance determination unit 150 determines that the space object B belonging to the mega constellation is the avoidance space object 69 to be avoided and operated.
In step S305, when the space object B does not belong to the mega constellation, neither the space object A nor the space object B belongs to the mega constellation. At this time, in step S307, the avoidance determination unit 150 does not determine the avoidance space object 69 because it is an example of performing individual adjustment.

In step S302, when the space object B does not belong to the mega constellation, the space object A belongs to the mega constellation and the space object B does not belong to the mega constellation. At this time, in step S304, the avoidance determination unit 150 determines that the space object A belonging to the mega constellation is the avoidance space object 69 to be avoided and operated.

FIG. 26 is a flow chart of avoidance decision processing based on conditions such as whether or not the space object according to the present embodiment is an orbit transition satellite.
FIG. 26 is an example of a process of determining the avoidance space object 69 based on conditions such as whether or not the space object is an orbit transition satellite that is transitioning in orbit. The process of 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 orbit transition satellite. Specifically, the avoidance determination unit 150 determines whether or not the space object is an orbit transition satellite by using the forecast flight state 515 of the orbit forecast information 51 shown in FIG.
In step S401, when the space object A is an orbit transition satellite, in step S402, the avoidance determination unit 150 determines whether or not the space object B belongs to the mega constellation.
In step S402, when the space object B belongs to the mega constellation, in step S403, the avoidance determination unit 150 determines that the space object B belonging to the mega constellation is the avoidance space object 69 to be avoided and operated.

In step S401, when the space object A is not an orbit transition satellite, in step S404, the avoidance determination unit 150 determines whether or not the space object B belongs to the mega constellation.
In step S404, when the space object B belongs to the mega constellation, in step S405, the avoidance determination unit 150 determines whether or not the space object B is an orbit transition satellite.
In step S405, when the space object B is an orbit transition satellite, the space object A is not an orbit transition satellite, and the space object B is an orbit transition satellite belonging to the mega constellation. At this time, in step S406, the avoidance determination unit 150 determines that the space object A is an avoidance space object 69 to be avoided and operated.

In step S402, if the space object B does not belong to the mega constellation, the space object A is an orbital transition satellite and the space object B does not belong to the mega constellation. At this time, in step S407, the avoidance determination unit 150 does not determine the avoidance space object 69 because it is an example of performing individual adjustment.

In step S404, if the space object B does not belong to the mega constellation, the space object A is not an orbital transition satellite and the space object B does not belong to the mega constellation. At this time, in step S407, the avoidance determination unit 150 does not determine the avoidance space object 69 because it is an example of performing individual adjustment.

In step S405, the space object B belongs to the mega constellation but is not an orbit transition satellite, and the space object A is not an orbit transition satellite. At this time, in step S407, the avoidance determination unit 150 does not determine the avoidance space object 69 because it is an example of performing individual adjustment.

FIG. 27 is a flow chart of avoidance determination processing based on conditions such as whether or not the space object according to the present embodiment has a collision avoidance function.
FIG. 27 is an example of a process of determining the avoidance space object 69 based on conditions such as whether or not the space object has a collision avoidance function in which the orbit is transitioning. The process of 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 by using the space object ID 511 of the orbit forecast information 51 shown in FIG. For example, the collision avoidance support device 100 may have a management table in which the space object ID and the function of the space object are associated with each other. The avoidance determination unit 150 may acquire the function of the space object from the management table by using the space object ID, and determine whether or not the space object has the collision avoidance function.

In step S501, when the space object A has a collision avoidance function, in step S502, the avoidance determination unit 150 determines whether or not the space object B has a collision avoidance function.
In step S502, when the space object B has a collision avoidance function, in step S503, the avoidance determination unit 150 determines whether or not the space object A invades the dense orbit. Specifically, the avoidance determination unit 150 determines whether or not the space object has a collision avoidance function by using the forecast flight state 515 of the orbit forecast information 51 shown in FIG.

In step S503, when the space object A invades the dense orbit, the space object A has a collision avoidance function and invades the dense orbit. Therefore, in step S504, the avoidance determination unit 150 determines that the space object A having a collision avoidance function and invading the dense orbit is the avoidance space object 69 to be avoided and operated.

In step S501, when the space object A does not have the collision avoidance function, in step S505, the avoidance determination unit 150 determines whether or not the space object B has the collision avoidance function.
In step S505, when the space object B has a collision avoidance function, in step S506, the avoidance determination unit 150 determines whether or not the space object B is in steady operation in a dense orbit.
In step S506, when the space object B is not in steady operation in the dense orbit, in step S507, the avoidance determination unit 150 determines that the space object B having the collision avoidance function is the avoidance space object 69 to be avoided.

If the space object B does not have the collision avoidance function in step S502, the process proceeds to step S506.
Further, in step S503, if the space object A does not enter the dense orbit, the process proceeds to step S507.

In step S505, when the space object B does not have the collision avoidance function, in step S509, the avoidance determination unit 150 determines whether or not the avoidance determination unit 150 requests the debris removal business operator to remove the debris.
If the debris removal business operator is not requested to remove the debris in step S509, the avoidance determination unit 150 determines that the debris is left unattended and does not determine the avoidance space object 69 in step S510.
When requesting the debris removal business operator to remove the debris in step S509, the avoidance determination unit 150 does not determine the avoidance space object 69 in step S508 because individual adjustment is required.
In step S506, if the space object B is in steady operation in a dense orbit, the process proceeds to step S508.

The avoidance determination unit 150 outputs an avoidance object notification 403 that notifies 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 that notifies the avoidance space object 69. Further, the avoidance determination unit 150 may transmit the avoidance object notification 403 to the management business device 40 of the management company corresponding to the avoidance space object 69.
If the avoidance space object 69 is not determined by individual adjustment or determination that it is not applicable, the avoidance determination unit 150 may output the avoidance object notification 403 including the fact that the avoidance space object 69 is not determined.

FIG. 28 is an example of a summary of the avoidance decision processing according to the present embodiment.
The rationale for exemplifying the avoidance determination process shown in FIGS. 22 to 27 is to determine an appropriate avoidance space object 69 while overcoming the following possibilities.
・ There is a risk of chaining when a collision occurs in a mega constellation.
-The area such as the vicinity of LEO sun-synchronous LST 10:30 or the polar region is an area where many satellites of multiple operators are concentrated, and there is a risk of chaining when a collision occurs.
-High-precision orbit information of mega constellation is owned by the mega constellation company and is not always disclosed as a forecast value.
・ Rocket launchers and operators that transition geostationary satellites from a geostationary transfer orbit (GTO) to a geostationary orbit have a risk of colliding with a mega constellation, but it is not always possible to arbitrarily select the timing of passing through a dangerous area. Absent.
-If multiple businesses on a dense track take evasive action without cooperation, there is a risk of collision at the evaded destination.
-There is a possibility that satellites that do not have the function of collision avoidance behavior may be included in the dense orbit.

<Machine learning process>
Next, the machine learning process in which the machine learning unit 160 updates the algorithm of the avoidance determination unit 150 by machine learning using the determination result of the avoidance determination unit 150 will be described.

Specific examples of the machine learning process by the machine learning unit 160 are as follows.
The machine learning unit 160 determines the algorithm if the results of the M1 processing to the M4 processing are the same. Further, the machine learning unit 160 makes individual adjustments when the processing results of the M1 processing to the M4 result are inconsistent.

FIG. 29 is an example of input information in the machine learning process according to the present embodiment.
The machine learning unit 160 performs AI machine learning and performs M1 processing to M4 processing in order to make a judgment process to be added when modifying the flowchart in the future according to the content of individual adjustment that occurs in the future, the judgment process and the judgment result. Optimized implementation order, added new judgment criteria, and
Perform processing such as optimizing the flow chart flow.

<Avoidance behavior processing by satellite constellation formation system>
Here, the satellite constellation forming system 600 when the avoidance object notification 403 output from the collision avoidance support device 100a is acquired will be described.
The satellite constellation formation system 600 forms, for example, a mega constellation. Based on the avoidance object notification 403 output from the collision avoidance support device 100a, the satellite constellation formation system 600 performs the avoidance action of the avoidance space object 69 when the avoidance space object 69 is a satellite included in the mega constellation. carry out.
Specifically, the satellite constellation forming unit shown in FIGS. 5, 7 and 8 generates an orbit control command 55 for the satellite notified as the avoidance space object 69 to perform the avoidance action. Then, the satellite constellation forming unit transmits the orbit control command 55 to the satellite.

Here, an example of an algorithm when a collision warning or an approach warning is issued for a mega constellation is shown below. For example, it is an algorithm of a satellite constellation forming unit that generates an orbit control command.
Set the following information as input conditions.
・ Whether or not the orbital altitude has passed during constellation operation ・ Incident angle with respect to the orbital altitude ・ Information on collision partner or approaching partner By setting the above information as an input condition, avoidance action should be taken based on the following criteria. Whether or not and the subject who should take evasive action are output as the judgment result.

The grounds for judging individual judgment items are as follows.
・ It is predicted that a huge number of warnings will be issued in mega constellations, and it is difficult to take evasive action for all warnings.
-If some of the satellites that make up the mega constellation take evasive action, there is a risk of collision with another satellite.
-It is necessary to compare the risk of taking evasive action with the risk of not taking evasive action to determine whether or not to implement evasive action.
-If only the mega constellation company has the high-precision orbit information forecast value and keeps it private, only the mega-constellation company can carry out highly accurate collision prediction analysis.
-It is necessary to share information on the risk analysis results by the mega constellation company and the policy of whether or not to implement avoidance actions with the stakeholders who are the targets of the collision.
-There is a possibility of overturning the primary judgment result by the algorithm and making an alternative proposal.

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

Until the process is established, it is necessary to coordinate opinions among stakeholders, so the algorithm implemented in the computer is a part of this. Machine learning will be conducted to make it a judgment process that should be added when modifying the flowchart in the future according to the content of future stakeholder response policy adjustments and the judgment process and judgment results. By machine learning, the execution order of M1 processing to M4 processing is optimized, new judgment criteria are added, and the flow chart flow is optimized.

Mega-constellation operators may conclude that they "do not take evasive action even if there is a risk of collision" in a situation where too many collision warnings are issued every day. From the standpoint of the other party in conflict, there is a possibility that the mega constellation operator will not give up on taking evasive action. In this case, there is a high possibility that opinions will be adjusted and a conclusion will be drawn on a collegial basis each time. Accumulation of a large number of such contradictory adjustment results may create new patterns in the judgment process leading to conclusions. By machine learning a new pattern of such a judgment process, it is possible to modify or add a processing flow.

In this embodiment, a collision avoidance support program that realizes the following functions has been described.
The collision avoidance support program causes a computer to execute a danger warning output process that identifies the existence of a danger prediction object based on orbit forecast information and outputs a danger warning before the space objects in a plurality of space objects collide with each other. The danger warning output processing is performed by at least one of the insurance company of the space insurance program that pays the insurance money from the premium collected in advance when the space object A and the space object B collide with each other, and at least one of the multiple space objects. A danger warning is output to the space object management company that manages the space.

The collision avoidance support device includes a space information recorder that includes orbit forecast information.
The danger warning output process determines whether or not a danger prediction object exists based on the orbit forecast information provided by the space information recorder, and outputs a danger warning when it is determined that the danger prediction object exists.

When the danger warning is output, the collision avoidance support program causes the computer to execute the avoidance space object determination process for determining the avoidance space object. The avoidance space object determination process determines the avoidance space object to be avoided among the space objects included in the danger prediction object based on the orbital forecast information provided by the space information recorder.

*** Explanation of the effect of this embodiment ***
In the collision avoidance support device according to the present embodiment, the grounds and results for identifying the space object to be evaded action are shown to the respective jurisdiction holders of the plurality of space objects which are danger prediction objects, and the evasion action is performed. Can be requested and supported. Therefore, according to the collision avoidance support device according to the present embodiment, there is an effect that the collision of a space object can be appropriately avoided.

*** Other configurations ***
<Modification example>
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 company that manages multiple space objects, and among multiple space objects. Supports collision avoidance between space objects.
The collision avoidance support system according to the present embodiment includes a database that stores space object information acquired by the space information recorder, and a server that includes avoidance operator determination means for determining a collision avoidance operator that executes collision avoidance. May be provided. A server realizes the following stages (also called means or parts) by a processing circuit such as a processor or an electronic circuit.
Specifically, the database may be a memory, an auxiliary storage device, or a file server. Specifically, the server is a collision avoidance support device. A specific example of the avoidance business operator determination means is the avoidance determination unit. The database may be provided in the server, or may be a device separate from the server.

The server has the following stages:
-The stage of receiving a notification from the space information recorder that a collision between space object A and space object B contained in multiple space objects has been foreseen.
-The stage of acquiring the estimated time or time zone in which a collision is predicted, the orbital forecast information of the space object A, and the orbital forecast information of the space object B from the space information recorder.
-The stage of notifying all or part of the business operator of space object A, the business operator of space object B, and the debris removal business operator, which is a collision warning or approach warning in the estimated time or time zone.
・ The stage of selecting a collision avoidance company.
-The stage of requesting the selected collision avoidance business operator to take collision avoidance action.

The space object information includes information indicating the presence or absence of the collision avoidance function of the space object.
The avoidance business operator determination means selects a management business operator that manages a space object having a collision avoidance function as a collision avoidance business operator when either the space object A or the space object B has a collision avoidance function. ..
Further, when both the space object A and the space object B have the collision avoidance function, the avoidance company determination means selects the collision avoidance company by using whether it is a stationary operation object or a non-stationary space object as an evaluation index. ..
Further, when both the space object A and the space object B have the collision avoidance function, the avoidance business operator determination means selects the collision avoidance business operator using whether or not it is a mega constellation satellite as an evaluation index for selection. ..
Further, the avoidance business operator determination means selects the debris removal business operator as the collision avoidance business operator when both the space object A and the space object B do not have the collision avoidance function.

Space object information includes the history of past space collision accidents.
The avoidance business operator determination means adds the evaluation index in the process of determining the collision avoidance business operator in the past space collision accident to the selection evaluation index, and selects the collision avoidance business operator.

The space information recorder includes orbit forecast information and orbit record information indicating the flight record value of the space object.
The server reports a collision warning or a danger warning, which is an approach warning, to a space insurance company that applies an insurance claim payment system that assesses accident liability and insurance claims according to the difference between the track forecast information and the track record information. Have stages.
It has the effect of encouraging stakeholders to make efforts to reduce accident liability and avoid collisions.

The database acquires the scheduled launch time and launch forecast information of the space object C acquired from the rocket launcher by the space information recorder from the space information recorder.
The server has the following stages:
-A stage in which the launch forecast information in the scheduled launch time information is notified to the mega constellation operator that manages the mega constellation satellite at the risk of collision with the space object C.
-The stage where the avoidance operator determination means requests the mega constellation operator to take collision avoidance action or provide information necessary for collision avoidance at the time of launching a rocket.
-A stage in which the rocket launcher is notified of space object information of a mega constellation satellite that has a risk of collision with space object C.

The database acquires the orbit transition scheduled time and transition forecast information of the space object D acquired from the orbit transition satellite operator by the space information recorder from the space information recorder.
The server has the following stages:
-A stage in which the transition forecast information at the scheduled orbit transition time is notified to the mega constellation operator that manages the mega constellation satellite at the risk of collision with the space object D.
-A stage in which the avoidance business operator determining means requests the mega constellation business operator to perform a collision avoidance action or to provide information necessary for collision avoidance at the time of orbit transition.
-The stage of notifying the orbit transition satellite operator of the space object information of the mega constellation satellite that has a risk of collision with the space object D.

The database acquires from the space information recorder the scheduled debris time and the debris forecast information of the space object E acquired from the satellite operator deorbited by the space information recorder or the debris collection operator.
The server has the following stages:
-The stage of notifying the mega constellation operator that manages the mega constellation satellite at the risk of collision of the space object E with the deorbit forecast information at the scheduled deorbit time.
-The stage where the avoidance business operator determination means requests the mega constellation business operator to take action to avoid a collision or to provide information necessary for collision avoidance at the time of deorbit.
-The stage of notifying the satellite operator that deorbits the space object information of the mega constellation satellite that is at risk of collision with the space object E, or the debris collection operator.

The server has a stage of reporting launch forecast information to a space insurance company that operates an insurance payment system that can be contracted when a collision risk at the time of launching a rocket is foreseen.
In addition, the server includes a stage of reporting transition forecast information to a space insurance company that operates an insurance claim payment system that can be contracted when a collision risk at the time of orbit transition is foreseen.
In addition, the server includes a stage of reporting deorbit forecast information to a space insurance company that operates an insurance payment system that can be contracted when a collision risk at the time of space object deorbit is foreseen.
This has the effect of encouraging stakeholders to make efforts to reduce accident liability and avoid collisions.

Further, the server includes a stage of providing the launch time information that can ensure flight safety at the time of launching the rocket.
Further, the server includes a step of providing the transition time information that can ensure flight safety at the time of orbit transition.
Further, the server includes a step of providing the deorbit time information that can ensure flight safety at the time of deorbit.

Embodiment 3.
In this embodiment, the differences from the first and second embodiments will be mainly described. The same reference numerals may be given to the same configurations as those of the first and second embodiments, and the description thereof may be omitted.

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

*** Explanation of configuration ***
FIG. 30 is a configuration diagram of the space insurance support system 550 and the space insurance support device 200 according to the present embodiment.
The space insurance support device 200 includes a responsibility evaluation unit 210, an insurance premium evaluation unit 220, and a storage unit 230 as functional elements. The space information recorder 50 and the alarm issuance information 141 are stored in the storage unit 230.

The functions of the responsibility evaluation unit 210 and the insurance premium evaluation 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. Further, the storage unit 230 may be provided separately as a memory 921 and an 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 the first embodiment. Further, the space insurance support program according to the present embodiment is a program that realizes the functions of the responsibility evaluation unit 210 and the insurance premium evaluation unit 220. That is, the space insurance support program according to the present embodiment causes the computer to execute the responsibility evaluation process and the insurance premium evaluation process.

*** Explanation of operation ***
The space insurance support process by the space insurance support device 200 according to the present embodiment will be described with reference to FIG. 31.

<Space insurance support processing: S200>
In step S21, the responsibility evaluation unit 210 evaluates the accident liability and the liability for damages when the danger prediction objects 65 collide with each other when the danger warning 25 generated based on the track forecast information 51 has not been issued. .. The liability evaluation unit 210 evaluates the accident liability and the liability for damages based on the forecast value of the trajectory of each of the danger prediction objects 65 and the orbit actual value of each of the danger prediction objects 65.
Specifically, the liability evaluation unit 210 evaluates the accident liability and the liability for damages to the management company that owns each space object of the danger prediction object 65. The responsibility evaluation unit 210 evaluates the accident liability and the liability for damages based on the space information recorder 50 including the orbit forecast information 51 and the orbit record information 52 in which the orbit record value is set.

In step S22, the insurance premium evaluation unit 220 evaluates the insurance premium in the management company that manages each of the plurality of space objects based on the forecast error 514. Specifically, the insurance premium evaluation unit 220 evaluates the insurance premium in 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 step S21 and step S22 may be reversed, or step S21 and step S22 may be performed in parallel.

Specific examples of space insurance support processing will be described below.

<About Space Insurance 201>
The space insurance 201 supported by the space insurance support device 200 according to the present embodiment determines the responsibility for the occurrence of an accident and the liability for damages based on the orbital record of the colliding space object, and covers the damage with the insurance premium. Insurance. In particular, the space insurance 201 is responsible for the occurrence of an accident when a collision accident occurs even though the forecast value of the orbit of the space object is disclosed as the orbit forecast information 51 and it can be predicted that a collision will not occur with each other. It is an insurance that determines the liability for damages and covers the damage with insurance premiums.

FIG. 32 is a diagram showing an example of information disclosure of a management company and an example of space insurance corresponding to the management company.
As stakeholders of business in outer space, management companies are roughly divided into satellite companies and rocket companies.
The mega constellation operator deploys satellites comprehensively in the sky. The mega constellation operator has a plan to deploy hundreds to thousands of satellites at an altitude of 1000 km or more, or a company with a plan to deploy several satellites at an orbital altitude of 300 km to 600 km. Exists.
There are also LEO constellation operators that operate multiple earth observation satellites on specific orbital planes in low earth orbit. There are also satellite operators that carry out commercial activities with a single satellite. In addition, a debris collection company for the purpose of debris collection will also appear.
Space objects owned by these management companies are at risk of colliding with each other. In particular, there is a high risk of collision during unsteady operation such as when the vehicle is put into orbit or when the vehicle leaves the orbit after the mission is completed. In addition, a business operator who puts a geostationary satellite into a geostationary orbit transitions to a geostationary orbit by the propulsion device of its own satellite after launching the rocket, so there is a risk of collision with a satellite in an orbit in the middle of the process.

It is effective as a collision avoidance measure to disclose the forecast values of the time and orbit information of the space objects held in advance between these businesses and to predict that they will not collide with each other. On the other hand, if, unfortunately, a collision accident occurs, it would be better if we could clarify the evidence of collision with an object that was operated according to the original forecast by deviating from one of the forecast values based on the track calendar record for the forecast value. It is effective in clarifying the responsibility for the occurrence of an accident and compensation for damages. As a means of covering the damage in terms of cost, it is effective to cover the damage with the premium of space insurance.

<About Space Information Recorder 50>
In the space insurance 201, the space information recorder 50 including the orbital forecast information 51 in which the predicted values of the time and orbital information of the space object are public information and the orbital record information 52 is used as evidence material for applying the space insurance.

The aircraft is equipped with a voice recorder for the purpose of verifying aircraft accidents. In addition, automobiles will be equipped with drive recorders for the purpose of verifying and providing evidence of automobile accidents.
A satellite constellation with thousands of satellites constructed at a low orbit altitude of about 600 km or less has a high risk of collision when a new rocket is launched. Therefore, for the same purpose as voice recorders and drive recorders, it is considered necessary to have a "space information recorder" that should also be called a satellite drive recorder.

The difference between an aircraft accident and a satellite collision is that even if the aircraft accident is an explosive accident, the onboard equipment may be recovered after the accident, so the voice recorder is designed to be robust enough to withstand an explosion. There is. In addition, since there is a driver in the aircraft, by recording not only the information of the measuring instruments but also the voice of the operator, the voice recording is left so that it can be verified after the accident, including the presence or absence of abnormalities in the instruments. It has become. On the other hand, in a satellite collision, it is difficult for the onboard equipment to dissipate into outer space and be recovered after the accident, and there is no operator. For this reason, voice recording is not required, and the main purpose is to record the data of the on-board measuring instruments, and the data is quickly transmitted to the ground or another satellite after acquisition, and the data up to just before the collision accident occurs in another place. Must be stored.

As a difference between a car accident and a satellite collision, a car drive recorder focuses on recording the operating condition of the car and the surrounding situation at the time of the accident in order to verify or use evidence as the responsibility for the accident. There is. If a head-on collision accident occurs and the accident location information is recorded, the lane in which the accident occurred can be verified and the location of the accident responsibility can be easily clarified. On the other hand, it does not have the purpose of transmitting its own future forecast information in advance. In addition, since the concept of driver's negligence liability exists, it is highly effective as evidence of liability and damage compensation. On the other hand, in satellite collisions, there is currently no concept equivalent to a lane and there is no driver, so there is no liability for negligence in satellite collisions, and there is also the concept of perpetrators and victims. I didn't do it.

At present, no international rules have been established regarding the location of liability and liability for damages in the event of a collision. However, as a means of avoiding collision accidents in the future, it is rational to share the orbital forecast values of space objects with stakeholders related to space objects in advance and take avoidance measures when collision risk is foreseen. As an evasion measure, it is effective for either of the parties who are expected to collide to take evasive action, and mutual cooperation is indispensable when both parties take evasive action. The risk of collision should be avoided as a result of both sides implementing independent collision avoidance operations. It is also important to avoid the risk of collision with another satellite when collision avoidance operation is performed.
It is important to identify whether or not the cause is a deviation from the predicted orbit published by the satellite in the event of a collision despite taking measures to avoid a collision. Therefore, the orbit history information of the space information recorder is important as objective evidence.

33 and 34 are diagrams showing a part of specific examples of the insurance premium evaluation process and the liability evaluation process according to the present embodiment.

<Specific example 1 of insurance premium evaluation processing>
The insurance premium evaluation unit 220 evaluates the insurance premium in the management company so that the smaller the forecast error 514, the lower the insurance premium rate.

The orbit forecast values of space objects include time error and position estimation error. Since the satellite flies at a speed of about 7 km to 10 km per second, the distance due to the time error in the direction of travel of the satellite becomes large. Geometrically expressing this creates a space on an elliptical cone centered on a space object, which is called an error bubble. The error range 502 in FIG. 15 is an example of an error bubble.
The position estimation error has various causes such as measurement data such as GPS reception provided by the own satellite or distance measurement data from a ground-mounted telescope, and the amount of error is also various. Normally, satellite operators have highly accurate forecast values and orbital calendar records for their own satellites. The accuracy of the orbit information held by the external business operator and the SSA business operator that distributes the measurement information from the ground has a large error.
When predicting the collision risk from the orbit forecast value, the collision risk is high because there is a high possibility that large error bubbles with a large amount of error will come into contact with each other. Further, as shown in the upper part of FIG. 33, the smaller the amount of error, the smaller the collision risk. Moreover, the smaller the amount of error, the smaller the difference between the orbital forecast value and the orbital calendar actual result. In addition, if the track calendar performance of a business operator with a small estimated error deviates from this, the insurance business operator may be exempted from liability.
For this reason, it is rational for insurance companies to set a low insurance premium rate because the smaller the estimated error amount, the lower the risk of causing an accident.

<Specific example 2 of insurance premium evaluation processing>
The insurance premium evaluation unit 220 is based on the orbit forecast information 51 and the orbit actual information 52 including each orbit actual value of the danger prediction object 65, and the smaller the difference between the orbit forecast value and the orbit actual value is, the more the insurance premium rate is. Evaluate the premium so that is low.

The forecast error 514 is a self-reported value of the management company. Since evaluation criteria are frequently used among multiple management companies, another means of evaluating the objective validity of insurance premium rates is also effective. Statistical analysis of past performance regarding the difference between the forecast value and the track calendar performance enables objective evaluation of the amount of error included in the forecast value, which is effective in ensuring fairness in setting the premium rate.

<Specific example 3 of insurance premium evaluation processing>
The insurance premium evaluation unit 220 evaluates the insurance money so that the smaller the difference between the forecast value of the track and the actual track value, the higher the insurance money paid.

If a space object that does not have a collision risk in the forecast value collides, there will be a difference between the forecast value and the orbital calendar record. However, it is reasonable to judge that the smaller this difference is, the lighter the responsibility for the collision accident. If it is not possible to determine the accident responsibility of the perpetrator and the victim of 100 to 0, and both sides have some responsibility, but the contingency cannot be denied and it is necessary to pay insurance money, the forecast value and the orbital calendar It is rational that the smaller the difference in performance, the higher the insurance money paid.

<Specific example 1 of responsibility evaluation processing>
The liability evaluation unit 210 evaluates the accident liability and the liability for damages so that the smaller the difference between the predicted value of the track and the actual track value, the less the accident liability and the liability for damages in the event of a collision. That is, in the space insurance 201, the smaller the difference between the forecast value of the space information recorder and the orbital calendar record, the more the basis for determining the reduction of accident liability and damage compensation liability in the event of a collision accident.

It is effective as an objective index when it is necessary to clarify accident liability and liability in situations where international STM rules have not been established.

<Specific example 2 of responsibility evaluation processing>
The liability evaluation unit 210 evaluates the accident liability and the liability for damages so that the accident that occurs even though the collision accident can be predicted in advance is exempted from the liability based on the forecast value of the orbit.

For the prediction of a collision accident, in addition to the self-efforts of each business operator, the means by which the SSA business operator issues a collision warning is also effective.
Businesses that do not avoid foreseen conflicts are in breach of their security obligations and it is reasonable for insurance businesses to be exempt.
If a business operator with a large amount of estimation error of the forecast value owns a large number of satellites, collision warnings will occur frequently, and if avoidance operation is not performed, the insurance money will not be paid even if a collision occurs. It has the effect of encouraging efforts to improve the accuracy of forecast values, and as a result, has the effect of reducing collision warnings.

<Specific example 3 of responsibility evaluation processing>
The liability evaluation department 210 is responsible for damages only to the parties involved in the collision accident in the third-party liability insurance insured by the rocket launcher engaged in the rocket launch business, and exempts higher-order damage from liability. Evaluate liability and liability.

In a mega constellation with thousands of aircraft at an altitude of 600 km or less, it is easy to assume that debris scattered due to a collision will collide with other satellites flying on the same orbital plane, nearby altitude, or nearby orbital plane. it can. Therefore, it cannot be asserted that the higher-order damage caused by the billiard accident is accidental. In addition, there is a risk that the total amount of damage will be a blue ceiling, it is appropriate to launch higher damage and exempt from liability insurance for third parties, and the total amount of damage will be within the expected scale, so the space insurance system Effective for ensuring sustainability.

Here, it is assumed that there are 40 orbital planes having an orbital altitude of about 340 km passing through the polar region, and a total of 2400 constellations with 60 satellites deployed on each orbital plane. Since all satellites pass through the polar region, it is necessary to perform extremely strict timing control for all satellites in order to allow collisions in a time-division manner. The number of satellite laps at an altitude of 340 km is about 15.7 laps, one lap is about 90 minutes, the satellite speed is about 7.7 km / sec, and the inter-satellite distance on one orbital surface is about 700 km, so satellites on a specific orbital surface pass through. The waiting time from that time until the succeeding satellite revisits is about 90 seconds. During this period, it takes about 2 seconds for 90 seconds / 40 planes to pass the satellite on 40 planes. This is an extremely strict management requirement from the technical level of satellite development, and there is a good possibility that it will collide with an error factor due to an unexpected malfunction in orbit.

The above is an example of a polar orbit, that is, an orbit inclination angle of 90 degrees, and in reality, the concentration of the polar region can be avoided by setting the orbit inclination angle to other than 90 degrees. However, for example, when the orbit inclination angle is about 50 degrees, there are many intersections of the orbital surfaces not only at high latitudes but also at mid-latitudes, and if the passing timings deviate at all the intersections, there is a risk of collision.
In a mega constellation that requires such strict operational timing control, if orbital errors occur due to collisions, there is a high possibility that collisions will be chained. In addition, since the debris scattered due to the collision dissipates at various speeds and directions, it can be easily inferred that higher-order damage will occur if a collision accident occurs in an area where thousands of satellites are concentrated in the vicinity.

<Specific example 4 of responsibility evaluation processing>
Liability assessment unit 210 evaluates accident liability and liability for damages so that life insurance or in-orbit liability insurance covers the higher damage caused by the debris scattered due to the collision.

A rocket or debris recovery satellite at the time of launch of a rocket that intrudes into the same orbit plane non-steadily under different orbit conditions such as elliptical orbits has a risk of causing a collision accident is there. Although we have a reasonable responsibility in the event of a collision, if the cause of higher damage caused by scattered debris is a dense situation such as a mega constellation, we will cover the damages with launch insurance or launch third party liability insurance. Is not rational. Therefore, it is rational to cover higher-order damage with the life insurance of the satellite or third-party liability insurance in orbit.

<Specific example 5 of responsibility evaluation processing>
Liability Evaluation Department 210 evaluates accident liability and liability for damages so as to exempt anyone other than the party paying life insurance as an individual satellite or satellite group.

Since the risk of a chain collision is presumed in a mega constellation, it is not rational to attribute all damage compensation for higher damage to the first collision.
It may also be more rational to treat thousands of satellites as a group of satellites rather than individually insuring them.
If the mega-constellation operator is aware of the risk of a chain collision in advance, pays the insurance premium, and covers the damage with insurance in the event of an accident, the accident occurrence probability, higher damage prediction, and the total amount of insurance premium to be paid The insurance premium rate can be set according to the above. Therefore, there is an effect that the insurance system can be constructed without adversely affecting the entire space insurance system.

<Specific example 6 of responsibility evaluation processing>
FIG. 35 is a diagram showing the risk of collision between a space object in steady operation and a space object in unsteady operation.
When the space object in steady operation collides with the space object in non-steady operation, the responsibility evaluation unit 210 makes the accident liability and the liability for damages on the management company side of the space object in non-stationary operation heavy. As such, evaluate accident liability and liability for damages.

Steady operation is the operation of a satellite that continues from several years in orbit to the end of its life span of 10 years or more. The satellite orbit in steady operation maintains a certain degree of reproducibility depending on physical phenomena. In many cases, it will be operated for a long time in a circular orbit. A group of satellites that regularly operate at the same altitude in a circular orbit while maintaining a constant phase interval will not collide even if dozens of satellites fly to the same orbit at the same time.
On the other hand, in transient orbits leading to orbit insertion, or in unsteady operations such as rocket launches, there is a risk of collision accidents because they intrude into the same orbital surface unsteadily under orbital conditions with different pi such as elliptical orbits. is there. There is a risk of collision with a large number of satellites, especially if they enter the orbital surface at a shallow relative angle. Therefore, it is rational to think that accident liability and liability should be set heavily.

<Specific example 7 of responsibility evaluation processing>
FIG. 36 is a diagram showing the risk of collision between a satellite in the middle of orbit transition of a geostationary satellite and a space object in steady operation.
If the satellite in the middle of the orbit transition of a stationary satellite collides with a space object that is in constant operation, the responsibility evaluation unit 210 should increase the accident liability and damage liability on the side of the management company of the space object that is in constant operation. To evaluate accident liability and liability for damages.

A geostationary satellite is usually launched into a geostationary transfer orbit GTO by a rocket, and then the orbit is transferred to a geostationary orbit by operating a propulsion device provided by the geostationary satellite. At this time, for example, in the method of operating the chemical propulsion device called the apogee kick motor at a distant point (apogee), it is difficult for the geostationary orbit input operator to avoid the collision because the timing of operation cannot be arbitrarily selected. Also, unlike rocket launchers, it is difficult to avoid collisions by looking at all satellite information of the mega constellation, including uncertainty after a lapse of time after launch.
It is obvious for mega constellation operators that satellites to be put into geosynchronous orbit will make orbital transitions over the equator, and the establishment of an autonomous collision avoidance function is being touted. It is rational to blame.

<Specific example 8 of responsibility evaluation processing>
FIG. 37 is a diagram showing the collision risk between the launched rocket and the mega constellation.
The liability evaluation unit 210 evaluates accident liability and liability for damages so as to be exempt from collision with a mega constellation, which is a large-scale satellite constellation formed at an orbital altitude of 600 km or less.

There is a mega constellation concept that deploys about 2,500 satellites at three different altitudes near 340 km, but there are large restrictions on avoiding collisions when launching a rocket, which may pose an excessive risk to insurance companies.
For example, assuming that there are about 40 orbital planes and about 60 satellites per orbital plane near an altitude of 340 km, the distance between satellites on the same orbital plane is about 700 km, and if the satellite speed is about 7.7 km, it is about 90. The satellite will revisit at time intervals of seconds. The time from the passage of the adjacent track surface to the revisit of the next track surface is about 18 minutes. When there are three different altitudes in the vicinity, the orbital planes gradually move in the longitude direction without synchronization. In this situation, a rocket launched from Giana near the equator needs to be launched through a gap because the next orbital surface will revisit after the three types of orbital surfaces have gone too far, and the time grace is on the order of several minutes. There is only.
Even if a collision occurs in this situation, it is hard to say that it is an accident, so it is rational to exempt it from liability.
As a result, it is possible to avoid an increase in the scale of insurance payments due to a collision accident of a low-earth orbit megaconste, which has a risk of frequent occurrence, and it is effective in ensuring the sustainability of space insurance.

<Specific example 8 of responsibility evaluation processing>
The liability evaluation unit 220 evaluates the accident liability and the liability for damages so as to exempt the person from taking the collision avoidance operation measures without prior notice in the collision accident between space objects having the function of carrying out the collision avoidance operation. To do.

At space stations or geostationary orbit satellites, collision avoidance operations are often carried out based on danger warnings. On the other hand, in low earth orbit satellites, in addition to the inter-satellite distance being closer to each stage than in geostationary orbit, there are also satellites such as CubeSat that do not have the function of collision avoidance operation. For this reason, when a danger warning is issued on a specific dense orbital surface of a low earth orbit satellite, if one satellite performs collision avoidance operation without cooperation with neighboring satellites, it will collide with another satellite in the vicinity. Risk arises.
In addition, some management companies have declared that they have autonomous collision avoidance operation means. If the satellites of multiple operators carry out autonomous avoidance operations without cooperation with neighboring satellites, there is a risk that collisions will occur at different orbit positions as a result of avoidance.
Therefore, according to Specific Example 8 of the liability evaluation process, the purpose is to incorporate the risk countermeasure as a contract premise of the insurance company, and the disclaimer is one of the rational measures.
If not exempted from liability, it will be necessary to create international rules that contribute to collision avoidance operations in dense orbits.

Embodiment 4.
In the present embodiment, the points different from the first to third embodiments will be mainly described. The same components as those in the first to third embodiments may be designated by the same reference numerals, and the description thereof may be omitted.

In the present embodiment, a collision insurance execution device that executes the operation of the space collision insurance 202 that compensates for the damage caused by the collision between the space objects in a plurality of space objects flying in space will be described.
With the advent of mega-constellation operators, it is more likely that collisions with space objects will occur not accidentally, but due to a predominant rate of occurrence or human misjudgment. Space insurance assumes accidents, but it requires insurance for accidents that have a significantly higher risk of occurrence than the statistical probability of accidental failures, that is, collision accidents that cannot be called accidental accidents. For example, space collision insurance 202, which can be purchased by throwing away after a satellite collision is predicted, is promising as a business model so that there is a throw-away insurance that applies only to the flight when boarding an aircraft. Space collision insurance 202 is also referred to as space object collision insurance.

*** Explanation of configuration ***
FIG. 38 is a configuration diagram of the collision insurance execution system 560 and the collision insurance execution device 260 according to the present embodiment.
The collision insurance execution device 260 includes an insurance processing unit 261 and a storage unit 262 as functional elements. The space information recorder 50 and the alarm issuance information 141 are stored in the storage unit 262.

The function of the insurance processing unit 261 is 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. Further, the storage unit 262 may be provided separately as a memory 921 and an 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 the first embodiment. Further, the collision insurance execution program according to the present embodiment is a program that realizes the function of the insurance processing unit 261. That is, the collision insurance execution program according to the present embodiment causes the computer to execute the insurance processing by the insurance processing unit 261.

*** Explanation of operation ***
The collision insurance execution process by the collision insurance execution device 260 according to the present embodiment will be described with reference to FIG. 39.

<Collision insurance execution processing: S300>
In step S61, the insurance processing unit 261 executes the operation of the space collision insurance 202.
The space collision insurance 202 is subscribed to by a management company that owns a space object for which a collision is predicted based on the orbit forecast information 51. The space collision insurance 202 will be terminated if the insurance money is paid when a foreseen collision accident actually occurs and the danger time zone in which the danger warning for the danger of the collision is issued has passed without any accident. ..
The insurance processing department 261 executes the operation of space collision insurance that the management company can join after the issuance of the danger warning. The insurance processing department 261 executes the operation of space collision insurance 202, in which a mega constellation company that owns a mega constellation, which is a large-scale satellite constellation, can subscribe on a satellite group basis and receive insurance money in the event of a collision accident. .. In addition, the insurance processing unit 261 operates the space collision insurance 202, which covers higher-order damage caused by a collision chain caused by a foreseen collision accident. In the space collision insurance 202, the insurance premium and the insurance premium rate fluctuate according to the past results of similar collision accidents.

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

<Specific example 1 of space collision insurance 202>
Space collision insurance 202 is space insurance that a stakeholder who owns a space object for which a collision is predicted can join after the collision warning is issued, based on public information based on the space object orbit information forecast value. The space collision insurance 202 will be terminated when the insurance money is paid when the foreseen collision accident actually occurs and the dangerous time zone in which the warning is issued has passed without any accident.

In the space collision insurance 202, in the launch insurance, the life insurance, the launch third party liability insurance, and the in-orbit third party liability insurance described in the third embodiment, the collision is predicted based on the public information in the space object orbit information forecast value. Stakeholders who own the created space objects can join after the collision warning is issued. The space collision insurance 202 will be paid when a foreseen collision accident actually occurs, and the contract will be terminated if the dangerous time zone in which the warning is issued has passed without any accident.
Danger warnings such as collision warnings may be issued by the SSA business operator based on the orbit forecast value disclosure information, or may be separately issued by a business operator whose livelihood is space object collision avoidance advice.
The insurance money paid after the collision occurs is set so that the insurance money will be higher when the error between the forecast value and the actual value is small, based on the precision orbit history record of the "space information recorder".
If both parties do not take evasive action despite the collision warning being issued, they will be exempted from liability and no insurance money will be paid.

<Specific example 2 of space collision insurance 202>
Space collision insurance 202 is space insurance that allows you to anticipate a collision accident and join ad hoc even if a collision warning is not issued. The space collision insurance 202 will be terminated when the insurance money is paid when the foreseen collision accident actually occurs and the dangerous time zone in which the warning is issued has passed without any accident.

At the time of launching a rocket, space objects that leave the orbit and are in the deorbit process, or space objects that fly in an elliptical orbit during the orbit transition process, have a risk of colliding with a mega constellation satellite that flies comprehensively in the sky. However, if the forecast value is not disclosed, or even if it is disclosed, the SSA operator or the trajectory analysis service operator may not be able to issue a collision warning at an appropriate timing. In this case, it is rational to take out ad hoc insurance at the discretion of the business operator without a collision warning. The contract will be terminated after successfully passing the dangerous orbit.

<Specific example 3 of space collision insurance 202>
FIG. 40 is a diagram showing the space collision insurance 202 according to the present embodiment.
Space collision insurance 202 can be subscribed to by a mega constellation company on a satellite group basis, and can receive insurance money in the event of a collision accident due to a collision warning or an ad hoc collision risk.

Many conflict risks are foreseen for mega-constellation operators in the future, and it is possible to choose between space insurance life insurance or third-party liability insurance, or ad hoc space collision insurance 202. .. In addition, since it is irrational to take out insurance for each individual satellite in a group of thousands of satellites, the satellite group of a specific altitude that implements a series of services in cooperation is covered by insurance collectively, and the individual satellites of the components are covered by insurance. It is rational to make insurance payments.
In addition, when the ad hoc space collision insurance 202 is used as a financial resource, it is appropriate to terminate the contract for rockets or space objects in the deorbit process after passing through the dangerous area, but the mega constellation companies generate ad hoc one after another. It is rational to have a mechanism to subscribe in a lump sum including the risk of collision.
Premiums should be set according to the size of the satellite group, the frequency of ad hoc collision risks foreseen, and the duration of the contract.

<Specific example 4 of space collision insurance 202>
Space collision insurance 202 covers higher-order damage caused by a collision chain caused by a pre-foreseen ad hoc collision accident.

In a group of satellites of mega constellation, a single component satellite flies in another satellite or a nearby orbit that flies in the same orbit plane in the case of explosive destruction or failure and loss of orbit control capability. There is a risk of colliding with another satellite in a chain reaction. If a large number of debris are scattered, they will spread over a long period of time, and there is a risk of biorating the entire altitude of the nearby orbit, which may cause enormous damage to mega constellation operators.
If these high-order damages that are foreseen in advance are covered by insurance, there is a possibility that the space collision insurance 202 will be established if the mega constellation company pays a large amount of insurance premiums.

<Specific example 5 of space collision insurance 202>
Space collision insurance 202 does not cover higher-order damage associated with a collision chain caused by a previously foreseen ad hoc collision accident.

If the party to the collision warning is a constellation company, the space collision insurance 202 covers only one aircraft in which a collision has occurred and does not care about damages caused by a chain accident.
In Space Collision Insurance 202 of Specific Example 4, which covers higher-order damage, it is difficult to estimate the scale of higher-order damage, and there is a concern that the risk of a rise in the premium rate after an accident or the risk of the sustainability of the insurance business itself. There is also. In a situation where the mega constellation company does not respond to the necessary and sufficient premium payment, it is rational to exclude the high-order damage that can be foreseen in advance from the insurance payment target as an exemption.

<Specific example 6 of space collision insurance 202>
In space collision insurance 202, the premium and the premium rate fluctuate according to the past record of similar collision accidents.

In the space collision insurance 202, the insurance premium and the insurance premium rate fluctuate based on the information in the similar space object collision accident that occurred in the past. Information on similar space object collision accidents that occurred in the past includes orbit forecast information 51 and orbit record information 52 of the space information recorder 50, damage compensation and proceedings in the accident, frequency of similar accidents, and insurance payment. There is information such as analysis results of past information on actual results.

In the above-described first to fourth embodiments, each part of the collision avoidance support device, the space insurance support device, and the collision insurance operation device has been described as independent functional blocks. However, the configuration of the collision avoidance support device, the space insurance support device, and the collision insurance operation device does not have to be the configuration as in the above-described embodiment. The functional blocks of the collision avoidance support device, the space insurance support device, and the collision insurance operation device may have any configuration as long as the functions described in the above-described embodiment can be realized. Further, each of the collision avoidance support device, the space insurance support device, and the collision insurance operation device may be one device or a system composed of a plurality of devices.

*** Other configurations ***
<Modification example>
Here, a modification of the third and fourth embodiments will be described.
The space insurance support system and the collision insurance execution system are also called insurance payment systems.
The insurance claim payment system includes a server including a database that records insurance claim payment contract information for each insurance contract and a database that records space object information.
The database is specifically a memory or an auxiliary storage device. Specifically, the server is a space insurance support device or a collision insurance operation device. Further, the space insurance support device and the collision insurance operation device may cooperate to realize the function of the server. A server realizes the following stages (also called means or parts) by a processing circuit such as a processor or an electronic circuit.
A specific example of the insurance premium rate setting means is the insurance premium evaluation department. A specific example of the insurance claim assessment method is the insurance processing department.

The contract information includes the insurance premium rate, the accident liability assessment, and the insurance claim amount.
The space object information includes the orbital forecast information of each of the space object A and the space object B in which the collision accident occurred, and the orbital record information of each of the space object A and the space object B in the time zone in which the collision occurred.
The server includes the following steps:
-The stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred.
・ The stage of assessing insurance payments based on the difference between actual track information and forecast track information.
・ The stage of paying insurance money.

Space object information includes space object collision warnings obtained from satellite information management companies.
The server also includes the following steps:
-The stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred.
・ The stage of assessing insurance payments based on the difference between actual track information and forecast track information.
・ The stage of paying insurance money.

The server also includes the following steps:
・ The stage of accepting a contract after obtaining a space object collision warning.
-The stage of determining the insurance premium rate based on the error information of the forecast orbit information recorded in the space object information.
-The stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred.
・ The stage of assessing insurance payments based on the difference between actual track information and forecast track information.
・ The stage of paying insurance money.
-The stage where payment is completed and the contract is terminated, the stage where the contract is terminated due to exemption from liability, or the stage where the contract is terminated without a collision accident due to a space object collision warning.

The server also includes the following steps:
-The stage of accepting a contract after obtaining a forecast of rocket launch, satellite orbit transition, or satellite passage in the middle of deorbit.
-The stage of determining the insurance premium rate based on the error information of the forecast orbit information recorded in the space object information.
-The stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred.
・ The stage of assessing insurance payments based on the difference between actual track information and forecast track information.
・ The stage of paying insurance money.
-The stage where payment is completed and the contract is terminated, the stage where the contract is terminated due to exemption from liability, or the stage where the contract is terminated without a collision accident due to a space object collision warning.

In the insurance claim payment system, the difference between the actual orbit information and the predicted orbit information is calculated at the stage of assessing the accident liability of the colliding space object A and the space object B by the difference between the actual orbit information and the predicted orbit information after the collision accident occurs. The larger the value, the heavier the accident liability is assessed.

In the insurance claim payment system, the difference between the actual orbital information and the forecasted orbital information at the stage of assessing the insurance claims paid for the colliding space object A and the space object B by the difference between the actual orbital information and the predicted orbital information after the collision accident occurs. The smaller the value, the higher the insurance money will be assessed.

In the insurance claim payment system, the smaller the estimated error amount, the lower the insurance premium rate at the stage of determining the insurance premium rate based on the error information of the forecast orbit information recorded in the space object information.

In the insurance claim payment system, although the space object collision warning acquired from the satellite information management company and the orbital forecast information of each of the space object A and the space object B for which a collision is predicted are acquired, the space object A Both the management company and the management company of space object B are exempt from liability for collision accidents in which a collision occurs without taking collision avoidance action.

In the insurance claim payment system, only the collision accident of the space object identified by the space object collision warning obtained from the satellite information management company is covered by the insurance claim, and the information exempting the higher damage caused by the ball thrust accident is included in the contract information. include.

In the insurance claim payment system, in addition to the collision accident of the space object identified by the space object collision warning obtained from the satellite information management company, the information that the insurance claim payment target includes the damage compensation for the higher damage caused by the ball thrust accident. Is included in the contract information.

In the insurance claim payment system, compensation for damages caused by a ball thrust accident at the stage of assessing the insurance claims paid for space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred. Is subject to insurance claim assessment.

In the insurance claim payment system, the contract information includes information that exempts higher-order damage caused by scattered debris caused by a collision at the time of launching a rocket or a collision of a debris removal satellite.

In the insurance payment system, the contract information includes information that is exempted if the party to the space object collision is a mega constellation operator and the insurance premium is not paid as an individual satellite or a group of satellites.

In the insurance claim payment system, an accident between space object A and space object B that collided due to the difference between the actual orbit information and the forecast orbit information after a collision accident between a space object that is operating constantly and a space object that is operating unsteadily occurs. At the stage of assessing liability, the accident liability on the non-routine operation side is heavily assessed.

In the insurance claim payment system, payment is made for space object A and space object B that collide with each other due to the difference between the actual orbit information and the forecast orbit information after a collision accident between a space object that is constantly operating and a space object that is operating unsteadily occurs. At the stage of assessing insurance claims, the insurance claims on the regular operation side are assessed at a high price.

In the insurance claim payment system, the accident liability of space object A and space object B that collided with each other based on the difference between the actual orbit information and the forecast orbit information after the collision accident between the satellite in the middle of the orbit transition and the space object in constant operation occurs is assessed. At this stage, lightly assess the accident liability of the satellite during the orbit transition.

In the insurance claim payment system, the insurance claims paid for space object A and space object B that collided due to the difference between the actual orbit information and the forecast orbit information after the collision accident between the satellite in the middle of the orbit transition and the space object in constant operation occurred. At the assessment stage, the insurance money on the regular operation side is assessed at a high price.

In the insurance claim payment system, the contract information includes information exempting from collision with a mega constellation operator formed at an altitude of 600 km or less.

In the insurance claim payment system, the contract information includes information exempted from liability when collision avoidance operation measures are taken without prior notice in a collision accident between space objects having a function of carrying out collision avoidance operation.

The insurance payment system allows mega-constellation operators to subscribe on a satellite-by-satellite basis and receive insurance in the event of a collision due to a collision warning or ad hoc collision risk.

In the insurance claim payment system, the error information included in the track forecast information includes the error amount calculation basis, and the clearer the basis, the lower the insurance premium rate is set.

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

In the insurance claim payment system, the premium rate assessment fluctuates according to the past record of similar collision accidents.

In the insurance claim payment system, the accident liability assessment and the insurance claim assessment fluctuate according to the past record of similar collision accidents.

In addition, the server includes the following stages.
・ The stage of accepting a contract after obtaining a space object collision warning.
・ The stage of determining the insurance premium rate based on the error information of the forecast orbit information recorded in the space object information,
-The stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred.
・ The stage of assessing insurance payments.
-The stage where the contract is terminated when the insurance payment is completed or the collision accident due to the space object collision warning does not occur.

The space insurance program causes a computer to perform a process of paying insurance money from a pre-collected premium when a space object A and a space object B collide with each other among a plurality of space objects.
The space insurance program is a danger warning that identifies the existence of a danger prediction object based on the orbit forecast information provided by the space information recorder and outputs a danger warning before the space objects in multiple space objects flying in space collide with each other. Provided with an output means.
Space collision insurance by the space insurance program is a space collision insurance that a management company that owns a space object for which a collision is foreseen joins after the issuance of a danger warning of the collision avoidance support program. It is an ad hoc space collision insurance that will be terminated if the insurance money is paid when it actually occurs and the danger time zone when the danger warning is issued to notify the danger of collision has passed without any accident.

Space collision insurance based on the space insurance program can be subscribed to by a mega constellation company that owns a mega constellation, which is a large-scale satellite constellation, on a satellite-by-satellite basis, and can receive insurance money in the event of a collision.

Space collision insurance under the Space Insurance Program does not cover higher-order damage associated with collision chains resulting from foreseen collisions.

Space collision insurance under the Space Insurance Program covers higher-order damage associated with a collision chain caused by a foreseen collision.

In space collision insurance by the space insurance program, the contents of the premium rate setting means and the insurance claim assessment means vary depending on the past results of similar collision accidents.

Embodiment 5.
In the present embodiment, the points different from the first to fourth embodiments will be mainly described. The same components as those in the first to fourth embodiments may be designated by the same reference numerals, and the description thereof may be omitted.

*** Explanation of configuration ***
FIG. 41 is a diagram showing a functional configuration example of the satellite constellation formation system 600.
The difference from FIG. 8 in FIG. 41 is that communication with the rocket launch business apparatus 46 is illustrated.

FIG. 42 is a configuration diagram of the 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 manages a plurality of space objects 60 flying in space. Specifically, the information management device 1000 is a satellite constellation business device 451 used by a satellite constellation business operator that forms a satellite constellation composed of a plurality of satellites. The mega constellation business device 41 or the LEO constellation business device 42 is an example of the satellite constellation business device 451.
The information management device 1000 discloses information on a plurality of space objects flying in space to another management business device 40, for example, information on a satellite constellation.
The other management business device 40 refers to another management business device on which the information management device 1000, which is its own device, is not mounted. Specifically, the other management business device 40 is a rocket launch business device 46, an orbit transition business device 44, or a debris recovery business device 45 used by a debris recovery business operator. Even when 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.
Further, the information management device 1000 centrally manages a satellite constellation business device used by a satellite constellation business operator that forms a satellite constellation composed of a plurality of satellites and a rocket launch business device used by a rocket launch business operator. It may be a device.

The management business device 40 manages 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 about a space object 60 such as an artificial satellite or debris.
The management business device 40 includes a mega constellation business device 41, a LEO constellation business device 42, a satellite business device 43, an orbit transition business device 44, a debris recovery business device 45, a rocket launch business device 46, and an SSA business device 47. Equipment is included.

The management business apparatus 40 may collect information about a space object such as an artificial satellite or debris, and provide the collected information to the information management apparatus 1000. Further, when the information management device 1000 is mounted on the 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 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 other hardware via a signal line and controls these other hardware.

The information management device 1000 includes an information disclosure unit 1100 and a storage unit 1400 as functional elements. The space information recorder 50 and the disclosure threshold value 141 are stored in the storage unit 1400. The disclosure threshold value 141 is a threshold value for determining whether or not to disclose the orbit forecast information 51.

The function of the information disclosure unit 1100 is 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. Further, the storage unit 1400 may be provided separately as a memory 921 and an 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 the first embodiment.

*** Explanation of operation ***
<Information disclosure processing: S1000>
FIG. 43 is a flow chart of the information disclosure process S1000 according to the present embodiment.
In the information disclosure process, the information disclosure unit 1100 supplies the track forecast information 51 to the other management business device 40 based on the disclosure threshold value 141 for determining whether or not to disclose the track forecast information 51 and the forecast error 514. Determine whether to disclose. For example, the information disclosure unit 1100 discloses the track forecast information 51 to another management business apparatus when the forecast error 514 is equal to or higher than the disclosure threshold value 141. Further, for example, when the forecast error 514 is smaller than the disclosure threshold value 141, the track forecast information 51 is not disclosed to other management business devices. A determination method other than the above may be used to determine whether to disclose or not disclose the information.

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

In step S1002, the information disclosure unit 1100 extracts the disclosure forecast information 552 from the plurality of orbit forecast information corresponding to the plurality of space objects included in the orbit forecast information 51. For example, the information disclosure unit 1100 extracts orbital forecast information having a forecast error 514 of disclosure threshold 141 or more as disclosure forecast information 552 from a plurality of orbital forecast information corresponding to a plurality of space objects included in the orbital forecast information 51. May be good. Further, the information disclosure unit 1100 may extract the disclosure forecast information 552 by another method. The information disclosure unit 1100 outputs the disclosure forecast information 552 to another management business device. At this time, when the information disclosure unit 1100 receives the information disclosure request 551, the disclosure forecast information 552 may be transmitted to another management business apparatus 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 apparatus 46 receives the disclosure forecast information 552 from the information management apparatus 1000.

<Satellite constellation control processing: S2000>
FIG. 44 is a flow chart of the satellite constellation control process S2000 according to the present embodiment.
Next, with reference to FIGS. 41 and 44, the satellite constellation control process S2000 when the satellite constellation formation system 600 acquires the rocket launch information 503 from the rocket launch business apparatus 46 that has received the disclosure forecast information 552. explain.
The satellite constellation control process S2000 is a process of 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 forming unit 11 acquires rocket launch information 503 including the launch point of the rocket at the rocket launch and the scheduled launch time of the rocket at the launch point from the rocket launch business device 46.

In step S2002, the satellite constellation forming unit 11 of the plurality of satellites, based on the rocket launch information 503, prevents each of the plurality of satellites from flying in the flight path at the scheduled time for the rocket to fly in the flight path after launch. Control each orbit. Specifically, the satellite constellation forming unit 11 raises or lowers the orbital altitude of each of the plurality of satellites by operating the propulsion devices 33 of each of the plurality of satellites, and the orbital planes of the plurality of satellites are launched. Control the orbit of each of the multiple satellites so that they deviate from the sky above the point. For example, the satellite constellation forming unit 11 generates an orbit control command 55 for performing the above orbit control and transmits it to the satellite 30.

Specific examples and effects of information disclosure processing and satellite constellation control processing will be described below.
FIG. 45 is a diagram showing the forecast value of the rocket launch and the error range of the satellite constellation 20. The satellite constellation 20 is, for example, a large-scale satellite constellation ranging from hundreds to thousands, that is, a mega constellation.

The upper part of FIG. 45 is a conceptual diagram in which the satellite constellation 20 is modeled in a two-dimensional space. The lower part of FIG. 45 is a conceptual diagram of a launch window for launching a rocket when the satellite constellation 20 in the upper part of FIG. 45 is located in the sky.
As shown in the lower part of FIG. 45, the launch window allowed for rocket launch is limited in consideration of the error range of each satellite of the satellite constellation 20.
Therefore, the satellite constellation formation 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 forecast value of the rocket launch and the error range of the satellite constellation 20.
The upper part of FIG. 46 is a conceptual diagram showing a satellite constellation 20 having a small error range. The lower part of FIG. 46 is a conceptual diagram showing satellite constellation 20 having a large error range.

As shown in the upper part of FIG. 46, in the satellite constellation operator's own system, the error range is reduced by using a method such as difference evaluation of intersatellite distance measurement data and GPS measurement value or statistical data evaluation. There is a possibility that it can be done.
If the satellite constellation operator does not disclose the error range, the rocket launcher will rely on external measurement information such as the SSA operator for information on the forecast value of the satellite orbit. As a result, there is a possibility that the rocket launcher can only grasp the forecast value with a large error range.
In this way, by configuring the orbit forecast information below the predetermined error range for a fee, it is possible to contribute to the business of providing the precise orbit forecast value useful for the rocket launcher.

Here, the orbit forecast information used when the rocket launcher launches the rocket is described. However, in addition to this, the present embodiment can be applied to various situations such as passing through a satellite constellation at the time of launching a satellite, passing through a satellite constellation at the time of collecting debris, or investigating the orbit of a space object.

*** Explanation of the effect of this embodiment ***
According to the information management device 1000 according to the present embodiment, the satellite constellation operator forming the mega constellation sets the predicted value of the orbit information of its own satellite into the rocket launcher, the geostationary satellite orbit input operator, or It can be disclosed to the debris collection company for a fee.
In order for rocket launchers to fulfill their flight safety obligations, they need predicted orbit information of the satellites that make up an accurate mega constellation. Therefore, according to the information management device 1000 according to the present embodiment, the asset value of the satellite orbit prediction information can be increased, and there is an effect that it can be a profit source for the satellite operator.

In addition, there is a high risk of collision with a mega constellation satellite in the process of deorbiting and deorbiting the satellite after the mission is completed. Similarly, there is a possibility that the responsibility of the Deorbit satellite operator who neglected the collision avoidance measures for the disclosed orbit information or the debris collection operator can be pursued, and the satellite orbit information has the effect of becoming a source of revenue. ..
Furthermore, the operator who inserts the geostationary satellite into orbit will make a transition to the geostationary orbit with the propulsion device provided by the satellite after launching it to the geostationary transfer orbit with a rocket, so there is a risk of collision with the mega constellation satellite in the process. Similar effects are expected.

According to the information management device 1000 according to the present embodiment, the rocket launcher can share the satellite orbit information forecast value of the low earth orbit altitude mega constellation operator. Therefore, it is possible for a rocket launcher to develop a rocket launch business whose competitiveness is to launch without collision risk without using the disclosure information of the predicted orbit information of the satellite.
When the satellite predicted orbit information itself has a paid value, the ability to launch a rocket without using the paid information has the effect of producing a cost reduction effect and becoming a source of competitiveness as a business operator.

According to the satellite constellation formation system 600 according to the present embodiment, in a rocket launch in which the launchable time at the launch point is limited, the satellite does not fly on the flight path in advance at the scheduled launch time of the launch point. The orbit of the satellite can be changed.
Planetary exploration spacecraft for rendezvous to planets flying in a particular orbit may limit the launch window that can be properly launched from the launch point to a short time of a few seconds. On the other hand, since the earth rotates with respect to the orbital plane of the satellite flying in the inertial space according to the law of nature, there is a risk that the satellite will happen to fly on the launch flight path and collide. In a mega constellation, satellites may fly on the same orbital plane for only a few tens of seconds, so it is difficult to avoid sufficient collisions unless measures are taken so that the orbital plane is not located in the sky. According to the satellite constellation formation system 600 according to the present embodiment, the satellite mega constellation side operates the propulsion devices provided by all satellites in advance so that the orbital surface is not located in the sky at a specific time of a specific launch point. .. Then, by raising or lowering the orbital altitude of the satellite and adjusting the relative relationship between the orbital plane and the earth's rotation, the orbital plane is shifted so that it is not located in the sky at a specific time of the specific launch point to avoid a collision. .. In a mega constellation, adjusting only individual satellites poses a risk of collision with another satellite, so it is important to adjust all satellites in synchronization.

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

The information management device manages the orbit forecast information provided by the management business device that manages the satellites forming the satellite constellation.
The processor of the information management device includes a disclosure threshold value and information disclosure propriety determination means for determining whether or not to disclose the information. The disclosure threshold is the satellite constellation when it is predicted that the satellite forming the satellite constellation and the space object for which the orbit forecast information has been acquired from other management business equipment will approach at a specific time based on the orbit forecast information. This is information for determining whether or not to disclose the orbit forecast information of the ration management business device.

The other management business equipment is a rocket launch business equipment, an orbit transition business equipment, or a debris collection business equipment.

The management business device A that manages the rocket launch includes a space information recorder A that records space object information A including launch time information and orbit forecast information of the rocket launch.
The management business device B that manages the satellites that form the satellite constellation is a space information recorder that records the forecast source period of multiple satellites that form the satellite constellation, the forecast orbit information, and the space object information B including the forecast error. B is provided.
The management business device C, which manages space object information by an analysis company that performs collision analysis between space objects, records various space object information acquired from the management business device used by the management company that manages a plurality of space objects. The space information recorder C is provided.
Space object information B is not disclosed to the space information recorder A and the space information recorder C owned by the satellite constellation management business apparatus.
Then, a single operator exclusively uses the space object information A and the space object information B to perform a collision analysis, derives a condition for ensuring flight safety at the time of launching the rocket, and avoids the collision.

The satellite constellation management business equipment discloses space object information B to space information recorder A and space information recorder C owned by other businesses for a fee.
Then, only a single operator uses the space object information A and the space object information B free of charge to perform collision analysis, derive conditions for ensuring flight safety at the time of launching the rocket, and avoid the collision.

Space object information B is not disclosed to the space information recorder A and the space information recorder C owned by the satellite constellation management business apparatus.
Then, the satellite constellation operator carries out collision analysis using space object information A and space object information B, and when a collision is foreseen, the satellite constellation company carries out avoidance actions to ensure flight safety. Secure.

*** Other configurations ***
In the present embodiment, the function of the information management device 1000 is realized by software. As a modification, the function 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 modified example of the present embodiment.
The information management device 1000 includes an electronic circuit instead 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 for Gate Array.
The function of the information management device 1000 may be realized by one electronic circuit, or may be realized by being distributed in a plurality of electronic circuits.
As another modification, some functions of the information management device 1000 may be realized by an electronic circuit, and the remaining functions may be realized by software.

Each of the processor and the electronic circuit is also called a processing circuit. That is, the function of the information management device 1000 is realized by the processing circuit.

In the above-described first to fifth embodiments, each device and each part of each system have been described as independent functional blocks. However, the configuration of each device and each system does not have to be the configuration as in the above-described embodiment. The functional blocks of each device and each system may have any configuration as long as the functions described in the above-described embodiment can be realized. Further, each device and each system may be composed of one device or a plurality of devices.

In the above embodiments 1 to 5, the names such as "part", "process", "procedure", "step", "process", and "means" in the constituent requirements of each device and each system are mutually exclusive. It can be read or rewritten as. For example, the "stage of paying insurance money" in the server described in the modified examples of the third and fourth embodiments can be read as a name such as "means for paying insurance money" or "department for paying insurance money". Further, the information disclosure unit of the information management device 1000 described in the fifth embodiment can be read as an information disclosure process, an information disclosure stage, an information disclosure process, or an information disclosure means.

Further, in the first to fifth embodiments, a plurality of parts may be combined and carried out. Alternatively, one part of these embodiments may be implemented. In addition, these embodiments may be implemented in any combination as a whole or partially.
In the first to fifth embodiments, the first to fifth embodiments may be freely combined. Further, 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.

It should be noted that the embodiments described above are essentially preferred examples and are not intended to limit the scope of the invention, the scope of application of the invention, and the scope of use of the invention. The above-described embodiment can be variously modified as needed.

20 satellite constellation, 21 orbital surface, 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 Equipment, 41 Mega Constellation Business Equipment, 42 LEO Constellation Business Equipment, 43 Satellite Business Equipment, 44 Orbit Transition Business Equipment, 45 Debris Recovery Business Equipment, 46 Rocket Launch Business Equipment, 47 SSA Business Equipment, 50 Space Information recorder, 51 orbital forecast information, 511,521 Space object ID, 512 Forecasting period, 513 Forecasting orbital element, 514 Forecast error, 515 Forecast flight status, 52 Orbital actual information, 522 Original period, 523 Actual orbital element, 524 Specific achievements, 525 Actual flight states, 241 Specific times, 242 Actual position coordinates, 515 Forecast flight states, 60 Space objects, 65 Danger prediction objects, 69 Avoidance space objects, 70 Earth, 100, 100a Collision avoidance support device, 110 Recorder processing Unit, 120 alarm control unit, 130 achievement presentation unit, 131 collision record, 140 storage unit, 141 alarm issuance information, 150 avoidance decision unit, 160 machine learning unit, 401 flight forecast information, 402 flight record information, 403 avoidance 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 Collision Prediction Object, 602 Approach Prediction Object, 65 Danger Prediction 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 (52)

In a space insurance support device that supports the operation of space insurance that compensates for damage caused by collisions between space objects in multiple space objects flying in space
It is a danger warning indicating that there is a danger prediction object which is a plurality of space objects whose positional relationship is dangerous at the same time among the plurality of space objects, and is a predicted value of the orbit of each of the plurality of space objects. When the danger prediction object collides with the danger warning generated based on a certain orbit forecast information, the forecast value of the orbit in each of the danger prediction objects and each of the danger prediction objects A space insurance support device equipped with a liability evaluation department that evaluates accident liability and liability for damages based on actual orbital values. The orbit forecast information includes a forecast error predicted in the orbit.
The space insurance support device is
The space insurance support device according to claim 1, further comprising an insurance premium evaluation unit for evaluating insurance premiums in a management company that manages each of the plurality of space objects based on the forecast error. The insurance premium evaluation department
Based on the orbit forecast information and the orbit actual information including each orbit actual value of the danger prediction object, the smaller the difference between the orbit forecast value and the orbit actual value, the lower the insurance premium rate. The space insurance support device according to claim 2, which evaluates insurance premiums. The insurance premium evaluation department
The space insurance support device according to claim 2 or 3, wherein the premium is evaluated so that the smaller the difference between the forecast value of the orbit and the actual orbit value, the higher the premium paid. The responsibility evaluation department
Claims 1 to 4 for evaluating accident liability and damage liability so that the smaller the difference between the forecast value of the track and the actual track value, the less the accident liability and the liability for damages in the event of a collision. The space insurance support device according to any one of the above items. The responsibility evaluation department
One of claims 1 to 5 for evaluating accident liability and liability for damages so that an accident that occurs even though a collision accident can be predicted in advance is exempted from the liability clause based on the predicted value of the trajectory. Space insurance support device described in. The responsibility evaluation department
In the third-party liability insurance for the rocket launcher who operates the rocket launch business, only the parties involved in the collision accident are covered by the damages, and the higher damages are exempted from the liability. The space insurance support device according to any one of claims 1 to 6 to be evaluated. The responsibility evaluation department
The description in any one of claims 1 to 7, which evaluates accident liability and liability for damages so that the higher damage caused by the debris scattered due to the collision is covered by life insurance or in-orbit liability insurance. Space insurance support device. The responsibility evaluation department
The space insurance support device according to any one of claims 1 to 8, which evaluates accident liability and liability for damages so as to exempt a party other than the party paying the life insurance as an individual satellite or a group of satellites. The responsibility evaluation department
In the event of a collision between a space object that is operating constantly and a space object that is operating unsteadily, the accident liability and liability for damages will be increased so that the management company of the space object that is operating unsteadily will be more liable for accidents and damages. The space insurance support device according to any one of claims 1 to 9, which evaluates liability for damages. The responsibility evaluation department
If a satellite in the middle of a stationary satellite's orbit transition collides with a space object that is in constant operation, accident liability and damages will be increased so that the management company of the space object that is in constant operation will be more liable for accidents and damages. The space insurance support device according to any one of claims 1 to 10 for evaluating liability. The responsibility evaluation department
According to any one of claims 1 to 11 for evaluating accident liability and liability for damages so as to be exempt from collision with a mega constellation which is a large-scale satellite constellation formed at an orbit altitude of 600 km or less. The listed space insurance support device. The responsibility evaluation department
Claim from claim 1 that evaluates accident liability and liability for damages so as to be exempt from liability if collision avoidance operation measures are taken without notice in a collision accident between space objects equipped with a function to perform collision avoidance operation Item 12. The space insurance support device according to any one of items 12. The responsibility evaluation department
The invention according to any one of claims 1 to 13, wherein the accident liability and the liability for damages are evaluated based on the space information recorder including the orbit forecast information and the orbit record information in which the orbit record value is set. Space insurance support device. In a collision insurance execution device that executes the operation of space collision insurance that compensates for damage caused by collisions between space objects in multiple space objects flying in space
Based on the orbital forecast information that is the predicted value of the orbit of each of the plurality of space objects, the management company that owns the space object for which a collision is foreseen subscribes to the space collision insurance, and the collision is foreseen. Insurance premiums will be paid when an accident actually occurs, and the contract will be terminated if the dangerous time zone in which a danger warning is issued to notify the danger of a collision has passed without an accident. Collision insurance execution device equipped with a processing unit. The insurance processing department
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 department
Claim 15 or claim that a mega constellation operator holding a mega constellation, which is a large-scale satellite constellation, executes the operation of the space collision insurance that can be subscribed to by satellite group and can receive insurance money in the event of a collision accident. 16. The collision insurance execution device according to 16. The insurance processing department
The collision insurance execution device according to any one of claims 15 to 17, which executes the operation of the space collision insurance that covers higher-order damage caused by a collision chain caused by a foreseen collision accident. The insurance processing department
The collision insurance execution device according to any one of claims 15 to 18, which executes the operation of the space collision insurance in which the insurance premium and the insurance premium rate fluctuate according to the past results of similar collision accidents. A database that records insurance payment contract information for each insurance contract,
An insurance payment system that includes a server with a database that records space object information.
The contract information is
The space object information including the insurance premium rate, the accident liability assessment, and the insurance claim assessment amount is
Orbit forecast information of space object A and space object B where the collision accident occurred, and
Includes orbital performance information of space object A and space object B in the time zone when the collision occurred.
The server
At the stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred,
At the stage of assessing insurance payments based on the difference between actual track information and forecast track information,
An insurance payment system with a stage of paying insurance. A database that records insurance payment contract information for each insurance contract,
An insurance payment system that includes a server with a database that records space object information.
The contract information is
The space object information including the insurance premium rate, the accident liability assessment, and the insurance claim assessment amount is
Space object collision warning obtained from satellite information management company,
Orbit forecast information of space object A and space object B, which are predicted to collide, and
Orbital performance information of space object A and space object B in the time zone where the collision was predicted,
Including
The server
At the stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred,
At the stage of assessing insurance payments based on the difference between actual track information and forecast track information,
An insurance payment system with a stage of paying insurance. A database that records insurance payment contract information for each insurance contract,
An insurance payment system that includes a server with a database that records space object information.
The contract information is
The space object information including the insurance premium rate, the accident liability assessment, and the insurance claim assessment amount is
Space object collision warning obtained from satellite information management company,
Orbital forecast information including forecast orbit information and error information of space object A and space object B for which a collision is predicted, and
Orbital performance information of space object A and space object B in the time zone where the collision was predicted,
Including
The server
At the stage of accepting a contract after obtaining a space object collision warning,
The stage of determining the insurance premium rate based on the error information of the forecast orbit information recorded in the space object information,
At the stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred,
At the stage of assessing insurance payments based on the difference between actual track information and forecast track information,
The stage of paying insurance money and
The stage of completing payment and terminating the contract, the stage of terminating the contract due to exemption from liability, or the stage of terminating the contract without a collision accident due to a space object collision warning.
Insurance claim payment system with. A database that records insurance payment contract information for each insurance contract,
An insurance payment system that includes a server with a database that records space object information.
The contract information is
The space object information including the insurance premium rate, the accident liability assessment, and the insurance claim assessment amount is
Space object collision warning obtained from satellite information management company,
Orbital forecast information including forecast orbit information and error information of space object A and space object B for which a collision is predicted, and
Orbital performance information of space object A and space object B in the time zone where the collision was predicted,
Including
The server
At the stage of accepting a contract after obtaining a forecast of rocket launch, satellite orbit transition, or satellite passage in the middle of deorbit,
The stage of determining the insurance premium rate based on the error information of the forecast orbit information recorded in the space object information,
At the stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred,
At the stage of assessing insurance payments based on the difference between actual track information and forecast track information,
The stage of paying insurance money and
The stage of completing payment and terminating the contract, the stage of terminating the contract due to exemption from liability, or the stage of terminating the contract without a collision accident due to a space object collision warning.
Insurance claim payment system with. At the stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred.
The insurance claim payment system according to any one of claims 20 to 22, wherein the larger the difference between the actual track information and the forecast track information, the heavier the accident liability is assessed. At the stage of assessing the insurance payments for space object A and space object B that collided with each other based on the difference between the actual orbit information and the forecast orbit information after the collision accident occurred.
The insurance claim payment system according to any one of claims 20 to 22, wherein the smaller the difference between the actual track information and the forecast track information, the higher the insurance claim. The insurance claim payment system according to claim 21, wherein the insurance premium rate becomes lower as the estimated error amount becomes smaller at the stage of determining the insurance premium rate based on the error information of the forecast orbit information recorded in the space object information. Space object collision warning obtained from satellite information management company,
Orbit forecast information of space object A and space object B, which are predicted to collide, and
Despite getting
The insurance claim payment system according to claim 21 or 22, wherein both the management company of space object A and the management company of space object B are exempt from a collision accident in which a collision occurs without taking collision avoidance action. .. From claim 20, the contract information includes information that only the collision accident of the space object identified by the space object collision warning obtained from the satellite information management company is covered by insurance and the higher damage caused by the ball thrust accident is exempted from liability. The insurance claim payment system according to any one of claim 22. In addition to the collision accident of the space object identified by the space object collision warning obtained from the satellite information management company, the contract information includes the information stating that the damage compensation for the higher damage caused by the ball thrust accident is included in the insurance payment target. The insurance claim payment system according to any one of claims 20 to 22. At the stage of assessing the insurance payments for space object A and space object B that collided with each other based on the difference between the actual orbit information and the forecast orbit information after the collision accident occurred.
The insurance claim payment system according to claim 29, wherein compensation for damages caused by a ramming accident is subject to insurance claim assessment. The insurance claim payment system according to claim 20 or 21, which includes information exempted from liability for higher damage caused by debris scattered due to a collision at the time of launching a rocket, a collision of a debris removal satellite, or the like, in the contract information. Any of claims 20 to 22 that includes information exempted when the party to the space object collision is a mega constellation operator and has not paid insurance premiums as an individual satellite or satellite group in the contract information. Insurance claim payment system described in item 1. At the stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident between the space object in steady operation and the space object in unsteady operation occurred. The insurance claim payment system according to any one of claims 20 to 22, which seriously assesses the accident liability on the non-routine operation side. The stage of assessing the insurance payments for space object A and space object B that collided with each other based on the difference between the actual orbit information and the forecast orbit information after a collision accident between a space object in steady operation and a space object in unsteady operation occurred. The insurance claim payment system according to any one of claims 20 to 22, wherein the insurance claims on the regular operation side are assessed at a high price. Orbit transition At the stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after a collision accident between a satellite in the middle of orbit transition and a space object in steady operation occurs, the orbit transition The insurance claim payment system according to any one of claims 20 to 22, which lightly assesses the accident liability of a satellite on the way. At the stage of assessing the insurance payments for space object A and space object B that collided with the difference between the actual orbit information and the forecast orbit information after the collision accident between the satellite in the middle of the orbit transition and the space object that is in constant operation, it is steady. The insurance claim payment system according to any one of claims 20 to 22, which assesses the insurance claim on the investment side at a high price. The insurance claim payment system according to claim 20, which includes information exempted from collision with a mega constellation operator formed at an altitude of 600 km or less in the contract information. 23. The contract information includes information exempted from liability when collision avoidance operation measures are taken without prior notice in a collision accident between space objects having a function of performing collision avoidance operation, according to claim 21 or claim 22. Insurance claim payment system. The insurance claim payment system according to claim 22 or 23, wherein a mega-constellation operator can subscribe in units of satellite groups and receive insurance claims in the event of a collision accident caused by a collision warning or an ad hoc collision risk. The insurance claim payment system according to claim 22 or 23, wherein the error information included in the track forecast information includes an error amount calculation basis, and the insurance premium rate is set to be lower as the basis is clearer. The insurance claim payment system according to claim 22 or 23, wherein the error information included in the track forecast information includes verification results, and the insurance premium rate is set lower as the verification results are enhanced. The insurance claim payment system according to claim 22 or 23, wherein the assessment of the insurance premium rate fluctuates according to the past record of similar collision accidents. The insurance claim payment system according to any one of claims 20 to 23, wherein the assessment of accident liability and the assessment of insurance claims vary depending on the past record of similar collision accidents. A database that records insurance payment contract information for each insurance contract,
An insurance payment system that includes a server with a database that records space object information.
The contract information is
The space object information including the insurance premium rate, the accident liability assessment, and the insurance claim assessment amount is
Space object collision warning obtained from satellite information management company,
Orbit forecast information of space object A and space object B, which are predicted to collide, and
Including orbital performance information in the time zone where a collision is predicted,
The server
At the stage of accepting a contract after obtaining a space object collision warning,
The stage of determining the insurance premium rate based on the error information of the forecast orbit information recorded in the space object information,
At the stage of assessing the accident liability of space object A and space object B that collided by the difference between the actual orbit information and the forecast orbit information after the collision accident occurred,
At the stage of assessing insurance payments,
The stage of terminating the contract when the insurance payment is completed or the collision accident due to the space object collision warning does not occur,
Insurance claim payment system with. It is a space insurance program that causes a computer to execute a process of paying insurance money from a pre-collected premium when a space object A and a space object B collide with each other among a plurality of space objects.
Before the space objects in multiple space objects flying in space collide with each other, the existence of the danger prediction object is identified based on the orbit forecast information provided by the space information recorder, and a danger warning is output.
After the issuance of the danger warning of the collision avoidance support program, which is equipped with the danger warning output means
A management company that owns a space object for which a collision is foreseen is insured for space collision insurance, and when a foreseen collision accident actually occurs, the insurance money is paid and a danger warning is notified of the danger of collision. A space insurance program that is an ad hoc space collision insurance that terminates the contract if the dangerous time zone in which was announced has passed without any accident. The space insurance program according to claim 45, wherein a mega constellation operator holding a mega constellation, which is a large-scale satellite constellation, can join by satellite group and receive insurance money in the event of a collision accident. The space insurance program according to claim 45 or 46, which does not cover higher damage associated with a collision chain resulting from a foreseen collision accident. The space insurance program according to any one of claims 45 to 47, which covers higher-order damage caused by a collision chain caused by a foreseen collision accident. The space insurance program according to any one of claims 45 to 48, wherein the contents of the insurance premium rate setting means and the insurance claim assessment means vary depending on the past results of similar collision accidents. It is a space insurance program that causes a computer to execute a process of paying insurance money from a pre-collected premium when a space object A and a space object B collide with each other among a plurality of space objects.
From the management business equipment used by the management business operator that manages a plurality of space objects flying in space, flight forecast information representing the flight forecast of each of the plurality of space objects is acquired, and the acquired flight forecast information is used. Based on this, the forecast source period of each orbit of the plurality of space objects, the forecast orbit element that specifies the orbit, and the forecast error predicted in the orbit are set as the orbit forecast information, and the orbit forecast information is used. A space insurance program that includes means for setting insurance premiums based on orbit forecast errors included in the orbit forecast information provided by the space information recorder. It is a space insurance program that causes a computer to execute a process of paying insurance money from a pre-collected premium when a space object A and a space object B collide with each other among a plurality of space objects.
As a means of assessing insurance claims
The flight record information representing the flight record of each of the plurality of space objects is acquired from at least one of each of the plurality of space objects flying in space and the management business device that manages the space object, and the acquired flight record. Based on the information, the actual period of each orbit of the plurality of space objects, the actual orbital element for specifying the orbit, and the actual position coordinates of each of the plurality of space objects are set as the orbital actual information. The orbital record information at the time when the space objects collide with each other is extracted as the collision record from the orbital record information provided by the space information recorder including the orbital record information, and the orbital forecast information at the time when the space objects collide with each other is extracted from the orbital forecast information. Is extracted as pre-collision forecast information,
Difference information between collision record and pre-collision forecast information of space object A Difference information B between collision record and pre-collision forecast information of space object B
A space insurance program that provides a means of assessing insurance claims by comparison with. The insurance premium rate setting means
The space insurance program according to claim 50, which changes the insurance premium rate based on the grounds and verification results, including the forecast error of the space information recorder.

Images