Data collection coordination function and network data analysis function framework for collection services in next-generation mobile networks

Abstract

This disclosure describes systems, methods, and devices associated with collection service coordination. A device may discover a network data analysis capability (NWDAF) through a network function repository capability (NRF). The device may send an analysis request or subscribe to the selected NWDAF with a criterion based on a collection data analysis ID, an event ID, and event parameters. The device may select an instance of a data collection coordination function (DCCF), when DCCF is used for data collection, based on DCCF coverage area information. The device may receive collection data or data analysis from the NWDAF after the NWDAF processes the data collected by the DCCF.

Description

CROSS-REFERENCE TO RELATED PATENT APPLICATION(S)

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 412,786, filed October 3, 2022, the disclosure of which is incorporated herein by reference as if fully set forth. TECHNICAL FIELD

[0002] This disclosure relates generally to systems and methods for wireless communications, and more particularly to a data collection coordination functions (DCCF) / network data analysis functions (NWDAF) framework for sensing services in next generation cellular networks. STATE OF THE ART

[0003] The Data Collection Coordination Function (DCCF) and the Network Data Analysis Function (NWDAF) are critical components in a modern telecommunications infrastructure, designed to guide network performance and end device (UE)-related data collection and analysis. However, the current framework is narrowly focused and excludes one category of valuable information: sensing data. As networks evolve, sensing data is becoming increasingly important for applications such as IoT, autonomous vehicles, and smart cities. Although the existing DCCF and NWDAF models excel at collecting and analyzing metrics related to network efficiency and UE behavior, they lack a standardized interface for integrating sensing data.This omission represents a significant gap, highlighting the need for an improved framework that can seamlessly integrate this important category of data into existing models. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1-7 depict illustrative schematic diagrams for collection service coordination according to one or more embodiments of the present disclosure. Fig. 8 illustrates a flow diagram of a process for an illustrative collection service coordination system according to one or more embodiments of the present disclosure. Fig. 9 illustrates an example network architecture according to one or more embodiments of the present disclosure. Fig. 10 schematically illustrates a wireless network according to one or more embodiments of the present disclosure. Fig. 11 illustrates components of a computing device according to one or more embodiments of the present disclosure. Fig. 12 illustrates a network according to various embodiments. DETAILED DESCRIPTION

[0004] The following description and drawings illustrate specific embodiments sufficiently to enable those skilled in the art to implement them. Other embodiments may incorporate structural, logical, electrical, process, algorithmic, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments recited in the claims include all available equivalents of those claims.

[0005] The framework for Data Collection Coordination Functions (DCCF) and Network Data Analysis Functions (NWDAF) is specified with different defined analyses and events that do not include sensing data. The current DCCF and NWDAF framework is primarily specified for collecting network performance data and UE-related data. It does not provide a standardized interface for handling sensing-related data. Therefore, there is a need for an improved framework that can integrate sensing data into the existing DCCF and NWDAF models.

[0006] Example embodiments of the present disclosure relate to systems, methods, and apparatus for a DCCF / NWDAF framework for sensing services in next generation mobile networks.

[0007] This disclosure provides solutions for at least the following scenarios. -The Collection Service Management Function (SSMF) architecture for interfacing with the Data Collection Coordination Function (DCCF) and the Network Data Analysis Function (NWDAF), Analysis Data Repository Function (ADRF). -The information exchanged between SSMF, DCCF and NWDAF to identify collection data and associated data filters. -The message flows for the collection data to be collected, transmitted, processed, and retrieved using the DCCF and NWDAF framework.

[0008] In one embodiment, a collection service coordination system may enable the collection service-related identifiers and information elements (IEs), i.e., the analysis ID, collection data filters, and collection event IDs, defined for SSMF to leverage the NWDAF / DCCF framework for collecting, processing, transmitting, and retrieving collection data. Example message flows are provided between SSMF and NWDAF, DCCF, and ADRF via the newly defined interfaces NS5, NS6, and NS7. One advantage of the collection service coordination system is that the cloudification of telecommunications networks requires additional computing infrastructure.

[0009] The above descriptions are illustrative and not limiting. Numerous other examples, configurations, processes, algorithms, etc., may exist, some of which are described in more detail below. Example embodiments will now be described with reference to the accompanying figures.

[0010] Fig. 1 depicts an illustrative schematic diagram for a collection service coordination according to one or more embodiments of the present disclosure.

[0011] With reference to Fig. 1 shows the architecture for DCCF / NWDAF data-related functions.

[0012] Three use cases for sensing services for COVID-19 and beyond were agreed upon in 3GPP SA1, including smart homes, highway animal detection, and weather monitoring. To enable a sensing service, a sensing service management function (SSMF) can be used to maintain the sensing service logic, algorithms, policies, and configurations. The SSMF connects to the RAN via AMF or a newly defined service-based interface (SBI) called NS2 to exchange sensing-related data and notifications.

[0013] To determine the amount of data exchanged between the RAN and CN, studies based on typical KPI requirements for the acquisition service and processing pipelines show that the amount of data per ray per frame can be very high, up to Gbits or even Tbits, if the RAN were to send the intermediate processing results to the CN. On the other hand, acquisition data is very valuable in generating a variety of results, ranging from basic acquisition goals, including object detection, to shape identification and object motion tracking (which are more advanced goals typically achievable through advanced post-processing). All such processing typically requires a large amount of acquisition data. Analytics can be generated based on applying AI / ML or post-processing the acquisition data.Therefore, the DCCF / NWDAF framework can be used to collect, transmit, post-process, and deliver detection data.

[0014] As defined in TS 23.288, Architecture Enhancements for 5G System (5GS) to support network data analytics services, the NWDAF includes two functions: a logical analysis function (AnLF) and a logical model training function (MTLF). The NWDAF can optionally include one or both functions. The DCCF is responsible for data collection, which could potentially prevent the same data from being collected multiple times, and is responsible for storing the data registry, preprocessing collected data, etc. DCCF / NWDAF can also work with the analytics data repository function (ADRF) to store the data and the messaging framework to deliver data efficiently via a messaging framework adapter function (MFAF). The architecture for these functions is described in Fig. 1 recorded.

[0015] In some embodiments, network data analytics are identified by an analytics ID and associated information, as shown in the table below (Table 7.1-2). Analysis information Requirements description Answer description Slice utilization level information Analysis ID: Load Level Information Utilization level provided as number of UE registrations and number of PDU sessions for a network slice and network slice instances, as well as resource utilization for network slice instances. Observed service experience information Analysis ID: Service Experience Observed service experience statistics or predictions can be provided for a network slice or application. They can be derived from a single UE, a group of UEs, or any UE. For a sliced service experience, they can be derived from an application, a set of applications, or all applications on the network slice. NF utilization information Analysis ID: NF Load Information Utilization statistics or forecast information for specific NF(s). Network performance information Analysis ID: Network Performance Statistics or predictions about the utilization in an area of interest; additionally, statistics or predictions about the number of UEs located in that area of interest. UE mobility information Analysis ID: UE Mobility Statistics or predictions on UE mobility. If visited AOI(s) are included in the analysis filter information, only statistics on UE mobility can be provided. UE communication information Analysis ID: UE Communication Statistics or predictions about UE communication. Expected UE behavior parameters Analysis ID: UE Mobility and / or UE Communication Analyses of UE mobility and / or UE communication. Information about abnormal UE behavior Analysis ID: Abnormal Behavior List of observed or expected exceptions, with exception ID, exception level, and other information depending on the observed or expected exceptions. User data backup information Analysis ID: User Data Congestion Statistics or predictions about user data congestion for transfer via the user plane, for transfer via the control plane, or both. QoS maintenance Analysis ID: QoS Sustainability For statistics, information about the location and time of the QoS change and the one or more thresholds that were exceeded; or for predictions, information about the location and time at which a potential QoS change may occur and which one or more thresholds may be exceeded. Session management congestion control experience Analysis ID: Session Management Congestion Control Experience Statistics on session management congestion control experience for specific DNN and / or S-NSSAI. Redundant transmission experience Analysis ID: Redundant Transmission Experience Statistics or predictions aimed at supporting redundant transmission decisions for URLLC services. Wi-Fi performance Analysis ID: WLAN Performance Statistics or predictions about the UE's Wi-Fi performance. Dispersion Analysis ID: UE Dispersion Statistics or predictions that identify the location (e.g., areas of interest) or network slice(s) where a UE or group of UEs distribute their data volume or distribute mobility or session management transactions, or both. DN performance Analysis ID: DN Performance User-level performance statistics or predictions for a specific edge computing application.

[0016] Among other things, embodiments of the present disclosure aim to provide solutions for: -The architecture for SSMF to connect to DCCF and NWDAF, ADRF. -The information exchanged between SSMF, DCCF and NWDAF to identify collection data and associated data filters. -The message flows for the collection data to be collected, transmitted, processed, and retrieved using the DCCF and NWDAF framework.

[0017] The DCCF and NWDAF framework is specified in TS 23.288, where various analyses and events are defined that do not involve sensing data. Furthermore, the current DCCF and NWDAF framework is primarily specified for collecting network performance data and UE-related data. It does not provide a standardized interface for handling sensing-related data. Embodiments of the present disclosure address these and other issues.

[0018] Some embodiments address collection service-related identifiers and IEs, such as the Analysis ID, collection data filters, and collection event IDs, defined for SSMF to leverage the NWDAF / DCCF framework for collecting, processing, transmitting, and retrieving collection data. Example message flows are provided between SSMF and NWDAF, DCCF, and ADRF via the newly defined interfaces NS5, NS6, and NS7.

[0019] Fig.2 depicts an illustrative schematic diagram for a collection service coordination according to one or more embodiments of the present disclosure.

[0020] With reference to Fig. 2 shows a reference architecture for a capture service.

[0021] Architecture for collecting, delivering, and processing detection data using the DCCF / NWDAF framework: In some embodiments, a sensing service management function (SSMF) may be used to control sensing services connected to the RAN via the AMF or a new SBI called NS2. In some embodiments, the interface between the SSMF and DCCF, the SSMF and NWDAF, and the SSMF and ADRF is referred to as NS5, NS6, and NS7, respectively. The RAN connects to the ADRF via NADRF or via N2 through the AMF. In various embodiments, the RAN may: -Connect to the Client Node (CN) Service-Based Architecture (SBA) over N2', which is an enhanced SBI over N2, allowing the RAN to consume ADRF services. -Connect to a co-located ADRF in the RAN via NADRF. -Connect to a new Service-Based Interface (SBI) between the RAN and the ADRF to consume ADRF services while N2 remains unchanged.

[0022] Similar to CN SBA, producer functions register with the NRF about their services with associated parameters and identifiers introduced below, so that the consumer function can discover a service or analytics producer using the identifiers, data and analytics filters. Collection data identifiers:

[0023] Collection data identifiers, such as analytics ID, collection event ID, and collection data filter, are the information used to describe and provide metadata for and retrieve collection data. A new analytics ID (or multiple ones): The collection service is added as an additional analytics ID for collection data in the NWDAF, shown in bold below. Analysis information Requirements description Answer description Slice utilization level information Analysis ID: Load Level Information Utilization level provided as number of UE registrations and number of PDU sessions for a network slice and network slice instances, as well as resource utilization for network slice instances. ... ... ... Collection service data Analysis ID: Sensing Service Capture data at different processing levels based on location, time window, frequency, update rate, detection angle, etc. .

[0024] It should be noted that there may be multiple analytics IDs related to collection services based on different use cases, which is outside the scope of this disclosure.

[0025] The collection data filter parameters are also defined to collect, describe, and retrieve the collection data and analytics. These collection data parameters can also be accessed as metadata for the collection service and can be used by the DCCF for data collection, by the ADRF for data storage, by the NWDAF for analytics-related processing, and so on. Table 1 Metadata for capture service: parameter Description Covered location The location of the capture job can be defined, for example, as a center point (latitude, longitude) and radius, angle from the center. mode NW-based or UE-based Timestamp Time at which the data is collected Refresh rate How often the capture task is repeated Position of the transmitter The position of the transmitter of the detection signal Position of the receiver The position of the receiver of the detection signal Field of view The field of view of the detection signal Acquisition resolution Accuracy of recording Data type The data type, the processing point in the collection, see Fig. 3 Data volume The total amount of data Recommended purpose - Object detection - Object range / speed / angle estimation - Object tracking - Object shape identification Confidence level The confidence level of the data

[0026] Collection event IDs must be defined to enable other NFs to be notified of the events and request data for a specific event related to the collection, listed in Table 2. The event notifications can be sent between RAN, SSMF, and NWDAF / DCCF / ADRF / NRF and act as a trigger for other processes. Example consumers are also listed below. Table 2: Event IDs for Collection Service: Event Event parameter name Parameter values Attribute Example consumption-NF Capture target status update Capture target indicator Detected Not detected Detection error - Indicator of whether the target is detected or not SSMF, DCCF, NWDAF Capture target mobility Acquisition target movement Detection target moves into or out of an area - Indicate that the detection target 1 is moving to another area - Indicate that the detection target 1 is moving to the area SSMF, DCCF, NWDAF Capture configuration update Collection configuration update 1. The required recording KPIs, e.g. • Refresh rate • Max detectable speed • Max detectable range • Field of view and / or angle of view • Speed resolution • Range resolution • Angular resolution • Speed, range, angle detection accuracy - View changes in any of the acquisition-related configurations RAN, SSMF 2. The acquisition reference signal configuration. Note: Acquisition reference signal attributes are derived and configured from KPIs. However, the acquisition reference signal configuration can be listed separately. 3. Acquisition measurement (or data) collection point (processing stage) Capability update Capability Acquisition accuracy, update rate, data processing level - Indication of a change in the detection capability of the RAN SSMF, AF Collection QoS update Collection Service QoS Detection accuracy, update rate - Indication of a change in the required collection service QoS SSMF, AF, RAN

[0027] Fig. 3 depicts an illustrative schematic diagram for a capture service coordination according to one or more embodiments of the present disclosure.

[0028] With reference to Fig. 3 shows an example of the acquisition target detection receiver processing.

[0029] Message flows for collection and delivery of capture data: Collection data storage:

[0030] The current DCCF / NWDAF framework does not restrict where data should be stored. Depending on the network deployment, an NWDAF and ADRF can be co-located, or they can be two separate network functions communicating via the NWDAF interface. The consumer NF, e.g., NWDAF or DCCF, requests the ADRF to store data or analytics. In this disclosure, the sensing data or sensing data analytics can be stored in the ADRF or the NWDAF. Different functions can trigger data sensing, such as RAN, NWDAF, and SSMF. If the NWDAF is the producer of the sensing data analytics, the NWDAF initiates data sensing based on the sensing data analytics request from the NF consumer, either by subscribing to the data sensing directly from the producer or via the DCCF. Sensing data sensing by the SSMF is outside the scope of this disclosure. Capturing data storage in the ADRF directly without DCCF:

[0031] The ADRF may collect and store detection data without DCCF, as described in Fig. 4 Error! Reference source not found. In certain embodiments, an ADRF may be co-located with the RAN. If the ADRF is a network function in the CN, the RAN may be connected to the ADRF via an SBI (NADRF). With this option, the RAN initiates the transfer of sensing data.

[0032] With reference to Fig. 4 there is a RAN requirement for the ADRF to store detection-related data via NADRF. 1) RAN sends a Nadrf_dataManagement_StoreRequest or Nadrf_dataManagement_StorageSubscriptionRequest to the ADRF to request or subscribe to store the collection data. This message must include the metadata for the collection data. a. Capture service along with the event ID as described in Table 2 if this save operation is triggered by an event b. The metadata describing the acquisition data 2) ADRF sends a Nadrf_dataManagement_StoreResponse or Nadrf_dataManagement_StorageSubscriptionResponse to indicate whether the storage or subscription of the collection data is successful.

