Network enabled modular luminaire and connector system

Abstract

Techniques are discussed for connector system for a modular luminaire. The connector system may comprise: a connector housing configured to be removably attached to a lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; and a network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

Description

Attorney Ref No.: 1817P0005WOefiling Date: February 20, 2026NETWORK ENABLED MODULAR LUMINAIRE AND CONNECTOR SYSTEMCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit and right of priority under 37 C.F.R. 1.55 and 35 U.S.C. 365(a) to United States Provisional Application Numbers (US Prov Nos) 63 / 761,105, filed February 20, 2025, entitled “SMART LINEAR LAMP WITH MODULAR SUBSCRIBER IDENTITY MODULE (SIM) CARD INTERFACE;” US Prov No 63 / 761,110, filed February 20, 2025, entitled “MODULAR SMART LINEAR LAMP WITH INTEGRATED LI-FI WIRELESS COMMUNICAITON FOR MULTI-CONNECTIVITY AND IOT APPLICATIONS;” US Prov No 63 / 761,113, filed February 20, 2025, entitled “SMART LUMINAIRE WITH MODULAR SUBSCRIBER IDENTITY MODULE (SIM) CARD INTERFACE FOR SECURE NETWORK INTEGRATION, IOT, AND CELLULAR CONNECTIVITY;” US Prov No 63 / 761,121, filed February 20, 2025, entitled “SMART LAMP WITH MODULAR SENSORS FOR ENVIRONMENTAL DATA CAPTURING AND IOT INTEGRATION;” US Prov No 63 / 761,130, filed February 20, 2025, entitled “LINEAR REMOVABLE, REPLACEABLE, AND UPGRADEABLE MULTI-FACETED SMART LAMP WITH EMBEDDED TECHNOLOGY, INDEPENDENT PLANE OPERATION, AND GLOBAL STANDARD COMPATIBILITY,” of which all of these recited provisional patent applications are incorporated by reference herein, in their respective entirety

[0002] This application is also related to information disclosed in United States Patent Numbers (US Pat Nos) 8,702,265, issued April 22, 2014, and titled “NON-CURVILINEAR LED LUMINARIES;” US Pat No 9,228,727, issued January 5, 2016, and titled “LIGHTING SYSTMEM;” US Pat No 9,644,828, issued May 9, 2017, and titled “NETWORKED LED LIGHTING SYSTMEM;” US Pat No 9,671,071, issued June 6, 2017, and titled “NETWORKED LED LIGHTING SYSTMEM;” US Pat No 9,671,072, issued June 6, 2017, and titled “NETWORKED LED LIGHTING SYSTMEM;” US Pat No 9,726,331, issued August 8, 2017, and titled “NETWORKED LED LIGHTING SYSTMEM;” US Pat No 9,726,332, issued August 8, 2017, and titled “NETWORKED LED LIGHTING SYSTMEM;” US Pat No 9,726,361, issued August 8, 2017, and titled “NETWORKED LED LIGHTING SYSTMEM;” US Pat No 9,739,427, issued August 22, 2017, and titled “NETWORKED LED LIGHTING SYSTMEM;” US Pat No 9,927,073, issued March 27, 2018, and titled “NETWORKED LED LIGHTING SYSTMEM;” US Pat No 10,302,292, issued May 28, 2019, and titled “CONNECTOR SYSTEM FOR LIGHTING ASSEMBLY;” and US Pat NoAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 202611,168,872, issued November 9, 2021, and titled “MOUNTING CLIP FOR NETWORKED LED LIGHTING SYSTEM,” of which all of these recited issued patents are incorporated by reference herein, in their respective entirety.TECHNICAL FIELD

[0003] Aspects of the disclosure relate generally to lighting systems, and more particularly to intelligent lighting systems.BACKGROUND

[0004] Over the years various types of illuminating assemblies and devices have been developed for indoor and / or outdoor illumination, such as torches, oil lamps, gas lamps, lanterns, incandescent bulbs, neon signs, fluorescent bulbs, halogen lights, and light emitting diodes. These conventional prior art illuminating assemblies and devices have met with varying degrees of success.

[0005] Incandescent light bulbs create light by conducting electricity through a thin filament, such as a tungsten filament, to heat the filament to a very high temperature so that it glows and produces visible light. Incandescent light bulbs emit a yellow or white color. Incandescent light bulbs, however, are very inefficient, as over 98% of its energy input is emitted and generated as heat. A standard 100-watt light bulb emits about 1700 lumens, or about 17 lumens per watt. Incandescent lamps are relatively inexpensive and have a typical lifespan of about 1,000 hours.

[0006] Fluorescent lamps (light bulbs - also known as tubes) conduct electricity through mercury vapor, which produces ultraviolet (UV) light. The ultraviolet light is then absorbed by a phosphor coating inside the lamp, causing it to glow, or fluoresce. While the heat generated by fluorescent lamps is much less than its incandescent counterpart, energy is still lost in generating the UV light and converting UV light into visible light. If the lamp breaks, exposure to mercury can occur. Linear fluorescent lamps are often five to six times the cost of incandescent bulbs but have life spans around 10,000 and 20,000 hours. Lifetime varies from 1,200 hours to 20,000 hours for compact fluorescent lamps. Some fluorescent lights flicker and the quality of the fluorescent light tends to be a harsh white due to the lack of a broad band of frequencies. Most fluorescent lights are not compatible with dimmers.

[0007] At present, there has been a move to replace fluorescent light tubes with light emitting diode (LED) lighting elements that generally offer, for example, an about 50% reduction inAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026energy consumption, up to approximately five times the lifespan, and provide instant-on flicker free light. Other advantages of LED lighting elements are that they generally have improved robustness, smaller size, faster switching, and excellent durability and reliability. LEDs emit more light per watt than incandescent light bulbs. LEDs can be tiny and easily placed on printed circuit boards and activate and turn on very quickly and can be readily dimmed. LEDs also emit a cool light with very little infrared light and come in multiple colors which are produced without the need for filters. Additionally, LEDs of different colors can be mixed to produce white light. Other advantages of LEDs include: high efficiency; low energy consumption; higher outputs at higher drive currents; shock resistant with no filament, glass or tube to break, contain no toxic substances, hazardous mercury or halogen gases.

[0008] With the development of efficient high-power LEDs, it has become more advantageous to use LED lighting and illumination. High power white light LED lighting is useful for illumination and for replacing incandescent and / or fluorescent lighting. LED streetlights are used on posts, poles and in parking garages. LED's are now used in stores, homes, stage and theaters, and public places. Furthermore, color LED's are useful in medical and educational applications such as for mood enhancement. In many countries incandescent lighting for homes and offices is no longer available and building regulations require new premises to use LED lighting.

[0009] Conventional prior art LED lighting that is powerful enough for room lighting, however, is relatively expensive and requires more precise current and heat management than fluorescent lamp sources of comparable output. Furthermore, conventional LED lighting can have a higher capital cost than other types of lighting and LED light tends to be directional with small areas of illumination. Moreover, conventional LED luminaries suffer from drawbacks due to a lack of lumen output and less than desirable light dispersion. Individually and combined, these aspects of conventional LED lighting can detract from efficient utilization of LED luminaries.

[0010] One problem that has plagued the lighting industry is associated with how conventional, elongate, tubular lighting components are operatively mounted through end connectors. As described in greater detail below, conventional tubular lighting, having a source of illumination that is an LED, a gas-discharge lamp that uses fluorescence to produce visible light, or another known source on, or within, a tubular body, typically utilizes a bi-pin / 2-pin means on the tubular body that mechanically supports the body in an operative state and effects electrical connection of the illumination source to a power supply. Specifically, known typesAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026of LED tube replacements for fluorescent tubes include utilizing type A (ballast compatible plug-and-play) LED tubes that allow for direct replacement of fluorescent tubes utilizing the existing fluorescent ballasts and wiring; type B (ballast bypass direct wire) LED tubes that require removing the ballast and wiring 120-277 volts of power directly to the sockets; utilizing type C (external driver) that utilizes a separate driver for maximum efficiency and diming capabilities.

[0011] A problem with these approaches is that they do not allow direct control of the LED elements and are not a standardized approach to allow for reliability and expandability. In addition, installation requires a precise initial angular orientation of the body and subsequent controlled repositioning thereof to simultaneously seat the pins at the opposite ends of the body. Often one or more of the pins are misaligned during this process so that electrical connection is not established. The same misalignment may cause a compromised mechanical connection whereas the body may escape from the connectors and drop so that it is damaged or destroyed.

[0012] In addition, known smart lighting solutions are constrained by fixed networking hardware, limited security, and forced obsolescence. Many lighting systems require physical replacement to support new connectivity standards, security protocols, or automation frameworks. This generally results in: unnecessary replacement costs for building owners and enterprises; E-waste accumulation due to frequent technology refresh cycles; security vulnerabilities in outdated networking hardware; and compatibility issues with evolving smart building automation and network security frameworks. Furthermore, the lack of decentralized, linear lamp-based cellular connectivity has prevented lighting systems from contributing to private networking, data security, environmental monitoring, and automation-based cloud integration.

[0013] Furthermore, the lack of decentralized, linear lamp-based cellular connectivity has prevented lighting systems from contributing to private networking, data security, environmental monitoring, and automation-based cloud integration.

[0014] Moreover, existing light fidelity (Li-Fi) solutions are permanently integrated into lighting fixtures, preventing modular upgrades and making retrofitting costly. Current Li-Fi-enabled luminaires lack compatibility with standardized lighting sockets, restricting widespread deployment. Deployment of Li-Fi systems requires replacing entire fixture arrays, limiting adoption in commercial, industrial, and government applications. Additionally, current Li-Fi solutions do not support multi-voltage operation, preventing broad integration across Power over Ethernet (PoE), low-voltage DC, and high-voltage AC networks.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0015] As such, there is a need for a system and method to address these issues.SUMMARY

[0016] Techniques are discussed for connector system for a modular luminaire. The connector system may comprise: a connector housing configured to be removably attached to a lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; and a network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

[0017] Also discussed is smart modular luminaire comprising: a lighting assembly; a connector housing configured to be removably attached to the lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; and a network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

[0018] Generally, there is a need for a scalable, modular, and upgradeable linear lighting solution that integrates cellular and Internet-of-Things (loT) communication, ensuring secure, dedicated, and independent operation within smart building infrastructures, industrial automation, and remote applications. Aspects of this disclosure overcome these challenges by providing a secure, modular linear lighting platform that enables programmable network access, cellular data transfer, edge computing, satellite communication, and decentralized connectivity while maintaining the functionality of a linear lamp.

[0019] Generally, there is also need for a scalable, modular, and upgradeable lighting solution that supports multiple power delivery modalities while also supporting secure wired and / or fully wireless communications. Aspects of this disclosure overcome these challenges by providing a modular luminaire and connector system that enables programmable network access, sensor data capture, edge processing, and multi -protocol connectivity while maintaining the functionality of a linear lamp.

[0020] In some implementations, the modular luminaire is configured to operate from an external power source that includes alternating current (AC) power, direct current (DC) power, or both. By way of example and not limitation, the external power source may include line-voltage AC, low-voltage DC distribution, PoE power delivery, or other standardized or proprietary power interfaces. In certain implementations, the luminaire includes powerAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026conversion circuitry configured to convert received AC and / or DC power to one or more regulated voltages for one or more light emitters, processors, communication devices, and / or sensors.

[0021] In some implementations, the modular luminaire is configured for “fully wireless” data connectivity in which control signals and / or sensed data are transmitted and received wirelessly while electrical power is provided via AC and / or DC (e.g., via a lamp holder, fixture wiring, or a DC bus). In other implementations, data connectivity may be provided via a wired data interface (e.g., Ethernet) and / or a combined power-and-data interface. Accordingly, wired networking examples (including Ethernet and PoE) are provided for illustration and do not limit the disclosure to any particular cabling or connector format.

[0022] In some implementations, the modular luminaire (and / or a network communication device associated with the modular luminaire) is configured to operate as a network gateway, router, bridge, access point, repeater, and / or mesh node for one or more wireless networks. For example, the modular luminaire may bridge between a wired backhaul and a wireless network, between two wireless networks, or between a local mesh network of luminaires and a remote network entity. This can enable decentralized connectivity, redundancy, and extension of network coverage in commercial, industrial, government, and remote environments.

[0023] In some implementations, the modular luminaire includes one or more sensors and is configured to collect environmental or operational data (e.g., occupancy, motion, temperature, humidity, air quality, vibration, acoustic, light level, and / or other parameters). The modular luminaire may transmit sensed data to a network entity using any suitable communication path, including one or more wireless protocols and / or one or more wired interfaces, and may optionally perform local preprocessing, aggregation, filtering, encryption, or buffering of the sensed data.

[0024] In some implementations, the modular luminaire supports multi -protocol link management, including detection of communication errors or degraded link conditions and automatic mitigation. Mitigation can include, for example, adjusting communication parameters, retry / retransmit behaviors, buffering data for later transmission, and / or switching between available wired and wireless communication modes to maintain connectivity.

[0025] In some implementations, the modular luminaire is mechanically compatible with one or more industry-standard lamp holders and / or retrofit interfaces (e.g., ANSI, IEC GJ 6.6 lamp holders and / or other lamp holder families), and may alternatively be implemented withAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026interchangeable adapter interfaces to support multiple fixture types and multiple power and communication connection points.

[0026] In general, techniques are discussed for a modular linear light emitting diode (LED) (or other type of light emitting technology) lamp featuring a subscriber identity module (SIM) card-based board, enabling secure, programmable loT network integration.

[0027] Also discussed are techniques for a lighting system that enables communication between connected loT sensors, HVAC controllers, security devices, and building automation systems.

[0028] Further discussed are techniques for a modular linear lighting solution that eliminates forced obsolescence, allowing users to replace only the loT module instead of discarding the entire linear lamp when networks evolve.

[0029] Other devices, apparatuses, systems, methods, features, and advantages of the invention will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional devices, apparatuses, systems, methods, features, and advantages be included within this description, be within the scope of the invention, and be protected by the accompanying claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0030] FIG. 1 is a system block diagram of an example of an implementation of modular luminaire 100 in accordance with the present disclosure.

[0031] FIG. 2 is a system block diagram of an example of an implementation of a connector system in accordance with the present disclosure.

[0032] FIG. 3 is a system diagram of an example of an implementation of networked lighting system (NLS) utilizing a plurality of modular luminaires in accordance with the present disclosure.

[0033] FIG. 4 is a system diagram of an example of another implementation of an NLS utilizing a plurality of modular luminaires each having a lighting assembly and at least one connector system in accordance with the present disclosure.

[0034] FIG. 5 is a system diagram of an example of an implementation of another NLS utilizing modular luminaires that include tubular lighting assemblies in accordance with the present disclosure.

[0035] FIG. 6A is a perspective view of an example of an implementation of a cylindrical, network compatible linear LED lighting assembly (LED tube lamp) having an external heatAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026sink extending over a portion of the circumference of an elongate body portion and having end cap assemblies at opposite ends of the body, showing an external Ethernet jack connected to the lamp by a jumper cable extending through the end wall of the end cap.

[0036] FIG. 6B is a side perspective view of the lamp of FIG. 6A with portions cut away to expose internal components, and showing an enlarged view of an end cap assembly comprising and cable connector mounted to a horizontally oriented PCB connector board for connecting an Ethernet cable and jack between a net.

[0037] FIG. 7 is a perspective view of an example of an implementation of a linear LED lamp, and shows cooperating connector assemblies (that include a connector system) at opposite ends of the body of the linear LED lamp, with the connector assembly at one end comprising a power over Ethernet (PoE) enabled sleeve adaptor configured to provide integrated power and data at one end of the linear LED lamp.

[0038] FIG. 8 is an enlarged perspective view of an example of an implementation of the PoE enabled sleeve adaptor of FIG. 7, showing an Ethernet cable plug connected to an integral jack at a base end of the sleeve adaptor and including a male Ethernet plug extending within the sleeve receptacle of the adapter.

[0039] FIG. 9A is side perspective view of an example of an implementation of a PoE enabled snap-fit connector having a proximal base end for mounting to a lighting fixture, a mid-portion including a snap-fit actuator assembly and extending to a distal tip portion configured as integral Ethernet plug, and showing cable wiring crimped directly to pins of the Ethernet plug.

[0040] FIG. 9B is right side view of the PoE enabled snap-fit connector assembly of FIG.9B.

[0041] FIG. 10A is a perspective view of an example of an implementation of a tubular lighting assembly in accordance with the present disclosure.

[0042] FIG. 10B is an enlarged view of one end of the tubular lighting assembly of FIG. 10A.

[0043] FIG. 11 is a system block diagram of an example of another implementation of a modular luminaire in accordance with present disclosure.

[0044] FIG. 12 is a system block diagram of an example of yet another implementation of a modular luminaire in accordance with present disclosure.

[0045] FIG. 13 A is a side view of an example of an implementation of the first connector system having a protruding section in accordance with the present disclosure.

[0046] FIG. 13B is a top view of the first connector system shown in FIG. 13 A.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0047] FIG. 14 is a bottom view of an example of an implementation of a connector system physically attached to a portion of a tubular lighting assembly in accordance with the present disclosure.

[0048] FIG. 15A is a prospective front view of the connector system detached from the tubular lighting assembly (as shown in FIG. 14) in accordance with the present disclosure.

[0049] FIG. 15B is an offset front view of the connector system shown in FIGS. 14 and 15 A.

[0050] FIG. 16 is another front view of the connector system shown in FIGS. 14 through 15B.

[0051] FIG. 17 is a system block diagram of an example of yet another implementation of a modular luminaire in accordance with present disclosure.

[0052] FIG. 18A is a side view of an example of an implementation of the modular luminaire shown in FIG. 17.

[0053] FIG. 18B is a perspective bottom view of the modular luminaire shown in FIG. 18 A.

[0054] FIG. 19 is an exploded assembly view of a three-sided delta non-curvilinear LED luminary in accordance with principles of the present disclosure.

[0055] FIG. 20 is an enlarged view of the right portions of the three-sided delta non-curvilinear LED luminary of FIG. 19.

[0056] FIG. 21 is an enlarged view of the left portions of the three-sided delta non-curvilinear LED luminary of FIG. 19.

[0057] FIG. 22 is an exploded assembly view of a two-sided non-curvilinear LED luminary in accordance with principles of the present disclosure.

[0058] FIG. 23 is an enlarged view of the right portions of the two-sided non-curvilinear LED luminary of FIG. 22.

[0059] FIG. 24 is an exploded assembly view of another two-sided non-curvilinear LED luminary in accordance with principles of the present disclosure.

[0060] FIG. 25 is an enlarged view of the right portions of the two-sided non-curvilinear LED luminary of FIG. 25.

[0061] FIG. 26 is a perspective view of an end cap connector board for a two-sided delta non-curvilinear LED in accordance with principles of the present disclosure.

[0062] FIG. 27 is a perspective view of surface mount connectors connected to the end cap connector board of FIG. 26.

[0063] FIG. 28 is a perspective view of a portion of a driver board connected to the surface mount connectors of FIG. 27.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0064] FIG. 29 is a perspective view of a portion of a three-sided delta heat sink tube positioned peripherally about the driver board and against the end cap connector board of FIG.28.

[0065] FIG. 30 is a perspective view of emitters on an emitter board with AC and DC power traces connected to the surface mount connectors and positioned about the heat sink tube of FIG. 29.

[0066] FIG. 31 is a perspective view of a portion of a lens about the emitters of FIG. 30.

[0067] FIG. 32 is a perspective view of a portion of an end cap at the left end of the lens of FIG. 31.

[0068] FIG. 33 is a perspective view of the two-sided delta non-curvilinear LED luminary with the end cap and showing portions of the lens removed to illustrate the emitters on the emitter board and the AC and DC power traces connected to the surface mount connectors in accordance with the present disclosure.

[0069] FIG. 34 is a perspective view of an end cap connector board or connector end board and driver board for a two-sided delta non-curvilinear LED luminary in accordance with principles of the present disclosure.

[0070] FIG. 35 is a perspective view of emitter board connectors connected to the end cap connector board and illustrating driver connectors connected to the driver board and the end cap connector board of FIG. 34.

[0071] FIG. 36 is a system block diagram of an example of an implementation of another NLS where the NCD is located external to the first connector system in accordance with the present disclosure.

[0072] FIG. 37 is a perspective view of an LED drop ceiling fixture with three-sided delta non-curvilinear LED luminaries mounted to a ceiling above ceiling panels in accordance with the present disclosure.

[0073] FIG. 38 is an enlarged view of portions of the LED drop ceiling fixture with three- sided delta non-curvilinear LED luminaries of FIG. 37.

[0074] FIG. 39 is a cross-section view of the LED drop ceiling fixture with three-sided delta LED non-curvilinear luminaries of FIG. 37.

[0075] FIG. 40 is an enlarged perspective view of the three-sided delta LED luminaries of FIG. 37

[0076] FIG. 41 is a perspective view of an outdoor menu board providing an outdoor sign with two-sided delta non-curvilinear LED luminaries such as for drive through menu boardAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026applications and illustrating the menu board door partially open in accordance with principles of the present invention.

[0077] FIG. 42 is an enlarged view of portions of the outdoor menu board of FIG. 41.

[0078] FIG. 43 is a perspective view of an indoor menu board providing an indoor sign with three-sided delta non-curvilinear LED luminaries such as for a restaurant, and illustrating one of the panel doors in a partially open position in accordance with principles of the present invention.

[0079] FIG. 44 is an enlarged view of portions of the indoor menu board of FIG. 43.

[0080] FIG. 45 is a schematic system diagram of an automated LED lighting system in accordance with the present disclosure.

[0081] FIG. 46 is a system block diagram of an example of another implementation of the connector system in accordance with the present disclosure.

[0082] FIG. 47 is a system block diagram of an example of another implementation of the connector system in a network configuration in accordance with the present disclosure.

[0083] FIG. 48 is a system block diagram of an example of an implementation of a lightfidelity (Li-Fi) enabled in accordance with the present disclosure.

[0084] FIG. 49 is a graphical plot of an example of an implementation of wireless communication and data transmission fields projected from the Li-Fi smart linear lamp in accordance with the present disclosure.

[0085] FIG. 50 is a system diagram of an example of an implementation that illustrates a Li-Fi-enabled linear lamp designed to be installed inside conventional lighting fixtures that accept standard linear-type lamps in accordance with the present disclosure.

[0086] FIG. 51 is a system block diagram of an example of a smart lamp system with topmounted sensor and bottom-mounted sensors, demonstrating the modular and adaptable nature of sensor placement within the lamp’s embodiment in accordance with the present disclosure.

[0087] FIG. 52 is system diagram of an example of an implementation of Li-Fi and Bluetooth-enabled smart lighting systems within an interconnected wireless communication environment in accordance with the present disclosure.

[0088] FIG. 53 is a system block diagram of an example of another implementation of a NLS including a network entity, a gateway luminaire, a plurality of mesh luminaires, a wide area network providing wireless backhaul, a remote power source providing AC and / or DC power, and user equipment (UE) in accordance with the present disclosure.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0089] FIG. 54 is a system block diagram of an example of an implementation of a power architecture in which a power management module selectively receives electrical power from one or more inputs including an AC input, a DC input, a PoE input, a USB-C Power Delivery (PD) input, and / or a wireless power receiver, and provides regulated power to a lighting assembly including an LED driver, a network communication device (NCD), a sensor array, and / or auxiliary / port power, optionally in coordination with energy storage in accordance with the present disclosure.

[0090] FIG. 55 is a system block diagram of an example of an implementation of a modular interface system including an end cap / connector housing having a modular interface bay and an interconnect configured to electrically couple a lighting assembly to interchangeable modules including an RJ45 / PoE module, a USB-C PD module, an AC / DC terminal module, a wireless bridge module, and / or a SIM / UICC module, in accordance with the present disclosure.

[0091] FIG. 56 is a system block diagram of an example of an implementation of a gateway / protocol bridge in which a gateway luminaire bridges communications between loT device(s) on a local wireless network and a network entity via one or more backhaul network(s), optionally using edge compute / buffering and / or local I / O (port) in accordance with the present disclosure.

[0092] FIG. 57 is a system block diagram of an example of an implementation of a commissioning workflow for provisioning an unprovisioned luminaire using a commissioning device via one or more local links (e.g., BLE, NFC, USB-C), including identifying the device, performing secure bootstrap / key exchange, provisioning credentials, joining a mesh and / or selecting a gateway, registering with a network entity, and entering an operational mode in accordance with the present disclosure.

