Intent based networking in a wireless communication system

Abstract

Various aspects of the present disclosure relate to a first network entity for wireless communication. The first network entity may be configured to, capable of, or operable to receive, from an application consumer, an intent service request; transmit, to a second network entity, a resolution request for resolving a feasibility issue for supporting the intent service request; and receive, from the second network entity, a resolution response.

Description

INTENT BASED NETWORKING IN A WIRELESS COMMUNICATIONSYSTEMTECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, including the intent based networking.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise knowns as network equipment (NE) supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and aDocket No. SMM920250137-GR-NPcondition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] The following abbreviations are relevant in the field addressed by this document: Analytical Data Repository Function (ADRF); Analytics Logical Function (AnLF); Application Function (AF); Application Programming Interface (API); Artificial Intelligence / Machine Learning (AI / ML); Binding Support Function (BSF); Configuration Management (CM); Data Collection Coordination Functionality (DCCF); Data Network Name (DNN); Identity (ID); Intent Based Networks (IBN); Internet Engineering Task Force (IETF); Internet of Things (IoT); Key Performance Indicator (KPI); Management Data Analytics (MDA); Management Function (MF); Management Service (MnS);Messaging Framework Adaptor Function (MFAF); Mobile Network Operator (MNO); Model Training Logical Function (MTLF); Network Data Analytics Function (NWDAF); Network Exposure Function (NEF); Network Function (NF); Network Functions Virtualization Orchestrator (NFVO); Network Repository Function (NRF); Operations, Administration and Maintenance (0AM); Performance Measurement (PM); Policy Control Function (PCF); Protocol Data Unit (PDU); Public Land Mobile Network (PLMN); Quality of Experience (QoE); Quality of Service (QoS); Radio Access Network (RAN);Reinforcement Learning (RL); Service Based Agreement (SLA); Session Management Function (SMF); Single - Network Slice Selection Assistance Information (S-NSSAI); 5th Generation of Mobile Communications (5G); 6th Generation of Mobile Communications (6G); User Data Manager (UDM); User Data Repository (UDR); User Equipment (UE); Virtual Machine (VM); Virtualised Network Function (VNF).

[0005] A first network entity for wireless communication is described. The first network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from an application consumer, an intent service request; transmit, to a second network entity, a resolution request forDocket No. SMM920250137-GR-NPresolving a feasibility issue for supporting the intent service request; and receive, from the second network entity, a resolution response.

[0006] A method performed or performable by the first network entity is described herein. The method may comprise receiving, from an application consumer, an intent service request; transmitting, to a second network entity, a resolution request for resolving a feasibility issue for supporting the intent service request; and receiving, from the second network entity, a resolution response.

[0007] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive, from an application consumer, an intent service request; transmit, to a second network entity, a resolution request for resolving a feasibility issue for supporting the intent service request; and receive, from the second network entity, a resolution response.

[0008] A second network entity for wireless communication is described. The second network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the second network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the second network entity to: receive, from a first network entity, a resolution request for resolving the feasibility issue, wherein the feasibility issue is for supporting an intent service request; and transmit, to the first network entity, a resolution response.

[0009] A method performed or performable by the second network entity is described herein. The method may comprise receiving, from a first network entity, a resolution request for resolving the feasibility issue, wherein the feasibility issue is for supporting an intent service request; and transmitting, to the first network entity, a resolution response.

[0010] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with atDocket No. SMM920250137-GR-NPleast one memory and configured to cause the processor to: receive, from a first network entity, a resolution request for resolving the feasibility issue, wherein the feasibility issue is for supporting an intent service request; and transmit, to the first network entity, a resolution response.BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0012] Figure 2 is a flow diagram illustrating an overview of NWDAF flavour including the potential input data sources and output consumers in accordance with aspects of the present disclosure.

[0013] Figure 3 is a flow diagram illustrating Al agent interaction options in accordance with aspects of the present disclosure.

[0014] Figure 4 is a flow diagram illustrating an overview of the Al agent fabric for autonomous operations in accordance with aspects of the present disclosure.

[0015] Figure 5 illustrates an example of a 5G IBN framework in accordance with aspects of the present disclosure.

[0016] Figure 6 illustrates an example of a process flow for an inter-domain on-demand request among Al Agents related to feasibility check, negotiation, and conflict resolution in accordance with aspects of the present disclosure.

[0017] Figure 7 illustrates an example of a process flow for an inter-domain subscription request among Al Agents related to feasibility check, negotiation, and conflict resolution in accordance with aspects of the present disclosure.

[0018] Figure 8 illustrates an example of a user equipment (UE) 800 in accordance with aspects of the present disclosure.

[0019] Figure 9 illustrates an example of a processor 900 in accordance with aspects of the present disclosure.Docket No. SMM920250137-GR-NP

[0020] Figure 10 illustrates an example of a network equipment (NE) 1000 in accordance with aspects of the present disclosure.

[0021] Figure 11 illustrates a flowchart of a method 1100 performed by a NE in accordance with aspects of the present disclosure.

[0022] Figure 12 illustrates a flowchart of a method 1200 performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0023] A wireless communication system (or wireless communication network), including one or more UE or one or more NE, may be configured according to a policy to support a service for an AF Consumer. An NE may determine the policy according to a request. If the policy cannot be supported, the wireless communication network (e.g., PCF) notifies the AF consumer to select an alternative policy. However, there is an ongoing requirement for an improved response and / or alternative resolution from the wireless communication network when the policy cannot be supported. Examples described herein tend to provide a mechanism for improving the response and / or resolution from the wireless communication network when the policy cannot be supported.

[0024] Aspects of the present disclosure are described in the context of a wireless communications system.

[0025] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LIE- A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16Docket No. SMM920250137-GR-NP(WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0026] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

[0027] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0028] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.Docket No. SMM920250137-GR-NP

[0029] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0030] An NE 102 may support communications with the CN 106, or with another NE102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0031] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0032] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104Docket No. SMM920250137-GR-NPmay communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0033] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5 G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0034] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0035] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, forDocket No. SMM920250137-GR-NPexample, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0036] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l , / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0037] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. InDocket No. SMM920250137-GR-NPsome implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0038] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0039] Figure 2 is a flow diagram 200 illustrating an overview of NWDAF flavours including the potential input data sources and output consumers in accordance with aspects of the present disclosure.

[0040] Flow diagram 200 illustrates the various NWDAF flavours and their respective input data and output result consumers, which may include 5G core NFs 235, AFs 210, 5G repositories 240, e.g., NRF, ADRF, UDM, etc., and the 0AM (MnS Consumer or MF) 242. MTLF 222 performs AI / ML model training and AnLF 224 inference. MTLF and AnLF may exchange AI / ML models, e.g., via the means of parameter exchange, serialization or containerization. Optionally, DCCF and MFAF 244 may be involved to distribute and collect repeated data towards or from various data sources.

[0041] TS 23.288 VI 9.1.0 considers several analytics services identified by an Analytics ID. These analytics services collect input data and process them using an ML model to derive the analytics output. NWDAF correlates different data inputs performing complex analytics that can be used as an insight by a consumer to assist in making decisions. Analytics ID is related to user behaviour, communication patterns, mobility, service experience, NF load, slice load, etc. The ML model in NWDAF AnLF may be trained and re-trained when its accuracy degrades. The NWDAF MTLF may be responsibleDocket No. SMM920250137-GR-NPfor carrying out the ML model training. The ML model training may be performed by collecting the appropriate input data.

[0042] Al in 6G networks is envisioned to be native or embedded in NFs replacing existing decision components or adding new components with intelligent capabilities. Native Al may also introduce intelligent control or the capability to manage the life-cycle management of Al-based components.

[0043] The Al native concept is described in Defining Al native: A key enabler for advanced intelligent telecom networks, Ericsson White paper, Feb. 2023 is as follows: “A / native is the concept of having intrinsic trustworthy Al capabilities, where Al is a natural part of the functionality, in terms of design, deployment, operation, and maintenance. An Al native implementation leverages a data-driven and knowledge-based ecosystem, where data / know ledge is consumed and produced to realize new Al-based functionality or augment and replace static, rule-based mechanisms with learning and adaptive Al when needed. ”

