KR20200129054A - Method and system for providing communication analysis of user equipment based on network data analysis - Google Patents

Abstract

Disclosed are a method and a system for providing communication analysis of a user device based on network data analysis. The method for providing communication analysis analyzes network data collected from a network function device to provide communication statistics and communication prediction of the user device as an analysis result. Therefore, a communication pattern of a user for a specific area can be predicted.

Description

Method and system for providing communication analysis of user equipment based on network data analysis {METHOD AND SYSTEM FOR PROVIDING COMMUNICATION ANALYSIS OF USER EQUIPMENT BASED ON NETWORK DATA ANALYSIS}

The present invention relates to a method and system for providing communication analysis of a user based on network data analysis.

User terminals use various types of communication services through a network. User terminals may or may not be satisfied with the communication service by using the communication service. For this, the network needs to predict the pattern of how the user terminal uses the communication service when the user terminal uses the communication service.

The present invention provides a method of predicting a user's communication pattern for a specific area.

A method for providing communication analysis according to an embodiment of the present invention includes the steps of: receiving, by an NWDAF device, a Nnwdaf_AnalyticsSubscription_Subscribe service operation from an NF device; Invoking an Nsmf_EventExposure_Subscribe service operation to the SMF device by the NWDAF device; Receiving, by the NWDAF device, an Nsmf_EventExposure_Notify service operation from the SMF device; Invoking, by the NWDAF device, a Namf_EventExposure_Subscribe service operation to the AMF device; Receiving, by the NWDAF device, a Namf_EventExposure_Notify service operation from the AMF device; Deriving, by the NWDAF device, a user terminal communication analysis in the form of user terminal communication statistics or user terminal communication prediction; And providing, by the NWDAF device, the Nnwdaf_AnalyticsInfo_Request response service operation or the Nnwdaf_AnalyticsSubscription_Notify service operation to the NF device for user terminal communication analysis.

The Nnwdaf_AnalyticsSubscription_Subscribe service operation includes an Analytics ID set as UE communication analytics, a Target of Analytics Reporting set as SUPI(s), an application ID, and a region of interest. It can include an Analytics Filter set to (Area of Interest).

The Naf_EventExposure_Subscribe service operation may include an event ID, an external user terminal ID, an application ID, and a region of interest.

The NWDAF device may subscribe to application-specific communication information identified by an application ID from AF devices for a user terminal.

The NWDAF device may invoke an smf_EventExposure_Subscribe service operation including an event ID, SUPI, application ID, and ROI to the SMF device.

The NWDAF device may call a Namf_EventExposure_Request service operation including an event ID and SUPI to the AMF device.

The NWDAF device may retrieve the type assignment code from the AMF device to provide the requested analysis to the NF device.

The user terminal communication statistics may include at least one of a user terminal group ID or a user terminal ID, a user terminal communication, a periodic communication indicator, a periodic time, a start time, a duration time, a traffic characteristic, a traffic volume, and a ratio.

The user terminal communication prediction may include at least one of a user terminal group ID or a user terminal ID, user terminal communication, periodic communication indicator, periodic time, start time, duration time, traffic characteristic, traffic volume, reliability, and ratio. .

According to an embodiment of the present invention The communication analysis providing system includes a processor, wherein the processor, the NWDAF device receives the Nnwdaf_AnalyticsSubscription_Subscribe service operation from the NF device, the NWDAF device calls the Nsmf_EventExposure_Subscribe service operation to the SMF device, and the NWDAF device performs the Nsmf_EventExposure_Notify service operation from the SMF device. When the call is received, the NWDAF device calls the Namf_EventExposure_Subscribe service operation to the AMF device, the NWDAF device receives the Namf_EventExposure_Notify service operation from the AMF device, and the NWDAF device derives user terminal communication analysis in the form of user terminal communication statistics or user terminal communication prediction. In addition, the NWDAF device may provide the Nnwdaf_AnalyticsInfo_Request response service operation or the Nnwdaf_AnalyticsSubscription_Notify service operation to the NF device for user terminal communication analysis.

The Nnwdaf_AnalyticsSubscription_Subscribe service operation includes an Analytics ID set as UE communication analytics, a Target of Analytics Reporting set as SUPI(s), an application ID, and a region of interest. It can include an Analytics Filter set to (Area of Interest).

The Naf_EventExposure_Subscribe service operation may include an event ID, an external user terminal ID, an application ID, and a region of interest.

The NWDAF device may subscribe to application-specific communication information identified by an application ID from AF devices for a user terminal.

The NWDAF device may invoke an smf_EventExposure_Subscribe service operation including an event ID, SUPI, application ID, and ROI to the SMF device.

The NWDAF device may call a Namf_EventExposure_Request service operation including an event ID and SUPI to the AMF device.

The NWDAF device may retrieve the type assignment code from the AMF device to provide the requested analysis to the NF device.

The user terminal communication statistics may include at least one of a user terminal group ID or a user terminal ID, a user terminal communication, a periodic communication indicator, a periodic time, a start time, a duration time, a traffic characteristic, a traffic volume, and a ratio.

The user terminal communication prediction may include at least one of a user terminal group ID or a user terminal ID, user terminal communication, periodic communication indicator, periodic time, start time, duration time, traffic characteristic, traffic volume, reliability, and ratio. .

According to an embodiment of the present invention, a user's communication pattern for a specific area can be predicted.

1 is a diagram illustrating a relationship between an NWDAF device and an NF device according to an embodiment of the present invention.
2 is a diagram illustrating a subscription and cancellation of a subscription for network data analysis according to an embodiment of the present invention.
3 is a diagram illustrating a request for network data analysis according to an embodiment of the present invention.
4 is a diagram illustrating a subscription and cancellation of an event exposure according to an embodiment of the present invention.
5 is a diagram illustrating a process of providing communication analysis of a user terminal according to an embodiment of the present invention.
6 is a diagram illustrating network function services provided by an NWDAF device according to an embodiment of the present invention.
7 is a diagram illustrating network function services consumed by an NWDAF device for data collection according to an embodiment of the present invention.
8 is a diagram illustrating service data related to user terminal communication according to an embodiment of the present invention.
9 is a diagram illustrating user terminal communication statistics according to an embodiment of the present invention.
10 is a diagram illustrating user terminal communication prediction according to an embodiment of the present invention.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, the scope of the patent application is not limited or limited by these embodiments. The same reference numerals in each drawing indicate the same members.

