Method and apparatus for improvements in application discovery and event exposure

Abstract

Provided is a communication method and system for integrating a fifth generation (5G) communication system for supporting higher data rates than the fourth generation (4G) and beyond with technology for the Internet of Things (IoT). [Solution] A method according to the present invention is a method for user equipment (UE) data collection by a network data analytics function (NWDAF), comprising the steps of receiving a request from a service consumer network function (NF) via an application function (AF) requesting UE data collection for analysis, discovering an AF providing UE data collection based on an AF profile of the AF, sending a subscription request to the AF for UE data collection for analysis, the request including at least one event identifier (ID), at least one event filter associated with the at least one event ID, and a target for event reporting, and receiving a notification from the AF on processed data collected according to the subscription.

Description

[Technical Field]

[0001] The present invention relates generally to improvements in application function (AF) discovery and event exposure. [Background technology]

[0002] Since the commercialization of fourth-generation (4G) communication systems, efforts have been made to develop improved fifth-generation (5G) or pre-5G (pre-5G) communication systems to meet the increasing demand for wireless data traffic. Therefore, 5G or pre-5G communication systems are also known as "Beyond 4G Networks" or "Post-LTE Systems." To achieve higher data rates, 5G communication systems are expected to be implemented in higher frequency (mmWave) bands, such as the 60 GHz band. To reduce radio wave propagation loss and extend transmission distances, technologies such as beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas are being discussed for 5G communication systems. In addition, in the 5G communication system, development is underway to improve the system network based on advanced small cells, cloud Radio Access Networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, moving networks, cooperative communications, CoMP (Coordinated Multi-Points), and receiver-side interference cancellation.For 5G systems, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding) and advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed.

[0003] The Internet is currently evolving from a human-centered connected network where humans generate and consume information to an IoT (Internet of Things) network where distributed entities such as things exchange and process information. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connections to cloud servers, is also emerging. Realizing the IoT requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology. Recent research has focused on sensor networks, M2M (Machine-to-Machine) communication, and MTC (Machine-Type Communication). In such an IoT environment, intelligent IT (Internet of Technology) services can be provided that create new value in human life by collecting and analyzing data generated by connected things. Through the integration and combination of existing IT (Information Technology) technologies and various industrial applications, the IoT has the potential to be applied in a variety of fields, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, M2M (Machine to Machine) communication, and MTC (Machine Type Communication) can be realized using techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN), a big data processing technology, is also considered an example of the fusion of 5G and IoT technologies.

[0005] Starting with Release 15, the 3rd Generation Partnership Project (3GPP®) is standardizing what is known as the 5th generation (5G) core service-based architecture (SBA) as part of the system architecture for 5G systems. As part of the system architecture for 5G systems, the 5G core SBA will continue to be developed in Releases 16, 17, and beyond. In the SBA, various network functions and associated services can communicate directly with each other as originators or consumers of services over a common bus known as the service-based interface (SBI).

[0006] It would be advantageous to provide a network data analytics function (NWDAF) within the SBA so that network functions have access to analytics for different purposes, including intelligent automated network configuration and deployment. Summary of the Invention [Problem to be solved by the invention]

[0007] The present invention has been made to address the above problems and shortcomings and to provide at least the advantages described below. [Means for solving the problem]

[0008] According to one aspect of the present invention, there is provided a method for user equipment (UE) data collection by a network data analytics function (NWDAF), comprising: receiving a request from a service consumer network function (NF) via an application function (AF) requiring UE data collection for analysis, discovering an AF that provides the UE data collection based on an AF profile of the AF, sending a request for subscription to the AF for the UE data collection for analysis, the request including at least one event identifier (ID), at least one event filter associated with the at least one event ID, and a target for event reporting, and receiving a notification from the AF regarding processed data collected according to the subscription.

[0009] According to another aspect of the present invention, there is provided a method for user equipment (UE) data collection by an application function (AF), the method including: receiving, from a network data analytics function (NWDAF), a request for subscription to an AF for the UE data collection for the analysis, the request including at least one event ID, at least one event filter associated with the at least one event ID, and a target for event reporting; collecting UE data according to the subscription; processing the UE data based on an agreed-upon policy for UE data collection configured in the AF, the at least one event ID, and the at least one event filter associated with the at least one event ID; and sending a notification regarding the processed UE data to the NWDAF.

