Abstract: Systems and methods for test data generation are described. In one implementation, the method includes receiving seed data having one or more characteristics. Further, the method includes obtaining a selection criterion indicating a selected portion of the seed data to be transformed. Based on the selection criterion, the seed data is transformed for at least a plurality of iterations to generate test data. The test data comprise a plurality of data sets including a primary data set generated in a first iteration and a secondary data set generated in each subsequent iteration. The primary data set includes transformed data corresponding to the selected portion of the seed data and non-transformed data corresponding to a remaining portion of the seed data and each secondary data set includes transformed data corresponding to the selected portion of the seed data.

Abstract: Replication and recovery for a protected private cloud infrastructure that may include hosts, virtual machines (VMs) provisioned on the hosts, storage arrays and a management server. Metadata is periodically captured and made accessible to a recovery site. Upon a recovery event, replication of storage arrays is halted, and a number of target machines corresponding to the management server and the hosts to be recovered are assigned. The assigned management server and hosts are then bare provisioned by installing operating systems or hypervisors as specified by the metadata. Only then are recovery target machines connected to the replicated storage arrays so that virtual machines can be activated.

Abstract: A burning control method for burning software to at least one chip is provided, the method includes: controlling the at least one chip to enter a download mode when the at least one chip is startup; initializing the at least one chip when the chip enters the download mode; executing a burning process to burn software into the at least one chip when the chip is initialized; controlling the at least one chip to enter the test mode when the burning process is completed; testing whether the software has been burned into the at least one chip successfully when the at least one chip is in the test mode.

Abstract: According to exemplary embodiments, a computer implemented method for functional testing of a processor design includes accessing a test template from a library of test templates, wherein the test template is configured to test a first selected function of the processor and inputting the test template to an automated test generation tool executed by a computer. The method further includes generating an instruction sequence based on the test template by the automated test generation tool and injecting an event instruction to the instruction sequence during the generating of the instruction sequence by the automated test generation tool, the injecting of the event instruction preserving testing of the first selected function of the processor and the event instruction being configured to test a second selected function of the processor. The method includes verifying a function of the processor by analyzing responses of the processor to the instruction sequence.

Abstract: Disclosed in the present invention are a method and an apparatus for restarting communication after registration of a subscriber identity module SIM card fails, which belongs to the field of mobile communications. The method includes: acquiring failure information about registration of the SIM card; displaying the failure information and prompt information on an interface, and receiving confirmation information that is replied by a user according to the prompt information; and restarting, according to the confirmation information, a communication processor under the condition of not turning off an application processor or not restarting the application processor, so as to re-register the SIM card.

Abstract: Synchronous local and cross-site switchover and switchback operations of a node in a disaster recovery (DR) group are described. In one embodiment, during switchover, a takeover node receives a failover request and responsively identifies a first partner node in a first cluster and a second partner node in a second cluster. The first partner node and the takeover node form a first high-availability (HA) group and the second partner node and a third partner node in the second cluster form a second HA group. The first and second HA groups form the DR group and share a storage fabric. The takeover node synchronously restores client access requests associated with a failed partner node at the takeover node.

Abstract: Techniques for providing session level replication and fail-over as a network service include generating a replication rule that replicates network traffic destined for a primary server from an originating server to a network controller and installing said rule in a switch component, identifying flows from the originating server to the primary server, replicating each incoming data packet intended for the primary server to the network controller for replication and forwarding to replica servers, determining said primary server to be in a failed state based on a number of retransmissions of a packet, to selecting one of the replica servers as a fail-over target, and performing a connection level fail-over by installing a redirection flow in the switch component that redirects all packets destined to the primary server to the network controller, which forwards the packets to the replica server and forwards each response from the replica server to said originating server.

Abstract: A method begins by a processing module determining that a data storage request is a cloud data storage request. The method continues with the processing module determining at least one of a cloud storage access reliability indication and a cloud storage data reliability indication for the data storage request. The method continues with the processing module sending the data storage request and the at least one of cloud storage access reliability indication and cloud storage data reliability indication to a cloud storage system.

Abstract: A debugging device for performing a debugging process through an electronic device external connector system is provided. The debugging device performs the debugging process to a target system, and the device comprises a first external connector, a switch, and a debugging module. The first external connector is connected to the external port of the target system. The switch is connected to the first external connector, and the switch chooses to activate the debugging process. The debugging module is connected to the switch, and the debugging module receives a universal asynchronous receiver/transmitter (UART) signal provided by the target system.

Abstract: Systems and method for embedded trace macrocell (ETM) devices configured to dynamically interleave architecture/program tracing with microarchitecture/hardware tracing. An ETM device includes logic to enable interleaved program tracing and hardware state sampling. A core interface is configured to receive program trace and hardware state information of a microprocessor and a combining module is configured to interleave the program trace and hardware state information. A packet generation module may be configured to packetize the program trace and hardware state information into packets at operational speeds of the microprocessor.

