Provision of data analytics in a telecommunication network

Abstract

A communication method and a system for converging a 5.sup.th-Generation (5G) communication system for supporting higher data rates beyond a 4.sup.th-Generation (4G) system with a technology for Internet of Things (IoT) is provided. The disclosure is applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as a smart home, a smart building, a smart city, a smart car, a connected car, health care, digital education, a smart retail, security and safety services. A method performed by a first entity performing a network data analytics function (NWDAF) is provided. The method includes receiving, from a second entity performing network function (NF), a first message for requesting observed service experience analytics, the first message including single-network slice selection assistance information (S-NSSAI) indicating a network slice, transmitting, to a third entity performing application function (AF) associated with the S-NSSAI, a second message for requesting service data associated with the observed service experience analytics, the second message including information on at least one application, receiving, from the third entity, the service data including at least one service experience for the at least one application, identifying the observed service experience analytics based on the service data, and transmitting, to the second entity, the observed service experience analytics.

Claims

1. A method performed by a first entity performing a network data analytics function (NWDAF), the method comprising: receiving, from a second entity performing a network function (NF), a message for requesting observed service experience information for a network slice, the message including single-network slice selection assistance information (S-NSSAI) indicating the network slice; obtaining service data including information on a service experience for an application related to the observed service experience information; obtaining network data including information on a quality of service (QoS) flow associated with the application; identifying the observed service experience information for the network slice based on the service data and the network data; and transmitting, to the second entity, the observed service experience information for the network slice, wherein the observed service experience information for the network slice includes information on a network slice service experience across at least one application including the application, and wherein the network slice service experience across the at least one application is obtained by averaging at least one service experience for the at least one application.

2. The method of claim 1, wherein the message for requesting the observed service experience information further includes information indicating at least one user equipment (UE), wherein, in case that the at least one UE is a UE on the network slice, the observed service experience information for the network slice includes a service experience for the UE, wherein, in case that the at least one UE is a group of UEs on the network slice, the observed service experience information for the network slice includes a service experience for the group of UEs, and wherein, in case that the at least one UE is any UE on the network slice, the observed service experience information for the network slice includes a service experience for all UEs on the network slice.

3. A method performed by a second entity performing a network function (NF), the method comprising: transmitting, to a first entity performing a network data analytics function (NWDAF), a message for requesting observed service experience information for a network slice, the message including single-network slice selection assistance information (S-NSSAI) indicating the network slice; and receiving, from the first entity, the observed service experience information for the network slice, wherein the observed service experience information on the network slice is identified based on service data and network data, wherein the service data includes information on a service experience for an application related to the observed service experience information, wherein the network data includes information on a quality of service (QoS) flow associated with the application, wherein the observed service experience information for the network slice includes information on a network slice service experience across at least one application including the application, and wherein the network slice service experience across the at least one application is obtained by averaging at least one service experience for the at least one application.

4. The method of claim 3, wherein the message for requesting the observed service experience information further includes information indicating at least one user equipment (UE), wherein, in case that the at least one UE is a UE on the network slice, the observed service experience information for the network slice includes a service experience for the UE, wherein, in case that the at least one UE is a group of UEs on the network slice, the observed service experience information for the network slice includes a service experience for the group of UEs, and wherein, in case that the at least one UE is any UE on the network slice, the observed service experience information for the network slice includes a service experience for all UEs on the network slice.

5. A first apparatus performing a network data analytics function (NWDAF), the first apparatus comprising: a transceiver; and a controller coupled with the transceiver and configured to: control the transceiver to receive, from a second entity performing a network function (NF), a message for requesting observed service experience information for a network slice, the message including single-network slice selection assistance information (S-NSSAI) indicating the network slice, obtain service data including information on a service experience for an application related to the observed service experience information, obtain network data including information on a quality of service (QoS) flow associated with the application, identify the observed service experience information for the network slice based on the service data and the network data, and control the transceiver to transmit, to the second entity, the observed service experience information for the network slice, wherein the observed service experience information for the network slice includes information on a network slice service experience across at least one application including the application, and wherein the network slice service experience across the at least one application is obtained by averaging at least one service experience for the at least one application.

6. The first apparatus of claim 5, wherein the message for requesting the observed service experience information further includes information indicating at least one user equipment (UE), wherein, in case that the at least one UE is a UE on the network slice, the observed service experience information for the network slice includes a service experience for the UE, wherein, in case that the at least one UE is a group of UEs on the network slice, the observed service experience information for the network slice includes a service experience for the group of UEs, and wherein, in case that the at least one UE is any UE on the network slice, the observed service experience information for the network slice includes a service experience for all UEs on the network slice.