[0033] The SSMF may establish collection data collection through the ADRF as part of the collection configuration process, as described in Fig. 5 shown.

[0034] With reference to Fig. Figure 5 shows a capture data collection configuration by the SSMF. 1) The SSMF sends an NS2-sensingConfiguration request to the RAN containing the data collection instructions. In addition to the configuration-related parameters (outside the scope of this disclosure), this message should include how the sensing data should be collected, an analysis ID (analyses for which collected data is requested or needed), a reporting threshold, a data storage endpoint (example - ADRF), a data collection target period (when data collection should be started and stopped), the sensing events to which the SSMF subscribes, and how the sensing data should be stored. In one example, the SSMF can instruct the RAN to store the sensing data with a filter, as described in Table 2, to be stored directly in the ADRF with an ADRF identifier, such as IP address, function ID, URI, etc.The RAN may also specify the capture data storage capability when the capture capabilities are registered with the SSMF. 2) The RAN sends an NS2_sensingConfiguration_response to the SSMF to indicate the configuration results.

[0035] Data collection by the DCCF: The SSMF may request a collection of detection data from the DCCF, which may further request a collection of data from the RAN as set out in Fig. 5. It should be noted that multiple BSs or UEs may be involved.

[0036] With reference to Fig. Figure 6 shows a process for data collection by the DCCF. 1) The SSMF can use an NRF to perform NF discovery and selection to find a DCCF that can coordinate data collection. The SSMF sends a subscription request for collection data collection to the DCCF with the required preprocessing and formatting. This message must include the collection analysis ID, the collection data filter, [ADRF endpoint], and [RAN identifier]. If the data relates to a specific event defined in Table 2, the event ID must be included. If an NWDAF subscribes to data directly from a RAN or a RAN has stored data in an ADRF, the NWDAF or ADRF can register the data collection profile (the NWDAF ID or ADRF ID specifies the ADRF or NWDAF registering the data collection profile) with the DCCF. 2) Optionally, the DCCF may check with the UDM or UDR whether this sensing data collection is permitted or the user's consent if any UE is involved. 3) The DCCF checks whether the required data corresponding to the capture analysis ID is already being collected. If not, the DCCF sends a data subscription request to the RAN with the requested capture data filter, as described in Table 2, with the DCCF specified as the notification destination. The RAN sends a data subscription response to indicate the subscription results. If the data is collected, the RAN can notify the DCCF and send the capture data to the DCCF. This message exchange requires capture data along with metadata to tag the data. When the capture data is sent to the DCCF, an MFAF can be used for data delivery. 4) The DCCF may perform further data processing and formatting based on the requests sent by the SSMF in step 1. 5) The DCCF notifies the SSMF and one or more additional notification endpoints included in step 1 that data is ready and sends the capture directly to the SSMF with its metadata. 6) Alternatively, the SSMF can retrieve capture data in a separate message. It can also receive the capture data via the MFAF. 7) The SSMF sends an Ndccf_dataManagement_unsubscribe request to stop data collection.

[0037] NWDAF-based data collection: The NWDAF may alternatively request collection data from the AMF via N2 or the SBI disclosed by the RAN for data management purposes. Retrieving coverage analyses from the NWDAF:

[0038] The SSMF can request capture data analyses from the NWDAF, which can collect capture data directly via the DCCF or the ADRF as a background process. The NWDAF can also register the supported analyses with the DCCF or the NRF as part of the NF profile for the SSMF to find the correct NWDAF instance based on capture data filters. The message flow is in Fig. 7 shown.

[0039] Referring to Fig. Figure 7 shows the collection data analysis retrieval from the NWDAF via the DCCF. 1) The SSMF discovers and selects an NWDAF via the NRF based on the analysis ID, supported services, NWDAF capabilities, and NWDAF coverage area information. 2) The SSMF sends an analysis request / subscription to the NWDAF with the criteria of the capture data or analytics based on the capture data analysis ID, the event ID and the parameters defined in Table 2, the target analytics reporting, the analytics filter information, the reporting endpoint (e.g., AF).

[0040] The term "analysis filter information" in the context of "UE (terminal device) mobility statistics or predictions" refers to the criteria or conditions defined to refine the analysis of terminal device behavior within a telecommunications network. If "visited AOI(s)" (areas of interest) is specified in the analysis filter, the focus is specifically limited to statistics regarding UE mobility within these predefined geographical or network areas. 3) When the DCCF is used for data collection and coordination in the network, the NWDAF selects a DCCF instance based on the DCCF coverage area information. 4) The NWDAF sends a dataManagement subscription request with the required preprocessing and formatting to the DCCF. This message must include the capture analytics ID, capture data filter, [ADRF endpoint], [RAN identifier], and [notification endpoints]. 5) The DCCF notifies the NWDAF and one or more additional notification endpoints included in step 3 via a dataManagement notification message with the requested broadcast data. 6) The NWDAF derives the requested collection service analyses based on the data received from the DCCF. 7) The NWDAF sends Nnwdaf_AnalyticsSubscription _Notify or replies to the SSMF with the requested capture data analysis.

[0041] In some embodiments, the SSMF sends a request to the DCCF with the criteria of the collection data or analytics based on the collection data analytics ID, the event ID, and the parameters defined in Table 2. Based on this trigger, the DCCF may subscribe to the NWDAF to receive collection service analytics.

[0042] In one or more embodiments, a collection service coordination system may enable the collection data analysis ID to be defined in addition to current analysis IDs to identify collection data and associated analyses.

[0043] In one or more embodiments, a capture service coordination system may enable capture event IDs to be defined to capture the capture-related events that could trigger another capture service process.

[0044] In one or more embodiments, a capture service coordination system may enable the capture data parameters, which could be used as a data filter or metadata, to collect, retrieve, tag, and store the capture data.

[0045] In one or more embodiments, a sensing service coordination system may enable the information identified above to be exchanged between RAN, SSMF, DCCF, NWDAF, ADRF.

[0046] In one or more embodiments, a collection service coordination system may enable the collection data analysis ID, event IDs, and collection data metadata to be used to: -Direct storage and tagging of acquisition data between RAN and ADRF. -Instructing the RAN through the SSMF on how to store the capture data and subscribe to capture event changes / updates. -Request by the SSMF to collect detection data through the DCCF or NWDAF. -Retrieval of collection data and analyses from the NWDAF by the SSMF.

[0047] In some embodiments, the one or more electronic devices, the one or more networks, the one or more systems, the one or more chips, or the one or more components or portions or implementations thereof may be Fig. 9-11 or any other figure herein may be adapted to perform one or more processes, techniques, or methods as described herein, or portions thereof. Such a process is Fig. 8 shown.

[0048] For example, the process at 802 may include discovering a network data analysis function (NWDAF) via a network function repository function (NRF).

[0049] The process further includes, at 804, sending an analysis request or subscribing to the selected NWDAF with a criterion based on a capture data analysis ID, an event ID, and event parameters.

[0050] The process further includes, at 806, selecting an instance of a data collection coordination function (DCCF), if DCCF is used for data collection, based on DCCF coverage area information.

[0051] The process further includes, at 808, receiving collection data or data analysis from the NWDAF after the NWDAF has processed the data collected by the DCCF.

[0052] The device may base the discovery and selection of the NWDAF on factors such as a collection service analytics ID, supported services, NWDAF capabilities, or NWDAF coverage area information. The device may also determine the NWDAF based on supported analytics registered with DCCF or NRF. In addition, the device may include an event ID comprising one of a collection target status update, collection target mobility, collection configuration update, collection capability update, or collection service quality update. The device may specify a reporting endpoint for the analytics, which could be an application function (AF). Furthermore, the device may send an Nnwdaf_AnalyticsSubsription_Subscribe message to the NWDAF and may be configured to receive an Nnwdaf_AnalyticsSubscription_Notify comprising the collection data or generated data analytics.The device can send a request to the DCCF with a capture data or analytics criterion based on the capture data analysis ID, the event ID, and the event parameters. The device can also cause the SSMF or another capture data and analytics consumer to register with the NWDAF to receive capture service analytics. Finally, the device can use interfaces between the SSMF and DCCF, the SSMF and NWDAF, and the SSMF and ADRF, which are NS5, NS6, and NS7, respectively.

[0053] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth in the Examples section below. For example, baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc., as described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples set forth below in the Examples section.

[0054] It is understood that the above descriptions are for illustrative purposes and are not intended to be limiting.

[0055] FIGS. 1 and 2 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments.

[0056] Fig. Figure 9 illustrates an exemplary network architecture 900 according to various embodiments. Network 900 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the embodiments are not limited in this respect, and the described embodiments may also apply to other networks that benefit from the principles described herein, e.g., future 3GPP systems or the like.

[0057] The network 900 includes a UE 902, which is a mobile or non-mobile computing device capable of communicating with a RAN 904 via a wireless connection. The UE 902 is communicatively coupled to the RAN 904 through a Uu interface, which may be applicable to both LTE and NR systems.Examples of the UE 902 include, but are not limited to, a smartphone, a tablet computer, a wearable computer, a desktop computer, a laptop computer, an in-vehicle infotainment system, an in-vehicle entertainment system, an instrument cluster, an overhead display (HUD), an on-board diagnostic device, a mobile instrument panel 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 device, a machine-type communication device, machine-to-machine (M2M), device-to-device (D2D), machine-type communication (MTC) device, an Internet of Things (IoT) device, and / or the like.Network 900 may include a plurality of UEs 902 directly coupled to each other via a D2D, ProSe, PC5, and / or sidelink (SL) interface. These UEs 902 may be M2M / D2D / MTC / IoT devices and / or vehicle systems communicating using physical sidelink channels, such as PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc., among others. UE 902 may perform blind decoding attempts of SL channels / links according to the various embodiments herein.

[0058] In some embodiments, the UE 902 may additionally communicate with an AP 906 via an over-the-air (OTA) connection. The AP 906 manages a WLAN connection, which may be used to offload some / all of the network traffic from the RAN 904. The connection between the UE 902 and the AP 906 may be implemented using any IEEE 802.11 protocol. Additionally, the UE 902, the RAN 904, and the AP 906 may utilize cellular-WLAN aggregation / integration (e.g., LWA / LWIP). With cellular-WLAN aggregation, the UE 902 may be configured by the RAN 904 to utilize both cellular and WLAN resources.

[0059] The RAN 904 includes one or more access network nodes (ANs) 908. The ANs 908 terminate the one or more air interfaces for the UE 902 by providing access layer protocols including RRC, PDCP, RLC, MAC, and PHY / L1 protocols. In this way, the AN 908 enables data / voice connectivity between the CN 920 and the UE 902. The ANs 908 may be a macrocell base station or a low-power base station for providing femtocells, picocells, or other similar cells with smaller coverage areas, smaller user capacities, or higher bandwidths compared to macrocells; or a combination thereof. In these implementations, an AN 908 is referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, etc.

[0060] An example implementation is a "CU / DU split" architecture, where the ANs 908 are implemented as a gNB central unit (CU) communicatively coupled to one or more distributed gNB units (DUs), where each DU may be communicatively coupled to one or more radio units (RUs) (also referred to as RRHs, RRUs, or the like) (see, e.g., 3GPP TS 38.401 v16.1.0 (2020-03)). In some implementations, the one or more RUs may be individual RSUs. In some implementations, the CU / DU split may include an ng-eNB CU and one or more ng-eNB DUs instead of or in addition to the gNB CU(s).The ANs 908 deployed as CUs may be implemented in a separate device or as one or more software entities running on server computers, for example, 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), and / or the like (although these terms may refer to different implementation concepts). Any other type of architecture, arrangement, and / or configuration may be used.

[0061] The plurality of ANs may be coupled together via an X2 interface (when the RAN 904 is an LTE-RAN or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 910) or an Xn interface (when the RAN 904 is an NG-RAN 914). Over the X2 / Xn interfaces, which in some embodiments may be divided into control / user plane interfaces, the ANs may communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0062] The ANs of the RAN 904 may each manage one or more cells, cell groups, component carriers, etc., to provide the UE 902 with an air interface for network access. The UE 902 may be simultaneously connected to a plurality of cells provided by the same or different ANs 908 of the RAN 904. For example, the UE 902 and the RAN 904 may utilize carrier aggregation to enable the UE 902 to connect to a plurality of component carriers, each corresponding to a Pcell or Scell. In dual-connectivity scenarios, a first AN 908 may be a master node providing an MCG, and a second AN 908 may be a secondary node providing an SCG. The first / second ANs 908 may be any combination of eNB, gNB, ng-eNB, etc.

[0063] The RAN 904 can provide the air interface over licensed or unlicensed spectrum. For operation in the unlicensed spectrum, nodes can use LAA, eLAA, and / or feLAA mechanisms based on CA technology with Pcells / Scells. Before accessing the unlicensed spectrum, nodes can perform media / carrier sensing, e.g., based on a listen-before-talk (LBT) protocol.

[0064] In V2X scenarios, the UE 902 or the AN 908 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure facility used for V2X communication. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; an eNB may be referred to as an "eNB-type RSU"; a gNB may be referred to as a "gNB-type RSU"; and the like. In one example, an RSU is a computing device coupled to radio frequency circuitry located at the roadside that supports connectivity for passing vehicular UEs.The RSU may also include internal data storage circuitry to store intersection geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may enable very low-latency communications required for high-speed events such as crash avoidance, traffic alerts, and the like. Additionally or alternatively, the RSU may also provide other cellular / Wi-Fi communication services. The RSU components may be housed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller that establishes a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0065] In some embodiments, the RAN 904 may be an E-UTRAN 910 with one or more eNBs 912. The E-UTRAN 910 provides an LTE air interface (Uu) with the following features: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; Turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI detection and beam management; PDSCH / PDCCH-DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial detection, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on sub-6 GHz bands.

[0066] In some embodiments, the RAN 904 may be a next-generation RAN (NG-RAN) 914 with one or more gNBs 916 and / or one or more ng-eNBs 918. The gNB 916 connects to 5G-capable UEs 902 via a 5G NR interface. The gNB 916 is connected to a 5GC 940 via an NG interface, which includes an N2 interface or an N3 interface. The ng-eNB 918 is also connected to the 5GC 940 via an NG interface, but may connect to a UE 902 via the Uu interface. The gNB 916 and the ng-eNB 918 may be interconnected via an Xn interface.

[0067] In some embodiments, the NG interface may be split into two parts, an NG-U interface (NG-U), which carries traffic data between the nodes of the NG-RAN 914 and a UPF 948 (e.g., N3 interface), and an NG control interface (NG-C), which is a signaling interface between the nodes of the NG-RAN 914 and an AMF 944 (e.g., N2 interface).

[0068] The NG-RAN 914 can provide a 5G NR air interface (also referred to as a Uu interface) with the following features: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetitive, simplex, and Reed-Muller codes for control; and LDPC for data. Similar to the LTE air interface, the 5G NR air interface can be based on CSI-RS, PDSCH / PDCCH DMRS. The 5G NR air interface may not use CRS, but instead use PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH, and a reference signal for timing tracking. The 5G NR air interface can operate in FR1 bands, which include sub-6 GHz bands, or FR2 bands, which include bands from 24.25 GHz to 52.6 GHz. The 5G NR air interface can include an SSB, which is a portion of a downlink resource grid containing PSS / SSS / PBCH.

