Method and apparatus for minimizing notification reports by a user plane function entity in a communication system

WO2026235529A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096757
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-08
Publication Date
2026-11-12

Smart Images

  • Figure KR2026096757_12112026_PF_FP_ABST
    Figure KR2026096757_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. In an embodiment, a method performed by a user plane function (UPF) entity in a wireless communication system is provided. The method includes: receiving a first message related to a first event subscription and a second message related to a second event subscription, wherein the first message and the second message include aggregation information for aggregating event notifications; detecting a first event corresponding to the first event subscription and a second event corresponding to the second event subscription; generating, based on the aggregation information, a single notification message by combining a first event report for the first event and a second event report for the second event; and transmitting, to a notification target network entity, the single notification message.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR MINIMIZING NOTIFICATION REPORTS BY A USER PLANE FUNCTION ENTITY IN A COMMUNICATION SYSTEM

[0001] An embodiment of the present disclosure relates to a method and apparatus for minimizing notification reports by a user plane function entity (UPF) in a communication system.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The present disclosure provides a method and apparatus for minimizing notification reports by a UPF in a communication system.

[0009] In an embodiment, a method performed by a user plane function (UPF) entity in a wireless communication system is provided. The method includes: receiving a first message related to a first event subscription and a second message related to a second event subscription, wherein the first message and the second message include aggregation information for aggregating event notifications; detecting a first event corresponding to the first event subscription and a second event corresponding to the second event subscription; generating, based on the aggregation information, a single notification message by combining a first event report for the first event and a second event report for the second event; and transmitting, to a notification target network entity, the single notification message.

[0010] According to the present disclosure, a method and apparatus for minimizing notification reports by a UPF in a communication system is provided.

[0011] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

[0012] Figure 1 illustrates an event exposure service between a user plane function (UPF) and a network function (NF) service consumer in a communication system according to an embodiment of the present disclosure.

[0013] Figure 2 illustrates an event exposure service procedure in which UPFs transmit separate notification messages for respective event subscriptions.

[0014] Figure 3 illustrates an event exposure service procedure in which a network entity transmitting messages for subscribing to UPF event reports is different from an NF service consumer receiving notification messages.

[0015] Figure 4 illustrates an event exposure service procedure using a notification aggregation reference ID according to an embodiment of the present disclosure.

[0016] Figure 5 illustrates an event exposure service procedure using a notification aggregation indication according to an embodiment of the present disclosure.

[0017] Figure 6 illustrates an event exposure service procedure using a notification correlation ID according to an embodiment of the present disclosure.

[0018] Figure 7 illustrates an event exposure service procedure in which a UPF aggregates event reports based on a notification aggregation reference ID and max_delay information according to an embodiment of the present disclosure.

[0019] Figure 8 illustrates an event exposure service procedure in which event reports are separately transmitted when an event trigger for another subscription does not occur within a max_delay duration according to an embodiment of the present disclosure.

[0020] Figure 9 illustrates an event exposure service procedure in which event reports are partially aggregated based on a notification aggregation reference ID and max_delay information according to an embodiment of the present disclosure.

[0021] Figure 10 illustrates an event exposure service procedure in which an NF service consumer subscribes to UPF event reports or UPF data via a PCF according to an embodiment of the present disclosure.

[0022] Figure 11 illustrates an event exposure service procedure in which an NF service consumer subscribes to UPF event reports or UPF data via a PCF using a notification aggregation indication according to an embodiment of the present disclosure.

[0023] Figure 12 illustrates an event exposure service procedure in which a UPF registers information on a capability of notification aggregation with an NRF and an NF service consumer discovers a UPF supporting the capability of notification aggregation according to an embodiment of the present disclosure.

[0024] Figure 13 illustrates an event exposure service procedure in which an NF service consumer subscribes to UPF event reports or UPF data via an SMF according to an embodiment of the present disclosure.

[0025] Figure 14 illustrates a method performed by a UPF entity in a communication system according to an embodiment of the present disclosure.

[0026] Figure 15 illustrates a method performed by a UPF entity for aggregating event reports based on delay information according to an embodiment of the present disclosure.

[0027] Figure 16 is a block diagram of a base station (BS) according to an embodiment of the disclosure.

[0028] Figure 17 is a block diagram of a network entity according to an embodiment of the disclosure.

[0029] In an embodiment, a method performed by a user plane function (UPF) entity in a wireless communication system is provided. The method includes: receiving a first message related to a first event subscription and a second message related to a second event subscription, wherein the first message and the second message include aggregation information for aggregating event notifications; detecting a first event corresponding to the first event subscription and a second event corresponding to the second event subscription; generating, based on the aggregation information, a single notification message by combining a first event report for the first event and a second event report for the second event; and transmitting, to a notification target network entity, the single notification message.

[0030] In an embodiment, a user plane function (UPF) entity is provided. The UPF entity includes: at least one processor; and at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UPF entity to: receive a first message related to a first event subscription and a second message related to a second event subscription, wherein the first message and the second message include aggregation information for aggregating event notifications, detect a first event corresponding to the first event subscription and a second event corresponding to the second event subscription, generate, based on the aggregation information, a single notification message by combining a first event report for the first event and a second event report for the second event, and transmit, to a notification target network entity, the single notification message.

[0031] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0032] In describing the embodiments, while numerous details are set forth for the purpose of illustration, it is understood that some aspects of the disclosure may be practiced with less than all of these details. Numerous variations and alternatives to the details provided herein are possible and are considered within the scope of the disclosure. In some instances, descriptions related to technical contents well-known in the art may be omitted so as to not obscure an understanding of the disclosure, and such omitted descriptions are understood to be within the scope of the disclosure.

[0033] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0034] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described herein in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth herein, but may be implemented in various different forms. Other features, aspects, and advantages of the subject matter described herein will become apparent from the disclosure. The following embodiments are merely examples to aid in an understanding of the disclosure and should not be construed to narrow the scope or spirit of the subject matter described herein in any way, but on the contrary, the disclosure covers all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims and equivalents thereof. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, terms which will be described herein are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0035] Herein, it will be understood that each block of flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0036] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0037] As used in embodiments of the disclosure, a “~unit / module” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit / module” does not always have a meaning limited to software or hardware. The “~unit / module” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit / module” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit / module” may be either combined into a smaller number of components and a “~unit / module,” or divided into additional components and a “~unit / module.” Moreover, the components and “~units / modules” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit / module” may include one or more processors.

[0038] The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0039] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the operating system, in order to control the overall operation of the device. Also, the one processor or the combination of processors is also capable of executing other processes and programs resident in the memory, such as processes for the disclosure.

[0040] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0041] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0042] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0043] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0044] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0045] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0046] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0047] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0048] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0049] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0050] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0051] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0052] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0053] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0054] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure. If a method step (e.g. transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as “in case that ~” or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state “~” (e.g. a bit length is above X), and then perform the method step in response to said determination.

[0055] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0056] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0057] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0058] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0059] In the embodiments of the present disclosure described herein, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0060] The drawings or flowcharts described herein illustrate example methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0061] The process of the flowchart may be performed by a device. One or more of the steps of the flowchart can be implemented by one or more processors / computer programs executing instructions to perform the noted functions.

[0062] The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0063] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0064] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0065] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms describedherein, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) or similar technical specifications, e.g., from the European telecommunications standards institute (ETSI), where appropriate.

[0066] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a wireless access unit, a BS controller, or a node on a network.

[0067] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5th generation (5G) base station architectures in which such CU and DU functional splits are implemented.

[0068] A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing communication functions.

[0069] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.

[0070] Furthermore, hereinafter, 5G mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0071] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0072] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), RRC, or MAC control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.

[0073] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), DCI, UE-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0074] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0075] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0076] Figure 1 illustrates an event exposure service between a user plane function (UPF) and a network function (NF) service consumer in a communication system according to an embodiment of the present disclosure.

[0077] Referring to Figure 1, a UPF (12) is a core network entity and may perform packet routing and forwarding, packet inspection, quality of service (QoS) handling, and traffic measurement and reporting within the user plane. In a service-based architecture (SBA) where control plane and user plane functions are separated, the UPF (12) may provide services to one or more network functions (NFs) through the Nupf service-based interface. The UPF (12) may provide a Nupf_EventExposure service, through which an NF service consumer (11) may subscribe to UPF events and receive notifications corresponding to such events. The NF service consumer (11) may include a session management function (SMF), a network data analytics function (NWDAF), or an application function (AF). The UPF (12) may monitor status changes or measurable information occurring during user traffic processing, generate corresponding event reports, and expose the event reports to the NF service consumer (11) through appropriate service operations.

[0078] A Nupf_EventExposure service may allow the NF service consumer (11) to subscribe to specific events at the UPF (12) and receive notifications when the events occur. According to 3GPP TS 29.564, Nupf_EventExposure service may be used to expose various UPF events, including QoS monitoring, user data usage measurements (e.g., volume, throughput), user data usage trend statistics, Time Sensitive Communication (TSC) management information, UE NAT mapping information, and payload header handling information. The NF service consumer (11) may utilize such event data or measurement information from the UPF (12), for example, for network optimization, policy-related processing, or analytics performed by an NWDAF.

[0079] In an embodiment, the NF service consumer (11) may create an event exposure subscription at the UPF by invoking a Nupf_EventExposure Subscribe operation (110). The NF service consumer (11), such as an AF or NWDAF, may transmit an Nupf_EventExposure_Subscribe request message to the UPF (12). The Nupf_EventExposure_Subscribe request message may be transmitted by using an HTTP POST method. The subscription request message may include information for identifying the target User Equipment (UE) (e.g., UE IP address, SUPI, or an "Any UE" indicator), the specific event types to be monitored, the granularity of measurement (e.g., per flow, per session, per application), and the event reporting mode (e.g., one-time, periodic, or continuous / event-triggered reporting). The subscription request message may further include an event notification URI, which indicates a target address for the UPF to send notifications, and a notification correlation ID, which allows the NF service consumer (11) to correlate received notifications with a corresponding subscription.

[0080] Upon receiving the subscription request message, the UPF (12) may create a subscription resource or subscription context for monitoring the specified event. The UPF (12) may transmit a Nupf_EventExposure_Subscribe response message to the NF service consumer (11). In an embodiment, when an immediate report flag is included in the subscription request message and a current status of the subscribed event is available, the UPF (12) may include an immediate report of the current event status in the response message. Alternatively, when the current status is not included in the response message, the UPF (12) may generate a report for the subscribed event and transmit a notification message to the NF service consumer (11).

[0081] In an embodiment, the subscription may be provided to the UPF (12) via an SMF. For example, an NF service consumer (11) may create or request a UPF-related event subscription through the SMF, and the SMF may provide subscription-related information to the UPF (12). Accordingly, the SMF may act as an intermediary between the NF service consumer (11) and the UPF (12) for subscription creation or provisioning. Even in this case, the UPF (12) may transmit a notification directly to the actual NF service consumer (11) indicated by the subscription. Therefore, the present disclosure may be applied both to a case where the NF service consumer (11) directly subscribes to the UPF (12) and to a case where subscription-related information is delivered to the UPF (12) through another network function, such as the SMF.

[0082] Once the subscription has been established, the UPF (12) may monitor the subscribed UPF event, collect UPF-related data, or detect an event corresponding to the subscription. When the subscribed event occurs, or when a reporting condition is satisfied, the UPF (12) may generate one or more event reports and transmit a Nupf_EventExposure Notify message including the one or more event reports to the notification target indicated in the subscription. The notification message may be transmitted to the event notification URI provided during the subscription phase using the HTTP POST method. The notification message may include, for example, NotificationData, one or more NotificationItems, event report information, and a notification correlation identifier. The notification correlation identifier may enable the NF service consumer (11) to associate the received notification with a corresponding subscription.

[0083] The NF service consumer (11) may transmit an acknowledgment to confirm successful receipt.

[0084] In an embodiment, a single NF service consumer (11) may be associated with multiple subscriptions. For example, an AF or NWDAF may request monitoring of multiple UEs, multiple PDU sessions, multiple event types, or multiple related data collection targets. In such a case, the UPF (12) may receive multiple subscriptions associated with the same NF service consumer (11). Each subscription may correspond to a different target or reporting condition, but the subscriptions may be related in terms of a reporting destination, a consumer identity, a monitored service context, or a common reporting purpose. Accordingly, when multiple event reports are generated for related subscriptions, the UPF (12) may handle the event reports in a manner that improves notification reporting efficiency. In the present disclosure, such a relationship may be used as a technical basis for aggregating or combining event reports associated with multiple subscriptions into a single notification message.

[0085] In an embodiment, the UPF (12) may transmit a separate notification message (e.g., an HTTP notification) for each of different event subscriptions that have been subscribed to the UPF (12). Even when the different event subscriptions are related to each other, the UPF (12) may need to transmit a separate notification message (e.g., a Nupf_EventExposure_Notify message) for each event related to each event subscription. For example, even when notification target addresses for all of the subscriptions are the same, the UPF may transmit separate notification messages respectively corresponding to the different event subscriptions.

[0086] The present disclosure provides a solution in which a NF service consumer (11) of UPF events, or a NF service consumer (11) of UPF data, can indicate to the UPF (12), or to another entity such as an SMF, that reports for multiple event subscriptions are to be aggregated or combined together into a single notification message. Accordingly, instead of transmitting separate notification messages respectively corresponding to a plurality of event subscriptions, the UPF (12) may generate and transmit a single notification message including event reports associated with the plurality of event subscriptions.

[0087] In an embodiment, the NF service consumer (11) may include a Notification aggregation ID in one or more messages related to event subscriptions. The Notification aggregation ID may indicate to the UPF that notifications or reports are to be combined together for event subscriptions that include the same notification aggregation ID and / or include the same target URI. Accordingly, when a plurality of event subscriptions include the same notification aggregation ID, the UPF may determine that event reports corresponding to the plurality of event subscriptions can be aggregated or combined into a single notification message.

[0088] In an embodiment, the NF service consumer (11) may include a notification aggregation indication in one or more messages related to event subscriptions. The notification aggregation indication may indicate to the UPF that notifications or reports are to be combined together for event subscriptions that include the notification aggregation indication and / or include the same target URI. Accordingly, when a plurality of event subscriptions include the notification aggregation indication, the UPF may determine whether to aggregate or combine event reports corresponding to the plurality of event subscriptions into a single notification message, for example, based on whether the plurality of event subscriptions have the same target URI.

[0089] In an embodiment, the NF service consumer (11) may include the same “notification correlation ID” in multiple messages, for example, event subscription messages transmitted toward the UPF. The same “notification correlation ID” may indicate to the UPF that notifications or reports are to be combined together for event subscriptions that include the same “notification correlation ID” and / or include the same target URI. Accordingly, the UPF may use the notification correlation ID not only for correlating a notification with a corresponding event subscription, but also as information for determining whether event reports associated with multiple event subscriptions are to be combined into a single notification message.

[0090] In an embodiment, the NF service consumer (11) may include information of multiple target sessions or UE IDs in one subscription message transmitted toward the UPF. In this case, the UPF may combine notifications or reports together for all of the target sessions or UE IDs included in the one subscription message, and may transmit the combined notifications or reports in a single notification message. Accordingly, event reports related to multiple target sessions or UE IDs may be provided to the NF service consumer (11) through one notification message, thereby reducing the number of notification messages transmitted by the UPF.

[0091] Figure 2 illustrates an event exposure service procedure in which UPFs transmit separate notification messages for respective event subscriptions.

[0092] Referring to Figure 2, UPF1 (21) and UPF2 (22) may correspond to the UPF (12) of Figure 1, and an NF service consumer (AF / NWDAF) (23) may correspond to the NF service consumer (11) of Figure 1.

[0093] As illustrated in Figure 2, the UPF1 (21) and UPF2 (22) may receive multiple messages related to event subscription from the NF service consumer (AF / NWDAF) (23). The messages related to event subscription may trigger the respective UPFs to start collecting data and to start notifying collected data or event reports to the NF service consumer (AF / NWDAF) (23). In an embodiment, the messages related to event subscription may include a Nupf_EventExposure_Subscribe request message. The messages related to event subscription may include one or more parameters. The one or more parameters may include, but are not limited to, Target UE(s) (e.g., UE IP address), Event type, Notification correlation ID, Notification target address / URI, Event-related information such as Data Network Name (DNN) and Single Network Slice Selection Assistance Information (S-NSSAI), Aggregation level (e.g., per flow, per session, per application), and reporting suggestion information. The reporting suggestion information may include max_delay or reporting time information for a report.

[0094] The notification correlation identifier may be used so that the NF service consumer (AF / NWDAF) (23) can correlate collected data or an event report transmitted by the UPF in a notification message with a particular event subscription. For example, when UPF1 (21) or UPF2 (22) is provided with a notification correlation identifier = abc related to an event subscription or data collection, the corresponding UPF may include the notification correlation identifier in a notification message including an event report or UPF data. Accordingly, when the NF service consumer (AF / NWDAF) (23) receives the notification message, the NF service consumer (AF / NWDAF) (23) may identify the event subscription to which the event report or UPF data included in the notification message corresponds.

