Navigation assistance system

The navigation support system addresses the lack of transparency in compliance with maritime rules by using rule estimation logic and data acquisition units to ensure safe and legal automated navigation, enhancing safety and compliance with COLREG.

WO2024248067A1PCT designated stage expired Publication Date: 2024-12-05MITSUI O S K LINES LTD
View PDF 10 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/019807
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-30
Filing Date
2024-05-30
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Current navigation systems fail to clearly present compliance with maritime rules, such as COLREG, and lack transparency in decision-making processes, leading to potential safety and legal issues in automated navigation systems.

Method used

A navigation support system that includes a rule estimation logic storage unit, own ship data acquisition, target data acquisition, and surrounding data acquisition units, generating situation recognition data to determine relative relationships and apply relevant rules, ensuring compliance with COLREG and other maritime regulations.

Benefits of technology

The system provides clear operations that comply with maritime rules, enhancing safety and legal compliance by transparently applying COLREG and other maritime regulations, improving the reliability of automated navigation decisions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024019807_05122024_PF_FP_ABST
    Figure JP2024019807_05122024_PF_FP_ABST
Patent Text Reader

Abstract

A navigation assistance system (1) has stored therein rule estimation logic for estimating an application relationship of a rule with respect to ship operation, and host ship setting data including a parameter that indicates a characteristic of a host ship. The navigation assistance system (1): acquires host ship data indicating information relating to the state of the host ship; acquires target data indicating information relating to the state of a target; acquires surroundings data indicating information relating to a situation in the surroundings of the host ship; generates, on the basis of the host ship data, the target data, and the surroundings data, situation recognition data indicating a situation for determining an operation of the host ship; identifies a relative relationship between the host ship and the target on the basis of the situation recognition data; and estimates an application rule to be applied to the host ship on the basis of the identified relative relationship and the host ship setting data in accordance with the rule estimation logic.
Need to check novelty before this filing date? Find Prior Art

Description

Navigation Support System

[0001] The present invention relates to a navigation support system that supports navigation.

[0002] In recent years, there has been a growing expectation for the realization of automated navigation to alleviate crew shortages and reduce workloads. Support technologies such as the Integrated Navigation System (INS), which integrates functions such as the Electronic Chart Display and Information System (ECDIS), Automatic Radar Plotting Aids (ARPA), and track control, have been introduced. However, most navigational watchkeeping tasks are still performed by crew members, and in order to realize automated navigation, it is necessary to automate these tasks.

[0003] Even if a device is technically feasible, it is difficult to install it if it lacks economic rationality, and the range of use is limited if it is not reliable enough. Furthermore, there are rules governing ship operation, such as treaties such as the Convention on the International Regulations for Preventing Collisions at Sea (COLREG) and the International Convention on Standards of Training, Certification and Watchkeeping for Seafarers (STCW), as well as domestic laws such as the Act on Preventing Collisions at Sea, Maritime Traffic Safety Act, Port Regulations Act, and Seafarers Act. Using devices that use technology that does not comply with these rules poses significant risks from the perspectives of safety and compliance.

[0004] In addition, the scope of application of rules applied to ship operations varies depending on the water area and topography, and some also vary depending on visibility based on weather and sea conditions. When proposing an avoidance route, it is necessary to determine the scope of application of rules based on these surrounding conditions. Furthermore, to determine the scope of application of rules, it is necessary to consider not only the relative positions of one's ship and other ships, but also the surrounding conditions.

[0005] However, various conventional technologies that suggest avoidance routes (see, for example, Patent Documents 1 to 6) do not present to the user the status of compliance with rules and the basis for judgment, and do not take into account differences in the rules that are applied depending on the surrounding circumstances.

[0006] Furthermore, many of the avoidance routes based on path planning to avoid obstacles using robotics technology do not comply with the rules set out in COLREG. Some of these avoidance routes may be acceptable according to COLREG, but may differ significantly from the sense of human navigation, or may pose safety issues in terms of the ship's own maneuvering performance and response to the movements of other ships, and may therefore be considered to not comply with the rules for safe ship operation.

[0007] Furthermore, the use of artificial intelligence (AI) for decision-making from target detection to avoidance is also being considered, but the fact that the decision-making process and rationale are a black box and unclear is problematic from the perspective of accountability.

[0008] Japanese Patent No. 6535896 Japanese Patent No. 7069371 Japanese Patent No. 7080320 Japanese Patent Application Laid-Open No. 2021-146778 Japanese Patent Application Laid-Open No. 2021-160550 Japanese Patent Application Laid-Open No. 2023-13071

[0009] An object of the present invention is to provide a navigation support system that can clarify operations that comply with various rules that apply to ship operation and the basis for those decisions.

[0010] A navigation support system according to an aspect of the present invention includes a rule estimation logic memory unit storing rule estimation logic for estimating the application of rules to the operation of a ship, an own ship setting data memory unit storing own ship setting data including parameters indicating the characteristics of the own ship, an own ship data acquisition unit acquiring own ship data indicating information about the state of the own ship, a target data acquisition unit acquiring target data indicating information about the state of a target, an ambient data acquisition unit acquiring ambient data indicating information about the situation around the own ship, and a storage unit for storing the own ship data acquired by the own ship data acquisition unit, the target data acquired by the target data acquisition unit, and the ambient data acquisition unit for storing the own ship data acquired by the own ship data acquisition unit and the ambient data acquired by the target data acquisition unit. The system includes a situation awareness data generation unit that generates situation awareness data indicating a situation for determining the operation of the ship based on target data and the surrounding data acquired by the surrounding data acquisition unit, a relative relationship identification unit that identifies the relative relationship between the ship and the target based on the situation awareness data generated by the situation awareness data generation unit, and a rule estimation unit that estimates an applicable rule to be applied to the ship based on the relative relationship identified by the relative relationship identification unit and the ship setting data stored in the ship setting data storage unit in accordance with the rule estimation logic stored in the rule estimation logic memory unit.

[0011] FIG. 1 is a schematic diagram illustrating the application of COLREG according to an embodiment of the present invention. FIG. 2 is a schematic diagram illustrating the application of rules based on the courses and speeds of the own ship and other ships according to this embodiment. FIG. 3 is a schematic diagram illustrating the relative relationship between the own ship and other ships, the action stage, and the action relationship according to this embodiment. FIG. 4 is a conceptual diagram illustrating the data structure of a preset scenario according to this embodiment. FIG. 5 is a structural diagram illustrating a configuration for converting an avoidance action into a machine-readable description according to this embodiment. FIG. 6 is a conceptual diagram illustrating the conversion from practical description data to machine-readable description data according to this embodiment. FIG. 7 is a conceptual diagram illustrating an overtaking scenario during a green phase according to this embodiment. FIG. 8 is a conceptual diagram illustrating an overtaking scenario during a yellow phase according to this embodiment. FIG. 9 is a conceptual diagram illustrating a meeting scenario during a green phase according to this embodiment. FIG. 10 is a conceptual diagram illustrating a meeting scenario during a yellow phase according to this embodiment. FIG. 11 is a conceptual diagram illustrating a crossing scenario from the right during a green phase according to this embodiment. FIG. 12 is a conceptual diagram illustrating a crossing scenario from the left during a yellow phase according to this embodiment. FIG. 13 is a conceptual diagram showing a scenario in which a ship is overtaken from the left during a yellow phase according to this embodiment. FIG. 14 is a conceptual diagram showing a scenario in which a ship is overtaken from the right during a yellow phase according to this embodiment. FIG. 15 is a conceptual diagram showing a scenario in which multiple targets are involved according to this embodiment. FIG. 16 is a conceptual diagram showing a scenario in which multiple targets, including targets not included in the calculation according to this embodiment. FIG. 17 is a configuration diagram showing the configuration of a navigation support system according to this embodiment. FIG. 18 is a configuration diagram showing the data configuration of a data storage unit according to this embodiment. FIG. 19 is an image diagram of a first screen for user settings displayed on a user terminal according to this embodiment. FIG. 20 is an image diagram of a second screen for user settings displayed on a user terminal according to this embodiment. FIG. 21 is a diagram showing example items in an integrated target list according to this embodiment. FIG. 22 is a conceptual diagram showing a state related to own ship operation according to this embodiment. FIG. 23 is a flowchart for determining a rule based on water area in the applicable rules according to this embodiment. FIG. 24 is a flowchart for determining a rule based on visibility in the applicable rules according to this embodiment.FIG. 25 is a flowchart for determining a rule based on positional relationships in the applicable rules according to this embodiment. FIG. 26 is a flowchart for determining a rule based on the state of other ships in the applicable rules according to this embodiment. FIG. 27 is a flowchart for determining a rule based on retained ships in the applicable rules according to this embodiment. FIG. 28 is a flowchart for determining an operation stage according to this embodiment. FIG. 29 is a flowchart for determining operation timing according to this embodiment. FIG. 30 is a flowchart for processing to determine an operation according to this embodiment. FIG. 31 is a flowchart showing in detail a portion of processing to determine an operation according to this embodiment. FIG. 32 is a state transition diagram showing state transitions of the collision avoidance execution unit according to this embodiment. FIG. 33 is a configuration diagram showing the configuration of a switch panel according to this embodiment. FIG. 34 is a flowchart for processing by the operation execution unit according to this embodiment. FIG. 35 is a flowchart for processing to confirm the operation of other ships according to this embodiment. FIG. 36 is a flowchart for processing to confirm the navigation of other ships according to this embodiment. FIG. 37 is a schematic diagram showing a method for calculating numerical values ​​used for determination according to this embodiment. FIG. 38 is an image diagram of a screen of a user terminal that displays the status of the watchkeeping execution unit according to this embodiment. FIG. 39 is a schematic diagram showing a case in which the navigation support system according to this embodiment is applied.

[0012] (Embodiment) First, referring to Figure 1, a description will be given of the situations in which the COLREG Convention is applied. Note that while the clause numbers and provisions of domestic laws corresponding to COLREG may not be identical to those of COLREG, the following explanation will use the clauses of COLREG. Furthermore, unless otherwise specified, parameters displayed on navigational instruments will use existing standard names and abbreviations. The relationship between one's own ship and another ship within each other's line of sight depends on the visible distance. The visible distance is determined by the eye height (height of the bridge) of each ship.

[0013] COLREG distinguishes between "Conduct of vessels in sight of one another" and "Conduct of vessels in restricted visibility," so it is necessary to determine whether the vessels are in sight of one another or in restricted visibility. COLREG also contains special provisions for narrow channels (Rule 9) and traffic separation systems (Rule 10), as well as other special provisions applicable in other situations.

[0014] Regarding lookouts, the regulation states that "vessels shall at all times maintain a proper lookout by sight, hearing and all other means appropriate to the circumstances, so as to enable them to fully assess their surroundings and the risk of collision with other vessels" (Rule 5). In automated navigation, it is assumed that image data acquired by a camera will be used as a substitute for sight, and audio data acquired by a microphone will be used as a substitute for hearing to understand the situation. The use of onboard navigational equipment such as radar, Automatic Identification System (AIS), and VHF radio falls under the category of "all other means."

[0015] Regarding safe speed, the regulations stipulate that consideration must be given to visibility, the state of vessel traffic congestion, the ship's stopping distance, turning and other maneuvering capabilities, the presence of lights from shore at night, the presence of lights from reflections of the ship's own lights, the state of the wind, the state of the sea surface and ocean currents, the state of proximity to obstacles to navigation, and the relationship between the ship's draft and water depth.In the case of using radar, consideration must also be given to the characteristics, performance and detection limits of the ship's radar, the impact of sea conditions, weather and other sources of interference on radar detection, the number of ships detected by radar, as well as their positions and movements, etc. (Rule 6).

[0016] In COLREG, the targets of collision avoidance actions are other ships, and targets other than ships, such as navigational aids, fishing gear, floating objects, and offshore structures, as well as shallow waters, reefs, coastlines, and sunken ships, which may become obstacles to one's own ship, are positioned as targets requiring attention in terms of safe speed and lookout.

[0017] Visibility conditions vary greatly due to the strong influence of weather and sea conditions. Even within a theoretically visible distance, visibility varies due to atmospheric conditions such as fog, dust, snowfall, and rainfall, as well as the time of day, twilight, and night. To detect other ships and recognize targets and more specifically predict their movements while continuing systematic observation and target movement prediction, the distance between the ship and the target becomes shorter. Sensors used for image recognition, etc., are configured to continuously recognize multiple targets without recognizing different targets as the same target. Furthermore, the process of integrating information from multiple sensors is performed while maintaining the integrity of each sensor and ensuring continuity and identity of tracking without integrating different targets.

