KR20210089108A - Method and apparatus for collecting network data - Google Patents

Abstract

A method for collecting network data and an NWDAF are provided, which include the steps of: sending a network open subscription request message including event reporting granularity parameters to an NF; receiving the data set determined by the NF based on the event reporting granularity parameter from the NF through an event open notification message in at least one reporting cycle; and performing network data analysis using the received data set. Accordingly, the efficiency of data collection can be improved, and real-time data collection can be improved.

Description

Network data collection method and device {METHOD AND APPARATUS FOR COLLECTING NETWORK DATA}

The present disclosure relates to a method and apparatus for collecting network data through approximation.

The Network Data Analytics Function (NWDAF) of the 5G mobile communication system collects raw data of each network function and application function to make it big data, and processes big data to provide network analysis information to network functions and It can be provided to application functions. However, too much raw data is collected in each network function and application function of the mobile communication system, and the frequency of generating raw data is too high, so that the load generated by data collection is very large in reality.

One embodiment provides a method for the NWDAF to collect network data.

Another embodiment provides an NWDAF that collects network data.

According to one embodiment, a method is provided for a network data analytics function (NWDAF) to collect network data from a network function (NF). The network data collection method includes: sending a network open subscription request message including an event reporting granularity parameter to the NF; a data set determined by the NF based on the event reporting granularity parameter receiving at least one reporting cycle from the NF via an event open notification message, and performing network data analysis using the received data set.

In the network data collection method, the network open subscription request message further includes a reporting type parameter, and the data set may be determined by the NF based on the event reporting granularity parameter and the reporting type parameter.

In the network data collection method, the step of receiving the data set determined by the NF based on the event reporting granularity parameter in at least one reporting cycle from the NF through an event open notification message is that the reporting type causes the NF to differ from the previous notification. When instructed to report a data set representing the difference between the data including at least one of newly added data, deleted data, changed data, or data not accounted for by the event reporting granularity compared to the data in the previous notification. receiving the set from the NF.

In the network data collection method, performing network data analysis using the received data set may include recombining data and data sets in a previous notification.

The network data collection method is, after receiving the data set from the NF in at least one reporting cycle, if an event open notification message is not received from the NF in the next reporting cycle of at least one reporting cycle, based on the event reporting granularity parameter The method may further include inferring data corresponding to the next reporting cycle from the data set received in at least one reporting cycle.

In the network data collection method, event reporting granularity is applied to one event-specific parameter, and the data set may include a plurality of event-specific parameters.

In the network data collection method, the event reporting granularity parameter may be a parameter indicating a maximum allowable error for network data.

In the network data collection method, the event reporting granularity parameter may indicate a range of data that the NF can ignore when collecting network data.

When the network data to be collected by the NF in the network data collection method is data represented by an identifier, the event reporting granularity parameter may indicate a previous notification or an identifier list.

When the network data to be collected by the NF in the network data collection method is data expressed in numbers, the event reporting granularity parameter may indicate a range of changes in the network data.

According to another embodiment, a network data analytics function (NWDAF) is provided. The NWDAF includes a processor, a memory, and a communication device, and the processor executes a program contained in the memory, the network open subscription including an event reporting granularity parameter and a reporting type parameter sending a request message to the NF; receiving a data set determined by the NF based on the event reporting granularity parameter and the reporting type parameter in at least one reporting cycle from the NF via an event open notification message; and Analyze the network data using the data set.

In the NWDAF, the processor receives the data set determined by the NF based on the event reporting granularity parameter and the reporting type parameter in at least one reporting cycle from the NF through an event open notification message. If the type instructs the NF to report a data set representing a difference from the previous alert, compared to the data in the previous alert, the newly added data, deleted data, changed data, or event reporting granularity parameter The step of receiving a data set including at least one of the non-existent data from the NF may be performed.

In the NWDAF, when performing the step of performing network data analysis using the received data set, the processor may perform a step of recombining the data set with the data in the previous notification.

In the NWDAF, the processor executes the program, and after receiving the data set from the NF in at least one reporting cycle, if it does not receive an event open notification message from the NF in the next reporting cycle of at least one reporting cycle, the event reporting granule The step of inferring data corresponding to the next reporting cycle from the data set received in at least one reporting cycle based on the rity parameter may be further performed.

