Method and apparatus for subscription and notification

Abstract

The embodiment of the invention provides a subscription and notification method and device. The method performed by the first NF includes receiving, from a third NF, a first notification message or a first desubscription response including notification data to be processed. The first notification message can also comprise second information for indicating the notification reason of the notification data to be processed.

Description

TECHNICAL FIELD

[0001] The non-limiting and exemplary embodiments of the present disclosure generally relate to the field of communication technology, and in particular to methods and apparatuses for subscription and notification. BACKGROUND

[0002] This section introduces aspects that can be helpful in further understanding the present disclosure. Thus, the statements of this section are to be read in this light and not as admissions of what is in or what is not in the prior art.

[0003] In networks, network capability exposure can be required in various scenarios. For example, network capability exposure can include exposing network events to external and to core network functions (NFs), exposing provisioning capabilities to external functions, exposing policy and charging capabilities to external functions, exposing core network internal capabilities for analytics, exposing analytics to external parties, network data analytics functions retrieving data from external parties, exposing the number of registered user equipment (UEs) and / or established protocol data unit (PDU) sessions for network slices subject to network slice admission control to core network NFs or external parties, etc.

[0004] A subscription-notification mechanism can be used for network capability exposure. For example, the subscription-notification mechanism is described in various 3GPP (Third Generation Partnership Project) specifications, such as 3GPP TS 23.501 V18.0.0, 3GPP TS 23.502 V18.0.0, 3GPP TS 23.288 V18.0.0, 3GPP TR 23.700-81 V18.0.0, the disclosures of which are incorporated by reference in their entireties.

[0005] When subscribing to event reporting, the event consumer NF can provide, for example, one or more event identifiers (IDs), event filter information, event reporting information, a target of event reporting, a notification target address (+ notification correlation ID) that allows the event receiving NF to associate the notification received from the event provider with this subscription, an expiration time (until which time the subscription is expected to remain active) representing a time, etc.

[0006] When the event provider NF accepts the subscription, the event consumer NF can receive an event notification message from the event provider NF.

[0007] For example, a NWDAF (Network Data Analytics Function) can provide a Nnwdaf_AnalyticsSubscription service that can support an analytics consumer NF to include analytics parameters encompassing event report information in a subscription of one or more analytics events to request the NWDAF to process one or more corresponding analytics events and to notify the analytics event based on the required triggering condition.

[0008] For example, a NWDAF, a DCCF (Data Collection Coordination) and an ADRF (Analytics Data Repository Function) support data management subscriptions for notifications and can include processing instructions in the subscription request.

[0009] Table 1 shows an example of event report information, which is identical to Table 4.15.1-1 of 3GPP TS 23.502 V18.0.0, the disclosure of which is incorporated by reference herein in its entirety.

[0010] Table 1: Event report information

[0011] . SUMMARY

[0012] This summary is provided in simplified form to present selected concepts of the disclosure, which are further described below in the detailed description. This summary is neither intended nor is it to be construed as indicating key or essential features of the claimed subject matter nor as limiting the scope of the claimed subject matter.

[0013] There are some problems with the existing subscription-notification mechanism.

[0014] For example, in some scenarios, such as a aggregator NF (e.g., NWDAF), bulk data processing, subscription (e.g., analytics subscription) transfer, or NF (e.g., DCCF) relocation, etc., there can be one or more stored unsent events before the notification triggering condition is met. If an exception occurs, such as, for example, the NF (e.g., NWDAF) can no longer process event data or analytics, the NF (e.g., DCCF) can no longer process the data, a cancel subscription request is received from the event (analytics) consumer NF, or the NF (e.g., NWDAF / DCCF) decides to send a termination request, etc., there can be several problems in, for example, the Nnwdaf_AnalyticsSubscription_Subscribe, Nnwdaf_DataManagement_Subscribe, and / or Ndccf_DataManagement_Subscribe service operations:

[0015] - there is no specification on how to handle one or more pending storage events, e.g., one or more NWDAF pending analytics events or one or more NWDAF / DCCF data management pending data events, when an exception occurs;

[0016] - if the exception case is, for example, a cancel subscription request received from an event consumer NF, the cancel subscription response message provided by the event producer NF cannot support the handling of one or more pending storage event notifications; or

[0017] - the service consumer NF cannot indicate requirements on how to handle such one or more stored unsent events when an exception occurs.

[0018] To overcome or alleviate at least one of the problems described above or other problems, embodiments of the present disclosure propose an improved solution for subscription and notification.

[0019] In a first aspect of the present disclosure, a method performed by a first network function (NF) is provided. The method comprises receiving, from a third NF, a first notification message or a first cancel subscription response comprising pending notification data.

[0020] In embodiments, the first notification message can further comprise second information indicating a notification cause of the pending notification data.

[0021] In embodiments, the first notification message can further comprise information informing the consumer instance when the data or analytics will be deleted.

[0022] In embodiments, the method can further comprise sending, to the third NF, a first notification response message comprising information indicating whether the consumer instance will retrieve the stored data or analytics before deletion.

[0023] In embodiments, the method can further comprise sending, to a second NF, a second notification message or a second cancel subscription response comprising the pending notification data.

[0024] In embodiments, the second notification message can further comprise second information indicating a notification cause of the pending notification data.

[0025] In embodiments, the second notification message can further comprise information informing the consumer instance when the data or analytics will be deleted.

[0026] In embodiments, the method can further comprise receiving, from the second NF, a second notification response message comprising information indicating whether the consumer instance will retrieve the stored data or analytics before deletion.

[0027] In an embodiment, the first NF and / or the second NF can comprise at least one of an analytics data repository function (ADRF), an aggregator NWDAF, a data collection coordination (DCCF), a network data analytics function (NWDAF), a network exposure function (NEF), an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a network slice admission control function (NSACF), an application function (AF), a policy control function (PCF), or a user plane function (UPF).

[0028] In an embodiment, the notification cause of the notification data to be processed can comprise at least one of an exception occurred in the event producer NF, the event producer NF is not able to process analytics, the event producer NF is not able to process event data, the event producer NF received a request to unsubscribe, the event producer NF decided to send a termination request, event data cannot be collected, a subscription is transferred, the DCCF is not able to process analytics data or collected data, or the aggregator NWDAF is not able to process analytics.

[0029] In an embodiment, the notification message can comprise at least one of a data management notification message, an analytics subscription notification message, or an event exposure notification message.

[0030] In an embodiment, the notification message can comprise a termination request.

[0031] In an embodiment, the third NF can comprise at least one of an analytics data repository function (ADRF), an aggregator NWDAF, a data collection coordination (DCCF), a network data analytics function (NWDAF), a network exposure function (NEF), an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a network slice admission control function (NSACF), an application function (AF), a policy control function (PCF), or a user plane function (UPF).

[0032] In a second aspect of the disclosure, a method performed by a second NF is provided. The method can comprise sending, to a first NF, a first notification message or a first unsubscribe response comprising notification data to be processed.

[0033] In an embodiment, the first notification message can further comprise second information indicating a notification cause of the notification data to be processed.

[0034] In an embodiment, the first notification message can further comprise information informing a consumer instance when data or analytics will be deleted.

[0035] In an embodiment, the method can further include receiving, from the first NF, a first notification response message including information indicating whether the consumer instance is to retrieve the stored data or analytics prior to deletion.

[0036] In an embodiment, the first NF can include at least one of an analytics data repository function (ADRF), an aggregator NWDAF, a data collection coordination (DCCF), a network data analytics function (NWDAF), a network exposure function (NEF), an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a network slice admission control function (NSACF), an application function (AF), a policy control function (PCF), or a user plane function (UPF).

[0037] In an embodiment, the notification cause of the notification data to be processed can include at least one of an exception occurring in an event producer NF, the event producer NF being unable to process analytics, the event producer NF being unable to process event data, the event producer NF receiving a request to cancel a subscription, the event producer NF deciding to send a termination request, event data being unable to be collected, a subscription being transferred, a DCCF being unable to process analytics data or collected data, or an aggregator NWDAF being unable to process analytics.

[0038] In an embodiment, the notification message can include at least one of a data management notification message, an analytics subscription notification message, or an event exposure notification message.

[0039] In an embodiment, the notification message can include a termination request.

[0040] In an embodiment, the third NF can include at least one of an analytics data repository function (ADRF), an aggregator NWDAF, a data collection coordination (DCCF), a network data analytics function (NWDAF), a network exposure function (NEF), an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a network slice admission control function (NSACF), an application function (AF), a policy control function (PCF), or a user plane function (UPF).

[0041] In a third aspect of the disclosure, a first NF is provided. The first NF includes a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The first NF is operable to receive, from a third NF, a first notification message including notification data to be processed or a first cancel subscription response. The first notification message can further include second information indicating a notification cause of the notification data to be processed.

[0042] In a fourth aspect of the disclosure, a third NF is provided. The third NF comprises a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The third NF is operable to send, to a first NF, a first notification message or a first unsubscribe response comprising notification data to be processed. The first notification message can further comprise second information indicating a notification cause of the notification data to be processed.

[0043] In a fifth aspect of the disclosure, a first NF is provided. The first NF comprises a first receiving module configured to receive, from a third NF, a first notification message or a first unsubscribe response comprising notification data to be processed. The first notification message can further comprise second information indicating a notification cause of the notification data to be processed.

[0044] In an embodiment, the first NF can further comprise a first sending module configured to send, to the third NF, a first notification response message comprising information indicating whether the consumer instance is to retrieve stored data or analytics before deletion.

[0045] In an embodiment, the first NF can further comprise a second sending module configured to send, to a second NF, a second notification message or a second unsubscribe response comprising notification data to be processed. The second notification message can further comprise second information indicating a notification cause of the notification data to be processed.

[0046] In an embodiment, the first NF can further comprise a second receiving module configured to receive, from the second NF, a second notification response message comprising information indicating whether the consumer instance is to retrieve stored data or analytics before deletion.

[0047] In a sixth aspect of the disclosure, a third NF is provided. The third NF comprises a sending module configured to send, to a first NF, a first notification message or a first unsubscribe response comprising notification data to be processed. The first notification message can further comprise second information indicating a notification cause of the notification data to be processed.

[0048] In an embodiment, the third NF can further comprise a receiving module configured to receive, from the first NF, a first notification response message comprising information indicating whether the consumer instance is to retrieve stored data or analytics before deletion.

[0049] In a seventh aspect of the disclosure, a computer program product comprising instructions which, when executed by at least one processor, cause the at least one processor to carry out the method according to any of the first aspect or the second aspect.

[0050] In an eighth aspect of the disclosure, a computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform a method according to any of the first or second aspects is provided.

[0051] Embodiments herein can provide a number of advantages, the following is a non-exhaustive list of examples of advantages. In some embodiments herein, the pending notification data (e.g. collection event) can avoid losing notifications from NFs (e.g. NWDAF / DCCF) when certain exceptions occur. In some embodiments herein, it supports enhancements for more refined and very accurate analytics processing related (e.g. NWDAF). In some embodiments herein, the pending notification data (e.g. analytics event) can enhance the actions of analytics consumers based on more refined and very accurate analytics outputs related. In some embodiments herein, the added “pending notification flag” in the event reporting information table in clause 4.15.1 of TS 23.502 v18.0.0 and the added usage description can also be commonly used by one or more other NF event open cases that have one or more stored unsent events when exceptions occur, to refine and enhance one or more exception event reporting and alignment processing with exception cases. In some embodiments herein, a flexible pending notification processing is proposed. In some embodiments herein, it can enable event consumer NFs to indicate event producer NF actions on how to handle one or more stored unsent events when exceptions occur. In some embodiments herein, it can enable event producer NFs to effectively handle pending notifications before handling exceptions. In some embodiments herein, it can enable flexible pending notification messaging to minimize processing impact. Embodiments herein are not limited to the above-mentioned features and advantages. Additional features and advantages will be recognized by those skilled in the art upon reading the following detailed description. BRIEF DESCRIPTION OF DRAWINGS

[0052] The above and other aspects, features, and advantages of various embodiments of the present disclosure will be more apparent from example embodiments, as described below, by reference to the accompanying drawings, in which like reference numerals or letters are used to denote like elements throughout. The accompanying drawings are shown to facilitate a fuller understanding of embodiments of the present disclosure and are not necessarily to scale:

[0053] Figure 1a A high level architecture in a fifth generation network according to embodiments of the disclosure is schematically illustrated;

[0054] Figure 1b A data collection architecture using data collection coordination according to embodiments of the disclosure is schematically illustrated;

[0055] Figure 1c An open architecture for network data analytics using data collection coordination is illustratively shown in accordance with an embodiment of the present disclosure;

[0056] Figure 1d A data storage architecture for analyzed and collected data is illustratively shown in accordance with an embodiment of the present disclosure;

[0057] Figure 2a A flow diagram of a first example of a subscription-notification NF service is shown in accordance with an embodiment of the present disclosure;

[0058] Figure 2b A flow diagram of a second example of a subscription-notification NF service is shown in accordance with an embodiment of the present disclosure;

[0059] Figure 2c A flow diagram of a subscription-notification using indirect communication is shown in accordance with an embodiment of the present disclosure;

[0060] Figure 3a A method flow diagram is shown in accordance with an embodiment of the present disclosure;

[0061] Figure 3b A method flow diagram is shown in accordance with another embodiment of the present disclosure;

