1461096062-472f754f-360f-4553-a619-efc074bb0715

1. A method for efficiently routing Internet Protocol (IP) traffic on paths between customer edge devices (CEs) across a provider network (\u201cCE-CE paths\u201d) in a computer network, the method comprising:
requesting from a path computation element (PCE), at a multi-homed CE, a set of CE-CE path metrics to one or more remote destination address prefixes;
in response, computing, at the PCE, a set of available CE-CE paths and current metrics to the remote destination address prefixes;
returning the corresponding CE-CE path metrics to the requesting CE; and
utilizing the CE-CE path metrics to load balance, by the requesting CE, IP traffic across links coupled to the requesting CE.
2. The method as in claim 1, further comprising:
learning, at the PCE, dynamic link attribute information of remote links from the provider network to one or more remote CEs.
3. The method as in claim 1, further comprising:
learning, at the PCE, dynamic link attribute information of links of the provider network.
4. The method as in claim 1, further comprising:
modifying IP forwarding entries of the requesting CE accordingly in order to perform IP traffic routing corresponding to the CE-CE path metrics.
5. The method as in claim 4, wherein utilizing the CE-CE path to load balance comprises:
an operation selected from the group comprising: asymmetrically load balancing according to the corresponding CE-CE path metrics; selecting a best path; removing a worst path and load balancing traffic on remaining paths; and removing any paths having CE-CE path metrics configurably worse than a best path and load balancing traffic on remaining paths.
6. The method as in claim 1, further comprising:
specifying the remote destination address prefixes in an access control list (ACL) of a request message.
7. The method as in claim 1, wherein the step of requesting further comprises:
requesting the set of CE-CE path metrics by a Path Computation Element (PCE) Communication Protocol (PCEP) request message.
8. The method as in claim 1, further comprising:
returning corresponding CE-CE path metrics to the requesting CE selected from a group comprising: path costs; utilized bandwidth; link utilization; and weighted values corresponding to path metrics.
9. The method as in claim 1, wherein the step of requesting further comprises:
requesting from the PCE, at the multi-homed CE, a set of CE-CE path metrics to one or more remote destination address prefixes along CE-CE paths that meet a set of requested path attributes.
10. The method as in claim 9, wherein the requested path attributes are selected from a group comprising: a maximum number of paths; diversity; maximum cost; and maximum delay.
11. The method as in claim 9, wherein the corresponding CE-CE path metrics returned to the requesting CE are selected from a group comprising: CE-CE path metrics corresponding to CE-CE paths that meet the set of requested path attributes; CE-CE path metrics corresponding to all CE-CE paths, along with an indication of CE-CE paths that do not meet the set of requested path attributes; and CE-CE path metrics corresponding to all CE-CE paths, along with an indication of corresponding requested path attributes for each of the CE-CE paths.
12. The method as in claim 1, further comprising:
in response to receiving a request from the CE, determining at the PCE whether to process the request based on one or more policies prior to computing the set of available CE-CE paths and current metrics.
13. The method as in claim 12, wherein the one or more policies define rules selected from a group comprising: dampening the requests; allowing requests from selected CEs; allowing requests to selected destination address prefixes; denying requests from selected CEs; and denying requests to selected destination address prefixes.
14. The method as in claim 12, further comprising:
in response to determining at the PCE not to process the request based on one or more policies, performing an action selected from a group comprising: rejecting the request; notifying the requesting CE of one or more policy violations; and ignoring the request.
15. The method as in claim 1, further comprising:
computing, at the PCE, the set of available CE-CE paths and current metrics to the remote destination address prefixes by i) selecting a set of provider edge devices (PEs) having advertised routes to the remote destination address prefixes, and ii) computing a set of best CE-CE paths and respective metrics to each PE of the set.
16. The method as in claim 1, further comprising:
storing, at the PCE, received requests along with corresponding computed CE-CE paths and current metrics;
returning the stored CE-CE path metrics to the requesting CE in the event there are no changes to the CE-CE paths and metrics; and
returning re-computed CE-CE path metrics to the requesting CE in the event there are changes to the CE-CE paths and metrics.
17. The method as in claim 1, further comprising:
requesting, at the requesting CE, that the PCE update the requesting CE of changes to CE-CE path metrics; and
returning re-computed CE-CE path metrics to the requesting CE in the event there are changes to the CE-CE paths and metrics.
18. The method as in claim 1, wherein the step of requesting further comprises:
requesting from the PCE, at the requesting CE, a set of CE-CE path metrics to one or more remote destination address prefixes, the requested set comprising CE-CE path metrics for a single best CE-CE path.
19. The method as in claim 1, wherein the PCE is a provider edge device (PE) locally attached to the requesting CE.
20. The method as in claim 1, wherein the PCE is an ingress PCE, the method further comprising:
requesting from an egress PCE, at the ingress PCE, a set of remote PE-CE path metrics to the remote destination address prefixes;
in response, computing, at the egress PCE, a set of available remote PE-CE paths and current metrics to the remote destination address prefixes; and
returning the corresponding remote PE-CE path metrics to the ingress PCE;
wherein the ingress PCE computes the set of available CE-CE paths and current metrics to the remote destination address prefixes based on the returned remote PE-CE paths and current metrics.
21. A system for efficiently routing Internet Protocol (IP) traffic on paths between customer edge devices (CEs) across a provider network (\u201cCE-CE paths\u201d) in a computer network, the system comprising:
means for requesting from a path computation element (PCE), at a multi-homed CE, a set of CE-CE path metrics to one or more remote destination address prefixes;
in response, means for computing, at the PCE, a set of available CE-CE paths and current metrics to the remote destination address prefixes;
means for returning the corresponding CE-CE path metrics to the requesting CE; and
means for utilizing the CE-CE path metrics to load balance, at the requesting CE, IP traffic across links coupled to the requesting CE.
22. The system as in claim 21, further comprising:
means for learning, at the PCE, dynamic link attribute information of remote links from the provider network to one or more remote CEs.
23. The system as in claim 21, further comprising:
means for modifying IP forwarding entries of the requesting CE accordingly in order to perform IP traffic routing corresponding to the CE-CE path metrics.
24. A computer readable medium containing executable program instructions for efficiently routing Internet Protocol (IP) traffic on paths between customer edge devices (CEs) across a provider network (\u201cCE-CE paths\u201d) in a computer network, the executable program instructions comprising program instructions for:
requesting from a path computation element (PCE), at a multi-homed CE, a set of CE-CE path metrics to one or more remote destination address prefixes;
in response, computing, at the PCE, a set of available CE-CE paths and current metrics to the remote destination address prefixes;
returning the corresponding CE-CE path metrics to the requesting CE; and
utilizing the CE-CE path metrics to load balance, by the requesting CE, IP traffic across links coupled to the requesting CE.
25. The computer readable medium as in claim 24, the executable program instructions further comprising program instructions for:
learning, at the PCE, dynamic link attribute information of remote links from the provider network to one or more remote CEs.
26. The computer readable medium as in claim 24, the executable program instructions further comprising program instructions for:
modifying IP forwarding entries of the requesting CE accordingly in order to perform IP traffic routing corresponding to the CE-CE path metrics.
27. A node adapted to efficiently route Internet Protocol (IP) traffic on paths between customer edge devices (CEs) across a provider network (\u201cCE-CE paths\u201d) in a computer network, the node comprising:
one or more network interfaces;
a processor coupled to the one or more network interfaces and adapted to execute software processes; and
a memory adapted to store a Path Computation Element (PCE) process executable by the processor, the PCE process configured to: i) receive from a multi-homed requesting CE, a request for a set of CE-CE path metrics to one or more remote destination address prefixes, ii) in response, compute a set of available CE-CE paths and current metrics to the remote destination address prefixes, iii) return the corresponding CE-CE path metrics to the requesting CE to allow the requesting CE to load balance IP traffic across links of the requesting CE.
28. The node as in claim 27, the PCE process further configured to:
learn dynamic link attribute information of remote links from the provider network to one or more remote CEs.
29. A node configured to efficiently route Internet Protocol (IP) traffic on paths between customer edge devices (CEs) across a provider network (\u201cCE-CE paths\u201d) in a computer network, the node comprising:
two or more network interfaces, the network interfaced multi-homed to the provider network;
a processor coupled to the network interfaces and adapted to execute software processes; and
a memory adapted to store one or more IP forwarding entries corresponding to the network interfaces, the memory also adapted to store a customer edge device (CE) process executable by the processor, the CE process configured to: i) request from a Path Computation Element (PCE) a set of CE-CE path metrics to one or more remote destination address prefixes, ii) receive from the PCE returned corresponding CE-CE path metrics, and iii) modify IP forwarding entries accordingly in order to load balance IP traffic on the paths corresponding to the CE-CE path metrics.

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 comprising:
receiving a plurality of flows, each flow comprising a plurality of packets, a first flow comprising a plurality of first packets, each first packet having the same source-destination address pair as the other first packets, a second flow comprising a plurality of second packets, each second packet having the same source-destination address pair as the other second packets; and
performing the following for each flow:
identifying a virtual path of a plurality of virtual paths for the each flow, each virtual path having a corresponding path record stored in a memory;
accessing the path record corresponding to the virtual path;
allocating one or more packet buffers to the each flow according to the corresponding path record;