[0044] Native Al may: (i) introduce own knowledge, (ii) interact autonomously with other components, (iii) adjust its objective depending on the evolution of collected data, and (iv) be aware of the environment, situation, and network conditions. The objectives of native Al can also be realized by introducing the concept of Al agents in mobile networks.

[0045] Al agents interact with network components and are used to act autonomously to meet requested objectives, e.g., provide insights and / or orchestrate 3GPP services.According to clause 6.5 in TR 22.870 V0.3.1, “Al Agents play a crucial role in modem telecommunications by enabling intelligent automation, decision-making, and adaptive network management. These agents are software-driven entities that leverage artificial intelligence, including machine learning and natural language processing, to interact with users, applications, and network components. In a 6G environment, Al agents enhance network efficiency by dynamically optimizing resources, predicting network conditions, and facilitating providing seamless communication between services.”

[0046] Figure 3 is a flow diagram 300 illustrating Al agent interaction options in accordance with aspects of the present disclosure. Flow diagram 300 shows the agentDocket No. SMM920250137-GR-NPinteractions for natural language intent 352, declarative intent 354, and imperative intent 356.

[0047] Al Agents may need to communicate with (i) users, (ii) other Al Agents and (iii) network resources, e.g., NFs, via existing APIs. Al Agent may interact using different types of Intents as illustrated in flow diagram 300 and documented in 3GPP TSG SA5 6G Workshop, Huawei view on SA5 Rel-20: 6G Priorities, 25-26 Jun. 2025: (i) based on natural language, e.g., LLM, when interacting with humans (e.g., natural language intent 352), (ii) declarative intents when an Al Agent interacts with another (e.g., declarative intent 354), and (iii) imperative intents when Al Agents interact with network resources (e.g., imperative intent 356).

[0048] Figure 4 is a flow diagram 400 illustrating an overview of the Al agent fabric for autonomous operations in accordance with aspects of the present disclosure.

[0049] Flow diagram 400 comprises Agent A (e.g., coverage optimisation agent) 451, Agent B (e.g., energy efficiency agent) 453, Agent C (e.g., throughput optimization agent) 455, Agent D (e.g., event assurance agent) 456, related tools (e.g., traffic prediction function) 457, and an Agent Fabric 458. Agent Fabric 458 comprises a registry, an agent gateway and observability. The registry provides a centra platform for multiple developers to register and discover agents, tools, and other resources. The agent gateway comprises authentication and authorisation which confirm the identity of each agent and ensure that only authorised agents are accessing certain services. The agent gateway also comprises message routing which routes incoming requests to appropriate agents in a task-oriented and load balancing manner. Observability provides runtime audit-able logging, data privacy protection and makes decisions in an explainable way.

[0050] Al Agents are built to perform a specific task, e.g., energy efficiency, and shall reason for the decisions that it takes. An overview of the Agent fabric 458 from 3GPP TSG SA5 6G Workshop, Huawei view on SA5 Rel-20: 6G Priorities, 25-26 Jun. 2025 is illustrated in flow diagram 400. Al Agents are initially authenticated before they can interact with the Agent Fabric 458 to discover other Al Agents and tools, and employ observability tools for taking decisions and for reporting.Docket No. SMM920250137-GR-NP

[0051] IETF discussed Intent-based Networks. An Intent is an expression of a desired state of a system or a service. It is declarative information about goals, utility, requirements, and constraints, providing flexibility to explore alternative options that can satisfy the consumer request. An Intent focuses on describing "what" needs to be achieved, and not "how". An Intent is agnostic of the underlying system architecture or infrastructure. Focusing on the outcome, an Intent enables automation with a greater operational efficiency and flexibility as elaborated in IETF RFC 9315.

[0052] There are different types of Intents including: (i) service, e.g., related to a customer SLA, (ii) networking or cloud including e.g., configuration, automated life-cycle management, and resource optimization, (iii) strategy that deals with policy and (iv) operational, e.g., such as migration and updates. An Intent can be modelled according to IETF RFC 9316 using the following three-tuple: Context, Capabilities, Constraints.

[0053] Context grounds the intent and determines if it is relevant or not for the current situation. Thus, context selects intents based on applicability. Capabilities describe the functionality that the intent can perform. Capabilities take different forms depending on the expressivity of the intent as well as the programming paradigm(s) used. Constraints define any restrictions on the capabilities to be used for that context.

[0054] An Intent is applied within a specific scope, such as: (i) connectivity, (ii) security, (iii) application and (iv) QoS / SLA. An Intent may be quantifiable such that its fulfilment can be measured and evaluated.

[0055] Applying an Intent inside a network can form a closed loop as described in IETF RFC 9417 with the following functional building blocks: Intent Ingestion and Interaction with Users for obtaining an Intent. Intent Translation into policies meaningful to network configuration and provisioning, so the network can act on. Intent Translation functions can be equipped algorithms that perform optimizations with the capability to learn and improve over time, especially when an Intent can be translated in different ways.Activation / Orchestration involves the configuration and provisioning steps that need to be orchestrated across the network and that were determined by the previous intent translation step, e.g., installation of policies. Assurance may rely on performance monitoring, analytics and ML to continuously monitor the network to verify that the desired Intent has beenDocket No. SMM920250137-GR-NPapplied, and the business outcomes are as expected. It involves monitoring, assessment to compare the actual network behaviour monitored with the expected intended behaviour, corrective actions when an Intent drift occurs and reporting to the consumer.

[0056] Some examples described herein generally relate to 5G Intent-based 3GPP compliant Networks. In some examples, the adoption of Intent in 5G networks may provide an architectural framework that combines the IBN and NWDAF for 5G networks with AI / ML. The framework allows a network intent from an IBN user, which is expressed in the form described in TS 28.312 V19.2.1, to be translated into a network policy. The translated network policy can be used to configure NFs in a target network. NF data is then collected and analysed by a selected NWDAF that verifies the impact of the intent and provides suggestions to optimize it.

[0057] Figure 5 illustrates an example of a 5GIBN framework 500 in accordance with aspects of the present disclosure. The 5G IBN framework 500 may be a 5G IBN architecture 500. The main components of the 5GIBN architecture 500 are illustrated in 5G IBN framework 500 and comprises:

[0058] An IBN User 510 that delivers a network Intent to IBN Controller 516 adopting data model documented in 3GPP TS 28.312 V19.2.1. An IBN Controller 516 controls and manages system components in the IBN framework 500. It translates a network intent into the corresponding network policy and selects appropriate NFs (e.g., NF-1 (NEF) 515). A Vendor's Management System 517 provides an image of a virtualized NF for a network service to the IBN framework 500 and registers the capability and access information of an NF with the IBN Controller 516. IBN Analyzer 520 monitors and analyses data from NFs (e.g., NF-1 (NEF) 515, NF-1 (PCF) 525, NF-n (loT Device) 527) for checking the activity and performance using AI / ML techniques. The IBN Analyzer 520 may be an NWDAF in 5G networks; e.g., as per 3GPP TS 23.288. If there is a network problem or Intent drift, e.g., QoS degradation, the IBN Analyzer 520 delivers a report to IBN Controller 516. NF can be virtual, physical or cloud native offering specific network services, e.g., PCF, NEF.

[0059] The modelling of the Intent in 5G networks may be to realize the IBN controller as an Intent handling function, which translates an incoming Intent request and configures the respective IBN components responsible for monitoring, assuring, and controlling theDocket No. SMM920250137-GR-NPexpected Intent outcome, i.e., the Intent life cycle management. The Intent handling function interacts with the consumer providing Intent reporting information, while facilitating the means for exploring the applicability of an Intent request and negotiation if needed.

[0060] The Intent request can be modelled as: a set of expectations that includes: (a) expectation objects, e.g., slice, area of interest, (b) expectation targets, e.g., metric, KPIs, and (c) conditions, e.g., equal to, greater from, with a given value range, the context that defines the conditions for applying the Intent, e.g., network conditions, e.g., when network is congested or when energy cost reduction is applied.

[0061] The intent request may also carry a utility function that describes how different metrics or KPIs are inter-related, e.g., introducing a mathematical function, or weights that define the relative importance of metrics or KPIs, so the Intent handling function would be aware how to prioritize Intent request that carry multiple metrics or KPIs.

