Systems and methods for vehicle pushback collision notification and avoidance

Abstract

This invention is entitled "System and Method for Vehicle Collision Notification and Avoidance". The invention discloses systems, methods, and non-transitory computer-readable media for vehicle collision notification and avoidance. A system may include attaching at least one camera to a vehicle and receiving vehicle information and geographic information about the vehicle and at least one other vehicle. The system may also include predicting the next position of the vehicle and the other vehicle, and determining whether the vehicle will collide with the other vehicle based on a comparison of the next position of the vehicle with the next position of the other vehicle. The system may also include generating a graphical representation of the collision between the vehicle and the other vehicle, and may transmit the graphical representation to a user device.

Description

Technical Field

[0001] Various embodiments of this disclosure generally relate to a service-oriented architecture for connecting vehicle rear-end collision notification and avoidance, and more specifically, to providing graphical or other notifications of potential collisions between vehicle maneuvers during ground operations. Background Technology

[0002] Airport gates and parking areas can be extremely congested, with both arriving and departing aircraft, and ground service vehicles and personnel serving and guiding them in and out of these areas. Avoiding collisions in these areas involves careful monitoring and control of the position and movement of aircraft and other vehicles as they maneuver within these zones. Pushback maneuvers can involve interactions or even collisions between personnel, aircraft, and / or equipment. Typically, an aircraft is pushed back using a trailer vehicle, and ground personnel assist the trailer driver in guiding the aircraft in reverse as it simultaneously turns to a position where it can start its engines and move forward onto the taxiway. At many (if not most) airports, the environment around the aircraft is monitored by these ground personnel and trailer drivers. These support personnel relay updates and statuses to the pilots via common visual signals and additional voice communications.

[0003] The background description provided in this invention is intended to give a general overview of the background of this disclosure. Unless otherwise specified by the invention, the materials described in this section are not prior art to the claims of this patent application and are not, by virtue of their inclusion in this section, acknowledged as prior art or suggestions of prior art. Summary of the Invention

[0004] According to certain aspects of this disclosure, systems and methods for providing vehicle push-back collision notification and avoidance via a connected service platform are disclosed.

[0005] In one embodiment, a computer-implemented method for vehicle collision notification and avoidance is disclosed. The method may include: establishing a field-of-view video of at least one camera coupled to a vehicle; transmitting the field-of-view video of the at least one camera coupled to the vehicle to a user equipment; receiving vehicle information about the vehicle; receiving other vehicle information about at least one other vehicle in the field-of-view video of the at least one camera coupled to the vehicle; receiving geographic information about the positions of the vehicle and the other vehicles; predicting the next position of the vehicle based on the vehicle information and the geographic information; predicting the next position of other vehicles based on the other vehicle information and the geographic information; determining whether the vehicle will collide with other vehicles based on a comparison of the next position of the vehicle with the next position of other vehicles; generating a graphical representation in the field-of-view video of the at least one camera coupled to the vehicle, wherein the graphical representation represents the collision of the vehicle with other vehicles; and transmitting the graphical representation of the collision of the vehicle with other vehicles to the user equipment.

[0006] According to another embodiment, a computer implementation system for vehicle collision notification and avoidance is disclosed. The computer implementation system may include a memory having processor-readable instructions stored therein; and at least one processor configured to access the memory and execute the processor-readable instructions, which, when executed by the processor, configure the processor to perform functions for: establishing a field-of-view video of at least one camera coupled to the vehicle; transmitting the field-of-view video of the at least one camera coupled to the vehicle to a user equipment; receiving vehicle information about the vehicle; and receiving information about the vehicle coupled to the vehicle. The system includes: receiving information about other vehicles in the field of view video of at least one camera; receiving geographic information about the positions of the vehicle and other vehicles; predicting the next position of the vehicle based on the vehicle information and geographic information; predicting the next position of other vehicles based on the information about other vehicles and geographic information; determining whether the vehicle will collide with other vehicles based on a comparison of the next position of the vehicle with the next position of other vehicles; generating a graphical representation in the field of view video of at least one camera coupled to the vehicle, wherein the graphical representation represents the collision of the vehicle with other vehicles; and transmitting the graphical representation of the collision of the vehicle with other vehicles to a user equipment.