[0093] FIG. 58 is a flow diagram of an example of an implementation of a method for link monitoring and failover including monitoring link quality, determining whether quality meets a threshold, operating a primary link when quality is acceptable, performing degraded-link mitigation when quality is unacceptable, evaluating whether recovery occurs in time, performing failover / handoff / rejoin to an alternate link when recovery does not occur in time, determining whether backhaul is available, performing store-and-forward buffering when backhaul is unavailable, and restoring a primary link when available in accordance with the present disclosure.

[0094] FIG. 59 is a system block diagram of an example of an implementation of a GJ6.6 lamp holder / adapter in which a GJ6.6 lamp holder mechanically and electrically couples to anAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026adapter module configured to receive an AC input and / or a DC input, perform rectification and / or DC-DC conversion, and provide regulated power to a modular luminaire in accordance with the present disclosure.

[0095] FIG. 60 is a system block diagram of an example of an implementation of a wireless power and wireless data system in which a wireless power transmitter provides inductive / RF power to a wireless power receiver of a modular luminaire, and the modular luminaire communicates wirelessly with a network entity and / or user devices, optionally using energy storage in accordance with the present disclosure.

[0096] FIG. 61 is a system block diagram of an example of an implementation of a NLS including a network entity, a gateway luminaire, a plurality of mesh luminaires, a wide area network providing wireless backhaul, a remote power source providing AC and / or DC power, and UEs in accordance with the present disclosure.

[0097] FIG. 62 is a system block diagram of an example of an implementation of a modular interface system including an end cap / connector housing having a modular interface bay 6204 and an interconnect configured to electrically couple a lighting assembly to interchangeable modules including an RJ45 / PoE module, a USB-C PD module, an AC / DC terminal module, a wireless bridge module, and / or a SIM / UICC module.

[0098] FIG. 63 is a system block diagram of an example of an implementation of a gateway / protocol bridge in which a gateway luminaire bridges communications between loT device(s) on a local wireless network and a network entity via one or more backhaul network(s), optionally using edge compute / buffering and / or local I / O (port) in accordance with the present disclosure.

[0099] FIG. 64 is a flow chart of an example of an implementation a method for a commissioning workflow for provisioning an unprovisioned luminaire using a commissioning device via one or more local links (e.g., BLE, NFC, USB-C), including identifying the device, performing secure bootstrap / key exchange, provisioning credentials, joining a mesh and / or selecting a gateway, registering with a network entity, and entering an operational mode.

[0100] FIG. 65 is a flow diagram of an example of an implementation a method for link monitoring and failover in accordance with the present disclosure.

[0101] FIG. 66 is a system block diagram of an example of an implementation of wireless mesh lighting network with gateway backhaul in accordance with the present disclosure.

[0102] FIG. 67 shows a front view of a four (4) sided light surface in accordance with the present disclosure.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0103] FIG. 68 is a system block diagram of an example of an implementation of a multiinput power architecture in which a luminaire node may receive power from one or more of an AC input, a DC input, a PoE input, a USB-C power delivery (PD) input, and / or a wireless power receiver in accordance with the present disclosure.

[0104] FIG. 69 is a system block diagram of an example of an implementation of connector system that includes an interface bay configured to receive an interchangeable interface module selected from a plurality of interface modules in accordance with the present disclosure.

[0105] FIG. 70 is a system block diagram of an example of an implementation of gateway luminaire node in accordance with the present disclosure.

[0106] FIG. 71 is a system flow diagram of an example of an implementation of wireless commissioning and / or onboarding workflow in accordance with present disclosure.

[0107] FIG. 72 is a system block diagram of an example of an implementation of backhaul selection and handoff state diagram in accordance with the present disclosure.

[0108] FIG. 73 is a system block diagram of an example of an implementation of an example adapter configured to mechanically couple to a lamp holder and electrically couple power to a luminaire node in accordance with the present disclosure.

[0109] FIG. 74 is a system block diagram of an example of operation of the luminaire node under full wireless operation in accordance with the present disclosure.DETAILED DESCRIPTION

[0110] Techniques are discussed for connector system for a modular luminaire. The connector system may comprise: a connector housing configured to be removably attached to a lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; and a network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

[0111] Also discussed is smart modular luminaire comprising: a lighting assembly; a connector housing configured to be removably attached to the lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; and a network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0112] Also discussed is a modular luminaire that may include a lighting assembly having a body with a length, a first connector system, and a second connector system. In this example, the first may include a first connector housing configured to be removably attached to the body of the lighting assembly, a first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly, and a first network device electrically coupled to the first end connector board, wherein the first network device is configured to communicate with a remote entity. The second connector system may include a second connector housing configured to be removably attached to the body of the lighting assembly at a location opposite the first connector housing along the length of the body of the lighting assembly, a second end connector board within the second connector housing, wherein the second end connector board is configured to electrically couple to the lighting assembly, and a second network device electrically coupled to the second end connector board, wherein the second network device is also configured to communicate with the remote entity.

[0113] Items and / or techniques described herein may provide one or more of the following capabilities, as well as other capabilities not mentioned. Other capabilities may be provided and not every implementation according to the disclosure must provide any, let alone all, of the capabilities discussed.

[0114] The description herein may refer to sequences of actions to be performed, for example, by elements of a computing device. Various actions described herein can be performed by specific circuits (e.g., an application specific integrated circuit (ASIC)), by program instructions being executed by one or more processors, or by a combination of both. Sequences of actions described herein may be embodied within a non-transitory computer-readable medium having stored thereon a corresponding set of computer instructions that upon execution would cause an associated processor to perform the functionality described herein. Thus, the various examples described herein may be embodied in a number of different forms, all of which are within the scope of the disclosure, including claimed subject matter.

[0115] In general, the connector systems and modular luminaires described herein may be implemented in multiple power and communication configurations. The examples shown in the drawings illustrate certain implementations that use wired data connectivity (e.g., Ethernet cabling), including implementations where a single cable provides both data connectivity and electrical power (e.g., Power over Ethernet (PoE)). It is appreciated that these are exampleAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026implementations, and that other wired and wireless implementations are contemplated without deviating from the teachings of the present disclosure.

[0116] In some implementations, the modular luminaire is configured for “wireless-first” or “wireless-only” data connectivity. In such implementations, the modular luminaire may receive electrical power via a lamp holder, socket, fixture wiring, or other power connector that provides alternating current (AC) power or direct current (DC) power, while network communications (including lighting control, provisioning, diagnostics, telemetry, and sensor data) are communicated via one or more wireless communication links. In some implementations, a wired data interface (e.g., an Ethernet interface) may be omitted, disabled, or used only as an optional commissioning and / or fallback interface.

[0117] As an example, the end connector board (e.g., end connector board 202) may include one or more power input stages configured to accept AC input power, DC input power, or both, and to provide one or more regulated DC rails to power: (i) LED drive circuitry of the lighting assembly; (ii) the network communication device (NCD); and / or (iii) one or more sensors. The one or more power input stages may include one or more of: rectification circuitry, powerfactor correction circuitry, galvanic isolation, surge protection, transient suppression, and / or one or more DC-to-DC converters. In some implementations, the modular luminaire is configured to be powered from a DC power source that is provided via a building DC distribution bus, a low-voltage power supply, a battery system, a solar system, and / or another DC power system.

[0118] In some implementations, the NCD includes one or more wireless transceivers (e.g., Wi-Fi, Bluetooth, Zigbee, Thread, Li-Fi, cellular, satellite, and / or low power wide area networking (LPWAN) transceivers) and is configured to communicate with the network entity, one or more remote devices, or both, via at least one wireless signal path. In some implementations, the NCD is configured to operate as a wireless access point, a wireless client, a mesh-network node, a repeater, and / or a gateway between: (i) a local wireless network and (ii) a wired network, cellular network, satellite network, and / or other backhaul network.

[0119] In some implementations, a plurality of modular luminaires are configured to form a wireless mesh network that supports forwarding of control messages and / or sensor data among luminaires. In these implementations, one or more luminaires may operate as gateway nodes that provide a backhaul connection between the wireless mesh network and the network entity (e.g., via a wired connection, Wi-Fi uplink, cellular uplink, and / or satellite uplink).Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0120] In some implementations, the NCD is configured to capture, aggregate, and / or process data from one or more sensors integrated with the modular luminaire and / or from one or more remote devices (e.g., loT devices) that are in wireless communication with the modular luminaire. The NCD may be configured to transmit sensed data and / or derived analytics to the network entity via one or more wireless links, including via encrypted communications and authenticated sessions. In some implementations, the NCD performs local data buffering, store-and-forward, time stamping, and / or edge-computing operations such that data capture and local control can continue during intermittent backhaul connectivity.

[0121] In some implementations, to improve reliability of wireless communications, the NCD is configured to implement one or more wireless robustness techniques, including one or more of: automatic repeat request (ARQ) messaging; acknowledgements and retries; forward error correction (FEC); interleaving; adaptive coding and / or modulation; antenna diversity; beamforming; frequency hopping; channel selection; transmit-power control; and / or failover between different wireless communication protocols. In some implementations, the NCD is configured to select between a wired communication path and a wireless communication path based on link status, bandwidth availability, latency, power consumption, and / or security policy.

[0122] In some implementations, the modular luminaire is configured to be commissioned and / or provisioned using a short-range wireless interface (e.g., Bluetooth, Li-Fi, near-field communication (NFC), RFID, or other short-range wireless techniques) that supports secure onboarding, device authentication, and network credential provisioning.NETWORK LIGHTING SYSTEM (NLS) AND NETWORK CONNECTOR SYSTEM

[0123] FIG. 1 is a system block diagram of an example of an implementation of modular luminaire 100 in accordance with the present disclosure. The modular luminaire 100 may be part of a network lighting system (NLS) 102 and include a lighting assembly 104 with a first connector system 106 and an optional second connector system 108. As an example, if the optional second connector system 108 is present, the lighting assembly 104 may be a tubular lighting assembly having a body 110 and the first connector system 106 and the optional second connector system 108 are located on opposite ends of the body 110 along a length 112 of the lighting assembly 104. In this example, the first connector system 106 and optional second connector system 108 may be electrically coupled to a remote power source 114 and one or both of the first connector system 106 and the optional second connector system 108 may beAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026in signal communication with a network entity 116. As an example, the network entity 116 may be, or include, one or more network devices, that may include, for example, a server type of computer-based device, control device / module, network switches, communication devices / sy stems, one or more peripheral devices, or other similar types of processing, control system, and / or communication systems.

[0124] FIG. 2 is a system block diagram of an example of an implementation of a connector system 200 in accordance with the present disclosure. Turning back to FIG. 1, each of the first connector system 106 and the optional second connector system 108 shown may be implemented as the connector system 200 shown in FIG. 2. The connector system 200 may include an end connector board 202 and a network communication device (NCD) 204 that are in signal communication with each other. In this example, the end connector board 202 may include a printed circuit board (PCB) that includes electrical connectors, circuits, components, and devices that are configured to electrically couple the end connector board 202 to the lighting assembly 104, and remote power source 114, and optionally allow the end connector board 202 to be in signal communication with the network entity 116. The NCD 204 may include any type of communication device that allows the NCD 204 to optionally communicate with the network entity 116, one or more remote devices 206, or both. As an example, the NCD 204 may include, for example, a universal integrated circuit card (UICC), a wireless fidelity (Wi-Fi) transceiver (i.e., covered by IEEE 802.11), wireless local area network (WLAN) transceiver (i.e., covered by IEEE 802.11), Bluetooth® transceiver (i.e., covered by IEEE 802.15.1), Zigbee transceiver (i.e., covered by IEEE 802.15.4 low-power, low-data-rate wireless mesh networking standard), cellular transceiver, light fidelity (Li-Fi) transceiver (i.e., covered by IEEE 802.11bb), low power, wide area networking (LoRaWan) transceiver, or other type of communication component and / or device. The NCD 204 may also include one or more sensors. In this example, the NCD 204 may be optionally in signal communication directly with the network entity 116, in signal communication with the network entity 116 indirectly through the end connector board 202, or both.

[0125] In other examples of implementations, an NCD may be configured to provide gateway functionality, including routing, bridging, relaying, or translating communications between (i) a wired interface (e.g., an Ethernet or other data interface coupled via the end connector board) and (ii) one or more wireless interfaces (e.g., Wi-Fi, cellular, satellite, Bluetooth, Zigbee / Thread, LoRaWAN, Li-Fi). As another example, multiple modularAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026luminaires may form a wireless mesh network and the NCD participates as a mesh node to forward data between modular luminaires and / or toward a network entity.

[0126] As another example, the NCD and / or the modular luminaire may support commissioning, provisioning, and maintenance using a local tool such as a mobile device, a handheld commissioning device, or a service interface. Commissioning may be performed using a short-range wireless protocol (e.g., Bluetooth®, NFC / RFID, Wi-Fi Direct) and / or a physical service connector (e.g., USB). Commissioning can include securely onboarding the modular luminaire to a network, configuring network credentials or profiles (including UICC / eSIM profiles), registering sensors, setting operating parameters, and / or initiating firmware updates.

[0127] As another example, the NCD may be configured to detect a communication error condition or degraded link state and to automatically initiate a corrective action. A communication error condition can include, for example, failure to as soci ate / authenticate, repeated packet loss, excessive latency, insufficient signal quality, inability to establish a link, or a loss of a backhaul connection. Corrective actions can include, for example, adjusting transmit power or channel parameters, re-selecting an access point, changing frequency / channel, switching between communication modes, enabling a fallback protocol, buffering data for later transmission, or sending diagnostic information to the network entity.

[0128] In this disclosure, the disclosed circuits, components, modules, and / or devices of, or associated with, the end connector board 202, NCD 204, network entity 116, remote power source 114, one or more remote devices 206, and other soon to be discussed circuits, components, modules, and / or devices are described as being “in signal communication” (or interchangeably as “in communication”) with each other, where signal communication refers to any type of communication and / or connection between the circuits, components, modules, and / or devices that allows a circuit, component, module, and / or device to pass and / or receive signals and / or information from another circuit, component, module, and / or device. The communication and / or connection may be along any signal path between the circuits, components, modules, and / or devices that allows voltages, currents, signals and / or information to pass from one circuit, component, module, and / or device to another and includes wireless or wired signal paths. The signal paths may be physical, such as, for example, conductive wires, electromagnetic wave guides, cables, attached and / or electromagnetic or mechanically coupled terminals, semi-conductive or dielectric materials or devices, or other similar physical connections or couplings. Additionally, signal paths may be non-physical such as free-spaceAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026(in the case of electromagnetic propagation) or information paths through digital components where communication information may be passed from one circuit, component, module, and / or device to another in varying digital formats without passing through a direct electromagnetic connection.

[0129] In FIG. 3, a system diagram of an example of an implementation of a NLS 300 is shown utilizing a plurality of modular luminaires 302 in accordance with the present disclosure. In this example, NLS 300 may include a network entity 304, remote power source 306, and the plurality of modular luminaires 302. In this example, the plurality of modular luminaires 302 may include, for example, N modular luminaires that include a first modular luminaire 308, second modular luminaire 310, and Nth modular luminaire 312. In some examples, the plurality of modular luminaires 302 may only include two modular luminaires (i.e., the first modular luminaire 308 and second modular luminaire 310), while in other examples the plurality of modular luminaires 302 may include any number of modular luminaires that the NLS 300 is capable of powering, communicating with, and / or controlling.

[0130] In this example, each modular luminaire of the plurality of plurality of modular luminaires 302 may be implemented, for example, as the modular luminaire 100 shown in FIG.1. The remote power source 306 may be implemented, for example, as the remote power source 114 and the network entity 304 may be implemented, for example, as the network entity 116, both shown in FIG. 1.

[0131] As a further example, each modular luminaire may be individually in signal communication with both the network entity 304 and the remote power source 306 either directly or through other corresponding modular luminaires. For example, the first modular luminaire 308, second modular luminaire 310, and the Nth modular luminaire 312 may each be individually and directly in signal communication with both the network entity 304 and the remote power source 306 (as shown in FIG. 3) or may be partially in direct signal communication with both the network entity 304 and the remote power source 306 and partially in indirect signal communication with the network entity 304 and the remote power source 306 as shown by the dashed lines between the first modular luminaire 308 and second modular luminaire 310, and the second modular luminaire 310 and the Nth modular luminaire 312. As a further example, the first modular luminaire 308 and Nth modular luminaire 312 may be in signal communication with (e.g., being electrically coupled) to remote power source 306, while the first modular luminaire 308 is also in signal communication with the network entity 304. In this example, the second modular luminaire 310 and any other modular luminaires betweenAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026the second modular luminaire 310 and the Nth modular luminaire 312 may optionally not be in direct signal communication (i.e., there is no direct wired or wireless connection) with either the network entity 304 and / or the remote power source 306. In this example, these modular luminaires may be in indirect signal communication with both the network entity 304 and / or the remote power source 306 via their corresponding adjacently connected modular luminaire. For example, the second modular luminaire 310 may be in signal communication with either the network entity 304 and / or the remote power source 306 via the first modular luminaire 308 that is in signal communication with both the network entity 304 and the remote power source 306. In this example, power from the remote power source 306 may be received by the second modular luminaire 310 via the first modular luminaire 308 and the second modular luminaire 310 may also communicate with the network entity 304 via the first modular luminaire 308. Other examples may include other combinations of different modular luminaires.

[0132] The remote power source 306 may be implemented as a power system that may include, for example, either an alternating current (AC) power panel 314, an electric generator 316, a solar system 318, other power source, or any combination thereof. In the case of the remote power source 306 including an AC power panel 314, the AC power panel 314 may receive electrical power from an external power source 320 such as, for example, an external power line from a utility company.

[0133] As another example, the remote power source may include a direct current (DC) power source such as a DC power supply, a rectified AC source, a building DC distribution bus, a PoE power sourcing equipment (PSE), a battery energy storage system, or another local or remote DC source. As an example, the remote power source provides low-voltage DC (e.g., nominal 5V, 12V, 24V, 48V, or other values) and / or provides regulated DC suitable for powering LED drivers, communication devices, processors, and sensors.

[0134] The network entity 304 may include, for example, one or more of the following: one or more computers 322; one or more network switches 324, one or more control modules 326; one or more peripheral devices 328; one or more memory devices 330; and one or more communication devices 332. In this example, the one or more computers 322 may include one or more server type of computer systems, the one or more network switches 324 may include, for example, an Ethernet and / or optical network switch, and the one or more communication devices 332 may include one or more transmitters, receivers, and / or transceivers.

[0135] In FIG. 4, a system diagram of an example of another implementation of a NLS 400 is shown utilizing a plurality of modular luminaires 402 each having a corresponding lightingAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026assembly and at least one corresponding connector system in accordance with the present disclosure. In this example, the NLS 400 includes the plurality of modular luminaires 402, the network entity 304, and remote power source 306. As a further example, each modular luminaires of the plurality of modular luminaires 402 may include a corresponding first connector system, lighting assembly, and optionally a second connector system. For example, a first modular luminaire 404 may include a first lighting assembly 406, a first connector system 408, and an optional second connector system 410. A second modular luminaire 412 may include a second lighting assembly 414, a third connector system 416, and an optional fourth connector system 418. An Nth modular luminaire 420 may include a third lighting assembly 422, a fifth connector system 424, and an optional sixth connector system 426. In this example, the first modular luminaire 404, the second modular luminaire 412, and themodular luminaire 420 may be in signal communication and operate in the same fashion as previously described in relation to the first modular luminaire 308, the second modular luminaire 310, and the Nth modular luminaire 312, except that in this example, the power received from the remote power source 306 and any communication between the network entity 304 and the corresponding first modular luminaire 404, the second modular luminaire 412, and the Nthmodular luminaire 420 is via the corresponding at least the first connector system 408, the third connector system 416, and the fifth connector system 424.

[0136] Turning to FIG. 5, a system diagram of an example of an implementation of another NLS 500 is shown utilizing modular luminaires that include tubular lighting assemblies in accordance with the present disclosure. In this example, each of the tubular lighting assemblies may be light emitting diode (LED) lighting assemblies that include one or more LED elements.

[0137] As a further example, the NLS 500 may include two network compatible linear LED lighting assemblies (i.e., a first linear LED lighting assembly 502 and a second linear LED lighting assembly 504 - also generally referred to as lamps) that are arranged end-to-end in series along a channel 506 along a ceiling grid of a room or other structure. In this example, the channel 506 may include a horizontally extending ledge 505 and vertically extending divider 507, as is typical of the upside-down T channels suspended by wires, cables or other means from the overhead structure. The first linear LED lighting assembly 502 has opposite connector systems (i.e., first connector system 508 and a second connector system 510), which are secured to the ceiling grid by mounting clips 512 and 514 respectively. The second linear LED lighting assembly 504 is similarly mounted using clips 516 and 518 at corresponding connector systems (i.e., a third connector system 520 and a fourth connector system 522),Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026respectively. In this example, the first linear LED lighting assembly 502 and second linear LED lighting assembly 504 may be networked to each other by a first jumper cable 524 having, for example, a male plug at each end mated with the corresponding network (e.g., Ethernet) jack in the end wall of the corresponding connector system 510 and 520. The second linear LED lighting assembly 504 may be networked to another adjacent linear LED lighting assembly of the system (not shown) using second jumper cable 526, and additional linear LED lighting assembly may be similarly mounted to the ceiling grid and connected to each other. This serially connected branch of linear LED lighting assembly may be networked to a centralized power distribution and control system through a signal path (i.e., cable 528) having a first plug 530 inserted in a jack connector of the first connector system 508 of the first linear LED lighting assembly 502. The jumper cable 526 may also be in signal communication with both the second connector system 510 and the third connector system 520 with a second plug 531 and a third plug 533, respectively, and the second jumper cable 526 may be in signal communication with the fourth connector system 522 via a fourth plug 535. If the jumper cables are sufficiently long, it may be preferable to keep their main span above the ceiling tiles and concealed from view. Alternatively, the cable may be concealed using a wiring raceway adapted to connect to the ceiling grid channels between adjacent lamps.

[0138] In this example, the first linear LED lighting assembly 502 and the second linear LED lighting assembly 504 may be part of a plurality of modular luminaires 532 that are in signal communication with both a remote power source 534 and a network entity 536 via the cable 528 and a network switch 538. The remote power source 534 may be the AC power panel 314 (shown in FIG. 3) that receives power from an external power source 320. In this example, the network switch 538 may be, for example, an Ethernet switch that is optionally part of the network entity 536.

[0139] In this example, a power and control system may include the network switch 538, which receives AC power over power line 540 from the AC power panel 314. The network switch 538 may also receive data from both the network entity 536 and the plurality of modular luminaires 532. Power and data are transmitted and communicated from the network switch 538 to the serially connected plurality of modular luminaires 532 over the cable 528 and the intermediate jumper cables (e.g., the first jumper cable 524). In this example, data may also be communicated from the plurality of modular luminaires 532 to the network entity 536 via the network switch 538.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0140] As a further example, the network entity 536 may also include a control module 542 that is also in signal communication with the network switch 538 (via signal path 544, which may be another cable) for receiving power at the control module 542 and communicating data between the control module 542 and the network switch 538. In this example, the control module 542 may be a central point of communication and may coordinate all data communications with the plurality of modular luminaires 532 and may also control the power supplied to the individual linear LED lighting assemblies of the plurality of modular luminaires 532. As an example, the control module 542 may include one or more processors that may include one or more computers or servers. As an example, various peripheral devices may be in signal communication with and networked to the control module 542, such as, for example, a computer 546 connected via signal path 548 (which may be a wired or wireless signal path) and a peripheral device 550 via signal path 552 (which may be a wired or wireless path), which may represent a variety of devices such as, for example, dimmers, sensors and controllers. It is appreciated by those persons of ordinary skill in the art that other peripheral devices (not shown) may also communicate with the control module 542 wirelessly, using, for example, Wi-Fi, Bluetooth®, Cellular, or other available wireless communication protocols. In one alternative, the control module 542 and network switch 538 may be implemented as a signal unit rather than as separate connected components and both may be part of the network entity 536.

