System and method for managing airfield lighting

Abstract

A system for integrating a plurality of incompatible ALCMSs into a unified ILCMS is disclosed. The system comprises a plurality of LECUs configured to interface with a plurality of LEs installed along an airfield. The system comprises a plurality of MCUs communicatively coupled to the plurality of LECUs. The system comprises a processor communicatively coupled to the plurality of MCUs and configured to determine an operational status of one or more LEs based on operational data received from the corresponding one or more MCUs, generate a unified representation of the operational status of the one or more LEs, and transmit one or more control signals to the corresponding one or more MCUs based on the operational status of one or more LEs. The system comprises a unified GUI configured to display the unified representation and enable user-initiated control of the one or more LEs across the plurality of incompatible ALCMSs.

Description

10259W0017SYSTEM AND METHOD FOR MANAGING AIRFIELD LIGHTING FIELD OF THE INVENTION

[0001] The present disclosure generally relates to the field of airfield lighting systems. More particularly, the present disclosure discloses a method and system for integrating a plurality of incompatible Airfield Lighting Control And Monitoring Systems (ALCMSs) into a unified Individual Lamp Control And Monitoring System (ILCMS).BACKGROUND

[0002] Airfield lighting systems are essential infrastructure components at airports, providing critical visual guidance for aircraft during takeoff, landing, and ground movement. The airfield lighting systems are designed to enhance safety and operational efficiency under various weather conditions and in low-visibility environments, such as fog, rain, or nighttime operations. Properly configured airfield lighting is crucial to ensuring aircraft’s safe navigation on runways, taxiways, and approach paths. As such, aviation authorities require specific lighting patterns and intensities for different phases of airport operations, ensuring standardized safety protocols across all airport facilities.

[0003] Airfield Lighting Control and Management System (ALCMS) serves as the backbone of airfield lighting infrastructure. The primary function of ALCMS is to enable precise control and management of the lighting systems throughout the airport. ALCMSs are responsible for controlling runway lights, taxiway lights, approach lights, and other airfield lighting elements, ensuring they meet operational demands in real-time. The ALCMSs use advanced technologies such as automated monitoring, remote management, and real-time data analytics to adjust lighting configurations as needed in response to changing weather, flight schedules, and operational requirements. In addition to improving safety, ALCMS optimizes energy usage and contributes to the sustainability goals of modem airports by reducing power consumption and minimizing operational costs.

[0004] A more advanced version of ALCMS is an Individual Lighting Control and Management System (ILCMS). ILCMS is required to meet the higher operational standards set by aviation authorities for Category II (CAT II) and Category III (CAT III) operations. ILCMS integrates and centralizes control10259W0017 functions, offering airports the ability to monitor and manage all lighting circuits across the airfield from a single platform. ILCMS ensures seamless operation under low-visibility conditions, making it essential for airports looking to expand their operational capacity and meet stringent safety regulations. The transition to ILCMS from conventional ALCMS allows for more efficient, reliable, and automated lighting management, which supports continuous operations even in challenging weather conditions.

[0005] Despite the numerous advantages of ALCMS and ILCMS, challenges persist due to the lack of interoperability among systems from different vendors. Airports often operate ALCMS from multiple manufacturers, resulting in fragmented and incompatible infrastructures. A typical ALCMS configuration includes Constant Current Regulators (CCRs) that supply power to airfield lamp fittings via physical electrical circuits. These CCRs are generally maintained separately and do not integrate easily with systems from different vendors. As a result, upgrading to a unified ILCMS is difficult and costly.

[0006] Further, upgrading from traditional, incompatible ALCMS to a unified ILCMS requires a complete overhaul of existing systems, including the replacement of CCRs and electrical circuits. This upgrading process not only incurs significant costs but also leads to operational downtime, which disrupts airport functions and can affect safety. Airports that cannot upgrade to ILCMS are limited to performing Category I (CAT I) operations, restricting their ability to conduct operations in low-visibility conditions. Given the regulatory requirements for CAT II and CAT III operations, the transition to ILCMS has become an urgent priority for airports seeking to comply with these standards and ensure the continued safety and efficiency of airfield operations.

[0007] Therefore, there is a need for solutions that can enable interoperability between existing ALCMS and facilitate the transition to ILCMS without incurring prohibitive costs, operational delays, or infrastructure overhauls.SUMMARY

[0008] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the invention. This summary is neither intended to identify key or essential inventive10259W0017 concepts of the invention nor is it intended for determining the scope of the invention.

