Abstract: A server system receives, from a plurality of content providers, including a first content provider and a second content provider, a set of values, each value corresponding to satisfaction of one or more conditions that apply to a state of an electric vehicle charging station (EVCS). The server system receives, from the EVCS, data collected by one or more sensors of the EVCS and determines, using the data, a first state of the EVCS during a first time frame, the first state satisfying a first condition for the first content provider and a second condition for the second content provider. The server system selects, based on values received for the respective conditions that are met by the first state of the EVCS, the first content provider and provides media content associated with the first content provider for display.

Abstract: Systems and methods are provided herein for delivering items using an electric vehicle charging station (EVCS) system. The EVCS system may comprise an EVCS for charge electric vehicles. The EVCS system may also comprise a delivery vehicle removably coupled to the EVCS. The EVCS may have a compartment and/or shelf designed to house the delivery vehicle. Upon receipt of a delivery request, the delivery vehicle departs from the EVCS and transports items (e.g., batteries, charges, purchases, etc.) to one or more users.

Abstract: Provided is an Adaptive Network Security System (“ANSS”) that receives a first set of network data, detects commonality in a set of parameters within the first set of network data using an unsupervised machine learning technique, and models an expected behavior based on the commonality in the set of parameters. The ANSS may determine a threat risk associated with a second set of network data based on an amount of deviation between the set of parameters from the second plurality of network data and the expected behavior, and may perform a particular action from different actions against the second set of network data in response to the set of parameters from the second set of network data deviating from the expected behavior and the threat risk.

Abstract: A method, a device, and a non-transitory storage medium are described in which a network performance optimization service is provided. A load balancer device may receive, from an end device, an application service request for an application service that is available from multiple server devices of an application layer network. The load balancer device may determine, from a source identifier associated with the end device and obtained from the application service request, that the source identifier does not map to a network traffic forwarding rule of a set of stored network traffic forwarding rules. In response, the load balancer device may map the source identifier to an application service profile of a set of stored application service profiles; select, based on the application service profile, a first server device of the multiple server devices and establish the first server device to be the destination of the application service request.

Abstract: A method, a device, and a non-transitory storage medium are described in which a network performance optimization service is provided. A load balancer device may receive, from an end device, an application service request for an application service that is available from multiple server devices of an application layer network. The load balancer device may determine, from a source identifier associated with the end device and obtained from the application service request, that the source identifier does not map to a network traffic forwarding rule of a set of stored network traffic forwarding rules. In response, the load balancer device may map the source identifier to an application service profile of a set of stored application service profiles; select, based on the application service profile, a first server device of the multiple server devices and establish the first server device to be the destination of the application service request.

Abstract: An adaptive congestion control device (“ACCD”) may dynamically optimize network congestion control for different active flows. The ACCD may initiate a first flow that is associated with a first set of flow parameters, may select a first congestion control algorithm from a plurality of congestion control algorithms based on the first set of parameters, and may control transmission of packets for the first flow according to the first congestion control algorithm. While the first flow is active, the ACCD may initiate a second flow that is associated with a different second set of flow parameters, may select a different second congestion control algorithm from the plurality of available congestion control algorithms based on the second set of parameters, and may control transmission of packets for the second flow according to the second congestion control algorithm.

Abstract: An adaptive congestion control device (“ACCD”) may dynamically optimize network congestion control for different active flows. The ACCD may initiate a first flow that is associated with a first set of flow parameters, may select a first congestion control algorithm from a plurality of congestion control algorithms based on the first set of parameters, and may control transmission of packets for the first flow according to the first congestion control algorithm. While the first flow is active, the ACCD may initiate a second flow that is associated with a different second set of flow parameters, may select a different second congestion control algorithm from the plurality of available congestion control algorithms based on the second set of parameters, and may control transmission of packets for the second flow according to the second congestion control algorithm.

Abstract: A controller may identify a problematic path from several paths over which to route egress traffic from a site, may determine a threshold amount of traffic to shift from the problematic path, and may implement different potential traffic shifts for shifting similar amounts of traffic as the threshold amount. The controller may provide the labels or header values that different nodes in the site may place in the egress traffic in order to control which path is used to distributed that egress traffic. The controller may modify routing policies affecting different Autonomous System numbers, address prefixes, or other routing parameters to select and/or shift egress traffic, that is associated with those routing parameters and that is about equal to the threshold amount of traffic, from the problematic path to a different path.

Abstract: A controller may identify a problematic path from several paths over which to route egress traffic from a site, may determine a threshold amount of traffic to shift from the problematic path, and may implement different potential traffic shifts for shifting similar amounts of traffic as the threshold amount. The controller may provide the labels or header values that different nodes in the site may place in the egress traffic in order to control which path is used to distributed that egress traffic. The controller may modify routing policies affecting different Autonomous System numbers, address prefixes, or other routing parameters to select and/or shift egress traffic, that is associated with those routing parameters and that is about equal to the threshold amount of traffic, from the problematic path to a different path.

Abstract: An actuator rotational limiter mechanism for a multiple disk-stack, shared actuator hard disk drive includes an actuator comb with a protruding pin, whereby rotation of the actuator comb is limited by an attraction between the pin and a magnet. An enclosure base may include a curved slot in which the pin is disposed, where one end of the slot may correspond to the head slider being near the inner diameter of a first disk stack and the other end of the slot may correspond to the head slider being near the inner diameter of a second disk stack adjacent to the first disk stack. The magnet may be disposed within or adjacent to the curved slot, at a midway location, whereby the pin is held in place by the magnet at a position that corresponds to the head slider being parked on a ramp positioned between the disk stacks.

Abstract: An actuator rotational limiter mechanism for a multiple disk-stack, shared actuator hard disk drive includes an actuator comb with a cam-lock feature and an actuator limiter with a rotatable cam-roller that is engagable with the cam-lock feature to temporarily hold in place the actuator comb. The cam-lock feature may be positioned at or near a middle location of a back arm of the actuator armature, where the actuator comb being held in place by the cam-roller corresponds to the head slider being positioned on a load/unload ramp between adjacent disk stacks.

Abstract: A load/unload ramp configured for a multiple disk-stack, shared actuator hard disk drive (HDD) includes a ramp part configured for loading and unloading a head stack assembly (HSA) from multiple directions, e.g., from multiple disk stacks, and a tooling part configured to couple with an HSA handling part. The HSA handling part is useful for handling a ramp-HSA assembly during installation, such as for moving the ramp along a guide channel of an HDD base, from an initial position to a final position at which a guide channel stop is reached.

Abstract: A load/unload ramp configured for a multiple disk-stack, shared actuator hard disk drive (HDD) includes two ramp parts configured to swivel-engage together. Each of the two ramp parts may have a sleeve configured for positioning over a swivel pin and a locking pin configured for positioning and movement within a corresponding receptacle constituent to an HDD base. Thus, each ramp part can be positioned to a respective initial locking position onto the base, a first disk stack installed, a first ramp part swiveled to a final locking position engaged with the first disk stack, and fixed to the base. Then an actuator assembly can be inserted and the corresponding actuator arms parked onto the first ramp part, a second disk stack installed, then the second ramp part swiveled to its final locking position engaged with the second disk stack, and fixed to the base.