In the NWDAF, the event reporting granularity parameter and the reporting type parameter are applied for one event-specific parameter, and the data set may include a plurality of event-specific parameters.

In the NWDAF, the event reporting granularity parameter may be a parameter indicating the maximum allowable error for network data.

In the NWDAF, the event reporting granularity parameter may indicate a range of data that the NF can ignore when collecting network data.

When the network data to be collected by the NF in the NWDAF is data represented by an identifier, the event reporting granularity parameter may indicate a previous notification or an identifier list.

When the network data to be collected by the NF in the NWDAF is data expressed in numbers, the event reporting granularity parameter may indicate a range of changes in the network data.

According to another embodiment, a network function (NF) is provided. The network function includes a processor, a memory, and a communication device, and the processor executes a program contained in the memory to open a network including an event reporting granularity parameter and a reporting type parameter Receiving a subscription request message from a network data analytics function (NWDAF), the data set determined based on the event reporting granularity parameter and the reporting type parameter, via an event open notification message at least one reporting cycle transmitting to the NWDAF, and receiving the analysis result of the network data generated by the NWDAF from the NWDAF.

By collecting network data by NWDAF based on event reporting granularity and reporting type, the efficiency of data collection can be improved and real-time data collection can be improved.

1 is a conceptual diagram illustrating a topology of a wireless communication system according to an embodiment.
2 is a flowchart illustrating a method for an NWDAF to collect network data from a network function according to an embodiment.
3 is a block diagram illustrating NF according to an embodiment.

Hereinafter, with reference to the accompanying drawings, it will be described in detail for those of ordinary skill in the art to which the present invention pertains to easily implement the embodiments of the present disclosure. However, the present description may be embodied in various different forms and is not limited to the embodiments described herein. And in order to clearly explain the present description in the drawings, parts irrelevant to the description are omitted, and similar reference numerals are attached to similar parts throughout the specification.

Throughout the specification, when a part "includes" a certain element, it means that other elements may be further included, rather than excluding other elements, unless otherwise stated.

In the present specification, expressions described in the singular may be construed in the singular or plural unless an explicit expression such as “a” or “single” is used.

As used herein, “and/or” includes each and every combination of one or more of the recited elements.

In this specification, terms including an ordinal number such as first, second, etc. may be used to describe various elements, but the elements are not limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present disclosure, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component.

In the flowchart described with reference to the drawings in this specification, the order of operations may be changed, several operations may be merged, some operations may be divided, and specific operations may not be performed.

1 is a conceptual diagram illustrating a topology of a mobile communication system according to an embodiment.

Referring to FIG. 1 , a core network of a wireless communication system according to an embodiment includes a plurality of network functions (Network Functions, NFs), and may connect a data network (DN) and a UE.

A (Radio) Access Network ((R)AN) may represent a base station providing 3GPP connectivity and another base station or access point (AP) providing non-3GPP connectivity, such as Wi-Fi. . (R)AN may be connected to an Access and Mobility Function (AMF) through an N2 interface, and may be connected to a User Plane Function (UPF) through an N3 interface.

The AMF may be responsible for the mobility management function of the UE. The AMF may provide an access and mobility management function independently of an access technology, that is, in units of terminals. Therefore, each terminal may be basically connected to one AMF.

A session management function (SMF) may be responsible for managing a session up to the UE. When multiple sessions are created in the terminal, a different SMF may be allocated to each session.

Policy Control Function (PCF) is a function of session management, mobility management, etc. based on packet flow information to ensure Quality of Service (QoS) received from an application function (AF). policy can be determined. The policy determined in PCF is transmitted to AMF, SMF, etc., and thereafter, mobility management, session management, QoS management, etc. may be performed in each NF.

The DN may transmit a protocol data unit (PDU) to be transmitted to the UE to the UPF or may receive a PDU transmitted from the UE through the UPF. UPF and DN can be connected through the N6 interface.

UPF may be set using the control signal information generated by the SMF, and the UPF may report its status to the SMF through the N4 interface.

The terminal and the AMF may be connected through the N1 interface.

The authentication server function (AUSF) may store data for authentication of the terminal.

