KR102659676B1 - Method and apparatus for COLLECTING DATA THROUGH EVENT EXPOSURE SERVICE - Google Patents

Abstract

Invoking a network open subscription service operation carrying event reporting information to the NEF, receiving an event opening notification from the NEF sent based on the reporting type parameter included in the event reporting information, and collecting data based on the notification. A method and device for collecting data through the following steps are provided.

Description

Method and apparatus for collecting data through event open service {Method and apparatus for COLLECTING DATA THROUGH EVENT EXPOSURE SERVICE}

This description relates to a method and device for collecting data through subscription to an event open service.

In a 3GPP 5G system, a network function such as a Network Data Analytics Function (NWDAF) can collect network data and analyze the network data to generate analytics. However, if too much raw data is collected from the network function and application function of the communication system and the frequency of occurrence of raw data is too high, the network load due to data collection may become very large.

One embodiment provides a method for collecting data from AF via NEF.

Another embodiment provides a method for collecting data from AF via NEF.

Another embodiment provides a method of providing data to NF via NEF.

According to one embodiment, a method for collecting data from an application function (AF) via a network exposure function (NEF) is provided. The method includes the steps of calling a network open subscription service operation accompanying event reporting information to the NEF, receiving an event opening notification from the NEF transmitted based on a reporting type parameter included in the event reporting information, and based on the notification. It includes the step of collecting data.

In the above embodiment, the method may further include performing data analysis using the collected data.

In the method of the above embodiment, the step of collecting data based on the notification may include determining that the same event as an event included in a previous notification is included in the notification if the same event has disappeared.

In the method of the above embodiment, the step of collecting data based on the notification may include determining that a different event has newly appeared when an event different from an event included in a previous notification is included in the notification.

In the method of the above embodiment, the step of collecting data based on the notification includes, when a second event different from the first event included in the previous notification is included in the notification, the second event determines that the first event has changed. May include steps.

In the method of the above embodiment, the event opening notification may be transmitted based on the reporting type parameter and the granularity of dynamics parameter included in the event reporting information.

In the method of the above embodiment, collecting data based on the notification may include inferring an event that occurred in AF from a dynamic granularity parameter and an event in a previous notification.

According to another embodiment, a method for collecting data from an application function (AF) via a network exposure function (NEF) is provided. The method includes calling a network open subscription service operation accompanying event reporting information to the NEF, receiving an event open notification transmitted based on a dynamic granularity (granularity of dynamics) parameter included in the event reporting information from the NEF. It includes steps to collect data based on notifications.

In the method of the other embodiment, collecting data based on the notification may include inferring an event that occurred in AF from dynamic granularity parameters and events in a previous notification.

In another embodiment, the method may further include performing data analysis using the collected data.

In the method of the other embodiment, the event opening notification may be transmitted based on the reporting type parameter and dynamic granularity parameter included in the event reporting information.

In the method of the other embodiment, collecting data based on the notification may include determining that the same event as an event included in a previous notification is included in the notification if the same event has disappeared.

In the method of the other embodiment, the step of collecting data based on the notification may include determining that a different event has newly appeared when an event different from an event included in a previous notification is included in the notification. .

In the method of the other embodiment, the step of collecting data based on the notification includes, if a second event that is different from the first event included in the previous notification is included in the notification, the second event determines that the first event has changed. It may include steps.

According to another embodiment, a method of providing data to a network function (NF) through a network exposure function (NEF) is provided. The method includes receiving a call of a network open subscription service operation carrying event reporting information from the NEF, and sending an event opening notification to the NEF based on a reporting type parameter included in the event reporting information.

In the method of the other embodiment, the step of transmitting an event opening notification to the NEF based on the reporting type parameter included in the event reporting information includes the event occurring when the generated event is different from the event included in the previous event opening notification. It may include the step of transmitting to NEF.

In the method of the other embodiment, the step of transmitting an event opening notification to the NEF based on the reporting type parameter included in the event reporting information includes the reporting type parameter included in the event reporting information and the granularity of dynamics. ) may include transmitting an event opening notification to the NEF based on

In the method of the other embodiment, the event opening notification may include one of a range of scalar values, a list of event identification information, and a previous notification.

By collecting network data based on dynamic 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 showing the topology of a mobile communication system according to an embodiment.
Figure 2 is a flowchart showing a method of subscribing to/unsubscribing to an event open service according to an embodiment.
Figure 3 is a flowchart showing a data collection method according to one embodiment.
Figure 4 is a block diagram showing network functions according to one embodiment.

Below, with reference to the attached drawings, embodiments of the present disclosure will be described in detail so that those skilled in the art can easily implement the present invention. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein. In order to clearly explain the description in the drawings, parts that are not related to the description are omitted, and similar parts are given similar reference numerals throughout the specification.

