WO2022032487A1

WO2022032487A1 - Apparatus and methods for coordination of analytics information accessing in communication networks

Info

Publication number: WO2022032487A1
Application number: PCT/CN2020/108484
Authority: WO
Inventors: Clarissa Marquezan; Riccardo Trivisonno; Yang Xin; Mirko Schramm; Xiaobo Wu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2020-08-11
Filing date: 2020-08-11
Publication date: 2022-02-17
Also published as: EP4190122A4; EP4190122A1; CN116134962A

Abstract

The disclosure presents a first entity that obtains Analytics Subscription Information (ASI) via a configuration by a management entity or received from a second entity, wherein the ASI comprises allowed and/or restricted analytics information for a User Equipment and/or a group of UEs that are controlled by a second entity, wherein the allowed and/or restricted analytics information are used for controlling a third entity to interact with a fourth entity. The processor further provides the ASI to a third entity. The second entity obtains ASI and provides the ASI to the first entity. The third entity obtains ASI, and provides a subscription or a request or an unsubscribe request or cancelation request to the fourth entity. The fourth entity obtains, from the third entity, a subscription or a request or an unsubscribe request or a cancelation request, and sends a response to the third entity.

Description

APPARATUS AND METHODS FOR COORDINATION OF ANALYTICS INFORMATION ACCESSING IN COMMUNICATION NETWORKS

TECHNICAL FIELD

The present disclosure relates to the field of communication networks, in particular, to 5 ^th generation mobile or cellular communication (5G) systems (5GS) and networks. The present disclosure is specifically related to coordinate the access to analytics information from a Network Data Analytics Function (NWDAF) consumed by Network Functions (NFs) of a communication network.

BACKGROUND

TS 23.288 defines the analytics framework for the 3GPP 5GS in Release 16 (R16) . TS 23.288 specifies that a Network Function (NF) , Application Functions (AFs) and Operations, Administration, and Maintenance (OAM) are allowed to consume analytics information (e.g., analytics identifications (IDs) ) from the NWDAF.

In TS 23.288 R16, the mechanisms and services for the analytics consumption are defined, as well as types of analytics IDs that can be generated by the NWDAF to support the analytics consumers (e.g., NF, AFs or OAM) to perform their tasks and to improve the performance of their target tasks.

The currently defined analytics IDs that can be produced by the NWDAF and can be consumed by analytics consumers may target the analytics of “any User Equipment (UE) ” , or UE groups, or specific UEs. Therefore, analytics consumers can subscribe or request analytics IDs for specific UEs or group of UEs from the NWDAF, and based on the analytics IDs information received from the NWDAF such analytics consumers may enforce a specific treatment for such UEs or group of UEs.

In essence, an analytics ID output for specific UEs (e.g., a list of UEs) or UE groups (e.g., identification of UE groups or a list of UE groups) , reflect the particular characteristics of the analytics ID (e.g., UE communication, UE Mobility, UE service experience, user data congestion, UE abnormal behavior, etc. ) for such indicated target.

A conventional method allows an AF to influence 5GS NFs. For example, the AF may have the capability to provide to the 5GS NFs different sets of information that can influence charging, traffic routing, Quality of Service (QoS) requirements for sessions of specific UEs, among others as specified in TS 23.501 and TS 23.502.

Regarding AF and analytics framework interactions, the AF may also be allowed to subscribe to analytics IDs generated by the NWDAF, directly or indirectly via a Network Exposure Function (NEF) ; and the AF can provide data to be collected by the NWDAF for analytics generation.

Furthermore conventional methods allow NFs accessing or consuming the analytics IDs from NWDAF, but for some typical scenarios, for example, more than one NF consume the analytics ID from the NWDAF, or a UE moved from one serving NF to a second serving NF, or relocation of the subscription of an analytics ID for specific UE from one first NWDAF to a second NWDAF, conventional methods will lead some problems.

SUMMARY

In view of the scenarios above, coordination between different network elements is needed in order to properly control the usage of one or more analytics IDs for one or more specific UEs or a group of UEs in the mobile network. Embodiments of the present disclosure aim to provide entities and methods for assisting triggering of 5G NFs interactions with the NWDAF in a mobile network. In particular, the embodiments of the disclosure may address the problem of sub-optimal usage of the network resources, of unnecessary signaling for configurations that do not apply to such UEs or group of UEs, and of sub-optimal usage of network resources for fulfilling applications needs.

The objective is achieved by the embodiments of the disclosure as described in the enclosed independent claims. Advantageous implementations of the embodiments of the disclosure are further defined in the dependent claims.

In particular, embodiments of the disclosure provide a mechanism for an AF or the OAM (e.g., second entity) to influence one or more 5GS NFs (e.g., third entity) to interact with the NWDAF (e.g., fourth entity) . The embodiments of the disclosure may enable one or more of the following operations:

● The AF (e.g., via NEF (e.g., second entity) ) may provide information that allows the 5GS to operate with a restricted and/or allowed analytics IDs that can be consumed for specific UEs or group of UEs, optionally, by defining the one or more NFs (types or instances) allowed to consume such analytics ID for specific UEs or group of UEs.

● In case that the AF provides information that is not a direct map among an allowed or restricted analytics ID and specific UEs or groups, and optionally, among one or more NF consumers of an analytics ID, there may exist a control plane entity (e.g., the NEF or the NWDAF) that receives this information and then maps such general descriptions into the precise restricted and/or allowed analytics IDs that can be consumed for specific UEs or a group of UEs, optionally, also by one or more NFs (types or instances) . The restricted and/or allowed analytics IDs that may be consumed for specific UEs or group of UEs, optionally, by defining the one or more NFs (types or instances) that are also allowed and/or restricted to consume such analytics ID for specific UEs or group of UEs is hereinafter referred to as the ASI.