[0069] The 5G NR air interface can use BWPs for various purposes. For example, the BWP can be used to dynamically adapt the SCS. For example, the UE 902 can be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is notified to the UE 902, the SCS of the transmission is also changed. Another application example of the BWP is energy saving. In particular, multiple BWPs with different frequency resources (e.g., PRBs) can be configured for the UE 902 to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with low traffic load while enabling energy savings for the UE 902 and, in some cases, the gNB 916. A BWP with a larger number of PRBs can be used for higher traffic load scenarios.

[0070] The RAN 904 is communicatively coupled to the CN 920, which includes network elements and / or network functions (NFs) to provide various functions to support data and telecommunications services to customers / subscribers (e.g., UE 902). The components of the CN 920 may be implemented in one physical node or in separate physical nodes. In some embodiments, NFV may be used to virtualize any or all of the functions provided by the network elements of the CN 920 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of the CN 920 may be referred to as a network segment, and a logical instantiation of a portion of the CN 920 may be referred to as a network subsegment.

[0071] The CN 920 may be an LTE-CN 922 (also referred to as an Evolved Packet Core (EPC) 922). The EPC 922 may include MME 924, SGW 926, SGSN 928, HSS 930, PGW 932, and PCRF 934, which are coupled together via interfaces (or "reference points"), as shown. The NFs in the EPC 922 are briefly introduced below.

[0072] The MME 924 implements mobility management functions to track the current location of the UE 902 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0073] The SGW 926 terminates an S1 interface to the RAN 910 and forwards data packets between the RAN 910 and the EPC 922. The SGW 926 can serve as a local mobility anchor point for inter-RAN node handovers and can also provide an anchor for inter-3GPP mobility. Other tasks may include regulatory monitoring, billing, and enforcement of certain policies.

[0074] The SGSN 928 tracks the location of the UE 902 and performs security functions and access control. The SGSN 928 also performs cross-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by the MME 924; MME 924 selection for handover, etc. The S3 reference point between the MME 924 and the SGSN 928 enables user and bearer information exchange for cross-3GPP access network mobility in idle / active states.

[0075] The HSS 930 contains a database for network users, including subscription-related information to support the handling of communication sessions by the network entities. The HSS 930 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 930 and the MME 924 can enable transmission of subscription and authenticator data to authenticate / authorize user access to the EPC 920.

[0076] The PGW 932 may terminate an SGi interface to a data network (DN) 936, which may include an application server (app server) / content server 938. The PGW 932 forwards data packets between the EPC 922 and the data network 936. The PGW 932 is communicatively coupled to the SGW 926 through an S5 reference point to enable user-level tunneling and tunnel management. The PGW 932 may also include a node for policy enforcement and accounting data collection (e.g., PCEF). Additionally, the SGi reference point may communicatively couple the PGW 932 to the same or a different data network 936. The PGW 932 may be communicatively coupled to a PCRF 934 through a Gx reference point.

[0077] The PCRF 934 is the policy and charging control element of the EPC 922. The PCRF 934 is communicatively coupled with the app / content server 938 to determine appropriate QoS and charging parameters for service flows. The PCRF 932 also provides associated rules for a PCEF (via the Gx reference point) with the corresponding TFT and QCI.

[0078] The CN 920 can be a 5GC 940, which includes AUSF 942, AMF 944, SMF 946, UPF 948, NSSF 950, NEF 952, NRF 954, PCF 956, UDM 958, and AF 960, which are coupled together via various interfaces, as shown. The NFs in the 5GC 940 are briefly introduced below.

[0079] The AUSF 942 stores data for the authentication of the UE 902 and handles authentication-related functions. The AUSF 942 can enable a common authentication framework for different access types.

[0080] The AMF 944 enables other functions of the 5GC 940 to communicate with the UE 902 and the RAN 904 and to subscribe to notifications about mobility events related to the UE 902. The AMF 944 is also responsible for registration management (e.g., for the registration of the UE 902), connection management, reachability management, mobility management, legal interception of AMF-related events, and access authentication and authorization. The AMF 944 ensures the transport of SM messages between the UE 902 and the SMF 946 and acts as a transparent proxy for forwarding SM messages. The AMF 944 also provides for the transport of SMS messages between the UE 902 and an SMSF. The AMF 944 interacts with the AUSF 942 and the UE 902 to perform various security anchor and context management functions.In addition, the AMF 944 is a termination point of a RAN-CP interface, which includes the N2 reference point between the RAN 904 and the AMF 944. The AMF 944 is also a termination point of the NAS (N1) signaling and performs NAS encryption and integrity protection.

[0081] The AMF 944 also supports NAS signaling with the UE 902 over an N3IWF interface. The N3IWF enables access to untrusted entities. The N3IWF can be a termination point for the N2 interface between the (R)AN 904 and the AMF 944 for the control plane and a termination point for the N3 reference point between the (R)AN 914 and the 948 for the user plane. The AMF 944 handles N2 signaling from the SMF 946 and the AMF 944 for PDU sessions and QoS, encapsulates and de-encapsulates packets for IPSec and N3 tunneling, marks N3 packets on the user plane in the uplink, and enforces QoS according to the N3 packet marking, taking into account the QoS requirements associated with such marking received over N2.The N3IWF can also forward UL and DL control plane NAS signaling between the UE 902 and AMF 944 via an N1 reference point between the UE 902 and AMF 944, and forward uplink and downlink user plane packets between the UE 902 and UPF 948. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 902. The AMF 944 can have a NAMF service-based interface and can be a termination point for an N14 reference point between two AMFs 944 and an N17 reference point between the AMF 944 and a 5G EIR (in . Fig. 9 not shown).

[0082] The SMF 946 is responsible for SM (for example, session establishment, tunnel management between UPF 948 and a 908); UE IP address assignment and management (including optional authorization); selection and control of a UP function; configuring traffic steering at UPF 948 to direct traffic to an appropriate destination; terminating interfaces to policy control functions; controlling part of policy enforcement, for accounting and QoS; lawful interception (for SM events and interface to LI system); terminating SM parts of NAS messages; downlink data notification; initiating specific SM information sent via AMF 944 over N2 to a 908; and determining an SSC mode of a session. SM refers to the management of a PDU session, and a PDU session or “session” refers to a PDU connection service that provides or enables the exchange of PDUs between the UE 902 and the DN 936.

[0083] The UPF 948 acts as an anchor point for intra-RAT and inter-RAT mobility, as an external PDU session point for connecting to the data network 936, and as a branch point for supporting a multi-homed PDU session. The UPF 948 also performs packet routing and forwarding, packet inspection, enforces a subset of user-plane policy rules, legally intercepts packets (UP collection), performs traffic usage reporting, performs user-plane QoS handling (e.g., packet filtering, gating, UL / DL rate enforcement), performs uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport-level packet marking in uplink and downlink, and performs downlink packet buffering and downlink data notification triggering. The UPF 948 may include an uplink classifier to support the routing of traffic flows to a data network.

[0084] The NSSF 950 selects a set of network slice instances to serve the UE 902. The NSSF 950 also determines the allowed NSSAI and the mapping to the subscribed S-NSSAIs, if necessary. The NSSF 950 also determines an AMF set to be used to serve the UE 902 or a list of AMF candidates 944 based on a suitable configuration and possibly by querying the NRF 954. The selection of a set of network slice instances for the UE 902 may be triggered by the AMF 944 to which the UE 902 is registered through interaction with the NSSF 950; this may result in a change of the AMF 944. The NSSF 950 interacts with the AMF 944 via an N22 reference point and can communicate with another NSSF in a visited network via an N31 reference point (not shown).

[0085] The NEF 952 securely exposes services and capabilities provided by 3GPP NFs to third parties, internal discovery / re-discovery, AFs 960, edge computing or fog computing systems (e.g., edge computing nodes, etc.). In such embodiments, the NEF 952 may authenticate, authorize, or throttle the AFs. The NEF 952 may also translate the information exchanged with the AF 960 and the information exchanged with internal network functions. For example, the NEF 952 may translate between an AF service identifier and internal 5GC information. The NEF 952 may also receive information from other NFs based on the disclosed capabilities of other NFs. This information may be stored as structured data in the NEF 952 or in a data storage NF using standardized interfaces.The stored information can then be disclosed by NEF 952 to other NFs and AFs or used for other purposes, such as analytics.

[0086] The NRF 954 supports service discovery functions, receives NF discovery requests from NF instances, and provides information about the discovered NF instances to the requesting NF instances. The NRF 954 also manages information about available NF instances and their supported services. The NRF 954 also supports service discovery functions, where the NRF 954 receives an NF discovery request from an NF instance or an SCP (not shown) and provides information about the discovered NF instances to the NF instance or SCP.

[0087] The PCF 956 provides policies to the control plane functions for enforcement and can also support a unified policy framework for governing network behavior. The PCF 956 can also implement a front-end to access subscription information relevant to policy decisions in a UDR of the UDM 958. In addition to communicating with functions via reference points, as shown, the PCF 956 has an NPCF service-based interface.

[0088] The UDM 958 processes subscription-related information to support the handling of communication sessions by the network entities and stores subscription data of the UE 902. For example, the subscription data may be communicated between the UDM 958 and the AMF 944 via an N8 reference point. The UDM 958 may include two parts, an application frontend and a UDR. The UDR may store subscription data and policy data for the UDM 958 and the PCF 956 and / or structured data for exposure and application data (including PFDs for application discovery, application request information for multiple UEs 902) for the NEF 952. The NEF 952 service-based interface may be used by the UDR 221 to allow the UDM 958, the PCF 956, and the NEF 952 to access a specific set of stored data, as well as read, update (e.g.,The UDM can contain a UDM FE, which is responsible for processing credentials, location management, subscription management, etc. Several different frontends 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 identification handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points, as shown, the UDM 958 can include the UDM service-based interface.

[0089] The AF 960 enables application influence on traffic routing, provides access to the NEF 952, and interacts with the policy framework for policy control. The AF 960 can influence the (re)selection of the UPF 948 and traffic routing. If the AF 960 is considered a trusted entity, the network operator can allow the AF 960 to interact directly with the relevant NFs. Furthermore, the AF 960 can be used for edge computing implementations.

[0090] The 5GC 940 can enable edge computing by selecting services from operators / third-party providers geographically close to a point where the UE 902 is connected to the network. This can reduce latency and network load. In edge computing implementations, the 5GC 940 can select a UPF 948 near the UE 902 and perform traffic routing from the UPF 948 to the DN 936 via the N6 interface. This can be done based on the UE subscription data, the UE location, and information provided by the AF 960, allowing the AF 960 to influence UPF (re)selection and traffic routing.

[0091] The data network (DN) 936 may represent various network operator services, Internet access, or third-party services that may be provided by one or more servers, e.g., application (app) / content server 938. The DN 936 may be, for example, an external public, a private PDN, or an operator-internal packet data network for providing IMS services. In this embodiment, the app server 938 may be coupled to an IMS via an S-CSCF or the I-CSCF. In some implementations, the DN 936 may represent one or more local DNs (LADNs), which are DNs 936 (or DN names (DNNs)) that a UE 902 can access in one or more specific areas. Outside of these specific areas, the UE 902 is unable to access the LADN / DN 936.

[0092] Additionally or alternatively, the DN 936 may be an edge DN 936, which is a (local) data network that supports the architecture for enabling edge applications. In these embodiments, the app server 938 may represent the physical hardware systems / devices that provide app server functionality and / or the application software located in the cloud or at an edge compute node that performs server function(s). In some embodiments, the app / content server 938 provides an edge hosting environment that provides the support required to run the edge application server.

[0093] In some embodiments, the 5GS may use one or more edge compute nodes to provide an interface and offload processing of wireless communication traffic. In these embodiments, the edge compute nodes may be included in or co-located with one or more RANs 910, 914. For example, the edge compute nodes may establish a connection between the RAN 914 and the UPF 948 in the 5GC 940. The edge compute nodes may use one or more NFV instances instantiated on the virtualization infrastructure within the edge compute nodes to process wireless connections to and from the RAN 914 and the UPF 948.

[0094] The interfaces of the 5GC 940 include reference points and service-based interfaces. The reference points include: N1 (between the UE 902 and the AMF 944), N2 (between RAN 914 and AMF 944), N3 (between RAN 914 and UPF 948), N4 (between the SMF 946 and UPF 948), N5 (between PCF 956 and AF 960), N6 (between UPF 948 and DN 936), N7 (between SMF 946 and PCF 956), N8 (between UDM 958 and AMF 944), N9 (between two UPF 948), N10 (between the UDM 958 and the SMF 946), N11 (between the AMF 944 and the SMF 946), N12 (between AUSF 942 and AMF 944), N13 (between AUSF 942 and UDM 958), N14 (between two AMFs 944; not shown), N15 (between PCF 956 and AMF 944 in the case of a non-roaming scenario, or between the PCF 956 in a visited network and the AMF 944 in the case of a roaming scenario), N16 (between two SMFs 946; not shown) and N22 (between AMF 944 and NSSF 950). Other Fig.9 reference point representations not shown may be used. The service-based representation in Fig. Figure 9 represents NFs within the control plane that allow other authorized NFs to access their services. Service-based interfaces (SBIs) include: Namf (SBI issued by AMF 944), Nsmf (SBI issued by SMF 946), Nnef (SBI issued by NEF 952), Npcf (SBI issued by PCF 956), Nudm (SBI issued by UDM 958), Naf (SBI issued by AF 960), Nnrf (SBI issued by NRF 954), Nnssf (SBI issued by NSSF 950), Nausf (SBI issued by AUSF 942). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) used in Fig.9 may also be used. In some embodiments, the NEF 952 may provide an interface to edge compute nodes 936x, which may be used to process wireless connections to the RAN 914. In some implementations, the system 900 may include an SMSF responsible for SMS subscription checking and verification and forwarding SM messages to / from the UE 902 to / from other entities, such as an SMS GMSC / IWMSC / SMS router. The SMS may also interact with the AMF 944 and the UDM 958 for a notification procedure that the UE 902 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying the UDM 958 when the UE 902 is available for SMS).

[0095] The 5GS may also include an SCP (or individual instances of the SCP) providing indirect communication (see, e.g., 3GPP TS 23.501 Section 7.1.1), delegated discovery (see, e.g., 3GPP TS 23.501 Section 7.1.1), message forwarding and routing to target NF / NF services, communication security (e.g., authorization of the NF service consumer to access the NF service producer API (see, e.g., 3GPP TS 33.501), load balancing, monitoring, congestion control, etc.); and discovery and selection functions for UDM(s), AUSF(s), UDR(s), PCF(s) with access to subscription data stored in the UDR based on the UE's SUPI, SUCI, or GPSI (see, e.g., 3GPP TS 23.501 Section 6.3). The The load balancing, monitoring, and congestion control functions provided by the SCP may be implementation-specific. The SCP can be deployed in a distributed manner. More than one SCP may be present in the communication path between different NF services.Although the SCP is not an NF instance, it can also be deployed in a distributed, redundant, and scalable manner.

[0096] Fig. 10 schematically illustrates a wireless network 1000 according to various embodiments. The wireless network 1000 may include a UE 1002 in wireless communication with an AN 1004. The UE 1002 and the AN 1004 may use the Fig. 9 are similar to and essentially interchangeable with the components of the same name described.

[0097] The UE 1002 may be communicatively coupled to the AN 1004 via the connection 1006. The connection 1006 is illustrated as an air interface to enable communicative coupling and may be consistent with cellular communication protocols, such as an LTE protocol or a 5G NR protocol operating at millimeter wave or sub-6 GHz frequencies.

