Collision Avoidance Assistance System and Open Architecture Data Repository

Abstract

To identify the presence of a dangerous predicted object on the basis of orbit forecast information of a space object, output a danger warning, and determine the space object for performing avoidance operation, before the space objects flying in the space collide with each other.SOLUTION: A server 602 of a collision avoidance assistance system 200 includes: when predicting that a space object A included in a plurality of space objects enters a range of a dangerous area, receiving, from a space information recorder 100, a notification that the space object A is predicted to enter the range; acquiring, from the space information recorder 100, a time period from when the space object A enters the range to when the space object A leaves the range, and orbit forecast information; notifying a danger warning in the time period to all or some of a business operator of the space object A, a satellite business operator having a satellite flying in the range of the dangerous area, and a debris removal business operator; selecting a collision avoidance business operator candidate by means of a collision avoidance selection unit 230; and requesting a collision avoidance action from a collision avoidance business operator.SELECTED DRAWING: Figure 19

Description

[Technical Field]

[0001] The present disclosure relates to a collision avoidance assistance system, an information management method, a megaconstellation business device, a debris removal business device, a debris removal system, a debris removal program, an SSA business device, a collision avoidance assistance business device, a satellite business device, a constellation business device, a rocket launch business device, a business device, and an open architecture data repository. [Background technology]

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

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

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

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

[0006] With the increase in space debris, the rise in the number of satellites due to the emergence of mega-constellations, and improvements in ground monitoring capabilities, it is becoming difficult to continue the traditional warning service provided by the US CSpOC. Space Situation Awareness (SSA) is required to determine whether debris will intrude into satellite constellations. However, Patent Document 1 does not describe a method for accurately predicting the intrusion of a space object into a densely populated area of ​​a satellite constellation.

[0007] The present disclosure aims to accurately predict the intrusion of space objects into dense areas of satellite constellations. [Means for solving the problem]

[0008] The collision avoidance assistance system according to the present disclosure comprises: A collision avoidance support system that acquires space object information from a space information recorder that records space object information acquired from a management business device used by a management business that manages multiple space objects, and supports collision avoidance between the multiple space objects, a server including a database for storing the space object information acquired from the space information recorder and a determination means for determining a collision avoidance operator; Equipped with The server receiving a notification from a space information recorder that a space object A included in the plurality of space objects is predicted to enter an orbital altitude range of 300 km to 1000 km where a constellation of satellites operating between 10:00 and 11:00 LST (Local Sun Time) is present; A step of acquiring the time period from when the space object A enters the range until when it leaves the range and orbital forecast information from a space information recorder; a step of notifying a danger alert for the time period to all or some of the operators of the space object A, satellite operators who own satellites flying in the range, and debris removal operators; selecting a candidate collision avoidance operator; A stage where collision avoidance operators are requested to take collision avoidance action. It has. [Effects of the Invention]

[0009] The collision avoidance assistance system according to the present disclosure has the effect of accurately predicting the intrusion of a space object into a densely populated area, selecting a collision avoidance operator, and requesting collision avoidance action. [Brief explanation of the drawings]

[0010] [Figure 1] An example of multiple satellites working together to provide communications services across the entire globe. [Figure 2] An example of Earth observation services realized by multiple satellites in a single orbital plane. [Figure 3] An example of a satellite constellation with multiple orbital planes that intersect near the polar regions. [Figure 4] An example of a satellite constellation with multiple intersecting orbital planes outside the polar regions. [Figure 5] A diagram of the satellite constellation formation system. [Figure 6] A diagram of the satellite configuration of the satellite constellation formation system. [Figure 7] A diagram of the ground equipment for the satellite constellation formation system. [Figure 8] An example of the functional configuration of a satellite constellation formation system. [Figure 9] 2 shows an example of a space information recorder according to the first embodiment. [Figure 10] 3 shows an example of orbit forecast information according to the first embodiment. [Figure 11] FIG. 4 is a flow diagram of an intrusion alarm process by the space information recorder according to the first embodiment. [Figure 12]10 shows an example of a predicted orbit of debris passing through a satellite constellation and an intrusion warning according to the first embodiment. [Figure 13] 10 shows an example of space object information in a space information recorder according to an embodiment. [Figure 14] 10 is a detailed example of orbit forecast information of space object information in the space information recorder according to the first embodiment. [Figure 15] 4 shows examples of approach warnings and collision warnings for space object information according to the first embodiment. [Figure 16] 10 shows an example of an intrusion alarm based on space object information according to the first embodiment. [Figure 17] 10 is a detailed example of orbit performance information of space object information in the space information recorder according to the first embodiment. [Figure 18] 10 shows a configuration example of a space information recorder according to a modified example of the first embodiment. [Figure 19] 10 shows an example of the configuration of a collision avoidance assistance system according to a second embodiment. [Figure 20] 10 shows another example of the configuration of the collision avoidance assistance system according to the second embodiment. [Figure 21] 11 shows an example of the configuration of a space information recorder provided in a megaconstellation business device according to the third embodiment. [Figure 22] 10 shows an example of the configuration of a debris removal satellite according to a fourth embodiment. [Figure 23] 10 shows an example of the configuration of a debris removal system according to a fourth embodiment. [Figure 24] 10 shows an example of the orbit of debris that enters the satellite orbital region according to the fourth embodiment. [Figure 25] 10 shows an example of the orbit of debris that enters the satellite orbital region according to the fourth embodiment. [Figure 26] FIG. 13 is a diagram showing an example of an OADR according to a fifth embodiment. [Figure 27] FIG. 13 is a diagram showing another example of the OADR according to the fifth embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

[0016] Fig. 3 is an example of a satellite constellation 20 having multiple orbital planes 21 that intersect near the polar regions, and Fig. 4 is an example of a satellite constellation 20 having multiple orbital planes 21 that intersect outside the polar regions. In the satellite constellation 20 of FIG. 3, the orbital inclination angle of each of the multiple orbital planes 21 is approximately 90 degrees, and each of the multiple orbital planes 21 exists in a different plane from each other. In the satellite constellation 20 of FIG. 4, the orbital inclination angle of each of the multiple orbital planes 21 is not approximately 90 degrees, and each of the multiple orbital planes 21 exists in a different plane from each other.

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

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

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

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

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

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

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

[0024] 5 to 8, an example of satellites 30 and ground equipment 700 in a satellite constellation forming system 600 that forms a satellite constellation 20 will be described. For example, the satellite constellation forming system 600 is operated by a satellite constellation business operator such as a megaconstellation business equipment 41, a LEO constellation business equipment 42, or a satellite business equipment 43.

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

[0026] The satellite constellation forming system 600 includes a satellite 30 and a ground facility 700. The satellite 30 includes a satellite communication device 32 that communicates with a communication device 950 of the ground facility 700. Fig. 5 illustrates the satellite communication device 32, which is one of the components included in the satellite 30.

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

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

[0029] FIG. 6 is a diagram showing the configuration of a satellite 30 of a satellite constellation forming system 600. The satellite 30 comprises a satellite control device 31, a satellite communication device 32, a propulsion device 33, an attitude control device 34, and a power supply device 35. It also comprises other components that realize various functions, but Fig. 6 will explain the satellite control device 31, the satellite communication device 32, the propulsion device 33, the attitude control device 34, and the power supply device 35. The satellite 30 is an example of a space object 60.

