Distribution of integrated analysis reports in wireless core networks

Abstract

A method and apparatus for creating and distributing analysis reports in a wireless core network are provided. The CNF requests analysis reports of multiple UEs from the NWDAF. In response to the request, the NWDAF compiles the requested data and generates analysis reports for the UEs identified in the request. During the compilation of the analysis data, the NWDAF performs cluster analysis to identify groups of UEs 100 that share the same analysis report (referred to herein as temporary groups), and generates a consolidated analysis report for each temporary group to reduce the number of analysis reports sent to the CNF 200.

Description

[0001] Related Applications

[0002] This application claims priority from European Application No. EP19382743.3 filed on September 2, 2019, the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to a network data analysis function (NWDAF) for a wireless core network, and more particularly to the generation and distribution of consolidated analysis reports in a wireless core network. Background Art

[0004] Release 15 (Rel-15) of the 3rd Generation Partnership Project (3GPP) standards for fifth generation (5G) networks introduced a new network function called the Network Data Analysis Function (NWDAF), and its basic functionality is specified in Release 16 (Rel-16), which is currently under development. More advanced use cases are planned for Rel-17.

[0005] According to Rel-16, NWDAF is able to generate statistics and predictions related to the activities of user equipment (UE) or UE groups. These statistics and predictions include, but are not limited to, UE mobility patterns (e.g., determining whether the UE is stationary or mobile, predicting the area the UE will visit, etc.) and UE communication patterns (communication time, duration, maximum uplink and downlink bit rates, etc.). The core network nodes (referred to herein as consumer network functions) in the 5G core network (5GC) can query NWDAF or subscribe to receive notifications from NWDAF to obtain statistics or predictions for UE or UE groups. Exemplary CNFs include access and mobility management functions (AMFs) and session management functions (SMFs).

[0006] If the CNF is interested in receiving analysis of a UE group, such a group is typically identified by an internal group identifier (ID). In this case, the NWDAF obtains a list of UE identities (e.g., User Permanent Identifiers (SUPIs)) of the members of the group from the Unified Data Management (UDM) function, generates an analysis for each of these UE identities, and transmits the analysis report to the CNF.

[0007] The current process envisioned by the Rel-16 standard has scalability issues. If the group of UEs for which analysis is generated is large (i.e., millions of subscribers), the response generated by the NWDAF contains analysis reports for each of these subscribers. As a result, the NWDAF will generate a large amount of traffic that can easily overwhelm the memory and processing resources required by the CNF to process these analysis reports. Summary of the invention

[0008] The present disclosure generally relates to the creation and distribution of analysis reports in a wireless core network. The CNF requests analysis reports for multiple UEs from the NWDAF. In response to the request, the NWDAF compiles the requested data and generates analysis reports for the UEs identified in the request. During the compilation of the analysis data, the NWDAF performs cluster analysis to identify groups of UEs 100 that share the same analysis report (referred to herein as temporary groups), and generates a consolidated analysis report for each temporary group to reduce the number of analysis reports sent to the CNF.

[0009] When a consumer NF requests an analysis report for a user group with a large number of members from the NWDAF, the techniques described herein mitigate the impact of massive signaling in the network and the requirements on the CPU, memory and storage of the consumer network function. The NWDAF clusters the results of the analysis report, creating a report per cluster per UE (sharing the report) rather than per UE. This mitigates the problem of massive signaling in the network (the more data that can be shared by the UEs, the less signaling). It also addresses the CPU, memory and storage issues of the consumer NFs, as they do not need to retain massive memory and storage for storing each individual analysis report, or even massive CPU to parse each individual analysis report.

[0010] One aspect of the present disclosure includes a method for distributing analysis reports of multiple UEs implemented by NWDAF. NWDAF receives a request for analysis reports of multiple UEs from a requesting network node (e.g., CNF). NWDAF compiles data for the analysis report and performs cluster analysis based on the compiled data to identify a reporting group, which includes two or more UEs among the multiple UEs 100 for which data is to be integrated. NWDAF generates an integrated analysis report based on the compiled data, which includes integrated data common to all members of the reporting group. In response to the request, NWDAF sends the integrated analysis report and a report group identifier identifying the reporting group associated with the integrated analysis report to the requesting node.

[0011] Another aspect of the present disclosure includes a method for obtaining analysis reports of multiple UEs implemented by a CNF in a wireless core network. The CNF sends a request for analysis reports of multiple UEs to an NWDAF or other producer node. In response to the request, the CNF receives from the NWDAF an integrated analysis report and a report group identifier identifying a report group associated with the integrated analysis report. The report group includes two or more UEs of the multiple UEs for which data has been integrated.

[0012] Another aspect of the present disclosure includes a network node (e.g., NWDAF) configured to provide an analysis report to a CNF. The network node includes an interface circuit for communicating with other network nodes in a communication network and a processing circuit. The processing circuit is configured to receive a request for an analysis report of multiple user equipments (UEs) from a requesting node. The processing circuit is further configured to: compile data for the analysis report, and perform cluster analysis based on the compiled data to identify a reporting group, the reporting group including two or more UEs of the multiple UEs for which data is to be integrated. The processing circuit is further configured to: generate an integrated analysis report based on the compiled data, the integrated analysis report including integrated data common to all members of the reporting group; and in response to the request, send the integrated analysis report and a report group identifier identifying the reporting group associated with the integrated analysis report to the requesting node.

