Techniques for network analysis opening from core network of wireless communication system

Abstract

Methods, systems, and devices for wireless communication are described. A first device may receive, from a second device, a first message indicating a plurality of set identifiers (IDs) associated with network analysis of a core network of a wireless communication system. Each set ID of the plurality of set IDs may correspond to a respective operation and a respective set of parameters. The first device may send a second message to a third device, the second message indicating a request for network analysis associated with a set ID of the plurality of set IDs. The request may be in accordance with the respective operation and the respective set of parameters corresponding to the set ID. In response to the request, the first device may receive a third message from the third device indicating the network analysis associated with the respective operation and the respective set of parameters corresponding to the set ID.

Description

Technical Field

[0001] The following relates to wireless communications, including techniques for network analysis from the core network of a wireless communications system. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth-generation (4G) systems (such as long-term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-S-OFDM).

[0003] A wireless multiple-access communication system may include one or more network entities, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for enabling network analysis from a core network of a wireless communication system. For example, the described technology may provide a framework for enabling network analysis to be exposed to an application layer of a protocol stack at a first device. The first device may receive a first message from a second device, the first message indicating a plurality of set identifiers (IDs) associated with network analysis of the core network of the wireless communication system. In this example, each set ID in the plurality of set IDs may correspond to a corresponding operation and a corresponding parameter set. The first device may send a second message to a third device, the second message indicating a request for network analysis associated with a set ID in the plurality of set IDs. The request may be based on the corresponding operation and the corresponding parameter set corresponding to the set ID. In response to the request, the first device may receive a third message from the third device, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0005] A method for wireless communication at a first device is described. The method may include: receiving a first message from a second device, the first message indicating a set of multiple set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set; sending a second message to a third device, the second message indicating a request for network analysis associated with a set ID in the set of multiple set IDs, the request being based on the corresponding operation and the corresponding parameter set corresponding to the set ID; and receiving a third message from the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0006] An apparatus for wireless communication at a first device is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a first message from a second device, the first message indicating a set of multiple set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set; send a second message to a third device, the second message indicating a request for network analysis associated with a set ID in the set of multiple set IDs, the request being based on the corresponding operation and the corresponding parameter set corresponding to the set ID; and receive a third message from the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0007] Another apparatus for wireless communication at a first device is described. The apparatus may include: means for receiving a first message from a second device, the first message indicating a set of multiple set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set; means for sending a second message to a third device, the second message indicating a request for network analysis associated with a set ID in the set of multiple set IDs, the request being based on the corresponding operation and the corresponding parameter set corresponding to the set ID; and means for receiving a third message from the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a first device is described. The code may include instructions executable by a processor to: receive a first message from a second device, the first message indicating a set of multiple set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set; send a second message to a third device, the second message indicating a request for network analysis associated with a set ID in the set of multiple set IDs, the request being based on the corresponding operation and the corresponding parameter set corresponding to the set ID; and receive a third message from the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the first message may include operations, features, components, or instructions for performing the following operations: receiving the first message via first application layer signaling as part of a registration process for an application supported at the first device and the second device, wherein the first message indicates a set of multiple set IDs and a corresponding operation corresponding to each set ID in the set of multiple set IDs, and wherein the set of multiple set IDs can be associated with the application.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the second message may include operations, features, components, or instructions for sending the second message via second application layer signaling, wherein the second message indicates the set ID so that the application layer of the protocol stack used at the first device may be unaware of the correspondence between each set ID and the corresponding parameter set.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the first message may include operations, features, components, or instructions for receiving the first message via non-access stratum (NAS) layer signaling, wherein the first message indicates the set of the plurality of set IDs and a corresponding operation corresponding to each set ID in the set of the plurality of set IDs.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first message further indicates a user equipment (UE) policy associated with one or more applications supported at the first device and the second device, and each set ID in the set of multiple set IDs can be associated with a corresponding application in the one or more applications.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the second message may include operations, features, components, or instructions for sending the second message via application layer signaling, wherein the second message indicates the corresponding parameter set corresponding to the set ID.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a fourth message from a fourth device, the fourth message indicating the set of the multiple set IDs and the corresponding parameter set corresponding to each set ID in the set of the multiple set IDs, wherein sending the second message indicating the request and the corresponding parameter set may be based on receiving the fourth message.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the fourth message may include operations, features, components, or instructions for receiving the fourth message via NAS layer signaling, wherein the fourth message further indicates a UE policy associated with one or more applications supported at the first device and the fourth device, and wherein each set ID in the set of multiple set IDs may be associated with a corresponding application in the one or more applications.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: sending the second message indicating the request for the network analysis is associated with performing the corresponding operation corresponding to the set ID.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the respective operation corresponding to the set ID may be associated with a machine learning (ML) model used at the first device or the second device or both.

[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the network analysis can be based on the corresponding parameter set corresponding to the set ID.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the corresponding parameter set corresponding to the set ID can be based on a service level agreement (SLA) associated with the second device.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the third message includes an indication to the first device of a statistic or prediction corresponding to the network analysis associated with the corresponding operation.

[0021] A method for wireless communication at a first device is described. The method may include: obtaining a first message from a second device, the first message indicating a set of multiple set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set; obtaining a second message from a third device, the second message indicating a request for network analysis associated with a set ID in the set of multiple set IDs, the request being based on the corresponding operation and the corresponding parameter set corresponding to the set ID; and outputting a third message to the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0022] An apparatus for wireless communication at a first device is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: obtain a first message from a second device, the first message indicating a set of multiple set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set; obtain a second message from a third device, the second message indicating a request for network analysis associated with a set ID in the set of multiple set IDs, the request being based on the corresponding operation and the corresponding parameter set corresponding to the set ID; and output a third message to the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0023] Another apparatus for wireless communication at a first device is described. The apparatus may include: means for obtaining a first message from a second device, the first message indicating a set of multiple set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set; means for obtaining a second message from a third device, the second message indicating a request for network analysis associated with a set ID in the set of multiple set IDs, the request being based on the corresponding operation and the corresponding parameter set corresponding to the set ID; and means for outputting a third message to the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0024] A non-transitory computer-readable medium storing code for wireless communication at a first device is described. The code may include instructions executable by a processor to: obtain a first message from a second device, the first message indicating a set of multiple set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set; obtain a second message from a third device, the second message indicating a request for network analysis associated with a set ID in the set of multiple set IDs, the request being based on the corresponding operation and the corresponding parameter set corresponding to the set ID; and output a third message to the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: outputting a fourth message via a network application function (Naf) in response to obtaining the second message indicating the request for the network analysis, wherein the fourth message indicates the corresponding parameter set; and obtaining a fifth message via the Naf in response to outputting the fourth message, wherein the fifth message indicates the network analysis, and wherein outputting the third message may be based on receiving the fifth message indicating the network analysis.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining the second message may include operations, features, components, or instructions for performing the following operations: obtaining the second message via application layer signaling, wherein the second message indicates the set ID; and identifying the corresponding parameter set corresponding to the set ID in response to obtaining the second message, wherein outputting the fourth message may be based on identifying the corresponding parameter set.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining the second message may include operations, features, components, or instructions for performing the following operations: obtaining the second message via application layer signaling, wherein the second message indicates the corresponding parameter set corresponding to the set ID, and wherein outputting the fourth message may be based on the second message indicating the corresponding parameter set.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the respective operation corresponding to the set ID may be associated with an ML model used at the second device or the third device, or both.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining the second message indicating the request for the network analysis associated with the corresponding operation corresponding to the set ID.

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the network analysis can be based on the corresponding parameter set corresponding to the set ID.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the corresponding parameter set corresponding to the set ID can be based on an SLA associated with the second device. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 An example of a wireless communication system supporting techniques for network analysis exposure from a core network of the wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0033] Figure 2 An example of a network architecture supporting techniques for network analysis exposure from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0034] Figure 3 An example of a wireless communication system supporting techniques for network analysis exposure from a core network of the wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0035] Figure 4 and Figure 5 Each illustrates an example of a process flow supporting techniques for network analysis exposure from a core network of a wireless communication system according to one or more aspects of the present disclosure.

[0036] Figure 6 and Figure 7 A block diagram illustrating a device supporting techniques for network analysis exposure from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0037] Figure 8 A block diagram illustrating a communications manager supporting techniques for network analysis exposure from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0038] Figure 9 A diagram illustrating a system including devices supporting techniques for network analysis exposure from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0039] Figure 10 and Figure 11 A block diagram illustrating a device supporting techniques for network analysis exposure from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 12 A block diagram illustrating a communications manager supporting techniques for network analysis exposure from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Figure 13 A diagram illustrating a system including devices supporting techniques for network analysis exposure from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0042] Figures 14 to 17 A flow chart illustrating a method of supporting techniques for network analysis opening from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0043] Some wireless communication systems may support a client-server architecture, in which operations associated with a software application may be divided between a provider of services or resources associated with the application and a requester of the services or resources. The application service provider may be referred to as an application server, and the application service requester may be referred to as an application client. In some examples, the application client may operate at the application layer of a protocol stack on a device, such as a user equipment (UE). That is, the wireless communication system may include one or more communication devices, such as UEs, that support one or more application clients. Operations associated with (e.g., supported by) the application may include artificial intelligence (AI) and machine learning (ML). That is, the application may support AI or ML (AI / ML) operations that may be divided (e.g., split) between the application server and the application client at the UE. In some examples, the application client at the UE may perform one or more AI / ML operations to generate or train AI / ML models that may be used at one or more other layers (e.g., lower layers) of the protocol stack at the UE. For example, an application client (e.g., an application layer, a higher layer of the protocol stack) may perform one or more AI / ML operations to generate an AI / ML model that may be used by lower layers of the protocol stack at the UE for channel estimation. In some examples, lower layers may use AI / ML models generated by an application client (e.g., at the application layer) to measure, predict, or report channel conditions experienced at the UE.

[0044] In some examples, an application server and an application client may determine (e.g., coordinate or select) how and when to partition one or more aspects of an AI / ML operation associated with an application. For example, the application server and the application client may determine a first portion of the AI / ML operation to be performed at the application client and a second portion of the AI / ML operation to be performed at the application server. Additionally, the application server and the application client may (e.g., dynamically) adjust the first portion of the AI / ML operation to be performed at the application client and the second portion of the AI / ML operation to be performed at the application server. That is, the application server and the application client may determine respective durations during which the application client may perform the first portion of the AI / ML operation and the application client may perform the second portion of the AI / ML operation.

[0045] In some examples, the processing power associated with a UE (e.g., a local device supporting an application client) may constrain the number or type of AI / ML operations that can be performed at the application client. Additionally, while the number or type of AI / ML operations that can be performed at an application server may be relatively less constrained (e.g., due to increased processing power relative to the UE), increasing the number of AI / ML operations performed at application server 335 may result in increased latency (e.g., processing delays) for some AI / ML operations.

[0046] In some examples, an application client or an application server, or both, can use network analytics associated with a core network of a wireless communication system to improve the performance of one or more AI / ML operations. For example, the application client or the application server, or both, can use network analytics to determine how and when to partition AI / ML operations associated with an application. Additionally, in some examples, the application client can obtain (e.g., download) one or more AI / ML models for AI / ML operations from the application server, and can use network analytics to determine when to obtain (or request) the AI / ML models from the application client.

[0047] A core network may implement one or more network functions, such as a network data analysis function (NWDAF), which the core network may use to collect information associated with a wireless communication system and generate network analytics. For example, the core network may use the NWDAF to provide network analytics function services for the wireless communication system. In some examples, the NWDAF may be associated with one or more analytics identifiers (IDs) corresponding to analytics types supported at the NWDAF. Thus, other network functions or communication devices (such as UEs) may use the analytics IDs to obtain network analytics (e.g., of the corresponding type) from the NWDAF. However, in some examples, the UE may not be able to interpret the analytics IDs. That is, the UE may lack information for identifying the analytics type that may be associated with a particular analytics ID. Furthermore, exposing the correspondence between the types of network analytics and analytics IDs may result in one or more security risks for mobile network operators (MNOs) that may support the NWDAF. Consequently, the core network may lack a mechanism for exposing network analytics (e.g., generated at the NWDAF) to the UE via such analytics IDs, let alone an efficient or relatively secure mechanism.

