Novel tools and techniques are provided for implementing call center-based automated interface between call center agents and network orchestration systems, in some cases, via application programming interfaces (“APIs”). In various embodiments, an automated services platform may collect, from data sources, data associated with services provided by a service provider. The collected data may be autonomously analyzed to identify any issues with provisioning a service(s) to a customer. If so, one or more automation actions may be autonomously identified to address the determined issue(s). The automated services platform may autonomously send instructions to automation bots to perform the identified one or more automation actions, and may generate and present a UI on a user terminal operated by a user, the UI displaying information regarding at least one of the at least one issue, the affected service(s), the identified one or more automation actions, or the automation bots, and/or the like.

A data processing method and apparatus are disclosed. The data processing method includes: receiving, by a first edge computing node in an edge computing cluster, a container image update instruction; obtaining, by the first edge computing node, a to-be-updated container image; and sending, by the first edge computing node, the to-be-updated container image to another edge computing node in the edge computing cluster. The first edge computing node is an edge computing node in the edge computing cluster, the edge computing cluster includes at least two edge computing nodes, and the container image update instruction is used to instruct the at least two edge computing nodes in the edge computing cluster to update a container image. In this way, the time required for downloading the container image is reduced.

A semiconductor device capable of performing filter processing while suppressing an increase in processing time is provided. The semiconductor device includes a microcontroller. The microcontroller comprises a CPU, a memory and a CAN-controller. The memory stores software. The CPU executes the software stored in the memory. The CAN controller is configured to add label information to the message information. The CAN routing software stored in the memory implements a filtering function for performing a filter processing for determining whether or not to route the message information by using the label information.

An embodiment of the present disclosure includes an RPC architecture that includes a central manager gateway with a client-facing side that allows for client access via web services protocols such as SOAP and REST. The central manager gateway further includes a server-facing side that can communicate with a plurality of network elements, with each network element implementing a common IDL architecture and RPC manager instance. Each of the network elements, and in particular their RPC manager instance, may communicate with other RPC manager instances to ‘learn’ the network topology for the system and maintain a topology database for purposes of exposing a naming service, e.g., a CORBA naming service. The network elements may elect one master element while the others remain as slaves. The central manager gateway may automatically locate the master network element and forward client requests to the same for servicing.

The present disclosure describes techniques for using instances of a connector to communicate with multiple target systems without a manual pre-configuration step for each of the multiple target systems. The connector may be an extensible program-code-template for creating objects to perform one or more operations. For example, each instance of the connector may obtain information regarding a corresponding target system, determine an interface to the corresponding target system based on the information, and translate requests for the corresponding target system according to the interface.

A medical device for use in patient resuscitation and that is configured to communicate with one or more management servers includes a memory, a processor communicably coupled to the memory and configured to store device status information including device-readiness information from a medical device self-test, and store clinical event information observed by the medical device during a use of the medical device during a clinical event, the clinical event information including CPR performance data, and a communication component communicably coupled to the processor and configured to wirelessly transmit the device status information and the clinical event information to the one or more management servers, wherein the medical device includes an external defibrillator, an automated external defibrillator, or a compression assistance device.

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for determining a to-be-uploaded NSD, so as to resolve a technical problem of a relatively low network service generation efficiency. In embodiments of the present invention, multiple NSDs are pre-stored, and when an NSD needs to be uploaded, it is only required to select an appropriate NSD from the stored NSDs for uploading; and when there is a service requirement, an NSD does not need to be generated before being uploaded. Therefore, a time required for uploading an NSD is reduced, and network service generation efficiency is improved.

A method includes polling, via a service specific manager operating on a software container in a cloud infrastructure, usage of different application resources and parameters for each service of a plurality of services provided in the cloud infrastructure to yield respective polled data for each service, collating, at the service specific manager, the respective polled data for each service to yield a collation, and based on the collation, deriving a respective weight for each service which a container manager can use to create multiple instances of a new service. The method further includes communicating the respective weight for each service to the container manager and determining, via the container manager, whether to scale up or scale down container services based on the respective weight for each service.

Techniques for configuring a network based on a Domain Name System (DNS) or network metadata policy for network control are disclosed. In some embodiments, a system, process, and/or computer program product for a DNS or network metadata policy for network control includes receiving a DNS or network metadata update at a DNS server (e.g., an authoritative or recursive DNS server) or an IP Address Management (IPAM) server, in which the DNS or network metadata update is determined to be relevant to the DNS or network metadata policy for network control; and sending the DNS or network metadata update to a network controller for a network, in which the network controller configures a plurality of network devices on the network based on the DNS or network metadata policy for network control.

A system includes an orchestrator for a software-defined network and configured to receive a request for operation of the software-defined network, a software-defined network controller in communication with the orchestrator through a northbound application programming interface, at least one network element in communication with the software defined network controller though a southbound application programming interface, and a mutable network element configured to receive the request and instantiate a virtual function within the mutable network element to test the at least one network element in accordance with the request.