● The ASI may be further stored in a control plane network function (e.g., in the Unified Data Management (UDM) (e.g., first entity) , and it may serve as a trigger for the one or more NFs to request subscription or unsubscription to an analytics IDs to an Analytics Function (e.g., the NWDAF) with inference capability upon UE registration, session management, UE mobility. It may serve as a trigger for the network control function to notify the one or more NFs (e.g., the AMF, SMF, or PCF, which are the NFs so far in 5GS consuming analytics ID within the network operator) about changes in allowed/restricted analytics IDs for specific UEs or group of UEs, optionally defined also per NF consumers of analytics IDs. Moreover, it may also serve as triggers for the network control function to request to an Analytics Function (e.g., the NWDAF) with training capabilities a model training (when analytics id is allowed and not model exist yet) .

Moreover, the embodiments of the disclosure may provide one or more of the following advantages:

● Allowing the coordination of mechanisms used in 5GS and an AF to control UEs and/or group of UEs, thereby limiting the occurrence of racing conditions when AFs and 5GS use analytics ID to treat specific UEs and/or group of UEs.

● Reducing the chances of wrong actions and waste of operator’s resources to specific UEs and/or group of UEs that do not follow the same pattern from majority of UEs in operator networks.

● Reduction of the operation cost for automation and maintenance of the all NFs configurations. Operators do not need to keep track of the analytics ID configuration that each NF instance needs to subscribe for specific UEs and/or group of UEs. This reduced the change management costs of operators. As NFs and UE subscriptions (i.e., new Sim cards) arrive and leave the system, operators need to keep all of the NFs configuration consistent and this has an unneglectable cost. A misconfiguration of analytics IDs associated with UEs and/or group of UEs in different NFs can lead to different treatment of UEs or group of UEs by different NFs in the system.

A first aspect of the present disclosure provides a first entity, wherein the first entity is used in a communication network, and the first entity comprising a processor, configured to obtain Analytics Subscription Information (ASI) via a configuration by a management entity or received from a second entity, wherein the ASI comprises allowed and/or restricted analytics information (e.g., analytics ID) for a UE and/or a group of UEs that are controlled by a second entity, wherein the allowed and/or restricted analytics information are used for controlling a third entity to interact with a fourth entity; and the processor being further configured to provide the ASI to a third entity.

The first entity may be, or may be incorporated in, UDM, NEF, NWDAF, etc. The first entity may be for managing ASI in the control plane of a mobile communication network.

The ASI may be, or may comprise information that, for example, defines the properties (e.g., restricted and/or allowed) of one or more analytics IDs for one or more specific UEs or one or more groups of UEs, and optionally per specific consumer of the analytics IDs. In addition, the ASI may further comprise information about subscriptions to one or more analytics IDs, and identification of the associated consumers of the analytics ID associated with such subscription to the analytics ID at a given point in time.

Furthermore, the ASI may also comprise information about consumer of the ASI, such as identification of the consumer of ASI and reference point information to interact with the consumer of ASI. It may be possible that the identification of the associated consumer of the analytics ID is equivalent to the identification of the consumer of ASI.

Hereinafter, the term analytics ID for one or more specific UEs or one or more groups of UEs is used equivalent to the term subscription or request to an analytics ID with the target of the analytics ID set to the specific UEs or the groups of UEs. Moreover, the definition of the properties (e.g. restricted and/or allowed) of one or more analytics IDs for one or more specific UEs or groups of UEs is presented when introducing such properties below.

The first entity may be able to, for example, obtain the ASI or obtain updated ASI via configuration by a management entity, or via interactions with a second entity. Moreover, the first entity may provide the ASI or the updated ASI to a third entity (e.g., a NF such as AMF or SMF, or PCF) . Further, the first entity may provide to a second entity the identification of any stored ASI.

The ASI may be, for example, obtained directly from second entity (e.g., when the second entity is allowed to directly communicate with the first entity) , or obtained indirectly from second entity (e.g., when the second entity is not allowed to directly communicate with the first entity and there exist an indirect step between the second entity providing the ASI and the first entity obtaining ASI) . An example of directly obtained is when AF can directly send the ASI to UDM (e.g., first entity) .

An example of indirectly obtained may be when AF sends the ASI to NEF and NEF sends the received ASI from AF to UDM. It is possible that UDM applies or not further processing over the received information from ASI. Examples of processing comprise: mapping or translation of information from the AF into information that is understandable by the communication network (e.g., UE IDs according with AF definitions that are mapped to the UE IDs according to the definitions of the communication network) .

The first entity may comprise a circuitry. The circuitry may comprise hardware (e.g., the processor) and software. The hardware may comprise analog or digital circuitry, or both analog and digital circuitry. In some embodiments, the circuitry comprises one or more processors and a non-volatile memory connected to the one or more processors. The non-volatile memory may carry executable program code which, when executed by the one or more processors, causes the device to perform the operations or methods described herein.

In an implementation form of the first aspect, the processor is further configured to provide one or more identifications of the ASI to the second entity.

In a further implementation form of the first aspect, the processor is further configured to receive, from the second entity, a first support information, wherein the first support information comprises mapping between the UE or the group of UEs behavior and a second set of analytics information, wherein the second set of analytics information is used to indicate possible analytics information related to UE or group of UE behavior, and/or generate the ASI based on the obtained first support information.

The first support information may be or may comprise information that may define the requirements from one or more NFs (such as AFs) or the OAM to influence the usage of one or more analytics IDs in the mobile network. The function of the first support information may be to serve as reference for the mapping between the requirements from one or more AFs or the OAM (e.g., in terms of allowed and/or restricted analytics IDs for specific UEs or group of UEs) and analytics IDs available in the communication network and/or the consumers of the analytics IDs per analytics IDs available in the communication network (e.g., in terms of analytics IDs per NF consumer of analytics ID) .

The analytics ID information in the first support information may serve to detect the intersection between the first support information and the second support information (e.g., available analytics ID in the communication network) . The requirement of such an analytics ID being allowed or restricted for one or more specific UEs and or one or more groups of UEs may serve to expand (in case of allowed) or reduce (in case of restricted) the permission of an NF to be able to consume the analytics ID that is expressed in the second support information.

The first support information field may comprise at least one of the following of type of information:

● Identification of Properties Provider: Identification of the entity providing the first support information. Examples of such identification are: IP address, NF ID, Application ID.

● Precise Information: This term defines the allowed or restricted analytics ID for List of UEs or group of UEs. This information can be represented as a tuple: (Analytics ID, Target UEs identification [list of UEs or group of UEs] , requirement [allowed /restricted] ) .

● General description (or Reference Description or Analytics Function-Associated Expected UE Behavior) : defining an UE behavior related to an analytics ID.

One possible implementation of the general description type of first support information fields may be represented by, for example, a tuple (Target UE, (Optional) Network Service, Behavior, and Behavior Property) .

■ The field type “Target UE” in the tuple may denote the UEs identification (e.g., UEs identification or group UE identification) , to which the general description applies.

■ The type of fields “Network Service” in the tuple may relate to the mobile network services that can be enforce by different NFs. This field is optional and when included it may have the function to support the determination of which NF (e.g., AMF if mobility management, SMF if session management, PCF if QoS management) is related to the Behavior field. Therefore, the “Network service” supports the definition of which NF consumer of analytics ID the allowed and restricted analytics ID should apply.

■ The type of field “Behavior” may define the relationship (e.g., mapping) between one or more analytics IDs (e.g., defined in 3GPP 5G architecture in TS 23.288 such as UE abnormal Behavior)

■ The type of field Behavior Property may define if the defined behavior is expected (e.g., regular Behavior) or if a deviation from Behavior is expected (e.g., Irregular Behavior) . An expected behavior, defines that the associated analytics ID to the behavior is allowed to be consumed; a deviation from expected behavior defines a restriction to consume the analytics ID.

Examples of values for the tuple of description in the first support information fields are described below:

■ (UE ID#1, Session Management, Communication Patterns, Deviation Expected (e.g., Irregular) )

■ Behavior “Communication Patterns” is mapped to analytics ID “UE Communication” , the deviation expected indicated that such analytics ID should not be generated for the UE or group of UEs, because, for instance, the UE or group of UE has irregular communication patterns

■ (List of UEs (ID#2, ID#3, .. ) , Mobility Management, Mobility Patterns, Irregular)

■ Behavior “Mobility Patterns” is mapped to analytics ID “UE Mobility”

■ (UE Group #A, Session Management, Frequent session request, Regular)

■ Behavior “Frequent session request” is mapped to analytics ID “UE abnormal behavior”

■ When an entity is supporting the usage of general descriptions with the Behavior fields, there is also the need for such entity to have the mapping between of the behavior field and one or more specific analytics IDs.

The second support information may be or may comprise information that may define the supported (e.g., available) analytics ID in the communication network, or the mapping between available one or more analytics IDs and consumers of these analytics IDs being able to consume such analytics in the communication network.

The function of the second support information is to serve as reference for the mapping between the requirements from one or more AFs or the OAM (e.g., in terms of allowed and/or restricted analytics IDs for specific UEs or group of UEs) which is enclosed in the first support information and the available analytics IDs in a communication network and/or the consumers of one or more analytics IDs per available analytics ID (e.g., in terms of analytics ID per consumer of the analytics ID) which is enclosed in the second support information. In the case that the second support information defines the supported one or more analytics IDs, this means that such analytics IDs can be consumed by any consumer.

In this case, a restricted or allowed analytics ID for specific UEs or group of UEs would apply to any NF. In the case that the second support information defines the mapping between available analytics IDs and NF consumers of analytics IDs, this means that allowing or restricting could be applied per analytics ID, per NF consumer of analytics ID.

The analytics ID in the second support information may assist detecting the intersection between the first and the second support information. The requirement of such analytics ID being allowed or restricted for a specific UEs and or group of UEs may assist to expand (in case of allowed) or reduce (in case of restricted) the permission of the NF able to consume the analytics ID that is expressed in the second support information.

The second support information fields may comprise the following information:

■ Tuple comprising (Identification of NF consumer of analytics IDs [type or instance]

■ List of supported analytics type identification (e.g., analytics IDs) ) .

Moreover, the request for second support information fields may define the properties or filters to be used for matching the properties or filters received in the request to the existing second support information. The request for second support information comprises any combination of the following fields:

■ Analytics type identification (e.g., Analytics ID)

■ NF consumer of analytics ID identification (e.g., NF type such as AMF or SMF or PCF Type; or NF instance such as AMF #1)

In a further implementation form of the first aspect, the processor being further configured to receive, from the third entity, a request for an ASI for a specific UE or for a specific group of UEs, and/or send an ASI response message to the third entity, the ASI response message comprising one or more ASI or an indication of no available ASI for that received request.

In a further implementation form of the first aspect, the request for ASI comprises one or more of:

- identification of the ASI,

- identification of the analytics information,

- identification of one or more UEs,

- identification of one or more group of UEs,

- identification of the second entity that provided the ASI,

- identification of the third entity related to the ASI,

- identification of an existing subscription or request to analytics information,

- identification of reference point to communicate with the third entity.

In a further implementation form of the first aspect, the ASI comprises one or more of:

- identification of the ASI,

- identification of second entity providing the ASI or the first support information,

- identification of third entity consuming the ASI and/or consuming the analytics information,

- allowed analytics information for a list of UEs or the group of UEs, or allowed analytics information for the list of UEs or the group of UEs per consumer of the analytics information,

- restricted analytics information for the list of UEs or the group of UEs, or restricted analytics information for the list of UEs or the group of UEs per consumer of the analytics information,

- identification of reference point to communicate with the third entity consuming the ASI and/or consuming the analytics information,

- identification of reference point to communicate with the second entity providing the ASI or first support information,

- identification of the analytics information subscription or request related to the third entity,

- one or more fields related to the subscription for an analytics information (e.g., analytics filter information, analytic reporting information, target of analytics reporting) .

In a further implementation form of the first aspect, the processor being further configured to obtain updated ASI via a configuration by a management entity or received from the second entity, and/or send a notification message to the third entity, the notification message indicating a change of the ASI.

For example, there may be two possible ways as follows:

● The changed ASI is included in the notification.

● Only indication of changing and the third entity will request for the updated ASI.

In addition, if there is no consumer of ASI for the obtained updated ASI, the first entity may not need to notify any third entity about the changed ASI.

In a further implementation form of the first aspect, the processor being further configured to receive Analytic Context Information (ACI) from the third entity, wherein the ACI comprises at least one of: an association of a third entity with an ASI, and an association of an ASI obtained by the third entity with an existing subscription or existing request or unsubscription or cancelation request for the third analytics information requested by the third entity from the fourth entity, where the third analytics information is based on the analytics information of the ASI, and is used in the interactions between the third entity and fourth entity or vice-versa.

The ACI may represents the association a certain NF with and ASI or a certain NF consumer instance of analytics ID with a subscription or request or unsubscription or cancelation request to a certain analytics ID at a given time. The function of the ACI is to enable the association of an ASI with a NF consumer of ASI, or the association of an ASI with an existing subscription or request or unsubscription or cancelation request for an analytics ID by an NF consumer of such analytics ID. The ACI is sent from the third entity in order to allow the first entity to have the proper information to notify the third entity about changes in the ASI. Furthermore, the analytics context information is related to the ASI. For instance, the ACI is a subset of information from ASI.

In a further implementation form of the first aspect, wherein the ACI comprises one or more of:

- identification of the third entity,

- identification of a reference point (e.g., interface or services) to communicate with the third entity,

- identification of the subscribed or requested third analytics information by the third entity (e.g., analytics subscription correlation ID) ,

- fields related to the subscribed or requested third analytics information by the third entity (e.g., analytics filter information, analytic reporting information, target of analytics reporting) .

In a further implementation form of the first aspect, the processor being further configured to send a model training request to the fourth entity, the model training request indicating a model training for the analytics information for the UE or the group of UEs associated with an obtained ASI needs to be performed by a fourth entity.

The advantage of the first aspect of this disclosure may be as follows:

First, the first aspect may allow the coordination of mechanisms used by an operator in a communication network for the consumption of analytics IDs related to UEs and/or groups of UEs. For example, the UEs and/or group of UEs may be controlled by a second entity, and the analytics IDs being consumed by the third entity, therefore, it may be possible to reduce (e.g., limit) the occurrence of racing conditions when second entity and third entities consume analytics ID from the fourth entity to control the specific UEs and/or group of UEs.

Second, the first aspect may allow the reduction of the operation cost for automation and maintenance of the all NFs configurations (e.g., third entities) . For example, operators of a communication network do not need to keep track of the analytics ID configuration that each NF instance is allowed or restricted to subscribe for specific UEs and/or group of UEs (e.g., ASI) . This reduces the change management costs of operators. As NFs and UE subscriptions (e.g., new user cards) arrive and leave the system, operators need to keep all of the NFs configuration consistent and this has an unneglectable cost.

Third, the first aspect may reduce the chances of wrong actions and waste of operator’s resources to specific UEs or group of UEs that do not follow the same pattern from majority of UEs in the communication network.

Fourth, the first aspects may reduce the changes of misconfiguration of analytics IDs associated with UEs and/or group of UEs in different NFs that can lead to different treatment of UEs or group of UEs by different NFs (e.g., third entity) in the communication network.

A second aspect of the disclosure provides a second entity, wherein the second entity is used in a communication network, and the second entity comprising a processor configured to obtain an ASI, wherein the ASI comprises allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by the second entity, wherein the allowed and/or restricted analytics information are used for controlling a third entity to interact with a fourth entity; and the processor being further configured to send the ASI to the first entity.

The second entity may be, or may incorporated in, e.g., the NEF or the NWDAF, or an AF. The second entity may be for supporting ASI management in the control plane a mobile communication network that is able to provide ASI or updated ASI to the first entity, and obtain the identification of a stored ASI from the first entity.

Obtaining the ASI may be, for example, obtaining directly from second entity, or obtaining indirectly from second entity, or generated based on first support information, or obtaining via configuration of a management entity.

Optionally, the second entity may be configured to obtain a first support information and/or a second support information, generate ASI based on at least one of: a first support information, and a second support information. Moreover, optionally, the second entity may be configured to provide ASI to first entity that is based on a generated ASI, and provide further support information for the first entity.

In an implementation form of the second aspect, the processor being further configured to receive, from the first entity, one or more identifications of the ASIs.

In a further implementation form of the second aspect, the processor being further configured to obtain a first support information; and generate the ASI based on the first support information.

In a further implementation form of the second aspect, the processor being further configured to send, to the first entity, updated ASI for the UE or the group of UEs.

In a further implementation form of the second aspect, the ASI comprises one or more of:

- identification of the ASI;

- identification of second entity providing the ASI or first support information;

- identification of third entity consuming the ASI and/or consuming the analytics information;

- allowed analytics information for a list of UEs or the group of UEs, or allowed analytics information for the list of UEs or the group of UEs per consumer of the analytics information;

- restricted analytics information for the list of UEs or the group of UEs, or restricted analytics information for the list of UEs or the group of UEs per consumer of the analytics information;

- identification of reference point to communicate with the third entity consuming the ASI and/or consuming the analytics information;

- identification of reference point to communicate with the second entity providing the ASI or first support information;

- identification of the analytics information subscription or request related to the third entity;

- a field related to the subscription for an analytics information.

The advantage of the second aspect of this disclosure may be as follows:

First, the second aspect may allow the coordination of mechanisms used by an operator in a communication network for the consumption of analytics IDs related to UEs and/or groups of UEs. For example, the UEs and/or group of UEs may be controlled by the second entity, and the analytics IDs being consumed by the third entity. Therefore, it may be possible to reduce (e.g., limit) the occurrence of racing conditions when second entity and third entities consume analytics ID from the fourth entity to control the specific UEs and/or group of UEs.

Second, the second aspect may reduce the chances of wrong actions and waste of operator’s resources to specific UEs or group of UEs that do not follow the same pattern from majority of UEs in the communication network.

Third, the second aspect may reduce the changes of misconfiguration of analytics IDs associated with UEs and/or group of UEs in different NFs (e.g., third entity) that can lead to different treatment of UEs or group of UEs by different NFs (e.g., third entity) in the communication network.

A third aspect of the disclosure provides a third entity, wherein the third entity is used in a communication network, and the third entity comprising a processor configured to obtain, from a first entity or from another third entity, ASI, wherein the ASI comprises allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by a second entity, wherein the allowed and/or restricted analytics information are used for controlling the third entity to interact with a fourth entity, and the processor being further configured to provide a subscription or a request or an unsubscribe request or a cancelation request to the fourth entity, for one or more third analytics information for the UE or the group of UEs based on the one or more obtained ASI, where one or more third analytics information are based on the analytics information of the one or more obtained ASI, and is used in the interactions between the third entity and fourth entity or vice-versa.

The third entity may be, or may incorporated in NFs, e.g., AMF, SMF, PCF. The third entity may be for consuming the ASI for one or more analytics interactions. The third entity may be configured to obtain ASI or updated ASI from first entity or from a further third entity, and provide the subscription or request to an Analytics Function (e.g., the fourth entity, e.g., the NWDAF) for analytics consumption of one or more specific analytics IDs for one or more specific UEs or one or more groups of UEs, wherein the analytics IDs and the specific UEs or groups of UEs are related to the obtained ASI. In addition, in the subscription or request comprises a list of restricted UEs or group of UEs according with the ASI.

The third entity may further be configured to provide a unsubscription or cancelation of request analytics IDs for the specific UEs or group of UEs, where the analytics ID and the specific UEs or group of UEs are related to the obtained ASI, and provide the analytics context information to the first entity.

Optionally, the third entity may be configured to forward the ASI information for a further third entity.

Moreover, optionally, e.g., when the third interacting with a fourth entity, the third entity may be configured to provide to the fourth entity a subscription or request for analytics IDs comprising any of the following fields: a list of restricted UEs or group of UEs according with the ASI, and consumer relocation flag.

In an implementation form of the third aspect, the subscription or the request or the unsubscribe request to the fourth entity, for one or more third analytics information comprises at least one of:

- restricted one or more UEs or group of UEs for the generation of the requested third analytics information, where the one or more UEs or group of UEs comprises the UEs or group of UEs of the one or more obtained ASI,

- consumer relocation information, wherein the consumer relocation information is obtained based on a need for a change of a consumer of third analytics information determined based on the ASI for the specific UEs or group of UEs.

In a further implementation form of the third aspect, the processor being further configured to send, to the first entity, a request for the ASI for the UE or the group of UEs, and/or receive an ASI response message from the first entity, the ASI response message comprising one or more ASIs or an indication of no available ASI for that sent request.

In a further implementation form of the third aspect, the request for ASI comprises one or more of:

- identification of the ASI,

- identification of the analytics information,

- identification of one or more UEs,

- identification of one or more group of UEs,

- identification of the second entity that provided the ASI,

- identification of the third entity related to the ASI,

- identification of reference point to communicate with the third entity.

In a further implementation form of the third aspect, the processor may be further configured to send a model training request to a fourth entity based on the obtained ASIs in the ASI response message.

In a further implementation form of the third aspect, the processor may be further configured to receive, from the first entity, a notification message, the notification message indicating a change of the ASI.

For example, the notification received from the first entity may be two possible ways as follows:

● The changed ASI is included in the notification.

In a further implementation form of the third aspect, the processor may be further configured to provide ACI to the first entity, wherein the ACI comprises at least one of: an association of a third entity with an ASI, and an association of an ASI obtained by the third entity with an existing subscription or existing request or unsubscription or cancelation for the third analytics information requested by the third entity to the fourth entity, where the third analytics information is based on the analytics information of the ASI, and is used in the interactions between the third entity and fourth entity or vice-versa.

In a further implementation form of the third aspect, the ACI comprises one or more of:

- identification of the third entity,

- identification of a reference point to communicate with the third entity,

- identification of the subscribed or requested third analytics information by the third entity,

- a field related to the subscribed or requested third analytics information by the third entity.

In a further implementation form of the third aspect, the ASI comprises one or more of:

- identification of the ASI,

- identification of second entity providing the ASI or first support information,

- one or more fields related to the subscription for an analytics information.

The advantage of the third aspect of this disclosure may be as follows:

First, the third aspect may allow the coordination of mechanisms used by an operator in a communication network for the consumption of analytics IDs related to UEs and/or groups of UEs. The UEs and/or group of UEs may be controlled by a second entity second, and the analytics IDs being consumed by the third entity, therefore, it may be possible to reduce (e.g., limit) the occurrence of racing conditions when second entity and third entities consume analytics ID from the fourth entity to control the specific UEs and/or group of UEs.

Second, the third aspect may allow the reduction of the operation cost for automation and maintenance of the all NFs configurations (e.g., third entities) . Operators of a communication network do not need to keep track of the analytics ID configuration that each NF instance is allowed or restricted to subscribe for specific UEs and/or group of UEs (e.g., ASI) . This reduces the change management costs of operators. As NFs and UE subscriptions (e.g., new user cards) arrive and leave the system, operators need to keep all of the NFs configuration consistent and this has an unneglectable cost.

Third, the third aspect may reduce the chances of wrong actions and waste of operator’s resources to specific UEs or group of UEs that do not follow the same pattern from majority of UEs in the communication network.

Fourth, the third aspects may reduce the changes of misconfiguration of analytics IDs associated with UEs and/or group of UEs in different NFs that can lead to different treatment of UEs or group of UEs by different NFs (e.g., third entity) in the communication network.

Fifth, the third aspect may allow for the optimization of resources used by the Analytics Functions (e.g., fourth entity) , by: a) allowing the fourth entity to become aware (e.g., via interaction with third entity) of UEs or group of UEs that should be removed from the calculation of the analytics ID and therefore reducing the data collection related to such UEs and/or group of UEs; b) allowing the Analytics Function (e.g., fourth entity) to become aware of an NF consumer of analytics ID relocation (via interaction with third entity) , and therefore the Analytics Function can reuse computation outputs and/or collected data from one existing analytics ID subscription for first NF consumer of such analytics ID to a second NF consumer of such analytics ID (i.e., the relocated NF consumer of analytics ID) ; c) reducing the time for providing the first analytics ID output for the relocated NF consumer of analytics ID, because the Analytics Function can reuse an already trained data model for the analytics ID for specific UEs and/or group of UEs, as well as already collected data for a previous analytics ID subscription from a different NF consumer of analytics ID to provide the analytics ID output for the relocated NF consumer of analytics ID.

A fourth aspect of the disclosure provides a fourth entity, wherein the fourth entity is used in a communication network, and the fourth entity comprising a processor configured to obtain, from a third entity, a subscription or a request or an unsubscribe request or a cancelation request, for one or more third analytics information for the UE or the group of UEs, the one or more third analytics information for the UE or the group of UEs based on ASI, wherein the ASI comprises analytics information for a UE and/or a group of UEs that are controlled by a second entity, wherein the allowed and/or restricted analytics information are used for controlling a third entity to interact with the fourth entity, and the third analytics information is based on the analytics information of the ASI, and is used in the interactions between the third entity and fourth entity or vice-versa, and the processor being further configured to send a response to the third entity.

The fourth entity may be, or may be incorporated in, the NWDAF. The fourth entity may be for analytics generation or analytics model training based on ASI.

The fourth entity may be configured to obtain a subscription or request from a third entity for analytics consumption of specific analytics IDs for the specific UEs or group of UEs, where the analytics ID and the specific UEs or group of UEs are related to the obtained ASI. In addition, in the subscription or request comprises a list of restricted UEs or group of UEs according with the ASI.

Moreover, the fourth entity may be configured to generate analytics ID output based on the received request. If the request indicated restricted UEs or group of UES, this means that the generated analytics is not considering such restricted UEs or group of UEs.

The fourth entity may further be configured to obtain a subscription or request from a third entity for analytics consumption of specific analytics IDs for the specific UEs or group of UEs, the subscription or request including a consumer relocation flag as a result of the third entity identifying the need to change the consumer of one or more analytics IDs for the specific UEs or group of UEs related to the obtained ASI.

In an implementation form of the fourth aspect, the subscription or the request or the unsubscribe request or the cancelation request may be obtained from the third entity, and comprises at least one of:

In a further implementation form of the fourth aspect, wherein the ASI comprises one or more of:

- identification of the ASI,

- identification of reference point to communicate with the second entity (200) providing the ASI (101) or first support information,

- one or more fields related to the subscription for an analytics information.

In a further implementation form of the fourth aspect, the fourth entity may further be configured to obtain a model training request from the first entity, the model training request indicating a model training for the analytics information for the UE or the group of UEs associated with an obtained ASI needs to be performed by a fourth entity.

The advantage of the fourth aspect of this disclosure may be as follows:

First, the fourth aspect may reduce the chances of wrong actions and waste of operator’s resources to specific UEs or group of UEs that do not follow the same pattern from majority of UEs in the communication network.

Second, the fourth aspects may reduce the changes of misconfiguration of analytics IDs associated with UEs and/or group of UEs in different NFs that can lead to different treatment of UEs or group of UEs by different NFs (e.g., third entity) in the communication network.

Third, the fourth aspect may allow for the optimization of resources used by the Analytics Functions (e.g., fourth entity) , by: a) allowing the fourth entity to become aware (e.g., via interaction with third entity) of UEs or group of UEs that should be removed from the calculation of the analytics ID and therefore reducing the data collection related to such UEs and/or group of UEs; b) allowing the Analytics Function (e.g., fourth entity) to become aware of an NF consumer of analytics ID relocation (via interaction with third entity) , and therefore the Analytics Function can reuse computation outputs and/or collected data from one existing analytics ID subscription for first NF consumer of such analytics ID to a second NF consumer of such analytics ID (i.e., the relocated NF consumer of analytics ID) ; c) reducing the time for providing the first analytics ID output for the relocated NF consumer of analytics ID, because the Analytics Function can reuse an already trained data model for the analytics ID for specific UEs and/or group of UEs, as well as already collected data for a previous analytics ID subscription from a different NF consumer of analytics ID to provide the analytics ID output for the relocated NF consumer of analytics ID.