[0095] The max_delay information or reporting time information may be used to inform the UPF about a maximum time for which transmission of a notification message related to an event report or UPF data can be delayed. For example, the maximum time may be counted from a time when a UPF event occurs or from a time when the UPF has collected particular data. The max_delay parameter may be included in reporting suggestion information provided to the UPF, or may be included in separate information or a separate container.

[0096] The notification target address or URI may be used to inform the UPF of a target address to which the UPF should transmit a notification message.

[0097] At step 205, the NF service consumer (AF / NWDAF) (23) may transmit a Nupf_EventExposure_Subscribe request message to UPF1 (21). The Nupf_EventExposure_Subscribe request message transmitted at step 205 may be related to a first event subscription. For example, the Nupf_EventExposure_Subscribe request message may include information for causing UPF1 (21) to monitor an event or collect data related to the first event subscription. The request message may further include a notification target address or URI and a notification correlation identifier associated with the first event subscription.

[0098] At step 210, UPF1 (21) may transmit a Nupf_EventExposure_Subscribe response message to the NF service consumer (AF / NWDAF) (23). The Nupf_EventExposure_Subscribe response message may indicate that the subscription request transmitted at step 205 has been accepted or that a subscription resource corresponding to the first event subscription has been created. In an embodiment, the response message transmitted at step 210 may include a subscription identifier, for example, subscription ID 1, associated with the first event subscription.

[0099] At step 215, the NF service consumer (AF / NWDAF) (23) may transmit a Nupf_EventExposure_Subscribe request message to UPF2 (22). The Nupf_EventExposure_Subscribe request message transmitted at step 215 may be related to a second event subscription. The second event subscription may be associated with a different target UE, a different PDU session, a different event type, a different aggregation level, or a different reporting condition from the first event subscription. At step 220, UPF2 (22) may transmit a Nupf_EventExposure_Subscribe response message to the NF service consumer (AF / NWDAF) (23) in response to the Nupf_EventExposure_Subscribe request message received at step 215.

[0100] At step 225, the NF service consumer (AF / NWDAF) (23) may transmit another Nupf_EventExposure_Subscribe request message to UPF1 (21). The Nupf_EventExposure_Subscribe request message transmitted at step 225 may be related to a third event subscription. At step 230, UPF1 (21) may transmit a Nupf_EventExposure_Subscribe response message to the NF service consumer (AF / NWDAF) (23) in response to the Nupf_EventExposure_Subscribe request message received at step 225. Accordingly, UPF1 (21) may maintain a plurality of event subscriptions associated with the same NF service consumer (AF / NWDAF) (23).

[0101] At step 235, the NF service consumer (AF / NWDAF) (23) may transmit another Nupf_EventExposure_Subscribe request message to UPF2 (22). The Nupf_EventExposure_Subscribe request message transmitted at step 235 may be related to a fourth event subscription. At step 240, UPF2 (22) may transmit a Nupf_EventExposure_Subscribe response message to the NF service consumer (AF / NWDAF) (23) in response to the Nupf_EventExposure_Subscribe request message received at step 235. Accordingly, UPF2 (22) may also maintain a plurality of event subscriptions associated with the same NF service consumer (AF / NWDAF) (23).

[0102] After the event subscriptions have been created, UPF1 (21) and UPF2 (22) may monitor events, collect data, or prepare event reports according to the respective event subscriptions.

[0103] At step 245, a trigger for event 2 may occur at UPF2 (22). In response to the trigger for event 2, UPF2 (22) may generate an event report or UPF data corresponding to the second event subscription. At step 250, UPF2 (22) may transmit a Nupf_EventExposure_Notify message, for example, a Nupf_Notify message, to the NF service consumer (AF / NWDAF) (23). The Nupf_EventExposure_Notify message transmitted at step 250 may include the event report or UPF data corresponding to event 2, and may further include a notification correlation identifier associated with the second event subscription.

[0104] At step 255, a trigger for event 4 may occur at UPF2 (22). In response to the trigger for event 4, UPF2 (22) may generate an event report or UPF data corresponding to the fourth event subscription. At step 260, UPF2 (22) may transmit another Nupf_EventExposure_Notify message, for example, another Nupf_Notify message, to the NF service consumer (AF / NWDAF) (23). The Nupf_EventExposure_Notify message transmitted at step 260 may include the event report or UPF data corresponding to event 4, and may further include a notification correlation identifier associated with the fourth event subscription.

[0105] At step 265, a trigger for event 1 may occur at UPF1 (21). In response to the trigger for event 1, UPF1 (21) may generate an event report or UPF data corresponding to the first event subscription. At step 270, UPF1 (21) may transmit a Nupf_EventExposure_Notify message, for example, a Nupf_Notify message, to the NF service consumer (AF / NWDAF) (23). The Nupf_EventExposure_Notify message transmitted at step 270 may include the event report or UPF data corresponding to event 1, and may further include a notification correlation identifier associated with the first event subscription.

[0106] At step 275, a trigger for event 3 may occur at UPF1 (21). In response to the trigger for event 3, UPF1 (21) may generate an event report or UPF data corresponding to the third event subscription. At step 280, UPF1 (21) may transmit another Nupf_EventExposure_Notify message, for example, another Nupf_Notify message, to the NF service consumer (AF / NWDAF) (23). The Nupf_EventExposure_Notify message transmitted at step 280 may include the event report or UPF data corresponding to event 3, and may further include a notification correlation identifier associated with the third event subscription.

[0107] As described above with reference to Figure 2, when the UPF needs to notify the NF service consumer (AF / NWDAF) (23) about collected data or an event report, the UPF may send a separate event notification message for each corresponding event subscription. In each of the separate event notification messages (e.g. Nupf_Notify message), the UPF includes the notification correlation ID in order to let the NF service consumer (AF / NWDAF) (23) know to which particular subscription the notification is related. In this procedure, the UPF needs to send separate notify messages (e.g., HTTP messages) for each of the different subscriptions. This inefficiency occurs even though the subscriptions might be related and / or provided to the same consumer or target address.

[0108] Additionally, an alternate procedure may be implemented where the entity or Network Function sending the message for subscribing to the UPF event report or data is different from the consumer of those UPF event reports or data to which the UPF sends the notification including the event report or UPF data.

[0109] Although Figure 2 illustrates a procedure in which the entity transmitting the messages for subscribing to UPF event reports or UPF data is the same as the NF service consumer (AF / NWDAF) (23) that receives notification messages including the event reports or UPF data, the present disclosure is not limited thereto. In another embodiment, an entity or a network function that transmits a message for subscribing to UPF event reports or UPF data may be different from a consumer of the UPF event reports or UPF data to which the UPF transmits a notification message including the event reports or UPF data.

[0110] Figure 3 illustrates an event exposure service procedure in which a network entity transmitting messages for subscribing to UPF event reports is different from an NF service consumer receiving notification messages.

[0111] Referring to Figure 3, UPF1 (31) and UPF2 (32) may correspond to the UPF1 (21) and UPF2 (22) of Figure 2, and the UPF (12) of Figure 1. Furthermore, the NF service consumer (AF / NWDAF) (34) may correspond to the NF service consumer (AF / NWDAF) (23) of Figure 2, and the NF service consumer (11) of Figure 1. Figure 3 differs from Figure 2 in that a network entity (33), rather than the NF service consumer (AF / NWDAF) (34), transmits messages for subscribing to UPF event reports or UPF data, while the UPFs (31, 32) transmit notification messages including event reports or UPF data to the NF service consumer (AF / NWDAF) (34). For example, the network entity (33) may be a Session Management Function (SMF) acting on behalf of the NF service consumer (AF / NWDAF) (34).

[0112] As illustrated in Figure 3, the network entity (33) may subscribe to UPF event reports or UPF data on behalf of, or in association with, the NF service consumer (AF / NWDAF) (34). In an embodiment, the network entity (33) may be a network function that is different from the NF service consumer (AF / NWDAF) (34). The network entity (33) may transmit one or more messages related to event subscription to UPF1 (31) and / or UPF2 (32). The messages related to event subscription may be messages that trigger UPF1 (31) and / or UPF2 (32) to start collecting data and to start notifying collected data or event reports to the NF service consumer (AF / NWDAF) (34). In an embodiment, the messages related to event subscription may include a Nupf_EventExposure_Subscribe request message.

[0113] At step 305, the network entity (33) may transmit a Nupf_EventExposure_Subscribe request message to UPF1 (31). The Nupf_EventExposure_Subscribe request message transmitted at step 305 may be related to a first event subscription. The Nupf_EventExposure_Subscribe request message may include one or more parameters for causing UPF1 (31) to monitor an event or collect data related to the first event subscription. For example, the one or more parameters may include Target UE(s), an event type, a notification correlation ID, a notification target address or URI, event-related information, an aggregation level, and reporting suggestion information. In this case, the notification target address or URI may indicate an address of the NF service consumer (AF / NWDAF) (34), even though the subscription request message is transmitted by the network entity (33).

[0114] At step 310, UPF1 (31) may transmit a Nupf_EventExposure_Subscribe response message to the network entity (33). The Nupf_EventExposure_Subscribe response message may indicate that the subscription request transmitted at step 305 has been accepted or that a subscription resource corresponding to the first event subscription has been created. In an embodiment, the response message transmitted at step 310 may include a subscription identifier associated with the first event subscription.

[0115] At step 315, the network entity (33) may transmit a Nupf_EventExposure_Subscribe request message to UPF2 (32). The Nupf_EventExposure_Subscribe request message transmitted at step 315 may be related to a second event subscription. The second event subscription may be associated with a different target UE, a different PDU session, a different event type, a different aggregation level, or a different reporting condition from the first event subscription. At step 320, UPF2 (32) may transmit a Nupf_EventExposure_Subscribe response message to the network entity (33) in response to the Nupf_EventExposure_Subscribe request message received at step 315.

[0116] At step 325, the network entity (33) may transmit another Nupf_EventExposure_Subscribe request message to UPF1 (31). The Nupf_EventExposure_Subscribe request message transmitted at step 325 may be related to a third event subscription. At step 330, UPF1 (31) may transmit a Nupf_EventExposure_Subscribe response message to the network entity (33) in response to the Nupf_EventExposure_Subscribe request message received at step 325. Accordingly, UPF1 (31) may maintain a plurality of event subscriptions associated with the NF service consumer (AF / NWDAF) (34), even though the subscription request messages are received from the network entity (33).

[0117] At step 335, the network entity (33) may transmit another Nupf_EventExposure_Subscribe request message to UPF2 (32). The Nupf_EventExposure_Subscribe request message transmitted at step 335 may be related to a fourth event subscription. At step 340, UPF2 (32) may transmit a Nupf_EventExposure_Subscribe response message to the network entity (33) in response to the Nupf_EventExposure_Subscribe request message received at step 335. Accordingly, UPF2 (32) may also maintain a plurality of event subscriptions associated with the NF service consumer (AF / NWDAF) (34), even though the subscription request messages are received from the network entity (33).

[0118] After the event subscriptions have been created, UPF1 (31) and UPF2 (32) may monitor events, collect data, or prepare event reports according to the respective event subscriptions. At step 345, a trigger for event 2 may occur at UPF2 (32). In response to the trigger for event 2, UPF2 (32) may generate an event report or UPF data corresponding to the second event subscription. At step 350, UPF2 (32) may transmit a Nupf_EventExposure_Notify message, for example, a Nupf_Notify message, to the NF service consumer (AF / NWDAF) (34). The Nupf_EventExposure_Notify message transmitted at step 350 may include the event report or UPF data corresponding to event 2, and may further include a notification correlation ID associated with the second event subscription.

[0119] At step 355, a trigger for event 4 may occur at UPF2 (32). In response to the trigger for event 4, UPF2 (32) may generate an event report or UPF data corresponding to the fourth event subscription. At step 360, UPF2 (32) may transmit another Nupf_EventExposure_Notify message, for example, another Nupf_Notify message, to the NF service consumer (AF / NWDAF) (34). The Nupf_EventExposure_Notify message transmitted at step 360 may include the event report or UPF data corresponding to event 4, and may further include a notification correlation ID associated with the fourth event subscription.

[0120] At step 365, a trigger for event 1 may occur at UPF1 (31). In response to the trigger for event 1, UPF1 (31) may generate an event report or UPF data corresponding to the first event subscription. At step 370, UPF1 (31) may transmit a Nupf_EventExposure_Notify message, for example, a Nupf_Notify message, to the NF service consumer (AF / NWDAF) (34). The Nupf_EventExposure_Notify message transmitted at step 370 may include the event report or UPF data corresponding to event 1, and may further include a notification correlation ID associated with the first event subscription.

[0121] At step 375, a trigger for event 3 may occur at UPF1 (31). In response to the trigger for event 3, UPF1 (31) may generate an event report or UPF data corresponding to the third event subscription. At step 380, UPF1 (31) may transmit another Nupf_EventExposure_Notify message, for example, another Nupf_Notify message, to the NF service consumer (AF / NWDAF) (34). The Nupf_EventExposure_Notify message transmitted at step 380 may include the event report or UPF data corresponding to event 3, and may further include a notification correlation ID associated with the third event subscription.

[0122] In an embodiment, as described above with reference to Figure 3, the network entity (33) that transmits the messages for subscribing to UPF event reports or UPF data may be different from the NF service consumer (AF / NWDAF) (34) that receives notification messages including the UPF event reports or UPF data. That is, UPF1 (31) and UPF2 (32) may receive subscription-related messages from the network entity (33), but may transmit notification messages to the NF service consumer (AF / NWDAF) (34) indicated by a notification target address or URI included in the corresponding subscription-related messages. Similarly to Figure 2, when UPF1 (31) or UPF2 (32) needs to notify the NF service consumer (AF / NWDAF) (34) about collected data or an event report, the corresponding UPF may send a separate event notification message for each corresponding event subscription.

[0123] Figure 4 illustrates an event exposure service procedure using a notification aggregation reference ID according to an embodiment of the present disclosure.

[0124] Referring to Figure 4, a UPF (41) and an NF service consumer (AF / NWDAF) (42) may correspond to the UPF1 (31) and / or UPF2 (32) and the NF service consumer (AF / NWDAF) (34) of Figure 3, the UPF1 (21) and / or UPF2 (22) and the NF service consumer (AF / NWDAF) (23) of Figure 2, and the UPF (12) and the NF service consumer (11) of Figure 1.

[0125] As illustrated in Figure 4, the NF service consumer (AF / NWDAF) (42), which is a consumer of UPF event exposure events, may decide to include a notification aggregation reference ID for event subscriptions that are related to each other or for which the NF service consumer (AF / NWDAF) (42) wants to aggregate or combine multiple event notifications or reports together. In an embodiment, the NF service consumer (AF / NWDAF) (42) may include a notification aggregation reference ID in one or more messages for subscribing to UPF event reports or UPF data for target UEs or target sessions that are related to each other, or for which the NF service consumer (AF / NWDAF) (42) wants to aggregate multiple event notifications or reports together. The notification aggregation reference ID may be used by the UPF (41) to determine whether event reports corresponding to different event subscriptions are to be combined into a single notification message.

[0126] At step 405, the NF service consumer (AF / NWDAF) (42) may transmit, to the UPF (41), a first subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The first subscription message may include one or more of first targets (e.g., Target = UE IP address 1), a notification target address, a notification correlation ID, and a first notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"). The first subscription message may be related to a first event subscription corresponding to a first target UE or a first target session.

[0127] At step 410, the UPF (41) may transmit, to the NF service consumer (AF / NWDAF) (42), a first response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the first subscription message transmitted at step 405. The first response message may indicate that the first subscription message has been accepted or that a subscription resource corresponding to the first event subscription has been created. Accordingly, the UPF (41) may maintain a subscription context associated with the first event subscription and the Notification aggregation reference ID 1.

[0128] At step 415, the NF service consumer (AF / NWDAF) (42) may transmit, to the UPF (41), a second subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The second subscription message may include one or more of second targets (e.g., Target = UE IP address 2), a notification target address, a notification correlation ID, and the first notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"). The second subscription message may be related to a second event subscription corresponding to a second target UE or a second target session. Since the second subscription message includes the same Notification aggregation reference ID 1 as the first subscription message, the first event subscription and the second event subscription may be recognized by the UPF (41) as event subscriptions for which event notifications or reports can be combined together.

[0129] At step 420, the UPF (41) may transmit, to the NF service consumer (AF / NWDAF) (42), a second response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the second subscription message transmitted at step 415. The second response message may indicate that the second subscription message has been accepted or that a subscription resource corresponding to the second event subscription has been created. Accordingly, the UPF (41) may maintain a subscription context associated with the second event subscription and the Notification aggregation reference ID 1.

