Intent manager entity and method in a communication network

Abstract

A method performed by an intent manager entity for determining an action to perform to fulfil a requirement in a communication network is provided. The intent manager entity performs (302) a risk assessment related to performing a proposed action to fulfil a requirement. The risk assessment is performed based an estimated characteristic related to the proposed action and a utility related to the characteristic. The intent manager entity determines (303) the action to perform based on the proposed action and the performed risk assessment.

Description

[0001] INTENT MANAGER ENTITY AND METHOD IN A COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to an intent manager entity and a method therein. In some aspects, they relate to performing risk assessments related to a proposed action.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0006] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC).

[0007] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] An intent manager framework as shown in Figure 1 is operated by one or more intents and controls one or more environments. Controlling an environment is done by observing the environment, reasoning around a combination of perceived situation and prior knowledge and taking actions on the environment. These steps together form a closed loop. The overall purpose of the intent manager is fulfilling intents.

[0010] An intent may be defined as the formal specification of all expectations including requirements, goals, and constraints given to a technical system. Examples of expectations are “At least 95% of Ultra Reliable Low Latency Communication (URLLC) users shall experience a latency of maximum 20 msec”, or “At least 80% of users of a conversational video service shall have a minimum Quality of Experience (QoE) of 4.0”, or “Energy consumption of a system shall be kept to a minimum”.

[0011] The preference of Key Performance Indicators (KPIs) for each intent is computed using a utility function which describes the benefit received when the KPI has a certain value. For example, the value of a QoE of 4.0 may have a value of 100. For lower levels of QoE the utility may reduce to zero while for higher values the utility may go up slightly. This is the case when more QoE is not as important as assuring a certain value. It is important to note that this utility is provided by the intent owner to the intent manager framework whenever a new intent is accepted. An intent management function, or intent manager, is an entity that operates an autonomous domain with intents. In its northbound interface, it receives intents, either from a human operator or from another intent manager. Its responsibility is to fulfil its received intents. It stores intents as knowledge objects, and makes autonomous decisions based on observing the managed environment. On its southbound interface, it sends intents or actions. Intent managers can be organized into hierarchies: For example, a toplevel intent manager is responsible for the end-to-end service management, while lower- level intent managers are responsible for different domains, e.g., RAN, Transport, Core, Cloud. In this hierarchy, the end-to-end intent manager breaks down intents to the domain-level intent managers.

[0012] A network driven by intents demands software capable of instantiating closed loops to fulfil the expectation expressed by the intents. In this paradigm, the intent manager is composed of the intent manager framework and software components with well-defined purposes, i.e. , agents. Agents have different roles, e.g., data grounding, action proposers, predictors, evaluators, and actuators, and are used by the intent manager to fulfil intents through the instantiation of closed loops.

[0013] Closed loops are instantiated upon the reception of new intents. Each expectation has a closed loop responsible for its fulfilment and each closed loop is composed by several agents. Agents have well-define roles and are selected by the intent manager framework using knowledge available in the knowledge base.

[0014] As depicted in Figure 1 , data grounding agents are responsible for querying the network, processing data, and storing the collected data into the knowledge base. Data grounding agents may collect raw data that describes the state of the managed environment. As an example, the data grounding agent using a user plane probe may periodically collect latency per UE as raw data, and then process it and calculate the average latency per UE for a specific period. It is the average latency per UE that is stored as a UE property in the knowledge base. The state of the managed environment is compared to the intent’s expectations.

[0015] When an expectation is not fulfilled, the intent manager creates knowledge objects called issues of type ‘cc:UnmetExpectation’. Once issues are present in the knowledge base, the cognitive core may create goals and select agents to propose solutions. Proposal agents may be as diverse as needed. They may implement many different procedures, e.g., if-then-else rules, reinforcement learning, optimization, and a mix of root cause analysis and rules, to solve the goal. Prediction agents estimate the effect of proposals on the system state before the proposed actions are potentially executed in the managed environment. With predictions available, the system estimates its impact on all active expectations.

