Abstract: Techniques for providing a fencing scheme for cluster systems without inherent hardware fencing. Storage nodes in an HA cluster communicate with one another over communication paths implemented through a variety of mechanisms, including drives and network connections. Each storage node in the HA cluster executes a fencing enforcer component operable to enforce actions or processes for initiating fencing of itself and/or initiating self-fencing of another storage node in the HA cluster determined to be malfunctioning. By providing for richer communications between storage nodes in an HA cluster and a richer set of actions or processes for fencing a malfunctioning storage node including self-fencing, the malfunctioning storage node can be made to exit the HA cluster in a more controlled fashion. In addition, a remaining storage node in the HA cluster can more safely take on the role of primary storage node with reduced risk of data corruption on shared resources.

Abstract: A method of performing authentication of a client for wireless communication includes: sending, by the client, a request to an authorization server via a proxy node, to obtain an access token, wherein the request to obtain the access token contains a client signature of the client; authenticating, by the authorization server, the client as a valid recipient of the access token; and authorizing, by the authorization server, the access token to the client after authenticating the client, wherein the authorization is based on at least the client signature contained in the request to obtain the access token.

Abstract: A method of performing validation of an access token under OAuth 2.0 protocol includes: providing, by an authorization server, the access token for service to a client in response to a request for the access token; adding, by the client, a client signature to at least the access token; forwarding, by the client, the access token as part of a service request to a resource server; and validating, by the resource server, whether the client is a valid owner of the access token, wherein the validation is based on at least the client signature of the access token. The validation is based on a hash of a combination of the service request, the access token and a shared secret key common to the client and the resource server, the output of which hash is added to the service request, and the resource server validates the hash.

Abstract: Techniques for rebooting a node may include: performing first processing that fails to reboot the node using a primary storage device of the node; responsive to the first processing failing to reboot the node using the primary storage device of the node, performing second processing that reboots the node using a secondary storage device of the node and executes a recovery operating system of the secondary storage device; determining, by the recovery operating system executing first code, whether the primary storage device of the node meets one or more criteria indicating that the primary storage device is faulty or defective; and responsive to determining the primary storage device of the node meets the one or more criteria, performing third processing that restores the primary storage device using the secondary storage device.

Abstract: Techniques for submitting unaligned IO data to an alignment-required IO stack of a storage system. The techniques include determining that IO data specified by an IO command contains unaligned IO data, and generating an IOCB and a tunneling IOCB. The IOCB includes information pertaining to the tunneling IOCB and the tunneling IOCB includes information pertaining to a sector-unaligned buffer for storing the IO data. The tunneling IOCB satisfies a sector-alignment requirement of an IO stack. The techniques include, in response to submitting the IO command and the information included in the IOCB to the IO stack, determining that the tunneling IOCB satisfies the sector-alignment requirement of the IO stack; having satisfied the sector-alignment requirement, building a driver command based on the IO command and the information included in the tunneling IOCB; and, transferring, by executing the driver command, the unaligned IO data from the sector-unaligned buffer to a storage device.

Abstract: Techniques for submitting unaligned IO data to an alignment-required IO stack of a storage system. The techniques include determining that IO data specified by an IO command contains unaligned IO data, and generating an IOCB and a tunneling IOCB. The IOCB includes information pertaining to the tunneling IOCB and the tunneling IOCB includes information pertaining to a sector-unaligned buffer for storing the IO data. The tunneling IOCB satisfies a sector-alignment requirement of an IO stack. The techniques include, in response to submitting the IO command and the information included in the IOCB to the IO stack, determining that the tunneling IOCB satisfies the sector-alignment requirement of the IO stack; having satisfied the sector-alignment requirement, building a driver command based on the IO command and the information included in the tunneling IOCB; and, transferring, by executing the driver command, the unaligned IO data from the sector-unaligned buffer to a storage device.

Abstract: Techniques for providing a fencing scheme for cluster systems without inherent hardware fencing. Storage nodes in an HA cluster communicate with one another over communication paths implemented through a variety of mechanisms, including drives and network connections. Each storage node in the HA cluster executes a fencing enforcer component operable to enforce actions or processes for initiating fencing of itself and/or initiating self-fencing of another storage node in the HA cluster determined to be malfunctioning. By providing for richer communications between storage nodes in an HA cluster and a richer set of actions or processes for fencing a malfunctioning storage node including self-fencing, the malfunctioning storage node can be made to exit the HA cluster in a more controlled fashion. In addition, a remaining storage node in the HA cluster can more safely take on the role of primary storage node with reduced risk of data corruption on shared resources.

Abstract: A technique manages drive space within a storage system having a main data services environment configured to perform data storage operations on behalf of a set of hosts and a simple data services environment configured to load the main data services environment. The technique involves, while the simple data services environment is running on the storage system, using the simple data services environment to load the main data services environment on to the storage system. The technique further involves, after the main data services environment is loaded on to the storage system, providing a drive space communication from the simple data services environment to the main data services environment. The technique further involves receiving, by the simple data services environment, allocation of drive space from the main data services environment in response to the drive space communication.