By collecting and analyzing various network data, NWDAF can help optimize the operation of network functions in the core network, such as AMF, SMF, and PCF. The NWDAF collects data, events, and status information from various network functions in the core network, and analyzes the collected data, events, and status information to provide various analysis information necessary for optimizing the operation of the network function. And each network function can optimize its operation by utilizing various analysis information generated by NWDAF.

2 is a flowchart illustrating a method for an NWDAF to collect network data from a network function according to an embodiment.

2 may show a data collection method of NWDAF that can improve data collection efficiency of NWDAF and support real-time data collection.

2, the NWDAF 100 is an event reporting granularity for data required for analysis (required data) and a reporting type (or reporting value flag)) can be determined (S110).

The NWDAF 100 according to an embodiment may determine a maximum allowable error for necessary data, and may set an event reporting granularity based on the determined maximum allowable error. The maximum allowable error determined by the NWDAF 100 may be a range of data that an NF reporting requested data can ignore based on event reporting granularity. In addition, the NWDAF 100 according to an embodiment may determine the reporting type in order to reduce the number of events to be collected and the signaling overhead of the core network and each network function.

The NWDAF 100 according to one embodiment provides a network exposure service provided by each network function (NF) to increase the efficiency of data collection and enable real-time (or near real-time) data collection. can utilize The request message sent by the NWDAF 100 to the NF 10 for subscription to the network open service may include parameters (event reporting granularity) that can tolerate some errors regarding the required data in the notification of each NF. have. In addition, the request message may include a parameter (reporting type) for requesting only data not delivered in the previous notification as necessary data.

Specifically, the NWDAF 100 according to an embodiment may determine the event reporting granularity and the reporting type as event reporting information of an event exposure subscribe operation. Table 1 below shows the event reporting granularity and reporting type determined by the NWDAF 100 according to an embodiment.

Event Reporting Information Parameters Explanation Event reporting granularity Indicates the maximum allowable error of data required during each event reporting cycle. Reporting type Specifies the type of alert (instructs to report only a set of data representing differences from previous alerts, or to report all necessary data in every reporting cycle).

When the event reporting granularity parameter is set by a consumer NF (eg, NWDAF) in the event open subscription procedure, an event open subscription request (Nnf_EventExposure_Subscribe request) message including the event reporting granularity parameter is received. One producer NF (producer NF) may transmit a notification including the requested data.

The producer NF may send a notification message containing the requested data to the consumer NF either periodically or every aperiodic reporting cycle during subscription of an event open.

If the change in the requested data from sending the first notification to sending the second notification to the consumer NF is within the data range determined by the event reporting granularity, the producer NF sends the requested data to the second notification It may not be sent as a message. The producer NF may check whether the change in data requested during one reporting cycle falls within the data range determined by the event reporting granularity. For example, when the requested data change is less than the data range predetermined by the event reporting granularity, or the requested data is included in the data set of a previous alert (e.g., requested data ⊂ data set of previous alerts) ), the producer NF may not deliver data to the consumer NF despite the event open subscription.

If NWDAF does not receive a notification message containing the required data during the reporting cycle, NWDAF infers the data for the current reporting cycle from the data in the notification message received in the previous reporting cycle based on the event reporting granularity. can do. For example, the NWDAF can infer data corresponding to the current reporting cycle by adding Gaussian noise (eg, zero-mean Gaussian noise) to the data included in the previous notification. In this way, the NWDAF can keep a full record of the necessary data corresponding to every reporting cycle during the subscription period, and the frequency of notification (or provision) of the necessary data can be greatly reduced.

The reporting type parameter can be set to use a different set of data than previous notifications, or it can be set to use all of the data needed.

If the reporting type parameter is set to use a different data set than the previous notification, the producer NF compares the previous notification with newly added data, or deleted data, or changed data, or A data set containing data not described in the event reporting granularity may be sent to the consumer NF through a notification message.

If the Reporting Type parameter is set to use all of the required data, the producer NF may send a notification to the consumer NF with the full set of requested data for each reporting cycle of the event notification.

When the NWDAF 100 sets the Reporting Type parameter to use a data set that represents the difference from the previous notification, the NWDAF 100 describes the newly added data, or the deleted data, or the changed data, or the event reporting granularity. A notification including data that has not been prepared may be received from the producer NF. In this case, the NWDAF 100 may re-assemble the data in the previous notification and the data in the subsequent notification. Thus, the reporting type parameter may make it possible to reduce the amount of data within each alert without loss of the required data.