[0013] Another aspect of the present disclosure includes a network node configured to request an analysis report from a producer node (e.g., NWDAF). The network node includes an interface circuit for communicating with other network nodes in a communication network and a processing circuit. The processing circuit is configured to send a request for analysis reports of multiple user equipments (UEs) to the producer node. The processing circuit is further configured to: in response to the request, receive from the producer node an integrated analysis report and a report group identifier identifying a report group associated with the integrated analysis report. The report group includes two or more UEs of the multiple UEs for which data has been integrated.

[0014] Another aspect of the present disclosure includes a network node (e.g., NWDAF) configured to: receive a request for an analysis report of multiple user equipments (UEs) from a requesting node; compile data for the analysis report; based on the compiled data, perform a cluster analysis to identify a reporting group, the reporting group including two or more UEs among the multiple UEs for which data is to be integrated; based on the compiled data, generate an integrated analysis report, the integrated analysis report including integrated data common to all members of the reporting group; and in response to the request, send the integrated analysis report and a report group identifier identifying the reporting group associated with the integrated analysis report to the requesting node.

[0015] Another aspect of the present disclosure includes a network node (e.g., CNF) configured to: send a request for analysis reports of multiple user equipments (UEs) to a producer node (e.g., NWDAF); and in response to the request, receive from the producer node an integrated analysis report and a report group identifier identifying a report group associated with the integrated analysis report; wherein the report group includes two or more UEs among the multiple UEs for which data has been integrated.

[0016] Another aspect of the present disclosure includes a computer program comprising instructions that, when executed by a processing circuit in a network node, cause the network node to perform a method as described herein. The computer program may be embodied in a carrier such as an electronic signal, an optical signal, a radio signal, or a non-transitory computer-readable storage medium. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A wireless core network according to an embodiment is shown.

[0018] Figure 2 Shown are the core network nodes involved in the creation and distribution of analysis reports.

[0019] Figure 3 is a signaling diagram illustrating a process for requesting and distributing an analysis report according to one embodiment.

[0020] Figure 4 is a signaling diagram illustrating a process for requesting and distributing an analysis report according to another embodiment.

[0021] Figure 5 is a flow chart illustrating an exemplary method performed by a producer network function (eg, NWDAF).

[0022] Figure 6 is a flow chart illustrating an exemplary method performed by a CNF (eg, AMF, SMF, UDM).

[0023] Figure 7 Functional components of an exemplary analysis network function (eg, NWDAF) are shown.

[0024] Figure 8 Functional components of exemplary consumer network functions (eg, AMF, SMF, UDM) are shown.

[0025] Fig. 9 A network node is shown that can be configured as a consumer network function (e.g., AMF, SMF, UDM) or a NWDAF. DETAILED DESCRIPTION

[0026] Now referring to the accompanying drawings, exemplary embodiments of the present disclosure will be described in the context of a 5G wireless communication network. Those skilled in the art will appreciate that the methods and apparatus described herein are not limited to use in 5G networks, but may also be used in wireless communication networks operating according to other standards.

[0027] Figure 1A wireless communication network 10 according to an exemplary embodiment is shown. The wireless communication network 10 includes a radio access network (RAN) 20 and a core network 30 that employs a service-based architecture. The RAN 20 includes one or more base stations 25 that provide radio access to UEs 100 operating within the wireless communication network 10. The base stations 25 are also referred to as gNodeBs (gNBs). The core network 30 provides connectivity between the RAN 20 and other packet data networks such as IMS or the Internet.

[0028] In an exemplary embodiment, the core network 30 includes a plurality of network functions (NFs), such as a user plane function (UPF) 35, an access and mobility management function (AMF) 40, a session management function (SMF) 45, a policy control function (PCF) 50, a unified data management (UDM) function 55, an authentication server function (AUSF) 60, a unified data repository (UDR) 65, a network open function (NEF) 70, and a network repository function (NRF) 75. In addition, the core network 30 includes a NWDAF 300 for generating and distributing analysis reports. These NFs include logical entities residing in one or more core network nodes, which can be implemented by one or more processors, hardware, firmware, or a combination thereof. These functions can reside in a single core network node, or can be distributed between two or more core network nodes.

[0029] In a conventional wireless communication network, various NFs (e.g., SMF 45, AMF 40, etc.) in the core network 30 communicate with each other through predefined interfaces. Figure 1 In the service-based architecture shown in , instead of predefined interfaces between control plane functions, the wireless communication network 10 uses a service model in which NFs query the NRF 75 or other NF discovery nodes to discover and communicate with each other.

[0030] Figure 2 Entities for creating and distributing analysis reports in a wireless core network 30 are shown. The entities involved in the creation and distribution of analysis reports include one or more CNFs 200, NWDAF 300, and UDR 65. CNF 200 includes a core network node that is a service consumer according to the 3GGP standard. CNF 200 may, for example, include AMF 40, SMF 45, or UDM 55 that requests an analysis report from NWDAF 300. CNF 200 sends a request for an analysis report to NWDAF 300 using the Nnwdaf interface. The request may specify a group of UEs 100 for which data is requested. For example, CNF 200 may request a predicted future trajectory for a group of UEs 100 or an activity pattern for a group of UEs 100.