[0130] At step 425, the NF service consumer (AF / NWDAF) (42) may transmit, to the UPF (41), a third subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The third subscription message may include one or more of third targets (e.g., Target = UE IP address 3), a notification target address, a notification correlation ID, and a second notification aggregation reference ID (e.g., "Notification reference ID 2" or "Notification aggregation reference ID 2"). The third subscription message may be related to a third event subscription corresponding to a third target UE or a third target session. Since the third subscription message includes the Notification aggregation reference ID 2, which is different from the Notification aggregation reference ID 1 included in the first subscription message and the second subscription message, the third event subscription may be distinguished from the first and second event subscriptions for notification aggregation.

[0131] At step 430, the UPF (41) may transmit, to the NF service consumer (AF / NWDAF) (42), a third response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the third subscription message transmitted at step 425. The third response message may indicate that the third subscription message has been accepted or that a subscription resource corresponding to the third event subscription has been created. Accordingly, the UPF (41) may maintain a subscription context associated with the third event subscription and the Notification aggregation reference ID 2.

[0132] At step 435, a trigger for subscription 1 may occur at the UPF (41). The trigger for subscription 1 may be a trigger for an event related to the first event subscription generated based on the first subscription message. In response to the trigger for subscription 1, the UPF (41) may collect data or generate an event report corresponding to the first event subscription. Since the first event subscription is associated with the Notification aggregation reference ID 1, the UPF (41) may determine that the event report corresponding to the first event subscription may be combined with another event report associated with the same Notification aggregation reference ID 1.

[0133] At step 440, a trigger for subscription 3 may occur at the UPF (41). The trigger for subscription 3 may be a trigger for an event related to the third event subscription generated based on the third subscription message. In response to the trigger for subscription 3, the UPF (41) may collect data or generate an event report corresponding to the third event subscription. Since the third event subscription is associated with the Notification aggregation reference ID 2, which is different from the Notification aggregation reference ID 1, the UPF (41) may determine that the event report corresponding to the third event subscription is not to be combined with the event report corresponding to the first event subscription.

[0134] At step 445, the UPF (41) may transmit, to the NF service consumer (AF / NWDAF) (42), a notification message for subscription 3. The notification message transmitted at step 445 may include collected data or an event report related to the event subscribed in step 425. In an embodiment, the UPF (41) may transmit the notification message for subscription 3 separately because the third event subscription has a different notification aggregation reference ID from the first event subscription and the second event subscription, or because the third event subscription does not include a notification aggregation reference ID corresponding to the first event subscription and the second event subscription. The notification message transmitted at step 445 may further include a notification correlation ID associated with the third event subscription.

[0135] At step 450, a trigger for subscription 2 may occur at the UPF (41). The trigger for subscription 2 may be a trigger for an event related to the second event subscription generated based on the second subscription message. In response to the trigger for subscription 2, the UPF (41) may collect data or generate an event report corresponding to the second event subscription. Since the second event subscription is associated with the same Notification aggregation reference ID 1 as the first event subscription, the UPF (41) may determine that the event report corresponding to the second event subscription and the event report corresponding to the first event subscription can be combined together.

[0136] At step 455, the UPF (41) may transmit, to the NF service consumer (AF / NWDAF) (42), a combined notification message for two reports. The combined notification message transmitted at step 455 may include collected data or event reports corresponding to both the first event subscription and the second event subscription. The UPF (41) may decide to transmit the combined notification message based on the first event subscription and the second event subscription containing the same Notification aggregation reference ID 1. In an embodiment, the UPF (41) may also include the Notification aggregation reference ID 1 in the combined notification message. In addition, the UPF (41) may include any of the notification correlation IDs received for the related event subscriptions, for example, the notification correlation ID received in the message transmitted at step 405 and / or the notification correlation ID received in the message transmitted at step 415.

[0137] In an embodiment, the UPF (41) may be triggered to transmit the combined notification message at step 455 when a reporting period for one or all of the subscribed events is completed, based on another parameter, or based on local configuration. For example, the UPF (41) may be triggered to transmit the combined notification message based on a max_delay time parameter. The UPF (41) may wait to report an event or UPF data until the max_delay time provided to the UPF (41) for that event is elapsed, and then may include all event reports that can be combined or aggregated together for one or more subscriptions in one notification message when the max_delay time is over. Reporting time information or reporting suggestion information may be used instead of the max_delay time for the same purpose.

[0138] As described above with reference to Figure 4, the NF service consumer (AF / NWDAF) (42) may include the same notification aggregation reference ID in messages related to a plurality of event subscriptions for which event notifications or reports are to be aggregated or combined together. The UPF (41) may determine, based on the notification aggregation reference ID, whether event reports corresponding to different event subscriptions are to be included in a single notification message. Accordingly, event reports associated with related subscriptions may be transmitted through a combined notification message, thereby reducing the number of notification messages transmitted from the UPF (41) to the NF service consumer (AF / NWDAF) (42).

[0139] Figure 5 illustrates an event exposure service procedure using a notification aggregation indication according to an embodiment of the present disclosure.

[0140] Referring to Figure 5, a UPF (51) and an NF service consumer (AF / NWDAF) (52) may correspond to the UPF (41) and the NF service consumer (AF / NWDAF) (42) of Figure 4, the UPF1 (31) and / or UPF2 (32) and the NF service consumer (AF / NWDAF) (34) of Figure 3, the UPF1 (21) and / or UPF2 (22) and the NF service consumer (AF / NWDAF) (23) of Figure 2, and the UPF (12) and the NF service consumer (11) of Figure 1.

[0141] As illustrated in Figure 5, the NF service consumer (AF / NWDAF) (52) may include a notification aggregation indication in one or more messages for subscribing to UPF event reports or UPF data. The notification aggregation indication may be included for target UEs or target sessions for which the NF service consumer (AF / NWDAF) (52) wants to aggregate or combine multiple event notifications or reports together. In an embodiment, the UPF (51) may determine whether to combine notifications for multiple subscriptions based on whether the notification aggregation indication is provided, whether notification target addresses are the same, whether notification correlation IDs are the same, or any combination thereof.

[0142] At step 505, the NF service consumer (AF / NWDAF) (52) may transmit, to the UPF (51), a first subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The first subscription message may include one or more of first targets (e.g., Target = UE IP address 1) and the notification aggregation indication. The first subscription message may be related to a first event subscription corresponding to a first target UE or a first target session.

[0143] At step 510, the UPF (51) may transmit, to the NF service consumer (AF / NWDAF) (52), a first response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the first subscription message transmitted at step 505. The first response message may indicate that the first subscription message has been accepted or that a subscription resource corresponding to the first event subscription has been created. Accordingly, the UPF (51) may maintain a subscription context associated with the first event subscription and the notification aggregation indication.

[0144] At step 515, the NF service consumer (AF / NWDAF) (52) may transmit, to the UPF (51), a second subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The second subscription message may include one or more of second targets (e.g., Target = UE IP address 2) and the notification aggregation indication. The second subscription message may be related to a second event subscription corresponding to a second target UE or a second target session. Since the second subscription message includes the notification aggregation indication, the second event subscription may be recognized by the UPF (51) as a subscription for which an event notification or report can be combined with another event notification or report.

[0145] At step 520, the UPF (51) may transmit, to the NF service consumer (AF / NWDAF) (52), a second response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the second subscription message transmitted at step 515. The second response message may indicate that the second subscription message has been accepted or that a subscription resource corresponding to the second event subscription has been created. Accordingly, the UPF (51) may maintain a subscription context associated with the second event subscription and the notification aggregation indication.

[0146] At step 525, the NF service consumer (AF / NWDAF) (52) may transmit, to the UPF (51), a third subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The third subscription message may include one or more of third targets (e.g., Target = UE IP address 3). Unlike the first and second subscription messages, the third subscription message may not include a notification aggregation indication. In Figure 5, the third subscription message may not include the notification aggregation indication. The third subscription message may be related to a third event subscription corresponding to a third target UE or a third target session.

[0147] At step 530, the UPF (51) may transmit, to the NF service consumer (AF / NWDAF) (52), a third response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the third subscription message transmitted at step 525. The third response message may indicate that the third subscription message has been accepted or that a subscription resource corresponding to the third event subscription has been created. Since the third event subscription may not include the notification aggregation indication, the third event subscription may be distinguished from the first and second event subscriptions for notification aggregation.

[0148] At step 535, a trigger for subscription 1 may occur at the UPF (51). The trigger for subscription 1 may be a trigger for an event related to the first event subscription generated based on the first subscription message. In response to the trigger for subscription 1, the UPF (51) may collect data or generate an event report corresponding to the first event subscription. Since the first event subscription is associated with the notification aggregation indication, the UPF (51) may determine that the event report corresponding to the first event subscription may be combined with another event report associated with a subscription for which notification aggregation is allowed.

[0149] At step 540, a trigger for subscription 3 may occur at the UPF (51). The trigger for subscription 3 may be a trigger for an event related to the third event subscription generated based on the third subscription message. In response to the trigger for subscription 3, the UPF (51) may collect data or generate an event report corresponding to the third event subscription. Since the third event subscription may not include the notification aggregation indication, the UPF (51) may determine that the event report corresponding to the third event subscription is not to be combined with the event report corresponding to the first event subscription, or may determine that the event report corresponding to the third event subscription is to be separately reported.

[0150] At step 545, the UPF (51) may transmit, to the NF service consumer (AF / NWDAF) (52), a notification message for subscription 3. The notification message transmitted at step 545 may include collected data or an event report related to the event subscribed in step 525. In an embodiment, the UPF (51) may transmit the notification message for subscription 3 separately because the third event subscription does not include the notification aggregation indication, or because the third event subscription does not satisfy a condition for aggregation with the first event subscription and the second event subscription. The notification message transmitted at step 545 may further include a notification correlation ID associated with the third event subscription.

[0151] At step 550, a trigger for subscription 2 may occur at the UPF (51). The trigger for subscription 2 may be a trigger for an event related to the second event subscription generated based on the second subscription message. In response to the trigger for subscription 2, the UPF (51) may collect data or generate an event report corresponding to the second event subscription. Since the second event subscription includes the notification aggregation indication, the UPF (51) may determine whether the event report corresponding to the second event subscription can be combined with the event report corresponding to the first event subscription. For example, the UPF (51) may determine that the event reports for the first and second event subscriptions can be combined when the notification target addresses are the same and / or the notification correlation IDs are the same.

[0152] At step 555, the UPF (51) may transmit, to the NF service consumer (AF / NWDAF) (52), a combined notification message for two reports. The combined notification message transmitted at step 555 may include collected data or event reports corresponding to both the first event subscription and the second event subscription. The UPF (51) may decide to transmit the combined notification message based on the notification aggregation indication being provided for the first event subscription and the second event subscription, and / or based on the notification target addresses being the same and / or the notification correlation IDs being the same. In an embodiment, the UPF (51) may include any of the notification correlation IDs received for the related event subscriptions, for example, the notification correlation ID received in the message transmitted at step 505 and / or the notification correlation ID received in the message transmitted at step 515.

[0153] In an embodiment, the UPF (51) may be triggered to transmit the combined notification message at step 555 when a reporting period for the subscribed events is completed, based on another parameter, or based on local configuration. For example, the UPF (51) may be triggered to transmit the combined notification message based on a max_delay time parameter. The UPF (51) may wait to report an event or UPF data until the max_delay time provided to the UPF (51) for that event is elapsed, and then may include all event reports that can be combined or aggregated together for one or more subscriptions in one notification message when the max_delay time is over. Reporting time information or reporting suggestion information may be used instead of the max_delay time parameter for the same purpose.

[0154] In an embodiment, in a procedure in which the UPF (51) and the NF service consumer (AF / NWDAF) (52) operate based on the notification aggregation indication as described with reference to Figure 5, the notification aggregation indication may be used instead of the notification aggregation reference ID in messages for subscribing to UPF event reports or UPF data. For example, in corresponding procedures described with reference to other figures, a notification aggregation indication may be used in place of a notification aggregation reference ID.

[0155] As described above with reference to Figure 5, the NF service consumer (AF / NWDAF) (52) may include a notification aggregation indication in messages related to a plurality of event subscriptions for which event notifications or reports are to be aggregated or combined together. The UPF (51) may determine, based on the notification aggregation indication and / or other conditions, such as a notification target address or a notification correlation ID, whether event reports corresponding to different event subscriptions are to be included in a single notification message. Accordingly, event reports associated with related subscriptions may be transmitted through a combined notification message, thereby reducing the number of notification messages transmitted from the UPF (51) to the NF service consumer (AF / NWDAF) (52).

[0156] Figure 6 illustrates an event exposure service procedure using a notification correlation ID according to an embodiment of the present disclosure.

[0157] Referring to Figure 6, a UPF (61) and a NF service consumer (62) may correspond to the UPF (51) and the NF service consumer (AF / NWDAF) (52) of Figure 5, the UPF (41) and the NF service consumer (AF / NWDAF) (42) of Figure 4, the UPF1 (31) and / or UPF2 (32) and the NF service consumer (AF / NWDAF) (34) of Figure 3, the UPF1 (21) and / or UPF2 (22) and the NF service consumer (AF / NWDAF) (23) of Figure 2, and the UPF (12) and the NF service consumer (11) of Figure 1.

[0158] As illustrated in Figure 6, a consumer may include the same notification correlation ID in one or more messages for subscribing to UPF event reports or UPF data for target UEs or target sessions for which the consumer wants to aggregate or combine multiple event notifications or reports together. In an embodiment, a consumer of UPF event exposure events may decide to include the same notification correlation ID for event subscriptions that are related to each other or for which the consumer wants to aggregate or combine multiple event notifications or reports together. The UPF (61) may then determine whether to combine notifications for multiple subscriptions based on whether the same notification correlation ID is provided and / or whether notification target addresses are the same.

[0159] At step 605, the NF service consumer (62) may transmit, to the UPF (61), first subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The first subscription message may include one or more of first targets (e.g., Target = UE IP address 1), a first notification correlation ID (e.g., Notification correlation ID 1), and a notification target address. The first subscription message may be related to a first event subscription corresponding to a first target UE or a first target session.

[0160] At step 610, the UPF (61) may transmit, to the NF service consumer (62), a first response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the first subscription message transmitted at step 605. The first response message may indicate that the first subscription message has been accepted or that a subscription resource corresponding to the first event subscription has been created. Accordingly, the UPF (61) may maintain a subscription context associated with the first event subscription, the first target, and Notification Correlation ID1.

[0161] At step 615, the NF service consumer (62) may transmit, to the UPF (61), a second subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The second subscription message may include one or more of second targets (e.g., Target = UE IP address 2) and the same first notification correlation ID (e.g., Notification correlation ID 1). In an embodiment, the second subscription message may further include the same notification target as the first subscription message. The second subscription message may be related to a second event subscription corresponding to a second target UE or a second target session. Since the second subscription message includes the same Notification Correlation ID1 as the first subscription message, the first event subscription and the second event subscription may be recognized by the UPF (61) as subscriptions for which event notifications or reports can be combined together.

[0162] At step 620, the UPF (61) may transmit, to the NF service consumer (62), a second response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the second subscription message transmitted at step 615. The second response message may indicate that the second subscription message has been accepted or that a subscription resource corresponding to the second event subscription has been created. Accordingly, the UPF (61) may maintain a subscription context associated with the second event subscription and Notification Correlation ID1.

[0163] At step 625, the NF service consumer (62) may transmit, to the UPF (61), a third subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The third subscription message may include one or more of third targets (e.g., Target = UE IP address 3) and a second notification correlation ID (e.g., Notification correlation ID 2). The third subscription message may be related to a third event subscription corresponding to a third target UE or a third target session. Since the third subscription message includes Notification Correlation ID2, which is different from Notification Correlation ID1 included in the first subscription message and the second subscription message, the third event subscription may be distinguished from the first event subscription and the second event subscription for notification aggregation.

[0164] At step 630, the UPF (61) may transmit, to the NF service consumer (62), a third response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the third subscription message transmitted at step 625. The third response message may indicate that the third subscription message has been accepted or that a subscription resource corresponding to the third event subscription has been created. Accordingly, the UPF (61) may maintain a subscription context associated with the third event subscription and Notification Correlation ID2.

[0165] At step 635, a trigger for subscription 1 may occur at the UPF (61). The trigger for subscription 1 may be a trigger for an event related to the first event subscription generated based on the first subscription message. In response to the trigger for subscription 1, the UPF (61) may collect data or generate an event report corresponding to the first event subscription. Since the first event subscription is associated with Notification Correlation ID1, the UPF (61) may determine that the event report corresponding to the first event subscription may be combined with another event report associated with the same Notification Correlation ID1.

[0166] At step 640, a trigger for subscription 3 may occur at the UPF (61). The trigger for subscription 3 may be a trigger for an event related to the third event subscription generated based on the third subscription message. In response to the trigger for subscription 3, the UPF (61) may collect data or generate an event report corresponding to the third event subscription. Since the third event subscription is associated with Notification Correlation ID2, which is different from Notification Correlation ID1, the UPF (61) may determine that the event report corresponding to the third event subscription is not to be combined with the event report corresponding to the first event subscription.