Throughout the specification, terminal refers to user equipment (UE), mobile station (MS), mobile terminal (MT), advanced mobile station (AMS), high reliability mobile station. (high reliability mobile station, HR-MS), subscriber station (SS), portable subscriber station (PSS), access terminal (AT), machine type communication device, MTC device), etc., and may include all or part of the functions of UE, MS, MT, AMS, HR-MS, SS, PSS, AT, etc.

In addition, the base station (BS) includes node B, evolved node B (eNB), gNB, advanced base station (ABS), and high reliability base station. HR-BS), access point (AP), radio access station (RAS), base transceiver station (BTS), MMR (mobile multihop relay)-BS, repeater that acts as a base station (relay station, RS), relay node (RN) that acts as a base station, advanced relay station (ARS) that acts as a base station, high reliability relay station (high reliability relay station) that acts as a base station , HR-RS), small base station [femto BS, home node B (HNB), home eNodeB (HeNB), pico BS, macro BS, micro base station ( micro BS), etc.], etc., and may refer to all or part of the functions of NB, eNB, gNB, ABS, AP, RAS, BTS, MMR-BS, RS, RN, ARS, HR-RS, small base station, etc. It may also be included.

Throughout the specification, when a part is said to “include” a certain element, this means that it may further include other elements rather than excluding other elements, unless specifically stated to the contrary.

In this specification, expressions described as singular may be interpreted as singular or plural, unless explicit expressions such as “one” or “single” are used.

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

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

In the flowchart described herein with reference to the drawings, the order of operations may be changed, several operations may be merged, certain operations may be divided, and certain operations may not be performed.

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

Referring to FIG. 1, the core network of a wireless communication system according to an embodiment includes a plurality of network functions (NF) and can connect a data network (DN) and UE.

