Artificial Intelligence and Machine Learning Technologies for Wireless Communications

Abstract

Artificial intelligence and machine learning techniques for wireless communications are provided. The present application relates to devices and components, including apparatus, systems and methods for application functions (AF) to directly access radio access network (RAN) management functions.

Description

[0001] Cross-references to other applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 541,620, filed on September 29, 2023, entitled “ARTIFICIAL INTELLIGENCE AND MACHINE LEARNING TECHNOLOGIES FOR WIRELESS COMMUNICATION,” which is incorporated herein by reference in its entirety for all purposes. Technical Field

[0003] The present application relates generally to communication networks, and in particular to techniques for influencing network functions through application functions. Background Art

[0004] Artificial intelligence and machine learning (AIML) can be used in wireless communications to automate tasks, optimize network resources, or predict and mitigate problems. AIML models can be used to optimize radio resource management (RRM) parameters such as channel allocation, power control, or scheduling. AIML can be used for mobility management, interference management, or security threat detection.

[0005] For example, AIML models and algorithms can be used in 3GPP networks in the context of network slicing. AIML can be used to automate the deployment and management of network slices. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 A network environment according to some embodiments is illustrated.

[0007] Figure 2 An operational flow / algorithm structure according to some embodiments is illustrated.

[0008] Figure 3 Signaling diagrams according to some embodiments are illustrated.

[0009] Figure 4 A network environment according to some embodiments is illustrated.

[0010] Figure 5 Signaling diagrams according to some embodiments are illustrated.

[0011] Figure 6 An operational flow / algorithm structure according to some embodiments is illustrated.

[0012] Figure 7 An operational flow / algorithm structure according to some embodiments is illustrated.

[0013] Figure 8An operational flow / algorithm structure according to some embodiments is illustrated.

[0014] Fig. 9 User equipment according to some embodiments is illustrated.

[0015] Fig.10 A network node according to some embodiments is illustrated. DETAILED DESCRIPTION

[0016] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of explanation rather than limitation, specific details, such as specific structures, architectures, interfaces and / or technologies, are set forth to provide a thorough understanding of the various aspects of some embodiments. However, it is apparent to those skilled in the art who benefit from the present disclosure that various aspects of various aspects can be practiced in other examples that depart from these specific details. In some cases, the description of well-known equipment, circuits and methods is omitted so that the description of various aspects will not be obscured by unnecessary details. For the purpose of this document, the phrase "A or B" refers to (A), (B) or (A and B), and the phrase "based on A" refers to "based at least in part on A", for example, it can be "based only on A" or it can be "based in part on A".

[0017] The following is a glossary of terms that may be used in this disclosure.

[0018] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functionality, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), and / or a digital signal processor (DSP). In some aspects, a circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for executing the functionality of the program code (or a combination of circuits used in an electrical or electronic system). In these aspects, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0019] As used herein, the term "processor circuit" refers to, is part of, or includes: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations; or recording, storing, or transferring digital data. The term "processor circuit" may refer to an application processor; a baseband processor; a central processing unit (CPU); a graphics processing unit; a single-core processor; a dual-core processor; a triple-core processor; a quad-core processor; or any other device capable of executing or otherwise operating computer-executable instructions (such as program code); a software module; or a functional process.

[0020] As used herein, the term "interface circuit" refers to, is a part of, or includes a circuit that enables information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces; for example, a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0021] As used herein, the term "user equipment" or "UE" refers to a device of a remote user having radio communication capabilities and which may describe network resources in a communication network. The terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0022] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0023] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, an electrical power, an input / output operation, a port or a network socket, a channel / link allocation, a throughput, a memory usage, a storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computer, storage or network resources provided by physical hardware elements. "Virtualized resources" may refer to computer, storage or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0024] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is transmitted. In addition, as used herein, the term "link" refers to a connection made between two devices for transmitting and receiving information.

[0025] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0026] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0027] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0028] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to a single content of an information element or a data element that contains content. An information element may include one or more additional information elements.

[0029] Figure 1 A network environment 100 according to some embodiments is illustrated. The network environment 100 may include a UE 104 coupled to a base station (BS) 108 of a radio access network (RAN). In some embodiments, the BS 108 is a next generation node B (gNB) providing one or more 3GPP new radio (NR) cells. In other embodiments, the BS 108 is an evolved node B (eNB) providing one or more long term evolution (LTE) cells. The air interface through which the UE 104 and the BS 108 communicate may be compatible with 3GPP technical specifications (TS), such as those defining fifth generation (5G) NR or later system standards (e.g., sixth generation (6G) standards).

[0030] The network environment 100 may include a network 105. The network 105 may provide services, such as voice or data connectivity, to the UE 104. The network 105 may include a core network (CN) 106 or a BS 108. The CN 106 may connect the BS 108 and the UE 104 to other entities, such as an edge data network (EDN), the Internet, or an application function (AF) 102. The CN 106 may be responsible for call and session configuration or control, mobility management, or service provisioning.

[0031] CN 106 may include one or more network functions, such as network exposure function (NEF) 116 or network function NF 112. NF 112 is a generic network function and may represent any network function provided by CN 106. NF 112 may manage or control the operation of a network node. For example, NF 112 may be a RAN management function that controls the operation and configuration of BS 108 or UE 104.

[0032] AF 102 may be a functional element that may provide information related to services or applications to other network functions. In some instances, AF 102 is a function managed by a network operator. In some instances, AF 102 may be a third-party function residing in the cloud or a third-party server.

[0033] AF 102 may be coupled to network 105 via CN 106. AF 102 may be coupled to NEF 116. In some embodiments, AF 102 may be coupled to NF 112. In some instances, AF 102 may communicate with NF 112 via NEF 116, e.g., AF 102 may send a message to NEF 116, and NEF 116 may forward the message to NF 112. In some instances, AF 102 may communicate directly with NF 112, e.g., AF 102 may send a message directly to NF 112.