[0030] The satellite control device 31 is a computer that controls the propulsion devices 33 and the attitude control device 34, and includes a processing circuit. Specifically, the satellite control device 31 controls the propulsion devices 33 and the attitude control device 34 in accordance with various commands transmitted from the ground facility 700. The satellite communication device 32 is a device that communicates with the ground facility 700. Specifically, the satellite communication device 32 transmits various data related to its own satellite to the ground facility 700. In addition, the satellite communication device 32 receives various commands transmitted from the ground facility 700. The propulsion device 33 is a device that provides thrust to the satellite 30 and changes the speed of the satellite 30. Specifically, the propulsion device 33 is an apogee kick motor, a chemical propulsion device, or an electric propulsion device. The apogee kick motor (AKM) is an upper stage propulsion device used to put an artificial satellite into orbit, and is also called an apogee motor (when a solid rocket motor is used) or an apogee engine (when a liquid engine is used). Chemical propulsion systems are thrusters that use monopropellant or bipropellant fuels. Electric propulsion systems include ion engines and Hall thrusters. An apogee kick motor is a device used for orbital transfer and can also be a type of chemical propulsion system. The attitude control device 34 is a device for controlling attitude elements such as the attitude of the satellite 30, its angular velocity, and line of sight. The attitude control device 34 changes each attitude element to a desired direction. Alternatively, the attitude control device 34 maintains each attitude element in a desired direction. The attitude control device 34 includes an attitude sensor, an actuator, and a controller. The attitude sensor is a device such as a gyroscope, an earth sensor, a sun sensor, a star tracker, a thruster, and a magnetic sensor. The actuator is a device such as an attitude control thruster, a momentum wheel, a reaction wheel, and a control moment gyro. The controller controls the actuator according to measurement data from the attitude sensor or various commands from the ground equipment 700. The power supply unit 35 includes devices such as solar cells, batteries, and a power control device, and supplies power to each device mounted on the satellite 30.

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

[0032] FIG. 7 is a configuration diagram of a ground facility 700 provided in the satellite constellation forming system 600. The ground equipment 700 controls programs for multiple satellites in all orbital planes. The ground equipment 700 is an example of ground equipment. The ground equipment is composed of a ground station such as a ground antenna device, a communication device connected to the ground antenna device, or a computer, and ground equipment as a server or terminal connected to the ground station via a network. The ground equipment may also include a communication device mounted on a moving object such as an aircraft, a self-propelled vehicle, or a mobile terminal.

[0033] The ground facility 700 forms the satellite constellation 20 by communicating with each satellite 30. The ground facility 700 includes a processor 910 as well as other hardware such as a memory 921, an auxiliary storage device 922, an input interface 930, an output interface 940, and a communication device 950. The processor 910 is connected to the other hardware via signal lines and controls the other hardware. The hardware of the ground facility 700 will be described later with reference to FIG. 8.

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

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

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

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

[0038] The processor 910 is a device that executes a program. The program is a program that realizes the functions of the ground equipment 700. In Fig. 8, the program that realizes the functions of the ground equipment 700 is a satellite constellation formation program that forms a satellite constellation. The processor 910 is an integrated circuit (IC) that performs arithmetic processing. Specific examples of the processor 910 include a central processing unit (CPU), a digital signal processor (DSP), and a graphics processing unit (GPU).

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

[0040] The input interface 930 is a port connected to an input device such as a mouse, a keyboard, or a touch panel. Specifically, the input interface 930 is a USB (Universal Serial Bus) terminal. Note that the input interface 930 may also be a port connected to a LAN (Local Area Network). The output interface 940 is a port to which a cable of a display device 941 such as a display is connected. Specifically, the output interface 940 is a USB terminal or an HDMI (registered trademark) (High Definition Multimedia Interface) terminal. Specifically, the display is an LCD (Liquid Crystal Display).

[0041] The communication device 950 includes a receiver and a transmitter, and is specifically a communication chip or a network interface card (NIC).

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

[0043] The ground equipment 700 may include multiple processors that replace the processor 910. These multiple processors share the task of executing a program. Each processor is a device that executes a program, just like the processor 910.

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

[0045] The "parts" of the parts of the ground equipment 700 may be read as "processing," "procedure," "means," "stage," or "step." Also, the "processing" of the passage determination processing, alarm generation processing, and alarm notification processing may be read as "program," "program product," or "computer-readable recording medium on which a program is recorded." "Processing," "procedure," "means," "stage," or "step" may be read as interchangeable with each other. The program causes the computer to execute each process, procedure, means, stage or step of the ground equipment 700, where the "part" in each part is replaced with "process," "procedure," "means," "stage" or "process." The programs may be provided in a state stored in a computer-readable recording medium, or may be provided as a program product.

[0046] ***Configuration Description*** FIG. 9 is a configuration diagram of a space information recorder 100 according to this embodiment. The space information recorder 100 communicates with the management business device 40. The space information recorder 100 may be mounted on the ground facility 700. The space information recorder 100 may also be mounted on the satellite constellation forming system 600. Alternatively, the space information recorder 100 may be mounted on at least one of the management business devices 40, such as the SSA business device 47. Alternatively, the space information recorder 100 may be mounted on an orbit analysis service provider.

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

[0048] The megaconstellation business device 41 manages a megaconstellation consisting of 100 or more satellites. The megaconstellation business device 41 is a computer of a megaconstellation operator that operates a large-scale satellite constellation, that is, a megaconstellation business. The LEO constellation business equipment 42 is a computer of a LEO constellation business operator that operates a low earth orbit constellation, i.e., a LEO constellation business. The satellite business device 43 is a computer of a satellite operator that handles one to several satellites. The orbital transfer business device 44 is a computer of the orbital transfer business that issues space object intrusion warnings to satellites. The debris removal business device 45 is a computer of a debris removal business operator that carries out the business of collecting debris. The rocket launch business device 46 is a computer of a rocket launch business that carries out rocket launch business. The SSA business device 47 is a computer of an SSA business operator that performs the SSA business, i.e., the space situational awareness business.

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

[0050] The space information recorder 100 includes a processor 910 as well as other hardware such as a memory 921 , an auxiliary storage device 922 , and a communication device 950 .

[0051] The space information recorder 100 includes, as functional elements, a determination unit 110, a notification unit 120, and a storage unit 140. The storage unit 140 stores orbit forecast information 51.

[0052] The functions of the determination unit 110 and the notification unit 120 are realized by software or hardware. The storage unit 140 is provided in the memory 921. Alternatively, the storage unit 140 may be provided in the auxiliary storage device 922. Moreover, the storage unit 140 may be provided separately in the memory 921 and the auxiliary storage device 922.

[0053] FIG. 10 is a diagram showing an example of orbit forecast information 51 included in space object information 500 according to this embodiment. The space information recorder 100 stores orbit forecast information 51 in which forecast values ​​for the orbit of a space object 60 are set in the memory unit 140. The space information recorder 100 may, for example, obtain forecast values ​​for the orbit of each of the multiple space objects 60 from a management business device 40 used by a management business operator that manages multiple space objects 60, and store this as orbit forecast information 51. Alternatively, the space information recorder 100 may obtain orbit forecast information 51 in which forecast values ​​for the orbit of each of the multiple space objects 60 are set from the management business operator, and store this in the memory unit 140. The management operators are operators that manage space objects 60 flying in space, such as satellite constellations, various satellites, rockets, and debris. As described above, the management business devices 40 used by each management operator are computers such as a megaconstellation business device 41, a LEO constellation business device 42, a satellite business device 43, an orbital transfer business device 44, a debris removal business device 45, a rocket launch business device 46, and an SSA business device 47.

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

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

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

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

[0058] The forecast error 514 is an error predicted for each orbit of a plurality of space objects. The forecast error 514 includes a heading error, a cross-directional error, and the basis for the error. In this way, the forecast error 514 explicitly indicates the amount of error contained in the actual value along with the basis. The basis for the amount of error includes some or all of the measurement means, the details of data processing performed as a means for improving the accuracy of position coordinate information, and the results of statistical evaluation of past data.

[0059] In the orbit forecast information 51 according to this embodiment, a forecast origin 512 and forecast orbital elements 513 are set for the space object 60. The forecast origin 512 and forecast orbital elements 513 can be used to determine the time and position coordinates in the near future of the space object 60. For example, the time and position coordinates in the near future for the space object 60 may be set in the orbit forecast information 51. In this way, the orbit forecast information 51 includes orbit information of the space object, including the epoch and orbital elements, or the time and position coordinates, and explicitly indicates the predicted values ​​of the space object 60 in the near future.