determining, from a priority field of the path record of the virtual path of the first flow, a specific number of packets to send from the virtual path of the first flow before sending any packets from a next virtual path listed on a transmit list of virtual paths with packets pending for transmission, wherein the next virtual path is the virtual path of the second flow, the priority field of the path record designating the specific number;
sending the specific number of first packets before sending any of the second packets;
receiving a next packet;
determining that the next packet is not associated with a path record stored in the memory;
generating a new path record to process the next packet; and
storing the new path record in the memory, wherein if the memory has insufficient space to store the new path record, one or more of the plurality of path records are removed from the memory before storing the new path record.
2. The method of claim 1, further comprising:
receiving a next packet;
identifying a next virtual path of a plurality of virtual paths for the next packet; and
buffering the next packet in the one or more packet buffers allocated to the next virtual path.
3. The method of claim 1, the performing the following for each flow further comprising:
allocating bandwidth to the each flow according to the path record.
4. The method of claim 1, the performing the following for each flow further comprising:
controlling a flow between a plurality of network nodes according to the path record.
5. The method of claim 1, the performing the following for each flow further comprising:
selecting a multicast mode for the each flow according to the path record.
6. The method of claim 1, the performing the following for each flow further comprising:
selecting a snoop mode for the each flow according to the path record.
7. The method of claim 1, further comprising:
receiving a packet of a flow;
determining from the path record of the virtual path of the flow that the virtual path is in a snoop mode; and
sending a copy of the packet to a CPU for processing.
8. The method of claim 1, the performing the following for each flow further comprising:
selecting a priority for the each flow according to the path record.
9. An apparatus comprising:
one or more ports configured to receive a plurality of flows, each flow comprising a plurality of packets, a first flow comprising a plurality of first packets, each first packet having the same source-destination address pair as the other first packets, a second flow comprising a plurality of second packet, each second packet having the same source-destination address pair as the other second packets; and
switch hardware configured to perform the following for each flow:
identify a virtual path of a plurality of virtual paths for the each flow, each virtual path having a corresponding path record stored in a memory;
access the path record corresponding to the virtual path;
allocate one or more packet buffers to the each flow according to the corresponding path record;