[0034] UE 104 may be communicatively coupled to BS 108 via a communication link 170. UE 104 may collect data related to the communication link 170 or other information related to UE 104. The collected data may be associated with the end user's intent, context, or expected action. For example, in a vehicle-to-everything (V2X) system, a UE (e.g., a vehicle) may have information related to a user's lane-crossing intent, distraction level, or destination. UE 104 may also receive information from network 105, other UEs, or other data networks. UE 104 may use the data to predict configurations, such as a business profile or operating mode. UE 104 may use an AIML model to analyze information and obtain predictions or results.

[0035] UE 104 may process the data and generate AIML data 110. UE 104 may share AIML data 110 with AF 102. UE 104 may share processed results 120 with AF 102. Processed results 120 may include predictions, inferences, or AIML models developed by UE 104 or an application or function associated with UE 104.

[0036] AF 102 may interact with network 105 to obtain authorization to access entities and elements associated with network 105. AF 102 may affect the operation of network 105 through its interaction with NEF 116 or NF 112. For example, AF 102 may affect the traffic routing of an application and interact with a policy control function (PCF) to enable policy control. NEF 116 may provide AF 102 with components for accessing network capabilities and resources. By opening capabilities (e.g., network functions or resources), NEF 116 or AF 102 may affect how the opened NFs or resources operate or interact with each other. AF 102 may affect data session configuration, traffic routing, or quality of service (QoS) parameters. Network 105 may send configuration 160 to UE 104 based on AF 102 influence.

[0037] In some embodiments, AF 102 may affect mobility, session management policies, and configurations associated with BS 108 or UE 104.

[0038] In some embodiments, AF 102 may act on behalf of UE 104 to affect the operation of network 105 based on information or inferences of the UE.

[0039] The network 105 may authorize the AF 102 to access the NEF 116 or NF 112. The network 105 may send an information open 150 to the AF 102. The information open 150 may include data applicable or associated with the AIML model or analysis. The information open 150 may include a list of NFs or resources that the AF 102 is authorized to access or influence.

[0040] AF 102 may provide AF impact data 140 to network 105. AF impact data 140 may include raw data (eg, measurement data), analyzed data (eg, AIML data or processed results), or AIML models or parameters.

[0041] Due to privacy issues, it may be desirable for the UE 104 or AF 102 to keep the raw measurements or data in the device. The AIML running locally can generate results and inferences based on this data. Direct access to the NF 112 can enable the UE 104 or AF 102 to perform real-time or near real-time procedures or support applications that may require fast control loops.

[0042] Figure 2 An operational flow / algorithm 200 structure is illustrated according to some embodiments. The operational flow / algorithm structure 200 is an example of the operation of the AF 102 affecting the network 105. The operational flow / algorithm structure 200 may be implemented by a network node (e.g., the network node 1000) or a component thereof (e.g., the processor 1004).