[0141] The NLS 500 may be a fully networked LED lighting system capable of a variety of smart lighting functionalities. As an example, the power 554 provided to the first linear LED lighting assembly 502 can be further distributed over the first jumper cable 524 to the second linear LED lighting assembly 504 and then to each consecutive linear LED lighting assemblies in the chain of the plurality of modular luminaires 532 in a like manner. Control data, commands, and other data may be communicated to NCDs (that may be implemented, for example, as the NCD 204 of FIG. 2) mounted within each connector system of each networked LED lighting system of the chain using a suitable addressing mechanism, with each NCD processing only those messages that are addressed to that connector system. Operational data generated or collected by the individual connector system may be communicated back to the control module 542 and / or one or more peripheral devices 550 over the same network path. In this example, the NLS 500 may be easily and inexpensively deployed using standard computer and networking equipment without requiring alteration or removal of existing lighting infrastructure or the installation of conventional tube lighting fixtures in the case of newAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026construction. It is appreciated by those persons of ordinary skill that the NLS 500 disclosed herein make it possible to deploy a complete room lighting system without installing new lighting fixtures or being confined to the physical arrangement of existing tube lighting fixtures in the ceiling grid.

[0142] In this example, the NLS 500 may utilize power of Ethernet (PoE) technology to provide power to both the plurality of modular luminaires 532 and optionally the network entity 536.

[0143] In general as described in this disclosure, PoE provides both data and power connectivity in one cable so that powered devices do not require a separate cable for each need. As an example, PoE has been used, for example, to power IP telephones, IP cameras, wireless access points, and remote Ethernet switches. PoE can provide DC power over long cable runs, e.g. hundreds of feet. Universal Serial Bus (USB) (including USB Type-C connectors and USB Power Delivery (USB-PD)) and IEEE 1394 (FireWire) are examples of other standardized technologies for high-speed data transfer, both of which also provide data and power. These techniques may be used for connecting peripherals to computers and recharging digital devices such as smartphones. These standards may regulate communication, encoding and device addressing protocols, port specifications, cabling requirements, connector designs, etc. to assure compatibility among devices, components and products, and to provide plug-and-play capability. It is appreciated that while PoE is described in many of the examples in this disclosure, the techniques, systems, and methods disclosed herein are not limited to PoE implementations and are also applicable to other standardized technologies capable of using a single cable to provide both data connectivity and electrical power to devices.

[0144] It is further appreciated that in some implementations the modular luminaires are powered using AC wiring and / or DC wiring (including via existing lamp holders or fixture wiring) while network communications are performed wirelessly. For example, one or more modular luminaires may receive electrical power via an AC lamp holder or a DC power bus and may communicate with the network entity using Wi-Fi, cellular, satellite, Bluetooth, Zigbee / Thread, Li-Fi, and / or other wireless protocols, including via a mesh network formed among multiple modular luminaires. In many of these examples, wired network cabling between lamps (e.g., Ethernet jumper cables) may be reduced or eliminated.

[0145] In general, PoE provides both data and power connectivity in one cable so that powered devices do not require a separate cable for each need. As an example, PoE has been used, for example, to power IP telephones, IP cameras, wireless access points, and remoteAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026Ethernet switches. PoE can provide DC power over long cable runs, e.g. hundreds of feet. Universal Serial Bus (USB) and IEEE 1394 (FireWire) are examples of other standardized technologies for high-speed data transfer, both of which also provide data and power. These techniques may be used for connecting peripherals to computers and recharging digital devices such as smartphones. These standards may regulate communication, encoding and device addressing protocols, port specifications, cabling requirements, connector designs, etc. to assure compatibility among devices, components and products, and to provide plug-and-play capability. It is appreciated that while PoE is described in this example, the techniques, systems, and methods disclosed herein are by no means limited to PoE implementations and are also applicable to other standardized technologies capable of using a single cable to provide both data connectivity and electrical power to devices.

[0146] It is also appreciated by those of ordinary skill in the art that in FIG. 5, shows that the linear LED lighting assemblies are mounted close together for purposes of illustrating the features of the NLS 500, the mounting clips and integrated PoE capabilities of the linear LED lighting assemblies provide the flexibility to arrange the linear LED lighting assemblies as desired to provide efficient lighting that meets the characteristics and needs of each particular application. It is noted that the linear LED lighting assembly distribution is not confined by the location of existing fixtures or building codes governing the placement of new fixtures in drop ceiling grids.

[0147] A 30-feet (ft) by 20-ft room, for example, may be illuminated by fifteen 4-ft linear LED lighting assemblies, arranged in three rows spaced, for example, approximately 6-ft apart and with 2-ft spacing between the ends of the five linear LED lighting assemblies in each row. In another example, a commercial workspace may have employee workstations that receive inadequate lighting due to their location between adjacent banks of ceiling grid lighting fixtures. Such a lighting system is easily augmented by mounting the disclosed modular luminaires having the linear LED lighting assemblies to the ceiling grid in between the existing fixtures to provide supplemental illumination on those intermediate regions.

[0148] Of course, many variations of the NLS 500 illustrated are possible, supported by the network enabled modular luminaires disclosed herein and convenient mounting clips for mounting the modular luminaires to the ceiling grid. Various control, sensor and computing devices may also be included in the NLS 500 to achieve desired objectives, and the centralized control system may connect to individual modular luminaires using a variety of network configurations, including the branch chain configuration shown, direct hub and spokeAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026connections to individual lamps, or any other network configuration. The modular luminaires may be equipped with network-enabled jacks and associated electronic components at one or both ends (i.e., at the corresponding connector systems) to support the desired network architecture.

[0149] Other mechanisms may be utilized to secure the modular luminaires to the ceiling grid. In one aspect, the modular luminaires can be secured to the ceiling grid using magnets to force the lamp upward against one or more metal channels of the ceiling grid. The magnets may be integrated, for example, into the end cap assemblies of the modular luminaires, or may be provided separate from the modular luminaires.

[0150] It is appreciated that a networked automated modular luminaires based LED lighting system consisting of individual modular luminaires mounted directly the ceiling grid such as NLS 500 offers certain advantages because building and safety codes govern various aspects of the wiring, electrical equipment and other devices installed in the space above a dropped ceiling. As such, new wiring must be routed in a way that will not interfere with existing equipment, and any installation into this space must comply with all regulations and will normally require the building owner to obtain a new inspection to certify compliance. The disclosed network compatible modular luminaires allow the entire system (i.e., the plurality of modular luminaries 532) to be installed below the drop ceiling without altering the space above.

[0151] As such, the installation process is simple, comparable to hanging holiday lighting. It involves simply attaching the mounting clips or other mounting devices to the ceiling grid at the desired locations, securing the modular luminaires to the clips, and then connecting the modular luminaires to the network using standard network (e.g., Ethernet) cables. Setting up the centralized control equipment of the network entity 536 may involve routine plug-and-play steps comparable to connecting peripherals to a personal computer, mostly involving plugging cables into corresponding jacks and turning on power switches. The NLS 500 may be installed directly by the consumer or a professional technician, but generally does not require use of an electrician or follow-up evaluation by a building inspector. And it makes it possible to quickly and economically install lighting in any room having a dropped ceiling and access to a highspeed Internet connection.EXAMPLES OF THE MODULAR LUMINAIRES AND THE CONNECTOR SYSTEM

[0152] In FIG. 6A, a perspective view of an example of an implementation of a cylindrical, network compatible linear LED lighting assembly (LED tube lamp) 600 having an externalAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026heat sink extending over a portion of the circumference of an elongate body portion and having end cap assemblies at opposite ends of the body, showing an external Ethernet jack connected to the lamp by a jumper cable extending through the end wall of the end cap. FIG. 6B is a side perspective view of the LED tube lamp of FIG. 6A with portions cut away to expose internal components, and showing an enlarged view of an end cap assembly comprising and cable connector mounted to a horizontally oriented PCB connector board for connecting an Ethernet cable and jack between a net.

[0153] Specifically, FIG. 6A shows a perspective view of a cylindrical LED tube lamp 600 having an external heat sink 602 extending over a portion of the circumference of an elongate body portion, and having end cap assemblies 604 and 606 at opposite ends of the body secured to the tube body by fasteners 608 and 610. FIG. 6B shows a partial cut-away view of a portion of the LED lamp 600 with a view of internal components of end cap assembly 606. The lamp body as depicted may illustrates a standard LED tube lamp design having an internally mounted LED emitter board 612 on which a series of LEDs 614 are arranged in one or more rows. A transparent or translucent outer lens 616 extends around a portion of the lamp body. Other lamp designs are also possible, including those having multi-sided heat sink and multiple LED emitter boards mounted at angles to each other as disclosed in other embodiments.

[0154] As shown in FIG. 6B, end cap assembly 606 houses a horizontally disposed internal PCB connector 618, which is in signal communication with connector 620 internal to the lamp body through conductive leads 622. An edge portion of the PCB connector 618 is supported within a slot 624 extending horizontally along inner surface of end wall 626 of the end cap assembly, and a post 628 supports the PCB at its opposite end. The connector 630 may be mounted on the PCB connector 618 and in signal communication (i.e., electrically coupled and / or connected) to the PCB connector 618 by pins 632. A short branch of network cable 634 may extend from the connector 630 to an external module 636, which in this example may be an Ethernet jack configured to receive a standard Ethernet cable plug for transmitting power and communicating data between a network entity (e.g., network entities 116, 304, or 536) and internal components of the LED tube lamp 600. The branch cable 634 may extend through an opening 640 formed in the end wall 626 of the end cap assembly 606. The connector 630 may alternatively connect to the emitter board 612 or to another circuit board associated with the LED tube lamp 600 body, and the branch cable 634 may extend through an opening located on a different surface of the end cap assembly 606 or through an opening of the heat sink 602. In this example, the LED tube lamp 600 may be mounted to a ceiling grid using the clip systemAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026or as otherwise described herein, with the branch cable 634 and the external module 636 being positioned above the ceiling tiles (not shown) to be out of view.

[0155] In this example, the end cap assembly 606 may be configured as the connection system 200 shown in FIG. 2 such that the end cap assembly 606 would include an end connector board 202 and the NCD 204. In this example, the PCB connector 618, post 628, connector 630, and pins 632 may be part of, or associated with, the end connector board 202.

[0156] FIG. 7 is a perspective view of an example of an implementation of a linear LED lamp 700, and shows cooperating connector assemblies (that include a connector system) at opposite ends of the body of the linear LED lamp 700, with the connector assembly at one end comprising a PoE enabled sleeve adaptor configured to provide integrated power and data at one end of the linear LED lamp 700. FIG. 8 is an enlarged perspective view of an example of an implementation of the PoE enabled connector sleeve 702 of FIG. 7, showing an Ethernet cable plug connected to an integral jack at a base end of the sleeve adaptor and including a male Ethernet plug extending within the sleeve receptacle of the adapter.

[0157] As such, FIGS. 7 and 8 illustrate another example of a NLS 704 to be connected to a network (including the network entity) for power and data communications and centralized smart lighting control. In this example, the NLS 704 may be configured to use single end power linear LED lamps in which only one end of the linear LED lamp 700 is configured to connect to and receive power from, for example, a local area network (LAN) (not shown). One end of linear LED lamp 700 may include an end cap 706 having an opening 708 in a sidewall thereof for engaging a snap-fit connector 710. The snap-fit connector 710 may include a base portion 712 extending to a narrowed leading end portion 714. The snap-fit connector 710 mounts to tabs of a lighting fixture support via slots adjacent side flanges 716. In this example, the snap-fit connector 710 may not be configured to receive external power or communicate data signals, and functions only to secure the end cap 706 to support 718. In this example, deployable portions 720 may be attached via a live hinge 722 to opposite sides of base portion 712, and capture an upper sidewall portion of the end cap 706 as the leading end portion 714 is inserted through the opening 708 and into an engaged position. Actuators connected to the deployable portions 720 allow the snap-fit mechanism to be disengaged from the end cap 706 assembly to separate the two components. The opposite end of linear LED lamp 700 may have an end cap assembly 724 comprising an integral Ethernet jack (not shown) accessible from the end wall 726 of the end cap assembly 724. The NLS 704 may also include the connector sleeve 702, which is adapted to mount to the support 718 via a second snap-fit connector 725 that mayAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026be optionally part of the connector sleeve 702. A base portion 728 of connector sleeve 702 includes slots 730 between flanges 732 and 734 on opposite sides thereof into which tabs of support 718 slide so that the connector sleeve 702 can be secured to support 718. The base portion 728 extends toward a sleeve portion 736 comprising a continuous cylindrical sidewall, which forms a receptacle 737 having an open end facing towards the opposite first snap-fit connector 710 and sized to receive the end cap assembly 724 of the linear LED lamp 700. The sleeve portion 736 is preferably of a cross-sectional shape that conforms to the cross-sectional shape of end cap assembly 724, which, in this example, is cylindrical. The connector sleeves may comprise a sleeve portion of other cross-sectional geometries, such as generally triangular, trapezoidal square or rectangular, are also contemplated for use with other lamps having corresponding end cap cross-sectional geometries. In one preferred form, the sleeve forms a receptacle of a generally triangular cross-section for receiving a generally triangular end cap assembly of a lamp comprising a multi-sided heat sink mounting multiple LED emitter boards.

[0158] As shown in the enlarged view of FIG. 8, the connector sleeve 702 may further comprise an internal adaptor module 740 of a general L-shape configuration. A first vertically extending portion 742 may comprise a female Ethernet jack accessible through the upper facing end wall of base portion 728. In this example, the jack (not shown) may be adapted to receive an Ethernet plug 744 attached to the end of a cable 746 to connect the sleeve to the LAN. The adapter module 740 may further include a second horizontally extending portion 748 that includes, for example, an integral Ethernet plug 750 at its tip. In this example, leads that are internal to the adapter provide electrical pathways between the pins of the jack (i.e., that receives the Ethernet plug 744) and the corresponding pins of plug 750. In this example, the sleeve portion 736 may be configured as a connector system 200 of FIG. 2 that also includes an NCD 752.

[0159] In this example, the linear LED lamp 700 may be installed in the fixture by inserting the end cap assembly 724 linearly along the length of the linear LED lamp 700 body and into the receptacle 737 of the connector sleeve 702. The connector sleeve 702 may be preferably sized so that end cap assembly 724 is easily guided into the receptacle 737, where it is supported in the vertical direction yet rotatable as well as adjustable in the horizontal direction. The linear LED lamp 700 is adjusted such that the receptacle of the jack in the end wall is aligned with plug 750, and then the linear LED lamp 700 is further advanced linearly until the plug 750 is fully inserted in the jack. In this configuration, the opening 708 in the other end cap 706 may be aligned with leading end portion 714 of the snap-fit connector 710. The end cap 706 mayAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026be moved upward so as to guide the leading end portion 714 into the snap-fit connection with the end cap 706. Securing the snap-fit connection locks the linear LED lamp 700 at its proper rotational orientation and prevents the linear LED lamp 700 from backing out linearly from connector sleeve 702, and the linear LED lamp 700 is thus securely maintained in an operational state. To remove an installed linear LED lamp 700, the snap-fit connection may be released using the actuators, which allows the end cap assembly 724 to be withdrawn from the receptacle 737 of connector sleeve 702.

[0160] This type of connector system utilizing the connector sleeve 702 and snap-fit connectors may provide convenience to the lamp installer and a more efficient installation methodology. With standard linear LED tube lamps typically ranging from 2 to 8 feet in length, it is cumbersome to properly align the cooperating components into the proper engaged position while handling a portion of the lamp that is significantly displaced from the lamp end being installed. Thus, lamp installation typically requires the installer to grasp a first end of the lamp and position it into engagement with its corresponding lamp holder, and then move to a position proximate the opposite end of the lamp to manipulate the opposite end into engagement with its lamp holder. Using the connector sleeve 702, however, both ends of the lamp may be installed by manipulating the lamp from the no power end. While grasping the lamp near the no power end, the installer may guide the opposite power end into the receptacle opening of connector sleeve 702 and gently adjust the lamp orientation until the plug inserts within the end cap jack receptacle. This requires only minimal dexterity. After the power end is seated in the receptacle 737 of the connector sleeve 702, the installer then moves the no power lamp end directly upward from the separated position and into snap-fit engagement with snap-fit connector 710 pre-mounted on support 718. Potentially significant time and associated labor savings may be achieved with this NLS 704 and installation method, especially in commercial environments requiring installation of hundreds or potentially thousands of linear LED tube lamps.

[0161] The network enabled LED lamps and connector systems disclosed herein provide safe and reliable means for securing linear LED lamps to a lighting fixture and providing networked power and data connectivity directly to the lamp. The disclosed snap-fit connector systems and corresponding network compatible lamp end cap assemblies allow implementing PoE or other network compatible LED tube lamps into existing facility lighting fixtures, without the need to replace existing fluorescent lighting fixtures or to install new integrated LED fixtures. This eliminates the added cost of disposing of the existing fixtures and altering the currentAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026fixture design and layout, greatly reduces labor and time of install, and avoids scheduling conflicts and disruptions of the work environment of the facility. Network cables cost very little compared to heavy duty copper wire and conduit used for traditional lighting, and integrated power and data networking technology has the potential to greatly enhance the power efficiency gains of LED tube lighting compared to conventional fluorescent tube lighting systems. The ceiling grid mounted network compatible LED lamps disclosed herein provide additional options for quickly and inexpensively installing smart LED lighting systems in numerous residential and commercial applications. These novel LED lamp and connector configurations allow for immediate adoption and more rapid penetration of integrated power and data technology in the lighting industry. Users may conveniently and inexpensively update a lighting system with simple lamp replacement as lamp performance and features improve with further technology advances. The inventions disclosed herein thus enable the next generation of digitally controlled and networked smart LED lighting systems to be implemented in the conventional tube lamp format, eliminating the need to replace the massive amount of infrastructure already in place to support this dominant and highly advantageous lighting format.

[0162] In FIG. 9A, a side perspective view of an example of an implementation of a PoE enabled snap-fit connector 900 is shown. The snap-fit connector 710 and second snap-fit connector 725 may be implemented as the snap-fit connector 900. In this example, the snap-fit connector 900 may include a proximal base end for mounting to a lighting fixture, a midportion including a snap-fit actuator assembly and extending to a distal tip portion configured as, for example, an integral Ethernet plug where cable wiring may be crimped directly to pins of the Ethernet plug. FIG. 9B is right side view of the PoE enabled snap-fit connector 900 of FIG. 9B.

[0163] The snap-fit connector 900 may have a base portion 902 and a narrowed leading end portion 904. A flange 906 may extend around the periphery of the base portion 902 at a proximal end thereof. Flanges 908 and 910 extend outwardly from opposite sidewalls of base portion 902 and define slots between the flanges 908, 910 and the peripheral flange 906 for engaging tabs of a support of a lighting fixture. Leading end portion 904 may be configured to insert into an opening in an upper surface of a lamp end cap assembly, and the tip portion of the leading end is configured as, for example, an Ethernet standard plug 912 as shown. The leading end portion 904 may have deployable parts 914, 916 attached to the sidewalls by live hinges 918, 920. The snap-fit connector 900 may also include actuators 922, 924 connected toAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026the deployable parts 914, 916 on opposite sides for causing the corresponding deployable parts to shift back and forth between the engaged and assembly positions. In this example, the snap-fit connector 900 includes a central channel 926 extending from its base end to the leading end and providing a pathway for an end portion of cable 928 to extend through the connector directly to the pins or contacts 932 of plug 912. The individual wires of the contacts 932 of the cable 928 may be crimped to the pins or contacts 934 of plug 912 in the conventional manner. The wire crimping step can be performed during installation of the lighting system. Alternatively, the snap-fit connector 900 may be supplied as an assembly including both the snap-fit connector 900 and a pre-attached branch cable of predetermined length. The assembly may also include a modular connector at the opposite end of the branch cable allowing for the connector assembly to be conveniently plugged into a corresponding modular connector of a main cable line of a networked lighting system.

[0164] In FIG. 10 A, a perspective view of an example of an implementation of a tubular lighting assembly 1000 is shown in accordance with the present disclosure. In this example, the tubular lighting assembly 1000 is shown as a linear LED lamp having a generally triangular cross-sectional shape that is releasably attached to two connector assemblies (i.e., first connector system 1002 and second connector system 1004) at opposite ends of the body of the tubular lighting assembly 1000. In this example, each of the two connector assemblies includes, for example, aPoE snap-fit connector 1006 and 1008, respectively.

[0165] In this example, the tubular lighting assembly 1000 may include a heat sink 1010 and one or more emitter panels 1012 having a plurality of LEDs 1014. As a further example, both the first end connector system 1002 and second connector system 1004 are shown to have a protruding section 1016 and optional second protruding section 1018, respectively, from the end cap assembly that includes a volume for a corresponding NCD (e.g., NCD 204 of FIG. 2) within the first connector system 1002 and second connector system 1004, respectively.

[0166] FIG. 10B is an enlarged view of one end of the tubular lighting assembly 1000 of FIG. 10 A. FIG.10B shows that the PoE snap-fit connector 1006 is configured to receive, as an example, a male Ethernet connector plug 1020 at a base end thereof. The plug 1020 may be in signal communication with the remote power source 114, network entity 116, or both via a cable 1022. In this example, the PoE snap-fit connector 1006 may be in signal communication with the end connector board 202 (shown in FIG. 2), the remote power source 114, network entity 116, via other devices, components, and / or circuitry.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0167] FIG. 11 is a system block diagram of an example of another implementation of a modular luminaire 1100 in accordance with present disclosure. In this example, the modular luminaire 1100 includes a first connector system 1102, a tubular lighting assembly 1104, and a second connector system 1106. In this example, the first connector system 1102 may be implemented as the connector systems 200, 702, or 1002, shown in FIGS. 2, 7, 8, 10A, and 10B, respectively, that includes an end connector board (not shown) and a NCD (not shown). Additionally, in this example, the second connector system 1106 is shown to not have a protruding section with a NCD similar to the example shown in FIGS. 7 and 8.

[0168] Turning to FIG. 12, a system block diagram of an example of yet another implementation of a modular luminaire 1200 is shown in accordance with present disclosure. This example is similar to the one shown in FIG. 11, except that in this example, the modular luminaire 1200 also includes a second connector system 1202 that also includes a NCD unlike the second connector system 1106 shown in FIG. 11. In this example, the second NCD may be located with a second protruding section 1204.

[0169] In FIG. 13 A, a side view of an example of an implementation of the first connector system 1102 having a protruding section 1108 in accordance with the present disclosure. FIG.13B is a top view of the first connector system 1102 shown in FIG. 13 A. In this example, the first connector system 1102 may include a NCD 1300 within the protruding section 1108 and a connector 1302 configured as the connector 1006 shown in FIGS. 10A and 10B. In this example, the connector 1302 may be configured to receive a snap-fit connector (e.g., the snap-fit connector 900 of FIGS. 9 A and 9B).

[0170] Turning to FIG. 14, a bottom view of an example of an implementation of a connector system 1400 physically attached to a portion of a tubular lighting assembly 1402 is shown in accordance with the present disclosure. This example is similar to the examples shown in FIGS. 10A through 13B, where the connector system 1400 includes a protruding section 1108 that extends outward from an upper portion 1406 of the connector system 1400 along a portion of the body of the tubular lighting assembly 1402.

[0171] FIG. 15A is a prospective front view of the connector system 1400 detached from the tubular lighting assembly 1402 (as shown in FIG. 14) in accordance with the present disclosure. In this view, the connector system 1400 is shown to have a connector 1500 at the top of the connector system 1400 (at the upper portion 1406 of the connector system 1400) that may be configured to receive a snap-fit connector (e.g., the snap-fit connector 900 of FIGS. 9A and 9B). The connector system 1400 is also shown to have an end connector board 1502 and aAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026NCD 1504, where the end connector board 1502 is shown located, for example, within the upper portion 1406 of the connector system 1400 and the NCD 1504 is shown located, for example, within the protruding section 1404 of the connector system 1400. Turning to FIG.15B, an offset front view of the connector system 1400 is shown and in FIG. 16, another front view of the connector system is shown.

[0172] FIG. 17 is a system block diagram of an example of yet another implementation of a modular luminaire 1700 in accordance with present disclosure. This example is similar to the one shown in FIG. 11 , except that the shape of the protruding section 1702 of the first connector system 1704 is different than the protruding section 1108 shown in FIG. 11. Instead of extending along the body of the tubular lighting assembly 1104, the protruding section 1702 extends outward from the tubular lighting assembly 1104.

[0173] In FIG. 18 A, a side view is shown of an example of the implementation of the modular luminaire 1700 shown in FIG. 17. FIG. 18B is a perspective bottom view of the modular luminaire 1700 shown in FIG. 18 A. In this example, the tubular lighting assembly 1104, the first connector system 1704 having a protruding section 1702, and the second connector system 1106 are shown. Additionally shown are a first connector 1800 and a second connector 1802 attached to the first connector system 1704 and second connector system 1106, respectively. In this example, both the first connector 1800 and a second connector 1802 may be implemented as snap-fit connector 900 shown in FIGS. 9 A and 9B.

