Patent ID: 12218809

DETAILED DESCRIPTION

FIG.1, discussed below, and the various embodiments used to describe the principles of the present 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 present disclosure may be implemented in any suitably arranged system or device.

According to the present disclosure there is provided a method, as set forth in the appended claims. Also provided is a network. Other features of the disclosure will be apparent from the dependent claims, and the description that follows.

The network data analytics function (NWDAF) provides Network Data Analytics Function Services for a 5G network or system, as defined in 3GPP TS 23.288 (Rel-16 NWDAF), which is incorporated herein in entirety by reference.

Observed service experience analytics is supported in Rel-16 NWDAF. It was agreed to use the same analytics type to provide service experience analytics for an application and for a network slice.

Service experience analytics are derived using UE-level measurements; both types (i.e., service experience analytics for an application and for a network slice) can use a single UE, a group of UEs, or all UEs (using the application/slice). However, it does not make sense to derive network slice service experience using a single UE metric.

However, it is not possible to distinguish between the two types of service experience analytics from a subscription/request service definition. Furthermore, multiple applications not on the same network slice are not supported.

Hence, there is a need to improve providing of service experience analytics.

Method

The first aspect provides a method of providing service experience analytics in a network, the method comprising:requesting or subscribing, by a service consumer from or to a network data analytics function (NWDAF) of the network, service experience analytics for one or more application(s) and/or service experience analytics for one or more network slice(s), via a request or a subscription;determining, by the NWDAF, whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the request or the subscription;providing, by the NWDAF to the service consumer, the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), according to a result of the determining.

In this way, service experience analytics discrimination for NWDAF is provided, since the NWDAF determines whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the request or the subscription. It should be understood that the request or the subscription may not explicitly identify or does not explicitly identify one or more application(s) and/or one or more network slice(s) for which the service experience analytics are requested or subscribed. In one example, the request or the subscription does not explicitly identify one or more application(s) and/or one or more network slice(s) for which the service experience analytics are requested or subscribed. That is, the request or the subscription may at most only implicitly identify one or more application(s) and/or one or more network slice(s), such that one or more application(s) and/or one or more network slice(s) for which the service experience analytics are requested or subscribed must be determined (i.e., established, worked out) from the request or the subscription. In one example, the request or the subscription at most only implicitly identifies one or more application(s) and/or one or more network slice(s) for which the service experience analytics are requested or subscribed. In other words, the NWDAF discriminates between the two types of service experience analytics (i.e., for an application and for a network slice), thereby enabling output of corresponding service experience analytics, for example by adaptation of all data inputs and output analytics so that the discrimination can be carried out at by the NWDAF. That is, the NWDAF selectively provides the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on (for example according to, using, determined from) the request or the subscription.

In one example, the service consumer is a network function (NF) or an operations, administration and maintenance (OAM).

In summary, the method according to the first aspect may comprise inter alia:1. Specification of which event filters are mandatory and which event filters are not mandatory, when a service consumer requests/subscribes to i) service experience analytics for an application, and ii) service experience analytics for a network slice; and/or2. A mechanism allowing differentiation of areas of interest when the service experience analytics are requested/subscribed for an application and for a network slice. For example, if the two types of analytics are requested with different areas of interest, two requests/subscriptions instead may be required; and/or3. Adaptation of output analytics formatting to allow for NWDAF to provide i) service experience analytics for a network slice only; ii) service experience analytics for an application only; and iii) service experience analytics for both a network slice and application(s); and/or4. Other additional minor alignments (e.g., unfeasibility to provide service experience for a network slice based only on one UE/SUFI, possibility of providing multiple service experience analytics for multiple applications without a linkage to the network slice analytics, etc.).

Particularly, according to Rel-16 NWDAF:1. There is no way to distinguish between the two types of service experience analytics from the subscription/request service definition;2. Input mandatory requirements for each type of analytics subscription/request are not mentioned, hence the two analytics types cannot be well differentiated;3. Multiple applications not on the same network slice are not properly supported when the service consumer requests service experience analytics for both applications and network slice;4. Output analytics tables should be designed to account for either type only or both;5. Location considerations: need to specify what to do when the area of interests for application and network slice are not the same (missing from Rel-16 NWDAF);6. There remains a need to specify how NWDAF knows when UE IDs need to be retrieved since “any UE” may apply for an application too.
Requesting or Subscribing.

The method comprises requesting or subscribing (also referred to as requesting/subscribing), by the service consumer from or to the NWDAF of the network, the service experience analytics for one or more application(s) and/or service experience analytics for one or more network slice(s), via the request or the subscription.