[0062] The Intent handling function is also responsible to provide Intent reporting capabilities, which may include: Intent fulfilment information for a specified expectation target or for a whole; Intent over an observation period Intent; conflict information, including conflict type and possible re-solutions; Intent feasibility check during intent preevaluation phase indicates if Intent expectation targets are feasible; Intent exploration enables the consumer to gain information regarding the best values for Intent targets and contexts during negotiation or pre-evaluation phase; Intent negotiation may occur in a preevaluation phase in where Intent feasibility and exploration are part of the negotiation or as a part of Intent fulfilment in where the Intent outcome is checked and / or recommendation are offered; the consumer may then provide feedback indicating satisfaction or the preferred outcome; and Intent utility function defines a method by which consumers can express the relative value of an Intent's expectations indicating variables and relative importance weights, mathematical function or its output.

[0063] An Intent may contain administration states which may include being activated, paused or suspended, degraded, terminated or deactivated. Mobile networks receive policy requirements that may apply to at least one UE from an authorized AF, related to existing or future PDU session. Policies are preconfigured or created by the PCF and enforced perDocket No. SMM920250137-GR-NPQoS flow considering the imposed AF requirements. These requirements may contain QoS characteristics or constrains, routing preferences, e.g., via local break out, time schedule rules, session binding information, relative priority and charging.

[0064] Once a policy cannot be fulfilled, the PCF 525 notifies the AF to negotiate the selection of an alternative considering the plethora of available policy options at the PCF 525. A negotiation process may assume that the core network resources allocated and the way they are configured, e.g., the location and the VMs allocated to realize an NF, are fixed exploring alternative policies that can make the best use. Previously, there was no real-time automated interaction between the core network and the 0AM when a policy is not feasible (e.g., the policy cannot be fulfilled). Typically, the 0AM operations take place on a longer time scale e.g., several minutes, and are reactive. For instance, a problem related to network congestion is monitored, analysed and then an action is taken to resolve it e.g., to reconfigure an NF e.g., scale-up or migrate it in another location, which tends to improve the service characteristics.

[0065] In addition, there was previously no means to influence how an 0AM reconfiguration can benefit a QoS flow or a PDU session since the 0AM operates on an aggregated basis considering a bulk of resources, e.g., a network slice. Furthermore, there was no negotiation and reasoning among the core network and the 0AM, e.g., explaining how to re-configure network resource and why a certain result is obtained or provide a recommendation for modifying a service, a location or time schedule.

[0066] Examples described herein relate to an Intents based interaction among Al Agents. Agentic Al tends to introduce automation and simplicity in mobile core networks. Agentic Al may be configured to interpret and handle an incoming Intent request, e.g., from a third party untrusted AF. The Agentic Al may facilitate the IBN controller 516 functionality or play the role of the Intent handling function. The use of Agentic Al brings intelligent capabilities and builds knowledge in handling an Intent request, e.g., using RL, based on network and service observations without a pre-determined logic or a set of given rules that rely on goal-oriented decisions. An Al Agent may also rely on language models to provide reasoning towards third parties, e.g., untrusted AFs, or when reporting towards third parties, e.g., untrusted AFs.Docket No. SMM920250137-GR-NP

[0067] An incoming Intent request may not be feasible if the desired resources are not available. The respective service priority or policy profile may not be sufficient for the expected service performance. Similarly, an ongoing Intent request may be deprioritized e.g., over a higher priority Intent request. An Al agent in the network (e.g., core network) may perform a negotiation process with the AF consumer. Previously, the negotiation process may comprise exchanging one or more options for adjusting the performance. The negotiation process may comprise selecting a policy. The selected policy may comprise different performance characteristics, e.g., with a different QoS profile. The performance of the different performance characteristics may be re-arranged (e.g., reduced processing latency but increasing the communication delay) and / or reduced (compared to the previous performance characteristics) but suitable for supporting the Intent request.

[0068] Previously, a negotiation process may assume a fixed number of resources. However, an 0AM may re-configure network resources, e.g., allocate a different VM instance to increase the capacity of an NF. An Al Agent has the intelligence or Al capability, e.g., RL capability, to analyse, and decide when to interact with other Al Agents across different domains, e.g., across the 0AM domain. This tends to enable a higher flexibility in resource allocation and policy adjustment during a negotiation process. An Al Agent may reason, e.g., determine why a resource is required, determine options for resource reconfiguration, or determine an impact to the service (of the Intent request).

[0069] The Al Agent in the core network (e.g., core network domain) may be colocated with NEF 515 to take advantage of its authorization and authentication capabilities as well as its capabilities to discover and select the appropriate APIs to interact with other NFs. Alternatively, it may closely interact with NEF 515 as a part of PCF 525, a new NF or new network entity. In the management plane, an Al Agent may be embedded with a resource orchestration function (e.g., a slice resource orchestrator), and / or be a part of component of an automation mechanism, e.g., governance of a closed loop, or be embedded in the NFVO to take care the scale up / down and migration of VNFs. Alternatively, it may be a new MF or a new network entity that interacts closely with a resource orchestration function or with a component of an automation mechanism or with the NFVO.Docket No. SMM920250137-GR-NP

[0070] Al Agents across different domains may establish an interchange for handling negotiations and conflict resolution. To discover an Al Agent, each Al Agent may be registered to an Al Agent registry repository.

[0071] The Al Agent registry repository may comprise at least one of: Al Agent permissions indicating the type of other Al Agents that are allowed to consume its services; Al Agent status, e.g. operational or faulty or during maintenance; PLMN ID for the Al Agent; Al Agent Address that may be reached; Al Agent type that indicates the Al Agent objective e.g., policy provision, resource allocation, or VNF provision; Serving technology domain, e.g., core network, 0AM, RAN, or application; Serving scope in terms of the geographical area; Al Agent load to indicate available computational capability including a timestamp relating to a previous update of the available computation capability; Al Agent capacity / priority for prioritizing the selection of Al Agents with the same capabilities;Serving object e.g., network slice identifier, edge cloud identifier, or application identifier; Service constraints e.g., upper bound latency, computing capabilities, energy expenditure, or minimum charging; or Reporting capabilities comprising a format and / or type of reporting, e.g., notification, streaming, file, reporting events or conflict types.

[0072] The parameters of the PLMN ID e.g., serving technology domain, address, serving scope or service object may be applicable if an Al Agent registers in an Al Agent registry. If the Al Agent register in an existing repository e.g., NRF as a capability of an NF, then the above parameters may be implied since such repository already belongs to a specific PLMN and domain.

[0073] Core network Al Agents (e.g., an Al agent in the core network) may register in the NRF as a capability of the respective NF in which they are embedded. The 0AM Al Agent (e.g., Al Agent in the 0AM) may register in the MnS Discovery Service Producer as a capability of the respective embedded MF. An Al Agent that is a standalone entity (e.g., a standalone Al Agent) may register as a capability of each inter-related NF or MF respectively. For example, a standalone Al Agent in the core network responsible for policy selection may be registered as a capability of NEF to assist untrusted AF to be authenticated and authorized, and / or may be registered as a capability of PCF for supporting trusted AFs that do not need to interact with NEF. A standalone Al Agent in theDocket No. SMM920250137-GR-NPOAM domain responsible for VNF management, e.g., scale up / down and VNF relocation, may be a part of slice orchestration MF and NF VO MF to manage VNF shared among an end-to-end slice and an edge cloud.

[0074] An Al Agent in the core network, before negotiating with the consumer, may select a counterpart Al Agent in the OAM domain to determine whether a potential resource re-configuration may resolve a shortage of resources or a potential conflict. Even if a resource re-configuration carried out by an OAM Al Agent cannot resolve an issue, the OAM Al Agent may support a negotiation e.g., by providing additional options for higher flexibility to the consumer.

[0075] Some examples described herein may relate to Intent APIs for inter-domain Al Agent Transaction. An Al Agent may interact with another Al Agent across a different technology domain. The interaction between Al Agents across a different technology domain may be performed using a set of APIs to facilitate Intent based exchange. The APIs may focus on a feasibility check, a negotiation, and a conflict resolution. An Intent based exchange among Al Agents may be on demand e.g., once a problem is encountered in the core network. An Intent based exchange among Al Agents may be on a regular basis e.g., to assess risks and enable a more efficient policy selection during negotiation and conflict resolution.

