Apparatus and method for signaling activation of UE-level measurement jobs

Abstract

Apparatuses and methods for signaling activation of UE level measurement jobs are provided herein. An apparatus includes an interface circuit and a processor circuit coupled to the interface circuit. The processor circuitry is to: decode a tracking job creation request received from a service consumer via the interface circuitry to create a tracking job for collecting UE-level measurements in the communication network; in response to the trace job creation request, encoding a trace session activation request for activating a trace session for transmission to the UDM; decoding a tracking session activation response which is received from the UDM and responds to the tracking session activation request, wherein the tracking session activation response is used for indicating an activation result of the tracking session; and in response to the tracking session activation response, encoding a tracking job creation response for transmission to the service consumer via the interface circuitry, the tracking job creation response indicating a creation result of the tracking job. Other embodiments may be described and / or claimed.

Description

[0001] Priority Statement

[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 620,707, filed on January 12, 2024, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD

[0003] Embodiments of the present disclosure generally relate to wireless communication, and more particularly, to apparatuses and methods for signaling activation of user equipment (UE)-level measurement operations. BACKGROUND ART

[0004] Artificial intelligence (AI) / machine learning (ML) technologies and related applications are being adopted by an increasing number of industries and have proven to be successful. Currently, these technologies are being applied to the telecommunications industry, including mobile networks. Although AI / ML technologies are generally quite mature, certain related aspects of these technologies are still evolving, and new complementary technologies are emerging. SUMMARY OF THE INVENTION

[0005] One aspect of the present disclosure provides an apparatus, including: an interface circuit; and a processor circuit coupled to the interface circuit, wherein the processor circuit is configured to: decode a tracking job creation request received from a service consumer via the interface circuit to create a tracking job for collecting user equipment (UE)-level measurement results in a communication network; encode a tracking session activation request for activating a tracking session in response to the tracking job creation request for transmission to a unified data management (UDM); decode a tracking session activation response received from the UDM in response to the tracking session activation request, the tracking session activation response being for indicating an activation result of the tracking session; and encode a tracking job creation response in response to the tracking session activation response for transmission to the service consumer via the interface circuit, the tracking job creation response being for indicating a creation result of the tracking job.

[0006] One aspect of the present disclosure provides an apparatus, including: a memory; and a processor circuit coupled to the memory, wherein the processor circuit is configured to: decode a first message received from a first network function (NF) or a first next-generation (NG) radio access network (RAN) node to activate a tracking session for a user equipment (UE)-level measurement operation, the first message carrying UE-level measurement configuration parameters; and initiate the tracking session, and wherein the memory is configured to store the UE-level measurement configuration parameters. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In the accompanying drawings, embodiments of the present disclosure will be illustrated by way of example and not limitation, where like reference numerals refer to like elements.

[0008] Figure 1 An example architecture of a system according to some embodiments of the present disclosure is shown.

[0009] Figure 2 An example network architecture according to some embodiments of the present disclosure is shown.

[0010] Figure 3 A flowchart of a method for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0011] Figure 4 A flowchart of a method for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0012] Figure 5 A flowchart of a method for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0013] Figure 6 A flowchart of a method for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0014] Figure 7 A flowchart of a method for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0015] Figure 8 A flowchart of a method for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0016] Figure 9 A flowchart of a method for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0017] Figure 10 A flowchart of a method for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0018] Figure 11 An example process for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0019] Figure 12 An example process for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0020] Figure 13 An example process for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure is shown.

[0021] Figure 14 Illustrates an example process for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure.

[0022] Figure 15 Illustrates an example process for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure.

[0023] Figure 16 Illustrates an example process for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure.

[0024] Figure 17 Illustrates an example process for signaling to activate UE-level measurement operations according to some embodiments of the present disclosure.

[0025] Figure 18 Illustrates an example process for signaling to deactivate UE-level measurement operations according to some embodiments of the present disclosure.

[0026] Figure 19 Illustrates an example process for signaling to deactivate UE-level measurement operations according to some embodiments of the present disclosure.

[0027] Figure 20 Depicts an example functional framework for ML and / or RAN intelligence.

[0028] Figure 21 Depicts an example AI / ML-assisted communication network including communication between two MLFs.

[0029] Figure 22 Illustrates a network according to various embodiments.

[0030] Figure 23 Schematically illustrates a wireless network according to various embodiments.

[0031] Figure 24 The block diagram of... illustrates components that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methods discussed herein according to some example embodiments.

[0032] Figure 25 Illustrates a network according to various embodiments. Detailed Description

[0033] The various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of the present disclosure to others skilled in the art. However, it will be readily apparent to those skilled in the art that many alternative embodiments can be practiced using portions of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be readily apparent to those skilled in the art that alternative embodiments can be practiced without these specific details. In other instances, well-known features are omitted or simplified in order to avoid obscuring the illustrative embodiments.

[0034] In addition, the various operations will be described as multiple discrete operations in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as implying that these operations must be order-dependent. In particular, these operations need not be performed in the order presented.

[0035] The phrases "in an embodiment," "in one embodiment," and "in some embodiments" are used repeatedly herein. This phrase generally does not refer to the same embodiment; however, it may. Unless the context dictates otherwise, the terms "comprising," "having," and "including" are synonyms. The phrases "A, B, or C" and "A / B / C" mean "(A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C)."

[0036] The present disclosure generally relates to wireless communication, cellular networks, cloud computing, edge computing, data centers, network topologies, communication system implementations, network convergence, artificial intelligence (AI) / machine learning (ML) technologies, and more particularly to techniques for signaling activation and deactivation of UE-level measurement operations.

[0037] Figure 1 An example architecture of a system 100 in accordance with some embodiments of the present disclosure is shown. The following description is provided with respect to an example system 100 operating in conjunction with the Long-Term Evolution (LTE) system standard and 5G or New Radio (NR) system standard provided by the 3GPP Technical Specification (TS). However, the example embodiments are not limited in this regard, and the described embodiments can be applied to other networks that would benefit from the principles described herein, such as future 3GPP systems (e.g., Sixth Generation (6G)) systems, Institute of Electrical and Electronics Engineers (IEEE) 802.16 protocols (e.g., Wireless Metropolitan Area Network (MAN), Worldwide Interoperability for Microwave Access (WiMAX), etc.).

[0038] As Figure 1As shown, system 100 may include UEs 101a and 101b (collectively referred to as "(one or more) UEs 101"). As used herein, the term "user equipment" or "UE" may refer to a device with radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio device, reconfigurable radio device, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface. In this example, UE 101 is shown as a smart phone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronic devices, cellular phones, smart phones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI) systems, in-vehicle entertainment (ICE) devices, instrument clusters (ICs), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashboard mobile devices (DMEs), mobile data terminals (MDTs), electronic engine management systems (EEMSs), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMSs), networked or "smart" devices, machine type communication (MTC) devices, machine-to-machine (M2M), Internet of Things (IoT) devices, and / or the like.

[0039] In some embodiments, any one of UEs 101 may include an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a PLMN, proximity-based services (ProSe), or device-to-device (D2D) communication, a sensor network, or an IoT network. The data exchange of M2M or MTC may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-term connections. The IoT UE may execute background applications (e.g., maintaining active messages, status updates, etc.) to facilitate the connection to the IoT network.

[0040] The UE 101 may be configured to connect to (e.g., communicatively couple with) the RAN 110. In an embodiment, the RAN 110 may be a Next Generation (NG) RAN or 5G RAN, an evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), or a legacy RAN such as UTRAN (UMTS Terrestrial Radio Access Network) or GERAN (GSM (Global System for Mobile Communications or Groupe Spécial Mobile) EDGE (GSM Evolution) Radio Access Network). As used herein, the term “NGRAN” etc. may refer to the RAN 110 operating in an NR or 5G system 100, and the term “E-UTRAN” etc. may refer to the RAN 110 operating in an LTE or 4G system 100. The UE 101 utilizes connections (or channels) 103 and 104 respectively, each connection including a physical communication interface or layer (discussed further below). As used herein, the term “channel” may refer to any tangible or intangible transmission medium for conveying data or a data stream. The term “channel” may be synonymous and / or equivalent to “communication channel”, “data communication channel”, “transmission channel”, “data transmission channel”, “access channel”, “data access channel”, “link”, “data link”, “carrier”, “radio frequency carrier”, and / or any other similar term representing a path or medium through which data is conveyed. Additionally, the term “link” may refer to a connection between two devices for the purpose of sending and receiving information via a Radio Access Technology (RAT).

[0041] In this example, the connections 103 and 104 are shown as air interfaces to enable communication coupling and may be consistent with a cellular communication protocol such as the Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Push-to-Talk over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long Term Evolution (LTE) protocol, Fifth Generation (5G) protocol, New Radio (NR) protocol, and / or any other communication protocol discussed herein. In an embodiment, the UE 101 may directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface 105 and may include one or more logical channels including, but not limited to, a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0042] UE 101b is shown as being configured to access an access point (AP) 106 (also referred to as "WLAN node 106", "WLAN 106", "WLAN terminal 106", or "WT 106", etc.) via connection 107. Connection 107 may include a local wireless connection, such as a connection compliant with any IEEE 802.11 protocol, where AP 106 will include a Wi-Fi router. In this example, AP 106 is shown as being connected to the Internet and not connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 101b, RAN 110, and AP 106 may be configured to utilize LTE-WLAN aggregation (LWA) operations and / or WLAN LTE / WLAN radio-level integration with IPsec tunnels (LWIP) operations. LWA operations may involve UE 101b in RRC_CONNECTED being configured by RAN node 111 to utilize radio resources of LTE and WLAN. LWIP operations may involve UE 101b using WLAN radio resources (e.g., connection 107) via an Internet Protocol Security (IPsec) protocol tunnel to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) sent over connection 107. The IPsec tunnel may include encapsulating the entire original IP packet and adding a new packet header, thus protecting the original header of the IP packet.

[0043] RAN 110 may include one or more RAN nodes 111a and 111b (collectively referred to as "(one or more) RAN nodes 111") that enable connections 103 and 104. As used herein, terms such as "access node (AN)", "access point", "RAN node", etc. may describe a device that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as base stations (BSs), next-generation Node Bs (gNBs), RAN nodes, evolved Node Bs (eNBs), Node Bs, roadside units (RSUs), transmission reception points (TRxP or TRP), etc., and may include terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, terms such as "NGRAN node" etc. may refer to a RAN node 111 (e.g., gNB) operating in an NR or 5G system 100, and terms such as "E-UTRAN node" etc. may refer to a RAN node 111 (e.g., eNB) operating in an LTE or 4G system 100. According to various embodiments, the RAN node 111 may be implemented as one or more dedicated physical devices such as macrocell base stations and / or low-power (LP) base stations such as femtocells, picocells, or other similar cells that provide a smaller coverage area, a smaller user capacity, or a higher bandwidth compared to macrocells.

[0044] In some embodiments, all or part of the RAN node 111 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a cloud radio access network (CRAN) and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN function partitioning, such as: PDCP partitioning, where the RRC and PDCP layers are operated by the CRAN / vBBUP, and other layer 2 (L2) protocol entities are operated by individual RAN nodes 111; MAC / PHY partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 111; or "lower PHY" partitioning, where the RRC, PDCP, RLC, MAC layers, and the upper part of the PHY layer are operated by the CRAN / vBBUP, and the lower part of the PHY layer is operated by individual RAN nodes 111. This virtualization framework allows the processor cores of the RAN node 111 to be freed up to execute other virtualized applications. In some implementations, individual RAN nodes 111 may represent via individual F1 interfaces ( Figure 1Individual gNB-DUs (not shown) connected to the gNB-CU. In these implementations, the gNB-DU may include one or more remote radio heads or radio front-end modules (RFEMs), and the gNB-CU may be operated by a server (not shown) located in the RAN 110 or by a pool of servers in a manner similar to CRAN / vBBUP. Additionally or alternatively, one or more RAN nodes 111 may be next-generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol termination to the UE 101 and are connected to the 5GC via the NG interface.

[0045] In a V2X scenario, one or more RAN nodes 111 may be or act as RSUs. The term "roadside unit" or "RSU" may refer to any transportation infrastructure entity for V2X communication. The RSU may be implemented in or by a suitable RAN node or a fixed (or relatively stationary) UE, where the RSU implemented in or by a UE may be referred to as a "UE-type RSU", the RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", the RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", etc. In one example, the RSU is a computing device coupled to a radio frequency circuit located by the roadside, which provides connectivity support for passing vehicle UEs 101 (vUE 101). The RSU may also include an internal data storage circuit for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate in the 5.9 GHz direct short-range communication (DSRC) frequency band to provide very low-latency communication required for high-speed events, such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may operate in the cellular V2X frequency band to provide the above-mentioned low-latency communication and other cellular communication services. Additionally or alternatively, the RSU may operate as a WiFi hotspot (2.4 GHz frequency band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communication. The (one or more) computing devices and some or all of the radio frequency circuits of the RSU may be encapsulated in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired (e.g., Ethernet) connection to a traffic signal controller and / or a backhaul network.

[0046] Any RAN node 111 can terminate the air interface protocol and can be the first point of contact for the UE 101. In some embodiments, any RAN node 111 can fulfill various logical functions of the RAN 110, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0047] In an embodiment, the UE 101 can be configured to communicate with each other or with any RAN node 111 via multi-carrier communication channels using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication technologies, such as but not limited to orthogonal frequency division multiple access (OFDMA) communication technologies (e.g., for downlink communication) or single carrier frequency division multiple access (SC-FDMA) communication technologies (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited to this aspect. The OFDM signal can include a plurality of orthogonal sub-carriers.

[0048] In some embodiments, a downlink resource grid can be used for downlink transmission from any RAN node 111 to the UE 101, and uplink transmission can use a similar technique. The grid can be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is the physical resource in the downlink for each time slot. Such a time-frequency plane representation is a common practice in OFDM systems, which makes radio resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM sub-carrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is denoted as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this can represent the smallest amount of resources that can be currently allocated. There are several different physical downlink channels transmitted using such resource blocks.

[0049] According to various embodiments, the UE 101 and the RAN node 111 transmit (e.g., send and receive) data via a licensed medium (also referred to as "licensed spectrum" and / or "licensed band") and an unlicensed shared medium (also referred to as "unlicensed spectrum" and / or "unlicensed band"). The licensed spectrum can include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum can include the 5 GHz band.

[0050] To operate in unlicensed spectrum, the UE 101 and the RAN node 111 may operate using Licensed-Assisted Access (LAA), Enhanced LAA (eLAA), and / or Further eLAA (feLAA) mechanisms. In these implementations, the UE 101 and the RAN node 111 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to the Listen-Before-Talk (LBT) protocol.

[0051] LBT is a mechanism where a device (e.g., UE 101, RAN nodes 111, 112, etc.) senses the medium (e.g., a channel or a carrier frequency) and transmits when the medium is sensed idle (or when a particular channel in the medium is sensed unoccupied). The medium sensing operation may include Clear Channel Assessment (CCA) which determines whether there are other signals on the channel using at least Energy Detection (ED) to determine whether the channel is occupied or idle. This LBT mechanism allows the cellular / LAA network to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks. ED may include sensing RF energy on the intended transmission band for a period of time and comparing the sensed RF energy with a predefined or configured threshold.

[0052] Typically, incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism called Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA). Here, when a WLAN node (e.g., a mobile station (MS) such as UE 101, AP 106) intends to transmit, the WLAN node may first perform CCA before transmitting. Additionally, a backoff mechanism is used to avoid collisions in the case where more than one WLAN node senses the channel as idle and transmits simultaneously. The backoff mechanism may be a counter randomly drawn within the contention window size (CWS) which exponentially increases upon occurrence of a collision and is reset to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some implementations, the LBT process for DL or UL transmission bursts respectively including PDSCH or PUSCH transmissions may have an LAA contention window of variable length between X and Y Extended CCA (ECCA) slots, where X and Y are the minimum and maximum values of the CWS for LAA. In one example, the minimum CWS for LAA transmission may be 9 microseconds (μs); however, the size of the CWS and the Maximum Channel Occupancy Time (MCOT) (e.g., the transmission burst) may be based on government regulatory requirements.

[0053] The LAA mechanism is based on the Carrier Aggregation (CA) technology of the Long Term Evolution - Advanced (LTE - Advanced) system. In CA, each aggregated carrier is called a Component Carrier (CC). A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated. Thus, the maximum aggregated bandwidth is 100 MHz. In a Frequency Division Duplex (FDD) system, the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, an individual CC can have a different bandwidth from other CCs. In a Time Division Duplex (TDD) system, for DL and UL, the number of CCs and the bandwidth of each CC are usually the same.

[0054] CA also includes separate serving cells to provide separate CCs. The coverage of serving cells may vary. For example, CCs on different frequency bands will experience different path losses. The Primary Serving Cell or Primary Cell (PCell) can provide the Primary Component Carrier (PCC) for both UL and DL, and can handle Radio Resource Control (RRC) and Non - Access Stratum (NAS) related activities. Other serving cells are called Secondary Cells (SCells), and each SCell can provide a separate Secondary Component Carrier (SCC) for both UL and DL. SCCs can be added and removed as needed, while changing the PCC may require the UE 101 to undergo a handover. In LAA, eLAA, and feLAA, some or all SCells can operate in the unlicensed spectrum (referred to as "LAA SCell"), and the LAA SCell is assisted by the PCell operating in the licensed spectrum. When the UE is configured with more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells, and the UL grants indicate the starting positions of different Physical Uplink Shared Channels (PUSCH) within the same subframe.

[0055] The Physical Downlink Shared Channel (PDSCH) can carry user data and higher - layer signaling to the UE 101. The Physical Downlink Control Channel (PDCCH) can carry information such as the transmission format and resource allocation related to the PDSCH channel. It can also notify the UE 101 of the transmission format, resource allocation, and Hybrid Automatic Repeat Request (H - ARQ) information related to the uplink shared channel. Generally, downlink scheduling (allocating control and shared channel resource blocks to the UE 101b within the cell) can be performed at any RAN node 111 based on the channel quality information fed back from any UE 101. The downlink resource allocation information can be sent on the PDCCH for each UE 101 (e.g., allocated to).

[0056] The PDCCH can use control channel elements (CCEs) to convey control information. Before mapping to resource elements, the complex-valued symbols of the PDCCH can first be organized into quadruples, and then a sub-block interleaver can be used to permute them for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine groups of four physical resource elements called resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. One or more CCEs can be used to transmit the PDCCH, depending on the size of the downlink control information (DCI) and the channel conditions. In LTE, four or more different PDCCH formats (e.g., aggregation levels, L = 1, 2, 4, or 8) with different numbers of CCEs can be defined.

[0057] Some embodiments can use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments can use an enhanced physical downlink control channel (EPDCCH), which uses PDSCH resources for control information transmission. One or more enhanced control channel elements (ECCEs) can be used to transmit the EPDCCH. Similar to above, each ECCE can correspond to nine groups of four physical resource elements called enhanced resource element groups (EREGs). In some cases, an ECCE may have a different number of EREGs.

[0058] RAN nodes 111 can be configured to communicate with each other via interface 112. In an embodiment where system 100 is an LTE system, interface 112 can be an X2 interface 112. The X2 interface can be defined between two or more RAN nodes 111 (e.g., two or more eNBs, etc.) connected to the EPC 120 and / or between two eNBs connected to the EPC 120. In some implementations, the X2 interface can include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U can provide a flow control mechanism for user data packets transmitted through the X2 interface and can be used to convey information about user data transfer between eNBs. For example, the X2-U can provide specific sequence number information for user data transmitted from the master eNB (MeNB) to the secondary eNB (SeNB); information about the successful sequential transmission of PDCP PDUs for user data from the SeNB to the UE 101; information about PDCP PDUs not delivered to the UE 101; information about the current minimum required buffer size at the SeNB for transmitting user data to the UE; and so on. The X2-C can provide access mobility functions within LTE, including context transfer from the source eNB to the target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0059] In an embodiment where system 100 is a 5G or NR system, interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to 5GC 120, between a RAN node 111 (e.g., gNB) connected to 5GC 120 and an eNB, and / or between two eNBs connected to 5GC 120. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide unguaranteed transfer of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide: management and error handling functions; functions for managing the Xn-C interface; mobility support for UEs 101 in the connected mode (e.g., CM-CONNECTED), including functions for managing UE mobility in the connected mode between one or more RAN nodes 111. Mobility support may include context transfer from an old (source) serving RAN node 111 to a new (target) serving RAN node 111; and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (target) serving RAN node 111. The protocol stack of the Xn-U may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer on top of the (one or more) UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn application protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be located on top of the IP layer and may provide guaranteed transfer of application layer messages. In the transport IP layer, point-to-point transmission is used to transfer signaling PDUs. In other implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the (one or more) user plane and / or control plane protocol stacks shown and described herein.

[0060] RAN 110 is shown communicatively coupled to a core network - in this embodiment, the core network (CN) 120. CN 120 may include a plurality of network elements 122, which are configured to provide various data and telecommunications services to consumers / subscribers (e.g., users of UE 101) connected to CN 120 via RAN 110. The term "network element" may describe a physical or virtualized device for providing wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as the following: networked computers, network hardware, network devices, routers, switches, hubs, bridges, radio network controllers, radio access network devices, gateways, servers, virtualized network functions (VNFs), network function virtualization infrastructure (NFVI), and / or the like. Components of CN 120 may be implemented in one physical node or separate physical nodes, including components that read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, network function virtualization (NFV) may be used to virtualize any or all of the above network node functions (described in further detail below) via executable instructions stored in one or more computer-readable storage media. The logical instantiation of CN 120 may be referred to as a network slice, and the logical instantiation of a part of CN 120 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions, or to execute from dedicated hardware onto physical resources including a combination of industry standard server hardware, storage hardware, or switches. In other words, an NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0061] Generally, application server 130 may be an element that provides an application that uses IP bearer resources in conjunction with a core network (e.g., UMTS packet service (PS) domain, LTE PS data service, etc.). Application server 130 may also be configured to support one or more communication services (e.g., Internet protocol voice (VoIP) sessions, PTT sessions, group communication sessions, social network services, etc.) for UE 101 via EPC 120.

[0062] In an embodiment, CN 120 may be a 5GC (referred to as "5GC 120", etc.), and RAN 110 may be connected to CN 120 via an NG interface 113. In an embodiment, NG interface 113 may be divided into two parts: an NG user plane (NG-U) interface 114, which carries traffic data between RAN node 111 and the user plane function (UPF); and an S1 control plane (NG-C) interface 115, which is a signaling interface between RAN node 111 and the AMF.

[0063] In an embodiment, CN 120 may be a 5G CN (referred to as "5GC 120", etc.), while in other embodiments, CN 120 may be an evolved packet core (EPC). In the case where CN 120 is an EPC (referred to as "EPC 120", etc.), RAN 110 may be connected to CN 120 via the S1 interface 113. In an embodiment, the S1 interface 13 may be divided into two parts: the S1 user plane (S1-U) interface 114, which carries traffic data between the RAN node 111 and the serving gateway (S-GW); and the S1-mobility management entity (MME) interface 115, which is a signaling interface between the RAN node 111 and the MME.

[0064] Figure 2 FIG. 200 shows an example network architecture 200 according to some embodiments of the present disclosure. Network 200 may operate in a manner consistent with the 3GPP technical specifications of an LTE or 5G / NR system. However, the example embodiments are not limited in this regard, and the examples may be applicable to other networks that benefit from the principles described herein, such as future 3GPP systems or similar systems.

[0065] Network 200 includes a UE 202, which is any mobile or non-mobile computing device designed to communicate with a RAN 204 via an air interface. UE 202 is communicatively coupled to RAN 204 via a Uu interface, which is applicable to both LTE and NR systems. Examples of UE 202 include, but are not limited to, smartphones, tablets, wearable devices (e.g., smartwatches, fitness trackers, smart glasses, smart clothing / fabric, head-mounted displays, smart programs, and / or similar devices), desktop computers, workstations, laptops, in-vehicle infotainment systems, in-vehicle entertainment systems, dashboards, head-up display (HUD) devices, on-vehicle diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, connected home appliances, machine-type communication devices, machine-to-machine (M2M), device-to-device (D2D), machine-type communication (MTC) devices, Internet of Things (IoT) devices, smart home appliances, flying drones or unmanned aerial vehicles (UAVs), ground drones or autonomous vehicles, robots, electronic signage, single-board computers (SBCs) (e.g., Raspberry Pi, Arduino, Intel Edison, etc.), plug-in computers, and / or any type of computing device (e.g., any type of computing device discussed herein).

[0066] Network 200 may include a set of UEs 202 that are directly coupled to each other via D2D, ProSe, PC5, and / or sidelink (SL) interfaces and / or any other suitable interfaces (such as any interfaces discussed herein). In a 3GPP system, SL communication involves communication between two or more UEs 202 using 3GPP technologies without traversing a network node. These UEs 202 may be M2M / D2D / MTC / IoT devices and / or vehicle-mounted systems that communicate using an SL interface, such as including: one or more SL logical channels (e.g., sidelink broadcast control channel (SBCCH), sidelink control channel (SCCH), and sidelink traffic channel (STCH)); one or more SL transport channels (e.g., sidelink shared channel (SL-SCH) and sidelink broadcast channel (SL-BCH)); and one or more SL physical channels (e.g., physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), physical sidelink feedback channel (PSFCH), physical sidelink broadcast channel (PSBCH), and / or similar channels). The UE 202 may perform blind decoding attempts on the SL channel / link according to various examples herein.

[0067] In some examples, the UE 202 may also communicate with the AP 206 via an over-the-air (OTA) connection. The AP 206 manages a WLAN connection, which can be used to offload some / all of the network traffic of the RAN 204. The connection between the UE 202 and the AP 206 may comply with any IEEE 802.11 protocol. In addition, the UE 202, RAN 204, and AP 206 may utilize cellular-WLAN aggregation / integration (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve the RAN 204 configuring the UE 202 to utilize cellular radio resources and WLAN resources simultaneously.

[0068] The RAN 204 includes one or more network access nodes (NANs) 214. The NAN 214 terminates the air interface of the UE 202 by providing access layer protocols (including RRC, PDCP, RLC, MAC, and PHY / L1 protocols). In this way, the NAN 214 can establish a data / voice connection between the CN 240 and the UE 202. The NAN 214 may be: a macrocell base station; or a low-power base station for providing femtocells, picocells, or other similar cells, which have a smaller coverage area, a smaller user capacity, or a higher bandwidth compared to the macrocell; or a combination thereof. In these implementations, the NAN 214 is referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRP, etc.

[0069] One example implementation is the "CU / DU separation" architecture, where NAN 214 is embodied as a gNB - Central Unit (CU) communicatively coupled to one or more gNB - Distributed Units (DUs), and each DU can be communicatively coupled to one or more Radio Units (RUs) (also referred to as RRHs, RRUs, etc.). In some implementations, one or more RUs can be individual RSU. In some implementations, the CU / DU separation can include an ng - eNB - CU and one or more ng - eNB - DUs instead of gNB - CU and gNB - DU, or can be supplementary to gNB - CU and gNB - DU. NAN 214 used as the CU can be implemented in a discrete device or as one or more software entities running on a server computer, e.g., as part of a virtual network including a virtual baseband unit (BBU) or BBU pool, Cloud RAN (CRAN), Radio Equipment Controller (REC), Radio Cloud Center (RCC), Centralized RAN (C - RAN), Virtualized RAN (vRAN), etc. (although these terms may refer to different implementation concepts). Any other type of architecture, arrangement, and / or configuration can also be used.

[0070] If RAN 204 is an LTE RAN or an Evolved Universal Terrestrial Radio Access Network (E - UTRAN) 210, a set of NAN214 are interconnected through the corresponding X2 interface; or if RAN 204 is an NG - RAN 214, a set of NAN 214 are interconnected through the corresponding Xn interface. In some examples, the X2 / Xn interface can be divided into control / user plane interfaces, which can allow ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0071] The NAN 214 of RAN 204 can each manage one or more cells, cell groups, member carriers, etc., to provide an air interface for UE 202 to access the network. UE 202 can be simultaneously connected to a set of cells provided by the same or different NAN 214 of RAN 204. For example, UE 202 and RAN 204 can use carrier aggregation to allow UE 202 to be connected to a set of member carriers, each member carrier corresponding to a PCell or an SCell. In a dual - connection scenario, the first NAN 214 can be the master node providing the MCG, and the second NAN 214 can be the secondary node providing the SCG. The first / second NAN 214 can be any combination of eNB, gNB, ng - eNB, etc.

[0072] The RAN 204 can provide an air interface through licensed spectrum or unlicensed spectrum. To operate in unlicensed spectrum, a node can use LAA, eLAA, and / or feLAA mechanisms based on the CA technology with the PCell / Scell. Before accessing the unlicensed spectrum, a node can perform medium / carrier sensing operations according to, for example, the listen-before-talk (LBT) protocol.