[0060] ***Explanation of Operation*** FIG. 11 is a flow diagram of an intrusion alarm process by the space information recorder 100 according to this embodiment. FIG. 12 is a diagram showing an example of a predicted orbit of debris passing through the satellite constellation 20 and an intrusion warning 111 according to this embodiment.

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

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

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

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

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

[0066] <Detailed function explanation of Space Information Recorder 100> The space information recorder 100 acquires and records space object information 500, which is orbital forecast information 51 for multiple space objects, from a management business device 40 used by a management business that manages multiple space objects flying in space. Space object information 500 includes forecast epochs 512, forecast orbital elements 513, and forecast errors 514 for multiple space objects.

[0067] FIG. 13 is an example of space object information 500 in the space information recorder 100 according to this embodiment. FIG. 14 is a detailed example of orbit forecast information 51 of space object information 500 in space information recorder 100 according to this embodiment. FIG. 15 shows an example of an approach warning 501 and a collision warning 502 in space object information 500 according to this embodiment. FIG. 16 shows examples of intrusion alarms 503, 504, and 505 in space object information 500 according to this embodiment.

[0068] 14, satellite IDs A, B, C, D, E, and F are provided by management operators 40a, such as satellite operators, SSA operators, rocket operators, debris removal operators, and orbital transfer operators. Also, debris IDs A, B, Γ, and Δ are provided by management operators 40b, such as satellite operators, SSA operators, and rocket operators. 14, the mega constellation IDs MA, MB, and MC indicate that the information is provided by the mega constellation operator 40c, and the mega constellation IDs MD, ME, and MF indicate that the information is provided by the mega constellation operator 40d. 14, CA in the constellation ID indicates that the information is provided by the constellation operator 40e, CB in the constellation ID indicates that the information is provided by the constellation operator 40f, and CC in the constellation ID indicates that the information is provided by the constellation operator 40g.

[0069] As shown in Figure 16, when it is predicted that space object A, which is included in multiple space objects, will enter a dense orbit or a high-latitude polar region, the space information recorder 100 records the time period from entry to departure and orbit forecast information. A dense orbit is an orbital altitude range of 300 km to 1000 km in which a constellation of satellites exists between 10:00 and 11:00 LST. Specifically, this is the case when the space information recorder 100 issues an intrusion warning 504 in FIG. The polar and high latitude regions are those areas above 80 degrees north latitude or above 80 degrees south latitude where polar orbiting satellites are concentrated, and in the range of orbital altitudes from 300 km to 1000 km. Specifically, this is the case when the space information recorder 100 issues an intrusion alarm 505 in FIG. 16.

[0070] As shown in Figure 13, the space information recorder 100 records as orbital information the upper and lower limit values ​​of the orbital altitude of a group of constellation satellites that fly at the same nominal altitude and work together to accomplish the same mission, obtained from the megaconstellation business equipment.

[0071] In addition, as shown in Figure 13, the space information recorder 100 records as orbit information the upper and lower limit values ​​of the orbital inclination angles of a group of constellation satellites that fly at the same nominal altitude and work together to accomplish the same mission, obtained from the megaconstellation business device.

[0072] When it is foreseeable that space object A will enter the orbital altitude and latitude bands where the satellites that make up the megaconstellation are located, the space information recorder 100 records the time period from the entry to the departure and the orbital forecast information. Specifically, this is the case when the space information recorder 100 issues an intrusion warning 503 in Figure 16.

[0073] The space information recorder 100 includes an issuing means (announcement unit 120) for issuing an intrusion alarm 111 when it is foreseeable that another space object will intrude into the orbital altitude band and latitude band in which the satellite group exists.

[0074] 17 is a detailed example of orbit performance information 519 of space object information 500 in space information recorder 100 according to this embodiment. Orbit performance information 519 is also called precise orbit performance or high-precision orbit performance information. Space object information 500 includes orbit forecast information 51 as well as orbit performance information 519 . Orbit performance information 519 includes the time of collision estimated by post-mortem verification after a collision accident between space object A and space object B, position information of space object A at or just before that time, and position information of space object B at or just before that time.

[0075] Furthermore, if space object A is a rocket and it is foreseeable that it will enter an orbital altitude and latitude band in which a group of satellites exists during launch, the space information recorder 100 records the time period from the time of entry to the time of departure, as well as orbital forecast information.

[0076] In addition, if space object A is a space object in the process of deorbiting and it is foreseeable that it will enter an orbital altitude and latitude band in which a group of satellites exists during the deorbiting process, the space information recorder 100 records the time period from entry to departure and orbit forecast information.

[0077] In addition, if space object A is a space object in the process of orbital transfer and it is foreseeable that it will enter an orbital altitude and latitude band in which a group of satellites exists during the orbital transfer, the space information recorder 100 records the time period from the entry to the departure and orbital forecast information.

[0078] The space information recorder 100 also acquires flight forecast information representing a forecast of the flight of each of the space objects from a management business device used by a management business that manages multiple space objects flying in space. Based on the acquired flight forecast information, the space information recorder 100 sets the forecast origin of the orbit of each of the space objects, the forecast orbital elements that specify the orbit, and the forecast error predicted in the orbit as orbit forecast information. The space information recorder 100 stores the orbit forecast information thus set. The space information recorder 100 registers the orbital forecast information obtained from the megaconstellation business device as orbital information, not as individual satellite information, but as the orbital altitude and orbital inclination of the satellite group. The space information recorder 100 is equipped with a warning means (warning unit 120) that issues an intrusion warning when it is foreseeable that another space object will intrude into the orbital altitude and latitude range in which the satellites constituting the megaconstellation exist. The latitude range in which the satellites exist depends on the orbital inclination angle.

[0079] ***Explanation of the effect of this embodiment*** Normally, when a space object collision is predicted, the SSA operator issues a proximity or collision warning, and the ISS or satellite operator takes evasive action as necessary. With the emergence of mega-constellations, it will become difficult for external organizations other than mega-constellation operators, who possess highly accurate orbital information, to conduct collision prediction analysis. Therefore, a review of this warning system is necessary. This embodiment focuses on a specific orbital altitude at which mega-constellation operators deploy satellites across the sky. A system is described that issues an intrusion warning for a satellite or debris that has deorbited and is currently descending its orbit and is predicted to pass through that altitude.

[0080] Furthermore, in areas near LST 10:30 and in dense orbits at altitudes of 500 to 800 km, or when passing through dense areas such as polar and high latitude regions, there are many satellites with a high risk of collision. There is also a high likelihood that many operators will be affected, and there is also concern that they will not be able to take evasive action. Around LST 10:30, sun-synchronous orbits are frequently used by optical satellites for Earth observation purposes. Polar-orbiting satellites frequently pass through polar and high latitude regions. Therefore, in this embodiment, a system has been described that issues an intrusion warning for dense orbits and polar and high latitude regions, even when it is predicted that a satellite or debris that has deorbited and is in orbital descent will intrude into the dense orbit.

[0081] Regarding intrusion warnings into mega-constellations, mega-constellation operators will be able to conduct collision analysis using their own high-precision orbital information and take action to avoid collisions if necessary. For warnings of intrusions into dense orbits and polar and high-latitude regions, it may be possible to avoid collisions by notifying the relevant parties as well as debris removal companies, and having the invading object remove the debris.