[0031] The NWDAF 300 according to the 3GGP standard is a service producer because it generates reports used by other network nodes. The NWDAF 300 receives a request for analysis data from the CNF 20 via the Nnwdaf interface, compiles the requested data, and generates an analysis report for the UE identified in the request. During the compilation of the analysis data, the NWDAF 300 performs cluster analysis to identify groups of UE 100 (referred to herein as temporary groups) that share the same analysis report, and generates an integrated analysis report for each temporary group to reduce the number of analysis reports sent to the CNF 200. The NWDAF 300 assigns a temporary group identifier to each temporary group. The temporary group identifier is usually valid for a limited period of time, and the NWDAF 300 assigns a group validity period to each temporary group. This group validity period can, for example, coincide with the time when the next prediction will be generated. Therefore, if the NWDAF 300 generates a prediction at 13:00 every 24 hours, the group validity period is set to the next 13:00.

[0032] In response to the request from CNF 200, NWDAF 300 transmits the integrated analysis report to the requesting CNF 200 in the form of a triplet, the triplet including the temporary group identifier of the temporary group, the group validity period of the temporary group, and the integrated analysis report applicable to the members of the temporary group. Additionally, NWDAF 300 may provide group acquisition information that helps CNF 200 retrieve a list of UEs 100 in the temporary group.

[0033] Upon receiving the integrated analysis report from the NWDAF 300, the CNF 200 is generally unaware of the UE 100 belonging to each temporary group. To address this issue, the CNF 200 uses group acquisition information to retrieve a list of UE IDs identifying the UE 100 in each temporary group. The CNF 200 may apply the integrated analysis report to all members of the temporary group. In an exemplary embodiment, the CNF 200 retrieves the UE ID directly from the NWDAF 300 for each temporary group. In other embodiments, the NWDAF 300 stores the UE ID associated with each temporary group in the UDR 65 or other external database. In this case, the CNF 200 may retrieve the UE ID from the UDR 65 or other external database for each temporary group.

[0034] In a large data set, it is likely that most UEs will be classified into groups with multiple members. However, there may be a situation where one of the UEs is an outlier and cannot be grouped with the other UEs. If the NWDAF 300 is configured to use groups, the NWDAF 300 can be configured to create a reporting group for a single member and generate a consolidated analysis report for a single member temporary group, even if the temporary group has only one member. This is useful because another UE can be added to the temporary group and allows the NWDAF to be configured to treat all groups in the same way regardless of the number of members in the group.

[0035] Although clustering techniques are intended to be used with large data sets, there may be situations where the data sets are small. Therefore, the NWDAF 300 can be configured to handle small data sets as well as large data sets. In cases where the data sets are very small, the analysis data for different UEs may be so scattered that it is not possible to classify two UEs into the same group. For example, consider a sample with 4 UEs, where the classification places each UE in a different quadrant. If the NWDAF 300 is configured to use temporary groups, it will create a single member group for each UE.

[0036] Figure 3 An exemplary process for providing analysis data to CNF 200 is shown. The process starts when CNF 200, such as AMF 40, SMF 45 or UDM 55, requests an analysis report for a group of UEs 100 by sending an analysis information request (denoted as Nnwdaf_AnalyticsInfo_Request) to NWDAF 300 (step 1). The analysis information request contains an indication of the type of analysis report requested (identified by an analysis ID), and an indication of the group of UEs 100 for which the request is made. The group of UEs 100 may be identified by a collective identifier (ID) such as an internal group ID or an external group ID. Alternatively, CNF 200 may provide in the request a list of UE IDs (e.g., SUPIs) for which analysis reports are requested.

[0037] In some embodiments of the present disclosure, CNF 200 may send an analysis subscription request (denoted as Nnwdaf_AnalyticSubscription_Subscribe) to NWDAF 300 to subscribe to receive periodic or aperiodic analysis reports for a specified group of UEs 100. The analysis subscription request also contains an indication of the type of analysis report requested (identified by an analysis ID), and an indication of the group of UEs 100 for which the request is made.

[0038] In response to receiving the analysis information / subscription request, the NWDAF 300 compiles the required information to generate the requested analysis report (step 2). Data compilation may include, for example, retrieving a list of UE IDs of UEs 100 that are members of the group associated with the internal group ID or external group ID provided in the request. The UE ID list may be retrieved, for example, from the UDM 55 or UDR 65. The data compilation may further include sending a request to other network functions and receiving a response from the other network functions to obtain, for each UE 100, source data required to generate the analysis report for the UE 100.

[0039] The NWDAF 300 generates a separate analysis report for each UE 100 identified by the analysis information / subscription request (step 3). In many cases, the list of UEs 100 for which analysis reports are requested will be very large, and it is impractical to send a separate report for each UE 100. In this case, the NWDAF 300 performs a cluster analysis process for determining the similarity and equivalence of the analysis reports for each of the individual UEs 100. The result of this process is the creation of one or more temporary groups (also referred to herein as report groups) that share the same analysis report. Each temporary group is associated with an integrated analysis report that is common to all members of the temporary group. A group validity period is also created, which is set to the time when the analysis report is considered outdated in the future. Typically, the group validity period may be the time when the NWDAF 300 is expected to have a new analysis report created based on more recent source data. Once the integrated analysis report is generated, NWDAF 300 sends an analysis information response (labeled as Nnwdaf_AnalyticsInfo_Response) containing the integrated analysis report generated by NWDAF 300 to CNF 200 (step 5). In one embodiment, the analysis information response includes a list of triples, each triple including a temporary group ID, an integrated analysis report applicable to all members of the temporary group, and an optional group validity period.

