Patent classifications
H04L69/10
USING HIGH SPEED DATA TRANSFER PROTOCOL
Using high speed data transfer protocol to transfer data between a host and a storage system includes determining if a portion of data is a candidate for being transferred using the high speed data transfer protocol if the portion is not a candidate for high speed data transfer, transferring the data using a relatively low speed data transfer protocol if the portion is a candidate for high speed data transfer, attempting to transfer the data using the high speed data transfer protocol, and if transferring the data using the high speed data transfer protocol is unsuccessful, transferring the data using the relatively low speed data transfer protocol. The high speed data transfer protocol may use a first connection and the relatively low speed data transfer protocol may use a second connection. The first connection may be a PCIe or InfiniBand connection. The second connection may be a FICON connection.
SYSTEM FOR PROCESSING MESSAGES OF DATA STREAM
A system for processing messages of a high rate data stream and an apparatus including: a message processor including a plurality of processor sub-modules and configured to read an input data stream, process the input data stream, and to output an output data stream; at least one payload memory storing data related to the input data stream and accessible to the message processor; at least one instruction memory accessible to the message processor and storing computer program instructions configuring the message processor to process the input data stream; and an application processor configured to rewrite the at least one instruction memory.
Computer device and method for reading or writing data by computer device
A computer device and a method for reading or writing data by a computer device are provided. In the computer device, a central processing unit (CPU) is connected to a cloud controller using a double data rate (DDR) interface. Because the DDR interface has a high data transmission rate, interruption of CPU can be avoided. In addition, the CPU converts a read or write operation request into a control command and writes the control command into a transmission queue in the cloud controller. Because the cloud controller performs a read operation or a write operation on a network device according to operation information in the control command, after writing the control command into the transmission queue, the CPU does not need to wait for an operation performed by the cloud controller and can continue to perform other processes.
Methods, devices and systems for non-disruptive upgrades to a distributed coordination engine in a distributed computing environment
A computer-implemented method and distributed system for maintaining consistency of client applications on a plurality of server nodes may comprise providing a first and second versions of a distributed coordination engine (DConE). The first version of the DConE may receive proposals, reach agreements thereon and generate a first ordering of agreements that specifies an order in which the client applications are to execute the agreed-upon proposals and correspondingly update their respective states. A ChangeVersion proposal may then be processed by the first version of the DConE, whereupon the first version of the DConE may stop reaching any further agreements. A second version of the DConE may then take over reaching agreements on the proposals and generate a second ordering of agreements, beginning with the agreed-upon ChangeVersion proposal. Any agreed-upon proposal, received from the first version of the DConE after the agreed-upon ChangeVersion proposal, may be sent back to the second version of the DConE to enable the second version of the DConE to reach agreement thereon.
METHODS, DEVICES AND SYSTEMS FOR NON-DISRUPTIVE UPGRADES TO A REPLICATED STATE MACHINE IN A DISTRIBUTED COMPUTING ENVIRONMENT
A computer-implemented method and distributed system for maintaining consistency of client applications on a plurality of server nodes may comprise providing a first and second versions of a distributed coordination engine (DConE). The first version of the DConE may receive proposals, reach agreements thereon and generate a first ordering of agreements that specifies an order in which the client applications are to execute the agreed-upon proposals and correspondingly update their respective states. A ChangeVersion proposal may then be processed by the first version of the DConE, whereupon the first version of the DConE may stop reaching any further agreements. A second version of the DConE may then take over reaching agreements on the proposals and generate a second ordering of agreements, beginning with the agreed-upon ChangeVersion proposal. Any agreed-upon proposal, received from the first version of the DConE after the agreed-upon ChangeVersion proposal, may be sent back to the second version of the DConE to enable the second version of the DConE to reach agreement thereon.
System and devices facilitating dynamic network link acceleration
A peer to peer dynamic network acceleration method and apparatus provide enhanced communications directly between two or more enhanced devices, such as enhanced clients. The enhanced clients may comprise a front-end, a back-end, or both. In general, the front-end and back-end of the enhanced clients work in concert to translate data into an enhanced protocol for communication between the enhanced clients. The enhanced protocol may provide acceleration, security, error correction, and other benefits. Data from various applications may be seamlessly translated between a first protocol and the enhanced protocol, such that the applications need not be modified to use the enhanced protocol. The enhanced clients may automatically detect one another to establish an enhanced communications channel automatically.
In-Service Quality Monitoring System with Intelligent Retransmission and Interpolation
A service request for communication services for communication clients is received. In response, a communication service network is set up to support the communication services. Routing metadata is generated for each of the communication clients. The routing metadata is to be used by each of the communication clients for sharing service quality information with a respective peer communication client over a light-weight peer-to-peer (P2P) network. The routing metadata is downloaded to each of the communication clients. A communication client may exchange service signaling packets or service data packets over the communication service network. When the communication client determines that there is a problematic region in a bitstream received from the communication server, the communication client can request a peer communication client for a service quality information portion related to the problematic region.
Method and facility for communication in a medical imaging facility and medical imaging facility
A method for communication between at least two computing facilities of a medical imaging facility via a single communication line is disclosed. In the method, communication information assigned to different communication types received in each case via a dedicated data input is merged to form data structures of a defined size to be transmitted via the communication line. The data structures are transmitted cyclically via the communication line with an interval of one cycle time and communication information of the different communication types is extracted from data structures received via the communication line and output at data outputs assigned to the respective communication types. The communication types include a first packet-oriented communication type and a second isochronous communication type corresponding to isochronous direct channel communication.
Computing system providing SaaS application integration with internet of things (IoT) sensors through automated application program interface (API) generation and related methods
A computing system may include a server configured to provide Software as a Service (SaaS) application sessions and at least one client computing device cooperating with the server to run a first one of the SaaS application sessions having a form including an input data field, and generate an application program interface (API) based upon the input data field from the form. The at least one client computing device may further link an output of an Internet of Things (IoT) sensor corresponding to the input data field to the API, and collect data output from the IoT sensor and populate the input data field in the form via the API.
MULTI-PATH RDMA TRANSMISSION
In accordance with implementations of the subject matter described herein, there provides a solution for multi-path RDMA transmission. In the solution, at least one packet is generated based on an RDMA message to be transmitted from a first device to a second device. The first device has an RDMA connection with the second device via a plurality of paths. A first packet in the at least one packet includes a plurality of fields, which include information for transmitting the first packet over a first path of the plurality of paths. The at least one packet is transmitted to the second device over the plurality of paths via an RDMA protocol. The first packet is transmitted over the first path. The multi-path RDMA transmission solution according to the subject matter described herein can efficiently utilize rich network paths while maintaining a low memory footprint in a network interface card.