Systems and methods for providing analytics identifiers in subscription change notifications

Abstract

A system and method are presented for providing at least one analytic identifier (ID) in a subscription change notification. A target data analytic function (DAF) may accept a transfer of at least one analytic subscription from a source DAF to a target DAF. The at least one analytic subscription may be associated with a new subscription correlation identifier (ID). The target DAF may send a notification message to an analytic consumer. The target DAF may include the new subscription correlation ID and an identification of the at least one analytic subscription.

Description

[Technical Field]

[0001] The present disclosure relates generally to wireless communications, including, but not limited to, systems and methods for providing at least one analysis identifier (ID) in a subscription change notification. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP®), a standards organization, is currently specifying a new air interface called 5G New Radio (5G NR) and the Next Generation Packet Core Network (NG-CN or NGC). 5G NR has three main components: the 5G Access Network (5G-AN), the 5G Core Network (5GC), and the User Equipment (UE). To facilitate the enablement of different data services and requirements, the elements of the 5GC, also known as network functions, have been simplified; some of them are software-based and some are hardware-based, so they can be adapted as needed. Summary of the Invention [Means for solving the problem]

[0003] The exemplary embodiments disclosed herein are directed not only to solving problems associated with one or more problems presented in the prior art, but also to providing additional features that will become readily apparent from a review of the following detailed description in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, these embodiments are presented by way of example, not limitation, and various modifications to the disclosed embodiments (including, for example, combining features from various disclosed examples, embodiments, and / or implementations) may be made while remaining within the scope of the present disclosure, as will be apparent to those skilled in the art reading this disclosure.

[0004] At least one aspect relates to the following system, method, apparatus, or computer-readable medium: A target data analysis function (DAF) (e.g., a network data analysis function (NWDAF)) may accept the transfer of at least one analytic subscription from a source DAF to the target DAF. The at least one analytic subscription may be associated with a new subscription correlation identifier (ID) (e.g., allocated / assigned by the target NWDAF). The target DAF may send a notification message (e.g., an Nnwdaf_EventsSubscription_Notify request message) to the analytic consumer. The target DAF may comprise the new subscription correlation ID and an identification of the at least one analytic subscription. The identification of the at least one analytic subscription may include at least one of an ID number, a name, a group number, a table index, or an item number. The notification message may further include at least one of an old subscription correlation ID associated with the source DAF (e.g., allocated / assigned by the source DAF) or a notification correlation ID.

[0005] In some embodiments, the analytics consumer may determine to modify or delete at least one other analytics subscription (e.g., those analytics subscriptions remaining with the source NWDAF) according to the identification of the at least one analytics subscription. The analytics consumer may send a request to the source NWDAF to modify or delete the at least one other analytics subscription.

[0006] In some embodiments, the analytics consumer may decide to modify or delete one or more of the at least one analytics subscriptions (e.g., those analytics subscriptions transferred to the target NWDAF) according to the identification of the at least one analytics subscription. The analytics consumer may send a request to the target DAF to modify or delete one or more of the at least one analytics subscription. In some embodiments, the at least one analytics subscription may consist of all analytics subscriptions that may be subscribed to by analytics subscriptions from the source DAF.

[0007] In some embodiments, the second target DAF may accept the transfer of at least one other analytical subscription from the source DAF to the second target DAF. The at least one other analytical subscription may be associated with a second new subscription correlation identifier (ID). The second target DAF may send a second notification message to the analytical consumer. The second notification message may comprise the second new subscription correlation ID and an identification of the at least one other analytical subscription. The analytical consumer may decide to modify or delete the at least one other analytical subscription according to the identification of the at least one analytical subscription. The analytical consumer may send a request to the second target DAF to modify or delete the at least one other analytical subscription.

[0008] In some embodiments, the second target DAF may accept (e.g., undertake, receive) the transfer of one or more analytic subscriptions of the at least one analytic subscription from the target DAF to the second target DAF. The one or more analytic subscriptions may be associated with a second new subscription correlation identifier (ID). The second target DAF may send a second notification message to the analytic consumer. The second notification message may comprise the second new subscription correlation ID and an identification of the one or more analytic subscriptions. The analytic consumer may decide to modify (e.g., update, change) or delete (e.g., terminate / terminate, cancel, unsubscribe) one or more analytic subscriptions according to the identification of the one or more analytic subscriptions. The analytic consumer may send a request to the second target DAF to modify or delete one or more analytic subscriptions.

[0009] In some embodiments, the analytics consumer may decide to modify or delete at least one analytics subscription remaining with the source DAF according to the identification of the at least one analytics subscription, and may send a request to the source DAF to modify or delete at least one analytics subscription remaining with the source DAF.

[0010] In some embodiments, the analytics consumer may determine to modify or delete at least one analytics subscription remaining with the target DAF according to the identification of the at least one analytics subscription and the identification of the one or more analytics subscriptions. The analytics consumer may send a request to the target DAF to modify or delete at least one analytics subscription remaining with the target DAF.

[0011] In some embodiments, an analytics consumer may receive a notification message (e.g., a Nnwdaf_EventsSubscription_Notify request message) from a target data analytics function (DAF). The notification message may comprise (i) a new subscription correlation identifier (ID) associated with at least one analytics subscription being transferred from the source DAF to the target DAF, and (ii) an identification of the at least one analytics subscription. The present invention provides, for example, the following. (Item 1) 1. A method, comprising: Accepting, by a target data analysis function (DAF), a transfer of at least one analytical subscription from a source DAF to a target DAF, wherein the at least one analytical subscription is associated with a new subscription correlation identifier (ID); sending, by the target DAF, a notification message to an analytics consumer, the notification message comprising the new subscription correlation ID and an identification of the at least one analytics subscription; A method comprising: (Item 2) Item 10. The method of item 1, wherein the notification message further comprises at least one of an old subscription correlation ID or a notification correlation ID associated with the source DAF. (Item 3) The analytics consumer: determining to modify or delete at least one other analytical subscription according to said identification of said at least one other analytical subscription; or sending a request to the source DAF to modify or delete the at least one other analytical subscription; Item 1, wherein the method performs at least one of the following: (Item 4) The analytics consumer: Deciding to modify or delete one or more of the at least one analytical subscription according to the identification of the at least one analytical subscription; or sending a request to the target DAF to modify or delete one or more of the at least one analytical subscription; Item 1, wherein the method performs at least one of the following: (Item 5) Item 10. The method of item 1, wherein the at least one analytical subscription consists of all analytical subscriptions subscribed to by the analytical consumer from the source DAF. (Item 6) The second target DAF is Accepting the transfer of at least one other analytical subscription from the source DAF to the second target DAF, wherein the at least one other analytical subscription is associated with a second new subscription correlation identifier (ID); Item 14. The method of item 1, further comprising sending a second notification message to the analytics consumer comprising the second new subscription correlation ID and an identification of the at least one other analytics subscription. (Item 7) The analytics consumer: determining to modify or delete the at least one other analytical subscription according to the identification of the at least one analytical subscription; or sending a request to the second target DAF to modify or delete the at least one other analytical subscription; Item 7. The method according to item 6, wherein at least one of the following is performed. (Item 8) The second target DAF is Accepting a transfer of one or more analytic subscriptions of the at least one analytic subscription from the target DAF to the second target DAF, the one or more analytic subscriptions being associated with a second new subscription correlation identifier (ID); Item 14. The method of item 1, sending a second notification message to the analytics consumer comprising the second new subscription correlation ID and an identification of the one or more analytics subscriptions. (Item 9) The analytics consumer: Deciding to modify or delete one or more analytical subscriptions according to the identification of the one or more analytical subscriptions; or sending a request to the second target DAF to modify or delete the one or more analytic subscriptions; 9. The method according to item 8, wherein at least one of the following is performed. (Item 10) The analytics consumer: Deciding to modify or delete at least one analytical subscription remaining with the source DAF according to the identification of the at least one analytical subscription; or sending a request to the source DAF to modify or delete the at least one analytical subscription remaining with the source DAF; 9. The method according to item 8, wherein at least one of the following is performed. (Item 11) The analytics consumer: determining to modify or delete at least one analytical subscription remaining with the target DAF according to the identification of the at least one analytical subscription and the identification of the one or more analytical subscriptions; or sending a request to the target DAF to modify or delete the at least one analytic subscription remaining with the target DAF; 9. The method according to item 8, wherein at least one of the following is performed. (Item 12) 1. A method, the method comprising receiving, by an analytics consumer, a notification message from a target data analytics function (DAF); The method, wherein the notification message comprises: (i) a new subscription correlation identifier (ID) associated with at least one analytical subscription transferred from a source DAF to the target DAF; and (ii) an identification of the at least one analytical subscription. (Item 13) 13. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of items 1 to 12. (Item 14) 13. A device comprising at least one processor configured to perform the method of any one of items 1 to 12. [Brief explanation of the drawings]