7. A second apparatus performing a network function (NF), the second apparatus comprising: a transceiver; and a controller coupled with the transceiver and configured to: control the transceiver to transmit, to a first entity performing a network data analytics function (NWDAF), a message for requesting observed service experience information for a network slice, the message including single-network slice selection assistance information (S-NSSAI) indicating the network slice, and control the transceiver to receive, from the first entity, the observed service experience information for the network slice, wherein the observed service experience information on the network slice is identified based on service data and network data, wherein the service data includes information on a service experience for an application related to the observed service experience information, wherein the network data includes information on a quality of service (QoS) flow associated with the application, wherein the observed service experience information for the network slice includes information on a network slice service experience across at least one application including the application, and wherein the network slice service experience across the at least one application is obtained by averaging at least one service experience for the at least one application.

8. The second apparatus of claim 7, wherein, the message for requesting the observed service experience information further includes information indicating at least one user equipment (UE), wherein, in case that the at least one UE is a UE on the network slice, the observed service experience information for the network slice includes a service experience for the UE, wherein, in case that the at least one UE is a group of UEs on the network slice, the observed service experience information for the network slice includes a service experience for the group of UEs, and wherein, in case that the at least one UE is any UE on the network slice, the observed service experience information for the network slice includes a service experience for all UEs on the network slice.

Description

DESCRIPTION OF DRAWINGS

(1) The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

(2) FIG. 1 illustrates a slice structure in a 5th generation (5G) network according to an embodiment of the disclosure;

(3) FIG. 2 illustrates a representation of a network data analytics function (NWDAF) employed in a 5G network according to an embodiment of the disclosure;

(4) FIG. 3 illustrates a representation of a function of a NWDAF according to an embodiment of the disclosure;

(5) FIG. 4 illustrates a representation of a function of a NWDAF according to an embodiment of the disclosure;

(6) FIG. 5 illustrates a message flow according to an embodiment of the disclosure;

(7) FIG. 6 illustrates a message flow according to an embodiment of the disclosure;

(8) FIG. 7 illustrates a block diagram of an entity performing network data analytics function (NWDAF) according to an embodiment of the disclosure; and

(9) FIG. 8 illustrates a block diagram of an entity performing network function (NF) according to an embodiment of the disclosure.

(10) Throughout the drawings, like reference numerals will be understood to refer to like parts, components, and structures.

DETAILED DESCRIPTION

(11) The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

(12) The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

(13) It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

(14) FIGS. 1 through 6, discussed below, and the various embodiments used to describe the principles of the disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the disclosure may be implemented in any suitably arranged system or device.

(15) FIG. 1 illustrates a slice structure in 5G networks according to an embodiment of the disclosure. Network slicing is a type of virtual networking architecture allowing for better network flexibility through the partitioning of network architectures into virtual elements. In essence, network slicing allows the creation of multiple virtual networks atop a shared physical infrastructure.

(16) Referring to FIG. 1, there are three such slices, although, as indicated, more or fewer may be provided. Different slices can be configured and optimized for different functions/users. In the example shown, different slices are configured for smal tphones, automotive devices and Massive IoT devices respectively. In practice, different slices can be configured in a very flexible way and, importantly, the physical resources assigned to different slices can be adapted as required.

(17) A problem with existing slicing arrangements is that it is not always possible to obtain performance data of sufficient granularity to allow effective optimization and resource allocation to occur. Alternatively, such data that is available is required to be processed in the Operation and Administration Maintenance (OAM) function, remote from the Core Network (CN).

(18) Part of the control of a 5G network, which permits enhanced performance involves the use of data analytics, which are employed to assist in the management and optimization of resources. A key component of this function is the network data Analytics function (NWDAF) which is used for data collection and data analytics. An NWDAF may be used for analytics for one or more Network Slices. The NWDAF may serve use cases belonging to one or several domains, e.g., service quality, traffic steering, dimensioning, security.

(19) The input data to the NWDAF may come from multiple sources, and the resulting actions undertaken by the consuming network function (NF) or application function (AF) may concern several domains (e.g., Mobility management, Session Management, service quality management, Application layer, Security management, NF life cycle management).

(20) FIG. 2 illustrates a representation of NWDAF employed in a 5G network according to an embodiment of the disclosure.

