Abstract: Provided herein are methods for treatment of cystic fibrosis (CF), including for patients with class I CFTR mutations. The methods may involve administration of a recombinant adeno-associated virus (rAAV) that includes an AV.TL65 capsid protein and a polynucleotide that includes an F5 enhancer and a tg83 promoter operably linked to a CFTR?R minigene, or a pharmaceutical composition thereof.

Abstract: A network element includes at least two Time Division Multiplexing (TDM) modules each including a TDM client interface, TDM processing circuitry, and circuit emulation circuitry; and a packet switch fabric connected to the at least two TDM modules in a Link Aggregation Group (LAG) for a protected TDM service, and configured to output a packet interface, wherein the protected TDM service is provided as a single packetized TDM stream via the packet interface from the packet switch fabric.

Abstract: A network element includes at least two Time Division Multiplexing (TDM) modules each including a TDM client interface, TDM processing circuitry, and circuit emulation circuitry; and a packet switch fabric connected to the at least two TDM modules in a Link Aggregation Group (LAG) for a protected TDM service, and configured to output a packet interface, wherein the protected TDM service is provided as a single packetized TDM stream via the packet interface from the packet switch fabric.

Abstract: A network element includes at least two Time Division Multiplexing (TDM) modules each including a TDM client interface, TDM processing circuitry, and circuit emulation circuitry; and a packet switch fabric connected to the at least two TDM modules and configured to output a packet interface, wherein a protected TDM service through the at least two TDM modules is provided as a single packetized TDM stream via the packet interface from the packet switch fabric.

Abstract: A network element includes at least two Time Division Multiplexing (TDM) modules each including a TDM client interface, TDM processing circuitry, and circuit emulation circuitry; and a packet switch fabric connected to the at least two TDM modules and configured to output a packet interface, wherein a protected TDM service through the at least two TDM modules is provided as a single packetized TDM stream via the packet interface from the packet switch fabric.

Abstract: A method, implemented in a hybrid network element supporting switching at a plurality of layers, for multilayer resource management between the plurality of layers, includes operating a control plane at Layer N between a plurality of network elements in a network, wherein control plane signaling at the Layer N is processed at each network element in a path for a service in the network; and operating a resource management protocol at Layer N+1 with another network element in the network by injecting and extracting messages from and to the control plane into a data path in the Layer N+1, wherein a service at the Layer N+1 operates over the Layer N, and wherein the resource management protocol messages are processed at an originating network element and a terminating network element and not at intermediate network elements in the path.

Abstract: A method, implemented in a hybrid network element supporting switching at a plurality of layers, for multilayer resource management between the plurality of layers, includes operating a control plane at Layer N between a plurality of network elements in a network, wherein control plane signaling at the Layer N is processed at each network element in a path for a service in the network; and operating a resource management protocol at Layer N+1 with another network element in the network by injecting and extracting messages from and to the control plane into a data path in the Layer N+1, wherein a service at the Layer N+1 operates over the Layer N, and wherein the resource management protocol messages are processed at an originating network element and a terminating network element and not at intermediate network elements in the path.

Abstract: Multiple service label types may be used in a given network element to optimize scalability of the data plane, minimize overhead associated with service label management, and allow new services to be offered. Service label management may be done in a dynamic manner so that service labels may be selected for routes in a dynamic fashion as the network changes. VPNs handled by the network element may have different types of service labels, and different routes within a particular VPN may be allocated different service label types. Service label requests may be stored on the data plane to allow a service label request database to be restored from the data plane upon a control plane failure, so that new service labels are not required to be allocated after a control plane failure.

Abstract: Multiple service label types may be used in a given network element to optimize scalability of the data plane, minimize overhead associated with service label management, and allow new services to be offered. Service label management may be done in a dynamic manner so that service labels may be selected for routes in a dynamic fashion as the network changes. VPNs handled by the network element may have different types of service labels, and different routes within a particular VPN may be allocated different service label types. Service label requests may be stored on the data plane to allow a service label request database to be restored from the data plane upon a control plane failure, so that new service labels are not required to be allocated after a control plane failure.