[0098] The UE 1002 may include a host platform 1008 coupled to a modem platform 1010. The host platform 1008 may include application processing circuitry 1012 that may be coupled to the protocol processing circuitry 1014 of the modem platform 1010. The application processing circuitry 1012 may execute various applications for the UE 1002 that provide / receive application data. The application processing circuitry 1012 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.

[0099] Protocol processing circuitry 1014 may implement one or more of the layer operations to enable the transmission or reception of data over link 1006. The layer operations implemented by protocol processing circuitry 1014 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0100] The modem platform 1010 may further include digital baseband circuitry 1016, which may implement one or more layer operations that are "below" layer operations performed by the protocol processing circuitry 1014 in a network protocol stack. These operations may include, for example, PHY operations, including one or more HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / de-mapping, modulation symbol mapping, determination of the received symbol / bit metric, precoding / decoding of multi-antenna ports, which may include one or more space-time, space-frequency, or spatial encodings, generation / detection of reference signals, generation and / or decoding of preamble sequences, generation / detection of synchronization sequences, blind decoding of control channel signals, and other related functions.

[0101] The modem platform 1010 may further include transmit circuitry 1018, receive circuitry 1020, RF circuitry 1022, and an RF front end (RFFE) 1024, which may include or be coupled to one or more antenna panels 1026. Briefly, the transmit circuitry 1018 may include a digital-to-analog converter, a mixer, intermediate frequency (IF) components, etc.; the receive circuitry 1020 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 1022 may include a low-noise amplifier, a power amplifier, power tracking components, etc. The RFFE 1024 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc.The selection and arrangement of the components of the transmit circuitry 1018, the receive circuitry 1020, the RF circuitry 1022, the RFFE 1024, and the antenna panels 1026 (collectively referred to as "transmit / receive components") may be specific to details of a specific implementation, such as, for example, whether the communication is TDM or FDM, occurs in mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be arranged in the same or different chips / modules, etc.

[0102] In some embodiments, the protocol processing circuitry 1014 may include one or more instances of control circuitry (not shown) for providing control functions for the transmit / receive components.

[0103] Reception at the UE 1002 may be established through and via the antenna arrays 1026, the RFFE 1024, the RF circuitry 1022, the receive circuitry 1020, the digital baseband circuitry 1016, and the protocol processing circuitry 1014. In some embodiments, the antenna arrays 1026 may receive a transmission from the AN 1004 by receive beamforming signals received by a plurality of antennas / antenna elements of the one or more antenna arrays 1026.

[0104] A transmission from the UE 1002 may be established by and via the protocol processing circuitry 1014, the digital baseband circuitry 1016, the transmit circuitry 1018, the RF circuitry 1022, the RFFE 1024, and the antenna arrays 1026. In some embodiments, the transmit components of the UE 1004 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna arrays 1026.

[0105] Similar to UE 1002, AN 1004 may include a host platform 1028 coupled to a modem platform 1030. Host platform 1028 may include application processing circuitry 1032 coupled to protocol processing circuitry 1034 of modem platform 1030. The modem platform may also include digital baseband circuitry 1036, transmit circuitry 1038, receive circuitry 1040, RF circuitry 1042, RFFE circuitry 1044, and antenna arrays 1046. The components of AN 1004 may be similar to, and substantially interchangeable with, the like-named components of UE 1002. In addition to the data transmission / reception described above, the components of AN 1008 may perform various logical functions, such as:RNC functions such as radio bearer management, dynamic management of uplink and downlink radio resources, and data packet scheduling.

[0106] Fig. 11 is a block diagram illustrating components of a computing device 1100, according to some embodiments, 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 methodologies discussed herein. In particular, Fig.11 is a diagrammatic representation of hardware resources 1101, including one or more processors (or processor cores) 1110, one or more memory / storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled via a bus 1140 or other interface circuitry. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1102 may be executed to provide an execution environment for one or more network slices / subslices utilizing the hardware resources 1101.

[0107] The processors 1110 include, for example, the processor 1112 and the processor 1114. The processors 1110 include circuitry such as, among others, one or more processor cores and one or more of caches, low-drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C, or a general-purpose programmable serial interface circuit, real-time clock (RTC), timer counters including interval and watchdog timers, general-purpose I / O, memory card controllers such as Secure Digital / Multimedia Card (SD / MMC) or the like, interfaces, Mobile Industry Processor Interface (MIPI) interfaces, and Joint Test Access Group (JTAG) test access ports.Processors 1110 may, for example, be a central processing unit (CPU), reduced instruction set computing (RISC) processors, Acorn RISC Machine (ARM) processors, complex instruction set computing (CISC) processors, graphics processing units (GPUs), one or more digital signal processors (DSPs) such as a baseband processor, application-specific integrated circuits (ASICs), a field-programmable gate array (FPGA), a radio frequency integrated circuit (RFIC), one or more microprocessors or controllers, another processor (including those mentioned herein), or a suitable combination thereof. In some implementations, processor circuitry 1110 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices (e.g., FPGAs, complex programmable logic devices (CPLDs), etc.), or the like.