[0007] According to another embodiment, a non-transitory computer-readable medium for vehicle collision notification and avoidance is disclosed. The non-transitory computer-readable medium may contain instructions for: establishing a field-of-view video of at least one camera coupled to a vehicle; transmitting the field-of-view video of the at least one camera coupled to the vehicle to a user equipment; receiving vehicle information about the vehicle; receiving other vehicle information about at least one other vehicle in the field-of-view video of the at least one camera coupled to the vehicle; receiving geographic information about the positions of the vehicle and other vehicles; predicting the next position of the vehicle based on the vehicle information and geographic information; predicting the next position of other vehicles based on the other vehicle information and geographic information; determining whether the vehicle will collide with other vehicles based on a comparison of the next position of the vehicle with the next position of other vehicles; generating a graphical representation in the field-of-view video of the at least one camera coupled to the vehicle, wherein the graphical representation represents the collision of the vehicle with other vehicles; and transmitting the graphical representation of the collision of the vehicle with other vehicles to the user equipment. Attached Figure Description

[0008] The accompanying drawings, which are incorporated in and form part of this specification, illustrate various exemplary embodiments and, together with the specification, serve to explain the principles of the disclosed embodiments.

[0009] Figure 1 An overview of a system for vehicle collision notification and avoidance according to one aspect of this disclosure is described.

[0010] Figure 2 An exemplary high-order system architecture for a collision notification and avoidance system according to one aspect of this disclosure is described.

[0011] Figure 3 A flowchart is depicted of an exemplary method for vehicle collision notification and avoidance according to one aspect of this disclosure.

[0012] Figure 4 An exemplary graphical display of a vehicle collision notification and avoidance system according to one aspect of this disclosure is depicted.

[0013] Figure 5 Exemplary computer devices or systems in which embodiments of the present disclosure or portions thereof may be implemented are shown. Detailed Implementation

[0014] As mentioned above, aircraft pushback maneuvers can involve interactions or even collisions between personnel, aircraft, and / or equipment. Given anticipated air traffic growth, it is necessary to analyze incidents involving collisions between a pushed aircraft and other moving or stationary objects operating on the airport tarmac to identify solutions for preventing aircraft pushback collisions.

[0015] This disclosure provides improvements to the vehicle pushback process. The vehicle pushback collision notification and avoidance system can be incorporated into an attachable and detachable camera system for improving pushback operations. The camera system can establish a wireless video feed to a monitoring device under the control of ground personnel, trailer vehicle drivers, or remote controllers to monitor the area surrounding the aircraft. The vehicle pushback collision notification and avoidance system may also include a ground-based collision avoidance algorithm using historical parking area pushback trajectory data and / or an airport surface model, and a forward positioning algorithm for predicting the future positions of various aircraft and objects on the airport apron.

[0016] The subject matter of this specification will now be described more fully below with reference to the accompanying drawings, which form part of the specification and illustrate specific exemplary embodiments by way of example. The description of the invention as “exemplary” embodiments or specific implementations should not be construed as being more preferred or advantageous than, for example, other embodiments or specific implementations; rather, it is intended to reflect or indicate that the one or more embodiments are one or more “exemplary” embodiments. The subject matter can be embodied in many different forms, and therefore the covered or claimed subject matter is intended to be construed as not being limited to any of the exemplary embodiments set forth in this invention; exemplary embodiments are provided merely for illustration. Likewise, the claimed or covered subject matter is intended to have a suitably broad scope. Among other things, for example, the subject matter can be embodied as a method, apparatus, component, or system. Therefore, embodiments can take the form, for example, hardware, software, firmware, or any combination thereof (other than software itself). Therefore, the following detailed description is not intended to be considered limiting.

[0017] Throughout the specification and claims, terms may have nuanced meanings as the context dictates or implies, in addition to their expressly stated meanings. Similarly, the phrase "in one embodiment" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment" as used herein does not necessarily refer to different embodiments. For example, the claimed subject matter is intended to include, in whole or in part, combinations of exemplary embodiments.

[0018] The terminology used below may be interpreted in its broadest and most reasonable manner, even when used in conjunction with specific embodiments of certain particular examples of this disclosure. Indeed, some terms may even be emphasized below; however, any term intended to be interpreted in any limited manner will be explicitly and specifically defined in this Detailed Description section. The foregoing general embodiments and the Detailed Description below are merely exemplary and illustrative, and not limited to the features protected by the claims.