[0082] Existing space insurance policies for collision accidents have covered accidental accidents or accidental breakdowns. However, the orbital altitudes adopted by mega-constellations, or the situations where intrusion warnings are issued when passing through dense orbits or polar or high latitudes, are difficult to call accidental accidents, and can be considered as foreseeable collision accidents. Furthermore, if a collision occurs, there is a high risk of it colliding with other satellites flying nearby, causing further damage. Therefore, in order to apply existing insurance, the frequency of accidents and the expected scale of damages will differ significantly, which will require a review of insurance rates, exclusion clauses, contract terms, and premiums. In particular, for mega-constellations, it is more reasonable to take out insurance for a group of satellites, rather than taking out space insurance for each individual satellite. In order to distinguish between accidental accidents and foreseeable collision accidents, it is conceivable to establish a new ad hoc space object collision insurance that can be purchased after a proximity or collision warning is issued, with the contract terminating once the foreseeable risk has been resolved. The space object intrusion warning system is a new concept in this regard, but it would be reasonable to have a system in place that allows space collision insurance to be purchased after an intrusion warning is issued, just like a proximity or collision warning.

[0083] In response to an intrusion alert, the invading party, the megaconstellation, the dense orbit satellite, and the polar transit satellite may take evasive action. In addition to this possibility, debris removal companies may also remove the intruding object to avoid a collision. Therefore, there are a wide range of response options. Furthermore, it is necessary to assess the risk of taking evasive action itself, such as whether taking evasive action would result in a collision with another space object. If it is determined that taking evasive action increases the risk, there may be an option to "not take evasive action in response to an intrusion alarm." Difficult negotiations will be necessary between the parties involved to decide who will take evasive action or who will outsource the debris removal to a company, and how to share the costs involved. Therefore, consulting or advice from collision avoidance support experts will be effective.

[0084] The space information recorder according to this embodiment can accurately predict the intrusion of space objects into densely populated areas such as megaconstellations, dense orbits, and polar and high latitude regions, and can also store detailed information on space objects in the event of a collision.

[0085] ***Other Configurations*** In this embodiment, the functions of the space information recorder 100 are realized by software. As a modification, the functions of the space information recorder 100 may be realized by hardware.

[0086] FIG. 18 is a diagram showing the configuration of a space information recorder 100 according to a modified example of this embodiment. The space information recorder 100 includes an electronic circuit 909 instead of a processor 910 . The electronic circuit 909 is a dedicated electronic circuit that realizes the functions of the space information recorder 100 . The electronic circuit 909 is specifically a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA, where GA is an abbreviation for Gate Array. The functions of the space information recorder 100 may be realized by one electronic circuit, or may be realized by distributing the functions across multiple electronic circuits. As another modification, some of the functions of the space information recorder 100 may be realized by electronic circuits, and the remaining functions may be realized by software.

[0087] Each of the processor and the electronic circuit is also called a processing circuitry. In other words, the functions of the space information recorder 100 are realized by the processing circuitry.

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

[0089] ***Configuration Description*** FIG. 19 is a diagram showing an example of the configuration of a collision avoidance assistance system 200 according to this embodiment. The collision avoidance support system 200 acquires space object information 500 from the space information recorder 100 and supports collision avoidance between multiple space objects. The space information recorder 100 records the space object information 500 acquired from a management business device 40 used by a management business operator that manages multiple space objects.

[0090] The collision avoidance assistance system 200 includes a database 601 and a server 602. The database 601 stores space object information 500 acquired from the space information recorder 100. The server 602 includes a determination means for determining a collision avoidance operator. The database 601 and the server 602 are included in a ground facility 701. The ground facility 701 is also called a collision avoidance assistance device.

[0091] The server 602 includes, as functional elements, a notification receiving unit 210, a danger notification unit 220, and a collision avoidance selection unit 230.

[0092] The notification receiving unit 210 has a step of receiving a notification from the space information recorder 100 that an intrusion has been predicted when it is foreseeable that a space object A included in the multiple space objects will intrude into the range of a danger area. The notification receiving unit 210 also has a step of acquiring from the space information recorder 100 the time period from when the space object A enters the danger zone until when it leaves, and orbit forecast information.

[0093] The danger notification unit 220 has a step of notifying the operator of space object A, the satellite operator that owns the satellite flying within the danger area, and all or some of the debris removal operators of a danger alert for that time period.

[0094] The collision avoidance selection unit 230 includes a step of selecting a collision avoidance business candidate and a step of requesting the collision avoidance business to take a collision avoidance action. The collision avoidance selection unit 230 is an example of a determination means.

[0095] In the following embodiments, a "unit" having a "stage" can be replaced with phrases such as "a unit has a function," "a unit realizes a function," or "a unit executes processing."

[0096] Specifically, it is as follows: The notification receiving unit 210 has the function of receiving a notification from the space information recorder 100 that an intrusion has been predicted when it is foreseen that space object A, which is included in multiple space objects, will intrude into the danger zone. The notification receiving unit 210 also has the function of acquiring from the space information recorder 100 the time period from when the space object A enters the danger zone until when it leaves, as well as orbit forecast information. The danger notification unit 220 has the function of reporting danger alerts for that time period to all or some of the operators of space object A, satellite operators that own satellites flying within the danger area, and debris removal operators. The collision avoidance selection unit 230 has a function of selecting collision avoidance business candidates and a function of requesting collision avoidance businesses to take collision avoidance actions.

[0097] Specific examples of the range of the danger area are as follows: For example, the notification receiving unit 210 receives an intrusion notification from the space information recorder 100 when it is foreseeable that space object A will intrude into the range of orbital altitudes of 300 km to 1000 km, where a constellation of satellites exists from 10:00 to 11:00 LST.

[0098] For example, the notification receiving unit 210 receives an intrusion notification from the space information recorder 100 when it is foreseeable that space object A will intrude into an area above 80 degrees north latitude or above 80 degrees south latitude, where polar orbiting satellites are densely concentrated, at an orbital altitude of 300 km to 1000 km.

[0099] For example, the notification receiving unit 210 receives an intrusion notification from the space information recorder 100 when it is foreseeable that space object A will intrude into the range of orbital altitude and latitude where a group of satellites that make up a megaconstellation consisting of 100 or more satellites exists.

[0100] The collision avoidance selection unit 230, which is a determination means, selects a management company for the space object A that has a collision avoidance function. The server 602 has a step of requesting the management company of the space object A to take intrusion avoidance action to change the time period or orbit of the intrusion of the space object A. Specifically, the collision avoidance selection unit 230 requests the management company of the space object A to take intrusion avoidance action to change the time period or orbit of the intrusion of the space object A.

[0101] The collision avoidance selection unit 230, which is a decision means, selects a debris removal company. The server 602 has a step of requesting the debris removal operator to take intrusion avoidance action to capture space object A and change the time period or orbit of the object to enter the danger zone. Specifically, the collision avoidance selection unit 230 requests the debris removal operator to take intrusion avoidance action to capture space object A and change the time period or orbit of the object to enter the danger zone.

[0102] The collision avoidance selection unit 230, which is a determination means, selects a megaconstellation operator. The server 602 has a step of requesting the megaconstellation operator to take action to avoid collision between the satellites that make up the megaconstellation and the space object A. Specifically, the collision avoidance selection unit 230 requests the megaconstellation operator to take action to avoid collision between the satellites that make up the megaconstellation and the space object A.

[0103] The collision avoidance assistance system 200 has a collision avoidance assistance program that causes a computer to execute the following processes. Before multiple space objects flying in space collide with each other, a process that identifies the presence of potentially dangerous objects based on the orbital forecast information of the space objects, outputs a danger warning, and determines which space objects should undergo avoidance operations. A process of obtaining flight forecast information representing the flight forecast of each of a plurality of space objects from a management business device used by a management business that manages a plurality of space objects flying in space. A process of setting the forecast origin of the orbit of each of the multiple space objects, the forecast orbit elements that identify the orbit, and the forecast error predicted in the orbit as orbit forecast information based on the acquired flight forecast information. - Danger warning output processing that outputs a danger warning indicating the presence of a potential dangerous object when it is predicted that another space object will enter the orbital altitude and latitude band in which the satellites that make up the megaconstellation exist, based on the orbital forecast information provided by the space information recorder.