[0108] The memory / storage devices 1120 may include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 1120 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), synchronous DRAM (SDRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, phase-change random access memory (PRAM), resistive memory such as magnetoresistive random access memory (MRAM), etc., and may include three-dimensional (3D) cross-point memory (XPOINT) from Intel® and Micron®.The memory / storage devices 1120 may also include persistent storage devices, which may be temporary and / or permanent storage of any type, including, but not limited to, non-volatile memory, optical, magnetic, and / or solid-state mass storage, and so on.

[0109] The communication resources 1130 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1104 or one or more databases 1106 or other network elements over a network 1108. For example, the communication resources 1130 may include wired communication components (e.g., for coupling via USB, Ethernet, Ethernet over GRE Tunnel, Ethernet over Multiprotocol Label Switching (MPLS), Ethernet over USB, Controller Area Network (CAN), Local Interconnect Network (LIN), DeviceNet, ControlNet, Data Highway+, PROFIBUS, or PROFINET, among many others), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, WiFi® components, and other communication components.Network connectivity may be provided to / from computing device 1100 via communication resources 1130 using a physical connection, which may be electrical (e.g., a copper interconnect) or optical. The physical connection also includes suitable input connectors (e.g., ports, receptacles, sockets, etc.) and output connectors (e.g., plugs, pins, etc.). Communication resources 1130 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned network interface protocols.

[0110] Instructions 1150 may comprise software, a program, an application, an applet, an app, or other executable code to cause at least one of the processors 1110 to perform any one or more of the methodologies discussed herein. Instructions 1150 may reside, in whole or in part, within at least one of the processors 1110 (e.g., within the processor's cache), the memory / storage devices 1120, or any suitable combination thereof. Furthermore, any portion of instructions 1150 may be transferred to the hardware resources 1101 from any combination of the peripheral devices 1104 or the databases 1106. Accordingly, the memory of the processors 1110, the memory / storage devices 1120, the peripheral devices 1104, and the databases 1106 are examples of computer-readable and machine-readable media.

[0111] Fig.12 illustrates a network 1200 according to various embodiments. The network 1200 may operate in a manner that complies with the 3GPP technical specifications for 6G systems. In some embodiments, the network 1200 may operate concurrently with the network 900. For example, in some embodiments, the network 1200 may share one or more frequency or bandwidth resources with the network 900. As a specific example, a UE (e.g., UE 1202) may be configured to operate in both the network 1200 and the network 900. Such a configuration may be based on a UE including circuitry configured to communicate with frequency and bandwidth resources of both the networks 900 and 1200. In general, multiple elements of the network 1200 may share one or more characteristics with elements of the network 900.For brevity and clarity, such elements may not be repeated in the description of network 1200.

[0112] The network 1200 may include a UE 1202, which may include any mobile or non-mobile computing device capable of communicating with a RAN 1208 over a wireless connection. The UE 1202 may be similar to the UE 902, for example. The UE 1202 may be, among other things, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, an overhead display (HUD), an on-board diagnostic device, a mobile dashboard 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 device, an engine-type communication device, an M2M or D2D device, an IoT device, etc.

[0113] Although in Fig. 12, in some embodiments, the network 1200 may include a plurality of UEs 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. Likewise, although Fig. 12, the UE 1202 may be communicatively coupled to an AP, such as the AP 906, as described with reference to Fig. 9. Although this is Fig. 12, the RAN 1208 may additionally include, in some embodiments, one or more ANs, such as the AN 908, as described with reference to Fig. 9. The RAN 1208 and / or the AN of the RAN 1208 may be referred to as a base station (BS), a RAN node, or using another term or name.

[0114] The UE 1202 and the RAN 1208 may be configured to communicate over an air interface, which 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 a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term "joint communication and sensing" may refer to a system that enables wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as "millimeter Wave" or "mmWave" frequency ranges.

[0115] The RAN 1208 may enable communication between the UE 1202 and a 6G core network (CN) 1210. In particular, the RAN 1208 may enable the transmission and reception of data between the UE 1202 and the 6G CN 1210. The 6G CN 1210 may include various functions, such as NSSF 950, NEF 952, NRF 954, PCF 956, UDM 958, AF 960, SMF 946, and AUSF 942. The 6G CN 1210 may additionally include UPF 948 and DN 936, as described in Fig. 12 shown.

[0116] In addition, the RAN 1208 may include various additional functions that are in addition to or alternative to functions of a legacy mobile network, such as a 4G or 5G network. Two such functions may include a compute control function (Comp-CF) 1224 and a compute service function (Comp-SF) 1236. The Comp-CF 1224 and the Comp-SF 1236 may be parts or functions of the compute service plane. The Comp-CF 1224 may be a control plane function that provides functionalities such as managing the Comp-SF 1236, generating and managing compute task contexts (e.g., create, read, modify, delete), interacting with the underlying compute infrastructure for compute resource management, etc. The Comp-SF 1236 may be a user plane function that serves as the gateway to interface compute service users (such as the UE 1202) and compute nodes behind a Comp-SF instance.Some functionalities of the Comp-SF 1236 may include: parsing compute service data received from users to compute tasks executable by compute nodes; maintaining a service mesh ingress gateway or service API gateway; enforcing service and billing policies; performance monitoring and telemetry collection, etc. In some embodiments, an instance of the Comp-SF 1236 may serve as the user-plane gateway for a cluster of compute nodes. An instance of the Comp-CF 1224 may control one or more instances of the Comp-SF 1236.

[0117] Two other such functions may include a communication control function (Comm-CF) 1228 and a communication service function (Comm-SF) 1238, which may be parts of the communication service plane. The Comm-CF 1228 may be the control plane function for managing the Comm-SF 1238, creating / configuring / releasing communication sessions, and managing the communication session context. The Comm-SF 1238 may be a user plane function for data transport. The Comm-CF 1228 and the Comm-SF 1238 may be considered upgrades to the SMF 946 and the UPF 948, respectively, with respect to a 5G system in Fig. 9. The upgrades provided by the Comm-CF 1228 and Comm-SF 1238 can enable service-aware transport. For legacy data transport (e.g., 4G or 5G), the SMF 946 and the UPF 948 can continue to be used.

[0118] Two other such functions may include a data control function (Data-CF) 1222 and a data service function (Data-SF) 1232, which may be parts of the data service plane. The Data-CF 1222 may be a control plane function and provides functionalities such as managing the Data-SF 1232, creating / configuring / releasing data services, managing data service contexts, etc. The Data-SF 1232 may be a user plane function and serve as the gateway between data service users (such as the UE 1202 and the various functions of the 6G-CN 1210) and data service endpoints behind the gateway. Specific functionalities may include parsing data service user data and forwarding it to appropriate data service endpoints, generating charging data, and reporting data service status.

[0119] Another such function may be the Service Orchestration and Chaining Function (SOCF) 1220, which may discover, orchestrate, and chain communication / compute / data services provided by functions in the network. Upon receiving service requests from users, the SOCF 1220 may interact with one or more of the Comp CF 1224, the Comm CF 1228, and the Data CF 1222 to identify instances of the Comp SF 1236, the Comm SF 1238, and the Data SF 1232, configure service resources, and create the service chain, which may include multiple instances of the Comp SF 1236, the Comm SF 1238, and the Data SF 1232 and their associated compute endpoints. Workload processing and data movement may then be performed within the created service chain. The SOCF 1220 can also be responsible for maintaining, updating and releasing a created service chain.

[0120] Another such function may be the Service Registration Function (SRF) 1214, which may act as a registry for system services provided in the user plane, such as services provided by service endpoints behind gateways of the Comp-SF 1236 and the Data-SF 1232 and services provided by the UE 1202. The SRF 1214 may be considered a counterpart of the NRF 954, which may act as the registry for network functions.

[0121] Other such functions may include an evolved service communication proxy (eSCP) and a service infrastructure control function (SICF) 1226, which may provide a service communication infrastructure for control plane services and user plane services. The eSCP may be related to the 5G service communication proxy (SCP), adding user plane service communication proxy capabilities. The eSCP is therefore expressed in two parts: eCSP-C 1212 and eSCP-U 1234 for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 1226 may control and configure eCSP instances regarding service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

[0122] Another such function is the AMF 1244. The AMF 1244 may be similar to the 944, but with additional functionality. In particular, the AMF 1244 may include potential functional repartitioning, such as relocating message forwarding functionality from the AMF 1244 to the RAN 1208.

[0123] Another such function is the Service Orchestration Expose Function (SOEF) 1218. The SOEF may be configured to expose service orchestration and chaining services to external users, such as applications.

[0124] The UE 1202 may include an additional function referred to as the Compute Client Service Function (Comp-CSF) 1204. The Comp-CSF 1204 may include both control plane functionalities and user plane functionalities and may interact with corresponding network-side functions, such as the SOCF 1220, the Comp-CF 1224, the Comp-SF 1236, the Data-CF 1222, and / or the Data-SF 1232 for service discovery, request / response, compute task workload exchange, etc. The Comp-CSF 1204 may also operate with network-side functions to decide whether a compute task should be executed on the UE 1202, the RAN 1208, and / or an element of the 6G CN 1210.

[0125] The UE 1202 and / or the Comp-CSF 1204 may include a service mesh proxy 1206. The service mesh proxy 1206 may act as a proxy for service-to-service communication in the user plane. Capabilities of the service mesh proxy 1206 may include addressing, security, load balancing, etc.

[0126] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth in the Examples section below. For example, baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc., as described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples set forth below in the Examples section.

[0127] Further examples of the presently described embodiments include the following non-limiting implementations. Each of the following non-limiting examples may stand alone or may be combined in any permutation or combination with one or more of the other examples provided below or throughout this disclosure.

[0128] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth in the examples section below. For example, baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc., as described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples set forth below.

[0129] The following examples relate to further embodiments.

[0130] Example 1 may include a device comprising: discovering a network data analytics function (NWDAF) via a network function repository function (NRF); sending an analytics request or subscribing to the selected NWDAF with a criterion based on a collection data analytics ID, an event ID, and event parameters; selecting an instance of a data collection coordination function (DCCF), if DCCF can be used for data collection, based on DCCF coverage area information; and receiving collection data or data analytics from the NWDAF after the NWDAF processes the data collected by the DCCF.

[0131] Example 2 may include implementing Example 1 and / or any other example herein, wherein the discovery and selection of the NWDAF may be based on a collection service analytics ID, supported services, NWDAF capabilities, or NWDAF coverage area information.

[0132] Example 3 may include the setup of Example 1 and / or any other example herein, wherein the processing circuitry may be further configured to determine the NWDAF based on supported analytics registered with the DCCF or NRF.

[0133] Example 4 may include the setup of Example 1 and / or any other example herein, wherein the event ID comprises one of collection target status update, collection target mobility, collection configuration update, collection capability update, or collection service quality update.

[0134] Example 5 may include the apparatus of Example 1 and / or any other example herein, wherein the processing circuitry may be further configured to specify a reporting endpoint for the analytics, such as an application function (AF).

[0135] Example 6 may include the apparatus of Example 1 and / or any other example herein, wherein the processing circuitry may be further configured to send an Nnwdaf_AnalyticsSubsription_Subscribe message to the NWDAF.

[0136] Example 7 may include the apparatus of Example 1 and / or any other example herein, wherein the processing circuitry may be further configured to receive Nnwdaf_AnalyticsSubscription_Notify comprising the capture data or generated data analytics.

[0137] Example 8 may include the apparatus of Example 1 and / or any other example herein, wherein the processing circuitry may be further configured to send a request to the DCCF with a criterion of the capture data or analytics based on the capture data analytics ID, the event ID, and the event parameters.

[0138] Example 9 may include the setup of Example 7 and / or any other example herein, wherein the processing circuitry may be further configured to cause the DCCF to register with the NWDAF to receive collection service analytics.

[0139] Example 10 may include the setup of Example 1 and / or any other example herein, wherein the interfaces between SSMF and DCCF, SSMF and NWDAF, SSMF and ADRF are NS5, NS6, and NS7, respectively.

[0140] Example 11 may include a computer-readable medium storing computer-executable instructions that, when executed by one or more processors, result in operations being performed, comprising: discovering a network data analysis capability (NWDAF) via a network function repository capability (NRF); sending an analysis request or subscribing to the selected NWDAF with a criterion based on a collection data analysis ID, an event ID, and event parameters; selecting an instance of a data collection coordination function (DCCF), if DCCF can be used for data collection, based on DCCF coverage area information; and receiving collection data or data analysis from the NWDAF after the NWDAF processes the data collected by the DCCF.

[0141] Example 12 may include the computer-readable medium of Example 11 and / or any other example herein, wherein the discovery and selection of the NWDAF may be based on a collection service analysis ID, supported services, NWDAF capabilities, or NWDAF coverage area information.

[0142] Example 13 may include implementing Example 11 and / or any other example herein, wherein the operations further comprise determining the NWDAF based on supported analytics registered with the DCCF or NRF.

[0143] Example 14 may include the computer-readable medium of Example 11 and / or any other example herein, wherein the event ID comprises one of collection target status update, collection target mobility, collection configuration update, collection capability update, or collection service quality update.

[0144] Example 15 may include the computer-readable medium of Example 11 and / or any other example herein, wherein operations further comprise specifying a reporting endpoint for the analytics, such as an application function (AF).

[0145] Example 16 may include the computer-readable medium of Example 11 and / or any other example herein, wherein operations further comprise sending an Nnwdaf_AnalyticsSubsription_Subscribe message to the NWDAF.

[0146] Example 17 may include the computer-readable medium of Example 11 and / or any other example herein, wherein the operations further comprise receiving Nnwdaf_AnalyticsSubscription_Notify comprising the collection data or generated data analytics.

[0147] Example 18 may include the computer-readable medium of Example 11 and / or any other example herein, wherein the operations further comprise sending a request to the DCCF with a criterion of the capture data or analytics based on the capture data analytics ID, the event ID, and the event parameters.

[0148] Example 19 may include the computer-readable medium of Example 17 and / or any other example herein, wherein the operations further comprise causing the DCCF to register with the NWDAF to receive collection service analytics.

[0149] Example 20 may include the computer-readable medium of Example 11 and / or any other example herein, wherein the interfaces between SSMF and DCCF, SSMF and NWDAF, SSMF and ADRF are NS5, NS6, and NS7, respectively.

[0150] Example 21 may include a method comprising: discovering a network data analysis capability (NWDAF) via a network function repository capability (NRF); sending an analysis request or subscribing to the selected NWDAF with a criterion based on a collection data analysis ID, an event ID, and event parameters; selecting an instance of a data collection coordination function (DCCF), if DCCF can be used for data collection, based on DCCF coverage area information; and receiving collection data or data analysis from the NWDAF after the NWDAF processes the data collected by the DCCF.

[0151] Example 22 may include the method of Example 21 and / or any other example herein, wherein the discovery and selection of the NWDAF may be based on a collection service analysis ID, supported services, NWDAF capabilities, or NWDAF coverage area information.

[0152] Example 23 may include the method of Example 21 and / or any other example herein, further comprising determining the NWDAF based on supported analyses registered with DCCF or NRF.

[0153] Example 24 may include the method of Example 21 and / or any other example herein, wherein the event ID comprises one of collection target status update, collection target mobility, collection configuration update, collection capability update, or collection service quality update.

[0154] Example 25 may include the method of Example 21 and / or any other example herein, further comprising specifying a reporting endpoint for the analytics, such as an application function (AF).

[0155] Example 26 may include the method of Example 21 and / or any other example herein, further comprising sending an Nnwdaf_AnalyticsSubsription_Subscribe message to the NWDAF.

[0156] Example 27 may include the method of Example 21 and / or any other example herein, further comprising receiving Nnwdaf_AnalyticsSubscription_Notify comprising the collection data or generated data analytics.

[0157] Example 28 may include the method of Example 21 and / or any other example herein, further comprising sending a request to the DCCF with a criterion of the capture data or analytics based on the capture data analytics ID, the event ID, and the event parameters.

[0158] Example 29 may include the method of Example 27 and / or any other example herein, further comprising causing the DCCF to register with the NWDAF to receive collection service analytics.

[0159] Example 30 may include the method of Example 21 and / or any other example herein, wherein the interfaces between SSMF and DCCF, SSMF and NWDAF, SSMF and ADRF are NS5, NS6, and NS7, respectively.

[0160] Example 31 may include an apparatus comprising means for: discovering a network data analysis capability (NWDAF) via a network function repository capability (NRF); sending an analysis request or subscribing to the selected NWDAF with a criterion based on a collection data analysis ID, an event ID, and event parameters; selecting an instance of a data collection coordination function (DCCF), if DCCF can be used for data collection, based on DCCF coverage area information; and receiving collection data or data analysis from the NWDAF after the NWDAF processes the data collected by the DCCF.

[0161] Example 32 may include implementing Example 31 and / or any other example herein, wherein the discovery and selection of the NWDAF may be based on a collection service analysis ID, supported services, NWDAF capabilities, or NWDAF coverage area information.

[0162] Example 33 may include implementing Example 31 and / or any other example herein, further comprising determining the NWDAF based on supported analyses registered with DCCF or NRF.

[0163] Example 34 may include the setup of Example 31 and / or any other example herein, wherein the event ID comprises one of collection target status update, collection target mobility, collection configuration update, collection capability update, or collection service quality update.

[0164] Example 35 may include implementing Example 31 and / or any other example herein, further comprising specifying a reporting endpoint for the analytics, such as an application function (AF).

[0165] Example 36 may include implementing Example 31 and / or any other example herein, further comprising sending an Nnwdaf_AnalyticsSubscription_Subscribe message to the NWDAF.

[0166] Example 37 may include implementing Example 31 and / or any other example herein, further comprising receiving Nnwdaf_AnalyticsSubscription_Notify comprising the collection data or generated data analytics.

[0167] Example 38 may include implementing Example 31 and / or any other example herein, further comprising sending a request to the DCCF with a criterion of the capture data or analytics based on the capture data analytics ID, the event ID, and the event parameters.

[0168] Example 39 may include implementing Example 37 and / or any other example herein, further comprising causing the DCCF to register with the NWDAF to receive collection service analytics.

[0169] Example 40 may include the setup of Example 31 and / or any other example herein, wherein the interfaces between SSMF and DCCF, SSMF and NWDAF, SSMF and ADRF are NS5, NS6, and NS7, respectively.

[0170] Example 41 may include an apparatus comprising means for performing any of the methods of Examples 1-40.

[0171] Example 42 may include a network node comprising a communications interface and processing circuitry coupled thereto and configured to perform the methods of Examples 1-40.

[0172] Example 43 may include an apparatus including means for performing one or more elements of a method or process associated with any of Examples 1-40, or any other method or process described herein.

[0173] Example 44 may include one or more non-transitory computer-readable media comprising instructions for causing an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in any of Examples 1-40 or a method associated therewith, or any other method or process described herein.

[0174] Example 45 may include a device including logic, modules, or circuitry to perform one or more elements of a method or associated method described in any of Examples 1-40, or any other method or process described herein.

[0175] Example 46 may include a method, technique, or process as described in or associated with any of Examples 1-40, or portions or sections thereof.

[0176] Example 47 may include an apparatus comprising: one or more processors; and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process described in or associated with any of Examples 1-40 or portions thereof.

[0177] Example 48 may include a signal as described in or associated with any of Examples 1-40, or portions or parts thereof.

[0178] Example 49 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or associated with any of Examples 1-40, or portions or parts thereof, or as otherwise described in the present disclosure.

[0179] Example 50 may include a signal encoded with data as described in or associated with any of Examples 1-40, or portions or sections thereof, or as otherwise described in the present disclosure.

[0180] Example 51 may include a signal encoded with or associated with a datagram, a packet, a frame, a segment, a protocol data unit (PDU), or a message as described in any of Examples 1-40, or sections or portions thereof, or as otherwise described in the present disclosure.

[0181] Example 52 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of Examples 1-40, or portions thereof.

[0182] Example 53 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to perform the method, techniques, or process as described in or related to any of Examples 1-40, or portions thereof.

[0183] Example 54 may include a signal in a wireless network as shown and described herein.

[0184] Example 55 may include a method for communicating in a wireless network as shown and described herein.

[0185] Example 56 may include a system for providing wireless communication as shown and described herein.

[0186] Example 57 may include means for providing wireless communication as shown and described herein.

[0187] An example implementation is an edge computing system that includes respective edge processing devices and nodes for invoking or performing the operations of the above examples or other subject matter described herein. Another example implementation is a client endpoint node operable to invoke or perform the operations of the above examples or other subject matter described herein. Another example implementation is an aggregation node, network hub node, gateway node, or core computing node, within or coupled to an edge computing system, operable to invoke or perform the operations of the above examples or other subject matter described herein.Another example implementation is an access point, a base station, a wayside unit, a roadside unit, or an on-premises unit, within or coupled to an edge computing system, operable to invoke or perform the operations of the above examples or other items described herein. Another example implementation is an edge provisioning node, a service orchestration node, an application orchestration node, or a multi-tenant management node, within or coupled to an edge computing system, operable to invoke or perform the operations of the above examples or other items described herein.Another example implementation is an edge node operating an edge provisioning service, an application or service orchestration service, a virtual machine provisioning service, a container provisioning service, a function provisioning service, and compute management, within or coupled with an edge computing system, operable to invoke or perform the operations of the above examples or other subject matter described herein. Another example implementation is an edge computing system operable as an edge mesh, as an edge mesh with sidecar loading, or with mesh-to-mesh communications, operable to invoke or perform the operations of the above examples or other subject matter described herein.Another example implementation is an edge computing system that includes aspects of network functions, acceleration functions, acceleration hardware, storage hardware, or compute hardware resources, operable to invoke or perform the use cases discussed herein using the examples above or other subject matter described herein. Another example implementation is an edge computing system configured to support client mobility, vehicle-to-vehicle (V2V), vehicle-to-environment (V2X), or vehicle-to-infrastructure (V2I) scenarios, optionally operating according to ETSI MEC specifications, operable to invoke or perform the use cases discussed herein using the examples above or other subject matter described herein.Another example implementation is an edge computing system configured for mobile wireless communications, including configurations according to 3GPP 4G / LTE or 5G network capabilities, operable to invoke or perform the use cases discussed herein using the examples above or other subject matter described herein. Another example implementation is a computing system configured for network communications, including configurations according to O-RAN capabilities, operable to invoke or perform the use cases discussed herein using the examples above or other subject matter described herein.

[0188] Any of the examples described above may be combined with any other example (or combination of examples) unless explicitly stated otherwise. The above description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be obtained from practice of various embodiments. TERMINOLOGY

[0189] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It is further understood that the terms "comprises" and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0190] For the purposes of this disclosure, the term "A and / or B" means (A), (B), or (A and B). For the purposes of this disclosure, the term "A, B, and / or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C). Throughout the description, the terms "in one embodiment" or "in some embodiments" may be used, each of which may refer to one or more of the same or different embodiments. Furthermore, the terms "comprising," "including," "having," and the like, as used with respect to embodiments of this disclosure, are synonymous.

[0191] The terms "coupled" and "communicatively coupled," along with derivatives thereof, are used herein. The term "coupled" can mean that two or more elements are in direct physical or electrical contact with each other, can mean that two or more elements indirectly touch each other but still cooperate or interact with each other, and / or can mean that one or more other elements are coupled or connected between the elements said to be coupled. The term "directly coupled" can mean that two or more elements are in direct contact with each other. The term "communicatively coupled" can mean that two or more elements can be in contact with each other by a communication means, including by a wire or other interconnection, by a wireless communication channel or link, and / or the like.

[0192] The term "circuitry" as used herein refers to hardware components, such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or as a group) and / or a memory (shared, dedicated, or as a group), an application-specific integrated circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide, are part of, or include the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.The term "circuitry" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to execute the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0193] The term "processor circuitry," as used herein, refers to, is part of, or includes circuitry capable of sequentially and automatically performing a sequence of arithmetic or logical operations or recording, storing, and / or transmitting digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes. Processing circuitry may include a plurality of hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators.The terms “application circuitry” and / or “baseband circuitry” may be considered synonymous and may be referred to as “processor circuitry”.

[0194] The term "memory" and / or "memory circuitry" as used herein refers to one or more hardware devices for storing data, including RAM, MRAM, PRAM, DRAM and / or SDRAM, core memory, ROM, magnetic disk storage media, optical storage media, flash memory devices, or other machine-readable media for storing data. The term "computer-readable medium" may include, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions or data.

[0195] The term "interface circuitry," as used herein, refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, for example, buses, I / O interfaces, peripheral component interfaces, network interface cards, and / or the like.

[0196] The term "terminal" or "UE," as used herein, refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term "terminal" or "UE" can be considered synonymous with, and may be referred to as, a client, mobile device, mobile apparatus, 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. Further, the term "terminal" or "UE" may include any type of wireless / wired device or any computing device, including a wireless communication interface.

[0197] The term "network element," as used herein, refers to a physical or virtualized device and / or physical or virtualized infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as a networked computer, networking hardware, network device, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and / or the like.

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

[0199] The term "device," "computing device," or the like, as used herein, refers to a computing device or computer system having program code (e.g., software or firmware) specifically configured to provide a specific computing resource. A "virtual device" is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computing device or is otherwise dedicated to providing a specific computing resource. The term "element" refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary, where an element can be any type of entity, including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof.The term "device" refers to a physical entity embedded within or attached to another physical entity in its vicinity, with capabilities to transfer digital information to or from that physical entity. The term "entity" refers to an individual component of an architecture or device, or information transferred as a payload. The term "controller" refers to an element or entity that has the capability to influence a physical entity, such as by changing its state or causing the physical entity to move.