[0062] Figure 3c A method flow diagram is shown in accordance with another embodiment of the present disclosure;

[0063] Figure 3d A method flow diagram is shown in accordance with another embodiment of the present disclosure;

[0064] Figure 3e A method flow diagram is shown in accordance with another embodiment of the present disclosure;

[0065] Figure 3f A method flow diagram is shown in accordance with another embodiment of the present disclosure;

[0066] Figure 3g A method flow diagram is shown in accordance with another embodiment of the present disclosure;

[0067] Figure 3h A method flow diagram is shown in accordance with another embodiment of the present disclosure;

[0068] Figure 4a A method flow diagram is shown in accordance with another embodiment of the present disclosure;

[0069] Figure 4b A method flow diagram is shown in accordance with another embodiment of the present disclosure;

[0070] Figure 4ca flowchart of a method according to another embodiment of the disclosure is shown;

[0071] Figure 4d a flowchart of a method according to another embodiment of the disclosure is shown;

[0072] Figure 5 a flowchart of a method according to another embodiment of the disclosure is shown;

[0073] Figure 6a a flowchart of a subscription-notification method according to another embodiment of the disclosure is shown;

[0074] Figure 6b a flowchart of a subscription-notification method according to another embodiment of the disclosure is shown;

[0075] Figure 7a a flowchart of a subscription-notification method according to another embodiment of the disclosure is shown;

[0076] Figure 7b a flowchart of a subscription-notification method according to another embodiment of the disclosure is shown;

[0077] Figure 8a a block diagram of an apparatus suitable for practicing some embodiments of the disclosure is shown;

[0078] Figure 8b a block diagram of a first NF according to embodiments of the disclosure is shown;

[0079] Figure 8c a block diagram of a second NF according to embodiments of the disclosure is shown; and

[0080] Figure 8d a block diagram of an event consumer NF according to embodiments of the disclosure is shown;

[0081] Figure 8e a block diagram of a first NF according to another embodiment of the disclosure is shown; and

[0082] Figure 8f a block diagram of a third NF according to another embodiment of the disclosure is shown. DETAILED DESCRIPTION

[0083] Embodiments of the present disclosure are described in detail with reference to the attached drawings. It should be understood that these embodiments are discussed solely for the purpose of better illustrating the present disclosure and are not intended to limit the scope of the present disclosure in any way. Reference throughout this specification to features, advantages or similar language does not mean that all of the features and advantages that can be achieved in accordance with the present disclosure should be or are implemented in any single embodiment of the present disclosure. Rather, language referring to the features and advantages is understood to mean that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, it should be understood that features and advantages described in the specification are not necessarily all-inclusive of other features and advantages that can be achieved in accordance with the concepts of the present disclosure. In one or more embodiments, the features, advantages, and characteristics described can be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the disclosure can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages can be recognized in certain embodiments that can not be present in all embodiments.

[0084] As used herein, the term “network” refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. A CDMA network can implement a radio technology such as Universal Terrestrial Radio Access (UTRA). UTRA includes WCDMA and other variants of CDMA. A TDMA network can implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad hoc networks, Wireless Sensor Networks, and so on. In the following description, the terms “network” and “system” can be used interchangeably. Also, communication between two devices in a network can be performed according to any suitable communication protocol, including but not limited to communication protocols defined by standard organizations such as 3GPP. For example, the communication protocols can include first generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols, and / or any other protocols that are currently known or are developed in the future.

[0085] The term “network equipment” or “network node” or “network function” refers to any suitable function that can be implemented in a (physical or virtual) network entity of a communication network. For example, a network function can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, e.g. on a cloud infrastructure. For example, a 5G system (5GS) can comprise a plurality of NFs such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Unified Data Management (UDM), Policy Control Function (PCF), Application Function (AF), Network Exposure Function (NEF), User Plane Function (UPF) and Network Repository Function (NRF), Radio Access Network (RAN), Service Communication Proxy (SCP), Network Data Analytics Function (NWDAF), Network Slice Selection Function (NSSF), Network Slice Specific Authentication and Authorization Function (NSSAAF), Network Data Analytics Function (NWDAF), Data Collection Coordination (DCCF), Analytics Data Repository Function (ADRF), Gateway Mobile Location Center (GMLC), Network Slice Admission Control Function (NSACF), etc. For example, a 4G system (e.g. LTE (Long Term Evolution)) can comprise a Mobility Management Entity (MME), a Home Subscriber Server (HSS), a PCRF (Policy and Charging Rules Function), a Packet Data Network Gateway (PGW), a PGW Control Plane (PGW-C), a Serving Gateway (SGW), a SGW Control Plane (SGW-C), an E-UTRAN Node B (eNB), etc. In other embodiments, e.g. depending on the specific network, the network functions can comprise different types of NFs.

[0086] The term "terminal device" refers to any end device that can access a communication network and receive services therefrom. By way of example and not limitation, a terminal device refers to a mobile terminal, user equipment (UE), or other suitable device. A UE can be, for example, a subscriber station (SS), a portable user station, a mobile station (MS), or an access terminal (AT). A terminal device can include, but is not limited to, a portable computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over Internet Protocol (VoIP) phone, a wireless local loop phone, a tablet, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), or the like. In the following description, the terms "terminal device," "terminal," "user equipment," and "UE" can be used interchangeably. As one example, a terminal device can represent a UE configured for communication in accordance with one or more communication standards promulgated by 3GPP (the Third Generation Partnership Project), such as the LTE standard or the NR standard by 3GPP. As used herein, a "user equipment" or "UE" can not necessarily have a "user" in the sense of a human user that owns and / or operates the relevant device. In some embodiments, a terminal device can be configured to transmit and / or receive information without direct human interaction. For example, a terminal device can be designed to transmit information to a network on a predetermined schedule or in response to external stimuli, such as a trigger signal from a base station. Alternatively, a UE can represent a device that is intended for sale to, or operation by, a human user but that is not primarily intended for machine communication.

[0087] As yet another example, in an Internet of Things (IoT) scenario, a terminal device can represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another terminal device and / or a network device. In this case, the terminal device can be a machine-to-machine (M2M) device, which in a 3GPP context can be referred to as a machine-type communication (MTC) device. As one particular example, a terminal device can be a UE implementing the 3GPP Narrow Band-Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices (e.g., electricity meters), industrial machinery, or home or personal appliances, e.g., refrigerators, televisions, personal wearables (e.g., watches), etc. In other scenarios, a terminal device can represent a vehicle or other equipment that is capable of monitoring and / or reporting on its operational status or other functions related to its operation.

[0088] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc. indicate that the embodiment described can include a particular feature, structure, or characteristic, but every embodiment can not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of those skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described or claimed. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0089] It should be understood that although the terms “first” and “second” etc. can be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0090] As used herein, the phrase “at least one of’ or “at least one of A or B” can be understood to mean “either or both of” A or B. The phrase “A and / or B” can be understood to mean “both A and B, or at least one of A and B”.

[0091] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including” when used herein, specify the presence of stated features, elements and / or components etc. but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0092] Note that the terms used herein are only for the convenience of description and to distinguish between nodes, devices or networks etc. Other terms having similar / same meanings can also be used as technology evolves.

[0093] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0094] Although the subject matter described herein can be implemented in any appropriate type of system using any suitable components, embodiments disclosed herein are described in relation to systems that are configured in accordance with Figure 1a , 1b, 1c and 1d are described as the communication system of the exemplary system architecture. Figure 1a 、 1b The system architectures of 1c, 1d, and 1d merely depict some exemplary elements. In practice, a communication system may further include any additional elements suitable for supporting communications between terminal devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or terminal device). The communication system may provide communications and various types of services to one or more terminal devices, facilitating access and / or use of services provided by or via the communication system by the terminal devices.

[0095] Figure 1a The high-level architecture of a fifth generation network according to an embodiment of the present disclosure is schematically shown. For example, the fifth generation network may be 5GS. Figure 1a The architecture is the same as Figure 4.2.3-1 of 3GPP TS 23.501 V18.0.0. Figure 1a The system architecture may include some exemplary elements such as AUSF, AMF, DN (Data Network), NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP (Service Communication Agent), NSSAAF (Network Slice Specific Authentication and Authorization Function), NSACF (Network Slice Admission Control Function), Edge Application Server Discovery Function (EASDF), etc.