[0073] Additionally or alternatively, the individual UE 202 provides radio information to one or more NANs 214 and / or one or more edge computing nodes (e.g., edge servers / hosts, etc.). The radio information can be in the form of one or more measurement reports and / or can include, for example, signal strength measurement information, signal quality measurement information, and / or similar measurement information. Each measurement report is tagged with a timestamp and a measurement location (e.g., the current location of the UE 202). As an example, the measurement information collected by the UE 202 and / or the measurement information included in the measurement reports can include one or more of the following: bandwidth (BW), network or cell load, latency, jitter, round-trip time (RTT), number of interruptions, out-of-order delivery of packets, transmission power, bit error rate, bit error ratio (BER), block error rate (BLER), packet error rate (PER), packet loss rate, packet reception rate (PRR), data rate, peak data rate, end-to-end (e2e) latency, signal-to-noise ratio (SNR), signal-to-interference-plus-noise ratio (SINR), signal-plus-noise-plus-distortion to signal-plus-distortion (SINAD) ratio, carrier-to-interference-plus-noise ratio (CINR), additive white Gaussian noise (AWGN), energy per bit to noise power density ratio (Eb / N0), energy per chip to interference power density ratio (Ec / I0), energy per chip to noise power density ratio (Ec / N0), peak-to-average power ratio (PAPR), reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RSSI), received channel power indicator (RCPI), received signal noise indicator (RSNI), received signal code power (RSCP), average noise plus interference (ANPI), GNSS cell frame timing for UE positioning in E-UTRAN or 5G / NR (e.g., the timing between the AP 206 or RAN node 208 reference time and the GNSS-specific reference time of a given GNSS), GNSS code measurements (e.g., the GNSS code phase (integer part and fractional part) of the propagation code of the i-th GNSS satellite signal), GNSS carrier phase measurements (e.g., the number of carrier phase cycles (integer part and fractional part) of the i-th GNSS satellite signal measured since the signal was locked; also known as accumulated delta range (ADR)), channel interference measurements, thermal noise power measurements, received interference power measurements, power histogram measurements, channel load measurements, STA statistics, and / or other similar measurements.RSRP, RSSI, and / or RSRQ measurements may include RSRP, RSSI, and / or RSRQ measurements of cell-specific reference signals, channel state information reference signals (CSI-RS), and / or synchronization signals (SS) or SS blocks of a 3GPP network (e.g., LTE or 5G / NR), as well as RSRP, RSSI, RSRQ, RCPI, RSNI, and / or ANPI measurements of various beacons, fast initial link setup (FILS) discovery frames, or probe response frames for a WLAN / WiFi (e.g., [IEEE80211]) network. Additionally or alternatively, other measurement methods may be used, such as those discussed in 3GPP TS 36.214 v17.0.0 (2022-03-31) (“[TS36214]”), 3GPP TS 38.215 v17.3.0 (2023-03-30) (“[TS38215]”), 3GPP TS 38.314 v17.3.0 (2023-06-30) (“[TS38314]”), [IEEE80211], etc. Additionally or alternatively, one or more NAN 214s may collect any of the above measurements (or combinations of measurements) and provide them to the edge computing node(s).

[0074] Additionally or alternatively, the measurements may include one or more of the following measurements: measurements related to a data radio bearer (DRB) (e.g., the number of DRBs attempted to be established, the number of successfully established DRBs, the number of active DRBs released, the in-session activity time of the DRB, the number of DRBs attempted to be resumed, the number of successfully resumed DRBs, etc.); measurements related to radio resource control (RRC) (e.g., the average number of RRC connections, the maximum number of RRC connections, the average number of stored inactive RRC connections, the maximum number of stored inactive RRC connections, the number of attempted, successful, and / or failed RRC connection establishments, etc.); measurements related to UE context (UECNTX); measurements related to radio resource utilization (RRU) (e.g., total DL PRB usage, total UL PRB usage, the distribution of total DL PRB usage, the distribution of total UL PRB usage, DL PRBs for data traffic, UL PRBs for data traffic, total available DL PRBs, total available UL PRBs, etc.); measurements related to registration management (RM); measurements related to session management (SM) (e.g., the number of PDU sessions requested to be established; the number of successfully established PDU sessions; the number of PDU sessions with setup failures, etc.); measurements related to GTP management (GTP); measurements related to IP management (IP); measurements related to policy association (PA); measurements related to mobility management (MM) (e.g., for inter-RAT, intra-RAT, and / or intra-frequency / inter-frequency handovers and / or conditional handovers: the number of handover preparations requested, successful, and / or failed; the number of handover resource allocations requested, successful, and / or failed; the number of handover executions requested, successful, and / or failed; the average and / or longest time for requested handover executions; the number of successful and / or failed handover executions per beam pair, etc.); measurements related to (one or more) virtualized resources (VR); measurements related to carrier (CARR); measurements related to QoS flow (QF) (e.g., the number of active QoS flows released, the number of QoS flows attempted to be released, the session activity time of the QoS flow, the session activity time of UE202, the number of QoS flows attempted to be established, the number of successfully established QoS flows, the number of QoS flows with establishment failures, the number of initial QoS flows attempted to be established, the number of successfully established initial QoS flows, the number of initial QoS flows with establishment failures, the number of QoS flows attempted to be modified, the number of successfully modified QoS flows, the number of QoS flows with modification failures, etc.); measurements related to application trigger (AT); measurements related to short message service (SMS); measurements related to power, energy, and environment (PEE); measurements related to NF service (NFS); measurements related to packet flow description (PFD); measurements related to random access channel (RACH); measurements related to measurement report (MR);Measurements related to Layer 1 Measurement (L1M); Measurements related to Network Slice Selection (NSS); Measurements related to Paging (PAG); Measurements related to Non-IP Data Delivery (NIDD); Measurements related to External Parameter Provision (EPP); Measurements related to Traffic Impact (TI); Measurements related to Connection Establishment (CE); Measurements related to Service Parameter Provision (SPP); Measurements related to Background Data Transfer Policy (BDTP); Measurements related to Data Management (DM); and / or any other performance measurements, such as those discussed in 3GPP TS 28.552 v18.3.0 (2023-06-27) (“[TS28552]”), 3GPP TS 32.425 v17.1.0 (2021-06-24) (“[TS32425]”), and / or similar documents.;

[0075] Radio information may be reported in response to trigger events and / or periodically. Additionally or alternatively, an individual UE 202 may report radio information and / or other information regarding data transmission with low periodicity or high periodicity according to the data transmission to be performed. Additionally or alternatively, one or more edge computing nodes may request measurement results from the NAN 214 with low periodicity or high periodicity, or the NAN 214 may provide measurement results to one or more edge computing nodes with low periodicity or high periodicity. Additionally or alternatively, one or more edge computing nodes may also obtain other relevant data, such as key performance indicators (KPIs), from one or more other edge computing nodes, core network functions (NFs), application functions (AFs), and / or other UEs 202, and these data may be obtained together with the measurement report or separately from the measurement report.

[0076] Additionally or alternatively, in the case of differences in the observed data from one or more UEs, one or more RAN nodes, and / or core network NFs (e.g., missing reports, data errors, etc.), simple extrapolation may be performed to supplement the obtained observed data, such as replacing values in previously reported and / or historical data, applying extrapolation filters, etc. Additionally or alternatively, an acceptable range of the observed data may be predetermined or configured. For example, CQI and MCS measurements may be configured to be only within the ranges defined by the appropriate 3GPP standards. In the case where the reported data value is meaningless (e.g., the value exceeds the acceptable range / boundary, etc.), the current learning / training set or such values over time may be discarded. For example, a packet transfer delay boundary may be defined or configured, and packets determined to be received after the packet transfer delay boundary may be discarded.

[0077] The UE 202 can also perform procedures for determining reference signal (RS) measurements and reports to provide the network with information about the quality of one or more wireless channels and / or the general communication medium, and this information can be used to optimize various aspects of the communication system. As an example, the measurement and reporting procedures performed by the UE 202 can include the measurement and reporting procedures discussed in the following documents: 3GPP TS 38.211 v17.5.0 (2023-06-26) (“[TS38211]”), 3GPP TS 38.212 v17.5.0 (2023-03-30) (“[TS38212]”), 3GPP TS 38.213 v17.6.0 (2023-06-26) (“[TS38213]”), 3GPP TS 38.214 v17.6.0 (2023-06-26) (“[TS38214]”), [TS38215], 3GPP TS 38.101-1 v18.2.0 (2023-06-30) (“[TS38101-1]”), 3GPP TS 38.104 v18.2.0 (2023-06-30) (“[TS38104]”), 3GPP TS 38.133 v18.2.0 (2023-06-30) (“[TS38133]”), [TS38331], etc. Physical signals and / or reference signals can include demodulation reference signals (DM-RS), phase-tracking reference signals (PT-RS), positioning reference signals (PRS), channel state information reference signals (CSI-RS), synchronization signal blocks (SSB), primary synchronization signals (PSS), secondary synchronization signals (SSS), sounding reference signals (SRS), etc.

[0078] In any of the examples discussed herein, any suitable data collection and / or measurement mechanism(s) can be used to collect the observed data. For example, data tagging (e.g., sequence numbers, etc.), packet tracking, signal measurement, data sampling, and / or timestamp techniques can be used to determine any of the above metrics / observed data. Data collection can be based on events that trigger data collection. Additionally or alternatively, data collection can also occur at the start or end of an event. Data collection can be continuous, discontinuous, and / or have start and stop times. The data collection techniques / mechanisms can be specific to the HW configuration / implementation or not specific to the HW and can also be based on various software parameters (e.g., OS type and version, etc.). Various configurations can be used to define any of the above data collection parameters. Such configurations can be defined by suitable specifications / standards, such as 3GPP (e.g., [5GEdge]), ETSI (e.g., [MEC]), O-RAN (e.g., [O-RAN]), Smart Edge Open (formerly OpenNESS) (e.g., [ISEO]), IETF (e.g., MAMS [RFC8743]), IEEE / WiFi (e.g., [IEEE80211], [WiMAX], [IEEE16090], etc.) and / or any other similar standards discussed herein.

[0079] In a V2X scenario, the UE 202 or the NAN 214 can be or act as a roadside unit (RSU), and the RSU can refer to any traffic infrastructure entity for V2X communication. The RSU can be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. The RSU implemented in or by a UE can be referred to as a "UE-type RSU"; the RSU implemented in or by an eNB can be referred to as an "eNB-type RSU"; the RSU implemented in or by a gNB can be referred to as a "gNB-type RSU"; and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located by the roadside, which can provide connection support for passing vehicle UEs. The RSU can also include an internal data storage circuit for storing intersection map geometries, traffic statistics, media, and applications / software for sensing and controlling current vehicle and pedestrian traffic. The RSU can provide extremely low-latency communication required for high-speed events, such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU can also provide other cellular / WLAN communication services. The components of the RSU can be encapsulated in a weatherproof enclosure suitable for outdoor installation and can include a network interface controller for providing a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network. Furthermore, one or more V2X RATs can be employed, which allow V2X nodes to communicate directly with each other, with infrastructure devices (e.g., NAN 214), and / or other devices / nodes. In some embodiments, at least two different V2X RATs can be used, including a WLAN V2X (W-V2X) RAT based on IEEE V2X technology (e.g., DSRC in the United States and ITS-G5 in Europe) and a cellular V2X (C-V2X) RAT based on 3GPP V2X technology (e.g., LTE V2X, 5G / NR V2X, etc.). In one example, the C-V2X RAT can use a C-V2X air interface, and the WLAN V2X RAT can use a W-V2X air interface.

[0080] The W-V2X RATs include, for example: IEEE "Wireless Access in Vehicular Environments (WAVE) Architecture Guidelines", IEEE Standards Association, IEEE 1609.0-2019 (April 10, 2019) ("[IEEE16090]"); "V2X Communication Message Set Dictionary", SAE INT'L (July 23, 2020) ("[J2735_202007]"); 5 GHz band Intelligent Transportation Systems (ITS-G5), [IEEE80211] (which is the Layer 1 (L1) and Layer 2 (L2) part of WAVE, DSRC, and ITS-G5); and / or IEEE Broadband Wireless Access System Air Interface Standard, IEEE Std 802.16-2017, pages 1-2726 (March 2, 2018) ("[WiMAX]"). The term "DSRC" refers to vehicle communication in the 5.9 GHz band commonly used in the United States, while "ITS-G5" refers to vehicle communication in the 5.9 GHz band used in Europe. Due to the applicability to any number of different RATs (including the [IEEE80211] RAT) that can be used in any geographical or political region, the terms "DSRC" (used in the United States among other regions) and "ITS-G5" (used in Europe among other regions) are used interchangeably in this disclosure. ETSI EN 302 663 V1.3.1 (2020-01) (hereinafter referred to as "[EN302663]") outlines the access layer of the ITS-G5 interface and describes the access layer of the ITS-S reference architecture. The ITS-G5 access layer includes [IEEE80211], as well as the functions of the distributed congestion control (DCC) method discussed in ETSI TS102 687 V1.2.1 (2018-04) (hereinafter referred to as "[TS102687]"). The access layer of the (one or more) 3GPP LTE-V2X-based interfaces is outlined in documents such as ETSI EN 303 613 V1.1.1 (2020-01), 3GPP TS23.285 v16.2.0 (2019-12); the 3GPP 5G / NR-V2X is outlined in documents such as 3GPP TR23.786 v16.1.0 (2019-06) and 3GPP TS23.287 v18.0.0 (March 31, 2023) ("[TS23287]").

[0081] In an example where RAN 204 is an E-UTRAN 210 with one or more eNBs 212, the E-UTRAN 210 provides an LTE air interface (Uu) whose parameters and characteristics are at least the same as those discussed in 3GPP TS 36.300 v17.2.0 (2022-09-30) (“[TS36300]”). In an example where RAN 204 is a next-generation (NG)-RAN 214 with a set of gNBs 216, each gNB 216 is connected to a 5G-capable UE 202 using a 5G-NR air interface (also referred to as the Uu interface), whose parameters and characteristics are discussed in [TS38300] and many other 3GPP standards. When the NG-RAN 214 includes a set of ng-eNBs 218, one or more ng-eNBs 218 are connected to the UE 202 via a 5G Uu and / or LTE Uu interface. The gNBs 216 and ng-eNBs 218 are connected to the 5GC 240 via corresponding NG interfaces (including the N2 interface, the N3 interface, and / or other interfaces). The gNBs 216 and ng-eNBs 218 are interconnected via the Xn interface. In addition, individual gNBs 216 are interconnected via corresponding Xn interfaces, and individual ng-eNBs 218 are interconnected via corresponding Xn interfaces. In some examples, the NG interface can be divided into two parts. One part is the NG user plane (NG-U) interface, which is used to transmit traffic data (e.g., the N3 interface) between NG-RAN 214 nodes and the UPF 248; the other part is the NG control plane (NG-C) interface, which is a signaling interface between NG-RAN 214 nodes and the AMF 244 (e.g., the N2 interface).

[0082] The NG-RAN 214 can provide a 5G-NR air interface (also referred to as the Uu interface) with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar codes, repetition codes, simplex codes, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface can rely on CSI-RS, PDSCH / PDCCH DMRS, which is similar to the LTE air interface. The 5G-NR air interface may not use CRS, but can: use PBCH DMRS for PBCH demodulation; use PTRS for phase tracking of PDSCH; use a tracking reference signal for time tracking. The 5G-NR air interface can operate in the FR1 band including frequencies below 6 GHz or in the FR2 band including frequencies from 24.25 GHz to 52.6 GHz. The 5G-NR air interface can include an SSB, which is an area in the downlink resource grid that includes PSS / SSS / PBCH.

[0083] The 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of the SCS. For example, UE 202 can be configured with multiple BWPs, where each BWP configuration has a different SCS. When a BWP change is indicated to UE 202, the transmitted SCS also changes. Another use case of BWPs is related to energy saving. In particular, multiple BWPs with different numbers of frequency resources (e.g., PRBs) can be configured for UE 202 to support data transmission in different traffic load scenarios. The BWP with fewer PRBs can be used for data transmission in low traffic load situations, while allowing power consumption savings at UE 202 and in some cases at gNB 216. The BWP with more PRBs can be used for scenarios with higher traffic loads.

[0084] In some implementations, an individual gNB 216 can include a gNB-CU and a set of gNB-DUs. Additionally or alternatively, gNB 216 can include one or more RUs. In these implementations, the gNB-CU can be connected to each gNB-DU via a corresponding F1 interface. In the case of network sharing with multiple cell ID broadcasts, each cell identity associated with a PLMN subset corresponds to a gNB-DU and its connected gNB-CU, sharing the same physical layer cell resources. To improve resilience, a gNB-DU can be connected to multiple gNB-CUs through appropriate implementations. Additionally, the gNB-CU can be divided into gNB-CU control plane (gNB-CU-CP) functions and gNB-CU user plane (gNB-CU-UP) functions. The gNB-CU-CP is connected to the gNB-DU via the F1 control plane interface (F1-C), the gNB-CU-UP is connected to the gNB-DU via the F1 user plane interface (F1-U), and the gNB-CU-UP is connected to the gNB-CU-CP via the E1 interface. In some implementations, one gNB-DU is only connected to one gNB-CU-CP, and one gNB-CU-UP is only connected to one gNB-CU-CP. To improve resilience, a gNB-DU and / or gNB-CU-UP can be connected to multiple gNB-CU-CPs through appropriate implementations. Under the control of the same gNB-CU-CP, one gNB-DU can be connected to multiple gNB-CU-UPs, and under the control of the same gNB-CU-CP, one gNB-CU-UP can be connected to multiple DUs. Xn-U can support data forwarding between gNB-CU-UPs during handovers within the gNB-CU-CP inside the gNB.

[0085] Similarly, an individual ng-eNB 218 may include an ng-eNB-CU and a set of ng-eNB-DUs. In these implementations, the ng-eNB-CU and each ng-eNB-DU are interconnected via corresponding W1 interfaces. The ng-eNB may include an ng-eNB-CU-CP, one or more ng-eNB-CU-UPs, and one or more ng-eNB-DUs. The ng-eNB-CU-CP and the ng-eNB-CU-UP are connected via an E1 interface. The ng-eNB-DU is connected to the ng-eNB-CU-CP via a W1-C interface and to the ng-eNB-CU-UP via a W1-U interface. Unless otherwise explicitly specified, the general principles described herein with respect to the gNB side also apply to the ng-eNB side and the corresponding E1 and W1 interfaces.

[0086] The node hosting the user plane part of the PDCP protocol layer (e.g., gNB-CU, gNB-CU-UP, and for EN-DC, MeNB or SgNB, depending on the bearer separation situation) performs user inactivity monitoring and further notifies its inactivity or (re)activation to the node having a control plane connection to the core network (e.g., via E1, X2, etc.). The node hosting the RLC protocol layer (e.g., gNB-DU) may perform user inactivity monitoring and further notify its inactivity or (re)activation to the node hosting the control plane (e.g., gNB-CU or gNB-CU-CP).

[0087] In these implementations, the NG-RAN 214 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN 214 architecture (e.g., NG-RAN logical nodes and the interfaces between them) is part of the RNL. For each NG-RAN interface (e.g., NG, Xn, F1, etc.), the relevant TNL protocols and functions are specified. The TNL provides services for user plane transmission and / or signaling transmission. In an NG-Flex configuration, each NG-RAN node is connected to all AMFs 244 in the AMF set within the AMF area that supports at least one slice also supported by the NG-RAN node. The AMF set and the AMF area are defined in [TS23501].

[0088] RAN 204 is communicatively coupled to CN 240, which includes network elements and / or network functions (NFs) for providing various functions to support the provision of data and telecommunications services to consumers / subscribers (e.g., UE 202). The components of CN 240 may be implemented in one physical node or separate physical nodes. In some examples, NFV may be utilized to virtualize any or all of the functions provided by the network elements of CN 240 onto physical computing / storage resources in servers, switches, etc. The logical instantiation of CN 240 may be referred to as a network slice, and a partial logical instantiation of CN 240 may be referred to as a network sub-slice.

[0089] In Figure 2 the example, CN 240 is 5GC 240, which includes an authentication server function (AUSF) 242, an access and mobility management function (AMF) 244, a session management function (SMF) 246, a user plane function (UPF) 248, a network slice selection function (NSSF) 250, a network exposure function (NEF) 252, a network repository function (NRF) 254, a policy control function (PCF) 256, a unified data management (UDM) 258, a unified data repository (UDR), an application function (AF) 260, and a network data analytics function (NWDAF) 262, which are coupled to each other through various interfaces as shown in the figure. The NFs in 5GC 240 are briefly introduced below.

[0090] NWDAF 262 is an NF capable of collecting data from: UE 202; (one or more) other NFs in 5GC 240 (e.g., AMF 244, SMF 246, UPF 248, PCF 256, UDM 258, network slice admission control function (NSACF), AF 260 (directly and / or through NEF 252)); operations, administration, and maintenance (OAM) entities / functions; external AF 260; DN 236; (one or more) servers 238; cloud computing services; edge computing nodes; and / or edge networks and / or other entities / elements available for analysis.

[0091] The NWDAF 262 includes one or more of the following functions: supporting data collection from the NF and the AF 260; supporting data collection from the OAM; registering for NWDAF services and exposing metadata to the NF and the AF 260; supporting the provision of analysis information to the NF and the AF 260; supporting ML model training and provision to (one or more) NWDAF 262 (e.g., those NWDAF that include analytical logic functions). Some or all of the NWDAF functions may be supported in a single instance of the NWDAF 262. The NWDAF 262 also includes an analytical reporting function, which includes means for allowing the discovery of types of analysis consumable by external parties and / or requesting the consumption of analysis information generated by the NWDAF 262. The NWDAF 262 may collect data from (one or more) NF and / or other entities / components / functions through an Nnf service-based interface associated with (one or more) NF and / or other entities / components / functions. The NWDAF 262 and the NF providing the data belong to the same PLMN. The Nnf interface is defined for the NWDAF 262 to request subscriptions for data transfer for a specific context, unsubscribe from data transfer, and request a specific data report for a specific context. The 5GS architecture also allows the NWDAF 262 to retrieve management data from the OAM entity by invoking the OAM service.

[0092] The NWDAF 262 interacts with different entities for different purposes, such as one or more of the following: data collection based on event subscriptions provided by the AMF 244, SMF 246, PCF 256, UDM 258, NSACF, AF 260 (directly or through the NEF 252), and the OAM; analysis and data collection using the DCCF 263; retrieving information from a data repository (e.g., subscriber-related information retrieved from the UDR 259 via the UDM 258); location information data collection from the LCS system; information storage and retrieval from the ADRF 266; analysis and data collection from the MFAF 265; retrieving information about the NF (e.g., NF-related information retrieved from the NRF 254); providing analysis on demand to consumers in accordance with Article 6 of [TS23288]; providing bulk data related to (one or more) analysis IDs; providing accuracy information related to (one or more) analysis IDs; and / or providing ML model accuracy information and / or ML model accuracy degradation related to one or more ML models. Articles 6.3.13 of [TS23501] and 5.2 of [TS23288] discuss the NWDAF discovery and selection process.

[0093] A single instance or multiple instances of NWDAF 262 can be deployed in a PLMN. If multiple instances of NWDAF 262 are deployed, the architecture supports deploying NWDAF 262 as a central NF, a distributed NF set, or a combination of both. If multiple instances of NWDAF 262 are deployed, NWDAF 262 can act as an aggregation point (e.g., aggregator NWDAF 262) and collect analysis information from other NWDAF 262 (which may have different service areas) to generate aggregated analysis (e.g., based on each analysis ID), possibly including analysis generated by itself. When there are multiple NWDAF 262, not all NWDAF 262 need to be able to provide the same type of analysis results. For example, some NWDAF 262 can specialize in providing certain types of analysis.

[0094] The analysis ID information element (IE) is used to identify the types of supported analysis that NWDAF 262 can generate. In some implementations, one or more NWDAF instances 262 can be collocated with another 5GS NF.

[0095] There may be different NWDAF instances 262 in 5GC 240, with specialization for each analysis type (and / or each analysis ID). The NWDAF configuration file stored in NRF 254 describes the functions of NWDAF instances 262, which will be described in more detail below. In a multi-NWDAF deployment scenario, NWDAF instances 262 can specialize in providing analysis for one or more analysis IDs. Each NWDAF instance 262 can serve a certain area of interest, one or more tracking area identities (TAI), one or more service areas, one or more registration areas, one or more DN names (DNN), one or more local DNNs, one or more DN access IDs (DNAI), and / or some other predefined or configured area / region, service, application, or other entity / element. Multiple NWDAF 262 can jointly serve one or more specific analysis IDs. NWDAF 262 may be capable of supporting the aggregation of analysis data received from other NWDAF 262 (e.g., based on each analysis ID), and may also have its own generated analysis data.

[0096] The NWDAF 262 may include an Analytics Logic Function (AnLF) 262a and / or a Model Training Logic Function (MTLF) 262b. The NWDAF 262 may include only the MTLF 262b, only the AnLF 262a, or both. The 5GS architecture allows an NWDAF that includes the AnLF 262a (referred to herein as "NWDAF-ANLF AnLF 262a", etc.) to use a trained ML model from the same or a different NWDAF that includes the MTLF 262b (also referred to herein as "NWDAF MTLF 262b") to provide services. The NWDAF-AnLF 262a uses the Nnwdaf interface to request and subscribe to the trained ML model provision service provided by the NWDAF-MTLF 262b. The Nnwdaf_MLModelProvision service provided by the NWDAF 262 enables an NF service consumer (NFc) to receive a notification (e.g., see clause 7.5 of [TS23288]) when an ML model that matches the subscription parameters in the NWDAF-MTLF 262b is available. The NWDAF 262 provides the Nnwdaf_MLModelInfo service, which enables the NFc to request and obtain ML model information from the NWDAF-MTLF 262b (e.g., see clause 7.6 of [TS23288]). The AnLF 262a is a logic function in the NWDAF 262 that is used to perform inference, derive analysis information (e.g., derive statistics, inference, and / or predictions according to an analysis consumer request), and expose analysis services (e.g., Nnwdaf_AnalyticsSubscription or Nnwdaf_AnalyticsInfo). In some implementations, the AnLF 262a is an AI / ML inference function included in the NWDAF 262. In various implementations, the AnLF 262a can be modeled by the NRM for AI / ML inference management discussed herein. The analysis information can be statistical information about past events or predictive information (e.g., generating predictions / inferences using one or more AI / ML models, etc.). The MTLF 262b is a logic function in the NWDAF 262 that is used to train AI / ML models and expose new training services (e.g., provide trained ML models), as defined in clauses 7.5 and 7.6 of [TS23288].

[0097] To ensure the accuracy of the analysis output for an analysis ID, based on the UE abnormal behavior analysis (including the abnormal UE list and the observed time window) from itself and / or other NWDAF 262, the NWDAF 262 will detect and may delete the input data from the (one or more) abnormal UEs 202, and then may generate a new ML model and / or analysis output for the analysis ID without the input data related to the abnormal UE list during the unobserved time window, and then send / update the ML model information and / or analysis output to the subscribed NWDAF service consumers.

[0098] To support the NF in discovering and selecting the NWDAF-MTLF 262b, NWDAF-AnLF 262a, or both, that can provide the required services (e.g., analysis exposure, AI / ML services (e.g., MLT, ML model provisioning, model testing, etc.), sensing services, communication services, and / or any other service(s) including any service discussed herein) for the required analysis types, when registering with the NRF 254, in addition to the other NRF registration elements of the NF profile, each NWDAF instance 262 shall provide a list of the supported analysis ID(s), which may be based on each supported service (e.g., AI / ML service, analysis exposure / service, sensing service, and / or any other service(s) including any service discussed herein). An NF that needs to discover a NWDAF instance 262 (which supports some specific service(s) for a specific type of analysis) can query the NRF 254 to obtain the NWDAF 262 that supports the required service(s) and the required analysis ID(s).

[0099] Since multiple NWDAF 262 instances may be deployed in the network, the NFc can use the NRF 254 to discover the (one or more) NWDAF 262 instances, unless the NWDAF information can be obtained in other ways (e.g., locally configured on the NFcs). If supported, the NFc can make additional queries to the UDM 258. The NWDAF selection function in the NFc selects the NWDAF instance 262 (or NWDAF-MTLF instance 262b and / or NWDAF-AnLF instance 262a) based on the available NWDAF 262 instances, the list of supported (one or more) analysis IDs stored / from the NRF 254 (e.g., possibly per supported service), the NWDAF capabilities (e.g., analysis aggregation capability, analysis metadata provisioning capability, ML model training capability, ML model deployment capability, etc.) and / or other NRF 254 registration elements of the NF profile. 3GPP TS23.288 (“[TS23288]”) defines other and / or alternative aspects of the NWDAF262 function.

[0100] The AUSF 242 stores the data used to authenticate the UE 202 and processes the authentication-related functions. The AUSF 242 can facilitate a common authentication framework for various access types.