[0200] The term "cloud computing" or "cloud" refers to a paradigm for enabling network access to a scalable and elastic pool of shareable computing resources with self-service provisioning and management on demand and without active user management. Cloud computing provides cloud computing services (or cloud services), which are one or more capabilities offered via cloud computing that are invoked using a defined interface (e.g., an API or the like). The term "computing resource" or simply "resource" refers to any physical or virtual component, or use of such components, with limited availability within a computer system or network.Examples of computing resources include use / access to servers, processor(s), storage devices, memory devices, memory areas, networks, electrical power, input / output (peripheral) devices, mechanical devices, network connections (e.g., channels / links, ports, network sockets, etc.), operating systems, virtual machines (VMs), software / applications, computer files, and / or the like. A "hardware resource" may refer to computing, storage, and / or network resources provided by one or more physical hardware elements. A "virtualized resource" may refer to computing, storage, and / or network resources provided to an application, device, system, etc., through a virtualization infrastructure.The term "network resource" or "communications resource" can refer to resources accessible by computing devices / systems over a communications network. The term "system resources" can refer to any type of shared entity to provide services and can include compute and / or network resources. System resources can be thought of as a set of coherent functions, network data objects, or services accessible by a server, where such system resources are located on a single host or multiple hosts and are uniquely identifiable. As used herein, the term "cloud service provider" (or CSP) refers to an organization that typically operates large-scale "cloud" resources consisting of centralized, regional, and edge data centers (such as those used in the public cloud context).In other examples, a CSP may also be referred to as a cloud service operator (CSO). References to "cloud computing" generally refer to computing resources and services offered by a CSP or CSO at remote locations with at least somewhat increased latency, distance, or constraints relative to edge computing.

[0201] As used herein, the term "data center" refers to a purpose-designed structure designed to house multiple high-performance computing and data storage nodes, allowing a large amount of computing, data storage, and networking resources to be co-located in a single location. These often include specialized rack and enclosure systems, appropriate heating, cooling, ventilation, security, fire suppression, and power systems. The term may also refer to a computing and data storage node in some contexts. A data center can vary in scale from a centralized or cloud data center (e.g., the largest), a regional data center, and an edge data center (e.g., the smallest).

[0202] As used herein, the term "edge computing" refers to the implementation, coordination, and use of computing and resources at locations closer to the "edge" or a collection of "edges" of a network. Deploying computing resources at the edge of the network can reduce application and network latency, reduce network backhaul traffic and associated energy consumption, enhance service capabilities, improve compliance with security or privacy requirements (particularly compared to traditional cloud computing), and improve total cost of ownership.As used herein, the term "edge compute node" refers to a real, logical, or virtualized implementation of a compute-capable element in the form of a device, gateway, bridge, system, or subsystem, component, whether operating in a server, client, endpoint, or peer mode, and whether located at an "edge" of a network or at a connected location further within the network. References to a "node" used herein are generally interchangeable with "device," "component," and "subsystem"; however, references to an "edge compute system" or "edge compute network" generally refer to a distributed architecture, organization, or collection of multiple nodes and devices organized to achieve or offer some aspect of services or resources in an edge computing environment.

[0203] Additionally or alternatively, the term "edge computing" refers to a concept, as described in [6], that enables operator and third-party services to be hosted close to the UE's access point to achieve efficient service delivery through lower end-to-end latency and load on the transport network. As used here, the term "edge computing service provider" refers to a mobile network operator or a third-party provider that offers edge computing services. As used here, the term "edge data network" refers to a local data network (DN) that supports the architecture to enable edge applications. As used here, the term "edge hosting environment" refers to an environment that provides the support required to run the edge application server.As used here, the term “application server” refers to application software in the cloud that performs the server function.

[0204] The term "Internet of Things" or "IoT" refers to a system of interconnected computing devices, mechanical and digital machines capable of transmitting data with little or no human interaction. It may involve technologies such as real-time analytics, machine learning and / or AI, embedded systems, wireless sensor networks, control systems, automation (e.g., smart home, smart building, and / or smart city technologies), and the like. IoT devices are typically low-power devices without strong computing or storage capabilities. "Edge IoT devices" can be any type of IoT device deployed at the edge of a network.

[0205] As used herein, the term "cluster" refers to a set or grouping of entities as part of an edge computing system (or edge computing systems) in the form of physical entities (e.g., different computing systems, networks, or network groups), logical entities (e.g., applications, functions, security constructs, containers), and the like. In some places, a "cluster" is also referred to as a "group" or a "domain." Cluster membership may be modified or influenced based on conditions or functions, including dynamic or property-based membership, network or system management scenarios, or various example techniques discussed below that can add, modify, or remove an entity in a cluster.Clusters may also include or be associated with multiple layers, levels, or properties, including variations in security characteristics and outcomes based on such layers, levels, or properties.

[0206] The term "application" can refer to a complete and deployable package, an environment, for achieving a certain function in an operational environment. The term "AI / ML application" or the like can be an application that includes some AI / ML models and application-level descriptions. The term "machine learning" or "ML" refers to the use of computer systems that implement algorithms and / or statistical models to perform one or more specific tasks without using explicit instructions, but instead relying on patterns and inference. ML algorithms create or estimate one or more mathematical models (referred to as "ML models" or the like) based on sample data (referred to as "training data," "model training information," or the like) to make predictions or decisions without being explicitly programmed to perform such tasks.In general, an ML algorithm is a computer program that learns from experience regarding some task and some performance metric, and an ML model can be any object or data structure generated after an ML algorithm is trained on one or more training datasets. After training, an ML model can be used to make predictions on new datasets. Although the term "ML algorithm" refers to different concepts than the term "ML model," as discussed herein, these terms can be used interchangeably for the purposes of the present disclosure.

[0207] The term "machine learning model," "ML model," or the like can also refer to ML methods and concepts used by an ML-assisted solution. An "ML-assisted solution" is a solution that addresses a specific use case using ML algorithms on the fly. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.), unsupervised learning (e.g., k-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, and the like. Depending on the implementation, a specific ML model might have many submodels, as components and the ML model can train all submodels with each other.Separately trained ML models can also be chained together in an ML pipeline during inference. An "ML pipeline" is a set of functionalities, functions, or feature entities specific to an ML-powered solution; an ML pipeline can include one or more data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. The "actor" is an entity that delivers an ML-powered solution using the results of ML model inference. The term "ML training host" refers to an entity, such as a network function, that hosts the model's training. The term "ML inference host" refers to an entity, such as a network function, that hosts the model during inference mode (which includes both model execution and, if applicable, online learning).The ML host informs the actor about the output of the ML algorithm, and the actor makes a decision about an action (an "action" is performed by an actor as a result of the output of an ML-assisted solution). The term "model inference information" refers to information used as input to the ML model to determine inferences. The data used to train an ML model and the data used to determine inferences may overlap, however, "training data" and "inference data" refer to different concepts.

[0208] The terms "instantiating," "instantiation," and the like, as used herein, refer to the creation of an instance. An "instance" also refers to a concrete occurrence of an object, which may occur, for example, during the execution of program code. The term "information item" refers to a structural element that contains one or more fields. The term "field" refers to individual contents of an information item or a data element that contains content. As used herein, a "database object," a "data structure," or the like may refer to any representation of information that takes the form of an object, attribute-value pair (AVP), key-value pair (CVP), tuple, etc.and may include variables, data structures, functions, methods, classes, database records, database fields, database entities, associations between data and / or database entities (also referred to as a “relationship”), blocks and links between blocks in blockchain implementations, and / or the like.

[0209] An "information object," as used herein, refers to a collection of structured data and / or any representation of information and may include, for example, electronic documents (or "documents"), database objects, data structures, files, audio data, video data, raw data, archive files, application packages, and / or any other similar representation of information. The terms "electronic document" or "document" may refer to a data structure, a computer file, or a resource used to record data and include various file types and / or data formats, such as word processing documents, spreadsheets, slide presentations, multimedia elements, web pages, and / or source code documents, and / or the like. Information objects may include, for example, markup and / or source code documents such as HTML, XML, JSON, Apex®, CSS, JSP, MessagePack™, Apache® Thrift™, ASN.1, Google® Protocol Buffers (protobuf), or other documents / formats as described here. An information object can have both a logical and a physical structure. Physically, an information object comprises one or more units called entities. An entity is a unit of storage that contains content and is identified by a name. An entity can reference other entities to cause their inclusion in the information object. An information object begins in a document entity, also called the root element (or "root"). Logically, an information object consists of one or more declarations, elements, comments, character references, and processing instructions, all of which are specified in the information object (e.g., using markup).

[0210] The term "data item" as used herein refers to an atomic state of a particular object with at least one specific property at a particular point in time. Such an object is typically identified by an object name or an object identifier, and the properties of such an object are typically defined as database objects (e.g., fields, records, etc.), object instances, or data elements (e.g., markup language elements / tags, etc.). Additionally or alternatively, the term "data item" as used herein may refer to data items and / or content items, although these terms may refer to different concepts. The term "data item" or "item" as used herein refers to a unit that is indivisible at a particular level of abstraction and has a clearly defined boundary. A data item is a logical part of an information object (e.g.,of an electronic document) that begins with a start tag (e.g. ". <element> ") and end with a suitable end tag (e.g. "< / element> “) or just an empty element tag (e.g. “ <element / > “). All characters between the start tag and the end tag, if any, are the content of the element (referred to herein as “content elements” or the like).

[0211] The content of an entity can comprise one or more content items, each of which is associated with a data type representation. A content item can contain, for example, attribute values, character values, URIs, qualified names (qnames), parameters, and the like. A qname is a fully qualified name of an element, attribute, or identifier in an information object. A qname associates a URI of a namespace with a local name of an element, attribute, or identifier in that namespace. To establish this connection, qname assigns a prefix to the local name that corresponds to its namespace. The qname consists of a URI of the namespace, the prefix, and the local name. Namespaces are used to uniquely name elements and attributes in information objects. Content elements can contain text content (e.g., " <element> Content element< / element> ”), attributes (e.g. “ <element attribute="„attributWert"">") and other elements called "child elements" (e.g. " <element1> <element2> Content element < / element1> "). An "attribute" can refer to a markup construct containing a name-value pair that exists within a start tag or an empty element tag. Attributes contain data related to their element and / or control the element's behavior.

[0212] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a particular device, such as computing devices, mechanical devices, memory space, processor / CPU time and / or processor / CPU utilization, processor and accelerator loads, hardware time or utilization, electrical power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database and applications, workload units, and / or the like. A "hardware resource" may refer to computing, storage, and / or network resources provided by one or more physical hardware elements.A "virtualized resource" can refer to computing, storage, and / or network resources provided to an application, device, system, etc., through a virtualization infrastructure. The term "network resource" or "communications resource" can refer to resources accessible by computing devices / systems over a communications network. The term "system resources" can refer to any type of shared entity used to provide services and can include computing and / or network resources. System resources can be viewed as a set of coherent functions, network data objects, or services accessible by a server, where such system resources are located on a single host or multiple hosts and are uniquely identifiable.The term "channel," as used herein, refers to any transmission medium, tangible or otherwise, used to communicate data or a data stream. The term "channel" may be synonymous with and / or equivalent to "communications 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 denoting a path or medium over which data is communicated. Additionally, the term "link," as used herein, refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information. As used herein, the term "radio technology" refers to a technology for wirelessly transmitting and / or receiving electromagnetic radiation for information transmission.The term "radio access technology" or "RAT" refers to the technology used for the underlying physical connection to a radio-based communications network. As used herein, the term "communications protocol" (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communications device and / or system to communicate with other devices and / or systems, including instructions for packetizing / depacketing data, modulating / demodulating signals, implementing protocol stacks, and / or the like.

[0213] As used herein, the term "radio technology" refers to a technology for wirelessly transmitting and / or receiving electromagnetic radiation for information transmission. The term "radio access technology" or "RAT" refers to the technology used for the underlying physical connection to a radio-based communications network. As used herein, the term "communication protocol" (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communications device and / or system to communicate with other devices and / or systems, including instructions for packetizing / depacketizing data, modulating / demodulating signals, implementing protocol stacks, and / or the like. Examples of wireless communications protocols that may be used in various embodiments include:include a radio communication technology according to the Global System for Mobile Communications (GSM), a radio communication technology according to the General Packet Radio Service (GPRS), a radio communication technology according to the Enhanced Data Rates for GSM Evolution (EDGE) and / or a radio communication technology of the Third Generation Partnership Project (3GPP) including, for example, 3GPP Fifth Generation (5G) or New Radio (NR), Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), Long Term Evolution (LTE), LTE-Advanced (LTE Advanced), LTE Extra, LTE-A Pro, cdmaOne (2G), Code Division Multiple Access 2000 (CDMA 2000), Cellular Digital Packet Data (CDPD), Mobitex, Circuit Switched Data (CSD), High-Speed CSD (HSCSD), Universal Mobile Telecommunications System (UMTS), Wideband Code Division Multiple Access (W-CDM), High Speed Packet Access (HSPA), HSPA Plus (HSPA+), Time Division-Code Division Multiple Access (TD-CDMA),Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), LTE LAA, MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UTRA (E-UTRA), Evolution-Data Optimized oder Evolution-Data Only (EV-DO), Advanced Mobile Phone System (AMPS), Digital AMPS (D-AMPS), Total Access Communication System / Extended Total Access Communication System (TACS / ETACS), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), Cellular Digital Packet Data (CDPD), DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Personal Handy-phone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), auch als ein generisches 3GPP-Zugangsnetz- oder GAN-Standard bezeichnet), Bluetooth®, Bluetooth Low Energy (BLE), IEEE 802.15.4-basierte Protokolle (z. B. IPv6 over Low power Wireless Personal Area Networks (6LoWPAN), WirelessHART, MiWi, Thread,802.11a, etc.), WiFi-direct, ANT / ANT+, ZigBee, Z-Wave, 3GPP device-to-device (D2D) or Proximity Services (ProSe), Universal Plug and Play (UPnP), Low-Power Wide-Area Network (LPWAN), Long Range Wide Area Network (LoRA) or LoRaWAN™ developed by Semtech and the LoRa Alliance, Sigfox, Wireless Gigabit Alliance (WiGig) standard, Worldwide Interoperability for Microwave Access (WiMAX), mmWave standards in general (e.g., wireless systems operating at 10-300 GHz and above, such as WiGig, IEEE 802.11ad, IEEE 802.11ay, etc.), V2X communication technologies (including 3GPP C-V2X), Dedicated Short Range Communications (DSRC) communication systems, such as Example Intelligent Transport Systems (ITS) including the European ITS-G5, ITS-G5B, ITS-G5C, etc. In addition to the standards listed above, any number of satellite uplink technologies may be used for the purposes of this disclosure, including, for example, radios,that conform to standards issued by, among others, the International Telecommunication Union (ITU) or the European Telecommunications Standards Institute (ETSI). The examples provided herein are thus understood to be applicable to various other communications technologies, both existing and not yet formulated.

[0214] The term "access network" refers to any network that uses any combination of radio technologies, RATs, and / or communication protocols used to connect user devices and service providers. In the context of WLANs, an "access network" is an IEEE 802 local area network (LAN) or metropolitan area network (MAN) between end devices and access routers connected to provider services. The term "access router" refers to a router that terminates a media access control (MAC) service from end devices and forwards user traffic to information servers according to Internet Protocol (IP) addresses.