[0018] COLREG stipulates that "A vessel shall use all means appropriate to the circumstances to determine whether there is a risk of collision with another vessel" (Rule 7). This requires the use of all means appropriate to the circumstances, regardless of the visibility distance. In other words, similar to Rule 5, not only visual observation and compass direction but also the use of radar, AIS, VHF, etc. is required. COLREG also stipulates that "A vessel shall not determine whether there is a risk of collision with another vessel based on insufficient radar information or other insufficient information" and "A vessel shall determine that there is a risk of collision with another vessel if it is unable to ascertain whether there is a risk of collision with that vessel" (Rule 7). The navigation support system 1 according to this embodiment has a function to detect the input of insufficient information and predict a decrease in the reliability of the information.

[0019] Regarding actions to avoid collision, the Act stipulates that "When a vessel takes action to avoid collision with another vessel, she shall, whenever possible, take such action without hesitation, in good time and in accordance with good maritime practice," and "When a vessel takes action to avoid collision with another vessel, she shall take such action in such a way as to enable her to pass at a safe distance from the other vessel" (Rule 8).As an exception in the event of an emergency, the Act stipulates that "When a vessel is in a special situation where there is an imminent danger as described in the preceding paragraph, she may exempt herself from the provisions of this Act in order to avoid the imminent danger" (Rule 2).

[0020] As described above, COLREG is defined assuming that there are multiple phases regarding actions to avoid collisions. Therefore, in this embodiment, the phase regarding the application of COLREG is referred to as the "COLREG phase." Furthermore, the phase in which the COLREG rules are applied is indicated by color to facilitate intuitive understanding. For example, the phase from detection to action with sufficient margin is indicated as "blue," the phase from action with sufficient margin to application of navigation rules to the vessel is indicated as "green," the phase from application of rules to the vessel up to the distance at which the vessel can pass while maintaining a safe passing distance from the vessel is indicated as "yellow," the phase from the safe passing distance to the occurrence of imminent danger is indicated as "red," and the phase at which imminent danger occurs is indicated as "black." In the drawings, colors are indicated in parentheses, but when displayed on various screens, etc. according to the embodiment, the colors are used. Although FIG. 1 defines phases in terms of the distance from the vessel to the other vessel for ease of understanding, phases may also be defined by time.

[0021] In this embodiment, three levels of "action timing" are set as indicators for determining the timing to start an action to avoid a collision: "too early," "available," and "too late." It is considered preferable to start an action as early as possible, but if the action of the other ship is started too early, it is not possible to predict the action of the other ship. Therefore, the stage at which there is a high possibility that the other ship will change course is set as "too early."

[0022] During navigation, a ship may need to take action to avoid collisions with multiple other ships. On the other hand, COLREG is generally applied to a one-to-one relationship. Therefore, in this embodiment, four "action stages" are defined to manage actions to be taken for each other ship: "No action required," "Pay attention," "In action," and "Cleared." The relationship between "No action required" and "Pay attention" does not change linearly based on distance and time, but can change from moment to moment depending on changes in the course and speed of the ship and other ships.

[0023] The COLREG phase, operation timing, and operation stage are states based on the relative relationship between the ship and the target, and are part of the factors that determine the application of the rules defined in COLREG.

[0024] The navigational device ECDIS has a target list function that displays target data acquired as navigational device data in list format. The ECDIS may be an existing device. The COLREG phase, operation timing, and operation stage are systematically observed using an integrated target list. The integrated target list is a list that manages integrated target data in which additional information indicating rule application decision factors is integrated into target data. The rule application decision factors are determined based on the relative relationship between the own ship and the target acquired from the navigational device.

[0025] Referring to Figure 2, the applicable rule that is estimated based on the relative relationship between the ship and the target and applied to the ship itself, i.e., the application of the rule based on the course and speed of the ship and other ships, will be described. In ship navigation, absolute heading is basically used. Absolute heading is measured clockwise from north, which is set as 0°. In this embodiment, the navigation method defined by COLREG is determined based on the relationship between the relative bearing (R.BRG: Relative Bearing) of other ships when the ship's heading is set as 0°, and the target aspect (TA: Target Aspect), which is the relative bearing from other ships to the ship itself. Because ships can have an overall length of several hundred meters or more, a consistent common reference point (CCRP) is used in navigation equipment.

[0026] CORLEG stipulates that "A vessel overtaking another vessel from a position more than 22 degrees 30 minutes behind the beam of that vessel (or, at night, from a position from which none of the vessel's side lights as defined in Article 21, paragraph 2 can be seen) is an overtaking vessel" (Rule 13). Furthermore, as a standard for the application of navigation, numerical standards for relative bearing are established, and in order to ensure their effectiveness, provisions are also made specifying the angle and color of illumination for each of the lights: "mast light," "side light," and "stern light" (Rule 21).

[0027] Regarding sidelights, it is stipulated that "a red light is a light mounted on the port side so that its beam illuminates an area from the aft direction to 22 degrees 30 minutes behind the port side beam, and a green light is mounted on the starboard side so that its beam illuminates an area from the aft direction to 22 degrees 30 minutes behind the starboard side beam," and that a sternlight is a "white light that illuminates a horizontal arc of 135 degrees, and is mounted so that its beam illuminates an area from the aft direction to 67 degrees 30 minutes on each side" (Rule 21). This allows mariners to grasp the relative relationship to other ships and target aspect at night based on the color and position of the light.

