Telefonaktiebolaget Lm Ericsson (publ)

Chunyan Fu

Wolfgang John

Roch Glitho

Joacim Halén

Ramamurthy Badrinath

Mina Sedaghat

Rachida Dssouli

James Kempf

Catalin Meirosu

Leonid Mokrushin

Aneta Vulgarakis Feljan

Farnaz Moradi

Klaus Raizer

Embodiments herein relate to a method performed by a network node () for handling monitoring of applications and/or services in a communication network. The network node () obtains an indication associated with a monitoring session to monitor a metric of a service and/or application; and also obtains a location of deployment of the service and/or application. The network node identifies one or more ongoing monitoring sessions for monitoring one or more metrics based on the metric associated with the indication and the location of deployment of the application or service. The network node () then selects a monitoring process based on the identification; and triggers the selected monitoring process.

Network node, monitoring node and methods performed therein

A method for allocating resources to applications in a distributed datacenter based on generated contact lists is described. The method includes, receiving, by a first resource manager, a placement request, which identifies resources needed for execution of an application; determining a policy associated with the application; generating a first contact list for the first resource manager based on the determined policy for the application; and searching resources in the distributed datacenter, based on the first contact list, to attempt to meet the identified resources of the placement request.

Adaptive application assignment to distributed cloud resources

A method for placement of processes in a distributed datacenter is described. The method includes receiving, by a first placement node, a placement request corresponding to a process; determining a load estimation for resources managed by the first placement node and a demand estimation for the process based on a process execution profile for the process; determining whether the placement request can be fulfilled with the resources managed by the first placement node based on the demand estimation of the process and the load estimation of the resources managed by the first placement node; executing the process with the resources managed by the first placement node in response to determining that the placement request can be fulfilled with the resources managed by the first placement node; generating an intermediate score based on the execution; and updating a performance score of the process execution profile based on the intermediate score.

Process placement in a cloud environment based on automatically optimized placement policies and process execution profiles

A method and a communication device for determining a score relating to a first agent module are described. The communication device receives information relating to at least one request, performed by another agent module separate from the first agent module, for consumption of a capability of the first agent module. The information relating to the at least one request includes information about the capability of the first agent module, information about an intention of the first agent module, and information about a policy for the capability. The communication device calculates the score in relation to the first agent module based on the information relating to the at least one request, wherein the score further is specified with respect to the capability.

Method and communication device for determining a score relating to a first agent module

Mechanisms for path continuity determination in an aggregate flow environment. An ingress node and a downstream node for which a path continuity check is desired are determined. The ingress node devolves, from an aggregate flow entry, one or more microflows that comprise packets which are destined for the downstream node. The downstream node is directed to generate corresponding microflows. Each microflow is associated with a continuity set identifier and has one or more timers, such as an idle timer and/or a hard timeout timer. Upon timeout of one of the timers, the ingress node and the downstream node send a microflow termination message that contains the continuity set identifier to a controller node. The controller node determines a path continuity status between the ingress node and the downstream node based on a receipt of one or more microflow termination messages from the ingress node and the downstream node.

Path continuity determination in an aggregate flow environment

A cluster of terminals, and an ad-hoc network of two or more such clusters, for carrying a multi-party, cluster-based, conference, wherein each cluster includes a super member comprising a super user agent, and one or more members including a user agent. Communications sessions are established between the super member of each cluster and each member terminals of the same cluster, and between the super members of each one of the first and second clusters. The user agent comprises identity of the super member, a conference identity, cluster parameters including a split value (Sv) indicative of a maximum number of terminals that may be part of the cluster, wherein when Sv is reached during the conference the cluster is split, and a merge value (Mv) indicative of a minimum number of terminals that may be part of the cluster, wherein when Mv is reached the cluster is merged with another cluster. The super user agent comprises a cluster member list, the conference identity, a cluster neighbour list, the one or more terminals also participating to the same conference, and cluster parameters.

Cluster of terminals and ad-hoc network for cluster-based multi-party conferencing

Methods for establishing a cluster-based multi-party conference and for carrying on the conference as participants join or leave the conference are provided. First, two or more terminals participating to the conference are joined in a cluster, wherein one of them is elected as a super member of the cluster. The other terminal is updated with the identity of the super member terminal, the identification of the conference, and with cluster parameters including a split value Sv indicative of a maximum number of terminals that may be part of the cluster, wherein when the split value Sv is reached during the conference, the cluster is split; and a merge value Mv indicative of a minimum number of terminals that may be part of the cluster, wherein when the merge value Mv is reached during the conference, the cluster is merged with another cluster. A method for splitting the cluster, and a method for merging two clusters are also provided.

Growing community of inventors

Pointe-Claire, Canada

Chunyan Fu