1. Device for the temperature control of microcomponents (2), in particular microreactors, which preferably has a plate-shaped design and preferably consists of silicon, characterised in that a temperature-control element (15, 20) is provided and in that a flat heat-conducting connection exists between the microcomponent (2) and the temperature-control element (15, 20).
2. Device according to claim 1, characterised in that the temperature-control element is a Peltier element (15).
3. Device according to claim 2, characterised in that a heat exchanger (18, 20), to which a cooling or heating medium can be fed, is arranged on the side of the Peltier element facing away from the microcomponent (2).
4. Device according to claim 3, characterised in that the heat exchanger (18) is formed by an enlarged surface for heat exchange with the ambient air.
5. Device according to claim 4, characterised in that a fan (19) is provided to support the heat exchange.
6. Device according to claim 1, characterised in that the temperature-control element is a heat exchanger (18, 20) to which a cooling or heating medium can be fed.
7. Device according to claim 3, characterised in that the heat exchanger (2) has a hollow design and is provided with line connections (21, 22) for the cooling or heating medium.
8. Device according to one of the preceding claims, characterised in that the heat-exchanging surface of the temperature-control element (18, 20) has essentially the size of the adjacent surface of the microcomponent (2).
9. Device according to one of claims 1 to 7, characterised in that the heat-exchanging surface of the temperature-control element is smaller than the adjacent surface of the microcomponent.
10. Device according to one of the preceding claims, characterised in that the holder (1, 3, 3) has a U-shaped accommodation part for the microcomponent (2) and for the temperature-control element (15), with two arms (5, 6), whose ends can be screwed to a pressure plate (3, 3).
11. Device according to claim 10, characterised in that the pressure plate (3) has a thickened central part (4) which fits between the arms (5, 6) of the U-shaped accommodation part (1).
12. Device according to one of claims 10 and 11, characterised in that an aperture (12) for the accommodation of the temperature-control element (15) is arranged in the region of the U-shaped accommodation part (1) that is opposite the pressure plate (3).
13. Device according to one of claims 10 to 12, characterised in that holes for the accommodation of connecting elements (10) are provided in the pressure plate.
14. Device according to one of claims 10 to 13, characterised in that electrical connections (17) for the temperature-control element (15) are provided on the accommodation part.
15. Device according to one of claims 10 to 14, characterised in that the holder (1, 3, 3) consists of thermally resistant plastic.
16. Device according to one of the preceding claims, characterised in that a plurality of microcomponents (2, 2) are held against one another and in that an outer microcomponent (2) is connected to the temperature-control element (15) in a heat-conducting manner.
17. Device according to claim 16, characterised in that, furthermore, the other outer microcomponent (2) is connected to a further temperature-control element (3) in a heat-conducting manner.
18. Device according to one of claims 16 and 17, characterised in that plates (23) of low thermal conductivity are arranged between adjacent microcomponents.
19. Device according to claim 18, characterised in that the plates have apertures for passing substances between the adjacent microcomponents, which are likewise provided with apertures.
20. Device according to one of the preceding claims, characterised in that at least one sensor for measuring the temperature of at least one microcomponent and which controls at least one regulator of the temperature-control element is provided.
21. Device according to claim 20, characterised in that the at least one sensor (24) is arranged in a groove (25) in a holder (3), which groove is open in the direction of the adjacent microcomponent.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method for a server to calculate access router to access router traffic matrixes by using ingress and egress files derived from flow records, each ingress file comprising a plurality of ingress records in which each ingress record represents an incoming flow, each egress file comprising a plurality of egress records in which each egress record represents an outgoing flow, comprising:
identifying ingress records in the ingress files and egress records in the egress files that match; and
calculating a traffic matrix using the ingress records and egress records that are matched, wherein the calculating the traffic matrix comprises creating a hash set for each egress file, and wherein the identifying and the calculating are performed by the server, wherein the calculating the traffic matrix further comprises:
creating a key value by concatenating source addresses and destination addresses from an egress record;
adding the key value to the hash set; and
creating a second key value by concatenating source addresses and destination addresses from an ingress record.
2. The method of claim 1, wherein the calculating the traffic matrix further comprises performing a test to determine if the second key value for the ingress record exists in a hash set for an egress file.
3. The method of claim 2, wherein the calculating the traffic matrix further comprises annotating an ingress record with indexes of egress routers for a flow record.
4. The method of claim 3 wherein the calculating the traffic matrix further comprises incrementing an egress router count in the ingress record when the ingress record is annotated.
5. The method of claim 4, wherein the calculating the traffic matrix further comprises searching the hash set for every egress file for the second key value for every ingress record.
6. The method of claim 5, wherein the calculating the traffic matrix further comprises calculating traffic matrix elements by processing the ingress records that are annotated.
7. The method of claim 6, wherein the calculating the traffic matrix further comprises identifying specific elements in the traffic matrix using data from an ingress record that is annotated.
8. The method of claim 7, wherein the calculating the traffic matrix further comprises identifying specific elements by an ingress router index, egress router indexes, and a type-of-service.
9. The method of claim 8, wherein the calculating the traffic matrix further comprises adding byte and packet counts from an ingress record that is annotated to the traffic matrix elements.
10. The method of claim 1, wherein the traffic matrix is calculated using non-sampled flow records.
11. The method of claim 10, wherein the traffic matrix is calculated for a virtual private network.
12. A method for a server to calculate access router to access router traffic matrixes by using ingress and egress files derived from flow records, each ingress file comprising a plurality of ingress records in which each ingress record represents an incoming flow, each egress file comprising a plurality of egress records in which each egress record represents an outgoing flow, comprising:
identifying ingress records in the ingress files and egress records in the egress files that match;
calculating a traffic matrix using the ingress records and egress records that are matched, wherein the calculating the traffic matrix comprises creating a hash set for each egress file, and wherein the identifying and the calculating are performed by the server, wherein the traffic matrix is calculated using sampled flow records;
using data from the traffic matrix to compute a distribution matrix;
post-processing the traffic matrix; and
outputting the traffic matrix.
13. The method of claim 12, wherein the post-processing the traffic matrix further comprises determining a total bytes and packets for each row of a plurality of rows of the traffic matrix.
14. The method of claim 13, wherein the post-processing the traffic matrix further comprises dividing the bytes and packets for each element in the traffic matrix by the totals computed for a row containing the element.
15. The method of claim 12, wherein the traffic matrix is calculated for a virtual private network.
16. An apparatus for calculating access router to access router traffic matrixes by using ingress and egress files derived from flow records, each ingress file comprising a plurality of ingress records in which each ingress record represents an incoming flow, each egress file comprising a plurality of egress records in which each egress record represents an outgoing flow, comprising:
a server configured to:
identify ingress records in the ingress files and egress records in the egress files that match; and
calculate a traffic matrix using the ingress records and egress records that are matched, wherein the server is further configured to calculate the traffic matrix by creating a hash set for each egress file, wherein the server is further configured to calculate the traffic matrix by:
creating a key value by concatenating source addresses and destination addresses from an egress record;
adding the key value to the hash set; and
creating a second key value by concatenating source addresses and destination addresses from an ingress record.