[0010] These and other aspects, features, and advantages of particular embodiments of the present invention will become more apparent from the following description taken in conjunction with the drawings. [Effects of the Invention]

[0011] SUMMARY OF THE INVENTION In accordance with the present invention, a method and apparatus for improved application feature discovery and event exposure can be provided. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 illustrates a data collection procedure from a UE according to one embodiment of the present invention. [Figure 2] FIG. 1 illustrates an AF discovery procedure, according to one embodiment of the present invention. [Figure 3] FIG. 2 illustrates a mapping procedure between a UE IP address and a SUPI according to one embodiment of the present invention. [Figure 4]FIG. 2 illustrates the structure of a network function entity according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0013] Various embodiments of the present invention will be described with reference to the drawings. However, it should be understood that the various embodiments of the present invention are not limited to the particular embodiments, and that various modifications, equivalents, and / or alternatives to the embodiments described herein may be made. In the description of the drawings, identical components are designated by similar reference numerals.

[0014] A method for AF discovery and AF event exposure is provided that collects and generates analytics by crowd-sourcing UE input data from multiple application clients on the UE, including new procedures, input parameters, event filters, and analytics filters for interaction between an AF (within or outside the mobile network operator (MNO) domain) with an NWDAF and other 5G core NFs.

[0015] 1-3 illustrate various network functions / entities whose functions and definitions are known in the art in at least 3GPP TS 23.501, 3GPP TS 23.502, and 3GPP TS 23.288. The various known functions of these network functions / entities are modified / enhanced as described below.

[0016] At least some of the various functions / entities may include one or more of the following:

[0017] UE, AF, Network exposure function (NEF), Network repository function (NRF), NWDAF, Session management function (SMF), Access and mobility management function (AMF), and / or Unified data repository (UDR).

[0018] FIG. 1 illustrates a procedure for collecting data from a UE according to one embodiment of the present invention.

[0019] Referring to FIG. 1 , in step 11, the NWDAF subscribes to the AF based on the policies agreed upon during the configuration step. If the AF is a trusted AF within the MNO domain, it configures event identification (ID) and / or AF identification marker corresponding to specific applications (e.g., internal and / or external application IDs) supporting UE data collection for the AF (e.g., related to network function (NF) load analytics or other analysis types) for event exposure from the AF. This configuration can be performed by the MNO (e.g., via operations, administration, and maintenance (OAM) procedures). If the AF is not a trusted AF (i.e., an untrusted AF), it can configure event IDs and / or AF identification markers corresponding to specific applications supporting UE data collection in the NEF (e.g., via OAM procedures).

[0020] In step 12, corresponding application client(s) at the UE level are configured to collect UE data at the corresponding AF addresses from step 11. Different application clients may be configured with different trusted (within the MNO domain) or untrusted AF addresses. The UE may be requested to provide consent at this step. UE-level application clients are configured only for UEs that grant such consent. If the UE revokes consent in the future, the corresponding application client can be reconfigured or signaled to stop UE data collection from that UE. Different application clients can be configured with different expiration periods for either the collected data or the user consent. When the collected data expires, the UE data can be deleted or removed. Upon expiration of the user consent period, a new request can be sent to the UE to renew or update the user consent. The configuration or reconfiguration can be triggered via the control plane (CP) (e.g., via a policy control function (PCF) based on the AF request). Alternatively, the configuration or reconfiguration can be triggered via the user plane (UP) (e.g., via application-level signaling over hypertext transfer protocol secure (HTPPS)).

[0021] In step 13, when the NWDAF receives a request from a service consumer NF requesting UE data collection via the AF (e.g., for NF load analysis or any other type of analysis), it follows the AF discovery procedure as described with reference to FIG. 2.

[0022] In step 14, the NWDAF subscribes to the event exposure capabilities of the AF (in case of trusted AF) or NEF (in case of untrusted AF) based on the AF profile discovered in step 13. Depending on its configuration, the NWDAF may F The NWDAF may contain the target of the analysis report (as a single UE or any UE), internal and / or external, if known, the event ID (i.e., a new event ID related to NF load analysis or any other analysis type), and the event / analysis filter or application ID related to the area of ​​interest.