[0043] The operation flow / algorithm structure 200 may include: performing AF authorization at 210. The AF may be Figure 1 AF authorization may be performed by a mobile network operator (MNO) or by a UE (e.g., Figure 1 UE 104 in the system executes.

[0044] AF can be a core network (for example, Figure 1 The AF is a component of a third-party service that interacts with the CN 106 in the AF to affect the operation of the network. The AF's authorization procedures ensure that the AF has the necessary permissions to interact with the network.

[0045] The operational flow / algorithm structure 200 may include determining aspects that may be affected by the AF at 220. For example, the AF may request access to the NF. The network may perform authorization, including user consent management operations, to determine whether the AF is granted access and determine the scope of access.

[0046] User consent management may involve obtaining explicit permission from the user before the AF can access or use certain information or services on behalf of the UE. Consent management may be necessary in handling sensitive information or operations that may affect user experience or privacy. For example, the AF may request access to a user's network slice. The network may need to ensure that the AF is authorized to access only specific network slices and prevent it from accessing information of other network slices. This authorization process may involve obtaining consent from the user.

[0047] The operational flow / algorithm structure 200 may include discovering available services or functions at 230. For example, the AF may discover available services through the NEF. The available services may be associated with services that the AF has the authority to access or influence.

[0048] Service discovery may involve the AF querying the network to determine available services. This may include communication with various NFs such as the Network Repository Function (NRF) or NEF.

[0049] The operational flow / algorithm structure 200 may include, at 240, discovering and connecting to a NF associated with the RAN (eg, a RAN management function or RAN NF) for real-time, non-real-time, or near real-time impact.

[0050] The AF may send impact data, such as raw data, AIML models, or UE-initiated data or models, to the NF. The NF may consider AF input (e.g., impact data) or data from other NFs (e.g., Network Data Analysis Function (NWDAF)).

[0051] The AF may influence network operation through parameter provisioning procedures. The AF may provide parameters to the network by, for example, parameter provisioning to NEF or other NFs. The receiving NF may use the received parameters to determine configuration parameters or network operation. For example, the AF may provide certain physical layer (PHY) configurations to the RAN NF. The RAN NF may use the PHY configurations to configure the UE, for example, via radio resource control (RRC) configuration signaling.

[0052] AIML provisioning may include obtaining UE (or end-user) consent. The consent may be a blanket consent provided to a specific AF, or it may be a granular consent provided per action or aspect affected. The consent may apply to a specific time period or geographic location. UE consent may be updated via network or application layer signaling (e.g., over-the-top (OTT) signaling).

[0053] AIML-based provisioning can provide granular control of UE configuration. For example, a UE can influence RAN parameters by accessing the RAN through the AF or the AF on behalf of the UE. Direct access to the RAN can enable fast control loops for near real-time operation. The AF can access the RAN node directly or through a local NEF (e.g., local to the RAN node). For example, the AF can access an AIML RAN NF, such as a RAN AI / ML model or data repository function or a RAN AIML model or data coordination function. Parameter provisioning can mask aspects related to user intent, sensitive or private information (e.g., identifiers), or system information (e.g., applications or device settings that are considered private).

[0054] The receiving NF may associate or combine the parameter provisioning input from the AF with the NWDAF. For example, the MNO may combine the AF input with the analysis from the NWDAF. The network may provide the relevant NWDAF analysis to the AF. The AF may combine or associate the NWDAF analysis and incorporate them into the parameter provisioning, or the AF may provide the NWDAF analysis to the UE and the UE may take the NWDAF analysis into account in the triggering parameter provisioning.

[0055] The AF may use parameter provisioning to influence CN parameters. For example, the AF may influence UE operation mode, long-term UE behavior (e.g., UE subscription for a slice), or short-term behavior (e.g., session lifetime or QoS flow lifetime). The AF may influence CN mobility management policies, such as the recommended registration area, the periodicity of the Mobility Registration Update (MRU) message, or parameters associated with radio link failure. The AF may influence the CN to dynamically change semantic communication flow characteristics.

[0056] The AF may use parameter provisioning to influence RAN configuration. For example, the AF may influence duty cycle, preferred carrier aggregation configuration, measurement configuration for power saving, radio resource allocation, beamforming selection, RRM, RAN mobility configuration including beam groups, or transmission and reception point (TRP) selection. The AF may influence the AIML mode at the NF.

[0057] AF may affect the network in device-to-device (D2D) communications. For example, AF may affect parameters associated with D2D authorization, sidelink UE selection, route selection, or sidelink RRM.

[0058] The AF may affect Open RAN (ORAN) functions across rApp, xApp, SMO, A1, E2, or O1. For example, the AF may affect multi-gNB coordination based on ORAN Xn. The rApp, xApp, SMO, A1, E2, O1, or Xn interface is an ORAN service or interface according to the ORAN specification.

[0059] The AF can influence the network policy through parameter provisioning. For example, the AF can recommend AIML policy selection or influence NFs associated with UE known performance indicators (KPIs), failures or error rates.

[0060] Figure 3 A signaling diagram 300 according to some embodiments is illustrated. The signaling diagram 300 may be an example of a provisioning procedure for setting a UE operating profile. The UE operating profile may include a set of UE configurations, such as radio access capabilities, network capabilities, or mobility preferences. For example, the UE or AF may influence network decisions related to mobility update timers, allowed network slices, or radio configurations. The UE may register one or more operating profiles with the network. Based on AIML inference, an AIML function at the UE or AF may determine and select an operating profile. For example, the AIML inference may be based on knowledge or information about AIML capabilities or available data sets. The UE or AF may call a NEF API to supply a configuration corresponding to the UE operating profile.

[0061] At 320, UE 104 may send a registration request to AF 102. For example, an AIML client in the UE may register with the AF to trigger authorization or login to MNO NEF 116. The UE may send the UE registration request using application layer signaling. The registration request or another message may include a list of provisioning parameters and consent inputs (e.g., one or more indications of one or more consents).

[0062] At 325, AF 102 may check whether authorization exists. If no authorization is associated with NEF 116, AF 102 may send an authorization request message to NEF 116. For example, AF 102 may request authorization from NEF 116 using an Nnef_AFAuthorization_Request message. The authorization request message may include a UE identifier (ID), a list of allowed UE provisioning parameters for which AF 102 has received user consent.

[0063] At 330, NEF 116 may perform authorization in response to the authorization request message from AF 102. NEF 116 may authorize AF 102 using the consent input and information associated with the consent retrieved from unified data management (UDM) 314. UDM may be a network node or NF that manages data for network users. For example, NEF 116 may retrieve UE consent information stored in UDM.

[0064] At 335, NEF 116 may send an authorization confirmation message to AF 102. For example, NEF 116 may use Nnef_AFAuthorization_Confirm message to inform AF 102 whether AF 102 is authorized to access NEF 116 or other NF. The authorization confirmation message may include an indication that AF 102 is authorized to access NEF 116 or other NF, such as authorization information. The authorization confirmation message may include an authorization ID. When accessing NEF 116 or other NF, AF 102 may use the authorization ID to indicate that it has authorization. The authorization confirmation may include a validity time that may indicate the duration for which the authorization is valid. AF 102 may configure a timer based on the validity time.

[0065] At 340, based on the AIML inference, the AIML client in the UE 104 may trigger the AF 102 to provide parameters. The UE 104 may send a trigger to the AF 102 using application layer signaling. The trigger may include an indication of the operating mode of the UE. The trigger may be based on an inference or a partial inference result. The inference or trigger may be combined with other inference results at the AF. Other inferences at the AF may be provided by a core network NF (e.g., NWDAF, RAN-related NF, or other CN NF).

[0066] At 345, AF 102 invokes a parameter provisioning service at the NF. AF 102 may invoke the parameter provisioning service at NEF 116 by sending a provisioning request message to NEF 116. For example, AF 102 may send a Nnef_ParameterProvision_Request message to NEF 116. The provisioning request message may include an indication associated with the AF 102 authorization ID, the UE ID, and provisioning parameters, such as an indication of a preferred operating profile for the UE. The time may be associated with a validity duration or a scheduled time. For example, the time indication may determine when the requested operating profile may be applied.

[0067] At 350, the NEF 116 may determine whether the AF 102 has authorization to invoke the requested service. The NEF 116 may retrieve the AF 102 authorization information from the UDM 314. For example, the NEF 116 may retrieve the provisioned operational profile from the UDM 314.

[0068] At 355, the NEF 116 may send a parameter provisioning confirmation message to the AF 102. For example, the NEF 116 may send the AF 102 an Nnef-ParameterProvision_Confirm message.

[0069] At 360, NEF 116 may invoke access and mobility management function (AMF) services for parameter provisioning. NEF 116 may invoke AMF services for provisioning by sending a provisioning request message to AMF 312. AMF 312 may be a function of the CN. For example, NEF 116 may send a Namf_UEParameterProvision_Request message to AMF 312. NEF 116 may send a provisioning request message to the AMF with which UE 104 is registered. The provisioning request message may include a UE ID, an indication of a preferred operating profile of the UE, and a validity time.

[0070] At 365, the AMF 312 may invoke the RAN Management Function (RMF) 318 service to update the UE context to supply the updated UE context parameters. Figure 1 AF 312 may send an update request message to RMF 318 to update the UE context with the provided UE context parameters. The UE context parameters may include an indication of a preferred operating profile of the UE. For example, AMF 312 may send Nran_UEContext_UpdateReq to BS108.

[0071] At 370, RMF 318 may update UE 104 configuration according to the updated UE context parameters. For example, RMF 318 may update UE 104 by instructing BS (e.g., Figure 1 The BS 108 in the UE sends a radio resource control (RRC) reconfiguration message to update the RRC configuration of the UE according to the operating profile indicated by the updated UE context.

[0072] Figure 4 A network environment 400 is illustrated according to some embodiments. The network is an example of NFs of the CN 106 available on a service bus 480. The service bus 480 may be used to facilitate communications between the connected NFs and the AF 102.

[0073] In some examples, a session management function (SMF) 410 may be connected to the service bus 480. The SMF 410 may be responsible for session establishment, modification, or release.

[0074] In some examples, registration function 420 can be connected to service bus 480. Registration function 420 can be responsible for managing registration of a UE or AF (eg, AF 102).

[0075] In some examples, an authentication function (AUSF) 430 may be connected to the service bus 480. AUSF 430 may support authentication of a network (e.g., Figure 1Authentication for access to the network 105).

[0076] In some examples, a policy management function (PCF) 440 may be connected to the service bus 480. The PCF 440 may control parameters that regulate user data traffic.

[0077] In some examples, RMF 318 can be connected to service bus 480. RAN management functions can control and configure the RAN (including Figure 1 The operation of BS108 and UE 104).

[0078] In some examples, an analysis function 460 (eg, NWDAF) may be connected to a service bus 480. The analysis function 460 may provide analysis to the core network NFs and operations and maintenance (O&M).

[0079] In some examples, a user plane function (UPF) 470 may be connected to the service bus 480. The UPF 470 may be responsible for handling user plane data traffic.

[0080] The AF 102 may directly invoke NFs connected to the service bus 480. For example, the AF 102 may directly invoke RAN services to update the UE selected configuration by sending a parameter provisioning request directly to the RMF 318. Direct access to NFs on the service bus 480 reduces latency and overhead for AF 102 requests compared to requests processed through the NEF.

[0081] The NEF may provide authorization and user consent checks required before allowing the AF 102 to invoke NF services directly on the service bus 480. Once authorized, the AF 102 may be allowed to interact directly with the NF (e.g., RMF 318). Authentication timers may regulate direct access. For example, the AF 102 may be allowed to interact directly with the NF on the service bus 480 within a predetermined timer. Other events such as UE mobility, cell reselection, or other network conditions may affect the AF 102's direct access to the NF.

[0082] Figure 5 A signaling diagram 500 is illustrated according to some embodiments. The signaling diagram 500 is an example of a provisioning procedure for setting a UE selected RAN configuration through a direct interface to the RMF 318.

[0083] The UE 104 may select a RAN configuration. The RAN configuration may include a PHY or RRC configuration. The UE 104 may select a RAN configuration based on AIML operation (eg, based on AIML requirements and capabilities and UE's knowledge of current and future requirements).

[0084] UE 104 may provide the AIML processing results or the selected preferred RAN configuration to AIML AF 102. UE may provide authorized metadata or enriched information to RMF 318 to enable RMF 318 to perform RAN configuration selection.

[0085] The AF 102 may call the NEF API to discover the RAN node to which the UE is connected or registered. The NEF may also authorize the AF 102 and check the user's consent for the impact on the UE behavior.

[0086] The authorized AF 102 may initiate establishment of an AIML session with the RMF 318. The AF 102 may send metadata or an indication of the selected RAN configuration directly to the RMF 318.

[0087] At 520, UE 104 may send a registration request to AF 102. For example, an AIML client in the UE may register with the AF to trigger authorization or login to MNO NEF 116. The UE may send the UE registration request using application layer signaling. The registration request or another message may include a list of provisioning parameters and a consent input.

[0088] At 525, the AF 102 may check whether authorization exists. If no authorization is associated with the NEF 116, the AF 102 may send an authorization request message to the NEF 116. For example, the AF 102 may request authorization from the NEF 116 using an Nnef_AFAuthorization_Request message. The authorization request message may include a UE identifier (ID), an indication of the type of updated AIML session with the RMF 318, a list of allowed UE provisioning parameters for which the AF 102 has received user consent, user consent input, and a request for a RAN controller identifier. The RAN controller identifier may be an address for directly invoking a service-based interface from a RAN node. Generally speaking, when a direct connection is directed to a NF, the controller identifier may be an address of a NF associated with the UE, such as an IP address or a URI.

[0089] At 530, the NEF 116 may perform authorization in response to the authorization request message from the AF 102. The NEF 116 may use the consent input and information associated with the consent retrieved from the unified data management (UDM) 314 to authorize the AF 102. The UDM may be a network node or NF that manages data for network users. For example, the NEF 116 may retrieve UE consent information stored in the UDM.

[0090] At 535, the NEF 116 may send a request to the AMF 312 with which the UE 104 is currently registered to retrieve the relevant RMF identifier that should receive the RAN configuration. The RMF identifier may be an Internet Protocol (IP) address or a Uniform Resource Identifier (URI) associated with the RMF or RAN node. Generally speaking, when the direct connection is directed to the NF, the controller identifier may be the address of the NF associated with the UE, such as an IP address or a URI.

[0091] At 540, the NEF 116 may send an authorization confirmation message to the AF 102. For example, the NEF 116 may use the Nnef_AFAuthorization_Confirm message to inform the AF 102 whether the AF 102 is authorized to access the NEF 116 or other NF (e.g., RMF 318). The authorization confirmation message may include an indication that the AF 102 is authorized to access the NEF 116 or other NF. The authorization confirmation message may include an authorization ID. When accessing the NEF 116 or other NF (e.g., RMF 318), the AF 102 may use the authorization ID to indicate that it has authorization. The authorization confirmation may include a validity time that may indicate the duration for which the authorization is valid. The AF 102 may configure a timer based on the validity time. The authorization confirmation may include an RMF address. The RMF address may indicate the RMF that should receive the RAN configuration. The RMF address may be an IP address or URI of the RMF or a corresponding RAN node.

[0092] At 545, based on the AIML inference, the AIML client in the UE 104 may trigger the AF 102 to initiate or modify an AIML session. The UE 104 may send the trigger using application layer signaling to the AF 102. The trigger may include an indication of the AF 102 authorization ID, the UE ID, or the UE's selected RAN configuration.

[0093] At 550, the AF 102 may invoke RAN services for UE configuration provisioning at the RMF 318. The AF 102 may invoke parameter provisioning services at the RMF 318 by sending an AIML session request to the RMF 318. For example, the AF 102 may send an Nran_AIMLSession_Create / NModify_Request message to the RMF 318. The session request message may include an indication associated with the AF 102 authorization ID, the UE ID, and an indication of the UE configuration provisioning (e.g., an indication of the selected RAN configuration of the UE).

[0094] At 555, RMF 318 may receive the UE selected RAN configuration and verify the request. For example, RMF 318 may verify the UE selected RAN configuration using the AF Authorization ID received in the Session Request message. RMF 318 may retrieve information about the UE's registered RAN configuration from UDM 314.

[0095] At 560, based on the successful authentication at 555, the RMF 318 may send a confirmation message to the AF 102. For example, the RMF 318 may send a Nran_AIMLSession_Create_Confirm message to the AF 102. The confirmation message may include a session ID.

[0096] At 565, RMF 318 may update UE 104 configuration according to the received selected RAN configuration. For example, RMF 318 may update UE 104 by instructing BS (e.g., Figure 1 The BS 108 in the UE sends a radio resource control (RRC) reconfiguration message to update the RRC configuration of the UE according to the selected RAN configuration indicated by the session request message.

[0097] Figure 6 An operation flow / algorithm structure 600 according to some embodiments is illustrated. The operation flow / algorithm structure 600 is an example of a NEF authorizing an AF to access a NF. The operation flow / algorithm structure 600 may be implemented by a network node (e.g., CN 106 or network node 1000) or a component thereof (e.g., processor 1004).

[0098] The operation flow / algorithm structure 600 may include receiving an authorization request from the AF at 610. The authorization request may be associated with access to the NF. The access to the NF may be indirect access through the NEF or direct access.

[0099] The request may be a request to access the NF on the service bus. For example, the request may be a request to access the RMF.

[0100] The operational flow / algorithm structure 600 may include determining whether the AF is authorized to access the NF at 620. The NEF may request and receive a message including an indication of consent associated with the UE from the UDM. The NEF may request and receive a message including an indication of an identifier of a network function associated with the UE from the AMF. The NEF may determine whether the AF is authorized to access the NF based on the indication of consent received from the UDM or the indication of the network identifier received from the AMF.

[0101] The operational flow / algorithm structure 600 may include transmitting a confirmation message to the AF indicating that the AF is authorized to access the NF at 630. The confirmation message may include a validity timer that may indicate how long the AF authorization is valid.

[0102] The NEF may also perform a parameter provisioning procedure. The NEF may receive a provisioning request from the AF. The NEF may determine that the AF is authorized to invoke the parameter provisioning service at the NEF. If the AF is successfully authorized, the NEF may send a confirmation message to the AF.

[0103] NEF and AF can establish an AIML session. The AIML session can provide the AF with access to partial inference results from the NF. In some instances, the NWDA NF can provide partial results to the AF. The AIML session can provide provisioning of configuration parameters to the AF. In direct access, the AF can establish an AIML session with the NF.

[0104] Figure 7 An operational flow / algorithm structure 700 according to some embodiments is illustrated. The operational flow / algorithm structure 700 is an example of an RMF for establishing direct access to an AF. The operational flow / algorithm structure 700 may be implemented by a network node (e.g., CN 106, BS 108, or network node 1000) or a component thereof (e.g., processor 1004).

[0105] The operation flow / algorithm structure 700 may include receiving a session request from the AF at 710, wherein the request is associated with the UE. The session request may include the UE ID and the authorization ID associated with the AF. The session request may include a configuration associated with the UE.

[0106] The operational flow / algorithm structure 700 may include sending a confirmation response to the AF at 720. The confirmation response may include a session ID.

[0107] The operation flow / algorithm structure 700 may include configuring the UE based on the session request at 730. For example, the RMF may instruct the BS to send an RRC reconfiguration message to the UE based on the UE configuration in the session request message.

[0108] Figure 8 An operation flow / algorithm structure 800 according to some embodiments is illustrated. The operation flow / algorithm structure 800 is an example of a UE establishing direct access to an RMF. The operation flow / algorithm structure 800 may be implemented by a UE (e.g., UE 104 or UE 900) or a component thereof (e.g., processing circuit 904).

[0109] The operational flow / algorithm structure 800 may include sending a registration request to the AF at 810. The registration request may include one or more indications associated with UE consent.

[0110] The operational flow / algorithm structure 800 may include sending a trigger to start an AIML session at 820. The trigger may include an indication of a configuration selected by the UE. The configuration selected by the UE may include a mobility management policy, a duty cycle, a carrier aggregation configuration, a measurement configuration, a radio resource management (RRM) configuration, a RAN mobility configuration, an AIML model selection indication, a resource allocation indication, or a beamforming selection indication.

[0111] The operational flow / algorithm structure 800 may include receiving a reconfiguration message from the RAN at 830. The reconfiguration message may be based on the configuration selected by the UE. In one example, the reconfiguration message may be an RRC reconfiguration message.

[0112] Fig. 9 UE 900 according to some embodiments is illustrated. UE 900 may be similar to Figure 1 UE 104 and is substantially interchangeable therewith.

[0113] UE 900 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an XR device, glasses, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a camcorder), a wearable device (e.g., a smart watch), or an IoT device.

[0114] UE 900 may include a processor 904, RF interface circuitry 908, memory / storage 912, a user interface 916, a sensor 920, a driver circuit 922, a power management integrated circuit (PMIC) 924, antenna structures 926, and a battery 928. The components of UE 900 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig. 9 The block diagram of UE 900 is intended to show a high-level view of certain of the components of UE 900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0115] Components of the UE 900 may be coupled to various other components via one or more interconnects 932, which may represent any type of interface circuit (e.g., a processor interface or a memory interface), input / output, bus (local, system, or extension), transmission line, trace, or optical connection that allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0116] The processor 904 may include processor circuits such as, for example, a baseband processor circuit (BB) 904A, a central processor unit circuit (CPU) 904B, and a graphics processor unit circuit (GPU) 904C. The processor 904 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 912) to cause the UE 900 to perform operations as described herein.

[0117] In some embodiments, the baseband processor circuit 904A can access the communication protocol stack 936 in the memory / storage device 912 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 904A can access the communication protocol stack 936 to: perform user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer and upper layers; and perform control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer and NAS layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 908.

[0118] The baseband processor circuit 904A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0119] The memory / storage 912 may include one or more non-transitory computer-readable media including instructions (e.g., a communication protocol stack 936) that may be executed by one or more processors in the processor 904 to cause the UE 900 to perform various operations described herein. The memory / storage 912 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 900. In some embodiments, some of the memory / storage 912 may be located on the processor 904 itself (e.g., L1 cache and L2 cache), while other memory / storage 912 is located outside the processor 904, but the processor may be accessed via a memory interface. The memory / storage 912 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0120] The RF interface circuit 908 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 900 to communicate with other devices through a radio access network. The RF interface circuit 908 may include various elements arranged in a transmission path or a reception path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, and control circuits.