[0012] Various exemplary embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and merely depict exemplary embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, the drawings are not necessarily drawn to scale.

[0013] [Figure 1]1 illustrates an example of a cellular communication network in which the techniques disclosed herein may be implemented according to embodiments of the present disclosure.

[0014] [Figure 2] 1 illustrates a block diagram of an example base station and a user equipment device according to some embodiments of the present disclosure.

[0015] [Figure 3] 1 illustrates an example of an analysis publishing architecture in a 5G system according to some embodiments of the present disclosure.

[0016] [Figure 4] FIG. 1 illustrates a sequence diagram of an analysis subscription operation according to some embodiments of the present disclosure.

[0017] [Figure 5] FIG. 1 illustrates a sequence diagram of an analysis subscription operation according to some embodiments of the present disclosure.

[0018] [Figure 6] FIG. 1 illustrates a sequence diagram of an analysis subscription operation according to some embodiments of the present disclosure.

[0019] [Figure 7] FIG. 1 illustrates a sequence diagram of an analysis subscription operation according to some embodiments of the present disclosure.

[0020] [Figure 8] FIG. 1 illustrates a sequence diagram of an analysis subscription operation according to some embodiments of the present disclosure.

[0021] [Figure 9] 1 illustrates a flow diagram for providing at least one analysis identifier (ID) in a subscription change notification according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0022] (1. Mobile Communications Technology and the Environment) 1 illustrates an exemplary wireless communication network and / or system 100 in which the techniques disclosed herein according to embodiments of the present disclosure may be implemented. In the following description, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as “network 100.” Such exemplary network 100 includes a base station 102 (hereinafter “BS 102,” also referred to as a wireless communication node) and a user equipment device 104 (hereinafter “UE 104,” also referred to as a wireless communication device) that may communicate with each other via a communication link 110 (e.g., a wireless communication channel), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 that overlap a geographic region 101. In FIG. 1, the BS 102 and the UE 104 are contained within the respective geographic boundaries of the cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating in its assigned bandwidth to provide adequate wireless communication coverage to intended users.

[0023] For example, the BS 102 may operate within an assigned channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via a downlink radio frame 118 and an uplink radio frame 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, the BS 102 and the UE 104 are generally described herein as non-limiting examples of "communication nodes" that may practice the methods disclosed herein. Such communication nodes may be capable of wireless and / or wired communication in accordance with various embodiments of the present solution.

[0024] 2 illustrates a block diagram of an exemplary wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) in accordance with some embodiments of the present solution. System 200 may include components and elements configured to support known or conventional operational features that need not be described in detail herein. In one exemplary embodiment, system 200 may be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment, such as wireless communication environment 100 of FIG. 1, as previously described.

[0025] The system 200 generally includes a base station 202 (hereinafter "BS 202") and a user equipment device 204 (hereinafter "UE 204"). The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled and interconnected as needed via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled and interconnected as needed via a data communication bus 240. The BS 202 communicates with the UE 204 over a communication channel 250, which may be any wireless channel or other medium suitable for the transmission of data as described herein.

[0026] As will be appreciated by those skilled in the art, system 200 may further include any number of modules other than those shown in FIG. 2 . Those skilled in the art will appreciate that the various exemplary blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this compatibility and compatibility of hardware, firmware, and software, the various exemplary components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software may depend on the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a manner suitable for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

[0027] According to some embodiments, the UE transceiver 230 may be referred to herein as an “uplink” transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each with circuitry coupled to an antenna 232. A duplexing switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-duplexed manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a “downlink” transceiver 210 including an RF transmitter and an RF receiver, each with circuitry coupled to an antenna 212. A downlink duplexing switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time-duplexed manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that the downlink transmitter is coupled to the downlink antenna 212 at the same time that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 may be timed so that the uplink transmitter is coupled to the uplink antenna 232 at the same time that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250. In some embodiments, there is truncated time synchronization with a minimum guard time between changes in duplex direction.

[0028] The UE transceiver 230 and the base station transceiver 210 are configured to communicate over a wireless data communication link 250 and cooperate with appropriately configured RF antenna devices 212 / 232 that may support a particular wireless communication protocol and modulation scheme. In some exemplary embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it will be understood that the present disclosure is not necessarily limited to application to a particular standard and associated protocol. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0029] According to various embodiments, the BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, the UE 204 may be embodied in various types of user devices, such as a mobile phone, a smartphone, a personal digital assistant (PDA), a tablet, a laptop computer, a wearable computing device, etc. The processor modules 214 and 236 may be implemented or realized using a general-purpose processor, a content-addressable memory, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. In this manner, the processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other such configuration.

[0030] Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, firmware, software modules executed by processor modules 214 and 236, respectively, or any practical combination thereof. Memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, each of memory modules 216 and 234 may be coupled to processor modules 210 and 230 such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 may be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions executed by processor modules 210 and 230, respectively. Each of the memory modules 216 and 234 may also include non-volatile memory for storing instructions executed by the processor modules 210 and 230, respectively.

[0031] The network communications module 218 generally represents the hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bidirectional communications between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communications module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, the network communications module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 may communicate with conventional Ethernet-based computer networks. In this manner, the network communications module 218 may include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). As used herein with respect to a specified operation or function, the terms “configured for,” “configured to,” and conjugations thereof refer to devices, components, circuits, structures, machines, signals, etc. that are physically configured, programmed, formatted, and / or arranged to perform the specified operation or function.

[0032] The Open Systems Interconnection (OSI) model (referred to herein as the "Open Systems Interconnection Model") is a conceptual and logical layout that defines network communications used by open systems (e.g., wireless communication devices, wireless communication nodes) to interconnect and communicate with other systems. The model is divided into seven subcomponents or layers, each of which represents a conceptual collection of services provided to the layers above and below it. The OSI model also defines logical networks and effectively describes computer packet transfers through the use of different layer protocols. The OSI model may be referred to as the seven-layer OSI model or seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the medium access control (MAC) layer. In some embodiments, the third layer may be the radio link control (RLC) layer. In some embodiments, the fourth layer may be the packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be the radio resource control (RRC) layer. In some embodiments, the sixth layer may be a non-access stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is another layer.

[0033] To enable those skilled in the art to make and use the present solution, various exemplary embodiments of the present solution are described below with reference to the accompanying drawings. As will be apparent to those skilled in the art, after reading this disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, any specific order or hierarchy of steps in the methods disclosed herein is merely an example approach. Based on design preferences, the specific order or hierarchy of steps in a disclosed method or process can be rearranged while remaining within the scope of the present solution. Thus, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or operations in a sample order, and that the present solution is not limited to the specific order or hierarchy presented, unless otherwise specified. 2. Systems and methods for providing analytics identifiers (IDs) in subscription change notifications

[0034] A Network Data Analysis Function (NWDAF) may transfer one or more of its analysis subscriptions to other NWDAF instances due to internal triggers (e.g., load balancing, graceful shutdown) and / or external triggers (e.g., user equipment (UE) mobility). The analysis subscription transfer procedure may be performed / accomplished / executed for all subscriptions or for a selected subset of subscriptions associated with a particular area, a particular analysis identifier (ID), a particular network function (NF), and / or a particular UE.

[0035] To collect data from user equipment, network functions, and / or operations, administration, and maintenance (OAM) systems, the NWDAF may extract data from microservice functions residing within the network core so that relevant data can be analyzed at scale. Analytics (e.g., including data or derived / generated from data) may include, for example, at least one of analysis of different types of network data and statistics to identify trends and patterns, or analysis of network / performance issues (e.g., packet loss, throughput, or latency). Analytics may be generated and / or provided by the NWDAF and may provide insight into what devices (e.g., device types, capabilities, operating modes) may be on the network and how devices communicate with each other. Analytics may also compare and correlate device analytics with data / analysis of other devices. Analytics consumers may request and / or subscribe to one or more specific analytics that the NWDAF may provide / generate. At least one of these analytics subscriptions may be forwarded to another NWDAF to deliver the corresponding analytics to the analytics consumer.

