Abstract: A vehicle-based mobile content delivery system comprises a projector configured to receive and project visual content, a projection surface for receiving and displaying the projected visual content, and a projector mounting system for securely mounting the projector and integrating the projector into a vehicle. The projector mounting system comprises a headrest projector mount compatible with an original headrest of the vehicle for enclosing and supporting the projector, a headrest coupling mechanism for coupling the projector to the headrest projector mount for support, and mounting channels that accommodate a range of headrest mounting rails of vehicles for connecting the projector mounting system to the vehicle.

Abstract: A vehicle-based mobile content delivery system comprises a projector configured to receive and project visual content, a projection surface for receiving and displaying the projected visual content, and a projector mounting system for securely mounting the projector and integrating the projector into a vehicle. The projector mounting system comprises a headrest projector mount compatible with an original headrest of the vehicle for enclosing and supporting the projector, a headrest coupling mechanism for coupling the projector to the headrest projector mount for support, and mounting channels that accommodate a range of headrest mounting rails of vehicles for connecting the projector mounting system to the vehicle.

Abstract: A mobility network architecture includes a control plane and data plane. The control plane supports notification of VLAN configurations. The data plane supports routing of data amongst VLANs. Each VLAN has an associated identifier value as well as a version number. The version number for a respective VLAN can be updated to a new value each time there is a change to the VLAN. Typically, a controller communicates over the control plane to notify each member switch when a version number has changed for a VLAN. If controller notification fails, a member switch can receive a notification from a neighboring switch that the version number for a VLAN has been modified. In response to detecting such a condition, the switch receiving the notification can prevent forwarding of data even though the switch does not receive notification from the controller that the version number for the VLAN has changed.

Abstract: A split-plane mobility network architecture separates control and data plane operations typically encapsulated in a conventional wireless controller. Configurations provide a unified split-plane mobility switch that separates the data transport and switching in a separate hardware element, and performs control plane operations via exchanges with a centralized topology, rather than simply by adjacent switches within range. In contrast to conventional switch deployment, in which the same switch handles processing demands of the control plane and the data plane, the disclosed approach separates the data plane processing base by employing a mobility agent to define adjacent switch visibility. Thus, the routing capabilities of the data plane may be enhanced, such as to handle increasingly bandwidth-hungry applications of the same user base, without uprooting the infrastructure defined by the control plane.

Abstract: A method, apparatus and computer program product for providing wireless control plane failover handling in a split-plane deployment is presented. A first AP in a split-plane deployment detects failure of a Wireless Control Plane (WCP) device. The first AP hides an SSID in beacons broadcast by the first AP. The first AP stores information for existing Mobile Units (MUs) that dissociate after the detection of the failure of the WCP device. The first AP will respond to probes from existing MUs; and also respond to probes from MUs that have their information stored in the AP, such that the first AP appears hidden from new MUs while being exposed to existing MUs.

Abstract: A method, apparatus and computer program product for providing wireless control plane failover handling in a split-plane deployment is presented. A first AP in a split-plane deployment detects failure of a Wireless Control Plane (WCP) device. The first AP hides an SSID in beacons broadcast by the first AP. The first AP stores information for existing Mobile Units (MUs) that dissociate after the detection of the failure of the WCP device. The first AP will respond to probes from existing MUs; and also respond to probes from MUs that have their information stored in the AP, such that the first AP appears hidden from new MUs while being exposed to existing MUs.

Abstract: A split-plane mobility network architecture separates control and data plane operations typically encapsulated in a conventional wireless controller. Configurations provide a unified split-plane mobility switch that separates the data transport and switching in a separate hardware element, and performs control plane operations via exchanges with a centralized topology, rather than simply by adjacent switches within range. In contrast to conventional switch deployment, in which the same switch handles processing demands of the control plane and the data plane, the disclosed approach separates the data plane processing base by employing a mobility agent to define adjacent switch visibility. Thus, the routing capabilities of the data plane may be enhanced, such as to handle increasingly bandwidth-hungry applications of the same user base, without uprooting the infrastructure defined by the control plane.

Abstract: A mobility network architecture includes a control plane and data plane. The control plane supports notification of VLAN configurations. The data plane supports routing of data amongst VLANs. Each VLAN has an associated identifier value as well as a version number. The version number for a respective VLAN can be updated to a new value each time there is a change to the VLAN. Typically, a controller communicates over the control plane to notify each member switch when a version number has changed for a VLAN. If controller notification fails, a member switch can receive a notification from a neighboring switch that the version number for a VLAN has been modified. In response to detecting such a condition, the switch receiving the notification can prevent forwarding of data even though the switch does not receive notification from the controller that the version number for the VLAN has changed.