[0076] An Al Agent in the core network may transmit (e.g., send, output) an Intent request for at least one of: a feasibility check, a negotiation, or a conflict resolution to an Al Agent in the OAM domain.

[0077] The Intent request (e.g., subscription or one time on demand request) may indicate at least one of: an Intent ID and / or Request ID for reporting or further correspondence in case of a subscription; Scope of request, e.g., type of problem or potential problem that focuses on resolving, including but not limited to the feasibility check, the negotiation or the conflict resolution; Service parameters that introduce infeasibility, involved in negotiation, or require conflict resolution, e.g., latency that cannot be achieved, or capacity / data rate to enhance, or an increase in capacity that conflicts energy saving goals; Degree of infeasibility, optimization target (e.g., for negotiation or in case of a subscription), or conflict to estimate (e.g., project) an amount a service parameterDocket No. SMM920250137-GR-NPis infeasible; Severity weight of each service parameter in the service performance or a utility function e.g., indicating any parameter interrelation. Acceptable drift indicating the service state deviation or specific parameter deviation when selecting a resolution to the issue raised; Service object in which these service parameters relate, e.g., slice, DNN, access technology; Expected or predicted user’s or set of users’ behaviour involved, including communication patterns, mobility and location habits to assist the OAM Al Agent with determining an appropriate resource re-configuration or optimization; Priority assigned to the service (e.g., in the case of conflict resolution a priority may relate to every service involved), which may be used to represent the relative preference when reconfiguring network resources for a certain service instead of another; Service constraints in regaining or “fixing” the service infeasibility, service optimization, service negotiation, or conflict resolution in terms of, e.g., cost, charging or energy expenditure; Geographical location of at least one of: where a service is not feasible, a service negotiation, a conflict raised, or where a subscription is received; Regularity of at least one of: a service not being feasible, a negotiation, or a conflict being raised; Target period related to a subscription; Events related to at least one of: a service not being feasible, a negotiation, or a conflict being raised, e.g., once the network load surpasses an indicated threshold, upon a mobility situation, or an energy saving situation; Reporting information comprising at least one of: a format of the report and information in the report, or a time window related to reporting, for a subscription the reporting information may further comprise at least one of: a reporting schedule (e.g., regularly or one time), a time to receiving a report, a number of reports, or an event related to reporting (e.g., the load surpass an indicated threshold).

[0078] The OAM Al Agent, once receiving a request related to an on-demand feasibility check, negotiation, conflict resolution or a subscription, initially performs authorization and authentication to ensure that the requesting Al Agent is allowed to access the OAM domain and request the specific service. Once the request is authorized, the OAM Al Agent sets up the respective monitoring and analytics observations; if not already in place.

[0079] The OAM Al Agent performs at least one of the following internal logic actions based on its local Al logic: Translates the service to derive the resource requirements (e.g.,Docket No. SMM920250137-GR-NPcapacity, data rate, latency); Determine the resource re-configuration (e.g., allocate bandwidth, scale up a specific VNF or relocate a VNF); Allocate an identifier to reference the resource re-configuration for reasoning and / or reporting; Determine the degree of resource re-configuration for resolving the issue raised (e.g., in terms of percentage, absolute value, number of parameters that were assigned the desired performance);Determine monitoring and observation components to assist tracking the performance of an Intent service request related to a subscription to identify potential risks for performance degradations; Determine the decision / execution components for carrying out the provision of the resource re-configuration; Determine the cost (e.g., charging or energy expenditure cost) related to the resource re-configuration; Determine the geographic location, path, or area affected by the resource re-configuration (e.g., the indicated location, a subset of the indicated location or a bigger area than the one indicated); Determine the time schedule related to resource re-configuration (e.g., re-configuring the selected resource), the time schedule may be selected to benefit entirely or partially the service provided that the service could tolerate flexibility in terms of the deployment time, while minimizing the negative impact on other services; Determine how it may affect other services with the goal to minimize any negative impact; Determine potential conflicts and risks for deploying the selected resource re-configuration considering other services considering the type of conflict (e.g., scope, parameters and impact); Determine a confidence degree in resolving the issue raised; or Maintaining reasoning on how a problem was resolved by keeping a record, e.g., of objectives, selecting actions, evaluate impact on resolution.

[0080] Once the 0AM Al Agent performs a resource re-configuration action (e.g., in response to an on-demand request or subscription) it may then respond to the Al Agent of the core network including at least one of the following parameters: Intent ID or Request ID; Service parameters that were impacted by the resource re-configuration; Indication of success in fulfilling the request or partial success in fulfilling the request with respect to (e.g., specified parameters, geographical area, time); Degree of service parameter recovery (e.g., when there is a partial success in fulfilling a request) to enable feasibility or an optimal negotiation, or conflict resolution; Determine potential conflicts and risks with respect to other specified services indicating the type of conflict (e.g., scope, parameters or impact); The service object ID affected by the resource re-configuration (e.g., slice, DNN,Docket No. SMM920250137-GR-NPaccess technology); Geographical location affected by the resource re-configuration (e.g., the indicated location, a subset of the indicated location or a bigger area than the one indicated); Target time when a service parameter is recovered, conflict is resolved or partially resolved, or the period the issue remains unsolved; Ongoing cost or cost projection related to the adoption of the resource re-configuration; Reasoning on how a problem was resolved (e.g., objectives, selecting actions, evaluate impact on resolution); or Determine the confidence degree in resolving the issue raised. Reasoning may be based on language models, which may be used to provide feedback towards third parties, e.g., untrusted AFs.

[0081] The 0AM Al Agent may respond to a subscription by reporting progress. The progress may comprise not comprise performing a resource re-configuration. The 0AM Al Agent may report a potential risk or conflict related to the given Intent ID or Request ID. The 0AM Al Agent may provide a confidence degree or reasoning in the response. The response may further comprise at least one of: the affected service object ID, the geographical location, the expected time, a potential recommendation related to resource control (e.g., routing, traffic offloading).

[0082] When the 0AM Al Agent cannot resolve the feasibility check or a negotiation or a conflict resolution request, it may provide an error notification comprising the Intent ID or Request ID and the reasoning why the problem could not be resolved. Such reasoning may comprise an indication of at least one of: a type of resources lacking (e.g., lack of capacity, computing, in a specific geographical area and time); a priority issue (e.g., the received request assigned priority is low for resolving the problem); potential other failures (e.g., maintenance, configuration errors); potential cost constraint reasons (e.g., in terms of charging or energy cost); Indicate failure related to a service object in which these service parameters relate (e.g., slice, DNN, access technology). Indicate failure related to a geographical location or time schedule; Indicate user behaviour issues (e.g., mobility that negatively influences the resource re-configuration); or Indicate best effort issue resolution if another attempt to resolve the issue will be carried out shortly. Reasoning may be based on language models, which may be used to provide feedback towards third parties, e.g., untrusted AFs.Docket No. SMM920250137-GR-NP

[0083] Some examples described herein relate to inter-domain Al Agent Interoperation. Some examples described herein introduce a set of different processes related to the interdomain exchange between an Al Agent in the core network and a counterpart Al Agent in the 0AM. The processes comprise a feasibility check, a negotiation, and a conflict resolution request. The processes may consider a related subscription.

[0084] Figure 6 illustrates an example of a process flow 600 for an inter-domain on- demand request among Al Agents related to feasibility check, negotiation, and conflict resolution in accordance with aspects of the present disclosure.

[0085] Figure 6 illustrates an example of a process flow 600 in accordance with aspects of the present disclosure. The process flow 600 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 600 may include an Al Agent (e.g., embedded in the NEF) 610 (e.g., Al Agent in the core network), an 0AM Registry 620, and an Al Agent (0AM e.g., Slice Orch) 630 which may be one or more examples of devices described herein with reference to Figure 1.

[0086] The process flow 600 may be referred to as a procedure, including one or more operations performed by one or more of the Al Agent (Core) 610, the 0AM Registry 620 and the Al Agent (0AM) 630.