(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 can be connected to the Access and Mobility Function (AMF) through the N2 interface and to the User Plane Function (UPF) through the N3 interface.

AMF may be responsible for the mobility management function of the UE. AMF can provide access and mobility management functions independently of access technology, that is, on a per-device basis. Therefore, each terminal can basically be connected to one AMF.

The Session Management Function (SMF) may be responsible for managing sessions up to the UE. When multiple sessions are created in the terminal, a different SMF may be assigned to each session.

The Policy Control Function (PCF) performs session management, mobility management, etc. based on packet flow information received from the Application function (AF) to ensure Quality of Service (QoS). Policies can be decided. The policy determined in the PCF is delivered to the AMF, SMF, etc., and then mobility management, session management, QoS management, etc. can be performed in each NF.

The DN can deliver a Protocol Data Unit (PDU) to be transmitted to the UE to the UPF or receive a PDU transmitted from the UE through the UPF. UPF and DN can be connected through the N6 interface.

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

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

The Authentication Server Function (AUSF) can store data for terminal authentication.

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

The network repository function (NRF) stores information such as the profile of the network function (capacity, load, status, etc. of the network function) and the service of the network function (capacity by service, load by service, status by service). It is an entity. Information stored in the NRF can be provided by calling service operations such as NFDiscovery_Request and NFManagement_NFStatusNotify.

The network exposure function (NEF) is an entity that safely opens the services and capabilities provided by 3GPP network functions to third party servers, etc. outside the ^3GPP network.

Any NF can discover and select the target NF it wants to interact with through NRF and NEF.

In this description, network capability exposure by NEF may include the following.

- Opening network events of the core network NF externally and/or internally

- Opening the provisioning capability to an external function

- Opening policy and charging capabilities to external functions

- Opening core network internal capabilities for analytics

- Opening the analysis to external parties

- Supporting NFs in the core network (e.g., NWDAF) to retrieve events from external parties and forwarding subscription/unsubscription requests to external parties' event reporting services.

A consumer of NF service (NF consumer) can provide the following to subscribe to the event reporting service.

- One or more event IDs: Here, the event ID is to identify the type of event to be subscribed to. According to one embodiment, the NF consumer has at least one of event service experience information, UE mobility information, UE communication information, and exception information that can be subscribed to. I can provide one.

Service experience information includes the average of observed service MoS and /or may include dispersion.

Exception information may include exception ID, exception level, exception trend, etc. regarding unexpected long-term/large rate flows and suspected DDoS attacks.

- Event filter information: Event filter information may provide event parameter types and event parameter values to satisfy the conditions for notifying the subscribed event ID. The event parameter type may be, for example, 'area of interest', and the event parameter value may be a list of tracking areas (TAs). Alternatively, the event filter information may be information about a slice of interest (network slice). Event filter information may depend on event ID. That is, event filter information can be provided for each event ID to be subscribed to. Within a subscription, different event IDs may be associated with different event filter information.

- Event Reporting Information: Event reporting information is described in Table 1 below. Within a subscription, every event ID can be associated with unique event reporting information.

- Target of Event Reporting: The target of event reporting may indicate a specific UE or PDU session, a group of UEs, or any UE (or all UEs). All event IDs within a subscription can be associated with the same target for event reporting. Here, the target of event reporting may correspond to multiple UEs or multiple PDU sessions.

- Notification target address (+ Notification Correlation ID): The notification target address can enable notifications received from an event provider with subscription to be correlated with the NF that receives the event. A subscription may be associated with a unique notification target address (+ notification correlation ID). When an NF consumer subscribes to the NF provider's service on behalf of another NF, the NF consumer can provide the other NF's notification target address (+ notification correlation ID) for the event ID to be delivered as a notification to the other NF. The NF consumer's notification target address (+ notification correlation ID) for subscription change may be related to the event notification. Each notification target address (+ notification correlation ID) may be associated with an associated event ID and/or set of event IDs.

- Expiry time: The expiry time can indicate how long you want the subscription to remain active. The consumer of the NF service can propose an expiration time by communicating the expiration time to the provider of the NF service. Based on the operator's policy, the provider of the NF service may determine whether the subscription has expired. When the subscription may expire, the provider of the NF service may determine the expiration time and provide the determined expiration time to the consumer of the NF service in response. When an event subscription is about to expire based on the expiration time proposed by the consumer of the NF service, and the consumer of the NF service wishes to continue receiving notifications, the consumer of the NF service sends a request to the NF service provider to extend the expiration time. You can update your subscription. If the expiration time associated with the subscription is reached, the subscription may be voided at the NF service provider. If the consumer of the NF service wants to continue receiving notifications, the consumer of the NF service needs to create a new subscription to the producer of the NF service.

When a subscription is accepted by the event provider NF, the consumer of the NF service may receive an identifier (subscription correlation ID) from the event provider NF that allows it to manage (modify, delete, etc.) the subscription.

A notification correlation ID may be assigned by a consumer NF that subscribes to event reporting, and a subscription correlation ID may be assigned by an NF that notifies when an event is met. Since these two correlation identifiers are optimized for finding subscriptions related to the context within each NF, they can both be assigned the same value, even though they are assumed to be different values.

Consumer NFs can use operations dedicated to subscription modification to add or delete event IDs from a subscription or to modify event filter information.

Events can be subscribed to by consumer NFs by providing event filters. And explicit cancellation of subscription by NF consumer is possible. The content of event reporting information is described in Table 1 along with the presence requirements for each information element.

In Table 1, the maximum number of reports can be applied to the subscription for one UE or one group of UEs. When a subscription is applied to a group of UEs, the parameters may be applied respectively to individual UEs within the group. The number of reports can be counted per granularity of dynamics.

Maximum duration of reporting may apply to subscriptions for one UE, a group of UEs, or any UE. When a subscription applies to UEs within a group, the maximum duration of reporting parameter may be applied to UEs in each group. When a subscription applies to any UE, the maximum duration of reporting parameter may apply to all affected UEs.

For a given subscription, if the maximum number of reports parameter and the maximum duration of reporting parameter are included, the subscription may be considered to expire when one of the conditions according to the two parameters is met.

Sampling ratio can be applied to subscriptions targeting a group of UEs or random UEs. When a sampling rate is provided, a random subset of target UEs may be selected according to the sampling rate and events related to the selected subset may be reported. The UE may remain selected until it is no longer managed by the event provider NF. A UE newly managed by the NF may be newly selected.

Group Reporting Guard Time is an optional parameter for group-based monitoring configuration to indicate the time that monitoring of event reporting related to UEs in the group can be aggregated before being transmitted to the consumer NF. The value of the group reporting protection time needs to be set smaller than the maximum duration of reporting. To continuously monitor reporting, the group reporting protection time can be restarted after expiration if the maximum duration of reporting is not reached. If the time remaining until the maximum duration of reporting is shorter than the group reporting protection time, the group reporting protection timer needs to be set to expire when the maximum duration of reporting expires. When the maximum duration of reporting expires, the group reporting protection time, even if it continues, can be considered expired and the aggregated monitoring of event reporting can be immediately transmitted to the destination.

Dynamic granularity can dictate which changes within a subscription's target event can be ignored, in favor of unnecessary notifications. Changes in dynamic granularity may be indicated as a range of scalar values (x,y), a list of event identification information (e.g., a list of SUPIs), or a previous notification. The range of scalar values (x,y) may mean [scalar value of previous notification - x, scalar value of previous notification + y). If dynamic granularity is provided, the provider NF can send notifications when changes in the target event are not accounted for within the dynamic granularity. Even if dynamic granularity is provided, the provider NF can transmit the first notification as is.

Reporting type is a parameter to reduce the amount of data in notifications. If a reporting type is provided, the provider NF can notify of newly appeared, disappeared, or changed events compared to previous notifications. Even if a reporting type is provided, the provider NF may send the first notification as is.

A notification corresponding to a subscription may include a notification correlation ID along with an event ID and may include an individual target associated with the notification (eg, UE or PDU session ID).

When the consumer of the NF service decides to terminate the event subscription, the consumer of the NF service can request the event provider NF to unsubscribe from the event through an unsubscribe service operation and cancel the event subscription. After receiving a request for unsubscription from a consumer of the NF service, the event provider NF may terminate the event subscription.

Below, the external opening of network capabilities and the opening of core network internal events and capabilities are explained.

When the immediate reporting flag in Table 1 is set, the first corresponding event report may be included in the output if corresponding information is available at the recipient of the event's subscription request.

The MTC provider information, which is an optional parameter, can be a reference parameter that can be provided by the AF or a reference parameter that can be determined by the NEF based on the AF to communicate. MTC provider information may identify the MTC service provider and/or MTC application. MTC provider information may be used by a service provider, for example, to distinguish between different customers.

Figure 2 is a flowchart showing a method of subscribing to/unsubscribing to an event open service according to an embodiment.

According to one embodiment, a consumer of an NF service may subscribe/unsubscribe to an event exposure service to collect data about related events. Here, the consumer of the NF service may be an entity within the cellular system, such as NWDAF.

The NF service consumer according to one embodiment uses 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. You can utilize it. The procedure shown in Figure 2 can be used when a consumer of an NF service (such as NWDAF) subscribes to data from a trusted AF in an external network.

When the NF service consumer sends a subscription request through a service operation to the NF service provider to subscribe to a network open service, a parameter that can tolerate some errors regarding the necessary data in each NF's notification is transmitted to the NF service provider together. You can. Additionally, the subscription request may include a parameter for requesting only data not delivered in the previous notification as necessary data.

Referring to FIG. 2, the NF service consumer according to one embodiment may request a subscription to an event ID from the NF service provider by calling the event open subscription (Nnf_EventExposure_Subscribe) service operation. Alternatively, the NF service consumer may request the NF service provider to unsubscribe to the event ID by calling the event open unsubscribe (Nnf_EventExposure_Unsubscribe) service operation (S111).

The service operation of event open subscription may involve dynamic granularity parameters and reporting type parameters. Dynamic granularity parameters and reporting type parameters may be predetermined by the NF service consumer.

The data required is the event ID, event filter (e.g., local information), and type of event reporting (e.g., all UEs, UEs in a specific group, or specific UE) accompanying the service operation requesting an event open subscription. can be indicated by

The NF service provider may be one of several network functions within a mobile communication system. Afterwards, the NF service provider can deliver the output according to the event open subscription service operation to the NF service consumer, and subscription/unsubscription for the event ID can be completed according to this output (S112).

A NF service consumer according to one embodiment may determine negligible changes to required data and set dynamic granularity based on the determined negligible changes. The ignorable changes determined by the NF service consumer may be the range of data that can be ignored by the NF reporting the requested data based on dynamic granularity. Additionally, the NF service consumer according to one embodiment may determine the quantity of events to be collected and the reporting type to reduce signaling overhead of the core network and each network function.

Specifically, the NF service consumer according to one embodiment may determine dynamic granularity and reporting type as event reporting information of an event exposure subscribe operation.

When the dynamic granularity parameter is set by a consumer NF (e.g., NWDAF) in the event open subscription procedure, an event open subscription request (Nnf_EventExposure_Subscribe) service action accompanying the dynamic granularity parameter is sent to the consumer NF. It is called by, and then the producer NF can send a notification containing the requested data to the consumer NF.

The producer NF may send notifications containing the requested data to the consumer NF periodically during subscription to the event opening or per aperiodic reporting cycle.

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

If the consumer NF does not receive a notification containing the required data during a reporting cycle, the consumer NF can infer the data for the current reporting cycle from the data in the notification received in the previous reporting cycle based on dynamic granularity. You can. For example, NWDAF can infer data corresponding to the current reporting cycle by adding Gaussian noise (e.g., zero-mean Gaussian noise) to data contained within previous notifications. This allows NWDAF to maintain a complete record of required data corresponding to every reporting cycle during the subscription period, and the frequency of notification (or provision) of required data can be significantly reduced.

The reporting type parameter can be set to use a different data set than the previous notification, or 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 includes newly added, deleted, or changed data compared to the previous notification. The data set can be sent to the consumer NF through a notification.

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

If the NF service consumer sets the reporting type parameter to use a data set that represents differences from previous notifications, the NF service consumer will receive notifications from the producer NF containing newly added, deleted, or changed data. You can. At this time, the NF service consumer can reassemble the data in the previous notification and the data in the subsequent notification, or infer data corresponding to the current notification from the data in the previous notification. Accordingly, the reporting type parameter may allow reducing the amount of data within each notification without losing necessary data.

Dynamic granularity parameters and reporting type parameters delivered to the NF service provider by the event open subscription request service operation may be maintained during the event open subscription of the NF service consumer. The duration of an event open subscription may include multiple reporting cycles, either periodic or aperiodic, in which notifications are sent to NF service consumers. Dynamic granularity parameters and reporting type parameters can be updated by re-invoking the Nnf_EventExposure_Subscribe service operation.

The NF service provider according to one embodiment may transmit the requested data to the NF service consumer through the first notification after the event open subscription starts. Afterwards, the NF service provider can transmit the requested data to the NF service consumer through an event open notification (Nnf_EventExposure_Notify) based on dynamic granularity and reporting type (S113).

For example, if the change in requested data between the previous reporting cycle and the next reporting cycle is within the range determined by dynamic granularity, the NF service provider may not send an event open notification to the NF service consumer in the next reporting cycle. Alternatively, if the change in the requested data is greater than the range determined by dynamic granularity, the NF service provider may send an event open notification to the NF service consumer in the next reporting cycle.

When the NF service provider according to one embodiment transmits an event open notification to the NF service consumer in the reporting cycle, it transmits all requested data or a different data set from the requested data in the previous notification depending on the reporting type parameter. can do. For example, if the Reporting Type parameter instructs the NF service provider to report differences from previous notifications, the NF service provider will send an event open notification containing a dataset containing newly added data, deleted data, or changed data. It can be sent to consumers.

Here, the first notification (e.g., first event opening notification) sent by the NF service provider to the NF service consumer may include all requested data regardless of the reporting type.

Referring to Figure 2, if the NF service consumer does not receive an event open notification from the NF service provider in the next reporting cycle of the reporting cycle in which the data set was received, the NF service consumer receives the data in the previous notification based on dynamic granularity. From the set, data corresponding to the current reporting cycle can be inferred. That is, the NF service consumer can infer data corresponding to the next reporting cycle of the previous reporting cycle from the data set received in the previous reporting cycle based on dynamic granularity, even if there are no notifications or data sets received in the current reporting cycle. there is.

When the NF service consumer receives an event open notification from the NF service provider at the end of the reporting cycle, and the event open notification contains a data set indicating differences from previous notifications, the NF service consumer collects the required data and data within the previous notification. Sets can be recombined. The NF service consumer can then perform network data analysis using the inferred data set, the reassembled data set, and/or all necessary data sets.

If the event ID of the event open subscription supports the collection of multiple data from the NF (i.e., the collection of multiple types of data is indicated by the event ID), the NF service consumer creates a dynamic granule for each data. You can set the rutty. Different types of dynamic granularity can be applied to different types of data that can be collected. Table 2 below shows examples of each type of data and examples of dynamic granularity that can be applied to each type of data.

data type Example data Example of dynamic granularity Data expressed as an identifier Application ID, filter information, location of the application (e.g., list of DNAI), UE ID(s) (e.g., SUPI, GPSI), UE group ID, DNN, S-NSSAI, QFI, TAC, UE location , Exception ID, Exception trend i) Previous notification or
ii) List of event identifying information (e.g. list of TA(s), etc.) data expressed as 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, exception level iii) Range of scalar value: x and y indicating the range of changes to the requested data within a previous notification (e.g. [scalar value of previous notification - x, scalar value of previous notification + y))