[0036] When the target NWDAF takes over one or more analytics subscriptions, the target NWDAF may inform / notify the analytics consumer about the successful transfer of the analytics subscriptions from another NWDAF via a subscription change notification. The notification may include the new subscription correlation ID assigned by the target NWDAF and the old subscription correlation ID allocated by the source NWDAF. The analytics consumer may replace the old subscription correlation ID with the new subscription correlation ID. The analytics consumer may use the new subscription correlation ID for further management of the corresponding subscriptions (e.g., to modify or delete some or all of the corresponding subscriptions).

[0037] However, if a source NWDAF transfers some of its analytic subscriptions to a target NWDAF, for the remaining analytic subscriptions still held at the source NWDAF, the analytic consumer may not be able to modify or delete the remaining analytic subscriptions using the old subscription correlation ID because the old subscription correlation ID may have already been replaced with a new one.

[0038] Figure 3 shows an example of an analytics publishing architecture in a 5G system. The NWDAF may publish (e.g., generate, provide, produce, output, publish) analytics results directly to any 5G Core (5GC) Network Function (NF) (e.g., Access and Mobility Management Function (AMF)) or via a Data Collection and Coordination Function (DCCF) / Messaging Framework Adapter Function (MFAF). The analytics publishing architecture may include at least one of the following functions: analytics consumer (e.g., AMF), Data Collection and Coordination Function (DCCF), Messaging Framework Adapter Function (MFAF), Analytics Data Repository Function (ADRF), and / or Network Data Analytics Function (NWDAF).

[0039] An analytics consumer may provide / include functionality to manage at least one subscription (unsubscription) to notifications of analytics information from the NWDAF. The DCCF may provide functionality to coordinate analytics and / or data collection from one or more NFs based on requests from one or more NF service consumers. The MFAF may provide functionality to allow NF consumers to configure or reconfigure the behavior of mapping data and / or analytics received by the MFAF to outbound notification endpoints. The ADRF may provide functionality to allow NF consumers to store, retrieve, and / or remove data or analytics from the ADRF. The NWDAF may provide analytics information for different analytics events to NF service consumers. An NWDAF instance may request the transfer of an analytics subscription to another NWDAF instance. (Implementation Example 0: Analysis Subscription Transfer Procedure Initiated by Source NWDAF)

[0040] In step 1, the analytics consumer may send a request message (e.g., an Nnwdaf_EventsSubscription_Subscribe request) to subscribe to at least one analysis (e.g., a type of analysis) from a source NWDAF. The request may include an identification of the analysis to which the analytics consumer is subscribed, a notification uniform resource identifier (URI), and / or a notification correlation ID.

[0041] In step 2, the source NWDAF may assign (e.g., generate, allocate) a subscription correlation ID associated with at least one analytics subscription. The source NWDAF may send a response message (e.g., Nnwdaf_EventsSubscription_SubscribeResponse) to the analytics consumer. The response message may include the subscription correlation ID.

[0042] In step 3 (e.g., an optional step), based on an external trigger and / or an internal trigger, the source NWDAF may decide to prepare an analytics subscription transfer (e.g., transfer of at least one analytics subscription of a subscribed analytics consumer from the source NWDAF) to the target NWDAF. The source NWDAF may discover one or more candidate target NWDAFs (e.g., NWDAF-Y and NWDAF-Z). The NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to the one or more candidate target NWDAFs. The request message may include instruction information (e.g., a prepared analytics subscription transfer instruction) within the request message. The one or more candidate target NWDAFs (e.g., NWDAF-Y and NWDAF-Z) may start data collection from network functions (NFs) or operations, administration, and maintenance (OAM) and may start analytics generation for the indicated analytics subscriptions. The source NWDAF may decide to select a target NWDAF (e.g., NWDAF-Y) from the one or more candidate target NWDAFs. The source NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to a selected target NWDAF (e.g., NWDAF-Y) to ask the selected target NWDAF to take over at least one analytics subscription from the source NWDAF. The source NWDAF may cancel prepared analytics subscription transfers to other candidate target NWDAF-Z. If there is a preparation step, the selected target NWDAF can take over at least one analytics subscription from the source NWDAF in a short period of time.

[0043] In step 4, the source NWDAF may determine to initiate an analytics subscription transfer from the source NWDAF to one or more other NWDAFs. The source NWDAF may determine one or more analytics subscriptions to transfer and may determine to perform the analytics subscription transfer (of the one or more determined analytics subscriptions) to the target NWDAF. The source NWDAF may determine one or more analytics subscriptions to be transferred to the target NWDAF based on, for example, the load, capabilities, and processing capabilities of the source NWDAF and / or the target NWDAF.

[0044] In step 5, the source NWDAF may perform NWDAF discovery and select a target NWDAF (e.g., from multiple target / candidate NWDAFs). If the target NWDAF has already been discovered as part of a prepared analysis subscription transfer, NWDAF discovery may be skipped.

[0045] In step 6, the source NWDAF may send a request message (using the Nnwdaf_EventsSubscription_Transfer service operation) to transfer to the target NWDAF one or more analytics subscriptions determined in step 4. The request message may include / identify / specify the analytics subscriptions being transferred and may include the notification URI and / or the notification correlation ID received by the source NWDAF from the analytics consumer in step 1, if not provided during the prepared analytics subscription transfer.

[0046] In step 7 (e.g., an optional step), the target NWDAF may send a response message (e.g., a Nnwdaf_EventsSubscription_Transfer response) to the source NWDAF (e.g., in response to the request message).

[0047] In step 8, the target NWDAF may accept the transfer of at least one analytic subscription (e.g., one or more analytic subscriptions determined in step 4 and / or identified in the request message) from the source DAF to the target DAF. The target NWDAF may take over / receive at least one analytic subscription (e.g., to perform the generation of analytics for consumption by analytics consumers) based on the information received from the source NWDAF. If not already done during the prepared analytic subscription transfer, the target NWDAF may allocate a new subscription correlation ID to the received / transferred analytic subscription.

[0048] In steps 9 and 10, the target NWDAF may inform / notify the analytics consumer about the success of the analytics subscription transfer using a request message (e.g., Nnwdaf_EventsSubscription_Notify). The new subscription correlation ID assigned / allocated by the target NWDAF and the old subscription correlation ID assigned / allocated by the source NWDAF may be provided / included / identified in the request message (e.g., Nnwdaf_EventsSubscription_Notify). The request message may include a notification correlation ID that allows the analytics consumer to correlate the notification to the initial subscription request made with the source NWDAF in step 1. The analytics consumer may send a response message (e.g., NnwdafEventsSubscriptionNotify response) to the target NWDAF (e.g., in response to the request message).

[0049] In step 11 (e.g., a conditional step), if the Nnwdaf_EventsSubscription_Transfer request received by the target NWDAF in step 6 included an “analytics context identifier,” the target NWDAF may request the “analytics context” by invoking the Nnwdaf_AnalyticsInfo_ContextTransfer service operation.

[0050] In step 12 (e.g., an optional step), if a response message was not sent in step 7, the target NWDAF may confirm the analytics subscription transfer (e.g., confirm acceptance of the analytics subscription transfer) by sending a response message (e.g., Nnwdaf_EventsSubscription_Transfer) to the source NWDAF.

[0051] In step 13, the target NWDAF may derive / generate (e.g., perform analysis or processing) a new output analysis based on the new input data.

[0052] In steps 14 and 15, the target NWDAF may inform / notify the analytics consumer about the new analytics using a subscription change notification or notification message (e.g., Nnwdaf_EventsSubscription_Notify message).

[0053] The target NWDAF may include an identification of the transferred analytics in the subscription change notification, which may enable the analytics consumer to identify which subscribed analytics have been transferred and which have not, so that the analytics consumer can use a new subscription correlation ID for the transferred analytics subscriptions and the old correlation subscription ID for the analytics subscriptions that remain with the source NWDAF. (Example implementation 1: Part of the subscribed analysis is transferred from the source NWDAF to the target NWDAF)

[0054] In step 1, an analytics consumer may send a request message (e.g., an Nnwdaf_EventsSubscription_Subscribe request) to subscribe to at least one analysis (e.g., a type of analysis) from a source NWDAF. The request message may include the analysis to which the analytics consumer is subscribed, a notification uniform resource identifier (URI), and / or a notification correlation ID.