Referring back to FIG. 2 , the NWDAF 100 according to an embodiment collects data of the NF 10 by calling an event open subscription request message (Nnf_EventExposure_Subscribe request) including an event reporting granularity and a reporting type as parameters. You can apply for a subscription to the NF (10) (S120). The required data is indicated by the event ID, event filter (eg, local information) included in the event open subscription request message, and the type of event reporting (eg, all UEs, UEs within a specific group, or specific UEs). can be

The NF 10 may be one of several network functions in a mobile communication system. Thereafter, the event open subscription of the NWDAF 100 may be determined by the NF 10 delivering an event open subscription response message (Nnf_EventExposure_Subscribe response) to the NWDAF 100 ( S130 ). The event reporting granularity parameter and reporting type parameter delivered to the NF 10 by the event open subscription request message may be maintained during the event open subscription of the NWDAF 100, and the duration of the event open subscription is determined by the NWDAF notification message. It may include a plurality of periodic or aperiodic reporting cycles transmitted to (100). In addition, the event reporting granularity parameter and the reporting type parameter may be updated by re-invoking the Nnf_EventExposure_Subscribe message.

The NF 10 according to an embodiment may transmit the requested data to the NWDAF 100 through the first notification after the event open subscription is started. Thereafter, the NF 10 may determine whether to transmit the requested data to the NWDAF 100 through an event open notification message (Nnf_EventExposure_Notify) based on the event reporting granularity in every reporting cycle (S140).

For example, if the change in requested data between the previous reporting cycle and the next reporting cycle is within the range determined by the event reporting granularity, the NF 10 sends an event open notification message to the NWDAF 100 in the next reporting cycle. may not be Alternatively, if the change in the requested data is larger than the range determined by the event reporting granularity, the NF 10 may transmit an event open notification message to the NWDAF 100 in the next reporting cycle.

When the NF 10 according to an embodiment sends an event open notification message to the NWDAF 100 in a reporting cycle, it transmits all requested data according to the reporting type parameter or data different from the requested data of the previous notification. set can be sent. For example, if the Reporting Type parameter indicates to report a difference from a previous notification, the NF 10 may report newly added data, or deleted data, or changed data, or data not described in the event reporting granularity. An event open notification message including the data set included may be transmitted to the NWDAF 100 . Alternatively, if the reporting type parameter indicates to report all of the requested data, the NF 10 may send all the requested data during the reporting cycle to the NWDAF 100 through an event open notification message.

Here, the first notification (eg, the first event open notification message) transmitted to the NWDAF 100 by the NF 10 may include all requested data regardless of the reporting type.

Referring to FIG. 2 , if the NWDAF 100 does not receive an event open notification message from the NF 10 in the next reporting cycle of the reporting cycle in which the data set is received, the NWDAF 100 is based on the event reporting granularity. can infer the data corresponding to the next reporting cycle from the data set in the previous notification. That is, the NWDAF 100 can infer data corresponding to the next reporting cycle from the data set received in the previous reporting cycle based on the event reporting granularity even if there is no notification message or data set received in the next reporting cycle. .

When the NWDAF 100 receives an event open notification message from the NF 10 at the end of the reporting cycle, and the event open notification message contains a data set representing the difference from the previous notification, the NWDAF 100 sends the previous notification It is possible to recombine the necessary data and data sets in (S150). The NWDAF 100 may then perform network data analysis using the inferred data set, the recombined data set, and/or any necessary data sets.

If the event ID of the event open subscription supports the collection of multiple data from the NF (ie, when the collection of multiple types of data is indicated by the event ID), the NWDAF 100 reports an event for each data. Granularity can be set. Different types of event reporting granularity can be applied to different types of data that can be collected. Table 2 below shows examples of each type of data and an example of event reporting granularity that can be applied to each type of data.