[0040] After receiving the analysis information response from NWDAF 300, CNF 200 queries NWDAF 300 to obtain a list of UE IDs that are members of each temporary group (step 6). The query (denoted as Nnwdaf_AnalyticsInfo_Group_Request) indicates the temporary group ID for which the UE ID is requested. The query is also referred to as a group information request in this article. In response to the group information request from CNF 200, NWDAF 300 sends a query response (denoted as Nnwdaf_AnalyticsInfo_Group_Response) including a list of UEIDs associated with each temporary group ID. The query response is also referred to as a group information response in this article. Using this information, CNF 200 can associate the integrated analysis report with each of these UE100 and take any desired actions. After the group validity period expires, both CNF 200 and NWDAF 300 delete the expired temporary group and its corresponding member list.

[0041] In some embodiments, the analysis information response returned in step 5 includes a list of temporary group IDs and an associated analysis report without a group validity period. In this case, when CNF 200 queries NWDAF 300 for group member information, the group validity period may be optionally provided in Nnwdaf_AnalyticsInfo_Group_Response. More specifically, for each temporary group ID included in the group information request sent in step 6, NWDAF 300 provides a triplet including a temporary group ID, a list of UE IDs associated with the temporary group ID, and a group validity period.

[0042] Figure 4 Another exemplary process for providing analytical data to CNF 200 is shown. Steps 1-4 are similar to those in Figure 3The process is the same as that shown in . The process starts when a CNF 200 such as an AMF, SMF or UDM requests an analysis report for a group of UE 100 by sending an analysis information request (denoted as Nnwdaf_AnalyticsInfo_Request) to the NWDAF 300 (step 1). The analysis information request contains an indication of the type of analysis report requested (identified by an analysis ID) and an indication of the group of UE 100 for which the request is made. The group of UE 100 may be identified by a collective identifier such as an internal group ID or an external group ID. Alternatively, the CNF 200 may provide a list of UE IDs (e.g., SUPIs) for which analysis reports are requested in the request. In some embodiments of the present disclosure, the CNF 200 may send an analysis subscription request (denoted as Nnwdaf_AnalyticSubscription_Subscribe) to the NWDAF 300 to subscribe to receive periodic or aperiodic analysis reports for a specified group of UE 100. The analytics subscription request also contains an indication of the type of analytics report being requested (identified by the analytics ID), and an indication of the group of UEs 100 for which the request is being made.

[0043] In response to receiving the analysis information / subscription request, the NWDAF 300 compiles the required information to generate the requested analysis report (step 2). Data compilation may include, for example, retrieving a list of UE IDs of UEs 100 that are members of a group identified by an internal group ID or an external group ID. The UE ID list may be retrieved, for example, from the UDM 55 or the UDR 65. The data compilation may further include sending a request to other network functions and receiving a response from the other network functions to obtain, for each UE 100, source data required to generate an analysis report for the UE 100.

[0044] The NWDAF 300 generates a separate analysis report for each UE 100 identified by the analysis information / subscription request (step 3). As previously mentioned, in many cases, it is impractical to send a separate report for each UE 100. Therefore, the NWDAF 300 performs a cluster analysis process to determine the similarity and equivalence of the analysis reports for each of the individual UEs 100. The result of this process is the creation of one or more temporary groups (reporting groups) that share the same analysis report. Each temporary group is associated with an integrated analysis report that is common to all members of the temporary group. A group validity period is also created, which is set to the time when the analysis report is considered outdated in the future. Typically, the group validity period may be the time when the NWDAF 300 is expected to have a new analysis report created based on more recent source data.

[0045] After completing the cluster analysis and identifying the temporary groups, the NWDAF 300 sends a create request to the UDR 65 to request the UDR 65 to create a record associating the group ID of each temporary group with the corresponding UE ID list (step 5). The create request (denoted as Nudr_DM_Create_Request) contains a triple for each temporary group, which includes the group ID, the UE ID list indicating the members of the temporary group, and the group validity period. In response to the create request, the UDR 65 stores information about each temporary group in the database and returns a create response (denoted as Nudr_DM_Create_Response) to confirm receipt of the create request and confirmation that the record is created for the temporary group (step 6).

[0046] Once the integrated analysis report is generated, the NWDAF 300 sends an analysis information response (labeled Nnwdaf_AnalyticsInfo_Response) containing the integrated analysis report generated by the NWDAF 300 to the CNF 200 (step 7). This step may be performed before steps 5 and 6, or in parallel with steps 5 and 6. In one embodiment, the analysis information response includes a list of triples, each of which includes a temporary group ID, an integrated analysis report applicable to all members of the group, and an optional group validity period.