(21) Referring to FIG. 2, NWDAF implementation, whereby the NWDAF 10 receives inputs from one or more NFs 20, one or more AFs 30, the unified data repository (UDR) 40 and the OAM 50 according to an embodiment of the disclosure. The data received from these sources is processed according to one or more analytics models and outputs are created and fed back, in this instance to one or more NFs 70, one or more AFs 70 and the OAM 80. Note that NFs 20, 60 may be the same NFs or at least have some commonality. Similarly for AFs 30, 70 and OAM 50, 80.

(22) A problem with NWDAF implementations in the prior art is that they are unable to provide service experience data analytics on a per-slice basis or, if they are, such analytics require the involvement of the OAM 50, 80, which is undesirable and takes this functionality away from the Core Network (especially the Control Plane, CP). This is useful in terms of optimizing network performance and/or configuration on a slice basis. This is increasingly beneficial when more and more network features are organized on a slice basis.

(23) Referring to FIG. 2, embodiments of the disclosure permit the creation and use of application service experience analytics on a slice level in the Control Plane i.e., without the direct involvement of the OAM.

(24) The operation of an embodiment is best illustrated by contrasting with the prior art operation.

(25) FIG. 3 illustrates a representation of a function of an NWDAF according to an embodiment of the disclosure.

(26) Referring to FIG. 3, the NWDAF 100 is communicatively coupled to at least one Consumer NF 110, at least one AF 120 and at least one NF (network data provider) 130. Messages are passed between each of these and the NWDAF 100 as follows:

(27) 3.1 The Consumer NF 110 makes an Observed Service Experience Analytics Subscriptions request (e.g., App ID, group of UEs) to NWDAF 100. In the context of this application, “Observed Service Experience” (OSE) is used interchangeably with “Quality of Experience” (QoE)

(28) 3.2 NWDAF 100 may requests an Application Service Data Subscription (Mean Opinion Score) to AF 120.

(29) 3.3 AF 120 reports Application Service Data Notification (Mean Opinion Score) to NWDAF 100.

(30) 3.4 NWDAF 100 may submits NF data request (Qos flow identifier (QFI), location, and the like) to NF 130.

(31) 3.5 NF 130 provides NF data notification (QFI, location, and the like) to NWDAF 100.

(32) 3.6 NWDAF 100 implements training algorithm to learn from supplied data.

(33) 3.7 NWDAF 100 provides data analytics to Consumer NF 110, including statistics of past performance or predictions of future performance.

(34) The numerals (3.1, 3.2, and the like) only indicate corresponding messages, and do not mean that any transmission order. Also, the messages may or may not be transmitted.

(35) Referring to FIG. 3, the operation represents the prior art and makes no allowance at all for network slicing.

(36) FIG. 4 illustrates a representation of a function of a NWDAF according to an embodiment of the disclosure.

(37) Referring to FIG. 4, the Consumer NF 210, AF_1-AF_n 220 and NF 230 are analogous and function substantially the same as the similarly numbered components in FIG. 3. The NWDAF 200 is operable according to an embodiment of the disclosure to deal with different messages and/or data and is therefore operable to provide analytics to the Consumer NF 210 on a per-slice basis.

(38) The messages passed between the various entities are

(39) 4.1 The Consumer NF 210 makes an Observed Service Experience Analytics Subscriptions request (S-NSSAI, any UE) to NWDAF 200. Note that S-NSSAI (single-network slice selection assistance information) is an identifier of a particular slice and “any UE” refers to the presence of any UE on that slice. By setting target of analytics reporting to “any UE”, the Consumer NF 210 obtains analytics for any UE on that network slice. Meanwhile, it is possible to request analytics for one or several UE(s) or a group of UEs as well as any UE on that network slice. In this embodiment, it is assumed that analytics for any UE on that network slice is requested. App ID(s) related to identifier of particular application for which analytics is requested may be included in the Observed Service Experience Analytics Subscription request, as described in FIG. 3. In this case, the Consumer NF 210 may obtain analytics for application(s), which operate(s) on that network slice, corresponding to the App ID(s). Or, the App ID(s) may not be included in the request for analytics, in this case, the Consumer NF 210 obtains analytics for all application operating on that network slice. In this embodiment, it is assumed that the App ID(s) is(are) included in the message 4.1.

(40) 4.2 NWDAF 200 may makes NF data request (QFI, location, App ID(s), and the like) to NF 230.

(41) 4.3 NF 230 provides NF data notification (QFI, location, App ID(s), and the like) to NWDAF 200.