[0009] According to one embodiment of the present disclosure, a system for integrating a plurality of incompatible Airfield Lighting Control And Monitoring Systems (ALCMSs) into a unified Individual Lamp Control And Monitoring System (ILCMS) is disclosed. The system comprises a plurality of Lighting Element Control Units (LECUs) configured to interface with a plurality of Lighting Elements (LEs) installed along an airfield. One or more LEs from the plurality of LEs are associated with an ALCMS from among the plurality of incompatible ALCMSs. The plurality of LECUs are a part of the unified ILCMS. The system further comprises a plurality of Master Control Units (MCUs) communicatively coupled to the plurality of LECUs. Each MCU is a part of the unified ILCMS and is configured to receive operational data from and transmit one or more control signals to the plurality of LECUs associated with the unified ILCMS. The system further comprises a processor communicatively coupled to the plurality of MCUs. The processor is configured to determine an operational status of one or more LEs from among the plurality of LEs based on the operational data received from the corresponding one or more MCUs. The processor is further configured to generate a unified representation of the operational status of the one or more LEs. The processor is further configured to transmit the one or more control signals to the corresponding one or more MCUs based on the operational status of one or more LEs. The system further comprises a unified Graphical User Interface (GUI) configured to display the unified representation and enable user- initiated control of the one or more LEs across the plurality of incompatible ALCMSs. The unified GUI translates heterogeneous communication protocols associated with the plurality of incompatible ALCMSs into a unified command protocol.

[0010] According to another embodiment of the present disclosure, a method for integrating a plurality of incompatible Airfield Lighting Control And Monitoring Systems (ALCMSs) into a unified Individual Airfield Lighting Control And Monitoring System (ILCMS) is disclosed. The method includes interfacing a plurality of Lighting Element Control Units (LECUs) with a plurality of Lighting Elements (LEs) installed along an airfield. One or more LEs from the plurality of10259W0017LEs are associated with an ALCMS from among the plurality of incompatible ALCMSs. The plurality of LECUs are a part of the unified ILCMS. The method further comprises communicatively coupling a plurality of Master Control Units (MCUs) to the plurality of LECUs. Each MCU is part of the unified ILCMS and configured to receive operational data from and transmit one or more control signals to the plurality of LECUs associated with the unified ILCMS. The method also comprises determining, by a processor communicatively coupled to the plurality of MCUs, an operational status of one or more LEs from among the plurality of LEs based on the operational data received from the corresponding one or more MCUs. The method further comprises generating, by the processor, a unified representation of the operational status of the one or more LEs. The method comprises transmitting, by the processor, one or more control signals to the corresponding MCUs based on the operational status of the one or more LEs. The method comprises displaying, via a unified Graphical User Interface (GUI), the unified representation. The method further comprises enabling, via the unified GUI, user-initiated control of the one or more LEs across the plurality of incompatible ALCMSs. The unified GUI translates heterogeneous communication protocols associated with the plurality of incompatible ALCMSs into a unified command protocol.

[0011] To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail in the accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:10259W0017

[0013] FIG. 1 illustrates an environment for managing airfield lighting, according to an embodiment of the present disclosure;

[0014] FIG. 2A illustrates a schematic diagram of a system for integrating a plurality of incompatible Airfield Lighting Control And Monitoring Systems (ALCMSs) into a unified Individual Lamp Control And Monitoring System (ILCMS), according to an embodiment of the present disclosure;

[0015] FIG. 2B illustrates a block diagram of the system for integrating the plurality of incompatible ALCMSs into the unified ILCMS 214, according to an embodiment of the present disclosure;

[0016] FIG. 3 illustrates a block diagram of a processing unit of the system, according to an embodiment of the present disclosure; and

[0017] FIGs. 4A-4B illustrate flowcharts depicting a method for integrating the plurality of incompatible ALCMSs into the unified ILCMS 214, according to an embodiment of the present disclosure.

[0018] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.DETAILED DESCRIPTION

[0019] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the various embodiments, and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the10259W0017 principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.

[0020] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the invention and are not intended to be restrictive thereof.

[0021] Reference throughout this specification to “an aspect,” “another aspect” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase “in an embodiment,” “in another embodiment” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0022] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by “comprises... a” does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.

[0023] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as not to unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term “or” as used herein, refers to a non-exclusive or unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the10259W0017 embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0024] As is traditional in the field, embodiments may be described and illustrated in terms of blocks that carry out a described function or functions. These blocks, which may be referred to herein as units or modules or the like, are physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware and software. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the invention. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the invention.

[0025] The accompanying drawings are used to help easily understand various technical features, and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.

[0026] FIG. 1 illustrates an environment 100 for managing airfield lighting 104, according to an embodiment of the present disclosure.

[0027] In an embodiment, the environment 100 may be an airfield environment. The airfield environment may be a designated area of land for operations of an aircraft 110, including takeoff, landing, and ground movement. The environment 100 may include a runway for takeoff and landing operations of the aircraft 110, a taxiway for ground movement between the runway and terminal areas of the aircraft 110, and apron areas for parking and servicing of the aircraft 110. The environment 100 may provide navigation guidance for the aircraft 110 during various phases of operations of the aircraft 110.10259W0017