[0048] Various aspects of the present disclosure generally relate to techniques for exposing network analytics from a core network of a wireless communication system, and more particularly, to a framework for exposing network analytics to an application client at a UE. For example, an application server may configure an application function at the core network, which may be referred to as an Information Exposure Application Function (IEAF), with one or more set IDs associated with network analytics available from a network development environment (NWDAF). In this example, the set IDs (e.g., each set ID) may be associated with a corresponding set of parameters, where the parameters may correspond to a corresponding type of network analytics available from the NWDAF. Additionally, the set IDs (e.g., each set ID) may correspond to corresponding operations that may be executed at the UE and for which the UE may utilize network analytics. For example, the operations may include AI / ML model splitting operations (e.g., determining how and when to partition AI / ML operations associated with an application) or AI / ML model downloading operations (e.g., determining when to download or request download of an AI / ML model from an application server), among others.

[0049] In some examples, an application layer of a protocol stack at a UE (e.g., an application client at the UE) may be configured with a set ID and a corresponding operation. Thus, without knowing the correspondence between each set ID and a corresponding parameter set, the application client may identify the set ID based on the operation performed at the application client, and use the set ID to obtain network analysis from the core network (e.g., via the IEAF). In some other examples, a non-access stratum (NAS) layer of a protocol stack at a UE (which may be more secure than the application layer) may be configured with a correspondence between each set ID and a corresponding parameter set. Thus, the NAS layer may map the set ID obtained from the application client to a corresponding parameter set, which may be used to obtain network analysis from the core network.

[0050] Aspects of the subject matter described herein can be implemented to achieve one or more of the following potential advantages. For example, as described herein, the described communications device may employ techniques for network analytics exposure from a core network of a wireless communications system to provide benefits and enhancements to the operation of the communications device, including enabling a UE to obtain network analytics from the core network. Additionally, such techniques may support increased security and increased performance associated with application layer AI / ML operations at the UE, among other possible benefits. Aspects of the present disclosure are initially described in the context of a wireless communications system, network architecture, and process flow. Aspects of the present disclosure are further illustrated with reference to apparatus diagrams, system diagrams, and flow charts related to techniques for network analytics exposure from a core network of a wireless communications system and described with reference to these diagrams.

[0051] Figure 1 An example of a wireless communication system 100 that supports techniques for opening network analysis from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0052] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices that take different forms or have different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entities 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entities 105 and the UEs 115 may support signal communication according to one or more radio access technologies (RATs).

[0053] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices that take different forms or have different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. The UEs 115 described herein may be capable of supporting communication with various types of devices such as Figure 1 Other UEs 115 or network entities 105 are shown communicating.

[0054] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0055] In some examples, network entities 105 can communicate with core network 130, with each other, or both. For example, network entities 105 can communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 can communicate with each other via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols), directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130). In some examples, network entities 105 can communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. Backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 can be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0056] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an eNodeB (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in a converged (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as the base station 140).

[0057] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 can include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit receive point (TRP). One or more components of the network entity 105 in the disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0058] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of the protocol stack can be employed between CU 160 and DU 165 such that CU 160 can support one or more layers of the protocol stack and DU 165 can support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within the protocol layer (e.g., some functions of a protocol layer may be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer may be performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0059] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to the core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0060] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between the IAB node 104 and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node that has a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., the F1AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of part of a backhaul link).

[0061] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (e.g., DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115.

[0062] For example, IAB node 104 may be referred to as a parent node supporting communications for child IAB nodes, or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection to the core network 130 (e.g., backhaul communication link 120) and may serve as a parent node for IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to UE 115 via IAB node 104, or may directly signal the transmissions to UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to IAB node 104 via the F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via the DU 165. That is, data may be relayed to and from IAB node 104 via signaling via the NR Uu interface of the MT to IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0063] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support the techniques described herein for network analysis exposure from the core network of a wireless communication system. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0064] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances or vehicles, meters, etc.

[0065] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0066] The UE 115 and the network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier used for the communication link 125 can include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel can carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 can support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between those devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0067] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order of the modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0068] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0069] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0070] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a Transmit Time Interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0071] According to various techniques, physical channels may be multiplexed using carriers for communication. Physical control channels and physical data channels may be multiplexed for signaling over downlink carriers, for example, using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of a carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0072] In some examples, network entities 105 (e.g., base stations 140, RUs 170) can be mobile and, therefore, provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but the different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0073] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms "ultra-reliable", "low latency" and "ultra-reliable low latency" are used interchangeably herein.

[0074] In some examples, a UE 115 can be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication can be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which can support aspects of such D2D communication configured by the network entity 105 (e.g., scheduled by the network entity). In some examples, one or more UEs 115 in such a group can be outside the coverage area 110 of the network entity 105 or can otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0075] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP services 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0076] The wireless communication system 100 can operate using one or more frequency bands that can range from 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clusters), but these waves can penetrate structures sufficiently for a macro cell to provide service to a UE 115 located indoors. Communication using UHF waves can be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) than communication using the lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0077] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in combination with component carriers operating using licensed bands. Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0078] A network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input, multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support RF beamforming for signals transmitted via the antenna ports.

[0079] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. The adjustments associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0080] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly for communication via logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection, error correction, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer may provide for the establishment, configuration, and maintenance of RRC connections between the UE 115 and the network entity 105 or core network 130 for radio bearers supporting user plane data. The PHY layer may map transport channels to physical channels.

[0081] The wireless communication system 100 may support a client-server architecture in which operations associated with an application may be partitioned between an application server and an application client (e.g., UE 115). The operations associated with the application may include AI / ML operations. The UE 115 or the application server, or both, may use network analytics associated with the core network 130 to determine how and when to partition the AI / ML operations associated with the application. Additionally, the UE 115 may obtain one or more AI / ML models for the AI / ML operations from the application server and may use network analytics to determine when to obtain the AI / ML models. In some examples, the core network 130 may lack a mechanism for exposing network analytics generated at the NWDAF included in the core network 130 to the UE 115.

[0082] However, in some other examples, the core network 130 (e.g., and the UE 115) may support a framework for exposing network analytics to application clients at the UE 115. For example, the core network 130 may include an IEAF that may be configured with one or more set IDs associated with network analytics that may be obtained from the NWDAF. The set IDs (e.g., each set ID) may be associated with a corresponding parameter set and may correspond to a corresponding operation that may be performed at the UE 115. The UE 115 may send a request to the IEAF at the core network 130 via application layer signaling for network analytics associated with the set ID corresponding to the operation performed at the UE 115. In response to the request, the IEAF may obtain the network analytics from the NWDAF based on the corresponding parameter set corresponding to the set ID. The IEAF may forward the network analytics to the UE 115 via application layer signaling. In some examples, using application layer signaling to obtain network analytics from the core network 130 may result in increased performance associated with application layer AI / ML operations at the UE, as well as other possible benefits.

[0083] Figure 2An example network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting techniques for network analysis exposure from the core network of a wireless communication system according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a that may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a via one or more disaggregated network entities 105 (e.g., a near-RT RIC 175-b via an E2 link, a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both). The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. A RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with a UE 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.

[0084] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, these network entities 105 may include a wired interface configured to receive signals on the wired transmission medium or to transmit signals to one or more of the other network entities 105 on the wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to transmit signals on a wireless transmission medium to one or more of the other network entities 105, or both.

[0085] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0086] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on functional partitioning, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0087] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0088] The SMO 180-a can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 can include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some implementations, the SMO 180-a can communicate with components configured according to a 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an 01 interface.The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0089] The non-RT RIC 175-a may be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, AI / ML workflows (including model training and updates), or policy-based guidance of applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a may be coupled to or in communication with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions via an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0090] In some examples, non-RT RIC 175-a may receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in near-RT RIC 175-b. Such information may be utilized by near-RT RIC 175-b and may be received at SMO 180-a or non-RT RIC 175-a from a non-network data source or from a network function. In some examples, non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions through SMO 180-a (e.g., via reconfiguration of O1) or via generation of RAN management policies (such as A1 policies).

[0091] In some examples, core network 130-a may use an A1 interface to expose network analytics associated with core network 130-a to UE 115. For example, core network 130-a may include one or more functions, such as an IEAF and a NWDAF. Core network 130-a may use the NWDAF to generate multiple types of network analytics, and use the IEAF to expose the network analytics generated at the NWDAF to UE 115 via the A1 interface. For example, UE 115 may include a data exposure client (DEC) and an application client that can communicate via an application programming interface (API). The application client may determine to perform an operation associated with an AI / ML model. The operation may be associated with a set ID corresponding to one or more types of network analytics generated at the NWDAF. For example, the set ID may correspond to a parameter set, where each parameter may correspond to a corresponding type of analysis that can be generated at the NWDAF. The application client may send a request for the network analytics associated with the set ID to the DEC, which may forward the request to the IEAF at core network 130-a. The IEAF may use the parameter set corresponding to the set ID to obtain the associated network analytics from the NWDAF. The IEAF may output the obtained network analysis to the DEC, which may forward the obtained network analysis to the application client. Opening the network analysis to the UE 115 via the A1 interface may enable the core network 130 to reduce the security risks associated with opening the network analysis and increase the performance of operations at the UE 115, among other possible benefits.

[0092] Figure 3 An example of a wireless communication system 300 that supports techniques for network analysis exposure from a core network of a wireless communication system according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may implement aspects of the wireless communication system 100 and the network architecture 200. For example, the wireless communication system 300 may include a UE 315 that may be a Figure 1 and Figure 2 Examples of UEs illustrated and described with reference to these figures. UE 315 may include DEC 345 and application client 340, which may be reference Figure 1 and Figure 2 The wireless communication system 300 may further include a core network 330, which may be composed of Figure 1 and Figure 2 Examples of core networks illustrated and described with reference to these figures. The core network 330 may include one or more core network functions, such as IEAF 305, NWDAF 310, and NEF 320, which may be referenced Figure 1 and Figure 2 Examples of corresponding functions described. In some examples, core network functions can communicate via one or more network application functions (Naf).

[0093] The wireless communication system 300 may support a client-server architecture in which operations associated with software applications may be divided between an application service provider (e.g., a provider of services or resources associated with the application), such as an application server 335, and an application client 340 (e.g., a requester of the services or resources). That is, the UE 315 may support an application associated with the application server 335 and may communicate with the application server 335 via the application client 340 using application-layer signaling. The application may support AI / ML operations at both the application server 335 and the application client 340. That is, the application may support AI / ML operations that may be divided (e.g., split) between the application server 335 and the application client 340 at the UE 315. In other words, the application layer of the protocol stack at the UE 315 (e.g., the application client 340) may perform AI / ML operations according to the associated application, and the AI / ML operations may be divided between the application server 335 and the application client 340.

[0094] In some examples, application server 335 and application client 340 may determine (e.g., coordinate) how and when to split various aspects of an AI / ML operation. For example, an application may request that both application server 335 and application client 340 manage (e.g., handle, execute, coordinate) the AI / ML operation associated with the application. Thus, application server 335 and application client 340 may determine a first portion of the AI / ML operation to be executed at application client 340 and a second portion of the AI / ML operation to be executed at application server 335. The first portion and the second portion may include different AI / ML operations or one or more identical AI / ML operations. Additionally, application server 335 and application client 340 may adjust (e.g., over time, such as dynamically) the first portion of the AI / ML operation to be executed at application client 340 and the second portion of the AI / ML operation to be executed at the application server. For example, the application server and application client may determine one or more respective time durations during which the application client may execute the first portion (or some other portion) of the AI / ML operation and the application client may execute the second portion (or some other portion) of the AI / ML operation.