[0055] In step 2, the source NWDAF may assign (e.g., generate, allocate) a subscription correlation ID associated with at least one analytics subscription. The source NWDAF may send a response message (e.g., Nnwdaf_EventsSubscription_SubscribeResponse) to the analytics consumer. The response message may include the subscription correlation ID.

[0056] In step 3 (e.g., an optional step), the source NWDAF may determine to prepare an analytics subscription transfer (e.g., transfer of at least one analytics subscription of a subscribed analytics consumer from the source NWDAF) for some of the subscribed analytics to the target NWDAF according to a trigger. For example, the trigger for the transfer may be due to a load balancing issue. The source NWDAF may discover one or more candidate target NWDAFs (e.g., NWDAF-Y and NWDAF-Z). The NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to the one or more candidate target NWDAFs. The request message may include instruction information (e.g., a prepared analytics subscription transfer instruction) within the request message. The one or more candidate target NWDAFs (e.g., NWDAF-Y and NWDAF-Z) may start data collection from network functions (NFs) or operations, administration, and maintenance (OAM) and may start analytics generation for the indicated analytics subscriptions. The source NWDAF may decide to select a target NWDAF (e.g., NWDAF-Y) from one or more candidate target NWDAFs. The source NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to the selected target NWDAF (e.g., NWDAF-Y) to ask the selected target NWDAF to take over at least one analytics subscription from the source NWDAF. The source NWDAF may cancel prepared analytics subscription transfers to other candidate target NWDAF-Z. If there is a preparation step, the selected target NWDAF can take over at least one analytics subscription from the source NWDAF in a short period of time.

[0057] In step 4, the source NWDAF may determine to initiate an analytics subscription transfer from the source NWDAF to one or more other NWDAFs. The source NWDAF may determine one or more analytics subscriptions to transfer and may determine to perform the analytics subscription transfer (of the one or more determined analytics subscriptions) to the target NWDAF. The source NWDAF may determine one or more analytics subscriptions to be transferred to the target NWDAF based on, for example, the load, capabilities, and processing capabilities of the source NWDAF and / or the target NWDAF.

[0058] In step 5, the source NWDAF may perform NWDAF discovery and select a target NWDAF (e.g., from multiple target / candidate NWDAFs). If the target NWDAF has already been discovered as part of a prepared analysis subscription transfer, NWDAF discovery may be skipped.

[0059] In step 6, the source NWDAF may send a request message (using the Nnwdaf_EventsSubscription_Transfer service operation) to transfer to the target NWDAF one or more analytics subscriptions determined in step 4. The request message may include / identify / specify the analytics subscriptions being transferred and may include the notification URI and / or the notification correlation ID received by the source NWDAF from the analytics consumer in step 1, if not provided during the prepared analytics subscription transfer.

[0060] In step 7 (e.g., an optional step), the target NWDAF may send a response message (e.g., a Nnwdaf_EventsSubscription_Transfer response) to the source NWDAF (e.g., in response to the request message).

[0061] In step 8, the target NWDAF may accept the transfer of at least one analytic subscription (e.g., one or more analytic subscriptions determined in step 4 and / or identified in the request message) from the source DAF to the target DAF. The target NWDAF may take over / receive at least one analytic subscription (e.g., to perform the generation of analytics for consumption by analytics consumers) based on the information received from the source NWDAF. If not already done during the prepared analytic subscription transfer, the target NWDAF may allocate a new subscription correlation ID to the received / transferred analytic subscription.

[0062] In steps 9 and 10, the target NWDAF may inform / notify the analytics consumer about the success of the analytics subscription transfer using a (e.g., Nnwdaf_EventsSubscription_Notify) request message. The new subscription correlation ID assigned / allocated by the target NWDAF, the transferred analysis IDs (e.g., a list of analysis IDs), and the old subscription correlation ID assigned / allocated by the source NWDAF may be provided / included / identified in the (e.g., Nnwdaf_EventsSubscription_Notify) request message. The request message may include a notification correlation ID that allows the analytics consumer to correlate notifications to the initial subscription request made with the source NWDAF in step 1. The analytics consumer may send a response message (e.g., NnwdafEventsSubscriptionNotify response) to the target NWDAF (e.g., in response to the request message).

[0063] In step 11 (e.g., a conditional step), if the Nnwdaf_EventsSubscription_Transfer request received by the target NWDAF in step 6 included an “analytics context identifier,” the target NWDAF may request the “analytics context” by invoking the Nnwdaf_AnalyticsInfo_ContextTransfer service operation.

[0064] In step 12 (e.g., an optional step), if a response message was not sent in step 7, the target NWDAF may confirm the analytics subscription transfer (e.g., confirm acceptance of the analytics subscription transfer) by sending a response message (e.g., Nnwdaf_EventsSubscription_Transfer) to the source NWDAF.

[0065] In step 13, the target NWDAF may derive / generate (e.g., perform analysis or processing) new output analytics based on the new input data (e.g., with respect to the forwarded analytics subscription).

[0066] In steps 14 and 15, the target NWDAF may inform / notify the analytics consumer about the new analytics using a subscription change notification or notification message (e.g., Nnwdaf_EventsSubscription_Notify message).

[0067] In steps 16 and 17, the analytics consumer may modify or delete at least one other analytics subscription at the source NWDAF by sending a request message (e.g., an Nnwdaf_EventsSubscription_Subscribe request or an Nnwdaf_EventsSubscription_Unsubscribe service operation) to the source NWDAF. The analytics consumer may know / recognize which subscriptions are still at the source NWDAF based on the transferred analytics ID. The request message may include the old subscription correlation ID assigned by the source NWDAF and received by the analytics consumer in step 2. The source NWDAF may send a response message (e.g., an Nnwdaf_EventsSubscription_(un)Subscribe response) to the analytics consumer.

[0068] In steps 18 and 19, the analytics consumer may modify or delete one or more of the at least one analytics subscription at the target NWDAF by sending a request message (e.g., Nnwdaf_EventsSubscription_Subscribe or Nnwdaf_EventsSubscription_Unsubscribe service operation). The analytics consumer may determine / know / recognize which subscriptions may be in the target NWDAF based on the transferred analytics ID. The request message may include the new subscription correlation ID assigned by the target NWDAF received by the analytics consumer in step 9. The target NWDAF may send a response message (e.g., Nnwdaf_EventsSubscription_(un)Subscribe response) to the analytics consumer.

[0069] The target NWDAF may include / embed an identification of the transferred analytics in the subscription change notification, which allows the analytics consumer to identify which subscribed analytics have been transferred and which have not, so that the analytics consumer can use a new subscription correlation ID for the transferred analytics subscriptions and the old correlation subscription ID for the analytics subscriptions that remain with the source NWDAF. (Implementation Example 2: All subscribed analyses are forwarded from the source NWDAF to the target NWDAF)

[0070] In step 1, the analytics consumer may send a request message (e.g., an Nnwdaf_EventsSubscription_Subscribe request) to subscribe to at least one analysis (e.g., a type of analysis) from a source NWDAF. The request may include an identification of the analysis to which the analytics consumer is subscribed, a notification uniform resource identifier (URI), and / or a notification correlation ID.

[0071] In step 2, the source NWDAF may assign (e.g., generate, allocate) a subscription correlation ID associated with at least one analytics subscription. The source NWDAF may send a response message (e.g., Nnwdaf_EventsSubscription_SubscribeResponse) to the analytics consumer. The response message may include the subscription correlation ID.

[0072] In step 3 (e.g., an optional step), the source NWDAF may determine to prepare analysis subscription transfers of subscribed analytics to the target NWDAF (e.g., transfer of all analytics subscriptions of subscribed analytics consumers from the source NWDAF) according to a trigger. For example, the trigger may result from the initiation or scheduling of a graceful shutdown. The source NWDAF may discover one or more candidate target NWDAFs (e.g., NWDAF-Y and NWDAF-Z). The NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to one or more candidate target NWDAFs. The request message may include instruction information (e.g., a prepared analytics subscription transfer instruction) within the request message. The one or more candidate target NWDAFs (e.g., NWDAF-Y and NWDAF-Z) may start data collection from network functions (NFs) or operations, administration, and maintenance (OAM) and may start analytics generation for the indicated analytics subscriptions. The source NWDAF may decide to select a target NWDAF (e.g., NWDAF-Y) from one or more candidate target NWDAFs. The source NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to the selected target NWDAF (e.g., NWDAF-Y) to ask the selected target NWDAF to take over at least one analytics subscription from the source NWDAF. The source NWDAF may cancel prepared analytics subscription transfers to other candidate target NWDAF-Z. If there is a preparation step, the selected target NWDAF can take over at least one analytics subscription from the source NWDAF in a short period of time.