[0023] In the case of a trusted AF, the area of ​​interest may be in the form of a tracking area (TA). In the case of an untrusted AF, the NEF may translate the area of ​​interest from a TA identified internally within the 5G core to an externally identified geographical zone, and vice versa. The NEF also translates any other event filters as needed, as described above. If the target of the report is any UE, an event / analysis filter related to the area of ​​interest or application ID is provided. If the target is any UE, the AF (directly or via the NEF) or NWDAF subscribes to AMF and SMF event exposures, as described with reference to Figure 3, to retrieve a list of subscription permanent identifiers (SUPIs) (or external UE IDs) and form a mapping between the SUPIs (or external UE IDs) and UE IP addresses.

[0024] Alternatively, the NWDAF may provide a list of searched 5G globally unique SUPIs (or external UE IDs) that support the corresponding application IDs. If some SUPIs (or external UE IDs) do not support the corresponding application IDs, the AF will exclude them from the data collection process.

[0025] If the NWDAF plans to direct certain types of data processing to the AF, new event / analysis filters for AF event exposures can be defined (e.g., for anonymization, normalization, aggregation, or other forms of refinement).

[0026] If the NWDAF plans to indicate a specific type of attribute as a clustering of UE collective behavior (e.g., based on route, destination, average speed, time interval taken by location, relative proximity, direction, speed, or any other clustering attribute / pattern recognition criteria), a new event / analysis filter for AF event exposure can be defined.

[0027] If the NWDAF plans to dictate a minimum number of UEs, a maximum number of UEs, or a specific threshold to trigger collective behavior characterization (e.g., UE speed, average speed, relative distance, or direction characterization), new event / analysis filters for AF event exposure can be defined.

[0028] The event filter for AF event exposure is set based on the request from the NWDAF service consumer (as an analysis filter set in the request to the NWDAF), or the event filter can be set based on the NWDAF internal configuration per analysis type (or event ID).

[0029] At step 15, each AF establishes secure application-layer connectivity to the corresponding UE application client (configured and agreed upon in 11 and 12) using the UE Internet Protocol (IP) address mapped from the SUPI in the AF (see Figure 3).

[0030] In step 16, UE data transmission of raw data to the AF occurs.

[0031] In step 17, each AF post-processes the collected data from multiple UEs (e.g., to aggregate, anonymize, normalize, or otherwise improve the collected data). This is based on instructions received from the NWDAF as input parameters or event filters in step 14. Once post-processing is complete, the AF may notify the NWDAF. Alternatively, the AF may store the data in a data repository such as a UDR via a Unified Data Management (UDM) service. The NWDAF may then collect the data from the UDR.

[0032] FIG. 2 illustrates an AP discovery procedure according to one embodiment of the present invention.

[0033] Referring to Figure 2, in step 21, a trusted AF within the MNO domain registers its capability directly with the NRF, reflecting support for an event ID corresponding to a specific application supporting UE data collection (e.g., a new event ID related to NF load analysis or any other analysis type). In the case of an untrusted AF, the NEF can be configured to register its AF capability with the NRF, reflecting support for an event ID corresponding to a specific application supporting UE data collection (e.g., a new event ID related to NF load analysis or any other analysis type). The mapping between event IDs and application IDs, internal and / or external, can be transparent or registered within the NRF. Multiple AFs (trusted, untrusted, or a combination of both), inside or outside the MNO domain, may support such an event ID, each covering some or all of the set of associated application IDs. Different AFs supporting a particular event ID may share a region of interest (Track Area (TRO)). AFor either trusted or untrusted AFs, additional metadata can be registered within the NRF indicating what types of attributes, clustering criteria, or triggers are supported, along with the event filters defined in Figure 1.

[0034] In step 22, the NWDAF uses the NRF discovery request and response service to identify AFs and collect data. The NWDAF includes the NEF NF type (in the case of an untrusted AF), the new event ID (or event ID), or optionally any internal and / or external application ID provided by the NWDAF service consumer. The NRF returns the matching NEF (in the case of an untrusted AF) or AF profile (in the case of a trusted AF) in the search response. Alternatively, in the case of a trusted AF, the NWDAF can be configured with a list of trusted AFs in the MNO domain that support the new event ID or event ID.