[0101] The AMF 244 allows other functions of the 5GC 240 to communicate with the UE 202 and the RAN 204, and subscribes to notifications about UE 202 mobility events. The AMF 244 is also responsible for registration management (e.g., registering the UE 202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 244 provides transmission for SM messages between the UE 202 and the SMF 246 and acts as a transparent proxy for routing SM messages. The AMF 244 also provides transmission for SMS messages between the UE 202 and the SMSF. The AMF 244 interacts with the AUSF 242 and the UE 202 to perform various security anchoring and context management functions. In addition, the AMF 244 is the termination point of the RAN-CP interface, which includes the N2 reference point between the RAN 204 and the AMF 244. The AMF 244 is also the termination point of the NAS (N1) signaling and performs NAS encryption and integrity protection.

[0102] The AMF 244 also supports NAS signaling between the UE 202 via the N3IWF interface. The N3IWF allows access to untrusted entities. The N3IWF can be the termination point of the N2 interface for the control plane between the (R)AN 204 and the AMF 244, or the termination point of the N3 reference point for the user plane between the (R)AN 204 and 248. Therefore, the AMF 244 processes N2 signaling for PDU sessions and QoS from the SMF 246 and the AMF 244, encapsulates / decapsulates packets for IPSec and N3 tunnels, marks N3 user plane packets in the UL, and enforces QoS corresponding to the N3 packet marking, taking into account the QoS requirements related to such marking received via N2. The N3IWF can also relay UL and DL control plane NAS signaling between the UE 202 and the AMF 244 via the N1 reference point between the UE 202 and the AMF 244, and relay UL and DL user plane packets between the UE 202 and the UPF 248. The N3IWF also provides a mechanism to establish an IPsec tunnel with the UE 202. The AMF 244 can expose Namf service-based interfaces and can be the termination point of the N14 reference point between two AMF 244s and the N17 reference point between the AMF 244 and the 5G-EIR ( Figure 2 not shown). In addition to the functions of the AMF 244 described herein, the AMF 244 can also provide support for network slice restrictions and network slice instance restrictions based on NWDAF analysis.

[0103] The SMF 246 is responsible for: SM (e.g., session establishment, tunnel management between the UPF 248 and the NAN 214); UE IP address allocation and management (including optional authorization); selection and control of the UPF function; configuring traffic steering at the UPF 248 to route traffic to the appropriate destination; terminating the interface towards the policy control function; controlling partial policy enforcement, charging, and QoS; lawful interception (for SM events and the interface with the LI system); terminating the SM part of the NAS message; DL data notification; initiating AN-specific SM information and sending it to the NAN 214 via the AMF 244 over N2; and determining the SSC mode of the session. SM refers to the management of the PDU session, and the PDU session or "session" refers to the PDU connection service that provides or enables the PDU exchange between the UE 202 and the DN 236. The SMF 246 may also include the following functions to support edge computing enhancements (e.g., see [TS23548]): selecting the EASDF 261 and providing its address to the UE as the DNS server for the PDU session; using the EASDF261 service defined in [TS23548]; and providing and updating the ECS address configuration information to the UE for supporting the application layer architecture defined in [TS23558]. The discovery and selection process for the EASDF 261 is discussed in Section 6.3.23 of [TS23501].

[0104] The UPF 248 acts as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnecting with the data network 236, and a branching point for supporting multi-homed PDU sessions. The UPF 248 also performs packet routing and forwarding, packet inspection, enforces the user plane part of the policy rules, lawful interception of packets (UP collection), performs traffic usage reporting, performs QoS handling for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), performs UL traffic verification (e.g., SDF to QoS flow mapping), transport layer packet marking in UL and DL, and performs DL packet buffering and DL data notification triggering. The UPF 248 may include a UL classifier to support routing traffic flows to the data network.

[0105] The NSSF 250 selects a set of network slice instances serving the UE 202. The NSSF 250 also determines the allowed NSSAI and its mapping to the subscribed S-NSSAI as required. The NSSF 250 also determines a set of AMFs or a list of candidate AMFs 244 for serving the UE 202 based on appropriate configuration and possibly by querying the NRF 254. Through interaction with the NSSF 250, the AMF 244 to which the UE 202 is registered can trigger the selection of a set of network slice instances for the UE 202; this may result in a change of the AMF 244. The NSSF 250 interacts with the AMF 244 via the N22 reference point; and can communicate with another NSSF in the visited network via the N31 reference point (not shown).

[0106] The NEF 252 securely exposes the services and capabilities provided by 3GPP NFs to third parties, internal exposure / re-exposure, AF 260, edge computing network / framework, etc. In such examples, the NEF 252 may authenticate, authorize, or throttle the AF 260. The NEF 252 uses the Nudr interface of the Unified Data Repository (UDR) to store / retrieve information as structured data. The NEF 252 also transforms the information exchanged with the AF 260 and the information exchanged with internal NFs. For example, as described in clause 5.6.7 of [TS23501], the NEF 252 may transform between an AF service identifier and internal 5GC information (e.g., DNN, S-NSSAI). In particular, the NEF 252 shields network and user sensitive information from the external AF 260 according to network policies. The NEF 252 also receives information from other NFs based on the capabilities exposed by other NFs. This information can be stored in the NEF 252 as structured data, or stored in a data storage NF using a standardized interface. Then, the stored information can be re-exposed by the NEF 252 to other NFs and AFs, or used for other purposes such as analysis. For example, according to the provisions of [TS23288], the NWDAF analysis can be securely exposed to the outside by the NEF 252. In addition, the NWDAF 262 can collect externally provided data through the NEF 252 for generating analysis results. As described in [TS23288], the NEF 252 processes and forwards requests and notifications between the NWDAF 262 and the AF(s) 260. In some examples, the NEF 252 may provide an interface(s) to one or more edge computing nodes 238, which can be used to handle the radio connection with the RAN 214 and / or offload tasks to the edge computing nodes 238.

[0107] The NRF 254 supports the service discovery function, receives NF discovery requests from NF instances, and provides information about the discovered NF instances to the NF instance that made the request. The NRF 254 also maintains the NF profiles of the available NF instances and the services they support. The NF profiles of the NF instances maintained in the NRF 254 include the following information: NF instance ID, NF type, PLMN ID (if it is a PLMN), PLMN ID + NID (if it is an SNPN), (one or more) network slice-related identifiers (e.g., S-NSSAI, NSIID), (one or more) network addresses of the NF (e.g., fully qualified domain name (FQDN), IP address, etc.), NF capacity information, NF priority information (e.g., for AMF selection), NF set ID, NF service set ID of the NF service instance; NF-specific service authorization information; names of the supported services (if applicable); (one or more) endpoint addresses of (one or more) instances of each supported service; identification of the stored data / information (e.g., for UDR profiles and / or other NF profiles); (one or more) other service parameters (e.g., DNN or DNN list, LADN DNN or LADN DNN list, notification endpoints for each type of notification that the NF service is interested in receiving, etc.); location information of the NF instance (e.g., geographical location, data center, etc.); (one or more) TAI; NF load information; routing indicator; home network public key identifier (for UDM 258 and AUSF 242); for UDM 258, AUSF 242, and NSSAAF, in the case of accessing an SNPN using the credentials owned by the credential holder with an AAA server, the identification of the credential holder (e.g., subscription permanent identifier (SUPI) based on the network-specific identifier domain); for UDM 258 and AUSF 242, if UDM 258 / AUSF 242 is used to access an SNPN using the credentials owned by the credential holder, the identification of the credential holder (e.g., the domain if a network-specific identifier-based SUPI is used; or MCC and MNC if an IMSI-based SUPI is used); for AUSF 242 and NSSAAF, in the case of SNPN Onboarding using a DCS with an AAA server, the identification of the DCS (e.g., the domain of the network-specific identifier-based SUPI); for UDM 258 and AUSF 242, for SNPN Onboarding if UDM 258 / AUSF 242 is used as the DCS, the identification of the DCS (e.g., the domain if a network-specific identifier-based SUPI is used; or MCC and MNC if an IMSI-based SUPI is used); for AMF 244, one or more GUAMI;For UPF 248, see clause 5.2.7.2.2 of [TS23502]; for UDM 258, UDM group ID, (one or more) ranges of SUPI, (one or more) ranges of GPSI, (one or more) ranges of internal group identifiers, (one or more) ranges of external group identifiers; for UDR, UDR group ID, (one or more) ranges of SUPI, (one or more) ranges of GPSI, (one or more) ranges of external group identifiers; for AUSF 242, AUSF group ID, (one or more) ranges of SUPI; for PCF 256, PCF group ID, (one or more) ranges of SUPI; for HSS, HSS group ID, (one or more) sets of IMPI, (one or more) sets of IMPU, (one or more) sets of IMSI, (one or more) sets of PSI, (one or more) sets of MSISDN; for NEF 252, (one or more) event IDs supported by AF 260; for NEF 252, (one or more) event exposure service event IDs supported by UPF 248; for NEF 252, (one or more) application identifiers supported by AF 260; for NEF 252, (one or more) ranges of external identifiers or domain names served by NEF (e.g., used when NEF 252 exposes AF information for analysis, as detailed in [TS23288]); in addition, NRF 254 may also store the mappings between UDM group ID and (one or more) SUPI, between UDR group ID and (one or more) SUPI, between AUSF group ID and (one or more) SUPI, and between PCF group ID and (one or more) SUPI, to discover UDM 258, UDR, AUSF 242, and PCF 256 using SUPI, SUPI ranges as specified in clause 6.3 of [TS23501], and / or interact with UDR to resolve UDM group ID / UDR group ID / AUSF group ID / PCF group ID based on the UE identity (e.g., SUPI); for BSF, IP domain list (as described in clause 6.1.6.2.21 of 3GPP TS29.510v18.2 (2023-03-29) (“[TS29510]”)), (one or more) ranges of (UE) IPv4 addresses or (one or more) ranges of (UE) IPv6 prefixes, (one or more) ranges of SUPI or (one or more) ranges of GPSI or BSF group ID; SCP domain to which the NF belongs; for DCCF 263, DCCF service area information, NF type of the data source, NF set ID of the data source (if any); for SMF 246, supported DNAI list;For SNPN, the ability to support SNPN Onboarding in the case of AMF and the ability to support user plane remote provisioning in the case of SMF 246; for UPF 248, IP address range, DNAI; additional NF profile parameters related to V2X are defined in 3GPP TS 23.287; additional ProSe-related NF profile parameters are defined in 3GPP TS 23.304; additional MBS-related NF profile parameters are defined in 3GPP TS 23.247; additional UAS-related NF profile parameters are defined in TS 23.256; and many other parameters discussed in [TS23501]. In some examples, such as when the NF instance has special service authorization information, the service authorization information provided by the OAM system is also included in the NF profile.;

[0108] For NWDAF 262, the NF profile includes: (one or more) supported analysis IDs (possibly per service), NWDAF service area information (e.g., a list of TAI for which NWDAF can provide services and / or data), supported analysis latency per analysis ID (if any), NF type of the NF data source, NF set ID of the NF data source (if any), analysis aggregation ability (if any), analysis metadata provisioning ability (if any), (one or more) ML model filtering information parameters S-NSSAI and (one or more) regions of interest of (one or more) trained ML models per analysis ID (if any), federated learning (FL) ability type (e.g., FL server or FL client, if any), time interval supporting FL (if any). The NWDAF 262 service area information is common for all supported analysis IDs. The analysis IDs supported by NWDAF 262 can be associated with the supported analysis latency. For example, an analysis report can be generated within a time (including data collection latency and inference latency) less than or equal to the supported analysis latency. The determination of the supported analysis latency and how NWDAF 262 avoids frequent updates of its supported analysis latency in the NRF may be related to the specific implementation of NWDAF.

[0109] PCF 256 provides policy rules for the control plane function to enforce these rules and may also support a unified policy framework to manage network behavior. PCF 256 can also implement a front end to access subscription information related to policy decisions in the UDR 259 of UDM 258. In addition to communicating with functions through reference points as shown, PCF 256 also exposes Npcf service-based interfaces.

[0110] The UDM 258 processes subscription-related information to support network entities in handling communication sessions and stores the subscription data of the UE 202. For example, the subscription data can be communicated via the N8 reference point between the UDM 258 and the AMF 244. The UDM 258 can include two parts: an application front end and a UDR. The UDR can store subscription data and policy data for the UDM 258 and the PCF 256, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 202) for the NEF 252. The Nudr service-based interface can be presented by the UDR to allow the UDM 258, the PCF 256, and the NEF 252 to access specific stored data sets, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM 258 can include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Multiple different front ends can serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown, the UDM 258 can also present a Nudm service-based interface.

[0111] Edge Application Server Discovery Function (EASDF) 261 presents an interface based on the Neasdf service and is connected to the SMF 246 via the N88 interface. One or more EASDF instances may be deployed within a PLMN, and the interaction between (one or more) 5GC NFs and the EASDF 261 occurs within the PLMN. The EASDF 261 includes one or more of the following functions: registering with the NRF 254 for EASDF261 discovery and selection; processing DNS messages according to instructions from the SMF 246; and / or terminating DNS security (if used). Processing DNS information according to instructions from the SMF 246 includes one or more of the following functions: receiving DNS message processing rules and / or BaselineDNSPattern from the SMF 246; exchanging DNS messages with / from the UE 202; forwarding DNS messages to the C-DNS or L-DNS for DNS queries; adding the EDNS Client Subnet (ECS) option to DNS queries for FQDNs; reporting information related to the received DNS messages to the SMF246; and / or buffering / dropping DNS messages from the UE 202 or DNS servers. The EASDF has a direct user plane connection with the PSA UPF via N6 (e.g., without any NAT) to transport DNS signaling exchanged with the UE. Deployment of NAT between the EASDF 261 and the PSA UPF 248 may or may not be supported. Other aspects of the EASDF 261 are discussed in [TS23548].

[0112] The AF 260 provides application impact on traffic routing, provides access to the NEF 252, and interacts with the policy framework for policy control. The AF 260 may affect UPF 248 (re)selection and traffic routing. Depending on the operator's deployment, when the AF260 is considered a trusted entity, the network operator may allow the AF260 to directly interact with the relevant NFs. In some implementations, the AF260 is used for edge computing implementations.

[0113] NFs that need to collect data from the AF 260 may directly subscribe / unsubscribe from the AF 260 or via the NEF 252 for notifications regarding the data collected from the AF260. The data collected from the AF 260 is used as input for the analysis by the NWDAF 262. Details of the data collected from the AF 260 and the interaction between the NEF 252, AF 260, and NWDAF 262 are described in [TS23288].

[0114] The 5GC 240 can implement edge computing by selecting an operator / third-party service that is geographically close to the point where the UE 202 is attached to the network. This can reduce latency and network load. In the edge computing implementation, the 5GC 240 can select a UPF 248 close to the UE 202 and perform traffic steering from the UPF 248 to the DN 236 through the N6 interface. This can be based on UE subscription data, UE location, and information provided by the AF 260, which allows the AF 260 to influence UPF (re)selection and traffic routing.

[0115] The data network (DN) 236 can represent various network operator services, Internet access, or third-party services, which can be provided by one or more servers, such as including an application (App) / content server 238. The DN 236 can be an operator external public network, a private PDN, or an operator internal packet data network, for example, for providing IMS services. In this example, the application server 238 can be coupled to the IMS through an S-CSCF or an I-CSCF. In some implementations, the DN 236 can represent one or more local DNs (LADNs), which are DNs 236 (or DN names (DNNs)) that the UE 202 can access in one or more specific areas. Outside of these specific areas, the UE 202 cannot access the LADN / DN 236.

[0116] Additionally or alternatively, the DN 236 can be an edge DN 236, which is a (local) DN that supports an architecture enabling edge applications. In these examples, the application server 238 can represent a physical hardware system / device providing application server functionality, and / or application software of an edge computing node residing in the cloud or performing (one or more) server functions. In some examples, the application / content server 238 provides an edge hosting environment that provides the support required for the execution of an edge application server.

[0117] In some examples, the 5GS can use one or more edge computing nodes to provide an interface and offload processing for wireless communication traffic. In these examples, the edge computing nodes can be included in or co-located with one or more RANs 204 or RAN nodes 214. For example, the edge computing nodes can provide a connection between the RAN 204 and the UPF 248 in the 5GC 240. The edge computing nodes can use one or more NFV instances instantiated on the virtualization infrastructure within the edge computing nodes to process wireless connections to and from the RAN 214 and the UPF 248.

[0118] In some implementations, the edge computing node provides a distributed computing environment for application and service hosting and also provides storage and processing resources to enable data and / or content to be processed closer to the subscriber (e.g., the user of UE 202), thereby reducing the response time. The edge computing node also supports a multi-tenant runtime and a hosting environment for (one or more) applications, including virtual device applications, middleware applications, and infrastructure services that can be delivered as packaged virtual machine (VM) images, content delivery services including content caching, mobile big data analytics, and compute offloading, etc. Compute offloading includes offloading compute tasks, workloads, applications, and / or services from UE 202, CN 240, DN 236, and / or (one or more) servers 238 to the edge computing node and vice versa. For example, a device application or a client application running in UE 202 can offload an application task or workload to one or more edge computing nodes. In another example, the edge computing node can offload an application task or workload to a group of UEs 202 (e.g., for distributed machine learning computations, etc.).

[0119] The edge computing node may include or be part of an edge system that employs one or more edge computing technologies (ECTs) (also referred to as "edge computing frameworks", etc.). The edge computing node may also be referred to as an "edge host" or an "edge server". The edge system includes a collection of edge servers and an edge management system (not shown) required to run edge computing applications in a carrier network or a subset of the carrier network. The edge server is a physical computer system that may include an edge platform and / or virtualization infrastructure and provides computing, storage, and network resources to edge computing applications. Each edge server is disposed at the edge of a corresponding access network and is arranged to provide computing resources and / or various services (e.g., compute task and / or workload offloading, cloud computing capabilities, IT services, and other similar resources and / or services discussed herein) relatively close to UE 202. The VI of the edge computing node provides a virtualization environment and virtualization resources for the edge host, and edge computing applications can run on the VI as VMs and / or application containers.

[0120] In an example implementation, the ECT is part of and / or operates according to the MEC framework, such as those discussed in the following documents: ETSI GR MEC 001v3.1.1 (2022-01), ETSI GS MEC 003v3.1.1 (2022-03), ETSI GS MEC 009v3.1.1 (2021-06), ETSI GS MEC 010-1v1.1.1 (2017-10), ETSI GS MEC 010-2v2.2.1 (2022-02), ETSI GS MEC 011v2.2.1 (2020-12), ETSI GS MEC 012V2.2.1 (2022-02), ETSI GS MEC 013V2.2.1 (2022-01), ETSI GS MEC 014v2.1.1 (2021-03), ETSI GS MEC015v2.1.1 (2020-06), ETSI GS MEC 016v2.2.1 (2020-04), ETSI GS MEC 021v2.2.1 (2022-02), ETSI GR MEC 024v2.1.1 (2019-11), ETSI GS MEC 028V2.2.1 (2021-07), ETSI GS MEC029v2.2.1 (2022-01), ETSI MEC GS 030v2.1.1 (2020-04) and ETSI GR MEC031v2.1.1 (2020-10) (collectively referred to herein as "[MEC]").This example implementation (and / or any other example implementation discussed herein) may also include NFV and / or other similar virtualization technologies such as those discussed in the following documents: ETSI GR NFV 001 V1.3.1 (2021-03), ETSI GS NFV 002 V1.2.1 (2014-12), ETSI GR NFV 003 V1.6.1 (2021-03), ETSI GS NFV 006 V2.1.1 (2021-01), ETSI GS NFV-IF 001 V1.1.1 (2015-01), ETSI GS NFV-IF 003 V1.1.1 (2014-12), ETSI GS NFV-INF 004 V1.1.1 (2015-01), ETSI GS NFV-MAN 001 v1.1.1 (2014-12), and / or Israel et al., OSM Release FIVE Technical Overview, ETSI OPENSOURCE MANO, OSM White Paper, 1st ed. (January 2019), https: / / osm.etsi.org / images / OSM-Whitepaper-TechContent-ReleaseFIVE-FINAL.pdf (collectively referred to as "[ETSINFV]"). Other virtualization technologies and / or service orchestration and automation platforms may be used, such as the virtualization technologies and / or service orchestration and automation platforms discussed in the following items: E2E Network Slicing Architecture, GSMA, Official Doc. NG.127, v1.0 (June 3, 2021); https: / / www.gsma.com / newsroom / wp-content / uploads / / NG.127-v1.0-2.pdf, Open Network Automation Platform (ONAP) documentation, Release Istanbul, v9.0.1 (February 17, 2022); https: / / docs.onap.org / en / latest / index.html ("[ONAP]"); the Service-Based Management Architecture (SBMA) discussed in 3GPP TS 28.533 v17.1.0 (2021-12-23) ("[TS28533]").