[0073] In step 4, the source NWDAF may determine to initiate analytic subscription transfers from the source NWDAF to one or more other NWDAFs. The source NWDAF may determine all analytic subscriptions to transfer and may determine to perform the analytic subscription transfers (of all determined analytic subscriptions) to the target NWDAF. The source NWDAF may determine that all analytic subscriptions should be transferred to the target NWDAF based on, for example, the load, capabilities, and processing capabilities of the source NWDAF and / or the target NWDAF.

[0074] In step 5, the source NWDAF may perform NWDAF discovery and select a target NWDAF (e.g., from multiple target / candidate NWDAFs). If the target NWDAF has already been discovered as part of a prepared analysis subscription transfer, NWDAF discovery may be skipped.

[0075] In step 6, the source NWDAF may send a request message (using the Nnwdaf_EventsSubscription_Transfer service operation) to transfer all analytic subscriptions determined in step 4 to the target NWDAF. The request message may include / identify / specify the analytic subscriptions being transferred and may include the notification URI and / or notification correlation ID received by the source NWDAF from the analytic consumer in step 1, if not provided during the prepared analytic subscription transfer.

[0076] In step 7 (e.g., an optional step), the target NWDAF may send a response message (e.g., a Nnwdaf_EventsSubscription_Transfer response) to the source NWDAF (e.g., in response to the request message).

[0077] In step 8, the target NWDAF may accept the transfer of all analytic subscriptions (e.g., all analytic subscriptions determined in step 4 and / or identified in the request message) from the source DAF to the target DAF. The target NWDAF may take over / receive analytic subscriptions (e.g., to perform generation of analytics for consumption by analytics consumers) based on the information received from the source NWDAF. If not already done during the prepared analytic subscription transfer, the target NWDAF may allocate new subscription correlation IDs to the received / transferred analytic subscriptions.

[0078] In steps 9 and 10, the target NWDAF may inform / notify the analytics consumer about the success of the analytics subscription transfer using a (e.g., Nnwdaf_EventsSubscription_Notify) request message. The new subscription correlation ID assigned / allocated by the target NWDAF, the transferred analysis IDs (e.g., a list of analysis IDs), and the old subscription correlation ID assigned / allocated by the source NWDAF may be provided / included / identified in the (e.g., Nnwdaf_EventsSubscription_Notify) request message. The request message may also include a notification correlation ID that allows the analytics consumer to correlate notifications to the initial subscription request made with the source NWDAF in step 1. The analytics consumer may send a response message (e.g., NnwdafEventsSubscriptionNotify response) to the target NWDAF (e.g., in response to the request message).

[0079] In step 11 (e.g., a conditional step), if the Nnwdaf_EventsSubscription_Transfer request received by the target NWDAF in step 6 included an “analytics context identifier,” the target NWDAF may request the “analytics context” by invoking the Nnwdaf_AnalyticsInfo_ContextTransfer service operation.

[0080] In step 12 (e.g., an optional step), if a response message was not sent in step 7, the target NWDAF may confirm the analytics subscription transfer (e.g., confirm acceptance of the analytics subscription transfer) by sending a response message (e.g., Nnwdaf_EventsSubscription_Transfer) to the source NWDAF.

[0081] In step 13, the target NWDAF may derive / generate (e.g., perform analysis or processing) new output analytics (corresponding to the forwarded analytics subscriptions) based on the new input data.

[0082] In steps 14 and 15, the target NWDAF may inform / notify the analytics consumer about the new analytics using a subscription change notification or notification message (e.g., Nnwdaf_EventsSubscription_Notify message).

[0083] In steps 16 and 17, the analytics consumer may modify or delete (using the analytics ID) one or more of the analytics subscriptions transferred to the target NWDAF by sending a request message (e.g., Nnwdaf_EventsSubscription_Subscribe or Nnwdaf_EventsSubscription_Unsubscribe service operation). The analytics consumer may know / recognize which subscriptions the target NWDAF has based on the transferred analytics ID. The request message may include the new subscription correlation ID assigned by the target NWDAF received by the analytics consumer in step 9. The target NWDAF may send a response message (e.g., Nnwdaf_EventsSubscription_(un)Subscribe response) to the analytics consumer.

[0084] The target NWDAF may include an identification of the transferred analytics in the subscription change notification, which allows the analytics consumer to identify which subscribed analytics have been transferred and which have not, so that the analytics consumer can use the new subscription correlation ID for the transferred analytics subscriptions and the old correlation subscription ID for the analytics subscriptions that remain / are maintained / retained in the source NWDAF.

[0085] All subscribed analytics may be forwarded from the source NWDAF to the target NWDAF. The source NWDAF may not indicate to the target NWDAF that all analytics subscriptions have been forwarded to the target NWDAF in the request message. Thus, the target NWDAF may not know whether all or some of the analytics subscribed to by the source NWDAF have been forwarded. Therefore, to allow the target NWDAF to accurately associate new subscription correlation IDs with the forwarded subscriptions, the target NWDAF may simply / always include a list of the subscriptions being forwarded, along with the new corresponding subscription correlation IDs, whenever it receives a forwarding. That is, from the target NWDAF's perspective, the newly added identification of the forwarded subscriptions may be mandatory for reporting to analytics consumers. (Implementation example 3: Subscribed analytics are forwarded to different target NWDAFs)

[0086] In step 1, an analytics consumer may send a request message (e.g., an Nnwdaf_EventsSubscription_Subscribe request) to subscribe to at least one (e.g., type of) analysis (e.g., subscriptions for analysis IDs 1, 2, and 3) from a source NWDAF. The request may include the analysis to which the analytics consumer is subscribed, a notification uniform resource identifier (URI), and / or a notification correlation ID.

[0087] In step 2, the source NWDAF may assign (e.g., generate, allocate) a subscription correlation ID associated with at least one analytics subscription (e.g., analytics subscription IDs 1, 2, and 3). The source NWDAF may send a response message (e.g., Nnwdaf_EventsSubscription_SubscribeResponse) to the analytics consumer. The response message may include the subscription correlation ID.

[0088] In some embodiments, a preparation step (not shown in FIG. 7) may be performed. The source NWDAF may decide to perform the preparation step. In the preparation step, the source NWDAF may discover one or more candidate target NWDAFs (e.g., NWDAF-Y and NWDAF-Z). The NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to one or more candidate target NWDAFs. The request message may include instruction information (e.g., a prepared analytics subscription transfer instruction) within the request message. The one or more candidate target NWDAFs (e.g., NWDAF-Y and NWDAF-Z) may initiate data collection from the network functions (NFs) or operations, administration, and maintenance (OAM) and may initiate analytics generation for the indicated analytics subscriptions. The source NWDAF may decide to select a target NWDAF (e.g., NWDAF-Y) from the one or more candidate target NWDAFs. The source NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to the selected target NWDAF (e.g., NWDAF-Y) to ask the selected target NWDAF to take over at least one analytics subscription from the source NWDAF. The source NWDAF may cancel prepared analytics subscription transfers to other candidate target NWDAF-Z. If there is a preparation step, the selected target NWDAF may take over at least one analytics subscription from the source NWDAF in a short period of time.

[0089] In step 3, based on an external trigger and / or an internal trigger, the source NWDAF may determine to initiate an analytics subscription transfer from the source NWDAF to one or more other NWDAFs. The source NWDAF may determine one or more of the at least one analytics subscription to transfer (e.g., analytics subscription IDs 1 and 2) and may determine to perform an analytics subscription transfer (of the one or more determined analytics subscriptions) to one or more target NWDAFs. The source NWDAF may determine one or more analytics subscriptions to be transferred to one or more target NWDAFs based on, for example, the load, capabilities, and processing capabilities of the source NWDAF and / or one or more target NWDAFs.

[0090] In step 4, the source NWDAF may perform NWDAF discovery and select one or more target NWDAFs (e.g., from multiple target / candidate NWDAFs). For example, the source NWDAF may select target NWDAF1 and target NWDAF2 to which to transfer subscriptions with analysis subscription ID1 and analysis subscription ID2, respectively.

[0091] In step 5, the source NWDAF may send a request message (using the Nnwdaf_EventsSubscription_Transfer service operation) to transfer analytics subscription ID1 to target NWDAF1. The request message may include / identify / specify the analytics subscription being transferred (e.g., ID1), the notification URI, and / or the notification correlation ID received by the source NWDAF from the analytics consumer in step 1.