[0167] At step 645, the UPF (61) may transmit, to the NF service consumer (62), a notification message for subscription 3. The notification message transmitted at step 645 may include collected data or an event report related to the event subscribed through the third subscription message. In an embodiment, the UPF (61) may transmit the notification message for subscription 3 separately because the third event subscription has a different notification correlation ID from the first event subscription and the second event subscription. The notification message transmitted at step 645 may include Notification Correlation ID2 so that the NF service consumer (62) may correlate the notification message with the third event subscription.

[0168] At step 650, a trigger for subscription 2 may occur at the UPF (61). The trigger for subscription 2 may be a trigger for an event related to the second event subscription generated based on the second subscription message. In response to the trigger for subscription 2, the UPF (61) may collect data or generate an event report corresponding to the second event subscription. Since the second event subscription is associated with the same Notification Correlation ID1 as the first event subscription, the UPF (61) may determine that the event report corresponding to the second event subscription and the event report corresponding to the first event subscription can be combined together.

[0169] At step 655, the UPF (61) may transmit, to the NF service consumer (62), a combined notification message for two reports. The combined notification message transmitted at step 655 may include collected data or event reports corresponding to both the first event subscription and the second event subscription. The UPF (61) may decide to transmit the combined notification message based on the first event subscription and the second event subscription containing the same Notification Correlation ID1 and / or based on the notification target addresses being the same. In an embodiment, the UPF (61) may include Notification Correlation ID1 in the combined notification message.

[0170] In an embodiment, the UPF (61) may be triggered to transmit the combined notification message at step 655 when a reporting period for the subscribed events is completed, based on another parameter, and / or based on local configuration. For example, the UPF (61) may be triggered to transmit the combined notification message based on a max_delay time parameter. The UPF (61) may wait to report an event or UPF data until the max_delay time provided to the UPF (61) for that event is elapsed, and then may include all event reports that can be combined or aggregated together for one or more subscriptions in one notification message when the max_delay time is over. Reporting time information or reporting suggestion information may be used instead of the max_delay time parameter for the same purpose.

[0171] In an embodiment, in a procedure in which the UPF (61) and the NF service consumer (62) operate based on the Notification Correlation ID as described with reference to Figure 6, the same Notification Correlation ID may be used instead of the Notification aggregation reference ID in messages for subscribing to UPF event reports or UPF data in corresponding procedures of other embodiments. For example, the same Notification Correlation ID may be used instead of the Notification aggregation reference ID in messages for subscribing to UPF event reports or UPF data.

[0172] As described above with reference to Figure 6, the NF service consumer (62) may include the same notification correlation ID in messages related to a plurality of event subscriptions for which event notifications or reports are to be aggregated or combined together. The UPF (61) may determine, based on the same notification correlation ID and / or whether the notification target addresses are the same, whether event reports corresponding to different event subscriptions are to be included in a single notification message. Accordingly, event reports associated with related subscriptions may be transmitted through a combined notification message, thereby reducing the number of notification messages transmitted from the UPF (61) to the NF service consumer (62).

[0173] Figure 7 illustrates an event exposure service procedure in which a UPF aggregates event reports based on a notification aggregation reference ID and max_delay information according to an embodiment of the present disclosure.

[0174] Referring to Figure 7, a UPF (71) and an NF service consumer (AF / NWDAF) (72) may correspond to the UPF (61) and the NF service consumer (62) of Figure 6, the UPF (51) and the NF service consumer (AF / NWDAF) (52) of Figure 5, the UPF (41) and the NF service consumer (AF / NWDAF) (42) of Figure 4, the UPF1 (31) and / or UPF2 (32) and the NF service consumer (AF / NWDAF) (34) of Figure 3, the UPF1 (21) and / or UPF2 (22) and the NF service consumer (AF / NWDAF) (23) of Figure 2, and the UPF (12) and the NF service consumer (11) of Figure 1.

[0175] As illustrated in Figure 7, the NF service consumer (AF / NWDAF) (72) may include a notification aggregation reference ID and reporting suggestion information in messages for subscribing to UPF event reports or UPF data. The reporting suggestion information may include max_delay information. The max_delay information may indicate a maximum delay time for which the UPF (71) may delay transmission of a notification message related to an event report or UPF data after an event trigger occurs or after corresponding data is collected. In an embodiment, when an event report corresponding to a subscription is associated with a notification aggregation reference ID, the UPF (71) may wait until the max_delay time is reached in order to aggregate another event report associated with the same notification aggregation reference ID.

[0176] At step 705, the NF service consumer (AF / NWDAF) (72) may transmit, to the UPF (71), a first subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The first subscription message may include one or more of first targets (e.g., Target = UE IP address 1), a first notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"), and reporting suggestion information including max_delay information. The first subscription message may be related to a first event subscription corresponding to a first target UE or a first target session.

[0177] At step 710, the UPF (71) may transmit, to the NF service consumer (AF / NWDAF) (72), a first response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the first subscription message transmitted at step 705. The first response message may indicate that the first subscription message has been accepted or that a subscription resource corresponding to the first event subscription has been created. Accordingly, the UPF (71) may maintain a subscription context associated with the first event subscription, the Notification aggregation reference ID 1, and the max_delay information.

[0178] At step 715, the NF service consumer (AF / NWDAF) (72) may transmit, to the UPF (71), a second subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The second subscription message may include one or more of second targets (e.g., Target = UE IP address 2), the same first notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"), and reporting suggestion information including max_delay information. The second subscription message may be related to a second event subscription corresponding to a second target UE or a second target session. Since the second subscription message includes the same Notification aggregation reference ID 1 as the first subscription message, the first event subscription and the second event subscription may be recognized by the UPF (71) as subscriptions for which event reports can be aggregated or combined together.

[0179] At step 720, the UPF (71) may transmit, to the NF service consumer (AF / NWDAF) (72), a second response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the second subscription message transmitted at step 715. The second response message may indicate that the second subscription message has been accepted or that a subscription resource corresponding to the second event subscription has been created. Accordingly, the UPF (71) may maintain a subscription context associated with the second event subscription, the Notification aggregation reference ID 1, and the max_delay information.

[0180] At step 725, an event trigger for subscription 1 may occur at the UPF (71). The event trigger for subscription 1 may be a trigger for an event related to the first event subscription generated based on the first subscription message. In response to the event trigger for subscription 1, the UPF (71) may collect data or generate an event report corresponding to the first event subscription. The UPF (71) may start a max_delay timer or may start measuring a max_delay duration for subscription 1 based on the max_delay information. In addition, the UPF (71) may start to aggregate other events or event reports associated with the same notification aggregation reference ID until the maximum delay time for the event corresponding to subscription 1 is reached.

[0181] At step 730, an event trigger for subscription 2 may occur at the UPF (71) before the max_delay duration for subscription 1 expires. The event trigger for subscription 2 may be a trigger for an event related to the second event subscription generated based on the second subscription message. In response to the event trigger for subscription 2, the UPF (71) may collect data or generate an event report corresponding to the second event subscription. Since the second event subscription is associated with the same Notification aggregation reference ID 1 as the first event subscription, and since the event trigger for subscription 2 occurs before the max_delay duration for subscription 1 expires, the UPF (71) may determine that the event report corresponding to subscription 2 can be combined with the event report corresponding to subscription 1.

[0182] At step 735, an event trigger for an event may occur when a reporting period is over for a periodic reporting type, or when an event is detected for a continuous or event-triggered reporting type. Accordingly, the event trigger for subscription 1 (i.e., UE 1) at step 725 and the event trigger for subscription 2 (i.e., UE 1) at step 730 may each correspond to expiration of a reporting period, detection of an event, collection of data, satisfaction of a reporting condition, or any other condition for generating or transmitting an event report.

[0183] At step 740, the UPF (71) may transmit, to the NF service consumer (AF / NWDAF) (72), a combined notification message for two reports. The combined notification message transmitted at step 740 may include an event report corresponding to subscription 1 (i.e., UE 1) and an event report corresponding to subscription 2 (i.e., UE 1) The UPF (71) may transmit the combined notification message at step 740 when the max_delay duration for subscription 1 expires, when a reporting period for one or more subscribed events is completed, based on another parameter, and / or based on local configuration. In an embodiment, the combined notification message may include the Notification aggregation reference ID 1 and / or one or more notification correlation IDs associated with the first event subscription and the second event subscription.

[0184] As described above with reference to Figure 7, when the NF service consumer (AF / NWDAF) (72) provides the same notification aggregation reference ID and max_delay information for multiple subscriptions, the UPF (71) may delay transmission of a notification message for a first triggered subscription within a maximum delay time and may wait for another event report associated with the same notification aggregation reference ID. When another event report associated with the same notification aggregation reference ID is generated before the maximum delay time is reached, the UPF (71) may aggregate the event reports and transmit the aggregated event reports in a single combined notification message. Accordingly, the number of notification messages transmitted from the UPF (71) to the NF service consumer (AF / NWDAF) (72) may be reduced while satisfying the maximum delay condition indicated by the reporting suggestion information.

[0185] Figure 8 illustrates an event exposure service procedure in which event reports are separately transmitted when an event trigger for another subscription does not occur within a max_delay duration according to an embodiment of the present disclosure.

[0186] Referring to Figure 8, a UPF (81) and an NF service consumer (AF / NWDAF) (82) may correspond to the UPF (71) and the NF service consumer (AF / NWDAF) (72) of Figure 7, the UPF (61) and the NF service consumer (62) of Figure 6, the UPF (51) and the NF service consumer (AF / NWDAF) (52) of Figure 5, the UPF (41) and the NF service consumer (AF / NWDAF) (42) of Figure 4, the UPF1 (31) and / or UPF2 (32) and the NF service consumer (AF / NWDAF) (34) of Figure 3, the UPF1 (21) and / or UPF2 (22) and the NF service consumer (AF / NWDAF) (23) of Figure 2, and the UPF (12) and the NF service consumer (11) of Figure 1.

[0187] As illustrated in Figure 8, the NF service consumer (AF / NWDAF) (82) may include a notification aggregation reference ID and reporting suggestion information in messages for subscribing to UPF event reports or UPF data. The reporting suggestion information may include max_delay information. In an embodiment, the max_delay information may define a maximum delay duration during which the UPF (81) may wait for another event report associated with the same notification aggregation reference ID before transmitting a notification message. Unlike the example described with reference to Figure 7, Figure 8 illustrates a case in which an event trigger for another subscription associated with the same notification aggregation reference ID does not occur within the max_delay duration, and thus the UPF (81) transmits separate notification messages.

[0188] At step 805, the NF service consumer (AF / NWDAF) (82) may transmit, to the UPF (81), a first subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The first subscription message may include one or more of first target (e.g., Target = UE IP address 1), a first notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"), and reporting suggestion information including max_delay information. The first subscription message may be related to a first event subscription corresponding to a first target UE or a first target session.

[0189] At step 810, the UPF (81) may transmit, to the NF service consumer (AF / NWDAF) (82), a first response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the first subscription message transmitted at step 805. The first response message may indicate that the first subscription message has been accepted or that a subscription resource corresponding to the first event subscription has been created. Accordingly, the UPF (81) may maintain a subscription context associated with the first event subscription, the Notification aggregation reference ID 1, and the max_delay information.

[0190] At step 815, the NF service consumer (AF / NWDAF) (82) may transmit, to the UPF (81), a second subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The second subscription message may include one or more of second targets (e.g., Target = UE IP address 2), the same first notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"), and reporting suggestion information including max_delay information. The second subscription message may be related to a second event subscription corresponding to a second target UE or a second target session. Since the second subscription message includes the same Notification aggregation reference ID 1 as the first subscription message, the first event subscription and the second event subscription may be recognized by the UPF (81) as subscriptions for which event reports can be aggregated or combined together if an aggregation condition is satisfied.

[0191] At step 820, the UPF (81) may transmit, to the NF service consumer (AF / NWDAF) (82), a second response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the second subscription message transmitted at step 815. The second response message may indicate that the second subscription message has been accepted or that a subscription resource corresponding to the second event subscription has been created. Accordingly, the UPF (81) may maintain a subscription context associated with the second event subscription, the Notification aggregation reference ID 1, and the max_delay information.

[0192] At step 825, an event trigger for subscription 1 may occur at the UPF (81). The event trigger for subscription 1 may be a trigger for an event related to the first event subscription generated based on the first subscription message. In response to the event trigger for subscription 1, the UPF (81) may collect data or generate an event report corresponding to the first event subscription. The UPF (81) may start a max_delay timer or may start measuring a max_delay duration for subscription 1 based on the max_delay information. During the max_delay duration for subscription 1 (i.e., UE 1), the UPF (81) may wait for another event report associated with the same Notification aggregation reference ID 1.

[0193] At step 830, the UPF (81) may transmit, to the NF service consumer (AF / NWDAF) (82), a notification report for subscription 1. The notification report transmitted at step 830 may include an event report or UPF data corresponding to subscription 1 (i.e., UE 1). In an embodiment, if no other event report associated with the same Notification aggregation reference ID 1 is generated before the max_delay duration for subscription 1 expires, the UPF (81) may transmit the notification report for subscription 1 without combining it with another event report. Accordingly, even though the first event subscription and the second event subscription are associated with the same Notification aggregation reference ID 1, the event report for subscription 1 may be transmitted separately when the event trigger for subscription 2 does not occur within the max_delay duration for subscription 1 (i.e., UE 1).

[0194] At step 835, an event trigger for subscription 2 may occur at the UPF (81). The event trigger for subscription 2 may be a trigger for an event related to the second event subscription generated based on the second subscription message. In response to the event trigger for subscription 2, the UPF (81) may collect data or generate an event report corresponding to the second event subscription. The UPF (81) may start a max_delay timer or may start measuring a max_delay duration for subscription 2 based on the max_delay information associated with the second event subscription. During the max_delay duration for subscription 2, the UPF (81) may wait for another event report associated with the same Notification aggregation reference ID 1.

[0195] At step 840, the UPF (81) may transmit, to the NF service consumer (AF / NWDAF) (82), a notification report for subscription 2. The notification report transmitted at step 840 may include an event report or UPF data corresponding to subscription 2 (i.e., UE 2). In an embodiment, if no other event report associated with the same Notification aggregation reference ID 1 is generated before the max_delay duration for subscription 2 expires, the UPF (81) may transmit the notification report for subscription 2 (i.e., UE 2) without combining it with another event report.

[0196] As described above with reference to Figure 8, even when multiple subscriptions are associated with the same notification aggregation reference ID, the UPF (81) may separately transmit event reports if event triggers for the multiple subscriptions do not occur within a relevant max_delay duration. For example, when the event trigger for subscription 2 occurs after the max_delay duration for subscription 1 expires, the UPF (81) may transmit the notification report for subscription 1 at step 830 and may separately transmit the notification report for subscription 2 at step 840. Accordingly, the UPF (81) may perform notification aggregation while also satisfying a maximum delay condition indicated by reporting suggestion information, thereby preventing aggregation from delaying an event report beyond an allowed maximum delay time.

[0197] Figure 9 illustrates an event exposure service procedure in which event reports are partially aggregated based on a notification aggregation reference ID and max_delay information according to an embodiment of the present disclosure.

[0198] Referring to Figure 9, a UPF (91) and an NF service consumer (AF / NWDAF) (92) may correspond to the UPF (81) and the NF service consumer (AF / NWDAF) (82) of Figure 8, the UPF (71) and the NF service consumer (AF / NWDAF) (72) of Figure 7, the UPF (61) and the NF service consumer (62) of Figure 6, the UPF (51) and the NF service consumer (AF / NWDAF) (52) of Figure 5, the UPF (41) and the NF service consumer (AF / NWDAF) (42) of Figure 4, the UPF1 (31) and / or UPF2 (32) and the NF service consumer (AF / NWDAF) (34) of Figure 3, the UPF1 (21) and / or UPF2 (22) and the NF service consumer (AF / NWDAF) (23) of Figure 2, and the UPF (12) and the NF service consumer (11) of Figure 1.

[0199] As illustrated in Figure 9, the NF service consumer (AF / NWDAF) (92) may include a notification aggregation reference ID and reporting suggestion information in messages for subscribing to UPF event reports or UPF data. The reporting suggestion information may include max_delay information. In an embodiment, the max_delay information may define a maximum delay duration during which the UPF (91) may wait for another event report associated with the same notification aggregation reference ID before transmitting a notification message. Figure 9 illustrates a case in which some event reports associated with the same notification aggregation reference ID are generated within a max_delay duration and are aggregated, while another event report associated with the same notification aggregation reference ID is generated after the combined notification message has already been transmitted and is therefore separately reported.

[0200] At step 905, the NF service consumer (AF / NWDAF) (92) may transmit, to the UPF (91), a first subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The first subscription message may include one or more of first targets (e.g., Target = UE IP address 1), a first notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"), and reporting suggestion information including max_delay information. The first subscription message may be related to a first event subscription corresponding to a first target UE or a first target session.