[0087] In the following description of the process flow 600, the operations or signalling performed between one or more of the Al Agent (Core) 610, the 0AM Registry 620 and the Al Agent (0AM) 630 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the Al Agent (Core) 610, the 0AM Registry 620 and the Al Agent (0AM) 630 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 600. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0088] The process flow 600 relates to an on-demand Request. The process flow 600 focuses on an on-demand request for a feasibility check, a negotiation and a conflictDocket No. SMM920250137-GR-NPresolution. The Al Agent (Core) 610 requests the counterpart Al Agent (0AM) 630 to determine whether a resource re-configuration can resolve an issue.

[0089] Process flow 600 initiates at step 671. The Al Agent (Core) 610 (e.g., an Al Agent residing in the core network, an Al Agent embedded or interrelated with NEF handling an Intent request from untrusted AF consumer identifies (e.g., determine) an infeasibility of an incoming Intent request (e.g., a feasibility issue) (e.g., due to lack of resources) The feasibility issue may comprise an Intent request that faces a performance drift. The feasibility issue may comprise a conflict due to the prioritization of another request or because another request imposes conflicting requirements.

[0090] The Al Agent (Core) 610 may not initially negotiate with the AF consumer for the selection of an alternative policy with a different service state or service parameters. Instead, the Al Agent (Core) 610 sends a resolution request to the Al Agent (0AM) 630 to check with the 0AM (e.g., via the Al Agent (0AM) 630, a counterpart Al Agent in the 0AM domain) if a potential resource re-configuration may resolve the feasibility issue.

[0091] In step 672, the Al Agent (Core) 610 selects (e.g., identifies, discovers, determines) the Al Agent (0AM) 630 by issuing (e.g., transmitting, sending) a discovery request to the 0AM Registry 620 or towards an MnS Discovery Service Producer in the 0AM. The discovery request may comprise at least one of: an Al Agent type, a service scope, a constraint and reporting capabilities. The 0AM registry 620 identifies (e.g., determines) one or more candidate Al Agent (0AM) by considering authorization information. The 0AM Registry 620 returns (e.g., sends, transmits) the one or more candidate Al Agent (0AM) to the Al Agent (Core) 630. The Al Agent (Core) 630 selects the Al Agent (0AM) 630 from the one or more candidate Al Agent (0AM) e.g., by considering a requirement.

[0092] In step 673, once the Al Agent (Core) 630 selects the Al Agent (0AM) 630, the Al Agent (Core) 630 sends (e.g., transmits, outputs) a request (e.g., a resolution request) for at least one of: a feasibility check of an incoming Intent request, a negotiation, or a conflict resolution of an ongoing Intent request that faces a performance drift. The request may contain at least one of: the Intent ID, operations scope, specific service parameters and related information, filter information, constraints, or reporting information.Docket No. SMM920250137-GR-NP

[0093] In step 674, the Al Agent (OAM) 630 translates (e.g., maps) the Intent service request into one or more network resources. The Al Agent (OAM) 630 determines a resolution how to resolve the feasibility issue e.g., by selecting which resources to reconfigure, by determining how the re-configuration shall take place, by determining the related cost, time, risks or conflicts, or by determining a reason for the resolution.

[0094] If the Al Agent (OAM) 630 is unable to resolve the feasibility issue, it may determine one or more reasons e.g., a the one or more reasons may comprise at least one of: a lack of resources, a prioritization issue, a user behaviour, a fault or error, or a cost reason. Reasoning may additionally be based on language models. The Al Agent (OAM) 630 may determine a compromised resolution. The Al Agent (OAM) 630 may send an indication of the one or more reasons or compromised resolution to the Al Agent (Core) 610.

[0095] In step 675, the Al Agent (OAM) 630 transmits a resolution response (e.g., a report) to the Al Agent (Core) 610. The resolution response may comprise an indication of at least one of: the Intent ID, the service parameters impacted by the resource reconfiguration, the potential conflicts, the risks and the confidence degree related to the resolution, the impacted location, the service objects and the associated cost, or the reasoning (e.g., how the feasibility issue was resolved). Alternatively, the resolution response may comprise an error notification and may further comprise reasoning e.g., why an error occurred and failed to provide a resource re-configuration including language and / or an indication.

[0096] Figure 7 illustrates an example of a process flow 700 for an inter-domain subscription request among Al Agents related to feasibility check, negotiation, and conflict resolution in accordance with aspects of the present disclosure.

[0097] Figure 7 illustrates an example of a process flow 700 in accordance with aspects of the present disclosure. The process flow 700 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 700 may include an Al Agent (e.g., embedded in the NEF) 710 (e.g., Al Agent in the core network), an OAM Registry 720, and an Al Agent (OAM e.g., Slice Orch) 730 which may be one or more examples of devices described herein with reference to Figure 1.Docket No. SMM920250137-GR-NP

[0098] The process flow 700 may be referred to as a procedure, including one or more operations performed by one or more of the Al Agent (Core) 710, the 0AM Registry 720 and the Al Agent (0AM) 730.

[0099] In the following description of the process flow 700, the operations or signalling performed between one or more of the Al Agent (Core) 710, the 0AM Registry 720 and the Al Agent (0AM) 730 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the Al Agent (Core) 710, the 0AM Registry 720 and the Al Agent (0AM) 730 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 700. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0100] Some examples described herein may relate to a subscription Request. The subscription request shown in Process flow 700 relates to a feasibility check, a negotiation and a conflict resolution. The Al Agent (Core) 710 requests the Al Agent (0AM) 730 to regularly check for resource optimizations for resolving a respective feasibility issue or potential feasibility issue(s) and may further request regular reports related to the progress and potential risks.

[0101] Process flow 700 initiates at steps 771-772. The Al Agent (Core) 710 (e.g., which may be embedded at NEF in the core network), identifies an infeasibility of an incoming Intent request (e.g., a feasibility issue). The feasibility issue may comprise an Intent request faces a performance drift. The feasibility issue may comprise the Intent request faces conflicting requirements. The Al Agent (Core) 710 sends a resolution request to the Al Agent (0AM) 730 to determine (e.g., check) if a potential resource reconfiguration may resolve the issue. The Al Agent (Core) 710 may subscribe to the Al Agent (0AM) proactively in case it faces an infeasibility issue and / or for identifying and resolving performance risks related to an ongoing service.Docket No. SMM920250137-GR-NP

[0102] The Al Agent (Core) 710 selects (e.g., identifies, discovers, determines) appropriate Al Agent (0AM) 730 through a discovery process carried out with the assistance of the 0AM Registry 720 or an MnS Discovery Service Producer in the 0AM.

[0103] In step 773, once the Al Agent (Core) 730 selects the Al Agent (0AM) 730, the Al Agent (Core) 730 sends (e.g., transmits, outputs) a subscription request either for at least one of: a feasibility check of an incoming Intent request, a negotiation, or a conflict resolution of an ongoing Intent request. The request may contain at least one of: the Intent ID, operations scope, specific service parameters and related information, filter information, constraints, and reporting information, or the time related to the subscription.

[0104] In step 774, the Al Agent (0AM) 730 translates the Intent service request into one or more network resources and deploys the monitoring or observation mechanisms to check potential performance degradations. The Al Agent (0AM) 730 regularly prepares a report for the Al Agent (Core) 710 comprising information relating to the progress and risks related to the service request for the indicated time of the subscription. The report may also contain language based on a language model.

[0105] Once a degradation or a potential degradation is observed, the Al Agent (0AM) 730 determines how to resolve it by selecting which resources to re-configure. The Al Agent (0AM) 730 may further determine at least one of: how the re-configuration shall take place, the related cost, time, risks and conflicts, or a reason for the resolution. If the Al Agent (0AM) 730 is unable to resolve the feasibility issue, it may determine one or more reasons e.g., the one or more reasons may comprise at least one of: a lack of resources, a prioritization issue, a user behaviour, a fault or error, or a cost reason. The Al Agent (0AM) 730 may determine a compromised resolution. The Al Agent (0AM) 730 may send an indication of the one or more reasons or compromised resolution and / or language output to the Al Agent (Core) 710.