A fifth aspect of the disclosure provides a method being performed by a first entity, the method comprising obtaining, by a processor, ASI, via a configuration by a management entity or received from a second entity, wherein the ASI comprises allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by a second entity, wherein the allowed and/or restricted analytics information are used for controlling a third entity to interact with a fourth entity; and providing, by the processor, the ASI to a third entity.

In an implementation form of the fifth aspect, the method further comprises providing one or more IDs of the ASI to the second entity.

In a further implementation form of the fifth aspect, the method further comprises receiving from the second entity, a first support information, wherein the first support information comprises mapping between the UE or the group of UEs behavior and a second set of analytics information, wherein the second set of analytics information is used to indicate possible analytics information related to UE or group of UE behavior, and/or generating the ASI based on the obtained first support information.

In a further implementation form of the fifth aspect, the method further comprises receiving from the third entity, a request for an ASI for a specific UE or for a specific group of UEs, and/or sending an ASI response message to the third entity, the ASI response message comprising one or more ASI or an indication of no available ASI for that received request.

In a further implementation form of the fifth aspect, the request for ASI comprises one or more of:

- identification of the ASI,

- identification of the analytics information,

- identification of one or more UEs,

- identification of one or more group of UEs,

- identification of the second entity that provided the ASI,

- identification of the third entity related to the ASI,

- identification of reference point to communicate with the third entity.

In a further implementation form of the fifth aspect, the ASI comprises one or more of:

- identification of the ASI,

- one or more fields related to the subscription for an analytics information.

In a further implementation form of the fifth aspect, the method further comprises obtaining updated ASI via a configuration by a management entity or received from the second entity, and/or sending a notification message to the third entity, the notification message indicating a change of the ASI.

In a further implementation form of the fifth aspect, the method further comprises receiving ACI from the third entity, wherein the ACI comprises at least one of: an association of a third entity with an ASI, and an association of an ASI obtained by the third entity with an existing subscription or existing request or unsubscription or cancelation request for the third analytics information requested by the third entity to the fourth entity, where the third analytics information is based on the analytics information of the ASI, and is used in the interactions between the third entity and fourth entity or vice-versa.

In a further implementation form of the fifth aspect, the ACI comprises one or more of:

- identification of the third entity,

- identification of a reference point to communicate with the third entity,

- fields related to the subscribed or requested third analytics information by the third entity.

In a further implementation form of the fifth aspect, the method further comprises sending a model training request to the fourth entity, the model training request indicating a model training for the analytics information for the UE or the group of UEs associated with an obtained ASI needs to be performed by a fourth entity.

The method of the fifth aspect achieves the advantages and effects described for the first entity of the first aspect.

A sixth aspect of the discourse provides a method being performed by a second entity, the method comprising obtaining, by a processor, an ASI, wherein the ASI comprises allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by the second entity, wherein the allowed and/or restricted analytics information are used for controlling a third entity to interact with a fourth entity; sending, by the processor, the ASI to the first entity.

In an implementation form of the sixth aspect, the method further comprises receiving, from the first entity, one or more IDs of the ASIs.

In a further implementation form of the sixth aspect, the method further comprises obtaining a first support information, wherein the first support information comprises mapping between the UE or the group of UEs behavior and a second set of analytics information, wherein the second set of analytics information is used to indicate possible analytics information related to UE or group of UE behaviour, and generating the ASI based on the first support information.

In a further implementation form of the sixth aspect, the method further comprises sending, to the first entity, updated ASI for the UE or the group of UEs.

In a further implementation form of the sixth aspect, the ASI comprises one or more of:

- identification of the ASI,

- one or more fields related to the subscription for an analytics information.

The method of the sixth aspect achieves the advantages and effects described for the second entity of the second aspect.

A seventh aspect of the disclosure provides a method being performed by a third entity, the method comprising obtaining, by a processor, from a first entity or from another third entity, ASI, wherein the ASI comprises allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by a second entity, wherein the allowed and/or restricted analytics information are used for controlling the third entity to interact with a fourth entity, and providing, by the processor, a subscription or a request or an unsubscribe request to the fourth entity, for one or more third analytics information for the UE or the group of UEs based on the one or more obtained ASI, where one or more third analytics information are based on the analytics information of the one or more obtained ASI, and is used in the interactions between the third entity and fourth entity or vice-versa.

In an implementation form of the seventh aspect, the subscription or the request or the unsubscribe request to the fourth entity, for one or more third analytics information comprises at least one of:

In a further implementation form of the seventh aspect, the method further comprises sending, to the first entity, a request for the ASI for the UE or the group of UEs, and/or receive an ASI response message from the first entity, the ASI response message comprising one or more ASIs or an indication of no available ASI for that sent request.

In a further implementation form of the seventh aspect, the request for ASI comprises one or more of:

- identification of the ASI,

- identification of the analytics information,

- identification of one or more UEs,

- identification of one or more group of UEs,

- identification of the second entity that provided the ASI,

- identification of the third entity related to the ASI,

- identification of reference point to communicate with the third entity.

In a further implementation form of the seventh aspect, the method further comprises sending a model training request to a fourth entity based on the obtained ASIs in the ASI response message.

In a further implementation form of the seventh aspect, the method further comprises receiving, from the first entity, a notification message, the notification message indicating a change of the ASI.

In a further implementation form of the seventh aspect, the method further comprises providing ACI to the first entity, wherein the ACI comprises at least one of: an association of a third entity with an ASI, and an association of an ASI obtained by the third entity with an existing subscription or existing request or unsubscription or cancelation for the third analytics information requested by the third entity to the fourth entity, where the third analytics information is based on the analytics information of the ASI, and is used in the interactions between the third entity and fourth entity or vice-versa.

In a further implementation form of the seventh aspect, the ACI comprises one or more of:

- identification of the third entity,

- identification of a reference point to communicate with the third entity,

In a further implementation form of the seventh aspect, the ASI comprises one or more of:

- identification of the ASI,

- one or more fields related to the subscription for an analytics information.

The method of the seventh aspect achieves the advantages and effects described for the third entity of the third aspect.

An eighth aspect of the discourse provides a method being performed by a fourth entity, the method comprising obtaining, by a processor, from a third entity, a subscription or a request or an unsubscribe request or a cancelation request, for one or more third analytics information for the UE or the group of UEs, the one or more third analytics information for the UE or the group of UEs based on Analytics Subscription Information, ASI, wherein the ASI comprises analytics information for a User Equipment, UE, and/or a group of UEs that are controlled by a second entity, wherein the allowed and/or restricted analytics information are used for controlling a third entity to interact with the fourth entity and the third analytics information is based on the analytics information of the ASI, and is used in the interactions between the third entity and fourth entity or vice-versa, and sending, by the processor, a response to the third entity.

In an implementation form of the eighth aspect, the subscription or the request or the unsubscribe request obtained from the third entity, comprises at least one of:

In a further implementation form of the eighth aspect, the ASI comprises one or more of:

- identification of the ASI,

- one or more fields related to the subscription for an analytics information.

The method of the eighth aspect achieves the advantages and effects described for the fourth entity of the fourth aspect.

A ninth aspect of the present disclosure provides a computer program comprising a program code for performing the method according to the one of the fifth to eighth aspects or any of their implementation forms.

A tenth aspect of the present disclosure provides a non-transitory storage medium storing executable program code which, when executed by a processor, causes the method according to the one of the fifth to eighth aspects or any of their implementation forms to be performed.

It has to be noted that all devices, elements, units and means described in the present application could be implemented in the software or hardware elements or any kind of combination thereof. All steps which are performed by the various entities described in the present application as well as the functionalities described to be performed by the various entities are intended to mean that the respective entity is adapted to or configured to perform the respective steps and functionalities. Even if, in the following description of specific embodiments, a specific functionality or step to be performed by external entities is not reflected in the description of a specific detailed element of that entity which performs that specific step or functionality, it should be clear for a skilled person that these methods and functionalities can be implemented in respective software or hardware elements, or any kind of combination thereof.

BRIEF DESCRIPTION OF DRAWINGS

The above described aspects and implementation forms will be explained in the following description of specific embodiments in relation to the enclosed drawings, in which

FIG. 1 depicts a schematic view of a first entity used in a communication network, according to an embodiment of the disclosure;

FIG. 2 depicts a schematic view of a second entity used in a communication network, according to an embodiment of the disclosure;

FIG. 3 depicts a schematic view of a third entity used in a communication network, according to an embodiment of the disclosure;

FIG. 4 depicts a schematic view of a fourth entity used in a communication network, according to an embodiment of the disclosure;

FIG. 5 depicts a schematic view of a diagram illustrating a procedure for obtaining or generating ASI;

FIG. 6 depicts a schematic view of a diagram illustrating a procedure for triggering analytics start/stop consumption;

FIG. 7 depicts a schematic view of a diagram illustrating a procedure for triggering model pre-training;

FIG. 8 depicts a schematic view of a diagram illustrating the first entity being exemplary based on an UDM for obtaining ASI;

FIG. 9 depicts a schematic view of a diagram illustrating the first entity being exemplary based on an UDM for obtaining ASI based on first support information;

FIG. 10 depicts a schematic view of a diagram illustrating the first entity being exemplary based on an UDM triggering analytic start/stop consumption;

FIG. 11 depicts a schematic view of a diagram illustrating the first entity being a UDM and the third entity being the NF indirectly obtaining ASI;

FIG. 12 depicts a schematic view of a diagram illustrating obtaining a change in the ASI;

FIG. 13 depicts a schematic view of a diagram illustrating triggering a model pre-training;

FIG. 14 depicts a schematic view of a flowchart of a method being performed by a first entity, according to an embodiment of the disclosure;

FIG. 15 depicts a schematic view of a flowchart of a method being performed by a second entity, according to an embodiment of the disclosure;

FIG. 16 depicts a schematic view of a flowchart of a method being performed by a third entity, according to an embodiment of the disclosure; and

FIG. 17 depicts a schematic view of a flowchart of a method being performed by a fourth entity, according to an embodiment of the disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

In order to ease of the description of this disclosure, some terms used in this disclosure are explained as below:

Analytics process: this process defines different possible capabilities that an Analytics Function can have. In this invention we consider examples of analytics process the following: analytics inference and analytics model training.

Analytics output: this term defines information resulting from the calculation (e.g., generation) of an analytics ID by an Analytics Function. In this invention, the term “consumption of an analytics ID” is equivalent to the term “consumption of analytics output for an analytics ID” or simply “consumption of analytics output” .

Analytics ID: this term defines an analytics identification or type that can be generated by an Analytics Function and consumed by an NF in an operator’s network. In this invention the term Analytics ID is used as a synonym of analytics information or analytics type or analytics identification. Examples of Analytics IDs are: Service Experience, UE Abnormal Behavior, UE Mobility, UE Communication, among others.