[0028] The environment 100 may further include airfield lighting 104. The airfield lighting 104 may be associated with a lighting infrastructure installed across the airfield environment. The airfield lighting 104 may provide visual guidance to aircraft pilots during low visibility conditions. The airfield lighting 104 may facilitate safe aircraft operations during nighttime and adverse weather conditions. The airfield lighting 104 may include a plurality of Lighting Elements (LEs) 106 (also referred to as LEs 106). The plurality of LEs 106 may be individual lighting units distributed throughout the airfield environment. The plurality of LEs 106 may include, but is not limited to, runway edge lights, taxiway lights, approach lights, and threshold lights. The plurality of LEs 106 may provide directional guidance and boundary marking for aircraft’s movements. The plurality of LEs 106 may operate at different brightness intensities based on visibility conditions and operational requirements.

[0029] In an embodiment, an operational status may be associated with each LE among the plurality of LEs 106. The operational status may indicate a current functional status of the LE. The operational status may include, but is not limited to, an active state, an inactive state, a dimmed state, and a fault state. Each LE may be configured to operate at multiple brightness intensity levels. The multiple brightness intensity levels may comply with International Civil Aviation Organization (ICAO) standards. The brightness intensity levels may range from high intensity for low visibility conditions to low intensity for normal visibility conditions. The plurality of LEs 106 may guide aircraft pilots through visual indication of safe operational paths within the airfield environment.

[0030] In an embodiment, the operational status of the plurality of LEs 106 may be controlled by an Individual Lamp Control And Monitoring System (ILCMS) server 102. The ILCMS server 102 may be an airfield control and monitoring server. The ILCMS server 102 may be a centralized control unit for airfield lighting management. The ILCMS server 102 may determine appropriate lighting configurations based on at least one of the current weather conditions, visibility levels, and air traffic requirements. The ILCMS server 102 may interface with Air Traffic Control (ATC) (not shown) to receive operational directives. The ILCMS server 102 may generate lighting control commands for specific operational scenarios. For example, the ILCMS server 102 may activate high-intensity runway10259W0017 lights during low visibility approaches and may dim taxiway lights during normal visibility conditions.

[0031] In an embodiment, the environment 100 may include a system 108 for integrating a plurality of incompatible Airfield Lighting Control And Monitoring Systems (ALCMSs) into a unified ILCMS 214. In an embodiment, the system 108 may be implemented in the environment 100.

[0032] Detailed implementation of the system 108 is described in subsequent paragraphs in reference to FIGs. 2A, 2B, and 3.

[0033] FIG. 2A illustrates a schematic diagram 200A of the system 108, according to an embodiment of the present disclosure.

[0034] In an embodiment, the system 108 may include a plurality of Lighting Element Control Units (LECUs) 202 (also referred to as LECUs 202). The plurality of LECUs may be configured to interface with the plurality of LEs 106. In particular, each of the LECUs 202A-202N among the LECUs 202 may be electrically connected to a corresponding LE 106A-1, or 106A-2, 106A-3 ... 106A- N. Further, it can be noted that the plurality of LEs 106 may include LE 106A-1- 106A-N, one or more LEs 106B, and one or more LEs 106C.

[0035] In an embodiment, the plurality of LEs 106 may be associated with the plurality of incompatible ALCMSs. For example, one or more LEs, such as LE 106A-1 to 106A-N, may be associated with ALCMS 1 from among the plurality of incompatible ALCMSs. Similarly, the one or more LEs 106B may be associated with ALCMS 2 from among the plurality of ALCMSs. The one or more LEs 106C may be associated with ALCMS 3 from among the plurality of ALCMSs. It can be noted that the plurality of incompatible ALCMSs, such as ALCMS 1, ALCMS 2, and ALCMS 3, may belong to different manufacturers. Accordingly, the plurality of ALCMSs may operate using different protocols and / or hardware configurations, making them inherently incompatible. Accordingly, in an embodiment, the system 108 is configured to integrate the plurality of incompatible ALCMSs into the unified ILCMS 214. Accordingly, each of the LECUs 202 may be a part of the unified ILCMS 214. Each LECU 202A-202N among the LECUs 204 may be configured to control the corresponding LE 106A- 1, or 106A-2, or 106A-3 ..., 106A-N. Each LECU 202A-202N among the LECUs10259W0017202 may be configured to monitor the operational state of the corresponding LE 106A-1-106A-N. Each of the LECUs 202 may collect operational data from the corresponding LE 106. The operational data may be used to determine the operational status of the corresponding LE 106. It should be noted that although the LECUs corresponding to LEs 106A-1-. . . 106A-N are shown in FIG. 2A, LEs 106B and 106C may also have corresponding LECUs (not shown). Such LECUs may be connected to LEs 106B and 106C in the same manner as LECUs 202 are connected to LE 106 A.

[0036] Further, the LECUs 202 may receive electrical power through High Voltage (HV) power supply. The HV power may provide the electrical energy required for the operation of the plurality of LEs 106.