It should be understood that the method thus comprises:requesting, by the service consumer from the NWDAF of the network, the service experience analytics for one or more application(s) and/or service experience analytics for one or more network slice(s), via the request; orsubscribing, by the service consumer to the NWDAF of the network, the service experience analytics for one or more application(s) and/or service experience analytics for one or more network slice(s), via the subscription.

In one example, the request or the subscription indicates: analytics filter information and target of analytics reporting. That is, the method may provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), using the analytics filter information, for example to determine whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), and the target of analytics reporting, for example to define output of the service experience analytics for one or more application(s) and/or service experience analytics for one or more network slice(s).

In one example, the request or the subscription indicates: (i) an analytics ID set to “service experience”; (ii) a target of analytics reporting selected from: one or more globally unique subscription permanent identifier (SUPI(s)); one or more internal group identifier(s); or “any UE”; (iii) analytics filter information; and optionally, (iv) a maximum number of objects and a maximum number of SUPIs; and

wherein determining, by the NWDAF, whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the request or the subscription, comprises determining, by the NWDAF, whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the target of analytics reporting and the analytics filter information indicated in the request or the subscription.

In one example, requesting or subscribing, by the service consumer from or to the NWDAF of the network, the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), via the request or the subscription, comprises requesting or subscribing, by the service consumer from or to the NWDAF of the network, the service experience analytics for one or more application(s) and the service experience analytics for one or more network slice(s) via separate requests or separate subscriptions, if different values of the target of analytics reporting or the analytics filter information are required for the separate requests or the separate subscriptions. For example, if service experience for both application(s) and network slice is desired but the target of analytics reporting or analytics filter information values (e.g., area of interest) need to be different, separate subscriptions/requests may be provided by the service consumer. That is, the method may manage a request or a subscription for one or more network slice(s) and/or one or more application(s) where each of the requests or subscriptions has different analytics filter information values.

By way of example, updates of the Rel-16 NWDAF specification enabling discrimination according to the method according to the first aspect is described below.

Rel-16 NWDAF specifies how the NWDAF can provide observed service experience (i.e., average of observed service MoS and/or variance of observed service MoS indicating service MOS distribution for services such as audio-visual streaming as well as services that are not audio-visual streaming such as V2X and web browsing services) analytics, in the form of statistics or predictions, to a service consumer. The service consumer may be an NF (e.g., PCF), or the OAM. The observed service experience analytics may provide one or both of the following:Service experience for a network slice: service experience for a group of UEs or any UE for a given application or a set of applications or any application (i.e., all applications) in a network slice;Service experience for an application: service experience for a UE or a group of UEs or any UE in an application or a set of applications.

Therefore, the observed service experience may be provided in Rel-16 NWDAF individually per UE or group of UEs, or globally, averaged per application or averaged across a set of applications on a network slice.

Discrimination according to the method according to the first aspect may be achieved by updating the Rel-16 NWDAF specification such that the service consumer of these analytics indicates in the request or subscription:(i) Analytics ID set to “service experience”;(ii) The target of analytics reporting: one or more SUPI(s) or internal group identifier(s), or “any UE”;(iii) Analytics filter information e.g., as defined in Table 1; and(iv) optionally, maximum number of objects and maximum number of SUPIs.
Analytics Filter Information.

Service experience analytics discrimination may be achieved by specifying which event filters of the analytics filter information are mandatory, as described below.

In one example, the analytics filter information defines respective application ID(s) identifying one or more application(s) for which the service experience analytics are requested or subscribed; andwherein determining, by the NWDAF, whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the target of analytics reporting and the analytics filter information indicated in the request or the subscription, comprises determining, by the NWDAF, to provide the service experience analytics for one or more application(s) identified by the respective application ID(s).

That is, if one or more application ID(s) identifying one or more application(s) are defined by the analytics filter information, the service experience analytics are provided for one or more application(s) identified by the respective application ID(s). In other words, one or more application ID(s) are mandatory if service experience analytics are to be provided for one or more application(s). That is, the method may differentiate which analytics filter information is mandatory for each type of service experience analytics (e.g., application ID for application service experience, S-NSSAI for network slice service experience). It should be understood that if one or more application ID(s) are defined by the analytics filter information, the rest of the analytics filter information applies to any network slice (i.e., all network slices) for one or more application(s) identified by the respective application ID(s). Conversely, it should be understood that if no application ID(s) are defined by the analytics filter information, the rest of the analytics filter information applies to any application (i.e., all applications) for one or more network slice(s) identified by the respective S-NSSAI(s).