[0121] In another example implementation, the ECT is within and / or operates according to the O-RAN framework. Various aspects of the O-RAN architecture are described in the following: O-RAN Working Group 1 (Use Cases and Overall Architecture), O-RAN Architecture Description, O-RAN Alliance WG1, O-RAN Hardening Description v09.00, Release 003 (June 2023) (“[ORAN.OAD]”); O-RAN Working Group 1 Slice Architecture, O-RAN Alliance WG1, Slice Architecture Technical Specification v10.00, Release 003 (June 2023); O-RAN Working Group 1 Use Case Detailed Specification Architecture, v11.00, Release 003 (June 2023) (“[ORAN.UseCases]”); O-RAN Working Group 2 (Non-RT RIC and A1 Interface Working Group) A1 Interface: Application Protocol, v04.00, R003 (March 2023) (“[ORAN.A1AP]”); O-RAN Working Group 2 (Non-RT RIC and A1 Interface Working Group) A1 Interface: General Aspects and Principles, v03.01, Release 003 (March 2023) (“[ORAN.A1GAP]”); O-RAN Working Group 2 (Non-RT RIC and A1 Interface Working Group) A1 Interface: Type Definitions, v05.01, R003 (June 2023) (“[ORAN.A1TD]”); O-RAN Working Group 2 (Non-RT RIC and A1 Interface Working Group) A1 Interface: Transport Protocol, v02.01, R003 (March 2023); O-RAN Working Group 2 AI / ML Workflow Description and Requirements v01.03 O-RAN Alliance WG2 (October 2021) (“[ORAN.AIML]”); O-RAN Working Group 2 (Non-RT RIC and A1 Interface Working Group): R1 Interface: General Aspects and Principles 5.0, v05.00, R003 (June 2023); O-RAN Working Group 2 (Non-RT RIC and A1 Interface Working Group) Non-RT RIC Architecture, v03.00, Release 003 (June 2023) (“[O-RAN.Non-RT-RIC-ARCH]”); O-RAN Working Group 2 (Non-RT RIC and A1 Interface Working Group): Use Cases and Requirements, v07.00, Release 003 (June 2023) (“[O-RAN.Use-Case-Requirements]”); O-RAN Working Group 3 Near Real-Time RAN Intelligent Controller Architecture and E2 General Aspects and Principles, v03.01, Release 003 (June 2023) (“[ORAN.E2GAP]”); O-RAN Working Group 3, Near Real-Time Intelligent Controller, E2 Application Protocol (E2AP), v03.01, Release 003 (June 2023) (“[ORAN.E2AP”); O-RAN Working Group 3, Near Real-Time Intelligent Controller E2 Service Model (E2SM), v03.01, Release R003 (June 2023) (“[ORAN.E2SM]”); O-RAN Working Group 3, Near Real-Time Intelligent Controller E2 Service Model (E2SM) KPM, v03.00, Release R003 (March 2023) (“[ORAN.E2SM-KPM]”); O-RAN Working Group 3 Near Real-Time Intelligent Controller E2 Service Model (E2SM), Cell Configuration and Control, v01.01, Release R003 (March 2023) (“[ORAN.E2SM-CCC]”); O-RAN Working Group 3 Near Real-Time Intelligent Controller E2 Service Model (E2SM) RAN Functional Network Interface (NI) v01.00 (February 2020) (“[ORAN.E2SM-NI]”); O-RAN Working Group 3 Near Real-Time Intelligent Controller E2 Service Model (E2SM) RAN Control v03.00, Release R003 (June 2023) (“[ORAN.E2SM-RC]”); O-RAN Working Group 3 (Near Real-Time RAN Intelligent Controller and E2 Interface Working Group): Near Real-Time RIC Architecture, v04.00, Release R003 (March 2023) (“[ORAN.RICARCH]”); O-RAN Working Group 4 (Open Fronthaul Interface Working Group) Control, User, and Synchronization Plane Specifications, v12.00, Release R003 (June 2023) (“[ORAN.CUS]”); O-RAN Fronthaul Working Group 4, Cooperative Transmission Interface Transmission Control Plane Specification, v04.00, Release R003 (June 2023); O-RAN Fronthaul Working Group 4, Cooperative Transmission Interface Transmission Management Plane Specification, v12.00, Release R003 (June 2023) (“[ORAN.MP]”); O-RAN Alliance Working Group 5, O1 Interface Specification for O-CU-UP and O-CU-CP v05.00, Release R003 (June 2023); O-RAN Alliance Working Group 5, O1 Interface Specification for O-DU v07.00, Release R003 (June 2023); O-RAN Alliance Working Group 6, O2 Interface General Aspects and Principles 4.0, v04.00, Release R003 (June 2023); O-RAN Working Group 6 (Cloudification and Orchestration) O-RAN Virtualized RAN Cloud Architecture and Deployment Scenarios v04.00 (October 2022) (“[ORAN.CADS]”); O-RAN Working Group 6 (Cloudification and Orchestration Working Group): O-RAN Accelerated Abstraction Layer General Aspects and Principles, v06.00, Release R003 (June 2023); O-RAN Working Group 6: O-Cloud Notification API Specification for Event Consumers, v03.00 (October 2022) (“[ORAN.O-RAN White Box Hardware Working Group, Hardware Reference Design Specification for Indoor Pico Cell with Fronthaul Split Option 6, v02.00, O-RAN Alliance WG7 (October 2021) (“[ORAN.IPC-HRD-Opt6]”); O-RAN WG7, Hardware Reference Design Specification for Indoor Pico Cell (FR1) with Split Architecture Option 7-2, v03.00, O-RAN Alliance WG7 (October 2021) (“[ORAN.IPC-HRD-Opt7-2]”); O-RAN WG7, Hardware Reference Design Specification for Indoor Picocell (FR1) with Split Architecture Option 8, v03.00 (October 2021) (“[ORAN.IPC-HRD-Opt8]”); O-RAN White Box Hardware Working Group, Hardware Reference Design Specification for Outdoor Microcell with Split Architecture Option 7.2, v03.00, O-RAN Alliance WG7 (October 2022) (“[ORAN.OMC-HRD-Opt7-2]”); O-RAN White Box Hardware Working Group, Hardware Reference Design Specification for Outdoor Macro Cell with Split Architecture Option 7.2, v03.00, Release R003 (June 2023) (“[ORAN.OMAC-HRD]”); O-RAN Open X-haul Transport Working Group, Management Interface for Transport Network Elements, v06.00, Release R003 (June 2023); O-RAN Open Transport Working Group 9, Xhaul Packet Switching Architecture and Solutions, v05.00, Release R003 (2 O-RAN.XPSAAS, June 2023) (“[ORAN.XPSAAS]”); O-RAN Open Xhaul Transport Working Group, Synchronized Architecture and Solution Specification, v03.00 (October 2022); O-RAN Open Xhaul Transport WG9, WDM-based Front-end Transport, v03.00, Release R003 (March 2023); O-RAN Operation and Maintenance Architecture, v09.00, Release R003 (June 2023) (“[ORAN.OAM-Arch]”); O-RAN Operation and Maintenance Interface Specification, v10.00, O-RAN Alliance WG10, Version R003 (June 2023) (“[ORAN.O1-Interface]”); O-RAN Information Model and Data Model Specification v05.00, O-RAN Alliance WG10, Version R003 (June 2023); and O-RAN: Towards an Open and Intelligent RAN, O-RAN Alliance White Paper (October 2018) (collectively, “[O-RAN]”). .

[0122] In another example implementation, the ECT is the architecture enabling edge applications of the 3rd Generation Partnership Project (3GPP) System Architecture Working Group 6 (SA6) (referred to as "[3GPP Edge Computing]" for short) and / or operates according to the architecture enabling edge applications of 3GPP SA6 (referred to as "[3GPP Edge Computing]" for short). For example, the architecture enabling edge applications of 3GPP SA6 (referred to as "[3GPP Edge Computing]" for short) is discussed in the following documents: 3GPP TS 23.222 ("[TS23222]"), 3GPP TS 23.401, 3GPP TS 23.434 ("[TS23434]"), 3GPP TS 23.501 ("[TS23501]"), 3GPP TS 23.502 ("[TS23502]"), 3GPP TS 23.548 ("[TS23548]"), 3GPP TS 23.558 ("[TS23558]"), 3GPP TS 23.682 ("[TS23682]"), 3GPP TR 23.700-98 ("[TR23700-98]"), 3GPP TS 28.104 ("[TS28104]"), 3GPP TS 28.105 ("[TS28105]"), 3GPP TS 28.532 ("[TS28532]"), 3GPP TS 28.533 ("[TS28533]"), 3GPP TS 28.535 ("[TS28535]"), 3GPP TS 28.536 ("[TS28536]"), 3GPP TS 28.538 ("[TS28538]"), 3GPP TS 28.541 ("[TS28541]"), 3GPP TS 28.545 ("[TS28545]"), 3GPP TS 28.550 ("[TS28550]"), 3GPP TS 28.554 ("[TS28554]"), 3GPP TS 28.622 ("[TS28622]"), 3GPP TS 29.122 ("[TS29122]"), 3GPP TS 29.222 ("[TS29222]"), 3GPP TS 29.522 ("[TS29522]"), 3GPP TR 28.908 ("[TR28908]"), 3GPP TS 33.122 ("[TS33122]") (collectively referred to as "[5G Edge]").

[0123] In another example implementation, the ECT is the following item and / or operates according to the following item: The Intelligent Edge Open Framework (formerly known as OpenNESS), which framework is in Discussed in the Smart Edge Open Developer Guide, Version 21.09 (September 30, 2021), available at https: / / smart-edge-open.github.io / (“[ISEO]”).

[0124] In another example implementation, the ECT operates according to the Multi-Access Management Service (MAMS) framework, which is discussed in the following documents: Kanugovi et al., Multi-Access Management Service (MAMS), Internet Engineering Task Force (IETF), Request for Comments (RFC) 8743 (March 2020) (“[RFC8743]”); Ford et al., TCP Extensions for Multipath Operations with Multiple Addresses, IETF RFC 8684, (March 2020); De Coninck et al., Multipath Extensions for QUIC (MP-QUIC), IETF DRAFT-DECONINCK-QUIC-MULTIPATH-07, IETA, QUIC Working Group (May 3, 2021); Zhu et al., User Plane Protocol for Multi-Access Management Service, IETF DRAFT-ZHU-INTAREA-MAMS-USER-PROTOCOL-09, IETA, INTAREA (March 4, 2020); and Zhu et al., General Multi-Access (GMA) Convergence Encapsulation Protocol, IETF RFC 9188 (February 2022) (collectively referred to as “[MAMS]”).

[0125] It should be understood that the above-described edge computing framework / ECT and service deployment examples are merely illustrative examples of ECT, and the present disclosure may be applicable to many other or additional edge computing / network technologies in various combinations and layouts of devices located at the network edge (including various edge computing networks / systems described herein). Additionally, the technologies disclosed herein may relate to other IoT edge network systems and configurations, and other intermediate processing entities and architectures may also be applicable to the present disclosure. Examples of such edge computing / network technologies include: [MEC]; [O-RAN]; [ISEO]; [5GEdge]; content delivery networks (CDNs) (also referred to as "content distribution networks", etc.); mobile service provider (MSP) edge computing and / or mobile as a service (MaaS) provider systems (e.g., systems used in the AECC architecture); nebula edge cloud systems; fog computing systems; small slice cloud edge cloud systems; mobile cloud computing (MCC) systems; re-architected central office as a data center (CORD), mobile CORD (M-CORD), and / or converged multi-access and core (COMAC) systems; and / or similar systems. Additionally, the technologies disclosed herein may relate to other IoT edge network systems and configurations, and other intermediate processing entities and architectures may also be used for the purposes of the present disclosure.

[0126] The interfaces of 5GC 240 include reference points and service-based interfaces. At least in some examples, a reference point is a point of attachment between two non-overlapping functional groups, elements, or entities. The reference points include: N1 (between UE 202 and AMF 244), N2 (between RAN 214 and AMF 244), N3 (between RAN 214 and UPF 248), N4 (between SMF 246 and UPF 248), N5 (between PCF 256 and AF 260), N6 (between UPF 248 and DN 236), N7 (between SMF 246 and PCF 256), N8 (between UDM 258 and AMF244), N9 (between two UPF 248), N10 (between UDM 258 and SMF 246), N11 (between AMF 244 and SMF 246), N12 (between AUSF 242 and AMF 244), N13 (between AUSF 242 and UDM 258), N14 (between two AMF 244; not shown), N15 (between PCF 256 and AMF 244 in non-roaming cases, or between the PCF 256 of the visited network and AMF 244 in roaming cases), N16 (between two SMF 246; not shown), and N22 (between AMF 244 and NSSF 250). Other reference point notations not shown in Figure 2 the text, such as any of those discussed in [TS23501], may also be used.

[0127] Figure 2 NFs within the control plane are represented based on service-based representations, where the NFs enable other authorized NFs to access their services. At least in some examples, a service-based interface (SBI) can enable an NF to access the services of one or more other NFs via the interface. In some implementations, the service-based interface is an API-based interface (e.g., northbound API, southbound API, HTTP / 2, RESTful, SOAP, A1AP, E2AP, and / or any other API, web service, application layer, and / or other communication protocols, such as any protocol discussed herein), and NFs can use these interfaces to invoke or call specific services or service operations. The SBI includes: Namf (SBI presented by AMF 244), Nsmf (SBI presented by SMF 246), Nnef (SBI presented by NEF 252), Npcf (SBI presented by PCF 256), Nudm (SBI presented by UDM 258), Naf (SBI presented by AF 260), Nnrf (SBI presented by NRF254), Nnssf (SBI presented by NSSF 250), Nausf (SBI presented by AUSF 242). Other service-based interfaces not shown herein (e.g., Nudr, N5g-eir, and Nudsf) can also be used, such as any interface discussed in [TS23501]. Figure 2 Other service-based interfaces not shown (e.g., Nudr, N5g-eir, and Nudsf), such as any interface discussed in [TS23501].

[0128] Although Figure 2 not shown, the system 200 may also include NFs not shown, such as UDR, unstructured data storage function (UDSF), network slice admission control function (NSACF), network slice specific and stand-alone non-public network (SNPN) authentication and authorization function (NSSAAF), UE radio capability management function (UCMF), 5G equipment identity register (5G-EIR), charging function (CHF), time-sensitive network (TSN) AF 260, time-sensitive communication and time synchronization function (TSCTSF), data collection coordination function (DCCF), analytical data repository function (ADRF), message framework adapter function (MFAF), binding support function (BSF), non-seamless WLAN offload function (NSWOF), service communication proxy (SCP), secure edge protection proxy (SEPP), non-3GPP interworking function (N3IWF), trusted non-3GPP gateway function (TNGF), wired access gateway function (W-AGF), and / or trusted WLAN interworking function (TWIF), as described in [TS23501].

[0129] The present disclosure generally relates to wireless communication, cellular networks, cloud computing, edge computing, data centers, network topologies, communication system implementations, network convergence, artificial intelligence (AI) / machine learning (ML) technologies, and in particular, to techniques for signaling activation and deactivation of UE-level measurement operations.

[0130] An increasing number of use cases are starting to rely on the availability of per-UE measurements, for example, management control loops (such as distributed self-organizing network (SON) (D-SON), centralized SON (C-SON), hybrid SON functions, etc.) and analysis and intelligent functions in the network (such as network data analytics function (NWDAF), RAN intelligent functions, etc.).

[0131] Some use cases require collecting UE-level measurement results from one or more 5GC network functions (NFs) and NG-RAN nodes, and correlating the measurement results from different functions and nodes for analysis. Therefore, in such cases, the UE-level measurement results provided by 5GC NFs and NG-RAN nodes need to be able to be correlated with each other.

[0132] However, the NG-RAN does not know the UE permanent ID (such as SUPI, IMEISV), and the gNB central unit (CU)-user plane (UP) does not use the identifiers used in 5GC (such as NGAP Id). Therefore, without signaling actions for UE-level measurement operations, it is not possible to support the correlation of UE-level measurements provided by 5GC and NG-RAN.

[0133] The present disclosure provides techniques and craftsmanship for signaling actions for UE-level measurement operations by reusing and extending trace mechanisms (such as the trace mechanisms defined in 3GPP TS 32.422 V18.1.0 (2023-12) (3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Telecommunications Management; Subscriber and Equipment Trace; Trace Control and Configuration Management (Release 18))). Specifically, embodiments include signaling actions for UE-level measurement operations by reusing and extending trace mechanisms. UE-level measurement results can be used to enable AI / ML applications / use cases in 5GS (such as training data, test data, validation data, inference data, etc.).

[0134] Figure 3 A flowchart of a method 300 for signaling activation of UE-level measurement operations according to some embodiments of the present disclosure is shown. Method 300 can be performed by a service producer, for example, a management service (MnS) producer (MnS-P). As shown, method 300 can include operations 310-340.

[0135] At 310, a trace job creation request received from a service consumer is decoded to create a trace job for collecting UE-level measurement results in a communication network. At 320, in response to the trace job creation request, a trace session activation request for activating a trace session is encoded for transmission to the UDM. At 330, a trace session activation response received from the UDM in response to the trace session activation request is decoded, and the trace session activation response is used to indicate the activation result of the trace session. At 340, in response to the trace session activation response, a trace job creation response is encoded for transmission to the service consumer, and the trace job creation response is used to indicate the creation result of the trace job.

[0136] Figure 4 FIG. 400 is a flowchart of a method 400 for signaling activation of a UE-level measurement job according to some embodiments of the present disclosure. The method 400 may be performed by a service consumer, e.g., an MnS consumer (MnS-C). As shown, the method 400 may include operations 410 and 420.

[0137] At 410, a trace job creation request is encoded for transmission to a service producer, and the trace job creation request is used to create a trace job for collecting UE-level measurement results in a communication network. At 420, a trace job creation response received from the service producer in response to the trace job creation request is decoded, and the trace job creation response is used to indicate the creation result of the trace job.

[0138] In some embodiments, the MnS-P and the MnS-C are included in a management system.

[0139] In some embodiments, a trace job may include: a job type indicating that the trace job is for UE-level measurement result collection; a trace target indicating the UE to be measured; management attributes for UE-level measurement configuration; a public land mobile network (PLMN) target; a job ID; a trace reference; an Internet protocol (IP) address of a trace collection entity for file-based trace reports; a uniform resource identifier (URI) of a trace report consumer for streaming trace reports; a trace report format; etc.

[0140] In some embodiments, the management attributes for UE-level measurement configuration include: UE-level measurement results to be collected; a UE-level measurement granularity period; an object instance to be measured; or a root object instance of the object to be measured.

[0141] In some embodiments, a service consumer may: encode a trace job deletion request for transmission to a service producer, the trace job deletion request being used to delete a trace job; and decode a trace job deletion response received from the service producer in response to the trace job deletion request, the trace job deletion response being used to indicate a deletion result of the trace job.

[0142] In some embodiments, a service producer may: decode a trace job deletion request received from a service consumer to delete a trace job; in response to the trace job deletion request, encode a trace session deactivation request for deactivating a trace session for transmission to the UDM; decode a trace session deactivation response received from the UDM in response to the trace session deactivation request, the trace session deactivation response being used to indicate a deactivation result of the trace session; and in response to the trace session deactivation response, encode a trace job deletion response for transmission to the service consumer, the trace job deletion response being used to indicate a deletion result of the trace job.

[0143] In some embodiments, a trace session activation request may carry UE-level measurement configuration parameters.

[0144] In some embodiments, the UE-level measurement configuration parameters may include: a trace target; a trace reference; a network element (NE) type for measurement; a UE-level measurement result of the NE type for measurement; a UE-level measurement granularity period; an IP address of a trace collection entity for file-based trace reports; a URI of a trace report consumer for streaming trace reports; a trace report format; etc.

[0145] In some embodiments, the NE type for measurement may include a 5G core network (5GC) NF or an NG-RAN node.

[0146] In some embodiments, the NE type for measurement includes the AMF, and the UE-level measurement configuration parameters are provided to the AMF via a Nudm_SDM_Notification message or a forward relocation request.

[0147] In some embodiments, the NE type for measurement includes the SMF, and the UE-level measurement configuration parameters are provided to the SMF via a Nsmf_PDUSession_CreateSMContext request, a Nsmf_PDUSession_UpdateSMContext request, a Nudm_SDM_Notification message, or a Nudm_UECM_Registration procedure.

[0148] In some embodiments, the NE types for measurement include the PCF, and the UE-level measurement configuration parameters are provided to the PCF via a session management policy establishment procedure or a session management policy modification procedure.

[0149] In some embodiments, the NE types for measurement include the UPF, and the UE-level measurement configuration parameters are provided to the UPF via an N4 session establishment procedure or an N4 session modification procedure.

[0150] In some embodiments, the NE types for measurement include NG-RAN nodes, and the UE-level measurement configuration parameters are provided to the NG-RAN nodes via a trace start message, an initial context setup request, or a handover request.

[0151] In some embodiments, the UE-level measurement configuration parameters further include: the type of NG-RAN node for measurement; or the UE-level measurement result of the type of NG-RAN node for measurement.

[0152] In some embodiments, the trace targets include a subscription permanent identifier (SUPI) or an international mobile station equipment identity and software version number (IMEISV).

[0153] Figure 5 A flowchart of a method 500 for signaling to activate a UE-level measurement job according to some embodiments of the present disclosure is shown. The method 500 may be executed by the UDM. As shown, the method 500 may include operations 510 and 520.

[0154] At 510, decode a trace session activation request received from a service producer to activate a trace session for a UE-level measurement job. The trace session activation request may carry UE-level measurement configuration parameters. At 520, encode a Nudm_SDM_Notification message carrying the UE-level measurement configuration parameters for transmission to the AMF to start the trace session.

[0155] In some embodiments, the UDM may start a trace session in response to a trace session activation request.

[0156] In some embodiments, the UDM may: generate UE-level measurements within a granularity period based on the trace session activation request to start a trace record session under the trace session; and report the results of the UE-level measurements for the trace record session to a trace collection entity (TCE).

[0157] In some embodiments, the results of the UE-level measurements are reported via a file-based report or a flow-based report.

[0158] In some embodiments, the UDM may: decode a tracing session deactivation request received from a service producer to deactivate a tracing session; and in response to the tracing session deactivation request, encode another Nudm_SDM_Notification message for transmission to the AMF to stop the tracing session.

[0159] In some embodiments, the UDM may stop the tracing record session under the tracing session based on the tracing session deactivation request.

[0160] Figure 6 A flowchart of a method 600 for signaling to activate a UE-level measurement job according to some embodiments of the present disclosure is shown. The method 600 may be performed by the AMF. As shown, the method 600 may include operations 610 and 620.

[0161] At 610, decode a first message received from the NF to activate a tracing session for the UE-level measurement job. The first message may carry UE-level measurement configuration parameters. At 620, encode a second message carrying the UE-level measurement configuration parameters for transmission to the SMF to start the tracing session.

[0162] In some embodiments, the AMF may start a tracing session in response to the first message.

[0163] In some embodiments, the first message includes a Nudm_SDM_Notification message, and the NF includes the UDM.

[0164] In some embodiments, the first message includes a forward relocation request, and the NF includes the MME.

[0165] In some embodiments, the second message includes a Nsmf_PDUSession_CreateSMContext request or a Nsmf_PDUSession_UpdateSMContext request.

[0166] In some embodiments, the AMF may: generate UE-level measurements within a granularity period based on the first message to start a tracing record session under the tracing session; and report the results of the UE-level measurements for the tracing record session to the TCE.

[0167] In some embodiments, the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0168] In some embodiments, the AMF may: decode the Nudm_SDM_Notification message received from the UDM to deactivate the tracing session; and in response to the Nudm_SDM_Notification message, encode an Nsmf_PDUSession_UpdateSMContext request to be transmitted to the SMF for stopping the tracing session.

[0169] In some embodiments, the AMF may stop the tracing record session under the tracing session based on the Nudm_SDM_Notification message.

[0170] Figure 7 A flowchart of a method 700 for signaling to activate a UE-level measurement job according to some embodiments of the present disclosure is shown. The method 700 may be executed by the SMF. As shown, the method 700 may include operations 710 and 720.

[0171] At 710, decode a third message received from the NF to activate a tracing session for the UE-level measurement job. The third message carries UE-level measurement configuration parameters. At 720, encode a fourth message carrying the UE-level measurement configuration parameters to be transmitted to the PCF for starting the tracing session.

[0172] In some embodiments, the third message includes an Nsmf_PDUSession_CreateSMContext request or an Nsmf_PDUSession_UpdateSMContext request, and the NF includes the AMF.

[0173] In some embodiments, the third message includes a Nudm_SDM_Notification message or a Nudm_UECM_Registration message, and the NF includes the UDM.

[0174] In some embodiments, the fourth message includes a session management policy establishment message or a session management policy modification message.

[0175] In some embodiments, the SMF may: generate UE-level measurements within a granularity period based on the third message to start a tracing record session under the tracing session; and report the results of the UE-level measurements for the tracing record session to the TCE.

[0176] In some embodiments, the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0177] In some embodiments, the SMF may: decode the fifth message received from the NF to deactivate the trace session; and in response to the fifth message, initiate a session management policy modification procedure with the PCF to stop the trace session.

[0178] In some embodiments, the SMF may stop the trace record session under the trace session based on the fifth message.

[0179] In some embodiments, the fifth message includes an Nsmf_PDUSession_UpdateSMContext request, and the NF includes the AMF.

[0180] In some embodiments, the fifth message includes an Nudm_SDM_Notification message, and the NF includes the UDM.

[0181] Figure 8 A flowchart of a method 800 for signaling to activate a UE-level measurement job according to some embodiments of the present disclosure is shown. The method 800 may be performed by the PCF. As shown, the method 800 may include operations 810 and 820.

[0182] At 810, decode the session management policy establishment message or the session management policy modification message received from the SMF to activate the trace session for the UE-level measurement job. The session management policy establishment message or the session management policy modification message may carry UE-level measurement configuration parameters. At 820, start the trace session.

[0183] In some embodiments, the PCF may: generate UE-level measurements within a granularity period based on the session management policy establishment message or the session management policy modification message to start a trace record session under the trace session; and report the results of the UE-level measurements for the trace record session to the TCE.

[0184] In some embodiments, the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0185] In some embodiments, the PCF may: decode another session management policy modification message received from the SMF to deactivate the trace session; and based on the another session management policy modification message, stop the trace session.

[0186] In some embodiments, the PCF may stop the trace record session under the trace session based on the another session management policy modification message.

[0187] Figure 9 A flowchart of a method 900 for signaling to activate a UE-level measurement job according to some embodiments of the present disclosure is shown. The method 900 may be performed by the UPF. As shown, the method 900 may include operations 910 and 920.

[0188] At 910, decode the N4 session establishment message or N4 session modification message received from the SMF to activate a trace session for UE-level measurement jobs. The N4 session establishment message or N4 session modification message may carry UE-level measurement configuration parameters. At 920, start the trace session.

[0189] In some embodiments, the UPF may: generate UE-level measurements within a granularity period based on the N4 session establishment message or N4 session modification message to start a trace record session under the trace session; and report the results of the UE-level measurements for the trace record session to the TCE.

[0190] In some embodiments, the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0191] In some embodiments, the UPF may: decode another N4 session modification message received from the SMF to deactivate the trace session; and stop the trace session based on the another N4 session modification message.

[0192] In some embodiments, the UPF may stop the trace record session under the trace session based on another N4 session modification message

[0193] Figure 10 A flowchart of a method 1000 for signaling to activate UE-level measurement jobs according to some embodiments of the present disclosure is shown. The method 1000 may be performed by an NG-RAN node. As shown, the method 1000 may include operations 1010 and 1020.

[0194] At 1010, decode a sixth message received from an NF or another NG-RAN node to activate a trace session for UE-level measurement jobs. The sixth message may carry UE-level measurement configuration parameters. At 1020, start the trace session.

[0195] In some embodiments, the UE-level measurement configuration parameters may include: trace target; trace reference; NG-RAN node type for measurement; UE-level measurement results of the NG-RAN node type for measurement; UE-level measurement granularity period; IP address of the trace collection entity for file-based trace reporting; URI of the trace report consumer for streaming trace reports; trace report format; NE type for measurement; UE-level measurement results of the NE type for measurement; etc.

[0196] In some embodiments, the NG-RAN node type for measurement includes a gNB central unit (CU)-control plane (CP), a gNB CU-user plane (UP), or a gNB distributed unit (DU).

[0197] In some embodiments, the sixth message includes a trace start message received from the AMF, an initial context setup request, or an NG handover request.

[0198] In some embodiments, the sixth message includes an Xn handover request or an Xn get UE context response received from another NG-RAN node.

[0199] In some embodiments, the NG-RAN node may: generate UE-level measurements within a granularity period based on the sixth message to initiate a trace recording session under a trace session; and report the results of the UE-level measurements for the trace recording session to the TCE.

[0200] In some embodiments, the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0201] In some embodiments, the NG-RAN node may: decode a deactivate trace message received from the AMF to deactivate the trace session; and stop the trace session based on the deactivate trace message.

[0202] In some embodiments, the NG-RAN node may stop the trace recording session under the trace session based on the deactivate trace message.

[0203] In some embodiments, the NG-RAN node may: release the UE context; and stop the trace session in response to the release of the UE context.

[0204] The signaling actions of the UE-level measurement job reuse and extend the trace mechanism defined in 3GPP TS 32.422, and the activation mechanisms of the 5GC and NG-RAN are described in the following subclauses.

[0205] 7.1 Signaling trace session activation and deactivation for UL-level measurement jobs

[0206] 7.1.1 Creation of a trace job from a management system

[0207] MnS consumers interact with MnS producers for UE-level measurement result collection and reporting. The MnS consumer requests the MnS producer to create a trace job for collecting UE-level measurement results on the UDM, and this trace job is managed by operations and notifications defined for the general supply management service as the MOI (MOI of the TraceJob IOC) (see clause 11.1.1 of 3GPP TS28.532). Specifically, the MnS consumer can use CreateMOI, getMOIAttributes, modifyMOIAttributes, deleteMOI to manage the MOI of the trace job representing the UE measurement job (create, obtain, modify, delete the attributes of the MOI), and receive corresponding notifications (notifyMOICreation, notifyMOIDeletion, notifyMOIAttributeValueChanges, notifyMOIChanges, notifyEvent).

[0208] The TraceJob IOC (defined in 3GPP TS28.622 V18.5.0 (2023-12) (3rd Generation Partnership Project; Technical Specification Group on Services and Systems Aspects; Telecommunications Management; General Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) (Release 18))) is enhanced to include configuration parameters for UE-level measurement.

[0209] 7.1.1.1 TraceJob

[0210] 7.1.1.1.1 Definition

[0211] A TraceJob instance represents the trace control and configuration parameters of a specific trace job (see 3GPP TS32.421 V18.1.0 (2023-12) (3rd Generation Partnership Project; Technical Specification Group on Services and Systems Aspects; Telecommunications Management; User and Equipment Trace; Trace Concepts and Requirements (Release 18)) and TS32.422). It can be name-contained by SubNetwork, ManagedElement, and ManagedFunction. If the trace activation is signaling-based, it should be name-contained by the UDM.

[0212] To activate a trace job, an MnS consumer can create an instance of a trace job object on an MnS producer. An MnS consumer can activate a trace job for another MnS consumer, as it is not required that the values of traceCollectionEntityIPAddress or traceReportingConsumerUri be its own.

[0213] When an MnS consumer wishes to deactivate a trace job, the MnS consumer can delete the corresponding TraceJob instance.

[0214] The attribute traceReference specifies a globally unique ID and identifies a trace session. A trace session can be activated for multiple network elements. traceReference is filled in by the consumer that requests the trace session (e.g., see TS32.422).

[0215] The jobId attribute represents the job identifier of a TraceJob instance. The jobId can be used to correlate multiple TraceJob instances. For example, the same jobId value can be configured for multiple desired TraceJob instances to generate data for a specific network analysis (e.g., RSRP values for M1 and RLF reports).

[0216] The attribute traceReportingFormat defines the method for reporting the generated measurement results. The options can include file-based reporting and stream-based reporting. In file-based reporting, the attribute traceCollectionEntityIPAddress is used to specify the IP address to which the trace records should be transferred, while in stream-based reporting, the attribute traceReportingConsumerUri specifies the streaming target.

[0217] The mandatory attribute traceTarget determines the target object of the TraceJob. Depending on the network element for which the trace session is activated, there can be different types of target objects. The attribute pLMNTarget defines the PLMN in the case of administratively-based activation when the RAN supports multiple PLMNs, for which the session will be selected in the trace session.

[0218] The attribute jobType specifies the type of data to be collected. Only in the case of tracing, the configuration parameters of the attribute traceConfig should be applied. In the cases of Immediate MDT only, Logged MDT only, RLF report only, RCEF report only, and Logged MBSFN MDT, the configuration parameters of the attribute mdtConfig or its subset should be applied. If only UE measurements are performed, the configuration parameters of the attribute ueMeasConfig should be applied. If it is any combination of tracing, Immediate MDT Trace, and UE measurements, the corresponding configuration parameters of the attributes traceConfig, mdtConfig, and ueMeasConfig are applicable.

[0219] MnS consumers are optional for the creation and deletion of TraceJob instances; when not supported, TraceJob instances can be created and deleted by the system or pre-installed.

[0220] 7.1.1.1.2 Attributes

[0221] The TraceJob IOC includes the attributes inherited from the Top IOC (defined in clause 4.3.29 of TS28.622) and the following attributes. In this document, the Support Qualifier (hereinafter referred to as S) of an attribute can be Mandatory (hereinafter referred to as M), Optional (hereinafter referred to as O), Conditionally Optional (hereinafter referred to as CO), or Conditionally Mandatory (hereinafter referred to as CM). "T" represents True and "F" represents False.

[0222] Attribute Name S Readable Writable Variable Notifyable jobType M T T F T pLMNTarget CM T T F T traceReportingConsumerUri CM T T F T traceCollectionEntityIPAddress CM T T F T traceReference M T T F T jobId O T T T T traceReportingFormat M T T F T traceTarget M T T F T traceConfig CM T T F T mdtConfig CM T T F T ueMeasConfig CM T T F T nPNTarget CM T T F T

[0223] 7.1.1.1.3 Attribute Constraints

[0224]

[0225] 7.1.1.2 UEMeasConfig< <datatype>>

[0226] 7.1.1.2.1 Definition

[0227] The < <datatype>>Defines the configuration parameters of the IOC TraceJob, which are specifically used for UE-level measurement result collection.

[0228] The attribute ueMeasurements defines the measurements to be generated, and the attribute ueGranularityPeriod defines the granularity period to be applied.

[0229] All of the following object instances that include the instance of the named TraceJob (basic object instance) fall within the scope of measurement result collection and measurement generation. UE-level measurements are generated only on object instances whose object class matches the object class associated with the measurements to be generated.

[0230] The optional attributes objectInstances and rootObjectInstances allow the scope to be restricted. When the attribute objectInstances exists, only the object instances identified by this attribute are within the scope. When the rootObjectInstances attribute exists, the subordinate objects of the root object identified by this attribute are also within the scope. These two attributes can exist simultaneously, which means the total scope is equal to the sum of the two scopes. An object instance can be included in the scope by both the objectInstances and rootObjectInstances attributes. When these two attributes exist simultaneously, the MnS producer does not consider it an error.

[0231] In some embodiments, changes to all other configurable attributes can only take effect at the start of the next granularity period. In some other embodiments, changes to all other configurable attributes will take effect immediately. The present disclosure does not impose a limitation in this regard.

[0232] 7.1.1.2.2 Attributes

[0233] Attribute Name S Readable Writable Variable Notifyable ueMeasurements CM T T F T ueMeasGranularityPeriod CM T T F T objectInstances O T T F T rootObjectInstances O T T F T

[0234] 7.1.1.2.3 Attribute Constraints

[0235] Name Definition ueMeasurements(CM S) This attribute appears only if UE-level measurement result collection is supported. ueMeasGranularityPeriod(CM S) This attribute appears only if UE-level measurement result collection is supported.

[0236] 7.1.1.3 Attribute Characteristics

[0237]

[0238]

[0239]

[0240] Some embodiments will be described below to illustrate the 5GC activation mechanism for UE-level measurement jobs.

[0241] 7.1.2 5GC Activation Mechanism for UE-Level Measurement Operations

[0242] Figures 11 - 17 Example procedures for signaling activation of UE-level measurement operations according to some embodiments of the present disclosure are shown respectively.

[0243] 7.1.2.1 UE Attaches to 5GC via NG-RAN

[0244] The UE-level measurement operation activation reuses the 5GC trace activation process described in clause 4.1.2.15 of TS 32.422. When the trace session is activated, the configuration parameters for UE-level measurement are added to the message.

[0245] Figure 11 An example procedure for signaling trace session activation for UE-level measurement operations in 5GC is shown, which is part of the PDU session establishment process for a registered UE. As shown, the example procedure may include the following operations or steps.

[0246] 1. The management system activates a trace session with the UDM. The following configuration parameters for UE-level measurement operations shall be included in the trace activation message:

[0247] - Trace target: SUPI or IMEISV;

[0248] - Trace reference;

[0249] - Trace report format;

[0250] - UE-level measurement configuration list, which includes:

[0251] - NE type for measurement;

[0252] - UE-level measurement list for the specified NE type (measurement types defined by entry e) of UE-level measurement specified in 3GPP TS28.558 V0.1.0 (2023-11) (3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Management and Coordination; User Equipment (UE) Level Measurement in 5G Systems (Release 18))).

[0253] - UE-level measurement granularity period (see ueMeasGranularityPeriod defined in TS28.622).

[0254] - IP address of the trace collection entity for file-based trace reports or URI of the trace report consumer for streaming trace reports.

[0255] 2. The UDM stores the configuration parameters of the UE-level measurement operation received from the management system.

[0256] 3. The UDM sends a Nudm_SDM_Notification message to the AMF, which contains the configuration parameter information of the UE-level measurement job (see Article 4.5.1 and Article 5.2.3.3 of 3GPP TS23.502 V18.4.0 (2023-12) (3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Procedures for 5G System (5GS); Stage 2 (18th Edition))).

[0257] 4. The AMF stores the configuration parameters of the UE-level measurement job received from the UDM.

[0258] 5. The AMF starts a tracking session according to the received configuration.

[0259] 6. The UE sends a PDU session establishment request to the AMF.

[0260] 7. The AMF sends a start tracking message through the NG interface (N2 interface from the perspective of 5GC).

[0261] 8. The NG-RAN node stores the configuration parameters of the UE-level measurement job received from the AMF. This step is part of the activation of NG-RAN signaling tracking - see Article 4.1.2.16 for details.

[0262] 9. The NG-RAN node starts a tracking session according to the received configuration. This step is part of the activation of NG-RAN signaling tracking - see Article 4.1.2.16 for details.

[0263] 10. The AMF selects an appropriate SMF.

