An image processing control device includes: a memory; and a processor coupled to the memory and configured to: determine, on a basis of a processing rate of an image processing program to be deployed, a type of transfer data extracted from video at a time of transferring the video to be processed by the image processing program to be deployed to be a moving image or a still image; and select, on a basis of the type of the transfer data, a deployment destination information processing device to which the image processing program to be deployed is deployed from among a plurality of information processing devices.

An image processing control device includes: a memory; and a processor coupled to the memory and configured to: determine, on a basis of a processing rate of an image processing program to be deployed, a type of transfer data extracted from video at a time of transferring the video to be processed by the image processing program to be deployed to be a moving image or a still image; and select, on a basis of the type of the transfer data, a deployment destination information processing device to which the image processing program to be deployed is deployed from among a plurality of information processing devices.

An application context relocation method performed by an edge enabler client (EEC) included in a user equipment (UE) in an edge computing system is provided. The application context relocation method includes determining to request an application context relocation by detecting that the application context relocation is required for a predicted or expected UE location; determining a target edge enabler server (T-EES) by using T-EES information received from an edge data network (EDN) configuration server; transmitting, to a source edge enabler server (SEES), an application context relocation request to start the application context relocation; receiving, from the S-EES, an application context relocation response, in response to the application context relocation request; and receiving, from the S-EES, an application context relocation notification of completion of the application context relocation.

An application context relocation method performed by an edge enabler client (EEC) included in a user equipment (UE) in an edge computing system is provided. The application context relocation method includes determining to request an application context relocation by detecting that the application context relocation is required for a predicted or expected UE location; determining a target edge enabler server (T-EES) by using T-EES information received from an edge data network (EDN) configuration server; transmitting, to a source edge enabler server (SEES), an application context relocation request to start the application context relocation; receiving, from the S-EES, an application context relocation response, in response to the application context relocation request; and receiving, from the S-EES, an application context relocation notification of completion of the application context relocation.

A system can include a gateway, a plurality of network function nodes, and a distributed load balancer including load balancer nodes each having a flow table portion stored thereon. The load balancer nodes can form a node chain having a tail and head nodes. A load balancer node can receive a packet from the gateway. In response, the load balancer node can generate a query, directed to the tail node, that identifies the packet and a network function identifier associated with a network function node that is proposed to handle a connection. The tail node can determine whether an entry for the connection exists in a flow table portion associated with the tail node. If not, the tail node can initiate an insert request for writing the entry for the connection via the head node. The entry can then be written to all load balancer nodes in the node chain.

A system can include a gateway, a plurality of network function nodes, and a distributed load balancer including load balancer nodes each having a flow table portion stored thereon. The load balancer nodes can form a node chain having a tail and head nodes. A load balancer node can receive a packet from the gateway. In response, the load balancer node can generate a query, directed to the tail node, that identifies the packet and a network function identifier associated with a network function node that is proposed to handle a connection. The tail node can determine whether an entry for the connection exists in a flow table portion associated with the tail node. If not, the tail node can initiate an insert request for writing the entry for the connection via the head node. The entry can then be written to all load balancer nodes in the node chain.

The present invention relates to communications methods and apparatus for distributing Session Initiation Protocol (SIP) messages among SIP processing entities including during periods of failure recovery. An exemplary method embodiment includes the steps of: establishing a first connection oriented protocol connection between a first Session Initiation Protocol Load Balancer (SLB) of a plurality of SLBs and a client device; receiving via the first connection oriented protocol connection at the first SLB a first SIP REGISTER request message from the first client device; determining, by the first SLB, based on information received from the client device, a first Session Border Controller (SBC) from a plurality of SBCs to send the first SIP REGISTER request message, said information uniquely identifying the first SBC from other SBCs in the plurality of SBCs; and sending, by the first SLB, the first SIP REGISTER request message to the first SBC.

A system can include a gateway, a plurality of network function nodes, and a distributed load balancer including load balancer nodes each having a flow table portion stored thereon. The load balancer nodes can form a node chain having a tail and head nodes. A load balancer node can receive a packet from the gateway. In response, the load balancer node can generate a query, directed to the tail node, that identifies the packet and a network function identifier associated with a network function node that is proposed to handle a connection. The tail node can determine whether an entry for the connection exists in a flow table portion associated with the tail node. If not, the tail node can initiate an insert request for writing the entry for the connection via the head node. The entry can then be written to all load balancer nodes in the node chain.

A system can include a gateway, a plurality of network function nodes, and a distributed load balancer including load balancer nodes each having a flow table portion stored thereon. The load balancer nodes can form a node chain having a tail and head nodes. A load balancer node can receive a packet from the gateway. In response, the load balancer node can generate a query, directed to the tail node, that identifies the packet and a network function identifier associated with a network function node that is proposed to handle a connection. The tail node can determine whether an entry for the connection exists in a flow table portion associated with the tail node. If not, the tail node can initiate an insert request for writing the entry for the connection via the head node. The entry can then be written to all load balancer nodes in the node chain.

A communication protocol includes one or more messages passed between Web routers over a reliable transmission protocol used for inter-Web router communication. These messages include information that allows the Web routers to dynamically update mappings of client addresses or address ranges to information object repository addresses based on client-to-server distance and server load. The mappings are preferably optimal mappings of the client addresses or address ranges to the information object repository addresses and the messages report updated distances from these information object repository addresses to the client addresses or address ranges. For example, the messages may report, for each updated distance, an associated client address or address range and/or an associated anchor address of a Web router co-located with an information object repository that is the subject of the message.