[0019] In this disclosure, the term “based on” means “at least partially based on”. The singular forms “a,” “an,” and “the” include plural references unless the context otherwise indicates otherwise. The term “exemplary” is used in the sense of “example” rather than “ideal.” The term “or” is intended to be inclusive and means any, any, several, or all of the listed items. The terms “comprising,” “including,” “having,” “containing,” or other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, or product that includes the list of elements does not necessarily include only those elements but may include other elements not expressly listed or inherent to those processes, methods, articles, or devices. Relative terms (such as “substantially” and “largely”) are used to indicate possible variations of ±10% in stated or understood values.

[0020] Now refer to the attached diagram, Figure 1 An overview of a system 100 for vehicle collision notification and avoidance according to one aspect of this disclosure is provided. While the aircraft is referred to herein as an exemplary vehicle for the systems and methods described herein, it should be understood that this disclosure is not limited to aircraft and can be applied to other vehicles, such as freight trucks, buses, and / or other vehicles.

[0021] System 100 may include an aircraft 101, a pushback assist application 105, an attachable camera 110, ground personnel 115, a ground aircraft database 106, an airport information database 107, and an external information database 108. Ground personnel 115 may include ground crew walking alongside the aircraft during pushback operations, as well as trailer vehicle drivers. The ground aircraft database 106 may include position and velocity information about the target aircraft and other external aircraft and objects, aircraft structural information, aircraft safety zone radius information, and wingtip separation clearance distance information. The airport information database 107 may include airport surface models, obstacles, guideline markings, surface history trajectories, and performance data. The external information database 108 may store information related to aircraft pushback or taxiway / runway clearance information.

[0022] The attachable camera 110 can be one or more cameras that can be temporarily or at least removably coupled to any desired location on the aircraft. Alternatively, the attachable camera 110 can actually be a fixed camera integrated into the aircraft's fuselage as OEM equipment or as aftermarket equipment. While the attachable camera 110 can be coupled to any desired location on the aircraft, in one embodiment, the attachable camera 110 can be coupled to the rear of the aircraft by ground personnel. In one embodiment, multiple attachable cameras can be coupled to multiple locations outside the aircraft to cover the entire surrounding environment of the aircraft. For example, in one embodiment, one or more cameras 110 can be configured to capture a 360-degree view, and different types of cameras can be used. For example, RGB cameras, infrared (IR) cameras, thermal cameras, or RGB-D depth cameras can all be used individually or together coupled to the aircraft. The camera 110 may include a wireless communication unit for transmitting real-time captured video to a monitoring device or to a remote server. Ground personnel 115 may have equipment for receiving real-time captured video communications from the camera 110. Devices capable of receiving real-time captured video can include smartphones, laptops, tablets, desktop computers, and wearable devices such as smart glasses, virtual reality headsets, augmented reality headsets, and smartwatches.

[0023] As mentioned above, Figure 1 This is provided as an example only. Other examples are possible and can be found in the references. Figure 1 The examples described are different. Figure 1 The number and layout of the devices and networks shown are provided as examples. In reality, with... Figure 1 Compared to those shown, there may be additional devices, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged differently. Additionally or alternatively, a group of devices in environment 100 (e.g., one or more devices) may perform one or more functions described as being performed by another group of devices in environment 100.

[0024] Figure 2 An exemplary high-order system architecture environment 200 for a collision notification and avoidance system according to one aspect of this disclosure is depicted. Environment 200 may include a ground vehicle database 106, an airport information database 107, an external information database 108, a push-back collision avoidance system 210, and a display 215.

[0025] The rear-end collision avoidance system 210 may include an attachable camera system 211, a collision prediction module 212, a communication system 213, and a graphics processing module 214. The attachable camera system corresponds to... Figure 1The drawn module can attach a camera 110 and perform similar functions. The collision prediction module 212, communication system 213, and graphics processing module 214 can correspond to... Figure 1 The depicted push-assist application 105 includes a collision prediction module 212 that incorporates a collision prediction algorithm to predict potential collisions between the push-assist vehicle and other external obstacles. The collision detection algorithm uses both computer vision techniques and regression models to predict potential collisions between the push-assist vehicle and other aircraft and obstacles. Computer vision techniques utilize video feeds provided by an attachable camera system 211 to identify other aircraft and obstacles around the push-assist vehicle. For example, the attachable camera system 211 may be a set of RGB-D cameras, and the collision detection algorithm can use depth maps provided by this set of RGB-D cameras to accurately measure the relative distance to any potential obstacle. The collision detection algorithm can also utilize estimated depth maps obtained from computer vision techniques from a set of RGB cameras to measure the relative distance to any potential obstacle. The regression model can use vehicle or aircraft position information, wingtip separation clearance distance information and aircraft structure information, speed and airport surface model information from ground aircraft database 106, historical backward trajectory data of specific parking areas from airport information database 107 and aircraft permitted path information from external information database 108 to predict the position of the backward aircraft at time "t+δ", where "t" is the current time and "δ" is the advance time.