[0106] In step 775, the Al Agent (0AM) 730 provides (e.g., sends, transmits, outputs) a regular report back to the Al Agent (Core) 710 comprising an indication of at least one of: the Intent ID, potential performance or conflict risks for certain locations, service objects and times, the associated cost, or other information related to report updating. The report may also contain language based on a language model.Docket No. SMM920250137-GR-NP

[0107] When a resource re-configuration is performed successfully to resolve the feasibility issue, the report may comprise an indication of at least one of: the Intent ID, the service parameters impacted by the resource re-configuration, the potential conflicts, the risks and the confidence degree related to the resolution, the impacted location, the service objects and the associated cost, or the reasoning (e.g., how the feasibility issue was resolved), and may include language. Alternatively, the resolution response may comprise an error notification and may further comprise reasoning e.g., why an error occurred and failed to provide a resource re-configuration including language and / or an indication.

[0108] In steps 776-777, the Al Agent (0AM) 730 regularly reports updates related to the process and potential risks, or upon an indicated event, e.g., slice load surpasses a threshold, or once a resource re-configuration is performed, a reason for its decisions. The Al Agent (0AM) 730 provides (e.g., sends, transmits, outputs) the respective report update to the Al Agent (Core) 710.

[0109] Figure 8 illustrates an example of a UE 800 in accordance with aspects of the present disclosure. The UE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0110] The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0111] The processor 802 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 802 may be configured to operate the memory 804. In some other implementations, the memory 804 may be integrated into the processor 802.Docket No. SMM920250137-GR-NPThe processor 802 may be configured to execute computer-readable instructions stored in the memory 804 to cause the UE 800 to perform various functions of the present disclosure.

[0112] The memory 804 may include volatile or non-volatile memory. The memory 804 may store computer-readable, computer-executable code including instructions when executed by the processor 802 cause the UE 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 804 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0113] In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to cause the UE 800 to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804). For example, the processor 802 may support wireless communication at the UE 800 in accordance with examples as disclosed herein. The UE 800 may be configured to support the arrangements described herein.

[0114] The controller 806 may manage input and output signals for the UE 800. The controller 806 may also manage peripherals not integrated into the UE 800. In some implementations, the controller 806 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 806 may be implemented as part of the processor 802.

[0115] In some implementations, the UE 800 may include at least one transceiver 808. In some other implementations, the UE 800 may have more than one transceiver 808. The transceiver 808 may represent a wireless transceiver. The transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

[0116] A receiver chain 810 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 810 may include one or more antennas for receive the signal over the air or wireless medium.Docket No. SMM920250137-GR-NPThe receiver chain 810 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 810 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 810 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0117] A transmitter chain 812 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 812 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 812 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0118] Figure 9 illustrates an example of a processor 900 in accordance with aspects of the present disclosure. The processor 900 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 900 may include a controller 902 configured to perform various operations in accordance with examples as described herein. The processor 900 may optionally include at least one memory 904, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 900 may optionally include one or more arithmetic-logic units (ALUs) 906. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0119] The processor 900 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.Docket No. SMM920250137-GR-NPThe processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 900) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0120] The controller 902 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 900 to cause the processor 900 to support various operations in accordance with examples as described herein. For example, the controller 902 may operate as a control unit of the processor 900, generating control signals that manage the operation of various components of the processor 900. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0121] The controller 902 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 904 and determine subsequent instruction(s) to be executed to cause the processor 900 to support various operations in accordance with examples as described herein. The controller 902 may be configured to track memory address of instructions associated with the memory 904. The controller 902 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 902 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 900 to cause the processor 900 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 902 may be configured to manage flow of data within the processor 900. The controller 902 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 900.

[0122] The memory 904 may include one or more caches (e.g., memory local to or included in the processor 900 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 904 may resideDocket No. SMM920250137-GR-NPwithin or on a processor chipset (e.g., local to the processor 900). In some other implementations, the memory 904 may reside external to the processor chipset (e.g., remote to the processor 900).

[0123] The memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 900, cause the processor 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 902 and / or the processor 900 may be configured to execute computer-readable instructions stored in the memory 904 to cause the processor 900 to perform various functions. For example, the processor 900 and / or the controller 902 may be coupled with or to the memory 904, the processor 900, the controller 902, and the memory 904 may be configured to perform various functions described herein. In some examples, the processor 900 may include multiple processors and the memory 904 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0124] The one or more ALUs 906 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 906 may reside within or on a processor chipset (e.g., the processor 900). In some other implementations, the one or more ALUs 906 may reside external to the processor chipset (e.g., the processor 900). One or more ALUs 906 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 906 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 906 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 906 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 906 to handle conditional operations, comparisons, and bitwise operations.Docket No. SMM920250137-GR-NP

[0125] The processor 900 may support wireless communication in accordance with examples as disclosed herein. The processor 900 may be configured to support a means for receiving, from an application consumer, an intent service request; transmitting, to a second network entity, a resolution request for resolving a feasibility issue for supporting the intent service request; and receiving, from the second network entity, a resolution response. The processor 900 may be configured to or operable to support a means for receiving, from a first network entity, a resolution request for resolving the feasibility issue, wherein the feasibility issue is for supporting an intent service request; and transmitting, to the first network entity, a resolution response.

[0126] Figure 10 illustrates an example of a NE 1000 in accordance with aspects of the present disclosure. The NE 1000 may include a processor 1002, a memory 1004, a controller 1006, and a transceiver 1008. The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0127] The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0128] The processor 1002 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1002 may be configured to operate the memory 1004. In some other implementations, the memory 1004 may be integrated into the processor 1002. The processor 1002 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the NE 1000 to perform various functions of the present disclosure.Docket No. SMM920250137-GR-NP

[0129] The memory 1004 may include volatile or non-volatile memory. The memory 1004 may store computer-readable, computer-executable code including instructions when executed by the processor 1002 cause the NE 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1004 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0130] In some implementations, the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to cause the NE 1000 to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004). For example, the processor 1002 may support wireless communication at the NE 1000 in accordance with examples as disclosed herein. The NE 1000 may be configured to support a means for receiving, from an application consumer, an intent service request; transmitting, to a second network entity, a resolution request for resolving a feasibility issue for supporting the intent service request; and receiving, from the second network entity, a resolution response. Alternatively, the NE 1000 may be configured to or operable to support a means for receiving, from a first network entity, a resolution request for resolving a feasibility issue, wherein the feasibility issue is for supporting an intent service request; and transmitting, to the first network entity, a resolution response.

[0131] The controller 1006 may manage input and output signals for the NE 1000. The controller 1006 may also manage peripherals not integrated into the NE 1000. In some implementations, the controller 1006 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1006 may be implemented as part of the processor 1002.

[0132] In some implementations, the NE 1000 may include at least one transceiver 1008. In some other implementations, the NE 1000 may have more than one transceiver 1008. The transceiver 1008 may represent a wireless transceiver. The transceiver 1008 mayDocket No. SMM920250137-GR-NPinclude one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.

[0133] A receiver chain 1010 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1010 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1010 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 1010 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1010 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0134] A transmitter chain 1012 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1012 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1012 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1012 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0135] Figure 11 illustrates a flowchart of a method 1100 in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0136] At 1102, the method 1100 may include receiving, from an application consumer, an intent service request. The operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by a NE as described with reference to Figure 10.Docket No. SMM920250137-GR-NP

[0137] At 1104, the method 1100 may include transmitting, to a second network entity, a resolution request for resolving a feasibility issue for supporting the intent service request. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed a NE as described with reference to Figure 10.

[0138] At 1106, the method 1100 may include receiving, from the second network entity, a resolution response. The operations of 1106 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1106 may be performed by a NE as described with reference to Figure 10.

[0139] It should be noted that the method 1100 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0140] Figure 12 illustrates a flowchart of a method 1200 in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0141] At 1202, the method 1200 may include receiving, from a first network entity, a resolution request for resolving a feasibility issue, wherein the feasibility issue is for supporting an intent service request. The operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by a NE as described with reference to Figure 10.

[0142] At 1204, the method 1200 may include transmitting, to the first network entity, a resolution response. The operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by a NE as described with reference to Figure 10.