[0016] The evaluation agent receives the estimated effect of all proposed actions in all active expectations and selects the best action. In the process, this component needs to identify conflicting actions, such as actions that improve some expectations, e.g., unmet expectations become met expectations, but degrade other expectations, e.g., met expectations become unmet expectations, and solve conflicts. Finally, with the best action selected, the actuator is triggered to implement the selected action.

[0017] SUMMARY

[0018] As a part of developing embodiments herein a problem was identified by the inventors and will first be discussed.

[0019] Prediction agents provide an estimate of the effects of an action. A proposed action triggers these agents to estimate the impact of an action on the managed environment, e.g., a wireless communication network. Current prediction agents lack the combination of a probability density function, with the utility function to accurately estimate the risk associated with the proposed action. For example, the proposal agent that proposes to minimize the power consumption, will propose to move all the UEs to the site with least power consumption. Moving all the UEs to one site will increase the load on it and may make the system unstable.

[0020] It is thus a problem how to minimize the risk of performing an action to fulfil a certain requirement.

[0021] An object of embodiments herein is to provide a mechanism handling communication, such as implementation of determining an action to perform based on a risk assessment, in an efficient manner, thereby improving the performance in the communication network.

[0022] According to an aspect of embodiments herein, the object is achieved by a method performed by an intent manager entity for determining an action to perform to fulfil a requirement in a communication network.

[0023] The intent manager entity performs a risk assessment related to performing a proposed action to fulfill a requirement. The risk assessment is performed based an estimated characteristic related to the proposed action and a utility related to the characteristic. The intent manager entity determines the action to perform based on the proposed action and the performed risk assessment.

[0024] According to another aspect of embodiments herein, the object is achieved by an intent manager entity configured to determine an action to perform to fulfil a requirement in a communication network.

[0025] The intent manager entity is configured to perform a risk assessment related to performing a proposed action to fulfill a requirement. The intent manager entity is configured to perform the risk assessment based an estimated characteristic related to the proposed action and a utility related to the characteristic.

[0026] The intent manager entity is configured to determine the action to perform based on the proposed action and the performed risk assessment.

[0027] BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0029] Figure 1 is a schematic block diagram according to prior art.

[0030] Figure 2 is a schematic block diagram illustrating embodiments of a wireless communications network.

[0031] Figure 3 is a flowchart depicting embodiments of a method in an intent manager entity.

[0032] Figure 4 is a schematic block diagram illustrating examples of embodiments herein.

[0033] Figure 5 is a diagram illustrating examples of embodiments herein.

[0034] Figure 6 is a diagram illustrating examples of embodiments herein.

[0035] Figure 7 is a schematic block diagram illustrating examples of embodiments herein.

[0036] Figure 8 is a schematic block diagram illustrating embodiments of an intent manager entity.

[0037] Figure 9 shows an example of a communication system QQ100 in accordance with some embodiments.

[0038] Figure 10 shows a UE QQ200 in accordance with some embodiments.

[0039] Figure 11 shows a network node QQ300 in accordance with some embodiments.

[0040] Figure 12 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 9, in accordance with various aspects described herein.

[0041] Figure 13 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. Figure 14 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.

[0042] DETAILED DESCRIPTION

[0043] Embodiments herein relate to risk assessment for performing an action in a communication network. As mentioned above, the object of embodiments herein is to provide a mechanism handling communication, such as implementation of determining an action to perform based on a risk assessment, in an efficient manner, thereby improving the performance in the communication network.

[0044] According to embodiments herein, a utility function may be used to determine which values of a KPI would lead to bad outcomes. This may mean that the utility function may flag certain value ranges of the KPI associated to it. By integrating a probability distribution function over these ranges, the probability of preferential and non-preferential outcomes may be determined.

