There is provided a method for handling a service request. The method is performed by a first service communication proxy (SCP) node. If no response is received from a second network function (NF) node of a service producer to a first request transmitted towards the second NF node via the first SCP node, where the first request is for the second NF node to execute a service requested by a first NF node of a service consumer, transmission of information is initiated towards the first NF node. The information is indicative that no response is received from the second NF node to the first request.

A method, medium, and apparatus for allowing evaluation of property, such as damaged property, remotely and efficiently. A mobile computing device may be used to conduct bilateral communication between a client and an agent for evaluating property. The communications may comprise methods and systems for reconnecting using login-free connections, and may further comprise methods and systems for determining that wait times exceed a threshold wait time and presenting the client an option to receive a call back.

A storage system performs data replication with a recovery point objective (RPO). The storage system replicates data at intervals through data transfers over a network. The storage system determines bandwidth of the network. The storage system determines the intervals for replicating the data, based on size of data transfers, network bandwidth, and the recovery point objective.

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

A method and a device for processing a failure in at least one distributed cluster, and a system, where the at least one distributed cluster includes a first distributed cluster. The first distributed cluster includes a first Master node, a first Slave node, a first reference node, and a first secondary node that serves as a backup of the first Master node. The first secondary node receives a heartbeat message that includes first indication information. The first secondary node determines, according to the first indication information, that the first reference node is disconnected from the first Master node. The first secondary node determines that the first secondary node is also disconnected from the first Master node when it is detected that a heartbeat message from the first Master node to the first secondary node is interrupted. The first secondary node determines the first Master node is faulty.

A network device comprises time measurement units configured to measure receipt times and transmit times of packets received/transmitted via network interfaces. One or more memories store configuration information that indicates certain network interface pairs and/or certain packet flows that are enabled for latency measurement. A packet processor includes a latency monitoring trigger unit configured to select, using the configuration information, packets that are forwarded between the certain network interface pairs and/or that belong to the certain packet flows for latency monitoring. One or more latency measurement units determine respective latencies for packets selected by the latency monitoring trigger unit using respective receipt times and respective transmit times for the packets selected by the latency monitoring trigger unit, calculates latency statistics for the certain network interface pairs and/or the certain packet flows using the respective latencies, and stores the latency statistics in the one or more memories.

Methods and systems for providing network models and network configurations for communications are described. The method includes establishing, by a device intermediary to a plurality of clients and servers, a first interface on a manager of the device for delivering a network model of the device from the manager of the device to a software defined network (SDN) controller of an SDN. The method includes providing, via the first interface, the network model configured to provide definitions of one or more network layer entities of the device that are configured to provide network layer services. The method includes establishing, a second interface on the manager of the device configured to transmit and receive communications between the device and the SDN controller. The method includes receiving, by the manager via the second interface, network configuration to configure the device to process SDN application requests received from the SDN controller.

Methods, systems, and computer-readable media for providing reliable switching between different transport protocols (e.g., TCP and UDP) are presented herein. In some embodiments, a computing platform may stop transmission over a transport protocol. Subsequently, the computing platform may synchronize buffers between a client and a host. For example, the buffer may include acknowledgments for undelivered reliable packets between the client and the host. Next, the computing platform may resume transmission over a different transport protocol. In some embodiments, when establishing an initial connection between a client and a host, connections may be attempted in parallel over multiple transport protocols. After a connection over a first transport protocol is established, if a connection is later established over a second transport protocol, the connection may be transitioned to the second transport protocol. Also, ticketing semantics may be preserved in the switch between the different transport protocols.

Methods, systems, and computer-readable media for providing reliable switching between different transport protocols (e.g., TCP and UDP) are presented herein. In some embodiments, a computing platform may stop transmission over a transport protocol. Subsequently, the computing platform may synchronize buffers between a client and a host. For example, the buffer may include acknowledgments for undelivered reliable packets between the client and the host. Next, the computing platform may resume transmission over a different transport protocol. In some embodiments, when establishing an initial connection between a client and a host, connections may be attempted in parallel over multiple transport protocols. After a connection over a first transport protocol is established, if a connection is later established over a second transport protocol, the connection may be transitioned to the second transport protocol. Also, ticketing semantics may be preserved in the switch between the different transport protocols.