[0201] At step 910, the UPF (91) may transmit, to the NF service consumer (AF / NWDAF) (92), a first response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the first subscription message transmitted at step 905. The first response message may indicate that the first subscription message has been accepted or that a subscription resource corresponding to the first event subscription has been created. Accordingly, the UPF (91) may maintain a subscription context associated with the first event subscription, the Notification aggregation reference ID 1, and the max_delay information.

[0202] At step 915, the NF service consumer (AF / NWDAF) (92) may transmit, to the UPF (91), a second subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The second subscription message may include one or more of second targets (e.g., Target = UE IP address 2), the same first notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"), and reporting suggestion information including max_delay information. The second subscription message may be related to a second event subscription corresponding to a second target UE or a second target session.

[0203] At step 920, the UPF (91) may transmit, to the NF service consumer (AF / NWDAF) (92), a second response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the second subscription message transmitted at step 915. The second response message may indicate that the second subscription message has been accepted or that a subscription resource corresponding to the second event subscription has been created. Accordingly, the UPF (91) may maintain a subscription context associated with the second event subscription, the Notification aggregation reference ID 1, and the max_delay information.

[0204] At step 925, the NF service consumer (AF / NWDAF) (92) may transmit, to the UPF (91), a third subscription message (e.g., a Nupf_EventExposure_Subscribe request message) for subscribing to UPF event reports or UPF data. The third subscription message may include one or more of third targets (e.g., Target = UE IP address 3), the same first notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"), and reporting suggestion information including max_delay information. The third subscription message may be related to a third event subscription corresponding to a third target UE or a third target session. Since the first to third subscription messages include the same Notification aggregation reference ID 1, the first to third event subscriptions may be recognized by the UPF (91) as subscriptions for which event reports can be aggregated or combined together when an aggregation condition is satisfied.

[0205] At step 930, the UPF (91) may transmit, to the NF service consumer (AF / NWDAF) (92), a third response message (e.g., a Nupf_EventExposure_Subscribe response message) corresponding to the third subscription message transmitted at step 925. The third response message may indicate that the third subscription message has been accepted or that a subscription resource corresponding to the third event subscription has been created. Accordingly, the UPF (91) may maintain a subscription context associated with the third event subscription, the Notification aggregation reference ID 1, and the max_delay information.

[0206] At step 935, an event trigger for subscription 1 may occur at the UPF (91). The event trigger for subscription 1 may be a trigger for an event related to the first event subscription generated based on the first subscription message. In response to the event trigger for subscription 1, the UPF (91) may collect data or generate an event report corresponding to the first event subscription. The UPF (91) may start a max_delay timer or may start measuring a max_delay duration for subscription 1 based on the max_delay information. During the max_delay duration for subscription 1, the UPF (91) may wait for another event report associated with the same Notification aggregation reference ID 1.

[0207] At step 940, an event trigger for subscription 2 may occur at the UPF (91) before the max_delay duration for subscription 1 expires. The event trigger for subscription 2 may be a trigger for an event related to the second event subscription generated based on the second subscription message. In response to the event trigger for subscription 2, the UPF (91) may collect data or generate an event report corresponding to the second event subscription. Since the second event subscription is associated with the same Notification aggregation reference ID 1 as the first event subscription, and since the event trigger for subscription 2 occurs before the max_delay duration for subscription 1 expires, the UPF (91) may determine that the event report corresponding to subscription 2 can be combined with the event report corresponding to subscription 1.

[0208] At step 945, the UPF (91) may transmit, to the NF service consumer (AF / NWDAF) (92), a combined notification message for two reports. The combined notification message transmitted at step 945 may include an event report corresponding to subscription 1 (i.e., UE 1), and an event report corresponding to subscription 2 (i.e., UE 2). The UPF (91) may transmit the combined notification message at step 945 when the max_delay duration for subscription 1 expires, when a reporting period for one or more subscribed events is completed, based on another parameter, and / or based on local configuration. In an embodiment, the combined notification message may include the Notification aggregation reference ID 1 and / or one or more notification correlation IDs associated with the first event subscription and the second event subscription.

[0209] At step 950, an event trigger for subscription 3 may occur at the UPF (91). The event trigger for subscription 3 may be a trigger for an event related to the third event subscription generated based on the third subscription message. In an embodiment, the event trigger for subscription 3 may occur after the combined notification message for subscription 1 and subscription 2 has been transmitted at step 945. In response to the event trigger for subscription 3, the UPF (91) may collect data or generate an event report corresponding to the third event subscription. Although the third event subscription is associated with the same Notification aggregation reference ID 1 as the first event subscription and the second event subscription, the event report corresponding to subscription 3 may not be combined with the event reports corresponding to subscription 1 and subscription 2 because the combined notification message for subscription 1 and subscription 2 has already been transmitted.

[0210] At step 955, the UPF (91) may transmit, to the NF service consumer (AF / NWDAF) (92), a notification report for subscription 3. The notification report transmitted at step 955 may include an event report or UPF data corresponding to subscription 3, for example, a report for UE 3. In an embodiment, the UPF (91) may transmit the notification report for subscription 3 separately when the event trigger for subscription 3 occurs after the aggregation window or max_delay duration used for the combined notification message of step 945 has expired, or after the combined notification message has already been transmitted. The notification report transmitted at step 955 may include the Notification aggregation reference ID 1 and / or a notification correlation ID associated with the third event subscription.

[0211] As described above with reference to Figure 9, even when three or more subscriptions are associated with the same notification aggregation reference ID, the UPF (91) may aggregate only event reports generated within an applicable max_delay duration or aggregation window. For example, when the event trigger for subscription 2 occurs before the max_delay duration for subscription 1 expires, the UPF (91) may transmit a combined notification message including the event reports for subscription 1 and subscription 2 at step 945. When the event trigger for subscription 3 occurs after the combined notification message has been transmitted, the UPF (91) may separately transmit a notification report for subscription 3 at step 955. Accordingly, the UPF (91) may flexibly aggregate event reports that satisfy an aggregation condition while separately reporting event reports that do not satisfy the aggregation timing condition, thereby reducing notification signaling while satisfying a maximum delay condition indicated by reporting suggestion information.

[0212] Figure 10 illustrates an event exposure service procedure in which an NF service consumer subscribes to UPF event reports or UPF data via a PCF according to an embodiment of the present disclosure.

[0213] Referring to Figure 10, UPF2 (101) and UPF1 (102) may correspond to the UPF (91) of Figure 9, the UPF (81) of Figure 8, the UPF (71) of Figure 7, the UPF (61) of Figure 6, the UPF (51) of Figure 5, the UPF (41) of Figure 4, the UPF1 (31) and / or UPF2 (32) of Figure 3, the UPF1 (21) and / or UPF2 (22) of Figure 2, and the UPF (12) of Figure 1. In addition, an NF service consumer (AF / NWDAF) (105) may correspond to the NF service consumer (AF / NWDAF) (92) of Figure 9, the NF service consumer (AF / NWDAF) (82) of Figure 8, the NF service consumer (AF / NWDAF) (72) of Figure 7, the NF service consumer (62) of Figure 6, the NF service consumer (AF / NWDAF) (52) of Figure 5, the NF service consumer (AF / NWDAF) (42) of Figure 4, the NF service consumer (AF / NWDAF) (34) of Figure 3, the NF service consumer (AF / NWDAF) (23) of Figure 2, and the NF service consumer (11) of Figure 1. An SMF (103) may be a session management function, and a PCF (104) may be a policy control function.

[0214] As illustrated in Figure 10, the NF service consumer (AF / NWDAF) (105) may request the PCF (104) to receive notifications related to certain UPF events or UPF data. In an embodiment, the NF service consumer (AF / NWDAF) (105) may include a notification aggregation reference ID in order to inform a UPF, via one or more intermediate network functions, that event reports or UPF data associated with multiple target UEs, multiple target sessions, or multiple event subscriptions are to be combined or aggregated into a single notification message.

[0215] At step 1005, the NF service consumer (AF / NWDAF) (105) may decide to receive notifications related to certain UPF events or UPF data. For example, the NF service consumer (AF / NWDAF) (105) may decide to receive notifications related to one or more events associated with a target UE, a plurality of target UEs, a target session, a plurality of target sessions, or a particular type of UPF data. In an embodiment, the NF service consumer (AF / NWDAF) (105) may decide to receive a combined notification for multiple target UEs or multiple target sessions, and may therefore determine to include a notification aggregation reference ID in a message transmitted toward the PCF (104).

[0216] At step 1010, the NF service consumer (AF / NWDAF) (105) may transmit, to the policy control function (PCF) (104), a message for requesting notification related to UPF events or UPF data. The message transmitted at step 1010 may be, for example, an Npcf_PolicyAuthorization_Create message, an Npcf_PolicyAuthorization_Update message, or an Npcf_PolicyAuthorization_Subscribe message. The message may include one or more of a UE address, information related to an event or data that is to be notified (e.g., related to header payload related events), information related to event reporting (e.g., reporting suggestion information, which may include max_delay or reporting time information for the report), a notification target address, a notification correlation ID, and a notification aggregation reference ID. In an embodiment, the notification aggregation reference ID may be used when the NF service consumer (AF / NWDAF) (105) wants to receive a combined notification for multiple target UEs or multiple target sessions together. The NF service consumer (AF / NWDAF) (105) may transmit similar messages to the PCF (104) for other target UEs with corresponding UE addresses.

[0217] At step 1015, the PCF (104) may transmit, to the SMF (103), a message based on the message received from the NF service consumer (AF / NWDAF) (105). The message transmitted at step 1015 may be, for example, an Nsmf_SMPolicyControl UpdateNotify message. The message may include one or more of an SM policy association ID or an SM policy reference, a policy and charging control (PCC) rule ID, information related to an event or data that is to be notified, information related to event reporting (e.g., max_delay or reporting time information), a notification target address, a notification correlation ID, and a notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"). In an embodiment, the PCF (104) may transmit the notification aggregation reference ID to the SMF (103) only when the SMF (103) has indicated support of a notification aggregation feature. The PCF (104) may transmit similar messages to the SMF (103) for other target UEs with corresponding UE addresses based on the messages received from the NF service consumer (AF / NWDAF) (105). In an embodiment, step 1015 may be performed as soon as the PCF (104) receives corresponding messages from the NF service consumer (AF / NWDAF) (105).

[0218] At step 1020, the SMF (103) may transmit, to UPF1 (102), a message for subscribing to UPF event reports or UPF data. The message transmitted at step 1020 may be, for example, an N4 Session Update message or a Nupf_EventExposure_Subscribe message. The message may include one or more of an N4 session ID, a UE address, information related to an event that is to be notified, a notification target address, a notification correlation ID, and a notification aggregation reference ID. In an embodiment, the SMF (103) may transmit the notification aggregation reference ID to UPF1 (102) only when UPF1 (102) supports the notification aggregation feature. Alternatively, the SMF (103) may transmit a notification aggregation indication to UPF1 (102) when UPF1 (102) supports the notification aggregation feature.

[0219] At step 1025, the SMF (103) may transmit, to UPF1 (102), another message for subscribing to UPF event reports or UPF data. The message transmitted at step 1025 may be, for example, an N4 Session Update message or a Nupf_EventExposure_Subscribe message, and may include a notification aggregation reference ID. In an embodiment, when the same UPF handles a session targeted by a message received from the PCF (104), the SMF (103) may transmit the message of step 1025 to UPF1 (102), which is the same UPF that receives the message of step 1020. The message transmitted at step 1025 may be based on one of the messages received from the PCF (104) at step 1015.

[0220] At step 1030, the SMF (103) may transmit, to UPF2 (101), another message for subscribing to UPF event reports or UPF data. The message transmitted at step 1030 may be, for example, an N4 Session Update message or a Nupf_EventExposure_Subscribe message, and may include a notification aggregation reference ID. In an embodiment, when a different UPF handles a session targeted by a message received from the PCF (104), the SMF (103) may transmit the message of step 1030 to UPF2 (101), which is different from UPF1 (102). In an embodiment, step 1020, step 1025, and step 1030 may be performed as soon as the SMF (103) receives corresponding messages from the PCF (104) at step 1015.

[0221] At step 1035, UPF1 (102) may start collecting data and / or start generating reports for events based on information received from the SMF (103) in step 1020 and step 1025. In an embodiment, UPF1 (102) may collect data or generate event reports for a plurality of target UEs, target sessions, or event subscriptions based on the information received from the SMF (103). For example, when the messages received by UPF1 (102) include the same notification aggregation reference ID, UPF1 (102) may determine that event reports generated based on the messages may be aggregated or combined together. Although Figure 10 illustrates that UPF1 (102) collects data and / or generates reports based on information received in step 1020 and step 1025, UPF2 (101) may also collect data and / or generate reports based on information received from the SMF (103) in step 1030.

[0222] At step 1040, when UPF1 (102) is triggered to transmit a notification message, UPF1 (102) may transmit, to the NF service consumer (AF / NWDAF) (105), a Nupf_EventExposure_Notify message. The Nupf_EventExposure_Notify message transmitted at step 1040 may include collected data or event reports for all related target UEs, target sessions, or subscriptions for which UPF1 (102) received the same notification aggregation reference ID from the SMF (103). For example, the Nupf_EventExposure_Notify message may include a combined or aggregated notification for two reports. In an embodiment, UPF1 (102) may determine to transmit the combined notification message, or a single notification message for multiple target UEs, multiple target sessions, or multiple event-subscription-related messages received by UPF1 (102), based on presence of the same notification aggregation reference ID.

[0223] In an embodiment, UPF1 (102) may determine to transmit the combined notification message based on one or more of the options described above in the present disclosure. For example, UPF1 (102) may determine to transmit the combined notification message based on presence of a notification aggregation indication, as described with reference to Figure 5. As another example, UPF1 (102) may determine to transmit the combined notification message based on presence of the same notification correlation ID, as described with reference to Figure 6. As another example, UPF1 (102) may determine to transmit the combined notification message based on information of multiple target sessions or UE IDs included in one subscription message. Therefore, although Figure 10 mainly describes the use of the notification aggregation reference ID, the procedure of Figure 10 may also be applied to a case where the UPF determines whether to aggregate or combine reports based on other aggregation information.

[0224] As described above with reference to Figure 10, the NF service consumer (AF / NWDAF) (105) may subscribe to UPF event reports or UPF data through the PCF (104) and the SMF (103). The PCF (104) may deliver aggregation-related information, such as a notification aggregation reference ID, to the SMF (103), and the SMF (103) may deliver the aggregation-related information to a corresponding UPF. The UPF may determine whether event reports associated with multiple target UEs, multiple target sessions, or multiple event subscriptions are to be combined or aggregated based on the aggregation-related information received from the SMF (103). Accordingly, the UPF may transmit a single notification message including event reports for multiple related subscriptions, thereby reducing the number of notification messages transmitted to the NF service consumer (AF / NWDAF) (105).

[0225] Figure 11 illustrates an event exposure service procedure in which an NF service consumer subscribes to UPF event reports or UPF data via a PCF using a notification aggregation indication according to an embodiment of the present disclosure.

[0226] Referring to Figure 11, UPF2 (111) and UPF1 (112) may correspond to UPF2 (101) and UPF1 (102) of Figure 10, the UPF (91) of Figure 9, the UPF (81) of Figure 8, the UPF (71) of Figure 7, the UPF (61) of Figure 6, the UPF (51) of Figure 5, the UPF (41) of Figure 4, the UPF1 (31) and / or UPF2 (32) of Figure 3, the UPF1 (21) and / or UPF2 (22) of Figure 2, and the UPF (12) of Figure 1. In addition, an NF service consumer (AF / NWDAF) (115) may correspond to the NF service consumer (AF / NWDAF) (105) of Figure 10, the NF service consumer (AF / NWDAF) (92) of Figure 9, the NF service consumer (AF / NWDAF) (82) of Figure 8, the NF service consumer (AF / NWDAF) (72) of Figure 7, the NF service consumer (62) of Figure 6, the NF service consumer (AF / NWDAF) (52) of Figure 5, the NF service consumer (AF / NWDAF) (42) of Figure 4, the NF service consumer (AF / NWDAF) (34) of Figure 3, the NF service consumer (AF / NWDAF) (23) of Figure 2, and the NF service consumer (11) of Figure 1. An SMF (113) may be a session management function, and a PCF (114) may be a policy control function.

[0227] As illustrated in Figure 11, the NF service consumer (AF / NWDAF) (115) may request the PCF (114) to receive notifications related to certain UPF events or UPF data. In an embodiment, the NF service consumer (AF / NWDAF) (115) may include a notification aggregation indication in order to inform a UPF, via one or more intermediate network functions, that event reports or UPF data associated with multiple target UEs, multiple target sessions, or multiple event subscriptions may be combined or aggregated into a single notification message. The procedure of Figure 11 may be similar to the procedure of Figure 10, except that the notification aggregation indication may be used instead of the notification aggregation reference ID.