[0026] If a potential collision is detected between the rearward-pushing aircraft and other aircraft and obstacles, the collision prediction module 212 can generate an alarm. The alarm can be either an auditory alarm (such as a siren) or a visual alarm, or both. The visual alarm can be generated via the graphics processing module 214 and can be a tag fed by a real-time camera that identifies the threatening object, and the tag feed is transmitted to the display 215 via the communication system 213. Figure 2 The display 215 depicted can be a display for a device used by ground personnel 115. The marked video feed can be in the form of augmented reality or virtual reality and can be transmitted to a mobile or wearable device operated by ground personnel, or it can be transmitted as a heads-up display. The video feed may also include a navigation display that depicts the taxiways and routes that the aircraft can follow. Ground personnel can use the video feed to monitor the positions of other vehicles or aircraft and obstacles around the push-back aircraft, and guide the entire push-back operation.

[0027] In one embodiment, the collision prediction module 212 may be implemented at a server at the airport or at a remote server. In another embodiment, the collision prediction module 212 may be implemented at an end-user device, such as on a trailer-mounted vehicle, to avoid data transmission delays between the system or different geographical locations.

[0028] Figure 2 The number and arrangement of modules, devices, and networks shown are provided as examples. In reality, with... Figure 2 Compared to those shown, there may be additional modules and devices, fewer modules, devices and / or networks, different modules, devices and / or networks, or modules, devices and / or networks arranged differently. Furthermore, Figure 2 The environment 200 includes two or more devices that can be implemented within a single device, or Figure 2 A single device in environment 200 can be implemented as multiple distributed devices. Additionally or alternatively, a group of devices in environment 200 (e.g., one or more devices) can perform one or more functions described as being performed by another group of devices in environment 200.

[0029] Figure 3 A flowchart is depicted of an exemplary method 300 for vehicle collision notification and avoidance according to one aspect of this disclosure.

[0030] Exemplary method 300 begins at step 301, where a tow bar is attached to the aircraft at the start of the aircraft pushback operation. At step 302, a trailer vehicle is attached to the other side of the tow bar. At step 303, ground personnel can attach or fix one or more cameras to the aircraft to monitor the area around the aircraft. At step 304, communication can be established between the one or more cameras and the ground personnel and / or the trailer vehicle driver. At step 305, other ground vehicles and obstacles around the aircraft can be identified. Identification can be performed by ground personnel by marking the location of obstacles in a view feed, or identification can be performed by machine vision learning. At step 306, it can be determined whether an obstacle exists. If an obstacle exists, an operation check message can be sent to ground personnel at step 307, and the determination at step 306 is repeated. If no obstacle exists, the method proceeds to step 308 to determine whether the aircraft has received pushback clearance. If pushback clearance has not been received, pushback clearance is requested at step 309, and step 308 is repeated. If pushback clearance has been received, the method proceeds to step 310, where a real-time video feed from the coupled camera can be transmitted to an end-user system or device, such as equipment used by ground personnel or trailer vehicle drivers, or to cockpit equipment operated by the flight crew, or to a remote controller. At steps 311 and 312, terminal aircraft and vehicle position information, as well as surface guidance line information and historical track data, can be provided to determine the predicted positions of the aircraft and vehicles surrounding the pushback vehicle at step 313. If the aircraft does not transmit position information itself, the terminal aircraft and position information may include information transmitted by Automatic Dependent Monitoring Broadcast (ADS-B) and other trailer vehicles. The predicted positions can then be transmitted to the Automatic Collision Detection and Alarm Notification module at step 314, where the module executes a collision detection algorithm to determine if any collision is likely. Any collision can be determined by the module using a regression model to predict the next possible vehicle or aircraft position at “t+δ”. At step 315, if any collision is imminent, the collision area can be marked in the camera's video feed. The collision area can be marked with different colors, for example, a red shading. The collision area can also be marked with shapes, for example, a highlighted square frame. The collision area can also be marked with animation, for example, an animation of the aircraft collision can be drawn in a live feed. Then, at step 316, an augmented camera video feed indicating the collision area can be transmitted to a trailer driver assistance application residing in the trailer, and at step 317, the augmented camera video feed can be transmitted to a ground personnel application, for example, executed on a ground personnel device. At step 318, it can be determined whether the aircraft is aligned with the taxiway. If it is determined not to be aligned, the process can return to step 314 to continue determining whether any collision is imminent.If it is confirmed that the aircraft is aligned with the taxiway, the aircraft pushback operation can be completed. At step 319, ground personnel disconnect the camera system from the aircraft. At step 320, the aircraft can be disconnected from the tow bar and trailer, and the aircraft can continue with the takeoff operation.

