Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/20—Administration of product repair or maintenance
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B19/00—Programme-control systems
  • G05B19/02—Programme-control systems electric
  • G05B19/18—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form
  • G05B19/408—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form characterised by data handling or data format, e.g. reading, buffering or conversion of data
  • G05B19/4083—Adapting programme, configuration
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B23/00—Testing or monitoring of control systems or parts thereof
  • G05B23/02—Electric testing or monitoring
  • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
  • G05B23/0218—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults
  • G05B23/0224—Process history based detection method, e.g. whereby history implies the availability of large amounts of data
  • G05B23/0227—Qualitative history assessment, whereby the type of data acted upon, e.g. waveforms, images or patterns, is not relevant, e.g. rule based assessment; if-then decisions
  • G05B23/0232—Qualitative history assessment, whereby the type of data acted upon, e.g. waveforms, images or patterns, is not relevant, e.g. rule based assessment; if-then decisions based on qualitative trend analysis, e.g. system evolution
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
  • G06Q10/063—Operations research, analysis or management
  • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
  • G06Q10/06311—Scheduling, planning or task assignment for a person or group
  • G06Q10/063118—Staff planning in a project environment
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L43/00—Arrangements for monitoring or testing data switching networks
  • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
  • H04L43/0823—Errors, e.g. transmission errors
• • H—ELECTRICITY
  • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
  • H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
  • H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
  • H05B47/20—Responsive to malfunctions or to light source life; for protection
  • H05B47/21—Responsive to malfunctions or to light source life; for protection of two or more light sources connected in parallel
  • H05B47/22—Responsive to malfunctions or to light source life; for protection of two or more light sources connected in parallel with communication between the lamps and a central unit
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B23/00—Testing or monitoring of control systems or parts thereof
  • G05B23/02—Electric testing or monitoring
  • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
  • G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
  • G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols

Definitions