Abstract: Multiple service label types may be used in a given network element to optimize scalability of the data plane, minimize overhead associated with service label management, and allow new services to be offered. Service label management may be done in a dynamic manner so that service labels may be selected for routes in a dynamic fashion as the network changes. VPNs handled by the network element may have different types of service labels, and different routes within a particular VPN may be allocated different service label types. Service label requests may be stored on the data plane to allow a service label request database to be restored from the data plane upon a control plane failure, so that new service labels are not required to be allocated after a control plane failure.

Abstract: A heat dissipation structure with aligned carbon nanotube arrays formed on both sides. The carbon nanotube arrays in between a heat source and a cooler are used as thermal interface material extending and dissipating heat directly from a heat source surface to a cooler surface. In some embodiments, an adhesive material can be used to dispense around carbon nanotube arrays and assemble the heat dissipation structure in between a heat source and a cooler. In some other embodiments, carbon nanotube arrays are formed on at least one of a heat source surface and a cooler surface and connect them together by further growing. The carbon nanotube arrays can be exposed to the environment instead of being in between a heat source and a solid cooler, and can serve as fins to enlarge heat dissipation area and improve thermal convection.

Abstract: A scheme for allowing logical routers to achieve data path efficiency and still maintain network visible virtual links is provided by allowing logical routers in the same physical router to share routing information using standard protocols in place of proprietary route leaking, and by analyzing received data packets to determine if they are tandem data packets or terminating data packets. Tandem data packets are routed directly to egress ports with a single pass through the switch fabric to achieve efficiency, while the TTL value of the packet is decremented twice to maintain the external appearance of the separation of the logical routers. Terminating data packets are routed to other logical routers over virtual links to allow network visibility of the inter-logical router links.

Abstract: Data traffic is conveyed through a node of a communications network. A parameter respecting the data traffic is assigned in an ingress interface of the node, and inserted into an intra-switch header attached to each packet. The data traffic, along with the intra-switch header are forwarded across the node to an egress interface. The parameter is then extracted from the intra-switch header, and used to control processing of the data traffic in the egress interface. The parameter may provide information identifying the source of the data traffic, but may also include other flow-specific information, such as, for example, a normalized DiffServ Code Point. The parameter may be used, in combination with an intra-switch multicast group ID to query one or more translation tables, to thereby enable egress-interface and/or egress port specific replication, forwarding and translation services in respect of the data traffic.

Abstract: A system and method of automatically configuring virtual private networks is provided. The virtual private networks disclosed, include multiple routers selectively connectable to the shared network, such that each of the routers is assigned at least one: shared network address, private network address and virtual private network identifier. Each router includes a controller configured to communicate a router configuration message over the shared network to other members of the same virtual private network. The router configuration message informs the other members of the virtual private network the address of the router and what devices are connected to the router.

Abstract: Upper layer 3 routing in conjunction with self-healing lower layer networks is more informed by the addition of reachability costs determined in the lower layer. Maintenance changes on the self-healing network are monitored. A change causes revision of reachability costs. The revised costs are communicated by lower layer logic to upper layer logic.

Abstract: Data traffic is conveyed through a node of a communications network. A parameter respecting the data traffic is assigned in an ingress interface of the node, and inserted into an intra-switch header attached to each packet. The data traffic, along with the intra-switch header are forwarded across the node to an egress interface. The parameter is then extracted from the intra-switch header, and used to control processing of the data traffic in the egress interface. The parameter may provide information identifying the source of the data traffic, but may also include other flow-specific information, such as, for example, a normalized DiffServ Code Point. The parameter may be used, in combination with an intra-switch multicast group ID to query one or more translation tables, to thereby enable egress-interface and/or egress port specific replication, forwarding and translation services in respect of the data traffic.