1. An implantable device, comprising:
a metallic device container;
a textured surface on a portion of the metallic device container, having an area root mean square value between 3.05 \u03bcm and 10.2 \u03bcm, wherein the textured surface includes a laser treated surface including a number of substantially spherical particles;
a thermoset polymer header forming an interface with at least a portion of the textured surface, wherein the thermoset polymer is an epoxy and the epoxy header is injection molded in place; and
wherein the thermoset polymer is an epoxy, and the epoxy header is injection molded in place.
2. The implantable device of claim 1, wherein the textured surface has an area root mean square value between 3.81 \u03bcm and 8.89 \u03bcm.
3. The implantable device of claim 1, wherein the textured surface has an area root mean square value between 3.30 \u03bcm and 3.81 \u03bcm.
4. The implantable device of claim 1, wherein the epoxy header has a Shore D hardness between approximately 80 and 90.
5. The implantable device of claim 1, wherein a volume fraction of resin to hardener in the epoxy is approximately 2 to 1.
6. The implantable device of claim 1, wherein the laser treated surface includes a periodic pattern.
7. The implantable device of claim 1, wherein the laser treated surface includes at least one pattern of ridges and troughs.
8. The implantable device of claim 1, wherein the epoxy header is substantially transparent.
9. The implantable device of claim 1, wherein the epoxy header has a glass transition of approximately 70 degrees C.
10. The implantable device of claim 1, wherein, in side load testing, the thermoset polymer header fails in the bulk for a metallic device container thickness between 16 mm and 4 mm.
11. The implantable device of claim 1, wherein, in side load testing, the thermoset polymer header fails in the bulk for a metallic device container thickness between 14 mm and 6 mm.
12. The implantable device of claim 1, wherein, in side load testing, the thermoset polymer header fails in the bulk for a metallic device container thickness between 12 mm and 8 mm.
13. An implantable device, comprising:
a metallic device container;
a textured surface on a portion of the metallic device container, having an area root mean square value between 3.05 \u03bcm and 10.2 \u03bcm, wherein the textured surface includes a laser treated surface including a number of substantially spherical particles; and
a thermoset polymer header forming an interface with at least a portion of the textured surface.
14. The implantable device of claim 13, wherein, in side load testing, the thermoset polymer header fails in the bulk for a metallic device container thickness between 16 mm and 4 mm.
15. The implantable device of claim 13, wherein the textured surface includes at least one pattern of ridges and troughs.
16. An implantable device, comprising:
a metallic device container;
a textured laser treated surface, including a periodic pattern of ridges and troughs, on a portion of the metallic device container, having an area root mean square value between 3.05 \u03bcm and 10.2 \u03bcm, wherein the textured surface includes a laser treated surface including a number of substantially spherical particles; and
a substantially transparent epoxy header forming an interface with at least a portion of the textured surface, wherein the epoxy header is injection molded in place, wherein the epoxy header has a Shore D hardness between approximately 80 and 90, wherein a volume fraction of resin to hardener in the epoxy is approximately 2 to 1, wherein the epoxy header has a glass transition of approximately 70 degrees C., wherein, in side load testing, the epoxy header fails in the bulk for a metallic device container thickness between 16 mm and 4 mm.
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 restoration in a mesh telecommunication network comprising:
sending a label switched path request to a plurality of nodes along a computed restoration path, wherein the label switched path request is sent from a predetermined node in the mesh telecommunication network in response to a determination that a label switched path has been switched to a computer service path;
wherein a plurality of shared resources along the computed restoration path are reserved without allocation; and
wherein the label switched path request is an rsvp-te protocol request comprising a shared reservation flag configured to cause a release of the computed restoration path resource allocation without causing a release of reserved resources associated with the computed restoration path and without causing a removal of the computed restoration path.
2. The method of claim 1, wherein the label switched path request comprises service path information, and wherein the service path information comprises a list of links used along the computer service path.
3. The method of claim 2, wherein the service path information comprises a list of shared risk link groups traversed by the computer service path.
4. The method of claim 1, wherein the label switched path request is an rsvp path message.
5. The method of claim 1, wherein the mesh telecommunication network is an optical network.
6. The method of claim 1, further comprising removing the reservation of shared resources along the computed restoration path responsive to an error message flag indicating that the computed restoration path could not be setup.
7. The method of claim 1, further comprising reserving the resources along the computed restoration path if and only if the label switched path request comprises the shared reservation flag, wherein the shared reservation flag is indicative of whether other flags are needed to support restoration.
8. The method of claim 1, further comprising allocating the shared resources along the computed restoration path.
9. The method of claim 1, wherein the label switched path request comprises a bit flag indicative of whether the label switched path is the computer service path or the computed restoration path.
10. The method of claim 1, wherein the label switched path request comprises a secondary bit indicative that the computed restoration path is a backup path for the computer service path.
11. A method for restoration in a mesh telecommunication network comprising:
halting transmissions along a restoration path and sending a message to a destination node confirming that a restored connection is normalized, wherein the transmissions are halted and the message is sent by a predetermined node in the mesh telecommunication network in response to a confirmation that the destination node has bridged and rolled a service path and the restoration path along the restored connection;
wherein the confirmation is an rsvp-te protocol message comprising an object that comprises a code;
wherein a first possible value of the code is indicative that bridging has been completed;
wherein a second possible value of the code is indicative that a rollbridge has been completed; and
wherein a third possible value of the code is indicative that a roll has been completed.
12. The method of claim 11, wherein the confirmation is an rsvp message.
13. The method of claim 11, further comprising verifying the service path.
14. The method of claim 11, further comprising verifying the service path using link management protocol.
15. A method for restoration in a mesh telecommunication network comprising:
sending a confirmation to a source node confirming that a service path and a restoration path have been bridged and rolled, wherein the confirmation is sent from a predetermined node in the mesh telecommunication network in response to a request to normalize a restored connection;
wherein the restoration path comprises reserved shared resources;
wherein the confirmation is an rsvp-te protocol message comprising an object that comprises a code;
wherein a first possible value of the code is indicative that bridging has been completed;
wherein a second possible value of the code is indicative that a rollbridge has been completed; and
wherein a third possible value of the code is indicative that a roll has been completed.
16. The method of claim 15, wherein the confirmation is an rsvp message.
17. The method of claim 15, further comprising verifying the service path.
18. The method of claim 15, further comprising verifying the service path using link management protocol.
19. The method of claim 15, further comprising resolving a determined label contention associated with normalizing the connection via a downstream label assignment for a uni-directional label switched path.
20. The method of claim 15, further comprising resolving a determined label contention associated with normalizing the connection via a higher node identification label assignment for a bi-directional label switched path.