[0104] The collision avoidance assistance system 200 also has a collision avoidance assistance program that causes a computer to execute the following processes. Before multiple space objects flying in space collide with each other, a process that identifies the presence of potentially dangerous objects based on the orbital forecast information of the space objects, outputs a danger warning, and determines which space objects should undergo avoidance operations. A process of obtaining flight forecast information representing the flight forecast of each of a plurality of space objects from a management business device used by a management business that manages a plurality of space objects flying in space. A process of setting the forecast origin of the orbit of each of a plurality of space objects, the forecast orbit elements that identify the orbit, and the forecast error predicted in the orbit as orbit forecast information based on the acquired flight forecast information. - When it is predicted based on orbital forecast information that another space object will intrude into the orbital altitude and latitude band in which the satellites that make up the megaconstellation are located, the avoidance space object determination process determines which space objects, among those predicted to be hazardous, will undergo avoidance operations.

[0105] FIG. 20 is a diagram showing another example of the configuration of a collision avoidance assistance system 200 according to this embodiment. As shown in FIG. 20, a ground facility 701 (collision avoidance support device) may include a space information recorder 100. The server 602 includes a danger warning output unit 240 that identifies the presence of a potential hazardous object based on the orbital forecast information of the space objects before a collision occurs between the space objects among a plurality of space objects flying in space, outputs a danger warning, and determines which space object should undergo avoidance operations. The danger notification unit 220 and the collision avoidance selection unit 230 are examples of the danger warning output unit 240. The space information recorder 100 acquires flight forecast information representing a forecast of the flight of each of the multiple space objects from the management business device 40. Then, based on the acquired flight forecast information, the space information recorder 100 sets the forecast origin of the orbit of each of the multiple space objects, the forecast orbit elements that specify the orbit, and the forecast error predicted in the orbit as orbit forecast information.

[0106] ***Explanation of the effect of this embodiment*** The collision avoidance assistance system according to this embodiment can accurately predict the intrusion of a space object into a densely populated area, select a collision avoidance operator, and request collision avoidance action.

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

[0108] ***Configuration Description*** In this embodiment, an example of a management business device 40 equipped with a space information recorder 100 will be described. In particular, an example of a mega constellation business device 41 equipped with the space information recorder 100 will be described. Also, an information management method by the mega constellation business device 41 equipped with the space information recorder 100 will be described.

[0109] FIG. 21 is a diagram showing an example of the configuration of the space information recorder 100 included in the megaconstellation business device 41 according to this embodiment. For example, the megaconstellation business device 41 and the SSA business device 47 share the space information recorder 100 .

[0110] The space information recorder 100 acquires and records orbital forecast information for a plurality of space objects from a management business device 40 that manages a plurality of space objects flying in space. The SSA business equipment 47 also includes a space information recorder 100 . The megaconstellation enterprise 41 provides orbital forecast information to the SSA enterprise 47 . In this embodiment, an information management method of the megaconstellation business device 41 that provides orbital forecast information to the space information recorder 100 that the SSA business device 47 has will be described.

[0111] The space information recorder 100 of the megaconstellation business device 41 has, as orbit forecast information, upper and lower limit values ​​of the orbital altitude of the satellites that make up the megaconstellation, flying at the same nominal altitude and working together to accomplish the same mission. The megaconstellation business device 41 provides this orbit forecast information (public orbit information 61) to the SSA business device 47.

[0112] The space information recorder 100 of the mega-constellation business device 41 has, as orbit forecast information, upper and lower limit values ​​of the orbital inclination angles of the satellites that make up the mega-constellation, flying at the same nominal altitude and working together to accomplish the same mission. The mega-constellation business device 41 provides this orbit forecast information (public orbit information 61) to the SSA business device 47.

[0113] The space information recorder 100 of the mega constellation business device 41 receives an intrusion alert from the SSA business device 47 when it is foreseeable that space object A will intrude into the orbital altitude and latitude band in which the mega constellation satellites are located. Space object A is a space object included in the space information recorder 100 provided in the SSA business device 47. The mega constellation satellites are a group of satellites that make up a mega constellation.

[0114] When it is foreseeable that space object A will enter the orbital altitude and latitude band in which the mega constellation satellites exist, space information recorder 100 of mega constellation business device 41 obtains the time period from when space object A enters until when it leaves, and orbit forecast information, from SSA business device 47. Space information recorder 100 of mega constellation business device 41 obtains the time period from when space object A enters until when it leaves, and orbit forecast information for space object A, from space information recorder 100 of SSA business device 47.

[0115] When it is foreseeable that space object A will enter the orbital altitude and latitude bands in which the mega constellation satellite group exists, the space information recorder 100 of the mega constellation business device 41 performs a collision analysis using high-precision orbit forecast information for the satellite group it owns and the orbit forecast information for space object A. The space information recorder 100 of the mega constellation business device 41 performs a collision analysis using high-precision orbit forecast information for the satellite group owned by the mega constellation operator and the orbit forecast information for space object A.

[0116] If it is foreseeable that space object A will enter the orbital altitude and latitude band in which the mega constellation satellites exist, and if a collision is predicted as a result of the above collision analysis, the space information recorder 100 of the mega constellation business device 41 will provide the SSA business device 47 with a collision warning, orbit forecast information for the satellite with which the collision is predicted, and the predicted time of the collision.

[0117] The space information recorder 100 of the mega constellation business device 41 uses the orbit forecast information of the space object A when it is predicted that the space object A will collide with a satellite that makes up the mega constellation. The space information recorder 100 of the mega constellation business device 41 uses the orbit forecast information of the space object A as a control index for collision avoidance actions by the mega constellation business device.

[0118] In the information management method of the mega constellation business device 41, when it is foreseeable that a space object A contained in the space information recorder 100 equipped in the SSA business device 47 will enter the orbital altitude and latitude band in which the mega constellation satellite group exists, the following procedure is carried out. The megaconstellation business device 41 performs collision analysis using high-precision orbital forecast information for the satellite group owned by the megaconstellation business device 41 and orbital forecast information for space object A. If a collision is predicted, the megaconstellation business device 41 provides a collision warning, orbital information of the satellite for which the collision is predicted, and the predicted time of the collision to the management business device of the space object A and the management business device of the space insurance company.

[0119] The information management method of the megaconstellation business device 41 performs the following steps. The megaconstellation business device 41 obtains flight forecast information representing the flight forecast of each of multiple space objects from a management business device used by a management company that manages multiple space objects flying in space. Based on the acquired flight forecast information, the mega-constellation business device 41 sets the forecast origin of the orbit of each of the multiple space objects, the forecast orbital elements that specify the orbit, and the forecast error predicted for the orbit as orbit forecast information. The mega-constellation business device 41 outputs information on the orbital altitude and orbital inclination of the mega-constellation satellite group to the space information recorder 100 that includes this orbit forecast information.

[0120] The information management method of the megaconstellation business device 41 performs the following steps. The danger warning acquisition means acquires a danger warning indicating the presence of a predicted intrusion object when it is foreseeable that another space object will intrude into the orbital altitude and latitude band in which the mega-constellation satellite group exists, based on the orbital forecast information possessed by the space information recorder 100.

[0121] The information management method for the debris removal business device 45 involves the following steps. The danger warning acquisition means acquires a danger warning indicating the presence of a predicted intrusion object when it is foreseeable that another space object will intrude into the orbital altitude and latitude band in which the mega-constellation satellite group exists, based on the orbital forecast information possessed by the space information recorder 100.

[0122] ***Explanation of the effect of this embodiment*** According to the information management method of the mega constellation business device of this embodiment, the SSA business device can use the orbital forecast information of the mega constellation satellite group to appropriately predict the intrusion of space object A into the orbital area of ​​the mega constellation satellite group. The megaconstellation business device can then take appropriate evasive action based on the orbital forecast information for space object A obtained from the SSA business device.

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