[0121] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 926 and continue to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 904.

[0122] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 926.

[0123] In various embodiments, the RF interface circuit 908 may be configured to transmit / receive signals in a manner compatible with NR access technology.

[0124] Antenna 926 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 926 may have an antenna panel that is omnidirectional, directional, or a combination thereof to achieve beamforming and multiple input, multiple output communications. Antenna 926 may include a microstrip antenna, a printed antenna manufactured on the surface of one or more printed circuit boards, a patch antenna, or a phased array antenna. Antenna 926 may have one or more panels designed for a specific frequency band (including a frequency band in FR1 or FR2).

[0125] The user interface circuit 916 includes various input / output (I / O) devices designed to enable a user to interact with the UE 900. The user interface 916 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual components for accepting input, and in particular includes one or more physical or virtual buttons (e.g., reset button), physical keyboard, keypad, mouse, touch pad, touch screen, microphone, scanner, headset, etc. The output device circuit includes any physical or virtual components for showing information or otherwise conveying information (such as sensor readings, actuator positioning, or other similar information). The output device circuit may include any number or combination of audio or visual displays, in particular including one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes (LEDs) and multi-character visual outputs or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 900.

[0126] Sensors 920 may include devices, modules, or subsystems that are designed to detect events or changes in their environment and send information about the detected events (sensor data) to some other device, module, or subsystem. Examples of such sensors include: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; and a microphone or other similar audio capture device.