[0264] 11. The AMF sends a Nsmf_PDUSession_CreateSMContext request to the selected SMF, which contains the configuration parameters of the UE-level measurement job.

[0265] 12. The SMF stores the configuration parameters of the UE-level measurement job received from the AMF.

[0266] 13. The SMF starts a tracking session according to the received configuration.

[0267] 14. The SMF selects an appropriate PCF.

[0268] 15. The SMF establishes a session management policy association with the PCF (see step 7 in Article 4.3.2.2.1 of 3GPP TS23.502), and provides the configuration parameter information of the UE-level measurement job to the PCF.

[0269] 16. As part of policy association, the PCF stores the configuration parameters of the UE-level measurement job received from the SMF.

[0270] 17. The PCF starts a tracing session according to the received configuration.

[0271] 18. The SMF selects an appropriate UPF.

[0272] 19. The SMF performs N4 session establishment with the UPF (see step 10 in clause 4.3.2.2.1 of 3GPP TS 23.502), and provides the UPF with the configuration parameter information of the UE-level measurement job.

[0273] 20. As part of the N4 session establishment, the UPF stores the configuration parameters of the UE-level measurement job received from the SMF.

[0274] 21. The UPF starts a tracing session according to the received configuration.

[0275] Figure 11 The example process of Figure 4 .1.2.15.1.2 (which Figure 4 .1.2.15.1.2 shows the signaling tracing session activation process in 5GC as part of the PDU session establishment process for a registered UE) is similar, but the configuration parameters of the UE-level measurement job replace the tracing control and configuration parameters in the process of Figure 4 .1.2.15.1.2.

[0276] According to Figure 11 , the 5GC NF and the NG-RAN node (if it appears as the NE type for measurement in the UE measurement configuration parameters) start a tracing session and UE-level measurement generation according to the received configuration at step 5, step 9, step 13, step 17, and step 21.

[0277] Figure 12 shows an example process of signaling tracing session activation for a UE-level measurement job in 5GC, which is part of the PDU session establishment process for a registered UE. In the Figure 11 example process, the SMF obtains the configuration parameters of the UE-level measurement job from the AMF. In contrast, in the Figure 12 example process, the SMF obtains the configuration parameters of the UE-level measurement job from the UDM via the Nudm_UECM_Registration process. As shown, the Figure 12 example process may include the following operations or steps.

[0278] 1. The management system activates a trace session with the UDM. The trace activation message shall include the following configuration parameters for UE-level measurement jobs:

[0279] - Trace target: SUPI or IMEISV;

[0280] - Trace reference;

[0281] - Trace report format;

[0282] - UE-level measurement configuration list, which includes:

[0283] - NE type for measurement;

[0284] - UE-level measurement list for the specified NE type (measurement types defined by entry e of UE-level measurements specified in TS28.558).

[0285] - UE-level measurement granularity period (see ueMeasGranularityPeriod defined in TS28.622).

[0286] - IP address of the trace collection entity for file-based trace reports or URI of the trace report consumer for streaming trace reports.

[0287] 2. The UDM stores the configuration parameters of the UE-level measurement job received from the management system.

[0288] 3. The UDM sends a Nudm_SDM_Notification message to the AMF, which contains the configuration parameter information of the UE-level measurement job (see Article 4.5.1 and Article 5.2.3.3 of TS23.502).

[0289] 4. The AMF stores the configuration parameters of the UE-level measurement job received from the UDM.

[0290] 5. The AMF starts a trace session according to the received configuration.

[0291] 6. The UE sends a PDU session establishment request to the AMF.

[0292] 7. The AMF sends a start trace message through the NG interface (N2 interface from the perspective of 5GC).

[0293] 8. The NG-RAN node stores the configuration parameters of the UE-level measurement job received from the AMF. This step is part of the activation of NG-RAN signaling trace - see Article 4.1.2.16 for details.

[0294] 9. The NG-RAN node starts a tracing session according to the received configuration. This step is part of the activation of NG-RAN signaling tracing - see clause 4.1.2.16 for details.

[0295] 10. The AMF selects an appropriate SMF.

[0296] 11. The AMF sends an Nsmf_PDUSession_CreateSMContext request to the selected SMF.

[0297] 12. The SMF executes the NuDM_UECM_Registration procedure with the UDM and receives the configuration parameters for the UE-level measurement job from the UDM.

[0298] 13. The SMF stores the configuration parameters for the UE-level measurement job received from the UDM.

[0299] 14. The SMF starts a tracing session according to the received configuration.

[0300] 15. The SMF selects an appropriate PCF.

[0301] 16. The SMF establishes a session management policy association with the PCF (see step 7 in clause 4.3.2.2.1 of 3GPP TS 23.502), and provides the PCF with the configuration parameter information for the UE-level measurement job.

[0302] 17. As part of the policy association, the PCF stores the configuration parameters for the UE-level measurement job received from the SMF.

[0303] 18. The PCF starts a tracing session according to the received configuration.

[0304] 19. The SMF selects an appropriate UPF.

[0305] 20. The SMF executes an N4 session establishment with the UPF (see step 10 in clause 4.3.2.2.1 of 3GPP TS 23.502), and provides the UPF with the configuration parameter information for the UE-level measurement job.

[0306] 21. As part of the N4 session establishment, the UPF stores the configuration parameters for the UE-level measurement job received from the SMF.

[0307] 22. The UPF starts a tracing session according to the received configuration.

[0308] Figure 12 The example process of Figure 4 .1.2.15.1.3 (this Figure 4 .1.2.15.1.3 shows the signaling trace session activation process in 5GC as part of the PDU session establishment process for a registered UE, where the SMF obtains trace control and configuration parameters from the UDM via the Nudm_UECM_Registration process) is similar, but the configuration parameters for UE-level measurement jobs replace those in TS 32.422 Figure 4 the trace control and configuration parameters in the process of.1.2.15.1.3.

[0309] According to Figure 12 , the 5GC NF and the NG-RAN node (if it appears as the NE type for measurement in the UE measurement configuration parameters) start the trace session and UE-level measurement generation according to the received configuration at steps 5, 9, 14, 18, and 22..

[0310] Figure 13 shows an example process of signaling trace session activation for UE-level measurement jobs in 5GC, which is part of the PDU session modification process for a registered UE with an ongoing PDU session. As shown, the example process may include the following operations or steps.

[0311] 1. The management system activates a trace session with the UDM. The trace activation message shall contain the following configuration parameters for UE-level measurement jobs:

[0312] - Trace target: SUPI or IMEISV;

[0313] - Trace reference;

[0314] - Trace report format;

[0315] - UE-level measurement configuration list, which includes:

[0316] - NE type for measurement;

[0317] - UE-level measurement list for the specified NE type (measurement types defined by entry e of UE-level measurements specified in TS28.558).

[0318] - UE-level measurement granularity period (see ueMeasGranularityPeriod defined in TS28.622).

[0319] - IP address of the trace collection entity for file-based trace reports or URI of the trace report consumer for streaming trace reports.

[0320] 2. The UDM stores the configuration parameters of the UE-level measurement job received from the management system.

[0321] 3. The UDM sends a Nudm_SDM_Notification message to the AMF, which contains the configuration parameter information of the UE-level measurement job (see Articles 4.5.1 and 5.2.3.3 of TS 23.502).

[0322] 4. The AMF stores the configuration parameters of the UE-level measurement job received from the UDM.

[0323] 5. The AMF starts a tracing session according to the received configuration.

[0324] 6. The AMF sends a Nsmf_PDUSession_UpdateSMContext request with the configuration parameters of the UE-level measurement job to the SMF.

[0325] 7. The SMF stores the configuration parameters of the UE-level measurement job received from the AMF.

[0326] 8. The SMF starts a tracing session according to the received configuration.

[0327] 9. The SMF performs session management policy modification with the PCF (see step 7 in Article 4.3.3.2 of 3GPP TS 23.502), and provides the configuration parameter information of the UE-level measurement job to the PCF.

[0328] 10. As part of the policy association, the PCF stores the configuration parameters of the UE-level measurement job received from the SMF.

[0329] 11. The PCF starts a tracing session according to the received configuration.

[0330] 12. The SMF performs N4 session modification with the UPF (see step 10 in Article 4.3.2.2.1 of 3GPP TS 23.502), and provides the configuration parameter information of the UE-level measurement job to the UPF.

[0331] 13. As part of the N4 session modification, the UPF stores the configuration parameters of the UE-level measurement job received from the SMF.

[0332] 14. The UPF starts a tracing session according to the received configuration.

[0333] 15. The AMF sends a start tracing message through the NG interface (N2 interface from the perspective of 5GC).

[0334] 16. The NG-RAN node stores the configuration parameters of the UE-level measurement job received from the AMF. This step is part of the activation of NG-RAN signaling tracing - see Article 4.1.2.16 for details.

[0335] 17. The NG-RAN node starts a tracing session according to the received configuration. This step is part of the activation of NG-RAN signaling tracing - see Article 4.1.2.16 for details.

[0336] Figure 13 The example process of is similar to that of TS 32.422 Figure 4 .1.2.15.1.4 (this Figure 4 .1.2.15.1.4 shows the signaling tracing session activation process in the 5GC as part of the PDU session modification process for a UE that has been registered and has an ongoing PDU session), but the configuration parameters of the UE-level measurement job replace the tracing control and configuration parameters in the process of TS 32.422 Figure 4 .1.2.15.1.4.

[0337] According to Figure 13 , the 5GC NF and the NG-RAN node (if it appears as the NE type for measurement in the UE measurement configuration parameters) start a tracing session and generate UE-level measurements according to the received configuration at steps 5, 8, 11, 14, and 17.

[0338] Figure 14 shows an example process of signaling tracing session activation for UE-level measurement jobs in the 5GC, which is part of the PDU session modification process for a UE that has been registered and has an ongoing PDU session. In Figure 13 's example process, the SMF obtains the configuration parameters of the UE-level measurement job from the AMF. In contrast, in Figure 14 's example process, the SMF obtains the configuration parameters of the UE-level measurement job from the UDM via the Nudm_SDM_Notification message. As shown in the figure, Figure 14 's example process may include the following operations or steps.

[0339] 1. The management system activates a tracing session with the UDM. The following configuration parameters for the UE-level measurement job shall be included in the tracing activation message:

[0340] - Tracing target: SUPI or IMEISV;

[0341] - Tracing reference;

[0342] - Tracing report format;

[0343] - UE-level measurement configuration list, which includes:

[0344] - NE type for measurement;

[0345] - List of UE-level measurements for the specified NE type (measurement types defined by entry e of UE-level measurements specified in TS28.558).

[0346] - UE-level measurement granularity period (see ueMeasGranularityPeriod defined in TS28.622).

[0347] - IP address of the trace collection entity for file-based trace reports or URI of the trace report consumer for streaming trace reports.

[0348] 2. The UDM stores the configuration parameters of the UE-level measurement job received from the management system.

[0349] 3. The UDM sends a Nudm_SDM_Notification message to the AMF, which contains the configuration parameter information of the UE-level measurement job (see clauses 4.5.1 and 5.2.3.3 of TS23.502).

[0350] 4. The AMF stores the configuration parameters of the UE-level measurement job received from the UDM.

[0351] 5. The AMF starts a trace session according to the received configuration.

[0352] 6. The UDM sends a Nudm_SDM_Notification message with the configuration parameter information of the UE-level measurement job to the SMF (see clauses 4.5.2 and 5.2.3.3 of TS23.502).

[0353] 7. The SMF stores the configuration parameters of the UE-level measurement job received from the UDM.

[0354] 8. The SMF starts a trace session according to the received configuration.

[0355] 9. The SMF performs session management policy modification with the PCF (see step 7 in clause 4.3.3.2 of 3GPP TS23.502), and provides the configuration parameter information of the UE-level measurement job to the PCF.

[0356] 10. As part of the policy association, the PCF stores the configuration parameters of the UE-level measurement job received from the SMF.

[0357] 11. The PCF starts a trace session according to the received configuration.

[0358] 12. The SMF performs N4 session modification with the UPF (see step 10 in clause 4.3.2.2.1 of 3GPP TS23.502), and provides the configuration parameter information of the UE-level measurement job to the UPF.

[0359] 13. As part of the N4 session modification, the UPF stores the configuration parameters of the UE-level measurement job received from the SMF.

[0360] 14. The UPF starts a trace session according to the received configuration.

[0361] 15. The AMF sends a start trace message through the NG interface (N2 interface from the perspective of 5GC).

[0362] 16. The NG-RAN node stores the configuration parameters of the UE-level measurement job received from the AMF. This step is part of the activation of NG-RAN signaling trace - see Article 4.1.2.16 for details.

[0363] 17. The NG-RAN node starts a trace session according to the received configuration. This step is part of the activation of NG-RAN signaling trace - see Article 4.1.2.16 for details.

[0364] Figure 14 The example process is similar to that of TS 32.422's Figure 4 .1.2.15.1.5 (this Figure 4 .1.2.15.1.5 shows the signaling trace session activation process in 5GC as part of the PDU session modification process for a UE that has been registered and has an ongoing PDU session), but the configuration parameters of the UE-level measurement job replace the trace control and configuration parameters in the process of TS 32.422's Figure 4 .1.2.15.1.5.

[0365] According to Figure 14 , the 5GC NF and the NG-RAN node (if it appears as the NE type for measurement in the UE measurement configuration parameters) start a trace session and generate UE-level measurements according to the received configuration at steps 5, 8, 11, 14, and 17.

[0366] 7.1.2.2 Inter-RAT handover between E-UTRAN and NG-RAN

[0367] Figure 15 shows the case where a UE served by 5GC with an ongoing PDU session and an active trace session performs an inter-RAT handover from NG-RAN to E-UTRAN and then back from E-UTRAN to NG-RAN.

[0368] As shown in the figure, the example process may include operations or steps 1 to 25. Figure 15 Steps 1, 2, 5, 8, 11, and 13 - 21 in [document] are part of the EPS to 5GS handover procedure using the N26 interface (for specific details, see clause 4.11.1.2.2 of 3GPP TS23.502). This disclosure does not attempt to re - define the working method of the EPS to 5GS handover procedure using the N26 interface, but rather explains the activation of signaling tracing.

[0369] When the MME sends a forward relocation request to the AMF, the MME shall include the following configuration parameters for tracing activation for UE - level measurement jobs:

[0370] - Tracing target: SUPI or IMEISV;

[0371] - Tracing reference;

[0372] - Tracing report format;

[0373] - UE - level measurement configuration list, which includes:

[0374] - NE type for measurement;

[0375] - UE - level measurement list for the specified NE type (measurement types defined by entry e of UE - level measurements specified in TS28.558).

[0376] - UE - level measurement granularity period (see ueMeasGranularityPeriod defined in TS28.622).

[0377] - IP address of the trace collection entity for file - based trace reports or URI of the trace report consumer for streaming trace reports.

[0378] Figure 15 The example procedure of [document] is the same as that of Figure 4 .1.2.15.2.2( Figure 4 .1.2.15.2.2 shows the activation of signaling tracing during the inter - RAT handover from E - UTRAN to NG - RAN), but the configuration parameters of the UE - level measurement job replace the trace control and configuration parameters in the procedure of Figure 4 .1.2.15.2.2 of

[0379] According to Figure 15 , the 5GC NF and NG - RAN nodes (if they appear as the NE type for measurement in the UE measurement configuration parameters) start trace sessions and UE - level measurement generation according to the received configuration at steps 4, 7, 10, 12, and 15.

[0380] 7.1.2.3 Non - 3GPP access scenario

[0381] Figure 16 Shows an example process for activating a signaling trace session for UE-level measurement operations in the 5GC, as part of the PDU session establishment process for a registered UE via untrusted non-3GPP access. As shown, the example process may include the following operations or steps.

[0382] 1. The management system activates a trace session with the UDM. The trace activation message shall contain the following configuration parameters for UE-level measurement operations:

[0383] - Trace target: SUPI or IMEISV;

[0384] - Trace reference;

[0385] - Trace report format;

[0386] - UE-level measurement configuration list, which includes:

[0387] - NE type for measurement;

[0388] - UE-level measurement list for the specified NE type (measurement types defined by entry e of UE-level measurements specified in TS28.558).

[0389] - UE-level measurement granularity period (see ueMeasGranularityPeriod defined in TS28.622).

[0390] - IP address of the trace collection entity for file-based trace reports or URI of the trace report consumer for streaming trace reports.

[0391] 2. The UDM stores the configuration parameters of the UE-level measurement operation received from the management system.

[0392] 3. The UDM sends a Nudm_SDM_Notification message to the AMF, which contains the configuration parameter information of the UE-level measurement operation (see clauses 4.5.1 and 5.2.3.3 of TS23.502).

[0393] 4. The AMF stores the configuration parameters of the UE-level measurement operation received from the UDM.

[0394] 5. The AMF starts a trace session according to the received configuration.

[0395] 6. Information exchanged between the UE and the AMF shall be sent to the N3IWF via the IPsec SA for NAS signaling established in accordance with clause 4.12.2 of 3GPP TS23.502.

[0396] 7. The UE sends a PDU session establishment request to the AMF.

[0397] 8. The AMF selects an appropriate SMF.

[0398] 9. The AMF sends an Nsmf_PDUSession_CreateSMContext request to the selected SMF.

[0399] 10. The SMF stores the configuration parameters of the UE-level measurement job received from the AMF.

[0400] 11. The SMF starts a trace session according to the received configuration.

[0401] 12. The SMF selects a suitable PCF.

[0402] 13. The SMF establishes a session management policy association with the PCF (see step 7 in clause 4.3.2.2.1 of 3GPP TS23.502), and provides the PCF with the configuration parameter information of the UE-level measurement job.

[0403] 14. As part of the policy association, the PCF stores the configuration parameters of the UE-level measurement job received from the SMF.

[0404] 15. The PCF starts a trace session according to the received configuration.

[0405] 16. The SMF performs N4 session establishment with the UPF (see step 10 in clause 4.3.2.2.1 of 3GPP TS23.502), and provides the UPF with the configuration parameter information of the UE-level measurement job.

[0406] 17. As part of the N4 session establishment, the UPF stores the configuration parameters of the UE-level measurement job received from the SMF.

[0407] 18. The UPF starts a trace session according to the received configuration.

[0408] 19. The AMF sends an N2 PDU session request to the N3IWF.

[0409] 20. The N3IWF determines the necessary number of IPsec sub-SAs and establishes these IPsec sub-SAs with the UE.

[0410] 21. The N3IWF sends a PDU session establishment acceptance to the UE.

[0411] 22. The N3IWF sends an N2 PDU session request confirmation to the AMF.

[0412] Figure 16 The example process of Figure 4 .1.2.15.3.2 (This Figure 4 .1.2.15.3.2 shows the signaling trace session activation process in 5GC, which is similar to the PDU session establishment process for a registered UE via untrusted non-3GPP access, but the configuration parameters of the UE-level measurement task replace the trace control and configuration parameters in Figure 4 .1.2.15.3.2's process.)

[0413] According to Figure 16 , the 5GC NF and the NG-RAN node (if it appears as the NE type for measurement in the UE measurement configuration parameters) start the trace session and UE-level measurement generation according to the received configuration at steps 5, 11, 15, and 18.

[0414] Figure 17 shows an example process of signaling trace session activation for UE-level measurement tasks in 5GC, which is part of the PDU session establishment process for a registered UE via untrusted non-3GPP access. In Figure 16 's example process, the SMF obtains the configuration parameters of the UE-level measurement task from the AMF. In contrast, in Figure 17 's example process, the SMF obtains the configuration parameters of the UE-level measurement task from the UDM through the Nudm_UECM_Registration process. As shown in the figure, Figure 17 's example process may include the following operations or steps.

[0415] 1. The management system activates a trace session with the UDM. The trace activation message should include the following configuration parameters for the UE-level measurement task:

[0416] - Trace target: SUPI or IMEISV;

[0417] - Trace reference;

[0418] - Trace report format;

[0419] - UE-level measurement configuration list, which includes:

[0420] - NE type for measurement;

[0421] - UE-level measurement list for the specified NE type (measurement types defined by entry e of UE-level measurements specified in TS28.558).

[0422] - UE-level measurement granularity period (see ueMeasGranularityPeriod defined in TS28.622).

[0423] - The IP address of the trace collection entity for file - based trace reports or the URI of the trace report consumer for streaming trace reports.

[0424] 2. The UDM stores the configuration parameters of the UE - level measurement job received from the management system.

[0425] 3. The UDM sends a Nudm_SDM_Notification message to the AMF, which contains the configuration parameter information of the UE - level measurement job (see clauses 4.5.1 and 5.2.3.3 of TS 23.502).

[0426] 4. The AMF stores the configuration parameters of the UE - level measurement job received from the UDM.

[0427] 5. The AMF starts a trace session according to the received configuration.

[0428] 6. The information exchanged between the UE and the AMF shall be sent to the N3IWF through the IPsec SA for NAS signaling established in accordance with clause 4.12.2 of 3GPP TS 23.502.

[0429] 7. The UE sends a PDU session establishment request to the AMF.

[0430] 8. The AMF selects an appropriate SMF.

[0431] 9. The AMF sends a Nsmf_PDUSession_CreateSMContext request to the selected SMF.

[0432] 10. The SMF executes the NuDM_UECM_Registration procedure with the UDM and receives the configuration parameters of the UE - level measurement job from the UDM.

[0433] 11. The SMF stores the configuration parameters of the UE - level measurement job received from the UDM.

[0434] 12. The SMF starts a trace session according to the received configuration.

[0435] 13. The SMF selects a suitable PCF.

[0436] 14. The SMF establishes a session management policy association with the PCF (see step 7 in clause 4.3.2.2.1 of 3GPP TS 23.502) and provides the configuration parameter information of the UE - level measurement job to the PCF.

[0437] 15. As part of the policy association, the PCF stores the configuration parameters of the UE - level measurement job received from the SMF.

[0438] 16. The PCF starts a tracing session according to the received configuration.

[0439] 17. The SMF executes N4 session establishment with the UPF (see step 10 in clause 4.3.2.2.1 of 3GPP TS 23.502), and provides the configuration parameter information of the UE-level measurement job to the UPF.

[0440] 18. As part of the N4 session establishment, the UPF stores the configuration parameters of the UE-level measurement job received from the SMF.

[0441] 19. The UPF starts a tracing session according to the received configuration.

[0442] 20. The AMF sends an N2 PDU session request to the N3IWF.

[0443] 21. The N3IWF determines the necessary number of IPsec sub-SAs and establishes these IPsec sub-SAs with the UE.

[0444] 22. The N3IWF sends a PDU session establishment acceptance to the UE.

[0445] 23. The N3IWF sends an N2 PDU session request confirmation to the AMF.

[0446] Figure 17 The example process of Figure 4 .1.2.15.3.3 (this Figure 4 .1.2.15.3.3 shows the signaling tracing session activation process in the 5GC, which is part of the PDU session establishment process for a registered UE through untrusted non-3GPP access) is similar, but the configuration parameters of the UE-level measurement job replace the tracing control and configuration parameters in the process of Figure 4 .1.2.15.3.3.

[0447] According to Figure 17 , the 5GC NF and the NG-RAN node (if it appears as the NE type for measurement in the UE measurement configuration parameters) start a tracing session and UE-level measurement generation according to the received configuration at step 5, step 12, step 16, and step 19.

[0448] Some embodiments will be described below to illustrate the NG-RAN activation mechanism for UE-level measurement jobs.

[0449] 7.1.3 NG-RAN Activation Mechanism for UE-Level Measurement Jobs

[0450] The UE-level measurement job activation in NG-RAN reuses the NG-RAN trace activation process described in clause 4.1.2.16 of TS 32.422, but the TRACE START, INITIALCONTEXT SETUP REQUEST, or HANDOVER REQUEST message received from the AMF contains the following configuration parameters for the UE-level measurement job:

[0451] - Trace target: SUPI or IMEISV;

[0452] - Trace reference;

[0453] - Trace report format;

[0454] - UE-level measurement configuration list, which includes:

[0455] - NE type for measurement;

[0456] - UE-level measurement list for the specified NE type (measurement types defined by entry e of UE-level measurements specified in TS 28.558).

[0457] - UE-level measurement granularity period (see ueMeasGranularityPeriod defined in TS 28.622).

[0458] - IP address of the trace collection entity for file-based trace reports or URI of the trace report consumer for streaming trace reports.

[0459] Some embodiments will be described below to illustrate the 5GC deactivation mechanism for UE-level measurement jobs. Figure 18 and Figure 19 respectively show example processes for signaling to deactivate UE-level measurement jobs according to some embodiments of the present disclosure.

[0460] 7.1.4 5GC Deactivation Mechanism for UE-Level Measurement Jobs

[0461] In 5GC, the signaling deactivation mechanism for UE-level measurement jobs is similar to the signaling deactivation mechanism for traces defined in clause 4.1.4.11 of TS 32.422, but changes the trace task and trace configuration parameters to configuration parameters for UE-level measurement result collection.

[0462] Figure 18 Shows an example of the signaling trace session deactivation process in 5GC. As shown, the example process may include the following operations or steps.

[0463] 1. The management system deactivates the trace session to the UDM.

[0464] 2. The UDM sends an Nudm_SDM_Notification message containing trace deactivation information to the AMF (see clause 5.2.3.3.3 of 3GPP TS 23.502).

[0465] 3. The AMF deactivates the trace session based on the received information.

[0466] 4. The AMF sends a DEACTIVATE TRACE message through the NG interface (N2 interface from the perspective of 5GC).

[0467] 5. The NG-RAN node deactivates the trace session based on the information received from the AMF. This step is part of the NG-RAN signaling trace deactivation - see clause 4.1.2.12 for details.

[0468] 6. The AMF sends an Nsmf_PDUSession_UpdateSMContext request to the SMF.

[0469] 7. The SMF deactivates the trace session based on the received information.

[0470] 8. The SMF performs session management policy modification with the PCF (see step 7 in clause 4.3.3.2 of 3GPP TS 23.502) and provides trace deactivation information to the PCF.

[0471] 9. The PCF deactivates the trace session based on the received information.

[0472] 10. The SMF performs N4 session modification with the UPF (see step 10 in clause 4.3.3.2 of 3GPP TS 23.502) and provides trace deactivation information to the UPF.

[0473] 11. The UPF deactivates the trace session based on the received information.

[0474] Figure 19 An example of the signaling trace session deactivation process in 5GC is shown. As shown, the example process may include the following operations or steps. In Figure 18 the example process, the SMF obtains trace session deactivation information from the AMF. In contrast, in Figure 19 the example process, the SMF obtains trace session deactivation information from the UDM. As shown, Figure 19 the example process may include the following operations or steps.

[0475] 1. The management system deactivates the trace session with the UDM.

[0476] 2. The UDM sends an Nudm_SDM_Notification message containing trace deactivation information to the AMF (see clause 5.2.3.3.3 of 3GPP TS 23.502).

[0477] 3. The AMF deactivates the trace session based on the received information.

[0478] 4. The AMF sends a DEACTIVATE TRACE message via the NG interface (N2 interface from the perspective of 5GC).

[0479] 5. The NG-RAN node deactivates the trace session based on the information received from the AMF. This step is part of the NG-RAN signaling trace deactivation - see clause 4.1.2.12 for details.

[0480] 6. The UDM sends an Nudm_SDM_Notification message with trace deactivation information to the SMF (see clause 5.2.3.3.3 of 3GPP TS 23.502).

[0481] 7. The SMF deactivates the trace session based on the received information.

[0482] 8. The SMF performs session management policy modification with the PCF (see step 7 in clause 4.3.3.2 of 3GPP TS 23.502) and provides the trace deactivation information to the PCF.

[0483] 9. The PCF deactivates the trace session based on the received information.

[0484] 10. The SMF performs N4 session modification with the UPF (see step 10 in clause 4.3.3.2 of 3GPP TS 23.502) and provides the trace deactivation information to the UPF.

[0485] 11. The UPF deactivates the trace session based on the received information.

[0486] Some embodiments will be described below to illustrate the NG-RAN deactivation mechanism for UE-level measurement operations.

[0487] 7.1.5 NG-RAN Deactivation Mechanism for UE-Level Measurement Operations

[0488] In the NG-RAN, the signaling deactivation mechanism for UE-level measurement operations is the same as the signaling deactivation mechanism for tracing defined in clause 4.1.4.12 of TS 32.422, but the tracing operations and tracing configuration parameters are changed to the configuration parameters for UE-level measurement result collection.

[0489] There may be different events for deactivating a trace session. In some embodiments, when the NG-RAN node receives a DEACTIVATE TRACE message using the NG interface, it shall deactivate the trace session for the specified trace reference. In some embodiments, when the NG-RAN node releases the UE context, the trace recording session shall be stopped and the trace session shall be deactivated at the NG-RAN node.

[0490] In some embodiments, if the NG-RAN node is unable to deactivate the trace session because it is handing over the UE to another NG-RAN node, the NG-RAN node shall use the NG interface to notify the AMF with a TRACE FAILURE INDICATION message.

[0491] Some embodiments will be described below to illustrate the determination / stop triggering of the trace recording session for UE-level measurement jobs.

[0492] 7.2 Trace Recording Session Start / Stop Triggering for UE-Level Measurement Jobs

[0493] 7.2.1 5GC Initiation Mechanism for UE-Level Measurement Jobs

[0494] In some embodiments, in the 5GC NF, when the NF starts generating UE-level measurements in each granularity period according to the received trace session activation message, the trace recording session shall start.

[0495] In some embodiments, for each trace recording session (e.g., each granularity period), the 5GC generates UE-level measurements.

[0496] In some embodiments, if there is insufficient available resource for recording, the 5GC NF may not start the trace recording session.

[0497] In some embodiments, when starting the trace recording session, the 5GC NF shall allocate a trace recording session reference for the trace recording session.

[0498] In some embodiments, when the trace recording session ends (e.g., UE-level measurements are generated at the end of the granularity period), the 5GC NF shall send a trace record containing the results of the UE-level measurements to the TCE according to the UE-level measurement report specified in Article 7.3.

[0499] 7.2.2 NG-RAN Initiation Mechanism for UE-Level Measurement Jobs

[0500] In some embodiments, in the NG-RAN, when the NG-RAN starts generating UE-level measurements in each granularity period according to the received trace session activation message, the trace recording session shall start.

[0501] In some embodiments, in the case where the tracking target is a null value, after activating cell traffic tracking for UE-level measurement operations in one or more measured cells, the NG-RAN node shall start a tracking record session for each granularity period and for each measured UE.

[0502] In some embodiments, when multiple PLMNs are supported in the RAN, the NG-RAN node shall only select the UE that includes pLMNTarget = selectedPLMN-Identity in the RRCConnectionSetup message when starting to collect UE-level measurement results (see 3GPP TS 38.331 V17.6.0 (2023-09) (3rd Generation Partnership Project; Radio Access Network Technical Specification Group; NR; Radio Resource Control (RRC) Protocol Specification (Release 17))). When the tracking record session ends (i.e., UE-level measurements are generated at the end of the granularity period), the NG-RAN node sends a tracking record containing the UE-level measurement results to the TCE according to the UE-level measurement report specified in Clause 7.3.

[0503] In some embodiments, if there are not enough resources for recording, the NG-RAN node may not start a tracking record session. However, the NG-RAN node shall store the UE-level measurement configuration parameters and forward these parameters when the UE is switched to another NG-RAN node via Xn or when another NG-RAN node obtains the UE context via Xn.

[0504] In some embodiments, when the NG-RAN node obtains the UE-level measurement configuration parameters through one of the following messages, a tracking record session shall be started at the NG-RAN node:

[0505] 1) The INITIAL CONTEXT SETUP REQUEST message from the AMF via NG;