[0035] FIG. 3 illustrates a mapping procedure between a UE IP address and a SUPI according to one embodiment of the present invention.

[0036] Referring to Figure 3, in step 31, the AF (or NEF) subscribes to Nnrf_NFDiscovery based on event filters provided for internal and / or external areas of interest or application IDs, if matching SMF and AMF instances are found.

[0037] However, as an alternative, the AF (or NEF) can find a matching SMF from the UDR (UDM service) based on the SUPI retrieved from the AMF.

[0038] In step 32, stepFor each AMF instance identified in 31, the AF (or NEF) subscribes to AMF event exposure (e.g., the UE moves in or out of the subscribed "area of ​​interest") and provides, for each AMF instance, the part of said area of ​​interest that matches the service area. The AMF instance notifies the SUPI with said area of ​​interest.

[0039] In step 33, a list of SUPIs is retrieved based on step 32, either individually or collectively.

[0040] In step 34, for each SMF instance identified in step 31, the AF (or NEF) subscribes to SMF event exposures (e.g., UE IP address / prefix allocation changes or Protocol Data Unit (PDU) session establishment and / or PDU session teardown from the SMF) and sets the target of the event report as the SUPI based on the list of SUPIs retrieved in steps 32 and 33. The SMF instance provides notification of the UE IP address (per SUPI).

[0041] In step 35, the AF (or NEF) creates and stores a mapping table based on step 34 that converts the SUPI to a UE IP address or vice versa.

[0042] To establish a connection to a UE application client in step 15 or step 16 of Figure 1 to collect UE data, the AF (or NEF) translates the internal SUPI into a corresponding UE IP address based on a mapping table. The UE IP address can be communicated from the AF to the UE application client via application-level signaling (e.g., between the AF and a media session handler in the UE application client), or vice versa. Alternatively, the UE IP address can be encapsulated within the UE data, using an additional security layer to scramble or protect the UE IP address when the UE sends data towards the AF.

[0043] The mapping of SUPI to UE IP address can be configured in the AF, NEF or stored in the UDR by the AF (via the UDM service).

[0044] The mapping of SUPI to UE IP address may be marked, anonymized, or removed from the AF, NEF, or UDR when the user's consent to the data expires or is revoked.

[0045] In the case where the SUPI cannot be exposed directly to either the AF (in the case of a trusted AF) or the NEF (in the case of an untrusted AF), the NWDAF may alternatively follow the procedure described in Figure 3 on behalf of the AF (or NEF). The NWDAF may convert the mapping between the SUPI and the UE IP address into a mapping between an external UE ID (e.g., a General Public Subscription Identifier (GPSI)) and the UE IP address that can be exposed and consumed by the AF (or NEF).

[0046] The mapping of external UE identities (eg, GPSI) to UE IP addresses can be configured in the AF, NEF, or stored in the UDR by the NWDAF (via the UDM service).

[0047] The mapping of external UE IDs (e.g., GPSI) to UE IP addresses can be marked, anonymized, or removed from the AF, NEF, or UDR when the user's consent to the data expires or is revoked.

[0048] 4 shows the structure of a network function entity according to an embodiment of the present invention. The network function (NF) entity according to an embodiment may include an NWDAF entity, an AF entity, an NRF entity, an NEF entity, an SMF entity, an AMF entity, and a UDR entity.

[0049] 4, the NF entity 40 includes a transceiver 41, a controller 42, and a storage unit 43. The controller 42 is defined as a circuit or an application-specific integrated circuit, or at least one processor.

[0050] The transceiver 41 sends and receives messages to / from other NF entities. The transceiver 41 sends requests for subscription to the event exposure functions of other NF entities according to the embodiments described above.

[0051] The controller 42 controls the overall operation of the NF entity 40. For example, the controller 42 processes data collected from UEs in accordance with the subscriptions of the NF entity 40 according to the above-described embodiments.

[0052] The storage unit 42 stores at least one of information transmitted and received via the transceiver 41 and information generated via the controller 42 according to the above-described embodiments. For example, the storage unit 42 stores a UE IP address or an application ID according to the above-described embodiments.