[0045] This may assess a risk as a probability that non-preferential situations may occur. Instead of just preferential / non-preferential outcomes with current prediction agents, multiple levels of risk may be introduced and evaluated through integration over the respective value ranges. For example, 0.9 utility would be considered acceptable, and 0.1 utility would be considered disastrous. 1.1 would be slightly preferential and 2.0 and above can be considered high gain. This may enable to consider the severity of possible degradations and the value of preferential outcomes in the decision. Solutions with too high probability for disaster may be filtered out even if the potential gain is high.

[0046] The previous way to assess risk is also possible to do in a multi-horizon scenario, in which the risk may be computed over different periods of times. For example, the risk that a non-preferential situation may be weighted more for close periods than over further periods. This would capture the uncertainty of the future, as many intents can come and go over periods of time.

[0047] According to examples of embodiments herein, risk analysis based KPI estimation to avoid situations that may lead to bad outcomes or disastrous situations is provided. In existing systems, the prediction agent only provides the side effect on the KPIs but does not make use of the utility function to determine what could be the risk associated with the proposed action. The proposed action might not have much side effect on the KPIs immediately but may take the system to a disastrous state. Thus, including utility function along with the PDF in the prediction agents risk analysis based on KPI estimation may be performed. This may be done in different time horizons to better capture the risk over time.

[0048] Examples of embodiments herein may e.g., bring the advantage of an improved stability of a communication system since the decision to take an action is evaluated first and high-risk situations may be proactively avoided. Both for the immediate, close, and further actions over time.

[0049] Further, examples of embodiments herein may e.g., bring the advantage of an explainable communication to the intent owner on the reasons of why some actions are taken or not and possible modification of the intent target.

[0050] Embodiments herein may be implemented in communication networks, e.g., wireless communication network, in general. Figure 2 is a schematic overview depicting a communication network 100. The communication network 100 comprises one or more RANs and one or more CNs. The communication network 100 may use a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, 5G, New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations. Embodiments herein relate to recent technology trends that are of particular interest in a 5G context, however, embodiments are also applicable in further development of the existing wireless communication systems such as e.g. WCDMA and LTE, or any future wireless communication systems such as 6G.

[0051] A number of network nodes operate in the communication network 100 such as e.g. a base station 101. The base station 101 provides radio coverage in a number of cells which may also be referred to as a beam or a beam group of beams.

[0052] The base station 101 may be any of a NG-RAN node, a transmission and reception point e.g. a base station, a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), agNB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of communicating with a wireless device within the service area served by the base station 101 depending e.g. on the first radio access technology and terminology used. The base station 101 may be referred to as a serving radio network node and communicates with a wireless device with Downlink (DL) transmissions to the wireless device and Uplink (UL) transmissions from the wireless device.

[0053] In the communication network 100, one or more UEs operate, such as e.g. the one or more wireless device 102. The wireless device 102 may also referred to as a UE, a device, an Internet of Things (loT) device, a mobile station, a non-access point (non-AP) STA, a STA, a user equipment and / or a wireless terminal, communicate via one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN). It should be understood by the skilled in the art that “wireless device” is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

[0054] The communication network 100 comprises a number of intent manager entities, such as e.g., an intent manager entity 110. An intent manager entity may also be referred to as an intent manager (IM) or an intent manager function (IMF). An intent manager entity is responsible for handling intents and controlling one or more environments, such the communication network 100, or parts thereof. Controlling an environment is done by observing the environment, reasoning around the combination of perceived situation and prior knowledge and taking actions on the environment. The intent manager entity 110 may implemented as standalone network nodes, or it may be part of other nodes, such as the base station 101 , the wireless device 102, CN nodes or any other node connected to, or part of, the wireless communication network 100.

[0055] Methods herein may be performed by the intent manager entity 110. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud 190 as shown in Figure 3, may be used for performing or partly performing the methods herein.