[0506] 2) The TRACE START message from the AMF via NG. If there is no UE-associated logical NG connection, the UE-associated logical NG connection will be established as part of the trace start process;

[0507] 3) The NG HANDOVER REQUEST message from the target AMF, as part of the AMF intra / inter handover process via NG;

[0508] 4) An Xn Handover Request message from the source NG-RAN node, as part of the NG-RAN node-to-node handover procedure via Xn;

[0509] 5) An Xn Retrieve UE Context Response message from the old NG-RAN node, after it has been sent to RRC_INACTIVE and then an RRC connection is established with the new NG-RAN node.

[0510] In some embodiments, for UE-level measurement result collection, the Tracking Reference Signal (TRSR) is not propagated during NG and Xn handovers.

[0511] 7.3 UE-level measurement reporting

[0512] In some embodiments, the results of UE-level measurements for each granularity period corresponding to each trace recording session are included in the trace recording and reported to the TCE. The UE-level measurement reporting mechanism is the same as the trace reporting mechanism specified in Clause 7 of TS 32.422, except that the trace recording includes the results of UE-level measurements.

[0513] With the technical solution of the present disclosure, signaling actions for UE-level measurement operations can be implemented by reusing and extending the trace mechanism.

[0514] Figure 20 An example functional framework 2000 for ML and / or RAN intelligence is depicted. The functional framework 2000 includes a data collection function 2005 that provides input data for a model training function 2010 and a model inference function 2015. AI / ML algorithm-specific data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) may or may not be performed in the data collection function 2005. Examples of input data may include: measurement results from UEs, RAN nodes, and / or additional or alternative network entities; feedback from an actor 2020; and / or (one or more) outputs from (one or more) ML models. The input data fed to the model training function 2010 is training data, and the input data fed to the model inference function 2015 is inference data.

[0515] The model training function 2010 is a function that performs ML model training, validation, and testing. As part of the model testing process and / or the model validation process, the model training function 2010 can generate model performance metrics. Examples of model performance metrics will be discussed below. If needed, the model training function 2010 can also be responsible for data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) based on the training data provided by the data collection function 2005.

[0516] The model training function 2010 performs model deployment / updating, where the model training function 2010 initially deploys the trained, validated, and tested ML model to the model inference function 2015, and / or delivers the updated model(s) to the model inference function 2015. Examples of model deployment and updating will be discussed below.

[0517] The model inference function 2015 is a function that provides ML model inference output (e.g., statistical inference, prediction, decision-making, probability and / or probability distribution, action, configuration, policy, data analysis, result, optimization, etc.). The model inference function 2015 can provide model performance feedback to the model training function 2010 when applicable. The model performance feedback can include various performance metrics related to generating the inference (e.g., any of the metrics discussed herein). The model performance feedback can be used to monitor the performance of the ML model when applicable. If needed, the model inference function 2015 can also be responsible for data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) based on the inference data provided by the data collection function 2005.

[0518] The model inference function 2015 generates inference output, i.e., the inference generated or otherwise produced when the model inference function 2015 operates on the ML model using the inference data. The model inference function 2015 provides the inference output to the actuator 2020. The details of the inference output are related to the specific use case and can be based on the specific type of ML model being used.

[0519] The actuator 2020 is a function that receives the inference output from the model inference function 2015 and triggers or otherwise performs corresponding operations based on the inference output. The actuator 2020 can trigger operations on other entities and / or itself. In some examples, the actuator 2020 is a NES function, a mobile optimization function, and / or a load balancing function. Additionally or alternatively, the inference output is related to NES, mobility optimization, and / or load balancing, and the actuator 2020 is one or more RAN nodes that perform various NES operations, mobility optimization operations, and / or load balancing operations based on the inference.

[0520] The actuator 2020 can also provide feedback to the data collection function 2005 for storage. The feedback includes information related to the actions performed by the actuator 2020. The feedback can include any information that may be required, which can be used to obtain training data (and / or test data and / or validation data), inference data, and / or data for monitoring the performance of the ML model and its impact on the network by updating KPIs, performance counters, etc.

[0521] Figure 21 Depicts an example AI / ML-assisted communication network including communication between ML functions (MLF) 2102 and MLF 2104. In some embodiments, ML models / entities can be used or utilized to facilitate wired and / or over-the-air communication between MLF 2102 and MLF 2104. In this embodiment, the operations of MLF 2102 and MLF 2104 comply with 3GPP technical specifications and / or technical reports of 5G and / or 6G systems, such as any of the technical reports discussed herein. In some examples, the communication mechanism between MLF 2102 and MLF 2104 includes any suitable access technology and / or RAT, such as any of the technologies and / or RATs discussed herein. Additionally, Figure 21 the communication mechanism in can be Figures 1 - 20 part of, or operate concurrently with, the other components, devices, systems, networks, and / or deployments described herein.

[0522] MLF 2102, 2104 can correspond to any entity / element discussed herein. In one example, MLF 2102 corresponds to MnF and / or MnS-P, and MLF 2104 corresponds to a consumer, MnS-C, and vice versa. In this example, the groups of MLFs can be mutually exclusive, or some or all of the MLFs in each group of MLFs can overlap or share. In another example, MLF 2102 and / or MLF 2104 are implemented by corresponding UEs (such as UE 902, UE 1002, UE 1202). Additionally or alternatively, MLF 2102 and / or MLF 2104 are implemented by the same UE or different UEs. In another example, MLF 2102 and / or MLF 2104 are implemented by a corresponding RAN or a corresponding NAN. Additionally or alternatively, some or all of the elements / entities in the individual MLFs 2102, 2104 can be implemented or operated by separate entities / elements.

[0523] As Figure 21 As shown, MLF 2102 and MLF 2104 include various AI / ML-related components, functions, elements, or entities, which can be implemented as hardware, software, firmware, and / or some combination thereof. In some examples, one or more AI / ML-related elements are implemented as part of the same hardware (e.g., integrated circuit, chip, or multi-processor chip), software (e.g., program, process, engine, etc.), or firmware as at least one other element, function, element, or entity. The AI / ML-related elements of MLF 2102 can be the same as or similar to the AI / ML-related elements of MLF 2104. For simplicity, various elements will be described from the perspective of MLF 2102, but it can be understood that unless otherwise explicitly stated, such descriptions apply to the similarly named / numbered elements of MLF 2104.

[0524] The data repository 2115 is responsible for data collection and storage. As an example, the data repository 2115 can collect and store RAN configuration parameters, NF configuration parameters, measurement data, RLM data, key performance indicators (KPIs), SLAs, model performance metrics, knowledge base data, ground truth data, ML model parameters, hyperparameters, and / or other data for model training, updating, and inference. In some examples, the data collection function (not shown) is part of or connected to the data repository 2115. The data collection function is a function that provides input data to the MLTF 2125 and the model inference function 2145. AI / ML algorithm-specific data preparation (e.g., data preprocessing and cleaning, formatting, and conversion) may or may not be performed in the data collection function. Examples of input data can include measurement results from UEs, RAN nodes, and / or additional or alternative network entities; feedback from actuators; and / or (one or more) outputs from (one or more) ML models. The input data fed to the MLTF 2125 is training data, and the input data fed to the model inference function 2145 is inference data.

[0525] The data collected is stored in the repository 2115 / stored by the repository 2115, and the stored data can be discovered and retrieved from the data repository 2115 by other components. For example, the inference data selection / filter 2150 can retrieve data from the data repository 2115 and provide the data to the inference engine 2145 to generate / determine inferences. In various examples, the MLF 2102 is configured to discover and request data from the data repository 2115 in the MLF 2104, and / or vice versa. In these examples, the data repository 2115 of the MLF 2102 can be communicatively coupled to the data repository 2115 of the MLF 2104 such that the corresponding data repositories 2115 can share the collected data with each other. Additionally or alternatively, the MLF 2102 and / or the MLF 2104 are configured to discover and request data from one or more external sources and / or data storage systems / devices.

[0526] The training data selection / filter 2120 is configured to generate training, validation, and test data sets for machine learning training (MLT) (or machine learning model training). One or more of these data sets can be extracted or otherwise obtained from the data repository 2115. The data can be selected / filtered according to the specific machine learning model to be trained. Optionally, the data can be transformed, augmented, and / or preprocessed (e.g., normalized) before being loaded into the data set. The training data selection / filter 2120 can label the data in the data set for supervised learning; or the data can be unlabeled for unsupervised learning. Then, the generated data set can be fed into the MLT function (MLTF) 2125.

[0527] The MLTF 2125 is responsible for training and updating (e.g., tuning and / or retraining) the ML models. A selected model (or set of models) can be trained using the data sets (including training, validation, testing) fed from the training data selection / filter 2120. The MLTF 2125 generates trained and tested ML models that can be used for deployment at any time. The generated trained and tested models can be stored in the model library 2135. Additionally or alternatively, the MLTF 2125 performs ML model training, validation, and testing. As part of the model testing process and / or model validation process, the MLTF 2125 can generate model performance metrics. Examples of model performance metrics will be discussed below. If needed, the MLTF 2125 is also responsible for data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) based on the data collection function and / or the training data provided by the training data selection / filter 2120. The MLTF 2125 performs model deployment / updating, where the MLTF 2125 initially deploys the trained, validated, and tested ML models to the model inference function 2145 and / or delivers the updated model(s) to the model inference function 2145. Examples of model deployment and updating will be discussed below.

[0528] The model library 2135 is responsible for the storage and exposure of ML models (trained and untrained). Various model data can be stored in the model library 2135. For example, the model data can include the trained / updated model(s), model parameters, hyperparameters, and / or model metadata such as model performance metrics, hardware platform / configuration data, model execution parameters / conditions, etc. In some examples, the model data can also include the inferences made when running the ML models. The model data can be discovered and requested by other MLF components (e.g., the training data selection / filter 2120 and / or the MLTF 2125). In some examples, the MLF 2102 can discover and request model data from the model library 2135 of the MLF 2104. Additionally or alternatively, the MLF 2104 can discover and / or request model data from the model library 2135 of the MLF 2102. In some examples, the MLF 2104 can configure models, model parameters, hyperparameters, model execution parameters / conditions, and / or other aspects of the ML models in the model library 2135 of the MLF 2102. For representational manageability, the ML models are also referred to herein as ML entities, i.e., the two terms ML model and ML entity can be used interchangeably herein.

[0529] The model management function 2140 is responsible for managing the ML models generated by the MLTF 2125. Such management functions may include: deploying the trained models, monitoring the performance of ML entities, reporting ML entity verification and / or performance data, etc. When deploying a model, the model management function 2140 can allocate and schedule the hardware and / or software resources for inference based on the received trained and tested model. For the purposes of this disclosure, the term "inference" refers to the process of using one or more trained ML models to generate statistical inferences, predictions, decisions, probabilities, and / or probability distributions, actions, configurations, policies, data analysis, results, optimizations, etc. based on new, unseen data (e.g., "input inference data"). In some examples, the inference process may include feeding the input inference data into an ML model (e.g., the inference engine 2145), passing the input inference data forward through the architecture / topology of the ML model, where the ML model performs calculations on the data using the parameters it has learned (e.g., weights and biases), and predicting the output. In some examples, the inference process may include data transformation before the forward pass, where the input inference data is preprocessed or transformed to match the format required by the ML model. In performance monitoring, based on the model performance KPIs and / or metrics, the model management function 2140 can decide to terminate a running model, start model retraining and / or adjustment, select another model, etc. In an example, the model management function 2140 of the MLF 2104 can configure the model management policy in the MLF 2102, and vice versa.

[0530] As described below, the inference data selection / filter 2150 is responsible for generating the dataset for model inference at the inference 2145. For example, the inference data can be extracted from the data repository 2115. The inference data selection / filter 2150 can select and / or filter the data according to the deployed ML model. The data can be transformed, augmented, and / or preprocessed in the same or similar manner as the transformation, augmentation, and / or preprocessing of the training data selection / filtering (e.g., as described for the training data selection filter 2120). The generated inference dataset can be fed into the inference engine 2145.

[0531] The inference engine 2145 (also referred to as "model inference function 2145", etc.) is responsible for performing / generating the inferences described herein. The inference engine 2145 consumes the inference data set provided by the inference data selector / filter 2150 and generates an ML model inference output, which includes one or more inferences. For example, an inference can be or include statistical inference, prediction, decision-making, probability and / or probability distribution, action, configuration, policy, data analysis, result, optimization, etc. The (one or more) inferences / (one or more) results can be provided to the performance measurement function 2130. When applicable, the model inference function 2145 can provide model performance feedback to the MLTF 2125 and / or the performance measurement function 2130. The model performance feedback can include various performance metrics related to generating the inferences (e.g., any of the metrics discussed herein). The model performance feedback can be used to monitor the performance of the ML model when applicable. If needed, the model inference function 2145 can also be responsible for data preparation (e.g., data preprocessing and cleaning, formatting and transformation) based on the inference data provided by the data collection function and / or the inference data selector / filter 2150. The model inference function 2145 generates an inference output, i.e., the inferences generated or otherwise generated when the model inference function 2145 runs the ML model using the inference data (set). The details of the inference output are related to the specific use case and can be based on the specific type of ML model being used.

[0532] In some examples, the model inference function 2145 provides the inference output to an actor (not shown). An actor is a function, engine, component, device, system, network, and / or other entity that receives the inference output from the model inference function 2145 and triggers or otherwise performs the corresponding (one or more) actions based on the inference output. The actor can trigger actions for other entities and / or itself. In some examples, the actor is a network energy saving (NES) function, a mobility robustness optimization (MRO) function, a load balancing optimization (LBO) function, and / or other self-organizing network (SON) functions, including any of the functions mentioned herein. Additionally or alternatively, the inference output is related to NES, MRO, and / or LBO, and the actor is one or more RAN nodes that perform various NES, MRO, and / or LBO operations based on the inference. The actor can also provide feedback to the performance measurement function 2130 and / or the data collection function / data repository 2115 for storage. The actor feedback includes information related to the actions performed by the actor. For example, the feedback includes any information that may be needed to obtain training data, test data, and / or validation data; inference data; and / or data for monitoring the performance of the ML model and its impact on the network by updating KPIs, performance counters, etc.

[0533] The performance measurement function 2130 is configured to measure model performance metrics (e.g., accuracy, momentum, precision, magnitude, recall / sensitivity, model bias, runtime latency, resource consumption, and / or other suitable metrics / measurements, such as any of the metrics / measurements discussed herein) of a deployed and executing model based on one or more inferences for monitoring purposes. The model performance data can be stored in the data repository 2115 and / or reported according to the validation report mechanism discussed herein.

[0534] The performance metrics that the performance measurement function 2130 can measure and / or predict can be based on specific AI / ML tasks and other inputs / parameters of the ML entity. The performance metrics can include model-based metrics and platform-based metrics. Model-based metrics are metrics related to the performance of the model itself and / or metrics that do not consider the underlying hardware platform. Platform-based metrics are related to the performance of the underlying hardware platform when running the ML model.

[0535] Model-based metrics can be based on a specific type of ML model and / or AI / ML domain. For example, regression-related metrics of a regression-based ML model can be predicted. Examples of regression-related metrics include error value, mean error, mean absolute error (MAE), mean reciprocal rank (MRR), mean squared error (MSE), root MSE (RMSE), correlation coefficient (R), coefficient of determination (R2), Golbraikh and Tropsha criteria, and / or other similar regression-related metrics, such as those discussed in the article by Naser et al. (Insights into Performance Fitness and Error Metrics for Machine Learning, arXiv:2006.00887v1 (17 May 2020) ("[Naser]")).

[0536] In another example, correlation-related metrics can be used to predict correlation-related models. Examples of correlation-related metrics include accuracy, precision (also known as positive predictive value (PPV)), mean average precision (mAP), negative predictive value (NPV), recall (also known as true positive rate (TPR) or sensitivity), specificity (also known as true negative rate (TNR) or selectivity), false positive rate, false negative rate, F-score (e.g., F1 score, F2 score, Fβ score, etc.), Matthews correlation coefficient (MCC), significance, receiver operating characteristic (ROC), area under the ROC curve (AUC), distance score, and / or other similar correlation-related metrics, such as those discussed in [Naser].

[0537] Additional or alternative model-based metrics can also be predicted, such as cumulative gain (CG), discounted CG (DCG), normalized DCG (NDCG), signal-to-noise ratio (SNR), peak signal-to-noise ratio (PSNR), structural similarity (SSIM), intersection over union (IoU), perplexity, bilingual evaluation understudy (BLEU) score, start score, Wasserstein metric, Fréchet inception distance (FID), string metric, edit distance, Levenshtein distance, Damerau–Levenshtein distance, number of evaluation instances (e.g., iterations, epochs, or events), learning rate (e.g., the speed at which an algorithm reaches (converges to) optimal weights), learning rate decay (or weight decay), number and / or type of computations, multiply and accumulates (MAC) number and / or type, multiply adds (MAdds) operation number and / or type, and / or other similar performance metrics related to the performance of the ML model.

[0538] Examples of platform-based metrics include latency, response time, throughput (e.g., the rate at which a processor or platform / system processes work), availability and / or reliability, power consumption (e.g., performance per watt and / or similar metrics), number of transistors, execution time (e.g., the amount of time to obtain an inference and / or similar metrics), memory footprint, memory utilization, processor utilization, processor time, number of computations, instructions per second (IPS), floating point operations per second (FLOPS), and / or other similar performance metrics related to the performance of the ML model and / or the underlying hardware platform used to run the ML model.

[0539] Additionally or alternatively, proxy metrics (e.g., metrics or attributes that serve as a stand-in or substitute for another metric or attribute) can be used to predict the performance of the ML model. For any of the above performance metrics, any suitable data collection and / or measurement mechanism can be used to predict and / or measure the total, average, and / or other distributions of such metrics.

[0540] Figure 22 Network 2200 is shown in accordance with various embodiments. Network 2200 may operate in a manner compliant with 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited thereto, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, and so on.

[0541] Network 2200 may include UE 2202, which may include any mobile or non-mobile computing device designed to communicate with RAN 2204 via an air interface. UE 2202 may be communicatively coupled to RAN 2204 via the Uu interface. UE 2202 may be, but is not limited to, a smart phone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, a dashboard, a head-up display device, an on-board diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine-type communication device, an M2M or D2D device, an IoT device, and so on.

[0542] In some embodiments, network 2200 may include multiple UEs that are directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels, such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, and so on.

[0543] In some embodiments, UE 2202 may also communicate with AP 2206 via an air interface. AP 2206 may manage a WLAN connection, which may be used to offload some / all network traffic from RAN 2204. The connection between UE 2202 and AP 2206 may conform to any IEEE 802.11 protocol, where AP 2206 may be a Wi-Fi router. In some embodiments, UE 2202, RAN 2204, and AP 2206 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve UE 2202 being configured by RAN 2204 to utilize both cellular radio resources and WLAN resources.

[0544] RAN 2204 may include one or more access nodes, e.g., AN 2208. AN 2208 may terminate the air interface protocol for UE 2202 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 2208 can enable data / voice connectivity between CN 2220 and UE 2202. In some embodiments, AN 2208 may be implemented in a discrete device or as one or more software entities running on a server computer, as part of, for example, a virtual network, which may be referred to as CRAN or virtual baseband unit pool. AN 2208 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 2208 may be a macro cell base station or a low-power base station for providing a femto cell, pico cell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macro cell.

[0545] In embodiments where RAN 2204 includes multiple ANs, they may be coupled to each other via an X2 interface (if RAN 2204 is an LTE RAN) or an Xn interface (if RAN 2204 is a 5G RAN). The X2 / Xn interface (which may be separated into a control / user plane interface in some embodiments) may allow ANs to convey information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0546] The ANs of RAN 2204 may each manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 2202. UE 2202 may be connected to multiple cells provided by the same or different ANs of RAN 2204 simultaneously. For example, UE 2202 and RAN 2204 may use carrier aggregation to allow UE 2202 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual connectivity scenario, the first AN may be the primary node providing the MCG, and the second AN may be the secondary node providing the SCG. The first / second ANs may be any combination of eNB, gNB, ng-eNB, etc.

[0547] RAN 2204 may provide an air interface via licensed spectrum or unlicensed spectrum. To operate in unlicensed spectrum, nodes may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCell / Scell. Before accessing unlicensed spectrum, nodes may perform medium / carrier sensing operations based on, for example, the listen-before-talk (LBT) protocol.

[0548] In a V2X scenario, UE 2202 or AN 2208 can be or can act as an RSU, which can refer to any traffic infrastructure entity for V2X communication. The RSU can be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. The RSU implemented in or by a UE can be referred to as a "UE-type RSU"; the RSU implemented in or by an eNB can be referred to as an "eNB-type RSU"; the RSU implemented in or by a gNB can be referred to as a "gNB-type RSU"; and so on. In one example, the RSU is a computing device coupled to a roadside radio frequency circuit that provides connectivity support to passing vehicle UEs. The RSU may also include an internal data storage circuit to store intersection map geometries, traffic flow statistics, media, and applications / software to sense and control ongoing vehicle and pedestrian traffic flow. The RSU can provide extremely low-latency communication required for high-speed events such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU can provide other cellular / WLAN communication services. The components of the RSU can be encapsulated in a weatherproof enclosure suitable for outdoor installation and can include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

[0549] In some embodiments, RAN 2204 can be an LTE RAN 2210 with an eNB, e.g., eNB 2212. The LTE RAN 2210 can provide an LTE air interface with the following characteristics: an SCS of 15 kHz; a CP-OFDM waveform for DL and an SC-FDMA waveform for UL; turbo coding for data and TBCC for control; and so on. The LTE air interface can rely on CSI-RS for CSI acquisition and beam management; rely on PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and rely on CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface can operate in a frequency band below 6 GHz.

[0550] In some embodiments, RAN 2204 may be an NG-RAN 2214 with a gNB, e.g., gNB 2216, or an NG-RAN 2214 with an ng-eNB, e.g., ng-eNB 2218. gNB 2216 may connect to a 5G-capable UE using a 5G NR interface. gNB 2216 may connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. ng-eNB 2218 may also connect to the 5G core via an NG interface, but may connect to the UE via an LTE air interface. gNB 2216 and ng-eNB 2218 may connect to each other via an Xn interface.

[0551] In some embodiments, the NG interface may be split into two parts, one being the NG user plane (NG-U) interface, which carries traffic data (e.g., the N3 interface) between nodes of the NG-RAN 2214 and the UPF 2248, and the other being the NG control plane (NG-C) interface, which is a signaling interface between nodes of the NG-RAN 2214 and the AMF 2244 (e.g., the N2 interface).

[0552] The NG-RAN 2214 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar codes, repetition codes, simplex codes, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking of PDSCH; and tracking reference signals for time tracking. The 5G-NR air interface may operate in the FR1 band including bands below 6 GHz or in the FR2 band including the band from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB, which is an area of the downlink resource grid including PSS / SSS / PBCH.

[0553] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of the SCS. For example, UE 2202 may be configured with multiple BWPs, where each BWP configuration has a different SCS. When a BWP change is indicated to UE 2202, the transmitted SCS is also changed. Another example use case of BWPs is related to power saving. Specifically, UE 2202 can be configured with multiple BWPs having different amounts of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with a small traffic load, while allowing power saving at UE 2202 and in some cases at gNB 2216. A BWP containing a larger number of PRBs can be used for scenarios with a higher traffic load.

[0554] RAN 2204 is communicatively coupled to CN 2220, which includes network elements to provide various functions to support data and telecommunications services for customers / subscribers (e.g., the user of UE 2202). The components of CN 2220 can be implemented in one physical node or separate physical nodes. In some embodiments, NFV can be utilized to virtualize any or all of the functions provided by the network elements of CN 2220 onto physical computing / storage resources in servers, switches, etc. The logical instantiation of CN 2220 can be referred to as a network slice, and the logical instantiation of a part of CN 2220 can be referred to as a network sub-slice.

[0555] In some embodiments, CN 2220 can be an LTE CN 2222, which can also be referred to as the EPC. LTE CN 2222 may include MME 2224, SGW 2226, SGSN 2228, HSS 2230, PGW 2232, and PCRF 2234, which are coupled to each other through interfaces (or "reference points") as shown. The functions of the elements of LTE CN 2222 can be briefly introduced as follows.

[0556] MME 2224 can implement mobility management functions to track the current location of UE 2202 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0557] SGW 2226 can terminate the S1 interface towards the RAN and route data packets between the RAN and LTE CN 2222. SGW 2226 can be a local mobility anchor point for inter-RAN node handovers and can also provide anchoring for inter-3GPP mobility. Other responsibilities can include lawful interception, charging, and some policy enforcement.

[0558] The SGSN 2228 can track the location of the UE 2202 and perform security functions and access control. In addition, the SGSN 2228 can execute EPC inter-node signaling for mobility between different RAT networks; select the PDN and S-GW according to the provisions of the MME 2224; select the MME for handover; and so on. The S3 reference point between the MME 2224 and the SGSN 2228 can enable the exchange of user and bearer information for mobility between 3GPP access networks in the idle / active state.

[0559] The HSS 2230 can include a database for network users, which includes subscription-related information to support the handling of communication sessions by network entities. The HSS 2230 can provide support for routing / roaming, authentication, authorization, name / address resolution, location compliance, and so on. The S6a reference point between the HSS 2230 and the MME 2224 can enable the transmission of subscription and authentication data to authenticate / authorize user access to the LTE CN 2220.

[0560] The PGW 2232 can terminate the SGi interface towards the data network (DN) 2236, which can include the application / content server 2238. The PGW 2232 can route data packets between the LTE CN 2222 and the data network 2236. The PGW 2232 can be coupled to the SGW 2226 through the S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 2232 can also include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 2232 and the data network 2236 can be an operator-external public or private PDN or an operator-internal packet data network, such as for the configuration of IMS services. The PGW 2232 can be coupled to the PCRF 2234 via the Gx reference point.

[0561] The PCRF 2234 is the policy and charging control element of the LTE CN 2222. The PCRF 2234 can be communicatively coupled to the application / content server 2238 to determine the appropriate QoS and charging parameters for the service flow. The PCRF 2232 can configure the associated rules into the PCEF with the appropriate TFT and QCI (via the Gx reference point).

[0562] In some embodiments, CN 2220 may be 5GC 2240. 5GC 2240 may include AUSF 2242, AMF 2244, SMF 2246, UPF 2248, NSSF 2250, NEF 2252, NRF 2254, PCF 2256, UDM 2258, and AF 2260, which are coupled to each other through interfaces (or "reference points") as shown. The functions of the elements of 5GC 2240 are briefly introduced as follows.

[0563] AUSF 2242 may store the data for the authentication of UE 2202 and handle authentication-related functions. AUSF 2242 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 2240 through the reference points as shown, AUSF 2242 may also expose a service-based interface for Nausf.