[0028] On the other hand, human senses recognize and share direction not only as an absolute direction but also as a direction zone and a point (point: 11.25°, which is 32 equal parts of 360°). In this embodiment, the heading of the ship is set to 0°, 0±x° is "right ahead" and 0+x° to 90° is "starboard ahead" ( <s>FWD), 90° to "starboard beam" ( <s>Abeam), 90° to 112.5° is the "starboard quarter" ( <s>Quarter), 112.5° to 180° is "starboard aft" ( <s>AFT), 180° is "right astern", 180° to 247.5° is "port aft" ( AFT), 247.5° to 270° is "port quarter" ( Quarter), 270° is "port side beam" ( Abeam), 270° to (0-x)° is "forward port side" ( The definition of "FWD" is based on the ±x° range from the forward bow. The reason for the ±x° range is that the criteria for "passing vessels" that apply to "when two power-driven vessels meet head-on or nearly head-on" are qualitatively defined as "when the other power-driven vessel is visible head-on or nearly head-on" (Rule 14), and there are also various criteria for determining this range. On the other hand, the rule stipulates that "sidelights must have a minimum luminous intensity or greater when viewed head-on, and their light must be blocked within a range of 1 to 3 degrees outward from the head-on" (Annex I 9.(a)(i)), and the residual light extends a maximum of 3 degrees to the opposite side. For this reason, in this embodiment, x° is set to 3°.

[0029] COLREG categorizes the navigation rules for vessels within the line of sight of each other into Rule 13 "Overtaking vessel" (Rule 13), Rule 14 "Head-on situation" (Rule 14), and Rule 15 "Crossing situation" (Rule 15), and prescribes the actions each vessel should take. Figure 2 shows the general correspondence between navigation rules and headings.

[0030] For example, Rule 15 of "Crossing Vessels" states, "When two power-driven vessels are crossing each other's paths and there is a risk of collision, the power-driven vessel which sees the other power-driven vessel on its starboard side shall keep out of the way of the other power-driven vessel. In this case, the power-driven vessel which must keep out of the way of the other power-driven vessel shall not cross in front of the bow of the other power-driven vessel unless it is unavoidable." In this way, COLREG qualitatively prescribes the actions each vessel must take. Each vessel can determine the application of the rules based on the angle at which the lights are visible.

[0031] More specifically, as shown in Figure 3, if another ship is located between 0° and 112.5° from your ship, your ship is showing its green light to the other ship. If the target aspect, which is your ship's relative bearing as seen from the other ship, is between 247.5° and 357°, the other ship is showing its red light to your ship. Based on this positional relationship, your ship can determine the condition that the other ship is "seen on the starboard side."

[0032] In the case of "overtaking vessels" (Rule 13), if another vessel is ahead of your vessel and is traveling at a faster speed than your vessel, you will not be able to catch up and therefore do not need to take action to avoid the other vessel, and if another vessel is behind your vessel and traveling at a slower speed than your vessel, you will not be able to catch up and therefore are not bound by the obligation to act by stand-on vessel. Therefore, the applicable rules are determined taking into account relative speeds.

[0033] Generally, the risk of collision is determined by the "closest point of approach" (CPA) displayed on the Automatic Radar Plotting Aids (ARPA), which are required to be installed on certain vessels. The CPA is calculated as the distance from your vessel to the point where a line extending the relative vector between your vessel and another vessel intersects with a circle centered on your vessel. The time it takes for another vessel to reach the CPA is called the "time to the closest point of approach" (TCPA). The distance to the point where the relative vector intersects with your vessel's heading is called the "bow crossing range" (BCR). The time it takes for another vessel to reach the BCR is called the "bow crossing time" (BCT). In practice, these values ​​are used to determine the risk of collision and whether or not action is required to ensure the vessel's required safe passing distance.

[0034] The relative relationship, operational stages, and operational relationships between the ship 31 and the other ship 32 will be described with reference to Figure 3. Figure 3 virtually illustrates the relationship between the position and relative orientation of the other ship 32 and the operational stages, and shows an example of a case where avoidance of a crossing ship on the starboard side is performed by changing course alone. In actual operation, in waters where the main engine is navigating as a ring-up engine, changing course alone is the main means of avoidance operation.

[0035] The navigation support system 1 according to this embodiment sets a plurality of check points (CPs) for checking the validity of a collision avoidance operation, and checks whether or not the pre-set requirements are met.

[0036] Check point CP1 is the starting point of the operation, and the ship 31's heading is turned toward the target. Check point CP2 is the point where the ship's heading (HDG) exceeds the true bearing of the other ship 32 to be avoided and is on a course that ensures the set CPA and BCR, i.e., the ship will be clear if it continues on this path. This is the point where the alternating course angle θ from the original course line is the largest. From check point CP2 onward, the ship 31 begins an operation called "follow the target stern" while maintaining the set CPA in order to minimize deviation from the original course while maintaining a safe passing distance. At this time, the ship 31 must maneuver in a way that does not cause the other ship 32 to feel uneasy. In any operation, clear actions must be taken to avoid arousing suspicion in the other ship 32 or leading to the possibility of a collision. Checkpoint CP3 is the point at which the operation to return to the original course begins, and is the point at which the original course and HDG (or course over ground (COG)) become parallel. The magnitude of the operation after checkpoint CP3 varies depending on the surrounding conditions. In the case of oceanic voyages, there is no need to immediately return to the original course; once the course of the ship 31 and the original course become parallel, there will be no deviation from the original course, and from this point onwards the ship 31 will gradually return to the original course. On the other hand, when sailing coastally, the ship 31 will continue to maneuver around the stern to quickly return to the original course. Checkpoint CP4 is the point at which it can be determined that the ship 31 has safely passed another ship 32. The determination of whether or not the ship has passed depends on the relationship of sight with the other ship 32 (Conduct of vessels in sight of one another). After passing the target, the restrictions on the ship's 31's movement are lifted, and the ship 31 continues to return to the original course in accordance with the surrounding circumstances. Checkpoint CP5 is the point at which the ship's position returns to the original course, remains constant, and it can be determined that avoidance maneuvering is complete.

[0037] In Figure 3, other ships 32 marked with "No action required" are in a situation where their CPA and BCR are above the set values ​​and there is no risk of collision. Other ships 32 marked with "Watch" are in a situation where their CPA or BCR is below the set value but no action has been initiated. Other ships 32 marked with "Operating" are in a situation where they are performing action based on a proposed avoidance route. Other ships 32 marked with "Pass" are in a situation where they have met the predetermined passing conditions. Also shown is a case where another ship 32 that was in the watch stage changes course, causing its CPA or BCR to exceed the set value, making no action necessary.

[0038] The give-way route R1 shown by the dashed line is an example of an operational route in the yellow phase when the navigation rules prescribed in COLREG are applied. In this case, another vessel 32 is approaching from the starboard front of the own vessel 31, posing a risk of collision, and the own vessel 31 becomes a give-way vessel. In addition, the own vessel 31 must comply with Rule 15, which states that "no vessel shall cross the bow of another power-driven vessel."

[0039] Furthermore, COLREG stipulates (Rule 8) that "When a vessel alters course or speed to avoid collision with another vessel, it shall, whenever possible, do so drastically so that the other vessel can easily observe the alteration," and "When a vessel takes action to avoid collision with another vessel, it shall do so in such a way that it can pass at a safe distance from the other vessel. In this case, the vessel shall carefully verify the effectiveness of the action until the other vessel has passed and is sufficiently far away." Therefore, when taking action to avoid collision, the action must include at least the following steps:

[0040] (a) A stage in which the change is made drastically so that other vessels can easily recognize it. The relationship between the CPA values ​​at each checkpoint is: CPA after the avoidance maneuver (checkpoint CP2) ≥ CPA during stern chasing (checkpoint CP3) ≥ CPA set as the safe passing distance (checkpoint CP4) > CPA before the avoidance maneuver (checkpoint CP1). The TCPA (checkpoint CP1), which is the start point of the action, is determined by distance or time when it is determined that the navigation rules prescribed in COLREG apply. The start point of the action varies depending on the speed and maneuverability of the own ship 31. The course angle θ required to ensure the set safe passing distance is also calculated based on the current speed, maneuverability, etc. By taking action early, the course angle α approaches the course angle β of the avoidance route during early avoidance maneuvering used in actual ocean voyages.

[0041] (b) Phase of passing another ship while maintaining a safe distance The CPA value when following behind is maintained at or above the set value from check point CP3 to the point where TCPA is equal to or less than 0 minutes (check point CP4). Also, to avoid maneuvering in a way that arouses suspicion in the other ship, the other ship 32 is prevented from being positioned to the starboard side of the ship 31. Even after passing the closest point of approach (check point CP4), observation is continued until the other ship 32 passes directly alongside the ship 31, and the CPA is prevented from falling below the set value. In this case, the CPA when following behind may be set.

[0042] (c) A stage in which the effect of the operation is carefully confirmed until the other vessel has passed and is sufficiently far away. The CPA value at checkpoints CP4 and CP5 is maintained at or above the set value so that the other vessel 32 does not become the closest vessel after passing directly alongside the vessel 31, and the vessel 31 operates to return to the original course. In this case, the TCPA of the other vessel 32 that was the target of avoidance will be displayed as the past or a negative value.

[0043] The avoidance route R2 shown by the solid line is an example of an operational route before the navigation rules defined in COLREG are applied, i.e., an example of an operational route in the green phase in this embodiment. In this case, the above-mentioned restrictions imposed by the navigation rules defined in COLREG are not imposed, so the degree of freedom in avoidance operations is increased.

[0044] In addition, COLREG stipulates that "When changing course in a wide area of ​​water, a vessel shall consider that changing course alone may be the most effective action to avoid a close approach to another vessel, provided that the change does not result in a significant new approach to the other vessel and is made significantly at the appropriate time" (Rule 8). Therefore, when changing course alone to avoid a collision, a sufficient amount of time and distance is required. In addition, in situations where a wide area of ​​water cannot be secured, it may not be possible to take the above-mentioned action, so actions will be taken according to various circumstances.

[0045] The above-mentioned checkpoints are different from waypoints (WPs) on the passage plan. Changing the latitude and longitude of a WP and its number to execute a collision avoidance maneuver constitutes a change to the passage plan, requiring an appropriate approval process. While changes to the passage plan vary depending on the ship management company's safety management system (SMS), approval by the captain and chief engineer on board, followed by approval by the ship management company on shore, is required. In ship operation, temporarily deviating from the original course to execute a collision avoidance maneuver does not constitute a change to the passage plan. In this embodiment, the WP is not changed, and sequential actions are determined based on the relative relationship with the other ship 32 that is the target of collision avoidance. As required by COLREG Article 8, the effectiveness of the actions can be carefully confirmed until the other ship 32 has passed and is sufficiently far away.

[0046] Furthermore, the own ship 31 may not always be able to execute avoidance maneuvers according to established rules, and various avoidance maneuvers may be necessary depending on the surrounding circumstances and the results of communication with the other ship 32. For example, even in a "crossing from starboard side" situation, if there is a sufficient distance to the other ship 32 or if a port turn is necessary for other reasons, a larger maneuver is required because the own ship 31 will cross in front of the other ship 32. The course angle in this case should be an amount that ensures not only the distance (CPA) set by the own ship 31 as a safe passing distance, but also a sufficient distance for the BCR as seen from the other ship 32. Furthermore, in a situation where the own ship 31 is crossing the bow of the other ship 32 by turning port, it is preferable to maintain that maneuver until the own ship 31 crosses the bow of the other ship 32, and the point at which the own ship 31 crosses the bow of the other ship 32 is checkpoint CP3.

[0047] In another case, in a "crossing from port side" relationship, once a meeting point is established, the other ship 32 has an obligation to give way, and the ship 31 has an obligation to maintain the line. However, the ship 31 may perform early give-way maneuvering during the green phase to prevent a meeting point from occurring. In this case, the course angle will be the one necessary to maintain the distance (CPA) set by the ship 31 as the safe passing distance, and normally, taking into account the possibility that the other ship 32 will turn starboard, the ship 31 will also perform a starboard turn to give way. Even in this case, it is preferable to maintain this action until the ship crosses the bow of the other ship 32, and the point at which the ship crosses the bow of the other ship 32 is checkpoint CP3.

[0048] As described above, in order to perform collision avoidance in accordance with COLREG, different actions are required depending on the situation at the time, and therefore different definitions are required for the conditions for determining that a checkpoint has been reached and the actions to be taken after the checkpoint has been reached. In this embodiment, multiple pre-set scenarios that define actions to be taken depending on the situation in which collision avoidance is required are created and registered.

[0049] 4 is an image diagram showing the data structure of a preset scenario. The preset scenario includes an identifier for identifying the scenario ("Scenario No." in the figure), application conditions under which the scenario can be applied, and an operation scenario that defines the conditions for reaching each of checkpoints CP1, CP2, CP3, CP4, and CP5 and the operation to be performed after reaching the checkpoints. In this example, the application conditions can be set as the water area, the number of other ships 32, the ship type, the rule, the COLREG phase, and the operation of the own ship. The preset scenario is created by the user at will, but a previously created scenario may also be used.

[0050] A configuration for converting avoidance actions into descriptions in a machine-readable formal language will be described with reference to FIG. 5 . A natural language is generally used to describe avoidance actions, such as the above-mentioned "follow the target stern." In order to convert such actions expressed in natural language into machine-readable descriptions that can be processed by a computer, a conversion dictionary 53 is provided in this embodiment. The conversion dictionary 53 is data for converting practical description data expressed in natural language and included in a preset scenario into machine-readable description data that can be processed by a computer.

[0051] Using a conversion dictionary 53, practical description data 51 expressed in qualitative expressions in COLREG and practical natural language is converted into machine-readable description data 52. The practical description data 51 is data in which practical decisions and actions are expressed in natural language. The machine-readable description data 52 is data expressed in the form of expressions, parameters, etc. used in general programming languages. Although detailed description rules differ depending on the programming language, by describing using widely used syntax and functions, conversion to adapt to the programming language to be implemented becomes easy.

[0052] The conversion dictionary 53, which conforms to the contents of COLREG written in qualitative natural language and converts practical expressions and natural language descriptions in operation procedure manuals (OPMs) into machine-readable descriptions, should ideally be created by someone with practical experience.

[0053] 6 shows a specific example in which practical description data 51 corresponding to the decisions and actions made by a human being in the case of collision avoidance shown in FIG. 3 is converted into machine-readable description data 52 using a conversion dictionary 53. Note that, since communication in English is required in the operation of ocean-going ships, natural language is usually written in English, but if the ship is operated only in a specific country such as Japan, it may be written in the language of that country.

[0054] Even when a decision is made by a human, parameters such as CPA, BCR, and HDG output from navigational equipment are used to determine rule application and avoidance action, and the numerical values ​​that serve as the criteria for judgment are expressed in practical natural language in documents such as the OPM. Specifically, in a crossing relationship, the condition at checkpoint CP2 is to orient the ship's heading (HDG) toward the target and perform avoidance maneuver so that the CPA is greater than the set safe passing distance. This is converted into a machine-readable description using syntax for solving optimization problems, such as "subject to CPA_t > CPA U_t, BCR_t > BCR U_t, HDG_o >= True BRG_t," which means maintaining the conditions that the CPA and BCR exceed the set values ​​and the HDG exceeds the set True BRG value, and "Minimize alteration(θ)," which means calculating the course angle θ that minimizes the course angle θ. By converting such programming languages ​​into syntax that is easily applicable, it becomes possible to create algorithms that perform actions similar to those of humans.

[0055] Examples of pre-set scenarios will be described with reference to Figs. 7 to 16. Fig. 7 shows an overtaking scenario during the green phase. Fig. 8 shows an overtaking scenario during the yellow phase. Fig. 9 shows a meeting scenario during the green phase. Fig. 10 shows a meeting scenario during the yellow phase. Fig. 11 shows a crossing scenario from the right during the green phase. Fig. 12 shows a "crossing from the port side" scenario during the yellow phase. Fig. 13 shows a "being overtaken from the port side" scenario during the yellow phase. Fig. 14 shows a "being overtaken from the starboard side" scenario during the yellow phase. Fig. 15 shows a scenario with multiple targets. Fig. 16 shows a scenario with multiple targets including targets not included in the calculation.

[0056] As shown in Figures 7 to 16, various patterns can be considered for the pre-configured scenarios. In each scenario, there are common parts and unique parts in the business description. Therefore, the unique parts of the business description are registered in the conversion dictionary 53 together with the corresponding machine-readable description as new description pairs.

[0057] Figures 12, 13, 14, and 15 illustrate scenarios in which the own ship 31 is the holding vessel. For example, in a crossing from the left, if early avoidance through give-way maneuvers is not possible, a holding obligation arises, and the set COLREG phase becomes the yellow phase, the own ship 31 must take action in accordance with the holding vessel provisions of Article 17. While maintaining course speed, the point at which the holding vessel begins to take action to avoid a collision with the give-way vessel as defined in Article 17, paragraph 2, is designated as checkpoint CP1. Furthermore, if the give-way vessel approaches too close and it is deemed that a collision cannot be avoided solely through the actions of the give-way vessel, the holding vessel is required to take the best possible cooperative action. The point at which this cooperative action begins is designated as checkpoint CP1'. Even in this case, the own ship 31 calculates the necessary course angle θ to maintain the distance set by the own ship 31 using CPA as the safe passing distance, but avoiding a collision remains the top priority. Therefore, even if the ship 31 cannot maintain a safe passing distance, it will begin to take avoidance action to avoid a collision and will begin to turn its own ship's heading (HDG) in a direction away from the other ship 32.

[0058] Here, the point at which the course angle is changed to θ or the point at which action is taken to avoid a collision as much as possible is set as check point CP2. In this case, too, the point at which the ship 31 crosses the bow of the other ship 32 is set as check point CP3, but if it is considered necessary to turn around to avoid a collision, the ship will continue to turn to starboard, and check point CP3 may not occur.

[0059] The ship 31 starts to return to the original course as soon as the target is cleared at check point CP4. When the ship's position returns to the original course at check point CP5 and the ship is on course, the avoidance maneuver is completed.

[0060] Even in a situation where the own ship 31 is being overtaken, if it is deemed that the overtaking ship is not taking appropriate action, the own ship 31 will abandon the course-holding action and take action by the holding ship and the best possible cooperative action will be taken. In this case, the own ship 31 can temporarily avoid a collision by changing course until it is parallel to the course of the other ship 32, and then after the other ship 32, which is faster than the own ship 31, gets ahead of the own ship 31, it will take action to return to the original course.

[0061] 15 and 16, a scenario in which there are multiple other ships 32 will be described. Collision avoidance operations in the presence of multiple other ships 32 depend on the system's ability to detect the other ships 32 and the functional limits of the collision avoidance algorithm that proposes an avoidance route. Boundary line L1 indicates the limit of the detection distance or the limit of the calculation range of the collision avoidance algorithm (collision avoidance plan formulation limit).

[0062] As shown in Figure 15, when all other ships 32 that should be the targets of collision avoidance operations are within detection distance and are the targets of calculation by the collision avoidance algorithm, the collision avoidance operations are composed of a smooth flow of steps from check point CP1 to check point CP5.

[0063] On the other hand, as shown in FIG. 16 , if there is another ship 32 that is beyond the limit for creating a collision avoidance plan or if the surrounding situation changes due to the action of the other ship 32, the other ship 32 is captured and recognized as a calculation target after the start of the collision avoidance operation at checkpoint CP1. Therefore, the collision avoidance route is calculated again during the collision avoidance operation, and an additional collision avoidance operation is performed, so the operation from checkpoint CP1 is repeated again. In such a situation, the user needs to understand the system's reliable range and the system's reconsidered state. For this reason, the distance at which the system can detect targets, the calculation range of the collision avoidance algorithm, targets that are to be avoided on the collision avoidance route, and changes must be displayed in a way that is easy for the user to understand. For example, as shown in FIGS. 15 and 16 , targets that are not subject to calculation may be displayed in a color (e.g., blue) that is not set in the COLREG phase.

[0064] In addition, for the scenarios shown in Figures 12 to 16, the practical description data 51 is converted into machine-readable description data 52 by registering description pairs of the practical description required for processing at each checkpoint and the converted machine-readable description in the conversion dictionary 53.

[0065] The configuration of the navigation support system 1 according to this embodiment will be described with reference to Fig. 17. Hereinafter, unless otherwise specified, the rules may be any rules such as treaties such as COLREG and STCW, domestic laws such as the Act on Preventing Collisions at Sea, Maritime Traffic Safety Act, Port Regulations Act, and Seafarers Act, and rules unique to industry associations and various companies, or may be a combination of two or more rules.

[0066] For example, the navigation support system 1 supports the work performed by the crew. The navigation support system 1 is connected to an integrated navigation system (INS) 2. The navigation support system 1 may include any equipment, devices, systems, etc. that are implemented on a ship to which the navigation support system 1 is applied. For example, the INS 2 may be a part of the system that constitutes the navigation support system 1. Here, for convenience of explanation, the navigation support system 1 and the INS 2 will be described as separate systems.

[0067] The navigation support system 1 performs navigation operations performed by humans using navigation equipment connected to the INS 2 as navigation support functions within an operational design domain (ODD) that is set as the range of operations in which the system can be trusted. Note that these functions are not limited to being performed as additional functions of the INS 2, but may also be performed by other intermediate systems or based on data obtained directly from individual onboard equipment.

[0068] For example, the navigation equipment connected to the INS 2 includes a radar 21, an AIS 22, a camera 23, an acoustic receiver 24, a radio 25, an Electronic Chart Display and Information System (ECDIS) 26, an autopilot 27, and a Voyage Data Recorder (VDR) 28. In addition, a main engine 29 and the like are connected to the INS 2. Navigation equipment information acquired from these navigation equipment is output from the INS 2 as navigation equipment data. Note that equipment not described here may be connected to the INS 2, and some of the equipment described here may not be connected.

[0069] For example, the automatic steering device 27 includes a heading control system (HCS) or a track control system (TCS).

[0070] The VDR 28 is a device that records the ship's navigation data (position information, speed, main engine RPM, etc.), voice communication within the bridge, image data from the radar 21, image data from the ECDIS 26, and the like.

[0071] In addition to the electronic navigation chart (ENC), the ECDIS 26 may display information entered by the user in a layer (user layer). Information that is not included in the ENC but is essential for the operation of the ship may be displayed in the user layer as lines, areas, or character strings. The ECDIS 26 can automatically perform safety checks on the ENC and user layer based on various parameters set by the user, while also presenting visual information to humans. Hereinafter, these functions may be collectively referred to as the ECDIS 26.

[0072] The navigation support system 1 is a computer system mainly composed of a computer. The computer has an arithmetic processing unit and a memory unit. The functions implemented in the navigation support system 1 are realized by the computer executing arithmetic processing in accordance with procedures such as programs stored in the memory unit. The computer system may be composed of any number of computers as long as it has at least one computer. The arithmetic processing unit may be composed of any hardware and may include any software. The memory unit may be composed of any number of storage media or any number of storage areas in the storage media. Furthermore, the various pieces of information stored in the memory unit do not need to be stored in a clearly distinguishable manner, and the names given to the information may be freely determined.

[0073] The navigation support system 1 includes a data storage unit 11, a watchkeeping execution unit 12, a collision avoidance execution unit 13, a watchkeeping management unit 14, an OOW call management unit 15, and a user terminal 16.

[0074] As shown in FIG. 18 , the data storage unit 11 stores rule estimation logic data 111, rule set data 112, own ship setting data 113, history data 114, situation awareness data 115, integrated target list data 116, conversion dictionary data 117, and pre-set scenario data 118. In addition to the above, the data storage unit 11 may also store data indicating any information. For example, the data storage unit 11 includes various data set by the user (hereinafter referred to as "user-set data"). The user-set data may include the above-mentioned data and information. Hereinafter, "information" refers to content to be processed in the navigation support system 1, and "data" refers to data recorded on a medium in a format that can be processed by the navigation support system 1, but information and data can be arbitrarily converted into each other.

[0075] The rule inference logic data 111 includes rule inference logic that describes a procedure for inferring compliance with various rules that apply to the operation of a ship. The rule inference logic is a machine-readable program written in a format that can be operated by a computer.

[0076] For example, the rule estimation logic includes applied rule estimation logic and rule-specific compliance confirmation logic. The applied rule estimation logic is logic for estimating which rule applies to the ship 31 from among multiple rules that apply to ship operation. The rule-specific compliance confirmation logic is logic for confirming whether the operating state of the ship 31 complies with the rules that apply to the ship 31. Note that the rule estimation logic is not limited to the configuration described here, and may be configured in any way as long as it is configured to achieve similar functions.

[0077] The rule set data 112 is information that defines the relationship between the rule estimation logic and parameters defined by other information. For example, the parameters used in the rule estimation logic include various parameters included in the ship setting data 113 and the situation awareness data 115.

[0078] The requirements qualitatively described in the various rules are defined as physical parameters such as distance, time, speed, or direction. The rule set data 112 includes information defining the correspondence between parameters used to identify a rule to be applied depending on a situation and parameters used to estimate compliance with the identified rule, and information included in the rule estimation logic data 111, the ship setting data 113, and the situation awareness data 115. The rule set data 112 also includes rule application condition information as parameters, including visibility information indicating the visibility state around the ship 31 and water area information indicating the water area in which the ship 31 is navigating. The visibility information and water area information may be defined using terms used as practical standards, such as the IMO Standard Marine Communication Phrases, or may be defined using a unique code system.

[0079] The ship setting data 113 includes parameters set according to the characteristics of the ship 31 and used in the rule inference logic included in the rule inference logic data 111, as well as user call conditions, which are conditions for the OOW call management unit 15 to execute an OOW call. For example, the ship setting data 113 includes information on the ship 31's navigation equipment data, the ship's condition, maneuverability, navigation area, ship congestion status, and instructions in the operation manual, and may also include any information that a human would use to make a judgment depending on the situation. For example, the ship setting data 113 is appropriately set by a user (e.g., a crew member). Data based on the ship's unique characteristics, such as the size, type, and maneuverability of the ship 31, may be set by the user or may be registered in advance as the ship setting data 113.

[0080] The history data 114 includes an integrated target list and a history of own ship operations.

[0081] The situation awareness data 115 is data generated by the situation awareness unit 123 based on navigation equipment data acquired from the INS 2 as data indicating situational awareness information required for processing in the collision avoidance execution unit 13, watch operation management unit 14, integrated target list management unit 121, target list update unit 122, and rule estimation unit 124. Here, situation awareness information is information required by STCW, including, for example, lookouts specified in COLREG, and is information that crew members should confirm during ship operation. In this embodiment, it refers to the situation of the ship 31 required to determine the ship's operation. The situation awareness data 115 is generated by referring to various parameters used in the rule estimation logic data 111, rule set data 112, and ship setting data 113.

[0082] The integrated target list data 116 is data that stores an integrated target list.

[0083] As shown in Figures 5 to 16, the conversion dictionary data 117 is a conversion engine used in the process of converting a preset scenario from a practical description to a machine-readable description. For example, the conversion dictionary data 117 includes data in which a practical description and a machine-readable description are stored as a description pair. The description rules for the machine-readable description may be in any format as long as they can be processed by the collision avoidance execution unit 13, and are set appropriately depending on the programming language used in the navigation support system 1. Furthermore, they do not necessarily need to be stored as a language pair with a fixed correspondence, and a conversion engine using AI (Artificial Intelligence) that has been confirmed to be sufficiently reliable may also be used.

[0084] As shown in FIG. 4 , the preset scenario data 118 includes one or more conditions for determining the ship's own ship operation, and includes data in which the ship's own ship operation is preset according to the situation at each of the defined multiple checkpoints. There is no limit to the number of scenarios that can be set in the preset scenario data 118. Information for defining the situation for selecting the scenario to be applied may be any data that can be handled in the situation awareness data 115. Furthermore, the data in which the ship's own ship operation is set may be any data that can be processed by the collision avoidance execution unit 13, and may correspond to at least one of a practical description or a machine-readable description. If the data is stored in a practical description, it may be converted into a machine-readable description using the conversion dictionary data 117 as a process performed by the collision avoidance execution unit 13. If the data is stored in a machine-readable description, the practical description input by the user when setting the scenario is converted into a machine-readable description using the conversion dictionary data 117 and stored in the preset scenario data 118. In addition, pre-configured scenario data 118 can be created even if it is stored in both practical descriptions and machine-readable descriptions, if the configuration does not include conversion dictionary data 117, or if it is necessary to use an exceptional description pair that is not stored in the conversion dictionary data 117.

[0085] The watchkeeping unit 12 performs calculations to automatically keep watch on the ship 31. The watchkeeping unit 12 includes an integrated target list management unit 121, a target list update unit 122, a situation recognition unit 123, and a rule estimation unit 124.

[0086] The integrated target list management unit 121 integrates target data acquired as navigation equipment data from multiple devices including navigation equipment, and records and manages the integrated target list data 116 to which additional information has been added in the data storage unit 11.

[0087] The target list update unit 122 generates additional information based on the rule set data 112, the own ship setting data 113, and the navigation equipment data acquired from the INS 2, and updates the current values ​​of the integrated target list data 116. Furthermore, user setting data including information set by the user in the ECDIS 26, lines, areas, and character string information created on a user layer may be used. The target list update unit 122 also updates the history of the integrated target list stored in the history data 114.

[0088] The situation recognition unit 123 acquires, as navigation equipment data, own ship data indicating information on the status of the own ship 31, target data indicating information on the status of targets including the other ships 32, and surrounding data indicating surrounding information on the situation around the own ship, including the sea area and disturbances, from the INS 2. The situation recognition unit 123 generates situation awareness data 115 based on the acquired various data, own ship setting data 113, and rule set data 112. The own ship data and target data include information such as position, heading, and speed. The situation awareness data 115 is data indicating situation judgments required mainly by lookout (Rule 5) and risk of collision (Rule 7).

[0089] The rule estimation unit 124 acquires parameters that serve as rule application determination factors from the own ship setting data 113 based on the relative relationship between the own ship 31 and the target identified from the situation recognition data 115. The rule estimation unit 124 uses the acquired rule application determination factors to estimate a rule that applies to the own ship 31 from among multiple rules that apply to ship operation, in accordance with the rule estimation logic stored in the rule estimation logic data 111. The number of rule estimation logics stored in the rule estimation logic data 111 is not limited to one, and may be multiple.

[0090] The collision avoidance execution unit 13 performs calculations for automatically performing collision avoidance. The collision avoidance execution unit 13 includes an operation determination unit 131, an operation confirmation unit 132, and an operation execution unit 133.

[0091] The operation determination unit 131 determines the ship's operation to avoid a collision based on the situation awareness data 115 and the integrated target list data 116. The avoidance algorithm used to determine the ship's operation may be a calculation method using relative vectors between the ship 31 and the other ship 32 as shown in FIG. 37 , or a method of calculating a route that avoids an existing dangerous area. Alternatively, the operation determination unit 131 may determine any operation of the ship 31. For example, the operation determination unit 131 may calculate and determine an operation for the ship 31 to automatically navigate toward the destination in a situation where all rules do not apply.

[0092] The operation confirmation unit 132 checks the compliance of the operation created by the operation determination unit 131 with the rules of the ship's operation by referring to the rule estimation logic data 111, the rule set data 112, the ship's setting data 113, the situation recognition data 115, and the integrated target list data 116. If the rules to be applied to the ship 31 have been determined, the operation confirmation unit 132 may check compliance with the determined rules, and if the rules to be applied to the ship 31 have not been determined, the operation confirmation unit 132 may check compliance with common rules that are applied regardless of the situation of the ship 31.

[0093] The operation checking unit 132 may check compliance with any ship operation related to an operation plan or an operation currently being executed, such as an operation manually performed by a crew member, an operation input from outside the navigation support system 1, or an operation currently being executed, in addition to the operation determined by the operation determining unit 131. The compliance check may use rule-specific compliance check logic stored in the rule estimation logic data 111.

[0094] The operation execution unit 133 executes an operation whose compliance has been confirmed by the operation confirmation unit 132 or an operation that does not require compliance confirmation. For example, the operation execution unit 133 outputs a control command to the automatic steering device 27 or the like to execute an operation.

[0095] The shift duties management unit 14 performs calculation processing for automatically managing shift duties. The shift duties management unit 14 includes a shift duties execution unit 141 and a situation change detection unit 142.

[0096] The watch duty execution unit 141 executes tasks that can be automated among those performed by a navigational watch, a radio watch, an officer of the watch (OOW), etc. For example, the tasks performed by the watch duty execution unit 141 include paying attention to changes in the surrounding conditions such as water area, weather and sea conditions, and navigation warnings, confirming the ship's position using multiple methods, and responding to distressed persons, etc., which are tasks other than watchkeeping and actions to avoid collisions.

[0097] The situation change detection unit 142 has a function of detecting conditions that exceed an ODD set by the user as a reliable operation range for operations automatically performed by the shift operation execution unit 141, and outputs a warning when the ODD is exceeded. The ODD may be set, for example, as numerical criteria based on weather and sea conditions and visibility for each device connected to the INS 2, or may be set as criteria based on the performance of hardware or software of devices required for executing collision avoidance, such as the auto target tracking of the radar 21 and an image recognition function using data acquired by the camera 23.

[0098] The STCW regulations list events in which "the officer in charge of the navigational watch must immediately notify the master," such as "when restricted visibility is encountered or is expected," "when there is a problem with the traffic situation or the movement of other ships 32," "when some difficulty occurs in maintaining course," and "when land or navigational landmarks cannot be sighted or soundings cannot be made by the scheduled time" (STCW code Part A Chapter viii Rule 40). In addition, some ship management companies have provisions requiring reporting to the master via SMS.

[0099] Such a report to the captain is called a calling Master. When such an event occurs, it is predicted that the reliability of the automatic operation control by the watchkeeping execution unit 12, the collision avoidance execution unit 13, etc. will decrease. When such an event occurs, the navigation support system 1 issues a report to call the user, the officer on watch (hereinafter referred to as an "OOW call"). The situation change detection unit 142 automatically detects a change in the situation that requires an OOW call.

[0100] When the situation change detection unit 142 detects a change in the OOW call situation, the OOW call management unit 15 notifies the user if the user call conditions stored in the ship setting data 113 are met. The OOW call management unit 15 also notifies the user if a flag indicating that the OOW call conditions in the integrated target list are met is turned on. The notification to the user may be performed in any manner. For example, the notification to the user may be displayed on a display or the like, or may be notified to the user by light, sound, vibration, or the like. The notification to the user may also be achieved via the user terminal 16.

[0101] The user terminal 16 is a portable terminal mainly composed of a computer that allows a user to use various functions of the navigation support system 1. The user terminal 16 presents information about the navigation support system 1, such as OOW calls, to users such as OOWs. The user terminal 16 may implement any function of the navigation support system 1 or display any information. The series of notifications and the user's response after the notification are specified by SMS.

[0102] For example, the navigation support system 1 includes a situation recognition unit 123 that generates situation recognition data 115 that indicates the surrounding situation including the ship 31 and the target, a data storage unit 11, a target list update unit 122, and an operation confirmation unit 132. The data storage unit 11 stores rule estimation logic data 111 that defines a process for estimating compliance with rules applied to ship operation, rule set data 112 that defines a correspondence with the situation recognition data 115, and ship setting data 113 that sets ship-specific information used for determining operations according to the ship's operating status as a parameter.

[0103] The target list update unit 122 updates the integrated target list. The integrated target list is a list for managing information on each target whose situation has been determined by the situation recognition unit 123, by adding additional information used in processing in the rule estimation logic based on the own ship setting data 113.

[0104] The operation checker 132 checks the input operation of the ship 31 for compliance with the rules based on the rule set data 112 and the integrated target list.

[0105] This enables the navigation support system 1 to present operations and the basis for those decisions in accordance with various rules that apply to ship operation and the ship's own settings.

[0106] Furthermore, when it can be determined that the automatic control by the navigation support system 1 is within the ODD range set as a reliable range, the navigation support system 1 has the watchkeeping execution unit 12 automatically perform watchkeeping, and based on the execution of the watchkeeping execution unit 12, the collision avoidance execution unit 13 automatically executes operations to avoid a collision.

[0107] Furthermore, when it is determined that various watch duties other than actions to avoid collisions are within the range of ODD, the watch duty execution unit 141 can automatically execute navigation watch duties.

[0108] When the watchkeeping execution unit 12, the collision avoidance execution unit 13, or the watch duty execution unit 141 detects that the ODD range has been exceeded, the OOW call management unit 15 outputs a signal to notify the user of an alarm or other notification. The OOW can grasp, at any location on the ship, that a situation requiring OOW action has arisen by receiving an OOW call display or other notification on the user terminal 16 they carry. For example, STCW regulations stipulate that the bridge must not be left unattended under any circumstances (STCW code Part A Chapter viii Rule 18.1). By carrying the user terminal 16, the OOW can serve as an alternative means of temporarily leaving the bridge.

[0109] 19 and 20, a description will be given of screens G5 and G6 that are displayed on the user terminal 16 and allow the user to set rule set data. Note that the screens G5 and G6 described here are merely examples, and any screen may be displayed on the user terminal 16.

[0110] Distance is measured in nautical miles (NM), and time is measured in minutes. Data input by the user is set in the data storage unit 11 as rule set data 112 and own ship setting data 113. For example, a user such as a captain, navigator, or crew member uses a user terminal 16 to set setting values ​​for determining the application of rules in the navigation support system 1. Specifically, the user sets various parameters according to the condition of the own ship 31, maneuverability, navigation area, surrounding conditions, ship congestion, and the operation manual, etc. The setting values ​​for the risk of collision are input numerically as CPA, BCR, and other parameters used by the user for judgment.

[0111] The COLREG phase item on screen G5 has input fields for inputting the respective setting values ​​of range (RNG) and TCPA as input parameters. Note that some of the setting values ​​may be automatically input into the input fields. For example, in the operation of a general merchant ship, the criterion for determining whether the safe passing distance is less than the CPA, which is set as a risk of collision. Therefore, on screen G5, the CPA may be automatically input as a setting value for determining whether the safe passing distance is less than the CPA, or the CPA may be manually input by the user.

[0112] The action stage item on screen G5 has an input field for inputting a setting value for switching between the stages of "no action required" and "pay attention." CPA and BCR are input as parameters in the input field.

[0113] The action timing item on screen G5 has an input field for inputting a setting value for switching between "too early," "possible," and "too late" stages. The COLREG phase, CPA, TCPA, BCR, and BCT are input as parameters for each action timing in the input fields. The "possible" stage input field also inputs a setting value for determining whether the CORLEG rule is applicable.

[0114] Values ​​that are desired to match the set values ​​set in the COLREG phase or operation stage items may be automatically input, or may be manually input if changes are required.

[0115] The items and input parameters described here are merely examples and may be changed as desired, and any input field may be set to allow automatic or individual input. A function may also be provided to check whether there are any inconsistencies in distance or time for multiple input values. The navigation support system 1 may automatically calculate setting values ​​from values ​​input by the user based on data such as the ship's maneuverability and sea area.

[0116] For example, as shown in screen G6 of Fig. 20, detailed conditions may be input into a user setting screen. In this example, conditions for determining the relative orientation, target aspect, other conditions, CORLEG phase, operation stage, operation timing, and fixed rule can be input for each applicable rule. The conditions may be input by selecting the parameters or logical symbols to be used using a drop-down menu or the like, or by entering an arbitrary logical expression as text.

[0117] The integrated target list will be described with reference to Figure 21. The integrated target list data 116 is a list for systematically observing and managing current information on targets, including other ships 32, detected by the INS 2. All target information included in the integrated target list data 116 is recorded in the history data 114.

[0118] The data for creating the integrated target list data 116 is acquired by onboard equipment. The navigation support system 1 acquires the data via the INS 2. For example, the data items managed by the integrated target list data 116 are as follows:

[0119] The "ID" item is a number or ship name that identifies the target. The "Lat." item indicates latitude. The "Lon." item indicates longitude. The "HDG" item indicates heading. The "STW" item indicates speed through water. The "RNG" item indicates range. The "R.BRG" item indicates relative bearing. The "CPA" item indicates closest point of approach. The "TCAP" item indicates time to the closest point of approach. The "BCR" item indicates bow crossing range. The "BCT" item indicates bow crossing time. The item "Nav. Status" indicates the navigational status.

[0120] These items are target data included in the navigation equipment data acquired from INS2.

[0121] The items "Target Aspect (TA)", "ACR", "COLREG Phase", "Applicable Rule", "Action Stage", "Action Timing", "Confirmation Rule", "Pass", and "OOW Call" are additional information data calculated as the above-mentioned additional information by the target list update unit 122 of the watchkeeping execution unit 12. Note that "ACR" indicates the Abeam Crossing Range (ACR), which is the point at which the own ship 31 crosses the straight line indicating its beam. In addition, own ship data indicating own ship information is also output from the navigation equipment data.

[0122] Among the data items managed by the integrated target list data 116, the time (TCPA, BCT, ACT, etc.) until the ship 31 reaches each of the specified points, including the point where the ship 31 and the target are closest to each other, the point where the target crosses the bow of the ship 31, and the point where the target crosses the beam of the ship 31, and the distance (CPA, BCR, ACR, etc.) between the ship 31 and the target at these specified points are treated as parameters of estimated values ​​based on current values.

[0123] In a real environment, the calculation result may fluctuate around the set value due to fluctuations in the ship 31 and the other ships 32, and as a result, it is expected that the judgment may change frequently. In such cases, the judgment result for that item may use an average value for a certain period of time, etc.

[0124] Furthermore, if the reliability of the information on other ships 32 is questionable based on the continuity of numerical values, or if the other ships 32 are behaving unnaturally, the data content of the integrated target list may not be reliable as is. In such cases, an OOW call may be executed. In this case, the "OOW call" item is turned on. For example, turning on the "OOW call" item means setting a flag indicating the execution of an OOW call (for example, changing a variable from "0" to "1").

[0125] For example, the integrated target list is data structured in a table format for calculations in the navigation support system 1, and some of the information in the integrated target list may not be displayed to the user.

[0126] Next, the determination rule will be described with reference to Fig. 22. The integrated target list is updated each time instantaneous data is acquired from the INS2, and additional information is also generated based on the instantaneous data.

[0127] In COLREG, once the applicable rule is determined, the applicable rule does not change due to successive changes in the relative relationship between the ship 31 and the other ships 32 based on avoidance actions. Therefore, in this embodiment, the applicable rule is considered to be determined when the "COLREG phase" becomes "yellow." The determined applicable rule is recorded as retained information in the integrated target list.

[0128] Figure 22 shows a state in which the relative relationship with another ship 32 changes as a result of the operation of the own ship 31. Additional information based on instantaneous data includes the applied rule, COLREG phase, operation timing, and changes over time in the operation stage. Retained information includes changes over time in the determined rule. In this example, the applied rule is "matching," the COLREG phase is not applicable (N / A: Not Applicable), the operation timing is "premature," and the operation stage is "no operation required" are displayed.

[0129] Subsequently, when the COLREG phase becomes "yellow" and the rule is confirmed as "passing," the confirmed rule is recorded in the retained information as "passing." Subsequently, as the ship 31 operates, the applicable rule determined by the instantaneous data is "opposite course vessel," but the confirmed rule is maintained as "passing." Then, when the target list update unit 122 receives an operation plan from the operation determination unit 131, the operation stage changes to "operating." However, if the operation received from the operation determination unit 131 is a port turn, which is prohibited by the COLREG, the operation confirmation unit 132 rejects the operation, and "port turn" is presented as the reason for rejection. If the plan is a starboard turn, the operation confirmation unit 132 approves the operation, and the operation stage remains "operating" until the passage conditions are met. Furthermore, even if the timing of the operation is "too late" based on the determination made based on the instantaneous data, the operation stage is already "operating," so an "OOW call" is not required.

[0130] In this way, during the period in which the applicable rule is considered to be determined based on the additional information, the information is held as a confirmed rule in the integrated target list regardless of the applicable rule calculated as instantaneous data. Therefore, it is possible to determine the compliance of COLREG with the collision avoidance operation once the applicable rule has been determined.

[0131] The procedure of the rule estimation logic for estimating the rule to be applied to the ship 31 will be described with reference to Figures 23 to 26.

[0132] The judgment results shown by dotted lines in the figure indicate that there are rules that must be followed when operating a ship, but the parameters for determining specific operations are not registered in the rule set.

[0133] For rules for which no rule set is registered, the operation confirmation unit 132 cannot confirm compliance of the operation of the other ship 32 with the rules. In this case, the operation confirmation unit 132 determines the applicable rules of the integrated target list, but turns on the item "OOW call" and stops processing.

[0134] The rules applied to ship operation include descriptions that can be interpreted as physical parameters such as distance, time, and direction, as well as vague descriptions based on human intuition. Therefore, for rules that are difficult to describe using physical parameters, or rules that are difficult to register as a rule set, such as rules that apply to specific water areas or times, the navigation support system 1 is configured to only identify which rules are generally applied, and to leave specific responses to humans.

[0135] For the rule determination indicated by the solid line, a rule set for the operation confirmation unit 132 to confirm the operation of the other ship 32 is registered in the rule set data 112 .

[0136] The procedure for rule estimation MT7 based on water area will be described with reference to Figure 23. The navigation support system 1 acquires the position information of the ship 31 (step S701) and refers to the boundary line set by the user of the ECDIS 26 (step S702). If the ship 31 is located in a water area to which a special rule applies, "special rule (Rule 1(b))" is set in the applicable rule field (Yes in step S703).

[0137] If the ship 31 is located in a water area where special rules are not applied and rules for narrow channels are applied, "narrow channels (Rule 9)" is set in the applicable rule item (Yes in step S704).

[0138] If the ship 31 is located in a water area where rules for narrow waterways, etc. do not apply, but rules for traffic separation schemes apply, "traffic separation scheme (Rule 10)" is set in the applicable rule item (Yes in step S705).

[0139] If none of the water area-based rules apply, the navigation support system 1 proceeds to visibility-based rule estimation MT8 (No in step S705).

[0140] The procedure for rule estimation MT8 based on visibility will be described with reference to Figure 24. The navigation support system 1 acquires the current visibility state (step S801). If the navigation support system 1 determines that visibility is restricted, it sets "Ship navigation in restricted visibility conditions (Rule 19)" in the applicable rule item (Yes in step S802).

[0141] The navigation support system 1 determines the visibility state from, for example, a visibility meter or an image captured by a camera, etc. Furthermore, since humans recognize the situation by the rain area captured by an X-band radar, such as "X miles to the rain area," the navigation support system 1 may determine the visibility state by combining the echo of rain and snow reflections on the radar with camera images.

[0142] If the visibility is not restricted, the navigation support system 1 proceeds to rule estimation MT9 based on the positional relationship between the own ship 31 and the other ships 32 (No in step S802).

[0143] The procedure for the positional relationship-based rule estimation MT9 will be described with reference to Figure 25. The navigation support system 1 acquires data for understanding the status of the target other ship 32 (step S901), and if it determines that the other ship 32 is behaving unpredictably or is likely to behave unpredictably, sets "crew's usual duties (Rule 2)" in the applicable rule field (Yes in step S902). Unpredictable behavior may be determined based on continuous observation of the movements of the other ship 32 or the ship type, etc. Depending on the ship type, it is possible to predict that the other ship 32 may behave unpredictably or that a voice call will be received from that other ship 32. Therefore, "crew's usual duties (Rule 2)" is set when the presence of that type of ship is detected near the course of the ship 31.

[0144] If the navigation support system 1 determines that the other ship 32 is not behaving unpredictably, it sets one of the following in the applicable rule field, based on the correspondence between the relative bearing and the target aspect registered in the rule set: "Overtaking / giving way vessel (Rules 13 and 16)," "Overtaken / holding vessel (Rules 13 and 17)," "Meeting / both actions (Rule 14)," "Crossing (starboard side) / giving way vessel (Rules 8, 15 and 16)," or "Crossing (port side / holding vessel (Rules 15 and 17)" (No in step S902, step S903).The navigation support system 1 then proceeds to rule estimation MT10 based on the state of other ships.

[0145] The procedure for rule estimation MT10 based on the state of other ships will be described with reference to Figure 26. The navigation support system 1 acquires data on the target other ship 32 (step S1001). If the navigation support system 1 determines that the other ship 32 is displaying lights and shapes different from those of the powered ship currently sailing or that the other ship 32 falls under the various types of ship navigation (Rule 18), it sets "various types of ship navigation (Rule 18) (excluding Rule 13)" in the applicable rule field (Yes in step S1002).

[0146] If the other ship 32 does not fall under these categories, and ``Overtaken / Holding Ship (Rule 13 and 17)'' or ``Crossing (Port Side) / Holding Ship (Rule 15 and 17)'' is not set in the applicable rule item, the navigation support system 1 maintains the applicable rule set in the rule estimation MT9 based on positional relationship (No in step S1003), and if ``Overtaken / Holding Ship (Rule 13 and 17)'' or ``Crossing (Port Side) / Holding Ship (Rule 15 and 17)'' is set, the navigation support system 1 proceeds to rule estimation MT11 for holding ships (Yes in step S1003).

[0147] The procedure for rule estimation MT11 in the case of a retained ship will be described with reference to Figure 27. The navigation support system 1 acquires data on the target ship 32 (step S1101), and if there is no risk of collision or the operation of the target ship 32 is appropriate, sets "Maintain course and speed (Rule 17(a)(i))" in the applicable rule item (No in step S1102, Yes in step S1103).

[0148] If the necessary warning signal has not been issued when there is doubt as to whether the other ship 32 is taking sufficient action to avoid a collision, the navigation support system 1 sets "warning signal (Rule 34(d))" in the applicable rule field (No in step S1104). If a warning signal has been issued, the navigation support system 1 determines whether the give-way vessel has approached too close to the ship 31 and whether it is deemed that a collision with the give-way vessel cannot be avoided solely through the actions of the give-way vessel (step S1105). If the condition is not met, the navigation support system 1 sets "action to avoid collision (Rule 17(a)(ii) (optional))" in the applicable rule field (No in step S1105). If the condition is met, the navigation support system 1 sets "best cooperative action (Rule 17(b))" in the applicable rule field (Yes in step S1105).

[0149] The above is the process for determining the applicable rule. Note that the notation of the determination result shown in the above explanation is merely an example, and any notation may be used as long as the applicable clause and action can be identified, and symbols such as IDs may also be used.

[0150] 28, the procedure of the operation stage determination MT12 for determining the operation stage of the ship 31 will be described. The navigation support system 1 acquires data of the target ship 32 (step S1201), and if "too late" is set in the operation timing item, turns on the item "OOW call" and returns to the initial processing (Yes in step S1202, step S1203).

[0151] If the navigation support system 1 determines that the operation stage item is set to "In Operation" and that the conditions for "Pass" are met, it changes the operation stage item to "Pass" and returns to the initial process (Yes in step S1204, Yes in step S1205, step S1206).On the other hand, if the navigation support system 1 determines that the conditions for "Pass" are not met and detects a situation requiring some kind of operation change, it turns on the item "OOW Call" and returns to the initial process (No in step S1205, Yes in step S1207, step S1208).

[0152] If the navigation support system 1 determines that "Pass" is set in the action stage item and that there is no new risk of collision, it returns to the initial process and does not change the action stage item (Yes in step S1209, No in step S1210). On the other hand, if the navigation support system 1 determines that there is a new risk of collision, or if "Pass" is not set in the action stage item, it sets either "No action required" or "Pay attention" in the action stage item according to the set conditions (No in step S1209, Yes in step S1210, step S1211).

[0153] Next, if the operation is being performed, the navigation support system 1 sets the operation stage item to "in operation" and then returns to the initial processing (Yes in step S1212, step S1213), and if the operation is not being performed, returns to the initial processing without changing the operation stage item (No in step S1212).

[0154] 29, the procedure of the action timing determination MT13 for determining the timing of the action of the ship 31 will be described. The navigation support system 1 acquires data on the target ship 32 (step S1301). If the navigation support system 1 determines that "passing" is set in the action stage field and that there is no risk of a new collision, it sets "NULL" in the action timing field (Yes in step S1302, No in step S1303, step S1304). "NULL" in the action timing field means that no action is required, and therefore no action timing is to be determined.

[0155] If the navigation support system 1 determines that there is a risk of a new collision and the operation stage item is set to "no operation required," it sets the operation timing item to "NULL" (Yes in step S1303, Yes in step S1305, step S1304).

[0156] If "Pass" is not set in the operation stage item and "No operation required" is set in the operation stage item, the navigation support system 1 sets "NULL" in the operation timing item (No in step S1302, Yes in step S1305, step S1304).

[0157] If "No action required" is not set in the action stage item, the navigation support system 1 determines whether the pre-set requirements for determining "too late" are met (No in step S1305, step S1306). If the navigation support system 1 determines that the requirements for determining "too late" are met, it sets "too late" in the action timing item, turns on the "OOW call" item, and returns to the initial processing (Yes in step S1306, steps S1307, S1308).

[0158] If the navigation support system 1 determines that the requirements for determining "too late" are not met, it determines whether the pre-set requirements for determining "possible" are met (No in step S1306, step S1309). If the navigation support system 1 determines that the requirements for determining "possible" are met, it sets "possible" in the operation timing item and returns to the initial processing (Yes in step S1309, step S1310).

[0159] If the navigation support system 1 determines that the requirements for determining "possible" are not met, it determines whether or not the pre-set requirements for determining "premature" are met (No in step S1309, step S1311). If the navigation support system 1 determines that the requirements for determining "premature" are met, it sets "premature" in the operation timing item and returns to the initial processing (Yes in step S1311, step S1312). If the navigation support system 1 determines that the requirements for determining "premature" are not met, it returns to the initial processing (No in step S1311).

[0160] 30, the procedure of the action decision judgment MT, which makes a judgment to decide the action of the ship 31, will be described. The action decision unit 131 extracts data on other ships 32 whose action timing is "watch" and determines whether or not an action is necessary. If the action timing is "possible," the action decision unit 131 determines that an action is necessary, and if the action timing is "too early," the action decision unit 131 returns to the initial processing (steps S1401 and S1402).

[0161] If the operation determination unit 131 determines that an operation is necessary but has not yet determined the action to be taken after the change, such as maintaining or changing the course or speed, it executes an "OOW call" and returns to the initial processing (No in step S1403, step S1404). In this case, maintaining the course and speed includes the operation of maintaining the course and speed in a situation where the navigation rules of the holding ship are applied to the own ship 31.

[0162] The operation determination unit 131 determines the course and speed based on the "application rules" of the integrated target list so that the CPA and BCR fall within a range greater than the set values. When the changed action is determined based on this determination of the course and running speed, the operation determination unit 131 performs the next process, assuming that the changed action has been determined.

[0163] When the operation determination unit 131 determines an operation such as maintaining or changing the course or speed, the operation determination unit 131 confirms the operation with the operation confirmation unit 132 (Yes in step S1403, step S1405). If the operation confirmation unit 132 cannot confirm the operation, the operation determination unit 131 returns to the initial process (No in step S1405). If the operation confirmation unit 132 can confirm the operation, the operation determination unit 131 performs a safety check using the ECDIS 26 or the like (Yes in step S1405, step S1406). If the safety check for the information or data set by the user in the ECDIS 26 is passed, the operation determination unit 131 saves the determined operation and returns to the initial process (Yes in step S1406, step S1407). If the safety check is not passed, the operation determination unit 131 returns to the initial process (No in step S1406).

[0164] Fig. 31 shows in more detail the processing of step S1402 in Fig. 30. The operation determination unit 131 determines that an operation is necessary when the operation timing in the integrated target list is "possible," and determines that an operation is unnecessary when the operation timing is "too early" or "too late" (No in step S14021, step S14021).

[0165] If the operation determination unit 131 determines that the operation is possible, it determines whether the situation is one in which the pre-defined scenario can be applied, and if it determines that the situation is one in which the pre-defined scenario cannot be applied, it executes an ``OOW call'' (No in step S14023, step S14024).

[0166] In this embodiment, multiple operation scenarios that can be executed under predetermined conditions are set in advance, as shown in Figure 4. The conditions include the area of ​​water in which the ship is sailing, the number of other ships 32, the rules, and the COLREG phase. These conditions may be any information that can be acquired by the situation recognition unit 123, and may be set by the user as appropriate.

[0167] Returning to FIG. 31 , if the operation determination unit 131 determines that the situation is one in which a preset scenario can be applied, it selects the most appropriate scenario at that time (Yes in step S14023, step S14025). The operation determination unit 131 calculates a safe speed based on the selected scenario (S14026). The operation determination unit 131 compares the calculated safe speed with the current ship speed, and if it determines that a speed change is necessary, it calculates a speed command and calculates a course angle θ based on the selected scenario (Yes in step S14027, steps S14028, S14029). If it determines that a speed change is not necessary, the operation determination unit 131 does not calculate a speed command, but calculates a course angle θ based on the selected scenario (No in step S14027, step S14029). This creates a changed course and speed (step S14030).

[0168] Next, the state transition of the collision avoidance execution unit 13 will be described with reference to FIG.

[0169] The collision avoidance execution unit 13 has three modes: a manual steering mode MD1, an automatic steering mode MD2, and an automatic collision avoidance (ACA) mode MD3. For example, switching among the modes MD1 to MD3 is performed by a mode changeover switch 412 on a switch panel 41 shown in FIG. 33. In addition, the switch panel 41 may be provided with a system selection switch 411 for selecting one of the automatic steering devices in the dual system. The system selection switch 411 may be configured in the same way as a switch installed on a typical ocean-going ship.

[0170] In the automatic collision prevention mode MD3, operations are executed based on state transitions as internal processing of the collision avoidance execution unit 13. The collision avoidance execution unit 13 performs state transitions based on information managed in the integrated target list, etc.

[0171] The automatic collision prevention mode MD3 has two states, a normal state ST1 and a danger response state ST2, and an OOW override state ST3 that can be executed from the normal state ST1 or the danger response state ST2. The OOW override state ST3 is a so-called override state in which a decision input by the user takes priority over a decision made by the operation decision unit 131, and manual operation is performed regardless of the switching of the switch.

[0172] The collision avoidance execution unit 13 switches to the normal state ST1 if the timing of action is not "too late," and switches to the danger response state ST2 if the timing of action is "too late."

[0173] The normal state ST1 is divided into an OOW-free state ST11 and an OOW-invoked state ST12, and is also divided into an ACA standby state ST13 and an ACA operation required state ST14. Each state transition is performed based on the integrated target list data 116 managed by the integrated target list management unit 121.

[0174] The OOW-less state ST11 is a state in which the OOW is not monitoring the operation of the collision avoidance execution unit 13. The OOW-invoked state ST12 is a state in which the OOW is monitoring the operation of the collision avoidance execution unit 13.

[0175] When an OOW call is made, the collision avoidance execution unit 13 goes into an OOW call state ST12, and when the OOW is released from the monitoring mission, goes into an OOW no state ST11.

[0176] The ACA standby state ST13 is a state in which the vehicle is on standby for automatic collision prevention operation, and the ACA operation required state ST14 is a state in which automatic collision prevention operation is required.

[0177] The collision avoidance execution unit 13 transitions to the ACA action required state ST14 when the action timing is "possible," and transitions to the ACA standby state ST13 when the collision avoidance operation is completed. The danger response state ST2 transitions between an automatic danger response state ST21 in which a programmed danger response is executed, and an OOW override state ST3.

[0178] The processing by the operation execution unit 133 will be described with reference to Fig. 34. The operation execution unit 133 executes an operation based on the selected scenario, and when it determines that collision avoidance has been completed, transitions to the ACA standby state ST13 (steps S3301 and S3302: Yes).

[0179] If it is determined that the avoidance has not been completed, the operation execution unit 133 determines whether a change in operation is necessary due to a change in the situation, and if it determines that a change in operation is necessary, it determines whether the next scenario has been selected by the operation determination unit 131 (No in step S3302, Yes in step S3303, step S3304).

[0180] If no change in operation is required or if the next scenario is selected, the operation based on the selected scenario continues to be executed (No in step S3303, Yes in step S3304, step S3301).

[0181] On the other hand, if the next scenario is not selected, the operation execution unit 133 executes an OOW call (step S3305). If an operation overridden by the OOW is performed, the operation transitions to the OOW override state ST3 (Yes in step S3306). If the operation is not performed, it is determined whether the state is dangerous (No in step S3306, step S3307). If it can be determined that the state is not dangerous even when an operation overridden by the OOW is not performed, the operation execution unit 133 continues to execute an operation based on the selected scenario (No in step S3307, step S3301). On the other hand, if the operation execution unit 133 determines that the state is dangerous, it transitions to the danger response state ST2 (Yes in step S3307).

[0182] 35, the procedure of the operation confirmation determination MT15 for confirming the operation of the ship 31 will be described. The operation confirmation unit 132 identifies the first other ship 32 for which operation confirmation should be performed, and determines that the operation confirmation is rejected for the other ship 32 that does not pass the safety check (No in step S1501). The reason why the operation confirmation unit 132 also performs a safety check following the operation determination unit 131 is to confirm the operation input from outside.

[0183] If the operation timing item is set to anything other than "too late," "too early," or "possible," the operation confirmation unit 132 determines that the operation confirmation is rejected (Yes in step S1503, Yes in step S1504, No in step S1505).

[0184] When "possible" is set in the operation timing field, the operation checker 132 determines whether the situation is one in which operation according to COLREG is to be applied. Specifically, the operation checker 132 determines whether the range (RNG) or TCPA is below a preset value (Yes in step S1505, step S1506). The preset value is the lower limit value below which navigation in the COLREG matching relationship is not applied. Therefore, when the range or TCPA is below the preset value, the situation is one in which navigation according to COLREG is to be applied.

[0185] If it is determined that the range or TCPA is below the set value, the operation checker 132 determines whether or not the navigation method defined in COLREG is being complied with (Yes in step S1506, step S1507).

[0186] If the operation checker 132 determines that the navigation method defined in the COLREG is not met, it rejects the operation check (No in step S1507).

[0187] Even if the navigation rules specified in COLREG are met or the situation is such that COLREG is not applicable, if the operation confirmation unit 132 determines that the avoidance action cannot maintain or ensure a safe distance, it will reject the operation confirmation (No in step S1506, Yes in step S1507, No in step S1508).

[0188] If the operation confirmation unit 132 determines that a safe distance can be maintained or ensured, it determines whether there are any other ships 32 whose operation should be confirmed (Yes in step S1508, step S1509). If the operation confirmation unit 132 determines that there are other ships 32 whose operation should be confirmed, it identifies the next other ship 32 and determines whether the range or TCPA of the identified other ship 32 is below the set value (Yes in step S1509, step S1510, step S1506).

[0189] When determining that the distance is safe, the operation confirmation unit 132 sets a condition that the distance does not fall below the CPA set as the safe passing distance, but an upper limit on the turning angle for avoidance may be set in order to keep deviation from the original course within an acceptable range or to prevent large turning angles from being executed based on the sole judgment of the system. Furthermore, if the upper limit on the turning angle is exceeded, the operation confirmation unit 132 may reject the operation confirmation or may execute an "OOW call."

[0190] If the operation check unit 132 has not determined that all of the other ships 32 whose operation should be checked have been rejected, it ends the operation check and determines that the check has been completed (No in step S1509).

[0191] 36, the procedure for the navigation confirmation determination MT16 for confirming the navigation of the ship 31 will be described. The navigation support system 1 acquires data on the target ship 32 (step S1601). If "Maintain course and speed (Rule 17(a)(i))" is set in the applicable rule item, the navigation support system 1 determines whether a change in course or speed has been proposed (Yes in step S1602, step S1603).

[0192] If the navigation support system 1 determines that a change in course or speed has been proposed, it determines that the system is not COLREG compliant (Yes in step S1603), and if it determines that a change in course or speed has not been proposed, it determines that the system is COLREG compliant (No in step S1603).

[0193] If "Overtaking / giving vessel (Rule 13 and 16)" is set in the applicable rule item, the navigation support system 1 determines whether a course change due to overtaking is proposed (Yes in step S1604, step S1605).

[0194] If the navigation support system 1 determines that a course change due to overtaking has been proposed, it determines that the course is COLREG compliant (Yes in step S1605), and if it determines that a course change has not been proposed, it determines that the course is not COLREG compliant (No in step S1605).

[0195] If "Crossing (starboard side) / giving vessel (Rules 15 and 16)" is set in the applicable rule item, the navigation support system 1 determines whether a course change is proposed (Yes in step S1606, step S1607).

[0196] The navigation support system 1 determines that the course change is not COLREG compliant (No in step S1607, Yes in step S1607, Yes in step S1608) if it determines that no course change has been proposed, or that the course change would cross the bow of the other ship 32. The navigation support system 1 determines that the course change is COLREG compliant (Yes in step S1607, No in step S1608) if it determines that a course change that does not cross the bow of the other ship 32 has been proposed.

[0197] If "Meeting / Both Turn Starboard (Rule 14)" is set in the applicable rule item, the navigation support system 1 determines whether a course change is being proposed (Yes in step S1609, step S1610).

[0198] If the navigation support system 1 determines that no course change has been proposed, or if it determines that a course change has been proposed but that the course change will not pass the port side of the other ship 32, it determines that the COLREG is not compliant (No in step S1610, Yes in step S1610, No in step S1611).

[0199] When the navigation support system 1 determines that a course change to pass on the port side of the other ship 32 is proposed, it determines that the course is COLREG compliant (Yes in step S1610, Yes in step S1611).

[0200] If the navigation support system 1 determines that none of the above rules are set in the applicable rule item, it rejects the navigation confirmation judgment and executes an "OOW call." Note that the navigation support system 1 may execute an "OOW call" in unexpected cases where a judgment cannot be made in the above-mentioned optional processing.

[0201] A method for calculating the numerical values ​​used in the judgment will be described with reference to Figure 37. When judging the risk of collision using radar 21, first, the velocity vectors of the own ship 31 and the other ship 32 are obtained as numerical values ​​indicating the relative relationship between the own ship 31 and the other ship 32, with the own ship 31 as the origin on a polar coordinate system that indicates the direction clockwise, with the own ship's bow direction as the top (so-called "head up") or north as the top (so-called "north up") at 0°. In the past, the relative vectors were plotted on flat plotting paper, and then numerical values ​​used for collision avoidance judgment, such as CPA and BCR, were calculated using trigonometric functions, but in recent years, calculated values ​​have been displayed as a function of radar.

[0202] In the navigation support system 1, the position of the ship 31 at the time of calculation is set as the origin, and processing is performed as a straight line and coordinates on the x and y axes (units NM) set in north-up.

[0203] Specifically, the own ship coordinates (OS) and other ship coordinates (TV) are calculated by converting the latitude and longitude of each ship into x-y coordinates, with the own ship 31 at the time of judgment as the origin, and the navigation support system 1 calculates the coordinates of the future predicted point based on the ship speeds and elapsed time of the own ship 31 and ship 32 at that time.

[0204] The own ship velocity vector (vO) can be determined from the speed (SPD_O) and course (CRS_O) of the own ship 31 obtained from the navigation equipment, and the other ship velocity vector (vT) can be determined from the speed (SPD_T) and course (CRS_T) of the other ship. From these, the relative vectors (rvT, rvO) of the own ship 31 and the other ship 32 can be calculated.

[0205] The navigation support system 1 specifies the following lines by their slopes and intercepts, and specifies the coordinates of virtual points for making various decisions by the intersections of the lines. In addition to the CPA and BCR in each coordinate system, the navigation support system 1 also calculates the coordinates of the Abeam Crossing Range (ACR), which is the point where a line extending the relative vector crosses a line indicating the beam of the own ship 31 and the other ship 32 that is perpendicular to the bow heading.

[0206] Here, the rvT line is a line containing the relative vector rvT that passes through the other ship coordinates (TV), the cpaO line is a line that passes through the own ship coordinates (OS) and is perpendicular to the rvT line, the bcr line is a line that extends the bow-stern line of the own ship 31 or the other ship 32, and the acr line is a line that passes through the own ship coordinates (OS) or the other ship coordinates (TV) and is perpendicular to the bcr line.

[0207] CPA(O) is the point where the rvT line and the cpaO line intersect at right angles, and CPA is the distance from the ship's position to the intersection point CPA(O). BCR(O) is the intersection point of the rvT line and the bcrO line, and BCR is the distance from the ship's position to the intersection point BCR(O). If the intersection point is in the direction of the ship's bow, the other ship 32 will pass the ship's bow.

[0208] ACR(O) is the intersection of the rvT line and the acrO line, and if the intersection is on the side of the bcrO line rotated 90 degrees clockwise from the bow direction (starboard side), the other ship 32 will pass on the starboard side of the ship 31, and if the intersection is on the side rotated 90 degrees counterclockwise, the other ship 32 will pass on the port side of the ship 31.

[0209] Regarding whether or not they will cross the bow direction of the other ship 32, the answer is Yes if the intersection of the extension of the bcrT line of the other ship 32 and the rvO line including the relative vector rvO passing through the own ship's coordinates (OS) is in the bow direction.Regarding whether or not they will pass on the port side of each other's powered vessels, the answer is Yes if the intersection ACR(O) of the acrO line and the rvT line of the own ship 31 and the intersection ACR(T) of the acrT line and the rvO line of the other ship 32 are on their respective port sides.

[0210] Such an operation confirmation decision may be performed in advance for a series of checkpoints from the end of the avoidance to returning to the original course when the operation decision unit 131 formulates an operation plan related to the avoidance, or may be performed each time the operation at each checkpoint is transitioned to.

[0211] Regarding the course and speed of the other ship 32 at a future time, the above-mentioned values ​​are calculated based on the assumption that the current values ​​will be maintained. However, if it is possible to predict changes in the course and speed of the other ship 32 based on destination information obtained from the AIS 22, for example, the values ​​may be calculated including the predicted changes in course and speed.

[0212] Furthermore, by continuously checking the operation even during operation and continuously monitoring changes in each value, it is possible to quickly detect situations in which it becomes inappropriate to continue operation, for example, due to unexpected behavior by another ship 32.

[0213] Furthermore, as shown in the figure, by imagining a circle with its center at the own ship's coordinates (OS) and its radius at the CPA that will be the target after the course change, and finding the relative vector (rv'T) after the course change on a tangent that passes through the other ship's coordinates (TV), it is possible to find the angle at which the own ship's speed vector (vO) will rotate (changing course while maintaining speed). By adopting either of the two tangents that provide a solution and that conforms to the applicable rules as described above, it is also possible to find the desired course change angle.