[0095] In some examples, processing power associated with UE 315 (e.g., a local device supporting application client 340) may constrain the number or type of AI / ML operations that may be performed at application client 340. Additionally, while the number or type of AI / ML operations that may be performed at application server 335 may be relatively less constrained (e.g., due to increased processing power at application server 335 relative to UE 315), increasing the number of AI / ML operations performed at application server 335 or assigning relatively more complex types of AI / ML operations to application server 335 may result in increased latency (e.g., processing delays) for some AI / ML operations.

[0096] In some examples, the application client 340 or the application server 335, or both, can use network analytics associated with the core network 330 of the wireless communication system 300 to improve performance associated with one or more AI / ML operations associated with the application. For example, the application client 340 (or the application server 335) can use one or more types of network analytics to determine how and when to partition the AI / ML operations associated with the application. That is, to support application-layer AI / ML split functionality, the application client 340 (or the application server 335) can request that the core network 330 expose network analytics to the UE 315 (e.g., to the application layer of the protocol stack at the UE 315) for use in determining how and when to partition the application-layer AI / ML operations between the application client 340 and the application server 335. In other words, to support application-layer AI / ML split functionality, it may be beneficial for the core network 330 to expose network analytics (e.g., network slice instance load prediction information, service experience prediction information, and user data congestion prediction information) to the application client 340 at the UE 315, so that the application client 340 can use the exposed network analytics to determine how and when to divide (e.g., split) application-layer AI / ML operations between the application client 340 and the application server 335. Additionally, in some examples, the application client 340 can obtain (e.g., download) an AI / ML model for one or more of the AI / ML operations associated with the application from the application server 335 (e.g., an application service provider). In such examples, the application client 340 can use the exposed network analytics to determine when to download (or request download) the AI / ML model from the application client 340. In other words, it may also be beneficial for the application client 340 to consider network analysis (e.g., network slice instance load prediction information, service experience prediction information, and user data congestion prediction information) to determine when to download (or request download) the AI / ML model from the application server 335.

[0097] The core network 330 may use one or more network functions, such as the NWDAF 310, to generate network analytics associated with the wireless communication system 300. For example, the NWDAF 310 may provide network data analytics functionality services for the wireless communication system 300 (e.g., a 5G system). Network data analytics functionality services may include, for example, an event subscription service (e.g., the Nnwdaf_EventsSubscription service) or a network analytics information service (e.g., the Nnwdaf_AnalyticsInfo service). The NWDAF 310 may collect information (e.g., data such as statistics, metrics, and events), generate network analytics based on the collected information (e.g., using AI / ML models), and provide the network analytics to consumers. In other words, the NWDAF 310 may obtain (e.g., collect) information such as statistics, metrics, and events, and use AI / ML models to generate statistics or predictions (e.g., network analytics) based on the obtained information.

[0098] In some examples, the NWDAF 310 can obtain information from UEs (e.g., including UE 315), applications (e.g., application server 335), other core network functions, network entities, and operations, administration, and maintenance (OAM) systems, among others. In some examples, the NWDAF 310 can obtain information (e.g., data) from the UE 315 and the application server 335 via one or more other functions. For example, the NWDAF 310 can obtain information from (and expose information to) the application server 335 via the NEF 320. Additionally, the NWDAF 310 can obtain information from the UE 315 via a data collection application function (DCAF).

[0099] AMF can be a reference Figure 1 An example of an AMF described herein. For example, the AMF may be a control plane entity (e.g., a control plane function) included in the core network 330 that can manage connections and manage mobility operations. The AMF may serve as an access point for communication devices such as UEs (e.g., UE 315) and network entities to the core network 330. For example, the AMF may communicate with network entities such as the core network 330 via a control plane interface (e.g., an N2 interface or a next generation control plane (NG-C) interface). Figure 1 and Figure 2 The AMF 310 may communicate with the CUs illustrated and described with reference to these figures. Additionally, the AMF may communicate with the UE 315 via NAS signaling (e.g., via the N1 interface). The NWDAF 310 may provide network analytics to consumers (e.g., other core network functions, OAM), or use one or more data repositories to store network analytics, or both.

[0100] In some examples, the core network 330 may include multiple NWDAFs (e.g., including NWDAF 310). In such examples, the NWDAFs (e.g., each NWDAF) may be associated with one or more analysis IDs. The analysis IDs associated with the NWDAFs (e.g., each analysis ID) may correspond to corresponding types of analysis supported at the NWDAF. For example, the NWDAF 310 may be associated with a first analysis ID corresponding to a first type of analysis supported by (and available from) the NWDAF 310. Thus, a consumer may request network analysis from the NWDAF 310 via the first analysis ID (e.g., may discover the NWDAF 310 to obtain network analysis). For example, a consumer may obtain network analysis from the NWDAF 310 via a subscription or request that may indicate one or more analysis IDs corresponding to the one or more types of analysis being requested. In some examples, the NWDAF 310 may enable consumers to subscribe to and unsubscribe from notifications, for example based on a threshold.

[0101] The network analytics provided by (e.g., generated at) the NWDAF 310 may include statistics and predictions (e.g., obtained using AI or ML operations). For example, the NWDAF 310 may provide statistics or predictions associated with the wireless communication system 300. In some examples, the wireless communication system 300 may support network slicing. In such examples, the NWDAF 310 may provide analytics (e.g., statistics or predictions) associated with a network slice instance, such as load level information, etc. Additionally, the NWDAF 310 may provide other information associated with the network slice instance, such as network slice congestion event notifications. A network slice instance (also referred to as a network slice) may correspond to a virtualized instance of a logical network, which may include a subset of available network resources (e.g., virtual resources, computing resources, networking resources, storage resources) and one or more rules for identifying services that can be supported via the subset of resources (e.g., defined by the subset of resources and the one or more rules). In some examples, the subset of resources allocated to a network slice may be based on one or more constraints of an application or service associated with the network slice. For example, a subset of resources may be allocated to a network slice to meet a service level agreement (SLA) for an application or service associated with the network slice. An SLA may be an example of a contract (e.g., an agreement) between an application service provider and an MNO. In some examples, the network analytics generated at and exposed by the NWDAF 310 may meet one or more SLAs associated with an MNO that may support the NWDAF 310. For example, to reduce security risks for the MNO, the MNO or application service provider may configure (e.g., enable) the NWDAF 310 (or one or more other core network functions) to expose one or more types of network analytics to consumers, which may be based on an SLA. In other words, the network analytics (e.g., data) exposed from the core network (e.g., via the NWDAF 310) may be based on one or more SLAs.

[0102] In some examples, the core network 330 may use one or more analysis IDs to identify the type of network analysis (e.g., different types of network analysis). For example, a consumer of network analysis from the NWDAF 310 may request a type of network analysis (e.g., network analysis data) from the NWDAF 310 using the analysis ID associated with that type of network analysis. In other words, the consumer may request a type of network analysis from the NWDAF 310 based on the value of the analysis ID indicated via the request (e.g., the value of the EvendId information element (IE)). The application client 340 may not be able to interpret (e.g., understand) the analysis ID. For example, the application layer of the protocol stack at the UE 315 may lack information for identifying the type of analysis that may be associated with a particular analysis ID. Therefore, the application client 340 may not be able to interpret the network analysis output (e.g., output data) from the NWDAF 310. In other words, the network analysis exposed to the application client 340 may be identified using an analysis ID that the application client 340 may not understand. The core network 330 can expose the analysis ID information to the application client 340 so that the application client 340 can interpret the network analysis output from the NWDAF 310. However, exposing the analysis ID information to the application client 340 may result in one or more security risks for the MNO. Therefore, it may be unclear whether or how the core network 330 can indicate network analysis (e.g., network-supported analysis information) to the application client 340. In other words, the core network 330 may lack a mechanism for exposing network analysis (e.g., network-supported analysis information) to the UE 315 application layer (e.g., application client 340), let alone an effective mechanism or a relatively secure mechanism.

[0103] In some examples, techniques for opening network analysis from the core network of a wireless communication system, as described herein, may provide a framework for opening network analysis to application clients 340 while maintaining (or improving) the security of the MNO. Figure 3As illustrated in the example of , application server 335 may configure IEAF 305 with one or more set IDs associated with network analytics from NWDAF 310. For example, IEAF 305 may obtain (e.g., via interface 361) a set ID indication 360 from application server 335, which may indicate multiple set IDs associated with network analytics available from NWDAF 310. In this example, a set ID (e.g., each set ID) may be associated with a corresponding parameter set and a corresponding operation. Parameters included in the parameter set corresponding to the set ID may correspond to a type of network analytics available from NWDAF 310. Additionally, the operation associated with the set ID may correspond to an operation executable at application client 340 (e.g., an operation for which application client 340 may use the obtained network analytics). For example, the operation may include an AI / ML model splitting operation (e.g., determining how and when to partition AI / ML operations associated with an application) or an AI / ML model downloading operation (e.g., determining when to download or request download of an AI / ML model from an application server), among others. Thus, in some examples, set ID indication 360 may indicate multiple parameter sets corresponding to multiple set IDs, multiple operations corresponding to multiple set IDs, or both. In other words, a configuration (e.g., a data collection application function) from application server 335 to IEAF 305 may indicate a set ID, corresponding operations associated with the set ID, and corresponding parameter sets corresponding to the set ID. In some examples, this configuration (e.g., an SLA configuration) may be based on one or more SLAs. For example, an SLA configuration may indicate (e.g., authorize) one or more types of network analytics (e.g., data) that may be made available to (e.g., shared with) application client 340. In other words, the multiple parameter sets corresponding to the multiple set IDs indicated to IEAF 305 via set ID indication 360 may correspond to (e.g., indicate, configure) the types of network analytics that may be made available to application client 340 (e.g., via IEAF 305). In some examples, application server 335 may provide SLA configuration to IEAF 305 via application layer signaling (eg, using interface 361 ) or via NEF 320 using interface 321 (eg, via control plane signaling within core network 330 ).

[0104] Associating the set ID with the corresponding operation performed by the application client 340 may enable the IEAF 305 to expose network analysis to the application client 340 without exposing the type of analysis associated with the set ID (e.g., the corresponding parameter set) to the application client 340. That is, without knowing the correspondence between each set ID and the corresponding parameter set, the application client 340 may identify the set ID based on the operation performed at the application client 340 and use the set ID to obtain network analysis from the core network (e.g., via the IEAF 305).

[0105] To obtain network analysis from the IEAF 305, the application client 340 may use an ID (e.g., an address) associated with the IEAF 305. For example, the PCF may indicate the address associated with the IEAF 305 to the DEC 345 (e.g., via NAS signaling through the AMF), and the DEC 345 may indicate the address associated with the IEAF 305 to the application client 340. In some examples, the PCF may provide the IEAF address to the DEC 345 via UE policy. The UE policy may provide information associated with mapping services (e.g., different services) to one or more PDU sessions (e.g., different PDU sessions) and one or more network slices. For example, the PCF may provide the DEC 345 at the UE 315 with an IEAF address configuration via UE policy, and the IEAF address configuration may indicate the IEAF address associated with the IEAF 305. In some examples, the PCF may provide the application client 340 with multiple set IDs configured at the IEAF 305 via the DEC 345. For example, the PCF may use a UE policy (e.g., indicated via the DEC 345) to provide the IEAF address, a plurality of set IDs, and a plurality of operations corresponding to the plurality of set IDs to the application client 340. In some other examples, the application client 340 may obtain the plurality of set IDs and the plurality of operations corresponding to the plurality of set IDs via the application server 335. In other words, the application client 340 may receive an indication of a plurality of set IDs associated with the network analysis of the core network 330 from the PCF (e.g., via the DEC 345) or from the application server 335, where each set ID corresponds to a respective operation and a respective parameter set.