[0056] The above described problem is addressed in a number of embodiments, some of which may be seen as alternatives, while some may be used in combination.

[0057] A method according to embodiments will now be described from the view of the intent manager entity 110 together with Figure 3. Figure 3 shows example embodiments of a method performed by the intent manager entity 110 for determining an action to perform to fulfil a requirement, e.g., in the communication network 100. The requirement may e.g., be a requirement of an intent. The method comprises the following actions, which actions may be taken in any suitable order. Actions that may be optional are presented in dashed boxes in Figure 3.

[0058] Action 301

[0059] In some embodiments, the intent manager entity 110 obtains a proposed action and an estimated characteristic. The proposed action is an action proposed to fulfil the requirement. The estimated characteristic is related to the proposed action. The estimated characteristic may comprise a PDF based estimation of the characteristic. Thus, the probability of obtaining a certain value of the characteristic when performing the proposed action may be derived from the estimated characteristic, such as the PDF based estimation of the characteristic.

[0060] In some embodiments, the estimated characteristic comprises at least two estimated characteristics.

[0061] Action 302

[0062] The intent manager entity 110 performs a risk assessment related to performing a proposed action to fulfil a requirement. The risk assessment is performed based on the estimated characteristic related to the proposed action. In other word, the intent manager entity 110 assesses the risk involved in performing the proposed action. This may e.g., mean that the risk of the ending up with an unfavourable value of the characteristic when performing the proposed action is determined. The requirement may e.g., be a requirement of an intent, which intent and / or requirement may be provided to the intent manager entity 110 by an intent owner or an entity associated with the intent and / or requirement.

[0063] In some embodiments, performing the risk assessment comprises combining a utility function associated with the estimated characteristic with a first Probability Density Function, PDF, associated with the characteristic. The utility function associated with the characteristic may comprise a function from which the utility of the characteristic may be derived. In other words, a value indicating the utility for certain value of the characteristic may be obtained from the utility function. The utility, or utility value, may, when used herein, may e.g., mean a preference, or preference value. That is, for a characteristic value the utility function gives a utility, or utility value, that shows the preference, or preference value, of said characteristic value. When combining the utility function with the PDF of the characteristic, the probability of obtaining a certain characteristic value may be obtained. This may enable to determine the risk of performing the proposed action, e.g., the probability of achieving a certain utility, or utility value, when performing the proposed action. Additionally, the probability of achieving a utility, or utility value, that is within a range of utility values may be determined. Different ranges may be determined based on the utility function and / or the requirement to fulfil. E.g., a first range indicating a preferred range, a second range indicating an acceptable range, and a third range indicating forbidden range. The utility, or utility value within the first range and / or the second range may mean that the requirement is fulfilled, while a utility, or utility value within the third range may mean that the requirement is not fulfilled.

[0064] In some embodiments, performing the risk assessment further comprises calculating a second PDF for the utility function, and wherein the second PDF is combined with the first PDF. As mentioned above, this may enable to determine the risk of performing the proposed action, e.g., the probability of achieving a certain utility, or utility value, when performing the proposed action. Additionally, the probability of achieving a utility, or utility value, that is within a range of utility values may be determined.

[0065] As mentioned above, the estimated characteristic may comprise at least two estimated characteristics. In some embodiments, performing the risk assessment comprises combining, for each estimated characteristic, a respective utility function associated with the estimated characteristic, with a respective first PDF associated with the characteristic. In other words, the utility function of a characteristic is combined with the PDF, such as the first PDF, associated with the characteristic. This is performed each of the at least two characteristics. As mentioned above, this may enable to determine the risk of performing the proposed action, e.g., the probability of achieving a certain utility, or utility value, when performing the proposed action, and / or the probability of achieving a utility, or utility value, that is within a range of utility values may be determined. Additionally, this, according to this example, this may be achieved for each of the at least two characteristics. Further, the risk assessment may comprise combining each of the utility function and first PDF combinations. By this, a combined risk assessment may be achieved, taking each of the at least two estimated characteristics into account. This may enable to determine the risk of performing the proposed action, e.g., the probability of achieving a certain utility, or utility value, when performing the proposed action, and / or the probability of achieving a utility, or utility value, that is within a range of utility values may be determined, where the risk is based on all of the at least two estimated characteristic.