[0124] ***Configuration Description*** FIG. 22 is a diagram showing an example of the configuration of a debris removal satellite 30a according to this embodiment. FIG. 23 is a diagram showing an example of the configuration of a debris removal system 400 according to this embodiment. In this embodiment, a debris removal system 400 will be described, which is composed of a debris removal satellite 30a equipped with a capture device 36 for capturing space objects and a propulsion device 33, and ground equipment 702 equipped with means for controlling the debris removal satellite 30a. The ground equipment 702 is also referred to as the ground system 72. In addition, in Figure 23, a control unit 191 is an example of means for controlling the debris removal satellite 30a. The ground facility 702 includes a space information recorder 100 that records space object information obtained from a management business device 40 that manages multiple space objects, and a server 602. The space information recorder 100 may be stored in a database 601.

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

[0126] The debris removal satellite 30a includes the components of the satellite 30 described in Figures 5 to 8, as well as a capture device 36 that captures debris. The debris removal satellite 30a captures debris in response to control commands 56 from a debris removal business device 45, and performs active orbit control operation during orbit descent to avoid areas with a high risk of collision with space objects during the deorbit process leading up to atmospheric re-entry. Active orbit control operation during orbit descent is also called active deorbit operation. The debris removal business equipment 45 may be mounted on the ground facility 702. The debris removal business equipment 45 may also be mounted on the debris removal business equipment 45, or on another device that communicates with the debris removal business equipment 45.

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

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

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

[0130] In this embodiment, the server 602 is specifically a debris removal business device. The database 601 may be provided in the server 602, or may be a device separate from the server 602. The server 602 realizes the following steps using processing circuitry such as a processor 910 or electronic circuitry. The following steps can be interpreted as functional elements, units, or means. Specifically, the database 601 may be a memory 921, an auxiliary storage device 922, or a file server. The functional configuration of the debris removal system 400 will be described below.

[0131] The server 601 receives an intrusion alert from the SSA business device 47 when it is foreseeable that a space object A, which is included in the plurality of space objects, will enter the range of orbital altitudes of 300 km to 1000 km where a constellation of satellites exists from 10:00 to 11:00 LST. The server 601 records the predicted time when space object A will enter the range and the orbital forecast information in the space information recorder 100. The server 601 controls the debris removal satellite 30a so that it approaches the space object A before the predicted time. The server 601 controls the debris removal satellite 30a to capture the space object A. The server 601 controls the debris removal satellite 30a to operate the propulsion device 33 to control both or either the orbital altitude and the orbital inclination angle, so that the space object A enters the atmosphere without passing through the range.

[0132] The server 601 receives an intrusion alert from the SSA operator when it is foreseeable that a space object A included in the plurality of space objects will intrude into an area at latitudes above 80 degrees north or 80 degrees south where a group of polar orbiting satellites is densely concentrated, and at an orbital altitude of 300 km to 1000 km. The server 601 records the predicted time when space object A will enter the range and the orbital forecast information in the space information recorder 100. The server 601 controls the debris removal satellite 30a so that it approaches the space object A before the predicted time. The server 601 controls the debris removal satellite 30a to capture the space object A. The server 601 causes the debris removal satellite 30a to operate the propulsion device 33 to change the orbital inclination angle, causing the space object A to enter the atmosphere without passing through the range.

[0133] The debris removal business device 45 captures one of the space objects flying in space before they collide with each other and changes its orbit to avoid the collision. The debris removal program of the debris removal business device 45 causes a computer to execute a process to obtain an intrusion alarm if it is foreseeable that another space object will intrude into the orbital altitude and latitude band in which the megaconstellation satellites exist.

[0134] In addition, the debris removal program of the debris removal business device 45 causes the computer to execute a process to obtain an intrusion alarm if it is foreseeable that another space object will intrude into an orbital plane or area where satellites are densely concentrated.

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

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

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

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

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

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

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

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

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

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

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

[0146] In the above first to fourth embodiments, the following business devices have been described.

[0147] The SSA business device is equipped with a space information recorder that acquires and records orbital forecast information for multiple space objects from a management business device that manages multiple space objects flying in space. When it is predicted that space object A will enter an area where a constellation of satellites is densely packed, the SSA business device will issue a danger alert to the following operators (business devices used by the operators). Specifically, the SSA business device will issue a danger alert to all or some of the operators of space object A, operators that own satellites flying in the area, megaconstellation satellite operators, debris removal operators, and space insurance operators. The SSA business device will also request collision avoidance operators to take collision avoidance action.

[0148] The space information recorder provided in the SSA business device is the space information recorder described in the above embodiment.

[0149] The SSA business device has the functions of the collision avoidance support system described in the above embodiment, or a space information recorder that executes a collision avoidance support program.

[0150] The SSA business device includes a space information recorder that executes the information management method described in the above embodiment.

[0151] The collision avoidance assistance business device is used by businesses that provide assistance in avoiding collisions between space objects. When it is predicted that space object A will enter an area where a constellation of satellites is densely packed, the collision avoidance support business device issues a danger alert to the following businesses (business devices used by businesses) and requests the collision avoidance businesses to take collision avoidance action. Specifically, the collision avoidance support business device notifies all or some of the businesses of space object A, businesses that own satellites flying in the area, megaconstellation satellite businesses, and debris removal businesses, and requests the collision avoidance businesses to take collision avoidance action.

[0152] Megaconstellation business equipment is business equipment used by megaconstellation operators who manage megaconstellation satellite groups consisting of 100 or more satellites. When the megaconstellation business device predicts that space object A will enter an area where the megaconstellation satellites are densely concentrated, it receives a danger warning and a request for collision avoidance action from the collision avoidance support business device and carries out collision avoidance action.

[0153] The debris removal business equipment is used by debris removal businesses that carry out debris removal businesses to remove debris from outer space. When it is predicted that space object A will enter an area where a constellation of satellites is densely packed, the debris removal business device receives a danger warning and a request for collision avoidance action from the collision avoidance support business device and carries out collision avoidance action.

[0154] The debris removal business device executes the functions of the debris removal system or the debris removal program described in the above embodiment.

[0155] A satellite enterprise is, for example, an enterprise that manages fewer than 10 satellites. When the satellite business device predicts that a space object A under its management will enter an area where a constellation of satellites is densely packed, it receives a danger warning and a request for collision avoidance action from the collision avoidance support business device and carries out collision avoidance action.

[0156] A constellation business device is, for example, a business device that manages a constellation consisting of 10 or more satellites. When the constellation business device predicts that a space object A under its management will enter an area where a constellation of satellites is densely packed, it receives a danger warning and a request for collision avoidance action from the collision avoidance support business device and carries out collision avoidance action.

[0157] Rocket launch business equipment is business equipment of a company that operates a rocket launch business to launch rockets. If a rocket launcher predicts that a rocket under its management will enter an area where satellites are densely packed or an altitude area where megaconstellation satellites fly, it will notify all or some of the following service devices of its flight plan and request collision avoidance. Specifically, the rocket launcher will notify all or some of the collision avoidance support service device, megaconstellation service device, or SSA service device of its flight plan and request collision avoidance.

[0158] If the business device predicts that space object A under its management will enter an area where satellites are densely packed or an altitude area where megaconstellation satellites fly during the orbital transfer process, it will notify all or some of the following business devices of its orbital transfer plan and request collision avoidance. Specifically, the business device will notify all or some of the collision avoidance support business device, megaconstellation business device, or SSA business device of its orbital transfer plan and request collision avoidance. The enterprise is a satellite enterprise or a constellation enterprise or a megaconstellation enterprise.

[0159] Embodiment 5 In this embodiment, the differences from or additions to the first to fourth embodiments will be mainly described. In this embodiment, the same components as those in the first to fourth embodiments will be denoted by the same reference numerals, and the description thereof will be omitted.

[0160] In this embodiment, an open architecture data repository that discloses orbital information of cosmic objects will be described. Hereinafter, the open architecture data repository may be referred to as OADR800. OADR is an abbreviation for Open Architecture Data Repository. Hereinafter, a specific example of OADR800 will be described.