[0096] According to an exemplary embodiment, the UE may establish a signaling connection with the AMF via reference point N1, such as Figure 1a This signaling connection enables the exchange of NAS (Non-Access Stratum) signaling between the UE and the core network, including the signaling connection between the UE and the (R)AN, and the N2 connection between the (R)AN and the AMF for the UE. The (R)AN can communicate with the UPF via reference point N3. The UE can establish a protocol data unit (PDU) session with the DN (data network, such as the operator's network or the Internet) through the UPF via reference point N6.

[0097] like Figure 1a As further shown in FIG, the example system architecture also includes service-based interfaces such as Nnrf, Nnef, Nausf, Nudm, Npcf, Namf, Nnsacf, Neasdf, and Nsmf exposed by NFs such as NRF, NEF, AUSF, UDM, PCF, AMF, NSACF, EASDF, and SMF. In addition, Figure 1aSome reference points are also shown, such as N1, N2, N3, N4, N6, and N9, which can support interactions between NF services in the NF. For example, these reference points can be implemented through respective NF service-based interfaces and by specifying some NF service consumers and providers and their interactions to perform specific system procedures.

[0098] Figure 1b A data collection architecture using data collection coordination according to embodiments of the disclosure is schematically illustrated. Figure 1b The architecture of FIG. 1 is the same as FIG. 4.2.0-1a of 3GPP TS 23.288 V18.0.0. Figure 1b The system architecture of FIG. 1 can include some exemplary elements, such as NWDAF, DCCF, MFAF (Message Forwarding Adapter Function), NRF / UDM / BSF (Binding Support Function), and any NF (Data Source).

[0099] As depicted in Figure 1b , the Ndccf interface is defined for the NWDAF to support one or more subscription requests for data forwarding, canceling a subscription for data forwarding, and requesting specific data reporting from the DCCF. If the data has not yet started to be collected, the DCCF requests the data from the data source using the Nnf service. The DCCF can collect the data and forward it to the NWDAF, or the DCCF can rely on a message forwarding framework to collect the data from the NF and forward it to the NWDAF.

[0100] Figure 1c A network data analytics exposure architecture using data collection coordination according to embodiments of the disclosure is schematically illustrated. Figure 1c The architecture of FIG. 2 is the same as FIG. 4.2.0-2a of 3GPP TS 23.288 V18.0.0. Figure 1c The system architecture of FIG. 2 can include some exemplary elements, such as NWDAF, DCCF, MFAF, NRF / UDM / BSF, and any NF.

[0101] As depicted in Figure 1c , the Ndccf interface is defined for any NF to support one or more subscription requests for network analytics, canceling a subscription for network analytics, and requesting specific network analytics reporting from the DCCF. If the analytics has not yet started to be collected, the DCCF requests the analytics from the NWDAF using the Nnwdaf service. The DCCF can collect the analytics and forward it to the NF, or the DCCF can rely on a message forwarding framework to collect the analytics and forward it to the NF.

[0102] Figure 1d A data storage architecture for analytics and collected data according to embodiments of the disclosure is schematically illustrated.Figure 1d The architecture is the same as Figure 4.2.1-1 of 3GPP TS 23.288 V18.0.0. Figure 1d The system architecture may include some exemplary elements, such as ADRF, DCCF, MFAF and NF.

[0103] As outlined in 3GPP TS 23.288 V18.0.0, the 5G system architecture allows the ADRF to store and retrieve collected data and analytics. The ADRF exposes Nadrf services for storage and retrieval of data by other 5GC NFs (e.g., NWDAF), which then use Nadrf services to access this data. Based on NF requests or configuration on the DCCF, the DCCF can determine the ADRF and interact directly or indirectly with it to request or store data. Consumer NFs can use the Nadrf_DataManagement_RetrievalSubscribe service operation to retrieve stored data or analytics from the ADRF and receive future notifications containing the corresponding data or analytics received by the ADRF.

[0104] Figure 1a 、 1b The various NFs shown in 1c and 1d may contain corresponding functions, for example, as defined in various 3GPP specifications (e.g., 3GPP TS 23.501 V18.0.0, 3GPP TS 23.502 V18.0.0, 3GPP TS 23.503 V18.0.0 and 3GPP TS 23.288 V18.0.0).

[0105] Figure 2a 1 is a flowchart illustrating a first example of a subscription-notification NF service according to an embodiment of the present disclosure, Figure 2a Same as Figure 7.1.2-2 of 3GPP TS 23.501 V18.0.0.

[0106] NF_A can subscribe to the NF service provided by NF_B by sending a subscription request to NF_B. NF_B can confirm the execution of the subscription request. NF_B can detect the occurrence of the monitored event and send an event report to NF_A via a notification message.

[0107] Figure 2b 1 is a flowchart illustrating a second example of a subscribe-notify NF service according to an embodiment of the present disclosure, Figure 2b Same as Figure 7.1.2-3 of 3GPP TS 23.501 V18.0.0.

[0108] NF_A can also subscribe to the NF service provided by NF_B on behalf of NF_C, i.e. it requests the NF service producer to send event notifications to one or more other consumers. In this case, NF_A includes in the subscription request the notification endpoint (i.e. notification target address) and notification correlation ID of NF_C. NF_A can also include in the subscription request additional notification endpoint and notification correlation ID of NF A associated with one or more subscription change related event IDs (e.g. subscription correlation ID change) so that NF_A can receive notifications of subscription change related events.

[0109] Figure 2c A flow diagram of subscription-notification using indirect communication is shown, Figure 2c Same as Figure 7.1.2-5 of 3GPP TS 23.501 V18.0.0.

[0110] In case of indirect communication, SCP is used by the NF service consumer (NF_A). SCP routes messages between the NF service consumer (NF_A) and the NF service producer (NF_B) based on routing binding indication (if available) and can perform discovery and associated selection of the NF service producer (NF_B) on behalf of the NF service consumer (NF_A). The NF service consumer (NF_A) can request the NF service producer (NF_B) to send event notifications to the NF service consumer (NF_A) or other consumers (NF_C) via the SCP.

[0111] Figure 3a A flow diagram of a method is shown, which can be performed by an apparatus implemented in a first network function (NF), or at a first NF, or implemented as a first NF, or an apparatus communicatively coupled to a first NF, according to an embodiment of the disclosure. Thus, the apparatus can provide means or modules for implementing various portions of the method 300, as well as means or modules for implementing other processes in conjunction with other components.

[0112] At block 302, the first NF can receive a first subscription request from a second NF. The first subscription request can include first information indicating whether an event producer NF is required to send notification data to be processed to an event consumer NF before handling an exception.

[0113] The first NF, the second NF, the event producer NF, and the event consumer NF can be any suitable network device, node, entity, or function. For example, the first NF, the second NF, the event producer NF, and the event consumer NF can be any NF as defined in various 3GPP specifications, such as 3GPP TS 23.501 V18.0.0, 3GPP TS 23.503 V18.0.0, and 3GPP TS 23.288 V18.0.0.

[0114] In embodiments, the second NF can be a DCCF service consumer, a NWDAF service consumer, or a data consumer.

[0115] In embodiments, the first NF can be a DCCF, a NWDAF, or a data source.

[0116] In embodiments, the first NF can comprise at least one of: an ADRF, an Aggregator NWDAF, a DCCF, a NWDAF, a NEF, an AMF, an SMF, a UDM, a GMLC, an NSACF, an AF, an SCP, a PCF, or a UPF.

[0117] In embodiments, the second NF can comprise at least one of: an ADRF, an Aggregator NWDAF, a DCCF, a NWDAF, a NEF, an AMF, an SMF, a UDM, a GMLC, an NSACF, an AF, an SCP, a PCF, or a UPF.

[0118] In embodiments, the event producer NF can comprise at least one of: an ADRF, an Aggregator NWDAF, a DCCF, a NWDAF, a NEF, an AMF, an SMF, a UDM, a GMLC, an NSACF, an AF, an SCP, a PCF, or a UPF.

[0119] In embodiments, the event consumer NF can comprise at least one of: an ADRF, an Aggregator NWDAF, a DCCF, a NWDAF, a NEF, an AMF, an SMF, a UDM, a GMLC, an NSACF, an AF, an SCP, a PCF, or a UPF.

[0120] The first subscription request can be any suitable subscription request, such as an existing subscription request or a new subscription request. In embodiments, the first subscription request can be any suitable subscription request as defined in various 3GPP specifications, such as 3GPP TS 23.502 V18.0.0, 3GPP TS 23.503 V18.0.0, and 3GPP TS 23.288 V18.0.0.

[0121] In an embodiment, the first subscription request can comprise at least one of: a data management subscription request (e.g. Ndccf_DataManagement_Subscribe request), an analytics subscription request (e.g. Nnwdaf_AnalyticsSubscription_Subscribe request), or an event exposure subscription request.

[0122] For example, the first subscription request can comprise at least one of: a Nnwdaf_AnalyticsSubscription_Subscribe request,

[0123] a Namf_EventExposure_Subscribe request,

[0124] a Nadrf_DataManagement_RetrievalSubscribe request,

[0125] a Npcf_PolicyAuthorization_Subscribe request,

[0126] a Nudm_SDM_Subscribe request,

[0127] a Ndccf_DataManagement_Subscribe request,

[0128] a Naf_EventExposure_Subscribe request,

[0129] a Nsmf_EventExposure_Subscribe request,

[0130] a Nnwdaf_MLModelProvision_Subscribe request,

[0131] a Nnsacf_SliceEventExposure_Subscribe request,

[0132] a Nnef_EventExposure_Subscribe request,

[0133] a Nnef_AnalyticsExposure_Subscribe request,

[0134] a Nnwdaf_DataManagement_Subscribe request,

[0135] a Nmfaf_3caDataManagement Subscribe request,

[0136] Nadrf_DataManagement_StorageSubscriptionRequest,

[0137] Namf_Communication_N1N2MessageSubscribe request,

[0138] Namf_Communication_N2InfoSubscribe request,

[0139] Namf_Communication_AMFStatusChangeSubscribe request,

[0140] Namf_Communication_NonUeN2InfoSubscribe request,

[0141] Nudm_EventExposure_Subscribe request,

[0142] Npcf_EventExposure_Subscribe request,

[0143] Npcf_AMPolicyAuthorization_Subscribe request,

[0144] Nnef_AMPolicyAuthorization_Subscribe request,

[0145] Nnef_TimeSynchronization_CapsSubscribe request,

[0146] Nudr_DM_Subscribe request,

[0147] Nbsf_Management_Subscribe request,

[0148] Nudsf_UnstructuredDataManagement_Subscribe request,

[0149] Nnssf_NSSAIAvailability_Subscribe request,

[0150] Nucmf_UECapabilityManagement_Subscribe request

[0151] Nupf_EventExposure_Subscribe request,

[0152] Ntsctsf_TimeSynchronization_CapsSubscribe request, or

[0153] Ntsctsf_QoSandTSCAssistance_Subscribe request, etc., as defined in 3GPP TS 23.502 V18.0.0 and 3GPP TS 23.288 V18.0.0.

[0154] The first subscription request can include any suitable information. For example, the first subscription request can include the event reporting information in Table 4.15.1-1.

[0155] In an embodiment, the first information can indicate that the event producer NF is to send pending notifications to the event consumer NF along with one or more stored unsent events before handling an exception (e.g., receiving a cancel subscription request, the event producer NF deciding to send a termination request, the event subscription being transferred, or batch or aggregate handling of event data can no longer be handled, etc.).

[0156] The first information can have any suitable form, e.g., a bit, a flag, an indicator, etc. In an embodiment, the first information can include a pending notification flag. Note that any other suitable name can be possible.

[0157] For example, the pending notification flag can enable a requirement for the event producer NF to send pending notifications of one or more stored unsent events before handling an exception (e.g., receiving a cancel subscription request, or the event producer NF deciding to send a termination request, the event subscription being transferred, or batch or aggregate handling of event data can no longer be handled, etc.).

[0158] In an embodiment, when the pending notification flag is set to true, it can indicate a requirement for the event producer NF to send pending notification data to the event consumer NF before handling an exception.

[0159] For example, when the pending notification flag is set to true, the event producer NF can send pending notifications of one or more stored unsent events before handling an exception. The pending notifications can be included in at least one of:

[0160] - in the same notification message if the event producer NF decides to send a termination request notification to the event consumer NF;

[0161] - in a cancel subscription response if the event consumer NF is itself a notification endpoint; or

[0162] - before the exception handling, included in a separate notification message containing the notification cause to be handled.

[0163] In an embodiment, when the pending notification flag is set to false or not present, it indicates that the event producer NF is not required to send the pending notification data to the event consumer NF before handling the exception.

[0164] For example, when the pending notification flag is set to false or not present, the event producer NF is not required to send the pending notification, and can discard one or more stored unsent events (e.g., if they cannot be handled at the time of the exception). Alternatively, the event producer NF can send the pending notification data to the event consumer NF before handling the exception.

[0165] The pending notification data can be any suitable notification data that has not been sent to the event consumer NF. For example, there can be one or more stored unsent events in the event producer NF before the notification trigger condition is met. Some example scenarios can include an aggregator NWDAF, batch data handling, analytics subscription transfer, or DCCF relocation, etc.

[0166] In an embodiment, the pending notification data can include at least one stored unsent event.

[0167] The exception can be any suitable exception, and the present disclosure is not limited in this regard. For example, the exception can cause the event producer NF to be unable to provide service to the event consumer NF. For example, the exception can be a hardware exception, a software exception, overload, maintenance, power saving, etc.

[0168] In an embodiment, the exception can include at least one of: the event producer NF being unable to handle analytics, the event producer NF being unable to handle event data, the event producer NF receiving a cancel subscription request, the event producer NF deciding to send a termination request, event data being unable to be collected, a subscription being transferred, a DCCF being unable to handle analytics data or collected data, or an aggregator NWDAF being unable to handle analytics.

[0169] Figure 3b A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in, or at, or as, or communicatively coupled to, a first NF. Thus, the device can provide means or modules for implementing various portions of the method 310, as well as means or modules for implementing other processes in conjunction with other components. For certain portions that have already been described in the above embodiments, their descriptions are omitted here for the sake of brevity.

[0170] At block 312, the first NF can send a second subscription request to a third NF. The second subscription request can include the first information.

[0171] The third NF can be any suitable network device, node, entity, or function. For example, the third NF can be any NF as defined in various 3GPP specifications (e.g., 3GPP TS 23.501 V18.0.0, 3GPP TS 23.503 V18.0.0, and 3GPP TS 23.288 V18.0.0).

[0172] In embodiments, the third NF can include at least one of: an ADRF, an Aggregator NWDAF, a DCCF, a NWDAF, a NEF, an AMF, an SMF, a UDM, a GMLC, an NSACF, an AF, an SCP, a PCF, or a UPF.

[0173] In embodiments, the third NF can be an event producer (e.g., a NWDAF as an analytics event producer, a data source as a data event producer).

[0174] In one scenario, the first NF is an event consumer (e.g., an analytics consumer or a data consumer), the second NF is a DCCF (coordination and batch processing of analytics data and / or collected data) or an Aggregator NWDAF (aggregation of analytics data), and the third NF is an event producer (e.g., a NWDAF as an analytics producer or a data source NF as a data collection producer).

[0175] The second subscription request can be any suitable subscription request, such as an existing subscription request or a new subscription request. In embodiments, the second subscription request can be any suitable subscription request as defined in various 3GPP specifications (e.g., 3GPP TS 23.502 V18.0.0, 3GPP TS 23.503 V18.0.0, and 3GPP TS 23.288 V18.0.0).

[0176] In embodiments, the second subscription request can include at least one of: a data management subscription request (e.g., a Ndccf_DataManagement_Subscribe request), an analytics subscription request (e.g., a Nnwdaf_AnalyticsSubscription_Subscribe request), or an event exposure subscription request.

[0177] For example, the second subscription request can include at least one of: a Nnwdaf_AnalyticsSubscription_Subscribe request,

[0178] Namf_EventExposure_Subscribe request,

[0179] Nadrf_DataManagement_RetrievalSubscribe request,

[0180] Npcf_PolicyAuthorization_Subscribe request,

[0181] Nudm_SDM_Subscribe request,

[0182] Ndccf_DataManagement_Subscribe request,

[0183] Naf_EventExposure_Subscribe request,

[0184] Nsmf_EventExposure_Subscribe request,

[0185] Nnwdaf_MLModelProvision_Subscribe request,

[0186] Nnsacf_SliceEventExposure_Subscribe request,

[0187] Nnef_EventExposure_Subscribe request,

[0188] Nnef_AnalyticsExposure_Subscribe request,

[0189] Nnwdaf_DataManagement_Subscribe request,

[0190] Nmfaf_3caDataManagement Subscribe request,

[0191] Nadrf_DataManagement_StorageSubscriptionRequest,

[0192] Namf_Communication_N1N2MessageSubscribe request,

[0193] Namf_Communication_N2InfoSubscribe request,

[0194] Namf_Communication_AMFStatusChangeSubscribe request,

[0195] Namf_Communication_NonUeN2InfoSubscribe request,

[0196] Nudm_EventExposure_Subscribe request,

[0197] Npcf_EventExposure_Subscribe request,

[0198] Npcf_AMPolicyAuthorization_Subscribe request,

[0199] Nnef_AMPolicyAuthorization_Subscribe request,

[0200] Nnef_TimeSynchronization_CapsSubscribe request,

[0201] Nudr_DM_Subscribe request,

[0202] Nbsf_Management_Subscribe request,

[0203] Nudsf_UnstructuredDataManagement_Subscribe request,

[0204] Nnssf_NSSAIAvailability_Subscribe request,

[0205] Nucmf_UECapabilityManagement_Subscribe request

[0206] Nupf_EventExposure_Subscribe request,

[0207] Ntsctsf_TimeSynchronization_CapsSubscribe request or

[0208] Ntsctsf_QoSandTSCAssistance_Subscribe request, and the like, as defined in 3GPP TS 23.502 V18.0.0 and 3GPP TS 23.288 V18.0.0.

[0209] The second subscription request can include any suitable information. For example, the second subscription request can include event reporting information in Table 4.15.1-1.

[0210] Figure 3c A flow diagram illustrating a method according to another embodiment of the disclosure is shown, which can be performed by a device implemented in, or at, or as, or communicatively coupled to, a first NF. Thus, the device can provide means or modules for implementing various portions of the method 320, as well as means or modules for implementing other processes in conjunction with other components. For certain portions that have already been described in the above embodiments, their descriptions are omitted here for brevity.

[0211] At block 322, the first NF can receive, from a third NF, a first message including notification data to be processed when an exception occurs at the event producer NF.

[0212] For example, the third NF can be the event producer NF. It can determine that an exception occurs, and send the first message including the notification data to be processed to the first NF. As another example, the third NF can receive the notification data to be processed from another NF (e.g., the event producer NF), and then send the first message including the notification data to be processed to the first NF.

[0213] At block 324, the first NF can send, to a second NF, a second message including the notification data to be processed.

[0214] The first message and / or the second message can also include any other suitable information. In embodiments, the first message and / or the second message can also include second information indicating a notification cause of the notification data to be processed.

[0215] The second information can have any suitable form, such as a bit, a flag, an indicator, etc. In embodiments, the second information can include the notification cause to be processed. Note that any other suitable name can be possible.

[0216] For example, the second information such as the notification cause to be processed can indicate one or more stored causes of the notification to be processed for the unsent event, e.g., data can no longer be collected, a cancel subscription request is received from the event consumer NF, or the event producer NF decides to send a termination request, etc.

[0217] In an embodiment, the notification cause of the notification data to be processed can comprise at least one of: an exception occurred in the event producer NF, the event producer NF is unable to process analytics, the event producer NF is unable to process event data, the event producer NF receives a cancel subscription request, the event producer NF decides to send a termination request, event data cannot be collected, the subscription is transferred, the DCCF is unable to process analytics data or collected data, or the aggregator NWDAF is unable to process analytics.

[0218] The first message and / or the second message can be any suitable message, e.g. an existing message or a new message. In an embodiment, the first message and / or the second message can comprise at least one of a notification message or a cancel subscription response.

[0219] For example, when the event producer NF receives a cancel subscription request, it can send a cancel subscription response. In this case, the first message and / or the second message can be the cancel subscription response.

[0220] The notification message can be any suitable notification message, e.g. an existing message or a new message. In an embodiment, the notification message can be a notification message corresponding to the first subscription request and / or the second subscription request.

[0221] In an embodiment, the notification message can comprise at least one of: a data management notification message, an analytics subscription notification message, or an event exposure notification message.

[0222] In an embodiment, the notification message can comprise a termination request.

[0223] For example, when the event producer NF (e.g. NWDAF) requests termination of (analytics) subscription, i.e. the event producer NF (e.g. NWDAF) will not provide further notifications related to this subscription anymore, with a reason value (e.g. user consent revoked, event producer NF overloaded, UE moved out of the event producer NF’s service area, etc.), the event producer NF (e.g. NWDAF) can send a notification message comprising a termination request.

[0224] Figure 3d A flowchart of a method according to another embodiment of the disclosure is shown, which can be performed by a device implemented in, or at, or as, or communicatively coupled to, a first NF. Thus, the device can provide means or modules for implementing various portions of the method 330, as well as means or modules for implementing other processes in conjunction with other components. For certain portions for which description has been provided above in connection with the embodiments described above, description thereof is omitted here for the sake of brevity.

[0225] At block 332, the first NF can determine that an exception occurred.

[0226] At block 334, the first NF can send, to the second NF or event consumer NF, a third message including the notification data to be processed based on the first information.

[0227] For example, the first NF can be an event producer NF. It can determine that an exception occurs and send, to the second NF or event consumer NF, a third message including the notification data to be processed.

[0228] The third message can further include any other suitable information. In embodiments, the third message can further include third information indicating a notification cause of the notification data to be processed.

[0229] The third information can have any suitable form, such as a bit, a flag, an indicator, etc. In embodiments, the third information can include the notification cause to be processed. Note that any other suitable name can be possible.

[0230] For example, the third information such as the notification cause to be processed can indicate one or more stored reasons for the unsent event’s notification to be processed, such as that the data can no longer be collected, a cancel subscription request is received from the event consumer NF, or the event producer NF decides to send a termination request, etc.

[0231] In embodiments, the notification cause of the notification data to be processed can include at least one of: an exception occurs in the event producer NF, the event producer NF cannot process analytics, the event producer NF cannot process event data, the event producer NF receives a cancel subscription request, the event producer NF decides to send a termination request, event data cannot be collected, a subscription is transferred, a DCCF cannot process analytics data or collected data, or an aggregator NWDAF cannot process analytics.

[0232] The third message can be any suitable message, such as an existing message or a new message. In embodiments, the third message includes at least one of a notification message or a cancel subscription response.

[0233] For example, when the first NF receives a cancel subscription request, it can send a cancel subscription response. In this case, the third message can be the cancel subscription response.

[0234] The notification message can be any suitable notification message, such as an existing message or a new message. In embodiments, the notification message can be a notification message corresponding to the first subscription request.

[0235] In embodiments, the notification message can include at least one of a data management notification message, an analytics subscription notification message, or an event exposure notification message.

[0236] In embodiments, the notification message can include a termination request.

[0237] For example, when an event producer NF (e.g. NWDAF) requests termination of (an analytics) subscription, i.e. the event producer NF (e.g. NWDAF) will no longer provide further notifications related to this subscription, with a cause value (e.g. user consent revoked, event producer NF overload, UE moved out of the event producer NF’s service area, etc.), the event producer NF (e.g. NWDAF) can send a notification message including the termination request.

[0238] Figure 3e A flow diagram illustrating a method according to another embodiment of the disclosure is shown, which can be performed by an apparatus implemented in, or at, or as, or communicatively coupled to, a first NF. Thus, the apparatus can provide means for implementing various portions of the method 340, as well as means for implementing other processes in conjunction with other components. For certain portions that have already been described in the above embodiments, their descriptions are omitted here for the sake of brevity.

[0239] At block 342, the first NF can receive, from a third NF, a first notification message or a first unsubscribe response including notification data to be processed.

[0240] In an embodiment, the first notification message can further include second information indicating a notification cause of the notification data to be processed.

[0241] In an embodiment, the first notification message can further include information informing the consumer instance when the data or analytics will be deleted.

[0242] Figure 3f A flow diagram illustrating a method according to another embodiment of the disclosure is shown, which can be performed by an apparatus implemented in, or at, or as, or communicatively coupled to, a first NF. Thus, the apparatus can provide means for implementing various portions of the method 350, as well as means for implementing other processes in conjunction with other components. For certain portions that have already been described in the above embodiments, their descriptions are omitted here for the sake of brevity.

[0243] At block 352, the first NF can send, to the third NF, a first notification response message including information indicating whether the consumer instance will retrieve the stored data or analytics before deletion.

[0244] Figure 3gA flow diagram illustrating a method according to another embodiment of the disclosure is shown, which can be performed by a device implemented in, or at, or as, or communicatively coupled to, a first NF. Thus, the device can provide means or modules for implementing various portions of the method 360, as well as means or modules for implementing other processes in conjunction with other components. For certain portions already described in the above embodiments, their descriptions are omitted here for the sake of brevity.

[0245] At block 362, the first NF can send, to the second NF, a second notification message or a second unsubscribe response including the notification data to be processed.

[0246] In embodiments, the second notification message can further include second information indicating a notification cause of the notification data to be processed.

[0247] In embodiments, the second notification message can further include information informing the consumer instance when the data or analytics will be deleted.

[0248] Figure 3h A flow diagram illustrating a method according to another embodiment of the disclosure is shown, which can be performed by a device implemented in, or at, or as, or communicatively coupled to, a first NF. Thus, the device can provide means or modules for implementing various portions of the method 370, as well as means or modules for implementing other processes in conjunction with other components. For certain portions already described in the above embodiments, their descriptions are omitted here for the sake of brevity.

[0249] At block 372, the first NF can receive, from the second NF, a second notification response message including information indicating whether the consumer instance will retrieve the stored data or analytics before deletion.

[0250] In embodiments, the first NF and / or the second NF can include at least one of an analytics data repository function (ADRF), an aggregator NWDAF, a data collection coordination (DCCF), a network data analytics function (NWDAF), a network exposure function (NEF), an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a network slice admission control function (NSACF), an application function (AF), a policy control function (PCF), or a user plane function (UPF).

[0251] In an embodiment, the notification reason for the pending notification data may include at least one of the following: an exception occurs in the event producer NF, the event producer NF cannot process the analysis, the event producer NF cannot process the event data, the event producer NF receives a cancel subscription request, the event producer NF decides to send a termination request, the event data cannot be collected, the subscription is transferred, the DCCF cannot process the analysis data or the collected data, or the aggregator NWDAF cannot process the analysis.

[0252] In an embodiment, the notification message may include at least one of a data management notification message, an analysis subscription notification message, or an event opening notification message.

[0253] In an embodiment, the notification message may include a termination request.

[0254] In an embodiment, the third NF may include at least one of the following: analysis data repository function (ADRF), aggregator NWDAF, data collection coordination (DCCF), network data analysis function (NWDAF), network exposure function (NEF), access and mobility management function (AMF), session management function (SMF), unified data management (UDM), network slice admission control function (NSACF), application function (AF), policy control function (PCF) or user plane function (UPF).

[0255] Figure 4a A flowchart illustrating a method according to another embodiment of the present disclosure is provided. This method can be performed by an apparatus implemented in a second NF, or implemented at a second NF, or implemented as a second NF, or communicatively coupled to a second NF. Thus, the apparatus can provide components or modules for implementing various portions of method 400, as well as components or modules for implementing other processes in conjunction with other components. For the sake of brevity, descriptions of certain portions already described in the above embodiments are omitted here.

[0256] At block 402, the second NF may send a first subscription request to the first NF. The first subscription request may include first information indicating whether the event producer NF is required to send notification data to be processed to the event consumer NF before processing an exception.

[0257] In an embodiment, the first subscription request may include at least one of a data management subscription request, an analysis subscription request, or an event open subscription request.

[0258] In an embodiment, the first information may include a pending notification flag.

[0259] In an embodiment, when the pending notification flag is set to true, it indicates that the event producer NF is required to send the pending notification data to the event consumer NF before handling the exception.

[0260] In an embodiment, when the pending notification flag is set to false or is not present, it indicates that the event producer NF is not required to send the pending notification data to the event consumer NF before handling the exception.

[0261] In an embodiment, the exception can comprise at least one of: the event producer NF is unable to process analytics, the event producer NF is unable to process event data, the event producer NF receives a request to unsubscribe, the event producer NF decides to send a termination request, the event data cannot be collected, the subscription is transferred, the DCCF is unable to process analytics data or collected data, or the aggregator NWDAF is unable to process analytics.

[0262] In an embodiment, the pending notification data can comprise at least one stored unsent event.

[0263] In an embodiment, the first NF can comprise at least one of: an ADRF, an aggregator NWDAF, a DCCF, a NWDAF, a NEF, an AMF, an SMF, a UDM, a GMLC, a NSACF, an AF, a SCP, a PCF, or a UPF.

[0264] In an embodiment, the second NF can comprise at least one of: an ADRF, an aggregator NWDAF, a DCCF, a NWDAF, a NEF, an AMF, an SMF, a UDM, a GMLC, a NSACF, an AF, a SCP, a PCF, or a UPF.

[0265] In an embodiment, the event producer NF can comprise at least one of: an ADRF, an aggregator NWDAF, a DCCF, a NWDAF, a NEF, an AMF, an SMF, a UDM, a GMLC, a NSACF, an AF, a SCP, a PCF, or a UPF.

[0266] In an embodiment, the event consumer NF can comprise at least one of: an ADRF, an aggregator NWDAF, a DCCF, a NWDAF, a NEF, an AMF, an SMF, a UDM, a GMLC, a NSACF, an AF, a SCP, a PCF, or a UPF.

[0267] Figure 4bA flowchart of a method according to another embodiment of the disclosure is shown, which can be performed by a device implemented in, or at, or as, or communicatively coupled to, a second NF. Thus, the device can provide means or modules for implementing various portions of the method 410, as well as means or modules for implementing other processes in conjunction with other components. For certain portions that have already been described in the above embodiments, their descriptions are omitted here for brevity.

[0268] At block 412, the second NF can receive, from the first NF or the event producer NF, a message including notification data to be processed when an exception occurs in the event producer NF.

[0269] For example, the first NF can be the event producer NF. It can determine that an exception occurs and send a message including notification data to be processed to the second NF. As another example, the first NF can receive notification data to be processed from another NF (e.g., the event producer NF) and then send a first message including the notification data to be processed to the second NF.

[0270] In embodiments, the message can further include fourth information indicating a notification cause of the notification data to be processed.

[0271] The fourth information can have any suitable form, such as a bit, a flag, an indicator, etc. In embodiments, the fourth information can include the notification cause to be processed. Note that any other suitable name can be possible.

[0272] In embodiments, the notification cause of the notification data to be processed can include at least one of: an exception occurs in the event producer NF, the event producer NF is unable to process analytics, the event producer NF is unable to process event data, the event producer NF receives a cancel subscription request, the event producer NF decides to send a termination request, event data cannot be collected, a subscription is transferred, a DCCF is unable to process analytics data or collected data, or an aggregator NWDAF is unable to process analytics.

[0273] The message can be any suitable message, such as an existing message or a new message. In embodiments, the message can include at least one of a notification message or a cancel subscription response.

[0274] In embodiments, the notification message can include at least one of a data management notification message, an analytics subscription notification message, or an event exposure notification message.

[0275] In embodiments, the notification message includes a termination request.

[0276] Figure 4cA flow diagram of a method according to another embodiment of the disclosure is shown, which can be performed by an apparatus implemented in, or at, or as, or communicatively coupled to, a third NF. Thus, the apparatus can provide means or modules for implementing various portions of the method 420, as well as means or modules for implementing other processes in conjunction with other components. For certain portions already described in the above embodiments, descriptions thereof are omitted here for the sake of brevity.

[0277] At block 422, the third NF can send, to the first NF, a first notification message or a first unsubscribe response including the notification data to be processed.

[0278] In embodiments, the first notification message can further include second information indicating a notification cause of the notification data to be processed.

[0279] In embodiments, the first notification message can further include information informing the consumer instance when the data or analytics will be deleted.

[0280] Figure 4d A flow diagram of a method according to another embodiment of the disclosure is shown, which can be performed by an apparatus implemented in, or at, or as, or communicatively coupled to, a third NF. Thus, the apparatus can provide means or modules for implementing various portions of the method 430, as well as means or modules for implementing other processes in conjunction with other components. For certain portions already described in the above embodiments, descriptions thereof are omitted here for the sake of brevity.

[0281] At block 432, the third NF can receive, from the first NF, a first notification response message including information indicating whether the consumer instance will retrieve the stored data or analytics before deletion.

[0282] In embodiments, the first NF can include at least one of an analytics data repository function (ADRF), an aggregator NWDAF, a data collection coordination (DCCF), a network data analytics function (NWDAF), a network exposure function (NEF), an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a network slice admission control function (NSACF), an application function (AF), a policy control function (PCF), or a user plane function (UPF).

[0283] In an embodiment, the notification cause of the notification data to be processed can comprise at least one of: an exception occurred in the event producer NF, the event producer NF is unable to process analytics, the event producer NF is unable to process event data, the event producer NF receives a request to cancel a subscription, the event producer NF decides to send a termination request, event data cannot be collected, a subscription is transferred, the DCCF is unable to process analytics data or collected data, or the aggregator NWDAF is unable to process analytics.

[0284] In an embodiment, the notification message can comprise at least one of a data management notification message, an analytics subscription notification message, or an event exposure notification message.

[0285] In an embodiment, the notification message can comprise a termination request.

[0286] In an embodiment, the third NF can comprise at least one of: an analytics data repository function (ADRF), an aggregator NWDAF, a data collection coordination (DCCF), a network data analytics function (NWDAF), a network exposure function (NEF), an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a network slice admission control function (NSACF), an application function (AF), a policy control function (PCF), or a user plane function (UPF).

[0287] Figure 5 A flow diagram illustrating a method according to another embodiment of the disclosure is shown, which can be performed by an apparatus implemented in the event consumer NF, or implemented at the event consumer NF, or implemented as the event consumer NF, or an apparatus communicatively coupled to the event consumer NF. Thus, the apparatus can provide means or modules for implementing various portions of the method 500, as well as means or modules for implementing other processes in conjunction with other components. For certain portions for which description has been provided in the above embodiments, a description thereof is omitted here for the sake of brevity.

[0288] At block 502, the event consumer NF can receive a message including notification data to be processed from the event producer NF when an exception occurs in the event producer NF.

[0289] In an embodiment, the first information can be used to indicate whether the event producer NF is required to send the notification data to be processed to the event consumer NF before handling the exception. The first information can be received by the event producer NF according to the above embodiments. Alternatively, the first information can be pre-configured in the event producer NF.

[0290] In an embodiment, the first information can comprise a notification flag to be processed.

[0291] In an embodiment, when the pending notification flag is set to true, it can indicate that the event producer NF is required to send the pending notification data to the event consumer NF before handling the exception.

[0292] In an embodiment, when the pending notification flag is set to false or not present, it can indicate that the event producer NF is not required to send the pending notification data to the event consumer NF before handling the exception.

[0293] In an embodiment, the exception can comprise at least one of: the event producer NF is unable to process analytics, the event producer NF is unable to process event data, the event producer NF receives a cancel subscription request, the event producer NF decides to send a termination request, the event data cannot be collected, the subscription is transferred, the DCCF is unable to process analytics data or collected data, or the aggregator NWDAF is unable to process analytics.

[0294] In an embodiment, the pending notification data can comprise at least one stored unsent event.

[0295] In an embodiment, the message can further comprise fifth information indicating a notification cause of the pending notification data.

[0296] The fifth information can be of any suitable form, e.g. a bit, a flag, an indicator, etc. In an embodiment, the fifth information can comprise a pending notification cause. Note that any other suitable name can be possible.

[0297] In an embodiment, the notification cause of the pending notification data can comprise at least one of: an exception occurred in the event producer NF, the event producer NF is unable to process analytics, the event producer NF is unable to process event data, the event producer NF receives a cancel subscription request, the event producer NF decides to send a termination request, the event data cannot be collected, the subscription is transferred, the DCCF is unable to process analytics data or collected data, or the aggregator NWDAF is unable to process analytics.

[0298] The message can be any suitable message, e.g. an existing message or a new message. In an embodiment, the message can comprise at least one of a notification message or a cancel subscription response.

[0299] In an embodiment, the notification message can comprise at least one of a data management notification message, an analytics subscription notification message, or an event exposure notification message.

[0300] In an embodiment, the notification message can comprise a termination request.

[0301] In an embodiment, the event producer NF may include at least one of an ADRF, an aggregator NWDAF, a DCCF, an NWDAF, a NEF, an AMF, an SMF, an UDM, a GMLC, an NSACF, an AF, an SCP, a PCF or a UPF.

[0302] In an embodiment, the event consumer NF may include at least one of an ADRF, an aggregator NWDAF, a DCCF, an NWDAF, a NEF, an AMF, an SMF, an UDM, a GMLC, an NSACF, an AF, an SCP, a PCF, or a UPF.

[0303] In an embodiment, a pending notification flag may be added to the event report information, which may indicate that the event consumer NF requires a pending notification action before the event producer NF handles the exception. The event report information may be included in the Nnwdaf_AnalyticsSubscription_Subscribe, Nnwdaf_DataManagement_Subscribe, and Ndccf_DataManagement_Subscribe service operations.

[0304] In an embodiment, flexible pending notification handling is proposed. If the consumer NF acts as a notification endpoint, the pending notification data can be included in the unsubscribe response, sent together with the termination request, or sent as a separate notification message.

[0305] In an embodiment, a pending notification reason may be added in the Nnwdaf_AnalyticsSubscription_Notify, Nnwdaf_DataManagement_Notify, and Ndccf_DataManagement_Notify service operations along with the reported pending event or events.

[0306] In an embodiment, it may enable the event consumer NF to instruct the event producer NF how to handle one or more stored unsent events when an exception occurs.

[0307] In an embodiment, it may enable the event producer NF to efficiently process pending notifications before handling exceptions.

[0308] In an embodiment, it may enable flexible pending notification messaging to minimize processing impact.

[0309] In an embodiment, an optional pending notification flag can be added in Table 4.15.1-1 of 3GPP TS 23.502 V18.0.0 as a new event reporting information parameter with the description “Indicates that the event producer NF shall send a pending notification with one or more stored unsent events to the event consumer NF before handling the exception (e.g. receiving a cancel subscription request or the event producer NF decides to send a termination request, etc.)”.

[0310] For example, Table 4.15.1-1 of 3GPP TS 23.502 V18.0.0 can be modified as follows.

[0311] Table 4.15.1-1: Event reporting information

[0312] .

[0313] In an embodiment, the following usage description can be added in clause 4.15.1 of 3GPP TS 23.502 V18.0.0.

[0314] The pending notification flag enables the requirement for the event producer NF to send a pending notification with one or more stored unsent events before handling the exception (e.g. receiving a cancel subscription request, or the event producer NF decides to send a termination request, the event subscription is transferred, or the batch or aggregate handling of event data can no longer be processed, etc.).

[0315] When the pending notification flag = TRUE, the event producer NF shall send a pending notification with one or more stored unsent events before handling the exception. The pending notification can be included in one of the following:

[0316] - in the same notification message if the event producer NF decides to send a termination request notification to the event consumer NF;

[0317] - in the cancel subscription response if the event consumer NF is itself a notification endpoint; or

[0318] - in a separate notification message containing the reason for the pending notification before handling the exception.

[0319] When the pending notification flag = FALSE or is not present, the event producer NF is not required to send a pending notification and can discard one or more stored unsent events if they cannot be processed at the time of the exception.

[0320] In an embodiment, clause 7.2.3 of 3GPP TS 23.288 V18.0.0 can be modified as follows. In clause 7.2.3, one or more pending notification events can be added as optional.

[0321] 7.2.3 Nnwdaf_AnalyticsSubscription_Unsubscribe service operation

[0322] Service operation name: Nnwdaf_AnalyticsSubscription_Unsubscribe.

[0323] Description: Unsubscribe from analytics of a NWDAF.

[0324] Input, mandatory: Subscription association ID.

[0325] Input, optional: None.

[0326] Output, mandatory: Operation execution result indication.

[0327] Output, optional: Pending notification data, which can contain one or more unsent event data.

[0328] In an embodiment, in clause 7.2.4 of 3GPP TS 23.288 V18.0.0, Nnwdaf_AnalyticsSubscription_Notify service operation, the following pending notification reason and description can be added as input optional parameters:

[0329] - Pending notification reason: indicates the reason of the pending notification of one or more stored unsent analytics events, e.g., the aggregator NWDAF has an exception before T1, receives a subscription cancellation request from analytics consumer NF or the NWDAF decides to send a termination request, etc.

[0330] In an embodiment, in clause 7.4.3 of 3GPP TS 23.288 V18.0.0, one or more pending notification events can be added as optional.

[0331] 7.4.3 Nnwdaf_DataManagement_Unsubscribe service operation

[0332] Service operation name: Nnwdaf_DataManagement_Unsubscribe.

[0333] Description: An NF consumer unsubscribes from a NWDAF for data.

[0334] Input, required: Subscription association ID.

[0335] Output, required: Operation execution result indication.

[0336] Output, optional: Pending notification data, which can contain one or more unsent event data.

[0337] In an embodiment, in clause 7.4.4 of 3GPP TS 23.288 V18.0.0, Nnwdaf_DataManagement_Notify service operation, the following pending notification reason and description can be added as input optional parameters.

[0338] The pending notification reason indicates the reason of the pending notification of one or more stored unsent events, e.g. the data cannot be collected anymore, a cancel subscription request is received from the event consumer NF or the event producer NF decides to send a termination request, etc.

[0339] In an embodiment, in clause 8.2.3 of 3GPP TS 23.288 V18.0.0, one or more pending notification events can be added as optional.

[0340] 8.2.3 Ndccf_DataManagement_Unsubscribe service operation

[0341] Service operation name: Ndccf_DataManagement_Unsubscribe

[0342] Description: The DCCF cancels the subscription to data or analytics from the consumer.

[0343] Input, required: Subscription association ID.

[0344] Input, optional: None.

[0345] Output, required: Operation execution result indication.

[0346] Output, optional: Pending notification data, which can contain one or more unsent event data.

[0347] In an embodiment, in clause 8.2.4 of 3GPP TS 23.288 V18.0.0, Ndccf_DataManagement_Notify service operation, the following pending notification reason and description can be added as input optional parameters.

[0348] The pending notification cause indicates the cause of the pending notification of one or more stored unsent events, e.g. that the data can no longer be collected, a cancel subscription request is received from the event consumer NF or the DCCF decides to send a termination request, etc.

[0349] Figure 6a A flowchart of a subscription-notification method according to another embodiment of the disclosure is shown.

[0350] It can provide an enhancement to the handling of pending analytics notifications during data management subscription / unsubscription / notification and analytics subscription / unsubscription / notification.

[0351] If the analytics consumer invokes the NWDAF service directly without DCCF interaction, similar procedures as in Figure 6 apply between the DCCF (as service consumer) and the NWDAF (as service producer).

[0352] Step 1. The analytics consumer can subscribe to analytics information via the DCCF by invoking the Ndccf_DataManagement_Subscribe service operation. A pending notification flag is added. When this pending notification flag is set to true, it indicates that the producer (i.e. DCCF) should / can report one or more pending unsent events if an exception occurs.

[0353] Step 2. If the analytics consumer does not identify a NWDAF instance or a NWDAF set, the DCCF can determine a NWDAF instance capable of providing the analytics.

[0354] Step 3. The DCCF can determine if the analytics requested in step 1 are already being collected. If the analytics consumer is already collecting the requested analytics, the DCCF can add the new analytics consumer to the list of analytics consumers that are subscribed to these analytics.

[0355] Step 4. The DCCF can invoke the Nnwdaf_AnalyticsSubscription_Subscribe service operation to the selected NWDAF. A pending notification flag can be added. When this pending notification flag is set to true, it indicates that the producer (i.e. NWDAF) should / can report one or more pending unsent events if an exception occurs.

[0356] Steps 5a and 5b. When a new output analytics is available and the event reporting trigger occurs, the NWDAF can notify the analytics information to the DCCF by invoking the Nnwdaf_AnalyticsSubscription_Notify service operation.

[0357] Steps 6a and 6b. The DCCF can send the analytics to all the notification endpoints indicated in step 1 using the Ndccf_DataManagement_Notify.

[0358] Step 7a. If an exception occurs in the producer (i.e. NWDAF) and the NWDAF decides to send a termination request in the notification message, one or more pending notification events can be added to the same notification message. The one or more pending notification events are newly added.

[0359] Step 7b. If an exception occurs in the producer (i.e. NWDAF), the NWDAF can decide to send one or more pending notification events with a pending notification cause in a separate notification message. The one or more pending notification events and the pending notification cause are newly added.

[0360] Step 8a. The DCCF can deliver the termination exception notification message to the consumer, the termination request and one or more pending notification events are included in the same notification message. The one or more pending notification events are newly added.

[0361] Step 8b. The DCCF can deliver the pending notification message to the consumer containing one or more pending notification events with a pending notification cause. The one or more pending notification events and the pending notification cause are newly added.

[0362] Step 9. When the analytics consumer no longer wishes the analytics to be collected, it can send the Ndccf_DataManagement_Unsubscribe request message to the DCCF.

[0363] Step 10. If there are no other analytics consumers subscribed to the analytics, the DCCF can unsubscribe with the NWDAF.

[0364] Step 11. The NWDAF can include one or more pending unsent analytics events in the Nnwdaf_AnalyticsSubscription_UnSubscribe response message to the DCCF. The one or more pending notification events are newly added.

[0365] Step 12. The DCCF can include the received one or more pending unsent analytics events in the Ndccf_DataManagement_Unsubscribe response message to the analytics consumer. The one or more pending notification events are newly added.

[0366] If other subscriptions are still valid, or the notification endpoint is not the consumer itself, one or more pending notification events can be sent to the specific analytics notification endpoint in separate notification messages as described in steps 7b and 8b.

[0367] Figure 6b A flowchart of a subscription-notification method according to another embodiment of the disclosure is shown.

[0368] It can provide enhancements to the handling of pending analytics notifications during data management subscription / unsubscription / notification and analytics subscription / unsubscription / notification.

[0369] If the analytics consumer invokes the NWDAF service directly without DCCF interaction, similar procedures as in Figure 6 apply between the DCCF (as service consumer) and the NWDAF (as service producer).

[0370] Step 1. The analytics consumer can subscribe to analytics information via the DCCF by invoking the Ndccf_DataManagement_Subscribe service operation. A pending notification flag is added. When the pending notification flag is set to true, it indicates that the producer (i.e. DCCF) should / can report one or more pending unsent events if an exception occurs.

[0371] Step 2. If the analytics consumer does not identify a NWDAF instance or a NWDAF set, the DCCF can determine a NWDAF instance capable of providing the analytics.

[0372] Step 3. The DCCF can determine if the analytics requested in step 1 are already being collected. If the analytics consumer is already collecting the requested analytics, the DCCF can add the new analytics consumer to the list of analytics consumers that subscribe to these analytics.

[0373] Step 4. The DCCF can invoke the Nnwdaf_AnalyticsSubscription_Subscribe service operation to the selected NWDAF. A pending notification flag can be added. When the pending notification flag is set to true, it indicates that the producer (i.e. NWDAF) should / can report one or more pending unsent events if an exception occurs.

[0374] Steps 5a and 5b. When a new output analytics is available and the event reporting trigger occurs, the NWDAF can notify the DCCF of the analytics information by invoking the Nnwdaf_AnalyticsSubscription_Notify service operation.

[0375] Steps 6a and 6b. DCCF can use Ndccf_DataManagement_Notify to send the analytics to all the notification endpoints indicated in Step 1.

[0376] Step 7a. If an exception occurs in the producer (i.e. DCCF) and the DCCF decides to send a termination request in the notification message, one or more pending notification events can be added to the same notification message. The one or more pending notification events are newly added.

[0377] Step 7b. If an exception occurs in the producer (i.e. DCCF), the DCCF can decide to send one or more pending notification events with pending notification reasons in separate notification messages. The one or more pending notification events and the pending notification reasons are newly added.

[0378] Step 8. When the analytics consumer no longer wishes analytics to be collected, it can send an Ndccf_DataManagement_Unsubscribe request message to the DCCF.

[0379] Step 9. The DCCF can include the received one or more pending unsent analytics events in the Ndccf_DataManagement_UnSubscribe response message to the analytics consumer. The one or more pending notification events are newly added.

[0380] Other subscriptions remain valid for the NWDAF and the DCCF only processes the one or more pending events for the consumer that has unsubscribed.

[0381] Figure 7a A flow diagram illustrating a subscription-notification method according to another embodiment of the disclosure is shown.

[0382] It can provide enhancements to the handling of pending data collection notifications during data management subscription / unsubscription / notification and data collection subscription / unsubscription / notification.

[0383] If the data consumer invokes the data source NF (e.g. AMF, SMF, AF Event Exposure) service directly without DCCF interaction, similar procedures as in the following flow diagram apply between the DCCF (as a service consumer) and the data source NF (as a service producer).

[0384] Step 1. Data consumer can subscribe to data collection information via DCCF by invoking the Ndccf_DataManagement_Subscribe service operation. A pending notification flag is added. When this pending notification flag is set to true, it indicates that the producer (i.e. DCCF) should report one or more pending unsent events if an exception occurs.

[0385] Step 2. If the consumer does not check user consent, the DCCF can check and handle user consent with the UDM.

[0386] Step 3. If the data consumer does not identify the data source instance, the DCCF can determine the data source NF instance that is able to provide the required data information.

[0387] Step 4. The DCCF can determine if the data requested in step 1 is already being collected. If the data consumer is already collecting the requested data, the DCCF can add the new data consumer to the list of data consumers that are subscribed to the data.

[0388] Step 5. The DCCF can invoke the Nnf_EventExposure_Subscribe service operation to the selected data source NF. A pending notification flag can be added. When this pending notification flag is set to true, it indicates that the producer (e.g. AMF, SMF, AF, etc.) should report one or more pending unsent events if an exception occurs.

[0389] Steps 6a-6b. When new data is available and the event reporting trigger occurs, the data source NF can notify the DCCF of the collected data by invoking the Nnf_EventExposure_Notify service operation.

[0390] Steps 7a-7b. The DCCF can send the collected data to all the notification endpoints indicated in step 1 using Ndccf_DataManagement_Notify.

[0391] Step 8a. If an exception occurs in the producer (e.g. AMF, SMF, AF, etc.) and the producer decides to send a termination request in the notification message, one or more pending notification events can be added to the same notification message together. The one or more pending notification events are newly added.

[0392] Step 8b. If an exception occurs in the producer (e.g. AMF, SMF, AF, etc.), the producer can decide to send one or more pending notification events with a pending notification cause in a separate notification message. The one or more pending notification events and the pending notification cause are newly added.

[0393] Step 9a. The DCCF can deliver a termination exception notification message to the consumer, the termination request and one or more pending notification events are contained in the same notification message. The one or more pending notification events are newly added.

[0394] Step 9b. The DCCF can deliver a pending notification message to the consumer, the pending notification message contains one or more pending notification events with a pending notification cause. The one or more pending notification events and the pending notification cause are newly added.

[0395] Step 10. When the data consumer no longer wishes data to be collected, it can send an Ndccf_DataManagement_Unsubscribe request message to the DCCF.

[0396] Step 11. If there are no other data consumers subscribed to the collected data, the DCCF can unsubscribe with the data source.

[0397] Step 12. The data source NF can include the pending unsent notification events (collected data) in an Nnf_EventExposure_UnSubscribe response message to the DCCF. The pending notification events (e.g. collected data) are newly added.

[0398] Step 13. The DCCF can include the received one or more pending unsent events (e.g. collected data) in an Ndccf_DataManagement_UnSubscribe response message to the data consumer. The one or more pending notification events are newly added.

[0399] If other subscriptions are still valid, or the notification endpoint is not the consumer itself, one or more pending notification events can be sent to the specific data notification endpoint in a separate notification message as described in steps 8b and 9b.

[0400] Figure 7b A flow diagram illustrating a subscription-notification method according to another embodiment of the disclosure is shown.

[0401] It can provide enhancements to the handling of pending data collection notifications during data management subscribe / unsubscribe / notification and data collection subscribe / unsubscribe / notification.

[0402] If the data consumer invokes the data source NF (e.g. AMF, SMF, AF Event Exposure) service directly without DCCF interaction, similar procedures between DCCF (as service consumer) and data source NF (as service producer) as in the following flow chart apply.

[0403] Step 1. The data consumer can subscribe to data collection information via DCCF by invoking the Ndccf_DataManagement_Subscribe service operation. A pending notification flag is added. When this pending notification flag is set to true, it indicates that the producer (i.e. DCCF) should report one or more pending unsent events if an exception occurs.

[0404] Step 2. If the consumer does not check user consent, the DCCF can check and handle user consent with UDM.

[0405] Step 3. If the data consumer does not identify the data source instance, the DCCF can determine the data source NF instance that is able to provide the required data information.

[0406] Step 4. The DCCF can determine whether the data requested in step 1 is already being collected. If the data consumer is already collecting the requested data, the DCCF can add the new data consumer to the list of data consumers that are subscribed to that data.

[0407] Step 5. The DCCF can invoke the Nnf_EventExposure_Subscribe service operation to the selected data source NF. A pending notification flag can be added. When the pending notification flag is set to true, it can indicate that the producer (e.g. AMF, SMF, AF, etc.) should report one or more pending unsent events if an exception occurs.

[0408] Steps 6a-6b. When new data is available and the event reporting trigger occurs, the data source NF can notify the DCCF of the collected data by invoking the Nnf_EventExposure_Notify service operation.

[0409] Steps 7a-7b. The DCCF can send the collected data to all the notification endpoints indicated in step 1 using Ndccf_DataManagement_Notify.

[0410] Step 8a. If an exception occurs in the producer (i.e. DCCF) and the DCCF decides to send a termination request in a notification message, one or more pending notification events can be added to the same notification message. The one or more pending notification events are newly added.

[0411] Step 8b. If an exception occurs in the producer (i.e. DCCF), the DCCF can decide to send one or more pending notification events with a pending notification reason in a separate notification message. The one or more pending notification events and the pending notification reason are newly added.

[0412] Step 9. When the data consumer no longer wishes data to be collected, it can send an Ndccf_DataManagement_Unsubscribe request message to the DCCF.

[0413] Step 10. The DCCF can include the received one or more pending unsent events in an Ndccf_DataManagement_UnSubscribe response message to the data consumer. The one or more pending notification events are newly added.

[0414] Other subscriptions to the data source remain valid and the DCCF only processes the one or more pending events for the unsubscribed consumer.

[0415] Embodiments herein can provide a number of advantages, the following is a non-exhaustive list of examples of advantages. In some embodiments herein, the pending notification data (e.g. collection event) can avoid losing the notifications from the NF (e.g. NWDAF / DCCF) when certain exception occurs. In some embodiments herein, it supports the enhancement of the related more refined and very accurate analytics processing (e.g. NWDAF). In some embodiments herein, the pending notification data (e.g. analytics event) can enhance the analytics consumer’s actions based on the related more refined and very accurate analytics output. In some embodiments herein, the added “pending notification flag” in the event reporting information table in clause 4.15.1 of TS 23.502 v18.0.0 and the added usage description can also be commonly used by one or more other NF event open cases that have one or more stored unsent events when an exception occurs, to refine and enhance one or more exception event reporting and the alignment processing with the exception cases. In some embodiments herein, a flexible pending notification processing is proposed. In some embodiments herein, it can enable the event consumer NF to indicate the event producer NF actions on how to handle one or more stored unsent events when an exception occurs. In some embodiments herein, it can enable the event producer NF to effectively handle the pending notification before handling the exception. In some embodiments herein, it can enable a flexible pending notification messaging to minimize the handling impact. Embodiments herein are not limited to the above features and advantages. Additional features and advantages will be recognized by those skilled in the art upon reading the following detailed description.

[0416] Figure 8a is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure. For example, the above-mentioned first NF, second NF, third NF, or event consumer NF can be implemented as or by the apparatus 800.

[0417] The apparatus 800 comprises at least one processor 821 (e.g. a digital processor (DP)) and at least one memory (MEM) 822 coupled to the processor 821. The apparatus 800 can further comprise a transmitter TX and a receiver RX 823 coupled to the processor 821. The MEM 822 stores a program (PROG) 824. The PROG 824 can include instructions which, when executed on the associated processor 821, enable the apparatus 800 to operate in accordance with embodiments of the present disclosure. The combination of at least one processor 821 and at least one MEM 822 can form a processing apparatus 825 suitable for implementing various embodiments of the present disclosure.

[0418] Various embodiments of the present disclosure can be implemented by a computer program executable by one or more of a processor 821, software, firmware, hardware, or combinations thereof.

[0419] The MEM 822 can be of any type suitable to the local technical environment, and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples.

[0420] The processor 821 can be of any type suitable to the local technical environment, and can include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architectures, as non-limiting examples.

[0421] In embodiments where the apparatus is implemented as or at a first NF, the memory 822 stores instructions executable by the processor 821, whereby the first NF is operative to perform any of the methods described above in relation to the first NF.

[0422] In embodiments where the apparatus is implemented as or at a second NF, the memory 822 stores instructions executable by the processor 821, whereby the second NF is operative to perform any of the methods described above in relation to the second NF.

[0423] In embodiments where the apparatus is implemented as or at an event consumer NF, the memory 822 stores instructions executable by the processor 821, whereby the event consumer NF is operative to perform any of the methods described above in relation to the event consumer NF.

[0424] In embodiments where the apparatus is implemented as or at a third NF, the memory 822 stores instructions executable by the processor 821, whereby the third NF is operative to perform any of the methods described above in relation to the third NF.

[0425] Figure 8b is a block diagram illustrating a first NF according to an embodiment of the present disclosure. As shown in the figure, the first NF 830 includes a first receiving module 831, configured to receive a first subscription request from a second NF. The first subscription request can include first information indicating whether an event producer NF is required to send notification data to be processed to an event consumer NF before handling an exception.

[0426] In embodiments, the first NF 830 can further include a first sending module 832, configured to send a second subscription request to a third NF. The second subscription request includes the first information.

[0427] In an embodiment, the first NF 830 can further include a second receiving module 833 configured to receive, from the third NF, a first message including notification data to be processed when an exception occurs in the event producer NF.

[0428] In an embodiment, the first NF 830 can further include a second sending module 834 configured to send, to the second NF, a second message including the notification data to be processed.

[0429] In an embodiment, the first NF 830 can further include a determining module 835 configured to determine that an exception occurs.

[0430] In an embodiment, the first NF 830 can further include a third sending module 836 configured to send, to the second NF or the event consumer NF, a third message including the notification data to be processed based on the first information.

[0431] Figure 8c is a block diagram illustrating a second NF according to an embodiment of the disclosure. As illustrated, the second NF 840 includes a sending module 841 configured to send, to a first NF, a first subscription request. The first subscription request can include first information indicating whether an event producer NF is required to send, to an event consumer NF, notification data to be processed before handling an exception.

[0432] In an embodiment, the second NF 840 can further include a receiving module 842 configured to receive, from the first NF or the event producer NF, a message including notification data to be processed when an exception occurs in the event producer NF.

[0433] Figure 8d is a block diagram illustrating an event consumer NF according to an embodiment of the disclosure. As illustrated, the event consumer NF 850 includes a receiving module 851 configured to receive, from an event producer NF, a message including notification data to be processed when an exception occurs in the event producer NF. The first information can be used to indicate whether the event producer NF is required to send, to the event consumer NF, the notification data to be processed before handling the exception.

[0434] Figure 8e is a block diagram illustrating a first NF according to another embodiment of the disclosure. As illustrated, the first NF 860 includes a first receiving module 861 configured to receive, from a third NF, a first notification message or a first unsubscription response including notification data to be processed. The first notification message can further include second information indicating a notification cause of the notification data to be processed.

[0435] In an embodiment, the first NF 860 can further comprise a first sending module 862 configured to send, to the third NF, a first notification response message comprising information indicating whether the consumer instance is to retrieve the stored data or analytics before deletion.

[0436] In an embodiment, the first NF 860 can further comprise a second sending module 863 configured to send, to the second NF, a second notification message or a second unsubscribe response comprising the notification data to be processed. The second notification message can further comprise second information indicating a notification cause of the notification data to be processed.

[0437] In an embodiment, the first NF 860 can further comprise a second receiving module 864 configured to receive, from the second NF, a second notification response message comprising information indicating whether the consumer instance is to retrieve the stored data or analytics before deletion.

[0438] Figure 8f is a block diagram illustrating a third NF according to another embodiment of the disclosure. As shown, the third NF 870 comprises a sending module 871 configured to send, to the first NF, a first notification message or a first unsubscribe response comprising the notification data to be processed. The first notification message can further comprise second information indicating a notification cause of the notification data to be processed.

[0439] In an embodiment, the third NF 870 can further comprise a receiving module 872 configured to receive, from the first NF, a first notification response message comprising information indicating whether the consumer instance is to retrieve the stored data or analytics before deletion.

[0440] The term unit or module can have the conventional meaning in the field of electronics, electrical and / or electronic devices and can include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer program or instructions for executing a corresponding task, process, computation, outputting and / or displaying function, and the like, such as those described herein.

[0441] Using the functional units, the first NF, the second NF, the third NF or the event consumer NF can not need a fixed processor or memory, and can arrange any computing resource and storage resource from the first NF, the second NF, the third NF or the event consumer NF in the communication system. The introduction of virtualization technology and network computing technology can improve the use efficiency of network resources and the flexibility of the network.

[0442] According to an aspect of the present disclosure, there is provided a computer program product tangibly stored on a computer readable storage medium and comprising instructions which, when executed on at least one processor, cause the at least one processor to perform any of the above methods.

[0443] According to an aspect of the present disclosure, there is provided a computer readable storage medium storing instructions which, when executed on at least one processor, cause the at least one processor to perform any of the above methods.

[0444] Embodiment 1. A method (300) performed by a first network function (NF), comprising:

[0445] receiving (302) a first subscription request from a second NF, wherein the first subscription request comprises first information indicating whether a producer NF is required to send pending notification data to a consumer NF before handling an exception.

[0446] Embodiment 2. The method of embodiment 1, wherein the first information comprises a pending notification flag.

[0447] Embodiment 3. The method of embodiment 2, wherein:

[0448] when the pending notification flag is set to true, it indicates that the producer NF is required to send pending notification data to the consumer NF before handling the exception; and / or

[0449] when the pending notification flag is set to false or is absent, it indicates that the producer NF is not required to send pending notification data to the consumer NF before handling the exception.

[0450] Embodiment 4. The method of any of embodiments 1-3, wherein the exception comprises at least one of:

[0451] the producer NF is unable to handle analytics;

[0452] the producer NF is unable to handle event data;

[0453] the producer NF receives a request to unsubscribe;

[0454] the producer NF decides to send a termination request;

[0455] event data cannot be collected;

[0456] the subscription is transferred;

[0457] the DCCF is unable to handle analytics data or collected data; or

[0458] The aggregator NWDAF is unable to process the analytics.

[0459] Embodiment 5. The method of any of embodiments 1-4, wherein the notification data to be processed comprises at least one stored unsent event.

[0460] Embodiment 6. The method of any of embodiments 1-5, further comprising:

[0461] sending (312) a second subscription request to the third NF, wherein the second subscription request comprises the first information.

[0462] Embodiment 7. The method of embodiment 6, further comprising:

[0463] receiving (322), from the third NF, a first message comprising the notification data to be processed when an exception occurs in the event producer NF; and

[0464] sending (324) a second message comprising the notification data to be processed to the second NF.

[0465] Embodiment 8. The method of embodiment 7, wherein the first message and / or the second message further comprises second information indicating a notification cause of the notification data to be processed.

[0466] Embodiment 9. The method of embodiment 8, wherein the notification cause of the notification data to be processed comprises at least one of:

[0467] an exception occurs in the event producer NF;

[0468] the event producer NF is unable to process the analytics;

[0469] the event producer NF is unable to process the event data;

[0470] the event producer NF receives a cancel subscription request;

[0471] the event producer NF decides to send a termination request;

[0472] the event data cannot be collected;

[0473] the subscription is transferred;

[0474] the DCCF is unable to process the analytics data or collected data; or

[0475] the aggregator NWDAF is unable to process the analytics.

[0476] Example 10. The method of any of embodiments 7-9, wherein the first message and / or the second message comprises at least one of:

[0477] a notification message, or

[0478] a cancel subscription response.

[0479] Example 11. The method of embodiment 10, wherein the notification message comprises at least one of:

[0480] a data management notification message,

[0481] an analytics subscription notification message, or

[0482] an event exposure notification message.

[0483] Example 12. The method of embodiment 10 or 11, wherein the notification message comprises a termination request.

[0484] Example 13. The method of any of embodiments 6-12, wherein the second subscription request comprises at least one of:

[0485] a data management subscription request,

[0486] an analytics subscription request, or

[0487] an event exposure subscription request.

[0488] Example 14. The method of any of embodiments 6-13, wherein the third NF comprises at least one of:

[0489] an analytics data repository function (ADRF),

[0490] an aggregator NWDAF,

[0491] a data collection coordination (DCCF),

[0492] a network data analytics function (NWDAF),

[0493] a network exposure function (NEF),

[0494] an access and mobility management function (AMF),

[0495] a session management function (SMF),

[0496] a unified data management (UDM),

[0497] a network slice admission control function (NSACF),

[0498] an application function (AF),

[0499] a policy control function (PCF), or

[0500] a user plane function (UPF).

[0501] Embodiment 15. The method of any of embodiments 1-5, further comprising:

[0502] determining (332) that an exception occurred; and

[0503] based on the first information, sending (334), to the second NF or an event consumer NF, a third message including notification data to be processed.

[0504] Embodiment 16. The method of embodiment 15, wherein the third message further includes third information indicating a notification cause of the notification data to be processed.

[0505] Embodiment 17. The method of embodiment 16, wherein the notification cause of the notification data to be processed includes at least one of:

[0506] an exception occurred in the event producer NF;

[0507] the event producer NF is unable to process analytics;

[0508] the event producer NF is unable to process event data;

[0509] the event producer NF received a request to cancel a subscription;

[0510] the event producer NF decided to send a termination request;

[0511] event data cannot be collected;

[0512] a subscription was transferred;

[0513] the DCCF is unable to process analytics data or collected data; or

[0514] the aggregator NWDAF is unable to process analytics.

[0515] Embodiment 18. The method of any of embodiments 15-17, wherein the third message includes at least one of:

[0516] a notification message, or

[0517] a cancel subscription response.

[0518] Embodiment 19. The method of embodiment 18, wherein the notification message includes at least one of:

[0519] a data management notification message,

[0520] analyzing the subscription notification message, or

[0521] an event exposure notification message.

[0522] Embodiment 20. The method of embodiment 18 or 19, wherein the notification message comprises a termination request.

[0523] Embodiment 21. The method of any of embodiments 1-20, wherein the first subscription request comprises at least one of:

[0524] a data management subscription request,

[0525] an analytics subscription request, or

[0526] an event exposure subscription request.

[0527] Embodiment 22. The method of any of embodiments 1-21, wherein at least one of the first NF or the second NF or the event producer NF or the event consumer NF comprises at least one of:

[0528] an analytics data repository function (ADRF),

[0529] an aggregator NWDAF,

[0530] a data collection coordination (DCCF),

[0531] a network data analytics function (NWDAF),

[0532] a network exposure function (NEF),

[0533] an access and mobility management function (AMF),

[0534] a session management function (SMF),

[0535] a unified data management (UDM),

[0536] a network slice admission control function (NSACF),

[0537] an application function (AF),

[0538] a policy control function (PCF), or

[0539] a user plane function (UPF).

[0540] Embodiment 23. A method (400) performed by a second network function (NF), comprising:

[0541] sending (402) a first subscription request to a first NF, wherein the first subscription request comprises first information indicating whether a event producer NF is required to send pending notification data to an event consumer NF before handling an exception.

[0542] Embodiment 24. The method of embodiment 23, wherein the first information comprises a pending notification flag.

[0543] Embodiment 25. The method of embodiment 24, wherein

[0544] when the pending notification flag is set to true, it indicates that the event producer NF is required to send pending notification data to the event consumer NF before handling an exception; and / or

[0545] when the pending notification flag is set to false or is not present, it indicates that the event producer NF is not required to send pending notification data to the event consumer NF before handling an exception.

[0546] Embodiment 26. The method of any of embodiments 23-25, wherein the exception comprises at least one of:

[0547] the event producer NF is unable to handle analytics;

[0548] the event producer NF is unable to handle event data;

[0549] the event producer NF receives a cancel subscription request;

[0550] the event producer NF decides to send a termination request;

[0551] the event data cannot be collected;

[0552] the subscription is transferred;

[0553] the DCCF is unable to handle analytics data or collected data; or

[0554] the aggregator NWDAF is unable to handle analytics.

[0555] Embodiment 27. The method of any of embodiments 23-26, wherein the pending notification data comprises at least one stored unsent event.

[0556] Embodiment 28. The method of any of embodiments 23-27, further comprising:

[0557] receiving (412) a message comprising the pending notification data from the first NF or the event producer NF when an exception occurs for the event producer NF.

[0558] Embodiment 29. The method of embodiment 28, wherein the message further comprises fourth information indicating a notification cause of the notification data to be processed.

[0559] Embodiment 30. The method of embodiment 29, wherein the notification cause of the notification data to be processed comprises at least one of:

[0560] an exception occurred in the event producer NF;

[0561] the event producer NF is unable to process analytics;

[0562] the event producer NF is unable to process event data;

[0563] the event producer NF receives a cancel subscription request;

[0564] the event producer NF decides to send a termination request;

[0565] event data cannot be collected;

[0566] the subscription is transferred;

[0567] the DCCF is unable to process analytics data or collected data; or

[0568] the aggregator NWDAF is unable to process analytics.

[0569] Embodiment 31. The method of any of embodiments 28-30, wherein the message comprises at least one of:

[0570] a notification message, or

[0571] a cancel subscription response.

[0572] Embodiment 32. The method of embodiment 31, wherein the notification message comprises at least one of:

[0573] a data management notification message,

[0574] an analytics subscription notification message, or

[0575] an event exposure notification message.

[0576] Embodiment 33. The method of embodiment 31 or 32, wherein the notification message comprises a termination request.

[0577] Embodiment 34. The method of any of embodiments 23-33, wherein the first subscription request comprises at least one of:

[0578] a data management subscription request,

[0579] an analytics subscription request, or

[0580] event exposure subscription request.

[0581] Embodiment 35. The method of any of embodiments 23-34, wherein at least one of the first NF or the second NF or the event producer NF or the event consumer NF comprises at least one of:

[0582] an analytics data repository function (ADRF),

[0583] a data collection coordination (DCCF),

[0584] a network data analytics function (NWDAF),

[0585] a network exposure function (NEF),

[0586] an access and mobility management function (AMF),

[0587] a session management function (SMF),

[0588] a unified data management (UDM),

[0589] a gateway mobile location center (GMLC),

[0590] a network slice admission control function (NSACF),

[0591] an application function (AF),

[0592] a service communication proxy (SCP),

[0593] a policy control function (PCF), or

[0594] a user plane function (UPF).

[0595] Embodiment 36. A method (500) performed by an event consumer NF, comprising:

[0596] receiving (502), from an event producer NF, a message comprising notification data to be processed when the event producer NF experiences an exception,

[0597] wherein the first information is used to indicate whether the event producer NF is required to send the notification data to be processed to the event consumer NF before processing the exception.

[0598] Embodiment 37. The method of embodiment 36, wherein the first information comprises a pending notification flag.

[0599] Embodiment 38. The method of embodiment 37, wherein

[0600] When the pending notification flag is set to true, it indicates that the event producer NF is required to send the pending notification data to the event consumer NF before handling the exception; and / or

[0601] When the pending notification flag is set to false or not present, it indicates that the event producer NF is not required to send the pending notification data to the event consumer NF before handling the exception.

[0602] Embodiment 39. The method of any of embodiments 36-38, wherein the exception comprises at least one of:

[0603] The event producer NF is unable to handle analytics;

[0604] The event producer NF is unable to handle event data;

[0605] The event producer NF receives a cancel subscription request;

[0606] The event producer NF decides to send a termination request;

[0607] The event data cannot be collected;

[0608] The subscription is transferred;

[0609] The DCCF is unable to handle analytics data or collected data; or

[0610] The aggregator NWDAF is unable to handle analytics.

[0611] Embodiment 40. The method of any of embodiments 36-39, wherein the pending notification data comprises at least one stored unsent event.

[0612] Embodiment 41. The method of any of embodiments 36-40, wherein the message further comprises fifth information indicating a notification cause of the pending notification data.

[0613] Embodiment 42. The method of embodiment 41, wherein the notification cause of the pending notification data comprises at least one of:

[0614] An exception occurs in the event producer NF;

[0615] The event producer NF is unable to handle analytics;

[0616] The event producer NF is unable to handle event data;

[0617] The event producer NF receives a cancel subscription request;

[0618] The event producer NF decides to send a termination request;

[0619] Event data cannot be collected; or

[0620] The subscription is transferred.

[0621] Embodiment 43. The method of any of embodiments 36-42, wherein the message comprises at least one of:

[0622] a notification message; or

[0623] a subscription cancellation response.

[0624] Embodiment 44. The method of embodiment 43, wherein the notification message comprises at least one of:

[0625] a data management notification message,

[0626] an analytics subscription notification message, or

[0627] an event exposure notification message.

[0628] Embodiment 45. The method of embodiment 43 or 44, wherein the notification message comprises a termination request.

[0629] Embodiment 46. The method of any of embodiments 36-45, wherein the event producer NF or the event consumer NF comprises at least one of:

[0630] an analytics data repository function (ADRF),

[0631] an aggregator NWDAF,

[0632] a data collection coordination (DCCF),

[0633] a network data analytics function (NWDAF),

[0634] a network exposure function (NEF),

[0635] an access and mobility management function (AMF),

[0636] a session management function (SMF),

[0637] a unified data management (UDM),

[0638] a network slice admission control function (NSACF),

[0639] an application function (AF),

[0640] a policy control function (PCF), or

[0641] a user plane function (UPF).

[0642] Example 47. A first NF (800) comprising:

[0643] a processor (821); and

[0644] a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the first NF (800) is operable to:

[0645] receive, from a second NF, a first subscription request, wherein the first subscription request comprises first information indicating whether an event producer NF is required to send, to an event consumer NF, notification data to be processed before handling an exception.

[0646] Example 48. The first NF of example 47, wherein the first NF is further operable to perform the method of any of examples 2-22.

[0647] Example 49. A second NF (800) comprising:

[0648] a processor (821); and

[0649] a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the second NF (800) is operable to:

[0650] send, to a first NF, a first subscription request, wherein the first subscription request comprises first information indicating whether an event producer NF is required to send, to an event consumer NF, notification data to be processed before handling an exception.

[0651] Example 50. The second NF of example 49, wherein the second NF is further operable to perform the method of any of examples 24-35.

[0652] Example 51. An event consumer NF (800) comprising:

[0653] a processor (821); and

[0654] a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the event consumer NF (800) is operable to:

[0655] receive, from an event producer NF, a message comprising notification data to be processed when the event producer NF experiences an exception;

[0656] The first information is used to indicate whether the event producer NF is required to send notification data to be processed to the event consumer NF before processing the exception.

[0657] Example 52. The event consumer NF of Example 51, wherein the event consumer NF is further operable to perform the method of any one of Examples 37-46.

[0658] Example 53. A computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method of any one of Examples 1-46.

[0659] Example 54. A computer program product comprising instructions which, when executed by at least one processor, cause the at least one processor to carry out the method of any one of Examples 1-46.

[0660] Furthermore, the disclosure can also provide a carrier containing the above computer program, wherein the carrier is one of an electronic signal, an optical signal, a radio signal or a computer readable storage medium. The computer readable storage medium can be, for example, an optical disc or an electronic storage device such as a RAM (Random Access Memory), a ROM (Read-Only Memory), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray disc, etc.

[0661] The techniques described herein can be implemented by various means depending upon the application. For example, these techniques can be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof. For a firmware or software implementation, the

[0662] The exemplary embodiments herein have been described above with reference to flowchart illustrations and block diagrams of methods and apparatuses. It will be understood that each block of the flowchart illustrations and block diagrams, and combinations of blocks in the flowchart illustrations and block diagrams, can be implemented by various means, including computer program instructions. These computer program instructions can be loaded into one or more general purpose computers, special purpose computers, or other programmable data processing apparatuses to produce a machine, such that the instructions which execute on the computer(s) or other programmable data processing apparatuses create means for implementing the functions specified in the flowchart block or blocks.

[0663] Moreover, while operations are depicted in a particular order, this should not be understood as requiring such an order, nor that all illustrated operations be performed, to implement desirable results. In certain circumstances, multitasking and parallel processing can be advantageous. Likewise, while several specific implementation details are contained in the above discussion, these should not be construed as limiting the scope of the subject matter described herein, but merely as describing aspects of certain implementations. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination.

[0664] While the specification contains many specific implementation details, these should not be construed as limiting the scope of any implementations or of what can be claimed, but as describing features that can be specific to particular implementations. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features can be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination and the claimed combination can be directed to a sub-combination or a variation of a sub-combination.

[0665] It will be apparent to those skilled in the art that, with the advance of technology, the inventive concept can be implemented in various ways. The foregoing embodiments are given for descriptive purposes only and, therefore, should not be taken in a limiting sense as the present disclosure should be limited only by the appended claims. As will be apparent to those skilled in the art, modifications and variations can be made without departing from the spirit and scope of the present disclosure. Such modifications and variations are considered to be within the scope of the present disclosure and the appended claims. The scope of the present disclosure is defined by the appended claims.

Claims

1. A method (340) performed by a first network function, NF, comprising: receiving (342), from a third NF, a first notification message or a first unsubscription response comprising notification data to be processed, wherein the first notification message further comprises second information indicating a notification cause of the notification data to be processed.

2. The method of claim 1, wherein, The first notification message further comprises information informing a consumer instance when data or analytics will be deleted.

3. The method of claim 2, further comprising: sending (352), to the third NF, a first notification response message comprising information indicating whether the consumer instance will retrieve stored data or analytics before deletion.

4. The method of any of claims 1-3, further comprising: sending (362), to a second NF, a second notification message or a second unsubscription response comprising the notification data to be processed, wherein the second notification message further comprises the second information indicating the notification cause of the notification data to be processed.

5. The method of claim 4, wherein, The second notification message further comprises information informing a consumer instance when data or analytics will be deleted.

6. The method of claim 5, further comprising: receiving (372), from the second NF, a second notification response message comprising information indicating whether the consumer instance will retrieve stored data or analytics before deletion.

7. The method of any one of claims 4-6, wherein, The first NF and / or the second NF comprises at least one of: an analytics data repository function, ADRF, a aggregator, NWDAF, a data collection coordination, DCCF, a network data analytics function, NWDAF, a network exposure function, NEF, an access and mobility management function, AMF, a session management function, SMF, a unified data management, UDM, a network slice admission control function, NSACF, an application function, AF, a policy control function, PCF, or a user plane function, UPF.

8. The method of any one of claims 1-7, wherein, The notification cause of the notification data to be processed comprises at least one of: an exception occurred in the event producer NF, the event producer NF is not able to process analytics, the event producer NF is not able to process event data, the event producer NF received an unsubscription request, the event producer NF decided to send a termination request, event data cannot be collected, a subscription is transferred, a DCCF is not able to process the analytics data or collected data, or an aggregator, NWDAF, is not able to process the analytics.

9. The method of any one of claims 1-8, wherein, The notification message comprises at least one of: a data management notification message; an analytics subscription notification message; or an event exposure notification message.

10. The method of any one of claims 1-9, wherein, The notification message comprises a termination request.

11. The method of any one of claims 1-10, wherein, The third NF comprises at least one of: an analytics data repository function, ADRF, a aggregator, NWDAF, a data collection coordination, DCCF, a network data analytics function, NWDAF, a network exposure function, NEF, an access and mobility management function, AMF, a session management function, SMF, a unified data management, UDM, a network slice admission control function, NSACF, an application function, AF, a policy control function, PCF, or a user plane function, UPF. User Plane Function, UPF.

12. A method (420) performed by a third Network Function, NF, comprising: sending (422), to a first NF, a first notification message or a first unsubscription response comprising notification data to be processed, wherein the first notification message further comprises second information indicating a notification cause of the notification data to be processed.

13. The method of claim 12, wherein, The first notification message further comprises information informing a consumer instance when data or analytics will be deleted.

14. The method of claim 13, further comprising: receiving (432), from the first NF, a first notification response message comprising information indicating whether the consumer instance will retrieve stored data or analytics before deletion.

15. The method of any one of claims 12-14, wherein, The first NF comprises at least one of: an Analytics Data Repository Function, ADRF, a Aggregator, NWDAF, a Data Collection Coordination, DCCF, a Network Data Analytics Function, NWDAF, a Network Exposure Function, NEF, an Access and Mobility Management Function, AMF, a Session Management Function, SMF, a Unified Data Management, UDM, a Network Slice Admission Control Function, NSACF, an Application Function, AF, a Policy Control Function, PCF, or a User Plane Function, UPF.

16. The method of any one of claims 12-15, wherein, The notification cause of the notification data to be processed comprises at least one of: an exception occurred in the event producer NF; the event producer NF cannot handle analytics; the event producer NF cannot handle event data; the event producer NF received an unsubscription request; the event producer NF decided to send a termination request; event data cannot be collected; a subscription was transferred; a DCCF cannot handle the analytics data or collected data; or a Aggregator, NWDAF, cannot handle the analytics. The notification message comprises at least one of:

17. The method of any one of claims 12-16, wherein, a Data Management notification message; an Analytics Subscription notification message; or an Event Exposure notification message. The notification message comprises a termination request.

18. The method of any one of claims 12-17, wherein, The third NF comprises at least one of:

19. The method of any one of claims 12-18, wherein, an Analytics Data Repository Function, ADRF, a Aggregator, NWDAF, a Data Collection Coordination, DCCF, a Network Data Analytics Function, NWDAF, a Network Exposure Function, NEF, an Access and Mobility Management Function, AMF, a Session Management Function, SMF, a Unified Data Management, UDM, a Network Slice Admission Control Function, NSACF, an Application Function, AF, a Policy Control Function, PCF, or a User Plane Function, UPF.

20. A first NF (800) comprising: a processor (821); and a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the first NF (800) is operative to: receive, from a third NF, a first notification message or a first unsubscription response comprising notification data to be processed, wherein the first notification message further comprises second information indicating a notification cause of the notification data to be processed. The first NF is further operative to perform the method of any one of claims 2 to 11.

22. A third NF (800) comprising:

21. The first NF of claim 20, wherein, ​ ​ a processor (821); and a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821) whereby the third NF (800) is operable to: send, to a first NF, a first notification message or a first unsubscribe response including notification data to be processed, wherein the first notification message further includes second information indicating a notification cause of the notification data to be processed.

23. The third NF of claim 22, wherein, the third NF is further operable to perform the method of any one of claims 13-19.

24. A computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1-19.

25. A computer program product comprising instructions that, when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1-19.

Images