[0174] It is noted that in all of the previous examples shown in FIGS. 2, 7, 8, 10A through 18B, the NCD is shown to be located in one of the connector system; however, it is appreciated by those of ordinary skill in the art that the NCD may be in signal communication with but physically located external to the connector system without deviating from the teachings of the present disclosure.

[0175] FIG. 19 is an exploded assembly view of a LED illuminating assembly 1900 comprising a three-sided modular LED lighting bar 1902 (LED light bar) providing a three-sided delta or triangular shaped non-curvilinear LED luminary 1904. FIG. 20 is an enlarged view of the right portions of the three-sided delta non-curvilinear LED luminary of FIG. 19. FIG. 20 is an enlarged view of the left portions of the three-sided delta non-curvilinear LED luminary of FIG. 19. The three-sided delta non-curvilinear LED luminary can have a three-sided delta triangular shaped metal heat sink 1905, such as formed from extruded aluminum. The intersecting comers 1906 providing apexes of the heat sink can be raised, rounded or chamfered, if desired. Elongated LED emitter PCB panels 1908, 1910, and 1912 can beAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026mounted or otherwise secured upon and / or positioned radially outwardly of the heat sink in a generally triangular or delta shape. Each of the LED emitter PCB panels can be rectangular and can contain one or more rows of aligned, aliquot, uniformly spaced modular LED emitters 1914. An internal non-switching elongated printed circuit board (PCB) driver 1916, also referred to as a driver board, can be positioned along the length of and within the interior area bounded by the heat sink. The heat sink can dissipate heat generated by the LED emitters and PCB driver. Emitter board terminals 1918, 1920, and 1922 can extend longitudinally outwardly from the LED emitter boards. Driver board terminals 1923 can be extend longitudinally outwardly from the PCB driver. The three-sided delta triangular shaped non-curvilinear LED luminary can have three-sided delta end cap PCB connectors 1924 and 1926 comprising connector end boards which are also referred to as end cap boards that can be secured to three-sided delta or triangular shaped end caps 1928 and 1930, respectively, by fasteners 1932, such as screws, through screw holes 1934 in the end caps. The end caps can have rounded corners 1936 or apexes. Power connector pins 1938 can extend laterally outwardly from the connector end boards through connector pin-receiving holes 1940 in the end caps for secure engagement with a light socket. The connector end boards can have end cap board terminals 1942 which extend longitudinally inwardly along its three sides which can connect to the emitter board terminals. The connector end boards can also have a driver board connecting terminals 1944 which extends longitudinally inwardly from central portions of the connector end boards and can be connected to the driver board terminals. A three-sided delta or triangular shaped covers 1946 can provide rims for positioning about the end caps. As best shown in FIG. 21, the connector end boards can each have a central U-shaped concave notched portion 1948 between two of the sides 1950 and 1952 and can have a lower third side 1954 which extends below the lower portions of the other two sides. The sides 1950 to 1956 can be straight, flat and planar.

[0176] FIG. 22 is an exploded assembly view of a LED illuminating assembly 2200 comprising a two-sided modular LED lighting bar 2202 (LED light bar) providing a two-sided elongated non-curvilinear LED luminary 2204 which is similar to the three-sided delta or triangular shaped non-curvilinear LED luminary of FIGS. 19-21 except there are only two elongated LED emitter PCB panels 2206 comprising modular LED emitter boards which can be mounted or otherwise secured upon and / or positioned radially outwardly of the two sides 2208 and 2210 of the three sides 2208 to 2212 of the three-sided delta or triangular shaped metal heat sink 2214. The two LED emitter panels can be positioned in a generally V shape.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0177] FIG. 23 is an enlarged view of the right portions of the two-sided non-curvilinear LED luminary of FIG. 22. Each of the LED emitter PCB panels can be rectangular and can contain one or more rows of aligned, aliquot, uniformly spaced LED emitters 2216. An internal non-switching elongated PCB driver 2218 can be positioned along the length of and within the interior area bounded by the heat sink. The heat sink can dissipate heat generated by the LED emitters and PCB driver. Emitter board terminals 2220 and 1 1, which are also referred to as emitter board connectors, can extend longitudinally outwardly from the LED emitter boards. Driver board terminals 2224 can extend longitudinally outwardly from the PCB driver. The two-sided delta triangular shaped non-curvilinear LED luminary can have three-sided delta or triangular connector end boards 2226 and 2228 comprising connector end boards which can be secured to three-sided delta or triangular shaped end caps 2230 and 2232, respectively, by fasteners 2234, such as screws, through screw holes 2236 in the end caps. Power connector pins 2240 can extend laterally outwardly from the connector end boards through connector pinreceiving holes 2242 in the end caps for secure engagement with a light socket. The connector end boards can have end cap board terminals 2244, which are also referred to as surface mount connectors, that can extend longitudinally inwardly along two of its three sides and can be aligned with and connect to the emitter board terminals. The connector end boards can also have a driver board connecting terminals 2224 which extends longitudinally inwardly from central portions of the PCB end cap connector boards and can be connected to the driver board terminals. An elongated light diffuser cover 2246 comprising a concave translucent or transparent light transmissive lens can cover the LED emitter boards for reflecting, diffusing and / or focusing light emitted from the LED emitters. The lens can be formed of plastic or glass and can be rounded, semicircular and positioned radially outwardly of the LED emitters. The lens can have inward facing feet 2248 which can snap fit about the heat sink.

[0178] FIG. 24 is an exploded assembly view of a LED illuminating assembly 2400 comprising a two-sided modular light bar 2402 providing another two-sided non-curvilinear LED luminary 2404 which is similar to the two-sided non-curvilinear LED luminary of FIGS.22-23 except that there are two sets or arrays 2406 of elongated LED emitter PCB panels comprising modular LED emitters which can be mounted or otherwise secured upon and / or positioned radially outwardly of the two sides of the three-sided delta or triangular shaped metal heat sink 2408.

[0179] FIG. 25 is an enlarged view of the right portions of the two-sided non-curvilinear LED luminary of FIG. 24. Each of the sets or arrays of modular LED emitter PCB panels haveAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026more than one LED emitter PCB panel, such as but not limited to, three elongated LED emitter PCB panels 2410, 2412, and 2414 providing modules which extend and are aligned and connected, lengthwise and longitudinally end to end via emitter PCB panel terminal connectors 2416 and 2418. Each of the LED emitter PCB panels can be rectangular and can contain one or more rows of aligned, aliquot, uniformly spaced LED emitters 2420. The LED luminary can have three-sided delta or triangular end cap connectors 2422 which comprise connector end boards that can be secured to three-sided delta or triangular shaped end caps 2424 by screws or other fasteners through screw holes 2426 in the end caps. Power connector pins 2428 can extend laterally outwardly from the connector end boards through connector pin-receiving holes in the end caps for secure engagement with end plugging into a light socket. The connector end boards can have end cap board terminals 2430 which can extend longitudinally inwardly along two of its three sides and can connect to the emitter board terminals. An elongated translucent or transparent light transmissive plastic lens 2432 comprising a diffuser cover of diffuser can cover the LED emitter boards. The lens can be rounded, semicircular and positioned radially outwardly of the LED emitters. The lens can have inward facing feet 2434 which can snap fit about the heat sink.

[0180] FIG. 26 is a perspective view of an end cap PCB connector 2600, also referred to as a connector end board or end cap board, for a LED illuminating assembly comprising a two-sided LED bar providing a two-sided delta or triangular non-curvilinear LED luminary, such as shown in FIGS. 22-23. The end cap PCB connector can have a central U-shaped concave notched portion 2602 between two of the sides comprising convex curved arcuate sides 2604 and 2606 and can have a lower third side, comprising a straight flat planar side 2608 which can extend below the lower portions of the two convex sides. The PCB connector can have connector pin-holes 2610, also referred to as AC power pin connectors or AC hot pin connector, as well as electrical traces 2612 for connecting the electrical components on the end cap PCB connector. As shown in FIG. 27, surface mount connectors 2614, 2616, 2618, which are also referred to as emitter board connectors or end cap board terminals, can be connected alongside portion of the connector end board in proximity to the sides of the connector end board. The surface mount connectors of the end cap PCB connector can be connected to drive board connectors 2620 (FIG. 28), also referred to as PCB driver connectors, of an internal nonswitching elongated driver board 2630 comprising a driver.

[0181] A three-sided delta or triangular shaped metal heat sink tube 2632 (FIG. 29), also referred to as a tubular heat sink, can be positioned peripherally about the driver board andAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026against the cap connector end board. The heat sink can have upwardly facing emitter boardsupporting channels 2634 and 2636 along its bottom edges to support elongated LED emitter PCB panels 2638 (FIG. 30), which are also referred to as modular LED emitter boards. The LED emitter PCB panels can be mounted or otherwise secured upon and / or be positioned radially outwardly of the heat sink to form a V-shaped array. Each of the LED emitter PCB panels can contain one or more rows of aligned, aliquot, uniformly spaced LED emitters 2640. The heat sink can dissipate heat generated by the LED emitters and driver board. Emitter board connectors 2642, which are also referred to as emitter board terminals, can extend from the ends of the emitter boards and connect to the surface mount connectors comprising end cap board terminals of the end cap PCB connector. Emitter traces 2644 can connect the LED emitters in series while end traces 2646 can connect the emitters to the emitter board connectors. An AC power trace 2648 can be positioned in parallel to an extra trace 2650 and a direct current (DC) trace 2652 on the emitter board. An elongated translucent or transparent light transmissive lens 2654 (FIG. 31) comprising a diffuser cover or diffuser can cover the LED emitter boards. The lens can be rounded, semicircular and / or positioned radially outwardly of the LED emitters. The elongated longitudinal lower ends 2656 of the lens can comprise feet and can fit in and be supported by channels of the heat sink. End caps 2658 (FIG. 32) can be positioned about the ends of the lens and end cap PCB connectors. FIG. 26 is a perspective view of the three-sided delta or triangular non-curvilinear LED luminary with the end cap and showing portions of the lens removed to illustrate the emitters on the emitter board and the AC and DC power traces connected to the surface mount connectors. As shown in FIG. 33, the end caps can have arcuate curved concave brackets 2660 comprising bracket segments which can extend longitudinally inwardly and can provide clamps positioned about portions of the periphery of the end caps to securely engage, grasp, snap fit, clamp and hold the top ends of the emitter boards. AC traces 3400 (FIG. 34) and DC traces 3402 can be connected to driver circuitry 3404 on the driver board 2630. In this example, the end cap PCB connector may have DC power terminals 3406 to conduct DC power to three LED strings as well as DC return terminals 3408 to receive DC from the LEDs. An AC neutral trace 3410 may extend from the opposite side. The end cap PCB connector can also have an AC neutral terminal 3412 and an AC hot terminal 3414.

[0182] Driver connectors 2620 (FIG. 35) can be connected to the driver circuitry as well as to the surface mount connectors 2616, also referred to as emitter board connectors, of the end cap PCB connector (connector end board or end cap board) 2612. In some arrangements, theAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026end cap connector board can have male connectors 3500 with longitudinally inwardly extending connector pins 3502 to matingly engage and plug into female connectors on the emitter boards and / or drive board and the end cap connector board can have female connectors 2614 to receive and plug into the longitudinally outwardly connector pins of matingly engageable (mating) male connectors on the emitter board and / or driver board. In the illustrated embodiment, there are a four-pin connectors at end of each emitter board and driver board, although for some longer light bars, it may be desirable to use six pin connectors.

[0183] It is appreciated by a person of ordinary skill in the art that in the examples described in relation to FIGS. 19 through 35, the end cap PCB connector 2600 may be an example of an implementation of the end connector board 202 and 1502 described in relation to FIGS. 2, 15 A, 15B, and 16. Additionally, while not shown directly in FIGS. 5, 7, 8, 18A through 25, and 33, the first connector system 508, second connector system 510, sleeve portion 736, first connector system 1704, the three-sided delta or triangular shaped end caps 1928 and 1930, the three-sided delta or triangular shaped end caps 2230 and 2232, and the three-sided delta or triangular shaped end caps 2424 may all be implemented as, for example, the connector system 200, the first connector system 1102, or the connector system 1400 having the NCD 204, NCD 1300, or NCD 1504, respectively.

[0184] It is also appreciated that in the previous examples, the corresponding connector system was shown to include the corresponding NCD within the corresponding connector system; however, this was only for illustration and it is appreciated that the NCD may also be located external to the corresponding connector system, where the NCD is external but is still in signal communication with the end connector board of the connector system.

[0185] For example, in FIG. 36, a system block diagram is shown for an example of an implementation of a NLS 3600 where the NCD 3602 is located external to the first connector system 3604 in accordance with the present disclosure. In this example, the NLS 3600 includes the lighting assembly 104 with a body 110, the NCD 3602, the first connector system 3604, a second connector system 3606, the remote power source 114, and the remote entity 116. In this example, the NCD 3602 is located external to the first connector system 3604 but is in signal communication (via signal path 3608) with the end connector board (not shown) within the first connector system 3604. The NCD 3602 may also, or instead of, be optionally in signal communication (via optional signal path 3610) with an end connector board (not shown) within the second connector system 3606. As an example, the NCD 3602 may be located along theAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026body 110 of the lighting assembly 104 or in proximity to the lighting assembly 104 such that the NCD 3602 may be connected to the first connector system 3604.

[0186] In this example, (and in the example shown in FIG. 2) the one or more remote devices 206 may be any type of wireless devices that are capable of communicating with NCD 3602 such as, for example, cellular telephones, satellite enabled devices, wirelessly connected computers (e.g., laptop computers, remote desktop and / or server computers with a wireless communication device), computer tablets, wireless communication devices, personal digital assistants (PDAs), Internet-of-Things (loT) devices, remote network devices, light networked devices, or other similar type of devices.

[0187] In addition, the NCD 3602 may also include, or be in signal communication with, one or more sensors (not shown) that are configured to detect environmental conditions, anomalies, motion, objects, or other information that are in the environment in which the lighting assembly 104 is located, e.g., the volume and area of an environment within a room, hallway, passage, or other physical location in which the lighting assembly 104 is located.

[0188] Based on the disclosure described in relation to FIGS. 1 through 36, the network enabled LED lamps (i.e., lighting assembly 104) and connector systems (i.e., connector systems 204 and 3604) disclosed herein provide safe and reliable means for securing linear LED lamps to a lighting fixture and providing networked power and data connectivity directly to the lamp. The disclosed snap-fit connector systems (i.e., connector sleeve 702, snap-fit connector 900, and connector 1006 discussed in relation to FIGS. 7 through 10B) and corresponding network compatible lamp end cap assemblies i.e., connector systems 204 and 3604) allow implementing PoE or other network compatible LED tube lamps into existing facility lighting fixtures, without the need to replace existing fluorescent lighting fixtures or to install new integrated LED fixtures. This eliminates the added cost of disposing of the existing fixtures and altering the current fixture design and layout, greatly reduces labor and time of install, and avoids scheduling conflicts and disruptions of the work environment of the facility. Network cables cost very little compared to heavy duty copper wire and conduit used for traditional lighting, and integrated power and data networking technology has the potential to greatly enhance the power efficiency gains of LED tube lighting compared to conventional fluorescent tube lighting systems. The ceiling grid mounted network compatible LED lamps disclosed herein provide additional options for quickly and inexpensively installing smart LED lighting systems in numerous residential and commercial applications. These novel LED lamp and connector configurations allow for immediate adoption and more rapid penetration ofAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026integrated power and data technology in the lighting industry. Users may conveniently and inexpensively update a lighting system with simple lamp replacement as lamp performance and features improve with further technology advances. The inventions disclosed herein thus enable the next generation of digitally controlled and networked smart LED lighting systems to be implemented in the conventional tube lamp format, eliminating the need to replace the massive amount of infrastructure already in place to support this dominant and highly advantageous lighting format.

[0189] As an example of an implementation of a lighting assembly in a building, referring to the drawings, FIG. 37 is a perspective view of a LED light illuminating assembly 3700 comprising an overhead LED lighting assembly providing overhead ceiling lighting with a two by four (2x4) LED drop ceiling fixture 3702 with a multiple sided modular LED lighting bars 3704, which are also referred to a multi-sided LED light bars. The lighting bars can include three-sided delta triangular shaped non-curvilinear LED luminaries 3706 which can be mounted to a ceiling 3708, such as by power connector pins 3710 extending from three-sided delta triangular shaped end caps 3712 which can securely engage light sockets 3714.

[0190] FIG. 38 is an enlarged view of portions of the multi-sided LED lighting bar comprising a LED drop ceiling fixture with three-sided delta non-curvilinear LED luminaries of FIG. 37. Upright metal side members 3716 can provide a bracket which can integrally extend between and connect the light sockets to overhead metal concave light reflectors 3718. The light reflectors can be positioned above the three-sided delta non-curvilinear LED luminaries to reflect light downwardly towards a floor. The three-sided delta non-curvilinear LED luminaries, sockets and reflectors can be positioned above light transmissive translucent ceiling panels 3720 (FIG. 37) providing light transmissive ceiling tiles arranged in a grid or pattern. The ceiling tiles can comprise an elongated light diffuser 3722 providing a light transmissive lens for diffusing and / or focusing light emitted from the LED emitted on towards the floor. The ceiling panels can be connected by a ceiling grid 3724 of longitudinal and lateral rows of ceiling panel-connectors 3726.

[0191] FIG. 39 is a cross-section view of the LED drop ceiling fixture with three-sided delta LED non-curvilinear luminaries and illustrating elongated LED emitter PCB panels 3728, which are also referred to as modular LED emitter boards. The LED PCB panels can be mounted or otherwise secured upon and / or positioned radially outwardly of the sides of an elongated three-sided, delta or triangular tubular metal heat sink 3730 (FIG. 37) to form a three-sided delta or triangular array or set of emitter boards. The intersecting sides of the three-sidedAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026heat sink can provide comers and apexes of the heat sink which sink can be raised, rounded, or chamfered, if desired. An internal non-switching PCB 3900 comprising a driver board can be positioned in the interior of the array to drive the emitter boards.

[0192] FIG. 40 is an enlarged perspective view of the three-sided delta LED luminaries. Each of the three-sided LED emitter PCB panels can contain a set, matrix or array of one or more rows of aligned, aliquot, uniformly spaced LED emitters 3732. The heat sink can comprise an aluminum extrusion and can dissipate heat generated by the LED emitters and driver.

[0193] FIG. 41 is a perspective view of an LED illuminating assembly 4100 comprising an elongated outdoor menu board 4102 which can provide an outdoor sign 4104 with two-sided modular LED lighting bars 4106 (LED light bars) comprising two-sided or delta non-curvilinear LED luminaries 4108 such as to drive through menu board applications. FIG. 41 also illustrates the front menu board door 4110 partially open. The front menu board can comprise a rectangular frame 4112 to peripherally surround and secure light transmissive panel(s) 4114 which can provide a door plea comprising an illuminated menu window 4116. The menu window can provide illuminated signage which can comprise an elongated light diffuser 4118 that can provide a light transmissive lens for diffusing and / or focusing light emitted from the LED outwardly. The front menu board door can be pivotally hinged or removably attached to the top 4120 or one of the sides 4122 of the outdoor menu board housing 4124. The back of the housing can also have a light transmissive panel(s), if it is desired to illuminate both the front and back of the outdoor menu board. The two-sided delta non-curvilinear LED luminaries can be connected, such as by power connector pins, to light socket assemblies 4126. The two-sided delta non-curvilinear LED luminaries can be positioned vertically, longitudinally, laterally, transversely, or horizontally in the interior of the outdoor menu board housing. A menu board vertical upright support post 4128, which can have a rectangular, square, or rounded cross section, can be mounted on a base plate and connected to the top of the menu board housing along the vertical centerline of the housing, to support and elevate the outdoor menu board housing, door and illuminated menu window. In this example, the upright support post 4128 may include a stand 4130. FIG. 42 is an enlarged view of portions of the outdoor illuminated menu board.

[0194] FIG. 43 is a perspective view of LED illuminating assembly 4300 comprising an elongated indoor menu board 4302 providing a wall mounted indoor sign 4304 with two- or three-sided modular LED lighting bars 4306 (LED light bars) comprising two- or three-sidedAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026delta non-curvilinear LED luminaries 4308 for use such as in, but not limited to a restaurant 4310 with a counter 4312, walls 4314, 4316, 4318, and 4320, exit and / or entrance door 4322 and the counter 4312 and illustrating one of the menu panel doors 4324 in a partially open position.

[0195] FIG. 44 is an enlarged view of portions of the indoor menu board. The back 4400 of the menu board can be securely mounted on a wall. The front of the menu board can comprise one or more menu panel doors such as a set or array of horizontally aligned menu panel doors. Each menu panel door can comprise a rectangular frame 4326 to peripherally surround and secure a light transmissive panel 4402 which can provide a door apex comprising an illuminated menu window 4404. The menu window can provide illuminated signage which can comprise an elongated light diffuser 4410 that can provide a light transmissive lens for diffusing and / or focusing light emitted from the LED outward into the room or interior of the restaurant. Each menu board panel door can be pivotally hinged or removably attached to the top 4406 or one of the sides 4408 of the menu board housing 4328. The two- or three-sided delta non-curvilinear LED luminaries can be connected, such as by power connector pins, to light socket assemblies 4412. The two-sided delta non-curvilinear LED luminaries can be positioned vertically, longitudinally, laterally, transversely or horizontally in the interior of the outdoor menu board housing.

[0196] In these examples, the network enabled LED lamps and connector systems disclosed herein provide safe and reliable means for securing linear LED lamps to a lighting fixture and providing networked power and data connectivity directly to the lamp. The disclosed snap-fit connector systems and corresponding network compatible lamp end cap assemblies allow implementing PoE or other network compatible LED tube lamps into existing facility lighting fixtures, without the need to replace existing fluorescent lighting fixtures or to install new integrated LED fixtures. This eliminates the added cost of disposing of the existing fixtures and altering the current fixture design and layout, greatly reduces labor and time of install, and avoids scheduling conflicts and disruptions of the work environment of the facility. Network cables cost very little compared to heavy duty copper wire and conduit used for traditional lighting, and integrated power and data networking technology has the potential to greatly enhance the power efficiency gains of LED tube lighting compared to conventional fluorescent tube lighting systems. The ceiling grid mounted network compatible LED lamps disclosed herein provide additional options for quickly and inexpensively installing smart LED lighting systems in numerous residential and commercial applications. These novel LED lamp andAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026connector configurations allow for immediate adoption and more rapid penetration of integrated power and data technology in the lighting industry. Users may conveniently and inexpensively update a lighting system with simple lamp replacement as lamp performance and features improve with further technology advances. The inventions disclosed herein thus enable the next generation of digitally controlled and networked smart LED lighting systems to be implemented in the conventional tube lamp format, eliminating the need to replace the massive amount of infrastructure already in place to support this dominant and highly advantageous lighting format.

[0197] Many automated lighting applications that can be implemented at lower cost and more effectively utilizing the principals of the lighting platform disclosed herein. Other applications of the disclosed subject matter will now be explained with reference to the functional design schematic provided as FIG. 45.

[0198] In FIG. 45, an example of an implementation of NLS 4500 is shown that is related to NLS 102 shown previously in FIG. 1, where the lighting assembly 104 is represented as a replaceable linear lamp 4501, the first connector system 106 is represented as connector 4520, network entity 116 may be implemented as including a central workstation 4530, and the remote power source 114 may include the power supply 4526. The connector 4522 may be a second connector that may be, as described earlier, implemented optionally as a second connector system 108 (FIG. 1). As such, the NLS 4500 may include a central workstation 4530 that can communicate with linear LED lamp 4501 via a network that can support wired, and optionally, wireless features.

[0199] Both power and lighting control (e.g. exchange of Ethernet control packets) may be provided via Ethernet cabling to the internal control node 4502 of the lamp to control operation of the lamp according to commands from a computer or other data processing device. Power from a power supply 4526 powers an Ethernet switch 4532, which delivers power and control data to the linear LED lamps of a lighting system, such as the replaceable linear lamp 4501, over an Ethernet network cable. The network connection may also allow the lamp control node to download patches, drivers, and program code. Although FIG. 45 shows the central workstation 4530 and external sensors 4528 connected to the replaceable linear lamp 4501 over a network cable connected to Ethernet switch 4532, the replaceable linear lamp 4501 may also be addressed wirelessly.