[0066] In some embodiments, performing the risk assessment further comprises, for each estimated characteristic, combining the respective first PDF and a respective second PDF associated with the estimated characteristic.As mentioned above, this may enable to determine the risk of performing the proposed action, e.g., the probability of achieving a certain utility, or utility value, when performing the proposed action, and / or the probability of achieving a utility, or utility value, that is within a range of utility values may be determined. Additionally, this, according to this example, this may be achieved for each of the at least two characteristics. Or, when the first PDF and second PDF combinations are combined, this may be achieved based on all of the at least two estimated characteristics.

[0067] In some embodiments, the risk assessment may be reported, such as sent, to an intent owner, such as an entity associated with the requirement to fulfil.

[0068] Action 303

[0069] The intent manager entity 110 determines the action to perform based on the proposed action and the performed risk assessment. In other words, the intent manager entity 110 determines the action to perform by evaluating the risk of performing a proposed action based on the risk assessment. This may e.g., comprise comparing a probability of achieving a utility, or utility value that is ‘good’, such as e.g., a utility, or utility value where the requirement is fulfilled, with a probability of achieving a utility, or utility value that is ‘bad’, such as e.g., a utility, or utility value where the requirement is not fulfilled. That is, the risk of performing the proposed action is evaluated when determining the action to perform.

[0070] The above embodiments will now be further explained and exemplified below. These below embodiments may be combined with any suitable embodiment as described above.

[0071] According to examples of embodiments herein, the intent manager entity 110 may comprise a risk analysis agent that assess the risk on the KPI estimates, such as e.g., the estimated characteristic, and provides the associated risks to the evaluation agent as shown in Figure 4.

[0072] To assess the risk of a system, e.g., the communication network 100, entering a bad state, PDF based KPI estimation may be used. Figure 5 shows the PDF of a KPI.

[0073] In Figure 6, the utility function for the KPI, e.g., provided by an intent owner, shows the preference of the intent owner for this KPI. In this example, the intent, such as the first and / or one or more second requirement, is related to a QoE intent, or requirement. It may be observed that for lower values of QoE, the utility is low but for higher values of QoE the utility is high. This may be explained as the marginal utility values, that is adding more units of a given KPI, may not return the same value for the intent owner. For example, for the range 2.2 to 5.0 of QoE:

[0074] • If the utility is > 7 => good state • If the utility is >= 5 and < 7 => satisfactory state

[0075] • If the utility is < 5 => bad state

[0076] It may be observed that by keeping the target value as 3.8 for the QoE expectation, the risk associated to it is low since is likely that the system will fall in an acceptable region.

[0077] The intent manager entity 110, e.g., the risk agent in the intent manager entity 110, may use these two inputs to compute the risk analysis to identify critical regions and feasible values for the QoE, as shown in Figure 7. The risk analysis agent may use one or more of the following to perform the risk analysis, or risk assessment:

[0078] The PDF of a KPI (p(KPI)), which may e.g., be obtained from a prediction agent in the intent manager entity 110.

[0079] The utility function for the KPI.

[0080] The intent manager entity 110, e.g., the risk analysis agent in the intent manager entity 110, may perform the following any one or more of the following two steps:

[0081] Compute the PDF of the utility function with respect to a given KPI (p(0 | KPI)) which can be derived from the utility function, where 0 is the utility function for the given KPI.

[0082] Combine both the PDFs, i.e. , PDF of a KPI and the PDF of a utility function with respect to the KPI, as f = p(0 | KPI) * p(KPI), where p(KPI) is the PDF of the KPI. In some examples, the PDF of the KPI may be combined with the utility function 0 as f = 0 * p(KPI).