data type Examples of data Example of event reporting granularity Data represented by an identifier Application ID, filter information, location of application (eg list of DNAI), UE ID(s) (eg SUPI, GPSI), UE group ID, DNN, S-NSSAI, QFI, TAC, UE location , Exception ID, Exception trend i) Previous notice
or
ii) a list of identifiers (eg, a list of TA(s), etc.) data represented by numbers Service experience, QoS flow bit rate, QoS flow packet delay, packet transmission, packet retransmission, traffic usage report, number of UEs, mobility registration update frequency (frequent mobility) registration update), uplink data rate (UL data rate), downlink data rate (DL data rate), traffic volume (traffic volume), exception level (exception level) iii) range of change: the range x and y (eg, [-x, +y) of allowable change to the requested data in the previous notification]

In Table 2, i) If the previous notification is applied as the event reporting granularity, the producer NF may transmit a notification message only when the requested data is different from the data of the previous notification. For example, when the NWDAF event reporting granularity collects the UE ID through subscription of the Nnf_EventExposure service, the producer NF compares it with the data in the previous notification to either add a new UE ID or the UE ID disappears from the data within the previous notification. In this case, the Nnf_EventExposure_Notify message can be called.

ii) If a List of identification is applied as an event reporting granularity, the producer NF sends an Nnf_EventExposure_Notify message if the change in the requested data (eg, identifier or ID) is not included in the 'Identifier List' can be sent to the consumer NF. For example, when the NWDAF collects the UE location (Location) through subscription of the Nnf_EventExposure service and the event reporting granularity is set to a predetermined TA list, the producer NF determines that the location of the UE is the TA of the event reporting granularity. Nnf_EventExposure_Notify message can be called when changing to a TA that is not in the list.

iii) If the range of change is applied as event reporting granularity, the producer NF indicates that the requested data is out of range [(data in previous notification-x), (data in previous notification+y)) When the Nnf_EventExposure_Notify message may be sent to the consumer NF. For example, when the NWDAF collects the number of UEs within a specific area from the AMF, and the event reporting granularity is set to (x=10, y=11), the number of UEs within the specific area is the data in the previous notification. AMF may not call the Nnf_EventExposure_Notify message if it is within the range [-10, +11) for . Thereafter, the NWDAF may determine data corresponding to the corresponding event reporting cycle within the range of [Previous Data-10, Previous Data+11) through inference.

When the 'Reporting Type' is set to use a data set that differs from the previous notification, the producer NF compares the previous notification with newly added data, or deleted data, or changed data, or event reporting granularity. Data sets containing undescribed data may be reported to the consumer NF in the event notification cycle. When the 'reporting type' is set to all required data, the producer NF can report all the requested data during the subscription at every event notification cycle.

The event reporting granularity parameter and the reporting type parameter in the Nnf_EventExposure_Subscribe message may be applied for one event specific parameter. A data set including a plurality of event-specific parameters (ie, configured by a plurality of event-specific parameters) may be delivered to the NWDAF 100 through an Nnf_EventExpsoure_Notify message.

When event reporting granularity is set, the calling condition of Nnf_EventExpsoure_Notify is as follows.

- Event ID supports single data collection: Producer NF may call Nnf_EventExposure_Notify when data change is out of data scope of event reporting granularity.

- Event ID supports multiple data collection (eg service data collected from AF):

* If the event reporting granularity is set only for specific data, the producer NF may call Nnf_EventExposure_Notify when the specific data change is out of the data range of the event reporting granularity.

* When the event reporting granularity is set for different types of data, the producer NF may call Nnf_EventExposure_Notify when at least one change to the data is out of the data range of the event reporting granularity.

For example, the NWDAF collects a data set of SUPI and UE locations for a specific group of UEs from AMF (Event ID = Location Report), and the event reporting granularity is set to "previous notification" for SUPI and UE locations, respectively. If so, the producer NF indicates that at least one UE location is different from the UE location of the previous announcement or the target SUPI is due to UE mobility (eg, a new UE moves into the area or an existing UE moves out of the area). You can call Nnf_EventExposure_Notify when it changes.

When the 'reporting type' is set in the Nnf_EventExposure_Subscribe procedure, an event specific parameter that can be delivered to the NWDAF 100 by Nnf_EventExposure_Notify may include the following content.

- when 'reporting type' is set to use a data set representing the difference from previous notifications,