In Table 2, i) if previous notification is applied as dynamic granularity, the producer NF can transmit a notification only if the requested data is different from the data of the previous notification. For example, when NWDAF collects UE IDs through a subscription to the Nnf_EventExposure service according to dynamic granularity, the producer NF compares it with the data within the previous notification when a new UE ID is added or the UE ID disappears from the data within the previous notification. The Nnf_EventExposure_Notify service operation can be called. ii) If a list of event identification information (List of events identification) is included in the dynamic granularity parameter, the producer NF can detect changes in the requested data (e.g. identifier or ID). If it is not included in the 'list of event identification information', the Nnf_EventExposure_Notify service action can be called. For example, when NWDAF collects the UE location through subscription to the Nnf_EventExposure service and dynamic granularity is set to a predetermined TA list, the producer NF determines that the UE's location is within the TA list of dynamic granularity. When changing to a TA that does not exist, the Nnf_EventExposure_Notify service action can be called.

iii) If the range of scalar value is included in the dynamic granularity parameter, the producer NF determines that the requested data is in the range [(data in previous notification-x), (data in previous notification+y)) When exiting, the Nnf_EventExposure_Notify service action can be called. For example, when NWDAF collects the number of UEs in a specific area from AMF and the dynamic granularity is set to (x=10, y=11), the number of UEs in a specific area is based on the data in the previous notification. If it is within the range [-10, +11), AMF may not call the Nnf_EventExposure_Notify service operation. Afterwards, NWDAF can determine the data corresponding to the event reporting cycle within the range of [previous data - 10, previous data + 11) through inference.