[0200] The switch 4532 may also be connected to external sensors 4528 deployed at various locations to sense conditions such as room occupancy, light levels, motion and other conditionsAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026that serve as inputs to pre-determined automated lighting control strategies. The switch 4532 may supply power to the external sensors 4528 in addition to receiving Ethernet packets containing data associated with the sensed conditions. One or more computer workstations, such as central workstation 4530, may be configured to run one or more lighting automation management software applications which allow an administrator to design, modify and implement automated lighting control strategies, as well as diagnose, monitor and report on various operational aspects of the lighting system under control. The central workstation 4530 may include one or more processors and one or more memories coupled to the one or more processors, as well as one or more programs that cause one or more processors to perform one or more of the lighting automation and / or management operations. These computer programs, which can also be referred to as programs, software, software applications, applications, components, or code, include machine instructions for a programmable processor, and can be implemented in a high-level procedural and / or object-oriented programming language, and / or in assembly / machine language. The computer programs may be stored in a machine and / or computer readable medium that may be stored one or more memories (see network entity 304 that includes one or more server and / or computers 322 and one or more memory device 330). Computer implemented methods consistent with one or more implementations of the current subject matter can be implemented by one or more data processors residing in a single computing system or multiple computing systems. Such multiple computing systems can be connected and can exchange data and / or commands or other instructions or the like via one or more connections, including but not limited to a connection over a network (e.g. the Internet, a wireless wide area network, a local area network, a wide area network, a wired network, or the like), via a direct connection between one or more of the multiple computing systems, etc. The switch 4532 may be operable to route control commands and other information and data between the central workstation 4530, the external sensors 4528, and the addressable networked lamps 4501 of the system. Each lamp and external sensor has a network location that may be known to the switch 4532, and is equipped with at least one standardized Ethernet communication interface so that it can be directly addressed by the Ethernet switch and can communicate data to the switch. The replaceable linear lamp 4501 can be mechanically installed into a lighting fixture 4524, which may be a conventional fluorescent lighting fixture or other existing or new LED lighting fixture, by means of one of the various snap-fit connector embodiments previously disclosed, at least one of which provides an associated Ethernet compliant modular connector for connecting replaceable linear lamp 4501 to the lightingAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026network. Alternatively, as disclosed in certain embodiments above, the replaceable linear lamp 4501 can be directly secured to a ceiling grid and an Ethernet cable plugged directly into an externally facing jack of the lamp end cap.

[0201] The PoE switch 4532 can provide power to the linear LED lamps and control circuitry, such that both power and transmission and receiving of the serial command strings can be accomplished via Ethernet. The replaceable linear lamp 4501 includes an internal control node 4502 and is an automation component in that it can be controlled by instructions executing within the lamp, or alternatively by instructions executing on the central workstation 4530. The lamp can be powered on or off, and its brightness, color and other operational characteristics can be controlled in an automated fashion. The control node 4502 may include processor 4504, which is configured to execute software for executing control commands and providing numerous other automated functions of the lamp. One or more aspects or features of the control node 4502 described herein can be realized in digital electronic circuitry, integrated circuitry, specially designed application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) computer hardware, firmware, software, and / or combinations thereof. These various aspects or features can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device. The electronics shown are intended to be representative of functional components and are not intended to exclude additional components.

[0202] The replaceable linear lamp 4501 may also include one or more internal sensors 1218 mounted to the lamp. The internal sensors 4518 and external sensors 4528 are additional automation components that can also be controlled by instructions executing within the lamp or by instructions executing on the central workstation 4530. The sensors can provide environmental feedback for use as an input to a program or set of instructions. For example, a sensor may supply an electrical signal indicating a sensed aspect of the external environment or of the lamp itself, for example a light level, a motion, a noise, or a temperature. The sensors themselves may also include aspects that may be controlled, including power on / off or sensitivity, for example.

[0203] At least one LED array is mounted to the lamp body, typically in the form of one or more LED emitter boards, to generate light when powered by a drive current. The schematicAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026of FIG. 45 shows the replaceable linear lamp 4501 having three parallel LED arrays 4512, 4514 and 4516. The control node 4502 may include a driver 4508 for precisely controlling the magnitude of DC current transmitted to each LED array, which is proportional to the intensity of light emitted by the LEDs. The driver 4508 may further include three sub-circuits, which are each connected to one of the LED arrays for controlling power to that individual array independent of the other arrays. This circuit arrangement provides three independently controllable LED channels A, B and C within a single lamp to support a wide range of desired lighting effects and operational flexibility.

[0204] In this example, the jack 4510 may be an RJ-45 socket. Other types of standard or not standard data connectors may similarly be used to source a combined data and power connection. A set of isolation components connected to the pins of the jack are used to isolate data signals from the power supplied by the pins. The control node 4502 may also communicates with circuitry in the switch 4532 via a network cable to negotiate a necessary power level for consumption by the lamp. The control node 4502 further includes power control module 4506, which may utilize one or more DC-to-DC converters to adjust the power supplied to the driver sub-circuits associated with the channels A, B and C of driver 4508. The isolated data signals are inputs to processor 4504, which may be a microcontroller, a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and may include a network communications controller, and memory device. The processor 4504 may transmit and receive communications from a remote device via the network cable and also uses power supplied by the cable. The processor 4504 may store and execute instruction for receiving environmental input from the external or internal sensors, instructions for adjusting operational aspects of the lamp, or instructions for adjusting aspects of the internal sensors 4518. The input from external sensors 4528 may be transmitted via the network cable or wirelessly per a standardized wireless communications protocol.

[0205] Implementations of the current subject matter can allow a building owner or administrator to monitor and control lighting power within the building as needed for occupants and policies, in addition to eliminating the use of such power when not necessary. This capability can, among other potential advantages, enable better optimization of lighting power utilization and thereby extend the life of LED lamps while reducing energy consumption. The system can be used to automate such functions as turning on lights automatically. When a person enters a room, for example, an external sensor 4528 may sense the movement send a signal to central workstation 4530, via the switch 4532, which may in turn broadcast EthernetAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026packets containing commands to activate one or more LED arrays of replaceable linear lamp 4501 and / or of other lamps of the system. The switch 4532 handles the routing of these control commands to the appropriate lamps. Alternatively, an internal sensor 4518 may communicate directly with the control node 4502 of the lamp, which then triggers the commands to turn on the LED arrays. The hardwired instructions and / or software code required to perform these automated functions may be stored and executed within the computer 4530 or within the control node 4502 or in some combination thereof. In one approach, the processor 4504 may be programmed to enable the replaceable linear lamp 4501 to adjust its own operational characteristics in response to the sensed environmental inputs.

[0206] Manually operated light switches may also be networked to the system, upon activation of which the processor 4504 may execute instructions that signal the power control module 4506 to control a channel of driver 4508 to turn one of the LED arrays on or off. Alternatively, the administrator may input parameters via a user interface of the central workstation 4530 causing commands to be transmitted to processor 4504 that specify adjusting the power to one or more of the LED arrays in order to adjust the intensity or tune the color of light output by the replaceable linear lamp 4501. The automation control logic can combine inputs from separate sensors, such as occupancy and light level sensors, to implement user defined or policy driven lighting control strategies.NETWORK CONNECTOR SYSTEM AND NETWORK LUMINAIRE

[0207] Turning back to FIG. 1, the modular luminaire 100 may be part of the NLS 102 and includes the lighting assembly 104 with the first connector system 106 and an optional second connector system 108. In this example, the first connector system 106 (e.g., the connector system 200, sleeve portion 736, first connector system 1002, first connector 1102, connector system 1400, first connector system 1704, first connector system 3604) may comprise: a connector housing (i.e., sleeve portion 736, configured to be removably attached to the lighting assembly 104; an end connector board 202 within the connector housing, where the end connector board 202 is in signal communication with the lighting assembly 104; and a NCD 204 in signal communication with the end connector board, where the NCD 204 is configured to communicate with the network entity 116. In this example, the NCD 204 may optionally be part of the first connector system 106 or external to but in signal communication with the end connector board 202 of the first connector system 106. As discussed previously, the end connector board 202 may be implemented as the end connector 1502 which may be, forAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026example, end cap PCB boards of the end cap PCB connector 1924 and / or 1926.

[0208] Specifically, FIG. 46 is a block diagram of an example of another implementation of the connector system 4600 in accordance with the present disclosure. The connector system 4600 may include the end connector board 4602 and a NCD 4604, where the end connector board 4602 is in signal communication with the lighting assembly 104, remote power source 114, and network entity 116. The NCD 4604 may include one or more communication devices 4606, one or more processors 4608, one or more memories 4610, one or more network interfaces 4612, and / or one or more sensors 4614. In this example, NCD 4604 may be in signal communication with the network entity 116 and one or more remote device 4615. The one or more remote devices 4615 may include loT devices, cellular telephones, satellite telephones, mobile computers, computer tables, PDAs, wireless networked devices, or other similar devices. In this example the one or more communication devices 4606 may include a Wi-Fi transceiver 4616, Bluetooth transceiver 4618, Li -Fi transceiver 4620, cellular transceiver 4622, satellite transceiver 4624, a radio-frequency identification (RFID) device 4626 (which may be transceiver, transmitter, or receiver) and / or a universal integrated circuit card (UICC) 4628 such as, for example, a smart card that may include a subscriber identity module (SIM) card. As previously discussed, the NCD 4606 may be a part of the connector system 4600 or it may be an external device, circuit, or component that may be in signal communication with the end connector board 4602 utilizing know wired and wireless techniques.

[0209] In this example, the SIM card allows the NCD 4606 to be a platform-agnostic communication device that may be configured to communicate with the network entity 116 and / or the one or more remote devices 4615 utilizing the UICC 4628, where the UICC is configured to store multiple network profiles that include a network profile for the network entity 116, one or more remote devices 4615, or both, that allows the NCD 4606 to communicate with the network entity 116, one or more remote devices 4615, or both. In this example, the NCD 4606 may be configured to download multiple network profiles for the UICC 4628.

[0210] In this example, the UICC may be a smart card that includes a subscriber identity module (SIM) card, where the communication device 4600 may be configured to communicate with one or more network devices (e.g., the network entity 116, one or more remote devices 4615, or both) utilizing the SIM card. It is appreciated that by utilizing a UICC 4628 (such as, for example, a SIM card), at least one of the communication devices of the one or more communication devices 4606 may be a platform-agnostic communication device that isAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026configured to communicate with the one or more network devices utilizing the UICC 4628 where the UICC 4628 may be configured to store multiple network profiles that include a network profile for the one or more network devices that allows a communication device of the one or more communication device 4606 to communicate with the one or more network devices, where the one or more network devices includes the network entity 116, the one or more remote devices 4615, or both. In this example, the UICC may be configured to download the multiple network profiles that include network protocols and security frameworks for the network entity 116, the one or more remote devices 4615, or both.

[0211] In this example, a SIM card generally acts a secure, portable, and unique ID card that when added to the NCD 4604, allows the one or more communication devices 4606 to connect to the secure devices and / or networks. When inserted into the NCD 4604, the SIM card may include a microchip that transmits identification (e.g., an international mobile subscriber identity (IMSI)) and authentication key to a network for access to that network. The SIM cards may be physical chips or embedded digital versions of SIM known as eSIMs that may be built into the NCD 4604.

[0212] As another example, the NCD 4606 may include a RFID device 4626 configured to communicate with one or more RFID cards. RFID cards are generally contactless smart cards that use electromagnetic fields and radio wave transmission to wireless transmit data to the RFID device 4626. This transmitted data may be utilized to allow access control or identification. The RFID device 4626 may be configured to operation in a low frequency (LF) (e.g., 125-150 kHz) operation for short-range (often used for access control - e.g., key fobs); high frequency (HF) (13.56 MHz) operation for smart cards, contactless credit cards, and security badges; ultra-high frequency (UHF) (860-960 MHz) operation for logistics and tracking over longer distances, sometimes up to several meters.

[0213] Turning to FIG. 47, a system block diagram of an example of another implementation of the connector system 4700 is shown in a network configuration in accordance with the present disclosure. In this example, the connector system 4700 includes an end connector board 4702 and an NCD 4704. As describe previously, the end connector board 4702 is in signal communication a lighting assembly 4706, a network entity 4708, and a remote power source (not shown). In this example, the network entity 4708 may optionally be in signal communication with one or more communication networks that include, for example, a general network 4710 (such as, for example, an internal network, an external network such as, for example, the Internet, or both), a cellular network 4712, a satellite network 4714, or other typeAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026of communications network. As a further example, the network entity 4708 may be in signal communication with: the general network 4710 via a wired or wireless signal path 4716; the cellular network 4712 via a signal path 4718 from the general network 4710 to the cellular network 4712 or, alternatively, via an antenna 4720 and wireless signal path 4722 to a base station 4724 of the cellular network 4712; and / or the satellite network 4714 via a signal path 4726 from the general network 4710 to the satellite network 4714 or, alternatively, via an antenna 4728 and wireless signal path 4730 to a satellite 4732 (generally of a satellite constellation) of the satellite network 4714.

[0214] The end connector board 4702 is in signal communication with the network entity 4708 and the NCD 4704 via signal paths 4734 and 4736, respectively; and the NCD 4704 may be in signal communication with network entity 4708 and one of more remote devices 4738 via signal paths 4740 and 4742, respectively. In this example, the one or more remote device 4738 may include, for example, an RFID device 4744, a first user equipment (UE) 4746, and second UE 4748.

[0215] In this example, a the terms "user equipment" (UE) and "base station" are not specific to or otherwise limited to any particular Radio Access Technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset tracking device, Internet of Things (loT) device, etc.) used to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a Radio Access Network (RAN). As used herein, the term "UE" may be referred to interchangeably as an "access terminal" or "AT," a "client device," a "wireless device," a "subscriber device," a "subscriber terminal," a "subscriber station," a "user terminal" or UT, a "mobile terminal," a "mobile station," a "mobile device," or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and / or the Internet are also possible for the UEs, such as over wired access networks, WiFi® networks (e.g., based on IEEE (Institute of Electrical and Electronics Engineers) 802.11, etc.) and so on. Two or more UEs may communicate directly in addition to or instead of passing information to each other through a network.

[0216] A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed. Examples of a base station include an Access Point (AP), a Network Node, a NodeB, an evolved NodeB (eNB), or a general Node BAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026(gNodeB, gNB). In addition, in some systems a base station may provide purely edge node signaling functions while in other systems it may provide additional control and / or network management functions.

[0217] UEs may be embodied by any of a number of types of devices including but not limited to printed circuit (PC) cards, compact flash devices, external or internal modems, wireless or wireline phones, smartphones, tablets, consumer asset tracking devices, asset tags, and so on. A communication link through which UEs can send signals to a RAN is called an uplink channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the RAN can send signals to UEs is called a downlink or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein the term traffic channel (TCH) can refer to either an uplink / reverse or downlink / forward traffic channel.

[0218] As used herein, the term "cell" or "sector" may correspond to one of a plurality of cells of a base station, or to the base station itself, depending on the context. The term "cell" may refer to a logical communication entity used for communication with a base station (for example, over a carrier), and may be associated with an identifier for distinguishing neighboring cells (for example, a physical cell identifier (PCID), a virtual cell identifier (VCID)) operating via the same or a different carrier. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (for example, machine-type communication (MTC), narrowband Internet-of-Things (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of devices. In some examples, the term "cell" may refer to a portion of a geographic coverage area (for example, a sector) over which the logical entity operates.

[0219] Turning back to FIG. 47, the NCD 4704 may utilize the RFID device 4626 to communicate directly with RFID device 4744 via signal path 4750. The NCD 4704 may then utilize different transceivers to communicate with UE 4746 and UE 4748 based on the type of device for each UE. Specifically, if either UE 4746 or UE 4748 is a Wi-Fi device, the NCD 4704 may utilize the Wi-Fi transceiver 4616 to communicate with the Wi-Fi UE, while if either UE 4746 or UE 4748 is a Bluetooth device, the NCD 4704 may utilize the Bluetooth transceiver 4618 to communicate with the Bluetooth UE. Additionally, if either UE 4746 or UE 4748 is a Li-Fi device, the NCD 4704 may utilize the Li-Fi transceiver 4620 to communicate with the Li-Fi UE.

[0220] It is appreciated that other types of transceivers can also be utilized by the NCD 4704Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026even if not shown for the purposes of ease of illustration. Specifically, the NCD 4704 may also include a WLAN transceiver (i.e., covered by IEEE 802.11), Zigbee transceiver (i.e., covered by IEEE 802.15.4 low-power, low-data-rate wireless mesh networking standard), low power, wide area networking (LoRaWan) transceiver, or other type of communication component and / or device.

[0221] As a further example, if the NCD 4704 includes a cellular transceiver 4622, the NCD 4704 may be configured to communicate with the UE 4746, UE 4748, or both if the UE are cellular devices. Moreover, if the NCD 4704 includes a satellite transceiver 4624, the NCD 4704 may be configured to communicate with the UE 4746, UE 4748, or both if the UE are satellite enabled devices. For example, if either UE 4746 or UE 4748 is a cellular device, the NCD 4704 may utilize the cellular transceiver 4622 to communicate with the cellular UE. In this example, the cellular transceiver 4622 may be, for example, a 3G, 4G, 5G, 6G, code division multiple access (CDMA), time division multiple access (TDMA), global system for mobile communications (GSM) type of transceiver.

[0222] In addition, the cellular transceiver 4622 may include a cellular repeater 4628 that is configured to receive the cellular signals from the base station 4724 and amplify and transmit them to and from the cellular UE(s). In this example, the cellular signals would be received by the network entity 4708 via the cellular antenna 4720 and sent to the cellular repeater 4628. As an alternative, the cellular transceiver 4622 may include instead (or in addition to) a local cellular femtocell 4630 that is a device that acts as a base station from the cellular network. In this example, the communication would be to and from the cellular UE to the cellular network 4712 via the cellular femtocell 4630 to the network entity 4708 through the general network 4710 to the cellular network 4712.

[0223] In a similar fashion, the satellite transceiver 4624 may include a satellite repeater 4632 that is configured to receive the satellite signals from the satellite 4732 and amplify and transmit them to and from the cellular UE(s). In this example, the satellite signals would be received by the network entity 4708 via the satellite antenna 4728 and sent to the satellite repeater 4632. As an alternative, the satellite transceiver 4624 may include instead (or in addition to) a local satellite femtocell 4634 that is a device that acts as a satellite transceiver from the satellite network. In this example, the communication would be to and from the satellite UE to the satellite network 4714 via the satellite femtocell 4634 to the network entity 4708 through the general network 4710 to the satellite network 4714.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0224] In these examples, the UEs may also be loT devices that may be embedded with sensors, software, and connectivity that enable them to collect, exchange, and act on data without human intervention thus allowing everyday objects to the Internet and allowing for intelligent, real-time monitoring and automation of the environment about the NLS. In this example, sensor in the loT sensors within the UEs may optionally augment or replace the one or more sensors 4614 of the NCD 4604. In this example, the SIM card at the NCD 4604 may provide for secure exchange of data between these types of loT UEs.

[0225] In a “smart building” application, these types of loT UEs allow the network entity 116 (or the network entity 116 in combination with the NCD 4604) to use the loT sensors of the UEs, artificial intelligence, and automated system to monitor, analyze, and control operations such as, for example, lighting, heating, ventilation, and air conditioning (HVAC), and security in real-time. By utilizing the techniques and system disclosed herein in relation to the NLS, the NLS allows for connecting these systems, such that smart buildings are able optimize energy consumption, improve occupant comfort, and enable predictive maintenance, creating a responsive, efficient, and sustainable environment. Applications of these techniques are useful for, as an example, commercial where automated lighting and climate control may be based on meeting room usage; hospitals / healthcare facilities where environmental monitoring and tracking of critical equipment is needed; educational facilities where optimizing energy use in large, sporadically occupied spaces are needed; and stadiums where managing crowd flow, lighting, and HVAC during high-traffic event is also needed.

[0226] As such, the techniques describe herein allow for a modular linear LED lamp featuring a SIM card NCD that enables secure, programmable loT network integration. In this example, the SIM card allows for the removable, replaceable, and upgradable SIM card module to interact directly with the power and lighting control systems of the modular linear LED lamp. The also allow for a lighting system that enables communication between connected loT sensors, HVAC controllers, security devices, and building automation systems. Additionally, the modular linear lighting solution disclosed may eliminate forced obsolescence, allowing users to replace only the loT module instead of discarding the entire linear lamp when networks evolve. The techniques also allow for a secure loT linear lighting system that can be integrated into military, healthcare, and educational infrastructure for real-time monitoring and automation. Moreover, a SIM-enabled linear lamp as discussed, allows secure wireless communication using Wi-Fi, Bluetooth Mesh, and Li-Fi to improve data security in high-risk environments. Further, a linear lamp system has been disclosed that allows manufacturers toAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026place SIM card modules in different locations within the linear lamp embodiment, enabling various aesthetic and functional designs. These types of smart linear lamps are capable of detecting environmental changes, transmitting data through secure mesh networks, and triggering automated responses in real time. Moreover, this disclosure discusses a lighting system that is designed for future-proofing smart buildings, enabling secure upgrades without requiring fixture replacements when new tenants or enterprises upgrade security policies, where this lighting infrastructure is capable of functioning agnostically within smart building automation, ensuring it can work independently of existing network protocols and security frameworks of new tenants or owners. By integrating a removable, programmable SIM cardbased module, this approach sets a new industry standard for scalable and secure lighting solutions. The NLS described supports secure edge cloud processing, ensuring data security and real-time analytics directly from the linear lamp fixture. The NLS also incorporates cellular technology, including 5G, 6G, and future wireless generations, allowing for independent data communication, aggregation, and transmission. Further, the NLS enables localized device connectivity, acting as a secured private cellular node to provide dedicated, tenant-specific network coverage and is capable of serving as an independent cellular hotspot, extending network coverage in dense urban environments and remote locations. In these example, the NLS described is a lamp system that tethers environmental sensors, SIM modules, and external network interfaces via wired or wireless connections. The NLS also allows private cellular and satellite-based networking for tenant-secured smart infrastructure; and supports direct-to-satellite connectivity using future satellite-based 6G / 7G and beyond-network communications.

[0227] Based on this disclosure, techniques for a lighting system that enables communication between connected loT sensors, HVAC controllers, security devices, and building automation systems have been discussed. Further discussed are techniques for a modular linear lighting solution that eliminates forced obsolescence, allowing users to replace only the loT module instead of discarding the entire linear lamp when networks evolve.

[0228] It is appreciated that in general, the present disclosure relates to intelligent lighting systems, specifically a modular linear LED lamp that integrates a SIM card-based interface for network integration, secure data transmission, loT automation, and advanced wireless communication. Techniques discussed in the present disclosure may enable seamless operation within smart building automation, loT, and global connectivity frameworks, with future expansion to satellite and beyond-network communication capabilities.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0229] Furthermore, the lack of decentralized, linear lamp-based cellular connectivity has generally prevented lighting systems from contributing to private networking, data security, environmental monitoring, and automation-based cloud integration. There resulted in a need for a scalable, modular, and upgradeable linear lighting solution that integrates cellular and loT communication, ensuring secure, dedicated, and independent operation within smart building infrastructures, industrial automation, and remote applications.

[0230] As discussed previously, this disclosure overcomes these challenges by providing a secure, modular linear lighting platform that enables programmable network access, cellular data transfer, edge computing, satellite communication, and decentralized connectivity while maintaining the functionality of a linear lamp.

[0231] In general, the NLS previously discussed in this disclosure may incorporate: modular SIM-based network interface that may be a removable, programmable SIM card-based communication module that enables dynamic network compatibility for loT, automation, cellular, and satellite communication; multi -protocol communication support that integrates Wi-Fi, Bluetooth Mesh, Li-Fi, and cellular networks (5G, 6G, and beyond), allowing each linear lamp to serve as a secure data node, an loT gateway, or a cellular hotspot while maintaining lighting functions; secure, encrypted network access that provides network segmentation, tenant-based security policies, and encrypted data transfer, preventing unauthorized access and cyber threats; flexible SIM card and sensor placement that enables multiple integration options, including internal slide slots, designated compartments, and externally tethered SIM enclosures or sensor hubs for adaptive, manufacturer-specific designs; edge cloud processing and artificial intelligence (Al) optimization that supports real-time data analysis, automated lighting adjustments, and Al-driven network load balancing within distributed smart infrastructure; decentralized private networking by allows each linear lamp to function as a private cellular or satellite communication node, contributing to localized, tenant-specific secure communications without requiring new infrastructure deployment; and potential future-proof upgradeability by ensuring network adaptability without replacing the physical fixture, allowing new communication protocols, security features, and sensor technologies to be implemented via modular SIM or firmware updates.