[0127] The driving circuit 922 may include software elements and hardware elements for controlling a specific device embedded in the UE 900, attached to the UE 900, or otherwise communicatively coupled to the UE 900. The driving circuit 922 may include a separate driver, thereby allowing other components to interact with or control various I / O devices that may be present in the UE 900 or connected to the UE. For example, the driving circuit 922 may include a circuit for facilitating coupling a universal integrated circuit card (UICC) or a universal subscriber identity module (USIM) to the UE 900. For another example, the driving circuit 922 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor circuit 920 and controlling and allowing access to the sensor circuit 920, a driver for obtaining actuator positioning of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0128] The PMIC 924 may manage power provided to various components of the UE 900. Specifically, with respect to the processor 904, the PMIC 924 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0129] In some embodiments, the PMIC 924 may control or otherwise be a part of various power saving mechanisms of the UE 900, including DRX, as discussed herein.

[0130] The battery 928 can power the UE 900, but in some examples, the UE 900 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. The battery 928 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 928 can be a typical lead-acid car battery.

[0131] Fig.10 A network node 1000 according to some embodiments is illustrated. The network node 1000 may be similar to, and substantially interchangeable with, a base station 108, a device implementing one of the network hops, an integrated access and backhaul (IAB) node, a network controlled repeater, or a server in a core network or an external data network.