Abstract: The present invention relates to an automatic testing apparatus used for testing a tested device. The automatic testing apparatus is fixed on a first side of a testing platform. The tested device executes a testing program while being tested, and transmits a test signal to a control unit of the testing platform for controlling a driving testing unit or a multimedia testing module to test the tested device and hence testing the tested device automatically. Thereby, testing costs can be saved and artificial factor affecting the test results can be avoided.

Abstract: A computer-implemented method for fault recovery in multi-tier applications may include: 1) identifying a plurality of clusters, 2) identifying a multi-tier application that includes a plurality of components, each cluster within the plurality of clusters hosting a component, 3) identifying a fault of a first component within the plurality of components on a first cluster within the plurality of clusters, the fault requiring a first recovery action, 4) identifying at least one dependency relationship involving the first component and a second component within the plurality of components on a second cluster within the plurality of clusters, 5) determining, based on the fault and the dependency relationship, that the second component requires a second recovery action to ensure that the multi-tier application operates correctly, and 6) performing the second recovery action on the second component. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Connectivity fault notification is provided by generating an alarm indication signal at a device that is logically adjacent to the fault, and forwarding the alarm indication signal upward through various levels to at least one client level entity. The alarm indication signal may be suppressed at any level for a service instance if service is restored at that level, or if a protection path prevents disruption of the service instance at that level, or auto-suppressed at an originating node based on number of times transmitted or elapsed time. The alarm indication signal may include a point of failure indicator such as the MAC address of the device that generates the alarm indication signal, or a failed resource identity such as an IEEE 802.1AB LLDP MAC Service Access Point (“MSAP”). Further, the alarm indication signal may be employed to trigger use of the protection path.

Abstract: An architecture for protecting against failure in a switched storage network using virtualization.

Abstract: Systems and methods are disclosed herein for performing a failover operation between a first distributed database cluster and a second distributed database cluster. In one aspect, the method includes blocking a plurality of software processes from making any new access requests to the first distributed database cluster and completing a current access request to the first distributed database cluster that was initiated by one of the plurality of software processes before the failover operation was initiated, waiting for data to replicate from the first distributed database cluster to the second distributed database cluster, wherein replicating includes any changes to the data from the current access request, and allowing the plurality of software processes to make the new access requests to the second distributed database cluster once the replicating has completed.

Abstract: A method begins by a processing module dispersed storage error encoding data to produce a set of encoded data slices and sending a set of write request messages to a set of dispersed storage (DS) units, wherein each of the set of write request messages includes an encoded data slice of the set of encoded data slices. The method continues with the processing module determining whether a pillar width number of favorable write response messages has been received within a write acknowledgement (ACK) time period. The method continues with the processing module executing a retry write process to at least one DS unit of the set of DS units from which a favorable write response message was not received during the write ACK time period when the pillar width number of favorable write response messages has not been received within the write ACK time period.

Abstract: A data processing apparatus having processing circuitry and debug circuitry is debugged by operating the processing circuitry to generate data. The debug circuitry is employed to generate trace elements indicative of the operation of the processing circuitry. Trace elements are caused to be output from the data processing apparatus over a communication bus capable of connecting a plurality of devices. The communication bus is controlled by a protocol for data interchange requiring data interchange from any device on the communication bus to be controlled by a single processing system. The passing of the trace elements onto the communication bus is controlled using an interface unit of the debug circuitry. The interface unit comprises a controller arranged to allow each of the interface unit and processing circuitry to be separate processing systems which can each independently control data interchange from the data processing apparatus.

Abstract: Error information is sent from a terminal adaptor that accesses a wireless network to terminal equipment coupled to access the wireless network through the terminal adaptor. The error information is sent in response to existence of any one of a plurality of errors conditions with respect to access to the wireless network. The error information includes an error type identifying a domain associated with a source of the error condition being reported and an error code providing a reject error cause for the error condition. One of the error conditions may include an unsolicited error received by the terminal adaptor from the wireless network or when a request by the TA is ignored by the wireless network.

Abstract: A disaster recovery system can include a plurality of resources arranged in a cloud computing environment. Each of the resources can be assignable to function within the cloud computing environment as part of one or more media systems. A content intake service can be programmed to control delivery of an incoming media asset to the cloud computing environment. A monitoring and recovery process can be programmed to monitor a primary media system to which the incoming media asset is being provided and, in response to detecting a disaster recovery condition, the monitoring and recovery process can intelligently manage selected resources of the plurality of resources based on the incoming media asset being delivered to the primary media system.

Abstract: Methods and apparatus for improved building of a hot spare storage device in a RAID storage system while avoiding reading of stale data from a failed storage device. In the recovery mode of the failed device, all data is write protected on the failed device. A RAID storage controller may copy as much readable data as possible from the failed device to the hot spare storage device. Unreadable data may be rebuilt using redundant information of the logical volume. Write requests directed to the failed device cause the addressed logical block address (LBA) to be marked as storing stale data. When a read request is directed to such a marked LBA, the read request returns an error status from the failed device to indicate that the data is stale. The RAID controller then rebuilds the now stale data for that LBA from redundant information of the logical volume.