[0047] After receiving the analysis information response from NWDAF 300, CNF 200 queries UDR 65 to obtain the UE ID list of UE 100 that is a member of each temporary group (step 8). In one embodiment, CNF 200 sends Nudr_DM_Query_Request to UDR 65, which contains a temporary group ID list for which UE ID is requested. This query is also referred to as a group information request in this article. In response to the group information request from CNF 200, UDR 65 sends a group information response (denoted as Nudr_Query_Response) including a UE ID list associated with each temporary group ID (step 9). CNF 200 can associate the integrated analysis report with each of the affected UE 100 and take any required actions. After the group validity period expires, both CNF 200 and UD40 delete all expired temporary groups and their corresponding member lists.

[0048] In some embodiments, the analysis information response returned in step 7 includes a list of temporary group IDs and an associated analysis report without a group validity period. In this case, the group validity period may be optionally provided in the query response by the UDR 65. More specifically, for each group ID included in the group information request sent in step 8, the UDR 65 provides a triplet including a temporary group ID, a list of UE IDs associated with the temporary group ID, and a group validity period.

[0049] Figure 5 An exemplary method 400 of distributing analysis reports of multiple UEs 100 implemented by the NWDAF 300 is shown. The actions shown in dashed lines are optional. The NWDAF 300 receives a request for analysis reports of multiple UEs 100 from a requesting network node (e.g., CNF 200) (box 410). The NWDAF 300 compiles data for the analysis report (box 420), and performs cluster analysis based on the compiled data to identify a reporting group, which includes two or more UEs 100 in the multiple UEs 100 for which data is to be integrated (box 430). The NWDAF 300 generates an integrated analysis report based on the compiled data, which includes integrated data common to all members of the reporting group (box 440). After generating the integrated report, in response to the request, the NWDAF 300 sends the integrated analysis report and a report group identifier identifying the reporting group associated with the integrated analysis report to the requesting node (box 450).

[0050] In some embodiments of method 100, NWDAF 300 stores group member information of the reporting group. In this case, NWDAF 300 may further receive a group information request including a group identifier associated with the temporary group from CNF 200 (block 460). In response to the group member request, NWDAF sends a UE ID list associated with the group ID of the reporting group to CNF 200 (block 470).

[0051] In other embodiments of the present disclosure, the group member information is stored by UDR 55 or other external databases. In this case, NWDAF 300 sends a create request to UDR 55 to create a group member record for each temporary group (block 480). Then, CNF 200 can query UDR 55 to obtain the group member information.

[0052] In some embodiments of method 400, the analytics information request is a subscription request from a requesting node requesting periodic or aperiodic analytics reports.

[0053] In some embodiments of the method 400, the analysis information request includes a group identifier identifying a group of UEs 100 for which the analysis report is requested. The group identifier includes one of an internal group ID or an external group ID.

[0054] Some embodiments of the method 400 further include requesting an identification of UEs 100 in the group of UEs 100 associated with the group identifier from a unified data management (UDM) function or UDR 65. In response to the request, the NWDAF 300 receives a list of UEs 100 in the group of UEs 100 associated with the group identifier from the UDM or UDR 65.

[0055] In some embodiments of the method 400, the analysis information request includes a list of individual UE 100 identifiers for which the analysis reports are requested. In one example, the individual UE 100 identifiers include a SUPI.

[0056] In some embodiments of method 400, compiling data includes requesting source data from one or more other network functions.

[0057] In some embodiments of method 400, the reporting group is a temporary group valid for a limited time. NWDAF 300 determines a group validity time for the reporting group and sends the group validity time to the requesting node along with the consolidated analysis report and the reporting group identifier.

[0058] In some embodiments of method 400, sending the analysis report and the report group identifier to the requesting node includes sending the integrated analysis report and the group identifier together in a single message. The single message may include a group validity time.

[0059] Some embodiments of the method 400 further include generating and sending a consolidated analysis report for two or more different reporting groups, each reporting group including a different UE among the plurality of UEs 100 .

[0060] Some embodiments of method 400 further include: identifying a second reporting group based on cluster analysis, the second reporting group including a single UE; generating a second integrated analysis report for the second reporting group based on the compiled data; and sending the second integrated analysis report and a report group identifier identifying the second reporting group associated with the second integrated analysis report to the requesting node in response to the request.

[0061] Figure 6An exemplary method 500 of obtaining analysis reports for multiple UEs 100 implemented by a CNF 200 in a wireless core network is shown. The actions shown in dashed lines are optional. The CNF 200 sends a request for analysis reports for multiple UEs 100 to the NWDAF 300 or other producer node (block 510). In response to the request, the CNF 200 receives an integrated analysis report and a report group identifier identifying a report group associated with the integrated analysis report from the NWDAF 300 (block 520). The report group includes two or more UEs 100 of the multiple UEs 100 for which data has been integrated.

[0062] In some embodiments of method 500, CNF sends a group information request including a reporting group identifier to NWDAF 300 or UDER 65 to obtain information about members of the reporting group (block 540). In response to the group information request, CNF 200 receives a list of UE 100 identifiers of UEs 100 in the reporting group (block 550).

[0063] Some embodiments of the method 500 further include: sending a second request including a reporting group identifier to the UDM or UDR. In response to the second request, the CNF 200 receives from the UDM or UDR 65 a list of UE 100 identifiers of the UEs 100 in the reporting group.

[0064] In some embodiments of method 500, the analytics information request is a subscription request from a requesting node requesting periodic or aperiodic analytics reports.