* If no event reporting granularity is applied to the subscription, event specific parameters include i) newly added data, ii) deleted data, and iii) changed data compared to previous notifications. If the notification contains identical data compared to the previous notification, then NWDAF may recognize that data is ii) deleted from the previous notification, and if the notification contains data that is not the same as compared to the previous notification, NWDAF may recognize the data in the notification as i) newly added data or iii) changed data.

* When event reporting granularity is applied to a subscription, event specific parameters may contain data whose change is not described within the event reporting granularity. If the notification contains identical data compared to the previous notification, NWDAF may recognize that the data in the notification is ii) deleted from the previous notification, and data that is not identical to the previous notification is included in the notification. If so, NWDAF may recognize the data in the notification as i) newly added data or iii) changed data.

- When the 'reporting type' is set to use all required data, event specific parameters can contain all required data.

As described above, the NWDAF 100 may improve the conventional Nnf_EventExposure_Subscribe procedure and Nnf_EventExposure_Notify service procedure by using the event reporting granularity parameter and the reporting type parameter.

The NWDAF 100 according to one embodiment may determine the appropriate event reporting granularity for the data needed to generate the analysis, and infer the data needed for the subscription period from the conditionally reported differences for previous notifications. can do. In addition, all NFs 10 in the mobile communication system that open an event are subject to data changes (i.e., data changes not accounted for by the event reporting granularity) outside a predetermined range of the event reporting granularity during the event reporting cycle. When there is, it is possible to provide the requested network data to the NWDAF 100 in view of the difference from the previous notification.

As described above, by collecting network data by NWDAF based on event reporting granularity and reporting type, the efficiency of data collection can be improved and real-time data collection can be improved.

3 is a block diagram illustrating NF according to an embodiment.

The NF according to an embodiment may be one of the NFs in a mobile communication system, and may be implemented in a computer system, for example, a computer-readable medium. Referring to FIG. 3 , the computer system 300 includes a processor 310 , a memory 330 , an input interface device 350 , an output interface device 360 , and a storage device 340 that communicate via a bus 370 . ) may include at least one of. Computer system 300 may also include a communication device 320 coupled to a network. The processor 310 may be a central processing unit (CPU) or a semiconductor device that executes instructions stored in the memory 330 or the storage device 340 . The memory 330 and the storage device 340 may include various types of volatile or nonvolatile storage media. For example, the memory may include read only memory (ROM) and random access memory (RAM). In the embodiment of the present disclosure, the memory may be located inside or outside the processor, and the memory may be connected to the processor through various known means. The memory is a volatile or non-volatile storage medium of various types, and for example, the memory may include a read-only memory (ROM) or a random access memory (RAM).

Accordingly, an embodiment may be implemented as a computer-implemented method, or as a non-transitory computer-readable medium having computer-executable instructions stored thereon. In one embodiment, when executed by a processor, the computer readable instructions may perform a method according to at least one aspect of the present disclosure.

The communication device 320 may transmit or receive a wired signal or a wireless signal.

On the other hand, the embodiment is not implemented only through the apparatus and/or method described so far, and a program for realizing a function corresponding to the configuration of the embodiment or a recording medium in which the program is recorded may be implemented, such implementation is described above. From the description of one embodiment, it can be easily implemented by those skilled in the art to which the present invention pertains. Specifically, the method (eg, network management method, data transmission method, transmission schedule generation method, etc.) according to the embodiment is implemented in the form of a program command that can be executed through various computer means, and can be recorded in a computer-readable medium. have. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded in the computer readable medium may be specially designed and configured for the embodiment, or may be known and available to those skilled in the art of computer software. The computer-readable recording medium may include a hardware device configured to store and execute program instructions. For example, the computer-readable recording medium includes magnetic media such as hard disks, floppy disks and magnetic tapes, optical recording media such as CD-ROMs and DVDs, and floppy disks. Such as magneto-optical media, ROM, RAM, flash memory, or the like. The program instructions may include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer through an interpreter or the like.

Although the embodiments have been described in detail above, the scope of the rights is not limited thereto, and various modifications and improved forms of those skilled in the art using the basic concepts defined in the following claims also belong to the scope of the rights.

Claims (20)