Various changes may be made to the embodiments described below. The embodiments described below are not intended to be limited to the embodiments, and should be understood to include all changes, equivalents, and substitutes thereto.

Terms such as first or second may be used to describe various components, but these terms should be understood only for the purpose of distinguishing one component from other components. For example, a first component may be referred to as a second component, and similarly, a second component may be referred to as a first component.

The terms used in the examples are used only to describe specific embodiments, and are not intended to limit the embodiments. Singular expressions include plural expressions unless the context clearly indicates otherwise. In the present specification, terms such as "comprise" or "have" are intended to designate the presence of features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, but one or more other features. It is to be understood that the presence or addition of elements or numbers, steps, actions, components, parts, or combinations thereof, does not preclude in advance.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiment belongs. Terms as defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and should not be interpreted as an ideal or excessively formal meaning unless explicitly defined in this application. Does not.

In addition, in the description with reference to the accompanying drawings, the same reference numerals are assigned to the same components regardless of the reference numerals, and redundant descriptions thereof will be omitted. In describing the embodiments, when it is determined that a detailed description of related known technologies may unnecessarily obscure the subject matter of the embodiments, the detailed description thereof will be omitted.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating a relationship between an NWDAF device and an NF device according to an embodiment of the present invention.

The Network Data Analytic Function (NWDAF) device 101 represents an operator managed network analytics logical function. NWDAF devices may include the following functions.

-Function to collect data from network function (NF) devices 102 and application function (AF) devices

-Ability to collect data from OAM (Operations, Administration and Maintenance) devices

-NWDAF service registration and metadata exposure function to NF devices 102 and AF devices

-Function to support analytics information provisioning to NF devices 102 and AF devices

<Reference Architecture for Data Analytics>

The NWDAF device 101 uses a mechanism and interface of a 5G core network and an OAM (Operations, administration and management) device. The NWDAF device 101 interacts with different entities for different purposes.

-AMF (Access and Mobility Management Function) device, SMF (Session Management Function) device, PCF (Policy Control Function) device, UDM (Unified Data Management) device, AF (Application Function) device (direct or NEF (Network Exposure Function)) Device) and event subscriptions provided by OAM devices.

-Retrieving information for information storage (e.g. UDR via UDM for subscription related information)

-Provide analysis needs for consumers

A single instance or multiple instances of the NWDAF device 101 may be deployed in a Public Land Mobile Network (PLMN). If multiple NWDAF instances are deployed, the architecture can support the NWDAF device 101 as a central NF device 102, a collection of distributed NF devices 102, or a combination thereof.

When there are multiple NWDAF devices 101, not all of the NWDAF devices 101 need to provide the same type of analysis result. Some of the NWDAF devices 101 may be specialized to provide a specific type of analysis. The Analytics ID information element is used to identify the type of analysis generated by the NWDAF device 101.

-NWDAF instance can be deployed with NF devices 102 of 5GS.

Referring to FIG. 1, an NWDAF device 101 based on a non-roaming architecture is shown. Through the 5G system architecture, the NWDAF device 101 can collect data from all NF (Network Function) devices. The NWDAF device 101 may belong to the same PLMN in which a network function for notifying data exists.

The Nnf interface is defined in order for the NWDAF device 101 to request a subscription for data delivery for a specific context, cancel the subscription for data delivery, and request a specific report of data for a specific context. The 5G system allows the NWDAF device 101 to call existing OAM services to retrieve management data from the OAM device.

The 5G system architecture allows NF devices in the 5G core network to request network analysis information from the NWDAF device 101. The NWDAF device 101 and the NF devices of the 5G core network consuming the analysis information belong to the same PLMN.

<Description of the NWDAF device 101>

The NWDAF device 101 provides analysis results to NF (Network Function) devices and OAM devices of a 5G core network. The analysis information may be statistical information or prediction information of past events. Other NWDAF instances exist in the 5G core network and can be specialized according to the analysis category. The function of the NWDAF instance is described in the NWDAF profile stored in the Network Repository Function (NRF) device.

To support NF devices 102, consumers of analytics, with discovery of an NWDAF instance that can provide a specific type of analytics, each NWDAF instance has a list of Analytic IDs and NF that support registration with NEF devices. Provides other NRF registration elements of the profile. Other NF devices 102 requesting the discovery of an NWDAF instance that provides support for a specific type of analysis may contact the NRF device and may include Analytic IDs that identify the desired type of analysis.

Consumers, i.e. NF devices 102 and OAM devices in the 5G core network, decide how to use the data analysis provided by the NWDAF device 101. The interaction between the NF devices 102 of the 5G core network and the NWDAF device 101 proceeds within the PLMN. The NWDAF device 101 does not have knowledge of the NF application logic. The NWDAF device 101 can use subscription data only for statistical purposes.

<NWDAF discovery and selection>

The NWDAF service consumer can select the NWDAF that supports the requested analysis information using the NWDAF discovery principle.

<NWDAF discovery and discovery>

Multiple instances of the NWDAF device 101 are deployed in the network. If the NWDAF information is not available by other means (eg, configured locally on the service consumer NF device 102 devices), the service consumer NF device 102 devices use the NRF device to discover NWDAF instances. The NWDAF selection function in service consumer NF device 102 devices selects an NWDAF instance based on the available NWDAF instances.

The following factors are considered by the service consumer NF device 102 device for NWDAF selection.

-S-NSSAI (Single Network Slice Selection Assistance Information)

-Analytics ID(s).

-NWDAF Serving Area information (e.g., a list of TAIs (Tracking Area Identifiers) related to analysis generated by the NWDAF device 101)

<UE related analytics>

The following describes user terminal related analyzes that may be provided by the NWDAF device.

-User terminal mobility analysis

-User terminal communication analysis