[0065] In some embodiments of the method 500, the analysis information request includes a group identifier identifying the group of UEs 100 for which the analysis report is requested. The group identifier may include, for example, one of an internal group ID or an external group ID.

[0066] In some embodiments of the method 500, the analysis information request includes a list of individual UE IDs for which the analysis report is requested. The individual UE IDs include, for example, a SUPI.

[0067] In some embodiments of method 500 , the reporting group is a temporary group that is valid for a limited time, and the CNF receives the group validity time from the NWDAF 300 .

[0068] In some embodiments of method 500, receiving the consolidated analysis report and the report group identifier includes receiving the consolidated analysis report and the group identifier together in a single message. In some embodiments, the single message may further include a group validity time.

[0069] Some embodiments of the method 500 further include receiving a consolidated analysis report for a plurality of reporting groups, each reporting group including a different UE from among the plurality of UEs 100 .

[0070] Some embodiments of the method further include receiving, in response to the request, from the producer node a second consolidated analysis report and a second reporting group identifier identifying a second reporting group associated with the second consolidated analysis report, wherein the second reporting group includes a single UE.

[0071] The method described herein can be implemented by a device including any functional component, module, unit or circuit. For example, in one embodiment, the device includes a corresponding circuit or circuit system configured to perform the steps shown in the method figure. In this regard, the circuit or circuit system may include a circuit and / or one or more microprocessors and a memory dedicated to performing certain functional processing. For example, the circuit system may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute a program code stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory, a buffer memory, a flash memory device, an optical storage device, etc. In several embodiments, the program code stored in the memory may include program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In an embodiment using a memory, the memory stores program code, which executes the techniques described herein when executed by one or more processors.

[0072] Figure 7The main functional components of a network node configured to act as a NWDAF 300 are shown. The network node includes a receiving unit 310, a compiling unit 320, a clustering unit 330, a generating unit 340, a sending unit 350, and an optional group information unit 360. The various units 310-360 can be implemented by hardware and / or software code executed by one or more processors or processing circuits. The receiving unit 310 is configured to receive a request for an analysis report of multiple UEs 100 from the CNF 200. The compiling unit 320 is configured to send a measurement report according to the data compiled for the analysis report. The clustering unit 330 is configured to perform cluster analysis based on the compiled data to identify a reporting group, the reporting group including two or more UEs 100 in the multiple UEs 100 for which data is to be integrated. The generating unit 340 is configured to generate an integrated analysis report based on the compiled data, the integrated analysis report including integrated data common to all members of the reporting group. The sending unit 350 is configured to send the integrated analysis report and the reporting group identifier identifying the reporting group associated with the integrated analysis report to CNF 200 in response to the request. When resending, the group information unit 360 is configured to store the group member data of the reporting group in an internal or external database. In the case where the group member data is stored internally, the group information unit 360 is configured to receive a group member request containing the reporting group identifier from CNF 200, and in response to the group member request, send a list of UE 100 identifiers of the UE 100 in the reporting group. In the case where the group member data is stored externally, the group information unit 360 is configured to send a creation request to UDR 65 or other external database to create a record for each temporary group. For each temporary group, the creation request includes a reporting group identifier and a list of UE 100 identifiers of the UE 100 in the reporting group indicated by the reporting group identifier. The creation request may also optionally include a group validity time for each temporary group.

[0073] Figure 8The main functional components of a network node configured to act as a CNF 200 are shown. The CNF 200 includes a sending unit 210, a receiving unit 220, and an optional group information unit 230. Each unit 210-230 can be implemented by hardware and / or software code executed by one or more processors or processing circuits. The sending unit 210 is configured to send a request for analysis reports of multiple UEs 100 to the NWDAF 300. The first receiving unit 220 is configured to receive an integrated analysis report and a report group identifier identifying a report group associated with the integrated analysis report from the NWDAF 300 in response to the request. When present, the group information unit 230 is configured to send a group information request to the NWDAF 300 or UDR 65 to obtain a list of UEs in one or more temporary groups. The group information request contains a report group identifier for each temporary group to which the request belongs. In response to the group information request, the group information unit 230 additionally receives from the NWDAF 300 or the UDR 65 a list of UE 100 identifiers of the UEs 100 in the reporting group.

[0074] Fig. 9 A core network node 600 is shown that can be configured to act as a CNF 200 or NWDAF 300 as described herein according to one embodiment. The core network node 600 includes an interface circuit 610, a processing circuit 620, and a memory 630. The interface circuit 610 couples the core network node 600 to a communication network and enables communication with other core network nodes in the wireless core network. The processing circuit 620 controls the overall operation of the core network node 600 and executes a computer program 640 stored in the memory 630 to perform one or more methods as described herein. The processing circuit 620 may include one or more microprocessors, hardware, firmware, or a combination thereof. The memory 630 includes both volatile and non-volatile memory for storing computer program code and data required for the operation of the processing circuit 620. The memory 630 may include any tangible, non-transitory computer-readable storage medium for storing data, including electronic, magnetic, optical, electromagnetic, or semiconductor data storage devices. The memory 630 stores a computer program 640 including executable instructions that configure the processing circuit 620 to perform operations according to the methods described herein. Figure 5 and 6Method 300 (for NWDAF 300) or method 400 (for CNF 200). In this regard, the computer program 640 may include one or more code modules corresponding to the above-mentioned components or units. Typically, computer program instructions and configuration information are stored in non-volatile memory such as ROM, erasable programmable read-only memory (EPROM), or flash memory. Temporary data generated during operation may be stored in volatile memory such as random access memory (RAM). In some embodiments, the computer program core network node 600 for configuring the processing circuit 620 as described herein may be stored in a removable memory such as a portable compact disk, a portable digital video disk, or other removable medium. The computer program 660 may also be embodied in a carrier such as an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0075] Those skilled in the art will also appreciate that the embodiments herein further include corresponding computer programs. The computer program includes instructions that, when executed on at least one processor of the device, cause the device to perform any of the above-mentioned corresponding processes. In this regard, the computer program may include one or more code modules corresponding to the above-mentioned components or units.