[0564] AMF 2244 may allow other functions of 5GC 2240 to communicate with UE 2202 and RAN 2204, and subscribe to notifications regarding mobility events for UE 2202. AMF 2244 may be responsible for registration management (e.g., for registering UE 2202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF 2244 may provide transmission for SM messages between UE 2202 and SMF 2246 and act as a transparent proxy for routing SM messages. AMF 2244 may also provide transmission for SMS messages between UE 2202 and SMSF. AMF 2244 may interact with AUSF 2242 and UE 2202 to perform various security anchoring and context management functions. In addition, AMF 2244 may be an end-point of the RAN CP interface, which may include or may be the N2 reference point between RAN 2204 and AMF 2244; and AMF 2244 may be an end-point of NAS (N1) signaling and perform NAS encryption and integrity protection. AMF 2244 may also support NAS signaling with UE 2202 through the N3 IWF interface.

[0565] The SMF 2246 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 2248 and the AN 2208); UE IP address allocation and management (including optional authorization); selection and control of the UPF function; configuring traffic steering at the UPF 2248 to route traffic to the appropriate destination; termination of the interface towards the policy control function; the control part of policy enforcement, charging, and QoS; lawful interception (for SM events and the interface to the LI system); termination of the SM part of NAS messages; downlink data notification; initiating AN-specific SM information sent to the AN 2208 via the AMF 2244 over N2; and determining the SSC mode of the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 2202 and the data network 2236.

[0566] The UPF 2248 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for the interconnection to the data network 2236, and a branching point for supporting multi-homed PDU sessions. The UPF 2248 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF to QoS flow mapping), perform transport-level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 2248 may include an uplink classifier to support routing traffic flows to the data network.

[0567] The NSSF 2250 may select a set of network slice instances to serve the UE 2202. If needed, the NSSF 2250 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI. The NSSF 2250 may also determine, based on appropriate configuration and possibly by querying the NRF 2254, the set of AMFs or a list of candidate AMFs to be used to serve the UE 2202. Selecting a set of network slice instances for the UE 2202 may be triggered by the UE 2202's registration with its serving AMF 2244 through interaction with the NSSF 2250, which may result in a change of AMF. The NSSF 2250 may interact with the AMF 2244 via the N22 reference point; and may communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, the NSSF 2250 may expose an Nnssf service-based interface.

[0568] The NEF 2252 can securely expose to third parties the services and capabilities provided by 3GPP network functions, internal exposure / re-exposure, the AF (e.g., AF 2260), edge computing, or fog computing systems, etc. In such an embodiment, the NEF 2252 can authenticate, authorize, or throttle the AF. The NEF 2252 can also translate the information exchanged with the AF 2260 and the information exchanged with internal network functions. For example, the NEF 2252 can translate between an AF service identifier and internal 5GC information. The NEF 2252 can also receive information from other NFs based on the exposed capabilities of other NFs. This information can be stored at the NEF 2252 as structured data, or stored at a data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF 2252 to other NFs and the AF, or used for other purposes, such as resolution. In addition, the NEF 2252 can expose Nnef service-based interfaces.

[0569] The NRF 2254 can support a service discovery function, receive NF discovery requests from NF instances, and provide information about the discovered NF instances to NF instances. The NRF 2254 also maintains information about available NF instances and the services they support. As used herein, terms such as "instantiation" can refer to the creation of an instance, and "instance" can refer to a specific occurrence of an object, which can occur, for example, during the execution of program code. In addition, the NRF 2254 can expose Nnrf service-based interfaces.

[0570] The PCF 2256 can provide policy rules to control plane functions to enable them to be enforced, and can also support a unified policy framework to constrain network behavior. The PCF 2256 can also implement a front end to access subscription information related to policy decisions in the UDR of the UDM 2258. In addition to communicating with functions via reference points as shown, the PCF 2256 can expose Npcf service-based interfaces.

[0571] The UDM 2258 can dispose of subscription-related information to support the network entity's disposition of communication sessions and can store the subscription data of the UE 2202. For example, the subscription data can be conveyed via the N8 reference point between the UDM 2258 and the AMF 2244. The UDM 2258 can include two parts, an application front-end and a UDR. The UDR can store subscription data and policy data for the UDM 2258 and the PCF 2256, and / or store structured data and application data for exposure (including PFDs for application detection, application request information for multiple UEs 2202) for the NEF 2252. The Nudr service-based interface can be presented by the UDR 221 to allow the UDM 2258, the PCF 2256, and the NEF 2252 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM can include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front-ends can serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identity disposition, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown in the figure, the UDM 2258 can also present the Nudm service-based interface.

[0572] The AF 2260 can provide an application impact on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0573] In some embodiments, the 5GC 2240 can implement edge computing by selecting an operator / third-party service geographically close to the point where the UE 2202 attaches to the network. This can reduce latency and load on the network. To provide edge computing implementation, the 5GC 2240 can select a UPF 2248 close to the UE 2202 and perform traffic manipulation from the UPF 2248 to the data network 2236 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by the AF 2260. In this way, the AF 2260 can affect UPF (re)selection and traffic routing. Based on operator deployment, when the AF 2260 is considered a trusted entity, the network operator can allow the AF 2260 to directly interact with the relevant NFs. In addition, the AF 2260 can present the Naf service-based interface.

[0574] The data network 2236 can represent various network operator services, Internet access, or third-party services, which can be provided by one or more servers, such as including application / content servers 2238.

[0575] Figure 23 FIG. schematically illustrates a wireless network 2300 in accordance with various embodiments. The wireless network 2300 may include a UE 2302 that wirelessly communicates with an AN 2304. The UE 2302 and the AN 2304 may be similar to components of similar names described elsewhere herein and are substantially interchangeable with these components.

[0576] The UE 2302 may be communicatively coupled with the AN 2304 via a connection 2306. The connection 2306 is illustrated as an air interface to enable the communicative coupling and may conform to a cellular communication protocol, such as the LTE protocol or the 5G NR protocol operating at mmWave or sub-6 GHz frequencies.

[0577] The UE 2302 may include a host platform 2308 coupled to a modem platform 2310. The host platform 2308 may include application processing circuitry 2312, which may be coupled to protocol processing circuitry 2314 of the modem platform 2310. The application processing circuitry 2312 may run various applications for the UE 2302 that originate / sink application data. The application processing circuitry 2312 may further implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

[0578] The protocol processing circuitry 2314 may implement one or more layer operations to facilitate sending or receiving data over the connection 2306. The layer operations implemented by the protocol processing circuitry 2314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0579] The modem platform 2310 may further include digital baseband circuitry 2316, which may implement one or more layer operations “below” the layer operations performed by the protocol processing circuitry 2314 in the network protocol stack. These operations may include, for example, PHY operations, which may include one or more of the following: HARQ-ACK functionality, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time, space-frequency, or space coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions.

[0580] The modem platform 2310 may further include a transmit circuit 2318, a receive circuit 2320, an RF circuit 2322, and an RF front end (RFFE) 2324, which may include or be connected to one or more antenna panels 2326. Briefly, the transmit circuit 2318 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, and so on; the receive circuit 2320 may include an analog-to-digital converter, a mixer, an IF component, and so on; the RF circuit 2322 may include a low-noise amplifier, a power amplifier, a power tracking component, and so on; the RFFE 2324 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), and so on. The selection and arrangement of the components of the transmit circuit 2318, the receive circuit 2320, the RF circuit 2322, the RFFE 2324, and the antenna panel 2326 (collectively referred to as "transmit / receive components") may depend on the details of the specific implementation, e.g., whether the communication is TDM or FDM, at mmWave or sub-6GHz frequencies, and so on. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be disposed on the same or different chips / modules, and so on.

[0581] In some embodiments, the protocol processing circuit 2314 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.

[0582] UE reception may be established by and via the antenna panel 2326, the RFFE 2324, the RF circuit 2322, the receive circuit 2320, the digital baseband circuit 2316, and the protocol processing circuit 2314. In some embodiments, the antenna panel 2326 may receive transmissions from the AN 2304 via receive beamforming signals received by a plurality of antennas / antenna elements of one or more antenna panels 2326.

[0583] UE transmission may be established by and via the protocol processing circuit 2314, the digital baseband circuit 2316, the transmit circuit 2318, the RF circuit 2322, the RFFE 2324, and the antenna panel 2326. In some embodiments, the transmit components of the UE 2304 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panel 2326.

[0584] Similar to UE 2302, AN 2304 may include a host platform 2328 coupled to a modem platform 2330. The host platform 2328 may include an application processing circuit 2332 coupled to a protocol processing circuit 2334 of the modem platform 2330. The modem platform may also include a digital baseband circuit 2336, a transmit circuit 2338, a receive circuit 2340, an RF circuit 2342, an RFFE circuit 2344, and an antenna panel 2346. The components of AN 2304 may be similar to the similarly named components of UE 2302 and are substantially interchangeable. In addition to performing data transmission / reception as described above, the components of AN 2308 may also perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0585] Figure 24 The block diagram of illustrates components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein. Specifically, Figure 24 illustrates a graphical representation of hardware resources 2400, which include one or more processors (or processor cores) 2410, one or more memory / storage devices 2420, and one or more communication resources 2430, each of which may be communicatively coupled via a bus 2440 or other interface circuit. For embodiments that utilize node virtualization (e.g., NFV), a hypervisor 2402 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 2400.

[0586] The processor 2410 may include, for example, a processor 2412 and a processor 2414. The processor 2410 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0587] The memory / storage device 2420 may include a main memory, disk storage, or any suitable combination thereof. The memory / storage device 2420 may include, but is not limited to, any type of volatile, non-volatile, or semi-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, and so on.

[0588] The communication resources 2430 may include an interconnect or network interface controller, component, or other suitable device to communicate with one or more peripheral devices 2404, one or more databases 2406, or other network elements via the network 2408. For example, the communication resources 2430 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, (or low-power ) components, components, and other communication components.

[0589] The instructions 2450 may include software, programs, applications, applets, apps, or other executable code for causing at least any one of the processors 2410 to execute any one or more of the methods discussed herein. The instructions 2450 may reside entirely or partially within at least one of the processors 2410 (e.g., within the cache memory of the processor), within the memory / storage device 2420, or any suitable combination thereof. Additionally, any portion of the instructions 2450 may be transferred from any combination of the peripheral devices 2404 or databases 2406 to the hardware resources 2400. Accordingly, the memories of the processors 2410, the memory / storage device 2420, the peripheral devices 2404, and the databases 2406 are examples of computer-readable and machine-readable media.

[0590] Figure 25 FIG. 2500 shows a network 2500 according to various embodiments. The network 2500 may operate in a manner compliant with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 2500 may operate concurrently with the network 2200. For example, in some embodiments, the network 2500 may share one or more frequency or bandwidth resources with the network 2200. As a specific example, a UE (e.g., UE 2502) may be configured to operate in both the network 2500 and the network 2200. Such a configuration may be based on the UE including circuitry configured to communicate with the frequency and bandwidth resources of both the network 2200 and the network 2500. Generally, several elements of the network 2500 may share one or more characteristics with the elements of the network 2200. For the sake of brevity and clarity, these elements may not be repeated in the description of the network 2500.

[0591] The network 2500 may include a UE 2502, which may include any mobile or non-mobile computing device designed to communicate with the RAN 2508 via an air interface. The UE 2502 may be similar to, for example, the UE 2202. The UE 2502 may be, but is not limited to, a smart phone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, a dashboard, a head-up display device, an on-vehicle diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine-type communication device, an M2M or D2D device, an IoT device, etc.

[0592] Although not specifically shown in Figure 25 , in some embodiments, the network 2500 may include multiple UEs that are directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels, such as but not limited to PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in Figure 25 , the UE 2502 may be communicatively coupled to an AP (e.g., the AP 2206 described with reference to Figure 22 ). Additionally, although not specifically shown in Figure 25 , in some embodiments, the RAN 2508 may include one or more ANs, such as the AN 2208 described with reference to Figure 22 . The RAN 2508 and / or the ANs of the RAN 2508 may be referred to as a base station (BS), a RAN node, or some other term or name.

[0593] UE 2502 and RAN 2508 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features such as communication in the terahertz (THz) or sub-terahertz bandwidth, or joint communication and sensing. As used herein, the term "joint communication and sensing" may refer to a system that enables wireless communication and radar-based sensing via various types of multiplexing. As used herein, the THz or sub-THz bandwidth may refer to communication in the frequency range of 80 GHz and above. This frequency range may additionally or alternatively be referred to as the "millimeter wave" or "mmWave" frequency range.

[0594] RAN 2508 may allow communication between UE 2502 and 6G core network (CN) 2510. Specifically, RAN 2508 may facilitate the transmission and reception of data between UE 2502 and 6G CN 2510. 6G CN 2510 may include various functions such as NSSF 2250, NEF 2252, NRF 2254, PCF 2256, UDM 2258, AF 2260, SMF 2246, and AUSF 2242. As Figure 25 shown, 6G CN 2510 may also include UPF 2248 and DN 2236.

[0595] In addition, RAN 2508 may include various additional functions that are additional or alternative to the functions of traditional cellular networks (such as 4G or 5G networks). Two such functions may include a Compute Control Function (Comp CF) 2524 and a Compute Service Function (Comp SF) 2536. Comp CF 2524 and Comp SF 2536 may be part of or functions of the compute service plane. Comp CF 2524 may be a control plane function that provides functions such as management of Comp SF 2536, generation and management of compute task contexts (e.g., create, read, modify, delete), interaction with the underlying compute infrastructure for compute resource management, and so on. Comp SF 2536 may be a user plane function that acts as an interface gateway between a compute service user (such as UE 2502) and the compute nodes behind the Comp SF instance. Some functions of Comp SF 2536 may include: parsing compute service data received from the user to compute tasks executable by the compute nodes; maintaining a service mesh ingress gateway or a service API gateway; enforcing service and charging policies; collecting performance monitoring and telemetry, and so on. In some embodiments, the Comp SF 2536 instance may act as a user plane gateway for a cluster of compute nodes. The Comp CF 2524 instance may control one or more Comp SF 2536 instances.

[0596] Two other such functions may include a Communication Control Function (Comm CF) 2528 and a Communication Service Function (Comm SF) 2538, which may be part of a communication service plane. The Comm CF 2528 may be a control plane function for managing the Comm SF 2538, creating / configuring / releasing communication sessions, and managing communication session context. The Comm SF 2538 may be a user plane function for data transmission. The Comm CF 2528 and Comm SF 2538 may be regarded as upgrades of the SMF 2246 and UPF 2248, for which the 5G system has been described in Figure 22 the 5G system described in

[0597] Two other such functions may include a Data Control Function (Data CF) 2522 and a Data Service Function (Data SF) 2532, which may be part of a data service plane. The Data CF 2522 may be a control plane function and provide functions such as Data SF 2532 management, data service creation / configuring / releasing, data service context management, etc. The Data SF 2532 may be a user plane function and act as a gateway between data service users (e.g., various functions of the UE 2502 and 6G CN 2510) and data service endpoints behind the gateway. Specific functions may include: parsing data service user data and forwarding it to the corresponding data service endpoints, generating charging data, reporting data service status.

[0598] Another such function may be a Service Orchestration and Chaining Function (SOCF) 2520, which may discover, orchestrate, and chain communication / computing / data services provided by functions in the network. After receiving a service request from a user, the SOCF 2520 may interact with one or more of the Comp CF 2524, Comm CF 2528, and Data CF 2522 to identify Comp SF 2536, Comm SF 2538, and Data SF 2532 instances, configure service resources, and generate a service chain, which may include multiple Comp SF 2536, Comm SF 2538, and Data SF 2532 instances and their associated computing endpoints. Then, workload processing and data movement may be performed within the generated service chain. The SOCF 2520 may also be responsible for maintaining, updating, and releasing the created service chain.

[0599] Another such function can be the service registration function (SRF) 2514, which can act as a registration center for system services provided in the user plane, such as services provided by the Comp SF 2536 and service endpoints behind the data SF2532 gateway, as well as services provided by the UE 2502. The SRF 2514 can be regarded as the counterpart of the NRF2254, which can act as a registration center for network functions.

[0600] Other such functions can include the evolved service communication proxy (eSCP) and the service infrastructure control function (SICF) 2526, which can provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G and adds user plane service communication proxy capabilities. The eSCP is thus expressed as two parts: eCSP-C 2512 and eSCP-U 2534, for control plane service communication proxy and user plane service communication proxy respectively. The SICF 2526 can control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, and so on.

[0601] Another such function is the AMF 2544. The AMF 2544 can be similar to 2244 but has additional functions. Specifically, the AMF 2544 can include potential function re-partitioning, such as moving the message forwarding function from the AMF 2544 to the RAN 2508.

[0602] Another such function is the service orchestration exposure function (SOEF) 2518. The SOEF can be configured to expose service orchestration and chained services to external users (such as applications).

[0603] UE 2502 may include an additional function called the Compute Client Service Function (comp CSF) 2504. The comp CSF 2504 may have both control plane functions and user plane functions, and may interact with corresponding network-side functions (e.g., SOCF 2520, Comp CF 2524, Comp SF 2536, Data CF 2522, and / or Data SF 2532) to achieve service discovery, request / response, compute task workload exchange, and so on. The Comp CSF 2504 may also cooperate with network-side functions to decide whether compute tasks should be run on elements of the UE 2502, RAN 2508, and / or 6G CN 2510.

[0604] UE 2502 and / or Comp CSF 2504 may include a service mesh proxy 2506. The service mesh proxy 2506 may act as a proxy for service-to-service communication in the user plane. The functions of the service mesh proxy 2506 may include one or more of addressing, security, load balancing, and so on.

[0605] The following paragraphs describe examples of various embodiments.

[0606] Example A1 includes an apparatus, comprising: an interface circuit; and a processor circuit coupled to the interface circuit, wherein the processor circuit is configured to: decode a trace job creation request received from a service consumer via the interface circuit to create a trace job for collecting user equipment (UE)-level measurement results in a communication network; in response to the trace job creation request, encode a trace session activation request for activating a trace session to be transmitted to a unified data management (UDM); decode a trace session activation response received from the UDM in response to the trace session activation request, the trace session activation response being for indicating an activation result of the trace session; and in response to the trace session activation response, encode a trace job creation response to be transmitted to the service consumer via the interface circuit, the trace job creation response being for indicating a creation result of the trace job.

[0607] Example A2 includes the apparatus according to Example A1 or any other example herein, wherein the trace job includes: a job type indicating that the trace job is for UE-level measurement result collection; a trace target indicating the UE to be measured; administrative attributes for UE-level measurement configuration; a public land mobile network (PLMN) target; a job ID; a trace reference; an Internet protocol (IP) address of a trace collection entity for file-based trace reports; a uniform resource identifier (URI) of a trace report consumer for streaming trace reports; or a trace report format.

[0608] Example A3 includes the apparatus described in Example A2 or any other example herein, wherein the management attributes for UE-level measurement configuration include: UE-level measurement results to be collected; UE-level measurement granularity period; object instances to be measured; or root object instances of the objects to be measured.

[0609] Example A4 includes the apparatus described in Example A1 or any other example herein, wherein the tracking session activation request carries UE-level measurement configuration parameters.

[0610] Example A5 includes the apparatus described in Example A4 or any other example herein, wherein the UE-level measurement configuration parameters include: tracking target; tracking reference; network element (NE) type for measurement; UE-level measurement results of the NE type for measurement; UE-level measurement granularity period; Internet Protocol (IP) address of the tracking collection entity for file-based tracking reports; Uniform Resource Identifier (URI) of the tracking report consumer for streaming tracking reports; or tracking report format.

[0611] Example A6 includes the apparatus described in Example A5 or any other example herein, wherein the NE type for measurement includes a fifth-generation (5G) core network (5GC) network function (NF) or a next-generation (NG) radio access network (RAN) node.

[0612] Example A7 includes the apparatus described in Example A5 or any other example herein, wherein the NE type for measurement includes an access and mobility management function (AMF), and the UE-level measurement configuration parameters are provided to the AMF via a Nudm_SDM_Notification message or a forward relocation request.

[0613] Example A8 includes the apparatus described in Example A5 or any other example herein, wherein the NE type for measurement includes a session management function (SMF), and the UE-level measurement configuration parameters are provided to the SMF via a Nsmf_PDUSession_CreateSMContext request, a Nsmf_PDUSession_UpdateSMContext request, a Nudm_SDM_Notification message, or a Nudm_UECM_Registration procedure.

[0614] Example A9 includes the apparatus described in Example A5 or any other example herein, wherein the NE type for measurement includes a policy control function (PCF), and the UE-level measurement configuration parameters are provided to the PCF via a session management policy establishment procedure or a session management policy modification procedure.

[0615] Example A10 includes the apparatus described in Example A5 or any other example herein, wherein the NE type for measurement includes a User Plane Function (UPF), and the UE-level measurement configuration parameters are provided to the UPF via an N4 session establishment procedure or an N4 session modification procedure.

[0616] Example A11 includes the apparatus described in Example A5 or any other example herein, wherein the NE type for measurement includes a Next Generation (NG) Radio Access Network (RAN) node, and the UE-level measurement configuration parameters are provided to the NG-RAN node via a trace start message, an initial context setup request, or a handover request.

[0617] Example A12 includes the apparatus described in Example A11 or any other example herein, wherein the UE-level measurement configuration parameters further include: the type of NG-RAN node for measurement; or the UE-level measurement result of the type of NG-RAN node for measurement.

[0618] Example A13 includes the apparatus described in Example A5 or any other example herein, wherein the trace target includes a Subscription Permanent Identifier (SUPI) or an International Mobile Station Equipment Identity and Software Version Number (IMEISV).

[0619] Example A14 includes the apparatus described in Example A1 or any other example herein, wherein the processor circuit is further configured to: decode a trace job deletion request received from the service consumer via the interface circuit to delete the trace job; in response to the trace job deletion request, encode a trace session deactivation request for deactivating the trace session to be transmitted to the UDM; decode a trace session deactivation response received from the UDM in response to the trace session deactivation request, the trace session deactivation response being used to indicate a deactivation result of the trace session; and in response to the trace session deactivation response, encode a trace job deletion response to be transmitted to the service consumer via the interface circuit, the trace job deletion response being used to indicate a deletion result of the trace job.

[0620] Example A15 includes the apparatus described in Example A1 or any other example herein, wherein the service consumer includes a Management Service Consumer (MnS-C).

[0621] Example A16 includes the apparatus described in any one of Examples A1 to A15 or any other example herein, wherein the apparatus is applicable to a service producer.

[0622] Example A17 includes the apparatus described in Example A16 or any other example herein, wherein the service producer includes a Management Service Producer (MnS-P).

[0623] Example A18 includes a method, comprising: decoding a tracking job creation request received from a service consumer to create a tracking job for collecting user equipment (UE) level measurement results in a communication network; in response to the tracking job creation request, encoding a tracking session activation request for activating a tracking session to be transmitted to a unified data management (UDM); decoding a tracking session activation response received from the UDM in response to the tracking session activation request, the tracking session activation response being for indicating an activation result of the tracking session; and in response to the tracking session activation response, encoding a tracking job creation response to be transmitted to the service consumer, the tracking job creation response being for indicating a creation result of the tracking job.

[0624] Example A19 includes the method according to Example A18 or any other example herein, wherein the tracking job includes: a job type indicating that the tracking job is for UE level measurement result collection; a tracking target indicating the UE to be measured; administrative attributes for UE level measurement configuration; a public land mobile network (PLMN) target; a job ID; a tracking reference; an Internet protocol (IP) address of a tracking collection entity for file-based tracking reports; a uniform resource identifier (URI) of a tracking report consumer for streaming tracking reports; or a tracking report format.

[0625] Example A20 includes the method according to Example A19 or any other example herein, wherein the administrative attributes for UE level measurement configuration include: UE level measurement results to be collected; a UE level measurement granularity period; an object instance to be measured; or a root object instance of the object to be measured.

[0626] Example A21 includes the method according to Example A18 or any other example herein, wherein the tracking session activation request carries UE level measurement configuration parameters.

[0627] Example A22 includes the method according to Example A21 or any other example herein, wherein the UE level measurement configuration parameters include: a tracking target; a tracking reference; a network element (NE) type for measurement; UE level measurement results of the NE type for measurement; a UE level measurement granularity period; an Internet protocol (IP) address of a tracking collection entity for file-based tracking reports; a uniform resource identifier (URI) of a tracking report consumer for streaming tracking reports; or a tracking report format.

[0628] Example A23 includes the method according to Example A22 or any other example herein, wherein the NE type for measurement includes a fifth generation (5G) core network (5GC) network function (NF) or a next generation (NG) radio access network (RAN) node.

[0629] Example A24 includes the method described in Example A22 or any other example herein, wherein the NE type for measurement includes an access and mobility management function (AMF), and the UE-level measurement configuration parameters are provided to the AMF via a Nudm_SDM_Notification message or a forward relocation request.

[0630] Example A25 includes the method described in Example A22 or any other example herein, wherein the NE type for measurement includes a session management function (SMF), and the UE-level measurement configuration parameters are provided to the SMF via a Nsmf_PDUSession_CreateSMContext request, a Nsmf_PDUSession_UpdateSMContext request, a Nudm_SDM_Notification message, or a Nudm_UECM_Registration procedure.

[0631] Example A26 includes the method described in Example A22 or any other example herein, wherein the NE type for measurement includes a policy control function (PCF), and the UE-level measurement configuration parameters are provided to the PCF via a session management policy establishment procedure or a session management policy modification procedure.

[0632] Example A27 includes the method described in Example A22 or any other example herein, wherein the NE type for measurement includes a user plane function (UPF), and the UE-level measurement configuration parameters are provided to the UPF via an N4 session establishment procedure or an N4 session modification procedure.

[0633] Example A28 includes the method described in Example A22 or any other example herein, wherein the NE type for measurement includes a next generation (NG) radio access network (RAN) node, and the UE-level measurement configuration parameters are provided to the NG-RAN node via a trace start message, an initial context setup request, or a handover request.

[0634] Example A29 includes the method described in Example A28 or any other example herein, wherein the UE-level measurement configuration parameters further include: the type of NG-RAN node for measurement; or the UE-level measurement result of the type of NG-RAN node for measurement.

[0635] Example A30 includes the method described in Example A22 or any other example herein, wherein the trace target includes a subscription permanent identifier (SUPI) or an international mobile station equipment identity and software version number (IMEISV).

[0636] Example A31 includes the method described in Example A18 or any other example herein, and further includes: decoding a tracking job deletion request received from the service consumer to delete the tracking job; encoding a tracking session deactivation request for deactivating the tracking session in response to the tracking job deletion request for transmission to the UDM; decoding a tracking session deactivation response received from the UDM in response to the tracking session deactivation request, the tracking session deactivation response being for indicating a deactivation result of the tracking session; and encoding a tracking job deletion response in response to the tracking session deactivation response for transmission to the service consumer, the tracking job deletion response being for indicating a deletion result of the tracking job.

[0637] Example A32 includes the method described in Example A18 or any other example herein, wherein the service consumer includes a Management Service Consumer (MnS-C).

[0638] Example A33 includes the method described in any one of Examples A18 to A32 or any other example herein, wherein the method is applicable to a service producer.

[0639] Example A34 includes the method described in Example A33 or any other example herein, wherein the service producer includes a Management Service Producer (MnS-P).

[0640] Example A35 includes an apparatus including components for performing the method described in any one of Examples A18 to A34.

[0641] Example A36 includes a computer-readable medium having instructions stored thereon, wherein the instructions, when executed by a processing circuit, cause the processing circuit to perform the method described in any one of Examples A18 to A34.

[0642] Example B1 includes an apparatus including: a memory; and a processor circuit coupled to the memory, wherein the processor circuit is configured to: decode a tracking session activation request received from a service producer to activate a tracking session for a user equipment (UE) level measurement job, the tracking session activation request carrying UE level measurement configuration parameters; and encode a Nudm_SDM_Notification message carrying the UE level measurement configuration parameters for transmission to an Access and Mobility Management Function (AMF) to initiate the tracking session, and wherein the memory is configured to store the UE level measurement configuration parameters.

[0643] Example B2 includes the apparatus described in Example B1 or any other example herein, wherein the UE-level measurement configuration parameters include: a tracking target; a tracking reference; a network element (NE) type for measurement; a UE-level measurement result of the NE type for measurement; a UE-level measurement granularity period; an Internet Protocol (IP) address of a trace collection entity for file-based trace reports; a Uniform Resource Identifier (URI) of a trace report consumer for streaming trace reports; or a trace report format.

[0644] Example B3 includes the apparatus described in Example B2 or any other example herein, wherein the NE type for measurement includes a fifth generation (5G) core network (5GC) network function (NF) or a next generation (NG) radio access network (RAN) node.

[0645] Example B4 includes the apparatus described in Example B2 or any other example herein, the NE type for measurement includes a session management function (SMF), and the UE-level measurement configuration parameters are provided to the SMF via an Nsmf_PDUSession_CreateSMContext request, an Nsmf_PDUSession_UpdateSMContext request, a Nudm_SDM_Notification message, or a Nudm_UECM_Registration procedure.

[0646] Example B5 includes the apparatus described in Example B2 or any other example herein, wherein the NE type for measurement includes a policy control function (PCF), and the UE-level measurement configuration parameters are provided to the PCF via a session management policy establishment procedure or a session management policy modification procedure.

[0647] Example B6 includes the apparatus described in Example B2 or any other example herein, wherein the NE type for measurement includes a user plane function (UPF), and the UE-level measurement configuration parameters are provided to the UPF via an N4 session establishment procedure or an N4 session modification procedure.

[0648] Example B7 includes the apparatus described in Example B2 or any other example herein, wherein the NE type for measurement includes a next generation (NG) radio access network (RAN) node, and the UE-level measurement configuration parameters are provided to the NG-RAN node via a trace start message, an initial context setup request, or a handover request.