NF consumer of analytics ID/ (IDs) : this term defines an NF type (e.g., NF of type AMF or SMF, or PCF) or an NF instance (e.g., AMF #1, AMF#2) that can consume analytics ID from an Analytics Function (e.g., NWDAF) .

NF consumer instance of analytics ID/IDs: this term defines a specific instance of an NF Type that can or is consuming analytics ID from an Analytics Function (e.g., NWDAF) .

NF consumer of ASI: This term defines a NF (e.g., type or instance) that can obtain the ASI for using it in order to trigger interactions with an Analytics Function. Examples of such interactions are: subscription to analytics IDs, request for model training.

NF with Model Training Capability: this term defines an NF that is able to perform machine learning model training for a given analytics ID.

Property of an analytics ID: this term property refers to a characteristic associated with an analytics ID. The property can be allowed analytics ID (which means that such analytics ID is allowed to be consumed) or restricted (which means that the analytics ID is not allowed to be consumed) .

Conventionally, methods for triggering analytics consumption are as follows:

● A first method is characterized by defining the overall triggers for NFs, and specifically for an Access and Mobility Management Function (AMF) , a Session Management Function (SMF) , or a Policy and Charging Function (PCF) . In particular, the solution defines that the AMF and the SMF could eventually decide which UEs to use as a target of an analytics ID for the subscription of the analytics ID from the NWDAF.

● A second method is characterized by the implicit assumption that if a UE moved from one serving NF to a second serving NF, the second serving NF automatically will subscribe/request analytics IDs for such UE.

● A third method is characterized by the relocation of the subscription of an analytics ID for specific UE from one first NWDAF to a second NWDAF. The principle is also related to the fact that a UE moved. In this case the UE moved out of the serving area from the first NWDAF and now is covered by the second NWDAF. Therefore, the subscription for analytics ID is then moved to the second NWDAF.

However, an issue of the conventional methods is that, for example, in none of these methods the AF is able to influence how the NFs, or the OAM subscribe to one or more analytics IDs for one or more specific UEs, or a group of UEs.

The present disclosure introduces ASI, which comprises allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by a second entity, wherein the allowed and/or restricted analytics information are used for controlling a third entity (e.g., a 5GS NF to interact with a fourth entity (e.g., with the NWDAF in the 5GS network) .

In particular, the disclosure presents a first entity that is configured to obtain ASI and provide the ASI to a third entity. The disclosure also presents a second entity that is configured to obtain ASI and provide the ASI to the first entity. The disclosure further presents a third entity that is configured to obtain ASI, and provide a subscription or a request or an unsubscribe request to the fourth entity based on the ASI. The disclosure further presents a fourth entity that is configured to obtain, from the third entity, a subscription or a request or an unsubscribe request based on the ASI, and send a response to the third entity.

The present disclosure also presents corresponding methods, wherein these methods may be performed by the first entity, the second entity, the third entity and the fourth entity, respectively

FIG. 1 depicts a schematic view of a first entity 100 used in a communication network 1, according to an embodiment of the disclosure.

The first entity 100 comprising a processor 110, configured to obtain ASI 101 via a configuration by a management entity or received from a second entity 200. The ASI 101 comprises allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by a second entity 200. The allowed and/or restricted analytics information are used for controlling a third entity 300 to interact with a fourth entity 400.

The processor 110 of the first entity 100 is further configured to provide the ASI 101 to a third entity 300.

Optionally, the processor 110 of the first entity 100 is further configured to provide the model training request 102 to a fourth entity 400.

Optionally, the processor 110 of the first entity 100 is further configured to obtain the first support information 103 from a second entity 200.

Optionally, the processor 110 of the first entity 100 is further configured to obtain the analytics context information 104 from a third entity 300.

The first entity 100 may further comprise a processing circuitry (not shown in FIG. 1) configured to perform, conduct or initiate the various operations of the first entity 100 described herein. The processing circuitry may comprise hardware and software. The hardware may comprise analog circuitry or digital circuitry, or both analog and digital circuitry. The digital circuitry may comprise components such as application-specific integrated circuits (ASICs) , field-programmable arrays (FPGAs) , digital signal processors (DSPs) , or multi-purpose processors.

In one embodiment, the processing circuitry comprises one or more processors and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code which, when executed by the one or more processors, causes the first entity 100 to perform, conduct or initiate the operations or methods described herein.

FIG. 2 depicts a schematic view of a second entity 200 used in a communication network 1, according to an embodiment of the disclosure.

The second entity 200 comprising a processor 210 configured to obtain an ASI 101. The ASI 101 comprises allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by the second entity 200. The allowed and/or restricted analytics information are used for controlling a third entity 300 to interact with a fourth entity 400.

The processor 210 of the second entity 200 may further configured to send the ASI 101 to the first entity 100, wherein the ASI 101 may be send to the first entity 100 directly or indirectly through a further network element.

The processor 210 of the second entity 200 may further be configured to send the first support information 103 to the first entity 100.

The second entity 200 may further comprise a processing circuitry (not shown in FIG. 2) configured to perform, conduct or initiate the various operations of the second entity 200 described herein. The processing circuitry may comprise hardware and software. The hardware may comprise analog circuitry or digital circuitry, or both analog and digital circuitry. The digital circuitry may comprise components such as application-specific integrated circuits (ASICs) , field-programmable arrays (FPGAs) , digital signal processors (DSPs) , or multi-purpose processors.

In one embodiment, the processing circuitry comprises one or more processors and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code which, when executed by the one or more processors, causes the second entity 200 to perform, conduct or initiate the operations or methods described herein.

FIG. 3 depicts a schematic view of a third entity 300 used in a communication network 1, according to an embodiment of the disclosure.

The third entity 300 comprising a processor 310 configured to obtain, from a first entity 100 or from another third entity 300, ASI 101. The ASI 101 comprises allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by a second entity 200. The allowed and/or restricted analytics information are used for controlling the third entity 300 to interact with a fourth entity 400.

The processor 310 of the third entity 300 may further be configured to provide a subscription or a request or an unsubscribe request or a cancelation request 301 to the fourth entity 400, for one or more third analytics information for the UE or the group of UEs based on the one or more obtained ASI 101, where one or more third analytics information are based on the analytics information of the one or more obtained ASI 101, and is used in the interactions between the third entity and fourth entity or vice-versa.

The processor 410 of the fourth entity 400 may further be configured to provide the ACI 104 to a first entity 100.

The third entity 300 may further comprise a processing circuitry (not shown in FIG. 3) configured to perform, conduct or initiate the various operations of the third entity 300 described herein. The processing circuitry may comprise hardware and software. The hardware may comprise analog circuitry or digital circuitry, or both analog and digital circuitry. The digital circuitry may comprise components such as application-specific integrated circuits (ASICs) , field-programmable arrays (FPGAs) , digital signal processors (DSPs) , or multi-purpose processors.

In one embodiment, the processing circuitry comprises one or more processors and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code which, when executed by the one or more processors, causes the third entity 300 to perform, conduct or initiate the operations or methods described herein.

FIG. 4 depicts a schematic view of a fourth entity 400 used in a communication network 1, according to an embodiment of the disclosure.

The fourth entity 400 comprising a processor 410 configured to obtain, from a third entity 300, a subscription or a request or an unsubscribe request or a cancelation request 301, for one or more third analytics information for the UE or the group of UEs, the one or more third analytics information for the UE or the group of UEs based on ASI 101. The ASI 101 comprises analytics information for a UE and/or a group of UEs that are controlled by a second entity 200, wherein the allowed and/or restricted analytics information are used for controlling a third entity 300 to interact with the fourth entity 400 and the third analytics information is based on the analytics information of the ASI, and is used in the interactions between the third entity and fourth entity or vice-versa.

The processor 410 of the fourth entity 400 may further be configured to obtain from the third entity a model training request 102 from a first entity 100 and/or a third entity 300.

The processor 410 of the fourth entity 400 may further be configured to send a response to the third entity 300.

The fourth entity 400 may further comprise a processing circuitry (not shown in FIG. 2) configured to perform, conduct or initiate the various operations of the fourth entity 400 described herein. The processing circuitry may comprise hardware and software. The hardware may comprise analog circuitry or digital circuitry, or both analog and digital circuitry. The digital circuitry may comprise components such as application-specific integrated circuits (ASICs) , field-programmable arrays (FPGAs) , digital signal processors (DSPs) , or multi-purpose processors.

In one embodiment, the processing circuitry comprises one or more processors and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code which, when executed by the one or more processors, causes the fourth entity 400 to perform, conduct or initiate the operations or methods described herein.

At next, the present disclosure is exemplary discussed based on mechanisms for NFs (such as trusted AFs, external AFs, control plane function in general) or OAM (e.g., management plane) to influence the 5GS NFs to interact with NWDAF.

Trusted AFs may be the AFs that are allowed by an operator of a communication network to invoke the services or interfaces exposed by NFs of a control plane of such communication network, wherein the AFs may directly invoke the services or interface exposed by NFs.

External AFs may be a specific type of NF that may be not allowed to invoke the services or reference points from any other NF of the control plane of the communication network. The external NFs communicate with other control plane NFs via one specific NF, such as Network Exposure Function, NEF. Therefore, in a communication network AFs can communicate with other NFs, wherein the communication may be directly or indirectly which is not restricted by this disclosure.

In the following, for ease of description and without limiting the present disclosure, the afore-mentioned mechanism is divided in three parts including part A, part B and part C as follows.

Part A: this part of the disclosure is exemplary discussed as a set of steps defining the interactions among the first entity 100 and the second entity 200 defined in this invention in order to allow the first entity 100 to obtain the ASI.

Part B: this part of the disclosure is exemplary discussed as a set of step defining the mechanisms of interaction between the first entity 100, the second entity 200, and the third entity 300 for using the ASI 101 as a trigger for starting or stopping the interactions among the third entity 300 and an Analytics Function (e.g., the fourth entity 400) .

Part C: this part of the disclosure is exemplary discussed as a set of steps defining the mechanisms of interaction between the first entity 100 and fourth entity 400 for using the ASI 101 as trigger model training interactions with an Analytics Function (e.g., fourth entity 400) .

It should be noted that, this disclosure divides the mechanism into three parts just for ease of description, the contents of the three parts can be combined easily for a skilled person and the mechanism described in the three parts form a whole solution.

Furthermore, in the following, the disclosure is discussed based on the first entity 100 being exemplary based on a UDM, and being used for ASI 101 management. Moreover, the second entity 200 is exemplary based on an AF or an NEF or an NWDAF, and being used for supporting ASI 101 management. Moreover, the third entity 300 is discussed as being an entity consuming ASI 101 for analytics interactions, for example, AMF, or SMF, for triggering a subscription to analytics information; or a NWDAF triggering a model training request to a further NWDAF with training capabilities, etc.

It should be noted that the exemplary of the following should not be understood a restriction to this disclosure. For example, the first may be some other control elements beyond UDM. For the other entities, it may also be some other network elements beyond the exemplary listed above.

Reference is now made to FIG. 5, which is a schematic view of a diagram illustrating obtaining or generating ASI 101.

The Part A comprises the set of steps of the disclosure that reflect the interaction among the entities until the ASI 101 is stored in the first entity 100. Moreover, three different alternatives are discussed for the first entity 100 obtaining the ASI 101. These alternatives are identified by the different cases indicated in Step 501 and are described in the following.

At 501 the first entity 100 obtains ASI 101 via a configuration. This step defines possible alternatives for the first entity 100 to obtain the ASI 101. Each case is discussed in more detailed bellow.

Case #A. 1: Obtaining ASI 101 via configuration (e.g., from the management plane) .

In this case (in step 1 of 501) the ASI 101 may be configured at the first entity 100. Such configuration can be performed for instance by management entities before the first entity 100 starts executing or during the execution of the first network entity. For example, the ASI 101 can be configured in a file that can be loaded by the first entity 100 and can be stored in the runtime memory of such entity 100.

Alternatively, the ASI 101 can be directly configured at a database, and the management plane entity may configure a bootstrap file at the first entity 100 to indicate the reference to the ASI 101 that are related to such first entity 100.

Alternatively, the first entity might expose a service that can be invoked by the management entity in order to configure the ASI at the first entity.

Case #A. 2: Obtaining ASI 101 from second entity 200:

In this case, there may exist direct and/or indirect interactions between the first entity 100 and the second entity 200.

The direct interaction may include that the second entity 200 can itself access the first entity 100 (e.g., invoking directly the services exposed by the First entity) . The indirect interaction may be, for example, that there is a further entity between the first entity 100 and the second entity 200 that forwards and or send any exchange of information between the first entity 100 and the second entity 200.

For the indirect interaction, when this intermediary entity is used to forward, no change is applied to the messages to and/or from first entity 100 and second entity 200. Or when this intermediary entity is used to send, it may be possible that the intermediary entity performs further processing in the messages to and/or from first entity 100 and second entity 200.

Examples of further processing by the intermediary entity comprise: mapping of information that are different between first entity 100 and second entity 200, such as UE ids format information; or translation of the network properties indicated by one of the entities to the network properties understandable by the other entity, such as area of interest send by the second entity 200 in the format of a path way and translated by the intermediary entity into list of tracking areas, TA, before sending the message to the first entity 100.

Nevertheless, mapping or translation of information exchanged between the first entity 100 and the second entity 200 is not limiting the type of further processing that an intermediary entity can apply when sending information between the first entity 100 and the second entity 200.

At 502 (for example, in the first step of 502) , in this case, the ASI 101 is available at the second entity 200. The second entity 200 provides the ASI 101 to the first entity 100 (directly or indirectly via an intermediary entity as described above) . Different mechanisms can be applied for the interaction between the second entity 200 and the first entity 100 in this step. Examples of such mechanisms are defined as follows:

The first entity 100 can expose a service that the second entity 200 can invoke. This type of interaction follows a request-response model of communication. The input parameters of the service operation of this service may comprise fields including the ASI 101.

The second entity 200 may invoke the service operation from the first entity 100 whenever the second entity 200 decides that an ASI 101 needs to be provided to the first entity 100. The provided ASI 101 may comprise the tuple: (identification of properties provider (e.g., the second entity 200 own identification) , allowed analytics ID, optionally per NF consumer of analytics ID, for list of UEs or group of UEs, restricted analytics ID, optionally per NF consumer of analytics ID, for list of UEs or group of UEs) .

It should be understood that the tuple above is only example, and the tuple may also include one or more of the parameters listed above, or may further include more parameters in the tuple which is not restricted by this disclosure.

Alternatively, the second entity 200 can expose a service that the first entity 100 can invoke. This type of interaction among the

entities

100 and 200 may follow an asynchronous communication model, for instance, based on call-back procedures or a subscribe-notify model. In this case, the input parameters of the service operation may be the identification of the first entity 100, or a reference point for the first entity 100 (e.g., interface or service endpoint address) that allows the second entity 200 to send to the first entity 100 the ASI 101, or the ASI 101 request fields (such as analytics IDs, or specific UEs, or specific Group of UEs) .

The second entity 200 may match the values of the ASI 101 request fields with the available ASI 101 and may send via the reference point informed by the first entity 100, the ASI 101 comprises the tuple: (identification of properties provider (e.g., the second entity 200 own identification) , allowed analytics ID, optionally per consumer of the analytics ID, for a list of UEs or a group of UEs, restricted analytics ID, optionally per NF consumer of analytics ID, for list of UEs or group of UEs) .

In addition, the second entity 200 may include, in the message to the first entity 100, a second entity 200 reference point (e.g., interface or service endpoint address) , which allows the first entity 100 to send to the second entity 200 (e.g., in Step 2) the identification of the ASI 101. The first entity 100 can be configured to periodically invoke the service operation of the second entity 200, in order to retrieve the ASI 101, or it can also indicate in the first message sent to the second entity 200 a periodicity by which the second entity 200 is to send to the first entity 100 the ASI 101 tuple.

If the communication between the first and second entity 200 is indirect, the entity forwarding the communications may have a mirror of the services exposed by the first entity 100 so that the second entity 200 can invoke such services. The entity forwarding, then forwards any message received from the second entity 200 to the first entity 100 by invoking the services provided by the first entity and vice versa.

Case #A. 3: Obtaining ASI 101 generated based on further processing.

In this case, the ASI 101 is not available at the second entity 200 and it needs to generate the ASI 101 before providing it to the first entity 100. Multiple steps involving the second entity 200 need to be performed before the second entity 200 is able to provide the ASI 101 information to the First entity 100. These steps are described as follows:

At 503 (Step 1a) : The second entity 200 is able to obtain the first support information. Different mechanisms can be used for the second entity 200 to obtain the first support information. Some of them are listed below:

The first support information can be configured at the second entity 200, for instance, by a management entity. Similar configuration mechanisms as discussed in Case #A. 1 Step 1 can be also applied in this Step 1a of Case #A. 2.

Alternatively, the first support information can be obtained from further entities, e.g., one or more AFs or Application Server or the OAM, of the mobile communication network, which can support the generation of the analytics subscription information. In this case, the second entity 200 can expose a service that can be invoked by the further entities. The input parameters of the service operation exposed by the second entity 200 comprise the first support information fields.

At 504 (Step 1b) : optionally, the second entity 200 is able to obtain the second support information. Different mechanisms can be used for the second entity 200 to obtain the first support information. Some of them are listed below:

The second support information can be configured at the second entity 200 for instance by management entities. Similar configuration mechanisms discussed in Case #A. 1 Step 1 can be also applied in this Step 1b of Case #A. 2.

The second support information can be obtained from further entities, e.g., from one or more AFs or an OAM, of the mobile communication network that can support the generation of the analytics subscription information. In this case, the second entity 200 can invoke services exposed by further entities, e.g., other NFs such as the NWDAF or NRF or UDM, or UDR, and request the second support information. The input parameters of the service operation invoked by the second entity 200 comprise the request for second support information fields.

At 505 (Step 1c) : optionally, the second entity 200 generates the ASI 101 based on the first and second support information. For instance, the ASI 101 generation can achieved by the mapping between the fields of the first and second support information. The generation is performed differently according with the type of the obtained first support information:

For the case of first support information obtained with precise information, the generation of ASI 101 may be achieved with the following steps:

A) A first set of tuple may be created based on the intersection of the first and second support information using the analytics ID as the index to identify the intersection. Tuples from both first and second support information that contain the same analytics IDs are selected for the first set of tuple.

B) A second set of tuples may be created by merging the fields of the tuples in the first set of tuples that have the same analytics ID. The second set of tuples may be included in the ASI 101 representing either “Allowed analytics ID per NF consumer of analytics ID for List of UEs or group of UEs” (if property of an analytics ID is allowed) , or “Restricted analytics ID per NF consumer of analytics ID for List of UEs or group of UEs” (if property of an analytics ID is restricted) .

