Application route selection policy rules in a wireless communication system
Distinct URSP rules for Al agent traffic in wireless communication systems improve service performance and privacy by optimizing routing and resource allocation, addressing the challenge of differentiated Al agent traffic handling.
Patent Information
- Application Number
- PCT/EP2026/055213
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2026-01-26
- Filing Date
- 2026-02-26
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems lack the ability to differentiate between application traffic and Al agent traffic, leading to suboptimal routing and resource allocation, which can impact service performance, execution speed, and privacy of Al agents.
Implementing distinct URSP rules for Al agent traffic, allowing the UE to selectively route Al agent traffic through appropriate network slices and edge clouds, decoupling it from regular application traffic to ensure optimal performance, security, and privacy.
Enhances Al agent service performance, execution speed, and privacy by optimizing network resource allocation and routing Al agent traffic through dedicated network slices and edge clouds, ensuring efficient and secure communication.
Smart Images

Figure EP2026055213_12112026_PF_FP_ABST
Abstract
Description
APPLICATION ROUTE SELECTION POLICY RULES IN A WIRELESS COMMUNICATION SYSTEMTECHNICAL FIELD
[0001] The present disclosure relates generally to wireless communication, including route selection policy rules for an application.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 a Docket No. SMM920250253-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] A UE for wireless communication is described. The UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the UE may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a first network entity, a first route selection policy rule for traffic of an Artificial Intelligence (Al) agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.
[0005] A method performed or performable by the UE is described herein. The method may comprise: receiving, from a first network entity, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.
[0006] 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 a first network entity, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.
[0007] 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: transmit, to a UE, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.Docket No. SMM920250253-GR-NP
[0008] A method performed or performable by the first network entity is described herein. The method may comprise: transmitting, to a UE, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.
[0009] 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: transmit, to a UE, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.
[0011] Figure 2 illustrates an example of a process flow for UE Route Selection Policy (URSP) rule creation and configuration in accordance with aspects of the present disclosure.
[0012] Figure 3 illustrates an example of a process flow for URSP rule updating in accordance with aspects of the present disclosure.
[0013] Figure 4 illustrates a flowchart of a method for using a URSP rule in accordance with aspects of the present disclosure.
[0014] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure.
[0015] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure.
[0016] Figure 7 illustrates an example of an NE 700 in accordance with aspects of the present disclosure.Docket No. SMM920250253-GR-NP
[0017] Figure 8 illustrates a flowchart of a method 800 performed by a UE in accordance with aspects of the present disclosure.
[0018] Figure 9 illustrates a flowchart of a method 900 performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION
[0019] A wireless communication system may comprise one or more UE and NE. The UE may comprise an application. The UE may be configured to route traffic from the application according to a URSP rule. The URSP rule may be determined by the wireless communication system (e.g., a policy control function (PCF) associated with the wireless communication system) based on connectivity capabilities of the UE and the requirements of the application. However, in cases where the application comprises an Al agent, the traffic of the Al agent may have different routing and / or performance requirements compared to the traffic of the application. The Al agent may be implemented as one or more software processes of the application and executing on one or more processors of the UE.
[0020] Some examples described herein relate to a UE, a first NE and method thereof that tend to improve the service provided by the Al agent by optimizing the service performance and improving network resource allocation for traffic of the Al agent.
[0021] Some examples described herein relate to a UE, a first NE and method thereof that tend to improve the execution speed of an Al agent for an application on the UE. Some examples described herein relate to a UE, a first NE and method thereof that tend to enable the UE to execute an Al agent for an application without providing user information to the network. Some examples described herein relate to a UE, a first NE and method thereof that tend to improve privacy when executing an Al agent for an application.
[0022] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further set forth in the accompanying drawings and the description below. The description set forth herein, in connection with the accompanying drawings, describes example implementations and does not represent all the implementations that may be implemented or that are within the scope Docket No. SMM920250253-GR-NPof the claims. The detailed description includes specific details for the purpose of providing an understanding of the implementations described. These implementations, however, may be practiced without these specific details. Additionally, the description set forth herein, in connection with the accompanying drawings is provided to enable a person having ordinary skill in the art to make or use the present 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 present disclosure. Although aspects of an NR system may be described for purposes of example, and NR terminology may be used in much of the description, the techniques described herein are applicable beyond NR networks. Thus, the present disclosure is not limited to the examples and implementations described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
[0023] 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 (LTE-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.16 (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.
[0024] 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 describedDocket No. SMM920250253-GR-NPherein 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.
[0025] 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.
[0026] 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.
[0027] 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.Docket No. SMM920250253-GR-NP
[0028] An NE 102 may support communications with the CN 106, or with another NE 102, 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).
[0029] 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.
[0030] 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 104 may 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).Docket No. SMM920250253-GR-NP
[0031] 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 5G 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.
[0032] 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., / t=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., / t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / / =1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=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., / t=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.
[0033] 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, for example, 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.Docket No. SMM920250253-GR-NP
[0034] 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., / t=0, / t=l, =2, jtz=3, =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., / t=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0035] 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. In some 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.Docket No. SMM920250253-GR-NP
[0036] 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., / t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / z=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / z=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., =2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / t=3), which includes 120 kHz subcarrier spacing.
[0037] Al agents are software systems that use Al to pursue goals (e.g., goal driven) and complete tasks on behalf of users. Al agents provide reasoning, planning, memory and have a level of autonomy to make decisions or self-initiate tasks, learn, and adapt.
[0038] Al agents may provide the following capabilities including: reasoning that uses logic and available information to draw conclusions e.g., analyze data, identify patterns, and make informed decisions based on evidence and context; planning strategically to achieve goals, e.g., identify the necessary steps, evaluate potential actions considering obstacles, and choose the best course of action based on available information and desired outcomes; observing information about the environment or situation through perception, sensing or interaction with other Al agents; acting to perform tasks based on decisions, plans, or external input, e.g., physical actions or actions like sending messages, updating data, or trigger other processes; collaborating effectively with humans or other Al agents, to achieve common goals. This requires the ability to communicate, understand others and coordinate resolving conflicts; and self-refining from experience, adjusting the behaviour based on feedback, and continuously enhance the performance and capabilities over time.
[0039] An Al Agent may introduce an adaptive repeated control loop that learns, considering a given target goal. It essentially defines a system that relies on the use of a Large Language Model (LLM), which is designed to understand, generate, and work in human language acting as the brain of an Al agent. An Al agent may employ one or more LLMs considering the supported tasks, target performance requirements, e.g., latency constraints, cost, privacy and various data related rules.Docket No. SMM920250253-GR-NP
[0040] An Al agent may also work with other tools including multi-modal tools that introduce different types of non-text input / output, (e.g., sensor data, images, performance measurements), software development tools, other external Application Programming Interface (API)s and services, memory tools (storage, knowledge), autonomous tools (e.g., task planner), Al agent communication protocols, security tools and human interface tools. The adoption of Al agents in the UE may introduce several benefits related to application performance optimization and automation, battery conservation and privacy. An Al agent in the UE may be adopted within an application, e.g., video, gaming, vehicular with each application having the capability to employ its own Al agent within the mobile device operating system or partially offloaded to the edge cloud.
[0041] The Al agent may run in the UE a few limited operations related to data privacy, real-time decisions or handle offline behaviour, e.g., when no network connectivity is possible. The Al agent may be equipped with a Small Language Model (SLM) that offers limited capabilities. On the edge cloud, the Al agent counterpart may host advanced operations, including a large-context LLM, planning and conflict-resolution tools, model update mechanisms, storage and knowledge management components, and access to tool APIs.
[0042] The Al agent in the UE may communicate to the LLM or other related tools via Model Context Protocol (MCP), which allows Al agents to provide context (e.g., user input, system state, or other environment data), instructions to access other tools, external memory and knowledge. The Al agent in the UE may communicate to the LLM or other related tools via Agent-to- Agent (A2A), which allow Al agent cooperation and result exchange allowing discovery assuming the presence of an Al agent registry that hold Al agent information, Al agent capabilities advertisement, task delegation, coordination and negotiation. The Al agent in the UE may communicate to the LLM or other related tools via Representational State Transfer (REST)full APIs or Hypertext Transfer Protocol Secure (HTTPS) + JavaScript Object Notation (JSON) or other existing Multi-access Edge Computing (MEC) related APIs.
[0043] Some examples described herein relate to how an Al agent in the UE discovers and selects counterpart components including LLMs deployed on specific edge clouds,Docket No. SMM920250253-GR-NPwhile ensuring the appropriate connectivity. Some examples described herein leverage URSP rules to enable the UE to select the suitable network route and connectivity (e.g., Domain Name Network (DNN)) for different categories of traffic, including Al agent-related traffic.
[0044] The URSP is generated and provided to the UE by the PCF. URSP rules allow the UE to determine how to route outgoing traffic, e.g., which network route to use for specific traffic, when a traffic descriptor and matching criteria are met. A URSP rule may be triggered by traffic matching. When multiple matching rules are met, the UE may follow priority rules (e.g., precedence) indicated in the URSP rules. When no rule is matched for a new traffic, the UE may employ a default routing logic.
[0045] Traffic may be routed to an established PDU Session. Traffic may be offloaded to non-3GPP access outside a PDU Session. Traffic may be routed via a Proximity-based services (ProSe) Layer-3 UE-to-Network Relay outside a PDU session. Traffic may trigger the establishment of a new PDU Session e.g., according to 3GPP TS 23.503 V20.0.0.
[0046] URSP rule enforcement may comprise all voice traffic being routed to Slice A. URSP rule enforcement may comprise all video traffic for application X being routed to DNN B. A URSP rule may be influenced by the Application Function (AF),. The AF may use access and mobility related policies to determine a URSP rule.
[0047] The PCF may make policy control decisions as elaborated in 3GPP TS 23.503 V20.0.0. The PCF may make Policy and Charging Control (PCC) decisions based on an input. The PCF may make policy control decisions based on operator policy.
[0048] The PCF may make policy control decisions with UE assistance. The UE may indicate, via the Session Management Function (SMF), its connection capabilities to a first PCF (e.g., for providing policies related to PDU sessions). When the first PCF observes a connectivity change, it may notify a second PCF (e.g., for determining the URSP rule) to trigger an update as per clause 4.16.163GPP TS 23.502 V20.0.0. This f may impact the amount of signalling and scalability.
[0049] The PCF may make policy control decisions without UE assistance. The PCF may verify that the traffic follows the URSP rule, e.g., by adopting Analytics ID "PDU Docket No. SMM920250253-GR-NPSession traffic analytics" as per 3GPP TS 23.288 V19.5.0. If the PCF is notified that the UE traffic is not following the URSP rule, the PCF may adjust the URSP rule, e.g., with respect to a specific application. The PCF may adjust the URSP rule for a UE. Adjusting the URSP rule may help overcome policy misconfigurations, Service Level Agreements (SLA) fulfilment and compatibility issues.
[0050] A conventional URSP rule is generated with respect to an application, e.g., per application ID. An Al agent may be inside an application. The Al agent may have the same connectivity characteristics as the application. The Al agent may have different connectivity characteristics to the application. The characteristics of the application may determine whether the Al agent has the same connectivity characteristics as the application. The performance and reliability requirements of the application traffic (e.g., traffic of the application) may differ from the performance and reliability requirements of Al agentic traffic (e.g., traffic of the Al agent).
[0051] Al agentic traffic may be classified and routed differently in the network. Al agentic traffic may be routed to a different edge using distinct port ranges and traffic descriptors. The edge may comprise an end point. A previous URSP rule does not describe Al agentic traffic. A previous URSP rule does not distinguish between Al agentic traffic and application traffic. Some examples described herein relate to a URSP rule that distinguishes between Al agentic traffic and application traffic.
[0052] Some examples described herein relate to an apparatus and a method that introduces URSP rules for assisting the UE to select routes for Al agentic traffic. An Al agent is associated with a specific application, but its traffic characteristics may differ from those of the application itself. In some examples described herein, different URSP rules are applied to application traffic and Al agent traffic, respectively.
[0053] The network (e.g., the PCF) may provide (e.g., send, transmit) two sets of URSP rules to the UE. The PCF may send a first set of URSP rules to the UE and a second set of URSP rules to the UE. For example, the first set of URSP rules may be for an extended Reality / Virtual Reality (XR / VR) streaming application. The XR / VR streaming application may comprise an Al agent for real-time optimization operations (e.g., dynamically adapt service quality, frame rate). The Al agent may provide offloading decisions to a nearby Docket No. SMM920250253-GR-NPedge cloud. The first set of URSP rules may be for the XR / VR streaming application. The second set of URSP rules may be for the Al agentic traffic.
[0054] For example, the first set of URSP rules may comprise rule A. Rule A may comprise routing XR / VR application traffic via an enhanced Mobile Broadband (eMBB) slice. The second set of URSP rules may comprise rule B. Rule B may comprise routing the associated Al Agent traffic using an Ultra-Reliable Low-Latency Communication (URLLC) slice towards a specific DNN. The specific DNN may enable selection of associated agentic tools.
[0055] In some examples described herein, the Al agentic traffic is decoupled from other application related traffic (e.g., traffic of the application). Examples described herein tend to allow rapid or near real-time interaction with potential Al agent tools including LLM located at a nearby edge cloud as the UE can immediately execute a URSP rule. Examples described herein tend to improve service quality that supports Al agentic traffic, e.g., related to an edge located LLM or other tools. Examples described herein tend to improve network resource allocation allowing Al agentic traffic to be steered directly towards the appropriate edge cloud avoiding transversing the core network. Examples described herein tend to enable Al agentic tools service discovery, by pre-configuring the UE with the appropriate URSP rules that provide the suitable connectivity towards the relative DNN. Examples described herein tend to improve security for Al agentic traffic by introducing isolation, e.g., employing a different slice, from other application traffic.
[0056] URSP rules may relate to the URSP rules specified in clause 4.23GPP TS 24.526 V19.3.0. The URSP rules may comprise Al agentic information. The Al agentic information may comprise a traffic descriptor for Al agentic traffic. The traffic descriptor may comprise at least one of one or more Al agent identifiers; or one or more sub-flow distinct identifiers when Al agentic traffic is treated as a part of an application (e.g., a connection capability). The Al agentic information may comprise an indication of Al agent context requirements. The Al agent context requirements may depend on at least one of the Al agent role (e.g., planning, inference); or the type of Al agent interaction including interaction with external tools, e.g., LLM at an edge cloud. The Al agent may require aDocket No. SMM920250253-GR-NPdifferent type of connectivity depending on the Al agent role or type of Al agent interaction.
[0057] In some examples described herein, a default URSP rule may match the application traffic and the Al agentic traffic to a single traffic descriptor. For example, in a specific location in where there is a single connectivity or slice option towards a DNN.
[0058] An AF may indirectly influence the creation of URSP rules for Al agentic traffic. The Al agentic traffic may be associated with an application. The AF may provide to the network (e.g., send to the PCF that determines the URSP for the UE) guidance for URSP determination as per clause 4.10.6.10 TS 23.502 V20.0.0. The guidance for URSP determination may comprise application guidance for handling the traffic of the Al agent of the application.
[0059] The application guidance may comprise at least one of: a service descriptor; or a service parameter for the traffic of the Al agent. The service descriptor may indicate at least one of: an AF-Service-Identifier, an Al Agentic Identifier or a sub-flow identifier, e.g., a connection capability. The service parameters may indicate at least one of: an expected Al agent role; an expected Al agentic interaction type e.g., with other Al agents or edge tools such as LLM; traffic characteristics of Al agentic communications; performance constraints, e.g., latency, reliability, related to Al agentic traffic; or connectivity preferences, e.g., related to a DNN and / or slice, related to Al agentic traffic. Different Al agent roles and Al agentic interactions may be associated with distinct types of traffic characteristics and performance constraints and hence the preference for connectivity may not be the same.
[0060] The UE may configure the URSP rule by updating the UE policy container. The UE may use the URSP rule once an application is launched. The UE may use the URSP rule when a specific traffic flow is initiated. An Al Agent related to an application in a UE (e.g., an Al agent of an application) may evolve via a self-refining process. The selfrefining process may adjust the Al agent depending on at least one of: the environment, consumer feedback, emerging application needs and performance requirements. Once the Al agent evolves, it may change at least one of: its behaviour, its role, or the external tools that it uses. A change to the Al agent may impact the associated traffic patterns, data Docket No. SMM920250253-GR-NPvolume and sensitivity to various performance constraints, e.g., latency. A change to the Al agent may be communicated from the application layer of the UE to the AF. The AF may provide new service parameters related to the Al agentic traffic to the PCF. The PCF may refine (e.g., adapt, modify) the URSP rule. The PCF may send (e.g., transmit) the refined URSP rules to the UE.
[0061] Figure 2 illustrates an example of a process flow 200 for URSP rule creation and configuration in accordance with aspects of the present disclosure. The process flow 200 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 200 may include a UE 210, an AMF 215, a PCF 220 (e.g., PCF for the UE), a User Data Manager (UDM) / User Data Repository (UDR) 230, and an AF 235, which may be one or more examples of devices described herein with reference to Figure 1.
[0062] The process flow 200 may be referred to as a procedure, including one or more operations performed by one or more of the UE 210, AMF 215, PCF 220, UDM / UDR 230, and AF 235. In the example of Figure 2, the process flow 200 may include an overview of URSP rule creation by the PCF and URSP rule configuration in the UE.
[0063] In the following description of the process flow 200, the operations or signalling performed between one or more of the UE 210, AMF 215, PCF 220, UDM / UDR 230, and AF 235 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 UE 210, AMF 215, PCF 220, UDM / UDR 230, and AF 235 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 200. 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.
[0064] Process flow 200 may relate to URSP Rule provision for enabling Applicationbased Al Agentic Services. The UE 210 may be provisioned (signalled) with URSP rules by the PCF 220. The PCF 220 may receive application guidance (via the AF 235) for URSP determination. The AF 235 allows the application to influence the creation of URSP rules indirectly.Docket No. SMM920250253-GR-NP
[0065] The AF 235 may provide application guidance when the service requirements change, e.g., in the context of this invention when an Al agent evolves. The application guidance may be considered by the PCF 220 once received from the AF 235. The application guidance may be stored at the UDR 230. The application guidance may be retrieved from the UDR 230 when needed. The impact of the application guidance in URSP rules is determined by the PCF 220. The PCF 220 may follow, ignore or alter the application guidance.
[0066] The UE policy association establishment among the AMF 215 and PCF 220, is a procedure for the PCF 220 responsible for provisioning UE policies to enable the delivery of URSP rules. The UE policy association establishment may be triggered by the AMF 215 during the UE registration process. The UE policy association establishment may be trigger when a UE 210 requires a policy, e.g., when an application is launched. The UE policy association establishment may be independent of any specific application. Once a policy association exists, the PCF 220 may provide policy updates.
[0067] The PCF 220 may provide a URSP rule when the UE 210 initially registers to the network. The PCF 220 may provide a URSP rule when the UE 210 performs an AMF relocation. The PCF 220 may provide a URSP rule when there is a related modification or feedback from the UE 210. Process flow 200 illustrates the steps related to how URSP rules are created and provisioned to the UE 210. Process flow 200 may be a non-roaming scenario. In a roaming scenario, a visiting PCF may also be involved.
[0068] Process flow 200 starts at step 271 in which the AF 235 sends (e.g., provides, transmits) application guidance to the PCF 220. The application guidance may comprise Al agent related information. The Al agent related information may comprise a service descriptor and / or a service parameter. The PCF 220 may use this information immediately or store it in the UDR 230 for future usage, e.g., to determine or update the respective URSP rules. The interaction with PCF 220 may take place direct if the AF 235 resides in the operator premises or via an NEF if the AF 235 is untrusted. The application guidance may be sent from the AF 235 to the PCF 220 before UE policy association establishment. The application guidance may be stored in the UDR 230. The AF 235 sending theDocket No. SMM920250253-GR-NPapplication guidance to the PCF 220 may trigger an update of URSP rule. The AF 236 may send the application guidance to the PCF 220 if the Al agent evolves.
[0069] In step 272, the AMF 215 stores a UE Policy Container in the UE Context when received from the UE 210. The AMF 215 establishes a UE Policy Association with the PCF 220 considering the value of the UE Policy Association Indicator from the UDM 230. The reception of the UE Policy Container from the UE 210 and the AMF local configuration may be as defined in clause 6.1.2.2.5 of TS 23.503 V20.0.0.
[0070] In step 273, the AMF sends (e.g., transmits) a Npcf_UEPolicyControl Create Request to the PCF 220. The Npcf UEPolicyControl Create Request may comprise at least one of: a Subscription Permanent Identifier (SUPI), an Access Type, a RAT, a Permanent Equipment Identifier (PEI), a User Location Information (ULI), a UE time zone, a Serving Network (e.g., Public Land Mobile Network (PLMN) ID, or NID e.g., see clause 5.34 of TS 23.501 V20.0.0), an Internal-Group-ID-list and UE Policy Container (e.g., a list of stored Public Service Identifiers (PSIs), an operating system identifier, an indication of UE support for Access Network Discovery & Selection Policy (ANDSP), an indication of UE capability of reporting URSP rule enforcement to network, or an indication of support of URSP delivery in EPS.
[0071] During UE initial registration, the AMF 215 may receive information from the UE 210. The AMF 215 may receive an indication of support of Non-3GPP InterWorking Function (N3IWF) selection from the UE 210. The AMF 215 may receive an indication of UE support for a Trusted Non-3GPP Gateway Function (TNGF) selection. The TNGF selection may be based on the slices the UE wishes to use over trusted non-3GPP access. The AMF 215 may send the information received from the UE 210 to the PCF 220.
[0072] In step 274, the PCF 220 may invoke the UDM / UDR 230 to retrieve (e.g., receive, obtain) at least one of: policy control subscription data or application guidance on the URSP Rule including information related to Al agents of an application. When a UE Policy Container is received at initial registration, the PCF 220 may store the PEI, the Operating System Identifier (OSId), the indication of UE capability of reporting URSP rule enforcement to network, the indication of support of URSP delivery in EPS or theDocket No. SMM920250253-GR-NPindication of UE support for ANDSP in the UDR using Nudr DM Create including DataSet "Policy Data" and Data Subset "UE context policy control data".
[0073] In step 275, the PCF 220 evaluates the subscription data, application guidance including Al agent related information and / or operator policy to create a URSP rule (including a URSP rule for Al agentic traffic). Each URSP rule may comprise at least one of: a precedence, a traffic descriptor, or a route selection.
[0074] In step 276, the PCF 220 sends (e.g., transmits) an Npcf_UEPolicyControl Create Response to the AMF 215. The Npcf UEPolicyControl Create Response may comprise at least one of: a UE policy, a URSP rule, or other policy information e.g., as described in clause 6.6.2.2 TS 23.503 V20.0.0.
[0075] In step 277, the PCF 220 triggers a UE Configuration Update Procedure. The PCF 220 sends (e.g., transmits) the UE policy container to the UE 210. The UE receives the UE policy container which triggers the UE 210 to configure the provided URSP rule. The UE 210 may configure the URSP rule related to the Al agentic traffic. The UE 210 may update the URSP rule relate to the Al agentic traffic.
[0076] When a Policy Control Request Trigger condition is met, the AMF 215 updates UE Policy Control Association and indicates the conditions that have changed to the PCF 220. The AMF 215 sends (e.g., transmits) a Npcf_UEPolicyControl Update Request comprising at least one of: a UE Policy Association ID, an Al agent ID, an application subflow ID, or a connection capabilities ID (e.g., if an application includes an Al agent). The connection capability ID may be associated with the SUPI defined in TS 29.525 V19.5.0. The PCF 220 may update the policy information including the URSP rule. The PCF 220 may provide the policy information including the URSP rule back invoking aNpcf UEPolicyControl Update response. A similar process may also apply upon an AMF relocation.
[0077] UE Policy Association establishment is a baseline control-plane procedure that creates a relationship between the UE 210 and the PCF 220. The AF 235 may provide input for the policy. The input from the AF 235 may be event driven. The input from the AF 235 may trigger changes to policies (e.g., URSP) e.g., to an existing policy.Docket No. SMM920250253-GR-NP
[0078] Figure 3 illustrates an example of a process flow 300 for URSP rule updating in accordance with aspects of the present disclosure. The process flow 300 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 300 may include a UE 310, an AMF 315, a first PCF 320 (e.g., PCF for the UE), a second PCF 325 (e.g., PCF for the PDU session), an SMF 340, and an NWDAF 345, which may be one or more examples of devices described herein with reference to Figure 1.
[0079] The process flow 200 may be referred to as a procedure, including one or more operations performed by one or more of the UE 310, AMF 315, first PCF 320 (e.g., PCF for the UE), second PCF 325 (e.g., PCF for the PDU session), SMF 340, and NWDAF 345. In the example of Figure 3, the process flow 300 may include an overview of URSP rule update based on UE 310 assistance.
[0080] In the following description of the process flow 300, the operations or signalling performed between one or more of the UE 310, AMF 315, first PCF 320 (e.g., PCF for the UE), second PCF 325 (e.g., PCF for the PDU session), SMF 340, and NWDAF 345 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 UE 310, AMF 315, first PCF 320 (e.g., PCF for the UE), second PCF 325 (e.g., PCF for the PDU session), SMF 340, and NWDAF 345 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 300. 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
[0081] Some examples described herein relate to updating the URSP Rule for battery saving using UE Assistance. The UE 310 may assist the process of URSP rule adjustment by providing feedback. The UE 310 feedback may not involve evaluating each URSP rule. The UE 310 may report, to the SMF 340, at least one of: an event (e.g., mobility), a connectivity capability, or network context information. In response to receiving the report from the UE 310, the SMF reports the update to the second PCF 325, which assesses the impact on existing PDU sessions and, if required, triggers the first PCF 320 to re-evaluate and update the URSP rule. The first PCF 320 may send (e.g., transmit) the updated URSPDocket No. SMM920250253-GR-NPrule to the UE 310. The URSP rule may be updated or re-evaluated periodically. The URSP rule may be updated based on at least one of: a location change, an access change that may cause a PDU session release, the expiration of a time window related to a specific route selection, or AF updates in the application guidance including Al agentic traffic.
[0082] Process flow 300 illustrates a process of updating URSP rules based on UE assistance considering support for battery saving.
[0083] Process flow starts at step 371 in which the UE Policy Association is established; for example using process flow 200 described above in relation to Figure 2.
[0084] In step 372, the first PCF 320 indicates to the UE 310 to send reporting of URSP rule enforcement as described in clause 6.6.2.4 of TS 23.503 V20.0.0. This reporting may include connectivity capabilities.
[0085] In step 373, the first PCF 320 responsible for the UE policy subscribes to obtain notifications of the event "UE reporting Connection Capabilities from associated URSP rule" as defined in clause 6.1.3.18 of TS 23.503 V20.0.0 from the second PCF 325 that handles the policy related to the PDU Session. In response, the second PCF 325 may provide connection capabilities and / or network context e.g., following the steps 3 to 6 as specified in Figure 4.16.16.2-1 of TS 23.502 V20.0.0.
[0086] The context related to the PDU session serves as an information source for determining a performance of the URSP rule. In option 1, the context related to the PDU session may be obtained in steps 374 and 375.
[0087] In step 374, the UE 310 sends (e.g., transmits, provides) a report of URSP rule enforcement to the SMF 340 (e.g., serving SMF). The SMF 340 may receive a UE report of URSP rule enforcement via a PDU session modification.
[0088] In step 375, the SMF 340 sends (e.g., transmits, reports) the received information to the second PCF 325 serving the PDU Session, by invoking Npcf_SMPolicyControl_Update e.g., as defined in clause 6.1.3.5 of TS 23.503 V20.0.0.
[0089] Alternatively, or in addition, in option 2 the context related to the PDU session may be obtained in step 376. In step 376, the second PCF 325 may be informed regardingDocket No. SMM920250253-GR-NPpotential changes on ongoing PDU sessions. The second PCF 325 r may subscribe to the NWDAF 245 for notifications regarding PDU session performance. The notification may use an Analytics ID = “PDU Session traffic”. The notifications may use traffic descriptors. The traffic descriptors may comprise at least one of: Single - Network Slice Selection Assistance Information (S-NSSAI), DNN, Application Identifier, ID - including Al agent ID, application sub-flow ID, or connection capabilities ID (e.g., if an application includes the Al agent). The notifications may be used to determine whether observed traffic matches the URSP rule traffic.
[0090] In step 377, the second PCF 325 may evaluate the UE report in correlation to other information received from NWDAF 345. The second PCF 325 may determine whether there is an impact related to the existing URSP rule. The impact may be in terms of at least one of: an application ID (including Al agent ID or application sub-flow ID), or a connection capabilities ID (if an application also includes an Al agent). The impact may serve as a trigger to inform the first PCF 320.
[0091] In step 378, the first PCF 320 is notified, by the second PCF 325, on the "UE reporting Connection Capabilities from associated URSP rule" by aNpcf PolicyAuthorization Notify service (including NotificationCorrelationld, Eventld set to "UE reporting Connection Capabilities from associated URSP rule", Eventinformation including the Connection Capabilities) e.g., as defined in clause 6.1.3.18 of TS 23.503 V20.0.0.
[0092] In step 379, the first PCF 320 checks the operator policies and may make policy control decisions related to URSP rule updates (e.g., with respect to an application ID and / or Al agent if an application supports also Al agent services) based on awareness of the UE report and other information e.g., as described in clause 6.1.1.5 of TS 23.503 V20.0.0.
[0093] In step 380, the first PCF 320 triggers a UE Configuration Update Procedure to send the UE policy container and trigger the UE to configure the provided URSP rules. This procedure may be performed to update URSP rules related to Al agentic traffic associated with a specific application.Docket No. SMM920250253-GR-NP
[0094] Figure 4 illustrates a flowchart 400 of a method for using a URSP rule in accordance with aspects of the present disclosure. Once URSP rules are created and configured to the UE, the UE may use them for specific applications including also associated Al agentic traffic. Flowchart 400 provides an overview of a process where an application “APP A” in a UE with Al agent capabilities “AIA B” leverages the benefits of edge cloud by allowing the Al agent to obtain from and edge cloud the desired LLM services “LLM_C”. Process flow 400 provides an overview of a process where a UE Application with Al agent capabilities use URSP rules for allowing the Al Agent to obtain LLM service from edge cloud.
[0095] Process flow 400 starts at step 401 in which the UE launches application APP A, which contains Al agent capabilities, e.g., AIA B. The operation of the AIA B requires an LLM service named LLM C, which may be obtained from the network edge cloud.
[0096] In step 402, the UE generates two types of traffic: application traffic related to APP A and Al agent traffic related to Al A B.
[0097] In step 403, the UE checks whether a pre-configured URSP rule matches the traffic of application APP A and / or the Al agent AIA B. If a match is found, the UE applies the corresponding URSP rule to enable the AIA B traffic to reach the target LLM service LLM_C via the specified DNN.
[0098] In step 404, if no suitable PDU session exists, the UE establishes a PDU session toward the indicated DNN to provide LLM C connectivity for the AIA B service, in accordance with the URSP rules. The PDU session is established through the RAN and UPF that enables DNN connectivity, with potential slice isolation if needed and the desired Quality of Service (QoS) enforcement.
[0099] In step 405, once the PDU session connectivity is establish towards the specified DNN, a DNS query is issued to discover the address of the desired LLM_C service.Optionally the DNN may be equipped with a gateway functionality that performs authentication and takes extra security measures related to the access of specific services.Docket No. SMM920250253-GR-NP
[0100] In step 406, the AIA B may then consume the required LLM C services, provided that connectivity, authentication, and service discovery have been successfully completed.
[0101] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure. The UE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, 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.
[0102] The processor 502, the memory 504, the controller 506, or the transceiver 508, 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.
[0103] The processor 502 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 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502. The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the UE 500 to perform various functions of the present disclosure.
[0104] The memory 504 may include volatile or non-volatile memory. The memory 504 may store computer-readable, computer-executable code including instructions when executed by the processor 502 cause the UE 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 504 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-transitoryDocket No. SMM920250253-GR-NPstorage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
[0105] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the UE 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504). For example, the processor 502 may support wireless communication at the UE 500 in accordance with examples as disclosed herein. The UE 500 may be configured to support a means for receiving, from a first network entity, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.
[0106] The controller 506 may manage input and output signals for the UE 500. The controller 506 may also manage peripherals not integrated into the UE 500. In some implementations, the controller 506 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.
[0107] In some implementations, the UE 500 may include at least one transceiver 508. In some other implementations, the UE 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.
[0108] A receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 510 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 510 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 510 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.Docket No. SMM920250253-GR-NP
[0109] A transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 512 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 512 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 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0110] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure. The processor 600 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 600 may include a controller 602 configured to perform various operations in accordance with examples as described herein. The processor 600 may optionally include at least one memory 604, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 600 may optionally include one or more arithmetic-logic units (ALUs) 606. 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).[OHl] The processor 600 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. The 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 600) 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).Docket No. SMM920250253-GR-NP
[0112] The controller 602 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 600 to cause the processor 600 to support various operations in accordance with examples as described herein. For example, the controller 602 may operate as a control unit of the processor 600, generating control signals that manage the operation of various components of the processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0113] The controller 602 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 604 and determine subsequent instruction(s) to be executed to cause the processor 600 to support various operations in accordance with examples as described herein. The controller 602 may be configured to track memory address of instructions associated with the memory 604. The controller 602 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 602 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 602 may be configured to manage flow of data within the processor 600. The controller 602 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 600.
[0114] The memory 604 may include one or more caches (e.g., memory local to or included in the processor 600 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 604 may reside within or on a processor chipset (e.g., local to the processor 600). In some other implementations, the memory 604 may reside external to the processor chipset (e.g., remote to the processor 600).
[0115] The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 600, cause the processor 600 to perform various functions described herein. The code may be stored in a non-transitoryDocket No. SMM920250253-GR-NPcomputer-readable medium such as system memory or another type of memory. The controller 602 and / or the processor 600 may be configured to execute computer-readable instructions stored in the memory 604 to cause the processor 600 to perform various functions. For example, the processor 600 and / or the controller 602 may be coupled with or to the memory 604, the processor 600, the controller 602, and the memory 604 may be configured to perform various functions described herein. In some examples, the processor 600 may include multiple processors and the memory 604 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.
[0116] The one or more ALUs 606 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 606 may reside within or on a processor chipset (e.g., the processor 600). In some other implementations, the one or more ALUs 606 may reside external to the processor chipset (e.g., the processor 600). One or more ALUs 606 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 606 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 606 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 606 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations.
[0117] The processor 600 may support wireless communication in accordance with examples as disclosed herein. The processor 600 may be configured to support a means for receiving, from a first network entity, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application. The processor 600 may be configured to or operable to support a means for transmitting, to a UE, a first route selection policy rule for traffic of an Al agent of an application, wherein the first routeDocket No. SMM920250253-GR-NPselection policy rule is different to a second route selection policy rule for traffic of the application.
[0118] Figure 7 illustrates an example of a NE 700 in accordance with aspects of the present disclosure. The NE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, 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.
[0119] The processor 702, the memory 704, the controller 706, or the transceiver 708, 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.
[0120] The processor 702 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 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the NE 700 to perform various functions of the present disclosure.
[0121] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the NE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 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.Docket No. SMM920250253-GR-NP
[0122] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the NE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the NE 700 in accordance with examples as disclosed herein. The NE 700 may be configured to support a means for transmitting, to a UE, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.
[0123] The controller 706 may manage input and output signals for the NE 700. The controller 706 may also manage peripherals not integrated into the NE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.
[0124] In some implementations, the NE 700 may include at least one transceiver 708. In some other implementations, the NE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.
[0125] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 710 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 710 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0126] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 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 Docket No. SMM920250253-GR-NPmore 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 712 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 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0127] Figure 8 illustrates a flowchart of a method 800 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.
[0128] At 802, the method 800 may include receiving, from a first network entity, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application. The operations of 802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a UE as described with reference to Figure 5.
[0129] It should be noted that the method 800 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.
[0130] Figure 9 illustrates a flowchart of a method 900 in accordance with aspects of the present disclosure. The operations of the method 900 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.
[0131] At 902, the method 900 may include transmitting, to a UE, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a NE as described with reference to Figure 7.Docket No. SMM920250253-GR-NP
[0132] It should be noted that the method 900 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.
[0133] There is provided herein a UE 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 UE to: receive, from a first network entity, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application. Such a UE tends to improve the performance of the Al agent service. The UE tends to optimize the network resource allocation for the traffic of the Al agent of the application.
[0134] The traffic of the Al agent may be different to the traffic of the application. The traffic of the Al agent may be separate from the traffic of the application. The Al agent may be part of the application. The Al agent may be a capability of an application. The traffic of the Al agent may comprise a sub-flow of the traffic of the application. The first route selection policy rule may comprise an indication of at least one of: a first traffic descriptor that identifies the traffic of the Al agent; a second traffic descriptor that identifies a subflow of the application or a connection capability of an application, wherein the sub-flow of the application comprises the traffic of the Al agent; or an Al agent context requirement.
[0135] The at least one processor may be further configured to cause the UE to configure traffic of the Al agent according to the first route selection policy rule. The first traffic descriptor may identify traffic of the Al agent that is different to the traffic of the application. The first traffic descriptor may identify traffic of the Al agent that is separate from the traffic of the application. The second traffic descriptor may identify traffic of the Al agent that comprises a sub-flow or a connection capability of the traffic of the application.
[0136] The at least one processor may be further configured to cause the UE to: transmit, to a session management function, SMF, a connectivity capability of the UE for updating the first route selection policy rule. The first route selection policy rule may map the traffic of the Al agent to the connectivity capability of the UE. The connectivity capability of the UE may relate to at least one of: a supported network slice, a supported Docket No. SMM920250253-GR-NPDNN, a supported cloud, a supported access type, or a supported PDU session type. The connectivity capability of the UE may comprise an indication enforcement of the first route selection policy rule. The connectivity capability of the UE may comprise an indication of first route selection policy rule enforcement.
[0137] The SMF may send an indication of the connectivity capability of the UE to a second network entity. The second network entity may comprise a second PCF. The second PCF mat comprise a PCF (for the PDU session). The second network entity may receive, from an NWDAF, PDU session performance analytics. The PDU session performance analytics may indicate whether the traffic of the Al agent matches the first route selection policy rule. The second network entity may determine, based on the indication of the connectivity capability of the UE, that the first route selection policy rule should be updated. The second network entity may determine, based on the PDU session performance analytics, that the first route selection policy rule should be updated. The second network policy may send, to the first network entity, an indication that the first route selection policy rule should be updated. The indication that the first route selection policy rule should be updated may comprise an indication of the connectivity capability of the UE. The first network entity may update the first route selection policy rule based on the connectivity capability of the UE.
[0138] The at least one processor may be further configured to cause the UE to: receive, from the first network entity, the second route selection policy rule for traffic of the application. The at least one processor may be further configured to cause the UE to update a policy container of the UE based on the second route selection policy rule. The at least one processor may be further configured to cause the UE to configuring traffic of the application according to the second route selection policy rule. The at least one processor may be further configured to cause the UE to: update a policy container of the UE based on the first route selection policy rule.
[0139] The at least one processor may be further configured to cause the UE to: transmit the traffic of the Al agent of the application according to the first route selection policy rule. Transmitting the traffic of the Al agent of the application according to the firstDocket No. SMM920250253-GR-NProute selection policy rule may comprise routing the traffic of the Al agent of the application according to the first route selection policy rule.
[0140] There is further provided herein a method performed or performable by a UE the method comprising: receiving, from a first network entity, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application. Such a method performed or performable by the UE tends to improve the performance of the Al agent service. The method tends to optimize the network resource allocation for the traffic of the Al agent of the application. Al agentic traffic may be routed to a different edge, e.g., end point, using distinct port ranges and traffic descriptors. The method may provide a URSP rule for Al agentic traffic. The method tends to distinguish how to handle Al agentic traffic from application traffic.
[0141] The first route selection policy rule may comprise an indication of at least one of: a first traffic descriptor that identifies the traffic of the Al agent; a second traffic descriptor that identifies a sub-flow or a connection capability of the application, wherein the sub-flow or a connection capability of the application comprises the traffic of the Al agent; or an Al agent context requirement. The method may further comprise transmitting, to a SMF, a connectivity capability of the UE for updating the first route selection policy rule. The method may further comprise receiving, from the first network entity, the second route selection policy rule for traffic of the application. The method may further comprise updating a policy container of the UE based on the first route selection policy rule. The method may further comprise transmitting the traffic of the Al agent of the application according to the first route selection policy rule.
[0142] There is further 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: transmit, to a UE, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application. Such a first network entity tends to improve responsiveness of theDocket No. SMM920250253-GR-NPAl agentic traffic performance, optimize the performance of Al agent service and improve the network resource allocation for the traffic of the Al agent of the application.
[0143] The first network entity may comprise a first PCF. The first route selection policy rule may comprise a first URSP rule. The first route selection policy rule may relate to network connectivity of the traffic of the Al agent of the application. The first route selection policy rule may relate to route selection of the traffic of the Al agent of the application. The second route selection policy rule may relate to network connectivity of the traffic of the application. The second route selection policy rule may relate to route selection of the traffic of the application.
[0144] The second route selection policy rule may comprise a second URSP rule. The application may run on the UE. The Al agent may run on the UE. The Al agent may be part of the application. The Al agent may be a capability of an application. The traffic of the Al agent may comprise Al agent traffic related to interaction with other Al agents or with relevant Al agents’ tools, e.g. LLM. The traffic of the Al agent may comprise Al agentic traffic. The traffic of the Al agent may be generated by the UE. The traffic of the application may be generated by the UE. The traffic of the application is different from the traffic of the Al agent of the application and has different performance characteristics.
[0145] The at least one processor may be further configured to cause the first network entity to transmit, to a UDM, the first route selection policy rule. The UDM may store the first route selection policy rule. The at least one processor may be further configured to cause the first network entity to retrieve (e.g., receive), from the UDM, the first route selection policy rule.
[0146] The first route selection policy rule may comprise an indication of at least one of: a first traffic descriptor that identifies the traffic of the Al agent; a second traffic descriptor that identifies a sub-flow or connection capability of the application, wherein the sub-flow of the application comprises the traffic of the Al agent; or an Al agent context requirement. The traffic descriptor identifying the traffic of the Al agent of the application may comprise a traffic descriptor to distinct Al agentic traffic. The traffic descriptor may be a traffic descriptor for Al agentic traffic. The at least one processor may be furtherDocket No. SMM920250253-GR-NPconfigured to cause the first network entity to determine the first route selection policy rule based on the received information for determining the first route selection policy rule.
[0147] The at least one processor may be further configured to cause the first network entity to: receive information for determining the first route selection policy rule, wherein the information for determining the first route selection policy rule comprises information related to at least one of a network condition; UE subscription information; analytics of connectivity performance; a connectivity capability of the UE; or application guidance for handling the traffic of the Al agent of the application. The information may comprise Al agent related information. The Al agent related information may include service description and / or service parameters.
[0148] The application guidance for handling the traffic of the Al agent of the application may comprise at least one of a service descriptor received from an AF; a service parameter for the traffic of the Al agent, wherein the service parameter is received from the AF; policy control subscription data received from a UDM; or information related to the Al agent received from a UDR. The first information related to the Al agent may comprise service parameters related to the traffic of the Al agent. The first information related to the Al agent may comprise application guidance for URSP determination. The first information related to the Al agent may comprise guidance for determining URSP rules. The service descriptor may comprise a service description. The service descriptor may comprise a connectivity capability of the application for the traffic of the Al agent.
[0149] The service parameter may comprise information related to at least one of a role of the Al agent; an interaction type of the Al agent; a characteristic of communication of the Al agent; a performance constraint of the Al agent; or a connectivity preference of the Al agent. The at least one processor may be further configured to cause the first network entity to: update the first route selection policy rule based on the information for determining the first route selection policy rule or updated application guidance information. The updated application guidance information may be generated by the AF. The AF may generate the updated application guidance information in response to receiving, from the UE, a notification that the Al agent has evolved. The notification that the Al agent has evolved may be generated by the application. The notification that the AlDocket No. SMM920250253-GR-NPagent has evolved may be generated by the Al agent. If the UE is already configured with a first route selection policy rule, this may need to be updated. Such an update may be required in response to a change in information for determining the first route selection policy rule. The at least one processor may be further configured to cause the first network entity to: receive, from a second network entity, an indication that the first route selection policy rule should be updated. The at least one processor may be further configured to cause the first network entity to: transmit, to the UE, the second route selection policy rule for traffic of the application.
[0150] There is further provided herein a method performed or performable by a first network entity, the method comprising: transmitting, to a UE, a first route selection policy rule for traffic of an Al agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application. Such a method performed or performable by the first network entity tends to improve responsiveness of the Al agentic traffic performance, optimize the performance of Al agent service and improve the network resource allocation for the traffic of the Al agent of the application.
[0151] The first route selection policy rule may comprise an indication of at least one of: a first traffic descriptor that identifies the traffic of the Al agent; a second traffic descriptor that identifies a sub-flow or connection capability of the application, wherein the sub-flow of the application comprises the traffic of the Al agent; or an Al agent context requirement. The method may further comprise receiving information for determining the first route selection policy rule, wherein the information for determining the first route selection policy rule comprises information related to at least one of: a network condition; UE subscription information; analytics of connectivity performance; a connectivity capability of the UE; or application guidance for handling the traffic of the Al agent of the application.
[0152] The application guidance for handling the traffic of the Al agent of the application may comprise at least one of: a service descriptor received from an AF; a service parameter for the traffic of the Al agent, wherein the service parameter is received from the AF; policy control subscription data received from a UDM; or informationDocket No. SMM920250253-GR-NPrelated to the Al agent received from a UDR. The service parameter may comprise information related to at least one of: a role of the Al agent; an interaction type of the Al agent; a characteristic of communication of the Al agent; a performance constraint of the Al agent; or a connectivity preference of the Al agent. The method may further comprise updating the first route selection policy rule based on the information for determining the first route selection policy rule or updated application guidance information. The updated application guidance information may be generated by the AF. The AF may generate the updated application guidance information in response to receiving, from the UE, a notification that the Al agent has evolved. The notification that the Al agent has evolved may be generated by the application. The notification that the Al agent has evolved may be generated by the Al agent. The method may further comprise transmitting, to the UE, the second route selection policy rule for traffic of the application.
[0153] Previously, URSP rules were generated with respect to specific applications. An Al agent that supports an application may have different traffic characteristics and require a connectivity towards a specific DNN via a certain network slice and / or separate PDU session. Some examples described herein relate to the decoupling of application traffic and Al agentic traffic. The Al agentic traffic may have stringent performance, security and reliability requirements.
[0154] Some examples described herein introduce URSP rules that assist the UE to select routes for Al agentic traffic that is associated with a specific application, but its traffic characteristics may differ. In some examples described herein, the URSP rules identify an Al agent, either through an explicit Al agent identifier or by treating the Al agent as a distinct application connectivity capability, considering the Al agent role and interactions with other tools. Al agent-related information may be provided by the application (e.g., via the AF) to guide the policy function responsible for the creation and update of URSP rules. The AF may update this guidance to reflect Al agent evolution based on input received from the UE application client. Previous solutions based on URSP rules do not address UE Al agentic traffic associated with an application having different traffic characteristics. Some examples described herein relate to URSP Rule provision forDocket No. SMM920250253-GR-NPenabling Application-based Al Agentic Services. Some examples described herein relate to URSP Rule Updates for Battery Saving with UE Assistance.
[0155] There is further provided herein a first network entity [e.g., PCF for URSP Rules] 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: determine URSP rules related to Al agentic traffic that is different from the application it supports and runs in a mobile equipment entity, and send these URSP rules to the mobile equipment for local configuration, enabling optimization of the Al agent service through improved route selection and / or network connectivity.
[0156] The URSP rules related to Al agentic traffic may be determined based on at least: the information related to network conditions, the analytics related to the related connectivity performance, the information from the mobile equipment related to its connectivity capabilities, and the application guidance information related to handling of the Al agentic traffic. The application guidance information may contain at least: a service descriptor related to an identifier of the Al agentic traffic or to a connectivity capability of the application related to Al agentic traffic, and a service parameter related to Al agentic traffic.
[0157] The service parameter related to Al agentic traffic may contains at least: information related to an Al agent role, information related to an Al agent interaction type a characteristic of Al agentic communication a performance constraint related to Al agentic service, and a connectivity preference related to Al agentic traffic. A first network entity may receive new application guidance information that reflect the traffic requirements of the evolved Al agent.
[0158] There is further provided herein a mobile equipment in wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and communication modem, which is configured to cause the mobile equipment to: separate the application traffic from the supporting Al agentic traffic, and configure and use a different URSP rules for network connectivity and route selection related to an application and supporting Al agent traffic. The usage of pre-configured URSP rules related to Al agentic traffic may: assure a rapid connectivity and interaction towards other Docket No. SMM920250253-GR-NPAl agents or potential Al agent tools, optimize the network resources by steering Al agentic traffic towards the most efficient interaction point, resolve Al agent service discovery related operations towards other Al agent or tools, or enhance security for Al agentic traffic by introducing isolation and enhanced authentication. The evolution of Al agent in the application client may: trigger an information exchange to update to the application server, and cause an update from the application service to the network policy providing new guidance information for creating URSP rules updates.
[0159] 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.
[0160] 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. SMM920250253-GR-NP
Claims
CLAIMSWhat is claimed is:
1. A user equipment, UE, for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the UE to:receive, from a first network entity, a first route selection policy rule for traffic of an artificial intelligence, Al, agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.
2. The UE of claim 1, wherein the first route selection policy rule comprises an indication of at least one of:a first traffic descriptor that identifies the traffic of the Al agent;a second traffic descriptor that identifies a sub-flow of the application, wherein the sub-flow of the application comprises the traffic of the Al agent; oran Al agent context requirement.
3. The UE of claim 1 or claim 2, wherein the at least one processor is further configured to cause the UE to:transmit, to a session management function, SMF, a connectivity capability of the UE for updating the first route selection policy rule.
4. The UE of any one of claims 1 to 3, wherein the at least one processor is further configured to cause the UE to:receive, from the first network entity, the second route selection policy rule for traffic of the application.
5. The UE of any one of claims 1 to 4, wherein the at least one processor is further configured to cause the UE to:update a policy container of the UE based on the first route selection policy rule.Docket No. SMM920250253-GR-NP6. The UE of any one of claims 1 to 5, wherein the at least one processor is further configured to cause the UE to:transmit the traffic of the Al agent of the application according to the first route selection policy rule.
7. A method performed or performable by a user equipment, UE, the method comprising:receiving, from a first network entity, a first route selection policy rule for traffic of an artificial intelligence, Al, agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.
8. A first network entity for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the first network entity to:transmit, to a user equipment, UE, a first route selection policy rule for traffic of an artificial intelligence, Al, agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.
9. The first network entity of claim 8, wherein the first route selection policy rule comprises an indication of at least one of:a first traffic descriptor that identifies the traffic of the Al agent;a second traffic descriptor that identifies a sub-flow of the application, wherein the sub-flow of the application comprises the traffic of the Al agent; oran Al agent context requirement.
10. The first network entity of claim 8 or claim 9, wherein the at least one processor is further configured to cause the first network entity to:Docket No. SMM920250253-GR-NPreceive information for determining the first route selection policy rule, wherein the information for determining the first route selection policy rule comprises information related to at least one of:a network condition;a UE subscription information;analytics of connectivity performance;a connectivity capability of the UE; orapplication guidance for handling the traffic of the Al agent of the application.
11. The first network entity of claim 10, wherein the application guidance for handling the traffic of the Al agent of the application comprises at least one of:a service descriptor received from an application function, AF;a service parameter for the traffic of the Al agent, wherein the service parameter is received from the AF;policy control subscription data received from a unified data management, UDM; orinformation related to the Al agent received from a unified data repository, UDR.
12. The first network entity of claim 11, wherein the service parameter comprises information related to at least one of:a role of the Al agent;an interaction type of the Al agent;a characteristic of communication of the Al agent;a performance constraint of the Al agent; ora connectivity preference of the Al agent.
13. The first network entity of any one of claims 8 to 12, wherein the at least one processor is further configured to cause the first network entity to:update the first route selection policy rule based on at least:the information for determining the first route selection policy rule; or updated application guidance information.Docket No. SMM920250253-GR-NP14. The first network entity of any one of claims 8 to 13, wherein the at least one processor is further configured to cause the first network entity to:transmit, to the UE, the second route selection policy rule for traffic of the application.
15. A method performed or performable by a first network entity, the method comprising:transmitting, to a user equipment, UE, a first route selection policy rule for traffic of an artificial intelligence, Al, agent of an application, wherein the first route selection policy rule is different to a second route selection policy rule for traffic of the application.Docket No. SMM920250253-GR-NP