[0649] Example B8 includes the apparatus described in Example B7 or any other example herein, wherein the UE-level measurement configuration parameter further includes: the type of NG-RAN node for measurement; or the UE-level measurement result of the type of NG-RAN node for measurement.

[0650] Example B9 includes the apparatus described in Example B2 or any other example herein, wherein the tracking target includes a subscription permanent identifier (SUPI) or an international mobile station equipment identity and software version number (IMEISV).

[0651] Example B10 includes the apparatus described in Example B1 or any other example herein, wherein the processor circuit is further configured to: generate UE-level measurements within a granularity period based on the tracking session activation request to initiate a tracking record session under the tracking session; and report the results of the UE-level measurements for the tracking record session to a tracking collection entity (TCE).

[0652] Example B11 includes the apparatus described in Example B10 or any other example herein, wherein the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0653] Example B12 includes the apparatus described in Example B1 or any other example herein, wherein the processor circuit is further configured to: decode a tracking session deactivation request received from the service producer to deactivate the tracking session; and in response to the tracking session deactivation request, encode another Nudm_SDM_Notification message for transmission to the AMF to stop the tracking session.

[0654] Example B13 includes the apparatus described in Example B12 or any other example herein, wherein the processor circuit is further configured to: stop the tracking record session under the tracking session based on the tracking session deactivation request.

[0655] Example B14 includes the apparatus described in Example B1 or any other example herein, wherein the service producer includes a management service producer (MnS-P).

[0656] Example B15 includes the apparatus described in any one of Examples B1 to B14 or any other example herein, wherein the apparatus is applicable to unified data management (UDM).

[0657] Example B16 includes a method that includes: decoding a trace session activation request received from a service producer to activate a trace session for a user equipment (UE)-level measurement job, the trace session activation request carrying UE-level measurement configuration parameters; and encoding a Nudm_SDM_Notification message carrying the UE-level measurement configuration parameters for transmission to an access and mobility management function (AMF) to initiate the trace session.

[0658] Example B17 includes the method of Example B16 or any other example herein, wherein the UE-level measurement configuration parameters include: a trace target; a trace reference; a network element (NE) type for measurement; a UE-level measurement result of the NE type for measurement; a UE-level measurement granularity period; an Internet protocol (IP) address of a trace collection entity for file-based trace reports; a uniform resource identifier (URI) of a trace report consumer for streaming trace reports; or a trace report format.

[0659] Example B18 includes the method of Example B17 or any other example herein, wherein the NE type for measurement includes a fifth generation (5G) core network (5GC) network function (NF) or a next generation (NG) radio access network (RAN) node.

[0660] Example B19 includes the method of Example B17 or any other example herein, the NE type for measurement includes a session management function (SMF), and the UE-level measurement configuration parameters are provided to the SMF via an Nsmf_PDUSession_CreateSMContext request, an Nsmf_PDUSession_UpdateSMContext request, a Nudm_SDM_Notification message, or a Nudm_UECM_Registration procedure.

[0661] Example B20 includes the method of Example B17 or any other example herein, wherein the NE type for measurement includes a policy control function (PCF), and the UE-level measurement configuration parameters are provided to the PCF via a session management policy establishment procedure or a session management policy modification procedure.

[0662] Example B21 includes the method of Example B17 or any other example herein, wherein the NE type for measurement includes a user plane function (UPF), and the UE-level measurement configuration parameters are provided to the UPF via an N4 session establishment procedure or an N4 session modification procedure.

[0663] Example B22 includes the method described in Example B17 or any other example herein, wherein the NE type for measurement includes a next-generation (NG) radio access network (RAN) node, and the UE-level measurement configuration parameter is provided to the NG-RAN node via a trace start message, an initial context setup request, or a handover request.

[0664] Example B23 includes the method described in Example B22 or any other example herein, wherein the UE-level measurement configuration parameter further includes: the type of NG-RAN node for measurement; or the UE-level measurement result of the type of NG-RAN node for measurement.

[0665] Example B24 includes the method described in Example B17 or any other example herein, wherein the trace target includes a subscription permanent identifier (SUPI) or an international mobile station equipment identity and software version number (IMEISV).

[0666] Example B25 includes the method described in Example B16 or any other example herein, further comprising: generating UE-level measurements within a granularity period based on the trace session activation request to initiate a trace record session under the trace session; and reporting the results of the UE-level measurements for the trace record session to a trace collection entity (TCE).

[0667] Example B26 includes the method described in Example B25 or any other example herein, wherein the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0668] Example B27 includes the method described in Example B16 or any other example herein, further comprising: decoding a trace session deactivation request received from the service producer to deactivate the trace session; and in response to the trace session deactivation request, encoding another Nudm_SDM_Notification message for transmission to the AMF to stop the trace session.

[0669] Example B28 includes the method described in Example B27 or any other example herein, further comprising: stopping the trace record session under the trace session based on the trace session deactivation request.

[0670] Example B29 includes the method described in Example B16 or any other example herein, wherein the service producer includes a management service producer (MnS-P).

[0671] Example B30 includes the method described in any one of Examples B16 to B29 or any other example herein, wherein the method is applicable to unified data management (UDM).

[0672] Example B31 includes an apparatus comprising components for performing the method according to any one of Examples B16 to B30.

[0673] Example B32 includes a computer-readable medium having instructions stored thereon, wherein the instructions, when executed by a processing circuit, cause the processing circuit to perform the method according to any one of Examples B16 to B30.

[0674] Example C1 includes an apparatus comprising: a memory; and a processor circuit coupled to the memory, wherein the processor circuit is configured to: decode a first message received from a network function (NF) to activate a trace session for a user equipment (UE)-level measurement job, the first message carrying UE-level measurement configuration parameters; and encode a second message carrying the UE-level measurement configuration parameters for transmission to a session management function (SMF) to initiate the trace session, wherein the memory is configured to store the UE-level measurement configuration parameters.

[0675] Example C2 includes the apparatus according to Example C1 or any other example herein, wherein the UE-level measurement configuration parameters include: a trace target; a trace reference; a network element (NE) type for measurement; a UE-level measurement result for the NE type for measurement; a UE-level measurement granularity period; an Internet protocol (IP) address of a trace collection entity for file-based trace reports; a uniform resource identifier (URI) of a trace report consumer for streaming trace reports; or a trace report format.

[0676] Example C3 includes the apparatus according to Example C2 or any other example herein, wherein the NE type for measurement includes a fifth generation (5G) core network (5GC) network function (NF) or a next generation (NG) radio access network (RAN) node.

[0677] Example C4 includes the apparatus according to Example C2 or any other example herein, wherein the NE type for measurement includes a policy control function (PCF), and the UE-level measurement configuration parameters are provided to the PCF via a session management policy establishment procedure or a session management policy modification procedure.

[0678] Example C5 includes the apparatus according to Example C2 or any other example herein, wherein the NE type for measurement includes a user plane function (UPF), and the UE-level measurement configuration parameters are provided to the UPF via an N4 session establishment procedure or an N4 session modification procedure.

[0679] Example C6 includes the apparatus described in Example C2 or any other example herein, wherein the NE type for measurement includes a next generation (NG) radio access network (RAN) node, and the UE-level measurement configuration parameter is provided to the NG-RAN node via a trace start message, an initial context setup request, or a handover request.

[0680] Example C7 includes the apparatus described in Example C6 or any other example herein, wherein the UE-level measurement configuration parameter further includes: the type of NG-RAN node for measurement; or the UE-level measurement result of the type of NG-RAN node for measurement.

[0681] Example C8 includes the apparatus described in Example C2 or any other example herein, wherein the trace target includes a subscription permanent identifier (SUPI) or an international mobile station equipment identity and software version number (IMEISV).

[0682] Example C9 includes the apparatus described in Example C1 or any other example herein, wherein the first message includes a Nudm_SDM_Notification message, and the NF includes a unified data management (UDM).

[0683] Example C10 includes the apparatus described in Example C1 or any other example herein, wherein the first message includes a forward relocation request, and the NF includes a mobility management entity (MME).

[0684] Example C11 includes the apparatus described in Example C1 or any other example herein, wherein the second message includes a Nsmf_PDUSession_CreateSMContext request or a Nsmf_PDUSession_UpdateSMContext request.

[0685] Example C12 includes the apparatus described in Example C1 or any other example herein, wherein the processor circuit is further configured to: generate UE-level measurements within a granularity period based on the first message to initiate a trace recording session under the trace session; and report the results of the UE-level measurements for the trace recording session to a trace collection entity (TCE).

[0686] Example C13 includes the apparatus described in Example C12 or any other example herein, wherein the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0687] Example C14 includes the apparatus described in Example C1 or any other example herein, wherein the processor circuit is further configured to: decode the Nudm_SDM_Notification message received from the NF to deactivate the trace session; and in response to the Nudm_SDM_Notification message, encode an Nsmf_PDUSession_UpdateSMContext request for transmission to the SMF to stop the trace session.

[0688] Example C15 includes the apparatus described in Example C14 or any other example herein, wherein the processor circuit is further configured to: stop the trace record session under the trace session based on the Nudm_SDM_Notification message.

[0689] Example C16 includes the apparatus described in any one of Examples C1 to C15 or any other example herein, wherein the apparatus is applicable to an access and mobility management function (AMF).

[0690] Example C17 includes a method, comprising: decoding a first message received from a network function (NF) to activate a trace session for a user equipment (UE)-level measurement job, the first message carrying UE-level measurement configuration parameters; and encoding a second message carrying the UE-level measurement configuration parameters for transmission to a session management function (SMF) to start the trace session.

[0691] Example C18 includes the method described in Example C17 or any other example herein, wherein the UE-level measurement configuration parameters include: a trace target; a trace reference; a network element (NE) type for measurement; a UE-level measurement result of the NE type for measurement; a UE-level measurement granularity period; an Internet protocol (IP) address of a trace collection entity for file-based trace reports; a uniform resource identifier (URI) of a trace report consumer for streaming trace reports; or a trace report format.

[0692] Example C19 includes the method described in Example C18 or any other example herein, wherein the NE type for measurement includes a fifth generation (5G) core network (5GC) network function (NF) or a next generation (NG) radio access network (RAN) node.

[0693] Example C20 includes the method described in Example C18 or any other example herein, wherein the NE type for measurement includes a policy control function (PCF), and the UE-level measurement configuration parameters are provided to the PCF via a session management policy establishment process or a session management policy modification process.

[0694] Example C21 includes the method described in Example C18 or any other example herein, wherein the NE type for measurement includes a User Plane Function (UPF), and the UE-level measurement configuration parameter is provided to the UPF via an N4 session establishment procedure or an N4 session modification procedure.

[0695] Example C22 includes the method described in Example C18 or any other example herein, wherein the NE type for measurement includes a Next Generation (NG) Radio Access Network (RAN) node, and the UE-level measurement configuration parameter is provided to the NG-RAN node via a trace start message, an initial context setup request, or a handover request.

[0696] Example C23 includes the method described in Example C22 or any other example herein, wherein the UE-level measurement configuration parameter further includes: the type of NG-RAN node for measurement; or the UE-level measurement result of the type of NG-RAN node for measurement.

[0697] Example C24 includes the method described in Example C18 or any other example herein, wherein the trace target includes a Subscription Permanent Identifier (SUPI) or an International Mobile Station Equipment Identity and Software Version Number (IMEISV).

[0698] Example C25 includes the method described in Example C17 or any other example herein, wherein the first message includes a Nudm_SDM_Notification message, and the NF includes a Unified Data Management (UDM).

[0699] Example C26 includes the method described in Example C17 or any other example herein, wherein the first message includes a forward relocation request, and the NF includes a Mobility Management Entity (MME).

[0700] Example C27 includes the method described in Example C17 or any other example herein, wherein the second message includes an Nsmf_PDUSession_CreateSMContext request or an Nsmf_PDUSession_UpdateSMContext request.

[0701] Example C28 includes the method described in Example C17 or any other example herein, further comprising: generating UE-level measurements within a granularity period based on the first message to initiate a trace record session under the trace session; and reporting the results of the UE-level measurements for the trace record session to a Trace Collection Entity (TCE).

[0702] Example C29 includes the method described in Example C28 or any other example herein, wherein the result of the UE-level measurement is reported via a file-based report or a flow-based report.

[0703] Example C30 includes the method described in Example C17 or any other example herein, further comprising: decoding the Nudm_SDM_Notification message received from the NF to deactivate the trace session; and in response to the Nudm_SDM_Notification message, encoding an Nsmf_PDUSession_UpdateSMContext request for transmission to the SMF to stop the trace session.

[0704] Example C31 includes the method described in Example C30 or any other example herein, further comprising: stopping the trace record session under the trace session based on the Nudm_SDM_Notification message.

[0705] Example C32 includes the method described in any one of Examples C17 to C31 or any other example herein, wherein the method is applicable to an access and mobility management function (AMF).

[0706] Example C33 includes an apparatus comprising components for performing the method described in any one of Examples C17 to C32.

[0707] Example C34 includes a computer-readable medium having instructions stored thereon, wherein the instructions, when executed by a processing circuit, cause the processing circuit to perform the method described in any one of Examples C17 to C32.

[0708] Example D1 includes an apparatus comprising: a memory; and a processor circuit coupled to the memory, wherein the processor circuit is configured to: decode a first message received from a network function (NF) to activate a trace session for a user equipment (UE)-level measurement job, the first message carrying UE-level measurement configuration parameters; and encode a second message carrying the UE-level measurement configuration parameters for transmission to a policy control function (PCF) to start the trace session, wherein the memory is used to store the UE-level measurement configuration parameters.

[0709] Example D2 includes the apparatus described in Example D1 or any other example herein, wherein the UE-level measurement configuration parameters include: a tracking target; a tracking reference; a network element (NE) type for measurement; a UE-level measurement result of the NE type for measurement; a UE-level measurement granularity period; an Internet Protocol (IP) address of a trace collection entity for file-based trace reports; a Uniform Resource Identifier (URI) of a trace report consumer for streaming trace reports; or a trace report format.

[0710] Example D3 includes the apparatus described in Example D2 or any other example herein, wherein the NE type for measurement includes a fifth-generation (5G) core network (5GC) network function (NF) or a next-generation (NG) radio access network (RAN) node.

[0711] Example D4 includes the apparatus described in Example D2 or any other example herein, wherein the tracking target includes a subscription permanent identifier (SUPI) or an International Mobile Station Equipment Identity and Software Version Number (IMEISV).

[0712] Example D5 includes the apparatus described in Example D1 or any other example herein, wherein the first message includes an Nsmf_PDUSession_CreateSMContext request or an Nsmf_PDUSession_UpdateSMContext request, and the NF includes an access and mobility management function (AMF).

[0713] Example D6 includes the apparatus described in Example D1 or any other example herein, wherein the first message includes an Nudm_SDM_Notification message or an Nudm_UECM_Registration message, and the NF includes a unified data management (UDM).

[0714] Example D7 includes the apparatus described in Example D1 or any other example herein, wherein the second message includes a session management policy establishment message or a session management policy modification message.

[0715] Example D8 includes the apparatus described in Example D1 or any other example herein, wherein the processor circuit is further configured to: generate UE-level measurements within a granularity period based on the first message to initiate a trace recording session under the trace session; and report the results of the UE-level measurements for the trace recording session to a trace collection entity (TCE).

[0716] Example D9 includes the apparatus described in Example D8 or any other example herein, wherein the results of the UE-level measurements are reported via file-based reports or stream-based reports.

[0717] Example D10 includes the apparatus described in Example D1 or any other example herein, wherein the processor circuit is further configured to: decode a third message received from the NF to deactivate the tracking session; and in response to the third message, initiate a session management policy modification process with the PCF to stop the tracking session.

[0718] Example D11 includes the apparatus described in Example D10 or any other example herein, wherein the processor circuit is further configured to: stop the trace record session under the tracking session based on the third message.

[0719] Example D12 includes the apparatus described in Example D10 or any other example herein, wherein the third message includes an Nsmf_PDUSession_UpdateSMContext request, and the NF includes an access and mobility management function (AMF).

[0720] Example D13 includes the apparatus described in Example D10 or any other example herein, wherein the third message includes an Nudm_SDM_Notification message, and the NF includes a unified data management (UDM).

[0721] Example D14 includes the apparatus described in any one of Examples D1 to D13 or any other example herein, wherein the apparatus is applicable to a session management function (SMF).

[0722] Example D15 includes a method, comprising: decoding a first message received from a network function (NF) to activate a tracking session for a user equipment (UE)-level measurement job, the first message carrying UE-level measurement configuration parameters; and encoding a second message carrying the UE-level measurement configuration parameters for transmission to a policy control function (PCF) to initiate the tracking session.

[0723] Example D16 includes the method described in Example D15 or any other example herein, wherein the UE-level measurement configuration parameters include: a tracking target; a tracking reference; a network element (NE) type for measurement; a UE-level measurement result of the NE type for measurement; a UE-level measurement granularity period; an Internet protocol (IP) address of a trace collection entity for file-based trace reports; a uniform resource identifier (URI) of a trace report consumer for streaming trace reports; or a trace report format.

[0724] Example D17 includes the method described in Example D16 or any other example herein, wherein the NE type for measurement includes a fifth-generation (5G) core network (5GC) network function (NF) or a next-generation (NG) radio access network (RAN) node.

[0725] Example D18 includes the method described in Example D16 or any other example herein, wherein the tracking target includes a Subscription Permanent Identifier (SUPI) or an International Mobile Station Equipment Identity and Software Version Number (IMEISV).

[0726] Example D19 includes the method described in Example D15 or any other example herein, wherein the first message includes an Nsmf_PDUSession_CreateSMContext request or an Nsmf_PDUSession_UpdateSMContext request, and the NF includes an Access and Mobility Management Function (AMF).

[0727] Example D20 includes the method described in Example D15 or any other example herein, wherein the first message includes a Nudm_SDM_Notification message or a Nudm_UECM_Registration message, and the NF includes a Unified Data Management (UDM).

[0728] Example D21 includes the method described in Example D15 or any other example herein, wherein the second message includes a session management policy establishment message or a session management policy modification message.

[0729] Example D22 includes the method described in Example D15 or any other example herein, further comprising: generating UE-level measurements within a granularity period based on the first message to initiate a tracking record session under the tracking session; and reporting the results of the UE-level measurements for the tracking record session to a Tracking Collection Entity (TCE).

[0730] Example D23 includes the method described in Example D22 or any other example herein, wherein the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0731] Example D24 includes the method described in Example D15 or any other example herein, further comprising: decoding a third message received from the NF to deactivate the tracking session; and in response to the third message, initiating a session management policy modification procedure with the PCF to stop the tracking session.

[0732] Example D25 includes the method described in Example D24 or any other example herein, further comprising: stopping the tracking record session under the tracking session based on the third message.

[0733] Example D26 includes the method described in Example D24 or any other example herein, wherein the third message includes an Nsmf_PDUSession_UpdateSMContext request, and the NF includes an access and mobility management function (AMF).

[0734] Example D27 includes the method described in Example D24 or any other example herein, wherein the third message includes an Nudm_SDM_Notification message, and the NF includes a unified data management (UDM).

[0735] Example D28 includes the method described in any one of Examples D15 to D27 or any other example herein, wherein the method is applicable to a session management function (SMF).

[0736] Example D29 includes an apparatus comprising components for performing the method described in any one of Examples D15 to D28.

[0737] Example D30 includes a computer-readable medium having instructions stored thereon, wherein the instructions, when executed by a processing circuit, cause the processing circuit to perform the method described in any one of Examples D15 to D28.

[0738] Example E1 includes an apparatus comprising: a memory; and a processor circuit coupled to the memory, wherein the processor circuit is configured to: decode a session management policy establishment message or a session management policy modification message received from a session management function (SMF) to activate a trace session for a user equipment (UE)-level measurement job, the session management policy establishment message or the session management policy modification message carrying UE-level measurement configuration parameters; and initiate the trace session, wherein the memory is configured to store the UE-level measurement configuration parameters.

[0739] Example E2 includes the apparatus described in Example E1 or any other example herein, wherein the UE-level measurement configuration parameters include: a trace target; a trace reference; a network element (NE) type for measurement; a UE-level measurement result of the NE type for measurement; a UE-level measurement granularity period; an Internet protocol (IP) address of a trace collection entity for file-based trace reports; a uniform resource identifier (URI) of a trace report consumer for streaming trace reports; or a trace report format.

[0740] Example E3 includes the apparatus described in Example E2 or any other example herein, wherein the NE type for measurement includes a fifth-generation (5G) core network (5GC) network function (NF) or a next-generation (NG) radio access network (RAN) node.

[0741] Example E4 includes the apparatus described in Example E2 or any other example herein, wherein the tracking target includes a Subscription Permanent Identifier (SUPI) or an International Mobile Station Equipment Identity and Software Version Number (IMEISV).

[0742] Example E5 includes the apparatus described in Example E1 or any other example herein, wherein the processor circuitry is further configured to: generate UE-level measurements within a granularity period based on the session management policy establishment message or the session management policy modification message to initiate a trace recording session under the trace session; and report the results of the UE-level measurements for the trace recording session to a Trace Collection Entity (TCE).

[0743] Example E6 includes the apparatus described in Example E5 or any other example herein, wherein the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0744] Example E7 includes the apparatus described in Example E1 or any other example herein, wherein the processor circuitry is further configured to: decode another session management policy modification message received from the SMF to deactivate the trace session; and stop the trace session based on the another session management policy modification message.

[0745] Example E8 includes the apparatus described in Example E7 or any other example herein, wherein the processor circuitry is further configured to: stop the trace recording session under the trace session based on the another session management policy modification message.

[0746] Example E9 includes the apparatus described in any one of Examples E1 to E8 or any other example herein, wherein the apparatus is applicable to a Policy Control Function (PCF).

[0747] Example E10 includes a method, comprising: decoding a session management policy establishment message or a session management policy modification message received from a Session Management Function (SMF) to activate a trace session for a User Equipment (UE)-level measurement job, the session management policy establishment message or the session management policy modification message carrying UE-level measurement configuration parameters; and initiating the trace session.

[0748] Example E11 includes the method described in Example E10 or any other example herein, wherein the UE-level measurement configuration parameters include: a tracking target; a tracking reference; a Network Element (NE) type for measurement; a UE-level measurement result for the NE type for measurement; a UE-level measurement granularity period; an Internet Protocol (IP) address of a Trace Collection Entity for file-based trace reporting; a Uniform Resource Identifier (URI) of a Trace Report Consumer for streaming trace reporting; or a trace report format.

[0749] Example E12 includes the method described in Example E11 or any other example herein, wherein the NE type for measurement includes a fifth-generation (5G) core network (5GC) network function (NF) or a next-generation (NG) radio access network (RAN) node.

[0750] Example E13 includes the method described in Example E11 or any other example herein, wherein the tracking target includes a subscription permanent identifier (SUPI) or an international mobile station equipment identity and software version number (IMEISV).

[0751] Example E14 includes the method described in Example E10 or any other example herein, further comprising: generating UE-level measurements within a granularity period based on the session management policy establishment message or the session management policy modification message to initiate a tracking record session under the tracking session; and reporting the results of the UE-level measurements for the tracking record session to a tracking collection entity (TCE).

[0752] Example E15 includes the method described in Example E14 or any other example herein, wherein the results of the UE-level measurements are reported via file-based reporting or flow-based reporting.

[0753] Example E16 includes the method described in Example E10 or any other example herein, further comprising: decoding another session management policy modification message received from the SMF to deacti...

Claims

1. An apparatus, comprising: An interface circuit; And A processor circuit, the processor circuit being coupled to the interface circuit, Wherein, the processor circuit is configured to: Decode a tracking job creation request received from a service consumer via the interface circuit to create a tracking job for collecting user equipment (UE) level measurement results in a communication network; In response to the tracking job creation request, encode a tracking session activation request for activating a tracking session to be transmitted to a unified data management (UDM); Decode a tracking session activation response received from the UDM in response to the tracking session activation request, the tracking session activation response being used to indicate the activation result of the tracking session; and In response to the tracking session activation response, encode a tracking job creation response to be transmitted to the service consumer via the interface circuit, the tracking job creation response being used to indicate the creation result of the tracking job.

2. The device according to claim 1, wherein The tracking job includes: A job type, indicating that the tracking job is for UE level measurement result collection; A tracking target, indicating the UE to be measured; Administrative attributes for UE level measurement configuration; A public land mobile network (PLMN) target; A job ID; A tracking reference; The Internet Protocol (IP) address of a tracking collection entity for file-based tracking reports; The uniform resource identifier (URI) of a tracking report consumer for streaming tracking reports; or A tracking report format.

3. The device according to claim 2, wherein, The administrative attributes for UE level measurement configuration include: UE level measurement results to be collected; The UE level measurement granularity period; The object instance to be measured; or The root object instance of the object to be measured.

4. The device according to claim 1, wherein The tracking session activation request carries UE level measurement configuration parameters.

5. The device according to claim 4, wherein, The UE level measurement configuration parameters include: A tracking target; A tracking reference; The type of network element (NE) for measurement; The UE level measurement results of the NE type for measurement; The UE level measurement granularity period; The Internet Protocol (IP) address of a tracking collection entity for file-based tracking reports; The uniform resource identifier (URI) of a tracking report consumer for streaming tracking reports; or A tracking report format.

6. The device according to claim 5, wherein The NE type for measurement includes a fifth generation (5G) core network (5GC) network function (NF) or a next generation (NG) radio access network (RAN) node.

7. The apparatus according to claim 5, wherein The NE type for measurement includes an access and mobility management function (AMF), and the UE level measurement configuration parameters are provided to the AMF via a Nudm_SDM_Notification message or a forward relocation request.

8. The device according to claim 5, wherein, The NE types for measurement include Session Management Function (SMF), and the UE-level measurement configuration parameters are provided to the SMF via an Nsmf_PDUSession_CreateSMContext request, an Nsmf_PDUSession_UpdateSMContext request, an Nudm_SDM_Notification message, or an Nudm_UECM_Registration procedure.

9. The apparatus according to claim 5, wherein The NE types for measurement include Policy Control Function (PCF), and the UE-level measurement configuration parameters are provided to the PCF via a session management policy establishment procedure or a session management policy modification procedure.

10. The device according to claim 5, wherein The NE types for measurement include User Plane Function (UPF), and the UE-level measurement configuration parameters are provided to the UPF via an N4 session establishment procedure or an N4 session modification procedure.

11. The device according to claim 5, wherein The NE types for measurement include Next Generation (NG) Radio Access Network (RAN) nodes, and the UE-level measurement configuration parameters are provided to the NG-RAN nodes via a trace start message, an initial context setup request, or a handover request.

12. The device according to claim 11, wherein, The UE-level measurement configuration parameters further include: the NG-RAN node types for measurement; or the UE-level measurement results of the NG-RAN node types for measurement.

13. The device according to claim 5, wherein, The trace targets include Subscription Permanent Identifier (SUPI) or International Mobile Station Equipment Identity and Software Version Number (IMEISV).

14. The device according to claim 1, wherein, The processor circuit is further configured to: decode a trace job deletion request received from the service consumer via the interface circuit to delete the trace job; in response to the trace job deletion request, encode a trace session deactivation request for deactivating the trace session to be transmitted to the UDM; decode a trace session deactivation response received from the UDM in response to the trace session deactivation request, the trace session deactivation response being used to indicate the deactivation result of the trace session; and in response to the trace session deactivation response, encode a trace job deletion response to be transmitted to the service consumer via the interface circuit, the trace job deletion response being used to indicate the deletion result of the trace job.

15. The device according to claim 1, wherein, The service consumer includes a Management Service Consumer (MnS-C).

16. The device according to any one of claims 1 to 15, wherein The apparatus is applicable to a Management Service Producer (MnS-P).

17. An apparatus, comprising: a memory; and a processor circuit coupled to the memory, wherein the processor circuit is configured to: decode a first message received from a first Network Function (NF) or a first Next Generation (NG) Radio Access Network (RAN) node to activate a trace session for a User Equipment (UE)-level measurement job, the first message carrying UE-level measurement configuration parameters; and initiate the trace session, and wherein the memory is used to store the UE-level measurement configuration parameters.

18. The apparatus according to claim 17, wherein The UE-level measurement configuration parameters include: trace targets; trace references; NG-RAN node type for measurement; UE-level measurement result of the NG-RAN node type for measurement; UE-level measurement granularity period; Internet Protocol (IP) address of the trace collection entity for file-based trace reports; Uniform Resource Identifier (URI) of the trace report consumer for streaming trace reports; or Trace report format.

19. The apparatus according to claim 17, wherein, The first message includes: A trace start message, an initial context setup request, or an NG handover request received from the Access and Mobility Management Function (AMF); An Xn handover request or an Xn get UE context response received from the first NG-RAN node; A trace session activation request received from the management system; A Nudm_SDM_Notification message received from the Unified Data Management (UDM); A forward relocation request received from the Mobility Management Entity (MME); A Nsmf_PDUSession_CreateSMContext request or a Nsmf_PDUSession_UpdateSMContext request received from the AMF; A Nudm_SDM_Notification message or a Nudm_UECM_Registration message received from the UDM; A session management policy establishment message or a session management policy modification message received from the Session Management Function (SMF); or A N4 session establishment message or a N4 session modification message received from the SMF.

20. The apparatus according to claim 17, wherein, The device is applicable to a second NF or a second NG-RAN node.

Images