In one example, the Analytics Filter Information defines respective S-NSSAI(s) identifying one or more network slice(s) for which the service experience analytics are requested or subscribed; andwherein determining, by the NWDAF, whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the target of analytics reporting and the analytics filter information indicated in the request or the subscription, comprises determining, by the NWDAF, to provide the service experience analytics for one or more network slice(s) identified by the respective S-NSSAI(s).

That is, if one or more S-NSSAI(s) identifying one or more network slice(s) are defined by the analytics filter information, the service experience analytics are provided for one or more network slice(s) identified by the respective S-NSSAI(s). In other words, one or more S-NSSAI(s) are mandatory if service experience analytics are to be provided for one or more network slice(s). It should be understood that if one or more network slice(s) are defined by the analytics filter information, the rest of the analytics filter information applies to any application (i.e., all applications) for one or more network slice(s) identified by the respective S-NSSAI(s). Conversely, it should be understood that if no S-NSSAI(s) are defined by the analytics filter information, the rest of the analytics filter information applies to any network slice (i.e., all network sliced) for one or more application(s) identified by the respective application ID(s).

It should be understood that if one or more application ID(s) are defined by the analytics filter information and one or more network slice(s) are defined by the analytics filter information, the rest of the analytics filter information applies to applies to any network slice (i.e., all network slices) for one or more application(s) identified by the respective application ID(s) and to any application (i.e., all applications) for one or more network slice(s) identified by the respective S-NSSAI(s).

In one example, the analytics filter information defines an area of interest for which the service experience analytics are requested or subscribed; andwherein providing, by the NWDAF to the service consumer, the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s) comprises providing, by the NWDAF to the service consumer, the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s) for the area of interest.
Determining.

The method comprises determining, by the NWDAF, whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the request or the subscription. That is, the NWDAF discriminates, based on the request or the subscription, whether to provide:1. the service experience analytics for one or more application(s); or2. the service experience analytics for one or more network slice(s); or3. the service experience analytics for one or more application(s) and the service experience analytics for one or more network slice(s).

It should be understood that the request or the subscription may not explicitly identify or does not explicitly identify one or more application(s) and/or one or more network slice(s) for which the service experience analytics are requested or subscribed. In one example, the request or the subscription does not explicitly identify one or more application(s) and/or one or more network slice(s) for which the service experience analytics are requested or subscribed. That is, the request or the subscription may at most only implicitly identify one or more application(s) and/or one or more network slice(s), such that one or more application(s) and/or one or more network slice(s) for which the service experience analytics are requested or subscribed must be determined (i.e., established, worked out) from the request or the subscription. In one example, the request or the subscription at most only implicitly identifies one or more application(s) and/or one or more network slice(s) for which the service experience analytics are requested or subscribed.

In one example, determining, by the NWDAF, whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the target of analytics reporting and the analytics Filter Information indicated in the request or the subscription, comprises determining, by the NWDAF, to provide the service experience analytics for one or more application(s) and the service experience analytics for one or more network slice(s), if the NWDAF is unable to determine whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the request or the subscription. For example, if no application ID is provided, the rest of the analytics filter information applies to any application (i.e., all applications) in one or more network slice(s). Conversely, for example, if no S-NSSAI is provided, the rest of the analytics filter information applies to any network slice (i.e., all network slices) for one or more application(s). That is, the method may determine the service experience analytics to be provided when, for example even when, the NWDAF cannot determined (for example identify) whether the request or subscription is for one or more application(s) or one or more network slice(s).

In one example, determining, by the NWDAF, whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the request or the subscription, comprises determining, by the NWDAF, to provide the service experience analytics for only one or more application(s) or the service experience analytics for only one or more network slice(s), based on the request or the subscription.

Providing.

The method comprises providing, by the NWDAF to the service consumer, the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), according to the result of the determining.

In one example, the result of the determining specifies providing, by the NWDAF to the service consumer, the service experience analytics for one or more application(s), for example for only one or more application(s). In one example, the result of the determining specifies providing, by the NWDAF to the service consumer, the service experience analytics for one or more network slice(s), for example for only one or more network slice(s). In one example, the result of the determining specifies providing, by the NWDAF to the service consumer, the service experience analytics for one or more application(s) and for one or more network slice(s).