[0037] In an embodiment, the system 108 may include a plurality of Master Control Units (MCUs) 204 (herein referred to as MCUs 204). Each of the MCUs 204 may be coupled to the LECUs 202. Each of the MCU 204A, 204B, . . .204M may be a part of the unified ILCMS 214. In an embodiment, the number of MCUs 204 may be equal to a number of LECUs 202. Accordingly, each of the LECUs 202 may be associated with an MCU from the MCUs 204. In another embodiment, the number of MCUs 204 may be different from the number of LECUs 202. Accordingly, one or more LECUs from among the LECUs 202 may be associated with one MCU from among the MCUs 204. Further, each of the MCUs 204A- 204M may be configured to receive the operational data from the corresponding one or more LECUs. Further, each of the MCUs 204A-204M may be configured to transmit one or more control signals to the corresponding one or more LECUs to control the one or more LEs 106.

[0038] The MCUs 204 may be configured to transmit the one or more control signals to a server switch 208 via a field switch 206. In an embodiment, the server switch 208 may be a centralized network switch integrated within a server or control infrastructure. For example, the server switch 208 is integrated within a Constant Current Regulator (CCR) Room 212 or Air Traffic Control (ATC) 210 that manages data communication between an ILCMS server 102, the system 108, and the MCUs 204.10259W0017

[0039] In an embodiment, the field switch 206 may be a network switch deployed in the airfield, typically near the plurality of LEs 106. The field switch 206 ensures that data from the LECUs 202 and the MCUs 204 is routed through the network for centralized monitoring. The field switch 206 ensures that data packets from each of the MCUs 204 are correctly forwarded to the ILCMS server 102 without delays or interference.

[0040] The ILCMS server 102 may be implemented at the ATC 210. The ATC 210 may be a facility responsible for directing aircraft movement within controlled airspace and on airport surfaces. The ATC 210 may coordinate aircraft takeoff, landing, and ground movement operations to ensure aviation safety. The MCUs 204 may be connected to the ILCMS server 102 through network infrastructure, including Optical Fiber Channel (OFC). The MCUs 204 may connect to the field switch 206 through OFC. The field switch 206 may connect to the server switch 208 through an additional OFC. The network infrastructure may enable data transmission between the system 108 and the ILCMS server 102.

[0041] Further, CCR Room 212 may connect to the system 108 through Category 6 (CAT6) network infrastructure. The CCR Room 212 may be a centralized facility for monitoring and controlling multiple airfield operations. The CCR Room 212 may include one or more CCRs. The one or more CCRs may act as a power source for the LEs. The one or more CCRs may be controlled through the ILCMS server 102 to change the intensity of various LEs.

[0042] The system 108 may further include a unified Graphical User Interface (GUI) 214A. The unified GUI 214A may be configured to display a unified representation and enable user-initiated control of the plurality of LEs 106 across the plurality of incompatible ALCMSs.

[0043] In an embodiment, the unified GUI 214A and the ILCMS server 102 may form the unified ILCMS 214. In an embodiment, the ILCMS server 102 may host the unified GUI 214A to control and monitor all the LEs. In an embodiment, failure of individual LE needs to be immediately addressed and fixed in the least possible time during CAT II and CAT III operations. Further, dual LE failure results in a downgrade of operational status from CAT III and CAT II to CAT I operation. With dual adjacent LE failures in the airfield lighting system, the airport10259W0017 is not allowed to operate under the CATIII procedure. The airport has to be immediately downgraded and CATIII operations suspended until the lamp failures can be addressed. The unified ILCMS 214 may identify the location of the failed LE. The unified ILCMS 214 may also alert ATC and operations personnel regarding LE failures in CAT III and CAT II conditions so that immediate actions can be taken by airport personnel. The unified GUI 214A may control the LEs in terms of their ON and OFF states by sending packet-based control messages to the various LEs. Periodically, the LE may send back its current state to the ILCMS server 102, as the ILCMS server 102 keeps track of the latest state of all LEs in the airfield lighting system.

[0044] In an embodiment, the MCUs 204 may be configured to be connected to the LECUs 202 over one or more communication channels. The one or more communication channels may be communication pathways for data transmission between the MCUs 204 and the LECUs 202. The one or more communication channels may include a Power-Line-Communication (PLC) channel and a wireless communication channel. The PLC channel may be a communication medium that utilizes existing electrical power lines for data transmission. The PLC channel may enable communication over the same electrical infrastructure that provides power to the plurality of LEs 106. The PLC channel may provide a reliable communication path without requiring additional cable infrastructure. The PLC channel may utilize a narrow band PLC technology or a mid-range band PLC technology for long-range communication. In an exemplary embodiment, the PLC channel may be configured to support physical data rates up to 300 kilobytes per second (kbps). The wireless communication channel may utilize a radio frequency-based communication medium. The wireless communication channel may operate without physical cable connections between the MCUs 204 and the LECUs 202. The wireless communication channel may correspond to a sub-Giga Hertz (GHz) radio frequency communication channel, i.e., the data transmission on the wireless communication channel may utilize radio frequency waves with a frequency in a range of 865 Mega Hertz (MHz) to 870 MHz.

[0045] Accordingly, the one or more communication channels may be configured to be established between the MCUs 204 and the LECUs 202. The one10259W0017 or more communication channels may provide redundant communication paths for enhanced system reliability.