When 'Reporting Type' is set to use datasets that differ from previous notifications, the producer NF will send the consumer a dataset containing newly added, deleted, or changed data compared to the previous notification. You can report to NF in the event notification cycle.

Nnf_EventExposure_Subscribe Dynamic granularity parameters and reporting type parameters accompanying service operations can be applied to one event-specific parameter. A data set containing a plurality of event-specific parameters (i.e., consisting of a plurality of event-specific parameters) may be delivered to the NF service consumer through the Nnf_EventExpsoure_Notify service operation.

When dynamic granularity is set, the calling conditions for Nnf_EventExpsoure_Notify are as follows.

- Event ID supports single data collection: Producer NF can call Nnf_EventExposure_Notify when a change in data falls outside the data scope of dynamic granularity.

- Event ID supports multiple data collection (e.g. service data collected from AF):

* If dynamic granularity is set only for specific data, the producer NF can call Nnf_EventExposure_Notify when changes to specific data fall outside the data range of dynamic granularity.

* When dynamic granularity is set for multiple types of data, the producer NF may call Nnf_EventExposure_Notify when at least one change to the data is outside the data range of the dynamic granularity.

For example, if NWDAF collects a dataset of SUPI and UE location for a specific UE group from AMF (Event ID = Location Report), and dynamic granularity is set to "old notification" for SUPI and UE location respectively, If present, the producer NF determines that at least one UE location is different from the UE location in the previous advertisement or the target SUPI changes due to UE mobility (e.g., a new UE moves into the area or an existing UE moves out of the area) When this occurs, Nnf_EventExposure_Notify can be called.