-Expected user terminal behavior parameters related to network data analysis

-Non-ideal behavior related to network data analysis

The NWDAF service consumer requests these analyzes individually or in combination. For example, an NWDAF service consumer may learn an expected user terminal behavior parameter for a group of user terminals or a specific user terminal by requesting an analysis of user terminal mobility and user terminal communication from the NWDAF device.

The expected use of such an analysis is that the AMF device learns about the expected user terminal behavior to derive the MICO mode configuration, or AF about the expected user terminal behavior for a provisioned 5G core network with appropriate user terminal parameters. The device is learning.

<User terminal communication analysis>

In order to support optimized operations such as customized mobility management, traffic routing handling, or QoQ enhancement in the 5G core network, the NWDAF device performs data analysis on user terminal communication patterns and user plane traffic, and analyzes results (e.g. , User terminal communication statistics or prediction) can be provided to NF devices of the 5G core network.

An NWDAF device supporting user terminal communication analysis may collect a communication description for each application from an AF device. If the consumer NF device provides the application ID, the NWDAF device may consider data from the AF device, the SMF device, and the UPF device corresponding to the application ID.

The following parameters may be included in the request of the consumer of the analysis.

(i) Target of Analytics Reporting, which is one user terminal or a group of user terminals

(ii) Analytics Filter Information

(iii) S-NSSAI

(iv) DNN

(v) the maximum number of objects

(vi) Application ID

(vii) Area of Interest

(viii) Analytics target period indicating the time period for which statistics or predictions are requested

(ix) Preferred level for accuracy of analysis (low/high)

(x) In the subscription, Notification Correlation ID and Notification Target Address

2 is a diagram illustrating a subscription and cancellation of a subscription for network data analysis according to an embodiment of the present invention.

<analytics exposure>

<analytics subscribe/analytics unsubscribe by NWDAF service consumer>

2 is an NWDAF service consumer (NF devices or OAM devices) 201 who subscribe to or unsubscribe from the NWDAF device 202 notifying analysis information using the Nnwdaf_AnalyticsSubscription service operation. Performed. In addition, this service is used by NWDAF service consumers 201 to modify existing analytics subscriptions.

1.The NWDAF service consumer 201 subscribes to analysis information or unsubscribes from analysis information by invoking the Nnwdaf_AnalyticsSubscription_Subscribe service operation or the Nnwdaf_AnalyticsSubscription_Unsubscribe service operation.

If a subscription to analysis information is received, the NWDAF device 202 may determine whether to trigger new data collection. If the service invocation relates to subscription modification, the NWDAF service consumer 201 includes an identifier (subscription correlation ID) that can be modified in the call of Nnwdaf_AnalyticsSubscription_Subscribe.

2. If the NWDAF service consumer 201 subscribes to the analysis information, the NWDAF device 202 may, based on a request from the NWDAF service consumer 201 (eg, analysis reporting parameter), the NWDAF service consumer ( 201) is notified of the analysis information by calling the Nnwdaf_AnalyticsSubscription_Notify service operation.

3 is a diagram illustrating a request for network data analysis according to an embodiment of the present invention.

<Analysis request by NWDAF service consumer>

3 is performed by an NWDAF service consumer (eg, NF devices or OAM devices) 301 requesting and obtaining NWDAF analysis information using the Nnwdaf_AnalyticsInfo service.

1. The NWDAF service consumer 301 may request analysis information from the NWDAF device 302 by calling the Nnwdaf_AnalyticsInfo_Request service operation. The parameters provided by the NWDAF service consumer 201 are described below.

When a request for analysis information is received, the NWDAF device 302 may determine whether triggering new data collection is necessary.

Input parameters included in the service operation described in FIGS. 2 to 3 are as follows.

<Contents of Analytics Exposure>

Consumers of the Nnwdaf_AnalyticsSubscription or Nnwdaf_AnalyticsInfo service operation provide the input parameters listed below.

(i) A list of Analytics ID(s):

The list of analysis IDs can identify the requested analysis.

(ii) Analytics Filter Information

The analysis filter information indicates conditions that must be performed in order to report the analysis information. The analysis filter information allows additional parameter types and sets of values to select the types of the requested analysis information. Analysis filter information is defined in the procedure.

(iii) Target of Analytics Reporting

The target of analysis reporting refers to an object for which analysis information is requested. In addition, the target of the analysis reporting indicates specific terminals, a group of terminals, or certain terminals.

(iv) Notification Target Address and Notification Correlation ID

The notification target address is for Nnwdaf_AnalyticsSubscription only. The notification target address and notification correlation ID allow correlating notifications received with the NWDAF device 302 with this subscription.

The analysis reporting information has the following parameters.

(i) Analytics Reporting Parameters

The analysis reporting parameter is for Nnwdaf_AnalyticsSubscription, and is determined for each event reporting parameter.

(ii) Reporting Thresholds

The reporting threshold is for Nnwdaf_AnalyticsSubscription and indicates a condition for the level of each requested analysis indicating when to be notified by the NWDAF device 302. Matching directions are provided as down, up and cross. If no matching direction is provided, the depot direction is cross.

(iii) Analytics target period

The analysis target period is the time interval [start..end] in the past (start time and end time in the past) or future (start time and end time in the future). In the past, the period to be analyzed is a request or subscription for statistics. The period to be analyzed in the future is a request or subscription for prediction. The time interval is expressed as the actual start time and the actual end time (eg UTC time). When the analytic statistical parameters indicate a periodic reporting mode, the time interval can be expressed as a positive or negative offset with respect to the reporting time. By setting the start time and end time to the same value, consumers of an analysis can request an analysis or subscribe to an analysis for a specific time rather than a time interval.

(iv) Preferred level of accuracy of the analytics (e.g., Low or High)

(v) time

The time is for Nnwdaf_AnalyticsInfo_Request and means the time when analysis information is needed. If the time reaches a point in time when the consumer no longer needs to wait for analysis information, the NWDAF device 302 may send an error response to the consumer.

(vi) Maximum number of objects requested by NWDAF service consumer 301