[0232] The techniques and systems previously described support multiple communication technologies, including Wi-Fi, Bluetooth Mesh, Li-Fi, and cellular networks (5G, 6G, and beyond), allowing for decentralized, secure, and scalable smart infrastructure. The techniques described allow each linear lamp can function independently as a cellular data node, an loTAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026sensor hub, an environmental monitoring unit, or a private network access point, with modular placement options for SIM card integration and sensor tethering.

[0233] These techniques also allow for future-proof linear lamp lighting systems that may be designed for global applications, with use cases spanning commercial, industrial, healthcare, military, education, emergency response, smart city infrastructure, and deep-space communication applications. These techniques may introduce a new industry standard for scalable, secure, and upgradeable lighting solutions by eliminating the limitations of fixed, embedded communication hardware.

[0234] Turning back to FIG. 46, if the NCD 4604 includes a Li-Fi transceiver 4620, the Li-Fi transceiver 4620 may be utilized to provide Li-Fi networking in an area covered by the connector system 4600. In FIG. 48, a system block diagram of an example of an implementation of a Li-Fi enabled NLS 4800 is shown in accordance with the present disclosure. The NLS 4800 is designed to provide removable, replaceable, and upgradeable functionality. In this example, the NLS 4800 may integrate high-speed Li-Fi communication, enabling ultra-fast, secure, and interference-free data transmission through light-based wireless connectivity. The diagram outlines the components and operational flow of a Li-Fi smart linear lamp 4802, which includes: an LED Light Source 4804 that is configured to function as both an illumination engine and a data-transmitting medium, emitting modulated light pulses to carry information to connected devices; an Li-Fi Transceiver 4806 that is configured to convert modulated light signals into wireless internet / data communication, allowing for seamless realtime connectivity with devices such as smartphones, laptops, and tablets; a power Input 4808 via PoE / AC / DC that may ensures versatile power compatibility, allowing the Li-Fi smart linear lamp 4802 to operate via low-voltage PoE or traditional AC / DC sources; loT Sensors 4810 that may be integrated within a delta-shaped housing (as discussed previously) of the Li-Fi smart linear lamp 4802, these loT sensors 4810 may capture environmental data 4812 such as temperature, humidity, motion, and air quality; and a loud Data Processing & Al Automation system 4814 that is configured to collected sensor data that may be transmitted to cloud-based Al-driven systems, enabling predictive analytics, automation, and smart building management.

[0235] FIG. 49 is a graphical plot 4900 of an example of an implementation of wireless communication and data transmission fields projected from the Li-Fi smart linear lamp 4802 in accordance with the present disclosure. This figure illustrates how various wireless technologies, including RF, Bluetooth, Li-Fi, Mesh Networking, and Cellular Signals, are emitted and propagated within a given space around the Li-Fi smart linear lamp 4802. TheAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026intersecting beams represent multi-directional signal transmission and reception, showcasing the ability of the Li-Fi smart linear lamp 4802 to establish and maintain connectivity with multiple external devices, networks, and communication infrastructures.

[0236] The overlapping networked structure shows the omnidirectional and multidirectional nature of the wireless signals, to allow for seamless coverage and data transfer efficiency. The Li-Fi-based transmission uses modulated light waves to communicate, while RF-based technologies such as Bluetooth, Mesh, and Cellular extend network reach beyond the immediate illumination area. This figure also demonstrates how the Li-Fi smart linear lamp 4802 functions as a dynamic hub for data capture, processing, and relay, further integrating with broader loT ecosystems.

[0237] The structured transmission pattern shows the capability of the Li-Fi smart linear lamp 4802 to dynamically adjust signal distribution, optimizing coverage based on real-time environmental conditions, device presence, and network load. This may ensure efficient and low-latency communication across a variety of smart infrastructure applications, including industrial automation, commercial security, smart building management, and military or emergency communication systems.

[0238] Additionally, this figure serves as a visual representation of the ability of NLS 4800 to integrate multiple antennas, allowing it to interface with terrestrial and satellite-based networks, ensuring long-range and high-bandwidth connectivity. The depiction further supports the removable, replaceable, and upgradable aspects of the SIM-based and sensor-driven system, allowing the lamp to evolve with advancing communication standards.

[0239] As previously discussed, the techniques and systems disclosed herein have described multi-plane intelligent linear lamp, designed to emit light at different angles while enabling wireless data transfer and advanced network communication in accordance with the present disclosure. In general, this multi-faceted lighting system enhances illumination flexibility, efficiency, and connectivity for smart building automation, industrial applications, and loT integration. The various intelligent lamps described herein may incorporate multiple independent lighting planes, allowing for customizable light distribution across different surfaces. This configuration enables task lighting, indirect illumination, directional beacons, wayfinding, emergency signaling, and adaptive architectural lighting, all within a single fixture.

[0240] The internal electronic system facilitates wireless data exchange, supporting Bluetooth, Li-Fi, Wi-Fi, and Mesh networks may act as a data transmission hub for seamlessAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026smart building device connectivity. The techniques described herein enable real-time sensor data collection, environmental monitoring, and automation signals to be transmitted to edge computing or cloud-based Al. The modular architecture of the various lamps previously described generally allow for removable, replaceable, and upgradeable LED light engines and embedded smart components, ensuring long-term adaptability. As previously describes these lamps may integrate SIM-based communication modules, environmental sensors, and AL driven control systems, further enhancing real-time automation and remote management.

[0241] Designed for intelligent energy regulation, the NLS previously describe may support both AC / DC and PoE inputs, optimizing power consumption while maintaining high performance. Its power management allows for real-time adjustments based on environmental conditions, occupancy detection, and automation needs. This multi-plane intelligent linear lamp represents a new type of smart lighting solutions, seamlessly combining customizable illumination, real-time automation, and advanced wireless connectivity into a scalable, upgradeable, and adaptable system for next-generation smart infrastructure.

[0242] FIG. 50 is a system diagram of an example of an implementation that illustrates a Li-Fi-enabled linear lamp designed to be installed inside conventional lighting fixtures that accept standard linear-type lamps. This implementation allows for the retrofitting of legacy lighting infrastructure, transforming traditional fixtures into high-speed Li-Fi communication hubs without requiring extensive modifications to existing electrical installations. By replacing conventional linear lamps with this Li-Fi-enabled solution, legacy fixtures may be seamlessly integrate into modem smart building networks, enabling wireless data transmission through modulated light signals.

[0243] The Li-Fi-enabled lamp functions both as an illumination source and a high-speed data transmission system, providing a secure, interference-free alternative to traditional radiofrequency -based wireless communication. When installed into existing fixtures, the lamp’s embedded Li-Fi transceiver modulates the LED light output at high speeds, enabling devices such as smartphones, laptops, and loT-enabled systems to connect to the internet and communicate wirelessly. This retrofit approach may ensure that legacy lighting systems can be upgraded without replacing entire fixture housings, reducing installation costs while providing next-generation connectivity.

[0244] The design of the Li-Fi-enabled lamp incorporates removable, replaceable, and upgradeable technology, allowing future enhancements such as increased data transmission speeds, improved energy efficiency, and additional loT sensor integration. This adaptabilityAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026may ensure long-term compatibility with evolving smart building technologies. The system also supports hybrid communication, enabling Li-Fi to operate alongside Bluetooth, Wi-Fi, and Mesh networking protocols, creating a comprehensive smart lighting and connectivity ecosystem.

[0245] This innovative approach may redefine the role of lighting in modem infrastructure by converting legacy fixtures into intelligent communication nodes capable of supporting realtime automation, secure data transfer, and Al-driven analytics. The seamless integration of Li-Fi-enabled lamps into conventional fixtures may demonstrate a transformative shift in smart lighting, offering a scalable, high-performance, and future-proof solution for smart buildings, industrial environments, and secure communication networks.

[0246] FIG. 51 is a system block diagram of an example of a smart lamp system 5100 with top-mounted sensor 5102 and bottom -mounted sensors 5104, demonstrating the modular and adaptable nature of sensor placement within the lamp’s embodiment. This figure showcases how sensors can be integrated at various positions on the lamp structure, allowing for customized deployment based on environmental and functional requirements.

[0247] The top-mounted sensor 5102 is configured to enable wireless loT communication, transmitting and receiving signals via Li-Fi, RF, Bluetooth, Wi-Fi, Mesh, or Cellular connectivity. This sensor 5102 can be utilized for motion detection, ambient light measurement, environmental monitoring, or network communication with other smart devices.

[0248] The bottom-mounted sensor 5104 demonstrates an alternative placement for sensors that may require proximity-based detection, thermal monitoring, or downward-facing illumination control. This configuration supports adaptive lighting, occupancy sensing, and real-time data acquisition based on user movement and environmental changes.

[0249] The direct mounting system 5106 signifies that these sensors (i.e., sensor 5102 and sensor 5104) can be removable, replaceable, and upgradable, ensuring scalability and adaptability for evolving loT applications. The sensors 5102 and 5104 can be clipped on, embedded, or surface-mounted at different positions within the housing or structural framework of the smart lamp system 5100, allowing for customized smart lighting implementations.

[0250] Additionally, this figure represents the wireless signal propagation paths, highlighting the bidirectional communication capabilities between the sensors, lamp control systems, and external networks. An integrated SIM card module may ensure seamless network connectivity, supporting real-time data processing, command execution, and cloud-based analytics.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0251] This versatile sensor placement approach enhances the lamp’s functionality, providing a potential future-proof solution for smart infrastructure applications such as commercial buildings, industrial facilities, military installations, and smart city deployments.

[0252] As such, based on this disclose, a modular, removable, and upgradeable smart linear lamp with Li-Fi technology, providing high-speed, light-based wireless data transmission and illumination is disclosed. Also disclosed is a Li-Fi-enabled linear lamp that is mechanically compatible with multiple industry-standard connection points, including IEC GJ 6.6 lamp holders, PoE RJ45 ports, and legacy fluorescent mechanical holders. This type of Li-Fi-enabled smart linear lamp may include a multi-power compatibility system, supporting PoE, AC / DC (2V-347V), and alternative wireless power reception technologies. Further as described earlier, the Li-Fi transceiver within the linear lamp may function both as a Li-Fi transmitter and receiver, enabling bi-directional optical communication. These examples allow for the implementation of a Li-Fi-powered linear lamp network, where multiple lamps may form a distributed mesh communication system for real-time, high-speed data transmission across large facilities. Moreover, this type of Li-Fi smart linear lamp may provide wireless connectivity for loT-enabled devices, transmitting environmental data via Li-Fi to cloud-based automation platforms.

[0253] Moreover, in these examples if the NCD of the NLS includes both a Wi-Fi transceiver and a Li-Fi transceiver, the lamp of the NLS may function as either a standalone Li-Fi access point or a supplementary wireless network node. In these examples, the NCD may be configured such that the Li-Fi transceiver components may be replaced independently of the lamp housing. As an example, the Li-Fi transceiver may be in signal communication with the NCD while not being physically part of the NCD. In this example, the Li-Fi transceiver may be a separate component, device, and / or circuit that is not physically part of the NCD or even the communication system (e.g., communication system 200) and my be located proximate to the communication system and / or modular luminaire 100 while being in signal communication with the NCD or, alternatively, modular luminaire 100 such that the Li-Fi transceiver communicates directly with the network entity 116.

[0254] In these examples, the Li-Fi transceiver may be a secondary communication device that allows for Li-Fi-enabled emergency communication and data system within a smart lamp form factor to ensure for uninterrupted wireless connectivity in a potential disaster and / or secure (i.e., government applications). Moreover, in these examples, a hybrid Li-Fi andAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026cellular-enabled lamp may be configured to transferring data through light-based and cellularbased networks so as to ensuring redundancy and high-speed communication.

[0255] FIG. 52 is system diagram of an example of an implementation of Li-Fi and Bluetooth-enabled smart lighting systems within an interconnected wireless communication environment 5200. The figure demonstrates how linear smart lamps 5202, 5204, 5206, 5208, and 5210 function as data transmission hubs, providing high-speed wireless connectivity via Li-Fi, Bluetooth, and other networked protocols.

[0256] The invisible light pulses 5212, 5214, 5216, 5218, 5220, 5222, 5224, 5226, 5228, 5230, and 5232 emitted by the lamps 5202, 5204, 5206, 5208, and 5210 represent Li-Fi data transmission, which allows for ultra-fast, secure, and low-latency wireless communication at speeds exceeding 1-6 Gbps. These pulses enable real-time internet access, device synchronization, and high-bandwidth data sharing, making the lighting system an integral part of the building’s network infrastructure.

[0257] Additionally, the figure shows potentially seamless connectivity between multiple smart devices, including laptops 5234, 5236, and 5238, mobile phones 5240, tablets 5242, and loT-enabled devices (not shown), through Li-Fi and Bluetooth communication channels. In this example, the lamps 5202, 5204, 5206, 5208, and 5210 may broadcast and receive data, ensuring a secure, interference-free wireless experience that integrates with existing networked environments.

[0258] The system architecture in this figure shows the multi-functional adaptability of the linear smart lamp technology, demonstrating how Li-Fi and Bluetooth connectivity can be integrated into removable, replaceable, and upgradeable smart lighting fixtures to enhance data exchange, automation, and intelligent building management. The modular lighting infrastructure disclosed further supports mesh networking, environmental sensing, and realtime analytics, ensuring that buildings, offices, and industrial spaces benefit from nextgeneration wireless solutions.

[0259] It is appreciated that the Li-Fi smart lamp system may enable enabling secure, programmable loT network integration, especially if combined with a SIM card. The disclosed Li-Fi smart lamp system may enable communication between connected loT sensors, HVAC controllers, security devices, and building automation systems. This allows for a modular luminaire lighting solution that eliminates forced obsolescence, allowing users to replace only the loT module instead of discarding the entire luminaire when networks evolve. As disclosed, this type of Li-Fi smart lamp system may be extended to an loT luminaire lighting systems thatAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026can be integrated into military, healthcare, and educational infrastructure for real-time monitoring and automation. Further, when combined with the previously disclosed SIM card, the SIM enabled Li-Fi luminaire may allow for secure wireless communication using Wi-Fi, Bluetooth Mesh, and Li-Fi to improve data security in high-risk environments. In these examples, it is appreciated that the SIM card module does not have to be located exclusively within the NCD (NCD 204 or 4604) or the connector system (e.g., connector system 200) and may, instead, be located within different locations within the modular luminaire such that locations of the SIM card module may be located in locations that are based on aesthetic and / or functional designs. It is noted that in the various examples previously discussed, the smart luminaire system described may be capable of detecting environmental changes, transmitting data through secure mesh networks, and triggering automated responses in real time.

[0260] As such, the techniques and system disclosed herein discusses techniques to advanced lighting and wireless communication systems, specifically to a removable, replaceable, and upgradeable linear lamp that integrates Li-Fi technology for high-speed, secure data communication. As was discussed, unlike existing Li-Fi systems, which are integrated into luminaires, these techniques establish Li-Fi as a modular, standalone, and mechanically adaptable smart lamp solution, enabling broad compatibility across multiple lighting infrastructures and connection standards.

[0261] In general, this novel lamp form factor is mechanically compatible with various industry-standard connection points, including: IEC GJ 6.6 lamp holders; legacy mechanical holders for fluorescent and LED-retrofit applications; PoE RJ45 interfaces for network-powered installations; and AC / DC power inputs (2V-347V) with interchangeable socket configurations.

[0262] In general, this comprehensive approach broadens market adoption by allowing new and existing infrastructures to seamlessly integrate Li-Fi technology without replacing complete fixture arrays.

[0263] These techniques, systems, and devices discussed introduced a smart linear lamp that integrates Li-Fi technology in a mechanically removable, replaceable, and upgradeable form factor. Unlike prior Li-Fi implementations, which were only available in luminaire-based designs, this approach provides Li-Fi capabilities within a standalone lamp structure, making it adaptable for a broad range of infrastructures.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0264] Also discussed previously was a modular, removable, and upgradeable smart linear lamp with Li-Fi technology, providing high-speed, light-based wireless data transmission and illumination.

[0265] Further the Li-Fi-enabled linear lamps discussed are mechanically compatible with multiple industry-standard connection points, including IEC GJ 6.6 lamp holders, PoE RJ45 ports, and legacy fluorescent mechanical holders.

[0266] In general, the features and advantages discussed in this disclosure include modular and upgradeable Li-Fi lamp design(s); multi-voltage and multi-connector compatibility; integrated Li-Fi transmitter and receiver system; smart loT and environmental monitoring; and broad market and industry applications.

[0267] Furthermore, the modular and upgradeable Li-Fi lamp design(s) allow for standardized IEC GJ 6.6-compatible mechanical housing; alternative compatibility with PoE RJ45, AC / DC power connectors, and legacy fluorescent holders; and upgradeable Li-Fi transceiver modules, allowing future Li-Fi advancements to be integrated without replacing the entire lamp.

[0268] Moreover, the multi-voltage and multi-connector compatibility allows for support of IEC GJ 6.6 lamp holders, PoE (RJ45, RJ-type connections), and AC / DC inputs (2V-347V); and adaptable socket interfaces for different lamp form factors (T5, T8, T12, U-bend, etc.).

[0269] Additionally, the integrated Li-Fi transmitter and receiver system allows for embedded LED modulation for high-speed optical data transmission; integrated photodiodes for bi-directional data communication between lamps and connected devices; and hybrid visible and infrared optical transmission to support both illuminated and non-illuminated Li-Fi data networks.

[0270] In this disclosure, the smart loT and environmental monitoring described allow for embedded sensors for occupancy, air quality, motion detection, and temperature monitoring; and wireless Li-Fi data transmission to Al-powered cloud systems for automation; smart building control integration for energy efficiency and real-time analytics.

[0271] The broad market and industry applications allow for commercial, industrial, and government Li-Fi networking; military-grade communication for secure, non-RF data transmission; emergency response and disaster zone communication; and horticultural smart farming with Li-Fi-controlled environmental monitoring.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0272] Moreover, the additional features and advantages discussed in this disclosure include modular mechanical compatibility; multi-voltage powering system; integrated Li-Fi communication system; and environmental loT sensor array.

[0273] The modular mechanical compatibility allows for the smart linear lamp to be designed to interface with various lamp holders, including IEC GJ 6.6, legacy fluorescent fixtures, and standardized PoE lamp connectors; and the housing to be designed for modular transceiver replacement, enabling future Li-Fi technology upgrades.

[0274] The multi-voltage powering system allows the lamp to support AC and DC voltage (2V-347V) via adapter-based socket configurations; and a PoE-powered option allows network-based installations without requiring traditional AC wiring.

[0275] The integrated Li-Fi communication system allows for a high-speed LED driver to modulate light intensity for real-time data transmission; photodiodes to be integrated into the lamp body capture incoming Li-Fi signals for bidirectional communication; and Al-powered transmission error correction and data optimization are employed for real-world Li-Fi networks.

[0276] The environmental loT sensor array allow for the smart sensor integration to collect real-time environmental data, such as temperature, humidity, motion detection, and air quality; and for Li-Fi-enabled cloud connectivity facilitates Al-driven automation and analytics.

[0277] Additionally, the techniques described support multiple communication technologies, including Wi-Fi, Bluetooth Mesh, Li-Fi, and cellular networks (5G, 6G, and beyond), allowing for decentralized, secure, and scalable smart infrastructure. The techniques described allow each linear lamp can function independently as a cellular data node, an loT sensor hub, an environmental monitoring unit, or a private network access point, with modular placement options for SIM card integration and sensor tethering.

[0278] FIG. 53 is a system block diagram of an example of an implementation of aNLS 5300 in accordance with the present disclosure. In this example, a wireless mesh NLS with gateway luminaire and wireless backhaul is disclosed. Specifically, the NLS 5300 may include a network entity 5302 (e.g., server, controller, cloud service), a gateway luminaire 5306, a plurality of mesh luminaires 5308, 5310, 5312, a wide area network 5314 (e.g., cellular / satellite / Internet) providing wireless backhaul, a remote power source 5304 (AC and / or DC) providing AC and / or DC power, and UE 5316 (e.g., commissioning device, user terminal) and 5318 (e.g., commissioning device, user terminal) in accordance with the present disclosure.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0279] In FIG. 54, a system block diagram is shown of an example of an implementation of a power architecture 5400 in accordance with present disclosure. In this example the power architecture 5400 may be a multi-input power architecture that supports AC, DC, PoE, USB-C PD, and wireless power. In this example, the power architecture 5400 may include a power management module 5414 (e.g., input selection, rectifier, DC-DC conversion, protection, isolation) that selectively receives electrical power from one or more inputs including an AC input 5402 (e.g., 90-277 VAC), a DC input 5404 (e.g., 12-48 VDC), a PoE input 5406 (e.g., RJ45 or other PoE interface), a USB-C Power Delivery (PD) input 5408, and / or a wireless power receiver 5410 (e.g., inductive / RF power receiver), and provides regulated power to a lighting assembly including an LED driver 5416, a NCD 5418, a sensor array 5420 (e.g., occupancy, ambient, environmental, camera, microphone), and / or auxiliary / port power 5422, optionally in coordination with energy storage 5412 (e.g., battery and / or supercapacitor).

[0280] FIG. 55 is a system block diagram of an example of an implementation of a modular interface system 5500 in accordance with the present disclosure. The modular interface system 5500 may have interchangeable connectivity and power modules and may include an end cap / connector housing 5502 (remove / replace / upgrade) having a modular interface bay 5504 and an interconnect 5506 (e.g., connector board, backplane, harness) configured to electrically couple a lighting assembly 5518 (e.g., LED array, driver, optics) to interchangeable modules including an RJ45 / PoE module 5508, a USB-C PD module 5510, an AC / DC terminal module 5512, a wireless bridge module 5514 (e.g., BLE / Zigbee / Thread / Wi-Fi / cellular, protocol translation), and / or a SIM / UICC module 5516 (e.g., for cellular connectivity).

[0281] FIG. 56 is a system block diagram of an example of an implementation of a gateway / protocol bridge 5600 in accordance with the present disclosure. In this example, the gateway / protocol bridge 5600 may be between local wireless networks 5604 (e.g., BLE / Zigbee / Thread / UWB) and backhaul networks 5610 (e.g., Wi- Fi / cellular / ethemet / satellite). In general, the gateway / protocol bridge 5600 is configured such that a gateway luminaire 5602 bridges communications between loT device(s) 5606 on a local wireless network 5604 and a network entity 5608 via one or more backhaul network(s) 5610, optionally using edge compute / buffering 5612 (e.g., store-and-forward, preprocessing, caching) and / or local I / O (port) 5614 (e.g., USB-C / RJ45 / GPIO).

[0282] FIG. 57 is a system block diagram of an example of implementation of a commissioning workflow 5700 in accordance with the present disclosure. The commissioning workflow 5700 may include secure bootstrap, credential provisioning, and mesh join and mayAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026be configured for provisioning an unprovisioned luminaire 5702 using a commissioning device 5716 (e.g., smartphone, tablet, laptop, service tool) via one or more local links (e.g., BLE, NFC, USB-C), including identifying the device 5704 (e.g., QR / NFC / MAC / serial), performing secure bootstrap / key exchange 5706, provisioning credentials 5708 (e.g., network keys, certificates, tokens), joining a mesh and / or selecting a gateway 5710, registering with a network entity 5712, and entering an operational mode 5714 (monitor / control).

[0283] FIG. 58 is a flow diagram of an example of implementation of a method for link monitoring and failover 5800 in accordance with the present disclosure. The method allows for link monitoring and failover / handoff including store-and-forward buffering; and includes monitoring link quality 5802, determining whether quality meets a threshold 5803, operating a primary link 5804 when quality is acceptable, performing degraded-link mitigation 5806 (e.g., retry, channel change, power adjust, reroute) when quality is unacceptable, evaluating whether recovery occurs in time 5807, performing failover / handoff / rejoin to an alternate link 5808 (handoff / rejoin) when recovery does not occur in time, determining whether backhaul is available 5809, performing store-and-forward buffering 5810 (upload when available) when backhaul is unavailable, and restoring a primary link 5812 when available.