• This application is related to the field of lighting network systems, and more particularly to a system to provide adaptive measure and coordinated maintenance for outdoor lighting systems.
• Outdoor Lighting Networks have been introduced by several companies to enable remote and intelligent management of outdoor lights.
• a conventional outdoor lighting management system 100 may have a two-layer architecture. On the lower layer, light points are grouped into segments. Each segment forms an Outdoor Lighting Network (OLN) 110, 120, 130, which could be based on different
• a Central Management System (CMS) 150 connects to the Segment
• SCs Controllers
• IP networks 140 manages the light points through the SCs.
• the networks connecting the CMS and SCs may be wire-ed, wireless and/or cellular networks.
• the CMS 150 may also manage each light point directly if each light point (i.e., network element) is reachable through cellular networks.
• Remote monitoring is one essential part of the outdoor lighting management to detect or predict failures. This remote monitoring relies on retrieving status
• the networks that relay the measurements from SCs 110.1, 120.1, 130.1, or light points to the CMS 150, become the bottlenecks for the
• the CMS 150 collects one measurement sample of 80 bytes from each light point every 15 minutes, the total traffic is 230.4 MB per month. In practice, this number is usually much higher because of the messaging overhead. Then the annual cost for OLN measurements alone for a small city can be about $5,000 depending on the charges imposed by the (e.g., cellular) network provider.
• maintenance is one of the most common and important operations for outdoor lights in a city.
• maintenance service could be provided by the customer (i.e., the city) or vendors. It could also be provided jointly by both the customer and vendors. For example, the customer may be responsible for cleaning and re-lamping devices while the vendors may maintain the network connectivity.
• the maintenance entities customer, vendors
• lack coordination because of the difficulties in OLN system integration and information sharing.
• a method for managing outside light networks comprising a plurality of network elements.
• the method comprises the steps of identifying attributes of the network elements, grouping corresponding ones of said identified attributes into at least attribute group, collecting attribute data from selected ones of the network elements in each of the at least one attribute group, and determining a status of each attribute of network elements within the at least one attribute group based on the collected attribute data.
• the amount of data collected among the elements within a group is limited by collecting data from selected ones of said network elements by defining a ratio M/N, wherein N is a number of elements in a corresponding attribute group and M is less than N; and for each element within a corresponding attribute group, generating a random number R, wherein R is in the range of 0 and 1 ; and transmitting a corresponding attribute value associated with the element when R ⁇ M/N.
• a system for managing light networks comprising a plurality of network elements, the system comprising a receiving system receiving attribute information, a processor in communication with a memory, the memory including code which when accessed by the processor causes the processor to identify attributes of the network elements, group corresponding ones of said identified attributes into at least attribute group, collect attribute data from selected ones of the network elements in each of the at least one attribute group and determine a status of each attribute of network elements within the at least one attribute group based on the collected attribute data.
• a system comprising a plurality of vendors, each vendor managing a network of a plurality of network elements; the system comprising a receiving system receiving status information from each of the vendors, the information comprising at least selected attributes associated with elements within a corresponding network, monitoring the attribute information among each of the networks, generating at least one work order when a status of a corresponding attribute exceeds a threshold value, and coordinating the at least one work order among the vendors to satisfy said work order.
• FIG 1 illustrates a conventional Command Management System (CMS)
• Figure 2 illustrates an exemplary process in accordance with the principles of the invention.
• Figure 3 illustrates a flow chart of an exemplary process in accordance with principles of the invention.
• Figure 4 illustrate an exemplary message format in accordance with the principles of the invention.
• Figure 5 illustrates an exemplary network configuration wherein different operators individually manage corresponding networks.
• Figure 6 illustrates an exemplary implementation for providing efficient coordination among the different networks and operators.
• FIG. 7 illustrates an exemplary maintenance work flow process in accordance with the principles of the invention.
• FIG. 8 illustrates an exemplary maintenance coordination process in accordance with the principles of the invention.
• reduction in overhead and associated costs may be achieved by reducing the amount of traffic from light points to the CMS, by eliminating the unnecessary measurement samples. For example, if two light points have the same luminaire that are installed within in a short time period, the load currents of two light points could be the same if their luminaires are working on the same dimming level. By using this correlation, samples of current of only one of the two light points may be taken and the single sample may be used for the two light points. The selection of which of the two luminaries samples may be made based on a selection of a fixed one of the two luminaries, on a round-robin basis (i.e., selection of a next luminary) or on a random basis.
• the adaptive sampling method described herein is advantageous as adaptive sampling in outdoor lighting measurement represented correlation in the measurement dependent on the attributes of the lights, which are already available in the management system.
• data compression and/or data aggregation can also be used to reduce the amount of traffic from light points to the CMS. These methods are orthogonal to the method described of the invention herein, and, thus, may be used together to further save measurement cost.
• the proposed method may be applied for collecting measurements for other OLN devices (e.g., temperature or ambient light sensors), the accuracy of the correlations in the sensor readings depends on the outdoor environment, which is hard to predict and quantify. Therefore, this invention focuses on discovering correlations in lighting related measurements.
• FIG. 2 illustrates an exemplary process 200 in accordance with the principles of the invention.
• OLN device or network element attributes are collected and stored in the CMS at block 210.
• Devices having a desired one of the attributes to be monitored are grouped into a corresponding correlation group at block 220.
• a determination is made whether a correlation among the devices within the group indeed exists (i.e., verification). If the correlation does not hold or exist, the correlation group is discarded at block 240. However, if the correlation group is determined to be valid, then the adaptive methods described herein are used to sample elements in the correlation group at block 250.
• FIG. 3 illustrates a flow chart of an exemplary process 300 in accordance with the principles of the invention.
• an OLN device after an OLN device is deployed, its static features are collected at block 310.
• the collection may be performed manually, by installation engineers, or may be performed dynamically by the OLN device initiating a connection to the CMS to register its features (attributes).
• the static features that are collected may include a device type, a device address used by the CMS to identify and communicate with the device, an installation date, a name of the device, a manufacturer, a model number, a serial number, etc., as well as the location of the device.
• These static features i.e., attributes
• the OLN device is incorporated into a group based on the static features or a group of devices may be formed based on the static features of the devices. For example, a group may be formed based on device type and date of installation.
• correlations groups may be formed based on manufacturer, for example.
• dynamic features of the elements or devices within the group are collected.
• the dynamic features or attribute values may be values such as load current, load voltage and output luminance, device temperature, environment temperature, etc.
• a verification of a correlation among the OLN devices or elements of the group is made.
• the OLN devices within each correlation group should have strong correlations in the values of the attribute(s) forming the group.
• a correlation group for load current may be built based on the model and the dimming levels of the luminaires, while a correlation group for load voltage could be built based on the segment of the power grid to which the devices are connected.
• Devices in which a correlation has been determined to not be strong are removed from the group. These removed devices are then group-ed with other similar devices at block 350. The group process repeats until the devices within the network are included in at least one group.
• the OLN devices or elements in the correlation group are then sampled.
• Sampling may be performed using one or more of a plurality of methods. For example, the sampling may randomly chose one or more devices from the group to sample or the samples may be selected from one or more devices in a round-robin manner.
• the sampling may randomly chose one or more devices from the group to sample or the samples may be selected from one or more devices in a round-robin manner.
• a limited number of samples are provided to the CMS that define the characteristics of the group.
• the limited number of samples may also be used to provide further verification of the strong correlation among the elements within the group.
• the sampling may be set up using a schedule wherein given a group of N devices, a sub-set of M devices may be sampled every period P.
• the CMS may send the information regarding (M, N) to the devices in the group.
• each device within the group generates a randomly number R. For example the devices may implement an even distribution in (0, 1).
• the device may then determine whether R ⁇ M/N, or R > M/N. If the device determines that R ⁇ M/N, then the device reports the corresonding attribute to the CMS. Otherwise the device does not report the attribute. In this way, by probability, there will be M out of the N devices in the group that reports its attribute to the CMS. Therefore, for each dynamic attribute to be monitored, an OLN device maintains 3 parameters: M, N and P, which are configured by messages from the CMS.
• the overhead in sampling the attributes of the group is significantly reduced as only M devices of a group of N device is providing attribute data.
• Use of probabilistic method of determining which devices reports corresponding attributes also provides further distribution of the elements providing reports. For example, if three attributes are to be reported, then rather that a select number of devices reporting their three attributes, each of M devices reports the attribute(s) associated with the group. Hence, the combined number of attributes may be received from significantly larger.
• Figure 4 illustrates an exemplary message format for communicating the sampling information from the CMS to the OLN device within the group.
• a request identification is provided at block 410.
• Address information regarding sender and receiver is provided at blocks 420 and 430, respectively.
• a configuration message format is provided and at block 450 the desired attribute is provided.
• the parameters for the sampling (M, N, P) are provided.
• each attribute may be provided at different periods (P), using a different number of devices (M) within the group of N devices.
• each attribute may be provided to the CMS at a different rate and from different devices (M).
• the sampling of the attributes of the OLN device may be spaced during a desired period of time rather than being collected at the start of the desired period of time (i.e., interrogation).
• the method for reducing communication between OLN devices and the CMS described herein is also applicable to the maintenance of the OLN.
• the maintenance entities lack coordination because of the difficulties in OLN system integration and information sharing.
• FIG. 5 illustrates an exemplary network configuration wherein different operators (CMS A, CMS B, CMS C) individually manage corresponding networks OLN A, OLN B and OLN C.
• CMS A, CMS B, CMS C individually manage corresponding networks OLN A, OLN B and OLN C.
• the attributes of each of these networks may be collected as previously discussed with regard to features such as burn hours, current and voltage loading bye each of the individual CMS operators.
• Figure 6 illustrates an exemplary implementation for providing efficient coordination among the different networks and operators.
• CMS 610 is further in communication with the selected ones of the elements in each of networks OLN A, OLN B, OLN C, which are managed by corresponding Vendor Management System VMS A 620, VMS-B 630, VMS-C 640.
• VMS A 620, VMS-B 630, VMS-C 640 As previously discussed group the devices within corresponding OLNs and receives sampled data from the devices within the corresponding OLN.
• CMS 610 may then coordinate the maintenance of the devices with the corresponding network operator (VMS) responsible for the network.
• VMS network operator
• each VMS 620, 630, 640 may also utilize the grouping and sampling methods described herein in order to monitor OLN status and determine need for OLN device maintenance while reducing communication overhead.
• both the CMS 610 and each VMS 620, 630, 640 may receive sample information from a desired number of devices within groups within corresponding networks to determine whether the devices are in need of maintenance or predict when maintenance may be necessary.
• the CMS 610 may, thus, discover attributes of OLN devices, as previously described, and the OLN devices within groups designated by the corresponding VMS may receive status to reports from the CMS 610, as indicated by a provided schedules.
• the VMS 620, 630, 640 may report status to the CMS regarding the OLN devices in corresponding networks.
• the VMS 620, 630, 640 may provide for a higher reporting rate from a higher number devices in a corresponding network, wherein the CMS 610 may provide for a lower reporting rate from a lower number of devices among the networks.
• the VMS 620, 630, 640 and the CMS 610 may then use different projection models to predict potential failures and/or the need to perform maintenance.
• OLN devices To detect or predict abnormalities (e.g., degradation, failures) of devices within the OLNs, collection of attribute values from OLN devices, such as segment controllers, lighting points, luminaires and sensors is required.
• attribute values As previously discussed, Table 1 shows an example of the attributes of light points that are to be collected. These values represent both static and dynamic values of the devices, and does not represent the total range of attributes that may be collected.
• Device Type Indicates the type of device: Light Point.
• CMS Address The unique application layer address used for by the CMS to identify and communicate with the devices.
• Geolocation The geographic information such as longitude and latitude coordinates. May also include street names, and types.
• Dimming Level Zero means the device is off. This can be used to calculate burning hours and then predict the residual lifetime.
• Load Current May be used to detect lamp anomaly behavior.
• Load Voltage May be used to detect lamp anomaly behavior.
• Lamp Temperature The temperature inside the lamp.
• Controller Current May be used to detect controller anomaly behavior.
• Controller Voltage May be used to detect controller anomaly behavior.
• the CMS 610 can establish direct connections to an OLN device to collect its attribute information.
• the CMS 610 may only have access to some of the attributes, while other attributes are only visible to the VMS 620, 630, 640.
• the load current and voltage could be disclosed to the customer, (e.g., CMS) while the controller current and voltage may be protected by the vendor (VMS).
• the CMS may only communicate with OLN devices through the corresponding VMS 620, 630, 640, where the VMS itself acts like an OLN device.
• the VMS may only disclose some of attributes of its associated OLN devices to the CMS 610.
• the VMS 620, 630, 640 needs to configure the visibility of the device attributes. Note that in another embodiment of the invention as shown in Figure 1 , all attributes are collected by the vendor and this visibility
• Attribute visibility may be pre-configured from the factory. It can also be configured during either the commission phase or the operation phase.
• the device can send the list of its attributes to either the VMS 620, 630, 640 by the commissioning tool used by the installation crew. Then the VMS 620, 630, 640 or the commissioning tool will reply to the device with a list of attributes that are allowed to publish to the CMS 610.
• the VMS may dynamically change the visibility of the device attributes by sending enabling or disabling message to the device.
• a device After a device determines the information of the CMS 610 as well as the list of attributes visible to the CMS 610, it may initiate a connection to the CMS 610 to register itself with the published attributes. Also, the device may be manually registered by a commissioning engineer, who uploads the information to the CMS 610. Then the CMS 610 will initiate a connection to the device to confirm the attribute lists.
• the OLN device will send a notification to the CMS 610. If a new attribute becomes visible (e.g., a new type of measurement capability), the OLN device will notify the CMS 610. If the CMS 610 is currently measuring one attribute that is determined to be invisible, the device will also generate an error message.
• a new attribute becomes visible (e.g., a new type of measurement capability)
• the OLN device will notify the CMS 610. If the CMS 610 is currently measuring one attribute that is determined to be invisible, the device will also generate an error message.
• Both the CMS and VSM may request an OLN device to report the status of its attributes, as previously described. If a measurement is required by both the CMS and a VMS, the device may only send it to the VMS 620, 630, 640 and then indicate in the message that this measurement needs to be forwarded to the CMS by the VMS. Since both the CMS 610 and VMSs 620, 630, 640 are typically servers on the internet, this method will save the bottlenecked uplinks from the devices to the servers.
• Device attribute values can not only be used to detect failures, but also to predict failures.
• Both the CMS 610 and VMS 620, 630, 640 could have their own models to detect and predict failures based on the information they collected, and then generate work orders with specific priorities and required crew specialties. For example, with the specified light lifetime and collected burning hour information, the CMS 610 may predict the residual lifetime of the light, which gradually decreases as a function of the burning hours. That is, the CMS 610 or VMS 620, for example, may determine, based on collected information, a trend and predicate when the trend exceeds a threshold value. The threshold value may indicate a failure or close to a failure condition.
• VMS 620, 630, 640 may have access to more information, for example lamp temperature. A VMS 620, 630, 640 may use this information to predict the lighting output performance and decide to replace a lamp if its output falls below a threshold
• the CMS 610 and VMS 620, 630, 640 may coordinate a work flow in providing for the maintenance of the devices within the group and/or network.
• the priority of work orders depends not only on the failure type, but also on the geolocation. If a light point on a major road or an intersection fails, it should have higher priority to be fixed than a light point failure on a rural road.
• the priority of different area types can be derived from standards and regulations. Also, if traffic information is collected through the OLNs, the priority could be set proportional to the amount of traffic.
• Both the CMS 610 and VMS 620, 630, 640 can generate work orders based on the
• Figure 7 illustrates an exemplary work order process 700 in accordance with the principles of the invention.
• the maintenance service is provided by multiple entities (e.g., different vendors, VMS A, VMS B) with their own maintenance crew, then the coordination between the maintenance entities is needed.
• each of vendors VMS A 710 and VMS B 720 may determine characteristics of elements in their corresponding network by taking measurements (or collecting data) 730 of attributes of the network elements as has been described with regard to Figure 3, for example.
• Each of the vendors 710, 720 may further determine abnormalities (or the potential of an abnormality occurring) in the elements of the corresponding network 740, also as previously described, and generate work orders 750.
• information regarding the abnormalities and the work orders may be provided to a CMS unit 770 to coordinate the activities necessary to complete the work orders.
• the CMS unit 770 may also collect data from network elements 775, determine abnormalities 780 and generate work orders 785.
• the CMS 770 may then dispatch crews to correct the abnormality or provide schedules to one or more the VMS 710,720 in order to coordinate the dispatching of crews to timely correct the abnormalities with a high efficiency.
• VMS 710 720 may schedule personnel to be dispatched at an appropriate time.
• Figure 8 illustrates an example process for coordinating the efforts among a plurality of maintenance entities to provide efficient coordination among the entities.
• Each entity has a list of engineers who have their own specialties.
• Each work order has the types and numbers of crew specialties required.
• work order Wl needs two specialties SI and one S2.
• the engineer El, E2 and E3 can be dispatched to work on Wl .
• W2 is independent of Wl
• the engineer E4 can be dispatched to work on W2.
• W3 can only be started when Wl is finished.
• a work order is generated, it is submitted to its designated maintenance entity.
• Each entity may use a scheduling algorithm to schedule its own work orders. Besides, it also maintains a list of its work order and the
• each scheduled work order may have a flexibility time frame, within which it is flexible to be started anytime without affecting the overall work order scheduling.
• work order W2 will have the flexibility to be started any time as long as it can be finished no later than work order Wl.
• Maintenance entities may share their lists of its work orders as well as the status and flexibility time frame through a publish/subscribe manor. For example, each entity may publish the list on its website or an open database, or send new work orders to other entities that have subscribed a specific type of work orders (e.g., within an specific area or with a specific work type).
• Each entity examines its scheduled work orders with scheduled and ongoing work orders from other entities. If the entity finds a potential to coordinate, the entity will initiate a negotiation with the other entity.
• a potential to coordinate could be that two work orders are at very close locations, and their flexibility allows time frames overlap. Then the two work orders could be scheduled to be concurrent so that they can share equipment or reduce the disruption on traffic.
• the above-described methods according to the present invention can be implemented in hardware, firmware or as software or computer code that can be stored in a recording medium such as a CD ROM, an RAM, a floppy disk, a hard disk, or a magneto-optical disk or computer code downloaded over a network originally stored on a remote recording medium or a non-transitory machine readable medium and to be stored on a local recording medium, so that the methods described herein can be rendered in such software that is stored on the recording medium using a general purpose computer(s), or a special processor(s) or in programmable or dedicated hardware(s), such as an ASIC or FPGA.
• microprocessor controller(s) or the programmable hardware(s) include memory components, e.g., RAM, ROM, Flash, etc. that may store or receive software or computer code that when accessed and executed by the computer(s), processor(s) or hardware(s) implement the processing methods described herein.
• memory components e.g., RAM, ROM, Flash, etc.
• processor(s) or hardware(s) implement the processing methods described herein.
• the execution of the code transforms the general purpose computer(s) into a special purpose computer(s) for executing the processing shown herein.