The maximum number of objects is limited to the number of objects in the analysis lists for each Nnwdaf_AnalyticsSubscription_Notify or Nnwdaf_AnalyticsInfo_Request response.

(v) Maximum number of SUPIs requested by NWDAF service consumer 301 (SUPImax)

The maximum number of SUPIs is limited to the number of SUPIs in an object. If SUPImax is not provided, the NWDAF device 302 may return all SUPIs related to the analysis object. If SUPImax is set to 0, the NWDAF device 302 does not provide any SUPI.

The NWDAF device may provide the output information listed below to the consumer through the Nnwdaf_AnalyticsSubscription service operation or the Nnwdaf_AnalyticsInfo service operation.

(i) Notification Correlation Information

Notification correlation information is for Nnwdaf_AnalyticsSubscription.

(ii) Analysis ID of the analysis information in the requested analysis target period

-In addition, the following additional information exists.

(i) Timestamp of analysis generation

The timestamp allows the consumer to decide until the received information is used. For example, NF devices may consider a notification received from an NWDAF device to be invalid for a given feedback based on a time stamp.

(ii) Valid period

The validity period defines the time period for whether the analysis information is valid.

(iii) Probability assertion

Probability assertion refers to the level of certainty or the confidence of a statistic/prediction.

4 is a diagram illustrating a subscription and cancellation of an event exposure according to an embodiment of the present invention.

<Procedures for Data Collection>

The data collection feature is based on the calculation of the network analysis, the NWDAF device 402 is a consumer of various sources (e.g., NF device 401 such as AMF device, SMF device, PCF device and AF device) or OAM device) to retrieve data.

All available data includes:

(i) OAM global NF data

(ii) NF data available in 5G core network (e.g., NRF device)

For example, behavior data related to individual user terminals (e.g., reachability of user terminals) or

Pre-computed metrics covering the population of user terminals per group of user terminals and spatial and temporal dimensions (e.g., by region over time period) (e.g., user terminals within a geographic region) Number)

(iii) Data available on the AF device

The NWDAF device uses at least one of the following services.

(i) Generic management services, Performance Management services, or Fault Supervision services provided by OAM devices to collect OAM global network function data.

(ii) Exposure services provided by NF devices to retrieve available data and other non-OAM pre-calculated metrics from NF devices.

(iii) Other network function services to collect NF Data (e.g., NRF device)

The NWDAF device 402 may acquire appropriate information to perform data collection on a user terminal or a group of user terminals.

-For Analytics ID, the NWDAF device 402 is configured with corresponding NF types and/or event IDs and/or OAM measurement types.

-The NWDAF device 402 may determine which NF instances of related NF types are serving a user terminal or a group of user terminals. Optionally, the NWDAF device may consider S-NSSAIs and an area of interest.

-The NWDAF device 402 may trigger a procedure of calling an Nnf_EventSubscribe service operation for collecting data from NF instances or subscribing to OAM services for collecting OAM measurements.

The NWDAF device 402 may perform data collection directly from the AF device or indirectly through the NEF device.

The NWDAF device 402 may discover events supported by the NF (network function) device 401.

The data collection procedure enables the NWDAF device 402 to efficiently collect data in an appropriate granularity.

When a request or subscription is received for statistics or prediction, the NWDAF device 402 cannot possess the data required to perform the service. At this time, the required data is as follows.

(i) Data from past monitoring periods. This data is needed for the provision of statistics and predictions that match the analysis target period.

(ii) Data from past long-term monitoring periods. This data is needed for model training.

In order to optimize the quality of service, the NWDAF device 402 performs the following actions.

-The NWDAF device 402 may return a probability assertion expressing confidence in the generated analysis. The prediction can be returned with zero confidence as described below. This reliability can increase in the case of a subscription.

-The value of reliability is expressed by the parameter "time when analytics information is needed", the parameter "preferred level of accuracy of the analytics" and data availability. Depends on the level or urgency being. If enough data is not collected to provide an estimate of the requested level of accuracy before the deadline, the service may return zero reliability. If not, the NWDAF device 402 waits until sufficient data has been collected before providing a response or first notification.

-To prepare for future requests for statistics from NF devices/OAM devices, the NWDAF device collects data about its own initiative (e.g., samples of user terminals (mobility)) according to the operator configuration, Returns the collected data in data storage.

The volume and maximum duration of data storage are subject to operational configuration. The NWDAF device 402 may decide to reduce the amount of data collection by prioritizing requests received from the analytics consumer, or by modifying the duration or sampling rate of the data collection.

If the NWDAF device 402 already has enough information to provide the requested analysis, the NWDAF device 402 skips the data collection step.

The data collected by the NWDAF device 402 is listed for each analysis of the input data.

The NWDAF device 402 skips the data collection step for some specific input data per requested analysis. (E.g., based on the preferred level of accuracy or the time the analysis is required, if some data is already available to the NWDAF device 402 for the requested analysis, or the NWDAF device 402 is Considering that you don't need all of them to provide all of your analysis)

<Data collection procedure from NF device>

4 is used by an NWDAF device to subscribe or unsubscribe to NF devices to notify data collection for related events using event exposure services.

1. The NWDAF device 401 may subscribe to the set of event IDs by calling the Nnf_EventExposure_Subscribe service operation, or cancel the subscription to the set of event IDs by calling the Nnf_EventExposure_Unsubscribe service operation.

2. If the NWDAF device 402 subscribes to the set of event IDs, the NF devices 401 notify the NWDAF device 402 by calling the Nnf_EventExposure_Notify service operation with an event report.

The NWDAF device 402 may use an immediate reporting flag to meet a request-response model for data collection from the NF devices 401.

<Use of exposure framework from NWDAF devices for data collection>

The NWDAF device 402 may subscribe or unsubscribe from event exposure services from NF devices that reuse the framework. This framework supports the possibility for NWDAF devices 402 to point to or call the following parameters.

(i) Event ID (Events-ID): One or more event IDs

(ii) Target of Event Reporting

It means objects targeted by the event of the target of event reporting. In a subscription, all event IDs are associated with the same target of event reporting. In the case of the NWDAF device 402, the objects may be user terminal(s), user terminal group(s), or any user terminal.

(iii) Event Filter Information

The event filter information provides event parameter types and event parameter values matching each other.

(iv) Notification Target Address and Notification Correlation ID

The notification target address and notification correlation ID allow the NWDAF device to correlate notifications and subscriptions received from the NF device with each other.

(v) Event Reporting Information

(vi) Expiry time

Notifications from NF devices or AF devices contain the top of the reported event and contain the information reported for the event.

(i) Notification Correlation Information provided by the NWDAF device 402

(ii) Target ID (if available for the event): e.g. User ID, SUPI and Generic Public Subscription Identifier (GPSI))