[0215] The term "SMTC" refers to an SSB-based measurement timing configuration configured with SSB MeasurementTimingConfiguration. The term "SSB" refers to a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, which includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a PBCH. The term "Primary Cell" refers to the MCG cell operating on the primary frequency and in which the UE either performs the Initial Call Establishment procedure or initiates the Call Reestablishment procedure. The term "Primary SCG Cell" refers to the SCG cell in which the UE performs Random Access when performing the Reconfiguration with Synchronization procedure for DC operation. The term "Secondary Cell" refers to a cell that provides additional radio resources in addition to a dedicated cell for a CA-configured UE.The term "secondary cell group" refers to the subset of coverage cells that includes the PScell and zero or more secondary cells for a UE configured with DC. The term "coverage cell" refers to the primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, since there is only one coverage cell consisting of the primary cell. The term "coverage cell" or "coverage cells" refers to the set of cells that includes the one or more special cells and all secondary cells for a UE configured with CA in RRC_CONNECTED. The term "special cell" refers to the Pcell of the MCG or the PScell of the SCG for DC operation; otherwise, the term "special cell" refers to the Pcell.

[0216] The term "A1 policy" refers to a type of declarative policy expressed using formal statements that enable the non-RT-RIC function in the SMO to guide the near-RT-RIC function and thus the RAN toward better fulfillment of the RAN intent.

[0217] The term "A1 enrichment information" refers to information used by a near-RT RIC that is collected or derived at a SMO / non-RT RIC either from data sources external to the network or from network functions themselves.

[0218] The term "A1 policy-based traffic steering process mode" refers to an operation mode in which the Near-RT RIC is configured by the A1 policy to use traffic steering actions to ensure a more specific notion of network performance (for example, to be applied to smaller groups of E2 nodes and UEs in the RAN) than that which it ensures in background traffic steering.

[0219] The term "background traffic steering processing mode" refers to an operating mode in which the Near-RT RIC is configured by O1 to use traffic steering actions to ensure general background network performance that applies broadly across E2 nodes and UEs in the RAN.

[0220] The term "RAN baseline behavior" refers to the default RAN behavior as configured by SMO on the E2 nodes.

[0221] The term "E2" refers to an interface connecting the Near-RT RIC and one or more O-CU-CPS, one or more O-CU-UPS, one or more O-DUS, and one or more O-eNBs.

[0222] The term "E2 node" refers to a logical node that terminates the E2 interface. In this version of the specification, ORAN nodes that terminate the E2 interface are: for NR access: O-CU-CP, O-CU-UP, O-DU, or any combination; and for E-UTRA access: O-eNB.

[0223] The term "intent," in the context of O-RAN systems / implementations, refers to a declarative policy to direct or guide the behavior of RAN functions, thereby enabling the RAN function to compute the optimal outcome to achieve the specified goal.

[0224] The term "intelligent O-RAN non-real-time RAN control" or "non-RT-RIC" refers to a logical function that enables non-real-time control and optimization of RAN elements and resources, an AI / ML workflow including model training and updates, and policy-based guidance of applications / features in near-RT-RIC.

[0225] The term "Near-RT-RIC" or "intelligent O-RAN near-real-time RAN control" refers to a logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained (e.g., UE-based, cell-based) data collection and actions over the E2 interface.

[0226] The term "O-RAN Central Unit" or "O-CU" refers to a logical node that hosts RRC, SDAP, and PDCP protocols.

[0227] The term "O-RAN Central Unit - Control Plane" or "O-CU-CP" refers to a logical node that hosts the RRC and the control plane portion of the PDCP protocol.

[0228] The term "O-RAN Central Unit - User Plane" or "O-CU-UP" refers to a logical node that hosts the user plane portion of the PDCP protocol and the SDAP protocol.

[0229] The term "distributed O-RAN unit" or "O-DU" refers to a logical node that hosts RLC / MAC / high-PHY layers based on a lower-layer functional division.

[0230] The term "O-RAN-eNB" or "O-eNB" refers to an eNB or ng-eNB that supports an E2 interface.

[0231] The term "O-RAN Radio Unit" or "O-RU" refers to a logical node that hosts a low-PHY layer and RF processing based on a lower-layer functional separation. This is similar to 3GPP's "TRP" or "RRH" but is more specific regarding the inclusion of the low-PHY layer (FFT / iFFT, PRACH extraction).

[0232] The term "O1" refers to an interface between orchestration and management entities (orchestration / NMS) and O-RAN-managed operations and management elements, through which FCAPS management, software management, file management, and other similar functions are to be achieved.

[0233] The term "RAN UE group" refers to aggregations of UEs whose grouping in the E2 nodes is set by E2 procedures, also based on the protection scope of A1 policies. These groups can then be the target of E2 CONTROL or POLICY messages.

[0234] The term "traffic steering action" refers to the use of a mechanism to change RAN behavior. Such actions include E2 procedures such as CONTROL and POLICY.

[0235] The term "inner routing loop" refers to the part of routing processing triggered by the arrival of periodic TS-related key performance measurements (KPMs) from E2 nodes, which includes UE grouping, setting up additional data collection from the RAN, and selecting and executing one or more optimization actions to enforce routing policies.

[0236] The term "outer routing loop" refers to the part of routing processing triggered by the near-RT-RIC setup or update procedure for routing-aware resources based on information from A1 policy setup or update, A1 enrichment (EI) information, and / or the result of a near-RT-RIC evaluation, which includes the initial configuration (prerequisites) and injection of related A1 policies, triggering conditions for TS changes.

[0237] The term "traffic steering processing mode" refers to an operating mode in which either the RAN or the Near-RT RIC is configured to ensure a specific network performance level. This performance level includes aspects such as cell load and throughput and may apply differently to different E2 nodes and UEs. During this process, traffic steering actions are used to meet the requirements of this configuration.

[0238] The term "traffic routing objective" refers to the intended performance result desired by the network configured to achieve near-RT RIC over O1.

[0239] Furthermore, each of the disclosed embodiments and example implementations may be embodied in various types of hardware, software, firmware, middleware, or combinations thereof, including control logic, and using such hardware or software in a modular or integrated manner. Furthermore, each of the software components or functions described herein may be implemented as software, program code, scripts, instructions, etc., that can be executed by processor circuits. These components, functions, programs, etc., may be developed in any suitable computer language, such asPython, PyTorch, NumPy, Ruby, Ruby on Rails, Scala, Smalltalk, Java™, C++, C#, „C", Kotlin, Swift, Rust, Go (oder „Golang"), EMCAScript, JavaScript, TypeScript, Jscript, ActionScript, Server-Side JavaScript (SSJS), PHP, Pearl, Lua, Torch / Lua mit Just-In-Time-Compiler (LuaJIT), Accelerated Mobile Pages Script (AMPscript), VBScript, JavaServer Pages (JSP), Active Server Pages (ASP), Node.js, ASP.NET, JAMscript, Hypertext Markup Language (HTML), erweiterbares HTML (XHTML), Extensible Markup Language (XML), XML User Interface Language (XUL), Scalable Vector Graphics (SVG), RESTful API Modeling Language (RAML), Wiki Markup oder Wikitext, Wireless Markup Language (WML), Java Script Object Notion (JSON), Apache® MessagePack™, Cascading Stylesheets (CSS), Extensible Stylesheet Language (XSL), Mustache Template Language, Handlebars Template Language, Guide Template Language (GTL), Apache® Thrift, Abstract Syntax Notation One (ASN.1), Google® Protocol Buffers (protobuf), Bitcoin Script, EVM® Bytecode, Solidity™, Vyper (derived from Python), Bamboo, Lisp Like Language (LLL), Simplicity provided by Blockstream™, Rholang, Michelson, Counterfactual, Plasma, Plutus, Sophia, Salesforce® Apex® and / or any other programming language or development tool, including proprietary programming languages and / or development tools. The software code may be stored as computer- or processor-executable instructions or instructions on a physical, non-transitory, computer-readable medium. Suitable media include, for example, RAM, ROM, magnetic media such as hard disks or floppy disks, or an optical medium such as CD (Compact Disc) or DVD (Digital Versatile Disk), flash memory and the like, or any combination of such storage or transmission devices. ABBREVIATIONS

