Patent classifications
H04L41/5041
NETWORK DEVICES
A network administration device may include one or more processors to receive operational information regarding a plurality of network devices; receive flow information relating to at least one traffic flow; input the flow information to a model, where the model is generated based on a machine learning technique, and where the model is configured to identify predicted performance information of one or more network devices with regard to the at least one traffic flow based on the operational information; determine path information for the at least one traffic flow with regard to the one or more network devices based on the predicted performance information; and/or configure the one or more network devices to implement the path information for the traffic flow.
Code Activation Management Method for Network Slicing Solutions, and Corresponding Entity, Server and Computer Program
Methods and apparatuses in the field of network slice management are disclosed. A method of managing, by means of an activation code management server (100), a plurality of activation codes (511 562) in a network includes steps of: providing (S31), for each of a plurality of network slices, a network slice identifier (570) in correspondence with a network slice; providing (S32) at least one VNF-product identifier (580), each VNF-product identifier (580) being in correspondence with a VNF; providing (S33) a plurality of activation code indicators (510, 520, 530, 540, 550, 560), each activation code indicator (510, 520, 530, 540, 550, 560 being indicative of one or more of the plurality of activation codes (511 562); and associating each of the plurality of activation code indicators (510, 520, 530, 540, 550, 560) with a corresponding network slice identifier (570) and a corresponding VNF-product identifier (580).
DISTRIBUTED COMPUTATION ORCHESTRATION FOR INTERNET-OF-THINGS DEVICES USING COAP AND LWM2M PROTOCOLS
An IoT electronic device executes services distributed by an IoT service orchestration device. A Lightweight Machine-to-Machine (LwM2M) request message is received. The LwM2M request message contains a LwM2M object identifying hardware resources of the IoT electronic device for which characteristics are requested. A LwM2M command is executed that accesses a LwM2M interface identified based on content of the LwM2M object to determine the characteristics of the hardware resources of the IoT electronic device which are identified by the LwM2M object. A response message contains information identifying the characteristics of the hardware resources of the IoT electronic device. The response message is communicated toward the IoT service orchestrator device. A service image is received for execution which is adapted by the IoT service orchestrator device, responsive to the information in the response message identifying the characteristics of the hardware resources of the IoT electronic device.
Request facilitation for approaching consensus for a service transaction
One or more systems, computer-implemented methods, and computer program products to facilitate a process for consensus regarding proceeding with a request of a transaction are provided. A system can comprise a memory that stores computer executable components and a processor that executes the computer executable components stored in the memory. The computer executable components can comprise a services component that operates a service of a transaction, where the services component approaches consensus regarding a request of the transaction by communicating with one or more other services components that operate one or more other services immediately upstream or downstream in the transaction to the service. The services component can approach the consensus by communicating only with the one or more other services components. To approach the consensus, the services component can communicate one or more messages that include one or more requests, votes or final decisions.
Method, Apparatus, and System for Sending Control Request Based on Key Value Configuration
A method, an apparatus, and a system for sending a control request based on a key value configuration. The method includes generating, by a client controller, a control request, wherein having a plurality of configuration parameters, wherein the plurality of configuration parameters comprise a flexible key value, a control object name, and a universally unique identifier (UUID), where the flexible key value identifies a requested control object, and the flexible key value is determined using at least one of the control object name or the UUID, and sending, by the client controller, the control request to a server controller, where the control request indicates to the server controller to configure the control object.
Context based firewall service for agentless machines
A system and method for performing firewall operations on an edge service gateway virtual machine that monitors traffic for a network. The method includes detecting, from a directory service executing on a computing device, a login event on the computing device, obtaining, from the detected login event, login event information comprising an identifier that identifies a user associated with the login event, storing the login event information as one or more context attributes in an attribute table, and applying a firewall rule to a data message that corresponds to the one or more context attributes.
Context based firewall service for agentless machines
A system and method for performing firewall operations on an edge service gateway virtual machine that monitors traffic for a network. The method includes detecting, from a directory service executing on a computing device, a login event on the computing device, obtaining, from the detected login event, login event information comprising an identifier that identifies a user associated with the login event, storing the login event information as one or more context attributes in an attribute table, and applying a firewall rule to a data message that corresponds to the one or more context attributes.
Requesting flexible user-plane services in a service-based architecture
Embodiments of a method of operation of a service requestor to request a service from a chain controller in a cellular communications network in which a user plane function is decomposed into a plurality of micro user plane functions are disclosed. In some embodiments, the method comprises sending, to the chain controller, a service description or a request to update a service description. The service description comprises one or more service template instances having respective service template definitions. Each service template definition of the respective service template definitions being data that defines a set of micro user plane functions that realize a service or a part of a service. Each service template instance of the one or more service template instances comprises data that defines a reference to the respective service template definition. The method further comprises receiving a reply from the chain controller.
Cloud infrastructure planning assistant via multi-agent AI
Cloud infrastructure planning systems and methods can utilize artificial intelligence/machine learning agents for developing a plan of demand, plan of record, plan of execution, and plan of availability for developing cloud infrastructure plans that are more precise and accurate, and that learn from previous planning and deployments. Some agents include one or more of supervised, unsupervised, and reinforcement machine learning to develop accurate predictions and perform self-tuning alone or in conjunction with other agents.
Network function virtualization compute element image upgrade
A network function virtualization (NFV) compute element installs an image supporting a virtualized network function (VNF) on the element. The image includes instructions/data to initiate a TCP connection between the element and a Software Defined Network (SDN) controller upon reboot of the element. Upon rebooting, the element establishes, as client in accordance with the instructions/data, a TCP connection with the controller. The element then accepts, as a cryptographic network protocol server, a connection via the TCP connection from the controller as a client in accordance with the instructions. Next, the element accepts, as a network management protocol server, a connection via the cryptographic network protocol connection from the controller as network management protocol client. The element receives, from the controller over the network management protocol connection, commands regarding the status of the rebooted element, and then transmits, to the controller over the network management protocol connection, responses to the commands.