(iii) time stamp

5 is a diagram illustrating a process of providing communication analysis of a user terminal according to an embodiment of the present invention.

The NWDAF device can provide user terminal communication analysis in the form of statistics or predictions or both to the NF device of the 5G core network.

1. The NF device of the 5G core network can call the Nnwdaf_AnalyticsSubscription_Subscribe service operation to the NWDAF device. The Nnwdaf_AnalyticsSubscription_Subscribe service operation is the Analytics ID set to UE communication analytics, Target of Analytics Reporting set to SUPI(s), Application ID, and area of interest. of Interest) can be included.

The NF device of the 5G core network transmits an analysis request for a specific user terminal to the NWDAF device using the Nnwdaf_AnalyticsInfo service operation or the Nnwdaf_AnalyticsSubscription_Subscribe service operation. The analysis type indicated by the analysis ID is set to "user terminal communication". The target of the analysis reporting is set as a list of SUPI and SUPI, and the analysis filter may include an application ID and a region of interest.

2a-b. The NWDAF device may invoke the Naf_EventExposure_Subscribe service operation to the AF device. The Naf_EventExposure_Subscribe service operation may include an event ID, an external user terminal ID, an application ID, and a region of interest.

To provide the requested analysis, the NWDAF device may subscribe to application-specific communication information identified by the application ID from AF devices for the user terminal. The event ID may indicate a communication report for the user terminal requested by the NF device of the 5G core network in step 1. The external user terminal ID may be obtained by the NWDAF device based on the user terminal internal ID such as SUPI. In the case of an external AF device, the NEF device may convert the requested ROI into a list of geographic zone identifiers.

If the NWDAF device already has the requested analysis available or has subscribed to the AF device, this procedure can be skipped.

2c-d. The NWDAF device may invoke the Nsmf_EventExposure_Subscribe service operation to the SMF device. The Nsmf_EventExposure_Subscribe service operation may include an event ID, SUPI, application ID, and ROI.

In order to provide the requested analysis, the NWDAF device can subscribe to the user terminal's information from SMF devices.

2e-f. The NWDAF device may invoke the Namf_EventExposure_Request service operation to the AMF device. The Namf_EventExposure_Request service operation may include an event ID and SUPI.

In order to provide the requested analysis, the NWDAF device may retrieve a Type allocation code from the AMF device.

The NWDAF device may determine the SMF device serving the user terminal.

3. The NWDAF device derives the requested analysis in the form of user terminal communication statistics or predictions, or both.

4. The NWDAF device may call the Nnwdaf_AnalyticsInfo_Request response service operation or the Nnwdaf_AnalyticsSubscription_Notify service operation to the NF device of the 5G core network.

The NWDAF device may provide the user terminal communication analysis requested to the NF device using either the Nnwdaf_AnalyticsInfo_Request response service operation or the Nnwdaf_AnalyticsSubscription_Notify service operation depending on the service used in Step 1.

5-7. If the NF device subscribes to the user terminal communication analysis in step 1, and the NWDAF device creates a new analysis, the newly created analysis is provided to the NF device.

6 is a diagram illustrating network function services provided by an NWDAF device according to an embodiment of the present invention.

Network function (NF) service operations shown in FIG. 6 are as follows.

(1) Nnwdaf_AnalyticsSubscription

Nnwdaf_AnalyticsSubscription service operation enables the NF service consumers to subscribe/unsubscribe for different type of analytics from NWDAF

(1) Nnwdaf_AnalyticsSubscription

The Nnwdaf_AnalyticsSubscription service operation allows an NF service consumer (Network Function Service Consumer) to subscribe or unsubscribe to different types of analytics from an NWDAF device.

(2) Nnwdaf_AnalyticsInfo

Nnwdaf_AnalyticsInfo service operation enables the NF service consumers to request and get different type of analytics information from NWDAF.

(2) Nnwdaf_AnalyticsInfo

The Nnwdaf_AnalyticsInfo service operation allows NF service consumers to request and obtain different types of analysis information from NWDAF devices.

7 is a diagram illustrating network function services consumed by an NWDAF device for data collection according to an embodiment of the present invention.

<Network Exposure>

Network capability exposure may include:

-Exposure of network events not only externally but also internally to NF devices in the core network

-Exposure of function provisioning towards external functions

-Exposure of policies and charging functions towards external functions

-Exposure of core network internal functions for analysis

-Exposure of analysis to outside parties

-Retrieve data from external parties by NWDAF devices

When subscribing to event reporting, the service consumer NF device provides:

(i) One or more event IDs (Event ID)

The event ID identifies the type of an event subscribed to, for example, to release a Protocol Data Unit (PDU) session, or the mobility of a user terminal (UE) outside an area of interest.

(ii) Event Filter Information

The event filter information is provided by matching an event parameter type and an event parameter value in order to satisfy a condition for notifying a subscribed event ID. The event parameter type may be an area of interest, and the event parameter value may be a list of tracking areas (TA). The event filter depends on the event ID. Event filter information is provided for each subscribed event ID. The event ID is associated with different event filter information.

(iii) Event Reporting Information

Event reporting information is associated with unique event reporting information in all event IDs within a subscription.

(iv) Target of Event Reporting

This refers to a specific user terminal, or PDU session, a group of user terminals, or some user terminal. All event IDs within a subscription are associated with the same target of event reporting.

(v) Notification Target Address and Notification Correlation ID

