Abstract: In an embodiment, a lighting management system (102) for managing operation of at least one light source (114) present in an environment is disclosed. The lighting management system comprises at least one sensor (116) configured to sense a lumen value of the at least one light source (114). The system (102) further comprises a controller (118) communicatively coupled to the at least one sensor (116) and a neighbouring control station (106). In an example, the controller (118) is configured to transmit a lumen status message to the neighbouring control station (106), if the sensed lumen value is outside a threshold lumen range. Furthermore, the controller (118) is configured to adjust the lumen value of the at least one light source (114) based on a control message received from the neighbouring control station (106).
DESC:Field of the Invention
The present disclosure relates to a Lighting Management System for managing lights in an environment.
Background
Conventional light management systems typically include a central station that is responsible for controlling the operations of a plurality of light sources, for example, Light Emitting Diode lamps, streetlights, etc., coupled thereto. Typically, the operation of a conventional light management system is static in nature. That is, the central station is configured to switch ON or switch OFF the light sources at predetermined times. For instance, in a street light management system, the central station may be configured to switch ON the streetlights in the evening and switch OFF the streetlights in the morning.
As is known, the light conditions in an environment are dynamic and may vary, for example, due to weather conditions. In such a case, as the conventional light management systems are configured to switch on the light sources at the predetermined time only, an individual may find it difficult to operate in such an environment. In such a case, a person, for example, an admin then has to manually override the system and turn on the light sources. This may prove to be a cumbersome task.
Therefore, there is a need for an improved light management system to address at least one of the aforementioned deficiencies.
Summary
This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the invention. This summary is neither intended to identify key or essential inventive concepts of the invention and nor is it intended for determining the scope of the invention.
In an embodiment, a lighting management system for managing operation of at least one light source present in an environment is disclosed. The lighting management system comprises at least one sensor configured to sense a lumen value of the at least one light source. The lighting management system further comprises a controller communicatively coupled to the at least one sensor and a neighbouring control station. In an example, the controller is configured to transmit a lumen status message to the neighbouring control station, if the sensed lumen value is outside a threshold lumen range. Furthermore, the controller is configured to adjust the lumen value of the at least one light source based on a control message received from the neighbouring control station.
In an embodiment, a method of managing operation of at least one light source present in an environment is disclosed. The method comprises sensing, by at least one light sensor, a lumen value of the at least one light source. The method further comprises transmitting, by a controller, a lumen status message to a neighbouring control station, if the sensed lumen value is outside a threshold lumen range. The method further comprises adjusting, by the controller, the lumen value of the at least one light source based on a control message received from the neighbouring control station.
To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail with the accompanying drawings.
Brief Description of the Drawings
These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
Fig. 1 illustrates a system for managing lights in an environment, according to an embodiment of the present disclosure;
Fig. 2 illustrates an example environment depicting a segment of a smart city where the system for managing lights is implemented, according to various embodiments of the present disclosure; and
Fig. 3 illustrates a method 300 for managing lights in an environment, according to an embodiment of the present disclosure.
Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have been necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.
Detailed Description of Figures
For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skilled in the art to which this invention belongs. The system, methods, and examples provided herein are illustrative only and not intended to be limiting.
The term “some” as used herein is defined as “none, or one, or more than one, or all.” Accordingly, the terms “none,” “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” The term “some embodiments” may refer to no embodiments or to one embodiment or to several embodiments or to all embodiments. Accordingly, the term “some embodiments” is defined as meaning “no embodiment, or one embodiment, or more than one embodiment, or all embodiments.”
The terminology and structure employed herein is for describing, teaching and illuminating some embodiments and their specific features and elements and does not limit, restrict or reduce the spirit and scope of the claims or their equivalents.
More specifically, any terms used herein such as but not limited to “includes,” “comprises,” “has,” “consists,” and grammatical variants thereof do NOT specify an exact limitation or restriction and certainly do NOT exclude the possible addition of one or more features or elements, unless otherwise stated, and furthermore must NOT be taken to exclude the possible removal of one or more of the listed features and elements, unless otherwise stated with the limiting language “MUST comprise” or “NEEDS TO include.”
Whether or not a certain feature or element was limited to being used only once, either way, it may still be referred to as “one or more features” or “one or more elements” or “at least one feature” or “at least one element.” Furthermore, the use of the terms “one or more” or “at least one” feature or element do NOT preclude there being none of that feature or element, unless otherwise specified by limiting language such as “there NEEDS to be one or more . ” or “one or more element is REQUIRED.”
Unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skills in the art.
Reference is made herein to some “embodiments.” It should be understood that an embodiment is an example of a possible implementation of any features and/or elements presented in the attached claims. Some embodiments have been described for the purpose of illuminating one or more of the potential ways in which the specific features and/or elements of the attached claims fulfil the requirements of uniqueness, utility and non-obviousness.
Use of the phrases and/or terms such as but not limited to “a first embodiment,” “a further embodiment,” “an alternate embodiment,” “one embodiment,” “an embodiment,” “multiple embodiments,” “some embodiments,” “other embodiments,” “further embodiment”, “furthermore embodiment”, “additional embodiment” or variants thereof do NOT necessarily refer to the same embodiments. Unless otherwise specified, one or more particular features and/or elements described in connection with one or more embodiments may be found in one embodiment, or may be found in more than one embodiment, or may be found in all embodiments, or may be found in no embodiments. Although one or more features and/or elements may be described herein in the context of only a single embodiment, or alternatively in the context of more than one embodiment, or further alternatively in the context of all embodiments, the features and/or elements may instead be provided separately or in any appropriate combination or not at all. Conversely, any features and/or elements described in the context of separate embodiments may alternatively be realized as existing together in the context of a single embodiment.
Any particular and all details set forth herein are used in the context of some embodiments and therefore should NOT be necessarily taken as limiting factors to the attached claims. The attached claims and their legal equivalents can be realized in the context of embodiments other than the ones used as illustrative examples in the description below.
Embodiments of the present invention will be described below in detail with reference to the accompanying drawings.
Fig. 1 illustrates an environment 100 implementing a lighting management system 102 or simply a system 102, for managing lights in the environment 100, according to an embodiment of the present disclosure. As depicted, the environment 100 includes a plurality of light units 104-1 to 104-N. The plurality of light units 104-1 to 104-N, hereinafter, may collectively be referred to as the light units 104, and each light unit therein may be referred to as the light unit 104. The environment 100 further includes a Neighbouring Control Station (NCS) 106, a Data Concentrator Unit (DCU) 108, a remote station(s) 110, and an analytics centre 112. The NCS 106 may be interchangeably referred to as central control station 106 or CCS 106.
In an example, each of the light units 104 includes a light source(s) 114, a sensor(s) 116, and a controller 118. Examples of the light source 114 may include, but is not limited to, an LED, a Halogen lamp, a CFL lamp, and the like. Examples of the sensor 116 may include, but are not limited to, motion sensor, brightness sensor, and the like. In an example, the controller 118 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the controller 118 is configured to fetch and execute computer-readable instructions and data stored in a memory coupled therewith. In an example, the controller 118 may be provided in a communication device, such as a gateway, or may be a standalone device. Furthermore, a communication module (not shown in the figure) coupled to the controller 118 or integral thereto may also be present.
In an example, the plurality of light units 104 may be interconnected with each other in a manner so as to form a SmartMesh. Accordingly, the light units 104 may exchange their operation data with each other. Furthermore, each of the light units 104 may be communicatively coupled to the NCS 106. Furthermore, at least one of the light units 104 may be communicatively coupled to the DCU 108. As depicted, the NCS 106 and the DCU 108 may be communicatively coupled to the remote station 110 and the analytics centre 112. Without limitation, the communication between the aforementioned entities may be realized using one or more of Zigbee, LoRa, PLC, Wi-Fi, Bluetooth, RF transceivers, GPRS, GPS, 3G, 4G, 5G, WiMAX, and the like.
In an example, the NCS 106 is configured to manage the operations of the light units 104. Accordingly, the NCS 106 is coupled to a database (not shown in the figure) that includes information associated with the light units 104. For instance, the database may include an identity (ID) and a flag status of each of the light units 104. The flag status may include information about an operational state of the light unit 104, i.e., ON or OFF. Further, the flag status includes a control field, wherein the NCS 106 may include control bits to control the operation of the light unit 104. Specifically, in an example, the NCS 106 may include bits for increasing or decreasing the luminosity, associated with the light source 114 of the light unit 104.
In an example, the DCU 108 is configured to receive operation data associated with the light units 104 from at least one of the light units 104. The operation data may include lumen values of the light units 104, their operation timings, and the like. In an example, the DCU 108 may provide the operation data to the remote station 110 and/or analytics centre 112 through the Internet. At the remote station 110, a user, for example, an administrator may view the operation data and accordingly may manage operations of the light units 104. Examples of the remote station 110 may include, but are not limited to, a desktop computer, a workstation computer, a laptop, a smartphone, a server, and the like. In an example, at the analytics centre 112, the operation data of the light unit 104 may be analyzed, for example, using machine learning techniques and artificial intelligence techniques. Based on the analysis, operation patterns of the light units 104 for different time periods may be determined. Accordingly, an anomaly in behaviour of the light units 104 may be easily detected based on the operation patterns.
According to an embodiment of the present disclosure, the system 102 may be implemented in environments, such as smart cities, warehouses, apartment facilities, and the like for managing operation of light sources 114 within the environment 100.
For managing the light sources 114 present in a given environment, in an example, the sensor 116 is configured to sense a lumen value of a light source 114. After sensing the lumen value of the light source 114, the sensor 116 provides or transmits the sensed lumen value to the controller 118.
In an example embodiment, the controller 118 is configured to receive the sensed lumen value of the light source 114 and ascertain if the sensed lumen value is within a threshold lumen range or not. The threshold lumen range may be understood as a range of lumen values determined based on a rated lumen of the light source 114 and an environment lumen value. Herein, the rated lumen value may be understood as a default or pre-set lumen value of the light source 114. The environment lumen value may be understood as a lumen value of the environment of the light unit 104. In an example, the environment lumen may be determined for a radial distance of one meter from the light source 114. As may be understood, the threshold lumen range may vary based on time periods and external factors, such as lights from nearby buildings, lights from the vehicles, light from other light sources, such as make-shift light arrangements done in the environment 100, and the like. Thus, as may be gathered, the threshold lumen range is dynamic. In an implementation, the threshold lumen range for varied time periods and environmental circumstances is stored in the operation data in a storage space (not shown in the figure) coupled with the controller 118.
As mentioned above, the controller 118 is configured to ascertain whether the sensed lumen value of the light source 114 is within the threshold lumen range or not. In an example, where the controller 118 ascertains that the sensed lumen value is within the threshold lumen range, the controller 118 takes no further action. Accordingly, the operation of the light source 114 continues as it is.
In another example, where the controller 118 ascertains that the sensed lumen value is not within the threshold lumen range, the controller 118 transmits a lumen status message to the NCS 106 using the communication module. In an example, the lumen status message includes an identity (ID) associated with the light unit 104, a current location of the light unit 104, and a result of the comparison.
In an example, the sensing of the lumen value of the light source 114 by the sensor 116 and the subsequent comparison of the sensed lumen value with the threshold lumen range by the controller 118 may be performed periodically, say, after every completion of a predetermined period.
On receiving the lumen status message, the NCS 106 updates the location of the light unit 104 in the database based on the ID. In an example, where the location remains unchanged, the updation includes not changing the location. Besides updating the location, the NCS 106 is configured to analyze the result of the comparison. Based on the analysis of the result of the comparison, the NCS 106 is configured to transmit a control message to the controller 118. The control message includes the flag status. As mentioned above, the flag status includes information about the operational state and a field for the control bit.
In an example where the comparison result indicates that the sensed lumen value is less than the threshold range, the NCS 106 includes a control bit “D”, to indicate an action of increasing the lumen of the light source 114 to bring it within the threshold range. In another example where the comparison result indicates that the sensed lumen value is more than the threshold range, the NCS 106 includes a control bit “B”, to indicate an action of decreasing the lumen of the light source 114 to bring it within the threshold range.
On receiving the control message, the controller 118 checks the operational state and the control field. If the operation state matches a current state of the light unit 104, the controller 118 takes no action regarding the operation state of the light unit 104. Regarding the control field, if the control bit therein is set to D, the controller 118 increases the lumen of the light source 114 to bring it within the threshold lumen range. Likewise, when the control bit is set to B, the controller 118 decreases the lumen of the light source 114 to bring it within the threshold lumen range. Thus, operation of the light source 114 is optimized as it is operated at an optimum range of luminosity that is optimum for a set of given environmental circumstances.
In an embodiment, when the lumen value is ascertained to be outside the threshold lumen range, the controller 118 may determine an angle of focus of the light source 114 based on measurements performed by the sensor 116. In said embodiment, the angle of focus is also included in the lumen status message. When the NCS 106 receives the lumen status message, the NCS 106 may analyze the angle of focus as well. In a case where the NCS 106 determines that the angle of focus is to be adjusted, the NCS 106 may include an additional bit related to the adjustment of the angle of focus in the control message. Accordingly, upon receiving the control message including the additional bit, the NCS 106 adjusts the angle of focus of the light source 114 as well. In an example, this may be done in conjunction with the adjustment of the lumen of the light source 114.
In another embodiment, the light unit 104 may include only the light source 114 and the sensor 116. In said embodiment, only a single controller 118 may be provided for the plurality of the light units 104. The single controller 118 may receive the lumen values of each of the light units 104 and may perform the management of the light units 104 based thereon, as described above.
According to an implementation of the present disclosure, the controller 118 of the light unit 104, or simply the controller 118 is configured to provide the lumen status messages corresponding to the plurality of light sources 114, to the NCS 106 after every fixed time interval. As an example, the controller 118 may provide the lumen status messages, say, after every 5 seconds.
In an example, the NCS 106 is configured to provide the operation data associated with the operation of the light units 104 to the remote station 110 and the analytics centre 112. The operation data may include the IDs, the location, and the operation behaviour of the light units 104. Accordingly, as mentioned above, the analytics centre 112 may implement various analytical models to identify the behaviour or the operation pattern of the light units 104.
In an implementation, the analytics centre 112 may detect an anomaly in the operation pattern of a light unit, say light unit 104-1. In said implementation, the analytics centre 112 may provide the ID of the light unit 104-1 to the NCS 106. Based on the ID, the NCS 106 may identify a location of the light unit 104-1 from the database. Accordingly, the NCS 106 may provide an alert notification to the concerned entities, for example, the administrators, local authorities, local in-charge, and the like.
According to an example embodiment of the present subject matter, a motion sensor 116 may be configured to sense vehicular traffic movement in the environment 100 near to the light source 114. The sensed traffic movement is provided to the controller 118 as traffic data. The traffic data includes details of traffic volume. The traffic volume may be understood as number of vehicles crossing a location of the light source 114 in a predefined unit of time. On receiving the traffic data, the controller 118 may be configured to compare the traffic volume with predefined traffic volume threshold. Accordingly, if the controller 118 ascertains that the traffic volume is greater than the threshold, the controller 118 may deduce that the light from the traffic vehicles may cause haphazard shifting of the dynamic threshold lumen range. Accordingly, frequent adjustment of the lumen value of the light source 114 may be caused which may be undesirable. For example, it may lead to battery or power drainage or may result in reduced lumen life.
Thus, to improve the battery life of the power source of the light source 114 and to enhance and increase the life of the light source 114, the controller 118 may be configured to suspend transmission of the lumen status message to the NCS 106. In an example, the controller 118 may be configured to suspend the transmission of the lumen status message to the NCS 106 for a time period for which the traffic volume remains above the threshold traffic volume. In an example, the motion sensor 116 may measure the traffic volume after a fixed time, say after every 1 seconds. Accordingly, in an example, if the controller 118 ascertains that now the traffic volume is less than the threshold traffic volume, the controller 118 resumes transmission of the lumen status message as described above.
Fig. 2 illustrates an example environment 200 depicting a segment of a smart city, where the system 102 may be implemented, according to an embodiment of the present disclosure. As depicted, the environment 200 may include the light units 104, the NCS 106, the DCU 108, the remote station 110, and the analytics centre 112. As further depicted, the environment 200 includes buildings 202 and vehicles 204. As may be further gathered, in the present example implementation, the light units 104 are street lights deployed along a road where the vehicles 204 operate.
As described above in detail in fig. 1, the lumen of the light units 104 may be compared with a threshold lumen range. In the present example implementation, external factors, such as lights from the buildings 202 and lights from the vehicles 204 affect the threshold lumen range. As aspects of the present subject matter provide for a dynamic threshold lumen range, that takes into account the external factors as well, operation of the light units 104 are optimized with greater accuracy. Furthermore, as described above, the anomalies in the operation behaviour of the light unit 104 may be detected. For instance, consider a scenario where owing to certain emergency event, unusual or irregular luminosity is observed in vicinity of the light unit 104. In such a case, the threshold lumen range would alter in an odd manner. In other words, the threshold lumen range would be different than the generally observed the threshold lumen ranges. In such a case, the analytics centre 112 may determine the anomaly and accordingly notify the NCS 106. In turn, the NCS 106 may then transmit alert notifications based on the location of the light unit 104.
Fig. 3 illustrates a method 300 for managing lights in an environment, according to an embodiment of the present disclosure. The description of fig. 3 is in reference to the descriptions of Fig. 1 and Fig. 2, as described above. For the sake of brevity, operational and constructional details of the system 100 are not provided in detail herein.
At step 302, a lumen value of a light source of a light unit is sensed. In an example, the sensor 116 may sense the lumen value of the light source 114 of the light unit 104. At step 304, it is ascertained if the lumen value is within a threshold lumen range or not. In a case where it is ascertained that the lumen value is not within the threshold lumen range, the method 300 proceeds to step 306. At step 306, a lumen status message is transmitted to a central control station. The lumen status message includes an ID of the light unit, a location of the light unit, and a result of the comparison between the lumen value and the threshold lumen range.
At step 308, a control message is configured by the NCS based on the lumen status message. In an example, the control message includes a flag status that indicates an operational state of the light unit and a control field. In a case where the sensed lumen value is less than the threshold lumen range, the control field includes a control bit “D” as explained above. On the other hand, where the sensed lumen value is more than the threshold lumen range, the control field includes a control bit “B” as explained above. At step 310, the control message is transmitted to the controller. At step 312, the lumen of the light source is adjusted by the controller. In a case where the lumen value is less than the threshold lumen range, the lumen value is increased to bring it within the threshold lumen range and vice-versa.
In an example, the method further comprises receiving, at a data concentrator unit, operational data associated with the at least one light source from the controller. The method further comprises transmitting, by the data concentrator unit, the operational data to an analytics centre. Furthermore, the method comprises identifying, by the analytics center, an anomaly in an operation pattern of the at least one light source based on the received operational data. Furthermore, the method comprises transmitting, by the analytics centre, a notification to the neighbouring control station upon identifying the anomaly in an operational pattern of the at least one light source. Furthermore, the method comprises unicasting/broadcast, by the neighbouring control station, an alert notification associated with the anomaly based on a location of the at least one light source.
In an example, the method further comprises measuring, by a motion sensor, a traffic volume at a location of the at least one light source. Furthermore, the method comprises controlling, by the controller, transmission of the lumen status message to the neighbouring control station based on the measured traffic volume and a predefined traffic volume threshold.
As may be gathered from above, aspects of the present disclosure provide for performance optimization and health management of light sources in an environment. Furthermore, system level integration is provided.
For example, regarding performance optimization, the operation data related to the operation of the lights may be gathered and Data clustering/grouping may be done at the analytics centre 112. Subsequently, coordination with the NCS 106 may be done and lumens of the light sources may be regulated and communication with traffic signals may be done.
Furthermore, regarding health management, the life of a light source may be determined based on the operation data that includes the hours of operation, no of cycles of regulation of the brightness, etc.
Additionally, comparison with the historical data may be done to detect for anomalies, predict failures, and initiate inventory management.
Furthermore, the system 102 provides for compatibility with existing system. For instance, the system 102 may be coupled to a traffic management system for vehicle traffic control. As already described, the system may be coupled to a building management system for optimization of lights within the building complex. Furthermore, the location of a building during emergency situations may also be done, for example, through light blinking. Furthermore, automation of the actuation of light sources may be done more accurately based on the pattern of the lights in vicinity. Accordingly, timely adjustments in the lumens of the light sources may also be done.
While specific language has been used to describe the present subject matter, any limitations arising on account thereto, are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein. The drawings and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment.
,CLAIMS:1. A lighting management system (102) for managing operation of at least one light source (114) present in an environment (100), the lighting management system (102) comprising:
at least one sensor (116) configured to sense a lumen value of the at least one light source (114);
a controller (118) communicatively coupled to the at least one sensor (116) and a neighbouring control station (106), wherein the controller (118) is configured to:
transmit a lumen status message to the neighbouring control station (106), if the sensed lumen value is outside a threshold lumen range; and
adjust the lumen value of the at least one light source (114) based on a control message received from the neighbouring control station (106).
2. The system (102) as claimed in claim 1, wherein the controller (118) is further configured to include an identity and a location of the at least one light source (114) in the lumen status message.
3. The system (102) as claimed in claim 1, wherein the control message comprises an operational state and a control bit, wherein the controller (118) is configured to increase the lumen of the at least one light source (114) when the control bit is “D” to make the lumen value within the threshold lumen range.
4. The system (102) as claimed in claim 1, wherein the control message comprises an operational state and a control bit, wherein the controller (118) is configured to decrease the lumen of the at least one light source (114) when the control bit is “B” to make the lumen value within the threshold lumen range.
5. The system (102) as claimed in claim 1, further comprising a data concentrator unit (108) configured to:
receive operational data associated with the at least one light source (114) from the controller (118); and
transmit the operational data to an analytics centre (112).
6. The system (102) as claimed in claim 5, wherein:
the analytics centre (112) is configured to:
identify an anomaly in an operation pattern of the at least one light source (114) based on the received operational data; and
transmit a notification to the neighbouring control station (106) upon identifying the anomaly in an operational pattern of the at least one light source (114); and
the neighbouring control station (106) is configured to unicast/broadcast an alert notification associated with the anomaly based on a location of the at least one light source (114).
7. The system (102) as claimed in claim 1, further comprising a motion sensor (116), wherein:
the motion sensor (116) is configured to measure a traffic volume at a location of the at least one light source (114); and
the controller (118) is configured to control transmission of the lumen status message to the neighbouring control station (106) based on the measured traffic volume and a predefined traffic volume threshold.
8. A method (300) of managing operation of at least one light source (114) present in an environment, the method comprising:
sensing, by at least one light sensor, a lumen value of the at least one light source (114);
transmitting, by a controller (118), a lumen status message to a neighbouring control station (106), if the sensed lumen value is outside a threshold lumen range; and
adjust, by the controller (118), the lumen value of the at least one light source (114) based on a control message received from the neighbouring control station (106).
9. The method (300) as claimed in claim 8, wherein the method further comprises including an identity and a location of the at least one light source (114) in the lumen status message.
10. The method (300) as claimed in claim 8, wherein the control message comprises an operational state and a control bit, wherein the method further comprises increasing the lumen of the at least one light source (114) when the control bit is “D” to make the lumen value within the threshold lumen range.
11. The method (300) as claimed in claim 8, wherein the control message comprises an operational state and a control bit, wherein the method further comprises decreasing the lumen of the at least one light source (114) when the control bit is “B” to make the lumen value within the threshold lumen range.
12. The method (300) as claimed in claim 8, further comprising:
receive, at a data concentrator unit (108), operational data associated with the at least one light source (114) from the controller (118); and
transmit, by the data concentrator unit (108), the operational data to an analytics centre (112).
13. The method (300) as claimed in claim 12, further comprising:
identifying, by the analytics centre (112), an anomaly in an operation pattern of the at least one light source (114) based on the received operational data; and
transmit, by the analytics centre (112), a notification to the neighbouring control station (106) upon identifying the anomaly in an operational pattern of the at least one light source (114); and
unicasting/broadcast, by the neighbouring control station (106), an alert notification associated with the anomaly based on a location of the at least one light source (114).
14. The method (300) as claimed in claim 8, wherein the method further comprises:
measuring, by a motion sensor (116), a traffic volume at a location of the at least one light source (114); and
controlling, by the controller (118), transmission of the lumen status message to the neighbouring control station (106) based on the measured traffic volume and a predefined traffic volume threshold.
| # | Name | Date |
|---|---|---|
| 1 | 201921021147-IntimationOfGrant30-08-2024.pdf | 2024-08-30 |
| 1 | 201921021147-TRANSLATIOIN OF PRIOIRTY DOCUMENTS ETC. [28-05-2019(online)].pdf | 2019-05-28 |
| 2 | 201921021147-STATEMENT OF UNDERTAKING (FORM 3) [28-05-2019(online)].pdf | 2019-05-28 |
| 2 | 201921021147-PatentCertificate30-08-2024.pdf | 2024-08-30 |
| 3 | 201921021147-PROVISIONAL SPECIFICATION [28-05-2019(online)].pdf | 2019-05-28 |
| 3 | 201921021147-CLAIMS [28-05-2024(online)].pdf | 2024-05-28 |
| 4 | 201921021147-FORM 1 [28-05-2019(online)].pdf | 2019-05-28 |
| 4 | 201921021147-COMPLETE SPECIFICATION [28-05-2024(online)].pdf | 2024-05-28 |
| 5 | 201921021147-DRAWINGS [28-05-2019(online)].pdf | 2019-05-28 |
| 5 | 201921021147-DRAWING [28-05-2024(online)].pdf | 2024-05-28 |
| 6 | 201921021147-FER_SER_REPLY [28-05-2024(online)].pdf | 2024-05-28 |
| 6 | 201921021147-DECLARATION OF INVENTORSHIP (FORM 5) [28-05-2019(online)].pdf | 2019-05-28 |
| 7 | 201921021147-Proof of Right (MANDATORY) [17-08-2019(online)].pdf | 2019-08-17 |
| 7 | 201921021147-OTHERS [28-05-2024(online)].pdf | 2024-05-28 |
| 8 | 201921021147-FORM-26 [19-08-2019(online)].pdf | 2019-08-19 |
| 8 | 201921021147-FER.pdf | 2023-11-28 |
| 9 | 201921021147-ORIGINAL UR 6(1A) FORM 1-230819.pdf | 2019-10-28 |
| 9 | 201921021147-FORM 18 [16-05-2023(online)].pdf | 2023-05-16 |
| 10 | 201921021147-DRAWING [26-05-2020(online)].pdf | 2020-05-26 |
| 10 | Abstract1.jpg | 2021-10-19 |
| 11 | 201921021147-COMPLETE SPECIFICATION [26-05-2020(online)].pdf | 2020-05-26 |
| 11 | 201921021147-CORRESPONDENCE-OTHERS [26-05-2020(online)].pdf | 2020-05-26 |
| 12 | 201921021147-COMPLETE SPECIFICATION [26-05-2020(online)].pdf | 2020-05-26 |
| 12 | 201921021147-CORRESPONDENCE-OTHERS [26-05-2020(online)].pdf | 2020-05-26 |
| 13 | 201921021147-DRAWING [26-05-2020(online)].pdf | 2020-05-26 |
| 13 | Abstract1.jpg | 2021-10-19 |
| 14 | 201921021147-FORM 18 [16-05-2023(online)].pdf | 2023-05-16 |
| 14 | 201921021147-ORIGINAL UR 6(1A) FORM 1-230819.pdf | 2019-10-28 |
| 15 | 201921021147-FER.pdf | 2023-11-28 |
| 15 | 201921021147-FORM-26 [19-08-2019(online)].pdf | 2019-08-19 |
| 16 | 201921021147-OTHERS [28-05-2024(online)].pdf | 2024-05-28 |
| 16 | 201921021147-Proof of Right (MANDATORY) [17-08-2019(online)].pdf | 2019-08-17 |
| 17 | 201921021147-DECLARATION OF INVENTORSHIP (FORM 5) [28-05-2019(online)].pdf | 2019-05-28 |
| 17 | 201921021147-FER_SER_REPLY [28-05-2024(online)].pdf | 2024-05-28 |
| 18 | 201921021147-DRAWING [28-05-2024(online)].pdf | 2024-05-28 |
| 18 | 201921021147-DRAWINGS [28-05-2019(online)].pdf | 2019-05-28 |
| 19 | 201921021147-FORM 1 [28-05-2019(online)].pdf | 2019-05-28 |
| 19 | 201921021147-COMPLETE SPECIFICATION [28-05-2024(online)].pdf | 2024-05-28 |
| 20 | 201921021147-PROVISIONAL SPECIFICATION [28-05-2019(online)].pdf | 2019-05-28 |
| 20 | 201921021147-CLAIMS [28-05-2024(online)].pdf | 2024-05-28 |
| 21 | 201921021147-STATEMENT OF UNDERTAKING (FORM 3) [28-05-2019(online)].pdf | 2019-05-28 |
| 21 | 201921021147-PatentCertificate30-08-2024.pdf | 2024-08-30 |
| 22 | 201921021147-TRANSLATIOIN OF PRIOIRTY DOCUMENTS ETC. [28-05-2019(online)].pdf | 2019-05-28 |
| 22 | 201921021147-IntimationOfGrant30-08-2024.pdf | 2024-08-30 |
| 1 | AMDSearchHistory201921021147AE_26-08-2024.pdf |
| 1 | SEARCHSTRATEGY201921021147E_24-11-2023.pdf |
| 2 | AMDSearchHistory201921021147AE_26-08-2024.pdf |
| 2 | SEARCHSTRATEGY201921021147E_24-11-2023.pdf |