[0031] Although Figure 3 An example block diagram is shown, but in some specific implementations, method 300 may include more than Figure 3 The blocks shown may contain more boxes, fewer boxes, different boxes, or boxes with different arrangements. Additionally or alternatively, two or more boxes of method 300 may be executed in parallel.

[0032] Figure 4 An exemplary high-order system architecture 400 of a collision notification and avoidance system according to one aspect of this disclosure is described.

[0033] Display 400 may include a trailer vehicle 401, an aircraft push-back trajectory path 402, and an aircraft direction 403. The aircraft is pushed back by the trailer vehicle 401, and display 400 may assist the trailer driver in reversing the aircraft's movement when the aircraft simultaneously turns to a position where it can start its engines and move forward onto a taxiway. Display 400 may display the aircraft push-back trajectory path 402 and aircraft direction 403 to the trailer driver via a real-time video feed provided by an attachable camera 110 for the trailer driver to follow. In one embodiment, for example during a push-back operation when ADS-B is off, the push-back aircraft may not broadcast position information; instead, the position of the push-back aircraft may be calculated based on information provided by a GPS receiver on the trailer vehicle. The information provided by the GPS receiver may include the trailer vehicle's speed, acceleration, and direction. A regression model may be used to pass the trailer vehicle information to collision prediction module 212 to predict the next possible position at time "t+δ", where "t" is the current time. In another implementation, the display 400 can use real-time video feeds from coupled cameras to construct a 360-degree view of the push-back aircraft's surroundings, providing warnings of any potential collisions as enhancements to the real-time video feeds. For example, green lines could be displayed to indicate safe distances from other obstacles, and red lines to indicate potential collisions. The trailer driver could then use the display 400 to assist in push-back maneuvers to avoid any possible collisions.

[0034] although Figure 4 An example of a user interface is shown, but in some specific implementations, the user interface 400 may have additional graphical objects, fewer graphical objects, or different graphical objects.

[0035] Figure 5A high-level functional block diagram of an exemplary computer device or system is depicted, wherein embodiments of this disclosure or portions thereof may be presented as, for example, computer-readable code. In some specific embodiments, a push-back assist application may correspond to device 500. Alternatively or additionally, a push-back collision avoidance system 210 may correspond to device 500. Furthermore, the above description is related to... Figures 1 to 4 Each of the exemplary computer server, database, user interface, module, and method described herein can be implemented in device 500 using hardware, software, firmware, a tangible computer-readable medium on which instructions are stored, or a combination thereof, and can be implemented in one or more computer systems or other processing systems. Figures 1 to 4 Each of the exemplary systems, user interfaces, and methods described herein.

[0036] If programmable logic is used, such logic can be executed on commercially available processing platforms or dedicated devices. Those skilled in the art will understand that various computer system configurations can be used to implement embodiments of the disclosed subject matter, including multi-core multiprocessor systems, minicomputers, mainframes, computers linked or clustered with distributed functions, and ubiquitous or microcomputers that can be embedded in virtually any device.

[0037] For example, at least one processor device and memory can be used to implement the above embodiments. The processor device can be a single processor, multiple processors, or a combination thereof. The processor device can have one or more processor "cores".

[0038] As mentioned above Figures 1 to 4 The various embodiments of this disclosure described in the examples can be implemented using device 500. After reading this specification, it will become apparent to those skilled in the art how to implement embodiments of this disclosure using other computer systems and / or computer architectures. Although operations may be described as sequential processes, some operations may actually be executed in parallel, concurrently, and / or in a distributed environment, wherein program code is stored locally and / or remotely for access by single-processor or multi-processor machines. Additionally, in some embodiments, the order of operations may be rearranged without departing from the substance of the disclosed subject matter.