Notification Target Address and Notification Correlation ID allows the NF device receiving the event to correlate the notification received from the event provider with the subscription. The subscription is associated with a specific notification target address. NF devices with different NF consumers When subscribing to an NF producer on behalf of a service consumer, the service consumer NF device is notified for the notification target address and notification correlation ID of the other NF device for the event ID that should be notified directly to other NF devices and the subscription change associated with event notification Include the target address and notification correlation ID.

(vi) Expiry time

Expiration time refers to the amount of time you want the subscription to remain active. The service consumer NF device proposes an expiration time and provides it to the NF service producer. Based on the operator policy, the NF service producer can decide whether the subscription can be terminated. If the subscription can be terminated, the NF service producer determines the expiration time and provides it as a response to the service consumer NF device. If the event subscription is about to expire based on the expiration time and the service consumer NF device wants to continue to receive notifications, the service consumer NF device updates the subscription to the NF service producer to extend the expiration time. When the expiration time associated with the subscription has been reached, the subscription becomes invalid at the NF service producer. If you want the service consumer NF device to keep receiving notifications, you must create a new subscription with the NF service producer.

When the subscription is approved by the event provider NF device, the service consumer NF device receives an identifier (subscription correlation ID) capable of additionally managing (modifying, deleting) the subscription from the event provider NF device.

The notification correlation ID is assigned by the service consumer NF device that subscribes to the event reporting, and the subscription correlation ID is assigned by the NF device notifying that the event is satisfied. Although the notification correlation ID and the subscription correlation ID are optimized to discover a subscription associated with a context in each NF device and are expected to be different, the notification correlation ID and the subscription correlation ID may be assigned the same value.

The service consumer NF device uses the action on subscription modification to add or delete event IDs to the subscription, or to modify event filter information. By providing an event filter, events are subscribed to by the service consumer NF device. The contents of the event reporting information are described in Table 1 according to the existence requirements of each information element.

[Table 1]

<Data collection from NF device>

Data collection from the NF device can be used by the NWDAF device to subscribe or unsubscribe to any Network Function (NF) devices that will be notified of data for a set of events.

Data collection from the NF device is based on the service of the AMF device, SMF device, UDM device, PCF device, NRF device, and AF device (if possible via NEF device).

-Event Exposure Service is provided by each NF device.

-Other NF services ("Nnrf_NFDiscovery and Nnrf_NFManagement" in NRF device)

Search behavior data (e.g., UE reachability) for individual UEs or groups of user terminals, and search for global user terminal information (e.g., geographical area). The data collection service is used directly to search for the number of user terminals that exist.

The NWDAF device can collect some of the UPF input data to derive analyses.

When an NWDAF device receives a request addressed to an Internal Group ID from a consumer, the NWDAF device is the network function of several 5G core networks such as AMF devices, SMF devices, UDM devices, PCF devices, NEF/AF devices, etc. (NF) You need to start collecting data from devices. The NWDAF device can first find an instance of the NF devices of the 5G core network required by sending a query to the NRF device.

To discover a UDM device, the NWDAF device can query the NRF device for the internal group ID as the target of the query. In order to discover AMF devices, SMF devices, PCF devices, NEF devices and AF devices, the NWDAF device needs to discover all instances in the network by using the Nnrf_NFDiscovery service.

It can be assumed that all members of the inner group ID belong to the same UDM group ID. The NWDAF device may select a UDM instance that supports the UDM group ID of the internal group ID.

Then, if data needs to be collected from the AMF device, SMF device, UDM device and PCF device, the NWDAF device starts collecting data with the internal group ID as the target (e.g., a given type of network function All instances subscribe to event exposure). Subscribing to all instances of the required source of event exposure deals with the mobility of user terminals across AMF devices or initiating new PDU sessions with other assigned SMF devices.

By collecting data from the AMF device and the SMF device, the NWDAF device may collect data directly from the AMF device or SMF device, or indirectly through the UDM device.

The NEF instance serving the specific network slice and/or the application of the user terminal should be determined using the NRF device or additional request parameters.

If the NWDAF device needs to collect data from an AF device located outside the operator's domain, the NWDAF device may contact the NEF device with SUPI or an internal group ID as a target for data collection. The NEF device can convert SUPI to GPSI or convert the inner group ID to the outer group ID by querying the UDM device before contacting the AF device.

<NEF device>

The NEF device can perform the following functions.

-Exposure of analytics function

NWDAF analysis is securely exposed by NEF (Network Exposure Function) devices for external parties.

-Ability to retrieve data from external party by NWDAF device

Data provided by external parties is collected by the NWDAF device through the NEF device for analysis generation. The NEF device handles and forwards requests and notifications between the NWDAF device and the AF device.

<Network Repository Function (NRF) Device>

The NRF device supports the following functions.

(i) If available on the NWDAF device, Supported Analytics ID(s), NWDAF Serving Area information (e.g., TAI for which the NWDAF device can provide analysis) List)

The NWDAF serving area information is common to all of the supported analysis IDs.

(ii) For NEF devices, event IDs supported by AF devices

(iii) For NEF devices, application IDs supported by AF devices

Event IDs and application IDs can be used when the NEF device exposes AF information for analysis purposes.

<Data collection from AF device>

An NF device that needs to collect data from an AF device can subscribe to or unsubscribe from notifications about data collected directly from the AF device or indirectly through the NEF device.

Data collected from the AF device can be used as input for analysis of the NWDAF device.

The details of the data collected from the AF device as well as the interaction between the NEF device, the AF device and the NWDAF devices are described below.

8 is a diagram illustrating service data related to user terminal communication according to an embodiment of the present invention.

<Input data>

An NWDAF device that supports data analysis for user terminal communication may collect communication information for user terminals in a 5G core network. The specific information collected by the NWDAF device includes service data related to user terminal communication.

Depending on the requested level of accuracy, data collection is provided as samples (e.g., a spatial subset of user terminals or a group of user terminals, a temporal subset of user terminal communication information). subsets))

The application ID is incidental. If the application ID is omitted, the collected user terminal communication information can be used for all applications for the user terminal.

(i) User terminal ID (UE ID)