[0143] It should be noted that the method 1200 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.Docket No. SMM920250137-GR-NP

[0144] There is provided herein a first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from an application consumer, an intent service request; transmit, to a second network entity, a resolution request for resolving a feasibility issue for supporting the intent service request; and receive, from the second network entity, a resolution response. Such a first network entity tends to improve agility of a wireless communication network to support the intent service request.

[0145] The resolution request may indicate a request to resolve the feasibility issue. The feasibility issue may be an issue that prevents the first network entity from supporting the intent service request. The resolution response may indicate a solution for resolving the feasibility issue. By performing the resolution response, the first network entity may support the intent service request. The intent service request may be a request for an intent service.

[0146] The at least one processor may be further configured to cause the first network entity to determine the feasibility issue for supporting the intent service request (e.g., for an on demand request). The first network entity may comprise an Al agent in a core network. The first network entity may be in the core network. The first network entity may comprise an IBN controller. The IBN controller may comprise embedded intelligence or an embedded model. The application consumer may comprise an AF consumer. The application consumer may comprise a vertical. The core network may be part of a wireless communication network (e.g., wireless communication system). The second network entity may be in the network management domain. The second network entity may comprise an 0AM component and / or entity. The intent service request may be for a service for the application consumer.

[0147] Transmitting, to a second network entity, a resolution request for resolving the feasibility issue may comprise transmitting, to an Al agent in the 0AM domain at the second network entity, a resolution request for resolving the feasibility issue. Receiving, from the second network entity, a resolution response may comprise receiving, from the AlDocket No. SMM920250137-GR-NPagent in the OAM domain at the second network entity, a resolution response. The Al agent in the OAM domain may comprise an OAM Al agent.

[0148] The feasibility issue may be related to at least one of: a lack of resources; a performance drift; a cost issue; or a conflict with a second intent service request. The resolution request may comprise an indication of at least one of: the feasibility issue; an intent identifier; an operations scope; a service parameter; filter information; a user behaviour information; a constraint; reporting information; or a subscription time.

[0149] The resolution response may comprise an indication of at least one of: an intent identifier; a service parameter impacted by a resource re-configuration; a conflict; a risk; a solution to the feasibility issue; a confidence degree of the solution to the feasibility issue; reasoning for the solution to the feasibility issue; an impacted location; a service object; a cost; or an error notification. The error notification may comprise a negative response to the resolution request. The error notification may comprise an indication as to why an error occurred. The intent service request may comprise an indication of at least one of: a goal for an intent service; a utility for the intent service; a requirement for the intent service or a constraint.

[0150] The at least one processor may be further configured to cause the first network entity to: transmit, to a third network entity, a discovery request comprising an indication of at least one of: an Al agent type; an operations scope; a service parameter; filter information; a constraint; reporting information; or a subscription time. The third network entity may comprise an Al agent repository. The third network entity may comprise an MnS Discovery Service Producer if the Al agent capability is embedded to an MF. The third network entity may comprise an OAM component or entity.

[0151] The at least one processor may be further configured to cause the first network entity to: receive, from the third network entity, an indication of an Al agent at the second network entity. The at least one processor may be further configured to cause the first network entity to: receive, from the third network entity, an indication of a plurality of Al agents at the second network entity. The Al agent at the second network entity may be one of the plurality of Al agents at the second network entity. The Al agent at the second network entity may comprise the Al agent in the OAM domain at the second networkDocket No. SMM920250137-GR-NPentity. The resolution request for resolving the feasibility issue may comprise a request for at least one of: a service risk assessment; or a resource re-configuration.

[0152] There is further provided herein a method performed or performable by a first network entity, the method comprising: receiving, from an application consumer, an intent service request; transmitting, to a second network entity, a resolution request for resolving a feasibility issue for supporting the intent service request; and receiving, from the second network entity, a resolution response. Such a method performed or performable by the first network entity tends to improve agility of a wireless communication network to support the intent service request.

[0153] The method may further comprise determining the feasibility issue for supporting the intent service request. The feasibility issue may be related to at least one of: a lack of resources; a performance drift; a cost issue; or a conflict with a second intent service request. The resolution request may comprise an indication of at least one of: the feasibility issue; an intent identifier; an operations scope; a service parameter; filter information; a user behaviour information; a constraint; reporting information; or a subscription time.

[0154] The resolution response may comprise an indication of at least one of: an intent identifier; a service parameter impacted by a resource re-configuration; a conflict; a risk; a solution to the feasibility issue; a confidence degree of the solution to the feasibility issue; reasoning for the solution to the feasibility issue; an impacted location; a service object; a cost; or an error notification. The intent service request may comprise an indication of at least one of: a goal for an intent service; a utility for the intent service; a requirement for the intent service or a constraint.

[0155] The method may further comprise transmitting, to a third network entity, a discovery request comprising an indication of at least one of: an Al agent type; an operations scope; a service parameter; filter information; a constraint; reporting information; or a subscription time. The method may further comprise receiving, from the third network entity, an indication of an Al agent at the second network entity. The resolution request for resolving the feasibility issue may comprise a request for at least one of: a service risk assessment; or a resource re-configuration.Docket No. SMM920250137-GR-NP

[0156] There is further provided herein a second network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second network entity to: receive, from a first network entity, a resolution request for resolving a feasibility issue for supporting an intent service request; and transmit, to the first network entity, a resolution response. Such a method performed or performable by the second network entity tends to improve agility of a wireless communication network to support the intent service request.

[0157] The method may further comprise determining the feasibility issue for supporting the intent service request. The feasibility issue may be related to at least one of: a lack of resources; a performance drift; a cost issue or a conflict with a second intent service request. The resolution request may comprise an indication of at least one of: the feasibility issue; an intent identifier; an operations scope; a service parameter; filter information; a constraint; reporting information; or a subscription time. The resolution response may comprise an indication of at least one of: an intent identifier; a service parameter impacted by a resource re-configuration; a conflict; a risk; a solution to the feasibility issue; a confidence degree of the solution to the feasibility issue; reasoning for the solution to the feasibility issue; an impacted location; a service object; or a cost. The intent service request may comprise an indication of at least one of: a goal for an intent service; a utility for the intent service; or a requirement for the intent service.

[0158] Determining the Al agent at the second network entity may comprise determining the Al agent at the second network entity based on authorisation information. The at least one processor may be further configured to cause the second network entity to: transmit, to the first network entity, an indication of an Al agent at the second network entity. The resolution request for resolving the feasibility issue may comprise a request for at least one of: a service risk assessment; or a resource re-configuration.

[0159] There is further provided herein a method performed or performable by a second network entity, the method comprising: receiving, from a first network entity, a resolution request for resolving a feasibility issue for supporting an intent service request; and transmitting, to the first network entity, a resolution response. Such a method performed orDocket No. SMM920250137-GR-NPperformable by the second network entity tends to improve agility of a wireless communication network to support the intent service request.

[0160] The feasibility issue may be related to at least one of: a lack of resources; a performance drift; a cost issue or a conflict with a second intent service request. The resolution request may comprise an indication of at least one of: the feasibility issue; an intent identifier; an operations scope; a service parameter; filter information; a constraint; reporting information; or a subscription time. The resolution response may comprise an indication of at least one of: an intent identifier; a service parameter impacted by a resource re-configuration; a conflict; a risk; a solution to the feasibility issue; a confidence degree of the solution to the feasibility issue; reasoning for the solution to the feasibility issue; an impacted location; a service object; or a cost. The intent service request may comprise an indication of at least one of: a goal for an intent service; a utility for the intent service; or a requirement for the intent service.

[0161] Examples described herein generally relate to when a policy cannot be fulfilled and the PCF notifies the AF consumer to negotiate the selection of an alternative policy considering the available policy options. Previously, a negotiation process may assume that the allocated resources in the core network and the way they are configured, e.g., to realize an NF, is fixed. The negotiation process may comprise exploring alternative policies. Previously, there was no means to notify the 0AM to explore a potential resource reconfiguration for accommodating an otherwise not feasible or conflicting policy. 0AM operations tend to take place on a longer time scale (e.g., several minutes). 0AM operations are reactive and based on an aggregated bulk of resources.