[0214] In this way, the navigation support system 1 can easily perform calculations to confirm compliance with COLREG navigation based on the position of the intersection between the heading direction of the own ship 31 and the other ship 32, as well as a straight line extended in a direction perpendicular to the heading direction, and the intersection of these straight lines with the relative vector.

[0215] 38, a description will be given of the screen G18 of the user terminal 16 that displays the status of the watch execution unit 12. Note that the screen G18 described here is an image diagram showing one example, and the displayed content may be freely changed.

[0216] Screen G18 shows an example in which information about the own ship 31, an integrated target list, and information about a selected other ship 32 are displayed on the ECDIS 26. The integrated target list displays a list of additional information about multiple other ships 32. When another ship 32 is selected and highlighted from the list, an additional information window for only that one other ship 32 is displayed. Depending on the size of the electronic chart display screen, a list of multiple ships may not be displayed, and a window for each ship may be displayed.

[0217] The integrated target list can display the applicable rules and the determined rules. The applicable rules and the determined rules are estimated according to rule estimation logic based on the relative relationship between the own ship 31 and the target and the surrounding information. The information necessary to identify the relative relationship between the own ship 31 and the target and the surrounding information is included in the own ship setting data 113 and the situation awareness data 115.

[0218] Therefore, the navigation support system 1 can display operations and the basis for those decisions that comply with various rules that apply to the operation of the own ship 31, based on the own ship setting data 113 and the situation awareness data 115. Furthermore, when the own ship 31 is in the OOW call state ST12, the other ship 32 in question and the reason for the call may be displayed on a display screen that warns the user of the OOW call state ST12.