In the case of an AF device, a user terminal ID (UE ID) means an SMF device, a GPSI, or a SUPI for an external user terminal ID.

(ii) Group ID

In the case of the SMF device, when the internal group ID is available, and in the case of the AF device, the external group ID is available, the group ID may be used to identify the user terminal group.

(iii) S-NSSAI

S-NSSAI is information for identifying a network slice.

(iv) DNN

DNN is a data network name of an area that provides PDU connection service.

(v) Application ID

The application ID is for identifying an application that provides service data.

(vi) Expected UE Behavior parameters

The expected user terminal behavior parameter is the same as the expected user terminal behavior parameter defined in other areas.

(vii) User terminal communication (UE communication)

User terminal communication is an application-specific communication description.

(viii) Communication start

Communication start is the timestamp at which communication begins.

(ix) Communication stop

Communication end is a timestamp at which communication ends.

(x) Uplink data rate (UL data rate)

The uplink data rate relates to communication.

(xi) Downlink data rate

The downlink data rate relates to communication.

(xii) Traffic volume

Traffic volume is about communication.

(xiii) Type Allocation code (TAC)

The type assignment code represents the terminal model and vendor information of the user terminal. User terminals having the same TAC have similar communication behavior.

A user terminal having the same TAC but different communication behavior from other user terminals may be an abnormal user terminal.

9 to 10 below describe output analytics for user terminal communication derived by the NWDAF device.

<Output Analytics>

The NWDAF device supporting user terminal communication analysis can provide the analysis result to the consumer NF device. The analysis results provided by the NWDAF device may include user terminal communication statistics and user terminal communication predictions.

Note: When the target of the analysis reporting is an individual user terminal, the ID (eg, SUPI) of any one user terminal may be included. Then, the NWDAF device may provide analysis communication results (eg, a list of communication time slots) to NF service consumers for the user terminal.

The results of user terminal groups address the group globally. The ratio is the proportion of user terminals in a group for a given communication at a given time and interval.

The number of user terminal communication entries (1 to max) is limited by the maximum number of objects provided as input parameters. Communication is provided by a time sequence that can overlap.

Depending on the list size limit, the least probable communications may not be provided for a given analysis target period.

9 is a diagram illustrating user terminal communication statistics according to an embodiment of the present invention.

(i) User terminal group ID or user terminal ID (UE group ID or UE ID)

The user terminal group ID or user terminal ID identifies a user terminal or a group of user terminals. The user terminal group ID or the user terminal ID may be an internal group ID or SUPI.

(ii) UE communications (1..max)

User terminal communication is a list of communication time slots.

(iii) Periodic communication indicator

The periodic communication indicator identifies whether the user terminal communicates periodically or not.

(iv) Periodic time

Periodic time, if periodic, is the interval time of periodic communication (average and deviation).

For example, every 1 hour

(v) Start Time

Start time is the observed start time (mean and deviation).

(vi) Duration Time

The duration is the duration of the communication (average and deviation).

(vii) Traffic characterization

Traffic characteristics are S-NSSAI, DNN, ports and other useful information.

(viii) Traffic volume

Traffic volume is the volume (average and deviation) for the uplink or downlink.

(ix) ratio

The ratio means the percentage of user terminals in the group.

10 is a diagram illustrating user terminal communication prediction according to an embodiment of the present invention.

(i) User terminal group ID or user terminal ID (UE group ID or UE ID)

The user terminal group ID or user terminal ID identifies a user terminal or a group of user terminals. The user terminal group ID or the user terminal ID may be an internal group ID or SUPI.

(ii) UE communications (1..max)

User terminal communication is a list of communication time slots.

(iii) Periodic communication indicator

The periodic communication indicator identifies whether the user terminal communicates periodically or not.

(iv) Periodic time

Periodic time, if periodic, is the interval time of periodic communication (average and deviation).

For example, every 1 hour

(v) Start Time

The start time is the predicted start time (mean and deviation).

(vi) Duration Time

The duration is the duration of the communication (average and deviation).

(vii) Traffic characterization

Traffic characteristics are S-NSSAI, DNN, ports and other useful information.

(viii) Traffic volume

Traffic volume is the volume (average and deviation) for the uplink or downlink.

(ix) Confidence

Reliability means the reliability of the prediction.

(x) ratio

The ratio means the percentage of user terminals in the group.

When the target of the analysis reporting includes an individual user terminal or any one user terminal ID (e.g., SUPI), the NWDAF device sends the analysis communication result (a list of predicted communication time slots) for the user terminal to NF service consumers. Can be provided to.

Meanwhile, the method according to the present invention is written as a program that can be executed on a computer and can be implemented in various recording media such as magnetic storage media, optical reading media, and digital storage media.

Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or combinations thereof. Implementations may include a data processing device, e.g., a programmable processor, a computer, or a computer program product, i.e. an information carrier, e.g., machine-readable storage It can be implemented as a computer program tangibly embodied in an apparatus (computer readable medium) or a radio signal. Computer programs, such as the computer program(s) described above, may be recorded in any type of programming language including compiled or interpreted languages, and as a standalone program or in a module, component, subroutine, or computing environment. It can be deployed in any form, including as other units suitable for the use of. A computer program can be deployed to be processed on one computer or multiple computers at one site, or to be distributed across multiple sites and interconnected by a communication network.

Processors suitable for processing a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. In general, the processor will receive instructions and data from read-only memory or random access memory or both. Elements of the computer may include at least one processor that executes instructions and one or more memory devices that store instructions and data. In general, a computer may include one or more mass storage devices, such as magnetic, magnetic-optical disks, or optical disks, to store data, receive data from, transmit data to, or both It may be combined so as to be. Information carriers suitable for embodying computer program instructions and data are, for example, semiconductor memory devices, for example, magnetic media such as hard disks, floppy disks and magnetic tapes, Compact Disk Read Only Memory (CD-ROM). ), Optical Media such as DVD (Digital Video Disk), Magnetic-Optical Media such as Floptical Disk, ROM (Read Only Memory), RAM (RAM) , Random Access Memory), flash memory, EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), and the like. The processor and memory may be supplemented by or included in a special purpose logic circuit structure.

