Abstract: A method for engaging a donor includes receiving, in a sewer, donor information and donation data for the donor, and sending a first communication to the donor. The first communication may be sent to the donor after completion of a donation and the method may monitor a time period after the donation to determine when a predetermined period of time has passed. The method may then generate and send a second communication to the donor after the passage of the predetermined time period. The second communication may remind the donor of that the donor is eligible to donate again and may include a preferred date and time for the donor to return to donate again. The preferred date and time may be based, at least in part, on heuristic information about the donation center's productivity. The method may also generate/send an additional message requesting a referral from the donor.

Abstract: A method for generating a directive for maintaining an objective includes integrating a control center system with a plurality of healthcare provider data systems and obtaining information from the healthcare provider data system(s). The method may then use artificial intelligence to correlate the obtained information against an identified business objective of a donation center and generate, using a heuristic model, a directive to the donation center(s) to achieve the identified business objective. The method may then present the directive a user and/or user system such that the directive may carried out.

Abstract: A method for remotely obtaining donor information includes identifying a donor after receiving donor specific information from the donor at a remote location and retrieving, at a plasma center, a donor questionnaire based, at least in part, on the donor specific information. The method may then present at least one question from the questionnaire to the donor at the remote location and receive at least one response to question(s) from the donor. Upon receipt of the response(s), the method processes the response(s) at the plasma center and assesses a result of the processed responses to achieve a result assessment based on the at least one response. The assessment may be either a passing assessment or a non-passing assessment. The method may then encode, if the assessment is a passing assessment, the assessment and provide the donor with the encoded assessment.

Abstract: A controller for a blood processing device has a body that may dock and undock with a first blood processing device to connect the controller to the first blood processing device and disconnect the controller from the first blood processing device. A processor within the controller controls the first blood processing device when the controller is docked with the first blood processing device and remotely controls the first blood processing device when undocked. The controller also has a user interface that displays information regarding the first blood processing device and an ongoing apheresis procedure when the controller is docked to the first blood processing device and when the controller is undocked from the first blood processing device.

Abstract: A fleet management system includes apheresis devices and a fleet management device remotely located from and in communication with the apheresis devices. Each apheresis device has a controller, firmware and firmware settings. The fleet management device includes an interface to allow a user to interact with the fleet management device, a server and a processor. The server receives information regarding the firmware/firmware settings of each of the apheresis devices and a firmware file from the user and/or a remote repository. The processor processes the information to determine which of the apheresis devices requires an update to the firmware/firmware settings. The server then distributes the firmware file to each apheresis device that requires the update. The system may also develop a fleet model for one or more donation centers that includes a recommend quantity of devices for the location(s) and/or whether devices should be moved from one location to another.

Abstract: End user on demand network resource instantiation in software-defined networks (SDN) may be provided by an SDN controller that receives an indication from a physical boost device operated by a network user. The boost device may indicate to the SDN controller that an improvement in network performance is desired by the network user. Once the indication is received, the SDN controller may implement network configuration changes for the improvement and cause the network user to be billed for the improvement.

Abstract: A wireless virtual private network (VPN) connection may be automatically instantiated from a wireless VPN client device using a VPN instantiation server. The VPN client device may automatically connect to the VPN instantiation server to obtain client configuration information for a VPN connection to a VPN endpoint server. The VPN instantiation server may instantiate the VPN endpoint server using a network function virtualization (NFV) platform. Then, the VPN client may establish a layer 2 tunnel across a wireless network to the VPN endpoint server.

Abstract: End user on demand network resource instantiation in software-defined networks (SDN) may be provided by an SDN controller that receives an indication from a physical boost device operated by a network user. The boost device may indicate to the SDN controller that an improvement in network performance is desired by the network user. Once the indication is received, the SDN controller may implement network configuration changes for the improvement and cause the network user to be billed for the improvement.

Abstract: Methods for performing dynamic interface identification and configuration are disclosed. The method may include assessing multiple configurable ports of a computing device to determine which ports are active and whether they are client-facing or network-facing. This may include sending a discovery message or a security protocol message to a network target to see if the target responds. The method may be performed by a dynamic interface manager executing on the computing device. The dynamic interface manager may configure a single active network-facing port as the only network interface for the device and may configure other active ports as client interfaces. The dynamic interface manager may enable internal connections between the network interface and the client interfaces. The dynamic interface manager may reassess the ports in response to connection changes, which may result in a different port being configured as the only network interface for the device.

Abstract: A wireless virtual private network (VPN) connection may be automatically instantiated from a wireless VPN client device using a VPN instantiation server. The VPN client device may automatically connect to the VPN instantiation server to obtain client configuration information for a VPN connection to a VPN endpoint server. The VPN instantiation server may instantiate the VPN endpoint server using a network function virtualization (NFV) platform. Then, the VPN client may establish a layer 2 tunnel across a wireless network to the VPN endpoint server.

