CN116134962A

CN116134962A - Apparatus and method for coordinating access of analysis information in a communication network

Info

Publication number: CN116134962A
Application number: CN202080105145.1A
Authority: CN
Inventors: 克拉丽莎·玛奎赞; 里卡多·特里维松诺; 辛阳; 米而科·施拉姆; 吴晓波
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-08-11
Filing date: 2020-08-11
Publication date: 2023-05-16
Also published as: EP4190122A4; WO2022032487A1; EP4190122A1

Abstract

The invention provides a first entity. The first entity obtains analysis subscription information (Analytics Subscription Information, ASI) through a configuration of a management entity or a configuration received from a second entity, wherein the ASI comprises permission and/or restriction analysis information of a user equipment and/or a set of UEs controlled by the second entity, the permission and/or restriction analysis information being used to control a third entity to interact with a fourth entity. The processor also provides the ASI to the third entity. The second entity obtains an ASI and provides the ASI to the first entity. The third entity obtains ASI and provides a subscription or request or an unsubscribe request to the fourth entity. The fourth entity obtains a subscription or request or an unsubscribe or cancel request from the third entity and sends a response to the third entity.

Description

Apparatus and method for coordinating access of analysis information in a communication network

Technical Field

The invention relates to the field of communication networks, in particular to fifth generation mobile or cellular communication (5 ^th generation mobile communication, 5G) systems (5G system,5 GS) and networks. The invention relates in particular to coordinating access to analysis information from a Network data analysis Function (Network Data Analytics Function, NWDAF) used by a Network Function (NF) in a communication Network.

Background

TS 23.288 defines an analysis framework for 3gpp 5gs in release 16 (R16). TS 23.288 specifies that Network Functions (NF), application functions (Application Function, AF), and Operations, administration, and Maintenance (OAM) are allowed to use analysis information (e.g., analysis Identification (ID)) from NWDAF.

The mechanisms and services for analysis use are defined in TS 23.288R16, as well as the types of analysis IDs that can be generated by NWDAF to support analysis users (e.g., NF, AF or OAM) to perform their tasks and to improve the performance of their target tasks.

The currently defined analysis ID, which may be generated by the NWDAF and may be used by the analysis User, may target the analysis of either User Equipment (UE), a group of UEs or a specific UE. Thus, analysis users may subscribe to or request the analysis ID of a particular UE or group of UEs from NWDAF, and based on the analysis ID information received from NWDAF, these analysis users may perform a particular process on these UEs or group of UEs.

Essentially, the analysis ID output of a particular UE (e.g., a list of UEs) or group of UEs (e.g., an identification of a group of UEs or a list of UE groups) reflects the particular characteristics of such an analysis ID indicative of a target (e.g., UE communication, UE mobility, UE service experience, user data congestion, UE anomalous behavior, etc.).

The traditional approach causes AF to affect 5GS NF. For example, the AF may have the capability to provide different sets of information to the 5GS NF, which may affect charging, traffic routing, quality of service (Quality of Service, qoS) requirements, and other requirements specified in TS 23.501 and TS 23.502 for sessions for a particular UE.

Regarding AF and analysis framework interactions, AF may also be allowed to subscribe directly or indirectly through network capability openness (Network Exposure Function, NEF) to analysis IDs generated by NWDAF; the AF may provide the NWDAF with data to be collected for analysis generation.

Furthermore, conventional approaches allow NFs to access or use an analytics ID from NWDAFs, but in some typical scenarios, for example, more than one NF uses an analytics ID from NWDAFs, or a UE moves from one service NF to a second service NF, or a subscription to an analytics ID of a particular UE is migrated from a first NWDAF to a second NWDAF, conventional approaches can lead to some problems.

Disclosure of Invention

In view of the above scenario, coordination between different network elements is required in order to properly control the use of one or more analytical IDs of one or more specific UEs or a group of specific UEs in a mobile network. It is an aim of embodiments of the present invention to provide an entity and method for assisting in triggering 5G NF to interact with NWDAF in a mobile network. Specifically, the embodiment of the invention can solve the problem of suboptimal utilization rate of network resources, unnecessary signaling caused by configuration of the UE or a group of UEs, and the problem of suboptimal utilization rate of network resources for meeting application requirements.

This object is achieved by the embodiments of the invention described in the appended independent claims. Advantageous implementations of embodiments of the invention are further defined in the dependent claims.

Specifically, embodiments of the present invention provide mechanisms for an AF or OAM (e.g., second entity) to affect one or more 5GS NF (e.g., third entity) interactions with NWDAF (e.g., fourth entity). Embodiments of the present invention may implement one or more of the following operations:

AF (e.g., by NEF (e.g., a second entity)) may provide information allowing the 5GS to operate using restrictions available to a particular UE or a group of particular UEs and/or allowing an analysis ID, optionally by defining one or more NFs (types or instances) allowing use of an analysis ID of a particular UE or a group of particular UEs.

If the information provided by the AF is not a direct mapping of the allowed or restricted analysis ID to a specific UE or group, optionally one or more NF users other than the analysis ID, there may be a control plane entity (e.g. NEF or NWDAF) that receives this information and then maps these general descriptions to the exact restrictions available for a specific UE or group of specific UEs and/or the allowed analysis ID (optionally also used by one or more NF (types or instances)). Optionally, the restriction and/or allowance of the analysis ID for a particular UE or a group of particular UEs may also be referred to as ASI hereinafter by defining one or more NFs (types or instances) that allow and/or restrict the use of the analysis ID of the particular UE or group of particular UEs.

ASI may also be stored in a control plane network function (e.g., in Unified DataManagement, UDM) (e.g., first entity) and may be used as a trigger event for one or more NFs to request subscription or unsubscribe analysis IDs from UE registration, session management, UE mobility to an analysis function with reasoning capability (e.g., NWDAF). ASI may be used as a network control function to inform one or more NFs (e.g., AMF, SMF or PCF, which are NFs in 5GS that have heretofore used an analysis ID within a network operator) of changes in the allow/limit analysis ID (optionally also according to NF user definitions of analysis IDs) for a particular UE or a group of particular UEs. Furthermore, ASI may also be used as a trigger for a network control function to request model training (when analysis of IDs is allowed and the model is not yet present) from a training capable analysis function (e.g., NWDAF).

Furthermore, embodiments of the invention may provide one or more of the following advantages:

allowing coordination of mechanisms used in the 5GS and AF to control the UE and/or group of UEs, limiting the occurrence of race conditions when the AF and 5GS use the analytics ID to handle a particular UE and/or group of UEs.

Reducing the chance of performing false actions and generating operator resource wastage with a particular UE and/or a group of UEs that adhere to different patterns with most UEs in the operator network.

The operating costs of automation and maintenance of all NF configurations are reduced. The operator need not keep track of the analysis ID configuration that each NF instance needs to subscribe to for a particular UE and/or group of UEs. This reduces the change management costs for the operator. As NF and UE subscriptions (i.e. new SIM cards) arrive and leave the system, the operator needs to keep the configuration of all NF consistent, which incurs a non-negligible cost. Mismatch of analysis IDs associated with UEs and/or a set of UEs in different NFs may result in different NFs in the system performing different treatments on the UE or set of UEs.

A first aspect of the invention provides a first entity. The first entity is for a communication network, the first entity comprising a processor for: obtaining analysis subscription information (Analytics Subscription Information, ASI) by managing a configuration of an entity or a configuration received from a second entity, wherein the ASI comprises permission and/or restriction analysis information (e.g., an analysis ID) of a UE or a group of UEs controlled by the second entity, the permission and/or restriction analysis information being used to control a third entity to interact with a fourth entity; the processor is further configured to provide the ASI to the third entity.

The first entity may be UDM, NEF, NWDAF or the like, or may be contained in UDM, NEF, NWDAF or the like. The first entity may be configured to manage ASI on a control plane of the mobile communication network.

ASI may be or may include, for example, information defining attributes (e.g., limit and/or allow attributes) of one or more analysis IDs of one or more specific UEs or groups of UEs, and optionally a specific user according to analysis IDs. Additionally, the ASI may also include information regarding subscriptions to one or more analytics IDs, as well as the identity of associated users of analytics IDs associated with such subscriptions to analytics IDs at a given point in time.

Furthermore, the ASI may also include information about the user of the ASI, such as an identification of the user of the ASI and reference point information for interacting with the user of the ASI. The identity of the associated user of the analysis ID may be identical to the identity of the user of the ASI.

Hereinafter, the term "analysis ID of one or more specific UEs or one or more groups of UEs" is equivalent to the term "subscription or request for analysis ID" in which the target of analysis ID is set to a specific UE or groups of UEs. Further, definitions of one or more analysis IDs of one or more specific UEs or groups of UEs are provided when these attributes (e.g., constraint and/or permission attributes) are introduced below.

The first entity can obtain the ASI or obtain the updated ASI, for example, by managing the configuration of the entity or by interacting with the second entity. Further, the first entity may provide the ASI or the updated ASI to a third entity (e.g., an NF such as an AMF, SMF, or PCF). Further, the first entity may provide the second entity with an identification of any stored ASI.

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

One example of indirect acquisition may be that the AF sends ASI to the NEF, which then sends ASI received from the AF to the UDM. The UDM may or may not further process the received information from the ASI. Examples of processing include: the information from the AF is mapped or converted to information that is understandable to the communication network (e.g., the UE ID defined according to the AF is mapped to the UE ID defined according to the communication network).

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

In an implementation manner of the first aspect, the processor is further configured to: one or more identifications of the ASI are provided to the second entity.

In another implementation manner of the first aspect, the processor is further configured to: receiving first support information from the second entity, wherein the first support information comprises a mapping between the behavior of the UE or the set of UEs and a second set of analysis information indicating possible analysis information related to the behavior of the UE or the set of UEs; and/or generating the ASI according to the acquired first support information.

The first support information may be or may include information that may define the requirements of one or more NFs (e.g., AFs) or OAM to affect the use of one or more analysis IDs in the mobile network. The first support information may be used as a reference for a mapping between requirements of one or more AFs or OAM (e.g., in terms of allowed and/or restricted analysis IDs for a particular UE or a group of particular UEs) and analysis IDs available in the communication network and/or analysis IDs of each analysis ID available in the communication network for users of the analysis IDs (e.g., in terms of analysis IDs of each NF user of analysis IDs).

The analysis ID information in the first support information may be used to detect an intersection between the first support information and the second support information (e.g., an available analysis ID in the communication network). The requirement that the analysis ID is allowed or restricted for one or more specific UEs and/or one or more groups of UEs may be used to extend (where allowed) or reduce (where restricted) the authority that NF can use the analysis ID represented in the second support information.

The first support information field may include at least one of the following types of information:

identity of the attribute provider: the identity of the entity providing the first support information. Examples of such identifications are: IP address, NF ID, application ID.

Accurate information: the term defines a list of allowed or restricted analysis IDs for a UE or group of UEs. This information can be represented as tuples: (analyze ID, target UE identity [ list of UEs or group of UEs ], requirement [ allow/restrict ]).

General description (or reference description or analysis function-associated expected UE behavior): UE behavior associated with the analysis ID is defined.

One possible implementation of the general description type of the first support information field may be represented by a tuple (target UE, (optional) network service, behavior and behavior attribute) or the like.

The field type "target UE" in the tuple may represent the UE identity (e.g., UE identity or group UE identity) for which the general description applies.

The field type "web services" in the tuple can be related to mobile web services executable by different NFs. This field is optional and when included may be used to support a determination of which NF (e.g., AMF if mobility management, SMF if session management, PCF if QoS management) is associated with the behavior field. Thus, a "web service" supports NF users that define which analytics ID is allowed and restricted from being applied by the analytics ID.

The field type "behavior" may represent a relationship between one or more analysis IDs (e.g., there is a definition in the 3gpp 5g architecture in TS 23.288, e.g., UE abnormal behavior).

The field type "behavior attribute" may indicate whether a defined behavior (e.g., regular behavior) or a biased behavior (e.g., irregular behavior) is expected. The expected behavior represents that the use of the analytical ID associated with the behavior is allowed; deviation behavior from expected behavior indicates that there is a constraint on using the analytical ID.

Examples of values describing tuples in the first supporting information field are as follows:

(UE ID #1, session management, communication mode, expected bias (e.g., unconventional))

The behavior "communication mode" maps to an analysis ID "UE communication", the expected deviation indicates that such analysis ID should not be generated for the UE or group of UEs, because, for example, the UE or group of UEs has an unusual communication mode.

(list of UEs (id#2, id#3 … …), mobility management, mobility mode, unconventional)

The behavior "mobility pattern" maps to the analysis ID "UE mobility".

(UE group #A, session management, frequent Session request, conventional)

The behavior "frequent session request" is mapped to the analysis ID "UE abnormal behavior".

When an entity supports the use of a generic description in the behavior field, it is also required that the entity has a mapping between the behavior field and one or more specific analysis IDs.

The second support information may be or may include information defining analysis IDs supported (e.g., available) in the communication network, or a mapping between one or more analysis IDs available and users of those analysis IDs, which users are able to use in the communication network.

The second support information is used as a reference for a mapping between requirements from one or more AFs or OAM (e.g., in terms of allowed and/or restricted analysis IDs for a particular UE or a group of particular UEs) included in the first support information and the available analysis IDs and/or one or more users of each available analysis ID in the communication network included in the second support information (e.g., in terms of analysis ID for each user of analysis ID). If the second support information defines one or more analysis IDs for support, this means that these analysis IDs can be used by any user.

In this case, the restriction or permission analysis ID of a particular UE or a group of particular UEs may be applicable to any NF. If the second support information defines a mapping between available analytics IDs and NF users of analytics IDs, this means that NF user applications that can be based on analytics IDs, are allowed or restricted.

The analysis ID in the second support information may assist in detecting an intersection between the first support information and the second support information. The requirement that the analysis ID is allowed or restricted for a particular UE and/or group of UEs may help to extend (where allowed) or reduce (where restricted) the rights of the NF to be able to use the NF of the analysis ID represented in the second support information.

The second support information field may include the following information:

the tuple includes (analyzes the identity of the NF user of the ID type or instance,

a list of supported analysis type identifications (e.g., analysis IDs)).

Further, the request for the second support information field may define an attribute or filter for matching the attribute or filter received in the request with existing second support information. The request for the second support information includes any combination of the following fields:

analysis type identification (e.g., analysis ID)

Analysis of ID identified NF Users (e.g., NF type, such as AMF or SMF or PCF type; or NF instance, such as AMF#1)

In another implementation manner of the first aspect, the processor is further configured to: receiving a request for an ASI for a particular UE or a group of particular UEs from the third entity; and/or sending an ASI response message to the third entity, wherein the ASI response message includes one or more ASIs or an indication that the received request has no ASI available.

In another implementation of the first aspect, the request for ASI includes one or more of:

-an identification of the ASI,

-an identification of the analysis information,

an identification of one or more UEs,

an identification of one or more groups of UEs,

providing an identification of the second entity of the ASI,

an identification of the third entity associated with the ASI,

identification of existing subscriptions or requests to analysis information,

-an identification of a reference point in communication with the third entity.

In another implementation of the first aspect, the ASI includes one or more of the following:

-an identification of the ASI,

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

an identification of the third entity using the ASI and/or using the analysis information,

a list of allowed analysis information for a UE or the set of UEs, or a list of allowed analysis information for a UE or the set of UEs for each user of the analysis information,

a list of UE or a list of UE restriction analysis information of said group of UEs, or a list of UE restriction analysis information of each user of said analysis information,

an identification of a reference point in communication with the third entity using the ASI and/or using the analysis information,

An identification of a reference point in communication with the second entity providing the ASI or the first support information,

an identification of the analysis information subscription or request associated with the third entity,

one or more fields related to analysis information subscription (e.g., analysis filter information, analysis report targets).

In another implementation manner of the first aspect, the processor is further configured to: acquiring updated ASI through configuration of a management entity or configuration received from the second entity; and/or sending a notification message to the third entity, wherein the notification message indicates a change of the ASI.

For example, there may be two ways:

the changed ASI is included in the notification.

The third entity only indicates that a change has occurred and will request an updated ASI.

In addition, if the acquired updated ASI has no ASI user, the first entity may not need to notify any third entity of the changed ASI.

In another implementation manner of the first aspect, the processor is further configured to: receiving analysis context information (Analytic Context Information, ACI) from the third entity, wherein the ACI comprises at least one of: and an association between a third entity and an ASI, and an association between an ASI acquired by the third entity and an existing subscription or an existing request or an unsubscribe or a cancel request for third analysis information requested by the third entity from the fourth entity, the third analysis information being based on the analysis information of the ASI and being used for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity.

ACI may represent an association of a particular NF with an ASI or a particular NF user instance of an analytics ID with a subscription or request or an unsubscribe or unsubscribe request for a particular analytics ID within a given time. The ACI is used to achieve the association of the ASI with the NF user of the ASI, or to achieve the association of the ASI with the existing subscription or request or unsubscribe or cancel request of the NF user of the analysis ID. ACI is issued from the third entity in order to allow the first entity to use the appropriate information to inform the third entity about the changes in ASI. Furthermore, the analysis context information is related to ASI. For example, ACI is a subset of information in ASI.

In another implementation of the first aspect, the ACI includes one or more of the following:

-an identification of the third entity,

an identification of a reference point (e.g. interface or service) in communication with the third entity,

an identification of the third analysis information subscribed or requested by the third entity (e.g., analysis subscription association ID),

fields related to the third analysis information subscribed to or requested by the third entity (e.g., analysis filter information, analysis report targets).

In another implementation manner of the first aspect, the processor is further configured to: and sending a model training request to the fourth entity, wherein the model training request indicates that model training of analysis information of the UE or a group of UEs associated with the acquired ASI needs to be performed by the fourth entity.

The first aspect of the invention may have the following advantages:

first, the first aspect may coordinate a mechanism for an operator in a communication network to use an analysis ID associated with a UE and/or a group of UEs. For example, the UE and/or a group of UEs may be controlled by the second entity and the analytics ID used by the third entity, and thus, race conditions that occur when the second and third entities use analytics IDs from the fourth entity to control a particular UE and/or a group of UEs may be reduced (e.g., restricted).

Second, the first aspect may reduce operational costs for automation and maintenance of all NF configurations (e.g., third entity). For example, the communications network operator need not keep track of analysis ID configurations (e.g., ASIs) that allow or restrict each NF instance to subscribe to for a particular UE and/or group of UEs. This reduces the change management costs for the operator. As NF and UE subscriptions (e.g., new subscriber cards) arrive and leave the system, operators need to keep the configuration of all NFs consistent, which incurs a non-negligible cost.

Third, the first aspect may reduce the chances of performing false actions and generating operator waste of resources with a particular UE or a group of particular UEs that follow different patterns with most UEs in the communication network.

Fourth, the first aspect may reduce variations in mismatch of analysis IDs associated with UEs and/or a group of UEs in different NFs, which may result in different NFs (e.g., third entities) in the communication network performing different treatments on the UE or the group of UEs.

A second aspect of the invention provides a second entity. The second entity is used for a communication network, the second entity comprises a processor, the processor is used for acquiring an ASI, wherein the ASI comprises permission and/or limitation analysis information of a UE and/or a group of UEs controlled by the second entity, and the permission and/or limitation analysis information is used for controlling a third entity to interact with a fourth entity; the processor is also configured to send the ASI to the first entity.

The second entity may be NEF or NWDAF or AF, etc., or may be included in NEF or NWDAF or AF, etc. The second entity may be configured to support ASI management on a control plane of a mobile communication network capable of providing the ASI or an updated ASI to the first entity and retrieving an identification of the stored ASI from the first entity.

The acquisition ASI may be, for example, acquired directly from the second entity, or acquired indirectly from the second entity, or generated from the first support information, or acquired through configuration of the management entity.

Alternatively, the second entity may be configured to: acquiring first support information and/or second support information; an ASI is generated based on at least one of the first support information and the second support information. Further, optionally, the second entity may be configured to: providing the ASI to the first entity according to the generated ASI; other support information is provided to the first entity.

In an implementation manner of the second aspect, the processor is further configured to: one or more identifications of the ASI are received from the first entity.

In another implementation manner of the second aspect, the processor is further configured to: acquiring first support information; and generating the ASI according to the first support information.

In another implementation manner of the second aspect, the processor is further configured to: and sending the updated ASI of the UE or the set of UEs to the first entity.

In another implementation manner of the second aspect, the ASI includes one or more of the following:

-an identification of the ASI;

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

-an identification of the third entity using the ASI and/or using the analysis information;

-a field related to analysis information subscription.

The second aspect of the invention may have the following advantages:

first, the second aspect may coordinate a mechanism for an operator in a communication network to use an analysis ID associated with a UE and/or a group of UEs. For example, the UE and/or a group of UEs may be controlled by the second entity, while the analytics ID is used by the third entity. Thus, it may be reduced (e.g., restricted) that a race condition occurs when the second and third entities use the analytics ID from the fourth entity to control a particular UE and/or a group of UEs.

Second, the second aspect may reduce the chances of performing false actions and generating operator waste of resources with a particular UE or a group of particular UEs that most UEs in the communication network follow different patterns.

Third, the second aspect may reduce variations in mismatch of analysis IDs associated with UEs and/or a set of UEs in different NFs (e.g., third entities), which may result in different NFs (e.g., third entities) in the communication network performing different treatments on the UE or the set of UEs.

A third aspect of the invention provides a third entity. The third entity is for a communication network, the third entity comprising a processor for: obtaining an ASI from a first entity or from another third entity, wherein the ASI comprises permission and/or restriction analysis information of a UE and/or a group of UEs controlled by a second entity, the permission and/or restriction analysis information being used to control the third entity to interact with a fourth entity; the processor is further configured to: providing, to the fourth entity, a subscription or request or an unsubscribe or cancel request for one or more third analysis information of the UE or the group of UEs based on the acquired analysis information of the one or more ASIs and for interaction between the third entity and the fourth entity or between the fourth entity and the third entity, according to the acquired one or more ASIs.

The third entity may be NF such as AMF, SMF, PCF or may be contained in NF such as AMF, SMF, PCF. The third entity may conduct one or more analysis interactions using the ASI. The third entity may be to: acquiring an ASI or an updated ASI from a first entity or from another third entity; a subscription or request for analysis use of one or more specific analysis IDs of one or more specific UEs or groups of UEs is provided to an analysis function (e.g., a fourth entity, e.g., NWDAF), wherein the analysis IDs and the specific UE or groups of UEs are related to the acquired ASI. In addition, a list of restricted UEs or a set of restricted UEs consistent with ASI is included in the subscription or request.

The third entity may also be configured to: providing an unsubscribe or cancel request for an analysis ID of a particular UE or a group of particular UEs, wherein the analysis ID and the particular UE or the group of particular UEs are related to the acquired ASI; the analysis context information is provided to the first entity.

Alternatively, a third entity may be configured to forward ASI information to another third entity.

Further, optionally, for example, when the third entity interacts with the fourth entity, the third entity may be configured to provide the fourth entity with a subscription or request for an analytics ID that includes any of the following fields: a list or set of restricted UEs consistent with ASI, and a user migration flag.

In an implementation manner of the third aspect, the subscription or request or the unsubscribe request for the one or more third analysis information provided to the fourth entity includes at least one of the following:

one or more restricted UEs or a set of restricted UEs for generating the requested third analysis information, wherein the one or more UEs or the set of UEs comprises the acquired one or more ASI UEs or the set of UEs,

-user migration information, wherein the user migration information is obtained by a user modifying, as required, third analysis information determined from ASI of the specific UE or the group of specific UEs.

In another implementation manner of the third aspect, the processor is further configured to: transmitting a request for ASI of the UE or the group of UEs to the first entity; and/or receiving an ASI response message from the first entity, wherein the ASI response message includes one or more ASIs or an indication that the transmitted request has no ASI available.

In another implementation manner of the third aspect, the request for ASI includes one or more of the following:

-an identification of the ASI,

-an identification of the analysis information,

an identification of one or more UEs,

an identification of one or more groups of UEs,

providing an identification of the second entity of the ASI,

an identification of the third entity associated with the ASI,

identification of existing subscriptions or requests to analysis information,

-an identification of a reference point in communication with the third entity.

In another implementation manner of the third aspect, the processor may be further configured to: and sending a model training request to the fourth entity according to the acquired ASI in the ASI response message.

In another implementation manner of the third aspect, the processor may be further configured to: a notification message is received from the first entity, wherein the notification message indicates a change of the ASI.

For example, the notification received from the first entity may have the following two possible ways:

the changed ASI is included in the notification.

In another implementation manner of the third aspect, the processor may be further configured to: providing an ACI to the first entity, wherein the ACI comprises at least one of: and the association between a third entity and an ASI, and the association between the ASI acquired by the third entity and the existing subscription or the existing request or the unsubscribe or the cancel of third analysis information requested by the third entity from the fourth entity, wherein the third analysis information is based on the analysis information of the ASI and is used for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity.

In another implementation of the third aspect, the ACI includes one or more of the following:

-an identification of the third entity,

an identification of a reference point in communication with the third entity,

an identification of the third analysis information subscribed or requested by the third entity,

-a field relating to the third analysis information subscribed or requested by the third entity.

In another implementation manner of the third aspect, the ASI includes one or more of the following:

-an identification of the ASI,

-one or more fields related to analysis information subscription.

The third aspect of the present invention may have the following advantages:

first, the third aspect may coordinate mechanisms by an operator in a communication network for using an analysis ID associated with a UE and/or a group of UEs. The UE and/or the set of UEs may be controlled by the second entity and the analysis ID used by the third entity, and thus, the occurrence of race conditions may be reduced (e.g., restricted) when the second and third entities use the analysis ID from the fourth entity to control a particular UE and/or the set of UEs.

Second, the third aspect may reduce operating costs for automation and maintenance of all NF configurations (e.g., third entity). The communications network operator need not keep track of the analysis ID configuration (e.g., ASI) that allows or restricts each NF instance to subscribe to a particular UE and/or group of UEs. This reduces the change management costs for the operator. As NF and UE subscriptions (e.g., new subscriber cards) arrive and leave the system, operators need to keep the configuration of all NFs consistent, which incurs a non-negligible cost.

Third, the third aspect may reduce the chances of performing false actions and generating operator waste of resources with a particular UE or a group of particular UEs that most UEs in the communication network follow different patterns.

Fourth, the third aspect may reduce variations in mismatch of analysis IDs associated with UEs and/or a group of UEs in different NFs, which may result in different NFs (e.g., third entities) in the communication network performing different treatments on the UE or the group of UEs.

Fifth, the third aspect may optimize resources used by an analysis function (e.g., a fourth entity) by: (a) Allowing the fourth entity to know (e.g., by interacting with the third entity) the UEs or set of UEs that should be deleted from the calculation of the analysis ID, thereby reducing the data collection associated with these UEs and/or the set of UEs; (b) Allowing the analysis function (e.g., fourth entity) to know the NF user to which the analysis ID is migrated (by interacting with the third entity), so that the analysis function can reuse the calculation output and/or data collected from one existing analysis ID subscription of the first NF user of the analysis ID to the second NF user of the analysis ID (i.e., the migrated NF user of the analysis ID); (c) The time to provide the first analysis ID output to the migrating NF user of the analysis ID is reduced because the analysis function can reuse the already trained data model for analysis IDs of a particular UE and/or group of UEs and reuse the collected data for previous analysis ID subscriptions from different NF users to provide the analysis ID output of the migrating NF user of the analysis ID.

A fourth aspect of the invention provides a fourth entity. The fourth entity is for a communication network, the fourth entity comprising a processor for obtaining from a third entity a subscription or request or an unsubscribe or cancel request for one or more third analysis information of a UE or a set of UEs, wherein the one or more third analysis information of the UE or the set of UEs is based on ASI comprising analysis information of a UE and/or a set of UEs controlled by a second entity, the permission and/or restriction analysis information is for controlling the third entity and the fourth entity to interact, the third analysis information is based on the analysis information of the ASI, and is for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity; the processor is further configured to send a response to the third entity.

The fourth entity may be NWDAF or may be included in NWDAF. The fourth entity may be used to generate analytics or analytics model training based on ASI.

The fourth entity may be configured to obtain from the third entity a subscription or request for analysis use of a specific analysis ID of a specific UE or a group of specific UEs, wherein the analysis ID and the specific UE or the group of specific UEs are related to the obtained ASI. In addition, a list of restricted UEs or a set of restricted UEs consistent with ASI is included in the subscription or request.

Further, the fourth entity may be configured to generate an analytics ID output based on the received request. If the request indicates a restriction UE or a set of restriction UEs, this means that the generated analysis does not take into account the restriction UE or the set of restriction UEs.

The fourth entity may also be configured to obtain from the third entity a subscription or request for analysis use of a particular analysis ID of a particular UE or a group of particular UEs, wherein the subscription or request includes a user migration flag that is a result of the third entity determining that a user of one or more analysis IDs of a particular UE or a group of particular UEs related to the obtained ASI needs to be changed.

In an implementation manner of the fourth aspect, the subscription or request or the unsubscribe request or the cancel request may be obtained from the third entity and include at least one of the following:

In another implementation manner of the fourth aspect, the ASI includes one or more of the following:

-an identification of the ASI,

an identification of a reference point in communication with the second entity (200) providing the ASI (101) or the first support information,

-one or more fields related to analysis information subscription.

In another implementation manner of the fourth aspect, the fourth entity may be further configured to: a model training request is obtained from the first entity, wherein the model training request indicates that model training of analysis information of a UE or a group of UEs associated with the obtained ASI needs to be performed by the fourth entity.

The fourth aspect of the present invention may have the following advantages:

first, the fourth aspect may reduce the chance of performing false actions and generating operator waste of resources with a particular UE or a group of particular UEs that follow different patterns with most UEs in the communication network.

The second, fourth aspect may reduce variations in mismatch of analysis IDs associated with UEs and/or a group of UEs in different NFs, which may result in different NFs (e.g., third entities) in the communication network performing different treatments on the UE or the group of UEs.

Third, fourth aspects may optimize resources used by an analysis function (e.g., a fourth entity) by: (a) Allowing the fourth entity to know (e.g., by interacting with the third entity) the UEs or set of UEs that should be deleted from the calculation of the analysis ID, thereby reducing the data collection associated with these UEs and/or the set of UEs; (b) Allowing the analysis function (e.g., fourth entity) to know the NF user to which the analysis ID is migrated (by interacting with the third entity), so that the analysis function can reuse the calculation output and/or data collected from one existing analysis ID subscription of the first NF user of the analysis ID to the second NF user of the analysis ID (i.e., the migrated NF user of the analysis ID); (c) The time to provide the first analysis ID output to the migrating NF user of the analysis ID is reduced because the analysis function can reuse the already trained data model for analysis IDs of a particular UE and/or group of UEs and reuse the collected data for previous analysis ID subscriptions from different NF users to provide the analysis ID output of the migrating NF user of the analysis ID.

A fifth aspect of the invention provides a method performed by a first entity. The method comprises the following steps: the processor obtains an ASI through a configuration of a management entity or a configuration received from a second entity, wherein the ASI comprises permission and/or restriction analysis information of a UE and/or a group of UEs controlled by the second entity, the permission and/or restriction analysis information being used for controlling a third entity to interact with a fourth entity; the processor provides the ASI to the third entity.

In an implementation manner of the fifth aspect, the method further includes: providing the second entity with one or more IDs of the ASI.

In another implementation manner of the fifth aspect, the method further includes: receiving first support information from the second entity, wherein the first support information comprises a mapping between the behavior of the UE or the set of UEs and a second set of analysis information indicating possible analysis information related to the behavior of the UE or the set of UEs; and/or generating the ASI according to the acquired first support information.

In another implementation manner of the fifth aspect, the method further includes: receiving a request for an ASI for a particular UE or a group of particular UEs from the third entity; and/or sending an ASI response message to the third entity, wherein the ASI response message includes one or more ASIs or an indication that the received request has no ASI available.

In another implementation manner of the fifth aspect, the request for ASI includes one or more of the following:

-an identification of the ASI,

-an identification of the analysis information,

an identification of one or more UEs,

an identification of one or more groups of UEs,

providing an identification of the second entity of the ASI,

an identification of the third entity associated with the ASI,

identification of existing subscriptions or requests to analysis information,

-an identification of a reference point in communication with the third entity.

In another implementation manner of the fifth aspect, the ASI includes one or more of the following:

-an identification of the ASI,

-one or more fields related to analysis information subscription.

In another implementation manner of the fifth aspect, the method further includes: acquiring updated ASI through configuration of a management entity or configuration received from the second entity; and/or sending a notification message to the third entity, wherein the notification message indicates a change of the ASI.

In another implementation manner of the fifth aspect, the method further includes: receiving an ACI from the third entity, wherein the ACI comprises at least one of: and the association between a third entity and an ASI, and the association between the ASI acquired by the third entity and the existing subscription or the existing request or the unsubscribe or the cancel request of third analysis information requested by the third entity from the fourth entity, wherein the third analysis information is based on the analysis information of the ASI and is used for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity.

In another implementation manner of the fifth aspect, the ACI includes one or more of the following:

-an identification of the third entity,

an identification of a reference point in communication with the third entity,

In another implementation manner of the fifth aspect, the method further includes: and sending a model training request to the fourth entity, wherein the model training request indicates that model training of analysis information of the UE or a group of UEs associated with the acquired ASI needs to be performed by the 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 invention provides a method performed by a second entity. The method comprises the following steps: the processor obtains an ASI, wherein the ASI comprises permission and/or restriction analysis information of a UE and/or a group of UEs controlled by the second entity, the permission and/or restriction analysis information being used to control a third entity to interact with a fourth entity; the processor sends the ASI to the first entity.

In one implementation manner of the sixth aspect, the method further includes: one or more IDs of the ASI are received from the first entity.

In another implementation manner of the sixth aspect, the method further includes: obtaining first support information, wherein the first support information comprises a mapping between the behavior of the UE or the set of UEs and a second set of analysis information indicating possible analysis information related to the behavior of the UE or the set of UEs; and generating the ASI according to the first support information.

In another implementation manner of the sixth aspect, the method further includes: and sending the updated ASI of the UE or the set of UEs to the first entity.

In another implementation manner of the sixth aspect, the ASI includes one or more of the following:

-an identification of the ASI,

-one or more fields related to analysis information subscription.

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 invention provides a method performed by a third entity. The method comprises the following steps: the processor obtains an ASI from a first entity or another third entity ASI, wherein the ASI comprises permission and/or restriction analysis information of a UE and/or a group of UEs controlled by a second entity, the permission and/or restriction analysis information being used to control the third entity to interact with a fourth entity; the processor provides a subscription or request or unsubscribe request to the fourth entity for one or more third analysis information of the UE or the group of UEs based on the acquired analysis information of the one or more ASIs and for interaction between the third entity and the fourth entity or between the fourth entity and the third entity.

In an implementation manner of the seventh aspect, the subscription or request or the unsubscribe request for the one or more third analysis information provided to the fourth entity includes at least one of the following:

In another implementation manner of the seventh aspect, the method further includes: transmitting a request for ASI of the UE or the group of UEs to the first entity; and/or receiving an ASI response message from the first entity, wherein the ASI response message includes one or more ASIs or an indication that the transmitted request has no ASI available.

In another implementation manner of the seventh aspect, the request for ASI includes one or more of the following:

-an identification of the ASI,

-an identification of the analysis information,

an identification of one or more UEs,

an identification of one or more groups of UEs,

providing an identification of the second entity of the ASI,

an identification of the third entity associated with the ASI,

identification of existing subscriptions or requests to analysis information,

-an identification of a reference point in communication with the third entity.

In another implementation manner of the seventh aspect, the method further includes: and sending a model training request to a fourth entity according to the acquired ASI in the ASI response message.

In another implementation manner of the seventh aspect, the method further includes: a notification message is received from the first entity, wherein the notification message indicates a change of the ASI.

In another implementation manner of the seventh aspect, the method further includes: providing an ACI to the first entity, wherein the ACI comprises at least one of: and the association between a third entity and an ASI, and the association between the ASI acquired by the third entity and the existing subscription or the existing request or the unsubscribe or the cancel of third analysis information requested by the third entity from the fourth entity, wherein the third analysis information is based on the analysis information of the ASI and is used for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity.

In another implementation manner of the seventh aspect, the ACI includes one or more of the following:

-an identification of the third entity,

an identification of a reference point in communication with the third entity,

In another implementation manner of the seventh aspect, the ASI includes one or more of the following:

-an identification of the ASI,

-one or more fields related to analysis information subscription.

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 invention provides a method performed by a fourth entity. The method comprises the following steps: a processor obtains from a third entity a subscription or request or an unsubscribe or cancel request for one or more third analysis information of a UE or a group of UEs, wherein the one or more third analysis information of the UE or the group of UEs is based on analysis subscription information (Analytics Subscription Information, ASI) comprising analysis information of a User Equipment (UE) and/or a group of UEs controlled by a second entity, the permission and/or restriction analysis information being used for controlling the third entity and the fourth entity to interact, the third analysis information being based on the analysis information of the ASI and being used for interactions between the third entity and the fourth entity or interactions between the fourth entity and the third entity; the processor sends a response to the third entity.

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

In another implementation manner of the eighth aspect, the ASI includes one or more of the following:

-an identification of the ASI,

-one or more fields related to analysis information subscription.

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 invention provides a computer program. The computer program comprises program code for performing the method according to any of the fifth to eighth aspects or any implementation thereof.

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

It should be noted that all devices, elements, units and modules described in this application may be implemented in software or hardware elements or any kind of combination thereof. All steps performed by the various entities described in this application, as well as functions to be performed by the various entities described are intended to mean that the respective entities are adapted to perform the respective steps and functions. Although in the following description of specific embodiments, specific functions or steps performed by external entities are not reflected in the description of specific detailed elements of the entity performing the specific steps or functions, it should be clear to a skilled person that these methods and functions may be implemented by corresponding hardware or software elements or any combination thereof.

Drawings

The various aspects and implementations described above will be described in the following description of specific embodiments, with reference to the accompanying drawings, in which:

FIG. 1 is a schematic diagram of a first entity for a communication network provided in one embodiment of the present invention;

FIG. 2 is a schematic diagram of a second entity for a communication network in accordance with one embodiment of the present invention;

FIG. 3 is a schematic diagram of a third entity for a communication network provided by one embodiment of the present invention;

FIG. 4 is a schematic diagram of a fourth entity for a communication network provided by one embodiment of the present invention;

FIG. 5 is a schematic diagram of a process for acquiring or generating an ASI;

FIG. 6 is a schematic diagram of a process for triggering the start/stop of use of an analysis;

FIG. 7 is a schematic diagram of a process for triggering model pre-training;

fig. 8 is a schematic diagram of a first entity taking UDM as an example to obtain ASI;

fig. 9 is a schematic diagram of a first entity taking UDM as an example to obtain ASI according to first supporting information;

FIG. 10 is a schematic diagram of a first entity triggering analysis start/stop use, for example UDM;

FIG. 11 is a schematic diagram of a first entity as a UDM and a third entity as an NF indirectly acquiring an ASI;

FIG. 12 is a schematic diagram of acquiring a change in an ASI;

FIG. 13 is a schematic diagram of trigger model pre-training;

FIG. 14 is a flow chart of a method performed by a first entity provided by one embodiment of the present invention;

FIG. 15 is a flow chart of a method performed by a second entity provided by one embodiment of the present invention;

FIG. 16 is a flow chart of a method performed by a third entity provided by one embodiment of the present invention;

fig. 17 is a flow chart of a method performed by a fourth entity provided by one embodiment of the invention.

Detailed Description

For convenience in describing the present invention, some terms used in the present invention are explained as follows:

analytical procedure (analytics process): this process defines the different possible capabilities that the analysis function may have. In the present invention, consider the following example of an analysis process: analytical reasoning and analytical model training.

Analysis output (analysis output): the term defines the information generated by the analysis function to calculate (e.g., generate) the analysis ID. In the present invention, the term "use of an analysis ID" is equivalent to the term "use of an analysis output of an analysis ID" or simply equivalent to "use of an analysis output".

Analysis ID (analytics ID): the term defines an analysis identity or type that may be generated by an analysis function and used by NFs in the operator network. In the present invention, the term "analysis ID" is synonymous with "analysis information" or "analysis type" or "analysis identification". Examples of analysis IDs include: service experience, UE abnormal behavior, UE mobility, UE communication, etc.

One or more NF users analyzing ID: the term defines NF types (e.g., NF such as AMF or SMF or PCF) or NF instances (e.g., amf#1, amf#2) that can use the analysis ID from the analysis function (e.g., NWDAF).

One or more NF user instances analyzing ID: the term defines a specific instance of NF type that may or may not use an analysis ID from an analysis function (e.g., NWDAF).

NF user of ASI: the term defines an NF (e.g., type or instance) that can acquire and use ASI in order to trigger interaction with analysis functions. Examples of such interactions include: subscription analysis ID, request model training.

NF with model training capability: the term defines that NF is able to perform machine learning model training for a given analytics ID.

Analyzing the properties of the ID: the term "attribute" refers to a feature associated with an analysis ID. The attribute may be an allow analysis ID (which indicates that use of such analysis ID is allowed) or a limit analysis ID (which indicates that use of analysis ID is not allowed).

Traditionally, the method used for trigger analysis is as follows:

the first approach is to define all trigger events for NF, in particular for access and mobility management functions (Access and MobilityManagement Function, AMF), session management functions (Session Management Function, SMF) or policy and charging functions (Policy and Charging Function, PCF). Specifically, the solution defines which UEs can ultimately be decided by AMF and SMF as targets for analysis ID to subscribe to analysis ID from NWDAF.

The second approach is an implicit assumption that if a UE moves from one service NF to a second service NF, the second service NF will automatically analyze the ID for that UE subscription/request.

A third method is to migrate the subscription of the analysis ID of a specific UE from one first NWDAF to a second NWDAF. This principle is also related to UE movement. In this case, the UE moves out of the service area of the first NWDAF, now covered by the second NWDAF. Thus, the subscription to the analytics ID moves to the second NWDAF.

However, one problem with conventional approaches is that, for example, in these approaches, the AF cannot affect the manner in which the NF or OAM subscribes to one or more analysis IDs of one or more specific UEs or a group of specific UEs.

The present invention introduces ASI. The ASI includes admission and/or restriction analysis information for UEs and/or a group of UEs controlled by the second entity, wherein the admission and/or restriction analysis information is used to control interaction of the third entity (e.g., 5GS NF) with the fourth entity (e.g., NWDAF in the 5GS network).

Specifically, the present invention provides a first entity for: an ASI is obtained and provided to a third entity. The invention also provides a second entity for: an ASI is obtained and provided to a first entity. The invention also provides a third entity for: an ASI is obtained and a subscription or request or an unsubscribe request is provided to a fourth entity in accordance with the ASI. The present invention also provides a fourth entity for: and acquiring a subscription or request or a unsubscribe request from the third entity according to the ASI, and sending a response to the third entity.

The invention also proposes corresponding methods, wherein these methods may be performed by a first entity, a second entity, a third entity and a fourth entity, respectively.

Fig. 1 is a schematic diagram of a first entity 100 for a communication network 1 according to one embodiment of the present invention.

The first entity 100 comprises a processor 110 for obtaining the ASI 101 by managing the configuration of the entity or the configuration received from the second entity 200. ASI 101 includes permission and/or restriction analysis information for a UE and/or a group of UEs controlled by second entity 200. The permission and/or restriction analysis information is used to control the interaction of the third entity 300 with the fourth entity 400.

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

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

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

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

The first entity 100 may also include processing circuitry (not shown in fig. 1) for performing, conducting, or initiating various operations of the first entity 100 described herein. The processing circuitry may include hardware and software. The hardware may include analog circuits or digital circuits, or both analog and digital circuits. The digital circuitry may include components such as application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), digital signal processors (digital signal processor, DSP), or multi-purpose processors.

In one embodiment, a processing circuit includes one or more processors and a non-transitory memory coupled to the one or more processors. The non-volatile memory may store executable program code that, when executed by the one or more processors, causes the first entity 100 to perform, or initiate the operations or methods described herein.

Fig. 2 is a schematic diagram of a second entity 200 for the communication network 1 provided in one embodiment of the invention.

The second entity 200 comprises a processor 210 for obtaining the ASI 101.ASI 101 includes permission and/or restriction analysis information for a UE and/or a group of UEs controlled by second entity 200. The permission and/or restriction analysis information is used to control the interaction of the third entity 300 with the fourth entity 400.

The processor 210 of the second entity 200 may also be configured to send the ASI 101 to the first entity 100, wherein the ASI 101 may be sent directly or indirectly through other network elements to the first entity 100.

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

The second entity 200 may also include processing circuitry (not shown in fig. 2) for performing, conducting, or initiating various operations of the second entity 200 described herein. The processing circuitry may include hardware and software. The hardware may include analog circuits or digital circuits, or both analog and digital circuits. The digital circuitry may include components such as application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), digital signal processors (digital signal processor, DSP), or multi-purpose processors.

In one embodiment, a processing circuit includes one or more processors and a non-transitory memory coupled to the one or more processors. The non-volatile memory may store executable program code that, when executed by the one or more processors, causes the second entity 200 to perform, or initiate the operations or methods described herein.

Fig. 3 is a schematic diagram of a third entity 300 for the communication network 1 provided in one embodiment of the invention.

The third entity 300 comprises a processor 310 for retrieving the ASI101 from the first entity 100 or from another third entity 300. ASI101 includes permission and/or restriction analysis information for a UE and/or a group of UEs controlled by second entity 200. The permission and/or restriction analysis information is used to control the interaction of the third entity 300 with the fourth entity 400.

The processor 310 of the third entity 300 may also be configured to provide a subscription or request or an unsubscribe request or a cancel request 301 for one or more third analysis information of the UE or the group of UEs to the fourth entity 400 according to the acquired one or more ASIs 101, wherein the one or more third analysis information is based on the acquired analysis information of the one or more ASIs 101 and is used for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity.

The processor 410 of the fourth entity 400 may also be used to provide the ACI 104 to the first entity 100.

The third entity 300 may also include processing circuitry (not shown in fig. 3) for performing, conducting, or initiating various operations of the third entity 300 described herein. The processing circuitry may include hardware and software. The hardware may include analog circuits or digital circuits, or both analog and digital circuits. The digital circuitry may include components such as application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), digital signal processors (digital signal processor, DSP), or multi-purpose processors.

In one embodiment, a processing circuit includes one or more processors and a non-transitory memory coupled to the one or more processors. The non-transitory memory may store executable program code that, when executed by the one or more processors, causes the third entity 300 to perform, or initiate the operations or methods described herein.

Fig. 4 is a schematic diagram of a fourth entity 400 for the communication network 1 provided in one embodiment of the invention.

The fourth entity 400 comprises a processor 410 for obtaining from the third entity 300 a subscription or request or an unsubscribe or cancel request 301 for one or more third analysis information of a UE or a group of UEs, wherein the one or more third analysis information of a UE or a group of UEs is based on the ASI 101.ASI 101 includes analysis information for UEs and/or a group of UEs controlled by second entity 200, allowing and/or limiting analysis information for controlling interaction of third entity 300 with fourth entity 400, the third analysis information being based on analysis information of the ASI and for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity.

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

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

The fourth entity 400 may include processing circuitry (not shown in fig. 2) for performing, conducting, or initiating various operations of the fourth entity 400 described herein. The processing circuitry may include hardware and software. The hardware may include analog circuits or digital circuits, or both analog and digital circuits. The digital circuitry may include components such as application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), digital signal processors (digital signal processor, DSP), or multi-purpose processors.

In one embodiment, a processing circuit includes one or more processors and a non-transitory memory coupled to the one or more processors. The non-volatile memory may store executable program code that, when executed by the one or more processors, causes the fourth entity 400 to perform, or initiate the operations or methods described herein.

Next, the present invention is exemplarily discussed in terms of mechanisms by which NF (e.g., trusted AF, external AF, control plane functions in general) or OAM (e.g., management plane) affects 5GS NF interactions with NWDAF.

The trusted AF may be an AF that an operator of the communication network allows to invoke NF-open services or interfaces of a control plane of the communication network, wherein the AF may invoke NF-open services or interfaces directly.

The external AF may be a specific type of NF that does not allow a service or reference point to be invoked from any other NF of the control plane of the communication network. The external NF communicates with the other control plane NF through a specific NF, such as network capability opening (Network Exposure Function, NEF). Thus, in a communication network, an AF may communicate with other NFs, where such communication may be direct or indirect, without limitation of the invention.

Hereinafter, for convenience of description and not limitation of the present invention, the above mechanism is divided into the following three parts: part a, part B and part C.

Part A: this portion of the invention is illustratively discussed as defining a set of steps between the first entity 100 and the second entity 200 in the present invention to allow the first entity 100 to obtain ASI.

Part B: this portion of the invention is illustratively discussed as defining a set of steps for interaction mechanisms between the first entity 100, the second entity 200, and the third entity 300 to trigger starting or stopping interactions between the third entity 300 and an analysis function (e.g., the fourth entity 400) using the ASI 101.

Part C: this portion of the invention is illustratively discussed as a set of steps defining an interaction mechanism between the first entity 100 and the fourth entity 400 to trigger interactions with analysis functions (e.g., the fourth entity 400) using ASI 101 for model training.

It should be noted that the mechanism is divided into three parts, and the contents of the three parts can be easily combined for the skilled person, and the mechanism described in the three parts forms the whole technical scheme for convenience of description.

Furthermore, the invention is discussed below on the basis of the first entity 100 being UDM-based and for ASI101 management. Further, the second entity 200 is AF or NEF or NWDAF based and is adapted to support ASI101 management. Further, the third entity 300 is an entity that performs analysis interactions using ASI101, for example, an AMF or SMF for triggering a subscription to analysis information; or NWDAF that triggers a model training request for another NWDAF with training capabilities, etc.

It should be noted that the following examples should not be construed as limiting the present invention. For example, the first entity may be some other control element than UDM. For other entities, some other network elements than the exemplary entities listed above are also possible.

Referring now to fig. 5, fig. 5 is a schematic diagram of an acquisition or generation ASI 101.

Section a includes a set of steps of the present invention that reflect interactions between entities until ASI101 is stored in first entity 100. Furthermore, the first entity 100 obtaining the ASI101 discusses three different alternatives. These alternatives are determined by the different circumstances indicated in step 501, as described below.

In 501, the first entity 100 obtains ASI101 through configuration. This step defines possible alternatives for the first entity 100 to acquire the ASI 101. Each case is described in detail below.

Case # a.1:ASI101 is obtained by configuration (e.g., from a management plane).

In this case (in step 1 of 501), ASI101 may be configured in first entity 100. Such configuration may be performed by a management entity or the like before the first entity 100 starts to perform or in the first network entity. For example, ASI101 may be configured in a file that may be loaded by first entity 100 and may be stored in a runtime memory of that entity 100.

Alternatively, ASI101 may be configured directly in a database and the management plane entity may configure a boot file in first entity 100 to indicate a reference to ASI101 associated with that first entity 100.

Alternatively, the first entity may open a service that the management entity may invoke in order to configure the ASI in the first entity.

Case # a.2:acquiring ASI101 from second entity 200:

in this case, there may be direct and/or indirect interaction between the first entity 100 and the second entity 200.

The direct interaction may include the second entity 200 itself having access to the first entity 100 (e.g., directly invoking a service opened by the first entity). An indirect interaction may be, for example, another entity between the first entity 100 and the second entity 200 that forwards and/or sends any information exchange between the first entity 100 and the second entity 200.

For indirect interaction, when the intermediate entity is used for forwarding, no changes are made to the messages to and from the first entity 100 and the second entity 200. Alternatively, the intermediate entity may further process messages to and from the first entity 100 and the second entity 200 when the intermediate entity is used for transmission.

Examples of further processing of intermediate entities include: mapping information different between the first entity 100 and the second entity 200, such as UE ID format information; or converts a network attribute indicated by one of the entities into a network attribute understandable by the other entity, e.g. a region of interest sent by the second entity 200 in the form of a path and converted by an intermediate entity into a list of Tracking Areas (TAs), before sending a message to the first entity 100.

Mapping or converting information exchanged between the first entity 100 and the second entity 200, however, does not limit the type of further processing that the intermediate entity may perform when sending information between the first entity 100 and the second entity 200.

In 502 (e.g., in a first step of 502), ASI 101 is available in second entity 200 in this case. The second entity 200 provides the ASI 101 to the first entity 100 (directly or indirectly through an intermediate entity as described above). In this step, the interaction between the second entity 200 and the first entity 100 may use different mechanisms. Examples of these mechanisms are defined as follows:

The first entity 100 may open a service that the second entity 200 may invoke. This type of interaction follows the request-response model of communication. The input parameters of the service operation of the service may include a field with ASI 101.

The second entity 200 may invoke a service operation from the first entity 100 whenever the second entity 200 determines that the ASI 101 needs to be provided to the first entity 100. The ASI 101 provided may include tuples: (identity of the attribute provider (e.g., identity of the second entity 200 itself), allowed analysis IDs for a list U or group of UEs (optionally, each NF user of analysis IDs), restricted analysis IDs for a list of UEs or group of UEs (optionally, each NF user of analysis IDs)).

It should be understood that the above-described tuples are exemplary only, and that the tuples may also include one or more of the above-described parameters, or may also include more parameters in the tuples, which are not limiting of the invention.

Alternatively, the second entity 200 may open a service that the first entity 100 may invoke. This type of interaction between

entities

100 and 200 may follow an asynchronous communication model, e.g., based on a callback procedure or subscription-notification model. In this case, the input parameter of the service operation may be an identification of the first entity 100, or a reference point (e.g., interface or service endpoint address) of the first entity 100 that allows the second entity 200 to send the ASI 101 to the first entity 100, or an ASI 101 request field (e.g., an analytics ID, or a specific UE, or a specific set of UEs).

The second entity 200 may match the value of the ASI 101 request field with the available ASI 101 and may send the ASI 101 including the following tuples through a reference point notified by the first entity 100: (identity of the attribute provider (e.g., identity of the second entity 200 itself), allowed analysis IDs for a list of UEs or a group of UEs (optionally, each user of analysis IDs), restricted analysis IDs for a list of UEs or a group of UEs (optionally, each NF user of analysis IDs)).

In addition, the second entity 200 may include a reference point (e.g., interface or service endpoint address) of the second entity 200 in the message sent to the first entity 100 that allows the first entity 100 to send the identity of the ASI 101 to the second entity 200 (e.g., in step 2). The first entity 100 may be configured to periodically invoke the service operation of the second entity 200 in order to retrieve the ASI 101 or may also instruct the second entity 200 in a first message sent to the second entity 200 about the period in which the ASI 101 tuple is sent to the first entity 100.

If the communication between the first entity and the second entity 200 is indirect, the entity forwarding the communication may have a mirror image of the services opened by the first entity 100 so that the second entity 200 may invoke such services. The forwarding entity then forwards any messages 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: ASI 101 generated from further processing is acquired.

In this case, ASI 101 is not available in second entity 200, so ASI 101 needs to be generated before ASI 101 is provided to first entity 100. Before the second entity 200 can provide ASI 101 information to the first entity 100, a number of steps involving the second entity 200 need to be performed. These steps are described below.

In 503 (step 1 a): the second entity 200 is able to obtain the first support information. The second entity 200 may use different mechanisms to obtain the first support information. Some of which are listed below:

the first support information may be configured in the second entity 200 by a management entity or the like. A similar configuration mechanism discussed in step 1 under case #a.1 may also be applied to step 1a under case #a.2.

Alternatively, the first support information may be obtained from other entities of the mobile communication network, such as one or more AF or application servers or OAM, which may support the generation of the analysis subscription information. In this case, the second entity 200 may open services that other entities may invoke. The input parameters of the service operation opened by the second entity 200 include a first support information field.

In 504 (step 1 b): alternatively, the second entity 200 can obtain the second support information. The second entity 200 may use different mechanisms to obtain the first support information. Some of which are listed below:

the second support information may be configured in the second entity 200 by a management entity or the like. A similar configuration mechanism discussed in step 1 under case #a.1 may also be applied to step 1b under case #a.2.

The second support information may be obtained from other entities of the mobile communication network, e.g. from one or more AFs or OAM, which may support the generation of analysis subscription information. In this case, the second entity 200 may invoke a service opened by other entities (e.g., other NFs, such as 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 a request for a second support information field.

In 505 (step 1 c): optionally, the second entity 200 generates the ASI 101 according to the first support information and the second support information. For example, ASI 101 may be generated by a mapping between fields of the first support information and the second support information. According to the type of the acquired first supporting information, the generation modes are different:

In the case of the first support information acquired using the accurate information, the ASI 101 may be generated by:

(A) The intersection may be identified using the analysis ID as an index from the intersection of the first support information and the second support information, thereby creating the first group of tuples. The tuples in the first support information and the second support information that include the same analysis ID are selected as the first group of tuples.

(B) The second group of tuples may be created by merging fields of tuples in the first group of tuples having the same analysis ID. The second set of tuples may be included in ASI 101, ASI 101 representing "allowed analysis ID of each NF user of analysis ID of a list of UEs or a set of UEs" (if the attribute of analysis ID is allowed), or "restricted analysis ID of each NF user of analysis ID of a list of UEs or a set of UEs" (if the attribute of analysis ID is restricted).

In the case of the first support information acquired by the general description, the ASI 101 may be generated by:

the first step may be to perform a mapping of the behavior field of the first support information to the analysis ID and a mapping of the behavior attribute field to an allow or limit attribute of the analysis ID. The second entity 200 may be configured with a mapping between possible values of the behavior field and the associated analysis ID and a mapping between behavior attributes and analysis ID attributes. The output of the mapping procedure may be a set of tuples including the target UE and the mapped analysis ID received in the first support information.

Then, the second entity 200 may perform the same steps (a) and (B) described in the case of the first support information acquired using the accurate information.

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

in accordance with processing the output of the first support information and the second support information, the second entity 200 is capable of generating an ASI 101 tuple (e.g., creating a data structure), the tuple comprising:

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

Allowing analysis of ID: optionally, each NF user of the analytical ID of a list of UEs or group of UEs: the second entity 200 may include in this field tuples in the mapping between the first support information and the second support information, which tuples serve as attributes for "allow" the analysis ID.

Restriction analysis ID: optionally, each NF user of the analytical ID of a list of UEs or group of UEs: the second entity 200 may include in this field tuples in the mapping between the first support information and the second support information, which tuples serve as attributes for "restricting" the analysis ID.

In 506 (step 1 d): the second entity 200 may provide the generated ASI 101 tuples to the first entity. The information sent to the second entity 200 may include one or more of the following ASIs 101: (identification of the attribute provider, allowed analysis ID for each NF user of analysis ID for a list of UEs or a group of UEs, restricted analysis ID for each NF user of analysis ID for a list of UEs or a group of UEs). The same interaction mechanism between the first entity and the second entity described in case #a.2 may also be applied to step 1d in case #a.3.

Note that if the first entity 100 is able to operate under either case #a.2 or case #a.3, only 507 (step 2) and 508 (step 3) are performed.

In a further implementation of the present proposal, the first entity 100 may perform a combination of the parts of case #a.2 and case #a.3. In this case, the second entity 200 may provide 502 the first support information to the first entity 100. The first entity can then perform 504 (step 1 b) and 505 (step 1 c) and generate an ASI from the first support information obtained from the second entity (200) and/or from the second support information. The first entity 100 also performs 507 (step 2) and 508 (step 3).

In 507 (step 2): alternatively, the first entity 100 may store the acquired ASI 101. In this step, the first entity 100 may extend the content of the ASI 101, including an identification of the field ASI 101, which uniquely identifies the ASI 101 information provided by the second entity.

Thus, if there are multiple instances where the second entity 200 provides ASI 101 tuples to the first entity 100, each of these ASI 101 tuples retrieved from the second entity 200 is uniquely identified and stored as a distinct record in the first entity 100. The first entity 100 may use an increment counter or the like to define such an identification or a more complex mechanism based on a hash algorithm of the identification of the attribute provider with some other unique information inside the first entity 100.

In 508 (step 3): the first entity 100 may provide the identification of the ASI 101 to the second entity 200. Examples of these mechanisms are as follows:

in case the first entity 100 opens a service that the second entity 200 can invoke: for example, the second entity 200 may send the ASI 101 tuple as an input parameter for the operation of the service open by the first entity 100. Thus, the output parameters of the same service would include the identity of ASI 101 associated with a particular second entity.

In case the second entity 200 opens a service that the first entity 100 can invoke: the first entity 100 may receive a reference point from the second entity 200 in step 1 to send the identity of the ASI 101 to the second entity 200. The first entity 100 may use the reference point to send the identity of the 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 communication will have a mirror image of the service opened by the first entity 100 or the second entity. The forwarding entity may be responsible for sending information (e.g., an identification of ASI 101) exchanged from the first entity 100 or the second entity 200 to the second entity 200 or the first entity 100.

Referring now to fig. 6, fig. 6 is a schematic diagram of a process of triggering the start/stop of the analysis.

Part B includes steps reflecting interactions between the first entity 100 and the third entity 300, wherein the third entity 300 is a user of the ASI 101.

It may be assumed that the steps of part B of the present invention may be performed after part a.

The third entity 300 may play different roles, their relationships will be described in further detail in the description of each case in section B. The roles considered include:

NF user or ASI 101: in this role, the third entity 300 may interact directly with the first entity 100 to obtain the ASI 101 from the first entity 100 or to send an ACI related to the ASI 101 to the first entity 100.

NF user analyzing ID: in this role, the third entity 300 may interact with an analysis function (e.g., NWDAF) to trigger starting (e.g., triggering a subscription or request for an analysis ID) or stopping (e.g., unsubscribing or canceling an analysis ID) analysis usage.

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

Furthermore, the first entity 100 and the third entity 300 interact to use the ASI 101 to trigger starting or stopping of the use of the analysis in the mobile network there are at least three possible alternatives including B1, B2 and B3. Each of these alternatives is described below.

Case # b.1: direct request ASI 101: in this case, third entity 300 may be an NF user of ASI 101, who may interact directly with first entity 100 to obtain ASI 101 to support NF users of ASI 101 to trigger subscription or request for an analytics ID (i.e., start using analytics) or to trigger unsubscribing or cancel an analytics ID (i.e., stop using analytics). The steps of the performed interaction are as follows.

In 601 (step 1): the third entity 300 may send a request (e.g., a request for an ASI) for the first entity 100 to retrieve the ASI 101. In this step, the interaction between the first entity 100 and the third entity 300 may use different mechanisms. Such mechanisms are exemplified as follows:

in one example, the first entity 100 may open a communication-compliant request-response model service that the third entity 300 may invoke. The third entity 300 invokes service operations from the first entity 100 based on lifecycle events related to one or more UEs or a group of UEs that the third entity 300 is serving (i.e., the third entity 300 is playing the service NF of some UE or groups of UEs), or based on local policies defined by the mobile network operator.

The input parameters for the service operation include an ASI 101 request field defined by the present invention. For example, if it is the first time the third entity 300 interacts with the first entity 100, the input parameters may include one or more of the following: an identification of the analysis ID, an identification of one or more UEs or a group of UEs, an identification of the NF user of the analysis ID (i.e. an identification of the third entity 300 itself, e.g. NF ID).

The third entity 300 may also be used to periodically retrieve ASI 101 through a local operator policy. In this case, the third entity 300 may comprise the aforementioned parameters (obtained from the first entity 100 as described in step 3 a) with or without the identification of the ASI 101.

In a second example, the first entity 100 may open a subscription-notification model-compliant service of communication that the third entity 300 may invoke. The third entity 300 may invoke a service operation from the first entity 100 according to the following:

(a) Lifecycle events related to one or more UEs or a group of UEs that the third entity 300 is serving (i.e., the third entity 300 acts as a serving NF for certain UEs or a group of UEs), or

(b) A mobile network operator defined local policy.

In this case, the input parameter of the service operation may be an ASI 101 request field, as the input parameter may be one or more of the following: an analysis ID, a particular UE, a group of particular UEs, an identification of NF users of the analysis ID (e.g., the third entity 300 may indicate its own identification, such as NF ID and/or NF type) or a reference point of the third entity 300 (e.g., an interface or service endpoint address, which may allow the first entity 100 to send a notification including the ASI 101 to the third entity 300).

The second entity 200 may match the value of the ASI 101 request field with the available ASI 101 and the reference point notified by the first entity 100 sends an ASI 101 comprising the following tuples: (identification of the attribute provider (e.g., identification of the second entity 200 itself), allowed analysis ID of each NF user of analysis ID of a list of UEs or a group of UEs, restricted analysis ID of each NF user of analysis ID of a list of UEs or a group of UEs).

The understanding of the tuples is as described before and will not be repeated.

In 602 (step 2): from the request received from the third entity 300, the first entity 100 may use the ASI 101 request field in the received request (e.g., a request for ASI) to determine where there is a matching ASI 101 from any combination of: the analysis ID, the identity of the UE, the identity of a group of UEs, the identity of the NF user who analyzed the ID (e.g., by NF type or NF instance).

In this sense, the first entity 100 may determine one or more ASIs 101 to provide to the third entity 300 based on the ASI 101 request field included in step 1 (601). For example, ASI 101 request may include an analysis ID field set to "any". This means that the third network entity is requesting any ASI 101 stored in the first entity 100 that is associated with the "analysis ID" request of the third entity 300.

In the following steps (step 3, including step 3a and step 3 b): after the first entity 100 performs the matching between the requested ASI101 field and the stored ASI101, the first entity 100 may determine whether one or more ASI101 are provided to the third entity 300.

In 603 (step 3 a): if there are one or more ASIs 101 to provide 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 a request-response model, the output parameters of the service that the first entity 100 opens (invoked by the third entity 300 as described in step 1) may include a list of matching ASIs 101 and their associated ASI101 identities.

If the communication model between the first entity 100 and the third entity 300 is a subscription-notification model, the output parameters of the service that the first entity 100 opens (as described in step 1, invoked by the third entity 300) may include a list of ASI101 identities, and the first entity 100 may send one or more matching ASI101 information (e.g., as a notification message) to the third entity 300 via a reference point indicated in a request (e.g., a request for ASI) received from the third entity 300.

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

In 604 (step 3 b): if no ASI101 is to be provided to the third entity 300, the first entity 100 sends a message to the third entity 300, wherein the message includes an indication that no ASI101 is available for any combination of values included in an ASI101 request field sent by the third entity 300.

Step 4 includes step 4a (605) and step 4b (406): based on the information received from the first entity, the third entity 300 may trigger further interactions with an analysis function (e.g., NWDAF) to analyze the ID based on one or more received ASI101 subscriptions (or requests) or unsubscribes (or cancel requests).

In 605 (step 4 a): if the third entity 300 receives an indication that no ASI101 is present, the third entity 300 may determine itself a subscription analysis ID and also which particular UEs or group of particular UEs are to be used as analysis targets when subscribing to or requesting an analysis ID for an analysis function (e.g., NWDAF).

If the third entity 300 receives one or more ASI101 including an allowed analysis ID for a particular UE or a group of particular UEs, the third entity 300 may subscribe to or request an analysis ID for an analysis function (e.g., NWDAF) using the analysis ID and the associated particular UE or group of particular UEs for each ASI101 received.

If the interaction between the third entity 300 and the analytics functionality may follow a subscription-notification model, the third entity 300 may also modify the existing subscription of analytics IDs (matching the same analytics ID in ASI 101) in the analytics functionality including a particular UE or a group of particular UEs, instead of creating a new subscription request for analytics functionality.

In 606 (step 4 b): if the third entity 300 receives one or more ASI 101 including a restriction analysis ID of a particular UE or a group of particular UEs, which are restricted in the one or more ASI 101, the third entity 300 may not trigger any new subscriptions or requests for analysis IDs.

If the third entity 300 has triggered a subscription or request for an analysis ID of a particular UE or group of particular UEs limited by one or more ASIs before acquiring the one or more ASIs, the third entity 300 unsubscribes or cancels the request for such an analysis ID of the particular UE or group of particular UEs by interacting with the analysis function.

If the interaction between the third entity 300 and the analysis function may follow a subscription-notification model, the third entity 300 may also modify the existing subscription of the analysis ID in the analysis function (matching the same analysis ID in ASI 101), delete a particular UE or a group of particular UEs from the existing subscription, instead of completely unsubscribing and creating a new subscription using only unrestricted parameters (e.g., target UEs).

Optionally, the services opened by the analysis function (e.g., fourth entity 400 or NWDAF) may be extended to allow NF users of the analysis ID (e.g., third entity 300) to indicate in the subscription or request the analysis target (e.g., the UE or set of UEs that should be included in the analysis ID calculation) and the limitation target of the analysis (e.g., the UE or set of UEs that must not be included in the analysis ID calculation).

Optionally, in 607 (optional step 5): based on the information received from the first entity 100, the third entity 300 may trigger in step 4 an interaction with an analysis function (e.g., NWDAF) to analyze the ID based on one or more received ASI 101 subscriptions (or requests) or unsubscribes (or cancel requests).

In step 5, the third entity 300 may provide the first entity 100 with analysis context information (Analytics Context Information, ACI) associated with each received ASI 101. The mechanism for such interaction between the first entity and the third entity 300 is based on the first entity 100 opening a service (or interface). For example, using the request-response mode of operation, the third entity 300 may invoke a service operation of the first entity 100 and may include one or more ASI 101 identifications as input parameters and an associated ACI including each ASI 101.

Note that 618 or step 6 may be performed in all cases described in section B.

In 617 (step 6): the first entity 100 may receive one or more ASI 101, an associated ACI for each ASI 101, and an identity of each received ASI 101 from the third entity 300, and the third entity 300 may update the respective stored ASI 101, including ACI information for such ASI 101 identities.

Case # b.2: ASI 101 is obtained indirectly. In this case, the third entity 300 may play two roles: NF serving UE or NF using analytical ID. The third entity 300 may obtain the ASI 101 without directly interacting with the first entity 100 to retrieve the ASI 101.

At 608 (step 1): in a mobile network, a UE may move from a first serving NF (i.e., NF serving the UE) to a new serving NF (i.e., new NF serving the UE). As a UE moves in the network, the context of such UE, i.e. all information required to provide mobile services to such UE, moves from a first service NF to a new service NF.

Thus, the present invention defines that the first third entity 300 playing the NF serving the UE may comprise ASI 101 and ASI 101 identification as part of the UE context.

The second third entity 300 (playing a new NF serving the UE) may indirectly obtain the ASI 101 by interacting with the first third entity 300. It may also be assumed that the first third entity 300 performs case #b.1 at a given point in time, thereby obtaining ASI 101 and ASI 101 identities of the analysis IDs of the UE or a group of UEs for the first time.

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

In 609 (steps 2 a) and 610 (step 2 b): based on ASI 101 obtained from another third entity 300, third entity 300 may perform the same actions as described in steps 4 (a and b) in case #b.1.

In 611 (step 3): the same actions as described in step 5 in case #b.1 are performed. The only difference may be that the ACI is related to the new NF user analyzing the ID, which is the third entity 300 acting as the new NF serving the UE. In addition, step 6 described in case #b.1 is also performed in case #b.2 as a final step.

Case # b.3: acquired changes in ASI 101: in this case, the present invention assumes that:

(a) There is a third entity that has retrieved ASI 101 (i.e., third entity 300 is an NF user of ASI 101);

(b) The second entity 200 may send the updated ASI 101 to the first entity. The updated ASI 101 sent by the second entity 200 to the first entity 100 may trigger the first entity 100 to interact with a third entity (NF user of ASI 101) to provide the updated ASI 101 to one or more third entities 300 (i.e., NF users of ASI 101).

At 612 (step 1): the third entity 300 may obtain ASI101 according to case #b.1 or case #b.2. The third entity 300 may be an NF user of an analysis ID of a specific UE or a group of specific UEs related to one or more acquired ASIs 101 that allows the analysis ID; alternatively, the third entity 300 may not be an NF user of the analytics ID, as the one or more ASIs 101 define a restricted analytics ID for a particular UE or group of particular UEs.

In 613 (step 2): the second entity 200 may provide one or more updated ASI101 or new ASI101 or updated first support information or new first support information to the first entity 100. The mechanism by which this occurs is similar to that described in step 1d under case #a.2 or case #a.3. When the second entity provides updated or new first support information, the first entity may generate an associated ASI 100 defined in the description of the portions of the cases #a.2 and #a.3 that the first entity is able to perform. Thus, after generation, the first entity may have an updated or new ASI 100.

In 614 (step 3): the first entity 100 may determine, for each updated ASI101, an ASI101 in which the attribute of the analysis ID has changed.

Examples of modifications may be (but are not limited to):

-a change of state from allowed to restricted analysis ID to all UEs or a group of UEs of the stored ASI 101;

-including or deleting a UE or a group of UEs in the permission or restriction analysis ID;

a specific NF user including or deleting an analysis ID in ASI 101 for a UE or a group of UEs to allow or restrict the analysis ID.

In the case of a new ASI 101, the first entity 100 may check whether there are any ACIs associated with the stored ASI 101, e.g., one or more information of the ASI related to the analysis subscription identification, the identification of the ASI and/or the user of the analysis ID, and one or more fields of the analysis subscription, may be affected by the new ASI 101.

Based on these performed identifications and checks, the first entity 100 is able to determine NF users of ASI 101 that are affected by the changed or new ASI 101.

One or more of the values of the ASI 101 field may be:

(a) Identification of NF user of ASI 101;

(b) Identification of NF user instances for an existing subscription for an analysis ID for a list of UEs or a group of UEs;

(c) Identification of a reference point (e.g., interface or service) in communication with NF user instances of an existing subscription to an analysis ID of a list of UEs or a group of UEs that allow the analysis ID or in communication with NF users of ASI 101;

The first entity 100 may interact with the third entity 300 according to the above-described fields and may provide the entity with an ASI101 and its associated ASI101 identification, wherein the altered ASI101 or an ASI101 added to the memory of the first entity 100 affects the third entity 300 as NF user of the analysis ID.

Examples of the effect of the added ASI101 are, for example, that an ASI101 may be added, that a certain analysis ID to be used for a certain UE or a group of UEs may now be restricted, that the ACI of a different ASI101 (an ASI101 already stored) comprises information of such an analysis ID presence analysis subscription with a new restricted UE or a group of UEs.

In 615 (steps 4 a) and 616 (step 4 b): based on ASI101 obtained from first entity 100, third entity 300 may perform the same actions as described in steps 4 (a and b) in case #b.1.

In 617 (step 5): the same operations as described in step 5 in case #b.1 may be performed.

At 618 (step 6): the same operations as described in step 6 of case #b.1 may be performed.

Referring now to fig. 7, fig. 7 is a schematic diagram of a process of triggering model pre-training.

Part C includes steps reflecting interactions between the first entity 100 and the fourth entity 400, the fourth entity 400 operating as NF with model training capabilities.

It is assumed that the step of part C may optionally be performed after part a.

In 701 (step 1): the first entity 100 may check the stored ASI 101 information and the permission analysis ID of a particular UE or a group of particular UEs. Alternatively, the first entity may only identify ASIs without ACI information associated with the ASI. For example, there is an ASI associated with a field user of the ASI that is not null, but the ASI field of the analysis subscription of the ASI is null.

In 702 (step 2): based on ASI 101 associated with the allowed analysis ID of a particular UE and without ACI information, first entity 100 may send an indication to fourth entity 400 that a model needs to be trained for the analysis ID of the particular UE or a group of particular UEs.

In 703 (step 3): for requests received from the first entity, the third entity 300 may analyze and determine whether a new machine learning model needs to be trained for the analysis ID of a particular UE or a group of particular UEs.

Optionally, as described in the steps under case b#1, case b#2, or case b.3, the third entity 300, which obtains the ASI from the first entity, may also perform 702 (step 2), and is the entity that sends the model training request to the fourth entity 400.

The present invention provides one embodiment of the technical solution according to the entities defined in the 3gpp 5g architecture in TS 23.501R16.

For example, the first entity 100 may be mapped to a UDM. The functionality of the second entity 200 may be mapped to three different entities including NF: AF, NEF and NWDAF according to the different embodiments to be provided. The third entity 300 maps to an AMF.

It should be appreciated that the first entity, the second entity and the third entity may be some other network element, which may be different network entities in different scenarios. For the rest of the embodiments in the present invention, the same understanding is assumed.

Referring now to fig. 8, fig. 8 is a schematic diagram of a first entity 100 taking UDM as an example to obtain ASI according to section a.

Fig. 8 shows an embodiment in case #a.1 and case #a.2. In this embodiment, the second entity 200 may map to an AF. However, there are other possible NFs that could also be embodiments of the second entity. For example, the NEF or NWDAF shown in fig. 8 may also have an ASI 101 available, which information is then provided to the UDM (i.e. an embodiment of the first entity).

Case # a.1: in 802, analysis subscription information can be configured and stored in a UDM.

Case # a.2: in 803 (step 1 a), if the operator allows the AF to provide analysis subscription information (ASI 101) directly to the UDM (step 1 a), it is provided directly, or indirectly through the NEF (in 804 or step 1 b). The AF may invoke a UDM open service including at least one of the following parameters: the AF identification, a list of allowed analysis IDs for a UE or a group of UEs, and a list of restricted analysis IDs for a list of UEs or a group of UEs.

In 802 (step 2), the UDM may receive and store analysis subscription information.

In 806, the UDM may provide the identification of ASI 101 to the AF directly (e.g., in step 3a (or 806)) or indirectly (e.g., through NEF in 807 (or step 3 b)). The AF may use this identification to change its associated stored ASI 101.

Referring now to fig. 9, fig. 9 is a schematic diagram of a first entity obtaining ASI as UDM from support information.

In fig. 9 (UDM-based embodiment of part a, case #a.3), an embodiment of case #a.3 is discussed, wherein the second entity 200 may generate an ASI 101 and then provide the generated ASI 101 to the first entity 100. The present embodiment shows that the first entity 100 is mapped to UDM and the second entity 200 is mapped to NEF.

Two alternatives of the embodiment are used to instruct the NEF, i.e. how accurately the second entity 200 obtains the second information. For example, the NEF may interact with NWDAF 900 or NRF 900 to obtain the second information. When the NEF interacts with the NWDAFs, the NEF should contact all NWDAFs in the system and retrieve from each NWDAF the analysis ID it supports.

However, NWDAF is not the only entity in 5GS that can provide a list of supported analytics IDs in the mobile network operator. For example, NRF also has this information. The NEF may query the NRF function and retrieve all NWDAF NF profiles. From the NWDAF NF profile, the NEF can determine all the analysis IDs supported by the mobile network operator.

Furthermore, in case #a.3, other NFs may also be mapped to the second entity 200. For example, the NWDAF may also contain the capabilities of the second entity.

In 902 (step 1): the AF may provide the NEF with an NWDAF-associated expected UE behavior, wherein the NWDAF-associated expected UE behavior is an embodiment of the first support information.

The NEF may generate analysis subscription information according to the information (first support information) retrieved from the AF 901 and information (e.g., second support information) on analysis IDs supported in the mobile network operator. There are two alternatives for NEF generation ASI 101.

Alternative #a.3.1: in 903 (step 2), the NEF is in this case configured with an analysis ID (e.g. second support information) supported in the mobile network operator.

In 904 (step 3), the NEF may perform a mapping of the NWDAF associated expected UE behavior (first support information) to supported analytics IDs (second support information) to generate ASI 101 for a particular UE or group of particular UEs.

Alternative #a.3.2: in 905, if the NEF is not configured with an analytics ID (second support information) supported in the mobile network operator, the NEF may interact with other NFs (e.g., NWDAF or NRF) to retrieve the analytics ID (second support information) supported in the operator network.

If the NEF interacts with the NRF to obtain the analysis ID (second support information) supported in the operator network, the NEF may use the existing NRF service to retrieve the existing NWDAF NF profile and its supported analysis ID. The NEF may create second support information from the information.

If the NEF interacts with the NWDAF to obtain the analysis IDs supported in the operator network (second support information), the NEF may need to call a new service from the NWDAF to retrieve a list of analysis IDs supported by the NWDAF.

In 906 (step 3), when the NEF acquires the analysis ID (second support information) supported in the operator network, the NEF may perform mapping of the NWDAF-associated expected UE behavior (first support information) to the supported analysis ID (second support information) in order to generate the ASI 101. The result of this mapping may be an ASI 101 for a particular UE or a group of particular UEs.

In 907 (step 4), the NEF invokes the UDM service to store the generated ASI 101. The parameters used in the UDM service called by NEF may be the same as those indicated in step 1d above.

In 908 (step 5), the UDM may receive and store the analysis subscription information.

In 910 (step 7 a), the UDM may provide the identity of the ASI 101 of the particular UE or group of particular UEs to the NEF as part of a response message to the service invoked by the NEF.

At 911 (step 7 b), the NEF may send a response to the AF including an association ID that allows the AF to make more changes in analyzing the subscription information. Such an association ID may be related to the ASI 101 identification received from the UDM and allow the AF to change the information of the associated ASI 101 stored in the UDM.

Referring now to fig. 10, fig. 10 is a schematic diagram of a first entity acquiring ASI as UDM and a third entity as NF.

In fig. 10, a UDM-based embodiment of part B, case #b.1, is discussed, the third entity 300 may obtain the ASI 101 for the first time. In an embodiment of case #b.1, the first entity 100 may be mapped to UDM and the third entity 300 may be mapped to NF serving UE, e.g. AMF. The present embodiment is not limited to the mapping of the third entity 300 to AMFs, but may also be mapped to SMFs, PCFs, any NF serving the UE to control UE sessions or mobility or policies or any other mobile operator services. The fourth entity 400 is mapped to NWDAF.

In this embodiment, it is considered that the steps relating to the section a of the present invention have been performed.

In 1001 (step 0), in this step, one or more UEs may perform session establishment or UE registration by interacting with the 5 GS. These interactions may be considered as lifecycle events that occur for the UE in the operator network (e.g., lifecycle events related to the UE).

For example, when a UE requests to set up, modify or delete a session, or when the UE is registering with the network, or when the network decides to perform some change to the UE.

Examples of modifications that may be performed by the network include: altering session quality of service (Quality of Service, qoS), altering the restriction of areas where the UE may use the operator network. These changes that the network may implement in the UE are also considered in the present invention as lifecycle events related to the UE.

In 1002 (step 1), a first service NF (e.g., AMF if the lifecycle event is a UE registration) may determine that the NF has no ASI 101 information about the UE (or UEs or groups of UEs) associated with the lifecycle event. The first service NF may call a service that is open to the UDM to retrieve ASI 101. The parameters included in the request may be the same as those described above.

Optionally, in 1003, the first service NF may retrieve this information from the UDM as part of the UE context information that the NF retrieves from the lifecycle event associated with the UE. The UDM may verify whether there are any ASI 101 associated with parameters included in the request received from the first service NF.

In 1004 (step 3 a), if there is a match, the UDM may send to the first service NF one or more ASIs 101 and their associated identities that match some or all of the fields indicated in the request received by the UDM.

In 1005 (step 3 b), if there is no match for any field, the UDM may send an indication to the first service NF that any request field does not apply to ASI 101.

In 1006 (step 4 a), if the first service NF receives an indication that no ASI 101 is applicable, the first service NF may determine, according to its internal logic or configuration, to further request an analysis ID associated with the UE. If a first service NF can receive one or more ASI 101 that include the allowed analysis IDs of one or more UEs that the NF is processing, the first service NF can trigger a subscription in NWDAF for analysis IDs of allowed analysis IDs related to the UE or a group of UEs that the first service NF is processing according to ASI 101.

If the first service NF receives one or more ASIs 101 that have restrictions on the analysis ID of the UE or group of UEs that the NF is serving, the first service NF may optionally perform 3 actions:

in 1007 (step 4 b), any subscription to the analysis ID of the UE or group of UEs indicated in ASI 101 is not triggered. Even if the internal logic or local policy of the first service NF determines that a subscription or requesting UE or a group of UE's analysis IDs indicated as restricted is required, the first service NF may not trigger a subscription since ASI 101 is received from the UDM.

In 1008 (step 4 c), if the first service NF already has a previous subscription whose analysis target includes analysis IDs indicated as UEs or a group of UEs restricted by ASI 101 received from the UDM, the first service NF may send a unsubscribe message to the NWDAF for these analysis IDs or send a cancel request to the NWDAF to stop generating such analysis IDs for a specific UE or a group of specific UEs in ASI 101.

In 1009 (step 4 d), if the first service NF already has any previous subscription for the analytics ID with the target of analytics ID set to "any UE", the first service NF may send a request to modify the subscription or a request for an analytics ID that keeps the target of analytics ID set to "any UE" but adds a new field of analytics filter information called analytics limit.

Analysis constraints may include tuples: limiting filter types (e.g., UE, set of UEs, network slice, application, region of interest, i.e., fields of all possible types that serve as analysis filter information or analysis targets according to the definition of different analysis IDs in TS 23.288), limiting values (e.g., list of UEs SUPI, S-nsai, application IDs, etc.).

In this case, the analysis limit may include: the UE field type should limit a list of UE identities that generate the analysis ID.

At 1010 (step 5), the NWDAF may make the appropriate changes in the existing analytics ID based on the request received from the first service NF and send the results of the requested changes back to the first service NF.

Examples of modifications include at least one of the following examples: confirm unsubscribe, indicate new analysis subscription identity, in case NWDAF has to modify the existing analysis ID that actually needs to be split into 2 separate analysis ID subscriptions (instead of modifying only according to the request of the first service NF).

In 1011 (step 6), the first service NF may receive a response from the NWDAF and determine whether analysis context information has to be provided to the UDM. The ACI may be sent if a new analysis subscription has been performed, or if any modification to the existing analysis subscription of ASI 101 has also been performed (e.g., subscription/request has been cancelled). The first service NF may invoke a service that is open to the UDM and includes the same parameters indicated above as input parameters.

Referring now to fig. 11, fig. 11 is a schematic diagram of a first entity as a UDM and a third entity as an NF indirectly acquiring ASI.

In fig. 11, a UDM-based embodiment of part B, case #b.2, is discussed, wherein the first entity 100 may be mapped to UDM and the third entity 300 may be mapped to a new NF, e.g. AMF, serving the UE. The present embodiment is not limited to the mapping of the third entity 300 to a new service NF, such as an AMF, but may also be mapped to an SMF, PCF, any NF serving a UE to control UE session or mobility or policy or any other mobile operator service. The fourth entity 400 may be mapped to NWDAF.

Initially (0, UE mobility), one or more UEs may interact with the UE mobility-related 5 GS. The UE may be served by a first service NF. The UE may move in the operator network and the first service NF may no longer be able to control the UE's connection and then switch the UE context and control to the new service NF.

The procedures of UE mobility and UE context transfer have been defined in 3gpp TS 23.502. When there is a UE context transfer, all information about the UE is transferred from the first service NF to the new service NF, directly transferred through CP messages exchanged between these entities or indirectly transferred through the first service NF that updates information about the UE in another entity (e.g., UDM), and then the new service NF acquires the required UE information from the other entity. In the present embodiment, a case of transferring the UE context is considered.

In step 1101 (step 1), this step considers the case where UE context information can be transferred from the first service NF to the new service NF during UE movement. The UE context includes ASI 101 associated with a UE or a group of UEs.

In 1102 (step 2 a) and 1103 (step 2 b), the new service NF decides to interact with the NWDAF to correctly reflect the permission and restriction analysis ID of the UE or group of UEs, based on ASI 101 received with the UE or group of UE contexts.

In step 1102 (step 2 a), an ACI may also be included if ASI 101 acquired through UE context transfer may include an allow analysis ID. Based on ACI, the new service NF can interact with NWDAF in order to change the user of the analysis ID of the UE that has just moved.

In this case, the new service NF may send an analyze subscription modification request in order to alter the notification objective of a particular UE or a group of particular UEs. The request may also include a user migration flag. The user migration flag may be used as an indication that there has been a subscription or request in the NWDAF for an analysis ID for a particular UE or group of particular UEs, but that the user of the analysis ID has changed.

If the new serving NF receives one or more ASIs 101 that have restrictions on the analysis ID of the NF's serving UE or group of UEs, the new serving NF may optionally perform 3 actions:

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

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

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

At 1106 (step 3), the NWDAF may make the appropriate changes in the existing analytics ID based on the request received from the new service NF and send the results of the requested changes back to the first service NF.

Examples of modifications include one or more of the following examples: confirm unsubscribe, confirm correct modification of existing analytics ID, or indicate new analytics subscription identification in case NWDAF must modify existing analytics ID that actually needs to be split into 2 separate analytics ID subscriptions (instead of just modifying according to the request of the first service NF).

The last action may be performed when the new service NF sends the NWDAF a user migration flag included in the subscription or request message. In this case, if the existing subscription of another user having an analysis ID cannot be moved completely to the new user, the NWDAF may divide the existing analysis ID into 2 analysis ID subscriptions, each having a different user, the UE or group of UEs in the analysis target are divided according to the indication transmitted by the new service NF according to step 2 a.

In 1107 (step 4), this step is the same as step 6 above, but the new service NF may be the entity that interacts with the UDM instead of the first service NF.

Referring now to fig. 12, fig. 12 is a schematic diagram of acquiring a change in ASI.

In fig. 12, a UDM-based embodiment of part B, case #b.3, is discussed, wherein the first entity 100 may be mapped to UDM, AF may be mapped to the second entity, and the third entity 300 may be mapped to NF serving the UE, e.g. AMF. The present embodiment is not limited to the mapping of the third entity 300 to AMFs, but may also be mapped to SMFs, PCFs, any NF serving the UE to control UE sessions or mobility or policies or any other mobile operator services. The fourth entity 400 may be mapped to NWDAF.

Initially (0 a), the steps associated with part a of the present invention are considered to have been performed. In 0.b, the steps relating to the #b.1 or #b.2 part of the present invention are considered to have been performed. Thus, the service NF may have ASI 101 information and interact with the NWDAF to subscribe to or request a specific UE or a group of allowed analysis IDs for a specific UE or to restrict itself to include the UE or group of UEs indicated in ASI 101 as part of the analysis ID needed to subscribe to or request the service NF.

In 1201 (step 1), the AF may determine that an existing ASI 101 needs to be changed. The AF may have determined that the analysis ID of a different UE or group of UEs of the original ASI 101 that needs to be limited or allowed to be provided to 5GS (directly or through NEF to UDM).

In 1202 (step 2), the AF may provide the updated ASI 101 directly or indirectly to the UDM through the NEF.

In 1203 (step 3), the UDM may receive the updated ASI 101 and determine that a NF user of the ASI 101 or NF user of the ASI 101 that needs to be further notified of the analysis ID indicated in the ACI portion has occurred to send the updated ASI 101 to each determined NF user of the analysis ID or NF user of the ASI 101 by the UDM.

Next, based on the received updated ASI 101, each service NF, in this case the NF user of the determined analysis ID or NF user of ASI 101, may examine the updated ASI 101 and determine the changes in interaction with NWDAF that must be performed.

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

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

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

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

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

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

Referring now to fig. 13, fig. 13 is a schematic diagram of trigger model pre-training.

In fig. 13, a UDM-based embodiment of part C is discussed, wherein a first entity 100 may be mapped to a UDM, an AF may be mapped to a second entity, and a third entity 300 may be mapped to any NF, e.g. NWDAF. The fourth entity 400 may be mapped to NWDAF capable of model training.

Initially, it is assumed (in step 0) that the steps related to part a of the present invention have been performed. Thus, the ASI 101 is acquired by the first entity 100 (i.e., UDM) or the third entity 300 (i.e., NF, e.g., NWDAF).

This embodiment contemplates 2 alternatives.

Alternative #c.1: the first entity 100 may trigger model training.

In 1301 (step 1), in this alternative, when the UDM receives ASI101 from AF (directly or through NEF), the UDM analyzes whether model training needs to be initiated according to local policy.

In 1302 (step 2), the UDM may invoke a service opened by the NWDAF with training capabilities to trigger one or more allowed analysis ID related model training of a particular UE or group of particular UEs related to ASI 101.

Alternative #c.2: the third entity 300 may trigger model training.

In 1303 (step 1), in the present embodiment, NF such as NWDAF is considered to be a user of ASI101 opened by UDM. The NWDAF may obtain ASI101 by interacting with the UDM, e.g. by calling a service that is open to the UDM to provide ASI 101. In this case, the NWDAF may not need ASI101 to trigger the analytical use, but may require ASI101 to determine in advance that model training needs to be triggered.

The NWDAF may trigger model training of such subscriptions/requests in advance before the subscription request of a particular UE or a group of particular UEs, which allows for analysis of the ID, reaches the NWDAF. This has the advantage that once the subscription/request reaches NWDAF with reasoning capabilities, the model can be used for reasoning. Thus, based on ASI101 obtained from the UDM, the nwdaf may decide to trigger model training for the analysis ID indicated as allowed in ASI 101.

In 1304 (step 2), the NWDAF may invoke a service opened by another NWDAF with training capabilities, indicating that the analysis ID and the specific UE or set of specific UEs should be used together for model training, i.e. according to the acquired analysis ID of the specific UE or set of specific UEs of ASI 101.

The next step may be an alternative.

In 1305 (step 3), the NWDAF with training capabilities may receive a request from the user, in this case another NWDAF, and decide to perform the requested model training.

Fig. 14 illustrates a method 1400 performed by the first entity 100 provided by one embodiment of the present invention.

The method 1400 includes step 1401: processor 110 obtains ASI 101 through a configuration of a management entity or a configuration received from second entity 200, wherein ASI 101 includes permission and/or restriction analysis information for a UE and/or a group of UEs controlled by second entity 200, which may be used to control third entity 300 to interact with fourth entity 400.

It should be appreciated that ASI 101 in the present invention may include one or more ASI 101, and if one ASI is indicated, multiple ASIs may be indicated generally indiscriminately.

The method 1400 further includes step 1402: the processor 110 provides the ASI 101 to the third entity 300.

Fig. 15 illustrates a method 1500 performed by the second entity 200 provided by one embodiment of the invention.

The method 1500 includes step 1501: processor 210 obtains ASI 101, wherein ASI 101 includes User Equipment (UE) and/or permission and/or restriction analysis information for a group of UEs controlled by second entity 200, which may be used to control third entity 300 to interact with fourth entity 400.

The method 1500 further includes step 1502: the processor 210 sends the ASI 101 to the first entity 100.

Fig. 16 illustrates a method 1600 performed by a third entity 200 provided by one embodiment of the invention.

The method 1600 includes step 1601: the processor 310 obtains the ASI 101 from the first entity 100 or from another third entity 300, wherein the ASI 101 comprises permission and/or restriction analysis information of a UE and/or a group of UEs controlled by the second entity 200, said permission and/or restriction analysis information being used to control the third entity 300 to interact with the fourth entity 400.

The method 1600 further includes step 1602: the processor 310 provides a subscription or request or an unsubscribe request for one or more third analysis information of the UE or the group of UEs to the fourth entity 400 according to the acquired one or more ASI 101, wherein the one or more third analysis information may be based on the acquired analysis information of the one or more ASI 101 and used for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity.

Fig. 17 illustrates a method 1700 performed by the fourth entity 400 provided by one embodiment of the present invention.

The method 1700 includes step 1701: the processor 410 obtains from the third entity 300 a subscription or request or unsubscribe request for one or more third analysis information of a UE or a group of UEs, wherein the one or more third analysis information of a UE or a group of UEs is based on ASI 101, the ASI 101 comprises analysis information of a UE and/or a group of UEs controlled by the second entity 200, which allow and/or restrict analysis information may be used to control the third entity 300 to interact with the fourth entity 400, the third analysis information is based on analysis information of the ASI, and is used for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity.

The method 1700 further includes step 1702: the processor 410 sends a response to the third entity 300.

It should be appreciated that the above-described method may have the same features as previously described, and that for simplicity, each feature is not set forth herein. It will be appreciated by those skilled in the art that a similar approach may be implemented in accordance with the teachings of the present invention.

The invention has been described in connection with various embodiments and implementations as examples. However, other variations can be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the invention, and the appended claims. In the claims and in the description, the word "comprising" does not exclude other elements or steps, and the terms "a" or "an" do 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 mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Claims

1. A first entity (100), the first entity (100) being for a communication network (1), the first entity (100) comprising:

a processor (110) for: acquiring analysis subscription information (Analytics Subscription Information, ASI) (101) by means of a configuration of a management entity or a configuration received from a second entity (200), wherein the ASI (101) comprises User Equipment (UE) controlled by the second entity (200) and/or permission and/or restriction analysis information of a set of UEs for controlling interaction of a third entity (300) with a fourth entity (400),

the processor (110) is further configured to provide the ASI (101) to the third entity (300).

2. The first entity (100) of claim 1, wherein the processor (110) is further configured to:

-providing one or more Identifications (IDs) of the ASI (101) to the second entity (200).

3. The first entity (100) of claim 1 or 2, wherein the processor (110) is further configured to:

-receiving first support information (103) from the second entity (200), wherein the first support information (103) comprises a mapping between the behaviour of the UE or the set of UEs and a second set of analysis information indicating possible analysis information related to the behaviour of the UE or the set of UEs; and/or

-generating said ASI (101) from said acquired first support information (103).

4. A first entity (100) according to any of claims 1 to 3, wherein the processor (110) is further configured to:

-receiving a request for an ASI (101) of a particular UE or a group of particular UEs from the third entity (300); and/or

-sending an ASI response message to the third entity (300), wherein the ASI response message comprises one or more ASIs (101) or an indication that the received request has no ASI available.

5. The first entity (100) of any of claims 1 to 4, wherein the request for ASI comprises one or more of:

-an identity of the ASI (101);

identification of the analysis information;

an identity of one or more UEs;

an identity of one or more groups of UEs;

-providing an identification of the second entity (200) of the ASI (101);

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

an identification of an existing subscription or request for analysis information;

-an identification of a reference point in communication with the third entity (300).

6. The first entity (100) of any one of claims 1 to 5, wherein the ASI comprises one or more of:

-an identity of the ASI (101);

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

-an identification of the third entity (300) using the ASI (101) and/or using the analysis information;

a list of allowed analysis information for a UE or the set of UEs, or a list of allowed analysis information for a UE or the set of UEs for each user of the analysis information;

a list of restricted analysis information for a UE or the set of UEs, or a list of restricted analysis information for a UE or the set of UEs for each user of the analysis information;

-an identification of a reference point in communication with the third entity (300) using the ASI (101) and/or using the analysis information;

-an identification of a reference point in communication with the second entity (200) providing the ASI (101) or the first support information (103);

an identification of the analysis information subscription or request associated with the third entity;

one or more fields related to analyzing information subscriptions.

7. The first entity (100) of any one of claims 1 to 6, wherein the processor (110) is further configured to:

acquiring updated ASI (101) through configuration of a management entity or configuration received from the second entity (200); and/or

-sending a notification message to the third entity (300), wherein the notification message indicates a change of the ASI (101).

8. The first entity (100) of any one of claims 1 to 7, wherein the processor (110) is further configured to:

receiving analysis context information (Analytic Context Information, ACI) (104) from the third entity (300), wherein the ACI (104) comprises at least one of: -association of a third entity (300) with an ASI (101), and-association of an ASI (101) obtained by the third entity (300) with an existing subscription or an existing request or an unsubscribe or a cancel request for third analysis information requested by the third entity (300) from the fourth entity (400), the third analysis information being based on the analysis information of the ASI (101) and being used for interaction between the third entity and the fourth entity or between the fourth entity and the third entity.

9. The first entity (100) of any one of claims 1 to 8, wherein the ACI (104) comprises one or more of:

-an identity of the third entity (300);

-an identification of a reference point in communication with the third entity (300);

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

-a field related to the third analysis information subscribed or requested by the third entity (300).

10. The first entity (100) of any one of claims 1 to 9, wherein the processor (110) is further configured to:

-sending a model training request (102) to the fourth entity (400), wherein the model training request (102) indicates that model training of analysis information of a UE or a group of UEs associated with the acquired ASI (101) needs to be performed by the fourth entity (400).

11. A second entity (200), the second entity (200) being for a communication network (1), the second entity (200) comprising:

a processor (210) for obtaining analysis subscription information (analytics subscription information, ASI) (101), wherein the ASI (101) comprises User Equipment (UE) controlled by the second entity (200) and/or permission and/or restriction analysis information of a group of UEs for controlling interaction of a third entity (300) with a fourth entity (400),

the processor (210) is further configured to send the ASI (101) to the first entity (100).

12. The second entity (200) of claim 10 or 11, wherein the processor (210) is further configured to:

one or more Identifications (IDs) of the ASI (101) are received from the first entity (100).

13. The second entity (200) of any one of claims 10 to 12, wherein the processor (210) is further configured to:

obtaining first support information (103), wherein the first support information (103) comprises a mapping between the behaviour of the UE or the set of UEs and a second set of analysis information indicating possible analysis information related to the behaviour of the UE or the set of UEs; and/or

-generating the ASI (101) from the first support information (103).

14. The second entity (200) of any one of claims 10 to 13, wherein the processor (210) is further configured to:

-sending the updated ASI (101) of the UE or the set of UEs to the first entity (100).

15. The second entity (200) of any of claims 10 to 14, wherein the ASI comprises one or more of:

-an identity of the ASI (101);

-an identification of the analysis information subscription or request associated with the third entity (300);

one or more fields related to analyzing information subscriptions.

16. A third entity (300), characterized in that the third entity (300) is for a communication network (1), the third entity (300) comprising:

a processor (310) for: obtaining analysis subscription information (Analytics Subscription Information, ASI) (101) from a first entity (100) or from another third entity (300), wherein the ASI (101) comprises User Equipment (UE) controlled by a second entity (200) and/or permission and/or restriction analysis information of a set of UEs, the permission and/or restriction analysis information being used to control the third entity (300) to interact with a fourth entity (400),

The processor (310) is further configured to: -providing, to the fourth entity (400), a subscription or request or an unsubscribe or cancel request (301) for one or more third analysis information of the UE or the group of UEs, based on the obtained analysis information of the one or more ASIs (101), and for an interaction between the third entity and the fourth entity or between the fourth entity and the third entity.

17. The third entity (300) of claim 16, wherein the subscription or request or unsubscribe request for one or more third analysis information provided to the fourth entity (400) comprises at least one of:

one or more restricted UEs or a set of restricted UEs for generating the requested third analysis information, wherein the one or more UEs or the set of UEs comprises the acquired UE or set of UEs of the one or more ASIs (101);

user migration information, wherein the user migration information is obtained by a user modifying third analysis information determined according to ASI (101) of the specific UE or the group of specific UEs as needed.

18. The third entity (300) of claim 16 or 17, wherein the processor (310) is further configured to:

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

An ASI response message is received from the first entity (100), wherein the ASI response message comprises one or more ASIs (101) or an indication that the transmitted request has no ASI available.

19. The third entity (300) of any of claims 16 to 18, wherein the request for ASI comprises one or more of:

-an identity of the ASI (101);

identification of the analysis information;

an identity of one or more UEs;

an identity of one or more groups of UEs;

-providing an identification of the second entity (200) of the ASI (101);

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

20. The third entity (300) of any of claims 16 to 19, wherein the processor (310) is further configured to:

-sending a model training request (102) to the fourth entity (400) according to the acquired ASI (101) in the ASI response message.

21. The third entity (300) of any of claims 16 to 20, wherein the processor (310) is further configured to:

a notification message is received from the first entity (100), wherein the notification message indicates a change of the ASI (101).

22. The third entity (300) of any of claims 16 to 21, wherein the processor (310) is further configured to:

providing analysis context information (Analytic Context Information, ACI) (104) to the first entity (100), wherein the ACI (104) comprises at least one of: -association of a third entity with an ASI (101), and-association of an ASI (101) obtained by the third entity (300) with an existing subscription or an existing request or an unsubscribe or a cancel (301) of third analysis information requested by the third entity (300) from the fourth entity (400), the third analysis information being based on the analysis information of the ASI (101) and being used for interaction between the third entity and the fourth entity or between the fourth entity and the third entity.

23. The third entity (300) of any of claims 16 to 22, wherein the ACI (104) comprises one or more of:

-an identity of the third entity (300);

24. The third entity (300) of any of claims 16 to 23, wherein the ASI (101) comprises one or more of:

-an identity of the ASI (101);

one or more fields related to analyzing information subscriptions.

25. A fourth entity (400), characterized in that the fourth entity (400) is for a communication network (1), the fourth entity (400) comprising:

a processor (410) for obtaining from a third entity (300) a subscription or request or an unsubscribe or cancel request (301) for one or more third analysis information of a UE or a group of UEs, wherein the one or more third analysis information of the UE or the group of UEs is based on analysis subscription information (Analytics Subscription Information, ASI) (101), the ASI (101) comprising analysis information of a User Equipment (UE) and/or a group of UEs controlled by a second entity (200), the permission and/or restriction analysis information being usable for controlling the interaction of the third entity (300) with the fourth entity (400), the third analysis information being based on analysis information of the ASI and being used for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity,

the processor (410) is further configured to send a response to the third entity (300).

26. The fourth entity (400) of claim 25, wherein the subscription or request or unsubscribe request or cancel request obtained from the third entity (300) comprises at least one of:

27. The fourth entity (400) of claim 25 or 26, wherein the ASI (101) comprises one or more of:

-an identity of the ASI (101);

fields related to analysis information subscription.

28. The fourth entity (400) according to any of claims 25 to 27, wherein the fourth entity (400) is further configured to:

a model training request (102) is obtained from the first entity (100), wherein the model training request (102) indicates that model training of analysis information of a UE or a group of UEs associated with the obtained ASI (101) needs to be performed by the fourth entity (400).

29. A method (1400) performed by a first entity (100), the method (1400) comprising:

a processor (110) obtains (1401) analysis subscription information (Analytics Subscription Information, ASI) (101) through a configuration of a management entity or a configuration received from a second entity (200), wherein the ASI (101) comprises User Equipment (UE) controlled by the second entity (200) and/or permission and/or restriction analysis information of a set of UEs, the permission and/or restriction analysis information being used to control a third entity (300) to interact with a fourth entity (400);

The processor provides (1402) the ASI (101) to the third entity (300).

30. A method (1500) performed by a second entity (200), the method (1500) comprising:

a processor (210) obtains (1501) analysis subscription information (analytics subscription information, ASI) (101), wherein the ASI (101) comprises User Equipment (UE) controlled by the second entity (200) and/or permission and/or restriction analysis information of a set of UEs, the permission and/or restriction analysis information being used to control a third entity (300) to interact with a fourth entity (400);

the processor (210) sends (1502) the ASI (101) to the first entity (100).

31. A method (1600) performed by a third entity (300), the method (1600) comprising:

a processor (310) obtains (1601) analysis subscription information (Analytics Subscription Information, ASI) (101) from a first entity (100) or from another third entity (300), wherein the ASI (101) comprises User Equipment (UE) controlled by a second entity (200) and/or permission and/or restriction analysis information of a set of UEs, the permission and/or restriction analysis information being used to control the third entity (300) to interact with a fourth entity (400);

The processor (310) provides (1602) a subscription or request or an unsubscribe request for one or more third analysis information of the UE or the group of UEs to the fourth entity (400) in accordance with the acquired one or more ASI (101), wherein the one or more third analysis information is based on the acquired analysis information of the one or more ASI (101) and is used for interaction between the third entity and the fourth entity or interaction between the fourth entity and the third entity.

32. A method (1700) performed by a fourth entity (400), the method (1700) comprising:

a processor (410) obtaining (1701) from a third entity (300) a subscription or request or an unsubscribe or cancel request for one or more third analysis information of a UE or a group of UEs, wherein the one or more third analysis information of the UE or the group of UEs is based on analysis subscription information (Analytics Subscription Information, ASI) (101), the ASI (101) comprising analysis information of a User Equipment (UE) and/or a group of UEs controlled by a second entity (200), the permission and/or restriction analysis information being usable for controlling the interaction of the third entity (300) with the fourth entity (400);

The processor (410) sends (1702) a response to the third entity (300).

33. A computer program comprising a program code for performing the method (1400, 1500, 1600, 1700) according to any of claims 29 to 32 when the program code is executed on a computer.