[0219] In addition, a function such as a trial maneuver installed in the radar 21 may be provided, and based on the operation determined by the operation determination unit 131 and confirmed by the operation confirmation unit 132, the future positional relationship between the own ship 31 and the other ship 32 may be calculated and displayed on the screen G18.

[0220] To ensure safe navigation, users are required to be familiar with existing navigation equipment. For example, the use of radar and ECDIS requires training and certification. This system also requires a training and education system for users to learn how to use it. In addition, after using the ACA for an extended period of time or before navigating an area requiring caution, it is necessary to confirm whether manual steering is possible. Such operating procedure manuals may be presented to users as electronic data by operating buttons or other devices on screen G18.

[0221] Use cases of the navigation assistance system 1 will be described with reference to Fig. 39. When the navigation assistance system 1 is used for automatic navigation, the following constraints must be taken into consideration in each of the cases shown in Fig. 19.

[0222] Case 1 is primarily intended for ocean voyages, with one or a small number of other ships 32 to consider. This is a situation in which course and speed changes, generally referred to as "avoidance," occur infrequently, and even if they do occur, early avoidance action is possible. While this can be handled using a rule set based on the above-described flowchart, it is necessary to appropriately execute an OOW call when the reliability of the watchkeeping execution unit 12 decreases.

[0223] Case 2 primarily assumes coastal navigation, where there are many other ships 32 and changes in course and speed for avoidance occur more frequently than in oceanic navigation. It is necessary to pay attention to the impact of avoidance actions on third ships so as not to approach new other ships 32 as a result of the avoidance actions. Furthermore, because there are often restrictions due to topography such as water depth, fishing gear, and navigational obstacles, nautical chart information must also be taken into account when avoiding collisions. Therefore, it is necessary to register a more detailed rule set linked to nautical chart information.