Landscapes

• Business, Economics & Management (AREA)
• Engineering & Computer Science (AREA)
• Human Resources & Organizations (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Strategic Management (AREA)
• Entrepreneurship & Innovation (AREA)
• Economics (AREA)
• General Business, Economics & Management (AREA)
• Operations Research (AREA)
• Theoretical Computer Science (AREA)
• Tourism & Hospitality (AREA)
• Quality & Reliability (AREA)
• Marketing (AREA)
• Automation & Control Theory (AREA)
• Development Economics (AREA)
• Educational Administration (AREA)
• Game Theory and Decision Science (AREA)
• Manufacturing & Machinery (AREA)
• Human Computer Interaction (AREA)
• Signal Processing (AREA)
• Environmental & Geological Engineering (AREA)
• Computer Networks & Wireless Communication (AREA)
• Circuit Arrangement For Electric Light Sources In General (AREA)

Priority Applications (4)

Applications Claiming Priority (2)

Publications (1)

Family

ID=49237540

Family Applications (1)

Country Status (5)

Cited By (3)

Families Citing this family (4)

Citations (6)

Family Cites Families (8)

• 2013
  • 2013-07-10 CN CN201380047096.0A patent/CN104620680B/zh not_active Expired - Fee Related
  • 2013-07-10 JP JP2015521126A patent/JP6422862B2/ja not_active Expired - Fee Related
  • 2013-07-10 US US14/413,728 patent/US20150213415A1/en not_active Abandoned
  • 2013-07-10 EP EP13766686.3A patent/EP2873304B1/en active Active
  • 2013-07-10 WO PCT/IB2013/055652 patent/WO2014009888A1/en not_active Ceased

Patent Citations (6)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events