[0039] like Figure 5As shown, device 500 may include a central processing unit (CPU) 520. CPU 520 can be any type of processor device, including, for example, any type of dedicated or general-purpose microprocessor device. Those skilled in the art will understand that CPU 520 can also be a single processor in a multi-core / multi-processor system (such systems operate individually) or in a cluster of computing devices operating in a cluster or server farm. CPU 520 can be connected to data communication infrastructure 510, such as a bus, message queue, network, or multi-core messaging scheme.

[0040] Device 500 may also include main memory 540, such as random access memory (RAM), and may also include secondary memory 530. Secondary memory 530 (e.g., read-only memory (ROM)) may be, for example, a hard disk drive or a removable storage drive. Such removable storage drives may include, for example, floppy disk drives, magnetic tape drives, optical disk drives, flash memory, etc. In this example, the removable storage drive reads from and / or writes to the removable storage unit in a well-known manner. The removable storage unit may include floppy disks, magnetic tapes, optical disks, etc., read from and written to by the removable storage drive. Those skilled in the art will understand that such removable storage units generally include computer-usable storage media in which computer software and / or data are stored.

[0041] In an alternative embodiment, auxiliary memory 530 may include other similar means that allow computer programs or other instructions to be loaded into device 500. Examples of such means may include program cartridge memory and cartridge memory interface (such as those present in video game devices), removable memory chips (such as EPROM or PROM) and associated sockets, and other removable memory units and interfaces that allow software and data to be transferred from removable memory units to device 500.

[0042] Device 500 may also include a communication interface (“COM”) 560. Communication interface 560 allows software and data to be transferred between device 500 and external devices. Communication interface 560 may include a modem, network interface (such as an Ethernet card), communication port, PCMCIA slot, and card, etc. Software and data transmitted via communication interface 560 may be in the form of signals, which may be electronic, electromagnetic, optical, or other signals that can be received by communication interface 560. These signals may be provided to communication interface 560 via a communication path of device 500, which may be implemented using, for example, wires or cables, optical fibers, telephone lines, cellular telephone links, RF links, or other communication channels.

[0043] The hardware components, operating system, and programming language of such devices are essentially conventional, and are therefore presumed to be sufficiently familiar to those skilled in the art. Device 500 may also include input and output ports 550 for connection to input and output devices such as keyboards, mice, touchscreens, monitors, displays, etc. Of course, various server functions can be implemented in a distributed manner on multiple similar platforms to distribute the processing load. Alternatively, these servers can be implemented through appropriate programming of a single computer hardware platform.

[0044] The systems, apparatuses, devices, and methods disclosed herein are described in detail by way of example with reference to the accompanying drawings. The examples discussed herein are merely illustrative and are provided to aid in the explanation of the apparatuses, devices, systems, and methods described herein. Any feature or component shown in the drawings or discussed below should not be considered mandatory for any particular implementation of any of these apparatuses, devices, systems, or methods unless expressly stated otherwise. For ease of reading and clarity, certain components, modules, or methods may be described only in conjunction with the specific drawings. Any indication of specific techniques, arrangements, etc., in this disclosure is either related to the specific example presented or is merely a general description of such techniques, arrangements, etc. The indication of specific details or examples is not intended to be, and should not be construed as, mandatory or limiting unless expressly stated otherwise. Any instance where a combination or sub-combination of components is not explicitly described should not be construed as indicating that any combination or sub-combination is impossible. It should be understood that modifications may be made to the disclosed and described examples, arrangements, configurations, components, elements, apparatuses, devices, systems, methods, etc., and may be necessary for the specific patent application. Furthermore, for any of the methods described, whether or not the method is described in conjunction with a flowchart, it should be understood that, unless the context otherwise indicates or requires, any explicit or implicit ordering of the steps performed during the execution of the method does not mean that these steps must be performed in the proposed order, but may be performed in a different order or in parallel.