[0240] Unless otherwise used herein, the terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR 21.905 v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein. Table 3 Abbreviations: 3GPP Third Generation Partnership Project IBE In-band emission PUSCH Shared physical uplink channel 4G Fourth generation IEEE Institute of Electrical and Electronics Engineers QAM Quadrature amplitude modulation 5G Fifth generation IEI Information element identification QCI QoS class of the identifier 5GC 5G core network IEIDL Information element identifier data length QCL Quasi-colocalization AC Application client IETF Internet Engineering Task Force QFI QoS flow ID, QoS flow identifier ACK Confirmation IF Infrastructure QoS Quality of service ACID Application client identification IN THE Interference measurement, intermodulation, IP multimedia QPSK Quadrature (quaternary) phase-shift keying AF Application function IMC IMS credentials QZSS Quasi-Zenith satellite system AM Confirmed mode IMEI International mobile device identity RA-RNTI Direct Access-RNTI AMBR Aggregated maximum bitrate IMGI International mobile group identity RAB Radio access bearer, random access burst AMF Access and mobility management function IMPI Private IP multimedia identity RACH Direct access channel TO Access network IMPULSE Public IP multimedia identity RADIUS Remote Authentication Dial In User Service ANR Automatic neighborhood relationship IMS IP multimedia subsystem RAN Radio access network AP Application protocol, antenna connection, access point IMSI International mobile subscriber identity EDGE Random number (used for authentication) API Application programming interface IoT Internet of Things RARE Direct access response APN Name of the access point IP Internet Protocol COUNCIL Radio access technology ARP Allocation and storage priority Ipsec IP security, Internet Protocol security ROUGH Routing area update ARQ Automatic retry request IP-CAN IP connectivity access network RB Resource block, radio carrier AS Access layer IP-M IP multicast RBG Resource block group ASP Application service providers IPv4 Internet Protocol Version 4 REG Resource element group ASN.1 Abstract Syntax Notation One IPv6 Internet Protocol Version 6 Rel Release EXIT Authentication server function IR Infrared REQ Requirement AWGN Additive white Gaussian noise IS Synchronous RF High frequency BAP Backhaul adaptation protocol IRP Integration reference point RI Rank indicator BCH Broadcast channel ISDN Digital network for integrated services RIV Resource indicator value BER Bit error ratio ISIM IM Service Identity Module RL radio connection BFD Beam failure detection ISO International Organization for Standardization RLC Radio link control, radio link control layer BLER Block error rate ISP Internet service provider RLC AM RLC Confirmed Mode BPSK Binary phase shift keying IMF Interworking function RLC UM RLC Unacknowledged Mode BRAS Broadband remote access server I-WLAN Interworking WLAN RLF Radio connection failure BSS Business support system Limitation of the convolutional code, individual USIM key length RLM Radio connection monitoring BS Base station kB Kilobyte (1000 bytes) RLM-RS Reference signal for RLM BSR Buffer status report kbps kilobits per second RM Registration management BW Bandwidth Kc Encryption key RMC Reference measuring channel BWP Bandwidth part Ki Individual participant authentication key RMSI Remaining MSI, remaining minimum system information C-RNTI Temporary cellular network identifier KPI Key performance indicator RN Relay node CA Carrier aggregation, certification authority KQI Key quality indicator RNC Wireless network control CAPEX Investment expenditure KSI Key phrase identifier RNL Radio network layer CBRA Access conflict-based direct access ksps Kilosymbols per second RNTI Temporary radio network identifier CC Component carrier, country code, cryptographic checksum KVM Virtual kernel machine ROHC Robust header compression CCA Clear channel evaluation L1 Layer 1 (physical layer) RRC Radio resource control, radio resource control layer CCE Control channel element L1-RSRP Layer 1 reference signal reception power RRM Radio resource management CCCH common control channel L2 Layer 2 (data link layer) RS Reference signal CE Coverage improvement L3 Layer 3 (network layer) RSRP Reference signal reception power CDM Content delivery network LAA Licensed Assisted Access RSRQ Reference signal reception quality CDMA Code division multiplex access LAN Local network RSSI Reception signal strength indicator CFRA Non-contentious random access LADN Local Area Data Network RSU Roadside unit CG cell group LBT Listen Before Talk RSTD Reference signal time difference CCF Billing gateway function LCM Lifecycle management RTP Real-time protocol CHF Clearing function LCR Low chip rate RTS Ready to send CI Cell identity LCS Location services RTT Orbital time CID Cell ID (e.g. positioning method) LCID Logic channel ID Rx reception, receiving, receiver CIM Common information model LI Shift indicator S1AP S1 application protocol CIR Carrier-to-interference ratio LLC Logic link control, low-layer compatibility S 1-MMES 1 for the control level CK Encryption key LPLMN Local PLMN S1-U S1 for the user level CM Connection management, conditionally mandatory LPP LTE positioning protocol S-GW Supply gateway CMAS Commercial mobile warning service LSB Least significant bit S-RNTI Temporary SRNC radio network identity CMD command LTE Long-Term Evolution S-TMSI Temporary SAE mobile station identification CMS Cloud management system LWA LTE Wi-Fi aggregation SA Standalone operating mode CO Conditionally optional LWIP LTE / WLAN radio layer integration with IPsec tunnel SAE System architecture development CoMP Coordinated multiple point LTE Long-Term Evolution SAP Service access point CORESET Tax resource rate M2M Machine-to-machine SAPD Service access point descriptor COTS Commercial series product MAC Media access control (protocol layer context) SAPI Service access point identifier CP Control plane, cyclic prefix, connection point MAC Message authentication code (security / encryption context) SCC Secondary component carrier, secondary CC CPD Connection point descriptor MAC-A MAC for authentication and key agreement (context TSG T WG3) Scell secondary cell CPE Equipment at the customer site MAC-I MAC for data integrity of signaling messages (context TSG T WG3) SCEF Fitness for duty detection function CPICH Joint pilot channel MANO Management and orchestration SC-FDMA Single-carrier frequency-division multiple access CQI Channel quality indicator MBMS Multimedia broadcast and multicast service SCG Secondary cell group CPU CSI processing unit, central processing unit MBSFN Multimedia Broadcast Multicast Service Single Frequency Network SCM Security context management C / R Command / Response field bit MCC Mobile country code SCS Subcarrier spacing CRAN Cloud radio access network, Cloud RAN MCG Master cell group SCTP Stream control transfer protocol CRB Common resource block MCOT Maximum channel occupancy time SDAP Service data adaptation protocol, service data adaptation protocol layer CRC Cyclic redundancy check MCS Modulation and coding scheme SDL Additional downlink CRI Channel health information resource indicator, CSI-RS resource indicator MDAF Management data analysis function SDNF Network function with structured data storage C-RNTI Cell RNTI MDAS Management Data Analysis Service SDP Meeting description minutes CS Circuit-switched MDT Minimizing drive tests SDSF Structured data storage function CSAR Cloud service archive ME mobile device SDU Service data unit CSI Channel status information MeNB Master eNB SEAF Safety anchor function CSI-IM CSI interference measurement MER Message error ratio SeNB Secondary eNB CSI-RS CSI reference signal MGL Measuring gap length SEPP Security Edge Protection Proxy CSI-RSRP CSI reference signal reception power MRP Measurement gap repetition period SFI Slot format specification CSI-RSR Q CSI reference signal reception quality MIB Master information block, management information base SFTD Spatial frequency-time diversity, SFN and frame timing difference CSI-SINR CSI signal-to-noise and interference ratio MIMO Multiple input-multiple output SFN System frame number CSMA Carrier verification multiple access MLC Mobile Location Center SgNB Secondary gNB CSMA / C A CSMA with collision avoidance MM Mobility management SGSN Serving GPRS support node CSS Common search space, cell-specific search space MME Mobility management entity S-GW Supply gateway CTF Settlement trigger function MN Master node SI System information CTS Ready to send MNO Mobile network operators SI-RNTI System Information RNTI CW Code word MO Measuring object, mobile origin SIB System information block CWS Competitive window size MPBCH Physical MTC broadcast channel SIM Participant identity module D2D Device-to-device MPDCCH Physical MTC downlink control channel SIP Meeting-initiated minutes DC Dual connectivity, direct current MPDSCH Shared physical MTC downlink channel SIP System-in-Package DCI Downlink control information MPRACH Physical MTC direct access channel SL Sidelink DF Insert flavor MPUSCH Shared physical MTC uplink channel SLA Service Level Agreement DL Downlink MPLS MultiProtocol Label Switching SM Session management DMTF Distributed Management Working Group MS Mobile station SMF Session management function DPDK Data plane development kit MSB Most significant bit SMS Short message service DM-RS, DMRS Demodulation reference signal, MSC Mobile switching center SMSF SMS function DN data network MSI Minimum system information, MCH planning information SMTC SSB-based measurement timing configuration DNN Data network name MSID Mobile station identification SN Secondary node, sequence number DNAI Data network access identifier MSIN Mobile station identification number SOC System-on-Chip DRB Data radio carrier MSISDN Mobile subscriber ISDN number SON Self-organizing network DRS Discovery reference signal MT Mobile completed, mobile completion SpCell Special cell DRX Discontinuous reception MTC Machine type communication SP-CSI-R NTI Semipersistent CSI-RNTI DSL Domain-specific language Digital subscriber line mMTC Massive MTC, massive machine type communication PLC Semi-persistent planning DSLAM DSL access multiplexer MU-MIM O Multi-user MIMO SQN Sequence number DwPTS Downlink pilot time slot MWUS MTC wake-up signal, MTC-WUS SR Planning requirement E-LAN Ethernet local area network NAKED Negative confirmation SRB Signaling radio carrier E2E end-to-end NAI Network access identifier SRS Sounding reference signal ECCA Advanced Clear Channel Assessment, Advanced CCA NAS Non-access stratum, non-access stratum layer SS Synchronization signal ECCE Improved control channel element, improved CCE NCT Network connectivity topology SSB Synchronization signal block ED Energy detection NC-JT Non-coherent joint transmission SSID Service record identifier EDGE Improved data rates for GSM Evolution (GSM Evolution) NEC Network capabilities discovery SS / PBCH block EAS Edge application server NE-DC NR-E-UTRA dual connectivity SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator EASID Edge application server identification NEF Network discovery function SSC Session and service continuity ECS Edge Configuration Server NF Network function SS-RSR P Synchronization signal-based reference signal reception power ECSP Edge computing service providers NFP Network forwarding path SS-RSRQ Synchronization signal-based reference signal reception quality EDN Edge data network NFPD Network forwarding path descriptor SS-SINR Synchronization signal-based signal-to-noise and interference ratio EEC Edge Enabler Client NFV Network function virtualization SSS Secondary synchronization signal EECID Edge enabler client identification NFVI NFV infrastructure SSSG Search space set group EES Edge Enabler Server NFVO NFV Orchestrator SSSIF Search space set indicator EESID Edge enabler server identification NG Next generation, next-gen SST Slice / Service Types BEFORE Edge hosting environment NGEN-D C NG-RAN-E-UTRA-NR dual connectivity SU-MIM O Single-user MIMO EGMF Exposure control management function NM Network manager SUL Additional uplink EGPRS Improved GPRS NMS Network management system TA Timing advance, tracking area EIR Equipment Identity Register N-PoP Network presence point TAC Tracking area code eLAA extended licensed assisted access, extended LAA NMIB, N -MIB Narrowband MIB DAY Timing Advance Group European Championship Element Manager NPBCH Physical narrowband broadcast channel TAI Persecution area identity eMBB enhanced mobile broadband NPDCCH Physical narrowband downlink control channel DEW Tracking area update EMS Element management system NPDSCH Shared physical narrowband downlink channel TB Transport block eNB Evolved NodeB, E-UTRAN NodeB NPRACH Narrowband random access channel TBS Transport block size EN-DC E-UTRA-NR dual connectivity NPUSCH Shared physical narrowband uplink channel TBD Still to be defined EPC Evolved Packet Core NPSS Narrowband primary synchronization signal TCI Transmission configuration indicator EPDCCH extended PDCCH, extended physical downlink control channel NSSS Narrowband secondary synchronization signal TCP Transmission communication protocol EPRE Energy per resource element NR New Radio, Neighborhood Relationship TDD Time duplex EPS Developed package system NRF NF repository function TDM Time-division multiplex EREG Extended REG, extended resource element groups NRS Narrowband reference signal TDMA Time-division multiple access ETSI European Telecommunications Standards Institute NS Network service TE End device ETWS Earthquake and tsunami warning system NSA Non-standalone operating mode TEID Tunnel endpoint identifier eUICC embedded UICC, embedded universal integrated circuit card NSD Network service descriptor TFT Traffic flow template E-UTRA Developed UTRA NSR Network service recording TMSI Temporary mobile subscriber identity E-UTRA N Developed UTRAN NSSAI Network Slice Selection Assistant Information TNL Network transport layer EV2X Advanced V2X S-NNSA I Individual NSSAI TPC Transmit power control F1AP F1 application log NSSF Network slice selection function TPMI Transmitted precoding matrix indicator F1-C F1 control plane interface NW network TR Technical report F1-U F1 user-level interface NWUS Narrowband wake-up signal, narrowband WLTS TRP, TRxP Transmission receiving point FACCH Fast associated control channel NZP Non-zero performance TRS Tracking reference signal FACCH / I F Fast associated control channel / full rate O&M Operation and maintenance TRX Transceiver FACCH / H Fast associated control channel / half rate ODU2 Optical Channel Data Unit - Type 2 TS Technical specifications, technical standard ACADEMIC SUBJECT Forward access channel OFDM Orthogonal frequency division multiplexing TTI Transmission time interval FAUSC H Fast uplink signaling channel OFDMA Orthogonal frequency division multiple access Tx transmission, transmit, transmitter Facebook Function block OOB Out-of-band U-RNTI Temporary UTRAN radio network identity FBI Feedback information OOS Not in sync UART Universal asynchronous receiver and transmitter FCC Federal Communications Commission OPEX Operating costs UCI Uplink control information FCCH Frequency correction channel OSI Other system information UE User terminal FDD Frequency duplex OSS Operational support system UDM Uniform data management FDM Frequency division multiplex OTA Over-the-Air / Air UDP User datagram protocol FDMA Frequency division multiple access PAPR Peak-to-average power ratio UDSF Network function for unstructured data storage FE Frontend PAR Peak-to-average ratio UICC Universal integrated circuit card FEC Forward error correction PBCH Physical broadcast channel UL Uplink FFS for further investigation PC Performance control, personal computer UM Unconfirmed mode FFT Fast Fourier Transformation PCC Primary component carrier, primary CC UML Unified modeling language feLAA further expanded licensed assisted access, further expanded LAA Pcell primary cell UMTS Universal mobile telecommunications system FN Frame number PCI Physical cell ID, Physical cell identity UP User level FPGA field programmable gate array PCEF Policy and fee enforcement function UPF User level function FR Frequency range PCF Policy control function URI Uniform resource identification FQDN fully qualified domain name PCRF Policy control and fee regulation function URL Unified Resource Locator G-RNTI Temporary GERAN radio network identity PDCP Packet data convergence protocol, packet data convergence protocol layer URLLC Ultra-reliable and low latency GERAN GSM EDGE RAN, GSM EDGE radio access network PDCCH Physical downlink control channel USB Universal Serial Bus GGSN Gateway GPRS support node PDCP Packet Data Convergence Protocol USIM Universal Subscriber Identity Module 1 GLONAS S GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Global Satellite Navigation System) PDN Packet data network, public data network USS UE-specific search space gNB Next-generation NodeB PDSCH Shared physical downlink channel ULTRA Terrestrial UTRA radio access gNB-CU gNB central unit, next-generation NodeB central unit PDU Protocol data unit UTRAN Universal Terrestrial Radio Access Network gNB-DU distributed gNB unit, next-generation distributed NodeB unit PEI Permanent equipment identifiers UwPTS Uplink pilot time slot GNSS Global Navigation Satellite System PFD Packet flow description V2I Vehicle-to-Infrastructure GPRS General packet-oriented radio service P-GW PDN Gateway V2P Vehicle-to-pedestrian GPSI Generic public subscriber identifier PHICH Physical Hybrid ARQ Indicator Channel V2V Vehicle-to-vehicle GSM Global System for Mobile Communications, Groupe Spécial Mobile PHY Physical layer V2X Vehicle-to-everything GTP GPRS tunnel protocol PLMN Public terrestrial mobile network VIM Virtualized Infrastructure Manager GTP-U GPRS tunneling protocol for user plane PIN Personal identification number VL Virtual Link GTS Go To Sleep Signal (related to WUS) PM Performance measurement VLAN Virtual LAN, Virtual Local Area Network RUBBER Globally unique MME identifier PMI Precoding matrix indicator VM Virtual machine GUTI Globally unique temporary UE identity PNF Physical network function VNF Virtualized network function HARQ Hybrid ARQ, hybrid automatic retry request PNFD Physical network function descriptor or VNFFG VNF forwarding graph HANDO Handover PNFR Physical network function recording VNFFG D VNF forwarding graph descriptor HFN HyperFrame number POC PTT over Cellular VNFM VNFM Manager HO Hard handover PP, PTP Point-to-point VoIP Voice over IP, Voice over Internet Protocol HLR Home location register PPP Point-to-point protocol VPLMN Visited public terrestrial mobile network HN home network PRACH Physical RACH VPN Virtual private network HO Handover PRB Physical resource block VRB Virtual resource block HPLMN Public terrestrial mobile home network PRG Physical resource block group WiMAX Worldwide Interoperability for Microwave Access HSDPA High-speed downlink packet access ProSe Proximity services, proximity-based service Wi-Fi Wireless local area network HSN Jump sequence number PRS Positioning reference signal WMAN Wireless urban network HSPA High-speed packet access PRR Packet reception radio WPAN Wireless personal network HSS Home subscriber server PS Parcel services X2-C X2 control plane HSUPA High-speed uplink packet access PSBCH Physical sidelink broadcast channel X2-U X2 user level HTTP Hypertext Transfer Protocol PSDCH Physical sidelink downlink channel XML Extensible Markup Language HTTPS Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL, ie port 443) PSCCH Physical sidelink control channel XRES Expected user response I-Block Information block PSSCH Shared physical sidelink channel XOR Exclusive OR ICCID Integrated circuit card identification PScell Primary Scell ZC Zadoff-Chu IAB Integrated access and backhaul PSS Primary synchronization signal ZP Zero Po ICIC Coordination of cross-cell interference PSTN Public telephone exchange network ID Identity, identifier PT-RS Phase tracking reference signal IDFT Inverse discrete Fourier transform PTT Push-to-Talk IE Information element PUCCH Physical uplink control channel

[0241] The foregoing description provides illustration and description of various embodiments, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be obtained from practice of various embodiments. Where specific details are set forth to describe embodiments of the disclosure, it should be apparent to those skilled in the art that the disclosure may be practiced without those specific details or with some variation thereof. It should be understood, however, that there is no intention to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives consistent with the present disclosure and the appended claims. QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited patent literature

[0000] US 63 / 412,786

[0001] < / element>

Claims

[1] Device for a network node, comprising: Discovering a network data analysis function (NWDAF) via a network function repository function (NRF); Sending an analysis request or subscribing to the selected NWDAF with a criterion based on a capture data analysis ID, an event ID, and event parameters; Selecting an instance of a data collection coordination function (DCCF), if DCCF is used for data collection, based on DCCF coverage area information; and Receiving collection data or data analysis from the NWDAF after the NWDAF has processed the data collected by the DCCF. [2] The device of claim 1, wherein the discovery and selection of the NWDAF is based on an analysis ID of the collection service, supported services, NWDAF capabilities, or NWDAF coverage area information. [3] The device of claim 1, wherein the processing circuitry is further configured to determine the NWDAF based on supported analyses registered with the DCCF or NRF. [4] The device according to claim 1, wherein the event ID comprises one of collection target status update, collection target mobility, collection configuration update, collection capability update, or collection service quality update. [5] The device of claim 1, wherein the processing circuitry is further configured to specify a reporting endpoint for the analyses, such as an application function (AF). [6] The device of claim 1, wherein the processing circuitry is further configured to send an Nnwdaf_AnalyticsSubsription_Subscribe message to the NWDAF. [7] The device of claim 1, wherein the processing circuitry is further configured to receive Nnwdaf_AnalyticsSubscription_Notify comprising the capture data or generated data analytics. [8] The apparatus of claim 1, wherein the processing circuitry is further configured to send a request to the DCCF with a criterion of the capture data or analyses based on the capture data analysis ID, the event ID, and the event parameters. [9] The apparatus of claim 7, wherein the processing circuitry is further configured to cause the SSMF or another collection data and data analysis consumer to register with the NWDAF to receive collection service analyses. [10] The device according to claim 1, wherein the interfaces between SSMF and DCCF, SSMF and NWDAF, SSMF and ADRF are NS5, NS6 and NS7, respectively. [11] A computer-readable medium storing computer-executable instructions which, when executed by one or more processors, result in operations being performed, comprising: Discovering a network data analysis function (NWDAF) via a network function repository function (NRF); Sending an analysis request or subscribing to the selected NWDAF with a criterion based on a collection data analysis ID for a collection service, an event ID, and event parameters; Selecting an instance of a data collection coordination function (DCCF), if DCCF is used for data collection, based on DCCF coverage area information; and Receiving collection data or data analysis from the NWDAF after the NWDAF has processed the data collected by the DCCF. [12] The computer-readable medium of claim 11, wherein the discovery and selection of the NWDAF is based on an analysis ID of the collection service, supported services, NWDAF capabilities, or NWDAF coverage area information. [13] The computer-readable medium of claim 11, wherein the operations further comprise determining the NWDAF based on supported analyses registered with the DCCF or NRF. [14] The computer-readable medium of claim 11, wherein the event ID comprises one of collection target status update, collection target mobility, collection configuration update, collection capability update, or collection service quality update. [15] The computer-readable medium of claim 11, wherein the operations further comprise specifying a reporting endpoint for the analytics, such as an application function (AF). [16] The computer-readable medium of claim 11, wherein the operations further comprise sending an Nnwdaf_AnalyticsSubsription_Subscribe message to the NWDAF. [17] The computer-readable medium of claim 11, wherein the operations further comprise receiving Nnwdaf_AnalyticsSubscription_Notify comprising the collection data or data analytics. [18] The computer-readable medium of claim 11, wherein the interfaces between SSMF and DCCF, SSMF and NWDAF, SSMF and ADRF are NS5, NS6, and NS7, respectively. [19] Method comprising: Discovering a network data analysis function (NWDAF) via a network function repository function (NRF); Sending an analysis request or subscribing to the selected NWDAF with a criterion based on a collection data analysis ID for a collection service, an event ID, and event parameters; Selecting an instance of a data collection coordination function (DCCF), if DCCF is used for data collection, based on DCCF coverage area information; and Receiving collection data or data analysis from the NWDAF after the NWDAF has processed the data collected by the DCCF. [20] The method of claim 19, wherein the discovery and selection of the NWDAF is based on a collection service analysis ID, supported services, NWDAF capabilities, or NWDAF coverage area information.

Images