[0132] The network node 1000 may include a processor 1004 , RF interface circuitry 1008 (if implemented as an access node), core node (CN) interface circuitry 1012 , memory / storage circuitry 1016 , and antenna structures 1026 .

[0133] Components of network node 1000 may be coupled to various other components via one or more interconnects 1028 .

[0134] The processor 1004, RF interface circuit 1008, memory / storage circuit 1016 (including communication protocol stack 1010), antenna structure 1026 and interconnect 1028 may be similar to those described in detail in the accompanying drawings. Fig. 9 Like named elements are shown and described.

[0135] The CN interface circuit 1012 may provide connectivity for a core network (e.g., a 5th Generation Core Network (5GC) compatible network interface protocol (such as a Carrier Ethernet protocol) or some other suitable protocol). Network connectivity may be provided to / from the network node 1000 via optical fiber or wireless backhaul. The CN interface circuit 1012 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1012 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0136] In some embodiments, the network node 1000 may be coupled to a transmission reception point (TRP) using an antenna structure 1026, a CN interface circuit, or other interface circuits.

[0137] It is well known that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and handled to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0138] For one or more aspects, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following embodiments. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below in the embodiments section.

[0139] Example

[0140] In the following sections, additional exemplary aspects are provided.

[0141] Embodiment 1 includes a method for being implemented by a network exposure function (NEF) of a cellular network, comprising: receiving an authorization request for a network function (NF) to access the cellular network from an application function (AF); determining by the NEF that the AF is authorized to access the NF of the cellular network; and transmitting to the AF a confirmation message including an indication that the AF is authorized to access the NF of the cellular network.

