Abstract: Provided are a computer program product, system, and method for transmitting video sub-streams captured from source sub-locations to extended-reality headsets worn by viewers at a target location. Video cameras, positioned to capture video at a source location, are assigned to source sub-locations of the source location. The video cameras assigned to a source sub-location capture video of the event from points-of-view of viewers within the source sub-location. The source sub-locations of the source location are associated with target sub-locations of a target location in which the viewer is located. The source location and the target location are in different geographical locations. A video sub-stream from video cameras assigned to a source sub-location is transmitted to be rendered in the extended-reality headset worn by a viewer located in a target sub-location associated with the source sub-location to which the video cameras that captured the video sub-stream are assigned.

Abstract: Providing a guide to volumetric video viewing includes receiving a request for a video from a viewer. At least one object of viewer's interest is determined. The video and object metadata associated with objects rendered in the video are received. Based on the object metadata, a position of at least one object of viewer's interest in the received video is identified. Viewer's view is guided toward the identified position in the video where the object of viewer's interest is found, as the video plays on a device of the viewer.

Abstract: According to one embodiment, a method, computer system, and computer program product for mitigating a camera failure during volumetric capture is provided. The embodiment may include monitoring respective status of functionality (SoF) array data structures of a set of cameras tasked with capturing volumetric video of a scene. The set of cameras comprises cameras designated as backup cameras and cameras designated for active volumetric capture. The embodiment may include detecting a failed camera of the cameras designated for active volumetric capture based on evaluation of an SoF array data structure of the failed camera. In response to detecting the failed camera, the embodiment may include determining whether a backup camera of the cameras designated as backup cameras is available to replace the failed camera. In response to determining the backup camera is available, the embodiment may include replacing the failed camera with the backup camera.

Abstract: According to one embodiment, a method, computer system, and computer program product for mitigating a camera failure during volumetric capture is provided. The embodiment may include monitoring respective status of functionality (SoF) array data structures of a set of cameras tasked with capturing volumetric video of a scene. The set of cameras comprises cameras designated as backup cameras and cameras designated for active volumetric capture. The embodiment may include detecting a failed camera of the cameras designated for active volumetric capture based on evaluation of an SoF array data structure of the failed camera. In response to detecting the failed camera, the embodiment may include determining whether a backup camera of the cameras designated as backup cameras is available to replace the failed camera. In response to determining the backup camera is available, the embodiment may include replacing the failed camera with the backup camera.

Abstract: Provided are techniques for offloading a task from an edge server that is integrated with a moving vehicle. One or more tasks are executed while performing monitoring of hardware and software components. In response to the monitoring, a failure is identified. In response to determining that the failure prevents the one or more tasks from being completed, a request message is broadcast to a plurality of peer moving edge servers to request assistance, an acknowledgement is received from each of the plurality of peer moving edge servers, one or more of the plurality of the peer moving edge servers is selected, and the one or more tasks are handed over to the selected one or more peer moving edge servers. In response to determining that the failure does not prevent the one or more tasks from being completed, continuing execution of the one or more tasks.

Abstract: Methods, computer program products, and systems are presented.

Abstract: A computer-implemented method, a system, and a computer program product for cloud object storage format conversion are provided. A processor identifies a target object format and an object storage bucket in a COS environment. The processor determines a function associated with objects in the storage bucket. The processor generates a conversion policy that includes converting a first format of an object to a target format, based on the function, the object storage bucket, the first format, and input from a user. The processor receives a request to perform the function on a object having a first format and an object storage bucket corresponding to performing the function on the object, and the processor triggering conversion of the object having the first format to the target format within the cloud environment, based on the conversion policy for the object storage bucket.

Abstract: Balancing computational loading across UAV-MEC devices by receiving information associated with a data processing task, determining a first computational loading associated with the data processing task relative to a capacity of a first device, sending the first computational loading and a first location to a second device, determining that the second device can support the first computational loading, deploying, the second device to the first location, and completing the first computational task using the first device and the second device.

Abstract: Example techniques of migration of cloud networks between different multi-cloud management platforms, are described. In an example, a migration request is received. The migration request is indicative of a source multi-cloud management platform from which a cloud network is to be migrated to a destination multi-cloud management platform. The cloud network to be migrated from the source multi-cloud management platform to the destination multi-cloud management platform is identified based on a user input. Management platform information from the source multi-cloud management platform is obtained. The management platform information is representative of policies and data associated with the cloud network stored in databases of the source multi-cloud management platform. The cloud network is registered at the destination multi-cloud management platform. The management platform information is associated with the cloud network based on a unique identification number of the cloud network.

Abstract: A method includes: creating and maintaining, by a cloud object storage server, plural order data structures that define respective orders of objects stored in a bucket in a cloud object storage system; receiving, from a client device, a request to download the objects using one of the respective orders; allocating an iterator for the request, wherein the iterator is associated with a respective one of the plural order data structures that defines the one of the respective orders; returning an iterator identifier of the iterator to the client device; receiving, from the client device, a call containing the iterator identifier; and returning the objects to the client device in the one of the respective orders using the iterator and the respective one of the plural order data structures.

Abstract: Example techniques of addition of nodes in cloud networks managed by a multi-cloud management platform, are described. In an example, a node addition request is received at a multi-cloud management platform. The node addition request includes identification information of a node and a cloud network in which the node is to be added. The identification information is indicative of a functionality of the node, a network address of the node, and an identifier of the cloud network. Based on the identifier of the cloud network, cloud account details of the cloud network may be obtained from one of the multi-cloud management platform and a user input. A controller node of the cloud network may be accessed based on the cloud account details. The node may be registered at the controller node of the cloud network, based on the identification information of the node and the cloud network.