[0053] At least some of the exemplary embodiments described herein may be configured, partially or entirely, using dedicated hardware. Terms such as "component," "module," or "unit" as used herein may include, but are not limited to, hardware devices such as circuits in the form of discrete or integrated components, field programmable gate arrays (FPGAs), or application-specific integrated circuits (ASICs) that perform particular tasks or provide related functionality. In some embodiments, the described elements may be configured to reside on tangible, persistent, addressable storage media and to execute on one or more processors. These functional elements, in some embodiments, include, by way of example, software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutine program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. While the exemplary embodiments are described with reference to components, modules, and units described herein, such functional elements may be combined into fewer elements or separated into additional elements. It should be understood that various combinations of any feature are described herein, and that the described features can be combined in any suitable combination. In particular, features of any exemplary embodiment can be combined with features of any other embodiment, as appropriate, except where such combinations are mutually exclusive. Throughout this specification, the terms "comprising" or "comprises" mean including the specified components but do not exclude the presence of other components.

[0054] Attention is directed to all articles and documents related to this invention that have been filed contemporaneously with or prior to this application and that are open to public inspection herewith, and the contents of all such articles and documents are incorporated herein by reference.

[0055] All features disclosed in this specification (including any claims and drawings set forth in the accompanying documents), and / or all steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and / or steps are mutually exclusive.

[0056] Each feature disclosed in this specification (including any accompanying claims and drawings), unless expressly stated otherwise, may be replaced by an alternative feature serving the same, equivalent, or similar purpose. Thus, unless expressly stated otherwise, each disclosed feature is an example of a generic series of equivalent or similar features.

[0057] While the present invention has been particularly shown and described with reference to specific embodiments thereof, it will be understood by those skilled in the art that various changes in form and detail can be made therein without departing from the spirit and scope of the invention. [Explanation of symbols]

[0058] 40 NF Entities 41 Transceiver 42 Controller 43 Storage section

Claims

1. 1. A method for supporting UE data collection from a user equipment (UE) by a network data analytics function (NWDAF), comprising: receiving a request from a service consumer network function (NF) requesting collection of the UE data for analysis, wherein the request includes analysis filter information, the analysis filter information being associated with at least one application identifier (ID); Discovering an application function (AF) that provides the UE data collection based on an AF profile of the AF, where the AF profile includes at least one event ID and at least one supported application ID supported by the AF; sending a request for a subscription to the AF for the analysis, wherein the subscription is for data collection of the UE; receiving a notification from the AF regarding processed data, wherein the processed data is collected according to the subscription; The UE data collection is performed by a user plane connection between the AF and the UE; A UE Internet Protocol (IP) address is used for the user plane connection.

2. 2. The method of claim 1, wherein the AF is configured based on an agreed upon policy for the UE data collection.

3. 2. The method of claim 1, wherein the UE is configured to collect the UE data at an address of the AF.

4. 2. The method of claim 1, wherein the analysis filter information relates to an area of ​​interest.

5. 10. The method of claim 1, wherein the AF profile is registered with a network repository function (NRF).

6. The step of discovering the AF comprises: sending an NRF discovery request to the NRF; The method of claim 5, further comprising: receiving an NRF discovery response from the NRF, the NRF discovery response including an AF profile of an AF matching the NRF discovery request.

7. The step of sending the subscription request comprises: determining a list of subscription permanent identifiers (SUPIs) from at least one of an access and mobility management function (AMF) and a session management function (SMF) based on the analysis filter information; and 2. The method of claim 1, further comprising: sending to the AF a request for subscription for the determined list of UEs associated with the list of SUPIs.

8. The method of claim 1, further comprising sending a request for a particular type of data processing from the AF to the AF based on event filter information.

9. 1. A method for user equipment (UE) data collection by an application function (AF), comprising: receiving, from a network data analytics function (NWDAF), a subscription request to the AF for collecting the UE data for analysis based on an AF profile of the AF, wherein the AF profile includes at least one event identifier (ID) and at least one supported application ID supported by the AF; collecting UE data from the UE based on the subscription; processing the UE data based on an agreed upon policy for UE data collection configured in the AF; sending a notification about the processed UE data to the NWDAF; The UE data collection is performed by a user plane connection between the AF and the UE; a UE Internet Protocol (IP) address used for the user plane connection; The method, wherein the subscription request is associated with analysis filter information, the analysis filter information being associated with at least one application ID.