[0224] Case 3 primarily assumes congested waters, pilotage districts, and ports and bays. In addition to considering the impact on the third vessel and nautical chart information, the Maritime Traffic Safety Act, the Port Regulations Act, and other special rules apply. Not only does the number of other vessels 32 simply increase, but special actions, such as traffic separation schemes, course changes, and time adjustments to head to pilot stations, anchorages, and other special locations, also occur. Furthermore, because the area is coastal, there are a variety of vessels, including fishing boats, passing vessels, and workboats, increasing the number of situations in which the intentions of other vessels cannot be understood. Therefore, the number of other vessels 32 whose behavior is difficult to predict increases, and a detailed rule set, including special rules linked to nautical chart information, must be registered. Predicting the behavior of other vessels 32 requires not only information obtained from existing navigation equipment but also advanced judgment, including image recognition.

[0225] According to this embodiment, by using the navigation support system 1, the applicability and compliance of rules are determined based on the integrated target list, so that operations that comply with various rules that apply to the operation of the ship 31 and the basis for such determination can be clarified.

[0226] Furthermore, it becomes easy to determine an action that meets the conditions required by the rules applied to the ship 31 and to execute an avoidance action at an appropriate time after confirming compliance with the rules.

[0227] In addition, by detecting situations that cannot be described in the rule set, situations in which navigational watch cannot be continued automatically, and situations in which the reliability of surrounding situation data has decreased, and notifying the user of the detected situations, the user will be able to recognize situations in which a human response is required, thereby improving the safety of navigational watch operations.