[0106] The application client 340 may establish a protocol data unit (PDU) session with the IEAF 305 (e.g., via the DEC 345) so that the application client 340 can obtain network analytics from the IEAF 305. In other words, as part of the data collection process, the DEC 345 may establish a PDU session (e.g., an application layer connection according to an open configuration) with the IEAF 305. In some examples, the PDU session may provide a connection between the application client 340 and the core network 330. For example, the application client 340 may use the PDU session to obtain network analytics from the IEAF 305 via the DEC 345. In other words, during the PDU session, the application client 340 may send (e.g., via the DEC 345) a network analysis request 365 for network analytics associated with a set ID (e.g., from among a plurality of set IDs), the network analysis request being in accordance with a corresponding operation and a corresponding parameter set corresponding to the set ID. For example, DEC 345 may send a network analysis request 365 (e.g., a data collection request) to IEAF 305 via application layer signaling (e.g., via A1 interface 355), and the network analysis request 365 may indicate a request for network analysis associated with the set ID. A1 interface 355 may be a Figure 2 An example of an A1 interface is illustrated and described with reference to the figure. The set ID can be based on an operation performed at the application client 340. For example, the application client 340 can determine to perform an operation associated with the set ID. Thus, in some examples, the application client can indicate the set ID associated with the operation to the IEAF 305 via a network analysis request 365 (e.g., through the DEC 345). In some other examples, the core network can configure a NAS layer of the protocol stack at the UE 315 with multiple parameter sets associated with multiple set IDs. In such examples, the network analysis request 365 can indicate the parameter set corresponding to the set ID.

[0107] In some examples, such as in response to the get network analytics request 365, the IEAF 305 may perform NWDAF discovery. For example, the IEAF 305 may use an analysis ID associated with the NWDAF 310 (e.g., and one or more of the parameters corresponding to the set ID) to discover the NWDAF 310 and obtain the network analytics from the NWDAF. In some examples, based on discovering the NWDAF 310, the IEAF 305 may use a service operation (e.g., an Nwdaf_AlantricsSubstription_subscribe service operation) to obtain event notifications (e.g., and the requested network analytics) from the NWDAF 310 (e.g., on a specific network slice instance that may be specified via a subscription indication). In some examples, subscription to the NWDAF 310 may be based on user consent. For example, in response to receiving the subscription indication, the NWDAF 310 may perform a user consent check. In some examples, based on the user consent check, the NWDAF 310 can use another service operation (e.g., the Nwdaf_AlantricsSubstription_Notify service operation) to notify the IEAF 305 of a subscription event (e.g., network analysis 370). In some examples, the event can include exceeding a threshold (e.g., a load threshold, a congestion threshold). Additionally or alternatively, the event can correspond to a periodic notification. For example, the NWDAF 310 can be configured to provide (or notify) the IEAF 305 of the network analysis 370 on a periodic basis.

[0108] In some examples, the IEAF 305 may use a service operation (or another type of request) to obtain the network analysis requested by the application client 340 from the NWDAF 310. For example, the IEAF 305 may output a message indicating a request for network analysis (e.g., the network analysis requested by the application client 340) via the Naf 325. The message may indicate a corresponding parameter set associated with the set ID.

[0109] In some examples, such as in response to the network analysis request 365, the application client 340 can receive the network analysis 370 from the IEAF 305. The network analysis 370 can be associated with a corresponding operation and a corresponding parameter set corresponding to the set ID. For example, the IEAF 305 can indicate (e.g., configure) the network analysis 370 (e.g., the data allowed to be exposed) to the DEC 345, which can forward the network analysis 370 to the application client 340 via the API 350.

[0110] The IEAF 305 may obtain network analysis 370 from the NWDAF 310 in response to a network analysis request 365 (e.g., via the Naf 325). The network analysis 370 may include load level information, such as analysis (e.g., predictions or statistics) associated with traffic load or resource usage within the network slice instance. Additionally or alternatively, the network analysis 370 may include analysis associated with a service experience (e.g., NWDAF 310 service) of an application or UE 315 (e.g., a UE group), load analysis associated with another core network function, network load performance analysis, future load prediction, UE behavior analysis (e.g., predicted behavior associated with the UE 315, abnormal behavior associated with the UE 315), UE mobility analysis, UE communication analysis (e.g., predictions or statistics associated with wireless communications at the UE 315), network congestion analysis, or quality of service (QoS) analysis, among others.

[0111] The IEAF 305 can output the network analysis 370 to the DEC 345 via application layer signaling (e.g., via the A1 interface 355). In other words, the DEC 345 can transmit a network analysis request 365 to the IEAF 305, receive the network analysis 370 (e.g., exposed data) from the IEAF 305, and forward the network analysis 370 to the application client 340, which can be a consumer of the network analysis 370 (e.g., exposed data). In some examples, enabling the application client 340 to obtain network analysis from the core network 330 can result in increased performance associated with application layer AI / ML operations at the UE 315, as well as other possible benefits.

[0112] Figure 4 An example of a process flow 400 supporting techniques for opening network analysis from a core network of a wireless communication system according to one or more aspects of the present disclosure is illustrated. The process flow 400 may be implemented or implemented at one or more aspects of the wireless communication system 100, the network architecture 200, and the wireless communication system 300. For example, the process flow 400 may be implemented at a UE 415, an NWDAF 410, a PCF 425, an IEAF 405, and an application server 420, which may be implemented by Figures 1 to 3Examples of corresponding devices illustrated and described with reference to these figures. Operations performed at UE 415, NWDAF 410, PCF 425, IEAF 405, and application server 420 may support improvements to network analysis exposure from the core network of the wireless communication system, among other benefits. In the following description of process flow 400, operations performed at UE 415, NWDAF 410, PCF 425, IEAF 405, and application server 420 may be performed in an order different from the example order shown. Additionally, operations performed at UE 415, NWDAF 410, PCF 425, IEAF 405, and application server 420 may be performed at different times. Some operations may be combined, and some operations may be omitted. In some examples, UE 415, NWDAF 410, PCF 425, IEAF 405, and application server 420 may support an architecture for exposing network analysis to the application layer of the protocol stack at UE 415.

[0113] The IEAF 405 may be configured with information for obtaining network analysis associated with the wireless communication system from the IEAF 405. The information may include a plurality of set IDs, corresponding operations corresponding to each set ID, and corresponding parameter sets associated with each set ID. In some examples, the information may be configured (e.g., pre-configured) at the IEAF 405 via an MNO supporting the IEAF 405, or may be provisioned to the IEAF 405, for example, via an application server 420 (e.g., via an application service provider).

[0114] For example, at 430, application server 420 may perform SLA configuration with IEAF 405. The SLA configuration may include application server 420 indicating to IEAF 405 a plurality of set IDs associated with network analytics available from NWDAF 410 and corresponding parameter sets. Each of the plurality of set IDs indicated to IEAF 405 (e.g., configured at IEAF 405 as part of the SLA configuration at 430) may correspond to a corresponding operation (e.g., an AI / ML operation) and a corresponding parameter set. In some examples, the SLA configuration at 430 may be based on an SLA between an application service provider (e.g., application server 420) and an MNO that may support IEAF 405 and NWDAF 410. For example, the application service provider may negotiate with the MNO regarding parameter sets (e.g., and corresponding analytics) that may be made available to UE 415 for multiple operations (e.g., for different purposes). That is, the application server 420 can use the SLA configuration at 430 to configure the IEAF 405 with multiple parameter sets (e.g., and a corresponding set ID associated with each parameter set), which correspond to multiple types of network analysis that the IEAF 405 can open to the UE 415 for multiple (e.g., different) operations.

[0115] As an illustrative example, the SLA configuration at 430 may include the application server 420 indicating a first set ID (e.g., set ID 1), a second set ID (e.g., set ID 2), a first parameter set corresponding to the first set ID, a second parameter set corresponding to the second set ID, a first operation associated with the first set ID, and a second operation associated with the second set ID. In this example, the operation associated with the first set ID may include an AI / ML model download operation. That is, the first set ID may be used by the application client at UE 415 (e.g., may be defined for the application client) to obtain network analytics, which the application client may use to improve AI / ML model downloads. In other words, the application client at UE 415 may use the network analytics associated with the first set ID to determine when to download the AI / ML model from the application server 420. Therefore, in some examples, the first parameter set corresponding to the first set ID may include parameters associated with service experience prediction analysis, parameters associated with QoS monitoring analysis, parameters associated with UE mobility prediction analysis, and so on. The operation associated with the second set ID may include an AI / ML model splitting operation. That is, the second ID can be used at the application client at UE 415 to obtain network analysis, which the application client can use to improve the division (e.g., splitting) of AI / ML model operations between the application client at UE 415 and application server 420. In other words, the application client at UE 415 can use the network analysis associated with the second set ID to determine when and how to split AI / ML model operations between the application client at UE 415 and application server 420. Therefore, in some examples, the second parameter set may include parameters associated with QoS sustainability prediction analysis, parameters associated with slice load prediction analysis, parameters associated with data network performance prediction analysis, and the like.

[0116] In order to request network analysis from the IEAF 405, the application layer of the protocol stack at the UE 415 (e.g., the application client at the UE 415) may be configured with multiple set IDs and multiple operations corresponding to the multiple set IDs. For example, the application client at the UE 415 may receive a set ID indication that indicates at least multiple set IDs (e.g., one or more set IDs among the set IDs configured at the IEAF 405) and a corresponding operation corresponding to each set ID.

[0117] In some examples, at 435, UE 415 may receive a set ID indication from application server 420 via application layer signaling. For example, UE 415 may receive an indication of multiple set IDs via application layer signaling that UE 415 may use to obtain network analysis (e.g., one or more types of network analysis) from IEAF 405. In some examples, UE 415 may receive the indication via configuration between application server 420 and an application client at UE 415. For example, UE 415 (e.g., an application client at UE 415) may receive the set ID indication during application layer registration (e.g., of an application associated with the application client at UE 415 and application server 420). In such an example, the multiple set IDs may correspond to the applications being registered. Additionally, application server 420 may send (e.g., transmit) the multiple set IDs and a corresponding operation (e.g., purpose) for each set ID to the application client at UE 415 (e.g., a UE application client). For example, the application server 420 may indicate to the application client at the UE 415 a first set ID (eg, set ID 1) that can be used for an AIML model download operation and a second set ID (eg, set ID 2) that can be used for an AI / ML model splitting operation.

[0118] In some other examples, at 440, UE 415 may receive a set ID indication from PCF 425 via NAS signaling (e.g., through AMF). For example, UE 415 may receive an indication of multiple set IDs that UE 415 may use to obtain network analysis (e.g., one or more types of network analysis) from IEAF 405 via another configuration between PCF 425 and UE 415. In some examples, PCF 425 may provide the set ID indication to UE 415 via UE policy. In such examples, the set ID indication may include a set ID for multiple application IDs (e.g., each application ID) included in the UE policy. The UE policy (e.g., including the set ID indication) may be communicated to UE 415 during a registration area update procedure (e.g., with PCF 425).

[0119] At 455, UE 415 may send a network analysis request for network analysis associated with a set ID from among the plurality of set IDs, the network analysis request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID to IEAF 405. In some examples, UE 415 may send the network analysis request to IEAF 405 via application layer signaling. In other words, the application client at UE 415 may send the network analysis request to IEAF 405 in conjunction with performing a corresponding operation corresponding to the set ID (e.g., via DEC at UE 415) to obtain the network analysis associated with the set ID.