(42) 4.4a NWDAF 200 may requests an Application_1 Service Data Subscription (Mean Opinion Score) to AF_1 220_1. The Application_1 corresponds to one of the App IDs included in the message 4.1. The message 4.4a may include the App ID corresponding to the Application_1.

(43) 4.5a AF_1 220_1 reports Application_1 Service Data Notification (Mean Opinion Score) to NWDAF 200.

(44) 4.4b and 4.5b repeat 4.4a and 4.5a n times for each application AF.

(45) 4.6 NWDAF 200 implements training algorithm to learn from supplied data for a Slice Service Experience.

(46) 4.7 NWDAF 200 provides data analytics to Consumer NF 210, including statistics of past performance or predictions of future performance on a per-slice basis. The data analytics provided is typically either statistics relating to the past e.g., QoS at a certain previous time and/or a prediction of future performance. The prediction may be based on the past performance and/or may make use of additional information available regarding future events.

(47) The numerals (4.1, 4.2, and the like) only indicate corresponding messages, and do not mean that any transmission order. Also, the messages may or may not be transmitted.

(48) The Consumer NF 210 may specify if it wishes to receive data analytics in a particular form e.g., past statistics or prediction of future performance.

(49) As an example, the Consumer NF 210 is the network slice selection function (NSSF). An example of the operation of NSSF is as follows: NSSF monitors Network Slice service experience by subscribing to NWDAF slice service experience analytics for the S-NSSAI(s) in operation (e.g., S-NSSAI_1, S-NSSAI_2, S-NSSAI_3). NSSF may detect a drop of service experience if/when the service experience of S-NSSAI_1 is predicted to drop or the statistics of the past indicate a continuous drop. Then, NSSF may perform slice level load distribution with new UE registrations and/or PDU session establishments and allocates them to a different S-NSSAI (e.g., S-NSSAI_2). As a result, NSSF assists with guaranteeing the service level agreement (SLA) of the Network Slices in the 5GC

(50) In addition, in slice level load distribution, based on the service experience analytics on the network slice(s), NSSF may perform slice selection efficiently. More specifically, when a UE needs to register with the network to get authorized to receive services, the UE initiates the registration procedure by transmitting, to an access and mobility management function (AMF), a registration request. AMF subscribes the Network slice information from NSSF by invoking Nnssf NSSelection Get service operation. NSSF collects Network Slice service experience by subscribing to NWDAF slice service experience analytics for the S-NSSAI(s) (e.g., S-NSSAI_1, S-NSSAI-2, S-NSSAI3 and the like), as described above. Based on the service experience(s) corresponding to the S-NSSAI(s), NSSF efficiently selects the network slice for serving the UE and notifies information on the selected network slice to AMF.

(51) The above examples illustrate how a consumer NF 210 may benefit from improved data analytics at a slice level, which can not only improve user experience, but also improve overall network performance by ensuring a better load distribution and allocation of finite resources.

(52) Examples of NF (network data provider) 130, 230 entities include access and mobility function (AMF), session management function (SMF), user plane function (UPF).

(53) By comparing FIGS. 3 and 4, the different parameters required in order to implement an embodiment of the disclosure are clear. In particular, the use of S-NSSAI in relation to any UE makes use of the defined slice identifier, which has previously been unused in the provision of analytics.

(54) An advantage of performing analytics provision in this way, away from the OAM, is that the OAM can often be a bottleneck in the network and by performing these operations in the Control Plane (CP), overall network performance can be enhanced. Furthermore, the OAM can be inflexible and embodiments of the disclosure may be more easily adapted to meet the needs of network operators.

(55) By providing analytics according to an embodiment of the invention, NFs are able to leverage statistics and predictions to thereby replace or complement functionality previously provided by the OAM.

(56) Further, embodiments of the disclosure are able to differentiate between observed service experience for application performance and for UE (or group of UEs) performance.

(57) Per-slice metrics are derived by means of per-UE observed service experience values.

(58) By means of the embodiment shown in FIG. 4, it is possible to determine slice-level analytics by utilizing observed service experience for applications as well as observed service experience analytics for a single UE or group of UEs. This is by virtue of the new parameters introduced and described in relation to FIG. 4.

(59) Furthermore, embodiments of the disclosure permit multi-application aggregation for slice QoE analytics by means of a mechanism to aggregate application observed service experience analytics to obtain slice-wide analytics in control plane, CP.

(60) Still further, multi-UE multi-application slice QoE analytics mapping and aggregation are provided by means of a mapping of the set of UEs and the set of applications to a single slice. In addition, a mechanism is provided to aggregate observed service analytics for a UE or group of UEs to obtain slice-wide analytics in control plane, CP.