[0142] Embodiment 2 includes a method according to embodiment 1 or other embodiments herein, wherein the network function is a radio access network (RAN) management function.

[0143] Embodiment 3 includes a method according to embodiment 1 or 2 or other embodiments herein, wherein the confirmation message includes an authorization identifier and a validity timer.

[0144] Embodiment 4 includes a method according to any one of embodiments 1 to 3 or other embodiments herein, wherein the authorization request for the NF to access the cellular network includes a UE identity and a UE consent input.

[0145] Embodiment 5 includes a method according to any one of embodiments 1 to 4 or other embodiments herein, wherein the access is direct access.

[0146] Embodiment 6 includes a method according to any one of embodiments 1 to 5 or other embodiments herein, wherein the authorization request for the NF to directly access the cellular network includes a controller identifier.

[0147] Embodiment 7 includes a method according to any one of embodiments 1 to 6 or other embodiments herein, wherein the confirmation message includes a NF address.

[0148] Embodiment 8 includes a method according to any one of embodiments 1 to 7 or other embodiments herein, wherein the NF address is an Internet Protocol (IP) address or a uniform resource identifier (URI) associated with the NF of the cellular network.

[0149] Embodiment 9 includes a method according to any one of embodiments 1 to 8 or other embodiments herein, wherein the determining that the AF is authorized to access the network function of the cellular network includes: receiving a first message including an indication of consent associated with a user equipment (UE) from a unified data management (UDM); receiving a second message including an indication of an identifier of the network function associated with the UE from an access and mobility management function (AMF); and determining the indication based on the indication of the consent associated with the UE or the indication of the identifier of the network function associated with the UE.

[0150] Embodiment 10 includes the method according to any one of embodiments 1 to 9 or other embodiments described herein, further comprising: receiving a NEF provisioning request from the AF to invoke a parameter provisioning service of the NEF; determining that the AF is authorized to invoke the parameter provisioning service; and sending a provisioning confirmation message to the AF.

[0151] Embodiment 11 includes a method according to any one of embodiments 1 to 10 or other embodiments herein, wherein the NEF provisioning request includes an authorization identifier associated with the AF, a UE identifier, a UE operating profile, and a validity time.

[0152] Embodiment 12 includes a method according to any one of embodiments 1 to 11 or other embodiments herein, further comprising: sending an AMF provisioning request to an access and mobility management function (AMF) for invoking a parameter provisioning service of the AMF.

[0153] Embodiment 13 includes a method according to any one of embodiments 1 to 12 or other embodiments herein, wherein the NF is a first NF, and the method further includes: sending a partial inference result associated with a second NF to the AF.

[0154] Embodiment 14 includes a method according to any one of embodiments 1 to 13 or other embodiments herein, wherein the second NF is a network data analysis (NWDA) NF.

[0155] Embodiment 15 includes a method for implementation by a radio access network (RAN) management function of a cellular network, comprising: receiving a session request associated with a user equipment (UE) from an application function (AF); sending a confirmation response associated with the session request to the AF; and configuring the UE based on the session request.

[0156] Embodiment 16 includes a method according to embodiment 15 or other embodiments herein, wherein the session request includes a UE identifier, a UE selected configuration, and an authorization identifier associated with the AF.

[0157] Embodiment 17 includes a method according to embodiment 15 or 16 or other embodiments herein, wherein configuring the UE based on the session request includes: sending a radio resource control (RRC) reconfiguration message to the UE.

[0158] Embodiment 18 includes a method for implementation by a user equipment (UE), comprising: sending a registration request to an application function (AF); sending a trigger to the AF to initiate or modify an AIML session based on AIML inference; and receiving a reconfiguration message from a radio access network (RAN) based on the trigger.

[0159] Embodiment 19 includes a method according to embodiment 18 or other embodiments herein, wherein the reconfiguration message is a radio resource control (RRC) reconfiguration message.

[0160] Embodiment 20 includes a method according to embodiment 18 or 19 or other embodiments herein, wherein the registration request includes a UE consent indication.

[0161] Embodiment 21 includes a method according to any one of embodiments 18 to 20 or other embodiments herein, further comprising: sending a RAN configuration selected by the UE to the AF.

[0162] Embodiment 22 includes a method according to any one of embodiments 18 to 21 or other embodiments herein, wherein the trigger includes an indication of a RAN configuration selected by the UE.

[0163] Embodiment 23 includes a method according to any one of embodiments 18 to 22 or other embodiments herein, wherein the UE-selected RAN configuration includes a physical layer (PHY) configuration or a radio resource control (RRC) configuration.