[0161] <Specific Example 1 of OADR800> OADR800 includes the above-described cosmic information recorder 100. OADR800 includes the cosmic information recorder 100 as a public database. By OADR800 including the cosmic information recorder 100, information sharing among operators becomes possible, and there is an effect that it can contribute to risk avoidance.

[0162] <Specific Example 2 of OADR800> OADR800 may include the above-described collision avoidance support system 200. Specific Example 2 is a form in which the collision avoidance support system 200 is included as an implementation form of OADR800 and mainly contributes to collision avoidance. Note that OADR800 may include business devices such as SSA business devices or debris removal business devices that contribute to grasping the cosmic situation.

[0163] When OADR800 is developed as a public institution, it is possible to perform risk analysis and evaluation analysis including confidential information, process orbital information into a publicly available state, and disclose conditional information. Therefore, it can effectively contribute to ensuring the flight safety of the universe.

[0164] <Specific Example 3 of OADR800> OADR800 may constitute the above-described collision avoidance support system 200. Specific Example 3 is a form in which OADR800 is developed as a component of the collision avoidance support system 200. It has the same effect as Specific Example 2.

[0165] <Specific Example 4 of OADR800> OADR800 shares information with all or part of the SSA business device 47, the megaconstellation business device 41, and the debris removal business device 45, and requests the implementation of the above-described information management method.

[0166] <Specific Example 5 of OADR800> FIG. 26 is a diagram showing an example of OADR800 according to the present embodiment. OADR800 includes a database 801 for storing orbit information of space objects and a space information management server (hereinafter referred to as server 802). The database 801 includes a first database 81 for storing non-public information and a second database 82 for storing public information. The server 802 performs a risk analysis by referring to the first database 81 and the second database 82, and discriminatively manages the free public information and the paid public information in the second database 82. Specifically, the server 802 includes a control unit 83 as a functional element, and the functions of the server 802 are realized by the control unit 83.

[0167] Among space objects, there are space objects whose orbit information is non-public due to security requirements. On the other hand, when performing a risk analysis such as approach or collision, it is necessary to perform the risk analysis including non-public information. Therefore, it is reasonable to separate the databases to avoid the risk of information leakage. In addition, there may be a mixture of free public information and paid public information among the public information, and it is necessary to perform discriminative management when publicly releasing information by OADR. By OADR separating non-public data from public data in a unified manner and then discriminatively managing the paid / free nature of the public information, it is possible to achieve appropriate information management in accordance with the need-to-know principle.

[0168] <Specific Example 6 of OADR800> In Specific Example 6, the server 802 performs a risk analysis by referring to the first database 81 and the second database 82, and discriminatively manages the unconditional public information and the conditional public information in the second database 82.

[0169] When a specific country develops OADR as a public institution, it is reasonable to unconditionally disclose information to the operators in that country and disclose information to other operators on a conditional basis. As conditions, monetization, price setting, disclosure item restrictions, disclosure information accuracy restrictions, disclosure frequency restrictions, non-disclosure to specific operators, etc. can be set.

[0170] <Specific Example 7 of OADR800> OADR800 includes the above-mentioned collision avoidance support business device. OADR800 discloses space information to all or part of the satellite business device 43, the LEO constellation business device 42 (constellation business device), the mega constellation business device 41, the rocket launch business device 46, the debris removal business device 45, and the SSA business device 47. OADR800 may apply Specific Example 7 to other business devices as needed.

[0171] <Specific Example 8 of OADR800> OADR800 discloses space information to all or part of the satellite business device 43, the LEO constellation business device 42 (constellation business device), the mega constellation business device 41, the rocket launch business device 46, the debris removal business device 45, the SSA business device 47, the collision avoidance support business device, and the space insurance business device 48 which is a business device used by space insurance operators, and instructs or requests or mediates the above-mentioned collision avoidance actions. The space insurance business device 48 is a business device used by the above-mentioned space insurance operators. OADR800 may apply Specific Example 8 to other business devices as needed.