[0083] Thus, risk analysis-based predictions may enable the identification of if the communication network 100 may end up in a bad state or good state given an proposed action. That is, in a region which may compromise any of the KPIs to be fulfilled by the intent manager entity 110 for all the intents it has accepted so far.

[0084] Thus, the risk analysis may enable the intent manager entity 110 to take actions that would not impact the utility. Hence, an action proposed will be evaluated based on not only the predicted state but also its associated risk.

[0085] In the previous example, the intent manager entity 110 considers only one intent, such as requirement, with a single KPI, such as the first characteristic, for the intent’s expectation. However, in more realistic scenarios there may be many intents with multiple KPIs for each one. Moreover, when a KPI is not fulfilled, i.e., the current value is lower than the one described in the intent, there may be multiple actions to solve the issues. This may lead to multiple proposal agents that propose different actions. Some of these actions may propose conflicting solutions for the KPIs, thus the goal of the prediction agent and the risk analysis agent is to find the best possible action that maximizes the value for the intent manager entity 110, without putting it in critical regions. In other words, the intent manager entity 110 would like to compute its overall utility.

[0086] The overall utility of the system, such as the communication network 100, captures the value for the entire given the intents the intent manager entity 100 is currently managing. This may mean that a greater utility is preferred over a lesser utility. In other words, the intent manager entity 100 may continuously try to maximize the overall utility. However, in certain scenarios, certain actions that are predicted to bring higher utilities may put the system in critical regions. Thus, it may be necessary to compute and consider the overall utility with the risks associated to each action. Hence, once we identify the risk associated zones for each of the KPI. The next step is to aggregate the identified risks and associated ranges into a single distribution that captures the overall utility.

[0087] To compute the overall utility, the Bayesian model may be used to combine different probability distributions for different KPIs into a single distribution.

[0088] Consider, fi, f2, ... , fnas probability distribution over utility with respect to each KPI that tells us probability of utility lying in a state, for example, good, bad or satisfactory, and is represented as: fi = p(0i | KPh) * p(KPh), where 01 is the utility function of the system with respect to KPh, p(KPh) is the PDF of KPh, and p(0i | KPh) is the PDF of the utility function 01 with respect to KPh..

[0089] To compute the joint probability distribution of utility with respect to all the KPIs, it can be computed as: p lf) = p(Ql\KPIl) * p(KPIl) * ... * p(0n \KPIri) * p(KPIn)

[0090] If the utility function is the same for each KPI, i.e, 01 = 02 = ... = 0n= 0; then, the joint probability distribution may be computed as: p([ / ) = p(Q\KPIl, ... ,KPIri) * p(KPI ) * p(KPP2.) * ... * p(KPIn)

[0091] This joint probability distribution can be learned with different methods such as

[0092] Maximum A Posteriori method and Maximum Likelihood Estimations which can be further combined with Monte Carlo simulations, and variational inferencing for approximations if the joint probability distribution is a complex function [4],

[0093] Once p(U) has been computed, the distribution can be sent to the evaluation agent which will decide which action to take based on the multiple p(U) generated by the multiple proposals to fulfill the intent’s KPIs.

[0094] Moreover, this risk may also be reported back to the intent owner, thus, can extend the current standards by:

[0095] • Adding the capability of exposure of risk to intent owners during an intent registration operation.

[0096] • Extend the periodic reporting from the intent handler to the intent owner to communicate the risk based on the utility. The intent owner would decide if the intent would continue as it or if an update is necessary. To facilitate the decision, the information sent would consider risk zones such as the ones explained in Figure 6.

[0097] To perform the method actions above, the intent manager entity 110 is determining an action to perform to fulfil a requirement in the communication network 100. The intent manager entity 110 may comprise an arrangement depicted in Figure 8.

[0098] The intent manager entity 110 may comprise an input and output interface 800 configured to communicate with each other. The input and output interface 800 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0099] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 860 of a processing circuitry in the intent manager entity 110 depicted in Figure 8, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the intent manager entity 110. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the intent manager entity 110.

