A circuit analysis tool is provided, enabled with software instructions, for minimizing circuit crosstalk. The instructions provide a first circuit connected to an output mode, having a last gate with a plurality of inputs and an output. The instructions calculate a first circuit victim net delay range (timing window) having a minimum delay (Vmin) and a maximum delay (Vmax). A second circuit is provided having an output connected to the output node to supply an aggressor net delay range (A1) having a minimum delay (A1min) and a maximum delay (A1max). The aggressor net delay range at least partially overlaps the victim net delay range. Without increasing the value of Vmax (critical path timing), the first circuit victim net delay range is shrunk, thereby minimizing crosstalk between the first and second circuits without an increase in first circuit maximum signal delay.
|
1. A circuit analysis tool, enabled with software instructions stored in a non-transitory computer-readable medium and executed by a processor, for minimizing circuit crosstalk, the instructions comprising:
providing a first circuit connected to an output node having a last gate with a plurality of inputs and an output;
calculating a first circuit victim net delay range having a minimum delay (Vmin) and a maximum delay (Vmax);
providing a second circuit having an output connected to the output node to supply an aggressor net delay range (A1) having a minimum delay (A1min) and a maximum delay (A1max), where the aggressor net delay range at least partially overlaps the victim net delay range;
without increasing the value of Vmax, shrinking the first circuit victim net delay range; and,
minimizing crosstalk between the first and second circuits without an increase in first circuit maximum signal delay.
10. A circuit analysis tool, enabled with software instructions stored in a non-transitory computer-readable medium and executed by a processor, for minimizing circuit crosstalk exposure, the instructions comprising:
providing a first circuit connected to an output node having a last gate with a plurality of inputs and an output;
providing a second circuit having an output connected to the output node to supply an aggressor net delay range (A1) having a minimum delay (A1min) and a maximum delay (A1max), where the aggressor net delay range at least partially overlaps the victim net delay range;
providing a third circuit having the output connected to the output node to supply an aggressor net delay range (A2) at least partially overlapping the victim net delay range and the aggressor net delay range (A1);
calculating a first circuit victim net delay range having a minimum delay (Vmin) and a maximum delay (Vmax);
adding a delay to a circuit selected from a group consisting of the second and third circuits, such that A1 does not overlap A2;
minimizing crosstalk between the first circuit, and the second and third circuits, without an increase in the first circuit maximum signal delay.
2. The instructions of
deriving a range of signal delays (Imin and Imax) for each last gate input (j);
in response to deriving the smallest Imin value and the largest Imax value, calculating the range of signal delays for the gate output;
wherein shrinking the victim net delay range includes:
for each input (j), finding the difference between the largest Imax value and the Ijmax value for that input; and,
adding a circuit delay prior to each gate input, equal to the difference.
3. The instructions of
wherein minimizing the crosstalk includes eliminating crosstalk between the first and second circuits.
4. The instructions of
selecting a margin value; and,
wherein shrinking the victim net delay range further includes finding the difference between Vmax and Vmin; and,
wherein adding the circuit delays prior to each gate input includes adding the circuit delays if the difference is greater than the margin value.
5. The instructions of
the instructions further comprising:
shrinking the second circuit aggressor net delay range (A1) without increasing the value of A1max.
6. The instructions of
calculating the second circuit aggressor net (A1) delay range as follows:
deriving a range of signal delays (Imin and Imax) for each last gate input (j);
in response to deriving the smallest Imin value and the largest Imax value, calculating the range of signal delays for the gate output;
wherein shrinking the second circuit aggressor net de ay range (A1) includes:
for each input (j), finding the difference between the largest Imax value and the Ijmax value for that input; and,
adding a circuit delay prior to each gate input, equal to the difference.
7. The instructions of
providing a third circuit having the output comiected to the output node to supply an aggressor net delay range (A2) at least partially overlapping the victim net delay range and the aggressor net delay range (A1);
adding a delay to a circuit selected from a group consisting of the second and third circuits, such that A1 does not overlap A2.
8. The instructions of
shrinking the aggressor net delay range of a circuit selected from a group consisting of the second circuit, the third circuit, and both the second and third circuits.
9. The instructions of
providing a third circuit having the output comiected to the output node to supply an aggressor net signal delay range (A2) at least partially overlapping the victim net delay range and the aggressor net delay range (A1);
the instructions further comprising:
shrinking the aggressor net delay range of a circuit selected from a group consisting of the second circuit, the third circuit, and both the second and third circuits.
|
1. Field of the Invention
This invention generally relates to signal networking and, more particularly, to a system and method for minimizing the susceptibility of a signal network to aggressor net timing window overlap.
2. Description of the Related Art
The size, complexity, and operating or switching speeds of semiconductor ICs have increased, while feature geometries have decreased, and interconnect systems for such ICs have dramatically increased in complexity. In many situations these factors have increased the possible impact on timing due to noise resulting from parasitic capacitance within the interconnect system.
As noted in Wikipedia, in a synchronous digital system, data is supposed to move in lockstep, advancing one stage on each tick of the clock signal. This is enforced by synchronizing elements such as flip-flops or latches, which copy their input to their output when instructed to do so by the clock. To the first order, only two kinds of timing errors are possible in such a system. First, a hold time violation may occur, when an input signal changes too quickly after the clock's active transition. Second, a setup time violation may occur when a signal arrives too late, and misses the time when it should advance. The time when a signal arrives can vary due to many reasons—the input data may vary, the circuit may perform different operations, the temperature and voltage may change, and there are manufacturing differences in the exact construction of each part.
One approach that is used to analyze the impact of the parasitic capacitances is to model the interconnect system as an arrangement of nets (interconnections between gate outputs and interconnected gate inputs) inter-coupled with parasitic capacitors. Static Timing Analysis (STA) is used to develop early and late arrival times (timing window) for each relevant net or node. This timing window is enlarged by a worst case assessment of crosstalk noise for both early and late arrival times using noise aware STA. This worst case timing window is used for timing analysis of all paths through the corresponding net and a list of paths that fail timing requirements are provided. In static timing analysis, the word static alludes to the fact that this timing analysis is carried out in an input-independent manner, and purports to find the worst-case delay of the circuit over all possible input combinations.
More explicitly, STA is a method of computing the expected timing of a digital circuit without performing a simulation. High-performance ICs have conventionally been characterized by the clock frequency at which they operate. Gauging the operation of a circuit at a specified speed requires an ability to measure, during the design process, its delay at numerous steps. Moreover, delay calculations must be incorporated into the inner loop of timing optimizers at various phases of design, such as logic synthesis, layout (placement and routing), and in in-place optimizations performed late in the design cycle. While such timing measurements can theoretically be performed using a rigorous circuit simulation, such an approach is liable to be too slow to be practical. Static timing analysis plays a vital role in facilitating the fast and reasonably accurate measurement of circuit timing. The main goal of static timing analysis is to verify that despite these possible variations, all signals will arrive neither too early nor too late, and hence proper circuit operation can be assured. Faster design times are a result of using simplified STA delay models, and a limited consideration of the effects of logical interactions between signals.
Also, since STA is capable of verifying every path, apart from helping locate setup and hold time violations, it can detect other serious problems like glitches, slow paths and clock skew. The critical path is defined as the path between an input and an output with the maximum delay. Once the circuit timing has been computed by one of the techniques below, the critical path can easily be found by using a traceback method. The arrival time of a signal is the time elapsed for a signal to arrive at a certain point. The reference, or time 0.0, is often taken as the arrival time of a clock signal. To calculate the arrival time, delay calculation of all the components in the path is required. Arrival times, and indeed almost all times in timing analysis, are normally kept as a pair of values—the earliest possible time at which a signal can change, and the latest.
Required time is the latest time at which a signal can arrive without making the clock cycle longer than desired. The computation of the required time proceeds as follows. At each primary output, the required times for rise/fall are set according to the specifications provided to the circuit. Next, a backward topological traversal is carried out, processing each gate when the required times at all of its fanouts are known. The slack associated with each connection is the difference between the required time and the arrival time. A positive slack (s) at a node implies that the arrival time at that node may be increased by (s) without affecting the overall delay of the circuit. Conversely, negative slack implies that a path is too slow, and the path must be sped up (or the reference signal delayed) if the whole circuit is to work at the desired speed.
The behavior of an electronic circuit is often dependent on various factors in its environment like temperature or local voltage variations. In such a case either STA needs to be performed for more than one such set of conditions, or STA must be prepared to work with a range of possible delays for each component, as opposed to a single value. If the design works at each extreme condition, then under the assumption of monotonic behavior, the design is also qualified for all intermediate points.
The use of corners in static timing analysis has several limitations. It may be overly optimistic, since it assumes perfect tracking—if one gate is fast, all gates are assumed fast, or if the voltage is low for one gate, it's also low for all others. Corners may also be overly pessimistic, for the worst case corner may seldom occur. In an IC, for example, it may not be rare to have one metal layer at the thin or thick end of its allowed range, but it would be very rare for all 10 layers to be at the same limit, since they are manufactured independently. Statistical STA, which replaces delays with distributions, and tracking with correlation, is a more sophisticated approach to the same problem.
The crosstalk effect between any 2 nets depends upon following factors: 1) the coupling capacitance between the aggressor and victim nets; 2) how fast the aggressor and/or the victim nets are switching; and, 3) the timing window overlap of the aggressor and victim nets. The first two factors are addressed by physically increasing the spacing between aggressor and victim nets, thereby reducing the capacitive coupling, and by upsizing/downsizing the driver of aggressor/victim net to change the transition times of the nets. The problem with the above techniques is that they directly involve changing the cells/nets in the timing critical path, which may change the normal timing (timing without crosstalk) of the critical path, and lead to an iterative design process. However, there has been little discussion in the art addressing the third factor—of minimizing the timing window overlap.
It would be advantageous if net crosstalk could be eliminated by shrinking the timing window overlap between aggressor and victim nets.
It would be advantageous if the timing window overlap could be shrunk without affecting the timing critical path of either the victim or aggressor net.
Described herein are a system and design method for reducing the crosstalk noise of coupled nets by addressing the physical design of a system-on-chip (SoC), without relocating or modifying the actual components of the affected nets. The simultaneous switching of the aggressor and victim nets is avoided by changing the timing windows of the nets, while maintaining the timing critical path specifications. Unlike other crosstalk reduction techniques, such as driver upsize of the victim or coupling capacitance reduction, the physical layouts of the affected nets are not modified, so that the original static timing analysis (STA) remains valid, thus avoiding analysis iterations.
Accordingly, a circuit analysis tool is provided, enabled with software instructions, for minimizing circuit crosstalk. The instructions provide a first circuit connected to an output mode, having a last gate with a plurality of inputs and an output. The instructions calculate a first circuit victim net delay range (timing window) having a minimum delay (Vmin) and a maximum delay (Vmax). A second circuit is provided having an output connected to the output node to supply an aggressor net delay range (A1) having a minimum delay (A1min) and a maximum delay (A1max). The aggressor net delay range at least partially overlaps the victim net delay range. Without increasing the value of Vmax (critical path timing), the first circuit victim net delay range is shrunk, thereby minimizing crosstalk between the first and second circuits without an increase in first circuit maximum signal delay.
The first circuit victim net delay range is calculated by deriving a range of signal delays (Imin and Imax) for each last gate input (j). The range of signal delays for the gate output is calculated in response to comparing the gate delay range for each input (j), deriving the smallest Imin value and the largest Imax value. The victim net delay range is shrunk by, for each input (j), finding the difference between the largest Imax value and the Ijmax value for that input. A circuit delay is added prior to each gate input, equal to the difference.
Additional details of the above-described method and a system of hardware devices connected with minimal signal crosstalk are provided below.
A first circuit 310 has a gate 314 with the delay d1, a first plurality of inputs connected to the first delay circuit outputs 306, and an output connected to an output node on line 312. The first circuit 310 has a victim net delay range with a minimum delay (Vmin) and a maximum delay (Vmax).
A second circuit 316 has an output connected to the output node on line 312 to supply the aggressor net delay range (A1) having a minimum delay (A1min) and a maximum delay (A1max). Ideally, the aggressor net delay range fails to overlap the victim net delay range, and Vmin>A1max.
Contrasting
To simplify this example, it is assumed that each output 306 has a discrete delay value, as opposed to a range of values. In this example, output 306a has the smallest Omin value of Pmin, while outputs 306b and 306n both have delays equal to (Pmin+d1), which is the largest Omax value. The delays associated with outputs 306b and 306n are not a problem, since these delays fall out of the aggressor net overlap, once the delay of the first circuit (d1) is added. However, the delay associated with output 306a (Omin=Pmin) would overlap the aggressor net, even after delay d1 is added. The addition of delay (d), associated with delay element 308 shrinks the victim net from (Pmin+d1) to Vmin ((Pmin+d1+d)), and prevents net overlap.
A second delay circuit 604 has a second plurality of inputs connected to the second preliminary circuit outputs 602, a second plurality of outputs 606a to 606p, and at least one delay element 608. Delay element 608 has a delay (Sd), and interposed between an input 602 and an output 606: The second delay circuit 604 has a second shrunken net delay range with a minimum delay (SDmin) and a maximum delay (SDmax), where SDmin=Sd+Smin, and SDmax=Smax. The second circuit 316 has a gate 610 with the delay d2, a second plurality of inputs connected to the second delay circuit outputs 606a through 606p, an output connected to the output node on line 312. The second circuit 316 has an aggressor net delay range with the minimum delay (A1min) greater than Vmax.
The second preliminary circuit 600 has a range of signal delays (Omin and Omax) for each output 602, and the second preliminary circuit delay range is found by contrasting the smallest Omin value and the largest Omax value. The second delay circuit 604 includes a delay element 608 connected to each input 602 with a delay equal to the difference between the largest Omax value and the Omax value for that input. Each input 602 may have a range of delays (Ojmin to Ojmax).
Also shown is a third circuit 612 having an aggressor net delay range (A2), characterized with a timing window A2min-A2max, which partially overlaps the victim net.
However, the shrunken victim net would still overlap aggressor net delay range (A1), if the second delay circuit 604 was not present. The shrinking of aggressor net delay range (A1) is performed in a manner analogous to the shrinking of the victim net. Again, to simplify the example, it is assumed that each output 602 has a discrete delay value, as opposed to a range of values. Output 602b may have the smallest Omin value of 5 min, while outputs 306a and 306p both have delay equal to (Smin+d2), which is the largest Omax value. The delays associated with outputs 602a and 602p are not a problem, since these delays fall out of the victim net overlap, once the delay of the second circuit (d2) is added. However, the delay associated with output 602b (Omin=Smin) would overlap the victim net, even after delay d2 is added. The addition of delay (Sd), associated with delay element 608 shrinks the aggressor net from (Smin+d2) to Vmin ((Pmin+d1+d)), and prevents net overlap.
TABLE 1
Node/net
Timing Window (min:max )
a1
3
ns:3.4 ns
b1
5.1
ns:5.4 ns
x1
3
ns:5.4 ns
a2
4.8
ns:5.4 ns
b2
5.5
ns:6 ns
x2
4.8
ns:6 ns
a3 = x1
3
ns:5.4 ns
b3 = x2
4.8
ns:6 ns
x3/v1
3
ns:6 ns
n1
3
ns:3.6 ns
n2
4
ns:5 ns
Since the timing windows of aggressors n1 and n2 are overlapping with the victim net v1, there is a timing impact in the highlighted timing critical path.
As can be seen from the figure, after delaying node a1 by 2 ns and node a2 by 0.6 ns, the timing window profile of the victim net v1 has shrunk again. Now, the victim net v1 timing window does not overlap the aggressor net n2 timing window. The crosstalk delta delay on net n2 becomes zero and the −200 ps setup slack changes into 0 ps. The timing critical path from flop FF2 1000 to flop FF3 1002 (highlighted in black) has not been delayed, achieving a positive slack. As described above in the explanation of
For example, four aggressor nets (A1, A2, A3, A4) are shown overlapping victim net v. There is a time interval t1-t2 when all the aggressors A1-A4 and V are switching. Since the timing window for all the nets overlap, the crosstalk impact is large. However by adding delay on certain aggressor nets and by optimizing the delay for other aggressor nets, their timing windows are shift towards the negative time axis (the max and min component of the timing window is reduced). The timing windows are shifted in such a manner that the minimum number of aggressor nets (1) switch simultaneously with the victim net v. Thus, the coupling impact of each of these aggressor nets on the victim net v is individual rather than being cumulative, reducing the crosstalk noise impact on the victim net v.
Various steps in the instructions may be referred to as a “component,” “module,” “system,” and the like, and are intended for use with an automated computing system entity, such as hardware, firmware, a combination of hardware and software, software, software stored on a computer-readable medium, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal).
The instructions described herein are stored on a physical memory medium or computer-readable medium. As used herein, the term “computer-readable medium” refers to any medium that participates in providing instructions to a processor for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks. Volatile media includes dynamic memory. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
Although the method performed by the instructions is depicted as a sequence of numbered steps for clarity, the numbering does not necessarily dictate the order of the steps. It should be understood that some of these steps may be skipped, performed in parallel, or performed without the requirement of maintaining a strict order of sequence. Generally however, the steps are performed in numerical order. The instructions start at Step 1600.
Step 1602 provides a first circuit connected to an output mode, having a last gate with a plurality of inputs and an output. Step 1604 calculates a first circuit victim net delay range having a minimum delay (Vmin) and a maximum delay (Vmax). Step 1606 provides a second circuit having an output connected to the output node to supply an aggressor net delay range (A1) having a minimum delay (A1min) and a maximum delay (A1max). The aggressor net delay range at least partially overlaps the victim net delay range. Without increasing the value of Vmax, Step 1608 shrinks the first circuit victim net delay range. Step 1610 minimizes crosstalk between the first and second circuits without an increase in first circuit maximum signal delay. If shrinking the first circuit victim net delay range in Step 1608 includes eliminating the overlap between the victim net delay range and aggressor net delay range, then Step 1610 eliminates crosstalk between the first and second circuits.
In one aspect, calculating the first circuit victim net delay range in Step 1604 includes substeps. Step 1604a derives a range of signal delays (Imin and Imax) for each last gate input (j). In response to deriving the smallest Imin value and the largest Imax value, Step 1604b calculates the range of signal delays for the gate output. Shrinking the victim net delay range in Step 1608 includes the following substeps. For each input (j), Step 1608b finds the difference between the largest Imax value and the Ijmax value for that input. Step 1608c adds a circuit delay prior to each gate input, equal to the difference.
In another aspect, Step 1601 selects a margin value. Then, shrinking the victim net delay range in Step 1608 includes additional substeps. Step 1608a finds the difference between Vmax and Vmin, and Step 1608c adds the circuit delays prior to each gate input if the difference is greater than the margin value.
As noted above in the explanation of
In a different aspect, Step 1607b provides a third circuit having the output connected to the output node to supply an aggressor net delay range (A2) at least partially overlapping the victim net delay range and the aggressor net delay range (A1). Step 1612 adds a delay to either the second or third circuit, such that A1 does not overlap A2. Note: Step 1612 may be performed in parallel with Step 1609, which shrinks the second circuit net delay range (A1), the third circuit net delay range (A2), or both A1 and A2. Alternately, Step 1607b provides a third circuit, and Step 1609 may shrinks the second circuit net delay range (A1), the third circuit net delay range (A2), or both A1 and A2, without the performance of Step 1612.
Systems and methods have been provided for reducing crosstalk between circuit net timing windows. Particular circuit elements and process steps have been used to illustrate the invention, but the invention is not necessarily limited to just these examples. Other variations and embodiments of the invention will occur to those skilled in the art.
Singla, Sunil Kumar, Koul, Sudhir
Patent | Priority | Assignee | Title |
10051078, | Jun 12 2007 | ICONTROL NETWORKS, INC | WiFi-to-serial encapsulation in systems |
10062245, | Mar 30 2010 | iControl Networks, Inc. | Cross-client sensor user interface in an integrated security network |
10062273, | Sep 28 2010 | ICONTROL NETWORKS, INC | Integrated security system with parallel processing architecture |
10078958, | Dec 17 2010 | ICONTROL NETWORKS, INC | Method and system for logging security event data |
10079839, | Jun 12 2007 | ICONTROL NETWORKS, INC | Activation of gateway device |
10091014, | Sep 23 2011 | ICONTROL NETWORKS, INC | Integrated security network with security alarm signaling system |
10127801, | Sep 28 2010 | ICONTROL NETWORKS, INC | Integrated security system with parallel processing architecture |
10127802, | Sep 28 2010 | ICONTROL NETWORKS, INC | Integrated security system with parallel processing architecture |
10140840, | Apr 23 2007 | iControl Networks, Inc. | Method and system for providing alternate network access |
10142166, | Mar 16 2004 | iControl Networks, Inc. | Takeover of security network |
10142392, | Jan 24 2007 | ICONTROL NETWORKS INC ; ICONTROL NETWORKS, INC | Methods and systems for improved system performance |
10142394, | Jun 12 2007 | iControl Networks, Inc. | Generating risk profile using data of home monitoring and security system |
10156831, | Mar 16 2005 | iControl Networks, Inc. | Automation system with mobile interface |
10200504, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols over internet protocol (IP) networks |
10212128, | Jun 12 2007 | ICONTROL NETWORKS, INC | Forming a security network including integrated security system components and network devices |
10223903, | Sep 28 2010 | ICONTROL NETWORKS, INC | Integrated security system with parallel processing architecture |
10225314, | Jan 24 2007 | ICONTROL NETWORKS, INC | Methods and systems for improved system performance |
10237237, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
10237806, | Apr 29 2010 | ICONTROL NETWORKS, INC | Activation of a home automation controller |
10242149, | Dec 17 2014 | International Business Machines Corporation | Enhancing integrated circuit noise performance |
10257364, | Aug 25 2008 | ICONTROL NETWORKS, INC | Security system with networked touchscreen and gateway |
10275999, | Apr 29 2010 | ICONTROL NETWORKS, INC | Server-based notification of alarm event subsequent to communication failure with armed security system |
10277609, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
10313303, | Jun 12 2007 | ICONTROL NETWORKS, INC | Forming a security network including integrated security system components and network devices |
10332363, | Apr 30 2009 | iControl Networks, Inc. | Controller and interface for home security, monitoring and automation having customizable audio alerts for SMA events |
10339791, | Jun 12 2007 | ICONTROL NETWORKS, INC | Security network integrated with premise security system |
10348575, | Jun 27 2013 | ICONTROL NETWORKS, INC | Control system user interface |
10365810, | Jun 27 2013 | ICONTROL NETWORKS, INC | Control system user interface |
10375253, | Aug 25 2008 | ICONTROL NETWORKS, INC | Security system with networked touchscreen and gateway |
10380871, | Mar 16 2005 | ICONTROL NETWORKS, INC | Control system user interface |
10382452, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
10389736, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
10423309, | Jun 12 2007 | iControl Networks, Inc. | Device integration framework |
10444964, | Jun 12 2007 | ICONTROL NETWORKS, INC | Control system user interface |
10447491, | Mar 16 2004 | iControl Networks, Inc. | Premises system management using status signal |
10498830, | Jun 12 2007 | iControl Networks, Inc. | Wi-Fi-to-serial encapsulation in systems |
10522026, | Aug 11 2008 | ICONTROL NETWORKS, INC | Automation system user interface with three-dimensional display |
10523689, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols over internet protocol (IP) networks |
10528698, | Dec 17 2014 | International Business Machines Corporation | Enhancing integrated circuit noise performance |
10528699, | Dec 17 2014 | International Business Machines Corporation | Enhancing integrated circuit noise performance |
10530839, | Aug 11 2008 | ICONTROL NETWORKS, INC | Integrated cloud system with lightweight gateway for premises automation |
10559193, | Feb 01 2002 | Comcast Cable Communications, LLC | Premises management systems |
10616075, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
10616244, | Jun 12 2006 | iControl Networks, Inc. | Activation of gateway device |
10657794, | Mar 26 2010 | ICONTROL NETWORKS, INC | Security, monitoring and automation controller access and use of legacy security control panel information |
10666523, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
10672254, | Apr 23 2007 | iControl Networks, Inc. | Method and system for providing alternate network access |
10674428, | Apr 30 2009 | ICONTROL NETWORKS, INC | Hardware configurable security, monitoring and automation controller having modular communication protocol interfaces |
10691295, | Mar 16 2004 | iControl Networks, Inc. | User interface in a premises network |
10692356, | Mar 16 2004 | iControl Networks, Inc. | Control system user interface |
10721087, | Mar 16 2005 | ICONTROL NETWORKS, INC | Method for networked touchscreen with integrated interfaces |
10735249, | Mar 16 2004 | iControl Networks, Inc. | Management of a security system at a premises |
10741057, | Dec 17 2010 | iControl Networks, Inc. | Method and system for processing security event data |
10747216, | Feb 28 2007 | ICONTROL NETWORKS, INC | Method and system for communicating with and controlling an alarm system from a remote server |
10754304, | Mar 16 2004 | iControl Networks, Inc. | Automation system with mobile interface |
10764248, | Mar 16 2004 | iControl Networks, Inc. | Forming a security network including integrated security system components and network devices |
10785319, | Jun 12 2006 | ICONTROL NETWORKS, INC | IP device discovery systems and methods |
10796557, | Mar 16 2004 | iControl Networks, Inc. | Automation system user interface with three-dimensional display |
10813034, | Apr 30 2009 | ICONTROL NETWORKS, INC | Method, system and apparatus for management of applications for an SMA controller |
10841381, | Mar 16 2005 | iControl Networks, Inc. | Security system with networked touchscreen |
10890881, | Mar 16 2004 | iControl Networks, Inc. | Premises management networking |
10930136, | Mar 16 2005 | iControl Networks, Inc. | Premise management systems and methods |
10942552, | Mar 24 2015 | iControl Networks, Inc. | Integrated security system with parallel processing architecture |
10979389, | Mar 16 2004 | iControl Networks, Inc. | Premises management configuration and control |
10992784, | Mar 16 2004 | ICONTROL NETWORKS, INC | Communication protocols over internet protocol (IP) networks |
10999254, | Mar 16 2005 | iControl Networks, Inc. | System for data routing in networks |
11032242, | Mar 16 2004 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
11043112, | Mar 16 2004 | iControl Networks, Inc. | Integrated security system with parallel processing architecture |
11082395, | Mar 16 2004 | iControl Networks, Inc. | Premises management configuration and control |
11089122, | Jun 12 2007 | ICONTROL NETWORKS, INC | Controlling data routing among networks |
11113950, | Mar 16 2005 | ICONTROL NETWORKS, INC | Gateway integrated with premises security system |
11129084, | Apr 30 2009 | iControl Networks, Inc. | Notification of event subsequent to communication failure with security system |
11132888, | Apr 23 2007 | iControl Networks, Inc. | Method and system for providing alternate network access |
11146637, | Mar 03 2014 | ICONTROL NETWORKS, INC | Media content management |
11153266, | Mar 16 2004 | iControl Networks, Inc. | Gateway registry methods and systems |
11159484, | Mar 16 2004 | iControl Networks, Inc. | Forming a security network including integrated security system components and network devices |
11175793, | Mar 16 2004 | iControl Networks, Inc. | User interface in a premises network |
11182060, | Mar 16 2004 | iControl Networks, Inc. | Networked touchscreen with integrated interfaces |
11184322, | Mar 16 2005 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
11190578, | Aug 11 2008 | ICONTROL NETWORKS, INC | Integrated cloud system with lightweight gateway for premises automation |
11194320, | Feb 28 2007 | iControl Networks, Inc. | Method and system for managing communication connectivity |
11201755, | Mar 16 2004 | iControl Networks, Inc. | Premises system management using status signal |
11212192, | Jun 12 2007 | iControl Networks, Inc. | Communication protocols in integrated systems |
11218878, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
11223998, | Mar 26 2010 | iControl Networks, Inc. | Security, monitoring and automation controller access and use of legacy security control panel information |
11237714, | Jun 12 2007 | Control Networks, Inc. | Control system user interface |
11240059, | Dec 20 2010 | iControl Networks, Inc. | Defining and implementing sensor triggered response rules |
11244545, | Mar 16 2004 | iControl Networks, Inc. | Cross-client sensor user interface in an integrated security network |
11258625, | Aug 11 2008 | ICONTROL NETWORKS, INC | Mobile premises automation platform |
11277465, | Mar 16 2004 | iControl Networks, Inc. | Generating risk profile using data of home monitoring and security system |
11284331, | Apr 29 2010 | ICONTROL NETWORKS, INC | Server-based notification of alarm event subsequent to communication failure with armed security system |
11296950, | Jun 27 2013 | iControl Networks, Inc. | Control system user interface |
11310199, | Mar 16 2004 | iControl Networks, Inc. | Premises management configuration and control |
11316753, | Jun 12 2007 | iControl Networks, Inc. | Communication protocols in integrated systems |
11316958, | Aug 11 2008 | ICONTROL NETWORKS, INC | Virtual device systems and methods |
11341840, | Dec 17 2010 | iControl Networks, Inc. | Method and system for processing security event data |
11343380, | Mar 16 2004 | iControl Networks, Inc. | Premises system automation |
11356926, | Apr 30 2009 | iControl Networks, Inc. | Hardware configurable security, monitoring and automation controller having modular communication protocol interfaces |
11367340, | Mar 16 2005 | iControl Networks, Inc. | Premise management systems and methods |
11368327, | Aug 11 2008 | ICONTROL NETWORKS, INC | Integrated cloud system for premises automation |
11368429, | Mar 16 2004 | iControl Networks, Inc. | Premises management configuration and control |
11378922, | Mar 16 2004 | iControl Networks, Inc. | Automation system with mobile interface |
11398147, | Sep 28 2010 | iControl Networks, Inc. | Method, system and apparatus for automated reporting of account and sensor zone information to a central station |
11405463, | Mar 03 2014 | iControl Networks, Inc. | Media content management |
11410531, | Mar 16 2004 | iControl Networks, Inc. | Automation system user interface with three-dimensional display |
11412027, | Jan 24 2007 | iControl Networks, Inc. | Methods and systems for data communication |
11418518, | Jun 12 2006 | iControl Networks, Inc. | Activation of gateway device |
11418572, | Jan 24 2007 | iControl Networks, Inc. | Methods and systems for improved system performance |
11423756, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
11424980, | Mar 16 2005 | iControl Networks, Inc. | Forming a security network including integrated security system components |
11449012, | Mar 16 2004 | iControl Networks, Inc. | Premises management networking |
11451409, | Mar 16 2005 | iControl Networks, Inc. | Security network integrating security system and network devices |
11489812, | Mar 16 2004 | iControl Networks, Inc. | Forming a security network including integrated security system components and network devices |
11496568, | Mar 16 2005 | iControl Networks, Inc. | Security system with networked touchscreen |
11537186, | Mar 16 2004 | iControl Networks, Inc. | Integrated security system with parallel processing architecture |
11553399, | Apr 30 2009 | iControl Networks, Inc. | Custom content for premises management |
11582065, | Jun 12 2007 | ICONTROL NETWORKS, INC | Systems and methods for device communication |
11588787, | Mar 16 2004 | iControl Networks, Inc. | Premises management configuration and control |
11595364, | Mar 16 2005 | iControl Networks, Inc. | System for data routing in networks |
11601397, | Mar 16 2004 | iControl Networks, Inc. | Premises management configuration and control |
11601810, | Jun 12 2007 | ICONTROL NETWORKS, INC | Communication protocols in integrated systems |
11601865, | Apr 30 2009 | iControl Networks, Inc. | Server-based notification of alarm event subsequent to communication failure with armed security system |
11611568, | Jan 24 2008 | iControl Networks, Inc. | Communication protocols over internet protocol (IP) networks |
11615697, | Mar 16 2005 | iControl Networks, Inc. | Premise management systems and methods |
11616659, | Aug 11 2008 | iControl Networks, Inc. | Integrated cloud system for premises automation |
11625008, | Mar 16 2004 | iControl Networks, Inc. | Premises management networking |
11625161, | Jun 12 2007 | iControl Networks, Inc. | Control system user interface |
11626006, | Mar 16 2004 | iControl Networks, Inc. | Management of a security system at a premises |
11632308, | Jun 12 2007 | iControl Networks, Inc. | Communication protocols in integrated systems |
11641391, | Aug 11 2008 | iControl Networks Inc. | Integrated cloud system with lightweight gateway for premises automation |
11646907, | Jun 12 2007 | iControl Networks, Inc. | Communication protocols in integrated systems |
11656667, | Mar 16 2004 | iControl Networks, Inc. | Integrated security system with parallel processing architecture |
11663902, | Apr 23 2007 | iControl Networks, Inc. | Method and system for providing alternate network access |
11665617, | Apr 30 2009 | iControl Networks, Inc. | Server-based notification of alarm event subsequent to communication failure with armed security system |
11677577, | Mar 16 2004 | iControl Networks, Inc. | Premises system management using status signal |
11700142, | Mar 16 2005 | iControl Networks, Inc. | Security network integrating security system and network devices |
11706045, | Mar 16 2005 | iControl Networks, Inc. | Modular electronic display platform |
11706279, | Jan 24 2007 | iControl Networks, Inc. | Methods and systems for data communication |
11711234, | Aug 11 2008 | iControl Networks, Inc. | Integrated cloud system for premises automation |
11722896, | Jun 12 2007 | iControl Networks, Inc. | Communication protocols in integrated systems |
11729255, | Aug 11 2008 | iControl Networks, Inc. | Integrated cloud system with lightweight gateway for premises automation |
11750414, | Dec 16 2010 | ICONTROL NETWORKS, INC | Bidirectional security sensor communication for a premises security system |
11757834, | Mar 16 2004 | iControl Networks, Inc. | Communication protocols in integrated systems |
11758026, | Aug 11 2008 | iControl Networks, Inc. | Virtual device systems and methods |
11778534, | Apr 30 2009 | iControl Networks, Inc. | Hardware configurable security, monitoring and automation controller having modular communication protocol interfaces |
11782394, | Mar 16 2004 | iControl Networks, Inc. | Automation system with mobile interface |
11792036, | Aug 11 2008 | iControl Networks, Inc. | Mobile premises automation platform |
11792330, | Mar 16 2005 | iControl Networks, Inc. | Communication and automation in a premises management system |
11809174, | Feb 28 2007 | iControl Networks, Inc. | Method and system for managing communication connectivity |
11810445, | Mar 16 2004 | iControl Networks, Inc. | Cross-client sensor user interface in an integrated security network |
11811845, | Mar 16 2004 | iControl Networks, Inc. | Communication protocols over internet protocol (IP) networks |
11815969, | Aug 10 2007 | iControl Networks, Inc. | Integrated security system with parallel processing architecture |
11816323, | Jun 25 2008 | iControl Networks, Inc. | Automation system user interface |
11824675, | Mar 16 2005 | iControl Networks, Inc. | Networked touchscreen with integrated interfaces |
11831462, | Aug 24 2007 | iControl Networks, Inc. | Controlling data routing in premises management systems |
11856502, | Apr 30 2009 | ICONTROL NETWORKS, INC | Method, system and apparatus for automated inventory reporting of security, monitoring and automation hardware and software at customer premises |
11893874, | Mar 16 2004 | iControl Networks, Inc. | Networked touchscreen with integrated interfaces |
11894986, | Jun 12 2007 | iControl Networks, Inc. | Communication protocols in integrated systems |
11900790, | Sep 28 2010 | iControl Networks, Inc. | Method, system and apparatus for automated reporting of account and sensor zone information to a central station |
11916870, | Mar 16 2004 | iControl Networks, Inc. | Gateway registry methods and systems |
11916928, | Jan 24 2008 | iControl Networks, Inc. | Communication protocols over internet protocol (IP) networks |
11943301, | Mar 03 2014 | iControl Networks, Inc. | Media content management |
11962672, | Aug 11 2008 | iControl Networks, Inc. | Virtual device systems and methods |
11991306, | Mar 16 2004 | iControl Networks, Inc. | Premises system automation |
11997584, | Apr 30 2009 | iControl Networks, Inc. | Activation of a home automation controller |
8543954, | Aug 31 2007 | Cadence Design Systems, INC | Concurrent noise and delay modeling of circuit stages for static timing analysis of integrated circuit designs |
8595669, | Aug 31 2007 | Cadence Design Systems, INC | Flexible noise and delay modeling of circuit stages for static timing analysis of integrated circuit designs |
8627254, | Jul 09 2010 | Altera Corporation | Method and apparatus for simultaneous switching noise optimization |
8769470, | Nov 29 2010 | CAVIUM INTERNATIONAL; MARVELL ASIA PTE, LTD | Timing closure in chip design |
9015644, | Aug 06 2012 | Wistron Corp. | Crosstalk analysis method |
9032349, | Aug 06 2012 | Wistron Corp. | Crosstalk analysis method |
9053267, | Dec 22 2011 | Intel Corporation | Noise analysis using timing models |
9092588, | Aug 06 2012 | Wistron Corp. | Crosstalk analysis method |
9129078, | Jul 01 2005 | Cadence Design Systems, Inc. | Static timing analysis of integrated circuit designs with flexible noise and delay models of circuit stages |
ER5799, |
Patent | Priority | Assignee | Title |
6499131, | Jul 15 1999 | Texas Instruments Incorporated | Method for verification of crosstalk noise in a CMOS design |
6637014, | Mar 06 2001 | NEC Corporation | Crosstalk mitigation method and system |
6988255, | Oct 09 2001 | GLOBALFOUNDRIES Inc | Generation of refined switching windows in static timing analysis |
7251797, | Nov 22 2004 | SHENZHEN XINGUODU TECHNOLOGY CO , LTD | Pessimism reduction in crosstalk noise aware static timing analysis |
7359843, | Sep 19 2003 | Cadence Design Systems, INC | Robust calculation of crosstalk delay change in integrated circuit design |
7383522, | Oct 08 2004 | Fujitsu Limited | Crosstalk-aware timing analysis |
7519932, | Apr 07 2005 | Kabushiki Kaisha Toshiba | System and method for analyzing crosstalk occurring in a semiconductor integrated circuit |
20040015338, | |||
20060112359, | |||
20070226673, | |||
20100083202, | |||
20100218152, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Mar 03 2010 | SINGLA, SUNIL | Applied Micro Circuits Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 024037 | /0407 | |
Mar 04 2010 | KOUL, SUDHIR | Applied Micro Circuits Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 024037 | /0407 | |
Mar 05 2010 | Applied Micro Circuits Corporation | (assignment on the face of the patent) | / | |||
Jan 26 2017 | Applied Micro Circuits Corporation | MACOM CONNECTIVITY SOLUTIONS, LLC | MERGER AND CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 042423 | /0700 | |
Jan 26 2017 | MACOM CONNECTIVITY SOLUTIONS, LLC | MACOM CONNECTIVITY SOLUTIONS, LLC | MERGER AND CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 042423 | /0700 | |
May 04 2017 | MACOM CONNECTIVITY SOLUTIONS, LLC SUCCESSOR TO APPLIED MICRO CIRCUITS CORPORATION | GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 042444 | /0891 |
Date | Maintenance Fee Events |
Dec 21 2015 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Apr 21 2017 | ASPN: Payor Number Assigned. |
Feb 10 2020 | REM: Maintenance Fee Reminder Mailed. |
Jul 27 2020 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
Date | Maintenance Schedule |
Jun 19 2015 | 4 years fee payment window open |
Dec 19 2015 | 6 months grace period start (w surcharge) |
Jun 19 2016 | patent expiry (for year 4) |
Jun 19 2018 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jun 19 2019 | 8 years fee payment window open |
Dec 19 2019 | 6 months grace period start (w surcharge) |
Jun 19 2020 | patent expiry (for year 8) |
Jun 19 2022 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jun 19 2023 | 12 years fee payment window open |
Dec 19 2023 | 6 months grace period start (w surcharge) |
Jun 19 2024 | patent expiry (for year 12) |
Jun 19 2026 | 2 years to revive unintentionally abandoned end. (for year 12) |