The present invention faces the issues of re-selection of another NF Service instance (103, 201) for a subsequent request (S-520, S-535) with a same data consistency (Consistency 1) as a previously selected NF Service instance (101). To solve this issue, the present invention provides for identifying at configuration, based on the deployment and on the Storage solution for the Session/context data, which instances (101, 103, 201) of the same service type have access with strong consistency to the same data, and provide this information to the consumer (40), so it is allowed to prioritize selection of an alternative NF service instance that supports strong consistency, whenever possible.

A registration method, a session establishment method, a terminal, and an access and mobility management function (AMF) entity, where the method includes: sending, by a terminal, a first message to the AMF entity, where the first message includes first information, first network slice selection information, and second network slice selection information, the first information includes information for requesting to establish a protocol data unit (PDU) session, the first network slice selection information is used by the AMF entity to select a first session management function (SMF) entity, and the second network slice selection information is used by the AMF entity to select a second SMF entity; and receiving, by the terminal, a second message from the AMF entity, where the second message includes second information, and the second information includes PDU session establishment accept information.

A registration method, a session establishment method, a terminal, and an access and mobility management function (AMF) entity, where the method includes: sending, by a terminal, a first message to the AMF entity, where the first message includes first information, first network slice selection information, and second network slice selection information, the first information includes information for requesting to establish a protocol data unit (PDU) session, the first network slice selection information is used by the AMF entity to select a first session management function (SMF) entity, and the second network slice selection information is used by the AMF entity to select a second SMF entity; and receiving, by the terminal, a second message from the AMF entity, where the second message includes second information, and the second information includes PDU session establishment accept information.

A computer manages reconfigurations of a Byzantine fault-tolerant, distributed computing system comprising a network of first nodes adhering to a given consensus protocol at a reconfiguration service. The computer services the network by receiving a request of change of status of a second node with respect to the network. The computer informs at least a subset of the first nodes of the received request. The computer obtains an approval of the request, whereby at least a subset of the first nodes collectively approve the change of status as a result of contributions processed according to the given consensus protocol. The computer updates a configuration log according to request approvals obtained by servicing the network. The computer addresses requests of clients about configurations of the network based on the updated configuration log.

Various examples for discovering policy bindings between group policy rules in a legacy management framework and unified endpoint management rules that are utilized in a modern mobile device management (MDM) device management framework. A configuration state view can allow an administrator to understand inconsistencies or conflicts between group policy rules and UEM rules.

There are provided measures for enabling/realizing inference-aware ML (machine learning) model provisioning, e.g. to support network data analytics, in a mobile/wireless communication system. Such measures exemplarily comprise that ML model request information, including model-related information indicating one or more properties of a requested ML model and inference-related information indicating one or more properties of execution of inference based on the requested ML model, is provided from a first network entity (representing a service consumer of a network data analytics service) to a second network entity (representing a service provider of the network data analytics service), the second network entity specifies an ML model to be provisioned based on the ML model request information, and ML model information about the specified ML model is provided from the second network entity to the first network entity.

Systems and methods include creating a graph of a network having i) vertices representing ports, and ii) edges representing possible connections between vertices; receiving a request for one or more paths in the network; traversing the graph to determine the one or more paths; responsive to encountering a non-local constraint in the graph, adding a traversal state based thereon; and responsive to satisfying the non-local constraint in the graph, removing the traversal state based thereon.

A system and a method of establishing seamless remote access VPN connections are described. For establishment of a VPN connection for a user device, a cluster leader of a cluster of controllers identifies an active controller and a standby controller, based on network load of each controller of the cluster of controllers. An active VPN connection is established between the user device and the active controller and a standby VPN connection is established between the user device and the standby controller. The standby VPN connection is utilized in place of the active VPN connection during failover of the active controller. Because information of an active session is regularly shared by the active controller to the standby controller, the standby controller can seamlessly resume the active session during failover of the active controller.

Some embodiments provide a method of migrating a first software defined (SD) network managed by a first network manager to a second SD network managed by a second network manager. The method of some embodiments is performed by a third network manager that provides an interface that allows a set of users to specify and review logical network components, which the first and second network managers can then respectively deploy in the first and second SD networks. The third network manager in some embodiments identifies for a migration manager a first group of two or more logical network components that the third network manager previously specified for the first network manager to deploy in the first SD network. The migration manager then uses this information to correctly convert the first group of logical network components to a second group of two or more logical components in an appropriate manner that will allow the third network manager to manage the second group of logical network components that is implemented in the second SD network.

A computational instance may includes a set of computing devices and a configuration management database (CMDB), wherein the CMDB contains a representation of a service deployed on a managed network, wherein the representation of the service includes metadata, service group membership, and an entry point, and wherein the computational instance is configured to: receive an instruction to export the representation of the service to a file; copy, to a metadata object in the file, the metadata; determine a hierarchical subset of the service groups that are related to the service; write, to one or more service group objects in the file, the hierarchical subset of the service groups; determine, from a list of entry points of the managed network, that the entry point is of the service; and write, to an entry point object in the file, the entry point.