[0045] Throughout this disclosure, references to components or modules generally refer to objects that can be logically combined to perform a function or a set of related functions. Similar reference numerals are generally intended to refer to the same or similar components. Components and modules may be implemented in software, hardware, or a combination of software and hardware. The term "software" is used broadly to include not only executable code such as machine-executable or machine-interpretable instructions, but also data structures, data storage, and computational instructions stored in any suitable electronic format, including firmware and embedded software. The terms "information" and "data" are used extensively and include a wide variety of electronic information, including executable code; content such as text, video data, and audio data, etc.; and various codes or tags. The terms "information," "data," and "content" are sometimes used interchangeably when the context permits.

[0046] The description and examples are intended to be illustrative only, and the true scope and substance of this disclosure are indicated by the following claims.

Claims

1. A computer-implemented method for vehicle collision notification and avoidance, the method comprising: Receive the field-of-view video from at least one camera coupled to the vehicle; The field-of-view video of the at least one camera coupled to the vehicle is transmitted to the user equipment; Receive vehicle information about the vehicle from the at least one camera or one or more databases; Receive other vehicle information from the at least one camera or one or more databases, the other vehicle information relating to at least one other vehicle in the field of view video of the at least one camera coupled to the vehicle; Receive geographic information about the location of the vehicle and the other vehicles from the at least one camera or one or more databases; The vehicle's next location is predicted based on the vehicle information and the geographic information. The next location of the other vehicles is predicted based on the other vehicle information and the geographical information; Whether the vehicle will collide with the other vehicles is determined based on a comparison of the vehicle's next position with the next positions of the other vehicles; A graphical representation is generated in the field-of-view video of the at least one camera coupled to the vehicle, wherein the graphical representation shows the collision between the vehicle and the other vehicles; as well as The graphical representation of the collision between the vehicle and the other vehicles is transmitted to the user equipment. Predicting the next location of the vehicle and the other vehicles involves using computer vision and regression models.

2. The computer implementation method of claim 1, wherein the at least one camera is removably coupled to the vehicle, and the at least one camera coupled to the vehicle is selected from RGB cameras, IR cameras, thermal cameras, and RGB-D cameras.

3. The computer implementation method according to claim 1, wherein the vehicle information and the other vehicle information include at least one of position information, speed information, aircraft structure information, aircraft safety zone radius ring information, and wingtip separation gap distance information.

4. The computer implementation method of claim 1, wherein the location of the vehicle is obtained from a GPS receiver on the vehicle or a trailer vehicle connected to the vehicle.

5. The computer implementation method according to claim 1, wherein the geographic information includes at least one of aircraft taxiway permitted path, airport surface guidance line information, historical retrospective trajectory information, and airport surface information.

6. The computer implementation method according to claim 1, wherein the user equipment is one of a smartphone, laptop computer, tablet computer, desktop computer, smart glasses, virtual reality headset, augmented reality headset, and smartwatch.

7. A computer-implemented system for vehicle collision notification and avoidance, the computer-implemented system comprising: A memory having processor-readable instructions stored therein; and At least one processor is configured to access the memory and execute processor-readable instructions, which, when executed by the processor, configure the processor to perform functions for the following operations: Receive the field-of-view video from at least one camera coupled to the vehicle; The field-of-view video of the at least one camera coupled to the vehicle is transmitted to the user equipment; Receive vehicle information about the vehicle from the at least one camera or one or more databases; Receive other vehicle information from the at least one camera or one or more databases, the other vehicle information relating to at least one other vehicle in the field of view video of the at least one camera coupled to the vehicle; Receive geographic information about the location of the vehicle and the other vehicles from the at least one camera or one or more databases; The vehicle's next location is predicted based on the vehicle information and the geographic information. The next location of the other vehicles is predicted based on the other vehicle information and the geographical information; Whether the vehicle will collide with the other vehicles is determined based on a comparison of the vehicle's next position with the next positions of the other vehicles; A graphical representation is generated in the field-of-view video of the at least one camera coupled to the vehicle, wherein the graphical representation shows the collision between the vehicle and the other vehicles; as well as The graphical representation of the collision between the vehicle and the other vehicles is transmitted to the user equipment. Predicting the next location of the vehicle and the other vehicles involves using computer vision and regression models.

8. The computer-implemented system of claim 7, wherein the at least one camera coupled to the vehicle is selected from RGB cameras, IR cameras, thermal cameras, and RGB-D cameras.

9. The computer-implemented system according to claim 7, wherein the vehicle information and the other vehicle information include at least one of position information, speed information, aircraft structure information, aircraft safety zone radius ring information, and wingtip separation gap distance information.

Images