Abstract: Methods and systems for improved address table flushing in distributed switching systems may be provided. In accordance with embodiments of the disclosure, a switch may include a plurality of line cards and a processor. Each line card may including a table of addresses. The processor may be configured to, in response to receipt of a plurality of simultaneous requests, each request a request to flush addresses associated with a particular flooding domain present on the switch, perform flushing of addresses based on an aggregate number of address entries for each particular flooding domain associated with the requests.

Abstract: A network element includes an ingress interface, a VSP queue, and a switch fabric (SWF). The ingress interface includes a first virtual subport (VSP) and a second VSP. The first VSP is configured to receive data traffic. The VSP queue is coupled to the second VSP such that data traffic transmitted to the VSP queue is transmitted from the network element via the second VSP. The SWF is configured to receive data traffic from the first VSP, determine whether an intended recipient of the data traffic is associated with the second VSP, and hairpin the data traffic to the VSP queue when the SWF determines that the intended recipient is associated with the second VSP.

Abstract: A method may include, by a first network interface: receiving a packet having a flow via a first port of the first network interface; examining the packet to determine an ingress local forwarding identifier (LFID) associated with the flow of the packet; converting the ingress LFID to a global forwarding identifier (GFID) of the network element; and forwarding the packet to a switching element. The method may also include, by the switching element: determining a second network interface for egress of the packet based on the GFID; and forwarding the packet to the second network interface. The method may further include, by the second network interface: converting the GFID to an egress LFID associated with the flow of the packet; and forwarding the packet to a second port of the second network interface and a flow of the second network interface based on the egress LFID.

Abstract: A network processing unit includes a first table, a forwarding table, and a processor. The first table includes a first entry for a network, including a network aging, which includes the network processing unit. The forwarding table includes a second entry associated with a network entity which includes an indication of whether network traffic associated with the entity has been encountered in the current or previous network aging period. The processor is configured to receive an indication from a hardware timer that a hardware aging cycle has ended, and then determine whether the network aging period has ended. If so, the processor is configured to determine for a first network entity in the forwarding table whether traffic associated with the entity has been encountered in the current or previous network aging period. If not, then the processor is configured to remove the given first network entity from the forwarding table.

Abstract: A network element includes an ingress interface, a VSP queue, and a switch fabric (SWF). The ingress interface includes a first virtual subport (VSP) and a second VSP. The first VSP is configured to receive data traffic. The VSP queue is coupled to the second VSP such that data traffic transmitted to the VSP queue is transmitted from the network element via the second VSP. The SWF is configured to receive data traffic from the first VSP, determine whether an intended recipient of the data traffic is associated with the second VSP, and hairpin the data traffic to the VSP queue when the SWF determines that the intended recipient is associated with the second VSP.

Abstract: Methods and systems for improved address table flushing in distributed switching systems may be provided. In accordance with embodiments of the disclosure, a switch may include a plurality of line cards and a processor. Each line card may including a table of addresses. The processor may be configured to, in response to receipt of a plurality of simultaneous requests, each request a request to flush addresses associated with a particular flooding domain present on the switch, perform flushing of addresses based on an aggregate number of address entries for each particular flooding domain associated with the requests.

Abstract: A network processing unit includes a first table, a forwarding table, and a processor. The first table includes a first entry for a network, including a network aging, which includes the network processing unit. The forwarding table includes a second entry associated with a network entity which includes an indication of whether network traffic associated with the entity has been encountered in the current or previous network aging period. The processor is configured to receive an indication from a hardware timer that a hardware aging cycle has ended, and then determine whether the network aging period has ended. If so, the processor is configured to determine for a first network entity in the forwarding table whether traffic associated with the entity has been encountered in the current or previous network aging period. If not, then the processor is configured to remove the given first network entity from the forwarding table.

Abstract: A method may include, by a first network interface: receiving a packet having a flow via a first port of the first network interface; examining the packet to determine an ingress local forwarding identifier (LFID) associated with the flow of the packet; converting the ingress LFID to a global forwarding identifier (GFID) of the network element; and forwarding the packet to a switching element. The method may also include, by the switching element: determining a second network interface for egress of the packet based on the GFID; and forwarding the packet to the second network interface. The method may further include, by the second network interface: converting the GFID to an egress LFID associated with the flow of the packet; and forwarding the packet to a second port of the second network interface and a flow of the second network interface based on the egress LFID.

Abstract: Embodiments provide a cooling device. The cooling device comprises a container configured as a heat sink. The container is at least partially made from heat conducting material. The cooling device further comprises endothermic chemical material which is contained in the container.