[0228] At step 1105, the NF service consumer (AF / NWDAF) (115) may decide to receive notifications related to certain UPF events or UPF data. For example, the NF service consumer (AF / NWDAF) (115) may decide to receive notifications related to one or more events associated with a target UE, a plurality of target UEs, a target session, a plurality of target sessions, or a particular type of UPF data. In an embodiment, the NF service consumer (AF / NWDAF) (115) may decide to receive a combined notification for multiple target UEs or multiple target sessions, and may therefore determine to include a notification aggregation indication in a message transmitted toward the PCF (114).

[0229] At step 1110, the NF service consumer (AF / NWDAF) (115) may transmit, to the policy control function (PCF) (114), a message for requesting notification related to UPF events or UPF data. The message transmitted at step 1110 may be, for example, an Npcf_PolicyAuthorization_Create message, an Npcf_PolicyAuthorization_Update message, or an Npcf_PolicyAuthorization_Subscribe message. The message may include one or more of a UE address, information related to an event or data that is to be notified (e.g., related to header payload related events), information related to event reporting (e.g., reporting suggestion information, which may include max_delay or reporting time information for the report), a notification target address, a notification correlation ID, and a notification aggregation indication. In an embodiment, the notification aggregation indication may be used when the NF service consumer (AF / NWDAF) (115) wants to receive a combined notification for multiple target UEs or multiple target sessions together. The NF service consumer (AF / NWDAF) (115) may transmit similar messages to the PCF (114) for other target UEs with corresponding UE addresses.

[0230] At step 1115, the PCF (114) may transmit, to the SMF (113), a message based on the message received from the NF service consumer (AF / NWDAF) (115). The message transmitted at step 1115 may be, for example, an Nsmf_SMPolicyControl UpdateNotify message. The message may include one or more of an SM policy association ID or an SM policy reference, information related to an event or data that is to be notified, information related to event reporting (e.g., max_delay or reporting time information), a notification target address, a notification correlation ID, and a notification aggregation indication. In an embodiment, the PCF (114) may transmit the notification aggregation indication to the SMF (113) only when the SMF (113) has indicated support of a notification aggregation feature. The PCF (114) may transmit similar messages to the SMF (113) for other target UEs with corresponding UE addresses based on the messages received from the NF service consumer (AF / NWDAF) (115). In an embodiment, step 1115 may be performed as soon as the PCF (114) receives corresponding messages from the NF service consumer (AF / NWDAF) (115).

[0231] At step 1120, the SMF (113) may transmit, to UPF1 (112), a message for subscribing to UPF event reports or UPF data. The message transmitted at step 1120 may be, for example, an N4 Session Update message or a Nupf_EventExposure_Subscribe message. The message may include one or more of an N4 session ID, a UE address, information related to an event that is to be notified, a notification target address, a notification correlation ID, and a notification aggregation indication. In an embodiment, the SMF (113) may transmit the notification aggregation indication to UPF1 (112) only when UPF1 (112) supports the notification aggregation feature.

[0232] At step 1125, the SMF (113) may transmit, to UPF1 (112), another message for subscribing to UPF event reports or UPF data. The message transmitted at step 1125 may be, for example, an N4 Session Update message or a Nupf_EventExposure_Subscribe message, and may include a notification aggregation indication. In an embodiment, when the same UPF handles a session targeted by a message received from the PCF (114), the SMF (113) may transmit the message of step 1125 to UPF1 (112), which is the same UPF that receives the message of step 1120. The message transmitted at step 1125 may be based on one of the messages received from the PCF (114) at step 1115.

[0233] At step 1130, the SMF (113) may transmit, to UPF2 (111), another message for subscribing to UPF event reports or UPF data. The message transmitted at step 1130 may be, for example, an N4 Session Update message or a Nupf_EventExposure_Subscribe message, and may include a notification aggregation indication. In an embodiment, when a different UPF handles a session targeted by a message received from the PCF (114), the SMF (113) may transmit the message of step 1130 to UPF2 (111), which is different from UPF1 (112). In an embodiment, step 1120, step 1125, and step 1130 may be performed as soon as the SMF (113) receives corresponding messages from the PCF (114) at step 1115.

[0234] At step 1135, UPF1 (112) may start collecting data and / or start generating reports for events based on information received from the SMF (113) in step 1120 and step 1125. In an embodiment, UPF1 (112) may collect data or generate event reports for a plurality of target UEs, target sessions, or event subscriptions based on the information received from the SMF (113). For example, when the messages received by UPF1 (112) include the notification aggregation indication and satisfy an aggregation condition, UPF1 (112) may determine that event reports generated based on the messages may be aggregated or combined together. Although Figure 11 illustrates that UPF1 (112) collects data and / or generates reports based on information received in step 1120 and step 1125, UPF2 (111) may also collect data and / or generate reports based on information received from the SMF (113) in step 1130.

[0235] At step 1140, when UPF1 (112) is triggered to transmit a notification message, UPF1 (112) may transmit, to the NF service consumer (AF / NWDAF) (115), a Nupf_EventExposure_Notify message. The Nupf_EventExposure_Notify message transmitted at step 1140 may include collected data or event reports for related target UEs, target sessions, or subscriptions for which UPF1 (112) received the notification aggregation indication from the SMF (113). For example, the Nupf_EventExposure_Notify message may include a combined or aggregated notification for two reports. In an embodiment, UPF1 (112) may determine to transmit the combined notification message, or a single notification message for multiple target UEs, multiple target sessions, or multiple event-subscription-related messages received by UPF1 (112), based on presence of the notification aggregation indication and / or based on another condition, such as the same notification target address or the same notification correlation ID.

[0236] In an embodiment, UPF1 (112) may determine to transmit the combined notification message based on one or more of the options described above in the present disclosure. For example, UPF1 (112) may determine to transmit the combined notification message based on presence of a notification aggregation indication, as described with reference to Figure 5. As another example, UPF1 (112) may determine to transmit the combined notification message based on presence of the same notification correlation ID, as described with reference to Figure 6. As another example, UPF1 (112) may determine to transmit the combined notification message based on information of multiple target sessions or UE IDs included in one subscription message. Therefore, although Figure 11 mainly describes the use of the notification aggregation indication in a procedure via the PCF (114) and the SMF (113), the procedure of Figure 11 may also be applied to a case where the UPF determines whether to aggregate or combine reports based on other aggregation information.

[0237] As described above with reference to Figure 11, the NF service consumer (AF / NWDAF) (115) may subscribe to UPF event reports or UPF data through the PCF (114) and the SMF (113). The PCF (114) may deliver aggregation-related information, such as a notification aggregation indication, to the SMF (113), and the SMF (113) may deliver the aggregation-related information to a corresponding UPF. The UPF may determine whether event reports associated with multiple target UEs, multiple target sessions, or multiple event subscriptions are to be combined or aggregated based on the aggregation-related information received from the SMF (113). Accordingly, the UPF may transmit a single notification message including event reports for multiple related subscriptions, thereby reducing the number of notification messages transmitted to the NF service consumer (AF / NWDAF) (115).

[0238] Figure 12 illustrates an event exposure service procedure in which a UPF registers information on a capability of notification aggregation with an NRF and an NF service consumer discovers a UPF supporting the capability of notification aggregation according to an embodiment of the present disclosure.

[0239] Referring to Figure 12, a UPF (121) may correspond to UPF2 (111) and / or UPF1 (112) of Figure 11, UPF2 (101) and / or UPF1 (102) of Figure 10, the UPF (91) of Figure 9, the UPF (81) of Figure 8, the UPF (71) of Figure 7, the UPF (61) of Figure 6, the UPF (51) of Figure 5, the UPF (41) of Figure 4, the UPF1 (31) and / or UPF2 (32) of Figure 3, the UPF1 (21) and / or UPF2 (22) of Figure 2, and the UPF (12) of Figure 1. In addition, an NF service consumer (AF / NWDAF) (123) may correspond to the NF service consumer (AF / NWDAF) (115) of Figure 11, the NF service consumer (AF / NWDAF) (105) of Figure 10, the NF service consumer (AF / NWDAF) (92) of Figure 9, the NF service consumer (AF / NWDAF) (82) of Figure 8, the NF service consumer (AF / NWDAF) (72) of Figure 7, the NF service consumer (62) of Figure 6, the NF service consumer (AF / NWDAF) (52) of Figure 5, the NF service consumer (AF / NWDAF) (42) of Figure 4, the NF service consumer (AF / NWDAF) (34) of Figure 3, the NF service consumer (AF / NWDAF) (23) of Figure 2, and the NF service consumer (11) of Figure 1. An NRF (122) may be a network repository function configured to support registration and discovery of network functions.

[0240] As illustrated in Figure 12, the UPF (121) may register information on a capability of notification aggregation with the NRF (122). The capability of notification aggregation may indicate that the UPF (121) supports aggregation or combination of event reports corresponding to multiple event subscriptions into a single notification message. In an embodiment, the NF service consumer (AF / NWDAF) (123) may discover, through the NRF (122), one or more UPFs supporting the capability of notification aggregation and may select a UPF that supports the capability of notification aggregation. Accordingly, the NF service consumer (AF / NWDAF) (123) may transmit a subscription message including aggregation-related information, such as a notification aggregation reference ID, to the selected UPF.

[0241] At step 1205, the UPF (121) may transmit, to the NRF (122), a registration message. The registration message may be, for example, an Nnrf_Register message. In an embodiment, the registration message may include information on a capability of notification aggregation of the UPF (121). The information on the capability of notification aggregation may indicate that the UPF (121) supports a function for aggregating or combining event reports associated with multiple event subscriptions into a single notification message.

[0242] At step 1210, the NRF (122) may transmit, to the UPF (121), a response message corresponding to the registration message transmitted at step 1205. The response message transmitted at step 1210 may indicate that the registration of the UPF (121) has been accepted or that the information on the capability of notification aggregation of the UPF (121) has been stored in the NRF (122). Accordingly, the NRF (122) may maintain information indicating that the UPF (121) supports the capability of notification aggregation.

[0243] At step 1215, the NF service consumer (AF / NWDAF) (123) may decide to discover one or more UPFs for a target UE, a plurality of target UEs, a Data Network Name (DNN), and / or Single Network Slice Selection Assistance Information (S-NSSAI). In an embodiment, the NF service consumer (AF / NWDAF) (123) may decide to discover one or more UPFs based on a need to subscribe to UPF event reports or UPF data for a target UE, a target session, or a target service context. The NF service consumer (AF / NWDAF) (123) may also decide to discover a UPF that supports notification aggregation in order to minimize excessive notification messages.

[0244] At step 1220, the NF service consumer (AF / NWDAF) (123) may transmit, to the NRF (122), a discovery request message. The discovery request message may be, for example, an Nnrf_Discover Request message. The discovery request message may include discovery criteria for discovering one or more UPFs. For example, the discovery criteria may include information related to a target UE, target UEs, a DNN, S-NSSAI, and / or a capability of notification aggregation. In an embodiment, the discovery request message may request discovery of one or more UPFs supporting the capability of notification aggregation.

[0245] At step 1225, the NRF (122) may transmit, to the NF service consumer (AF / NWDAF) (123), a discovery response message. The discovery response message may be, for example, an Nnrf_Discover Response message. The discovery response message may include information on one or more selected UPFs. In an embodiment, the discovery response message may optionally include information on whether the selected UPF supports the capability of notification aggregation. For example, the discovery response message may include information indicating that the UPF (121) supports the capability of notification aggregation.

[0246] At step 1230, the NF service consumer (AF / NWDAF) (123) may determine whether to select a UPF based on the information received from the NRF (122). In an embodiment, the NF service consumer (AF / NWDAF) (123) may select only a UPF that supports the capability of notification aggregation in order to minimize excessive notifications. Alternatively or additionally, the NF service consumer (AF / NWDAF) (123) may decide to send a notification aggregation reference ID only when the selected UPF supports the capability of notification aggregation. For example, when the discovery response message indicates that the UPF (121) supports the capability of notification aggregation, the NF service consumer (AF / NWDAF) (123) may select the UPF (121) and may include aggregation-related information in a subsequent subscription message transmitted to the UPF (121).

[0247] At step 1235, the NF service consumer (AF / NWDAF) (123) may transmit, to the selected UPF (121), a subscription message for subscribing to UPF event reports or UPF data. The subscription message may be, for example, a Nupf_EventExposure_Subscribe request message. The subscription message may include one or more of a target, for example, Target = UE IP address1, and a notification aggregation reference ID, for example, Notification aggregation reference ID 1. In an embodiment, the subscription message may further include a notification target address or URI, a notification correlation ID, reporting suggestion information, max_delay information, or other event-related information. The notification aggregation reference ID may indicate that event reports associated with subscriptions including the same notification aggregation reference ID are to be aggregated or combined together.

[0248] At step 1240, the UPF (121) may transmit, to the NF service consumer (AF / NWDAF) (123), a response message corresponding to the subscription message transmitted at step 1235. The response message transmitted at step 1240 may be, for example, a Nupf_EventExposure_Subscribe response message. The response message may indicate that the subscription message has been accepted or that a subscription resource corresponding to the event subscription has been created. Accordingly, the UPF (121) may maintain a subscription context associated with the event subscription and the Notification aggregation reference ID 1.

[0249] At step 1245, the UPF (121) may transmit, to the NF service consumer (AF / NWDAF) (123), a notification message including combined or aggregated notification information. The notification message may be, for example, a Nupf_EventExposure_Notify message. In an embodiment, the notification message transmitted at step 1245 may include combined or aggregated notification information for two reports. For example, when two event reports are associated with the same notification aggregation reference ID and satisfy an aggregation condition, the UPF (121) may include the two event reports in a single notification message and transmit the single notification message to the NF service consumer (AF / NWDAF) (123). The notification message may include the notification aggregation reference ID and / or one or more notification correlation IDs corresponding to the aggregated event reports.

[0250] As described above with reference to Figure 12, the UPF (121) may register, with the NRF (122), information indicating that the UPF (121) supports the capability of notification aggregation. The NF service consumer (AF / NWDAF) (123) may discover the UPF (121) through the NRF (122) and may determine whether to select the UPF (121) based on the capability of notification aggregation. When the UPF (121) supports the capability of notification aggregation, the NF service consumer (AF / NWDAF) (123) may transmit a subscription message including aggregation-related information, such as a notification aggregation reference ID, to the UPF (121). Accordingly, the UPF (121) may transmit a combined or aggregated notification message for multiple reports, thereby reducing the number of notification messages transmitted from the UPF (121) to the NF service consumer (AF / NWDAF) (123).

[0251] Figure 13 illustrates an event exposure service procedure in which an NF service consumer subscribes to UPF event reports or UPF data via an SMF according to an embodiment of the present disclosure.

[0252] Referring to Figure 13, a UPF (131) may correspond to the UPF (121) of Figure 12, UPF2 (111) and / or UPF1 (112) of Figure 11, UPF2 (101) and / or UPF1 (102) of Figure 10, the UPF (91) of Figure 9, the UPF (81) of Figure 8, the UPF (71) of Figure 7, the UPF (61) of Figure 6, the UPF (51) of Figure 5, the UPF (41) of Figure 4, the UPF1 (31) and / or UPF2 (32) of Figure 3, the UPF1 (21) and / or UPF2 (22) of Figure 2, and the UPF (12) of Figure 1. In addition, an NF service consumer (AF / NWDAF) (134) may correspond to the NF service consumer (AF / NWDAF) (123) of Figure 12, the NF service consumer (AF / NWDAF) (115) of Figure 11, the NF service consumer (AF / NWDAF) (105) of Figure 10, the NF service consumer (AF / NWDAF) (92) of Figure 9, the NF service consumer (AF / NWDAF) (82) of Figure 8, the NF service consumer (AF / NWDAF) (72) of Figure 7, the NF service consumer (62) of Figure 6, the NF service consumer (AF / NWDAF) (52) of Figure 5, the NF service consumer (AF / NWDAF) (42) of Figure 4, the NF service consumer (AF / NWDAF) (34) of Figure 3, the NF service consumer (AF / NWDAF) (23) of Figure 2, and the NF service consumer (11) of Figure 1. An SMF (132) may be a session management function, and a UDM (133) may be a unified data management function.

[0253] As illustrated in Figure 13, the NF service consumer (AF / NWDAF) (134) may subscribe to UPF event reports or UPF data through the SMF (132). In an embodiment, the NF service consumer (AF / NWDAF) (134) may discover or identify the SMF (132) serving a target UE address or a UE session through the UDM (133), and may transmit, to the SMF (132), a subscription message including aggregation-related information, such as a notification aggregation reference ID. The SMF (132) may check the notification aggregation reference ID and provide the notification aggregation reference ID to the UPF (131) when the UPF (131) supports a notification aggregation feature.

