Embodiments of this application disclose a data transmission system, including an over the air OTA server, a master electronic control unit ECU, and a node ECU. The master ECU is configured to obtain a size of a target software package from the OTA server. The master ECU is further configured to transmit to a node ECU, the size of the target software package, or obtain a size of a remaining storage space of the node ECU from the node ECU.

There is provided a method of operating a Service Communication Proxy, SCP, node (608, 1000) in a communication network as a proxy network repository function, NRF, for a first network function, NF, producer node in the communication network. The first NF producer node (602, 1100) is to migrate from a direct communication mode with a first NF consumer node (606) to an indirect communication mode with the first NF consumer node (606) via the SCP node (608, 1000). The SCP node (608, 1000) discovers a NF profile for the first NF producer node (602, 1100), wherein the NF profile for the first NF producer node (602, 1100) is stored by a first network repository function, NRF, node (604) in the communication network, and the NF profile comprises a service address for the first NF producer node (602, 1100); receives a registration request from the first NF producer node (602, 1100), wherein the registration request is a request to register a NF profile for the first NF producer node (602, 1100) at a NRF node (604), wherein the registration request indicates the service address for the first NF producer node (602, 1100); and, in response to the received registration request, sends an update request to the first NRF node (604) to update the NF profile for the first NF producer node (602, 1100) stored by the first NRF node (604) to replace the service address of the first NF producer node (602, 1100) with a first service address of the SCP node (608, 1000) that is associated with the service address of the first NF producer node (602, 1100).

There is provided a method of operating a Service Communication Proxy, SCP, node (608, 1000) in a communication network as a proxy network repository function, NRF, for a first network function, NF, producer node in the communication network. The first NF producer node (602, 1100) is to migrate from a direct communication mode with a first NF consumer node (606) to an indirect communication mode with the first NF consumer node (606) via the SCP node (608, 1000). The SCP node (608, 1000) discovers a NF profile for the first NF producer node (602, 1100), wherein the NF profile for the first NF producer node (602, 1100) is stored by a first network repository function, NRF, node (604) in the communication network, and the NF profile comprises a service address for the first NF producer node (602, 1100); receives a registration request from the first NF producer node (602, 1100), wherein the registration request is a request to register a NF profile for the first NF producer node (602, 1100) at a NRF node (604), wherein the registration request indicates the service address for the first NF producer node (602, 1100); and, in response to the received registration request, sends an update request to the first NRF node (604) to update the NF profile for the first NF producer node (602, 1100) stored by the first NRF node (604) to replace the service address of the first NF producer node (602, 1100) with a first service address of the SCP node (608, 1000) that is associated with the service address of the first NF producer node (602, 1100).

A method for receiving firmware including pieces of firmware data is provided. The method is performed by a first apparatus in a multicast group including at least the first apparatus and a second apparatus. The method includes (a) receiving first meta-information for the firmware data from the second apparatus, (b) generating, based on the first meta-information, second meta-information for at least one piece of firmware data to be used to apply the firmware to the first apparatus, among the firmware data, and (c) receiving, based on the second meta-information, the at least one piece of firmware data from a firmware providing apparatus or the second apparatus. The first meta-information includes at least history information including version and partitioning information for each of the pieces of firmware data, and the second meta-information includes at least the history information for each of the at least one piece of firmware data.

Disclosed herein is a system for automating the causality detection process when upgrades are deployed to different resources that provide a service. The resources can include physical and/or virtual resources (e.g., processing, storage, and/or networking resources) that are divided into different, geographically dispersed, resource units. To determine whether a root cause of a problem is associated with an upgrade event that has recently been deployed, a system is configured to use telemetry data to compute an upgrade-to-upgrade score that represents differences between two different upgrade events that are deployed to the same resource unit. The system is further configured to use telemetry data to compute an upgrade unit-to-unit score that represents differences between the same upgrade event being deployed to two different resource units. The scores can be used to output an alert, for an analyst, that signals whether a recently deployed upgrade event is the cause of a problem.

Examples described here include systems and methods for configuring device settings for a number of user devices across an enterprise. A management server can provide a user interface at an administrator console for creating a profile and identifying an associated device type. The management server can then retrieve a schema file associated with the device type. Based on information in the schema file, the management server can populate the user interface at the administrator console with available configuration options pertaining to the device type. An administrator can configure the options and send instructions to the management server to deploy the profile across the number of user devices. The management server can instruct each user device to download a device configuration application from an application repository and transmit the settings information to an agent application of the user device that has permission to configure the device configuration application.

Examples described here include systems and methods for configuring device settings for a number of user devices across an enterprise. A management server can provide a user interface at an administrator console for creating a profile and identifying an associated device type. The management server can then retrieve a schema file associated with the device type. Based on information in the schema file, the management server can populate the user interface at the administrator console with available configuration options pertaining to the device type. An administrator can configure the options and send instructions to the management server to deploy the profile across the number of user devices. The management server can instruct each user device to download a device configuration application from an application repository and transmit the settings information to an agent application of the user device that has permission to configure the device configuration application.

Systems, methods and/or computer program products for managing and dynamically automating service mesh communications between microservices, eliminating unnecessary exposure of microservice ports and increasing security between microservices of the service mesh. The control plane collects data describing communications between microservices and tracks the frequency at which microservices communicate. Collected data is fed to machine learning models which outputs a forecast predicting future communication interactions between microservices. Using the predicted requirements for facilitating communications between microservices of the service mesh, an allowed list of communications can be generated describing the microservices allowed to send and receive communications, duration of communications allowed, when such communications are allowed, and the ports that will be used for facilitating the communication between microservices. Administrators of the service mesh may manually override the one or more approved aspects of the dynamically generated allowed list configured automatically by the service mesh.

The invention is notably directed to a method, computer program product, and computer system for running software inside containers. The method relies on a computerized system that includes a composable disaggregated infrastructure, in addition to general-purpose hardware. The computerized system is configured to dynamically allocate computerized resources, which include both general resources and specialized resources. The former are enabled by the general-purpose hardware, while the latter are enabled by specialized network-attached hardware components of the composable disaggregated infrastructure. The method maintains a table capturing specializations of the specialized network-attached hardware components. At runtime, software is run inside each container by executing corresponding functions. A first subset of the functions are executed using the general resources, whereas a second subset of the functions are executed using the specialized resources, by offloading the second subset of functions to respective components of the specialized network-attached hardware components, in accordance with the specializations.

The invention is notably directed to a method, computer program product, and computer system for running software inside containers. The method relies on a computerized system that includes a composable disaggregated infrastructure, in addition to general-purpose hardware. The computerized system is configured to dynamically allocate computerized resources, which include both general resources and specialized resources. The former are enabled by the general-purpose hardware, while the latter are enabled by specialized network-attached hardware components of the composable disaggregated infrastructure. The method maintains a table capturing specializations of the specialized network-attached hardware components. At runtime, software is run inside each container by executing corresponding functions. A first subset of the functions are executed using the general resources, whereas a second subset of the functions are executed using the specialized resources, by offloading the second subset of functions to respective components of the specialized network-attached hardware components, in accordance with the specializations.