For the case of first support information obtained with general description, the generation of ASI 101 may be achieved with the following steps:

A first step may be to perform the mapping between the behavior field of first support information to the analytics IDs, and the mapping of the behavior property field to the allowed or restricted properties of an analytics ID. The second entity 200 may be configured with the mapping between possible values of behavior field and the associated analytics ID, as well as with the mapping of behavior property and the properties of analytics IDs. The output of the process of mapping may be a set of tuples containing the Target UE received in the first support information and the mapped Analytics IDs.

The second entity 200 then may perform the same steps (A) and (B) described for the case of the first support information obtained with precise information.

The next steps may be independent from the type of the first support information:

Based on the output of the processing of the first and second support information, the second entity 200 is able to generate an ASI 101 tuple (e.g., create a data structure) that contains:

Identification of properties provider: in this case the second entity 200 includes in this field its own identification (e.g., NF ID instance or IP address, or reference name) .

Allowed analytics ID: optionally per NF consumer of analytics ID, for List of UEs or group of UEs: the second entity 200 may include in this field the tuples from the mapping between first and second support information that as property of analytics ID “allowed” . Restricted analytics ID: optionally per NF consumer of analytics ID, for List of UEs or group of UEs: the second entity 200 may include in this field the tuples from the mapping between first and second support information that as property of analytics ID “restricted” .

At 506 (step 1d) : The second entity 200 may provide the generated ASI 101 tuple to the first entity. The information sent to the second entity 200 may comprise one or more of the following ASI 101: (Identification of Properties Provider, Allowed analytics ID per NF consumer of analytics ID for List of UEs or group of UEs, Restricted analytics ID per NF consumer of analytics ID for List of UEs or group of UEs) . The same mechanisms described in Case #A. 2 for the interaction between First and Second Entities can be applied also for Step 1d in Case #A. 3.

Note that, 507 (Steps 2) and 508 (step 3) are only executed, if the first entity 100 is capable of operating with Case #A. 2 or Case #A. 3.

In a further implementation of this proposal, it is also possible a combination of parts of Case #A. 2 and Case #A. 3 being executed by the first entity 100. In this case, the second entity 200 may provide alternatively at 502 the first support information to the first entity 100. The first entity is then able to execute 504 (Step 1b) and 505 (Step 1c) and generate the ASI based on the obtained first support information from the second entity (200) and/or on the second support information. The first entity 100 further executes 507 (Step 2) and 508 (Step 3) .

At 507 (Step 2) : optionally, the first entity 100 may store the obtained ASI 101. In this step the first entity 100 may extend the content of the ASI 101 including the field Identification of ASI 101 which is uniquely identifying the ASI 101 information provided by the second entity.

Therefore, if there exist the case that multiple second entities 200 provide ASI 101 tuples to the first entity 100, each of these obtained ASI 101 tuples from the second entities 200 will be uniquely identified and stored as different records at the first entity1 00. The first entity 100 can use for instance incremental counters to define such identification or using more sophisticated mechanisms based on hashing the identification of properties provider with some other unique information inside the first entity 100.

At 508 (Step 3) : the first entity 100 may provide to the second entity 200 the identification of ASI 101. Examples of such mechanisms are provided as follows:

In the case that the first entity 100 exposes a service that the second entity 200 can invoke: The second entity 200 would have sent, for example, the ASI 101 tuple as input parameters of the service operation exposed by the first entity 100. Therefore, the output parameters of the same service will contain the Identification of ASI 101 associated to the particular second entity.

In the case that the second entity 200 exposes a service that the first entity 100 can invoke: The first entity 100 may receive from the second entity 200 in Step 1 a reference point to send to the second entity 200 the identification of ASI 101. The first entity 100 may use this reference point to send then the Identification of ASI 101 to the second entity 200.

If the communication between the first entity 100 and the second entity 200 is indirect, the entity forwarding the communications will have a mirror of the services exposed by the first entity 100 or second entity. The entity forwarding may be responsible to send information (e.g., Identification of ASI 101) exchanged from the first entity 100 or the second entity 200 respectively to the second entity 200 or the first entity 100.

Reference is now made to FIG. 6, which is a schematic view of a procedure for triggering analytics start/stop consumption.

The Part B comprises the steps that reflect the interaction among the first entity 100 and the third entity 300, being the third entity 300 a consumer of ASI 101.

It may be assumed that the steps of the Part B of this invention can be executed after part A has been executed.

The third entity 300 might assume different roles and their relationship will be further detailed in the description of each case in Part B. The roles that we consider comprise:

- NF consumer or ASI 101: in this role that third entity 300 may be directly interacting with the first entity 100 in order to obtain ASI 101 from the first entity 100, or send ACI related to an ASI 101 to the first entity 100.

- NF consumer of analytics ID: in this role, the third entity 300 may interact with an Analytics Function (e.g., the NWDAF) in order to trigger the start (e.g., trigger the subscription or request to the analytics ID) or stop (e.g., unsubscription or cancelation of the analytics ID) of analytics consumption.

- NF Serving UE: in this role, the third entity 300 may be the entity (e.g., SMF or AMF, or PCF) that is at a given point in time providing mobile services (e.g., session management, or mobility management, QoS management) to a UE or group of UE.

Moreover, at least three possible alternatives including B1, B2, and B3 are defined for the first entity 100 and the third entity 300 to interact in order to use the ASI 101 to trigger the start or stop of analytics consumption in a mobile network. Each one of these alternatives are described as follows.

Case #B. 1: Direct request for ASI 101: in this case, the third entity 300, which may be a NF consumer of ASI 101, may directly interact with the first entity 100 to obtain the ASI 101 to support such NF consumer of the ASI 101 to trigger the subscription or request to analytics ID (i.e., start of analytics consumption) or to trigger the unsubscription or cancelation of an analytics ID (i.e., stop the analytics consumption) . The steps of the interactions performed are described as follows.

At 601 (Step 1) : the third entity 300 may send a request for first entity 100 to retrieve the ASI 101 (e.g., a request for an ASI) . Different mechanisms can be applied for the interaction between first entity 100 and third entities 300 in this step. Examples of such mechanisms may be as follows:

In one example, the first entity 100 may expose a service following a request-response model of communication that the third entity 300 can invoke. The third entity 300 invokes the service operation from the first entity 100 upon a) lifecycle events related to one or more UEs or group of UEs that such third entity 300 is serving (i.e., the third entity 300 is assuming the role of serving NF for certain UEs or groups of UEs) , or upon local policies defined by the mobile network operator.

The input parameters of the service operation comprise the ASI 101 request fields defined in this invention. For instance, if it is the first time that the third entity 300 is interacting with the first entity 100 the input parameters may contain one or more of: Identification of analytics IDs, Identification of one or more UEs or group of UEs, Identification of NF consumer of analytics ID (i.e., the third entity’s 300 own identification such as NF ID) .

It is also possible that the third entity 300 may be configured by local operator policies to periodically retrieve the ASI 101. In this situation, the third entity 300 may include the before mentioned parameters with or without the Identification of the ASI 101 (which is obtained from the First entity 100 as it is described in Step 3a) .

In a second example, the first entity 100 can expose a service following a subscription-notify model of communication that the third entity 300 can invoke. The third entity 300 may invoke the service operation from the first entity 100 upon:

a) lifecycle events related to one or more UEs or group of UEs that such third entity 300 is serving (i.e., the third entity 300 is assuming the role of serving NF for certain UEs or group of UEs) , or

b) local policies defined by the mobile network operator.

In this case, the input parameters of the service operation may be ASI 101 request fields, as the input parameters may be one or more of: analytics IDs, or specific UEs, or specific group of UEs, Identification of NF consumer of analytics ID (e.g., the third entity 300 can indicate its own identification such as NF ID and/or NF Type) or a reference point for the third entity 300 (e.g., interface or service endpoint address, which may allow the first entity 100 to send to the third entity 300 notifications with the ASI 101.

The second entity 200 may match the values of the ASI 101 request fields with the available ASI 101 and sends via the reference point informed by the first entity 100, the ASI 101 containing the tuple: (Identification of Properties Provider (e.g., the second entity 200 own identification) , Allowed analytics ID per NF consumer of analytics ID for List of UEs or group of UEs, Restricted analytics ID per NF consumer of analytics ID for List of UEs or group of UEs) .

The understanding of the tuple is as described before and is not elaborated again.

At 602 (Step 2) : Based on the received request from the third entity 300, the first entity 100 may use the ASI 101 request fields from the received request (e.g., a request for an ASI) to identify where there is a matching ASI 101 based on any combination of the following: analytics IDs, identification of UEs, identification of group of UEs, identification of NF consumer of analytics ID (e.g., by NF type or NF instance) .

In this sense, depending on the ASI 101 request fields included in step 1 (601) , it is possible that the first entity 100 identifies one or more ASIs 101 to be provided to the third entity 300. For instance, the ASI 101 request can comprise the analytics ID field set to “any” . This means that the Third network entity is requesting any ASIs 101 stored at the first entity 100 related to the “analytics ID” request by the third entity 300.

At next (step 3 including

steps

3a and 3b) : After the first entity 100 performed the matching between requested ASI 101 fields and the stored ASI 101, the first entity 100 may identify whether there is one or more ASIs 101 to be provided or not to the third entity 300.

At 603 (Step 3a) : In case there is one or more ASIs 101 to be provided to the third entity 300, the first entity 100 may send a message to the third entity 300 including the one or more ASIs 101.

If the communication model between the first entity 100 and the third entity 300 is request-response model, the output parameters of the service exposed by the first entity 100 (invoke by the third entity 300 as described in Step 1) may include the list of matched ASIs 101 with their associated ASIs 101 identifications.

If the communication model between the first entity 100 and the third entity 300 is subscription-notification model, the output parameters of the service exposed by the first entity 100 (invoke by the third entity 300 as described in Step 1) may include the list of ASI 101 identifications, and the first entity 100 may send via the reference point indicated in the received request from the third entity 300 (e.g., a request for an ASI) the one or more matched ASIs 101 information to third entity 300 (e.g., as a notification message) .

Alternatively, if in the request received from the third entity 300 there is an immediate return flag, the first entity 100 may include in the response of the received request (e.g., a request for an ASI) to the third entity 300.

At 604 (Step 3b) : In case there is no ASI 101 to be provided to the third entity 300, the first entity 100 sends a message to the third entity 300 including an indication of no available ASI 101 for any combination of values included in the ASI 101 request fields sent by the third entity 300.

Step 4 including steps 4a (605) and 4b (406) : Based on the received information from the first entity, the third entity 300 may trigger further interactions with Analytics Functions (e.g., NWDAF) in order to subscribe (or request) or unsubscribe (or cancel a request) for analytics ID based on the one or more received ASIs 101.

At 605 (Step 4a) : In case the third entity 300 received an indication of no ASI 101, the third entity 300 may decide by itself to subscribe to analytics IDs also deciding which specific UEs or group of UEs will be used as target of analytics when subscribing or requesting the analytics ID for the Analytic Function (e.g. the NWDAF) .

In the case that the third entity 300 received one or more ASIs 101 with allowed analytics ID for specific UEs or group of UEs, the third entity 300 may for each received ASI 101, use the analytics ID and associated specific UEs or group of UEs to subscribe or request the analytics ID for the Analytic Function (e.g. NWDAF) .

In case of the interaction between the third entity 300 and the Analytics Function may follow a subscribe-notify model. It is also possible that the third entity 300 modifies existing subscriptions for analytics IDs (matching the same analytics IDs from the ASI 101) at the Analytics Function including the specific UEs or group of UEs, instead of creating a new subscription request to the Analytics Function.

At 606 (Step 4b) : In case the third entity 300 received one or more ASIs 101 with restricted analytics ID for specific UEs or group of UEs, the third entity 300 might not trigger any new subscription or requests to the analytics IDs with the specific UEs or group of UEs indicated as restricted in the one or more ASI 101.

If the third entity 300 had previously to obtaining the ASI (s) triggered subscriptions or requests to the analytics IDs for specific UEs or group of UEs indicated as restricted by the ASI (s) , the third entity 300 unsubscribe or cancel the request for such analytics IDs for specific UEs or group of UEs via interaction with the Analytics Function.

In case of the interaction between the third entity 300 and the Analytics Function may follow a subscribe-notify model, it is also possible that the third entity 300 may modify existing subscriptions for analytics IDs (matching the same analytics IDs from the ASI 101) at the Analytics Function removing the specific UEs or group of UEs from the existing subscription, instead of completely unsubscribing to and creating a new subscription only with the parameters (e.g., target UEs) that are not restricted.

Alternatively, the service exposed by the Analytics Function (e.g., fourth entity 400, or NWDAF) can be extended in order to allow NF consumers of analytics ID, such as the third entity 300, to indicate in the subscription or request both the target of analytics (e.g., UEs or group of UEs that should be included in the calculation of the analytics ID) and the restricted target of analytics (e.g., UEs or group of UEs that must not be included in the calculation of the analytics ID) .

Optionally, at 607 (optional step 5) : Based on the received information from the first entity 100, the third entity 300 may trigger in step 4 the interactions with Analytics Functions (e.g., NWDAF) in order to subscribe (or request) or unsubscribe (or cancel a request) for analytics ID based on the one or more received ASIs 101.

In Step 5, the third entity 300 may provide to the first entity 100 the Analytics Context Information (ACI) associated with each received ASI 101. The mechanism to be used for this interaction between First and third entity 300 is based on the first entity 100 exposing a service (or an interface) . For instance, using a request-response operation mode the third entity 300 can invoke the service operation of the first entity 100 and may include as input parameters one or more ASI 101 identifications and for each ASI 101 the associated ACI.

Note that, 618 or Step 6 may execute in all cases described in Part B.

At 617 (Step 6) : The first entity 100 may receive the one or more ASI 101 and for each ASI 101 the associated ACI from the third entity 300 and for each received ASI 101 identification, the third entity 300 may update the respective stored ASIs 101 including the ACI information for such ASI 101 identification.

Case #B. 2: Indirect acquisition of ASI 101: In this case, the third entity 300 may perform two roles: a NF serving a UE or NF consuming analytics ID. The third entity 300 may obtain the ASI 101 without a direct interaction with the First entity 100 for retrieving the ASI 101.

At 608 (Step 1) : In mobile networks, UEs can move from a first serving NF (i.e., NF Serving UE) to a new Serving NF (i.e., new NF serving UE) . When a UE moves in the network the context of such UE, i.e., all information required to provide the mobile services to such UE, is moved from the first Serving NF to the new Serving NF.

Therefore, this disclosure defines that a first third entity 300 with the NF serving UE role may include as part of the UE context the ASI 101 and the ASI 101 identification.

A second third entity 300 (acting with the role of new NF Serving UE) may obtain the ASI 101 indirectly via interaction with a first third entity 300. It may also be assumed that the first third entity 300 has at a given point in time executed the Case #B. 1 to obtain for the first time the ASI 101 and ASI 101 identification for the analytics IDs for UEs or group of UEs.

The transfer of information from the first third entity 300 to a second third entity 300 can be done using existing mechanisms defined in current mobile network specification.

At 609 (Step 2a) and 610 (step 2b) : Based on the obtained ASI 101 from another third entity 300, the third entity 300 may perform the same actions as described in Case #B. 1 Step 4 (a and b) .

At 611 (Step 3) : Same actions as described in Case #B. 1 Step 5. The only difference may be that the ACI is related to the new NF consumer of analytics ID, which is the third entity 300 acting as new NF Serving UE. Additionally, the Step 6 described in Case #B. 1 is also executed in the Case #B. 2 as the final step.

Case #B. 3: Changes in obtained ASI 101: In this case, this disclosure assumes that:

a) there exist Third Entities that already retrieved the ASI 101 (i.e., the third entity 300 is an NF consumer of ASI 101) ;