[0076] The embodiment further includes a carrier embodying such a computer program. The carrier may include one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium.

[0077] In this regard, embodiments herein further include a computer program product stored on a non-transitory computer-readable (storage or recording) medium and comprising instructions that, when executed by a processor of a device, cause the device to perform as described above.

[0078] The embodiment further includes a computer program product, the computer program product including program code parts, when the computer program product is executed by a computing device, these program code parts are used to perform the steps of any one of the embodiments herein. The computer program product can be stored on a computer readable recording medium.

[0079] When a consumer NF requests an analysis report for a user group with a large number of members from the NWDAF 300, the techniques described herein mitigate the impact of massive signaling in the network and the requirements on the CPU, memory and storage of the consumer network function. The NWDAF clusters the results of the analysis report, thereby creating a report per cluster per UE 100 (sharing the report), rather than creating a report per UE 100. This mitigates the problem of massive signaling in the network (the more data that can be shared by the UEs 100, the less signaling). It also addresses the CPU, memory and storage issues of the consumer NFs, as they do not need to retain massive memory and storage for storing each individual analysis report, or even massive CPU to parse each individual analysis report.

Claims

1. A method (400) implemented by a core network node in a wireless core network for distributing analysis reports of a plurality of UEs (100), the method comprising: receiving (410) a request for analysis reports of the plurality of UEs (100) from a requesting node (40, 45, 200, 600); compiling (420) data for said analysis report; Based on the compiled data, performing (430) a cluster analysis to identify a reporting group including two or more UEs (100) of the plurality of UEs (100) for which data is to be consolidated; generating ( 440 ) an integrated analysis report based on the compiled data, the integrated analysis report including integrated data common to all members of the reporting group; In response to the request, the consolidated analysis report and a report group identifier identifying the report group associated with the consolidated analysis report are sent (450) to the requesting node (40, 45, 200, 600).

2. The method (400) according to claim 1, wherein: The request is a subscription request from the requesting node (40, 45, 200, 600) for requesting a periodic or aperiodic analysis report.

3. The method (400) according to claim 1 or 2, wherein: The request includes a group identifier identifying a group of UEs (100) for which an analysis report is requested.

4. The method (400) according to claim 3, wherein: The group identifier comprises one of an internal group identifier or an external group identifier.

5. The method (400) according to claim 3, further comprising: requesting from a unified data management (UDM) function (55) or a unified data repository (UDR) function (65) an identification of the UE (100) in the group of UEs (100) associated with the group identifier; and In response to the request, a list of UEs (100) in the group of UEs (100) associated with the group identifier is received from the UDM (55) or UDR (65).

6. The method (400) according to claim 1 or 2, wherein: The request includes a list of individual UE (100) identifiers for which analysis reports are requested.

7. The method (400) according to claim 6, wherein: The individual UE (100) identifier comprises a User Permanent Identifier (SUPI).

8. The method (400) according to claim 1 or 2, wherein: Compiling the data includes requesting source data from one or more other network functions.

9. The method (400) according to claim 1 or 2, wherein: The reporting group is a temporary group valid for a limited time.

10. The method (400) according to claim 9, further comprising: The group validity period of the report group is determined, and the group validity period is sent to the requesting node together with the integrated analysis report and a report group identifier (40, 45, 200, 600).

11. The method (400) according to claim 10, wherein: Sending the analysis report and the report group identifier to the requesting node (40, 45, 200, 600) includes sending the integrated analysis report and the group identifier together in a single message.

12. The method (400) according to claim 11, wherein: The single message further includes the group validity time.

13. The method (400) according to claim 1 or 2, further comprising: receiving (460) a group information request from the requesting node (40, 45, 200, 600), the group information request including the reporting group identifier; as well as In response to the group information request, a list of UE (100) identifiers of UEs (100) in the reporting group is sent (470) to the requesting node (40, 45, 200, 600).

14. The method (400) according to claim 1 or 2, further comprising: A request is sent (480) to a data repository to create a new record associating the reporting group identifier with a list of UE (100) identifiers of UEs (100) in the reporting group.

15. The method (400) according to claim 1 or 2, further comprising: An integrated analysis report for two or more different reporting groups is generated and sent, each reporting group including a different UE among the plurality of UEs (100).

16. The method (400) according to claim 1 or 2, further comprising: Based on the cluster analysis, identifying a second reporting group, the second reporting group comprising a single UE (100); generating a second integrated analysis report for the second reporting group based on the compiled data; In response to the request, the second integrated analysis report and a report group identifier identifying the second report group associated with the second integrated analysis report are sent to the requesting node (40, 45, 200, 600).