A method for a network data analytics function (NWDAF) to collect network data from a network function (NF), comprising:
sending a network open subscription request message including event reporting granularity parameters to the NF;
receiving the data set determined by the NF based on the event reporting granularity parameter from the NF through an event open notification message in at least one reporting cycle; and
performing network data analysis using the received data set.
A network data collection method comprising a. In claim 1,
The network open subscription request message further includes a reporting type parameter,
and the data set is determined by the NF based on the event reporting granularity parameter and the reporting type parameter. In claim 2,
Receiving the data set determined by the NF based on the event reporting granularity parameter from the NF through an event open notification message in at least one reporting cycle,
If the reporting type instructs the NF to report a data set representing a difference from a previous alert, compare the data in the previous alert with newly added data, deleted data, changed data, or the event reporting granularity Receiving from the NF a data set including at least one of data not described by a parameter
Containing, network data collection method. In claim 3,
Performing network data analysis using the received data set comprises:
recombining the data set with the data in the previous notification.
Containing, network data collection method. In claim 1,
If, after receiving the data set from the NF in the at least one reporting cycle, an event open notification message is not received from the NF in the reporting cycle next to the at least one reporting cycle, based on the event reporting granularity parameter inferring data corresponding to the next reporting cycle from the data set received in the at least one reporting cycle;
Further comprising a, network data collection method. In claim 1,
wherein the event reporting granularity parameter is applied for one event specific parameter, and the data set includes a plurality of event specific parameters. In claim 1,
wherein the event reporting granularity parameter is a parameter indicating a maximum allowable error for the network data. In claim 1,
and the event reporting granularity parameter indicates a range of data that the NF can ignore when collecting the network data. In claim 8,
When the network data to be collected by the NF is data represented by an identifier, the event reporting granularity parameter indicates a previous notification or an identifier list. In claim 8,
When the network data to be collected by the NF is data expressed in numbers, the event reporting granularity parameter indicates a range of change of the network data. A network data analytics function (NWDAF) comprising:
a processor, a memory, and a communication device;
The processor executes the program included in the memory,
sending a network open subscription request message including an event reporting granularity parameter and a reporting type parameter to the NF;
Receiving the data set determined by the NF based on the event reporting granularity parameter and the reporting type parameter from the NF through an event open notification message in at least one reporting cycle, and
Analyzing network data using the received data set.
NWDAF to do. In claim 11,
When the processor performs the step of receiving the data set determined by the NF based on the event reporting granularity parameter and the reporting type parameter from the NF through an event open notification message in at least one reporting cycle,
When the reporting type instructs the NF to report a data set that represents a difference from a previous alert, compare the data in the previous alert to newly added data, deleted data, changed data, or to the event reporting granularity. receiving from the NF a data set including at least one of data not described by
to do, NWDAF. In claim 12,
When the processor performs the step of performing network data analysis using the received data set,
recombining the data set with the data in the previous notification.
to do, NWDAF. In claim 11,
The processor executes the program,
If, after receiving the data set from the NF in the at least one reporting cycle, an event open notification message is not received from the NF in the reporting cycle next to the at least one reporting cycle, based on the event reporting granularity parameter inferring data corresponding to the next reporting cycle from the data set received in the at least one reporting cycle;
To do more, NWDAF. In claim 11,
wherein the event reporting granularity is applied for one event specific parameter and the data set comprises a plurality of event specific parameters. In claim 11,
wherein the event reporting granularity parameter is a parameter indicating a maximum allowable error for the network data. In claim 11,
wherein the event reporting granularity parameter indicates a range of data that the NF can ignore when collecting the network data. In claim 17,
When the network data to be collected by the NF is data represented by an identifier, the event reporting granularity parameter indicates a previous notification or an identifier list, NWDAF. In claim 17,
When the network data to be collected by the NF is data expressed in numbers, the event reporting granularity parameter indicates a range of change of the network data. As a network function (NF),
a processor, a memory, and a communication device;
The processor executes the program included in the memory,
Receiving a network open subscription request message comprising an event reporting granularity parameter and a reporting type parameter from a network data analytics function (NWDAF);
transmitting a data set determined based on the event reporting granularity parameter and the reporting type parameter to the NWDAF in at least one reporting cycle through an event open notification message; and
Receiving an analysis result for the network data generated by the NWDAF from the NWDAF
NF to do

Images