[0046] In an embodiment, the MCUs 204 and the LECUs 202 may be configured to be connected in a mesh configuration. The mesh configuration may provide multiple interconnected communication paths between the LECUs 202. The mesh configuration may enable direct communication between any two LECUs among the LECUs 202. In an advantageous aspect, the mesh configuration may provide enhanced network resilience through alternative communication routes in case of individual link failures.

[0047] Further operational details of the system 108 are described in reference to FIGs. 2B-3.

[0048] FIG. 2B illustrates an exemplary schematic diagram 200B of the system 108, according to an embodiment of the present disclosure.

[0049] As shown, in an exemplary embodiment, the LCEUs 202 may be connected to the LEs 106A-1 to 106A-N. The LECUs 202 may directly control the operation of various airfield lighting fixtures. For example, if an aircraft is scheduled to land on a runway during low visibility, the LECUs 202 may ensure that the corresponding LEs are powered on and functioning at the correct intensity, based on the aircraft’s proximity. The LECUs 202 can also adjust light intensity based on weather conditions, such as fog, ensuring that the lights are sufficiently bright for safe navigation. In an embodiment, the LECUs 202 may be spatially distributed across the airfield environment in proximity to the corresponding LEs 106. Each LECU among the LECUs 202 may be positioned adjacent to or within the immediate vicinity of the corresponding LE.

[0050] The LECUs 202 may be connected with the MCUs 204. The MCUs 204 may act as a control center for the lighting system and manage real-time data exchange. The MCUs 204 may be positioned within the airfield environment to enable communication with the LECUs 202. The MCUs 204 may be centrally located within the airfield environment to optimize communication range with the distributed LECUs 202. The MCUs 204 may be housed in a control building or electrical substation facility within the airfield environment. The MCUs 204 may10259W0017 be configured to be connected to the LECUs 202 over one or more communication channels.

[0051] In an embodiment, the LCEUs 202 and the MCUs 204 may communicate via a communication network interface 216. The communication network interface 216 may facilitate data exchange among the LECUs 202 and the MCUs 204 using a common communication protocol. The communication network interface 216 may include at least one of a wired network and a wireless network. For example, the wired network may include, but is not limited to, the PLC, OFC, and CAT6. The wireless network may include, but is not limited to, a sub-GHz radio frequency communication channel.

[0052] In an embodiment, the system 108 may further comprise a processing unit 218. The processing unit 218 has been further explained in reference to FIG. 3.

[0053] In an embodiment, the system 108 may be implemented with the ILCMS server 102.

[0054] FIG. 3 illustrates a block diagram of a processing unit of the system, according to an embodiment of the present disclosure.

[0055] As shown, the processing unit 218 may include, but is not limited to, a processor 302, a memory 304, a data unit 306, and modules 308. The modules 308 may be coupled to the processor 302 and the memory 304.

[0056] The processor 302 may be a single processing unit or several units, wherein all units may include multiple computing units. The processor 302 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and / or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 302 may be adapted to fetch and execute computer-readable instructions and data stored in the memory 304.

[0057] The processor 302 may be a general-purpose processor, such as a Central Processing Unit (CPU), an application processor (AP), or a Graphics Processing10259W0017Unit (GPU), a Visual Processing Unit (VPU), and / or an Artificial Intelligence (Al)-dedicated processor such as a Neural Processing Unit (NPU).

[0058] The memory 304 may include any non-transitory computer-readable medium known in the art including, for example, volatile memory, such as Static Random-Access Memory (SRAM) and Dynamic Random-Access Memory (DRAM), and / or non-volatile memory, such as Read-Only Memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.

[0059] The data unit 306 may serve as a repository for storing processed data, received data, and generated data by one or more of the modules 308.

[0060] The modules 308 amongst other things, may include routines, programs, objects, components, data structures, which perform particular tasks or implement data types. The modules 308 may also be implemented as signal processor(s), state machine(s), logic circuitries, and / or any other device or component that manipulates signals based on operational instructions.

[0061] Further, the modules 308 may be implemented in hardware, instructions executed by a processing circuit, or by a combination thereof. The processing circuit may comprise a computer, a processor, a state machine, a logic array, or any other suitable devices capable of processing instructions. The processor may be a general-purpose processor that executes instructions to cause the general- purpose processor to perform the required tasks, or the processing circuit may be dedicated to performing the required functions. In another embodiment of the present disclosure, the processor 302, via the modules 308, may be configured to execute machine-readable instructions (software) which perform the working of the system 108 within the scope of the present disclosure as described in forthcoming paragraphs.

[0062] The modules 308 may include a determining module 310, a generating module 312, a transmitting module 314, and a detecting module 316.