When 'Reporting Type' is set in the Nnf_EventExposure_Subscribe procedure, event specific parameters that can be delivered to the NF service consumer by Nnf_EventExpsoure_Notify may include the following contents.

- When 'Reporting Type' is set to use a data set that represents differences from previous notifications,

* If dynamic granularity is not applied to the subscription, event-specific parameters include i) newly added data, ii) deleted data, and iii) changed data compared to the previous notification. If identical data is contained within the notification compared to the previous notification, NWDAF may recognize that data as ii) data deleted from the previous notification; NWDAF can recognize the data in the notification as i) newly added data or iii) changed data.

* When dynamic granularity is applied to a subscription, event-specific parameters may contain data whose changes are not accounted for within the dynamic granularity. If the notification contains identical data compared to the previous notification, NWDAF may recognize that the corresponding data within the notification is ii) data deleted from the previous notification, and ii) data that is not identical compared to the previous notification is included within the notification. If present, NWDAF can recognize the corresponding 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 NF service consumer can improve the conventional Nnf_EventExposure_Subscribe procedure and Nnf_EventExposure_Notify service procedure by using dynamic granularity parameters and reporting type parameters.

A NF service consumer according to one embodiment can determine an appropriate dynamic granularity for the data needed to generate analytics and infer the data needed during the subscription period from differences reported conditional on previous notifications. In addition, all NF service providers in the mobile communication system that open events are required to: In terms of differences from previous notifications, the requested network data can be provided to the NF service consumer.

Figure 3 is a flowchart showing a data collection method according to one embodiment.

A consumer of an NF service (e.g., NWDAF) according to one embodiment may collect data and/or information from AF through a provider (e.g., NEF) of the NF service (e.g., event opening service). there is. Available data (AF collectable data or AF available data) that AF can provide to consumers of NF services is registered in NEF, and when necessary, AF available data can be registered in NEF through OAM configuration. AF available data may include at least one of AF identification, AF service identification, and available data to be collected per application. For example, AF service identification information may be endpoint information of the Naf_EventExposure service operation. Available data to be collected per application may be identified, for example, by event ID(s).

Referring to FIG. 3, after AF available data is registered in the NEF 300, the NEF 300 may create an event open service related to the AF available data. Here, the event open service regarding AF available data may have a new event ID (EventID). Thereafter, the NEF 300 may update the registration information (e.g., NF profile of the NEF) of the NEF 300 in the NRF 100 by calling the Nnrf_NFManagement_NFUpdate_request service operation (S211). Here, the registration information of the NEF 300 may include at least one of a newly generated event ID for AF available data, AF identification information related to the generated event ID, and application ID(s).