[0254] At step 1305, the NF service consumer (AF / NWDAF) (134) may decide to discover one or more SMFs for a target UE session, a plurality of target UE sessions, a Data Network Name (DNN), and / or Single Network Slice Selection Assistance Information (S-NSSAI). For example, the NF service consumer (AF / NWDAF) (134) may decide to discover an SMF serving a target UE address or a target UE session in order to subscribe to UPF event reports or UPF data associated with the target UE or the target UE session.

[0255] At step 1310, the NF service consumer (AF / NWDAF) (134) may transmit, to the UDM (133), a request message for discovering or identifying the SMF (132) serving the target UE address or the target UE session. The request message may include information related to the target UE, the target UE address, the target UE session, the DNN, and / or the S-NSSAI. In an embodiment, the NF service consumer (AF / NWDAF) (134) may ask the UDM (133) for information on the SMF serving the target UE address or the UE session.

[0256] At step 1315, the UDM (133) may transmit, to the NF service consumer (AF / NWDAF) (134), a response message corresponding to the request message transmitted at step 1310. The response message may include information identifying the SMF (132) serving the target UE address or the target UE session. Accordingly, the NF service consumer (AF / NWDAF) (134) may determine the SMF (132) to which a subscription message for UPF event reports or UPF data is to be transmitted.

[0257] At step 1320, the NF service consumer (AF / NWDAF) (134) may transmit, to the SMF (132), a subscription message for subscribing to UPF event reports or UPF data. The subscription message transmitted at step 1320 may be, for example, an Nsmf_EventExposure_Subscribe message. The subscription message may include one or more of a target (e.g., Target = UE IP address 1), a notification target address, a notification correlation ID, and a notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"). In an embodiment, the notification aggregation reference ID may be used when the NF service consumer (AF / NWDAF) (134) wants to receive a combined notification for multiple target UEs, multiple target sessions, or multiple event subscriptions.

[0258] At step 1325, the SMF (132) may check the notification aggregation reference ID included in the subscription message received at step 1320. In an embodiment, the SMF (132) may determine whether the UPF (131) supports the notification aggregation feature. When the UPF (131) supports the notification aggregation feature, the SMF (132) may determine to provide the notification aggregation reference ID to the UPF (131). In contrast, when the UPF (131) does not support the notification aggregation feature, the SMF (132) may omit forwarding the notification aggregation reference ID or may process the subscription message without using the notification aggregation reference ID.

[0259] At step 1330, the SMF (132) may transmit, to the UPF (131), a message for subscribing to UPF event reports or UPF data. The message transmitted at step 1330 may be, for example, a Nupf_EventExposure_Subscribe message. The message may include one or more of a target (e.g., Target = UE IP address 1), a notification target address, a notification correlation ID, and the notification aggregation reference ID (e.g., "Notification aggregation reference ID 1"). In an embodiment, the SMF (132) may provide the notification aggregation reference ID to the UPF (131) only when the UPF (131) supports the notification aggregation feature. Based on the message received from the SMF (132), the UPF (131) may collect data or generate event reports associated with the target UE, the target session, or the corresponding event subscription.

[0260] At step 1335, the UPF (131) may transmit, to the NF service consumer (AF / NWDAF) (134), a Nupf_EventExposure_Notify message. The Nupf_EventExposure_Notify message transmitted at step 1335 may include combined or aggregated notification information for two reports. For example, when two event reports are associated with the same notification aggregation reference ID and satisfy an aggregation condition, the UPF (131) may include the two event reports in a single notification message and transmit the single notification message to the NF service consumer (AF / NWDAF) (134). The notification message may include the notification aggregation reference ID and / or one or more notification correlation IDs corresponding to the aggregated event reports.

[0261] In an embodiment, the UPF (131) may determine to transmit the combined notification message based on one or more of the options described above in the present disclosure. For example, the UPF (131) may determine to transmit the combined notification message based on presence of the same notification aggregation reference ID. As another example, the UPF (131) may determine to transmit the combined notification message based on presence of a notification aggregation indication, as described with reference to Figure 5. As another example, the UPF (131) may determine to transmit the combined notification message based on presence of the same notification correlation ID, as described with reference to Figure 6. As another example, the UPF (131) may determine to transmit the combined notification message based on information of multiple target sessions or UE IDs included in one subscription message.

[0262] As described above with reference to Figure 13, the NF service consumer (AF / NWDAF) (134) may discover the SMF (132) serving a target UE address or a target UE session through the UDM (133), and may subscribe to UPF event reports or UPF data through the SMF (132). The SMF (132) may deliver aggregation-related information, such as a notification aggregation reference ID, to the UPF (131) when the UPF (131) supports the notification aggregation feature. The UPF (131) may determine whether event reports associated with multiple target UEs, multiple target sessions, or multiple event subscriptions are to be combined or aggregated based on the aggregation-related information received from the SMF (132). Accordingly, the UPF (131) may transmit a single notification message including event reports for multiple related subscriptions, thereby reducing the number of notification messages transmitted to the NF service consumer (AF / NWDAF) (134).

[0263] Figure 14 illustrates a method performed by a UPF entity in a communication system according to an embodiment of the present disclosure.

[0264] Referring to Figure 14, the UPF entity performing the method of Figure 14 may correspond to the UPF (131) of Figure 13, the UPF (121) of Figure 12, UPF2 (111) and / or UPF1 (112) of Figure 11, UPF2 (101) and / or UPF1 (102) of Figure 10, the UPF (91) of Figure 9, the UPF (81) of Figure 8, the UPF (71) of Figure 7, the UPF (61) of Figure 6, the UPF (51) of Figure 5, the UPF (41) of Figure 4, the UPF1 (31) and / or UPF2 (32) of Figure 3, the UPF1 (21) and / or UPF2 (22) of Figure 2, and the UPF (12) of Figure 1.

[0265] As illustrated in Figure 14, the UPF entity may receive messages related to a plurality of event subscriptions, detect events corresponding to the plurality of event subscriptions, generate a single notification message by combining event reports corresponding to the detected events based on aggregation information, and transmit the single notification message to a notification target network entity. In an embodiment, the notification target network entity may be an NF service consumer, such as an AF entity or an NWDAF entity, or any other entity indicated by a notification target address or URI.

[0266] At step 1410, the UPF entity may receive a first message related to a first event subscription and a second message related to a second event subscription. The first message and the second message may include aggregation information for aggregating event notifications. In an embodiment, each of the first message and the second message may be a message for subscribing to UPF event reports or UPF data. For example, each of the first message and the second message may include a Nupf_EventExposure_Subscribe request message, an N4 Session Update message, or another message for causing the UPF entity to monitor a UPF event, collect UPF data, and / or generate an event report.

[0267] In an embodiment, the first message and the second message may include one or more of a target UE, a target UE address, a target session, an event type, information related to an event or data that is to be notified, a notification target address or URI, a notification correlation ID, an aggregation level, reporting suggestion information, delay information, and aggregation information. The aggregation information may include at least one of a reference identifier for notification aggregation, a notification aggregation indication, a notification correlation ID, information indicating multiple target sessions or UE IDs, or any other information usable for determining whether event reports corresponding to different event subscriptions are to be aggregated or combined together.

[0268] In an embodiment, the aggregation information may include a reference identifier for notification aggregation. For example, the reference identifier for notification aggregation may correspond to a notification aggregation reference ID described in pervious embodiments. When reference identifiers included in the first message and the second message are the same, the UPF entity may determine that event reports corresponding to the first event subscription and the second event subscription are related to each other and may be combined into a single notification message.

[0269] In an embodiment, the aggregation information may include an indication for notification aggregation. For example, the indication for notification aggregation may correspond to a notification aggregation indication described in pervious embodiments. The indication for notification aggregation may indicate that notifications or event reports corresponding to one or more event subscriptions may be combined together. In an embodiment, the UPF entity may combine event reports based on the notification aggregation indication and based on notification target addresses associated with the first message and the second message being the same. For example, when the first message and the second message include the notification aggregation indication and have the same notification target address or URI, the UPF entity may determine that event reports corresponding to the first message and the second message are to be transmitted through a single notification message.

[0270] In an embodiment, the first message and the second message may be received from at least one of an application function (AF) entity, a network data analytics function (NWDAF) entity, or a session management function (SMF) entity. For example, the first message and the second message may be directly received from an NF service consumer, such as an AF or NWDAF. Alternatively, the first message and the second message may be received from an SMF. In an embodiment, the first message and the second message may be received based on policy information generated by a policy control function (PCF) entity. For example, the PCF entity may generate or provide policy-related information including aggregation-related information, and the SMF entity may provide corresponding information to the UPF entity.

[0271] In an embodiment, before or in association with receiving the first message and the second message, the UPF entity may transmit, to a network repository function (NRF) entity, information on a capability of notification aggregation of the UPF entity. For example, the UPF entity may register information indicating that the UPF entity supports notification aggregation. In this case, the aggregation information may be included in the first message and the second message based on the UPF entity supporting notification aggregation. For example, an NF service consumer may discover a UPF entity supporting notification aggregation through the NRF entity, select the UPF entity, and transmit a subscription message including aggregation information to the UPF entity.

[0272] In an embodiment, the first message may include information identifying a plurality of target sessions or a plurality of UE IDs. The UPF entity may determine that event reports or UPF data corresponding to the plurality of target sessions or the plurality of UE IDs are to be combined together, and may generate a single notification message including the event reports or UPF data corresponding to the plurality of target sessions or the plurality of UE IDs.

[0273] At step 1420, the UPF entity may detect a first event corresponding to the first event subscription and a second event corresponding to the second event subscription. In an embodiment, the first event and the second event may be events subscribed to by the first message and the second message, respectively. The first event and the second event may each correspond to a UPF event, UPF data, collected data, a reporting condition, expiration of a reporting period, or a condition for generating an event report.

[0274] In an embodiment, detection of the first event or the second event may occur when a reporting period is over for a periodic reporting type, or when an event is detected for a continuous or event-triggered reporting type. For example, the UPF entity may detect an event when a subscribed QoS monitoring event, user data usage measurement event, user data usage trend statistics event, TSC management information event, UE NAT mapping information event, payload header handling information event, or another subscribed UPF event occurs. In response to detecting the first event, the UPF entity may generate or prepare a first event report corresponding to the first event subscription. In response to detecting the second event, the UPF entity may generate or prepare a second event report corresponding to the second event subscription.

[0275] In an embodiment, at least one of the first message or the second message may include delay information related to a maximum delay allowed for the UPF entity to transmit a notification message including an event report after an event corresponding to an event subscription is detected. The delay information may correspond to max_delay information or reporting time information included in reporting suggestion information. The delay information may indicate a maximum time for which the UPF entity may delay transmission of an event report in order to wait for another event report that can be aggregated or combined together.

[0276] In an embodiment, the UPF entity may start a timer based on the delay information in response to detecting the first event corresponding to the first event subscription. For example, when the first event is detected, the UPF entity may start a timer for a max_delay duration associated with the first event subscription. During the timer, the UPF entity may wait for another event report associated with the same aggregation information, such as the same notification aggregation reference ID, the same notification aggregation indication and same notification target address, or the same notification correlation ID. When the second event is detected before the timer expires, the UPF entity may determine that the first event report and the second event report can be combined together.

[0277] At step 1430, the UPF entity may generate, based on the aggregation information, a single notification message by combining a first event report for the first event and a second event report for the second event. In an embodiment, the single notification message may be a Nupf_EventExposure_Notify message including the first event report and the second event report. The single notification message may include combined or aggregated notification information for a plurality of reports, and may further include one or more of a notification aggregation reference ID, a notification aggregation indication, a notification correlation ID, a notification target address or URI, and information identifying event subscriptions corresponding to the first event report and the second event report.

[0278] In an embodiment, when the aggregation information includes a reference identifier for notification aggregation, the UPF entity may combine the first event report and the second event report based on reference identifiers included in the first message and the second message being the same. For example, when the first message and the second message include the same Notification aggregation reference ID 1, the UPF entity may determine that the first event report and the second event report are to be combined into the single notification message.

[0279] In an embodiment, when the aggregation information includes an indication for notification aggregation, the UPF entity may combine the first event report and the second event report based on notification target addresses associated with the first message and the second message being the same. For example, when the first message and the second message include the notification aggregation indication and indicate the same notification target address or URI, the UPF entity may determine that the first event report and the second event report are to be combined into the single notification message.

[0280] In an embodiment, when the first message and the second message include the same notification correlation ID, the UPF entity may determine that the first event report and the second event report are related to each other and may combine the first event report and the second event report into the single notification message. In this case, the same notification correlation ID may be used not only to allow the NF service consumer to correlate a notification message with a subscription, but also as information for determining whether multiple event reports are to be combined together.

[0281] In an embodiment, when a timer is started based on the delay information in response to detecting the first event, the UPF entity may combine the first event report and the second event report based on detecting the second event before the timer expires. For example, when the second event is detected within the max_delay duration associated with the first event, the UPF entity may include both the first event report and the second event report in the single notification message. In contrast, when the second event is not detected before the timer expires, the UPF entity may transmit a notification message including the first event report without waiting for the second event report. Accordingly, the UPF entity may aggregate event reports while satisfying the maximum delay allowed for transmission of a notification message.

[0282] At step 1440, the UPF entity may transmit, to a notification target network entity, the single notification message. In an embodiment, the notification target network entity may be identified based on a notification target address or URI included in at least one of the first message or the second message. The notification target network entity may be an NF service consumer, such as an AF entity or an NWDAF entity, or may be another entity configured to receive UPF event reports or UPF data.

[0283] In an embodiment, the UPF entity may transmit the single notification message based on expiry of the timer started based on the delay information. For example, when the timer expires after the first event report and the second event report have been combined, the UPF entity may transmit the single notification message including the first event report and the second event report to the notification target network entity. In another embodiment, the UPF entity may transmit the single notification message when a reporting period for one or more subscribed events is completed, based on another parameter, or based on local configuration.

[0284] In an embodiment, the single notification message transmitted at step 1440 may include information allowing the notification target network entity to identify subscriptions corresponding to the event reports included in the single notification message. For example, the single notification message may include one or more notification correlation IDs corresponding to the first event subscription and the second event subscription. The single notification message may also include the aggregation information, such as a notification aggregation reference ID or information indicating that the event reports have been aggregated.

[0285] As described above with reference to Figure 14, the UPF entity may receive a plurality of messages related to a plurality of event subscriptions, detect events corresponding to the plurality of event subscriptions, generate a single notification message by combining event reports corresponding to the detected events based on aggregation information, and transmit the single notification message to a notification target network entity. The aggregation information may include, for example, a reference identifier for notification aggregation, an indication for notification aggregation, a notification correlation ID, information on multiple target sessions or UE IDs, or any combination thereof. The UPF entity may further use delay information, such as max_delay information, to determine a time period during which event reports may be aggregated. Accordingly, the UPF entity may reduce the number of notification messages transmitted to an NF service consumer while satisfying a maximum delay condition for event reporting.

[0286] Figure 15 illustrates a method performed by a UPF entity for aggregating event reports based on delay information according to an embodiment of the present disclosure.

[0287] Referring to Figure 15, the UPF entity performing the method of Figure 15 may correspond to the UPF entity performing the method of Figure 14, the UPF (131) of Figure 13, the UPF (121) of Figure 12, UPF2 (111) and / or UPF1 (112) of Figure 11, UPF2 (101) and / or UPF1 (102) of Figure 10, the UPF (91) of Figure 9, the UPF (81) of Figure 8, the UPF (71) of Figure 7, the UPF (61) of Figure 6, the UPF (51) of Figure 5, the UPF (41) of Figure 4, the UPF1 (31) and / or UPF2 (32) of Figure 3, the UPF1 (21) and / or UPF2 (22) of Figure 2, and the UPF (12) of Figure 1.

[0288] As illustrated in Figure 15, the UPF entity may start a timer based on delay information when a first event corresponding to a first event subscription is detected, may detect a second event corresponding to a second event subscription before the timer expires, may generate a single notification message by combining a first event report and a second event report, and may transmit the single notification message based on expiry of the timer. The method of Figure 15 may be understood as a detailed embodiment of the method described with reference to Figure 14, particularly an embodiment in which the UPF entity controls a timing of notification aggregation using delay information, such as max_delay information.

[0289] Before step 1510, the UPF entity may receive a first message related to a first event subscription and a second message related to a second event subscription. The first message and the second message may include aggregation information for aggregating event notifications. In an embodiment, at least one of the first message or the second message may include delay information related to a maximum delay allowed for the UPF entity to transmit a notification message including an event report after an event corresponding to an event subscription is detected. The delay information may include max_delay information, reporting time information, or reporting suggestion information including the max_delay information or the reporting time information.

[0290] In an embodiment, the aggregation information may include a reference identifier for notification aggregation. For example, the first message and the second message may include the same notification aggregation reference ID. In this case, the UPF entity may determine that event reports corresponding to the first event subscription and the second event subscription can be combined together. In another embodiment, the aggregation information may include an indication for notification aggregation. In this case, the UPF entity may determine whether to combine event reports based on the indication for notification aggregation and based on notification target addresses associated with the first message and the second message being the same. In another embodiment, the UPF entity may determine whether to combine event reports based on the same notification correlation ID included in the first message and the second message, or based on information of multiple target sessions or UE IDs included in a subscription message.