Abstract: A method, computer program product, and computing system for generating a sideband communication channel between a storage kernel driver and an error handling module of a storage system. One or more messages on the storage kernel driver may be detected. At least one message of the one or more messages may be communicated, via the sideband communication channel, from the storage kernel driver to the error handling module.

Abstract: A method, computer program product, and computing system for generating a sideband communication channel between a storage kernel driver and an error handling module of a storage system. One or more messages on the storage kernel driver may be detected. At least one message of the one or more messages may be communicated, via the sideband communication channel, from the storage kernel driver to the error handling module.

Abstract: Techniques for rebooting a node may include: performing first processing that fails to reboot the node using a primary storage device of the node; responsive to the first processing failing to reboot the node using the primary storage device of the node, performing second processing that reboots the node using a secondary storage device of the node and executes a recovery operating system of the secondary storage device; determining, by the recovery operating system executing first code, whether the primary storage device of the node meets one or more criteria indicating that the primary storage device is faulty or defective; and responsive to determining the primary storage device of the node meets the one or more criteria, performing third processing that restores the primary storage device using the secondary storage device.

Abstract: A method of performing validation of an access token under OAuth 2.0 protocol includes: providing, by an authorization server, the access token for service to a client in response to a request for the access token; adding, by the client, a client signature to at least the access token; forwarding, by the client, the access token as part of a service request to a resource server; and validating, by the resource server, whether the client is a valid owner of the access token, wherein the validation is based on at least the client signature of the access token. The validation is based on a hash of a combination of the service request, the access token and a shared secret key common to the client and the resource server, the output of which hash is added to the service request, and the resource server validates the hash.

Abstract: An embodiment wireless communication system includes a base station and a software defined network (SDN)-enabled switch/router configured to communicate data packets with the base station. The wireless communication system also includes a computing platform running at least one virtual device and that is configured to communicate with the SDN-enabled switch/router and to provide software to configure operation of the SDN-enabled switch/router.

Abstract: Techniques are presented for implementing a scalable approach to keeping track of the metadata validity of persistently-stored metadata for storage objects. In contrast with prior approaches, improved techniques only store a list of the invalid (or quarantined) objects rather than all objects regardless of validity of their metadata. Under normal circumstances, only a small number of storage objects are invalid at any given time, as the system generally takes steps to repair the invalid objects in the normal course of operation. Thus, the number of invalid objects tends to be small, barring some catastrophic system failure. Only a small amount of expensive privileged persistent storage is therefore needed. A health level may also be used to indicate many failures, indicative of catastrophic system failure.

Abstract: Techniques are presented for implementing a scalable approach to keeping track of the metadata validity of persistently-stored metadata for storage objects. In contrast with prior approaches, improved techniques only store a list of the invalid (or quarantined) objects rather than all objects regardless of validity of their metadata. Under normal circumstances, only a small number of storage objects are invalid at any given time, as the system generally takes steps to repair the invalid objects in the normal course of operation. Thus, the number of invalid objects tends to be small, barring some catastrophic system failure. Only a small amount of expensive privileged persistent storage is therefore needed. A health level may also be used to indicate many failures, indicative of catastrophic system failure.

Abstract: A method for connection rehoming by a user equipment includes attaching to a first network attachment point (AP) and establishing a first connection to a first packet data network (PDN) interface, and moving from the first network AP to a second network AP. The method includes discovering a first cost associated with the first connection is high, and rehoming the first connection, thereby establishing a second connection coupling the UE to a second network AP and to a second PDN interface, wherein a second cost associated with the second connection is low.

Abstract: A described embodiment includes a method for managing operational components on wireless base station including providing a base station. The base station includes a software defined network (SDN) configured to support at least one virtual machine. A computing platform is provided that is in communication with the base station. The computing platform includes at least one virtual machine management unit. The virtual machine management unit configures the at least one virtual machine on the base station to perform at least one function of a base station.

Abstract: Described are techniques for building a code entity. A plurality of configuration files are selected in accordance with a target and target variant. The target identifies hardware and software platform information about an environment in which the code entity is to be configured for execution. The target variant identifies a software build variation for a particular target. One or more build phases are performed using the plurality of configuration files selected in said selecting. The code entity is generated as an output of performing the one or more build phases where the code entity varies with the target and target variant.

Abstract: A method for managing prefixes of a mobile node (MN) includes receiving a servable prefix and a cost associated with the servable prefix from a first router serving the MN, wherein the servable prefix is one of a plurality of prefixes assigned to the MN that is servable by the first router, deciding whether to release the servable prefix through the first router in accordance with the cost associated with the servable prefix, and releasing the servable prefix when the MN has decided to release the servable prefix.

Abstract: An embodiment method of routing network traffic includes configuring flow tables of a virtual switch using an OpenFlow protocol. The virtual switch is disposed at a network radio node. The method includes receiving network traffic destined for a user equipment (UE) at the virtual switch and establishing, by a packet data convergence protocol (PDCP) layer, a data radio bearer (DRB) for the network traffic between a virtual port on the virtual switch and the UE. The method also includes routing the network traffic over the DRB from the virtual port, through the PDCP layer, and toward the UE according to the flow tables.