(61) Embodiments of the disclosure utilize observed service experience to derive slice-level analytics at the NWDAF 200. This is achieved by the NWDAF 200 requesting the necessary data in relation to applications and/or UEs.

(62) In an embodiment of the disclosure, QoE analytics can be used to guarantee a service level agreement (SLA) per slice. This can be done either by aggregating applications service experience over the same slice and/or by mapping and aggregating service experience by a set of UEs using a number of applications over the same slice.

(63) In another embodiment of the disclosure, observed service experience analytics are provided for applications, and slice QoE analytics are derived by averaging. In this alternative, slice-wide analytics are derived by employing observed service experience analytics for a set of applications. An aggregation mechanism (e.g., averaging) is further used to derive a slice QoE metric as data analytics.

(64) A particular problem which is addressed and overcome by embodiments of the disclosure is that prior art observed service experience output analytics are not suitable for per-slice QoE measurements. This is because deriving a suitable slice QoE metric in multi-UE multi-application scenarios over a single slice requires an Application-UE mapping, yet no such mapping is provided as analytics output in the prior art. In the prior art, attempts have been made to address this shortcoming by providing a list of Subscription Permanent Identifier (SUPIs) for which the analytics is requested, as well as a list of applications on the slice, but no mapping from applications to UEs is provided. As such, a slice QoE metric derived using prior art analytics derived from such output analytics would be incorrect since the request may be just for a subset of UEs.

(65) In a still further embodiment of the disclosure, there is included a mapping of UEs and applications to the slice target of the optimization in the slice QoE analytics, obtained through observed user experience. The mapping can be performed by providing the following structure of output parameters: S-NSSAI is given as output for observed service experience A list of applications is provided for that slice, each of which contains the list of SUPIs utilizing such slice The observed service experience is provided as an output parameter of that list

(66) As an alternative, IDs of registered subscribers to the slice may be also provided.

(67) To aggregate per-UE per-Application measurements, averaging may be used. The averaging may be a simple arithmetic averaging, use of a media value, Root Mean Square averaging or any form of averaging suitable in the circumstances.

(68) FIGS. 5 and 6 are analogous to FIGS. 3 and 4 respectively and show call flows in a manner typically used in the applicable standards specifications.

(69) FIG. 5 illustrates a message flow according to an embodiment of the disclosure.

(70) Referring to FIG. 5, the prior art call flows and relate to the prior art system shown in FIG. 3.

(71) FIG. 6 illustrates a message flow according to an embodiment of the disclosure.

(72) Referring to FIG. 6, in operation 1, the consumer 210 requests the Analytics ID “Service Experience” for all UEs or a group of UEs on a particular Network Slice, identified by an S-NSSAI.

(73) In operation 2a, NWDAF 200 may subscribes to the network data from NF 230 by invoking Nnf_EventExposure_Subscribe service operation with the Event ID.

(74) In addition, service experience data may need to be collected from multiple Applications.

(75) In operations 2b and 2c, if each Application is hosted in a separate AF, NWDAF 200 may subscribes the service data in Table 1 from the different AFs (220_1, 220_2, and the like) by invoking Nnef_EventExposure_Subscribe or Naf_EventExposure_Subscribe services for each Application (Event ID=Service Data, Event Filter information=(Application ID, Area of Interest), Target of Event Reporting=Any UE) as defined TS 23.502. FIG. 6 shows an example procedure with two AFs 220_1, 220_2. If one AF provides the service experience data of multiple Applications, the set of Application IDs is provided by NWDAF 200 to the AF with the Naf_EventExposure_Subscribe service operation, as defined TS 23.502.

(76) TABLE-US-00001 TABLE 1 Information Description Application ID To identify the service and support analytics per type of service (the desired level of service) IP filter Identify a service flow of the information UE for the application Locations of Locations of application represented Application by a list of DNAI(s). The NEF 240 may map the AF-Service-Identifier information to a list of DNAI(s) when the DNAI(s) being used by the application are statically defined. Service Refers to the QoE per service flow as Experience established in the SLA and during on boarding. It can be either e.g., MOS or video MOS as specified in ITU-T P.1203.3 [11] or a customized MOS Timestamp A time stamp associated to the Service Experience provided by the AF, mandatory if the Service Experience is provided by the ASP.

(77) With the data received from at least one AF 220_1, 220_2 (directly or via NEF 240), (and possibly from at least one NF 230), NWDAF 200 provides data analytics to the consumer 210 in operation 3, including statistics of past performance or predictions of future performance on a per-slice basis.