In one example, providing, by the NWDAF to the service consumer, the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), according to a result of the determining comprises notifying the service experience analytics to the service consumer as specified in 3GPP TS 23.288. For example, the NWDAF may or shall notify the result of the analytics to the consumer as specified in 3GPP TS 23.288.

In one example, providing, by the NWDAF to the service consumer, the service experience analytics for one or more application(s) comprises providing, by the NWDAF to the service consumer, the service experience analytics for one or more application(s), wherein the service experience analytics for one or more application(s) comprises service experience statistics for one or more application(s) and/or service experience predictions for one or more application(s). That is, the service experience analytics may include the service experience statistics and/or the service experience predictions for one or more application(s).

In one example, the service experience statistics for one or more application(s) and/or the service experience predictions for one or more application(s) respectively include a spatial validity thereof and/or a validity period thereof. That is, the spatial validity (i.e., the area for which these service experience analytics for one or more application(s) applies) and/or the validity period (i.e., the validity period for which these service experience analytics for one or more application(s) applies such as defined in REL-16 NWDAF) may be defined.

In one example, the service experience statistics for one or more application(s) and/or the service experience predictions for one or more application(s) respectively include service experience statistics for each application of one or more application(s) and/or the service experience predictions for each application of one or more application(s). That is, these service experience analytics may be provided for each application of one or more application(s), for example from 0 to max applications (i.e., 0 . . . max, where max is a maximum allowed size of the list). In contrast, conventionally, the service experience statistics and the service experience predictions included a single list, such that if the service experience analytics were requested for a single application, the service experience analytics were nevertheless provided for both the application and the network slice used for that application, together with others according instead to the method according to the first aspect, if the service experience analytics are determined to be only provided for a single application, a size of the network slice list is 0. Similarly, if the service experience analytics are determined to be only provided for a single network slice, a size of the application list is 0. That is, the method may provide service experience analytics distinguishing service experience values for a network slice and service experience values for an application.

In one example, providing, by the NWDAF to the service consumer, the service experience analytics for one or more network slice(s) comprises providing, by the NWDAF to the service consumer, the service experience analytics for one or more network slice(s), wherein the service experience analytics for one or more network slice(s) comprises service experience statistics for one or more network slice(s) and/or service experience predictions for one or more network slice(s). That is, the service experience analytics may include the service experience statistics and/or the service experience predictions for one or more network slice(s).

In one example, the service experience statistics for one or more network slice(s) and/or the service experience predictions for one or more network slice(s) respectively include a spatial validity thereof and/or a validity period thereof. That is, the spatial validity (i.e., the area for which these service experience analytics for one or more network slice(s) applies) and/or the validity period (i.e., the validity period for which these service experience analytics for one or more network slice(s) applies such as defined in REL-16 NWDAF) may be defined.

In one example, the service experience statistics for one or more network slice(s) and/or the service experience predictions for one or more network slice(s) respectively include service experience statistics for each network slice of one or more network slice(s) and/or the service experience predictions for each network slice of one or more network slice(s). That is, these service experience analytics may be provided for each network slice of one or more network slice(s), for example from 0 to max network slices (i.e., 0 . . . max, where max is size of list). In contrast, conventionally, the service experience statistics and the service experience predictions included a single list, such that if the service experience analytics were requested for a single network slice, the service experience analytics were nevertheless provided for both the network slice and for all application(s) using the network slice. According instead to the method according to the first aspect, if the service experience analytics are determined to be only provided for a single network slice, a size of the application list is 0. Similarly, if the service experience analytics are determined to be only provided for a single Application, a size of the network slice list is 0. That is, the method may provide service experience analytics distinguishing service experience values for a network slice and service experience values for an application.

In one example, the service experience statistics for the application(s) or the service experience statistics for the network slice(s) are provided individually per UE or group of UEs, or globally, averaged per application or averaged across a set of applications on a network slice.

Network.

The second aspect provides a network comprising a network data analytics Function (NWDAF) and a service consumer;wherein the service consumer is configured to request or subscribe, from or to the NWDAF, service experience analytics for one or more application(s) and/or service experience analytics for one or more network slice(s), via a request or a subscription; andwherein the NWDAF is configured to:determine whether to provide the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), based on the request or the subscription; andprovide, to the service consumer, the service experience analytics for one or more application(s) and/or the service experience analytics for one or more network slice(s), according to a result of the determining.

The network, the NWDAF, the service consumer, the requesting, the subscribing, the request, the subscription, the determining, the providing and/or the result of the determining may be as described with respect to the first aspect.

The network may be configured to implement any method step as described with respect to the first aspect.

In one example, the network comprises and/or is a 5G network.