determine, from a priority field of the path record of the virtual path of the first flow, a specific number of packets to send from the virtual path of the first flow before sending any packets from a next virtual path listed on a transmit list of virtual paths with packets pending for transmission, wherein the next virtual path is the virtual path of the second flow, the priority field of the path record designating the specific number;
send the specific number of first packets before sending any of the second packets;
receive a next packet;
determine that the next packet is not associated with a path record stored in the memory;
generate a new path record to process the next packet; and
store the new path record in the memory, wherein if the memory has insufficient space to store the new path record, one or more of the plurality of path records are removed from the memory before storing the new path record.
10. The apparatus of claim 9:
the one or more ports configured to:
receive a next packet; and

the switch hardware configured to:
identify a next virtual path of a plurality of virtual paths for the next packet; and
buffer the next packet in the one or more packet buffers allocated to the next virtual path.
11. The apparatus of claim 9, the switch hardware configured to perform the following for each flow:
allocate bandwidth to the each flow according to the path record.
12. The apparatus of claim 9, the switch hardware configured to perform the following for each flow:
control a flow between a plurality of network nodes according to the path record.
13. The apparatus of claim 9, the switch hardware configured to perform the following for each flow:
select a multicast mode for the each flow according to the path record.
14. The apparatus of claim 9, the switch hardware configured to perform the following for each flow:
select a snoop mode for the each flow according to the path record.
15. The apparatus of claim 9:
the one or more ports configured to:
receive a packet of a flow; and

the switch hardware configured to:
determine from the path record of the virtual path of the flow that the virtual path is in a snoop mode; and
send a copy of the packet to a CPU for processing.
16. The apparatus of claim 9, the switch hardware configured to perform the following for each flow:
select a priority for the each flow according to the path record.