[0100] The intent manager entity 110 and / or processor 860 is configured to determine an action to perform to fulfil a requirement in the communication network 100. The intent manager entity 110 and / or processor 860 is configured to perform a risk assessment related to performing a proposed action to fulfil a requirement. The intent manager entity 110 and / or processor 860 is configured to perform the risk assessment based an estimated characteristic related to the proposed action and a utility related to the characteristic.

[0101] The intent manager entity 110 and / or processor 860 is configured to determine the action to perform based on the proposed action and the performed risk assessment.

[0102] In some embodiments, the intent manager entity 110 and / or processor 860 may further be configured to perform the risk assessment by combining the utility function associated with the estimated characteristic with a first PDF associated with the characteristic.

[0103] In some embodiments, the intent manager entity 110 and / or processor 860 may further be configured to perform the risk assessment by further calculating a second PDF for the utility function, and wherein the second PDF is combined with the first PDF.

[0104] In some embodiments, the estimated characteristic is adapted to comprise at least two estimated characteristics.

[0105] In some embodiments, the intent manager entity 110 and / or processor 860 may further be configured to perform the risk assessment by combining, for each estimated characteristic, a respective utility function associated with the estimated characteristic, with a respective first PDF associated with the estimated characteristic.

[0106] In some embodiments, the intent manager entity 110 and / or processor 860 may further be configured to perform the risk assessment by further, for each estimated characteristic, calculating a second PDF for the utility function associated with the estimated characteristic, and wherein, for each estimated characteristic, the second PDF is combined with the first PDF.

[0107] In some embodiments, the intent manager entity 110 and / or processor 860 may further be configured to obtain the proposed action and the estimated characteristic.

[0108] The intent manager entity 110 may further comprise a memory 870 comprising one or more memory units. The memory 870 comprises instructions executable by the processor 860 in the intent manager entity 110. The memory 870 is arranged to be used to store e.g. intents, actions, characteristics, risk assessments, utility functions, utilities, PDFs, data, configurations, and applications to perform the methods herein when being executed in the intent manager entity 110. In some embodiments, a computer program 880 comprises instructions, which when executed by the respective at least one processor 860, cause the at least one processor 860 of the intent manager entity 110 to perform the actions above.

[0109] In some embodiments, a respective carrier 890 comprises the respective computer program 880, wherein the carrier 890 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0110] Thus, embodiments herein may disclose the intent manager entity 110 configured to determine an action to perform to fulfil a requirement in the communication network 100. The intent manager entity 110 comprises the processor 860 and the memory 870, said memory 870 comprising instructions executable by said processor 860 whereby said intent manager entity 110 is operative to perform any of the methods herein.

[0111] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a base station, for example.

[0112] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and nonvolatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0113] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0114] ADDITIONAL EXPLANATION

[0115] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0116] Figure 9 shows an example of a communication system QQ100 in accordance with some embodiments.

[0117] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108 (being examples of the base station 110). The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110 being examples of the base station 110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108. Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O- CLI-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112 being examples of the wireless device 121) to the core network QQ106 over one or more wireless connections.

[0118] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0119] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0120] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), Subscription Identifier Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0121] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0122] As a whole, the communication system QQ100 of Figure 9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0123] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0124] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi- RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0125] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0126] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0127] Figure 10 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0128] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0129] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure QQ2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0130] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0131] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0132] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0133] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0134] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0135] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0136] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0137] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0138] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smartwatch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure QQ2.