(78) The statistics of past performance are provided as Table 2 below.

(79) TABLE-US-00002 TABLE 2 Information Description S-NSSAI Identifies the Network Slice for which analytics information is provided. ServiceExperience List of observed service experience (1 . . . n) information for each Application. >Application ID Identification of the application. > Service Type of Service Experience analytics, Experience Type e.g., on voice, video, other. >Service Service Experience over the Analytics Experience target period (average, variance). >SUPI list List of SUPI(s) for each application, (1 . . . n) applicable only to detailed Service Experience. >Ratio Estimated percentage of UEs with similar service experience (in the group, or among all UEs). >Spatial Area where the estimated Service validity Experience applies. If Area of Interest information was provided in the request or subscription, spatial validity may be a subset of the requested Area of Interest. >Validity period Validity period as defined in clause 6.1.3. Slice service Service experience across applications experience on a Network Slice over the Analytics target period (average, variance).

(80) The predictions of future performance are provided as Table 3 below.

(81) TABLE-US-00003 TABLE 3 Information Description S-NSSAI Identifies the Network Slice for which analytics information is provided. ServiceExperience List of observed service experience (1 . . . n) information for each Application. >Application ID Identification of the application. >Service Type of Service Experience analytics, Experience Type e.g., on voice, video, other. >Service Service Experience over the Analytics target period Experience (average, variance). >SUPI list List of SUPI(s) for each application, (1 . . . n) applicable only to detailed Service Experience. >Ratio Estimated percentage of UEs with similar service experience (in the group, or among all UEs). >Spatial Area where the estimated Service validity Experience applies. If Area of Interest information was provided in the request or subscription, spatial validity may be a subset of the requested Area of Interest. >Validity period Validity period as defined in clause 6.1.3. Slice service Service experience across applications experience on a Network Slice over the Analytics target period (average, variance).

(82) FIG. 7 illustrates a block diagram of an entity performing network data analytics function (NWDAF) according to an embodiment of the disclosure.

(83) Referring to FIG. 7, an entity performing NWDAF 700 of an embodiment includes a transceiver 702, a memory 704 and a controller 706.

(84) The transceiver 702 is capable of transmitting/receiving signals to/from other entities.

(85) The memory 704 is capable of storing at least one of the following: information related to the entity performing NWDAF 700 and information transmitted/received via the transceiver 702.

(86) The controller 706 is capable of controlling operations of the entity performing NWDAF 700. The controller 706 is capable of controlling the entity performing NWDAF to perform operations related to the entity performing NWDAF as described in the embodiments.

(87) FIG. 8 illustrates a block diagram of an entity performing network function (NF) according to an embodiment of the disclosure.

(88) Referring to FIG. 8, an entity performing NF 800 of an embodiment includes a transceiver 802, a memory 804, and a controller 806.

(89) The transceiver 802 is capable of transmitting/receiving signals to/from other entities.

(90) The memory 804 is capable of storing at least one of the following: information related to the entity performing NF 800 and information transmitted/received via the transceiver 802.

(91) The controller 806 is capable of controlling operations of the entity performing NF 800. The controller 806 is capable of controlling the entity performing NF to perform operations related to the entity performing NF as described in the embodiments.

(92) At least some of the example embodiments described herein may be constructed, partially or wholly, using dedicated special-purpose hardware. Terms, such as ‘component’, ‘module’ or ‘unit’ used herein may include, but are not limited to, a hardware device, such as circuitry in the form of discrete or integrated components, a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), which performs certain tasks or provides the associated functionality. In some embodiments of the disclosure, the described elements may be configured to reside on a tangible, persistent, addressable storage medium and may be configured to execute on one or more processors. These functional elements may in some embodiments include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Although the example embodiments have been described with reference to the components, modules and units discussed herein, such functional elements may be combined into fewer elements or separated into additional elements. Various combinations of optional features have been described herein, and it will be appreciated that described features may be combined in any suitable combination. In particular, the features of any one example embodiment may be combined with features of any other embodiment of the disclosure, as appropriate, except where such combinations are mutually exclusive. Throughout this specification, the term “comprising” or “comprises” means including the component(s) specified but not to the exclusion of the presence of others.

(93) Attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference.

(94) All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the operations of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or operations are mutually exclusive.

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

(96) The disclosure is not restricted to the details of the foregoing embodiment(s). The disclosure extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the operations of any method or process so disclosed.

(97) While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.