The NRF 100, which has received a request to update registration information from the NEF 300, may store the registration information of the NEF 300 (i.e., the NF profile of the NEF 300) (S212). Here, the registration information of the NEF (300) to be stored in the NRF (100) includes information about AF available data (e.g., event ID linked to AF available data, AF identification information related to event ID, and application ID, etc.) can do. Afterwards, the NRF (100) may call the Nnrf_NFManagement_NFUpdate_response service operation for the NEF (300) (S213).

Thereafter, when the NF service consumer 200 needs to collect available data from the AF 400, it may call the Nnrf_NFDiscovery_Request_request service operation for the NRF 100 (S214). At this time, the NF service consumer 200 may query the NRF 100 for the appropriate NEF 300 to collect available data using the NEF NF Type, a list of event IDs, etc. as parameters. AF identification information and application ID may also be used as parameters to be transmitted from the NF service consumer 200 to the NRF 100.

The NRF (100) matches the query of the NF service consumer (200) regarding AF available data with the registered NF profile of the NEF (300), and calls the Nnrf_NFDiscovery_Request_response service operation to send information about the matched NEF (300) to the NF service. It can be delivered to the consumer (200) (S215). Thereafter, the NF service consumer 200 can identify available AF data for each application and determine an appropriate NEF 300 to collect the identified available AF data.

The NF service consumer 200 can subscribe to the event open service for collecting data of the AF 400 by calling the Nnef_EventExposure_Subscribe service operation for the NEF 300. Alternatively, the NF service consumer 200 may cancel the subscription to the event open service for collecting data of the AF 400 by calling the Nnef_EventExposure_Unsubscribe service operation for the NEF 300 (S220). If the subscription to the event open service is approved by the NEF 300, the NEF 300 may record the association of the event trigger and the identity of the NF service consumer 200. User consent may or may not be required for the NF service consumer 200 to retrieve user data in the AF, and the user's consent may be stored in the NEF 300.

As described above, the Nnef_EventExposure_Subscribe service operation transmitted by the NF service consumer 200 to the NEF 300 may be accompanied by event reporting information. Event reporting information may include at least one of reporting type and/or granularity of dynamics.

The NEF 300 can subscribe to the event open service for collecting data of the AF 400 by calling the Naf_EventExposure_Subscribe service operation for the AF 400. Alternatively, the NEF 300 may cancel the subscription to the event open service by calling the Naf_EventExposure_Unsubscribe service operation to the AF 400 (S230). Here, Naf_EventExposure_Subscribe/Unsubscribe may entail at least one of a reporting type parameter and a dynamic granularity parameter.

When the NEF (300) subscribes to the event open service for collecting data of the AF (400), the AF (400) sends events related to AF available data to the NEF (300) by calling the Naf_EventExposure_Notify service operation according to the event reporting information of the subscription. ) can be notified (S240).

Thereafter, when a notification regarding an event is received from the AF 400, the NEF 300 may deliver the event related to the AF available data to the NF service consumer 200 by calling the Nnef_EventExposure_Notify service operation (S250).

When the reporting type parameter is included in the event reporting information of step S220, the AF 400 may deliver an event related to AF available data to the NEF 300 through a notification when the generated event is different from a previously reported event. Alternatively, the NEF 300 may deliver an event related to AF available data to the NF service consumer 200 when an event received from the AF 400 is different from a previously reported event. Here, the difference between the event received from the AF 400 and the previously reported event is the newly appeared event, disappeared event, and changed event in the previously reported event (or notification). event) may be included.

If the same event as the event of the previous notification is included in the notification from the NEF 300, the NF service consumer 200 may determine that the same event has disappeared. Otherwise, the NF service consumer 200 may determine that the event appears newly or that it has changed. For example, when an event that is different from an event included in a previous notification is included in an event opening notification, the NF service consumer 200 may determine that the different events above appear newly or determine that the different events have changed. there is. Additionally, the NF service consumer 200 may restore events that are not included in the current notification but are included in the previous notification from the previous notification.

When the dynamic granularity parameter is included in the event reporting information of step S220, the NF service consumer 200 can infer the event that occurred in the AF 400 from the applied dynamic granularity and the event in the previous notification.

As described above, the efficiency of data collection can be improved and real-time data collection can be improved by the consumer NF collecting network data based on dynamic granularity and reporting type from AF through NEF.

Figure 4 is a block diagram showing network functions according to one embodiment.

The network function according to one embodiment may be implemented in a computer system, for example, a computer-readable medium. Referring to FIG. 4, the computer system 400 includes a processor 410, a memory 430, an input interface device 450, an output interface device 460, and a storage device 440 that communicate through a bus 470. ) may include at least one of Computer system 400 may also include a communication device 420 coupled to a network. The processor 410 may be a central processing unit (CPU) or a semiconductor device that executes instructions stored in the memory 430 or the storage device 440. Memory 430 and storage device 440 may include various types of volatile or non-volatile storage media. For example, memory may include read only memory (ROM) and random access memory (RAM). In embodiments 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. Memory is various forms of volatile or non-volatile storage media, for example, memory may include read-only memory (ROM) or random access memory (RAM).

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