[0120] In some examples, the application client at UE 415 may not know the corresponding parameters for each set ID. That is, the application client at UE 415 may not know the correspondence between each set ID and the corresponding parameter set. In such an example, the network analysis request sent at 455 may indicate the set ID. For example, the application client at UE 415 may transmit a network analysis request (e.g., a data request) indicating the set ID to IEAF 405 to request network analysis (e.g., parameters) for a corresponding operation (e.g., purpose). For example, the network analysis request may indicate a first set ID to request network analysis for an AI / ML model download operation, or indicate a second set ID to request network analysis for an AI / ML model split operation. In other words, the UE 415 receives a plurality of set IDs from the PCF 425 (e.g., in a UE policy that may be sent at 440) or from the application server 420 (e.g., during application registration that may occur at 435) via a set ID indication, and transmits a set ID of the plurality of set IDs to the IEAF 405 in a network analysis request (e.g., a data collection request) at 455 to request network analysis associated with the set ID.

[0121] In such an example, at 460, the IEAF 405 may map the set ID indicated via the network analysis request to the corresponding parameter set. In some examples, the IEAF 405 may map the set ID to the corresponding parameter set based on the SLA configuration at 430. For example, the set ID may include a first set ID (e.g., set ID 1), and the IEAF 405 may map the first set ID to a parameter set corresponding to service experience prediction analysis, QoS monitoring analysis, and UE mobility prediction analysis. Alternatively, the set ID may include a second set ID (e.g., set ID 2), and the IEAF 405 may map the second set ID to a parameter set corresponding to QoS sustainability prediction analysis, slice load prediction analysis, and data network performance prediction analysis. In some examples, the IEAF 405 may transmit the corresponding parameter set to the NWDAF 410 to obtain the corresponding analysis.

[0122] In some other examples, the NAS layer of the protocol stack used at UE 415 may be aware of the corresponding parameters for each set ID. For example, at 445, UE 415 may receive a parameter set indication from PCF 425 via NAS layer signaling. That is, the NAS layer of the protocol stack at UE 415 may receive the parameter set indication from PCF 425 via configuration between PCF 425 and UE 415. The parameter set indication may include multiple set IDs, corresponding operations corresponding to each set ID, and corresponding parameter sets corresponding to each set ID. In some examples, the multiple set IDs may correspond to multiple applications. For example, a UE policy may indicate multiple application IDs associated with multiple (e.g., different applications). In such an example, PCF 425 may include the set ID for each application ID in a UE policy (e.g., in a parameter set indication) (e.g., transmitted to UE 415 via NAS signaling during a registration area update procedure).

[0123] In some examples, at 450, the NAS layer of the protocol stack at UE 415 may map the set ID to the corresponding parameter set. For example, the application layer of the protocol stack at UE 415 (e.g., an application client at UE 415) may provide the set ID to the NAS layer of the protocol stack at UE 415 to request the parameter set corresponding to the set ID. That is, the NAS layer of the protocol stack at UE 415 may obtain an indication of the set ID (e.g., corresponding to an operation performed at UE 415) from the application client at UE 415 so that UE 415 can include the parameter set in the network analysis request sent from UE 415 at 455. In other words, the application client at UE 415 provides the set ID to the NAS layer at UE 415 (e.g., to request the corresponding parameter set). In response, the NAS layer at UE 415 maps the parameter set corresponding to the set ID based on a UE policy (e.g., provided by PCF 425) and transmits the requested parameters to IEAF 405 in a network analysis request (e.g., a data collection request).

[0124] In some examples, the IEAF 405 may perform NWDAF discovery at 465. For example, in response to obtaining the network analysis request at 455, the IEAF 405 may perform NWDAF discovery to obtain a network analysis corresponding to a parameter set, which may have been indicated to the IEAF 405 via the network analysis request or determined at the IEAF 405 based on the IEAF mapping the set ID indicated via the network analysis request to the corresponding parameter set (e.g., at 460).

[0125] At 470, UE 415 may receive the network analysis from IEAF 405 via application layer signaling in response to the network analysis request. The network analysis may be associated with a corresponding operation and a corresponding parameter set corresponding to the set ID. In some examples, using IEAF 405 to expose network analysis to UE 415 may result in increased security and increased performance associated with application layer AI / ML operations at UE 415, among other possible benefits.

[0126] Figure 5 An example of a process flow 500 supporting techniques for opening network analysis from a core network of a wireless communication system according to one or more aspects of the present disclosure is illustrated. The process flow 500 may implement or be implemented at one or more aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, and the process flow 400. For example, the process flow 500 may be implemented at the UE 515, the NWDAF 510, the IEAF 505, and the application server 520, which may be implemented by Figures 1 to 4 Examples of corresponding devices illustrated and described with reference to these figures. Operations performed at the UE 515, NWDAF 510, IEAF 505, and application server 520 may support improvements to opening up network analysis from the core network of the wireless communication system, among other benefits. In the following description of process flow 500, the operations performed at the UE 515, NWDAF 510, IEAF 505, and application server 520 may be performed in an order different from the example order shown. Additionally, the operations performed at the UE 515, NWDAF 510, IEAF 505, and application server 520 may be performed at different times. Some operations may be combined, and some operations may be omitted. In some examples, the UE 515, NWDAF 510, IEAF 505, and application server 520 may support an architecture for opening up network analysis to the application layer of the protocol stack at the UE 515.

[0127] At 525, the IEAF 505 may obtain a set ID indication from the application server 520. The set ID indication may indicate a plurality of set IDs associated with network analysis obtained from the NWDAF 510 (e.g., included in the core network of the wireless communication system). In some examples, each of the plurality of set IDs may correspond to a corresponding operation and a corresponding parameter set. For example, the IEAF 505 may receive the set ID indication from the application server 520 via an SLA configuration between the application server 520 and the IEAF 505. In some examples, the SLA configuration may be based on an SLA. That is, an application service provider associated with the application server 520 may negotiate with an MNO supporting the IEAF 505 and the NWDAF 510 regarding parameter sets that may correspond to the set IDs (e.g., and may be exposed from the core network for different purposes). For example, the SLA configuration may indicate each parameter set corresponding to each set ID. As an illustrative example, the SLA configuration may indicate a first set ID (e.g., set ID 1) that may be used (e.g., defined) for an AI / ML model download operation at the UE 515. The first set ID may correspond to a parameter set that includes parameters associated with service experience prediction analysis, parameters associated with QoS monitoring analysis, and parameters associated with UE mobility prediction analysis, among others. Additionally, the SLA configuration may indicate a second set ID (e.g., set ID 2) that may be used (e.g., defined) for an AI / ML model splitting operation at the UE 515. The second set ID may correspond to a parameter set that includes parameters associated with QoS sustainability prediction analysis, parameters associated with slice load prediction analysis, and parameters associated with data network performance prediction analysis.

[0128] At 530, the IEAF 505 may obtain, via application layer signaling, from the UE 515 (e.g., from an application client at the UE 515) a first network analysis request for network analysis associated with a set ID from among the plurality of set IDs indicated to the IEAF 505 via the set ID indication (e.g., received at 525). In some examples, the first network analysis request may indicate a set ID according to a corresponding operation to request network analysis. For example, the set ID included in the first network analysis request may be according to a corresponding operation and a corresponding parameter set corresponding to the set ID. For example, the application client at the UE 515 may transmit the first network analysis request to the IEAF 505 in conjunction with performing a corresponding operation corresponding to the set ID (e.g., via DEC at the UE 515) to obtain network analysis associated with the set ID. In other words, the UE 515 may transmit a first network analysis request (e.g., a data request) to the IEAF 505 to request analysis of an operation (e.g., a specific operation) such as an AI / ML model download operation or an AI / ML model split operation. Therefore, the first network analysis request may indicate the corresponding set ID. In such an example, the IEAF 505 may use the set ID to identify the corresponding parameter set (eg, for obtaining network analysis from the NWDAF 510).

[0129] For example, at 535, the IEAF 505 may map the set ID to a corresponding parameter set. That is, based on receiving the set ID from the UE 515 at the IEAF 505 via a first network analysis request (e.g., in a data collection request), the IEAF 505 may map the corresponding parameters to the received set ID. In other words, the IEAF 505 may identify the corresponding parameter set corresponding to the set ID in response to obtaining the first network analysis request (e.g., indicating the set ID). In some examples, the IEAF 505 may map the set ID to the parameters based on the SLA configuration. For example, the IEAF 505 may map a first set ID (e.g., set ID 1) to parameters associated with service experience prediction analysis, QoS monitoring analysis, and UE mobility prediction analysis. Additionally, the IEAF 505 may map a second set ID (e.g., set ID 2) to parameters associated with QoS sustainability prediction analysis, slice load prediction analysis, and data network performance prediction analysis.

[0130] In some other examples, the first network analysis request may indicate a corresponding parameter set corresponding to a set ID to request network analysis according to a corresponding operation. For example, the first network analysis request message may indicate a first parameter set corresponding to a first set ID to request analysis associated with an AI / ML model download operation, and indicate a second parameter set corresponding to a second ID to request analysis associated with an AI / ML model split operation.

[0131] In some examples, at 540, the IEAF 505 may output a second network analysis request to the NWDAF 510 (e.g., via the NAF). The second network analysis request may indicate a request for network analysis from the NWDAF 510. For example, the second network analysis request may indicate a parameter set corresponding to a set ID to request the corresponding analysis. That is, the IEAF 505 may transmit the parameters corresponding to the set ID to the NWDAF 510.

[0132] In some examples, at 545, the IEAF 505 may obtain an indication of network analysis from the NWDAF 510 (e.g., via the NAF). For example, the IEAF 505 may obtain the indication of network analysis from the NWDAF 510 in response to the second network analysis request. In some examples, the second network analysis request and the indication of network analysis (e.g., obtained in response to the second network analysis request) may be communicated between the IEAF 505 and the NWDAF 510 according to the NWDAF discovery process.

[0133] At 550, the IEAF 505 may output an indication of the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID to the UE 515. For example, the IEAF 505 may output the network analysis in response to the first network analysis request. In some examples, the IEAF 505 may output the indication of the network analysis to the UE 515 via application layer signaling. That is, the IEAF 505 may output the indication of the network analysis to the application client at the UE 515 (e.g., via the DEC at the UE 515). In some examples, outputting the network analysis to the UE 515 via application layer signaling may result in increased performance associated with application layer AI / ML operations at the UE 515, as well as other possible benefits.

[0134] Figure 6 A block diagram 600 illustrates a device 605 that supports techniques for network analysis opening from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0135] The receiver 610 may provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for performing network analysis opening from the core network of the wireless communication system). The information may be delivered to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0136] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to techniques for opening network analysis from the core network of the wireless communication system), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0137] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for network analysis exposure from a core network of a wireless communication system as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0138] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0139] Additionally or alternatively, in some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting means for performing the functions described herein), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0140] In some examples, communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0141] According to examples as disclosed herein, the communication manager 620 may support wireless communication at a first device (e.g., device 605). For example, the communication manager 620 may be configured to or otherwise support components for receiving a first message from a second device, the first message indicating a set of multiple set IDs associated with a network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set. The communication manager 620 may be configured to or otherwise support components for sending a second message to a third device, the second message indicating a request for a network analysis associated with a set ID in the set of multiple set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. The communication manager 620 may be configured to or otherwise support components for receiving a third message from the third device in response to the request, the third message indicating a network analysis associated with the corresponding operation and parameter set corresponding to the set ID.

[0142] By including or configuring a communication manager 620 according to examples as described herein, the device 605 (e.g., a processor controlling or otherwise coupled with the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) may support techniques for reducing processing and more efficiently utilizing communication resources.