b) the second entity 200 may send updated ASI 101 to the first entity. The updates ASI 101 sent by the second entity 200 to the First entity 100 may trigger the first entity 100 to interact with the Third entities (NF consumers of ASI 101) in order to provide the updated ASI 101 to such one or more third entities 300 (i.e., NF consumers of ASI 101) .

At 612 (Step 1) : The third entity 300 may obtain the ASI 101 as per Case #B. 1 or Case #B.2. The third entity 300 may be an NF consumer of analytics IDs for allowed analytics ID for specific UEs or group of UEs according with one or more obtained ASI 101; or that the third entity 300 may be not NF consumer of analytics IDs because the one or more ASIs 101 define restricted analytics ID for specific UEs or group of UEs.

At 613 (Step 2) : the second entity 200 may provide one or more updated ASIs 101 or new ASIs 101 to the First entity 100 or updated first support information or new first support information. The mechanism for this to happen are similar to those described in Step 1d of Case #A. 2 or Case #A. 3. When the second entity provides updates or new first support information, the first entity may generate the associated ASIs 100 as defined in the description of the first entity being able to execute parts of Case #A. 2 and Case #A. 3. Therefore, after this generation, the first entity may have the updated or new ASIs 100.

At 614 (Step 3) : The first entity 100 may identify for each updated ASI 101, the ASIs 101 that have a change on properties of analytics ID.

Examples of changes may be (but not restricted) :

- the status change from allowed to restricted analytic ID to all the UEs or group of UEs of the stored ASI 101;

- inclusion or removal of UEs or group of UEs in allowed or restricted analytics IDs;

- inclusion or removal of specific NF consumers of analytics IDs from the ASI 101 for a allowed or restricted analytics ID for UEs or group of UEs.

In the case a new ASI 101, the First entity 100 may check if there is any ACI associated with stored ASIs 101, e.g., the one or more information of the ASIs that are related to analytics subscription identification, identification of the consumer of the ASI and/or analytics ID, and one or more fields of analytics subscriptions, that could be affected by the new ASI 101.

Based on these performed identifications and checks, the First entity 100 may be able to identify the NF consumers of ASI 101 that are affected by the changes or new ASIs 101.

one of more of the values of the ASI 101 fields may be:

(a) identification of NF consumer of ASI 101;

(b) Identification of NF consumer instance of analytics ID for an existing subscription for allowed analytics ID for list of UEs or group of UEs; and

(c) Identification of reference point (e.g., interface or services) to communicate with the NF consumer instance of analytics ID of existing subscription for allowed analytics ID for list of UEs or group of UEs or with NF consumer of ASI 101;

The first entity 100 may base on the fields above interact with the third entity 300 and may provide to such entity the ASI 101 and its associated ASI 101 identification, for the ASIs 101 that were changed or ASIs 101 that are added to the first entity 100 storage by are affecting the third entity 300 role as NF consumer of analytics IDs.

Examples of the effect of an added ASI 101, it for instance an ASI 101 that may be added and it may be now restricting a certain analytics IDs to be consumed for a certain UE or group of UE, and the ACI of a different ASIs 101 (already stored ASI 101) contains the information that there exist an analytics subscription for such analytics IDs with the new restricted UEs or group of UEs.

At 615 (step 4a) and 616 (step 4b) : Based on the obtained ASI 101 from the first entity 100, the third entity 300 may perform the same actions as described in Step 4 (a and b) of Case #B. 1.

At 617 (step 5) : Same operations as described in Step 5 of Case #B. 1 may be performed.

At 618 (step 6) : Same operations as described in Step 6 of Case #B. 1 may be performed.

Reference is now made to FIG. 7, which is a schematic view of a procedure for triggering a model pre-training.

The Part C comprises the steps that reflect the interaction among the First entity 100 and the fourth entity 400, the fourth entity 400 operating as the NF with model training capability.

It is assumed that the steps of the Part C may optionally be executed after part A has been executed.

At 701 (step 1) : the First entity 100 may check the stored ASI 101 information and the allowed analytics ID for specific UEs or group of UEs. Optionally it can identify only the ASIs that have no ACI related information to such ASIs. For instance, there exist an ASI associated with the fields consumer of ASI not empty, but the ASI field of analytics subscriptions for such ASI is empty.

At 702 (step 2) : based on the ASIs 101 identified with allowed analytics ID for specific UEs and no ACI information, the First entity 100 may send an indication to the fourth entity 400 that a model needs to be trained for the analytics IDs for specific UEs or group of UEs.

At 703 (step 3) : for request received from the First entity, the third entity 300 may analyze and determine whether new machine learning models for the analytics ID with specific UEs or group of UEs need to be trained.

Alternatively, it is also possible that a third entity 300 that obtained an ASI from the first entity as defined in the steps of Case B#1, or Case B#2, or Case #B. 3 may execute the 702 (Step 2) and be the entity that sends the model training request to the fourth entity 400

This disclosure presents an embodiment of the proposed solution based on the entities defined in 3GPP 5G architecture in TS 23.501 R16.

The first entity 100 may, for example, be mapped into UDM. The functionalities of the second entity 200 may be mapped to three different entities including NFs: AF, NEF, and NWDAF according with the different embodiments to be presented. The third entity 300 is mapped to AMF.

It should be understood that the first entity, the second entity and the third entity may be some other network elements and they may be different network entities in different scenarios. For the remaining embodiments in this disclosure, the same understanding is assumed.

Reference is now made to FIG. 8, which is a schematic view of the first entity 100 being exemplary a UDM obtaining ASI according to part A.

The FIG. 8 illustrates the embodiments of the Case #A. 1 and Case #A. 2. In this embodiment, the second entity 200 may be mapped to AF. Nevertheless, there are other possible NFs that can also be the embodiment of the second entity. For instance, NEF, or NWDAF displayed in FIG. 8, can also have the ASI 101 available and then provide such information to the UDM (i.e., embodiment of First entity) .

Case #A. 1: at 802, the analytics subscription information may be configured and stored in the UDM.

Case #A. 2: at 803 (step 1a) AFs provides the analytics subscription information (ASI 101) to UDM directly (step 1a) , if AF is allowed by operator to do so, or indirectly via NEF (at 804 or Step 1b) . The AF may invoke the service exposed by UDM including at least one of following parameters: AF identification, list of allowed analytics ID for UEs or group of UEs, and list of restricted analytics ID for List of UEs or group of UEs.

At 802 (step 2) , the UDM may receive and store the analytics subscription information.

At 806 UDM may provide to AF directly (e.g. in Step 3a (or 806) ) or indirectly (e.g. via NEF at 807 (or Step 3b) ) the identification of the ASI 101. AF may use such identification to change its associated stored ASIs 101.

Reference is now made to FIG. 9 which is a schematic view of the first entity being a UDM obtaining ASI based on support information