[0228] It is to be understood that additional advantages and modifications may readily occur to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details and representative embodiments shown and described herein. Accordingly, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and their equivalents. < / s> < / s> < / s> < / s>

Claims

1. A rule estimation logic memory unit storing rule estimation logic for estimating the application relationship of rules to the operation of the ship; an own ship setting data memory unit storing own ship setting data including parameters indicating characteristics of the own ship; an own ship data acquisition unit for acquiring own ship data indicating information regarding the state of the own ship; a target data acquisition unit for acquiring target data indicating information regarding the state of a target; a surrounding data acquisition unit for acquiring surrounding data indicating information regarding the situation around the own ship; a situation awareness data generation unit for generating situation awareness data indicating a situation for determining the operation of the own ship, based on the own ship data acquired by the own ship data acquisition unit, the target data acquired by the target data acquisition unit, and the surrounding data acquired by the surrounding data acquisition unit; a relative relationship identification unit for identifying the relative relationship between the own ship and the target based on the situation awareness data generated by the situation awareness data generation unit; and a rule estimation unit for estimating an application rule to be applied to the own ship, based on the relative relationship identified by the relative relationship identification unit and the own ship setting data stored in the own ship setting data storage unit in accordance with the rule estimation logic stored in the rule estimation logic memory unit. A navigation support system comprising:

2. The navigation support system described in claim 1, characterized in that it comprises: an integrated target list memory unit that stores an integrated target list for managing integrated target data in which additional information used to estimate the application rule by the rule estimation unit is integrated into the target data acquired by the target data acquisition unit; an integrated target data creation unit that creates the integrated target data including the application rule estimated by the rule estimation unit; and an integrated target list update unit that updates the integrated target list stored in the integrated target list memory unit based on the integrated target data created by the integrated target data creation unit.

3. The navigation support system of claim 2, wherein the integrated target list update unit retains the applicable rule as a confirmed rule for a period during which it is deemed confirmed that the applicable rule is applied to the ship based on the additional information.

4. The navigation support system described in claim 3, characterized in that it is provided with an operation confirmation unit that confirms compliance of the own ship's operation, which is the operation of the own ship, with at least one of the fixed rules or common rules that are applied regardless of the situation of the own ship, based on the integrated target list stored in the integrated target list memory unit and the situation awareness data generated by the situation awareness data generation unit.

5. The navigation support system described in claim 3, characterized in that it is provided with an action determination unit that determines the ship's own action, which is the action of the ship, to avoid collision with the target based on the integrated target list stored in the integrated target list memory unit and the situation awareness data generated by the situation awareness data generation unit.

6. A navigation support system as described in claim 5, further comprising a preset scenario memory unit in which preset scenario data including one or more conditions for determining the ship's operation and the ship's operation according to each of the situations of a plurality of checkpoints is stored, and the operation determination unit includes determining the ship's operation based on the preset scenario data stored in the preset scenario memory unit.

7. A navigation support system as described in claim 5, further comprising a conversion dictionary memory unit storing conversion dictionary data for converting practical descriptions expressed in natural language into machine-readable descriptions that can be processed by a computer, and the operation determination unit includes determining the ship's own operation based on the conversion dictionary data stored in the conversion dictionary memory unit.

8. The navigation support system described in claim 4, characterized in that the additional information includes the time until the ship arrives and the estimated distance between the ship and the target at a number of specified points including the closest point of approach between the ship and the target, the point where the target crosses the ship's bow, and the point where the target crosses the ship's lateral direction, and the operation confirmation unit includes confirming the compliance based on the estimated distance included in the integrated target list stored in the integrated target list memory unit and the ship's setting data stored in the ship's setting data memory unit.

9. A navigation support system as described in claim 4, further comprising a rule set memory unit storing a rule set that defines a correspondence between parameters used in the rule estimation logic, visibility information indicating the visibility conditions around the ship, and water area information indicating the water area in which the ship is sailing, and the operation confirmation unit includes confirming compliance with a rule selected from a plurality of rules to be applied to the ship based on the rule set stored in the rule set memory unit.

10. The navigation support system described in claim 4, characterized in that the rule estimation logic memory unit stores rule estimation logic for estimating a holding rule when the own ship becomes a retained ship, and the operation confirmation unit includes confirming compliance with the holding rule when the own ship becomes the retained ship according to the confirmed rule.

11. The navigation support system described in claim 1, characterized in that the ship setting data includes user call conditions, and is further equipped with a user call processing unit that performs processing to notify a user terminal used by a user of a call when the user call conditions are met based on the situation awareness data generated by the situation awareness data generation unit.

Citation Information

Patent Citations

  • Sailing route generation device

    JP2021146778A

  • Collision avoidance route searching device, collision avoidance route searching support device, collision avoidance route searching method, collision avoidance route searching support method, and program

    JP2021160550A

  • Marine navigation support device, marine navigation support method, program

    JP2023013071A

  • Navigational aids

    JP6535896B2

  • Avoidance support device

    JP7069371B2