[0143] Figure 7 A block diagram 700 illustrates a device 705 that supports techniques for network analysis opening from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0144] Receiver 710 may provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for opening network analysis from the core network of a wireless communication system). The information may be delivered to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0145] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to techniques for opening network analysis from the core network of the wireless communication system), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0146] Device 705 or its various components may be examples of means for performing various aspects of the techniques for opening network analysis from a core network of a wireless communication system as described herein. For example, communications manager 720 may include a set ID indicating component 725, a network analysis requesting component 730, a network analysis component 735, or any combination thereof. Communications manager 720 may be an example of aspects of communications manager 620 as described herein. In some examples, communications manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 710, transmitter 715, or both. For example, communications manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in conjunction with receiver 710, transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0147] According to examples disclosed herein, the communication manager 720 can support wireless communication at a first device (e.g., device 705). A set ID indication component 725 can be configured to or otherwise support means for receiving a first message from a second device, the first message indicating a set of multiple set IDs associated with a network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set. A network analysis request component 730 can be configured to or otherwise support means for sending a second message to a third device, the second message indicating a request for a network analysis associated with a set ID in the set of multiple set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. A network analysis component 735 can be configured to or otherwise support means for receiving a third message from the third device in response to the request, the third message indicating a network analysis associated with the corresponding operation and parameter set corresponding to the set ID.

[0148] Figure 8 Block diagram 800 illustrates a communication manager 820 that supports techniques for network analysis opening from a core network of a wireless communication system, in accordance with one or more aspects of the present disclosure. Communication manager 820 can be an example of communication manager 620, communication manager 720, or aspects of both, as described herein. Communication manager 820 or its various components can be examples of means for performing various aspects of the techniques for network analysis opening from a core network of a wireless communication system, as described herein. For example, communication manager 820 can include a set ID indicating component 825, a network analysis requesting component 830, a network analysis component 835, a parameter set indicating component 840, a UE policy component 845, or any combination thereof. Each of these components can communicate directly or indirectly with one another (e.g., via one or more buses).

[0149] According to examples disclosed herein, the communication manager 820 may support wireless communication at a first device. The set ID indication component 825 may be configured to or otherwise support components for receiving a first message from a second device, the first message indicating a set of multiple set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set. The network analysis request component 830 may be configured to or otherwise support components for sending a second message to a third device, the second message indicating a request for network analysis associated with a set ID in the set of multiple set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. The network analysis component 835 may be configured to or otherwise support components for receiving a third message from the third device in response to the request, the third message indicating a network analysis associated with the corresponding operation and parameter set corresponding to the set ID.

[0150] In some examples, to support receiving a first message, the set ID indication component 825 may be configured as or otherwise support components for receiving a first message via first application layer signaling as part of a registration process for an application supported at the first device and the second device, wherein the first message indicates a set of multiple set IDs and a corresponding operation corresponding to each set ID in the set of multiple set IDs, and wherein the set of multiple set IDs is associated with the application.

[0151] In some examples, to support sending a second message, the network analysis request component 830 may be configured to or otherwise support components for sending the second message via second application layer signaling, wherein the second message indicates a set ID such that an application layer of the protocol stack used at the first device is unaware of the correspondence between each set ID and the corresponding parameter set.

[0152] In some examples, to support receiving a first message, set ID indicating component 825 may be configured to or otherwise support means for receiving a first message via NAS layer signaling, wherein the first message indicates a set of a plurality of set IDs and a corresponding operation corresponding to each set ID in the set of the plurality of set IDs. In some examples, the first message further indicates a UE policy associated with one or more applications supported at the first device and the second device. In some examples, each set ID in the set of the plurality of set IDs is associated with a corresponding application in the one or more applications.

[0153] In some examples, to support sending a second message, parameter set indicating component 840 may be configured or otherwise support means for sending a second message via application layer signaling, where the second message indicates a respective parameter set corresponding to the set ID.

[0154] In some examples, the set ID indication component 825 may be configured to or otherwise support components for receiving a fourth message from a fourth device, the fourth message indicating a set of multiple set IDs and a corresponding parameter set corresponding to each set ID in the set of multiple set IDs, wherein sending a second message indicating the request and the corresponding parameter set is based on receiving the fourth message.

[0155] In some examples, to support receiving a fourth message, the UE policy component 845 may be configured to or otherwise support components for receiving a fourth message via NAS layer signaling, wherein the fourth message further indicates a UE policy associated with one or more applications supported at the first device and the fourth device, and wherein each set ID in the set of multiple set IDs is associated with a corresponding application in the one or more applications.

[0156] In some examples, sending a second message indicating a request for network analysis is associated with performing a corresponding operation corresponding to the set ID. In some examples, the corresponding operation corresponding to the set ID is associated with an ML model used at the first device, the second device, or both.

[0157] In some examples, the network analysis is based on a corresponding set of parameters corresponding to the set ID. In some examples, the corresponding set of parameters corresponding to the set ID is based on an SLA associated with the second device.

[0158] In some examples, the third message includes an indication to the first device of statistics or predictions corresponding to the network analysis associated with the corresponding operation.

[0159] Figure 9 A diagram illustrates a system 900 including a device 905 supporting techniques for network analysis exposure from a core network of a wireless communication system, in accordance with one or more aspects of the present disclosure. Device 905 may be an example of, or include components of, device 605, device 705, or UE 115 as described herein. Device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 905 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communications manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, memory 930, code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0160] I / O controller 910 can manage input and output signals for device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor (such as processor 940). In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0161] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, wired, or wireless links, as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets; providing the modulated packets to the one or more antennas 925 for transmission; and demodulating packets received from the one or more antennas 925. The transceiver 915, or the transceiver 915 and the one or more antennas 925, may be examples of the transmitter 615, the transmitter 715, the receiver 610, the receiver 710, or any combination thereof, or components thereof, as described herein.

[0162] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform the various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium (such as system memory) or another type of memory. In some cases, the code 935 may not be directly executable by the processor 940, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 930 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0163] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to cause the device 905 to perform various functions (e.g., various functions or tasks supporting technologies for opening network analysis from a core network of a wireless communication system). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, the processor 940 and the memory 930 being configured to perform the various functions described herein.

[0164] According to the examples disclosed herein, the communication manager 920 may support wireless communication at a first device. For example, the communication manager 920 may be configured to or otherwise support a component for receiving a first message from a second device, the first message indicating a set of multiple set IDs associated with a network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set. The communication manager 920 may be configured to or otherwise support a component for sending a second message to a third device, the second message indicating a request for a network analysis associated with a set ID in the set of multiple set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. The communication manager 920 may be configured to or otherwise support a component for receiving a third message from the third device in response to the request, the third message indicating a network analysis associated with the corresponding operation and parameter set corresponding to the set ID.

[0165] By including or configuring a communications manager 920 according to examples as described herein, the device 905 can support techniques for improving communications reliability, reducing latency, and improving utilization of processing power.

[0166] In some examples, the communication manager 920 can be configured to use or otherwise cooperate with the transceiver 915, one or more antennas 925, or any combination thereof to perform various operations (e.g., receive, monitor, transmit). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 can be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 can include instructions that can be executed by the processor 940 to cause the device 905 to perform various aspects of the techniques for network analysis opening from the core network of the wireless communication system as described herein, or the processor 940 and the memory 930 can be otherwise configured to perform or support such operations.

[0167] Figure 10 A block diagram 1000 illustrates a device 1005 that supports techniques for network analysis opening from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a network entity 105 or a core network 130 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0168] Receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0169] The transmitter 1015 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0170] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the techniques for network analysis exposure from a core network of a wireless communication system as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0171] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0172] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting means for performing the functions described herein), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0173] In some examples, communication manager 1020 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 can receive information from receiver 1010, transmit information to transmitter 1015, or be integrated with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0174] According to examples disclosed herein, the communication manager 1020 may support wireless communication at a first device (e.g., device 1005). For example, the communication manager 1020 may be configured to or otherwise support components for obtaining a first message from a second device, the first message indicating a set of multiple set IDs associated with a network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set. The communication manager 1020 may be configured to or otherwise support components for obtaining a second message from a third device, the second message indicating a request for a network analysis associated with a set ID in the set of multiple set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. The communication manager 1020 may be configured to or otherwise support components for outputting a third message to the third device in response to the request, the third message indicating a network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0175] By including or configuring a communication manager 1020 according to examples as described herein, the device 1005 (e.g., a processor controlling or otherwise coupled to the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) may support techniques for reducing processing and more efficiently utilizing communication resources.

[0176] Figure 11A block diagram 1100 illustrates a device 1105 supporting techniques for network analysis opening from a core network of a wireless communication system in accordance with one or more aspects of the present disclosure. The device 1105 may be an example of aspects of the device 1005, or the network entity 105, or the core network 130 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0177] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0178] The transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0179] Device 1105 or its various components may be examples of means for performing various aspects of the techniques for opening network analysis from a core network of a wireless communication system as described herein. For example, communications manager 1120 may include a set ID component 1125, an analysis request indication component 1130, an analysis indication component 1135, or any combination thereof. Communications manager 1120 may be an example of aspects of communications manager 1020 as described herein. In some examples, communications manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 1110, transmitter 1115, or both. For example, communications manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in conjunction with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0180] According to examples disclosed herein, a communication manager 1120 can support wireless communication at a first device (e.g., device 1105). A set ID component 1125 can be configured to or otherwise support components for obtaining a first message from a second device, the first message indicating a set of multiple set IDs associated with a network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set. An analysis request indication component 1130 can be configured to or otherwise support components for obtaining a second message from a third device, the second message indicating a request for a network analysis associated with a set ID in the set of multiple set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. An analysis indication component 1135 can be configured to or otherwise support components for outputting a third message to the third device in response to the request, the third message indicating a network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0181] Figure 12Block diagram 1200 illustrates a communications manager 1220 that supports techniques for network analysis opening from a core network of a wireless communication system, in accordance with one or more aspects of the present disclosure. Communications manager 1220 can be an example of communications manager 1020, communications manager 1120, or aspects of both, as described herein. Communications manager 1220 or its various components can be examples of means for performing various aspects of the techniques for network analysis opening from a core network of a wireless communication system, as described herein. For example, communications manager 1220 can include a set ID component 1225, an analysis request indication component 1230, an analysis indication component 1235, a parameter identification component 1240, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualized component associated with the network entity 105 or the core network 130, between devices, components, or virtualized components associated with the network entity 105 or the core network 130), or any combination thereof.

[0182] According to examples disclosed herein, communication manager 1220 can support wireless communication at a first device. Set ID component 1225 can be configured to or otherwise support components for obtaining a first message from a second device, the second message indicating a set of multiple set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set. Analysis request indication component 1230 can be configured to or otherwise support components for obtaining a second message from a third device, the second message indicating a request for network analysis associated with a set ID in the set of multiple set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. Analysis indication component 1235 can be configured to or otherwise support components for outputting a third message to the third device in response to the request, the third message indicating a network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0183] In some examples, analysis request indication component 1230 can be configured to or otherwise support means for outputting a fourth message via Naf in response to obtaining a second message indicating a request for network analysis, wherein the fourth message indicates a corresponding parameter set. In some examples, analysis indication component 1235 can be configured to or otherwise support means for obtaining a fifth message via Naf in response to outputting the fourth message, wherein the fifth message indicates network analysis, and wherein outputting the third message is based on receiving the fifth message indicating network analysis.

[0184] In some examples, to support obtaining the second message, set ID component 1225 can be configured or otherwise support means for obtaining the second message via application layer signaling, wherein the second message indicates the set ID. In some examples, to support obtaining the second message, parameter identification component 1240 can be configured or otherwise support means for identifying a corresponding parameter set corresponding to the set ID in response to obtaining the second message, wherein outputting the fourth message is based on identifying the corresponding parameter set.

[0185] In some examples, to support obtaining a second message, the analysis request indication component 1230 may be configured as or otherwise support components for obtaining a second message via application layer signaling, wherein the second message indicates a corresponding parameter set corresponding to the set ID, and wherein outputting the fourth message is based on the second message indicating the corresponding parameter set.