[0063] In an embodiment, the determining module 310 may be configured to determine the operational status of one or more LEs from among the plurality of LEs 106. The determining module 310 may determine the operational status of the10259W0017 one or more LEs based on the operational data received from the corresponding one or more MCUs. For example, the determining module 310 may determine the operational status of the LE 106A-1 as the active state based on the operational data received from the corresponding MCU 204A (indicating that LE 106A-1 is functioning normally). Similarly, the determining module 310 may determine the operational status of the LE 106A-2 as the inactive state based on the operational data received from the corresponding MCU 204A (indicating that LE 106A-2 is turned off or in standby mode). In a similar manner, the determining module 312 may determine the operational status of the one of the LEs 106B as the dimmed state based on the operational data received from the MCU 204C (indicating that LE 106B is working but at a reduced brightness). Further, the determining module 312 may determine the operational status of the one of the LEs 106C as the fault state based on the operational data received from the MCU 204C (indicating that LE 106C is malfunctioning or broken). In an embodiment, the corresponding MCU may receive the operational data from the corresponding LCEU. For example, the MCU 204A may receive the operational data associated with LE 106A-1 from the LCEU 202 A. Similarly, the MCU 204 A may receive the operational data associated with LE 106A-2 from the LCEU 202B.

[0064] Then, the generating module 312 may generate a unified representation of the operational status of the one or more LEs. For example, the generating module 312 may generate the unified representation of the operational status of the LEs 106A-1, 106A-2, 106B, and 106C. The unified representation may show the states of the LEs in a simplified form, for example: LE 106A-1 : Active, LE 106A-2: Inactive, LE 106B: Dimmed, LE 106C: Faulted. In a further example, the unified representation may group LEs based on runway location, such as “Runway 1 - LE 106A-1, 106A-2, 106A-3: Active; Runway 2 - LE 106B: Dimmed; LE 106C: Faulted,” allowing for easier situational awareness by airfield operators.

[0065] Then, the transmitting module 314 may be configured to transmit the one or more control signals to the corresponding one or more MCUs based on the operational status of one or more LEs. The one or more control signals may indicate one or more control actions corresponding to the LE among the plurality of LEs 106. For example, if the operational status of an LE is dimmed state, the one or more control signals may indicate increasing the brightness level of the10259W0017 corresponding LE (e.g., increasing the brightness of LE 106B). Similarly, if the operational status of the LE is the inactive state, the one or more control signals may indicate activating the corresponding LE (e.g., sending a control signal to activate LE 106A-2). In an embodiment, the corresponding MCU may then forward the one or more control signals to the corresponding LCEU via the communication network interface 216. Accordingly, the corresponding LCEU may perform the one or more control actions associated with the corresponding LE. For example, LCEU 202B may activate the LE 106A-2 based on the one or more control signals. In a different case, if LE 106A-2 is overheating, the one or more control signals may direct the corresponding LCEU to reduce intensity or perform a temporary shutdown. In another example, LCEU 202B may activate the LE 106A-2 based on the one or more control signals. Similarly, LCEU 202C may switch LE 106A-3 to a safe-mode pattern to mitigate damage. Accordingly, the system 108 may control individual LEs from among the plurality of LEs 106 in real-time.

[0066] Then, the unified GUI 214A may be configured to display the unified representation. In an embodiment, the unified GUI 214A is accessible via a dashboard hosted on the ILCMS server 102. For example, the unified representation of the operational status of the LEs 106A-1, 106A-2, 106B, and 106C may be displayed on the unified GUI 214A, such as a dashboard. Further, the unified GUI 214A may enable user-initiated control of the one or more LEs across the plurality of incompatible ALCMSs. In particular, a user may control the LEs using the unified GUI 214A. For example, the user may perform the one or more control actions via the corresponding LCEU using the unified GUI 214A. In an example, the user may click on LE 106C in the dashboard to issue a maintenance reset command after physical replacement. Further, to enable the user-initiated control, the unified GUI 214A translates heterogeneous communication protocols associated with the plurality of incompatible ALCMSs into a unified command protocol. In an embodiment, the unified command protocol may include, but is not limited to, a command-response based communication protocol. For instance, the user may interact with the unified GUI 214A to control LEs from different manufacturers. For example, the unified 214A GUI may convert a “turn on” command from Protocol A (Manufacturer 1) LCEU10259W0017 into Protocol B format for a Manufacturer 2 LCEU seamlessly. In an embodiment, once the unified GUI 214A enables the user-initiated control, the user may disconnect / turn off the plurality of incompatible ALCMSs. Accordingly, each of the plurality of LEs 106 is functionally associated with a corresponding ALCMS from the plurality of incompatible ALCMSs. In an embodiment, the plurality of LECUs 202 and the plurality of MCUs 204 are configured to interface directly with the plurality of LEs 106. Hence, the plurality of LECUs 202 and the plurality of MCUs 204 do not communicate with a server of the corresponding ALCMS, the GUI of the corresponding ALCMS, or any ALCMS-specific communication protocol. The plurality of LECUs 202 and the plurality of MCUs 204 operate entirely independently of existing ALCMS infrastructure. Instead, the plurality of LECUs 202 and the plurality of MCUs 204 communicate through the unified ILCMS 214 to monitor and control the plurality of LEs 106 without reliance on or interaction with the corresponding ALCMS. Further, the unified GUI 214A may manage the plurality of LEs 106 across the airfield. Further, there is no physical interconnection between the plurality of incompatible ALCMs 202. Instead, a virtual integration between the unified ILCMS 214, the plurality of LECUs 202, and the plurality of MCUs 204 via the communication network interface 216 facilitates the logical aggregation of the plurality of incompatible ALCMs 202 into the unified ILCMS 214. The connection between the plurality of incompatible ALCMSs 202 and the unified ILCMS 204 may be logical or virtual, not physical. Such a configuration enables seamless integration and centralized control of heterogeneous ALCMSs without requiring modification of or communication with the ALCMS.