[0164] Embodiment 24 includes a method according to any one of embodiments 18 to 23 or other embodiments herein, wherein the RAN configuration selected by the UE includes a mobility management policy, a duty cycle, a carrier aggregation configuration, a measurement configuration, a radio resource management (RRM) configuration, a RAN mobility configuration, an AIML model selection indication, a resource allocation indication, or a beamforming selection indication.

[0165] Another embodiment may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in accordance with or related to any of Embodiments 1 to 24, or any other method or process described herein.

[0166] Another embodiment may include a method, technique or process described or related to any one of embodiments 1 to 24 or a portion or component thereof.

[0167] Another embodiment may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform methods, techniques, or processes described in or related to any one of embodiments 1 to 24 or portions thereof.

[0168] Another embodiment comprises a signal as described or relating to any one of embodiments 1 to 24, or parts or components thereof.

[0169] Another embodiment may include a datagram, information element, packet, frame, segment, PDU or message as described or related to any one of embodiments 1 to 24 or parts or components thereof or otherwise described in the present disclosure.

[0170] Another embodiment may include a signal encoded with data as described or associated with any one of embodiments 1 to 24, or parts or components thereof, or otherwise described in this disclosure.

[0171] Another embodiment may include a signal encoded with a datagram, IE, packet, frame, segment, PDU or message as described or related to any one of embodiments 1 to 24 or parts or components thereof or otherwise described in the present disclosure.

[0172] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process described in or related to any one or part of embodiments 1 to 24.

[0173] Another embodiment may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described or related to any one or part of embodiments 1 to 24.

[0174] Another embodiment may include a signal in a wireless network as shown and described herein.

[0175]

[0013] Another embodiment may include a method of communicating in a wireless network as shown and described herein.

[0176]

[0013] Another embodiment may include a system for providing wireless communications as shown and described herein.

[0177]

[0013] Another embodiment may include an apparatus for providing wireless communications as shown and described herein.

[0178] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the various aspects to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various aspects.

[0179] Although the above aspects have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

1. A method comprising: Processing an authorization request received from an application function (AF) for a network function (NF) to access a cellular network; Determining that the AF is authorized to access the NF of the cellular network; as well as A confirmation message is generated for sending to the AF, wherein the confirmation message includes authorization information of the NF indicating that the AF is authorized to access the cellular network.

2. The method of claim 1, wherein the NF is a Radio Access Network (RAN) management function. The method of claim 1 , wherein the confirmation message includes an authorization identifier and a validity timer.

4. The method of claim 1, wherein the authorization request for the NF to access the cellular network includes a user equipment (UE) identity and a UE consent input.

5. The method according to claim 1, wherein: The access is direct access; The authorization request for the NF to directly access the cellular network includes a controller identifier; and The confirmation message includes the NF address.

6. The method of claim 5, wherein the NF address is an Internet Protocol (IP) address or a Uniform Resource Identifier (URI) associated with the NF of the cellular network.

7. The method of claim 5, wherein the determining that the AF is authorized to access the network function of the cellular network comprises: processing a first message received from a unified data management (UDM) including an indication of consent associated with a user equipment (UE); processing a second message received from an access and mobility management function (AMF) including an indication of an identifier of the network function associated with the UE; as well as The authorization information is determined based on the indication of the consent associated with the UE or the indication of the identifier of the network function associated with the UE.

8. The method according to any one of claims 1 to 7, further comprising: processing a NEF provisioning request received from the AF to invoke a parameter provisioning service; Determining that the AF is authorized to invoke the parameter provisioning service; as well as A provisioning confirmation message is generated for sending to the AF.

9. The method of claim 8, wherein the NEF provisioning request includes an authorization identifier associated with the AF, a UE identifier, a UE operating profile, and a validity time.

10. The method according to claim 8, further comprising: Generate an AMF provisioning request for sending to an access and mobility management function (AMF) for invoking a parameter provisioning service of the AMF.

11. The method of claim 1 , wherein the NF is a first NF, and the method further comprises: Generate a partial inference result associated with the second NF for sending to the AF.

12. The method of claim 11, wherein the second NF is a Network Data Analysis (NWDA) NF.

13. An apparatus comprising a processing circuit, the processing circuit being configured to: Processing a session request associated with a user equipment (UE), the session request received from an application function (AF); generating a confirmation response associated with the session request for transmission to the AF; and The UE is configured based on the session request.

14. The apparatus of claim 13, wherein the session request comprises a UE identifier, a UE selected configuration, and an authorization identifier associated with the AF.

15. The apparatus of claim 13, wherein to configure the UE based on the session request, the processing circuit is configured to: A radio resource control (RRC) reconfiguration message is generated for sending to the UE.

16. One or more computer-readable media having instructions to be executed to cause a processing circuit to: generating a registration request for sending to an application function (AF); generating a trigger for sending to the AF for initiating or modifying an artificial intelligence machine learning (AIML) session based on AIML inference; and A reconfiguration message is processed based on the trigger, the reconfiguration message being received from a radio access network (RAN).

17. The one or more computer-readable media of claim 16, wherein the reconfiguration message is a radio resource control (RRC) reconfiguration message and the registration request includes a UE consent indication.

18. The one or more computer-readable media of claim 16, wherein the instructions are to be executed to further cause the processing circuit to: Generate a UE selected RAN configuration for sending to the AF.

19. One or more computer-readable media according to claim 18, wherein: The trigger comprises an indication of a RAN configuration selected by the UE; and The RAN configuration selected by the UE includes a physical layer (PHY) configuration or a radio resource control (RRC) configuration.

20. The one or more computer-readable media of claim 18, wherein the UE-selected RAN configuration comprises a mobility management policy, a duty cycle, a carrier aggregation configuration, a measurement configuration, a radio resource management (RRM) configuration, a RAN mobility configuration, an AIML model selection indication, a resource allocation indication, or a beamforming selection indication.

Images