[0186] In some examples, the corresponding operation corresponding to the set ID is associated with an ML model used at the second device, the third device, or both. In some examples, obtaining a second message indicating a request for network analysis is associated with the corresponding operation corresponding to the set ID.

[0187] In some examples, the network analysis is based on a corresponding set of parameters corresponding to the set ID. In some examples, the corresponding set of parameters corresponding to the set ID is based on an SLA associated with the second device.

[0188] Figure 13 A diagram illustrates a system 1300 including a device 1305 supporting techniques for network analysis exposure from a core network of a wireless communication system, in accordance with one or more aspects of the present disclosure. Device 1305 may be an example of, or include components of, device 1005, device 1105, network entity 105, or core network 130 as described herein. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, including communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components that support outgoing and incoming communications, such as a communications manager 1320, a transceiver 1310, an antenna 1315, memory 1325, code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0189] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or obtain operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip assembly installed in the device 1305. In some examples, the transceiver is operable to support communications via one or more communication links (eg, communication link 125 , backhaul communication link 120 , midhaul communication link 162 , fronthaul communication link 168 ).

[0190] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may also include BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0191] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) to cause the device 1305 to perform various functions (e.g., various functions or tasks supporting technologies for opening network analysis from the core network of a wireless communication system). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, the processor 1335 and the memory 1325 being configured to perform the various functions described herein. The processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, virtual machine, or container instance)) that can host functionality (e.g., by executing code 1330) to perform the functions of the device 1305. The processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305 (such as in the memory 1325). In some implementations, the processor 1335 may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes those inputs to produce a set of outputs (which may be passed to other systems or components of the device 1305, for example). For example, the processing system of the device 1305 may refer to a system that includes various other components or subcomponents of the device 1305, such as the processor 1335, or the transceiver 1310, or the communication manager 1320, or other components or combinations of components of the device 1305. The processing system of device 1305 can be interfaced with other components of device 1305 and can process information (such as input or signals) received from other components or output information to other components. For example, the chip or modem of device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, among other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, so that device 1305 can transmit information output from the chip or modem.Additionally or alternatively, in some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1305 can obtain information or signal input and the information can be transmitted to the processing system. A person skilled in the art will readily recognize that the first interface can also obtain information or signal input, and the second interface can also output information or signal output.

[0192] In some examples, bus 1340 may support communications for protocol layers of a protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1305 or between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

[0193] In some examples, communication manager 1320 can manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 can manage the delivery of data communications to client devices, such as one or more UEs 115. In some examples, communication manager 1320 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with UEs 115 in coordination with other network entities 105. In some examples, communication manager 1320 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0194] According to examples disclosed herein, the communication manager 1320 may support wireless communication at a first device (e.g., device 1305). For example, the communication manager 1320 may be configured to or otherwise support components for obtaining a first message from a second device, the second message indicating a set of multiple set IDs associated with a network analysis of a core network of a wireless communication system, wherein each set ID in the set of multiple set IDs corresponds to a corresponding operation and a corresponding parameter set. The communication manager 1320 may be configured to or otherwise support components for obtaining a second message from a third device, the second message indicating a request for a network analysis associated with a set ID in the set of multiple set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. The communication manager 1320 may be configured to or otherwise support components for outputting a third message to the third device in response to the request, the third message indicating a network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0195] By including or configuring a communications manager 1320 according to examples as described herein, the device 1305 can support techniques for improving communications reliability, reducing latency, and improving utilization of processing power.

[0196] In some examples, the communication manager 1320 can be configured to use or otherwise cooperate with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, obtain, monitor, output, transmit). Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 can be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 can include instructions that can be executed by the processor 1335 to cause the device 1305 to perform various aspects of the techniques for performing network analysis opening from the core network of the wireless communication system as described herein, or the processor 1335 and the memory 1325 can be otherwise configured to perform or support such operations.

[0197] Figure 14 A flow chart illustrating a method 1400 for supporting techniques for opening network analysis from a core network of a wireless communication system according to one or more aspects of the present disclosure is illustrated. The operations of the method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE as described in reference to Figures 1 to 9The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0198] At 1405, the method may include: receiving a first message from a second device, the first message indicating a set of a plurality of set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of a plurality of set IDs corresponds to a corresponding operation and a corresponding parameter set. The operations of 1405 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The described set ID indicates that the component 825 executes.

[0199] At 1410, the method may include sending a second message to a third device, the second message indicating a request for network analysis associated with a set ID in the set of a plurality of set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. The operations of 1410 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a third device as described in reference to Figure 8 The described network analysis requests component 830 to execute.

[0200] At 1415, the method may include: receiving a third message from the third device in response to the request, the third message indicating a network analysis associated with a corresponding operation and a corresponding parameter set corresponding to the set ID. The operations of 1415 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed by the reference Figure 8 The described network analysis component 835 performs.

[0201] Figure 15 A flow chart illustrating a method 1500 for supporting techniques for opening network analysis from a core network of a wireless communication system according to one or more aspects of the present disclosure is illustrated. The operations of the method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE as described in reference to Figures 1 to 9 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0202] At 1505, the method may include: as part of a registration process for an application supported at the first device and the second device, receiving a first message from the second device via first application layer signaling, the first message indicating a set of a plurality of set IDs associated with network analysis of a core network of the wireless communication system, wherein the first message indicates the set of the plurality of set IDs and a respective operation corresponding to each set ID in the set of the plurality of set IDs, and wherein the set of the plurality of set IDs is associated with the application. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a method as described in reference to Figure 8 The described set ID indicates that the component 825 executes.

[0203] At 1510, the method may include sending a second message to a third device, the second message indicating a request for network analysis associated with a set ID in the set of a plurality of set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. The operations of 1510 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The described network analysis requests component 830 to execute.

[0204] At 1515, the method may include: receiving a third message from the third device in response to the request, the third message indicating a network analysis associated with a corresponding operation and a corresponding parameter set corresponding to the set ID. The operations of 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The described network analysis component 835 performs.

[0205] Figure 16 A flow chart illustrating a method 1600 for supporting techniques for opening network analysis from a core network of a wireless communication system according to one or more aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE as described in reference to Figures 1 to 9 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0206] At 1605, the method may include: receiving a first message from a second device via NAS layer signaling, the first message indicating a set of a plurality of set IDs associated with network analysis of a core network of a wireless communication system, wherein the first message indicates the set of the plurality of set IDs and a corresponding operation corresponding to each set ID in the set of the plurality of set IDs. The operations of 1605 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a method as described in reference to Figure 8 The described set ID indicates that the component 825 executes.

[0207] At 1610, the method may include sending a second message to a third device, the second message indicating a request for network analysis associated with a set ID in the set of a plurality of set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. The operations of 1610 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Figure 8 The described network analysis requests component 830 to execute.

[0208] At 1615, the method may include: receiving a third message from the third device in response to the request, the third message indicating a network analysis associated with a corresponding operation and a corresponding parameter set corresponding to the set ID. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 8 The described network analysis component 835 performs.

[0209] Figure 17 A flow chart illustrating a method 1700 for supporting techniques for network analysis opening from a core network of a wireless communication system according to one or more aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by a network entity or component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 The network entity or core network described herein performs. In some examples, the network entity or core network may execute an instruction set to control functional elements of the network entity or core network, respectively, to perform the described functions. Additionally or alternatively, the network entity or core network may use dedicated hardware to perform various aspects of the described functions.

[0210] At 1705, the method may include: obtaining a first message from a second device, the first message indicating a set of a plurality of set IDs associated with network analysis of a core network of a wireless communication system, wherein each set ID in the set of a plurality of set IDs corresponds to a corresponding operation and a corresponding parameter set. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figure 12 The described set ID component 1225 performs.

[0211] At 1710, the method may include: obtaining a second message from a third device, the second message indicating a request for network analysis associated with a set ID in a set of a plurality of set IDs, the request being based on a corresponding operation and a corresponding parameter set corresponding to the set ID. The operations of 1710 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Figure 12 The described analysis request directs component 1230 to perform.

[0212] At 1715, the method may include: outputting a third message to the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID. The operation of 1715 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1715 may be performed by the reference Figure 12 The described analysis directs component 1235 to perform.

[0213] The following provides an overview of various aspects of the disclosure:

[0214] Aspect 1: A method for wireless communication at a first device, the method comprising: receiving a first message from a second device, the first message indicating a plurality of set IDs associated with a network analysis of a core network of a wireless communication system, wherein each of the plurality of set IDs corresponds to a corresponding operation and a corresponding parameter set; sending a second message to a third device, the second message indicating a request for a network analysis associated with a set ID in the plurality of set IDs, the request being based on the corresponding operation and the corresponding parameter set corresponding to the set ID; and receiving a third message from the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0215] Aspect 2: A method according to aspect 1, wherein receiving the first message includes receiving the first message via first application layer signaling as part of a registration process for an application supported at the first device and the second device, wherein the first message indicates the multiple set IDs and the corresponding operations corresponding to each of the multiple set IDs, and wherein the multiple set IDs are associated with the application.

[0216] Aspect 3: A method according to Aspect 2, wherein sending the second message includes: sending the second message via second application layer signaling, wherein the second message indicates the set ID, so that the application layer of the protocol stack used at the first device is unaware of the correspondence between each set ID and the corresponding parameter set.

[0217] Aspect 4: The method according to aspect 1, wherein receiving the first message includes: receiving the first message via NAS layer signaling, wherein the first message indicates the multiple set IDs and the corresponding operation corresponding to each set ID in the multiple set IDs.

[0218] Aspect 5: A method according to Aspect 4, wherein the first message further indicates a UE policy associated with one or more applications supported at the first device and the second device, and each of the multiple set IDs is associated with a corresponding application in the one or more applications.

[0219] Aspect 6: The method according to any one of aspects 1, 4 and 5, wherein sending the second message comprises sending the second message via application layer signaling, wherein the second message indicates the corresponding parameter set corresponding to the set ID.

[0220] Aspect 7: According to the method according to Aspect 6, the method also includes: receiving a fourth message from a fourth device, the fourth message indicating the multiple set IDs and the corresponding parameter set corresponding to each set ID in the multiple set IDs, wherein sending the second message indicating the request and the corresponding parameter set is at least partially based on receiving the fourth message.

[0221] Aspect 8: A method according to Aspect 7, wherein receiving the fourth message includes: receiving the fourth message via NAS layer signaling, wherein the fourth message further indicates a UE policy associated with one or more applications supported at the first device and the fourth device, and wherein each of the multiple set IDs is associated with a corresponding application among the one or more applications.

[0222] Aspect 9: The method according to any one of aspects 1 to 8, wherein sending the second message indicating the request for the network analysis is associated with performing the corresponding operation corresponding to the set ID.

[0223] Aspect 10: The method according to any one of aspects 1 to 9, wherein the respective operation corresponding to the set ID is associated with an ML model used at the first device or the second device or both.

[0224] Aspect 11: The method according to any one of aspects 1 to 10, wherein the network analysis is based at least in part on the respective parameter set corresponding to the set ID.

[0225] Aspect 12: The method of any one of aspects 1 to 11, wherein the respective set of parameters corresponding to the set ID is based at least in part on an SLA associated with the second device.

[0226] Aspect 12: The method of any one of aspects 1 to 11, wherein the third message includes an indication to the first device of statistics or predictions corresponding to the network analysis associated with the corresponding operation.

[0227] Aspect 13: A method for performing wireless communication at a first device, the method comprising: obtaining a first message from a second device, the first message indicating a plurality of set IDs associated with a network analysis of a core network of a wireless communication system, wherein each set ID in the plurality of set IDs corresponds to a corresponding operation and a corresponding parameter set; obtaining a second message from a third device, the second message indicating a request for a network analysis associated with a set ID in the plurality of set IDs, the request being based on the corresponding operation and the corresponding parameter set corresponding to the set ID; and outputting a third message to the third device in response to the request, the third message indicating the network analysis associated with the corresponding operation and the corresponding parameter set corresponding to the set ID.