1461096049-40130cfb-f372-4e13-86ae-30f5464be551

1. A tracking device for use with a radioactive material comprising: a radiation detector associatable with a radioactive material in that it is adapted to be placed within a container for containing a radioactive material in a radiation shielded enclosed volume, to detect radiation activity from the material in the enclosed volume; a radio frequency identification module associatable with a container for containing a radioactive material in a radiation shielded enclosed volume, which comprises at least: a data register to store a unique product identification code, a processor with a data transfer link to each of the radiation detector and data register to receive and process a live data stream of activity data from the detector and associate this with the unique product identification code in a processed data packet, an antenna to enable transmission of a data item comprising both the unique product identification code and processed activity data to a remote data capture means; wherein at least the antenna is adapted to be placed in mechanical association with a container but outside the radiation-shielded enclosed volume.
2. A tracking device in accordance with claim 1 wherein some or all of the elements other than the antenna constituting the radio frequency identification module are adapted to be placed in mechanical association with a container but outside the radiation-shielded enclosed volume, in use comprising a low-radiation environment.
3. A tracking device in accordance with claim 1 wherein at least the data register, processor and antenna are compactly associated together in a single radio frequency identification unit.
4. A tracking device in accordance with claim 3 wherein the radio frequency identification unit comprises a single integrated solid state electronics unit.
5. A tracking device in accordance with claim 3 wherein the radio frequency identification unit comprises a housing defining attachment means for releasable or permanent attachment of the unit to a container as a radio frequency identification tag.
6. A tracking device in accordance with claim 1 further comprising a power source to power one or more of the identification unit, the processor, the antenna, and the detector.
7. A tracking device in accordance with claim 6 wherein the power source is portable, comprising a battery or a hydrogen fuel cell.
8. A tracking device in accordance with claim 1 wherein the detector comprises a detector element fabricated from a semiconductor material or materials selected to exhibit inherently as a direct material property a direct variable photoelectric response to source radiation.
9. A tracking device in accordance with claim 8 wherein the semiconductor material is a wide direct bandgap semiconductor.
10. A tracking device in accordance with claim 8 wherein the semiconductor material is formed as a bulk single crystal.
11. A tracking device in accordance with claim 8 wherein the materials making up the semiconductor detector element are selected from cadmium telluride, cadmium zinc telluride (CZT), cadmium manganese telluride (CMT), germanium, lanthanum bromide, thorium bromide.
12. A tracking device in accordance with claim 11 wherein the materials making up the semiconductor detector element are selected from cadmium telluride, cadmium zinc telluride (CZT), cadmium manganese telluride (CMT) and alloys thereof.
13. A trackable container for storage and transit of radioactive material comprises:
an enclosure of radioactive shielding material defining a shielded enclosed volume in which a radioactive material may be contained, and
a tracking device in accordance with claim 1 mechanically associated with the container in such mariner that at least the detector is within the shielded enclosed volume, and in such manner that the remainder of the device is in direct mechanical association with the container and that at least the antenna is outside the shielded enclosed volume.
14. A trackable container in accordance with claim 13 wherein at least the data register, processor and antenna are associated with the container outside the contained and shielded volume.
15. A trackable container in accordance with claim 14 wherein the data register, processor andantenna are mounted on a surface of the container or incorporated into the structure thereof.
16. A system for tracking at least one radioactive material source comprising:
at least one radiation-shielded container and tracking device in accordance with claim 13 associated with such a radioactive material source, the container suitable for containing such a radioactive material in an enclosed and radiation-shielded manner;
a radioactive material management system which includes at least one database, the at least one database having a set of electronic data records stored therein providing an associative reference between a unique identification code and an expected radioactive activity behaviour for at least one radioactive material source; data capture means for capturing a data item including the unique product identification code and processed activity data from a tracking device from time to time, and for passing the data to the management system;
wherein the management system is adapted to make use of the unique product identification code thereby received to identify the first set of electronic data records stored in the dataset by association with that code, to make a comparison of the received activity data associated with that unique product identification code and predicted activity data from the database, and to output a result of that comparison as a verification of the radioactive material.
17. A system in accordance with claim 16 comprising a large plurality of tracking devices each associated with a radioactive material source andor with a container suitable for containing such a radioactive material source, each of the data registers of the radio frequency identification modules of each such said device being provided with a unique product identification code.
18. A system in accordance with claim 16 further comprising a plurality of automated and or user-operated data capture units for capturing data from tracking devices at a plurality of remote distributed locations, some or all of the data capture units being remote from the management system, and in remote data communication therewith.
19. A system in accordance with claim 16 wherein the radioactive material management system is adapted to output a verification data result in the form of a two state or passfail result indicating whether the contents of the container associated with the unique product identification code received correspond to the expected activity stored in the database within predetermined tolerance limits.
20. A method of tracking and verification of a plurality of radioactive material sources, over time, the method comprising:
associating a radiation detector with a radioactive material by placing a radiation detector within a container defining a radiation-shielded enclosed volume in which is contained radioactive material;
associating a radio frequency identification module with a radioactive material in data communication with the radiation detector, which module comprises at least a data register to store a unique product identification code, a processor to receive and process a data stream of activity data from the detector and associate this with the unique product identification code, and an antenna, such that at least the antenna is placed in mechanical association with a container but outside the radiation-shielded enclosed volume;
operating the processor to produce a data item comprising both the unique product identification code and processed activity data;
retrieving the data item via a remote data capture means;
passing the data item to a radioactive source management system which includes at least a database having a set of electronic data records stored therein providing an associative reference between a unique identification code and an expected radioactive activity behaviour for each radioisotope source;
for each data item so transmitted, using the unique product identifications code received by the management system to identify the first set of electronic data records stored in a data set by association with that code;
comparing predicted activity data from the database with received activity data within predetermined tolerance limits; and
outputting the result of that comparison as a verification of the radioactive material source.
21. A method in accordance with claim 20 wherein a plurality of tracking devices are provided, each associated with an individual radioactive material source.
22. A method in accordance with claim 20 wherein a plurality of remote data capture means are provided, and data is collected at a plurality of locations.

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. An offset rotary joint unit equipped with a rotation correction mechanism,
wherein one offset rotary joint unit comprises a first arm containing a motor, a rotation correction arm rotationally driven around the axial line of said first arm, and a second arm rotationally driven around an axial line obliquely intersecting with said rotation correction arm,
wherein said first arm and said rotation correction arm are linked via a rotation correction joint mechanism, and said rotation correction arm and said second arm are linked via an offset rotary joint mechanism,
wherein said rotation correction joint mechanism and said offset rotary joint mechanism are both driven with the same drive shaft and the same drive source via a two-shaft reversal mechanism, and
wherein the two-shaft reversal mechanism comprises two shafts driven by the motor in opposite directions.
2. The offset rotary joint unit equipped with a rotation correction mechanism according to claim 1, wherein said rotation correction joint mechanism synchronously rotates in a reverse direction relative to the rotation of said offset rotary joint mechanism, thereby allowing said second arm to execute a two-dimensional bending motion with respect to said first arm without the use of a hinge joint.
3. The offset rotary joint unit equipped with a rotation correction mechanism according to claim 2, wherein said first arm, said rotation correction arm, and said second arm are formed as hollow cylindrical bodies, and joint control units including a motor, an angle encoder, a motor control circuit, and a communication circuit are integrally housed inside said hollow cylindrical bodies.
4. The offset rotary joint unit equipped with a rotation correction mechanism according to claim 3, wherein touch sensors are wound around the entire or a portion of said first arm, said rotation correction arm, and said second arm, and covered with a sheath, touch sensor signal processing circuits are disposed inside these arms, and the contact pressure information detected by said touch sensors is picked up as electric signals and taken into account in controlling said offset rotary joint unit.
5. The offset rotary joint unit equipped with a rotation correction mechanism according to claim 1, wherein said first arm, said rotation correction arm, and said second arm are formed as hollow cylindrical bodies, and joint control units including a motor, an angle encoder, a motor control circuit, and a communication circuit are integrally housed inside said hollow cylindrical bodies.
6. The offset rotary joint unit equipped with a rotation correction mechanism according to claim 1, wherein touch sensors are wound around the entire or a portion of said first arm, said rotation correction arm, and said second arm, and covered with a sheath, touch sensor signal processing circuits are disposed inside these arms, and the contact pressure information detected by said touch sensors is picked up as electric signals and taken into account in controlling said offset rotary joint unit.
7. The offset rotary joint unit equipped with a rotation correction mechanism according to claim 1, wherein bellows are formed on a portion of the hollow cylindrical body of said first arm, said rotation correction arm, or said second arm.
8. The offset rotary joint unit equipped with a rotation correction mechanism according to claim 1, wherein an end of said second arm is parallel to an end of said first arm when in an unrotated position.