[0092] In step 6, the target NWDAF1 may send a response message (e.g., Nnwdaf_EventsSubscription_Transfer response) to the source NWDAF (e.g., in response to the request message).

[0093] In step 7, the source NWDAF may send a request message (using the Nnwdaf_EventsSubscription_Transfer service operation) to transfer the analytics subscription (e.g., ID2) to the target NWDAF2. The request message may include / identify / specify the analytics subscription (e.g., ID2) being transferred, the notification URI, and / or the notification correlation ID received by the source NWDAF from the analytics consumer in step 1.

[0094] In step 8, the target NWDAF2 may send a response message (e.g., Nnwdaf_EventsSubscription_Transfer response) to the source NWDAF (e.g., in response to the request message).

[0095] In step 9, the target NWDAF1 may accept the transfer of at least one analytics subscription (e.g., analytics subscription ID1) from the source NWDAF to the target NWDAF1. The target NWDAF1 may take over / receive at least one analytics subscription (e.g., to perform analytics generation for consumption by analytics consumers) based on information received from the source NWDAF. The target NWDAF1 may assign a new subscription correlation ID (e.g., subscription correlation ID1) to the received / transferred analytics subscription.

[0096] In steps 10 and 11, the target NWDAF1 may inform / notify the analytics consumer about the success of the analytics subscription transfer using a request message (e.g., Nnwdaf_EventsSubscription_Notify). The new subscription correlation ID assigned / allocated by the target NWDAF1, the transferred analytics ID (e.g., analytics subscription ID1), and the old subscription correlation ID assigned / allocated by the source NWDAF may be provided / included / identified in the request message (e.g., Nnwdaf_EventsSubscription_Notify). The request message may also include a notification correlation ID that allows the analytics consumer to correlate the notification to the initial subscription request made with the source NWDAF in step 1. The analytics consumer may send a response message (e.g., NnwdafEventsSubscriptionNotify response) to the target NWDAF1 (e.g., in response to the request message).

[0097] In step 12, the target NWDAF2 may accept the transfer of at least one analytics subscription (e.g., analytics subscription ID2) from the source NWDAF to the target NWDAF2. The target NWDAF2 may take over / receive at least one analytics subscription (e.g., to perform analytics generation for consumption by analytics consumers) based on information received from the source NWDAF. The target NWDAF2 may assign a new subscription correlation ID (e.g., subscription correlation ID2) to the received / transferred analytics subscription.

[0098] In steps 13 and 14, the target NWDAF2 may inform / notify the analytics consumer about the success of the analytics subscription transfer using a request message (e.g., Nnwdaf_EventsSubscription_Notify). The new subscription correlation ID assigned / allocated by the target NWDAF2, the transferred analytics ID (e.g., analytics subscription ID2), and the old subscription correlation ID assigned / allocated by the source NWDAF may be provided / included / identified in the request message (e.g., Nnwdaf_EventsSubscription_Notify). The request message may also include a notification correlation ID that allows the analytics consumer to correlate notifications to the initial subscription request made with the source NWDAF in step 1. The analytics consumer may send a response message (e.g., NnwdafEventsSubscriptionNotify response) to the target NWDAF2 (e.g., in response to the request message).

[0099] In steps 15 and 16, the analytics consumer may modify or delete the analytics subscription (e.g., ID3) at the source NWDAF by sending a request message (e.g., Nnwdaf_EventsSubscription_Subscribe request or Nnwdaf_EventsSubscription_Unsubscribe service operation). The analytics consumer may know / recognize which subscriptions may still be in the source NWDAF based on the analytics IDs received in steps 10 and 11 and steps 13 and 14. The request message may include the old subscription correlation ID assigned by the source NWDAF received by the analytics consumer in step 2. The source NWDAF may send a response message (e.g., Nnwdaf_EventsSubscription_(un)Subscribe response) to the analytics consumer.

[0100] In steps 17 and 18, the analytics consumer may modify or delete an analytics subscription (e.g., ID1) at the target NWDAF1 by sending a request message (e.g., Nnwdaf_EventsSubscription_Subscribe or Nnwdaf_EventsSubscription_Unsubscribe service operation). The analytics consumer may know / recognize which subscriptions the target NWDAF1 may have based on the analytics subscription IDs received in steps 10 and 11. The request message may include the new subscription correlation ID assigned by the target NWDAF1 received by the analytics consumer in step 10. The target NWDAF1 may send a response message (e.g., Nnwdaf_EventsSubscription_(un)Subscribe response) to the analytics consumer.

[0101] In steps 19 and 20, the analytics consumer may modify or delete an analytics subscription (e.g., ID2) at the target NWDAF2 by sending a request message (e.g., Nnwdaf_EventsSubscription_Subscribe or Nnwdaf_EventsSubscription_Unsubscribe service operation). The analytics consumer may know / recognize which subscriptions may be in the target NWDAF2 based on the analytics subscription IDs received in steps 13 and 14. The request message may include the new subscription correlation ID assigned by the target NWDAF2 received by the analytics consumer in step 13. The target NWDAF2 may send a response message (e.g., Nnwdaf_EventsSubscription_(un)Subscribe response) to the analytics consumer.

[0102] Target NWDAF1 and target NWDAF2 may include an identification of the transferred analytics in the subscription change notification, which allows the analytics consumer to identify which subscribed analytics have been transferred and which have not, so that the analytics consumer can use a new subscription correlation ID for the transferred analytics subscriptions and the old correlation subscription ID for the analytics subscriptions that remain with the source NWDAF. (Implementation Example 4: The forwarded analysis is further forwarded from the target NWDAF to another NWDAF)

[0103] In step 1, an analytics consumer may send a request message (e.g., an Nnwdaf_EventsSubscription_Subscribe request) to subscribe to at least one (e.g., type) analysis (e.g., analysis subscription IDs 1, 2, and 3) from a source NWDAF. The request may include the analysis to which the analytics consumer is subscribed, a notification uniform resource identifier (URI), and / or a notification correlation ID.

[0104] In step 2, the source NWDAF may assign (e.g., generate and allocate) a subscription correlation ID associated with at least one analytics subscription (e.g., analytics subscription IDs 1, 2, and 3). The source NWDAF may send a response message (e.g., Nnwdaf_EventsSubscription_SubscribeResponse) to the analytics consumer. The response message may include the subscription correlation ID.

[0105] In some embodiments, a preparation step (not shown in FIG. 8) may be performed. The source NWDAF may decide to perform the preparation step. In the preparation step, the source NWDAF may discover one or more candidate target NWDAFs (e.g., NWDAF-Y and NWDAF-Z). The NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to one or more candidate target NWDAFs. The request message may include instruction information (e.g., a prepared analytics subscription transfer instruction) within the request message. The one or more candidate target NWDAFs (e.g., NWDAF-Y and NWDAF-Z) may initiate data collection from the network functions (NFs) or operations, administration, and maintenance (OAM) and may initiate analytics generation for the indicated analytics subscriptions. The source NWDAF may decide to select a target NWDAF (e.g., NWDAF-Y) from the one or more candidate target NWDAFs. The source NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to the selected target NWDAF (e.g., NWDAF-Y) to ask the selected target NWDAF to take over at least one analytics subscription from the source NWDAF. The source NWDAF may cancel prepared analytics subscription transfers to other candidate target NWDAF-Z. If there is a preparation step, the selected target NWDAF may take over at least one analytics subscription from the source NWDAF in a short period of time.

[0106] In step 3, based on an external trigger and / or an internal trigger, the source NWDAF may determine to initiate an analytics subscription transfer from the source NWDAF to one or more other NWDAFs. The source NWDAF may determine one or more of the at least one analytics subscription to transfer (e.g., analytics subscription IDs 1 and 2) and may determine to perform an analytics subscription transfer (of the one or more determined analytics subscriptions) to the target NWDAF. The source NWDAF may determine one or more analytics subscriptions to be transferred to the target NWDAF based on, for example, the load, capabilities, and processing capabilities of the source NWDAF and / or the target NWDAF.

[0107] In step 4, the source NWDAF may perform NWDAF discovery and select a target NWDAF-A (e.g., from multiple target / candidate NWDAFs). For example, the source NWDAF may select a target NWDAF-A for the analysis ID1 subscription and the analysis ID2 subscription.