The communication device 420 can transmit or receive wired signals or wireless signals.

Meanwhile, the embodiments of the present invention are not only implemented through the apparatus and/or method described so far, but may also be implemented through a program that realizes the function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded. This implementation can be easily implemented by anyone skilled in the art from the description of the above-described embodiments. Specifically, methods according to embodiments of the present invention (e.g., network management method, data transmission method, transmission schedule creation method, etc.) are implemented in the form of program instructions that can be executed through various computer means, and are stored in a computer-readable medium. can be recorded The computer-readable medium may include program instructions, data files, data structures, etc., singly or in combination. Program instructions recorded on the computer-readable medium may be specially designed and configured for embodiments of the present invention, or may be known and usable by those skilled in the art of computer software. A computer-readable recording medium may include a hardware device configured to store and perform program instructions. For example, computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, and floptical disks. It may be the same magneto-optical media, ROM, RAM, flash memory, etc. Program instructions may include not only machine language code such as that created by a compiler, but also high-level language code that can be executed by a computer through an interpreter, etc.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements made by those skilled in the art using the basic concept of the present invention defined in the following claims are also possible. It falls within the scope of rights.

Claims (18)

A method in which a data collecting device collects data from an application function (AF) through a network exposure function (NEF),
The device calling a network open subscription service operation involving event reporting information to the NEF,
The device receiving an event opening notification from the NEF, which is transmitted based on a reporting type parameter included in the event reporting information, and
The device collecting the data based on the notification
How to include . In paragraph 1:
performing data analysis using the data collected by the device.
How to include more. In paragraph 1:
The step of collecting the data based on the notification is,
If the same event as an event included in a previous notification is included in the notification, determining that the same event has disappeared
Method, including. In paragraph 1:
The step of collecting the data based on the notification is,
If an event different from an event included in a previous notification is included in the notification, determining that the different event has newly appeared
Method, including. In paragraph 1:
The step of collecting the data based on the notification is,
If a second event that is different from the first event included in the previous notification is included in the notification, determining that the second event is a change to the first event.
Method, including. In paragraph 1:
The method of claim 1, wherein the event open notification is transmitted based on the reporting type parameter and the granularity of dynamics parameter included in the event reporting information. In paragraph 6:
The step of collecting the data based on the notification is,
Inferring an event occurring in the AF from the dynamic granularity parameters and events in the previous notification
How to include . A method in which a data collecting device collects data from an application function (AF) through a network exposure function (NEF),
The device calling a network open subscription service operation involving event reporting information to the NEF,
The device receiving an event opening notification from the NEF, which is transmitted based on a granularity of dynamics parameter included in the event reporting information, and
The device collecting the data based on the notification
How to include . In paragraph 8:
The step of collecting the data based on the notification is,
Inferring an event occurring in the AF from the dynamic granularity parameters and events in the previous notification
How to include . In paragraph 8:
performing data analysis using the data collected by the device.
How to include more. In paragraph 8:
The method wherein the event opening notification is transmitted based on the reporting type parameter and the dynamic granularity parameter included in the event reporting information. In paragraph 11:
The step of collecting the data based on the notification is,
If the same event as an event included in a previous notification is included in the notification, determining that the same event has disappeared
Method, including. In paragraph 11:
The step of collecting the data based on the notification is,
If an event different from an event included in a previous notification is included in the notification, determining that the different event has newly appeared
Method, including. In paragraph 11:
The step of collecting the data based on the notification is,
If a second event that is different from the first event included in the previous notification is included in the notification, determining that the second event is a change to the first event.
Method, including. A method in which a device collecting data provides data to a network function (NF) through a network exposure function (NEF),
the device receiving an invocation of a network open subscription service operation carrying event reporting information from the NEF, and
The device transmitting an event opening notification to the NEF based on the reporting type parameter included in the event reporting information.
How to include . In paragraph 15:
The step of transmitting an event opening notification to the NEF based on the reporting type parameter included in the event reporting information,
When the generated event is different from the event included in the previous event opening notification, transmitting the generated event to the NEF
Method, including. In paragraph 15:
The step of transmitting an event opening notification to the NEF based on the reporting type parameter included in the event reporting information,
Transmitting an event open notification to the NEF based on the reporting type parameter and granularity of dynamics included in the event reporting information.
Method, including. In paragraph 17:
The method of claim 1, wherein the event opening notification includes a range of scalar values, a list of event identification information, and one of a previous notification.

Images