[0067] Further, the detecting module 316 may be configured to detect one or more fault conditions in one or more LEs from among the plurality of LEs 106. The detecting module 316 may detect the one or more fault conditions based on one or more sensing elements present in the corresponding LECU. The one or more fault conditions may include, but are not limited to, faulty LE and replacement of the LE. In an embodiment, the one or more sensing elements may be current-based sensing elements, such as current transformers, shunt resistors, etc. If the detecting module 316 detects the one or more fault conditions, the system 108 may alert the users regarding the failed LE. For example, if LE 106C10259W0017 is malfunctioning, an alert may be generated. In another instance, multiple LEs on the same power circuit may simultaneously fault, triggering a “group fault” alert indicating possible feeder cable damage. Accordingly, the fault can be immediately rectified. However, in case of an MCU failure, the system 108 may set the corresponding LECUs in the previous LE state and alert the user for immediate rectification or handle it through a redundant MCU. For instance, if MCU 204 A fails, the system could revert the state of LE 106A-1 to the previous active state while notifying the user of the failure. In another example, redundant MCU 204Z may automatically assume control of LE 106A-2 without operator intervention.

[0068] In a further embodiment, the processor 302 is configured to receive / transmit operational data associated with the one or more LEs from a first airfield lighting system and a second airfield lighting system associated with a first manufacturer and a second manufacturer, respectively. For example, LEs 106A- 1-106A-N may belong to a legacy system supplied by Manufacturer A using proprietary serial communication, while LEs 106B are from Manufacturer B using Ethernet-based Modbus Transmission Control Protocol (TCP). The processor 302 can parse both protocols, convert them to a unified schema, and transmit or visualize the combined data seamlessly on the unified GUI 214A.

[0069] FIGs. 4A-4B illustrate flowcharts depicting a method 400 for integrating the plurality of incompatible ALCMSs into the unified ILCMS 214, according to an embodiment of the present disclosure. The method 400 may be implemented by the system 108. For the sake of brevity, constructional and operational features of the system 108 that are already explained in the description of the previous figures are not explained in detail in the description of FIGs. 4A-4B.

[0070] At step 402, the method 400 may include interfacing the plurality of LECUs 202 with the plurality of LEs 106 installed along an airfield. One or more LEs from the plurality of LEs 106 may be associated with an ALCMS from among the plurality of incompatible ALCMSs. The plurality of LECUs 202 are a part of the unified ILCMS 214.

[0071] At step 404, the method 400 may include communicatively coupling the MCUs 204 to the plurality of LECUs 202. Each MCU may be a part of the unified10259W0017ILCMS 214 and configured to receive data from and transmit one or more control signals to the plurality of LECUs 202 associated with the unified ILCMS 214.

[0072] At step 406, the method 400 may include determining, by the processor 302 communicatively coupled to the plurality of MCUs 204, an operational status of one or more LEs from among the plurality of LEs 106 based on the operational data received from the corresponding one or more MCUs.

[0073] At step 408, the method 400 may include generating, by the processor 302, a unified representation of the operational status of the one or more LEs.

[0074] At step 410, the method 400 may include transmitting, by the processor 302, one or more control signals to the corresponding MCUs based on the operational status of the one or more LEs.

[0075] At step 412, the method 400 may include displaying, via the unified GUI 214A, the unified representation.

[0076] At step 414, the method 400 may include enabling, via the unified GUI 214A, user-initiated control of the one or more LEs across the plurality of incompatible ALCMSs. The unified GUI translates heterogeneous communication protocols associated with the plurality of incompatible ALCMSs into the unified command protocol.

[0077] In a further embodiment, the method 400 may include detecting the one or more fault conditions in one or more LEs from among the plurality of LEs based on one or more sensing elements present in the corresponding LECU.

[0078] In a further embodiment, the method 400 may include receiving / transmitting the operational data associated with the one or more LEs from a first airfield lighting system and a second airfield lighting system associated with a first manufacturer and a second manufacturer, respectively.