[0139] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0140] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0141] Figure 11 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O- RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0142] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0143] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0144] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0145] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0146] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0147] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0148] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0149] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0150] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0151] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0152] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0153] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0154] Figure 12 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure QQ1, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0155] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 14 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0156] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. Figure 13 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O- Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0157] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0158] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0159] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0160] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0161] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0162] Figure 14 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 9 and / or UE QQ200 of Figure QQ2), network node (such as network node QQ110a of Figure 9 and / or network node QQ300 of Figure QQ3), and host (such as host QQ116 of Figure 9 and / or host QQ400 of Figure 12) discussed in the preceding paragraphs will now be described with reference to Figure 14. Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0163] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure QQ1) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0164] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0165] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0166] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0167] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0168] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment.

[0169] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0170] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0171] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0172] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0173] When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of".

[0174] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

CLAIMS1. A method performed by an intent manager entity (110) for determining an action to perform to fulfil a requirement in a communication network (100), the method comprising: performing (302) a risk assessment related to performing a proposed action to fulfill a requirement, wherein the risk assessment is performed based an estimated characteristic related to the proposed action and a utility related to the characteristic, determining (303) the action to perform based on the proposed action and the performed risk assessment.

2. The method according to claim 1, wherein performing (302) the risk assessment comprises combining the utility function associated with the estimated characteristic with a first Probability Density Function, PDF, associated with the characteristic.

3. The method according to claim 2, wherein performing (302) the risk assessment further comprises calculating a second PDF for the utility function, and wherein the second PDF is combined with the first PDF.

4. The method according to any of claims 1-3, wherein the estimated characteristic comprises at least two estimated characteristics.

5. The method according to claim 4, wherein performing (302) the risk assessment comprises combining, for each estimated characteristic, a respective utility function associated with the estimated characteristic, with a respective first PDF associated with the estimated characteristic.

6. The method according to claim 5, wherein performing (302) the risk assessment further comprises, for each estimated characteristic, calculating a second PDF for the utility function associated with the estimated characteristic, and wherein, for each estimated characteristic, the second PDF is combined with the first PDF.

7. The method according to any of claims 1-6, wherein the method further comprises: obtaining (301) the proposed action and the estimated characteristic.

8. A computer program (880) comprising instructions, which when executed by a processor (860), causes the processor (860) to perform actions according to any of the claims 1-7.

9. A carrier (890) comprising the computer program (880) of claim 8, wherein the carrier (890) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

10. An intent manager entity (110) configured to determine an action to perform to fulfil a requirement in a communication network (100), the intent manager entity (110) further being configured to: perform a risk assessment related to performing a proposed action to fulfill a requirement, wherein the intent manager entity (110) is configured to perform the risk assessment based an estimated characteristic related to the proposed action and a utility related to the characteristic, determine the action to perform based on the proposed action and the performed risk assessment.

11. The intent manager entity (110) according to claim 10, wherein the intent manager entity (110) is configured to perform the risk assessment by combining the utility function associated with the estimated characteristic with a first Probability Density Function, PDF, associated with the characteristic.

12. The intent manager entity (110) according to claim 11 , wherein the intent manager entity (110) is configured to perform the risk assessment by further calculating a second PDF for the utility function, and wherein the second PDF is combined with the first PDF.

13. The intent manager entity (110) according to any of claims 10-12, wherein the estimated characteristic is adapted to comprise at least two estimated characteristics.

14. The intent manager entity (110) according to claim 13, wherein the intent manager entity (110) is configured to perform the risk assessment by combining, for each estimated characteristic, a respective utility function associated with the estimated characteristic, with a respective first PDF associated with the estimated characteristic.

15. The intent manager entity (110) according to claim 14, wherein the intent manager entity (110) is configured to perform the risk assessment by further, for each estimated characteristic, calculating a second PDF for the utility function associated with the estimated characteristic, and wherein, for each estimated characteristic, the second PDF is combined with the first PDF.

16. The intent manager entity (110) according to any of claims 10-15, wherein the intent manager entity (110) is further configured to: obtain the proposed action and the estimated characteristic.

Images