[0228] Aspect 14: The method according to Aspect 13 further includes: outputting a fourth message via Naf in response to obtaining the second message indicating the request for the network analysis, wherein the fourth message indicates the corresponding parameter set; and obtaining a fifth message via Naf in response to outputting the fourth message, wherein the fifth message indicates the network analysis, and wherein outputting the third message is at least partially based on receiving the fifth message indicating the network analysis.

[0229] Aspect 15: A method according to Aspect 14, wherein obtaining the second message includes: obtaining the second message via application layer signaling, wherein the second message indicates the set ID; and identifying the corresponding parameter set corresponding to the set ID in response to obtaining the second message, wherein outputting the fourth message is at least partially based on identifying the corresponding parameter set.

[0230] Aspect 16: A method according to Aspect 14, wherein obtaining the second message includes: obtaining the second message via application layer signaling, wherein the second message indicates the corresponding parameter set corresponding to the set ID, and wherein outputting the fourth message is at least partially based on the second message indicating the corresponding parameter set.

[0231] Aspect 17: The method according to any one of Aspects 13 to 16, wherein the respective operation corresponding to the set ID is associated with an ML model used at the second device or the third device or both.

[0232] Aspect 18: The method according to any one of aspects 13 to 17, wherein obtaining the second message indicating the request for network analysis is associated with the corresponding operation corresponding to the set ID.

[0233] Aspect 19: The method according to any one of aspects 13 to 18, wherein the network analysis is based at least in part on the respective parameter set corresponding to the set ID.

[0234] Aspect 20: The method according to any one of aspects 13 to 19, wherein the respective set of parameters corresponding to the set ID is based at least in part on an SLA associated with the second device.

[0235] Aspect 21: An apparatus for wireless communication at a first device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 12.

[0236] Aspect 22: An apparatus for wireless communication at a first device, the apparatus comprising at least one means for performing the method according to any one of aspects 1 to 12.

[0237] Aspect 23: A non-transitory computer-readable medium storing code for wireless communication at a first device, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 12.

[0238] Aspect 24: An apparatus for wireless communication at a first device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 13 to 20.

[0239] Aspect 25: An apparatus for wireless communication at a first device, the apparatus comprising at least one means for performing the method according to any one of aspects 13 to 20.

[0240] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication at a first device, the code comprising instructions executable by a processor to perform the method according to any one of aspects 13 to 20.

[0241] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects of two or more of these methods may be combined.

[0242] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used throughout much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0243] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0244] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0245] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. Features that implement the functions may also be physically located at different locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0246] Computer-readable medium includes both non-transient computer storage media and communication media, and it includes any medium that promotes a computer program to be transferred from one location to another location.Non-transient storage medium can be any available medium that can be accessed by a general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by a general or special-purpose computer or a general or special-purpose processor in the form of an instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and optical disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc. Magnetic disk can reproduce data magnetically, and optical disc can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0247] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so 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). Moreover, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0248] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database, or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Furthermore, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0249] In the drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number to distinguish between similar components. If only the first reference number is used in the specification, the description applies to any of the similar components having the same first reference number, regardless of the second or subsequent reference numbers.

[0250] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The detailed description includes specific details to provide an understanding of the described technology. However, these technologies may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0251] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a first device, the apparatus comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a first message from a second device, the first message indicating a plurality of set identifiers associated with a network analysis of a core network of a wireless communication system, wherein each set identifier of the plurality of set identifiers corresponds to a respective operation and a respective set of parameters; sending a second message to a third device, the second message indicating a request for network analysis associated with a set identifier from the plurality of set identifiers, the request being in accordance with the corresponding operation and the corresponding parameter set corresponding to the set identifier; as well as A third message is received from the third device in response to the request, the third message indicating the network analysis associated with the respective operation and the respective parameter set corresponding to the set identifier.

2. The apparatus of claim 1 , wherein the instructions to receive the first message are executable by the processor to cause the apparatus to: As part of a registration process for an application supported at the first device and the second device, the first message is received via first application layer signaling, wherein the first message indicates the multiple set identifiers and the corresponding operation corresponding to each of the multiple set identifiers, and wherein the multiple set identifiers are associated with the application.

3. The apparatus of claim 2, wherein the instructions to send the second message are executable by the processor to cause the apparatus to: The second message is sent via second application layer signaling, wherein the second message indicates the set identifier so that an application layer of a protocol stack used at the first device is unaware of a correspondence between each set identifier and the corresponding parameter set.

4. The apparatus of claim 1 , wherein the instructions to receive the first message are executable by the processor to cause the apparatus to: The first message is received via non-access stratum layer signaling, wherein the first message indicates the plurality of set identifiers and the respective operation corresponding to each of the plurality of set identifiers.

5. The device according to claim 4, wherein: The first message further indicates a UE policy associated with one or more applications supported at the first device and the second device, and Each set identifier of the plurality of set identifiers is associated with a corresponding application of the one or more applications.

6. The apparatus of claim 1 , wherein the instructions to send the second message are executable by the processor to cause the apparatus to: The second message is sent via application layer signaling, wherein the second message indicates the corresponding parameter set corresponding to the set identifier.

7. The apparatus of claim 6, wherein the instructions are further executable by the processor to cause the apparatus to: A fourth message is received from a fourth device, the fourth message indicating the plurality of set identifiers and the corresponding parameter set corresponding to each of the plurality of set identifiers, wherein sending the second message indicating the request and the corresponding parameter set is based at least in part on receiving the fourth message.

8. The apparatus of claim 7, wherein the instructions to receive the fourth message are executable by the processor to cause the apparatus to: The fourth message is received via non-access stratum layer signaling, wherein the fourth message further indicates a UE policy associated with one or more applications supported at the first device and the fourth device, and wherein each of the multiple set identifiers is associated with a corresponding application in the one or more applications.

9. The apparatus of claim 1, wherein sending the second message indicating the request for the network analysis is associated with performing the corresponding operation corresponding to the set identifier.

10. The apparatus of claim 1, wherein the respective operation corresponding to the set identifier is associated with a machine learning model used at the first device or the second device or both.

11. The apparatus of claim 1, wherein the network analysis is based at least in part on the respective parameter sets corresponding to the set identifier.

12. The apparatus of claim 1, wherein the respective set of parameters corresponding to the set identifier is based at least in part on a service level agreement associated with the second device.

13. The apparatus of claim 1, wherein the third message comprises an indication to the first device of statistics or predictions corresponding to the network analysis associated with the corresponding operation.

14. An apparatus for wireless communication at a first device, the apparatus comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: obtaining, from a second device, a first message indicating a plurality of set identifiers associated with a network analysis of a core network of a wireless communication system, wherein each set identifier of the plurality of set identifiers corresponds to a respective operation and a respective set of parameters; obtaining, from a third device, a second message indicating a request for network analysis associated with a set identifier from the plurality of set identifiers, the request being in accordance with the corresponding operation and the corresponding set of parameters corresponding to the set identifier; as well as A third message is output to the third device in response to the request, the third message indicating the network analysis associated with the respective operation and the respective parameter set corresponding to the set identifier.

15. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: outputting, via a network application function, a fourth message in response to obtaining the second message indicating the request for the network analysis, wherein the fourth message indicates the corresponding parameter set; and A fifth message is obtained via the network application function in response to outputting the fourth message, wherein the fifth message indicates the network analysis, and wherein outputting the third message is based at least in part on receiving the fifth message indicating the network analysis.

16. The apparatus of claim 15, wherein the instructions to obtain the second message are executable by the processor to cause the apparatus to: obtaining the second message via application layer signaling, wherein the second message indicates the set identifier; and The corresponding parameter set corresponding to the set identifier is identified in response to obtaining the second message, wherein outputting the fourth message is based at least in part on identifying the corresponding parameter set.

17. The apparatus of claim 15, wherein the instructions to obtain the second message are executable by the processor to cause the apparatus to: The second message is obtained via application layer signaling, wherein the second message indicates the corresponding parameter set corresponding to the set identifier, and wherein outputting the fourth message is based at least in part on the second message indicating the corresponding parameter set.

18. The apparatus of claim 14, wherein the respective operation corresponding to the set identifier is associated with a machine learning model used at the second device or the third device or both.

19. The apparatus of claim 14, wherein obtaining the second message indicating the request for network analysis is associated with the respective operation corresponding to the set identifier.

20. The apparatus of claim 14, wherein the network analysis is based at least in part on the respective set of parameters corresponding to the set identifier.

21. The apparatus of claim 14, wherein the respective set of parameters corresponding to the set identifier is based at least in part on a service level agreement associated with the second device.

22. A method for wireless communication at a first device, the method comprising: receiving a first message from a second device, the first message indicating a plurality of set identifiers associated with a network analysis of a core network of a wireless communication system, wherein each set identifier of the plurality of set identifiers corresponds to a respective operation and a respective set of parameters; sending a second message to a third device, the second message indicating a request for network analysis associated with a set identifier from the plurality of set identifiers, the request being in accordance with the corresponding operation and the corresponding parameter set corresponding to the set identifier; as well as A third message is received from the third device in response to the request, the third message indicating the network analysis associated with the respective operation and the respective parameter set corresponding to the set identifier.

23. The method of claim 22, wherein receiving the first message comprises: As part of a registration process for an application supported at the first device and the second device, the first message is received via first application layer signaling, wherein the first message indicates the multiple set identifiers and the corresponding operation corresponding to each of the multiple set identifiers, and wherein the multiple set identifiers are associated with the application.

24. The method of claim 23, wherein sending the second message comprises: The second message is sent via second application layer signaling, wherein the second message indicates the set identifier so that an application layer of a protocol stack used at the first device is unaware of a correspondence between each set identifier and the corresponding parameter set.

25. The method of claim 22, wherein receiving the first message comprises: The first message is received via non-access stratum layer signaling, wherein the first message indicates the plurality of set identifiers and the respective operation corresponding to each of the plurality of set identifiers.

26. The method of claim 22, wherein sending the second message comprises: The second message is sent via application layer signaling, wherein the second message indicates the corresponding parameter set corresponding to the set identifier.

27. The method according to claim 26, further comprising: A fourth message is received from a fourth device, the fourth message indicating the plurality of set identifiers and the corresponding parameter set corresponding to each of the plurality of set identifiers, wherein sending the second message indicating the request and the corresponding parameter set is based at least in part on receiving the fourth message.

28. A method for wireless communication at a first device, the method comprising: obtaining, from a second device, a first message indicating a plurality of set identifiers associated with a network analysis of a core network of a wireless communication system, wherein each set identifier of the plurality of set identifiers corresponds to a respective operation and a respective set of parameters; obtaining, from a third device, a second message indicating a request for network analysis associated with a set identifier from the plurality of set identifiers, the request being in accordance with the corresponding operation and the corresponding set of parameters corresponding to the set identifier; as well as A third message is output to the third device in response to the request, the third message indicating the network analysis associated with the respective operation and the respective parameter set corresponding to the set identifier.

29. The method according to claim 28, further comprising: outputting, via a network application function, a fourth message in response to obtaining the second message indicating the request for the network analysis, wherein the fourth message indicates the corresponding parameter set; and A fifth message is obtained via the network application function in response to outputting the fourth message, wherein the fifth message indicates the network analysis, and wherein outputting the third message is based at least in part on receiving the fifth message indicating the network analysis.

30. The method of claim 29, wherein obtaining the second message comprises: obtaining the second message via application layer signaling, wherein the second message indicates the set identifier; as well as The corresponding parameter set corresponding to the set identifier is identified in response to obtaining the second message, wherein outputting the fourth message is based at least in part on identifying the corresponding parameter set.

Images