[0079] At least by virtue of the aforesaid, the present disclosure at least provides various advantages. For example, the present disclosure provides techniques to effectively integrate multiple incompatible ALCMS systems into a single ILCMS system. Further, the present disclosure provides real-time monitoring and controlling of individual LEs. The present disclosure provides techniques to10259W0017 integrate a plurality of incompatible ALCMSs into the unified ILCMS without the need for additional wiring. The present disclosure provides a safer and more reliable unified ILCMS. The disclosed techniques provide a proficient fault identification and maintenance system. The disclosed techniques result in increased power saving. The present disclosure provides techniques to integrate a plurality of incompatible ALCMSs into the unified ILCMS at a low cost. Further, the present disclosure provides techniques for seamlessly upgrading airfields with legacy and existing systems to CAT II / III supporting ILCMS with almost no downtime to airfield operations.

[0080] The present disclosure herein demonstrates high reliability under varying environmental conditions. Furthermore, the present disclosure achieves performance requirements by airfield application, including low-latency communication, fast data transfers, secure data transmission, and support for simplified installation, configuration, fault detection, and maintenance procedures.

[0081] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.

[0082] The drawings and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.

Claims

10259W0017We Claim:

1. A system (108) for integrating a plurality of incompatible Airfield Lighting Control And Monitoring Systems (ALCMSs) into a unified Individual Lamp Control And Monitoring System (ILCMS) (214), the system (108) comprising: a plurality of Lighting Element Control Units (LECUs) (202) configured to interface with a plurality of Lighting Elements (LEs) (106) installed along an airfield, wherein one or more LEs from the plurality of LEs (106) are associated with an ALCMS from among the plurality of incompatible ALCMSs and the plurality of LECUs (202) are a part of the unified ILCMS (214); a plurality of Master Control Units (MCUs) (204) communicatively coupled to the plurality of LECUs (202), wherein each MCU is a part of the unified ILCMS (214) and is configured to receive operational data from and transmit one or more control signals to the plurality of LECUs (202) associated with the unified ILCMS (214); a processor (302) communicatively coupled to the plurality of MCUs (204), the processor (302) being configured to: determine an operational status of one or more LEs from among the plurality of LEs (106) based on the operational data received from the corresponding one or more MCUs; generate a unified representation of the operational status of the one or more LEs; and transmit the one or more control signals to the corresponding one or more MCUs based on the operational status of one or more LEs; and a unified Graphical User Interface (GUI) (214A) configured to display the unified representation and enable user-initiated control of the one or more LEs across the plurality of incompatible ALCMSs, wherein the unified GUI translates heterogeneous communication protocols associated with the plurality of incompatible ALCMSs into a unified command protocol.

2. The system (108) as claimed in claim 1, further comprising: a communication network interface (216) configured to facilitate data exchange among the plurality of LECUs (202) and the plurality of MCUs (204) using a common communication protocol.10259W00173. The system (108) as claimed in claim 2, wherein the communication network interface (216) includes at least one of a wired network and a wireless network.

4. The system (108) as claimed in claim 1, wherein the processor (302) is further configured to detect one or more fault conditions in one or more LEs from among the plurality of LEs (106) based on one or more sensing elements present in corresponding LECU.

5. The system (108)as claimed in claim 1, wherein the unified GUI (214A) is accessible via a dashboard hosted on an ILCMS server (102).

6. The system (108) as claimed in claim 1, wherein the processor (302) is configured to receive / transmit the operational data associated with the one or more LEs from a first airfield lighting system and a second airfield lighting system associated with a first manufacturer and a second manufacturer, respectively.

7. The system (108) as claimed in claim 1, wherein the system is configured to control individual LEs from among the plurality of LEs (106) in real-time.

8. A method (400) for integrating a plurality of incompatible Airfield Lighting Control And Monitoring Systems (ALCMSs) into a unified Individual Airfield Lighting Control And Monitoring System (ILCMS) (214), the method (400) comprising: interfacing (402) a plurality of Lighting Element Control Units (LECUs) (202) with a plurality of Lighting Elements (LEs) (106) installed along an airfield, wherein one or more LEs from the plurality of LEs (106) are associated with an ALCMS from among the plurality of incompatible ALCMSs and the plurality of LECUs (202) are a part of the unified ILCMS (214); communicatively coupling (404) a plurality of Master Control Units (MCUs) (204) to the plurality of LECUs (202), wherein each MCU is part of the unified ILCMS (214) and configured to receive operational data from and transmit one or more control signals to the plurality of LECUs (202) associated with the unified ILCMS (214); determining (406), by a processor (302) communicatively coupled to the plurality of MCUs (204), an operational status of one or more LEs from among the plurality of LEs (106) based on the operational data received from the corresponding one or more MCUs; generating (408), by the processor (302), a unified representation of the operational status of the one or more LEs; transmitting (410), by the processor (302), one or more control signals to the corresponding MCUs based on the operational status of the one or more LEs; and displaying (412), via a unified Graphical User Interface (GUI) (214A), the unified representation; and10259W0017 enabling (414), via the unified GUI (214 A), user-initiated control of the one or more LEs across the plurality of incompatible ALCMSs, wherein the unified GUI translates heterogeneous communication protocols associated with the plurality of incompatible ALCMSs into a unified command protocol.

Images