[0162] Examples described herein relates to an Al Agent for handling an Intent service request from an AF consumer. This tends to enable inter-domain Al Agentic interaction (e.g., between an Al Agent in the core network and an Al agent in the 0AM) for real-time resource re-configuration, e.g., allocation of additional communication resources or VNFs or VNF relocation, to handle core network policy requirements that are either infeasible or create a conflict. Some examples described herein introduce an Al Agent discovery process and the respective APIs to facilitate the inter-domain Al Agent interaction to handle feasibility checks, negotiations, and conflict resolution issues. Some examples describedDocket No. SMM920250137-GR-NPherein relate to on-demand resolution requests. Some examples described herein relate to subscription resolution requests.

[0163] Previously, there was no real-time interaction between the core network and 0AM for proactive or real-time resource re-configuration. Previously, the 0AM monitored the allocated resources and provided a re-configuration once identified, which tends to be on a different time scale and resource quantity compared to the operations of the core network. Some examples described herein relate to an on-demand request for inter-domain Al Agent interoperation. Some examples described herein relate to a subscription request for inter-domain Al Agent interoperation.

[0164] There is further provided herein a first network entity [e.g., Core Network Al Agent, Al Agent (Core)] for wireless communication, comprising: at least one memory; and at least one autonomous intelligent logic with the capability to learn from acting; and at least one processor coupled with the at least one memory and intelligent logic, and configured to cause the first network entity to: receive a first declarative service request from an application consumer related to a goal, a utility, a requirement and for such declarative service request, provision mechanisms to assess its performance and upon a feasibility or conflict incident or for establishing a service assessment subscription, select a second network entity [e.g., 0AM Al Agent, Al Agent (0AM)] and send a second declarative service request to such second network entity to enable a service risk assessment and / or a resource re-configuration.

[0165] The processor may be further configured to cause the first network entity to: discover and select the second network entity based on at least one of the following parameters: access permissions information, availability information, network reconfiguration and / or service control capabilities, technology domain specific information, service scope in time and geographical space, service constraints due to hardware, software and cost, or reporting capabilities.

[0166] The processor may be further configured to cause the first network entity to: send a second declarative service request to the second network entity that contains at least one of the following parameters: a service request identifier, a scope and / or an objective and / or a type of feasibility or conflict issue faced, a service parameter and / or a service stateDocket No. SMM920250137-GR-NPthat cause a feasibility or conflict issue, a degree that describes a measure of a feasibility or conflict issue, an expected user behaviour during which a feasibility or conflict issue is raised, an acceptable deviation related to the resolution of a feasibility or conflict issue, a priority assigned to the service that faces a feasibility or conflict issue, a service constraint and / or cost related to the resolution of a feasibility or conflict issue, a location and / or a service object and / or an event and / or a time that relates with a feasibility or conflict issue a weight or a utility function that shows the interrelation of the parameters involved in the service where a feasibility or conflict issue is raised, a reporting information related to a feasibility or conflict issue.

[0167] There is further provided herein a second network entity for wireless communication, comprising: at least one memory; and at least one autonomous intelligent logic with the capability to learn from acting; and at least one processor coupled with the at least one memory and intelligent logic, and configured to cause the second network entity to resolve a feasibility or conflict issue by translating a goal, a utility, a requirement related to a second declarative service request into a network resource and determining if the imposed cost constrains and / or other conflicts and risks allows to deploy it on the identified network objects, geographical location and time before indicating the network components to execute it.

[0168] The processor may be further configured to cause the second network entity to: determine a reason regarding its resource re-configuration decision with that reasoning containing at least one of the following pieces of information: a service request identifier, an identifier related to a resource that got re-configured, an identifier related to network objects affected by the resource that got re-configured, an indication of a geographical location and time related with the resource that got re-configured, a degree that measures how much a resource got reconfigured, an indication that determines a potential conflict and / or risk, an indication that determines upon a conflict and / or risk, which way and by what measure if a resource re-configuration affected other services, an indication of a cost related to a resource re-configuration, an indication of a confidence degree related to a resource re-configuration, an indication of a project value of the impact of the resource reDocket No. SMM920250137-GR-NPconfiguration in resolving a feasibility or conflict issue. A reason may contain language based on a language model.

[0169] The processor may be further configured to cause the second network entity to: determine a reason regarding a failure or error related with an attempt to perform a resource re-configuration with that reasoning containing at least one of the following pieces of information: a service request identifier, an identifier related to a resource attempted to get re-configured, an indication of the failure type, an indication of a cost constraint issue, an indication of a user behaviour issue, an indication of a failure related to a service object and / or location and / or time schedule, a recommendation of an alternative resolution for resolving the feasibility or conflict issue. A reason may contain language based on a language model.

[0170] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0171] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.Docket No. SMM920250137-GR-NP

Claims

CLAIMSWhat is claimed is:

1. A first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from an application consumer, an intent service request; transmit, to a second network entity, a resolution request for resolving a feasibility issue for supporting the intent service request; and receive, from the second network entity, a resolution response.

2. The first network entity of claim 1 , wherein the feasibility issue related to at least one of: a lack of resources; a performance drift; a cost issue; or a conflict with a second intent service request.

3. The first network entity of claim 1 or claim 2, wherein the resolution request comprises an indication of at least one of: the feasibility issue; an intent identifier; an operations scope; a service parameter; filter information; a user behavior information; a constraint; reporting information; or a subscription time.Docket No. SMM920250137-GR-NP4. The first network entity of any one of claims 1 to 3, wherein the resolution response comprises an indication of at least one of: an intent identifier; a service parameter impacted by a resource re-configuration; a conflict; a risk; a solution to the feasibility issue; a confidence degree of the solution to the feasibility issue; reasoning for the solution to the feasibility issue; an impacted location; a service object; a cost; or an error notification.

5. The first network entity of any one of claims 1 to 4, wherein the intent service request comprises an indication of at least one of: a goal for an intent service; a utility for the intent service; a requirement for the intent service or a constraint.

6. The first network entity of any one of claims 1 to 5, wherein the at least one processor is further configured to cause the first network entity to: transmit, to a third network entity, a discovery request comprising an indication of at least one of: an Al agent type; an operations scope; a service parameter; filter information; a constraint; reporting information; orDocket No. SMM920250137-GR-NPa subscription time.

7. The first network entity of claim 6, wherein the at least one processor is further configured to cause the first network entity to: receive, from the third network entity, an indication of an Al agent at the second network entity.

8. The first network entity of any one of claims 1 to 7, wherein the resolution request for resolving the feasibility issue comprises a request for at least one of: a service risk assessment; or a resource re-configuration.

9. The first network entity of any one of claims 1 to 8, wherein the at least one processor is further configured to cause the first network entity to: determine the feasibility issue for supporting the intent service request.

10. A method performed or performable by a first network entity, the method comprising: receiving, from an application consumer, an intent service request; transmitting, to a second network entity, a resolution request for resolving a feasibility issue for supporting the intent service request; and receiving, from the second network entity, a resolution response.

11. A second network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second network entity to: receive, from a first network entity, a resolution request for resolving a feasibility issue for supporting an intent service request; and transmit, to the first network entity, a resolution response.Docket No. SMM920250137-GR-NP12. The second network entity of claim 11, wherein the feasibility issue is related to at least one of: a lack of resources; a performance drift; a cost issue or a conflict with a second intent service request.

13. The second network entity of claim 11 or claim 12, wherein the resolution request comprises an indication of at least one of: the feasibility issue; an intent identifier; an operations scope; a service parameter; filter information; a constraint; reporting information; or a subscription time.

14. The second network entity of any one of claims 11 to 13, wherein the resolution response comprises an indication of at least one of: an intent identifier; a service parameter impacted by a resource re-configuration; a conflict; a risk; a solution to the feasibility issue; a confidence degree of the solution to the feasibility issue; reasoning for the solution to the feasibility issue; an impacted location; a service object; or a cost.Docket No. SMM920250137-GR-NP15. A method performed or performable by a second network entity, the method comprising: receiving, from a first network entity, a resolution request for resolving a feasibility issue for supporting an intent service request; and transmitting, to the first network entity, a resolution response.Docket No. SMM920250137-GR-NP

Images