10. 10. The method of claim 9, wherein the UE is configured to collect the UE data at an address of the AF.

11. The method of claim 9, wherein the AF profile is registered in a network repository function (NRF).

12. 11. The method of claim 10, further comprising establishing a user plane connection to the UE.

13. The step of establishing a user plane connection comprises: Finding a session management function (SMF) from a unified data repository (UDR) based on a subscription permanent identifier (SUPI) retrieved from an access and mobility management function (AMF); Sending a subscription request to an event exposure function of the SMF, including an event reporting target set in the SUPI, to the SMF based on the list of SUPIs retrieved from the AMF; receiving a UE IP address corresponding to the UE from the SMF; and mapping the UE IP address to the SUPI. the list of SUPIs is determined based on the analysis filter information; 13. The method of claim 12, wherein the analysis filter information relates to an area of ​​interest.

14. A Network Data analytics function (NWDAF) for supporting UE data collection from a user equipment (UE), comprising: Transceiver and a controller connected to the transceiver; The controller and controlling the transceiver to receive a request from a service consumer network function (NF) requesting collection of the UE data for analysis, wherein the request includes analysis filter information, the analysis filter information being associated with at least one application identifier (ID); Discover an application function (AF) that provides the UE data collection based on an AF profile of the AF, where the AF profile includes at least one event identifier (ID) and at least one supported application ID supported by the AF; controlling the transceiver to send to the AF a request for a subscription to the AF for the analysis, wherein the subscription is for data collection of the UE; configured to control the transceiver to receive notifications from the AF regarding processed data, wherein the processed data is collected according to the subscription; The UE data collection is performed via a user plane connection between the AF and the UE; The NWDAF is characterized in that a UE Internet Protocol (IP) address is used for the user plane connection.

15. The analysis filter information relates to an area of ​​interest; The NWDAF of claim 14, wherein the AF profile is registered with a network repository function (NRF).

16. The controller further controlling the transceiver to transmit an NRF discovery request to the NRF; The NWDAF of claim 15, configured to control the transceiver to receive from the NRF an NRF discovery response including an AF profile of the AF matching the NRF discovery request.

17. The controller further determining a list of subscription permanent identifiers (SUPIs) from at least one of an access and mobility management function (AMF) and a session management function (SMF) based on the analysis filter information; The NWDAF of claim 14, configured to control the transceiver to send to the AF a subscription request for the determined list of UEs associated with the list of SUPIs.

18. An application function (AF) for user equipment (UE) data collection, comprising: A transceiver; a controller connected to the transceiver; The controller and controlling the transceiver to receive, from a network data analytics function (NWDAF), a request for subscription to the AF for collecting the UE data for analysis based on an AF profile of the AF, wherein the AF profile includes at least one event identifier (ID) and at least one supported application ID supported by the AF; collecting UE data from the UE based on the subscription; processing the UE data based on an agreed upon policy for the UE data collection configured in the AF; configured to control the transceiver to send a notification regarding the processed UE data to the NWDAF; The UE data collection is performed by a user plane connection between the AF and the UE; a UE Internet Protocol (IP) address used for the user plane connection; The AF, wherein the subscription request is associated with analysis filter information, and the analysis filter information is associated with at least one application ID.

19. The AF of claim 18, wherein the AF profile is registered with a network repository function (NRF).

20. The controller further configured to establish the user plane connection to the UE; Establishing the user plane connection comprises: locating a session management function (SMF) from a unified data repository (UDR) based on a subscription permanent identifier (SUPI) retrieved from an access and mobility management function (AMF); Controlling the transceiver to send, to the SMF, a subscription request to an event exposure function of the SMF, including an event reporting target set in the SUPI, based on the list of SUPIs retrieved from the AMF; Controlling the transceiver to receive a UE IP address corresponding to the UE from the SMF; further comprising mapping the UE IP address to the SUPI; the list of SUPIs is determined based on the analysis filter information; 20. The AF of claim 18, wherein the analysis filter information relates to an area of ​​interest.

Images