Further, the computer-readable medium may be any available medium that can be accessed by a computer, and may include both a computer storage medium and a transmission medium.

While this specification includes details of a number of specific implementations, these should not be construed as limiting to the scope of any invention or claim, but rather as a description of features that may be peculiar to a particular embodiment of a particular invention. It must be understood. Certain features described herein in the context of separate embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination. Furthermore, although features operate in a particular combination and may be initially described as so claimed, one or more features from a claimed combination may in some cases be excluded from the combination, and the claimed combination may be a subcombination. Or sub-combination variations.

Likewise, although operations are depicted in the drawings in a specific order, it should not be understood that such operations must be performed in that particular order or sequential order shown, or that all illustrated operations must be performed in order to obtain a desired result. In certain cases, multitasking and parallel processing can be advantageous. In addition, separation of the various device components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and the program components and devices described are generally integrated together into a single software product or packaged in multiple software products. You should understand that you can.

On the other hand, the embodiments of the present invention disclosed in the specification and drawings are only presented specific examples to aid understanding, and are not intended to limit the scope of the present invention. In addition to the embodiments disclosed herein, it is apparent to those of ordinary skill in the art that other modified examples based on the technical idea of the present invention may be implemented.

Claims (16)

Receiving, by the NWDAF device, a Nnwdaf_AnalyticsSubscription_Subscribe service operation from the NF device;
Calling the Nsmf_EventExposure_Subscribe service operation to the SMF device by the NWDAF device;
Receiving, by the NWDAF device, an Nsmf_EventExposure_Notify service operation from the SMF device;
Invoking, by the NWDAF device, a Namf_EventExposure_Subscribe service operation to the AMF device;
Receiving, by the NWDAF device, a Namf_EventExposure_Notify service operation from the AMF device;
Deriving, by the NWDAF device, a user terminal communication analysis in the form of user terminal communication statistics or user terminal communication prediction;
NWDAF device providing the Nnwdaf_AnalyticsInfo_Request response service operation or Nnwdaf_AnalyticsSubscription_Notify service operation to the NF device for user terminal communication analysis
Including,
The Nnwdaf_AnalyticsSubscription_Subscribe service operation,
User terminal communication analytics (Analytics ID) set to UE communication analytics, Target of Analytics Reporting set to SUPI(s), Application ID (Application ID) and Area of Interest Communication analysis providing method including set Analytics Filter The method of claim 1,
The Naf_EventExposure_Subscribe service operation,
Communication analysis providing method including event ID, external user terminal ID, application ID, and region of interest. The method of claim 1,
The NWDAF device,
A communication analysis providing method for subscribing communication information for each application identified by an application ID from AF devices for a user terminal. The method of claim 1,
The NWDAF device,
Communication analysis providing method for calling smf_EventExposure_Subscribe service operation including event ID, SUPI, application ID, and region of interest to an SMF device. The method of claim 1,
The NWDAF device,
A method for providing communication analysis that calls the Namf_EventExposure_Request service operation including an event ID and SUPI to an AMF device. The method of claim 1,
The NWDAF device, a communication analysis providing method for retrieving a type assignment code from the AMF device to provide the requested analysis to the NF device. The method of claim 1,
The user terminal communication statistics,
A method for providing communication analysis including at least one of a user terminal group ID or user terminal ID, user terminal communication, periodic communication indicator, periodic time, start time, duration time, traffic characteristic, traffic volume, and ratio. The method of claim 1,
The user terminal communication prediction,
User terminal group ID or user terminal ID, user terminal communication, periodic communication indicator, periodic time, start time, duration, traffic characteristic, traffic volume, reliability, and a communication analysis providing method comprising at least one of a ratio. In the communication analysis providing system,
The communication analysis providing system includes a processor,
The processor,
The NWDAF device receives the Nnwdaf_AnalyticsSubscription_Subscribe service operation from the NF device,
The NWDAF device calls the Nsmf_EventExposure_Subscribe service operation to the SMF device,
The NWDAF device receives the Nsmf_EventExposure_Notify service operation from the SMF device,
The NWDAF device calls the Namf_EventExposure_Subscribe service operation to the AMF device,
The NWDAF device receives the Namf_EventExposure_Notify service operation from the AMF device,
The NWDAF device derives user terminal communication analysis in the form of user terminal communication statistics or user terminal communication prediction,
The NWDAF device provides the Nnwdaf_AnalyticsInfo_Request response service operation or the Nnwdaf_AnalyticsSubscription_Notify service operation to the NF device for user terminal communication analysis,
The Nnwdaf_AnalyticsSubscription_Subscribe service operation,
User terminal communication analytics (Analytics ID) set to UE communication analytics, Target of Analytics Reporting set to SUPI(s), Application ID (Application ID) and Area of Interest Communication analysis providing system including set Analytics Filter. The method of claim 9,
The Naf_EventExposure_Subscribe service operation,
Communication analysis providing system including event ID, external user terminal ID, application ID, and region of interest. The method of claim 9,
The NWDAF device,
Communication analysis providing system for subscribing communication information for each application identified by an application ID from AF devices for a user terminal. The method of claim 9,
The NWDAF device,
Communication analysis providing system that calls the smf_EventExposure_Subscribe service operation including event ID, SUPI, application ID, and region of interest to the SMF device. The method of claim 9,
The NWDAF device,
Communication analysis providing system that calls Namf_EventExposure_Request service operation including event ID and SUPI to AMF device. The method of claim 9,
The NWDAF device is a communication analysis providing system for retrieving a type assignment code from the AMF device to provide the requested analysis to the NF device. The method of claim 9,
The user terminal communication statistics,
A communication analysis providing system including at least one of a user terminal group ID or user terminal ID, user terminal communication, periodic communication indicator, periodic time, start time, duration time, traffic characteristic, traffic volume, and ratio. The method of claim 9,
The user terminal communication prediction,
A communication analysis providing system including at least one of a user terminal group ID or user terminal ID, user terminal communication, periodic communication indicator, periodic time, start time, duration time, traffic characteristic, traffic volume, reliability, and ratio.

Images