[0291] At step 1510, the UPF entity may start a timer based on the delay information in response to detecting the first event corresponding to the first event subscription. The first event may be an event subscribed to by the first message. In an embodiment, the first event may be detected when a reporting period is over for a periodic reporting type, when an event is detected for a continuous or event-triggered reporting type, when UPF data is collected, or when a reporting condition associated with the first event subscription is satisfied. In response to detecting the first event, the UPF entity may generate or prepare a first event report corresponding to the first event subscription and may start the timer based on the delay information. The timer may correspond to a max_delay duration during which the UPF entity may wait for another event report that can be aggregated with the first event report.

[0292] In an embodiment, the delay information used at step 1510 may be received from an application function (AF) entity, a network data analytics function (NWDAF) entity, or a session management function (SMF) entity. For example, the first message and the second message including the delay information may be received from at least one of an AF entity, an NWDAF entity, or an SMF entity. In another embodiment, the first message and the second message may be received based on policy information generated by a policy control function (PCF) entity. For example, as described with reference to Figure 10 or Figure 11, the PCF may provide policy-related information including aggregation-related information or delay information to the SMF, and the SMF may provide corresponding information to the UPF entity.

[0293] In an embodiment, before receiving the first message and the second message, or before performing step 1510, the UPF entity may transmit, to a network repository function (NRF) entity, information on a capability of notification aggregation of the UPF entity. The UPF entity may register information indicating that the UPF entity supports notification aggregation. In this case, the aggregation information and / or the delay information may be included in the first message and the second message based on the UPF entity supporting notification aggregation.

[0294] At step 1520, the UPF entity may detect the second event before the timer expires. The second event may correspond to the second event subscription and may be an event subscribed to by the second message. In an embodiment, the second event may be detected when a reporting period is over, when an event is detected, when UPF data is collected, or when a reporting condition associated with the second event subscription is satisfied. In response to detecting the second event, the UPF entity may generate or prepare a second event report corresponding to the second event subscription.

[0295] In an embodiment, when the second event is detected before the timer expires, the UPF entity may determine whether the second event report can be combined with the first event report. For example, when the first message and the second message include the same notification aggregation reference ID, the UPF entity may determine that the first event report and the second event report are associated with the same aggregation group. As another example, when the first message and the second message include a notification aggregation indication and have the same notification target address or URI, the UPF entity may determine that the first event report and the second event report can be combined together. As another example, when the first message and the second message include the same notification correlation ID, the UPF entity may determine that the first event report and the second event report can be combined together.

[0296] At step 1530, the UPF entity may generate a single notification message combining the first event report and the second event report. In an embodiment, the single notification message may be generated based on detecting the second event before the timer expires and based on the first event report and the second event report satisfying an aggregation condition. The aggregation condition may include, for example, the first message and the second message including the same notification aggregation reference ID, the first message and the second message including a notification aggregation indication and having the same notification target address or URI, the first message and the second message including the same notification correlation ID, or the first event subscription and the second event subscription being associated with multiple target sessions or UE IDs to be reported together.

[0297] In an embodiment, the single notification message generated at step 1530 may be a Nupf_EventExposure_Notify message. The single notification message may include the first event report corresponding to the first event subscription and the second event report corresponding to the second event subscription. The single notification message may further include one or more of a notification aggregation reference ID, a notification aggregation indication, a notification correlation ID associated with the first event subscription, a notification correlation ID associated with the second event subscription, a notification target address or URI, and information identifying the first event subscription and the second event subscription. Accordingly, a notification target network entity receiving the single notification message may identify that the single notification message includes event reports corresponding to multiple event subscriptions.

[0298] At step 1540, the UPF entity may transmit, to a notification target network entity, the single notification message based on expiry of the timer. In an embodiment, the notification target network entity may be an NF service consumer, such as an AF entity or an NWDAF entity, or another entity indicated by a notification target address or URI included in the first message and / or the second message. The UPF entity may transmit the single notification message when the timer started at step 1510 expires. Accordingly, the UPF entity may delay transmission of the first event report within a maximum delay allowed by the delay information and may transmit the first event report and the second event report together when the timer expires.

[0299] In an embodiment, when the second event is detected before expiry of the timer, the UPF entity may combine the first event report and the second event report and transmit the single notification message based on expiry of the timer. In contrast, when the second event is not detected before expiry of the timer, the UPF entity may transmit a notification message including the first event report without combining the first event report with the second event report. Accordingly, the UPF entity may aggregate event reports when possible while preventing transmission of an event report from being delayed beyond the maximum delay indicated by the delay information.

[0300] As described above with reference to Figure 15, the UPF entity may use delay information to control a time window for aggregating event reports. When the first event corresponding to the first event subscription is detected, the UPF entity may start a timer based on the delay information. When the second event corresponding to the second event subscription is detected before the timer expires, the UPF entity may generate a single notification message by combining the first event report and the second event report. The UPF entity may then transmit the single notification message to the notification target network entity based on expiry of the timer. Accordingly, the UPF entity may reduce the number of notification messages transmitted to the notification target network entity while satisfying a maximum delay condition for event reporting.

[0301] Figure 16 is a block diagram of a base station (BS) according to an embodiment of the disclosure.

[0302] The BS 1600 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 1600 through a wireless channel. The BS 1600 may perform communication with a node or an entity of a network through wired or wireless communication.

[0303] Referring to Figure 16, the BS 1600 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1601, at least one processor (hereinafter, referred to as simply “processor”) 1602, and at least one memory (hereinafter, referred to as simply “memory”) 1603. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1601, the processor 1602, and the memory 1603 of the BS 1600 may operate. However, components of the BS 1600 are not limited to the exemplary components illustrated in Figure 16. In another embodiment, the BS 1600 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1601, the processor 1602, or the memory 1603 may be integrated in the form of one component.

[0304] The transceiver 1601 may be a communication circuit or communication circuitry that enables the BS 1600 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1601 may enable the BS 1600 to transmit or receive a signal to or from the UE through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 1601 may support various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1601) may include all subsequent generations of evolved wireless communications. According to an embodiment, the transceiver 1601 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 1601 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1601 may output a signal received through a wireless channel to the processor 1602 and may transmit, through a wireless channel, a signal output from the processor 1602.

[0305] Meanwhile, according to an embodiment of the present disclosure, the BS 1600 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 1600 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in Figure 16, when the BS 1600 performs wired communication, the BS 1600 may further include a separate network interface for wired communication in addition to the transceiver 1601. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0306] The processor 1602 may control general operations of the BS 1600 according to embodiments of the disclosure. The processor 1602 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1602 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1603, individually, collectively or in any combination thereof. Further, the processor 1602 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0307] The processor 1602 may be electrically, operatively, and / or communicatively coupled to the transceiver 1601 to control the transceiver 1601.

[0308] The processor 1602 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1602 may be included in one chip (or IC) and the other part of the processor 1602 may be included in another chip. (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1601 or the memory 1603.

[0309] The processor 1602 may perform or control or cause an operation of the BS 1600 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1602 may control operations of the BS 1600 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 1600 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 1602 may execute a computer program, codes, or instructions stored in the memory 1603, so as to control other components of the BS 1600 to enable execution of various operations.

[0310] The memory 1603 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1603 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0311] The memory 1603 may be electrically, operatively, and / or communicatively coupled to the processor 1602 and may be accessed by the processor 1602.

[0312] The memory 1603 may store a computer program, codes, or instructions executable by the processor 1602. According to an embodiment, a computer program, codes, or instructions executable by the processor 1602 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1603, the processor 1602 may perform various functions according to an embodiment of the disclosure.

[0313] According to an embodiment of the disclosure, operations of the BS 1600 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1603 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0314] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with a network entity (for example, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), etc.) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0315] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0316] Figure 17 is a block diagram of a network entity according to an embodiment of the disclosure.

[0317] The network entity 1700 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 1700.

[0318] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0319] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN), etc.

[0320] Referring to Figure 17, the network entity 1700 may include at least one network interface 1701, at least one processor 1702 (hereinafter, “processor”), and at least one memory 1703 (hereinafter, “memory”). As described above, a NF may be implemented in the form of a physical device such as the network entity 1700, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in Figure 17. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0321] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 1701, the processor 1702, and the memory 1703 of the network entity 1700 may operate. However, components of the network entity 1700 are not limited to the example components illustrated in Figure 17. In another embodiment, the network entity 1700 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 1701, the processor 1702, or the memory 1703 may be integrated in the form of one component.

[0322] The network interface 1701 is a collective term for a transmitter part of the network entity 1700 and a receiver part of the network entity 1700, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 1701 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 1701 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 1701 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0323] The processor 1702 may control general operations of the network entity 1700 according to embodiments of the disclosure. The processor 1702 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1702 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1703, individually, collectively or in any combination thereof. Further, the processor 1702 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0324] According to an embodiment, the processor 1702 may be electrically, operatively, and / or communicatively coupled to the network interface 1701 to control the network interface 1701.

[0325] The processor 1702 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1702 may be included in one chip (or IC) and the other part of the processor 1702 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the network interface 1701 or the memory 1703.

[0326] The processor 1702 may perform or control or cause an operation of the network entity 1700 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1702 may control operations of the network entity 1700 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 1702 may execute a computer program, codes, or instructions stored in the memory 1703, so as to control other components of the network entity 1700 to enable execution of various operations.

[0327] The memory 1703 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1703 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0328] The memory 1703 may be electrically, operatively, and / or communicatively coupled to the processor 1702 and may be accessed by the processor 1702.

[0329] The memory 1703 may store a computer program, codes, or instructions executable by the processor 1702. According to an embodiment, a computer program, codes, or instructions executable by the processor 1702 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1703, the processor 1702 may perform various functions according to an embodiment of the disclosure.

[0330] According to an embodiment of the disclosure, operations of the network entity 1700 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1703 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0331] In an embodiment, a method performed by a user plane function (UPF) entity in a wireless communication system is provided. The method includes: receiving a first message related to a first event subscription and a second message related to a second event subscription, wherein the first message and the second message include aggregation information for aggregating event notifications; detecting a first event corresponding to the first event subscription and a second event corresponding to the second event subscription; generating, based on the aggregation information, a single notification message by combining a first event report for the first event and a second event report for the second event; and transmitting, to a notification target network entity, the single notification message.

[0332] In an embodiment, the aggregation information includes a reference identifier for a notification aggregation, and the generating of the single notification message comprises: combining a first event report and a second event report based on reference identifiers included in the first message and the second message being the same.

[0333] In an embodiment, the aggregation information includes an indication for a notification aggregation, and the generating of the single notification message comprises: combining a first event report and a second event report based on notification target addresses associated with the first message and the second message being the same.

[0334] In an embodiment, at least one of the first message or the second message includes delay information related to a maximum delay allowed for the UPF entity to transmit a notification message including an event report after an event corresponding to an event subscription is detected.

[0335] In an embodiment, the method further includes: starting a timer based on the delay information in response to detecting the first event corresponding to the first event subscription, wherein the generating of the single notification message comprises: combining the first event report and the second event report based on detecting the second event before the timer expires, and the transmitting of the single notification message comprises: transmitting the single notification message based on expiry of the timer.

[0336] In an embodiment, the first message and the second message are received from at least one of an application function (AF) entity, a network data analytics function (NWDAF) entity or a session management function (SMF) entity.

[0337] In an embodiment, the first message and the second message are received based on policy information generated by a policy control function (PCF) entity.

[0338] In an embodiment, the method further includes: transmitting, to a network repository function (NRF) entity, information on a capability of notification aggregation of the UPF entity, the aggregation information is included in the first message and the second message based on the UPF entity supporting notification aggregation.

[0339] In an embodiment, a user plane function (UPF) entity is provided. The UPF entity includes: at least one processor; and at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UPF entity to: receive a first message related to a first event subscription and a second message related to a second event subscription, wherein the first message and the second message include aggregation information for aggregating event notifications, detect a first event corresponding to the first event subscription and a second event corresponding to the second event subscription, generate, based on the aggregation information, a single notification message by combining a first event report for the first event and a second event report for the second event, and transmit, to a notification target network entity, the single notification message.

[0340] In an embodiment, the aggregation information includes a reference identifier for a notification aggregation, and the instructions further cause the UPF entity to: combine a first event report and a second event report based on reference identifiers included in the first message and the second message being the same.

[0341] In an embodiment, the aggregation information includes an indication for a notification aggregation, and the instructions further cause the UPF entity to: combine a first event report and a second event report based on notification target addresses associated with the first message and the second message being the same.

[0342] In an embodiment, at least one of the first message or the second message includes delay information related to a maximum delay allowed for the UPF entity to transmit a notification message including an event report after an event corresponding to an event subscription is detected.

[0343] In an embodiment, the instructions further cause the UPF entity to: start a timer based on the delay information in response to detecting the first event corresponding to the first event subscription, combine the first event report and the second event report based on detecting the second event before the timer expires, and transmit the single notification message based on expiry of the timer.

[0344] In an embodiment, the first message and the second message are received from at least one of an application function (AF) entity, a network data analytics function (NWDAF) entity or a session management function (SMF) entity.

[0345] In an embodiment, the first message and the second message are received based on policy information generated by a policy control function (PCF) entity.

[0346] In an embodiment, the instructions further cause the UPF entity to: transmit, to a network repository function (NRF) entity, information on a capability of notification aggregation of the UPF entity, wherein the aggregation information is included in the first message and the second message based on the UPF entity supporting notification aggregation.

[0347] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

Claims

A method performed by a user plane function (UPF) entity in a communication system, the method comprising:receiving a first message related to a first event subscription and a second message related to a second event subscription, wherein the first message and the second message include aggregation information for aggregating event notifications;detecting a first event corresponding to the first event subscription and a second event corresponding to the second event subscription;generating, based on the aggregation information, a single notification message by combining a first event report for the first event and a second event report for the second event; andtransmitting, to a notification target network entity, the single notification message.The method of claim 1,wherein the aggregation information includes a reference identifier for a notification aggregation, andwherein the generating of the single notification message comprises: combining a first event report and a second event report based on reference identifiers included in the first message and the second message being the same.The method of claim 1,wherein the aggregation information includes an indication for a notification aggregation, andwherein the generating of the single notification message comprises: combining a first event report and a second event report based on notification target addresses associated with the first message and the second message being the same.The method of claim 1, wherein at least one of the first message or the second message includes delay information related to a maximum delay allowed for the UPF entity to transmit a notification message including an event report after an event corresponding to an event subscription is detected.The method of claim 4, further comprising:starting a timer based on the delay information in response to detecting the first event corresponding to the first event subscription,wherein the generating of the single notification message comprises: combining the first event report and the second event report based on detecting the second event before the timer expires, andwherein the transmitting of the single notification message comprises: transmitting the single notification message based on expiry of the timer.The method of claim 1, wherein the first message and the second message are received from at least one of an application function (AF) entity, a network data analytics function (NWDAF) entity or a session management function (SMF) entity.The method of claim 6, wherein the first message and the second message are received based on policy information generated by a policy control function (PCF) entity.The method of claim 1, further comprising:transmitting, to a network repository function (NRF) entity, information on a capability of notification aggregation of the UPF entity,wherein the aggregation information is included in the first message and the second message based on the UPF entity supporting notification aggregation.A user plane function (UPF) entity comprising:at least one processor; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UPF entity to:receive a first message related to a first event subscription and a second message related to a second event subscription, wherein the first message and the second message include aggregation information for aggregating event notifications,detect a first event corresponding to the first event subscription and a second event corresponding to the second event subscription,generate, based on the aggregation information, a single notification message by combining a first event report for the first event and a second event report for the second event, andtransmit, to a notification target network entity, the single notification message.The UPF entity of claim 9,wherein the aggregation information includes a reference identifier for a notification aggregation, andwherein the instructions further cause the UPF entity to: combine a first event report and a second event report based on reference identifiers included in the first message and the second message being the same.The UPF entity of claim 9,wherein the aggregation information includes an indication for a notification aggregation, andwherein the instructions further cause the UPF entity to: combine a first event report and a second event report based on notification target addresses associated with the first message and the second message being the same.The UPF entity of claim 9, wherein at least one of the first message or the second message includes delay information related to a maximum delay allowed for the UPF entity to transmit a notification message including an event report after an event corresponding to an event subscription is detected.The UPF entity of claim 12, wherein the instructions further cause the UPF entity to:start a timer based on the delay information in response to detecting the first event corresponding to the first event subscription,combine the first event report and the second event report based on detecting the second event before the timer expires, andtransmit the single notification message based on expiry of the timer.The UPF entity of claim 9, wherein the first message and the second message are received from at least one of an application function (AF) entity, a network data analytics function (NWDAF) entity or a session management function (SMF) entity.The UPF entity of claim 14, wherein the first message and the second message are received based on policy information generated by a policy control function (PCF) entity.