[0108] In step 5, the source NWDAF may send a request message (using the Nnwdaf_EventsSubscription_Transfer service operation) to transfer the analytics subscriptions (e.g., ID1 and ID2) to the target NWDAF-A. The request message may include / identify / specify the analytics subscriptions ID1 and ID2 being transferred, the notification URI, and / or the notification correlation ID received by the source NWDAF from the analytics consumer in step 1.

[0109] In step 6, the target NWDAF-A may send a response message (e.g., Nnwdaf_EventsSubscription_Transfer response) to the source NWDAF (e.g., in response to the request message).

[0110] In step 7, the target NWDAF-A may accept the transfer of at least one analytics subscription (e.g., analytics subscription IDs 1 and 2) from the source NWDAF to the target NWDAF-A. The target NWDAF-A may take over / receive at least one analytics subscription (e.g., to perform analytics generation for consumption by analytics consumers) based on the information received from the source NWDAF. The target NWDAF-A may assign a new subscription correlation ID (e.g., subscription correlation ID 1) to the received / transferred analytics subscription.

[0111] In steps 8 and 9, the target NWDAF-A may inform / notify the analytics consumer about the success of the analytics subscription transfer using a request message (e.g., Nnwdaf_EventsSubscription_Notify). The new subscription correlation ID assigned / allocated by the target NWDAF-A, the transferred analytics IDs (e.g., a list of analytics subscription IDs including IDs 1 and 2), and the old subscription correlation ID assigned / allocated by the source NWDAF may be provided / included / identified in the request message (e.g., Nnwdaf_EventsSubscription_Notify). The request message may also include a notification correlation ID that allows the analytics consumer to correlate the notification to the initial subscription request made with the source NWDAF in step 1. The analytics consumer may send a response message (e.g., NnwdafEventsSubscriptionNotify response) to the target NWDAF-A (e.g., in response to the request message).

[0112] In some embodiments, a preparation step (not shown in FIG. 8) may be performed. The target NWDAF may decide to perform the preparation step. In the preparation step, the target NWDAF may discover one or more candidate target NWDAFs (e.g., NWDAF-E and NWDAF-F). The NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to one or more candidate target NWDAFs. The request message may include instruction information (e.g., a prepared analytics subscription transfer instruction) within the request message. The one or more candidate target NWDAFs (e.g., NWDAF-E and NWDAF-F) may initiate data collection from network functions (NFs) or operations, administration, and maintenance (OAM) and may initiate analytics generation for the indicated analytics subscriptions. The target NWDAF may decide to select a target NWDAF (e.g., NWDAF-E) from the one or more candidate target NWDAFs. The target NWDAF may send a request message (e.g., Nnwdaf_EventsSubscription_Transfer) to the selected target NWDAF (e.g., NWDAF-E) to ask the selected target NWDAF to take over at least one analytics subscription from the target NWDAF. The target NWDAF may cancel prepared analytics subscription transfers to other candidate target NWDAF-Fs. If there is a preparation step, the selected target NWDAF can take over at least one analytics subscription from the target NWDAF in a short period of time.

[0113] In step 10, based on an external trigger and / or an internal trigger, the target NWDAF-A may determine to initiate an analytics subscription transfer from the target NWDAF-A to another target NWDAF. The target NWDAF-A may determine one or more analytics subscriptions (e.g., analytics subscription ID 2) to transfer among at least one analytics subscription (e.g., analytics subscription ID 1 and 2) being transferred to the target NWDAF-A and may determine to perform an analytics subscription transfer (of the one or more determined analytics subscriptions) to another target NWDAF. The target NWDAF-A may determine one or more analytics subscriptions to be transferred to the target NWDAF-B based on, for example, the load, capabilities, and processing capabilities of the source NWDAF, the target NWDAF-A, and / or the target NWDAF-B.

[0114] In step 11, target NWDAF-A may perform NWDAF discovery and select target NWDAF-B (e.g., from multiple target / candidate NWDAFs). For example, target NWDAF-A may select target NWDAF-B for analysis subscription ID2.

[0115] In step 12, the target NWDAF-A may send a request message (using the Nnwdaf_EventsSubscription_Transfer service operation) to transfer the analytics subscription (with ID2) to the target NWDAF-B. The request message may include / identify / specify the analytics subscription (with ID2) being transferred, the notification URI, and / or the notification correlation ID received by the source NWDAF from the analytics consumer in step 1.

[0116] In step 13, the target NWDAF-B may send a response message (e.g., Nnwdaf_EventsSubscription_Transfer response) to the target NWDAF-A (e.g., in response to the request message).

[0117] In step 14, the target NWDAF-B may accept the transfer of at least one analytics subscription (e.g., analytics subscription ID2) from the target NWDAF-A to the target NWDAF-B. The target NWDAF-B may take over / receive at least one analytics subscription (e.g., to perform analytics generation for consumption by analytics consumers) based on the information received from the target NWDAF-A. The target NWDAF-B may assign a new subscription correlation ID (e.g., subscription correlation ID2) to the received / transferred analytics subscription.

[0118] In steps 15 and 16, the target NWDAF-B may inform / notify the analytics consumer about the success of the analytics subscription transfer using a request message (e.g., Nnwdaf_EventsSubscription_Notify). The new subscription correlation ID assigned / allocated by the target NWDAF-B, the transferred analytics ID (e.g., analytics subscription ID2), and the old subscription correlation ID assigned / allocated by the source NWDAF may be provided / included / identified in the request message (e.g., Nnwdaf_EventsSubscription_Notify). The request message may also include a notification correlation ID that allows the analytics consumer to correlate the notification to the initial subscription request made with the source NWDAF in step 1. The analytics consumer may send a response message (e.g., NnwdafEventsSubscriptionNotify response) to the target NWDAF-B (e.g., in response to the request message).

[0119] In steps 17 and 18, the analytics consumer may modify or delete the analytics subscription (having ID 3) at the source NWDAF by sending a request message (e.g., an Nnwdaf_EventsSubscription_Subscribe request or an Nnwdaf_EventsSubscription_Unsubscribe service operation). The analytics consumer may know / recognize which subscriptions may still be in the source NWDAF based on the list of analytics subscription IDs received in steps 8 and 9. The request message may include the old subscription correlation ID assigned by the source NWDAF received by the analytics consumer in step 2. The source NWDAF may send a response message (e.g., an Nnwdaf_EventsSubscription_(un)Subscribe response) to the analytics consumer.

[0120] In steps 19 and 20, the analytics consumer may modify or delete the analytics subscription (ID1) at the target NWDAF-A by sending a request message (e.g., Nnwdaf_EventsSubscription_Subscribe or Nnwdaf_EventsSubscription_Unsubscribe service operation). The analytics consumer may know / recognize which subscriptions the target NWDAF-A may have based on the list of analytics subscription IDs received in steps 8 and 9 and the analytics subscription IDs received in steps 15 and 16. The request message may include the new subscription correlation ID assigned by the target NWDAF-A received by the analytics consumer in step 8. The target NWDAF-A may send a response message (e.g., Nnwdaf_EventsSubscription_(un)subscribe response) to the analytics consumer.

[0121] In steps 21 and 22, the analytics consumer may modify or delete the analytics subscription (having ID2) at the target NWDAF-B by sending a request message (e.g., Nnwdaf_EventsSubscription_Subscribe or Nnwdaf_EventsSubscription_Unsubscribe service operation). The analytics consumer may know / recognize which subscriptions the target NWDAF-B may have based on the list of analytics subscription IDs received in steps 8 and 9 and the analytics subscription IDs received in steps 15 and 16. The request message may include the new subscription correlation ID assigned by the target NWDAF-B received by the analytics consumer in step 15. The target NWDAF-B may send a response message (e.g., Nnwdaf_EventsSubscription_(un)subscribe response) to the analytics consumer.

[0122] The target NWDAF-A and target NWDAF-B may include / embed an identification of the transferred analytics in the subscription change notification, which allows the analytics consumer to identify which subscribed analytics have been transferred and which have not, so that the analytics consumer can use the new subscription correlation ID for the transferred analytics subscriptions and the old correlation subscription ID for the analytics subscriptions that remain with the source NWDAF.

[0123] It should be understood that one or more features from the above implementation examples are not limited to a particular implementation example and can be combined in any aspect (e.g., in any priority and / or order, simultaneously or otherwise).

[0124] FIG. 9 illustrates a flow diagram for providing at least one analysis identifier (ID) in a subscription change notification according to an embodiment of the present disclosure. Method 900 may be implemented using any one or more of the components and devices detailed herein in connection with FIGS. 1-2. In summary, method 900 may be performed by a targeted data analysis function (DAF) in some embodiments. Depending on the embodiment, additional, fewer, or different operations may be performed in method 900. At least one aspect of the operations relates to a system, method, apparatus, or computer-readable medium.