In one example, the service consumer is a network function (NF) or an operations, administration and maintenance (OAM).

Throughout this specification, the term “comprising” or “comprises” means including the component(s) specified but not to the exclusion of the presence of other components. The term “consisting essentially of” or “consists essentially of” means including the components specified but excluding other components except for materials present as impurities, unavoidable materials present as a result of processes used to provide the components, and components added for a purpose other than achieving the technical effect of the disclosure, such as colourants, and the like.

The term “consisting of” or “consists of” means including the components specified but excluding other components.

Whenever appropriate, depending upon the context, the use of the term “comprises” or “comprising” may also be taken to include the meaning “consists essentially of” or “consisting essentially of”, and also may also be taken to include the meaning “consists of” or “consisting of”.

The optional features set out herein may be used either individually or in combination with each other where appropriate and particularly in the combinations as set out in the accompanying claims. The optional features for each aspect or exemplary embodiment of the disclosure, as set out herein are also applicable to all other aspects or exemplary embodiments of the disclosure, where appropriate. In other words, the skilled person reading this specification should consider the optional features for each aspect or exemplary embodiment of the disclosure as interchangeable and combinable between different aspects and exemplary embodiments.

Analytics Filter Information.

[Table 1] provides an example of how analytics filter information may be adapted to enable service experience analytics discrimination at NWDAF.

Examples of the analytic filter information.MandatoryInformationDescriptionAppNSApplication IDThe identification of the application(s)YN(0...max)for which the analytics information(NOTE 1)is subscribed or requested.S-NSSAIIdentifies the network slice forNYwhich analytics information issubscribed or requested.NSI ID(s)Identifies the network slice instance(s)NNfor which analytics informationis subscribed or requested.Area of InterestIdentifies the Area (i.e., set ofYY(NOTE 2)TAIs), as defined in TS 23.501where the analytics informationis subscribed or requested.Media/applicationIdentifies the Media/applicationNNbandwidthbandwidth requirementof the application.DNNDNN to access the application.NNDNAIIdentifier of a user plane access to oneNNor more DN(s) where applications aredeployed as defined in TS 23.50.NOTE 1: If no application ID is provided, the rest of Analytics Filter information applies to any application (i.e., all applications) in the network slice.NOTE 2: Area of interest is not mandatory for application service experience if target of analytics reporting is not set to “any UE.”An analytics target period that indicates the time window for which the statistics or predictions are requested;In a subscription, the notification correlation ID and the notification target address.

The NWDAF shall notify the result of the analytics to the consumer as specified in 3GPP TS 23.288.

NWDAF collects the network data from AF (directly or via NEF) and from other 5GC NF(s) in order to calculate and provide statistics and predictions on the observed service experience to a consumer NF or to OAM.

Based on the analytics filter information and the target of analytics reporting provided by the service consumer in the analytics subscription or request, NWDAF determines whether service experience analytics should be delivered for i) application(s), ii) network slice, iii) both application(s) and network slice. The details of the discrimination are implementation-specific.

If service experience for both application(s) and network slice is desired but the target of analytics reporting or analytics filter information values (e.g., area of interest) need to be different, separate subscriptions/requests may be provided by the service consumer.

Output Analytics.

By way of example, updates of the Rel-16 NWDAF specification enabling discrimination according to the method according to the first aspect is described below.

The NWDAF services as defined in Rel-16 NWDAF are used to expose the analytics.Service experience statistics information is defined in Table 2 as defined in Rel-16 NWDAF.Service experience predictions information is defined in Table 3 as defined in Rel-16 NWDAF.

This information may be updated, as detailed below:

Rel-16 NWDAF: service experience statistics updated.InformationDescriptionS-NSSAIIdentifies the Network Slice forwhich analyticsinformation is provided.Slice instance serviceList of observed service experienceexperiences (0...max)information for each Network Sliceinstance.>NSI IDIdentifies the Network Sliceinstance within the Network Slice.>Network Slice instanceService experience acrossservice experienceApplications on a Network Sliceinstance over the Analyticstarget period (average, variance).>SUPI list (0...SUPImax)List of SUPI(s) for each slice instanceservice experience.>RatioEstimated percentage of UEs withsimilar service experience (in thegroup, or among all UEs).>Spatial validityArea where the Network Slice serviceexperience analytics applies.>Validity periodValidity period for the Network Sliceservice experience analytics as definedin clause 6.1.3.Application serviceList of observed service experienceexperiences (0...max)information for each Application.>S -NSSAIIdentifies the Network Slice of theApplication>Application IDIdentification of the Application.>Service Experience TypeType of Service Experienceanalytics, e.g., on voice, video, other.>Service ExperienceService Experience over the Analyticstarget period (average, variance).>SUPI list (0...SUPImax)List of SUPI(s) for each applicationservice experience.>RatioEstimated percentage of UEswith similar service experience (inthe group, or among all UEs).>Spatial validityArea where the Application serviceexperience analytics applies.>Validity periodValidity period for the Applicationservice experience analyticsas defined in clause 6.1.3.