[0284] FIG. 59 is a system block diagram of an example of an implementation of a GJ6.6 lamp holder / adapter 5900 in accordance with the present disclosure. The GJ6.6 lamp holder / adapter 5900 may include a GJ6.6 lamp holder / adapter supporting AC or DC input and conversion to internal DC rails in which a GJ6.6 lamp holder 5902 may be mechanically and electrically couples to an adapter module 5906 (mechanical / electrical interface) configured to receive an AC input 5908 and / or a DC input 5910, perform rectification 5912 and / or DC-DC conversion 5914, and provide regulated power to a modular luminaire 5904.

[0285] FIG. 60 is a system block diagram of an example of an implementation of a wireless power and wireless data system 6000 in accordance with present disclosure. In this example, the wireless power and wireless data system 6000 may be a fully wireless embodiment that includes wireless power and wireless data capture / b ackhaul. Specifically, the wireless power and wireless data system 60 may be in wireless power transmitter 6002 provides inductive / RF power to a wireless power receiver 6004 of a modular luminaire 6006, and the modular luminaire 6006 communicates wirelessly with a network entity 6012 and / or user devices 6010, 6014, optionally using energy storage 6016 (e.g., optional battery).

[0286] FIG. 61 is a system block diagram of an example of an implementation of aNLS 6101 including a network entity 6102, a gateway luminaire 6106, a plurality of mesh luminairesAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 20266108, 6110, 6112, and 6114, a wide area network 6116 providing wireless backhaul, a remote power source 6120 providing AC and / or DC power, and UEs 6134 and 6136, in accordance with the present disclosure. In this example, the network entity 6102 may be in signal communication with a satellite network 6130, Wi-Fi network 6132, and / or cellular network 6134.

[0287] FIG. 62 is a system block diagram of an example of an implementation of a modular interface system 6200 including an end cap / connector housing 6202 having a modular interface bay 6204 and an interconnect 6206 configured to electrically couple a lighting assembly 6218 to interchangeable modules including an RJ45 / PoE module 6208, a USB-C PD module 6210, an AC / DC terminal module 6212, a wireless bridge module 6214, and / or a SIM / UICC module 6216.

[0288] FIG. 63 is a system block diagram of an example of an implementation of a gateway / protocol bridge 6300 in which a gateway luminaire 6302 bridges communications between loT device(s) 6312 and 6332 on a local wireless network 6304 and a network entity 6308 via one or more backhaul network(s) 6310 (e.g., a satellite), optionally using edge compute / buffering 6312 and / or local I / O (port).

[0289] FIG. 64 is a flow chart of an example of an implementation a method for a commissioning workflow 6400 for provisioning an unprovisioned luminaire using a commissioning device via one or more local links (e.g., BLE, NFC, USB-C), including identifying the device 6404, performing secure bootstrap / key exchange 6406, provisioning credentials 6408, joining a mesh and / or selecting a gateway 6410, registering with a network entity 6412, and entering an operational mode 6414.

[0290] FIG. 65 is a flow diagram of an example of an implementation a method 6500 for link monitoring and failover in accordance with the present disclosure. The method 6500 may include monitoring link quality 6502, determining whether quality meets a threshold 6504, operating a primary link 6506 when quality is acceptable, performing degraded-link mitigation 6508 when quality is unacceptable, evaluating 6510 whether recovery occurs in time, performing 6512 failover / handoff / rejoin to an alternate link when recovery does not occur in time, determining 6514 whether backhaul is available, performing 6516 store-and-forward buffering when backhaul is unavailable, and restoring 6518 a primary link when available.

[0291] In FIG. 66, a system block diagram is shown of an example of an implementation of wireless mesh lighting network 6600 with gateway backhaul in accordance with the present disclosure. In this example, the wireless mesh lighting network 6600 includes a mesh topologyAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026among luminaires that includes a gateway luminaire providing backhaul via Wi-Fi / cellular / satellite. This example illustrates an implementation that supports wireless-only deployments, gateway terminology, and mesh routing embodiments that extends some of the previous examples that were described as being connected / coupled via wires. Specifically, the mesh lighting network 6600 illustrates an example of an implementation of an example lighting network in which a plurality of luminaire nodes communicate via the wireless mesh network 6600 and at least one gateway luminaire node provides a backhaul connection to a network entity 6620.

[0292] The wireless mesh network 6600 may include a premises (i.e., a zone within or about a structure) 6601 in signal communication with a network 6622 that may be, for example, a private WAN or the Internet. The network 6622 may be in signal communication with the network entity 6620 (which may be a cloud service-based network entity) via, for example, a secure session 6624 (e.g., TLS / VPN). In this example, the wireless mesh network 6600 within the premises 6601 may include a plurality of luminaires (e.g., luminaire nodes 6602, 6604, and 6606) that may each include circuitry, devices, modules, and / or components to control the lighting; and optional sensors. Additionally, the wireless mesh network 6600 within the premises 6601 may be configured to exchange control data, sensor data, and / or network routing information. In this example, the wireless mesh network 6600 within the premises 6601 may also include a gateway luminaire node 6610 that may include a mesh router that may provide a backhaul connection. As a further example, the wireless mesh network 6600 within the premises 6601 may also include one or more optional sensors 6630 and 6632 (that may be, for example, occupancy, environmental, air quality, temperature, etc. type of sensors), one or more mesh links 6612, 6614, and 6616, and one or more UEs 6640 (e.g., cellphone, tablet, laptop, etc.). In this example, the mesh links 6612, 6614, and 6616 may allow the plurality of luminaires (e.g., luminaire nodes 6602, 6604, and 6606) to be in signal communication with the gateway luminaire node 6610 and themselves. In this example, the wireless mesh network 6600 within the premises 6601 may also include backhaul signal path 6618 (e.g., Wi-Fi, cellular, satellite, etc.) or optional commissioning link 6642 (e.g., Bluetooth®, NFC, Wi-fi, etc.) between the gateway luminaire node 6610 and user UE 6640 and the wireless sensors 6630 and 6632 may be in signal communication with both the luminaire nodes 6602 and 6606 via optional low-power sensor links 6634 and 6636, respectively, that may each be, for example, a Bluetooth®, Thread, Zigbee, etc. type of signal path. As an example, a selected luminaire (e.g., gateway luminaire node 6610) may provide a backhaul connection 6618 to theAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026network 6622 and the network entity 6620 using one or more wireless interfaces (e.g., Wi-Fi, cellular, satellite) and may route communications between the mesh and the network entity 6620.

[0293] Turning to FIG. 67, a front view of example of another implementation of a four (4) sided light surface is shown in accordance with the present disclosure. This example is to illustrate that the present disclosure is not limited to two- or three-side delta designs as previously shown in FIGS. 15A through 16, and 19-35. The design may be extended to four or more sided light surfaces without departing from the spirit of the disclosure.

[0294] FIG. 68 is a system block diagram of an example of an implementation of a multiinput power architecture 6800 in which a luminaire node may receive power from one or more of an AC input 6802, a DC input 6804, a PoE input 6806, a USB-C power delivery (PD) input 6808 (e.g., USB-C or USB4) , and / or a wireless power receiver 6810 in accordance with the present disclosure. The luminaire node may include a power management module (e.g., input selector 6820) configured to accept and prioritize multiple power sources, including AC mains (via AC / DC conversion 6822), an external DC supply (via DC / DC conversion 6824), PoE 6806 (which may be Ethernet plus power), USB-C PD 6806, and / or wireless power transfer 6810 (e.g., inductive or resonant power transfer). In this example, the power management module 6820 may provide regulated power to an LED driver 6830, control / communication electronics 6840 (e.g., MCU / SoC plus radio), and sensor module(s) 6850 (e.g., environmental, occupancy, etc.), and may charge / discharge an energy storage device 6860 (e.g., a battery, supercapacitor, etc.) for backup operation.

[0295] It is appreciated that utilizing this architecture, there are multiple AC / DC powering options beyond PoE that USB-C PD and an optional wireless power receiver, plus energy storage / backup.

[0296] FIG. 69 is a system block diagram of an example of an implementation of connector system 6902 that includes an interface bay configured to receive an interchangeable interface module selected from a plurality of interface modules in accordance with the present disclosure. The connector system 6902 may be an interchangeable interface module that may include an expansion bay for, as an example, USB-C and other connection types. This allows the connector system 6902 to support non-Ethernet interfaces (e.g., USB-C, RS-485, optical, etc.) and a modular “interface bay” concept. In this example, the connector system 6902 may include an interface bay configured to receive an interchangeable interface module selected from a plurality of different interface modules.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0297] In some embodiments, a connector system 6902 may include an interface bay that mechanically and electrically mates with an interchangeable interface module (e.g., 6904A-6904D). The interchangeable interface modules may include, for example, USB-C / USB4 module 6904A, Ethernet module (optional PoE) 6904B, fieldbus module (e.g., RS-485 / DALI) 6904C, and optical / fiber module 6904D that maybe inserted / removed (i.e., 6906, 6908, 6910, and 6912) from the connector system 6902. In this example, the selected module may provide a selected external interface 6922 such as USB-C (optionally supporting power delivery and data), Ethernet, fieldbus interfaces (e.g., RS-485 or DALI), optical / fiber interfaces, and / or other physical interfaces to external devices 6920 (e.g., sensors, gateways, tool, etc.). Internally, the interface bay of the connector system 6902 may be in signal communication with a controller 6914 via an internal bus 6916.

[0298] FIG. 70 is a system block diagram of an example of an implementation of gateway luminaire node 7000 in accordance with the present disclosure. In this example, the gateway luminaire node 7000 may operate a protocol bridge that allows for protocol bridging / routing, security, and mesh / backhaul interfaces and is associated to gateways, local protocol translation, and edge processing that is connected to the discussion related to FIGS. 46-47. In general, FIG. 56 illustrates a functional block diagram illustrating an example gateway luminaire node including a protocol bridge configured to route and / or translate communications among a mesh interface, a backhaul interface, and one or more local device interfaces.

[0299] As an example, the luminaire node 700 may operate as a gateway by executing routing and / or protocol-translation functionality (e.g., protocol bridge 7006) between a local mesh network (mesh interface 7010) and an external network (backhaul interface 7012). The gateway node may further interface with local user equipment via BLE / NFC (7016) and / or Li-Fi (7014), and may enforce security policies using a security module 7004 (e.g., key storage, attestation, authentication). In this example, the gateway luminaire node 7000 may include an edge processor 7002, security module 7004, protocol bridge 7006, authentication / keys link 7008, one or more mesh interface 7010, one or more backhaul interface 7012, Li-Fi interface (optional) 7014, local device interface (BLE / NFC) 7016, one or more sensor interface 7018, sensor data 7020, network entity 7022, neighbor nodes 7024, one or more user equipment 7026, one or more loT device(s) 7028, and example links 7030, 7032, 7034, and 7036.

[0300] FIG. 71 is a system flow diagram of an example of an implementation of wireless commissioning and / or onboarding workflow in accordance with present disclosure. This example illustrates a process for device onboarding (e.g., BLE / NFC / QR commissioning)Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026which is often a key differentiator in modern wireless loT deployments. In this example, the commissioning workflow illustrates how a commissioning device (e.g., smartphone / tablet) 7102 provisions a luminaire node 7110 using a local wireless link 7108 and the luminaire node subsequently registers with a network entity 7102.

[0301] As an example, the luminaire node 7110 may be commissioned using a commissioning device (e.g., smartphone or installer tool) 7102 that reads 7106 an out-of-band identifier (e.g., QR / NFC / serial) 7104 and establishes a local wireless link 7108 (e.g., BLE, NFC, Wi-Fi Direct) to securely provision network credentials 7112 and / or cryptographic material. Following provisioning, the luminaire node 7102 may join 7114 a local network (e.g., local network / AP) 7122 and register with a network entity 7102 for configuration, policy enforcement, and / or software updates (see 7116 and 7118).

[0302] FIG. 72 is a system block diagram of an example of an implementation of backhaul selection and handoff state diagram 7200. Generally, FIG. 72 is a state diagram illustrating an example backhaul selection and handoff process for maintaining network connectivity of a luminaire node using one or more available communication interfaces. This state diagram illustrates a requested ‘handoff concept by illustrating network selection and failover among multiple wireless backhauls (Wi-Fi, mesh, cellular, satellite) and an offline store-and-forward mode. Using this process, a luminaire node may implement a connectivity manager configured to select among multiple communication interfaces based on availability and / or policy. When a preferred interface becomes unavailable or falls below a threshold, the node may hand off communications to an alternative interface (e.g., via mesh routing, cellular, or satellite) and may buffer data locally during offline operation for later transmission. In this example, the states may include Wi-Fi backhaul state 7202, mesh backhaul state 7204, cellular backhaul state 7206, satellite backhaul state 7208, offline / store-and-forward state 7210, and example transition conditions 7212 through 7238.

[0303] FIG. 73 is a system block diagram of an example of an implementation of an example adapter 7306 configured to mechanically couple to a lamp holder 7302 and electrically couple power to a luminaire node 7320 in accordance with the present disclosure. In this example, the example lamp holder 7302 may be GJ6.6 family type of lamp holder. The adapter 7306 may be configured to support for retrofit embodiments using legacy lamp holders, including the requested GJ6.6 family type of lamp holders. In this example, the adaptor may support both AC and DC retrofit power pathways.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0304] In this example, the luminaire node 7320 may receive power via the adapter 7306 (via a power / data output 7308) that is configured to interface with an existing lamp holder 7302 (e.g., GJ6.6 family), where the adapter 7306 may be coupled to lamp holder 7302, via pins 7304, and may provide AC and / or DC power form a AC / DC power source 7312 to the luminaire node 7320 and may optionally provide a data interface, depending on the deployment.

[0305] FIG. 74 is a system block diagram of an example of operation of the luminaire node 7402 under full wireless operation in accordance with the present disclosure. In this example, the operation is shown to be fully wireless including wireless power and wireless data capture. In this example, the luminaire node 7402 may include a light, controller, and radios and may be in signal communication with a wireless power transmitter 7404 (e.g., a pad, coil, emitter, etc.), one or more wireless sensors 7410 (e.g., environmental, occupancy, etc.), one or more UEs 7412 (e.g., cellphones, tablets, laptops, etc.), an energy storage device 7430 (e.g., a battery or supercapacitor), and a network entity 7420 (e.g., a server or cloud based network device).

[0306] It is appreciated that in this disclosure the following terms are defined as follows. Gateway: A device or luminaire node configured to provide a backhaul connection between a local network (e.g., a luminaire mesh and / or local sensor network) and an external network or network entity, optionally performing routing, protocol translation, and security functions. Backhaul: A communication path between a luminaire node (or gateway node) and a network entity, which may be implemented using one or more wired and / or wireless interfaces including Wi-Fi, cellular, satellite, and / or Ethernet. Wireless Mesh Network: A network in which a plurality of luminaire nodes and / or sensor nodes communicate over wireless links and may relay communications for other nodes, optionally using multi-hop routing. Commissioning: A process of onboarding / provisioning a luminaire node, including associating the node with a premises or controller, providing network credentials and / or cryptographic material, and registering the node with a network entity. Handoff / Failover: A process of transitioning communications from one communication interface or network path to another (e.g., Wi-Fi to cellular or mesh to Wi-Fi) based on availability, link quality, policy, cost, or other criteria, optionally maintaining session continuity and / or buffering data. USB-C Power Delivery (USB-C PD): A standardized power delivery mechanism for providing DC power over a USB-C interface, which may be used to power a luminaire node and / or power connected peripherals. Wireless Power Transfer: Transfer of energy from a transmitter to a receiver without direct wired electrical contact, including inductive, resonant inductive, capacitive,Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026radio-frequency, or other wireless power techniques. Store-and-Forward: A mode in which a node buffers data locally when no communication path is available, and transmits the buffered data when connectivity is restored.Implementation examples

[0307] Implementation examples are provided in the following numbered clauses.

[0308] Clause 1. A connector system for a modular luminaire, the connector system comprising: a connector housing configured to be removably attached to a lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; and a network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

[0309] Clause 2. The connector system of clause 1, wherein the NCD includes a communication device configured to communicate with the network entity.

[0310] Clause 3. The connector system of clause 2, wherein the communication device includes at least one transceiver that is selected from the group consisting of a wireless fidelity (Wi-Fi) transceiver, Bluetooth transceiver, light fidelity (Li-Fi) transceiver, cellular transceiver, and satellite transceiver.

[0311] Clause 4. The connector system of clause 3, wherein the cellular transceiver is a cellular repeater or a femtocell.

[0312] Clause 5. The connector system of clause 3, wherein the satellite transceiver is a satellite repeater or a femtocell.

[0313] Clause 6. The connector system of clause 3, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

[0314] Clause 7. The connector system of clause 6, wherein a loT device is a sensor configured to sense environmental conditions of an environment of which the connector system is located within.

[0315] Clause 8. The connector system of clause 3, wherein the Wi-Fi transceiver is configured to communicate with one or more remote devices.

[0316] Clause 9. The connector system of clause 8, wherein the communication device is configured to operate as a Wi-Fi access point for the one or more remote devices.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0317] Clause 10. The connector system of clause 3, wherein the Li-Fi transceiver is configured to communicate with one or more remote devices.

[0318] Clause 11. The connector system of clause 10, wherein the communication device is configured to operate as a Li-Fi access point for the one or more remote devices.

[0319] Clause 12. The connector system of clause 3, wherein the cellular transceiver is configured to communicate with one or more remote devices utilizing either a cellular signal repeater or cellular service femtocell.

[0320] Clause 13. The connector system of clause 3, wherein the satellite transceiver is configured to communicate with one or more remote devices utilizing either a satellite signal repeater or satellite service femtocell.

[0321] Clause 14. The connector system of clause 2, wherein the communication device includes a radio-frequency identification (RFID) device configured to communicate with an RFID card.

[0322] Clause 15. The connector system of clause 2, wherein the NCD further includes at least one device that is selected from the group consisting of one or more processors, one or more memories, one or more network interfaces, and one or more sensors.

[0323] Clause 16. The connector system of clause 2, wherein the NCD further includes a universal integrated circuit card (UICC).

[0324] Clause 17. The connector system of clause 16, wherein the UICC is a smart card.

[0325] Clause 18. The connector system of clause 17, wherein the smart card includes a subscriber identity module (SIM) card.

[0326] Clause 19. The connector system of clause 18, wherein the communication device is further configured to communicate with one or more network devices utilizing the SIM card.

[0327] Clause 20. The connector system of clause 19, wherein the communication device is a platform-agnostic communication device that is configured to communicate with the one or more network devices utilizing the SIM card, the UICC is configured to store multiple network profiles that include a network profile for the one or more network devices that allows the communication device to communicate with the one or more network devices, and the one or more network devices includes the network entity, the one or more remote devices, or both.

[0328] Clause 21. The connector system of clause 20, wherein the UICC is configured to download the multiple network profiles that include network protocols and security frameworks.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0329] Clause 22. The connector system of clause 1, wherein the modular luminaire is a light-emitting diode (LED) lamp, and the connector system is a device that is compliant with a GJ6.6 standard.

[0330] Clause 23. The connector system of clause 2, wherein the network device further includes a sensor.

[0331] Clause 24. The connector system of clause 23, wherein the sensor is an environmental sensor that is a temperature sensor, motion sensor, humidity sensor, sound sensor, light sensor, radiation sensor, gas sensor, or air quality sensor.

[0332] Clause 25. The connector system of clause 2, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

[0333] Clause 26. The smart modular luminaire of clause 25, wherein a loT device is a sensor configured to sense environmental conditions of an environment of which the connector system is located within.

[0334] Clause 27. A smart modular luminaire comprising: a lighting assembly; a connector housing configured to be removably attached to the lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; and a network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

[0335] Clause 28. The smart modular luminaire of clause 27, wherein the NCD includes a communication device configured to communicate with the network entity.

[0336] Clause 29. The smart modular luminaire of clause 28, wherein the communication device includes at least one transceiver that is selected from the group consisting of a wireless fidelity (Wi-Fi) transceiver, Bluetooth transceiver, light fidelity (Li-Fi) transceiver, cellular transceiver, and satellite transceiver.

[0337] Clause 30. The smart modular luminaire of clause 29, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

[0338] Clause 31. The smart modular luminaire of clause 30, wherein a loT device is a sensor configured to sense environmental conditions of an environment of which the connector system is located within.-n-Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0339] Clause 32. The smart modular luminaire of clause 29, wherein the Wi-Fi transceiver is configured to communicate with one or more remote devices.

[0340] Clause 33. The smart modular luminaire of clause 32, wherein the communication device is configured to operate as a Wi-Fi access point for the one or more remote devices.

[0341] Clause 34. The smart modular luminaire of clause 29, wherein the Li-Fi transceiver is configured to communicate with one or more remote devices.

[0342] Clause 35. The smart modular luminaire of clause 34, wherein the communication device is configured to operate as a Li-Fi access point for the one or more remote devices.

[0343] Clause 36. A modular luminaire comprising: a lighting assembly having a body with a length; a network device; a first connector system including a first connector housing configured to be removably attached to the body of the lighting assembly, and a first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly; and a second connector system including a first connector housing configured to be removably attached to the body of the lighting assembly, a first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly, wherein the network device is electrically coupled to the first end connector board, wherein the first network device is configured to communicate with a remote entity.

[0344] Clause 37. The modular luminaire of clause 36, wherein the first connector system includes the network device.

[0345] Clause 38. The modular luminaire of clause 36, wherein the network device is located along the body of the lighting assembly external to both the first connector housing and the second connector housing. Clause 39. The modular luminaire of clause 37, wherein the second connector system includes a second network device configured to communicate with the remote entity.

[0346] Clause 40. A modular luminaire comprising: a lighting assembly having a body with a length; a first connector system; a second connector system; and a network device configured to communicate with a remote entity, wherein the first connector system includes a first connector housing configured to be removably attached to the body of the lighting assembly, a first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly, the second connector system includes a second connector housing configured to be removably attached to the body of the lighting assembly at a location opposite the first connector housing along theAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026length of the body of the lighting assembly, a second end connector board within the second connector housing, wherein the second end connector board is configured to electrically couple to the lighting assembly, and the network device is at a location along the body of the lighting assembly that is between first connector system and the second connector system, and is in signal communication with the first end connector board, second end connector board, or both.

[0347] Clause 41. A connector system for a modular luminaire, the connector system comprising: a connector housing configured to be removably attached to a lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; and a network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

[0348] Clause 42. The connector system of clause 41, wherein the NCD includes a communication device configured to communicate with the network entity.

[0349] Clause 43. The connector system of clause 42, wherein the communication device includes at least one transceiver that is selected from the group consisting of a wireless fidelity (Wi-Fi) transceiver, Bluetooth transceiver, light fidelity (Li-Fi) transceiver, cellular transceiver, and satellite transceiver.

[0350] Clause 44. The connector system of clause 43, wherein the cellular transceiver is a cellular repeater or a femtocell.

[0351] Clause 45. The connector system of clause 43, wherein the satellite transceiver is a satellite repeater or a femtocell.

[0352] Clause 46. The connector system of clause 43, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

[0353] Clause 47. The connector system of clause 46, wherein an loT device is a sensor configured to sense environmental conditions of an environment in which the connector system is located.

[0354] Clause 48. The connector system of clause 43, wherein the Wi-Fi transceiver is configured to communicate with one or more remote devices.

[0355] Clause 49. The connector system of clause 48, wherein the communication device is configured to operate as a Wi-Fi access point for the one or more remote devices.

[0356] Clause 50. The connector system of clause 43, wherein the Li-Fi transceiver is configured to communicate with one or more remote devices.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0357] Clause 51. The connector system of clause 50, wherein the communication device is configured to operate as a Li-Fi access point for the one or more remote devices.

[0358] Clause 52. The connector system of clause 43, wherein the cellular transceiver is configured to communicate with one or more remote devices utilizing either a cellular signal repeater or cellular service femtocell.

[0359] Clause 53. The connector system of clause 43, wherein the satellite transceiver is configured to communicate with one or more remote devices utilizing either a satellite signal repeater or satellite service femtocell.

[0360] Clause 54. The connector system of clause 42, wherein the communication device includes a radio-frequency identification (RFID) device configured to communicate with an RFID card.

[0361] Clause 55. The connector system of clause 42, wherein the NCD further includes at least one device that is selected from the group consisting of one or more processors, one or more memories, one or more network interfaces, and one or more sensors.

[0362] Clause 56. The connector system of clause 42, wherein the NCD further includes a universal integrated circuit card (UICC).

[0363] Clause 57. The connector system of clause 56, wherein the UICC is a smart card.

[0364] Clause 58. The connector system of claim 57, wherein the smart card includes a subscriber identity module (SIM) card.

[0365] Clause 59. The connector system of clause 58, wherein the communication device is further configured to communicate with one or more network devices utilizing the SIM card.