17. A network node (600) implemented in a communication network and configured to distribute analysis reports of a plurality of UEs (100) to a requesting node (40, 45, 200, 600) in the communication network, the network node comprising: An interface circuit (610) for communicating with other network nodes in the communication network; The processing circuit (620) is configured to: Receiving a request for analysis reports of the plurality of UEs (100) from the requesting node (40, 45, 200, 600); compiling data for said analytical report; Based on the compiled data, performing a cluster analysis to identify a reporting group, the reporting group comprising two or more UEs (100) of the plurality of UEs (100) for which data is to be consolidated; generating an integrated analysis report based on the compiled data, the integrated analysis report including integrated data common to all members of the reporting group; as well as In response to the request, the integrated analysis report and a report group identifier identifying the report group associated with the integrated analysis report are sent to the requesting node (40, 45, 200, 600).

18. The network node (600) according to claim 17, wherein: The request is a subscription request from the requesting node (40, 45, 200, 600) for requesting a periodic or aperiodic analysis report.

19. The network node (600) according to claim 17 or 18, wherein: The request includes a group identifier identifying a group of UEs (100) for which an analysis report is requested.

20. The network node (600) according to claim 19, wherein The group identifier comprises one of an internal group identifier or an external group identifier.

21. The network node (600) according to claim 19, wherein: The processing circuit (620) is further configured to: requesting from a unified data management (UDM) function (55) or a unified data repository (UDR) function (65) an identification of a UE (100) in the group of UEs (100) associated with the group identifier; and In response to the request, a list of UEs (100) in the group of UEs (100) associated with the group identifier is received from the UDM (55) or UDR (65).

22. The network node (600) according to claim 17 or 18, wherein: The request includes a list of individual UE (100) identifiers for which analysis reports are requested.

23. The network node (600) according to claim 22, wherein: The individual UE (100) identifier comprises a User Permanent Identifier (SUPI).

24. The network node (600) according to claim 17 or 18, wherein: The processing circuit (620) is further configured to: request source data from one or more other network functions.

25. The network node (600) according to claim 17 or 18, wherein The reporting group is a temporary group valid for a limited time.

26. The network node (600) according to claim 25, wherein The processing circuit (620) is further configured to determine a group validity period of the reporting group and send the group validity period together with the integrated analysis report and a reporting group identifier to the requesting node (40, 45, 200, 600).

27. The network node (600) according to claim 26, wherein The processing circuit (620) is further configured to send the consolidated analysis report and the group identifier together in a single message.

28. The network node (600) according to claim 27, wherein The single message further includes the group validity time.

29. The network node (600) according to claim 17 or 18, wherein: The processing circuit (620) is further configured to: receiving a group membership request from the requesting node (40, 45, 200, 600), the group membership request including the reporting group identifier; as well as In response to the group membership request, a list of UE (100) identifiers of UEs (100) in the reporting group is sent to the requesting node (40, 45, 200, 600).

30. The network node (600) according to claim 17 or 18, wherein: The processing circuit (620) is further configured to send a request to a data repository to create a new record, the new record associating the reporting group identifier with a list of UE (100) identifiers of UEs (100) in the reporting group.

31. The network node (600) according to claim 17 or 18, wherein: The processing circuit (620) is further configured to generate and send an integrated analysis report for two or more different reporting groups, each reporting group including a different UE among the plurality of UEs (100).

32. The network node (600) according to claim 17 or 18, wherein: The processing circuit (620) is further configured to: Based on the cluster analysis, identifying a second reporting group, the second reporting group comprising a single UE (100); generating a second integrated analysis report for the second reporting group based on the compiled data; In response to the request, the second integrated analysis report and a report group identifier identifying the second report group associated with the second integrated analysis report are sent to the requesting node (40, 45, 200, 600).

33. A network node (300, 600) for obtaining analysis reports of a plurality of UEs (100) in a communication network, the network node comprising components configured to perform the following operations: receiving a request for analysis reports of the plurality of UEs (100) from a requesting node (40, 45, 200, 600); compiling data for said analytical report; Based on the compiled data, performing a cluster analysis to identify a reporting group, the reporting group comprising two or more UEs (100) of the plurality of UEs (100) for which data is to be consolidated; generating an integrated analysis report based on the compiled data, the integrated analysis report including integrated data common to all members of the reporting group; In response to the request, the integrated analysis report and a report group identifier identifying the report group associated with the integrated analysis report are sent to the requesting node (40, 45, 200, 600).

34. The network node (300, 600) according to claim 33, further comprising means configured to perform the method according to any one of claims 2-16.

35. A computer program comprising executable instructions which, when executed by processing circuitry in a network node of a wireless communication network, cause the network node to perform a method according to any one of claims 1-16.

36. A computer-readable storage medium containing a computer program comprising executable instructions which, when executed by a processing circuit in a network node in a wireless communication network, cause the network node to perform a method according to any one of claims 1-16.

37. A non-transitory computer-readable storage medium containing a computer program comprising executable instructions which, when executed by a processing circuit in a network node in a wireless communication network, cause the network node to perform the method according to any one of claims 1-16.

Images