[0172] <Specific Example 9 of OADR800>[ Figure 27 is a diagram showing another example of OADR800 according to the present embodiment. [[ID=X]] OADR800 includes the above-mentioned space information recorder 100 and the server 802. The space information recorder 100 comprises a first database 81 for storing public information and a second database 82 for storing private information. The server 802 acquires space object information, including non-disclosed information, from all or some of the business devices provided in the CSpOC, namely, the space traffic management device 49, the SSA business device 47, the collision avoidance support business device, the megaconstellation business device 41, and the debris removal business device 45, and stores the information in the second database 82. The server 802 also generates conditional disclosure information that limits the targets and contents of disclosure and stores the information in the first database 81. The server 802 then transmits the conditional disclosure information only to specific business devices among the SSA business device 47, the collision avoidance support business device, the megaconstellation business device 41, the debris removal business device 45, and the space insurance business device 48. The OADR 800 may apply Example 9 to other business devices as needed.

[0173] A space traffic control system is a device that continuously monitors space objects and manages space traffic. For example, the US CSpOC continuously monitors space objects and issues a warning if it predicts that two space objects may approach or collide with each other.

[0174] Confidential information on space objects held by CSpOC that contributes to national security may be disclosed only to OADR, but the risk of approach and collision must be analyzed and predicted, including confidential information. After processing the information into one that can be made conditionally public, the conditionally public information that contributes to collision avoidance support can be shared only with business devices related to collision risk, enabling private businesses to take action to avoid collisions. In addition, for space object information held by private businesses that cannot be made public, OADR can similarly process it into conditionally publicly available information, making it possible to avoid collisions.

[0175] The functions and effects of the OADR 800 according to this embodiment will be further described below.

[0176] Studies are underway to establish a public information system called OADR for orbital information on space objects, allowing businesses to share information and ensure the safety of space object flights. If OADR is established as a public institution for international cooperation, it may be given the authority to give instructions or requests to businesses across borders. For example, in order to centrally manage orbital information on space objects held by operators around the world, it would be reasonable to instruct or request OADR to provide orbital information under rules based on international agreements.

[0177] If a particular country establishes an OADR as a public institution, it may be granted the authority to issue instructions or requests to businesses in that country. On the other hand, it is possible that the system will be such that information is disclosed unconditionally to businesses in the country in question, and conditionally to businesses in other countries. Disclosure conditions can include charging a fee, setting a price, limiting the items to be disclosed, limiting the accuracy of the information to be disclosed, limiting the frequency of disclosure, and not disclosing to specific businesses. For example, there may be differences between the country in question and other countries in terms of whether information is provided free of charge or for a fee, or in the amount of compensation paid for obtaining the information. The conditions for disclosure set by OADR will have an impact on the creation of space traffic management systems and industrial competitiveness.

[0178] It would be reasonable for classified information on space objects that contributes to national security to be kept confidential from the public, even though it would be maintained by the OADR, which is a public institution run by the government. For this reason, the OADR may have a database for storing confidential information in addition to a database for disclosing information. Furthermore, among the space object information held by private businesses, there is information that cannot be made public due to trade secrets or other reasons, and information that is subject to constant maneuvering control and is therefore not appropriate to be made public in terms of the amount of information or frequency of updates.

[0179] When analyzing and assessing the risk of approach and collision of space objects, it is necessary to consider the orbital information of all space objects, regardless of whether the space objects are confidential or not. For this reason, it is reasonable for OADR, as a public institution, to conduct risk analysis, including confidential information, and to make the results of its analysis and evaluation conditionally public, as follows: For example, if OADR predicts a risk, it will process the information into one that can be made public, and then make conditional disclosure by placing restrictions on the subjects or content of disclosure, such as disclosing only trajectory information during dangerous time periods to those who will contribute to risk avoidance.

[0180] If the number of orbital objects increases in the future, and the risk of approach and collision increases, various risk avoidance measures will be necessary, such as means for debris removal operators to remove dangerous debris, and means for megaconstellation operators to avoid collisions by changing their orbital positions or passing timing. If OADR, a public organization, could instruct or request operators to take risk avoidance actions, it could be expected to have a tremendous effect on ensuring the safety of space flights. In cases where a space object managed by an emerging country, venture business, university, or other entity with little experience in space business and little information useful for risk avoidance is predicted to enter the orbital altitude range where a mega-constellation flies, OADR will act as an intermediary and transmit information to the necessary entity, enabling quick and effective risk avoidance.

[0181] Furthermore, by implementing risk avoidance measures and introducing space insurance to private businesses, we can also contribute to the promotion and industrialization of space traffic management. OADR can be realized in a variety of ways, including having only a public database, possessing risk analysis means, collision avoidance support means, or SSA means and actively contributing to risk avoidance, or by giving instructions, requests, mediation, or introductions to businesses and contributing to risk avoidance through information management.

[0182] When an SSA operator conducts a collision prediction analysis of debris and determines that there is a risk of approach or collision with a satellite that makes up a megaconstellation, it is reasonable to decide on evasive action as follows: Unlike approach / collision warnings for individual satellites as with normal satellites, an intrusion warning is issued to the megaconstellation operator as a forecast of the passage of the orbital altitude that makes up the megaconstellation, and the megaconstellation operator then identifies the satellite in question and decides on evasive action. Similarly, for warnings of densely populated areas such as dense orbital planes or polar regions, it would be reasonable to issue an intrusion warning for the densely populated area and create a system that includes outsourcing response actions to debris removal companies.In the above-mentioned embodiment, we have described a space information recorder and OADR that are equipped with a means for an SSA company to issue a warning when debris enters a specific altitude or densely populated area.

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

[0184] Furthermore, it is possible to combine two or more parts of the first to fifth embodiments. Alternatively, it is possible to implement only one part of these embodiments. In addition, it is possible to implement any combination of these embodiments, either as a whole or in part. That is, in the first to fifth embodiments, the parts of the first to fifth embodiments can be freely combined, or any of the components can be modified, or any of the components in the first to fifth embodiments can be omitted.

[0185] It should be noted that the above-described embodiments are essentially preferred examples and are not intended to limit the scope of the present disclosure, the scope of application of the present disclosure, and the scope of use of the present disclosure. The above-described embodiments can be modified in various ways as necessary. [Explanation of symbols]

[0186] 20 Satellite constellation, 21 Orbital plane, 30 Satellite, 30a Debris removal satellite, 31 Satellite control device, 32 Satellite communication device, 33 Propulsion device, 34 Attitude control device, 35 Power supply device, 36 Capture device, 40 Management business device, 41 Mega constellation business device, 42 LEO constellation business device, 43 Satellite business device, 44 Orbital transfer business device, 45 Debris removal business device, 46 Rocket launch business device, 47 SSA business device, 51 Orbital forecast information, 52 Satellite orbit forecast information, 53 Debris orbit forecast information, 200 Collision avoidance support system, 210 Notification reception unit, 220 Danger notification unit, 230 Collision avoidance selection unit, 240 Danger warning output unit, 400 Debris removal system, 501 Approach warning, 502 Collision warning, 511 Space object ID, 512 Forecast origin, 513 Forecast orbital elements, 514 Forecast error, 60 Space object, 61 Public orbital information, 70 Earth, 100 Space information recorder, 110 Determination unit, 111, 503, 504, 505 Intrusion alarm, 120 Issuance unit, 140 Memory unit, 191 Control unit, 55 Orbital control command, 56 Control command, 57 Capture command, 301 Satellite orbital region, 500 Space object information, 600 Satellite constellation formation system, 11, 11b Satellite constellation formation unit, 300 Satellite group, 700, 701, 702 Ground equipment, 510 Orbital control command generation unit, 520 Analysis and prediction unit, 909 Electronic circuit, 910 Processor, 921 Memory, 922 Auxiliary storage device, 930 Input interface, 940 Output interface, 941 Display device, 950 Communication device, 800 OADR, 801 database, 802 server, 81 first database, 82 second database, 83 control unit, 48 space insurance business device, 49 space traffic management device.

Claims

1. A collision avoidance support system that acquires space object information from a space information recorder that records space object information acquired from a management business device used by a management business that manages multiple space objects, and supports collision avoidance between the multiple space objects, a server including a database for storing the space object information acquired from the space information recorder and a determination means for determining a collision avoidance operator; Equipped with The server receiving a notification from a space information recorder that a space object A included in the plurality of space objects is predicted to enter an orbital altitude range of 300 km to 1000 km, in which a constellation of satellites exists between 10:00 and 11:00 LST (Local Sun Time); A step of acquiring a time period from when the space object A enters the range until when it leaves the range and orbital forecast information from a space information recorder; A step of notifying a danger alert for the time period to all or some of the operators of the space object A, satellite operators who own satellites flying in the range, and debris removal operators; selecting a candidate collision avoidance operator; A stage where collision avoidance operators are requested to take collision avoidance action. A collision avoidance assistance system.

2. A collision avoidance support system that acquires space object information from a space information recorder that records space object information acquired from a management business device used by a management business that manages multiple space objects, and supports collision avoidance between the multiple space objects, a server including a database for storing the space object information acquired from the space information recorder and a determination means for determining a collision avoidance operator; Equipped with The server receiving a notification from a space information recorder that a space object A included in the plurality of space objects is predicted to intrude into an area at an orbital altitude of 300 km to 1000 km at a latitude of 80 degrees north or 80 degrees south or higher where polar orbit satellites are densely concentrated; a step of acquiring a time period from when the space object A enters the range until when it leaves the range and orbital forecast information from a space information recorder; A step of notifying a danger alert for the time period to all or some of the operators of the space object A, satellite operators who own satellites flying in the range, and debris removal operators; selecting a candidate collision avoidance operator; A stage where collision avoidance operators are requested to take collision avoidance action. A collision avoidance assistance system.

3. A collision avoidance support system that acquires space object information from a space information recorder that records space object information acquired from a management business device used by a management business operator that manages multiple space objects, and supports collision avoidance between the multiple space objects, a server including a database for storing space object information acquired from the space information recorder and a determination means for determining a collision avoidance operator; Equipped with The server receiving a notification from a space information recorder that a space object A included in the plurality of space objects is predicted to intrude into an orbital altitude and latitude range in which a group of satellites constituting a mega-constellation consisting of 100 or more satellites exists; a step of acquiring a time period from when the space object A enters the range until when it leaves the range and orbital forecast information from a space information recorder; a step of notifying a danger alert for the time period to all or some of the operators of the space object A, the megaconstellation operators, and the debris removal operators; selecting a candidate collision avoidance operator; A stage where collision avoidance operators are requested to take collision avoidance action. A collision avoidance assistance system.

4. The determination means selects a management company of the space object A equipped with a collision avoidance function, The server:

3. The collision avoidance support system according to claim 1, further comprising a step of requesting the management company of the space object A to take intrusion avoidance action by changing the time period or orbit of the space object A to intrude.

5. The decision means selects a debris removal operator, The server:

3. The collision avoidance support system according to claim 1 or claim 2, further comprising a step of requesting the debris removal company to take intrusion avoidance action by capturing space object A and changing the time period or orbit of the intrusion into the range.

6. The determining means selects a mega-constellation operator; The server:

4. A collision avoidance support system according to claim 3, further comprising a step of requesting a megaconstellation operator to take action to avoid a collision between a group of satellites constituting the megaconstellation and the space object A.

7. 1. An open architecture data repository that publishes orbital information for space objects, comprising: An open architecture data repository comprising a collision avoidance assistance system according to any one of claims 1 to 6.

8. 1. An open architecture data repository that publishes orbital information for space objects, comprising: An open architecture data repository constituting the collision avoidance assistance system according to any one of claims 1 to 6.

Images