[0366] Clause 60. The connector system of clause 59, wherein the communication device is a platform-agnostic communication device that is configured to communicate with the one or more network devices utilizing the SIM card, the UICC is configured to store multiple network profiles that include a network profile for the one or more network devices that allows the communication device to communicate with the one or more network devices, and the one or more network devices includes the network entity, the one or more remote devices, or both.

[0367] Clause 61. The connector system of clause 60, wherein the UICC is configured to download the multiple network profiles that include network protocols and security frameworks.

[0368] Clause 62. The connector system of clause 41, wherein the modular luminaire is a light-emitting diode (LED) lamp, and the connector system is a device that is compliant with a GJ6.6 standard.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0369] Clause 63. The connector system of clause 62, wherein the NCD further includes a sensor.

[0370] Clause 64. The connector system of clause 63, wherein the sensor is an environmental sensor that is a temperature sensor, motion sensor, humidity sensor, sound sensor, light sensor, radiation sensor, gas sensor, or air quality sensor.

[0371] Clause 65. The connector system of clause 62, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

[0372] Clause 66. The connector system of clause 65, wherein an loT device is a sensor configured to sense environmental conditions of an environment in which the connector system is located.

[0373] Clause 67. A smart modular luminaire comprising: a lighting assembly; a connector housing configured to be removably attached to the lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; and a network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

[0374] Clause 68. The smart modular luminaire of clause 67, wherein the NCD includes a communication device configured to communicate with the network entity.

[0375] Clause 69. The smart modular luminaire of clause 68, wherein the communication device includes at least one transceiver that is selected from the group consisting of a wireless fidelity (Wi-Fi) transceiver, Bluetooth transceiver, light fidelity (Li-Fi) transceiver, cellular transceiver, and satellite transceiver.

[0376] Clause 70. The smart modular luminaire of clause 69, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

[0377] Clause 71. The smart modular luminaire of clause 70, wherein a loT device is a sensor configured to sense environmental conditions of an environment of which the connector system is located within.

[0378] Clause 72. The smart modular luminaire of clause 69, wherein the Wi-Fi transceiver is configured to communicate with one or more remote devices.

[0379] Clause 73. The smart modular luminaire of clause 72, wherein the communication device is configured to operate as a Wi-Fi access point for the one or more remote devices.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0380] Clause 74. The smart modular luminaire of clause 69, wherein the Li-Fi transceiver is configured to communicate with one or more remote devices.

[0381] Clause 75. The smart modular luminaire of clause 74, wherein the communication device is configured to operate as a Li-Fi access point for the one or more remote devices.

[0382] Clause 76. A modular luminaire comprising: a lighting assembly having a body with a length; a first connector system including a first connector housing configured to be removably attached to the body of the lighting assembly, and a first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly; a second connector system including a second connector housing configured to be removably attached to the body of the lighting assembly, and a second end connector board within the second connector housing, wherein the second end connector board is configured to electrically couple to the lighting assembly; and a network device electrically coupled to at least one of the first end connector board or the second end connector board, wherein the network device is configured to communicate with a remote entity.

[0383] Clause 77. The modular luminaire of clause 76, wherein the first connector system includes the network device.

[0384] Clause 78. The modular luminaire of clause 76, wherein the network device is located along the body of the lighting assembly external to both the first connector housing and the second connector housing.

[0385] Clause 79. The modular luminaire of clause 77, wherein the second connector system includes a second network device configured to communicate with the remote entity.

[0386] Clause 80. A modular luminaire comprising: a lighting assembly having a body with a length; a first connector system; a second connector system; and a network device configured to communicate with a remote entity, wherein the first connector system includes a first connector housing configured to be removably attached to the body of the lighting assembly, a first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly, the second connector system includes a second connector housing configured to be removably attached to the body of the lighting assembly at a location opposite the first connector housing along the length of the body of the lighting assembly, a second end connector board within the second connector housing, wherein the second end connector board is configured to electrically couple to the lighting assembly, and the network device is at a location along the body of the lightingAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026assembly that is between the first connector system and the second connector system, and is in signal communication with the first end connector board, second end connector board, or both.

[0387] Clause 81. The connector system of clause 80, wherein the end connector board is configured to receive electrical power comprising at least one of alternating current (AC) power or direct current (DC) power.

[0388] Clause 82. The connector system of clause 41, further comprising power conversion circuitry configured to provide one or more regulated DC voltages for powering at least one of the lighting assembly, the NCD, or one or more sensors.

[0389] Clause 83. The connector system of clause 80, wherein the connector system includes at least one physical interface selected from the group consisting of an RJ-type connector, a Universal Serial Bus (USB) connector, and an IEEE 1394 connector.

[0390] Clause 84. The connector system of clause 83, wherein the USB connector is a USB Type-C connector configured to support USB Power Delivery (USB-PD).

[0391] Clause 85. The connector system of clause 81, wherein the communication device is configured to communicate with the network entity wirelessly without requiring a wired data cable between the connector system and the network entity.

[0392] Clause 86. The connector system of clause 81, wherein the NCD is configured to operate as at least one of a gateway, router, bridge, repeater, access point, or mesh node between a first network and a second network.

[0393] Clause 87. The connector system of clause 86, wherein the NCD is configured to participate in a wireless mesh network with one or more other modular luminaires and forward communications between mesh nodes.

[0394] Clause 88. The connector system of clause 81, wherein the communication device is configured to detect a communication error condition and, in response, automatically perform a corrective action.

[0395] Clause 89. The connector system of clause 48, wherein the corrective action includes switching from a first communication mode to a second communication mode.

[0396] Clause 90. The connector system of clause 22, wherein the GJ6.6-compliant device is configured to mate with a lamp holder that provides AC power, DC power, or both.

[0397] Clause 91. The smart modular luminaire of clause 27, wherein the lighting assembly is powered by at least one of AC power or DC power, and wherein the NCD communicates with the network entity via at least one wireless transceiver.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0398] Clause 92. The smart modular luminaire of clause 27, wherein network communications and sensor data transmission are performed via wireless communications while the lighting assembly is powered via AC or DC.

[0399] Clause 93. The connector system of clause 81, wherein the NCD is configured to be commissioned or provisioned using a mobile device via a short-range wireless interface.

[0400] These also techniques allow for future-proof linear lamp lighting systems that may be designed for global applications, with use cases spanning commercial, industrial, healthcare, military, education, emergency response, smart city infrastructure, and deep-space communication applications. These techniques may introduce a new industry standard for scalable, secure, and upgradeable lighting solutions by eliminating the limitations of fixed, embedded communication hardware.

[0401] Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software and computers, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0402] As used herein, the singular forms “a,” “an,” and “the” include the plural forms as well, unless the context clearly indicates otherwise. Thus, reference to a device in the singular (e.g., “a device,” “the device”), including in the claims, includes at least one, i.e., one or more, of such devices (e.g., “a processor” includes at least one processor (e.g., one processor, two processors, etc.), “the processor” includes at least one processor, “a memory” includes at least one memory, “the memory” includes at least one memory, etc.). The phrases “at least one” and “one or more” are used interchangeably and such that “at least one” referred-to object and “one or more” referred-to objects include implementations that have one referred-to object and implementations that have multiple referred-to objects. For example, “at least one processor” and “one or more processors” each includes implementations that have one processor and implementations that have multiple processors.

[0403] The terms “comprises,” “comprising,” “includes,” and / or “including,” as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026

[0404] Also, as used herein, “or” as used in a list of items (possibly prefaced by “at least one of’ or prefaced by “one or more of’) indicates a disjunctive list such that, for example, a list of “at least one of A, B, or C,” or a list of “one or more of A, B, or C” or a list of “A or B or C” means A, or B, or C, or AB (A and B), or AC (A and C), or BC (B and C), or ABC (i.e., A and B and C), or combinations with more than one feature (e.g., AA, AAB, ABBC, etc.). Thus, a recitation that an item, e.g., a processor, is configured to perform a function regarding at least one of A or B, or a recitation that an item is configured to perform a function A or a function B, means that the item may be configured to perform the function regarding A, or may be configured to perform the function regarding B, or may be configured to perform the function regarding A and B. For example, a phrase of “a processor configured to measure at least one of A or B” or “a processor configured to measure A or measure B” means that the processor may be configured to measure A (and may or may not be configured to measure B), or may be configured to measure B (and may or may not be configured to measure A), or may be configured to measure A and measure B (and may be configured to select which, or both, of A and B to measure). Similarly, a recitation of a means for measuring at least one of A or B includes means for measuring A (which may or may not be able to measure B), or means for measuring B (and may or may not be configured to measure A), or means for measuring A and B (which may be able to select which, or both, of A and B to measure). As another example, a recitation that an item, e.g., a processor, is configured to at least one of perform function X or perform function Y means that the item may be configured to perform the function X, or may be configured to perform the function Y, or may be configured to perform the function X and to perform the function Y. For example, a phrase of “a processor configured to at least one of measure X or measure Y” means that the processor may be configured to measure X (and may or may not be configured to measure Y), or may be configured to measure Y (and may or may not be configured to measure X), or may be configured to measure X and to measure Y (and may be configured to select which, or both, of X and Y to measure).

[0405] As used herein, unless otherwise stated, a statement that a function or operation is “based on” an item or condition means that the function or operation is based on the stated item or condition and may be based on one or more items and / or conditions in addition to the stated item or condition.

[0406] Substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used, and / or particular elements might be implemented in hardware, software (including portable software, such as applets, etc.) executedAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026by a processor, or both. Further, connection to other computing devices such as network input / output devices may be employed. Components, functional or otherwise, shown in the figures and / or discussed herein as being connected or communicating with each other are communicatively coupled unless otherwise noted. That is, they may be directly or indirectly connected to enable communication between them.

[0407] The systems and devices discussed above are examples. Various configurations may omit, substitute, or add various procedures or components as appropriate. For instance, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of the configurations may be combined in a similar manner. Also, technology evolves and, thus, many of the elements are examples and do not limit the scope of the disclosure or claims.

[0408] Specific details are given in the description herein to provide a thorough understanding of example configurations (including implementations). However, configurations may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail in order to avoid obscuring the configurations. The description herein provides example configurations, and does not limit the scope, applicability, or configurations of the claims. Rather, the preceding description of the configurations provides a description for implementing described techniques. Various changes may be made in the function and arrangement of elements.

[0409] Having described several example configurations, various modifications, alternative constructions, and equivalents may be used. For example, the above elements may be components of a larger system, wherein other rules may take precedence over or otherwise modify the application of the disclosure. Also, a number of operations may be undertaken before, during, or after the above elements are considered. Accordingly, the above description does not bound the scope of the claims.

Claims

Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026CLAIMS:What is claimed.

1. A connector system for a modular luminaire, the connector system comprising: a connector housing configured to be removably attached to a lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; anda network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

2. The connector system of claim 1, wherein the NCD includes a communication device configured to communicate with the network entity.

3. The connector system of claim 2, wherein the communication device includes at least one transceiver that is selected from the group consisting of a wireless fidelity (Wi-Fi) transceiver, Bluetooth transceiver, light fidelity (Li-Fi) transceiver, cellular transceiver, and satellite transceiver.

4. The connector system of claim 3, wherein the cellular transceiver is a cellular repeater or a femtocell.

5. The connector system of claim 3, wherein the satellite transceiver is a satellite repeater or a femtocell.

6. The connector system of claim 3, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

7. The connector system of claim 6, wherein a loT device is a sensor configured to sense environmental conditions of an environment of which the connector system is located within.

8. The connector system of claim 3, wherein the Wi-Fi transceiver is configured to communicate with one or more remote devices.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 20269. The connector system of claim 8, wherein the communication device is configured to operate as a Wi-Fi access point for the one or more remote devices.

10. The connector system of claim 3, wherein the Li-Fi transceiver is configured to communicate with one or more remote devices.

11. The connector system of claim 10, wherein the communication device is configured to operate as a Li-Fi access point for the one or more remote devices.

12. The connector system of claim 3, wherein the cellular transceiver is configured to communicate with one or more remote devices utilizing either a cellular signal repeater or cellular service femtocell.

13. The connector system of claim 3, wherein the satellite transceiver is configured to communicate with one or more remote devices utilizing either a satellite signal repeater or satellite service femtocell.

14. The connector system of claim 2, wherein the communication device includes a radio-frequency identification (RFID) device configured to communicate with an RFID card.

15. The connector system of claim 2, wherein the NCD further includes at least one device that is selected from the group consisting of one or more processors, one or more memories, one or more network interfaces, and one or more sensors.

16. The connector system of claim 2, wherein the NCD further includes a universal integrated circuit card (UICC).

17. The connector system of claim 16, wherein the UICC is a smart card.

18. The connector system of claim 17, wherein the smart card includes a subscriber identity module (SIM) card.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 202619. The connector system of claim 18, wherein the communication device is further configured to communicate with one or more network devices utilizing the SIM card.

20. The connector system of claim 19, whereinthe communication device is a platform-agnostic communication device that is configured to communicate with the one or more network devices utilizing the SIM card, the UICC is configured to store multiple network profiles that include a network profile for the one or more network devices that allows the communication device to communicate with the one or more network devices, andthe one or more network devices includes the network entity, the one or more remote devices, or both.

21. The connector system of claim 20, wherein the UICC is configured to download the multiple network profiles that include network protocols and security frameworks.

22. The connector system of claim 1, whereinthe modular luminaire is a light-emitting diode (LED) lamp, andthe connector system is a device that is compliant with a GJ6.6 standard.

23. The connector system of claim 2, wherein the network device further includes a sensor.

24. The connector system of claim 23, wherein the sensor is an environmental sensor that is a temperature sensor, motion sensor, humidity sensor, sound sensor, light sensor, radiation sensor, gas sensor, or air quality sensor.

25. The connector system of claim 2, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

26. The smart modular luminaire of claim 25, wherein a loT device is a sensor configured to sense environmental conditions of an environment of which the connector system is located within.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 202627. A smart modular luminaire comprising:a lighting assembly;a connector housing configured to be removably attached to the lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; anda network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

28. The smart modular luminaire of claim 27, wherein the NCD includes a communication device configured to communicate with the network entity.

29. The smart modular luminaire of claim 28, wherein the communication device includes at least one transceiver that is selected from the group consisting of a wireless fidelity (Wi-Fi) transceiver, Bluetooth transceiver, light fidelity (Li-Fi) transceiver, cellular transceiver, and satellite transceiver.

30. The smart modular luminaire of claim 29, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

31. The smart modular luminaire of claim 30, wherein a loT device is a sensor configured to sense environmental conditions of an environment of which the connector system is located within.

32. The smart modular luminaire of claim 29, wherein the Wi-Fi transceiver is configured to communicate with one or more remote devices.

33. The smart modular luminaire of claim 32, wherein the communication device is configured to operate as a Wi-Fi access point for the one or more remote devices.

34. The smart modular luminaire of claim 29, wherein the Li-Fi transceiver is configured to communicate with one or more remote devices.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 202635. The smart modular luminaire of claim 34, wherein the communication device is configured to operate as a Li-Fi access point for the one or more remote devices.

36. A modular luminaire comprising:a lighting assembly having a body with a length;a network device;a first connector system includinga first connector housing configured to be removably attached to the body of the lighting assembly, anda first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly; anda second connector system includinga first connector housing configured to be removably attached to the body of the lighting assembly,a first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly, wherein the network device is electrically coupled to the first end connector board, wherein the first network device is configured to communicate with a remote entity.

37. The modular luminaire of claim 36, wherein the first connector system includes the network device.

38. The modular luminaire of claim 36, wherein the network device is located along the body of the lighting assembly external to both the first connector housing and the second connector housing.

39. The modular luminaire of claim 37, wherein the second connector system includes a second network device configured to communicate with the remote entity.

40. A modular luminaire comprising:a lighting assembly having a body with a length;a first connector system;a second connector system; andAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026a network device configured to communicate with a remote entity,whereinthe first connector system includesa first connector housing configured to be removably attached to the body of the lighting assembly,a first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly,the second connector system includesa second connector housing configured to be removably attached to the body of the lighting assembly at a location opposite the first connector housing along the length of the body of the lighting assembly,a second end connector board within the second connector housing, wherein the second end connector board is configured to electrically couple to the lighting assembly, andthe network deviceis at a location along the body of the lighting assembly that is between first connector system and the second connector system, andis in signal communication with the first end connector board, second end connector board, or both.

41. A connector system for a modular luminaire, the connector system comprising: a connector housing configured to be removably attached to a lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; anda network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

42. The connector system of claim 41, wherein the NCD includes a communication device configured to communicate with the network entity.

43. The connector system of claim 42, wherein the communication device includes at least one transceiver that is selected from the group consisting of a wireless fidelity (Wi-Fi)Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026transceiver, Bluetooth transceiver, light fidelity (Li-Fi) transceiver, cellular transceiver, and satellite transceiver.

44. The connector system of claim 43, wherein the cellular transceiver is a cellular repeater or a femtocell.

45. The connector system of claim 43, wherein the satellite transceiver is a satellite repeater or a femtocell.

46. The connector system of claim 43, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

47. The connector system of claim 46, wherein an loT device is a sensor configured to sense environmental conditions of an environment in which the connector system is located.

48. The connector system of claim 43, wherein the Wi-Fi transceiver is configured to communicate with one or more remote devices.

49. The connector system of claim 48, wherein the communication device is configured to operate as a Wi-Fi access point for the one or more remote devices.

50. The connector system of claim 43, wherein the Li-Fi transceiver is configured to communicate with one or more remote devices.

51. The connector system of claim 50, wherein the communication device is configured to operate as a Li-Fi access point for the one or more remote devices.

52. The connector system of claim 43, wherein the cellular transceiver is configured to communicate with one or more remote devices utilizing either a cellular signal repeater or cellular service femtocell.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 202653. The connector system of claim 43, wherein the satellite transceiver is configured to communicate with one or more remote devices utilizing either a satellite signal repeater or satellite service femtocell.

54. The connector system of claim 42, wherein the communication device includes a radio-frequency identification (RFID) device configured to communicate with an RFID card.

55. The connector system of claim 42, wherein the NCD further includes at least one device that is selected from the group consisting of one or more processors, one or more memories, one or more network interfaces, and one or more sensors.

56. The connector system of claim 42, wherein the NCD further includes a universal integrated circuit card (UICC).

57. The connector system of claim 56, wherein the UICC is a smart card.

58. The connector system of claim 57, wherein the smart card includes a subscriber identity module (SIM) card.

59. The connector system of claim 58, wherein the communication device is further configured to communicate with one or more network devices utilizing the SIM card.

60. The connector system of claim 59, whereinthe communication device is a platform-agnostic communication device that is configured to communicate with the one or more network devices utilizing the SIM card, the UICC is configured to store multiple network profiles that include a network profile for the one or more network devices that allows the communication device to communicate with the one or more network devices, andthe one or more network devices includes the network entity, the one or more remote devices, or both.

61. The connector system of claim 60, wherein the UICC is configured to download the multiple network profiles that include network protocols and security frameworks.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 202662. The connector system of claim 41, whereinthe modular luminaire is a light-emitting diode (LED) lamp, andthe connector system is a device that is compliant with a GJ6.6 standard.

63. The connector system of claim 62, wherein the NCD further includes a sensor.

64. The connector system of claim 63, wherein the sensor is an environmental sensor that is a temperature sensor, motion sensor, humidity sensor, sound sensor, light sensor, radiation sensor, gas sensor, or air quality sensor.

65. The connector system of claim 62, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

66. The connector system of claim 65, wherein an loT device is a sensor configured to sense environmental conditions of an environment in which the connector system is located.

67. A smart modular luminaire comprising:a lighting assembly;a connector housing configured to be removably attached to the lighting assembly; an end connector board within the connector housing, wherein the end connector board is in signal communication with the lighting assembly; anda network communication device (NCD) in signal communication with the end connector board, wherein the NCD is configured to communicate with a network entity.

68. The smart modular luminaire of claim 67, wherein the NCD includes a communication device configured to communicate with the network entity.

69. The smart modular luminaire of claim 68, wherein the communication device includes at least one transceiver that is selected from the group consisting of a wireless fidelity (Wi-Fi) transceiver, Bluetooth transceiver, light fidelity (Li-Fi) transceiver, cellular transceiver, and satellite transceiver.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 202670. The smart modular luminaire of claim 69, wherein the communication device is configured to communicate with one or more Internet-of-Things (loT) devices that are remote from the connector system.

71. The smart modular luminaire of claim 70, wherein a loT device is a sensor configured to sense environmental conditions of an environment of which the connector system is located within.

72. The smart modular luminaire of claim 69, wherein the Wi-Fi transceiver is configured to communicate with one or more remote devices.

73. The smart modular luminaire of claim 72, wherein the communication device is configured to operate as a Wi-Fi access point for the one or more remote devices.

74. The smart modular luminaire of claim 69, wherein the Li-Fi transceiver is configured to communicate with one or more remote devices.

75. The smart modular luminaire of claim 74, wherein the communication device is configured to operate as a Li-Fi access point for the one or more remote devices.

76. A modular luminaire comprising:a lighting assembly having a body with a length;a first connector system includinga first connector housing configured to be removably attached to the body of the lighting assembly, anda first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly;a second connector system includinga second connector housing configured to be removably attached to the body of the lighting assembly, anda second end connector board within the second connector housing, wherein the second end connector board is configured to electrically couple to the lighting assembly; andAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026a network device electrically coupled to at least one of the first end connector board or the second end connector board, wherein the network device is configured to communicate with a remote entity.

77. The modular luminaire of claim 76, wherein the first connector system includes the network device.

78. The modular luminaire of claim 76, wherein the network device is located along the body of the lighting assembly external to both the first connector housing and the second connector housing.

79. The modular luminaire of claim 77, wherein the second connector system includes a second network device configured to communicate with the remote entity.

80. A modular luminaire comprising:a lighting assembly having a body with a length;a first connector system;a second connector system; anda network device configured to communicate with a remote entity,whereinthe first connector system includesa first connector housing configured to be removably attached to the body of the lighting assembly,a first end connector board within the first connector housing, wherein the first end connector board is configured to electrically couple to the lighting assembly,the second connector system includesa second connector housing configured to be removably attached to the body of the lighting assembly at a location opposite the first connector housing along the length of the body of the lighting assembly,a second end connector board within the second connector housing, wherein the second end connector board is configured to electrically couple to the lighting assembly, andthe network deviceAttorney Ref. No.: 1817P0005WOefiling Date: February 20, 2026is at a location along the body of the lighting assembly that is between the first connector system and the second connector system, andis in signal communication with the first end connector board, second end connector board, or both.

81. The connector system of claim 80, wherein the end connector board is configured to receive electrical power comprising at least one of alternating current (AC) power or direct current (DC) power.

82. The connector system of claim 41, further comprising power conversion circuitry configured to provide one or more regulated DC voltages for powering at least one of the lighting assembly, the NCD, or one or more sensors.

83. The connector system of claim 80, wherein the connector system includes at least one physical interface selected from the group consisting of an RJ-type connector, a Universal Serial Bus (USB) connector, and an IEEE 1394 connector.

84. The connector system of claim 83, wherein the USB connector is a USB Type-C connector configured to support USB Power Delivery (USB-PD).

85. The connector system of claim 81, wherein the communication device is configured to communicate with the network entity wirelessly without requiring a wired data cable between the connector system and the network entity.

86. The connector system of claim 81, wherein the NCD is configured to operate as at least one of a gateway, router, bridge, repeater, access point, or mesh node between a first network and a second network.

87. The connector system of claim 86, wherein the NCD is configured to participate in a wireless mesh network with one or more other modular luminaires and forward communications between mesh nodes.Attorney Ref. No.: 1817P0005WOefiling Date: February 20, 202688. The connector system of claim 81, wherein the communication device is configured to detect a communication error condition and, in response, automatically perform a corrective action.

89. The connector system of claim 48, wherein the corrective action includes switching from a first communication mode to a second communication mode.

90. The connector system of claim 22, wherein the GJ6.6-compliant device is configured to mate with a lamp holder that provides AC power, DC power, or both.

91. The smart modular luminaire of claim 27, wherein the lighting assembly is powered by at least one of AC power or DC power, and wherein the NCD communicates with the network entity via at least one wireless transceiver.

92. The smart modular luminaire of claim 27, wherein network communications and sensor data transmission are performed via wireless communications while the lighting assembly is powered via AC or DC.

93. The connector system of claim 81, wherein the NCD is configured to be commissioned or provisioned using a mobile device via a short-range wireless interface.

Images