[0125] A target data analysis function (DAF) (e.g., a network data analysis function (NWDAF)) may accept the transfer of at least one analytic subscription from a source DAF to the target DAF. The at least one analytic subscription may be associated with a new subscription correlation identifier (ID) (e.g., allocated / assigned by the target NWDAF). The target DAF may send a notification message (e.g., an Nnwdaf_EventsSubscription_Notify request message) to the analytics consumer. The target DAF may include the new subscription correlation ID and an identification of the at least one analytic subscription being transferred. The identification of the at least one analytic subscription may include at least one of an ID number, a name, a group number, a table index, or an item number. The notification message may further include at least one of an old subscription correlation ID associated with the source DAF (e.g., allocated / assigned by the source DAF) or a notification correlation ID.

[0126] In some embodiments, the analytics consumer may determine to modify or delete at least one other analytics subscription (e.g., those analytics subscriptions remaining with the source NWDAF) according to the identification of the at least one analytics subscription. The analytics consumer may send a request to the source NWDAF to modify or delete the at least one other analytics subscription.

[0127] In some embodiments, the analytics consumer may decide to modify or delete one or more of the at least one analytics subscriptions (e.g., those analytics subscriptions transferred to the target NWDAF) according to the identification of the at least one analytics subscription. The analytics consumer may send a request to the target DAF to modify or delete one or more of the at least one analytics subscription. In some embodiments, the at least one analytics subscription may consist of all analytics subscriptions subscribed to by the analytics consumer from the source DAF.

[0128] In some embodiments, the second target DAF may accept the transfer of at least one other analytical subscription from the source DAF to the second target DAF. The at least one other analytical subscription may be associated with a second new subscription correlation identifier (ID). The second target DAF may send a second notification message to the analytical consumer. The second notification message may include the second new subscription correlation ID and an identification of the at least one other analytical subscription. The analytical consumer may decide to modify or delete the at least one other analytical subscription according to the identification of the at least one analytical subscription. The analytical consumer may send a request to the second target DAF to modify or delete the at least one other analytical subscription.

[0129] In some embodiments, the second target DAF may accept the transfer of one or more analytical subscriptions of at least one analytical subscription from the target DAF to the second target DAF. The one or more analytical subscriptions may be associated with a second new subscription correlation identifier (ID). The second target DAF may send a second notification message to the analytical consumer. The second notification message may include the second new subscription correlation ID and identification of the one or more analytical subscriptions. The analytical consumer may decide to modify or delete one or more analytical subscriptions according to the identification of the one or more analytical subscriptions. The analytical consumer may send a request to the second target DAF to modify or delete one or more analytical subscriptions.

[0130] In some embodiments, the analytics consumer may decide to modify or delete at least one analytics subscription remaining with the source DAF according to the identification of the at least one analytics subscription, and may send a request to the source DAF to modify or delete at least one analytics subscription remaining with the source DAF.

[0131] In some embodiments, the analytics consumer may determine to modify or delete at least one analytics subscription remaining with the target DAF according to the identification of at least one analytics subscription (e.g., identifying one transferred to the target DAF) and the identification of one or more analytics subscriptions (e.g., identifying those transferred to a second target DAF). The analytics consumer may send a request to the target DAF to modify or delete at least one analytics subscription remaining with the target DAF.

[0132] In some embodiments, an analytics consumer may receive a notification message (e.g., a Nnwdaf_EventsSubscription_Notify request message) from a target data analytics function (DAF). The notification message may include (i) a new subscription correlation identifier (ID) associated with at least one analytics subscription being transferred from the source DAF to the target DAF, and (ii) an identification of the at least one analytics subscription.

[0133] While various embodiments of the present solution have been described above, it should be understood that they are presented by way of example only, and not by way of limitation. Similarly, various diagrams may depict example architectures or configurations provided to enable those skilled in the art to understand example features and functionality of the present solution. However, as such skilled in the art will appreciate, the solution is not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. Furthermore, as will be appreciated by those skilled in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the example embodiments described above.

[0134] It is also understood that any reference to an element herein using a designation such as "first," "second," etc., does not generally limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to a first and a second element does not imply that only two elements may be used or that the first element must precede the second element in any way.

[0135] Additionally, those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, and symbols that may be referred to in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0136] Those skilled in the art will further recognize that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of the two), firmware, various forms of programs or design code incorporating instructions (which may be referred to herein for convenience as “software” or “software modules”), or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these techniques, depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functions in various ways for each particular application, and such implementation decisions do not depart from the scope of the present disclosure.

[0137] Furthermore, those skilled in the art will understand that the various example logic blocks, modules, devices, components, and circuits described herein can be implemented in or performed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may further include an antenna and / or transceiver for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other suitable configuration for performing the functions described herein.

[0138] If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any medium that can enable a computer program or code to be transferred from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0139] As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purposes of explanation, various modules are described as individual modules, but as will be apparent to one skilled in the art, two or more modules may be combined to form a single module that performs associated functions according to embodiments of the present solution.

[0140] Additionally, memory or other storage devices and communication components may be used in embodiments of the solution. For clarity, it will be appreciated that the above description describes embodiments of the solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without detracting from the solution. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units do not indicate a strict logical or physical structure or organization, but merely to suitable means for providing the described functionality.

[0141] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. 1. A method, comprising: A target data analysis function (DAF) receives, from a source DAF, a request message to transfer a complete set of analysis subscriptions from the source DAF to the target DAF; the target DAF sending a notification message to an analysis consumer; Including, The method, wherein the communication message includes (i) a new subscription correlation identifier (ID), (ii) an identification of a portion of the complete set of analytical subscriptions to be transferred, and (iii) an old subscription correlation ID associated with the source DAF, wherein the new subscription correlation ID is associated with the portion of the complete set of analytical subscriptions, and the identification of the portion of the complete set of analytical subscriptions includes a list of analytical subscription IDs.

2. The method of claim 1 , wherein the notification message further includes a notification correlation ID.

3. 1. A method, the method comprising: an analytics consumer receiving a notification message from a target data analytics function (DAF); The method, wherein the notification message includes (i) a new subscription correlation identifier (ID), (ii) an identification of a portion of the complete set of analytical subscriptions to be transferred from the source DAF to the target DAF, and (iii) an old subscription correlation ID associated with the source DAF, wherein the new subscription correlation ID is associated with the portion of the complete set of analytical subscriptions, and the identification of the portion of the complete set of analytical subscriptions includes a list of analytical subscription IDs.

4. The method of claim 3 , wherein the notification message further includes a notification correlation ID.

5. A target data analysis function (DAF), comprising: the target DAF comprises at least one processor; The at least one processor receiving, via a transceiver, from a source DAF, a request message to transfer a complete set of analysis subscriptions from said source DAF to said target DAF; sending a notification message to an analytics consumer via said transceiver; and The communication message includes (i) a new subscription correlation identifier (ID), (ii) an identification of a portion of the complete set of analytical subscriptions to be transferred, and (iii) an old subscription correlation ID associated with the source DAF, wherein the new subscription correlation ID is associated with the portion of the complete set of analytical subscriptions, and the identification of the portion of the complete set of analytical subscriptions includes a list of analytical subscription IDs.

6. The target DAF of claim 5 , wherein the notification message further includes a notification correlation ID.

7. an analytics consumer, the analytics consumer comprises at least one processor; the at least one processor is configured to receive, via a receiver, a notification message from a target data analysis function (DAF); The notification message includes (i) a new subscription correlation identifier (ID), (ii) an identification of a portion of the complete set of analytical subscriptions to be transferred from the source DAF to the target DAF, and (iii) an old subscription correlation ID associated with the source DAF, wherein the new subscription correlation ID is associated with the portion of the complete set of analytical subscriptions, and the identification of the portion of the complete set of analytical subscriptions includes a list of analytical subscription IDs.

8. The analytics consumer of claim 7 , wherein the notification message further includes a notification correlation ID.

9. 10. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, are capable of causing the one or more processors to perform the method of claim 1.

10. 10. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, are capable of causing the one or more processors to perform the method of claim 2.

11. 4. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, are capable of causing the one or more processors to perform the method of claim 3.

12. 5. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, are capable of causing the one or more processors to perform the method of claim 4.

Images