Abstract: Example implementations relate to method and system for data management in a computing system, such as an edge server having a processing resource. During operation, the processing resource collects data from a plurality of smart devices and process a portion of the data at each edge-stage of a plurality of first edge-stages to generate partially processed data. Further, the processing resource evaluates a data processing load at an edge-stage of the plurality of first edge-stages based on a throughput of the edge-stage or a size of a data processing queue of a next edge-stage of the plurality of first edge-stages. The processing resource further pushes the partially processed data to the next edge-stage or a portion of the partially processed data to an external computing system and a remaining portion of the partially processed data to the next edge-stage, based on the data processing load at the edge-stage.

Abstract: Example techniques of addition of nodes in cloud networks managed by a multi-cloud management platform, are described. In an example, a node addition request is received at a multi-cloud management platform. The node addition request includes identification information of a node and a cloud network in which the node is to be added. The identification information is indicative of a functionality of the node, a network address of the node, and an identifier of the cloud network. Based on the identifier of the cloud network, cloud account details of the cloud network may be obtained from one of the multi-cloud management platform and a user input. A controller node of the cloud network may be accessed based on the cloud account details. The node may be registered at the controller node of the cloud network, based on the identification information of the node and the cloud network.

Abstract: Example techniques of addition of nodes in cloud networks managed by a multi-cloud management platform, are described. In an example, a node addition request is received at a multi-cloud management platform. The node addition request includes identification information of a node and a cloud network in which the node is to be added. The identification information is indicative of a functionality of the node, a network address of the node, and an identifier of the cloud network. Based on the identifier of the cloud network, cloud account details of the cloud network may be obtained from one of the multi-cloud management platform and a user input. A controller node of the cloud network may be accessed based on the cloud account details. The node may be registered at the controller node of the cloud network, based on the identification information of the node and the cloud network.

Abstract: Example implementations relate to method and system for data management in a computing system, such as an edge server having a processing resource. During operation, the processing resource collects data from a plurality of smart devices and process a portion of the data at each edge-stage of a plurality of first edge-stages to generate partially processed data. Further, the processing resource evaluates a data processing load at an edge-stage of the plurality of first edge-stages based on a throughput of the edge-stage or a size of a data processing queue of a next edge-stage of the plurality of first edge-stages. The processing resource further pushes the partially processed data to the next edge-stage or a portion of the partially processed data to an external computing system and a remaining portion of the partially processed data to the next edge-stage, based on the data processing load at the edge-stage.

Abstract: The disclosure describes techniques for converting a source cloud network to a destination cloud network. In one implementation, a method includes: receiving a user request to convert a source cloud network to a destination cloud network; in response to receiving the request, invoking a driver based on the destination cloud network specified in the user request; using at least the invoked driver to retrieve cloud configuration data of the source cloud network and an operating system (OS) image of the destination cloud network; using at least the retrieved cloud configuration data of the source cloud network and the retrieved OS image of the destination cloud network, converting the source cloud network to the destination cloud network, wherein converting comprises: registering a controller and compute node of the source cloud network as a controller and compute node of the destination cloud network; and sending a notification that the conversion was completed.

Abstract: Example techniques of addition of nodes in cloud networks managed by a multi-cloud management platform, are described. In an example, a node addition request is received at a multi-cloud management platform. The node addition request includes identification information of a node and a cloud network in which the node is to be added. The identification information is indicative of a functionality of the node, a network address of the node, and an identifier of the cloud network. Based on the identifier of the cloud network, cloud account details of the cloud network may be obtained from one of the multi-cloud management platform and a user input. A controller node of the cloud network may be accessed based on the cloud account details. The node may be registered at the controller node of the cloud network, based on the identification information of the node and the cloud network.

Abstract: Example techniques of migration of cloud networks between different multi-cloud management platforms, are described. In an example, a migration request is received. The migration request is indicative of a source multi-cloud management platform from which a cloud network is to be migrated to a destination multi-cloud management platform. The cloud network to be migrated from the source multi-cloud management platform to the destination multi-cloud management platform is identified based on a user input. Management platform information from the source multi-cloud management platform is obtained. The management platform information is representative of policies and data associated with the cloud network stored in databases of the source multi-cloud management platform. The cloud network is registered at the destination multi-cloud management platform. The management platform information is associated with the cloud network based on a unique identification number of the cloud network.

Abstract: The disclosure describes techniques for converting a source cloud network to a destination cloud network. In one implementation, a method includes: receiving a user request to convert a source cloud network to a destination cloud network; in response to receiving the request, invoking a driver based on the destination cloud network specified in the user request; using at least the invoked driver to retrieve cloud configuration data of the source cloud network and an operating system (OS) image of the destination cloud network; using at least the retrieved cloud configuration data of the source cloud network and the retrieved OS image of the destination cloud network, converting the source cloud network to the destination cloud network, wherein converting comprises: registering a controller and compute node of the source cloud network as a controller and compute node of the destination cloud network; and sending a notification that the conversion was completed.

Abstract: Example techniques of cloud migration are described. In an example, a migration request is received. The migration request is indicative of a destination cloud network and a compute node to be migrated from a source cloud network to the destination cloud network. A virtual machine (VM) information of the compute node is determined based on the migration request. The VM information is indicative of a VM hosted at the compute node in the source cloud network, a storage volume associated with the VM, and a network address associated with the VM. The compute node, the VM, the storage volume, and the network address are registered in the destination cloud network, based on the migration request and the VM information. The compute node, the VM, the storage volume, and the network address are deregistered from the source cloud network.