Rel-16 NWDAF: service experience predictions.InformationDescriptionS-NSSAIIdentifies the Network Slice for which analyticsinformation is provided.Network SliceList of observed service experienceinstance serviceinformation for eachexperiences (0...max)Network Slice instance.>NSI IDIdentifies the Network Slice instancewithin the Network Slice.>Network Slice instanceService experience across Applicationsservice experienceon a Network Slice instance over theAnalytics target period (average, variance).>SUPI list (0...SUPImax)List of SUPI(s) for each slice instanceservice experience.>RatioEstimated percentage of UEs with similar serviceexperience (in the group, or among all UEs).>Spatial validityArea where the Network Slice service experienceanalytics applies.>Validity periodValidity period for the Network Slice serviceexperience analytics as defined in clause 6.1.3.>Probability assertionConfidence of this prediction.Application serviceList of predicted service experienceexperiences (0...max)information for each Application.>S-NSSAIIdentifies the Network Slice of the Application>Application IDIdentification of the Application.>Service ExperienceType of Service Experience analytics,Typee.g., on voice, video, other.>Service ExperienceService Experience over the Analyticstarget period (average, variance).>SUPI list (0...SUPImax)List of SUPI(s) for each applicationservice experience.>RatioEstimated percentage of UEs with similar serviceexperience (in the group, or among all UEs).>Spatial validityArea where the Application serviceexperience analytics applies.>Validity periodValidity period for the Applicationservice experience analyticsas defined in clause 6.1.3.>Probability assertionConfidence of this prediction.NOTE 1: Based on the service experience analytics discrimination, NWDAF may provide the output analytics in Tables 2 and 3 corresponding to network slice, application, or both.NOTE 2: If multiple network slice instances are not deployed for the S-NSSAI or NSI IDs are not available, only one network slice instance service experience entry is provided. In that case, the NSI ID is not provided and the network slice instance service experience indicates the service experience for the S-NSSAI.NOTE 3: The SUPI list and ratio in the service experience information for an application can be omitted, if the corresponding parameter(s) is/are provided and with the same value(s) in the service experience information for the slice instance which the application belongs to.

The number of service experiences and SUPIs are limited respectively by the maximum number of objects and the maximum number of SUPIs provided as part of analytics reporting information by the NWDAF service consumer.

FIG.1illustrates a network entity according to embodiments of the present disclosure.

Referring to theFIG.1, the network entity100may include a processor110, a transceiver120and a memory130. However, all of the illustrated components are not essential. The network entity100may be implemented by more or less components than those illustrated inFIG.1. In addition, the processor110and the transceiver120and the memory130may be implemented as a single chip according to another embodiment.

The network entity100may correspond to the NWDAF described above.

The aforementioned components will now be described in detail.

The processor110may include one or more processors or other processing devices that control the provided function, process, and/or method. Operation of the network entity100may be implemented by the processor110.

The transceiver120may include a RF transmitter for up-converting and amplifying a transmitted signal, and a RF receiver for down-converting a frequency of a received signal. However, according to another embodiment, the transceiver120may be implemented by more or less components than those illustrated in components.

The transceiver120may be connected to the processor110and transmit and/or receive a signal. The signal may include control information and data. In addition, the transceiver120may receive the signal through a wireless channel and output the signal to the processor110. The transceiver120may transmit a signal output from the processor110through the wireless channel.

The memory130may store the control information or the data included in a signal obtained by the network entity100. The memory130may be connected to the processor110and store at least one instruction or a protocol or a parameter for the provided function, process, and/or method. The memory130may include read-only memory (ROM) and/or random access memory (RAM) and/or hard disk and/or CD-ROM and/or DVD and/or other storage devices.

Although a preferred embodiment has been shown and described, it will be appreciated by those skilled in the art that various changes and modifications might be made without departing from the scope of the disclosure, as defined in the appended claims and as described above.

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.

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

Each feature disclosed in this specification (including any accompanying claims, 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.

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 and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed.

Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.