In FIG. 9 (UDM-Based Embodiment for Part A –Case #A. 3) , the embodiment for the Case #A. 3 where the second entity 200 may generate the ASI 101 and then provide the generated ASI 101 to the first entity 100 is discussed. This embodiment shows the first entity 100 mapped to UDM and the second entity 200 mapped to NEF.

Two alternatives of embodiments are described to indicate how exactly the NEF, i.e., second entity 200 obtains the second information. For example, the NEF may interact with NWDAF 900 or NRF 900 in order to obtain either the second information. When NEF interacts with NWDAF, the NEF should contact all NWDAFs in the system and retrieve from each one of them their supported analytics IDs.

Nevertheless, NWDAF is not the only entity in the 5GS that would be able to provide the list of supported analytics IDs in the mobile network operators. For instance, NRF has also this information. NEF can query the NRF function and retrieve all the NWDAF NF profiles. Based on the NWDAF NF Profiles the NEF can determine all the analytics IDs supported by the mobile network operator.

Furthermore, other NFs could also be mapped to the second entity 200 also in this Case #A.3. For instance, NWDAF can also enclose the capabilities of the second entity.

At 902 (step 1) : AFs may provide to NEF the NWDAF-Associated Expected UE behavior, being the NWDAF-Associated Expected UE behavior the embodiment of the first support information.

NEF may generate the analytics subscription information based on the information retrieved from AF 901 (the first support information) and information about supported analytics IDs in the mobile network operator (e.g., second support information) . There exist two alternatives for NEF to generate such ASI 101.

Alternative #A. 3.1: at 903 (step 2) , in case NEF is configured with the supported analytics IDs in the mobile network operator (e.g., second support information) .

At 904 (step 3) , NEF may perform the mapping of the NWDAF-Associated Expected UE behavior (first support information) to the supported analytics IDs (second support information) to generate the ASI 101 the specific UEs or group of UEs.

Alternative #A. 3.2: at 905, in case NEF is not configured with the supported analytics IDs in the mobile network operator (second support information) , NEF may interact with further NFs (e.g., NWDAFs or NRF) to retrieve the supported analytics ID in the operator’s network (second support information) .

In case NEF interacts with NRF to obtain the supported analytics IDs in the operator’s network (second support information) , it can use existing NRF services to retrieve the existing NWDAF NF Profiles with their supported analytic ID. Based on this information NEF may create the second support information.

In case NEF interacts with NWDAF to obtain the supported analytics IDs in the operator’s network (second support information) , it may needs to invoke a new service from NWDAF to retrieve the list of supported analytics ID by such NWDAF.

At 906 (step 3) , when NEF obtains the supported analytic IDs in the operator’s network (second support information) , NEF may perform the mapping of the NWDAF-Associated Expected UE behavior (first support information) to the supported analytics IDs (second support information) in order to generate the ASI 101. The result of this mapping may be the ASI 101 for the specific UEs or group of UEs.

At 907 (step 4) , NEF invokes UDM services in order to store the generated ASI 101. The parameters used in the UDM service invoked by NEF may be the same as the ones indicated in Step 1d as it is described above.

At 908 (step 5) , the UDM may receive and store the analytics subscription information.

At 910 (step 7a) , the UDM may provide to NEF the identification of the ASI 101 the specific UEs or group of UEs, as part of the response message for the invoked service by NEF.

At 911 (step 7b) , the NEF may send a response to AF including a Correlation ID that allows AF to perform further changes in the analytics subscription information. Such correlation ID may be related to the ASI 101 identification received from UDM, and allows AFs to change it associated ASI 101 information stored at UDM.

Reference is now made to FIG. 10 which is a schematic view of the first entity being a UDM and the third entity being an NF obtaining ASI.

In FIG. 10, the UDM-Based Embodiment for Part B –Case #B. 1 is discussed that an ASI 101 may be obtained for the first time by third entity 300. In the embodiment for the Case #B.1 where the First entity 100 may be mapped into UDM, and the third entity 300 may be mapped to an NF serving UEs such as AMF. This embodiment is not restricted only to the third entity 300 mapped to AMF, it could also be to SMF, PCF, any NF that serves UEs for controlling the UEs session or mobility or policies, or any other mobile operator service. The fourth entity 400 is mapped to NWDAF.

In this embodiment, it is considered that the steps related to part A of the invention have been executed.

At 1001 (step 0) , in this step, one or more UEs may be performing session establishment or UE registration via interactions with 5GS. These interactions can be seen as lifecycle events that happen with UEs in the operator’s network (e.g., lifecycle events related to UEs) .

For instance, when a UE request a session to be established, or modified, or removed; or when the UE is registering in to the network, or also when the network decides to perform some changes at the UE.

Examples of the changes that the network may perform comprise: changing session QoS (Quality of Service) , changing restrictions of areas that UEs can use the operator’s network. These changes that the network can enforce in the UE are also considered in this invention as lifecycle events related to UEs.

At 1002 (step 1) , the first Serving NF (e.g., AMF if the lifecycle event is UE registration) , may determine that such NF has no ASI 101 information about the UE (or UEs, or groups of UEs) related to the lifecycle event. The first Serving NF may invoke the service exposed by UDM to retrieve the ASI 101. The parameters included in the request may be the same ones as described above.

Alternatively, at 1003, the first Serving NF can retrieve this information from UDM as part of the UE context information retrieved by NFs upon lifecycle events related to the UEs. UDM may verify if there exist any ASI 101 related to the parameters included in the received request from the First Serving NF.

At 1004 (step 3a) , if there is a match, UDM may send to first Serving NF the one or more ASI 101 and their associated identification that were matched to some or all the fields indicated in the request received by UDM.

At 1005 (step 3b) , if there was not a match for any field, UDM may send to the first Serving NF an indication of no applicable ASI 101 for any of the requested fields.

At 1006 (step 4a) , in case the first Serving NF received an indication of no application ASI 101, the first Serving NF can decide according to its internal logic or configuration to further request analytics ID related to the UEs. In the case the First Serving NF may receive one or more ASIs 101 with allowed analytics IDs for the one or more UEs such NF is handling, the first Serving NF based the ASI 101 may trigger the subscription to analytics IDs at NWDAF for the allowed analytics ID with the UEs or group of UEs that such first Serving NF is treating.

In case the first Serving NF received one or more ASI 101 with restrictions to analytics ID for the UEs or group of UEs such NF is serving, the first Serving NF may optionally perform 3 actions:

At 1007 (step 4b) , not trigger any subscription to analytics ID for the UEs or group of UEs indicated in the ASI 101. Even if an internal logic or local policy of such first Serving NF identifies the need for subscribing or requesting analytics ID for the UEs or group of UEs indicated as restricted, such First Serving NF may not trigger the subscription due to the received ASI 101 from UDM.

At 1008 (step 4c) , if the first Serving NF had already any previous subscriptions of analytics IDs with target of analytics including the UEs or group of UEs indicated as restricted by the received ASI 101 from UDM, the first Serving NF may send a unsubscribe message to NWDAF for such analytics IDs or send a cancelation request to NWDAF to stop the generation of such analytics ID for the specific UEs or group of UEs in the ASI 101.

At 1009 (step 4d) , if the first Serving NF had already any previous subscriptions of analytics IDs with target of analytics ID set to ‘’Any UE” , the First Serving NF may send a request to modify the subscription or request for analytics IDs maintaining the target of analytics ID set to ‘’Any UE” but adding a new field of Analytics Filter Information called Analytics Restriction.

The Analytics Restriction may comprise the tuple: restricted filter type (e.g., UE, group of UE, network slice, application, area of interest, i.e., all possible types of fields used as Analytics Filter Information or Target of Analytics as per the definition of the different analytics IDs in TS 23.288) , restricted value (e.g., list of UE SUPIs, S-NSSAIs, Application IDs, etc. ) .

In this case, the Analytics Restriction may comprise: UE field type, and the list of UE identifications that should be restricted from the generation of the analytics ID.

At 1010 (step 5) , the NWDAF may perform the appropriated changes in the existing analytics ID according to the request received from the First Serving NF, and sends back to the First Serving NF the result of the requested changes.

Examples of changes comprise at least one of: confirmation of unsubscription, indication of a new analytics subscription identification in case NWDAF had to modify an existing analytics ID needed actually to be divided into 2 separated analytics ID subscriptions (instead of just modified as requested by the First Serving NF) .

At 1011 (step 6) , the First Serving NF may receive the response back from NWDAF and determine if the Analytics Context Information must be provided to UDM. It may send the ACI in case a new analytics subscription have been executed, or if any modification for an existing analytics subscription to an ASI 101 have also been performed (e.g., the subscription/request was cancelled) . The First Serving NF may invoke the service exposed by UDM and includes as input parameter the same parameters indicated, as described above.

Reference is now made to FIG. 11, which is a schematic view of a diagram illustrating the first entity being a UDM and the third entity being the NF indirectly obtaining ASI.

In FIG. 11, UDM-Based embodiment for Part B –Case #B. 2 is discussed, where the first entity 100 may be mapped into UDM, and the third entity 300 may be mapped to a New NF serving UEs such as AMF. This embodiment is not restricted only to the third entity 300 mapped to a New Serving NF such AMF, it could also be to SMF, PCF, any NF that serves UEs for controlling the UEs session or mobility or policies, or any other mobile operator service. The fourth entity 400 may be mapped to the NWDAF.

In the beginning (0. UE mobility) , one or more UEs may be performing interactions with 5GS related to the UE mobility. The UE may be being served by a first Serving NF. The UE may move in the operator’s network, the first serving NF may be no longer capable of controlling the UE’s connectivity and then handover the UE context and control to a New Serving NF.

The procedures for UE mobility and UE context transfer have been defined in 3GPP TS 23.502. When there is a UE context transfer, all information regarding the UE is directly transferred from the first Serving NF to the new Serving NF, via CP messages exchanged among such entities, or indirectly via the first Serving NF updating information about the UE in another entity, such as UDM, and then the New Serving NF obtaining the required UE information from the another entity. In this embodiment, we consider the case where the UE context is transferred

At step 1101 (step 1) , this step considers the case where during UE mobility procedures, the UE context information may be transferred from the first serving NF to the new serving NF. Included in the UE context comprises ASI 101 related to such UE or such UE group.

At 1102 (step 2a) and 1103 (step 2b) , based on the ASIs 101 received together with the UE or UE group context, the new Serving NF decides to interact with the NWDAF in order to properly reflect the allowed and restricted analytics IDs for UE or UE group.

At step 1102 (step 2a) , in case the ASI 101 obtained via UE context transfer may comprise the allowed analytics ID, it may also comprise the ACI. Based on the ACI, the new serving NF can interact with NWDAF in order to change the consumer of the analytics ID for UE that just moved.

In this case, the new serving NF can send an analytics subscription modification request in order to change the Notification Target for the specific UE or group of UE. Such request can also include a consumer relocation flag. Such consumer relocation flag may be used as an indication that there exist in NWDAF already a subscription or request for analytics ID for the specific UE or UE group, but the consumer of the analytics ID has changed.

In case the new Serving NF received one or more ASI 101 with restrictions to analytics ID for the UEs or group of UEs such NF is serving, the new Serving NF may optionally perform 3 actions:

At 1103 (step 2b) , this step is the same as Step 4b described above, but instead of the first Serving NF, the new serving NF may be the entity interacting with NWDAF.

At 1104 (step 2c) , this step is the same as Step 4c described above, but instead of the first Serving NF, the new serving NF may be the entity interacting with NWDAF.

At 1105 (step 2d) , this step is the same as Step 4d described above, but instead of the first Serving NF, the new serving NF may be the entity interacting with NWDAF.

At 1106 (step 3) , NWDAF may perform the appropriated changes in the existing analytics ID according to the request received from the new Serving NF, and send back to the first Serving NF the result of the requested changes.

Examples of changes may comprise one or more of: confirmation of unsubscription, confirmation of proper modification of existing analytics ID, or indication of a new analytics subscription identification in case NWDAF had to modify an existing analytics ID needed actually to be divided into 2 separated analytics ID subscriptions (instead of just modified as requested by the first Serving NF) .

The last type of action may be performed in the case when the new Serving NF sends the consumer relocation flag included in the subscription or request message to NWDAF. In this case, if the existing subscription with another consumer for the analytic ID cannot be entirely moved to the new consumer, NWDAF may split the existing analytics ID into 2 analytics ID subscriptions each with a different consumer and a split of UE or group of UE in the target of analytics following the indication send by the New serving NF as per Step 2a.

At 1107 (step 4) , this step is the same as Step 6 described above, but instead of the first Serving NF, the new serving NF may be the entity interacting with UDM.

Reference is now made to FIG. 12 which is a schematic view of a diagram illustrating obtaining a change in the ASI.

In FIG. 12, UDM-Based embodiment for Part B –Case #B. 3, where the first entity 100 may be mapped into UDM, the AF may be mapped to the second entity, and the third entity 300 may be mapped to an NF serving UEs such as AMF. This embodiment is not restricted only to the third entity 300 mapped to AMF, it could also be to SMF, PCF, any NF that serves UEs for controlling the UEs session or mobility or policies, or any other mobile operator service. The fourth entity 400 may be mapped to the NWDAF.

In the beginning (0a) , it is considered that the steps related to part A of the invention have been executed. At 0. b, it is considered that the steps related to part #B. 1 or #B. 2 of the disclosure have been executed. Therefore, the Serving NF may have the ASI 101 information and interacted with NWDAF in order to subscribe or request allowed analytics IDs for specific UE or group of UEs, or it is restricting itself from including the UEs or group of UEs indicated in the ASI 101 as part of the subscription or request to analytics IDs such Serving NF requires.

At 1201 (step 1) , the AF may identify the need to change an existing ASI 101. The AF might have identified the need either to restrict or allow analytics IDs for different UEs or group of UEs from the original ASI 101 provided to 5GS, directly to UDM or via NEF.

At 1202 (step 2) , the AF may provide the updated ASIs 101 directly to UDM or indirectly via NEF.

At 1203 (step 3) , the UDM may receive the updated ASIs 101 and identify the need to further notify the NFs consumers of analytics ID indicated in the ACI part or the NF consumers of ASIs 101 that changes have occurred. The UDM sends to each identified NF consumer of analytics ID or NF consumer of ASI 101 the updated ASIs 101.

At next, based on the received updated ASI 101, each Serving NF, which in this case is the identified NF consumer of analytics ID or NF consumer of ASI 101, may check the updated ASI 101 and determine the changes in the interactions with NWDAF that must be performed.

At 1204 (step 4a) , this step may be the same as Step 4a described above, but instead of the first Serving NF, the serving NF may be the entity interacting with NWDAF.

At 1205 (step 4b) , this step may be the same as Step 4b described above, but instead of the first Serving NF, the Serving NF may be the entity interacting with NWDAF.

At 1206 (step 4c) , this step may be the same as Step 4c described above, but instead of the first Serving NF, the Serving NF may be the entity interacting with NWDAF.

At 1207 (step 4d) , this step may be the same as Step 4d described above, but instead of the first Serving NF, the Serving NF may be the entity interacting with NWDAF.

At 1208 (step 5) , this step may be the same as Step 5 described above, but instead of the first Serving NF, the Serving NF may be the entity interacting with NWDAF.

At 1209 (step 6) , this step may be the same as Step 6 described above, but instead of the first Serving NF, the Serving NF may be the entity interacting with NWDAF.

Reference is now made to FIG. 13 which is a schematic view of diagram illustrating triggering a model pre-training.

In FIG. 13, UDM-Based embodiment for Part C is discussed, where the first entity 100 may be mapped into UDM, the AF may be mapped to the second entity, and the third entity 300 may be mapped to any NF such an NWDAF. The fourth entity 400 may be mapped to NWDAF capable of model training.

In the beginning, it is assumed that (at step 0) , the steps related to part A of the invention have been executed. Therefore either the first entity 100, i.e., UDM or the third entity 300, i.e., NF such as NWDAF obtained the ASI 101.

This embodiment considers 2 alternatives.

Alternative #C. 1 –The first entity 100 may trigger the model training.

At 1301 (step 1) , in this alternative, when the UDM received the ASI 101 from the AF (directly of via NEF) , UDM analyses according with local policies whether the model training should be initiated.

At 1302 (step 2) , the UDM may invoke the services exposed by an NWDAF with training capability in order to trigger the model training related to one or more allowed analytics IDs for specific UEs or group of UEs related to the ASIs 101.

Alternative #C. 2 –The third entity 300 may trigger the model training

At 1303 (step 1) , in this embodiment, it is considered that an NF such as NWDAF can be the consumer or the ASI 101 exposed by UDM. NWDAF may obtain the ASIs 101 based on the interactions with UDM, for instance by invoking the service exposed by UDM to provide the ASIs 101. In this case NWDAF may not need the ASIs 101 for triggering analytics consumption, but it may require the ASIs 101 to identify the need for triggering model training in advance.

Before a subscription request for the allowed analytics ID for specific UEs or group of UEs arrive at such NWDAF, the NWDAF may trigger the model training for such subscription/request beforehand. The advantage is that the model would be ready to be used for inference as soon as the subscription/request arrives at the NWDAF with inference capability. Therefore, based on the ASIs 101 obtained from UDM, the NWDAF may decide to trigger model training for analytics IDs indicated as allowed in the ASI 101.

At 1304 (step 2) , the NWDAF may invoke the services exposed by another NWDAF with training capability indicating the analytics IDs and the specific UEs or group of UEs that should be considered for the model training, being the analytics IDs for specific UEs or group of UEs based on the obtained ASIs 101.

The next step may be alternatives.

At 1305 (step 3) , the NWDAF with training capabilities may receive the request from a consumer, in this case another NWDAF, and decide on executing the requested model training.

FIG. 14 shows a method 1400 being performed by a first entity 100, according to an embodiment of the disclosure.

The method 1400 comprises a step 1401 of obtaining, by a processor 110, ASIs 101 via a configuration by a management entity or may be received from a second entity 200, wherein the ASIs 101 comprises allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by a second entity 200, wherein the allowed and/or restricted analytics information may be used for controlling a third entity 300 to interact with a fourth entity 400.

It should be understood that the ASIs 101 in this disclosure may comprise one or more ASIs 101, if an ASI is indicated, it may generally indicate ASIs without differentiation.

The method 1400 further comprises a step 1402 of providing, by the processor 110, the ASIs 101 to a third entity 300.

FIG. 15 shows a method 1500 being performed by a second entity 200, according to an embodiment of the disclosure.

The method 1500 comprises a step 1501 of obtaining, by a processor 210 ASIs 101 wherein the ASIs 101 comprises allowed and/or restricted analytics information for a User Equipment, UE, and/or a group of UEs that are controlled by the second entity 200, wherein the allowed and/or restricted analytics information may be used for controlling a third entity 300 to interact with a fourth entity 400.

The method 1500 further comprises a step 1502 of sending, by the processor 210, the ASIs 101 to the first entity 100.

FIG. 16 shows a method 1600 being performed by a third entity 200, according to an embodiment of the disclosure.

The method 1600 comprises a step 1601 of obtaining, by a processor 310, from a first entity 100 or from another third entity 300, ASIs 101, wherein the ASIs 101 comprise allowed and/or restricted analytics information for a UE and/or a group of UEs that are controlled by a second entity 200, wherein the allowed and/or restricted analytics information are used for controlling the third entity 300 to interact with a fourth entity 400.

The method 1600 further comprises a step 1602 of providing, by the processor 310, a subscription or a request or an unsubscribe request to the fourth entity 400, for one or more third analytics information for the UE or the group of UEs based on the one or more obtained ASIs 101, wherein one or more third analytics information may be based on the analytics information of the one or more obtained ASIs 101, and is used in the interactions between the third entity and fourth entity or vice-versa.

FIG. 17 shows a method 1700 being performed by a fourth entity 400, according to an embodiment of the disclosure.

The method 1700 comprises a step 1701 of obtaining, by a processor 410, from a third entity 300, a subscription or a request or an unsubscribe request, for one or more third analytics information for the UE or the group of UEs, the one or more third analytics information for the UE or the group of UEs based on ASIs 101, wherein the ASIs 101 comprise analytics information for a UE and/or a group of UEs that are controlled by a second entity 200, wherein the allowed and/or restricted analytics information may be used for controlling a third entity 300 to interact with the fourth entity 400, and the third analytics information is based on the analytics information of the ASI, and is used in the interactions between the third entity and fourth entity or vice-versa.

The method 1700 further comprises a step 1702 of sending, by the processor 410, a response to the third entity 300.

It should be understood that the methods above may have the same features as described before and not each feature is elaborated here just for simplicity. For a skilled person should understand that similar methods can be achieved based on the teaching of this disclosure.

The present disclosure has been described in conjunction with various embodiments as examples as well as implementations. However, other variations can be understood and effected by those persons skilled in the art and practicing the claimed disclosure, from the studies of the drawings, this disclosure and the independent claims. In the claims as well as in the description the word “comprising” does not exclude other elements or steps and the indefinite article “a” or “an” does not exclude a plurality. A single element or other unit may fulfill the functions of several entities or items recited in the claims. The mere fact that certain measures are recited in the mutual different dependent claims does not indicate that a combination of these measures cannot be used in an advantageous implementation.

Claims

A first entity (100) , wherein the first entity (100) is used in a communication network (1) , and the first entity (100) comprising:

a processor (110) , configured to obtain Analytics Subscription Information, ASI, (101) via a configuration by a management entity or received from a second entity (200) , wherein the ASI (101) comprises allowed and/or restricted analytics information for a User Equipment, UE, and/or a group of UEs that are controlled by a second entity (200) , wherein the allowed and/or restricted analytics information are used for controlling a third entity (300) to interact with a fourth entity (400) ; and

the processor (110) being further configured to provide the ASI (101) to a third entity (300) .
The first entity (100) according to claim 1, the processor (110) being further configured to:

provide one or more identifications, IDs, of the ASI (101) to the second entity (200) .
The first entity (100) according to claim 1 or 2, the processor (110) being further configured to:

receive, from the second entity (200) , a first support information (103) , wherein the first support information (103) comprises mapping between the UE or the group of UEs behavior and a second set of analytics information, wherein the second set of analytics information is used to indicate possible analytics information related to UE or group of UE behaviour; and/or

generate the ASI (101) based on the obtained first support information (103) .
The first entity (100) according to one of the claims 1 to 3, the processor (110) being further configured to:

receive, from the third entity (300) , a request for an ASI (101) for a specific UE or for a specific group of UEs; and/or

send an ASI response message to the third entity (300) , the ASI response message comprising one or more ASI (101) or an indication of no available ASI for that received request.
The first entity (100) according to one of the claims 1 to 4, wherein the request for ASI comprises one or more of:

- identification of the ASI (101) ;

- identification of the analytics information;

- identification of one or more UEs;

- identification of one or more group of UEs;

- identification of the second entity (200) that provided the ASI (101) ;

- identification of the third entity (300) related to the ASI (101) ;

- identification of an existing subscription or request to analytics information;

- identification of reference point to communicate with the third entity (300) .
The first entity (100) according to one of the claims 1 to 5, wherein the ASI comprises one or more of:

- identification of the ASI (101) ;

- identification of second entity (200) providing the ASI (101) or the first support information (103) ;

- identification of third entity (300) consuming the ASI (101) and/or consuming the analytics information;

- allowed analytics information for a list of UEs or the group of UEs, or allowed analytics information for the list of UEs or the group of UEs per consumer of the analytics information;

- restricted analytics information for the list of UEs or the group of UEs, or restricted analytics information for the list of UEs or the group of UEs per consumer of the analytics information;

- identification of reference point to communicate with the third entity (300) consuming the ASI (101) and/or consuming the analytics information;

- identification of reference point to communicate with the second entity (200) providing the ASI (101) or first support information (103) ;

- identification of the analytics information subscription or request related to the third entity;

- one or more fields related to the subscription for an analytics information.
The first entity (100) according to one of the claims 1 to 6, the processor (110) being further configured to:

obtain updated ASI (101) via a configuration by a management entity or received from the second entity (200) ; and/or

send a notification message to the third entity (300) , the notification message indicating a change of the ASI (101) .
The first entity (100) according to one of the claims 1 to 7, the processor (110) being further configured to:

receive Analytic Context Information, ACI, (104) from the third entity (300) , wherein the ACI (104) comprises at least one of: an association of a third entity (300) with an ASI (101) , and an association of an ASI (101) obtained by the third entity (300) with an existing subscription or existing request or unsubscription or cancelation request for the third analytics information requested by the third entity (300) from the fourth entity (400) , wherein the third analytics information is based on the analytics information of the ASI (101) , and is used in the interactions between the third entity and fourth entity or vice-versa.
The first entity (100) according to one of the claims 1 to 8, wherein the ACI (104) comprises one or more of:

- identification of the third entity (300) ;

- identification of a reference point to communicate with the third entity (300) ;

- identification of the subscribed or requested third analytics information by the third entity (300) ;

- fields related to the subscribed or requested third analytics information by the third entity (300) .
The first entity (100) according to anyone of the claims 1 to 9, the processor (110) being further configured to:

send a model training request (102) to the fourth entity (400) , the model training request (102) indicating a model training for the analytics information for the UE or the group of UEs associated with an obtained ASI (101) needs to be performed by a fourth entity (400) .
A second entity (200) , wherein the second entity (200) is used in a communication network (1) , and the second entity (200) comprising:

a processor (210) configured to obtain an analytics subscription information, ASI, (101) wherein the ASI (101) comprises allowed and/or restricted analytics information for a User Equipment, UE, and/or a group of UEs that are controlled by the second entity (200) , wherein the allowed and/or restricted analytics information are used for controlling a third entity (300) to interact with a fourth entity (400) ; and

the processor (210) being further configured to send the ASI (101) to the first entity (100) .
The second entity (200) according to claim 10 or 11, the processor (210) being further configured to:

receive, from the first entity (100) , one or more identifications, IDs, of the ASIs (101) .
The second entity (200) according to one of claims 10 to 12, the processor (210) being further configured to:

obtain a first support information (103) , wherein the first support information (103) comprises mapping between the UE or the group of UEs behaviour and a second set of analytics information, wherein the second set of analytics information is used to indicate possible analytics information related to UE or group of UE behaviour; and

generate the ASI (101) based on the first support information (103) .
The second entity (200) according to one of the claims 10 to 13, the processor (210) being further configured to:

send, to the first entity (100) , updated ASI (101) for the UE or the group of UEs.
The second entity (200) according to one of the claims 10 to 14, wherein the ASI comprises one or more of:

- identification of the ASI (101) ;

- identification of second entity (200) providing the ASI (101) or first support information (103) ;

- identification of third entity (300) consuming the ASI (101) and/or consuming the analytics information;

- allowed analytics information for a list of UEs or the group of UEs, or allowed analytics information for the list of UEs or the group of UEs per consumer of the analytics information;

- restricted analytics information for the list of UEs or the group of UEs, or restricted analytics information for the list of UEs or the group of UEs per consumer of the analytics information;

- identification of reference point to communicate with the third entity (300) consuming the ASI (101) and/or consuming the analytics information:

- identification of reference point to communicate with the second entity (200) providing the ASI (101) or first support information (103) ;

- identification of the analytics information subscription or request related to the third entity (300) ;

- one or more fields related to the subscription for an analytics information.
A third entity (300) , wherein the third entity (300) is used in a communication network (1) , and the third entity (300) comprising:

a processor (310) configured to obtain, from a first entity (100) or from another third entity (300) , Analytics Subscription Information, ASI, (101) wherein the ASI (101) comprises allowed and/or restricted analytics information for a User Equipment, UE, and/or a group of UEs that are controlled by a second entity (200) , wherein the allowed and/or restricted analytics information are used for controlling the third entity (300) to interact with a fourth entity (400) ; and

the processor (310) being further configured to provide a subscription or a request or an unsubscribe request or a cancelation request (301) to the fourth entity (400) , for one or more third analytics information for the UE or the group of UEs based on the one or more obtained ASI (101) , where one or more third analytics information are based on the analytics information of the one or more obtained ASI (101) , and is used in the interactions between the third entity and fourth entity or vice-versa.
The third entity (300) according to claim 16, wherein the subscription or the request or the unsubscribe request to the fourth entity (400) , for one or more third analytics information comprises at least one of:

- restricted one or more UEs or group of UEs for the generation of the requested third analytics information, where the one or more UEs or group of UEs comprises the UEs or group of UEs of the one or more obtained ASI (101) ;

- consumer relocation information, wherein the consumer relocation information is obtained based on a need for a change of a consumer of third analytics information determined based on the ASI (101) for the specific UEs or group of UEs.
The third entity (300) according to claim 16 or 17, the processor (310) being further configured to:

send, to the first entity (100) , a request for the ASI (101) for the UE or the group of UEs; and/or

receive an ASI response message from the first entity (100) , the ASI response message comprising one or more ASIs (101) or an indication of no available ASI for that sent request.
The third entity (300) according to one of the claims 16 to 18, wherein the request for ASI comprises one or more of:

- identification of the ASI (101) ;

- identification of the analytics information;

- identification of one or more UEs;

- identification of one or more group of UEs;

- identification of the second entity (200) that provided the ASI (101) ;

- identification of the third entity (300) related to the ASI (101) ;

- identification of an existing subscription or request to analytics information;

- identification of reference point to communicate with the third entity (300) .
The third entity (300) according to one of the claims 16 to 19, the processor (310) being further configured to:

send a model training request (102) to a fourth entity (400) based on the obtained ASIs (101) in the ASI response message.
The third entity (300) according to one of the claims 16 to 20, the processor (310) being further configured to:

receive, from the first entity (100) , a notification message, the notification message indicating a change of the ASI (101) .
The third entity (300) according to one of the claims 16 to 21, the processor (310) being further configured to:

provide Analytic Context Information, ACI, (104) to the first entity (100) , wherein the ACI (104) comprises at least one of: an association of a third entity with an ASI (101) , and an association of an ASI (101) obtained by the third entity (300) with an existing subscription or existing request or unsubscription or cancelation (301) for the third analytics information requested by the third entity (300) to the fourth entity (400) , wherein the third analytics information is based on the analytics information of the ASI (101) , and are used in the interactions between the third entity and fourth entity or vice-versa.
The third entity (300) according to one of the claims 16 to 22, wherein the ACI (104) comprises one or more of:

- identification of the third entity (300) ;

- identification of a reference point to communicate with the third entity (300) ;

- identification of the subscribed or requested third analytics information by the third entity (300) ;

- a field related to the subscribed or requested third analytics information by the third entity (300) .
The third entity (300) according to one of the claims 16 to 23, wherein the ASI (101) comprises one or more of:

- identification of the ASI (101) ;

- identification of second entity (200) providing the ASI (101) or first support information (103) ;

- identification of third entity (300) consuming the ASI (101) and/or consuming the analytics information;

- allowed analytics information for a list of UEs or the group of UEs, or allowed analytics information for the list of UEs or the group of UEs per consumer of the analytics information;

- restricted analytics information for the list of UEs or the group of UEs, or restricted analytics information for the list of UEs or the group of UEs per consumer of the analytics information;

- identification of reference point to communicate with the third entity (300) consuming the ASI (101) and/or consuming the analytics information;

- identification of reference point to communicate with the second entity (200) providing the ASI (101) or first support information (103) ;

- identification of the analytics information subscription or request related to the third entity;

- one or more fields related to the subscription for an analytics information.
A fourth entity (400) , wherein the fourth entity (400) is used in a communication network (1) , and the fourth entity (400) comprising:

a processor (410) configured to obtain, from a third entity (300) , a subscription or a request or an unsubscribe request or a cancelation request (301) , for one or more third analytics information for the UE or the group of UEs, the one or more third analytics information for the UE or the group of UEs based on Analytics Subscription Information, ASI, (101) wherein the ASI (101) comprises analytics information for a User Equipment, UE, and/or a group of UEs that are controlled by a second entity (200) , wherein the allowed and/or restricted analytics information are used for controlling a third entity (300) to interact with the fourth entity (400) , and the third analytics information is based on the analytics information of the ASI, and is used in the interactions between the third entity and fourth entity or vice-versa; and

the processor (410) being further configured to send a response to the third entity (300) .
The fourth entity (400) according to claim 25, wherein the subscription or the request or the unsubscribe request or the cancelation request obtained from the third entity (300) , comprises at least one of:

- restricted one or more UEs or group of UEs for the generation of the requested third analytics information, where the one or more UEs or group of UEs comprises the UEs or group of UEs of the one or more obtained ASI (101) ;

- consumer relocation information, wherein the consumer relocation information is obtained based on a need for a change of a consumer of third analytics information determined based on the ASI (101) for the specific UEs or group of UEs.
The fourth entity (400) according to claim 25 or 26, wherein the ASI (101) comprises one or more of:

- identification of the ASI (101) ;

- identification of second entity (200) providing the ASI (101) or first support information (103) ;

- identification of third entity (300) consuming the ASI (101) and/or consuming the analytics information;

- allowed analytics information for a list of UEs or the group of UEs, or allowed analytics information for the list of UEs or the group of UEs per consumer of the analytics information;

- restricted analytics information for the list of UEs or the group of UEs, or restricted analytics information for the list of UEs or the group of UEs per consumer of the analytics information;

- identification of reference point to communicate with the third entity (300) consuming the ASI (101) and/or consuming the analytics information;

- identification of reference point to communicate with the second entity (200) providing the ASI (101) or first support information (103) ;

- identification of the analytics information subscription or request related to the third entity (300) ;

- a field related to the subscription for an analytics information.
The fourth entity (400) according to 25 and 27, wherein the fourth entity (400) is further configured to:

obtain a model training request (102) from the first entity (400) , the model training request (102) indicating a model training for the analytics information for the UE or the group of UEs associated with an obtained ASI (101) needs to be performed by a fourth entity (400) .
A method (1400) being performed by a first entity (100) , the method (1400) comprising:

obtaining (1401) , by a processor (110) , Analytics Subscription Information, ASI, (101) via a configuration by a management entity or received from a second entity (200) , wherein the ASI (101) comprises allowed and/or restricted analytics information for a User Equipment, UE, and/or a group of UEs that are controlled by a second entity (200) , wherein the allowed and/or restricted analytics information are used for controlling a third entity (300) to interact with a fourth entity (400) ; and

providing (1402) , by the processor, the ASI (101) to a third entity (300) .
A method (1500) being performed by a second entity (200) , the method (1500) comprising:

obtaining (1501) , by a processor (210) an analytics subscription information, ASI, (101) wherein the ASI (101) comprises allowed and/or restricted analytics information for a User Equipment, UE, and/or a group of UEs that are controlled by the second entity (200) , wherein the allowed and/or restricted analytics information are used for controlling a third entity (300) to interact with a fourth entity (400) ; and

sending (1502) , by the processor (210) , the ASI (101) to the first entity (100) .
A method (1600) being performed by a third entity (300) , the method (1600) comprising:

obtaining (1601) , by a processor (310) , from a first entity (100) or from another third entity (300) , Analytics Subscription Information, ASI, (101) wherein the ASI (101) comprises allowed and/or restricted analytics information for a User Equipment, UE, and/or a group of UEs that are controlled by a second entity (200) , wherein the allowed and/or restricted analytics information are used for controlling the third entity (300) to interact with a fourth entity (400) ; and

providing (1602) , by the processor (310) , a subscription or a request or an unsubscribe request to the fourth entity (400) , for one or more third analytics information for the UE or the group of UEs based on the one or more obtained ASI (101) , where one or more third analytics information are based on the analytics information of the one or more obtained ASI (101) , and is used in the interactions between the third entity and fourth entity or vice-versa.
A method (1700) being performed by a fourth entity (400) , the method (1700) comprising:

obtaining (1701) , by a processor (410) , from a third entity (300) , a subscription or a request or an unsubscribe request or a cancelation request, for one or more third analytics information for the UE or the group of UEs, the one or more third analytics information for the UE or the group of UEs based on Analytics Subscription Information, ASI, (101) wherein the ASI (101) comprises analytics information for a User Equipment, UE, and/or a group of UEs that are controlled by a second entity (200) , wherein the allowed and/or restricted analytics information are used for controlling a third entity (300) to interact with the fourth entity (400) ; and

sending (1702) , by the processor (410) , a response to the third entity (300) .
A computer program comprising a program code for performing the method (1400, 1500, 1600, 1700) according to one of the claims 29 to 32, when executed on a computer.