Method and apparatus for event handling in service-based communication architecture in wireless communication system

Abstract

The present disclosure relates to a method implemented in a network entity for event handling in a service-based communication architecture, where the method comprises: receiving at least one request from one or more subscriber network functions for subscribing to one or more services available at the network entity, wherein the one or more services are created by one or more publisher network functions; creating a subscription to the one or more services based on the request; receiving one or more event messages from the one or more publisher network functions while creating a subscription to the one or more services; and upon receiving the one or more event messages, sending the one or more event notifications to the one or more subscriber network functions.

Description

Technical Field

[0001] This application is based on and claims priority to Indian Provisional Patent Application No. 202341036172 filed on May 25, 2023, and Indian Full Patent Application No. 202341036172 filed on January 11, 2024, both filed in accordance with 35 USC §119(a), the disclosure of each of which is incorporated herein by reference in its entirety.

[0002] This disclosure relates to wireless networks. More specifically, this disclosure relates to systems and methods for event processing in service-based communication architectures. Background Technology

[0003] Given the successive generations of wireless communication development, technologies have been developed primarily for human-oriented services such as voice calls, multimedia services, and data services. Following the commercialization of 5G (5th generation) communication systems, the number of connected devices is expected to grow exponentially. These will increasingly connect to communication networks. Examples of connected things can include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve across a wide range of form factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. To provide a variety of services by connecting hundreds of billions of devices and things in the 6G (6th generation) era, continuous efforts have been made to develop improved 6G communication systems. For these reasons, 6G communication systems are referred to as "beyond 5G" systems.

[0004] The 6G communication system, which is expected to be commercialized around 2030, will have peak data rates in the trillion (1,000 gigabits) bps range and radio latency of less than 100 μsec, and will therefore be 50 times faster than 5G communication systems and have 1 / 10 of the radio latency of 5G communication systems.

[0005] To achieve such high data rates and ultra-low latency, 6G communication systems have been considered for implementation in the terahertz band (e.g., the 95 GHz to 3 THz band). Given that path loss and atmospheric absorption in the terahertz band are more severe than those in the mmWave (millimeter wave) band introduced in 5G, technologies capable of ensuring signal transmission distance (i.e., coverage) will become even more critical. As key technologies for ensuring coverage, it is necessary to develop radio frequency (RF) components, antennas, novel waveforms with better coverage than orthogonal frequency division multiplexing (OFDM), beamforming and massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, and multi-antenna transmission technologies such as massive MIMO. Furthermore, new technologies for improving terahertz band signal coverage have been discussed, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS).

[0006] Furthermore, to improve spectrum efficiency and overall network performance, the following technologies have been developed for 6G communication systems: full-duplex technology, enabling uplink and downlink transmissions to use the same frequency resources simultaneously; network technologies for integrated utilization of satellites, High Altitude Platform Stations (HAPS), etc.; improved network architectures to support mobile base stations and achieve network operation optimization and automation; dynamic spectrum sharing technology via conflict avoidance based on spectrum usage prediction; the use of artificial intelligence (AI) in wireless communication to improve overall network operation by leveraging AI from the design phase of 6G development and internalized end-to-end AI support capabilities; and next-generation distributed computing technologies to overcome the limitations of UE computing capabilities through access to ultra-high-performance communication and computing resources on the network, such as mobile edge computing (MEC), cloud, etc. In addition, efforts are ongoing to enhance connectivity between devices, optimize networks, promote the software-defined networking of network entities, and increase the openness of wireless communication by designing new protocols for use in 6G communication systems, developing mechanisms for achieving hardware-based secure environments and secure data use, developing technologies for maintaining privacy, and improving network connectivity, software-defined networking of network entities.

[0007] The research and development of 6G communication systems in hyper-connectivity, including human-to-machine (P2M) and machine-to-machine (M2M) communication, is expected to enable the next hyper-connected experience. Specifically, services such as truly immersive extended reality (XR), high-fidelity mobile holograms, and digital copies are anticipated to be available through 6G communication systems. Furthermore, services such as remote surgery, industrial automation, and emergency response for enhanced security and reliability will be provided through 6G communication systems, enabling these technologies to be applied to various fields such as industry, healthcare, automotive, and home appliances. Summary of the Invention

[0008] Technical issues

[0009] This disclosure relates to wireless communication systems, and more specifically, to designing the separation of service logic and management functions in a 6G core network.

[0010] Solution to the problem

[0011] The aspects of this disclosure are intended to at least address the aforementioned problems and / or disadvantages, and to at least provide the advantages described below. Therefore, one aspect of this disclosure is to provide a system and method for event processing in a service-based communication architecture.

[0012] Other aspects will be set forth in part in the description which follows, and in part will be apparent from the description, or may be learned by practicing the embodiments presented.

[0013] According to one aspect of this disclosure, a method for event handling in a service-based communication architecture implemented in a network entity is provided. The method includes receiving from one or more subscriber network functions a request to subscribe to one or more services available at the network entity, wherein the one or more services are created by one or more publisher network functions; creating a subscription to the one or more services for the one or more subscriber network functions based on the received request; receiving one or more event messages from the one or more publisher network functions upon creation of the subscription to the one or more services, wherein the one or more event messages indicate the occurrence of an event associated with the one or more services; and sending one or more event notifications to the one or more subscriber network functions upon receiving the one or more event messages, wherein the one or more event notifications notify the one or more subscriber network functions of the occurrence of the event associated with the one or more services.

[0014] According to another aspect of this disclosure, a system for event processing in a service-based communication architecture is provided. The system includes a memory storing one or more computer programs and one or more processors communicatively coupled to the memory, wherein the one or more computer programs include computer-executable instructions that, when executed by the one or more processors, cause the system to receive from one or more subscriber network functions at least one request for subscribing to one or more services available at a network entity, wherein the one or more services are created by one or more publisher network functions; to create subscriptions to the one or more services for the one or more subscriber network functions based on the received requests; and, upon creation of subscriptions to the one or more services, to receive one or more event messages from the one or more publisher network functions, wherein the one or more event messages indicate the occurrence of an event associated with the one or more services; and to send one or more event notifications to the one or more subscriber network functions, wherein the one or more event notifications notify the one or more subscriber network functions of the occurrence of an event associated with the one or more services.

[0015] According to another aspect of this disclosure, one or more non-transitory computer-readable storage media are provided for storing computer-executable instructions that, when executed by one or more processors of the system, cause the system to perform operations. The operations include receiving from one or more subscriber network functions at least one request for subscribing to one or more services available at a network entity, wherein the one or more services are created by one or more publisher network functions; creating a subscription to the one or more services for the one or more subscriber network functions based on the received request; receiving one or more event messages from the one or more publisher network functions upon creation of the subscription to the one or more services, wherein the one or more event messages indicate the occurrence of an event associated with the one or more services; and sending one or more event notifications to the one or more subscriber network functions upon receiving the one or more event messages, wherein the one or more event notifications inform the one or more subscriber network functions of the occurrence of the event associated with the one or more services.

[0016] Other aspects, advantages, and salient features of this disclosure will become apparent to those skilled in the art from the following detailed description of various embodiments disclosed in conjunction with the accompanying drawings.

[0017] Beneficial effects of the invention

[0018] According to embodiments of this disclosure, wireless communication can be performed efficiently. In particular, a separation design of service logic and management functions is implemented in 6G core networks. Attached Figure Description

[0019] The above and other aspects, features and advantages of certain embodiments of this disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, wherein:

[0020] Figure 1 A flowchart illustrating a solution for creating services based on relevant technologies is shown;

[0021] Figure 2 A block diagram illustrating multiple network functions (NFs) according to relevant technologies is shown;

[0022] Figure 3 A block diagram of a system for event processing in a service-based communication architecture according to an embodiment of the present disclosure is shown;

[0023] Figure 4 A block diagram of multiple modules of a system at the core network for event processing in a service-based communication architecture according to an embodiment of the present disclosure is shown.

[0024] Figure 5A A block diagram depicting the operation of a system for event processing in a service-based communication architecture according to various embodiments of the present disclosure is shown;

[0025] Figure 5B A block diagram depicting the operation of a system for event processing in a service-based communication architecture according to various embodiments of the present disclosure is shown;

[0026] Figure 5C A block diagram depicting the operation of a system for event processing in a service-based communication architecture according to various embodiments of the present disclosure is shown;

[0027] Figure 6A A block diagram depicting the architecture of an event broker function (EBF) according to embodiments of the present disclosure is shown;

[0028] Figure 6B A flowchart illustrating messages supported by a publisher application programming interface (API) associated with network functions, according to various embodiments of this disclosure, is shown;

[0029] Figure 6C A flowchart illustrating messages supported by a publisher application programming interface (API) associated with network functions, according to various embodiments of this disclosure, is shown;

[0030] Figure 7A A flowchart illustrating EBF-supported messages according to an embodiment of this disclosure is shown;

[0031] Figure 7BA flowchart of messages supported by a subscriber API associated with network functions is shown according to an embodiment of this disclosure;

[0032] Figure 8 A flowchart illustrating event handling in a service-based communication architecture according to an embodiment of the present disclosure is shown;

[0033] Figure 9 A block diagram depicting an architecture for network functions of event processing in a service-based communication architecture according to embodiments of the present disclosure is shown;

[0034] Figure 10A A block diagram depicting the architecture of an EBF according to an embodiment of the present disclosure is shown;

[0035] Figure 10B A flowchart illustrating the selection criteria for EBF sets and instance identities (IDs) of a repository proxy service according to an embodiment of this disclosure is shown;

[0036] Figure 11 A flowchart illustrating the execution of session operations according to an embodiment of the present disclosure is shown;

[0037] Figure 12 A block diagram is shown depicting the storage of event sets in a library according to an embodiment of the present disclosure;

[0038] Figure 13 A flowchart is shown for receiving one or more desired events from one or more publisher network functions according to an embodiment of this disclosure;

[0039] Figure 14 The illustration shows schematic representations of use case scenarios depicting a system for improving the security of network functions according to embodiments of the present disclosure; and

[0040] Figure 15 A process flow depicting a method for event handling in a service-based communication architecture according to embodiments of the present disclosure is shown.

[0041] Throughout the accompanying drawings, it should be noted that the same reference numerals are used to depict the same or similar elements, features, and structures. Detailed Implementation

[0042] The fifth-generation (5G) core network is a fundamental component of 5G wireless communication systems. The 5G core (5GC) plays a crucial role in providing advanced capabilities and services. The 5G core network is designed based on a service-based network architecture that includes network functions (NFs) and uses synchronous service-based interfaces for inter-NF communication. This means that communication between NFs is facilitated via a request-response mechanism. However, there are situations where NFs need to notify other NFs of events. These situations require asynchronous communication. NFs are building blocks of the service-based architecture, providing specific functionalities to enable proper network operation and management. To enable asynchronous communication between NFs, an event exposure service is used to enable a subscription notification mechanism.

[0043] Figure 1 A flowchart illustrating a solution for creating services based on relevant technologies is shown.

[0044] refer to Figure 1 The call flow illustrates how to subscribe to events in the network.

[0045] In operation 102, the NF service consumer shares subscription requests with the Session Management Function (SMF).

[0046] In addition, in operation 104, SMF creates a subscription based on the received subscription request.

[0047] Figure 2 A block diagram illustrating multiple network functions (NFs) according to relevant technologies is shown.

[0048] refer to Figure 2 For example, multiple NFs may be Access and Mobility Management Function (AMF) 202, Session Management Function (SMF) 204, Network Exposure Function (NEF) 206, User Defined Function (UDF) 208, and Policy Control Function (PCF) 210. In embodiments of this disclosure, multiple NFs include the same services that perform a set of functions, such as event generation, subscription, unsubscription, notification, etc.

[0049] To optimally design microservices / NFs, several principles must be followed when designing NFs. These principles correspond to the Single Reasonability Principle, high cohesion and low coupling, and reusability. Under the Single Reasonability Principle, NFs need to be designed with a single concern. Furthermore, high cohesion and low coupling require that NFs have minimal interdependencies in completing tasks. Regarding reusability, NFs are required to be designed for optimal reuse, and code redundancy must be minimized. The current NF design in 5GC fails to follow these principles. For example, the current NF design violates the Single Reasonability Principle because it manages event subscriptions and notifications to services other than the core services provided by the NF. Additionally, defining a single service across multiple NFs in the current NF design leads to code redundancy, violating the reusability principle.

[0050] Furthermore, event exposure services, as part of an NF, cause certain performance issues. For example, a producer NF delivers events to all consumer NFs that have already subscribed to the event (the 3GPP has already defined 30+ NFs in the core in TS 23.502). Additionally, for service-based architectures, the number of NFs may increase dramatically in 6G, facilitating the easier addition of new services to the network. With a large number of NFs requesting event subscriptions, responding to these requests can be challenging and resource-intensive for producer NFs. Moreover, frequent event generation and processing message delivery to multiple NFs can also impact other core functions, such as mobility management in the AMF. Furthermore, frequent event generation and processing message delivery to multiple NFs can also lead to high process completion times, increased latency, and inefficient NF resource utilization.

[0051] Furthermore, the event exposure service, as part of the NF (Network Functions), leads to poor recovery from node failures. Consumer NFs and producer NFs create multiple subscriptions to receive events. In the event of a signaling storm or node failure, the NF needs to release resources allocated to subscription or consumer resources, such as callbacks, uniform resource allocators (URLs), etc. As a result, the signaling storm or node failure causes the loss of all subscription state, and the NF needs to resubscribe to events.

[0052] Therefore, a technology is needed to overcome the above problems.

[0053] The above information is presented as background information only to aid in understanding this disclosure. No determination is made, and no assertion is made, regarding whether anything in the foregoing can be used as prior art with respect to this disclosure.

[0054] The following description, provided with reference to the accompanying drawings, is intended to aid in a full understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. It includes various specific details to aid understanding, but these details are to be considered exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of this disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and structures may be omitted.

[0055] The terms and words used in the following description and claims are not limited to their literal meaning, but are used by the inventors only to enable a clear and consistent understanding of this disclosure. Therefore, it will be apparent to those skilled in the art that the following description providing various embodiments of this disclosure is for illustrative purposes only and is not intended to limit the purpose of this disclosure as defined by the appended claims and their equivalents.

[0056] It should be understood that, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” include plural indicators. Thus, for example, a reference to “component surface” includes a reference to one or more such surfaces.

[0057] Throughout this specification, references to "aspect," "on the other hand," or similar language mean that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment of this disclosure. Therefore, the appearance of phrases such as "in an embodiment," "in another embodiment," and similar language throughout this specification may, but not necessarily, refer to the same embodiment.

[0058] The terms “comprises,” “comprising,” or any other variations thereof are intended to cover non-exclusive inclusion, such that a process or method that includes a list of steps may include not only those steps but also other steps not expressly listed or inherent to such process or method. Similarly, without further constraints, a list of one or more devices, subsystems, elements, structures, or components beginning with “comprising…” does not exclude the presence of other devices or subsystems or elements or structures or components, or additional devices or subsystems or elements or structures or components.

[0059] It should be understood that the boxes in each flowchart and the combination of flowcharts can be executed by one or more computer programs that include computer-executable instructions. The entirety of one or more computer programs can be stored in a single memory device, or one or more computer programs can be divided into different parts stored in multiple different memory devices.

[0060] Any function or operation described herein can be processed by a processor or a combination of processors. A processor or combination of processors is circuitry that performs processing and includes circuitry such as an application processor (AP, e.g., a central processing unit (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, a connectivity chip, a sensor controller, a touch controller, a fingerprint 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, a microprocessor unit (MPU), a system-on-a-chip (SoC), an IC, etc.

[0061] Figure 3 A block diagram of a system for event processing in a service-based communication architecture according to an embodiment of the present disclosure is shown.

[0062] refer to Figure 3 In embodiments of this disclosure, system 300 corresponds to a network entity for event processing in a service-based communication architecture. For example, a network entity is a network function, an entity residing in a Service Communication Agent (SCP) network function, or a network function within a service-based communication network. The architecture of the network function for event processing in a service-based communication architecture has been referenced at least in subsequent paragraphs. Figure 9 The details are described below. In embodiments of this disclosure, event handling corresponds to the process of managing and responding to various events, incidents, or occurrences that may affect the operation, performance, and security of the network. Furthermore, system 300 is implemented in a core network 302 (such as a fifth-generation (5G) core network).

[0063] System 300 may include one or more processors / controllers 304, input / output (I / O) interfaces 306, multiple modules 308, and memory 310.

[0064] In embodiments of this disclosure, one or more processors / controllers 304 may be operatively coupled to each of a corresponding I / O interface 306, a plurality of modules 308, and a memory 310. In one embodiment of this disclosure, one or more processors / controllers 304 may include at least one data processor for executing processes in a virtual memory area network. One or more processors / controllers 304 may include dedicated processing units, such as integrated system (bus) controllers, memory management control units, floating-point units, graphics processing units, digital signal processing units, etc. In one embodiment of this disclosure, one or more processors / controllers 304 may include a central processing unit (CPU), a graphics processing unit (GPU), or both. One or more processors / controllers 304 may be one or more general-purpose processors, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other devices now known or hereafter developed for analyzing and processing data. One or more processors / controllers 304 may execute software programs, such as manually generated (i.e., programmed) code, to perform desired operations. In embodiments of this disclosure, the processor / controller may be a general-purpose processor (such as a CPU, application processor (AP), etc.), a graphics-only unit (such as a GPU), a vision processing unit (VPU), and / or an artificial intelligence (AI) dedicated processor (such as a neural processing unit (NPU)).

[0065] Furthermore, one or more processors / controllers 304 control the processing of input data based on predefined operating rules or machine learning (ML) models stored in non-volatile memory and volatile memory. The predefined operating rules or ML models are provided through training or learning.

[0066] Here, "learning-provided" means creating an ML model with predefined operational rules or desired characteristics by applying learning techniques to multiple learning datasets. Learning can be performed within the device itself, where the ML is executed according to the embodiment, and / or can be implemented via a separate server / system.

[0067] Furthermore, ML models can consist of multiple neural network layers. Each layer has multiple weight values, and layer operations are performed by computing the previous layer and operating on the multiple weights. Examples of neural networks include, but are not limited to, Convolutional Neural Networks (CNNs), Deep Neural Networks (DNNs), Recurrent Neural Networks (RNNs), Restricted Boltzmann Machines (RBMs), Deep Belief Networks (DBNs), Bidirectional Recurrent Deep Neural Networks (BRDNNs), Generative Adversarial Networks (GANs), and Deep Q-Networks.

[0068] Learning techniques are methods for training a predetermined target device (e.g., a robot) using multiple learning datasets to enable, allow, or control the target device to make determinations or predictions. Examples of learning techniques include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0069] One or more processors / controllers 304 can be configured to communicate with one or more input / output (I / O) devices via corresponding I / O interfaces. I / O interfaces 306 can employ communication methods such as Code Division Multiple Access (CDMA), High-Speed ​​Packet Access (HSPA+), Global System for Mobile Communications (GSM), Long Term Evolution (LTE), and Global Microwave Access Interoperability (WiMAX).

[0070] One or more processors / controllers 304 may be configured to communicate with a communication network via a network interface. In embodiments of this disclosure, the network interface may be an I / O interface 306. The network interface may connect to the communication network to enable the core network 302 to connect to electronic devices, such as smartphones. The network interface may employ connectivity protocols, including but not limited to direct interconnect, Ethernet (e.g., twisted pair 10 / 300 / 3000Base T), Transmission Control Protocol / Internet Protocol (TCP / IP), Token Ring, IEEE 802.11 a / b / g / n / x, etc. The communication network may include, but is not limited to, direct interconnect, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, etc.

[0071] In some embodiments of this disclosure, memory 310 may be communicatively coupled to one or more processors / controllers 304. Memory 310 may be configured to store data and instructions executable by one or more processors / controllers 304. Memory 310 may include, but is not limited to, non-transitory computer-readable storage media, such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media, etc. In one example, memory 310 may include a cache or random access memory for one or more processors / controllers 304. In alternative examples, memory 310 is part of one or more processors / controllers 304, such as a processor's cache memory, system memory, or other memory. In some embodiments of this disclosure, memory 310 may be an external storage device or database for storing data. Memory 310 is operable to store instructions executable by one or more processors / controllers 304. The functions, actions, or tasks shown or described in the figures may be performed by a programmed processor / controller for executing instructions stored in memory 310. Functions, actions, or tasks are independent of a specific type of instruction set, storage medium, processor, or processing strategy, and can be executed by software, hardware, integrated circuits, firmware, microcode, etc., operating individually or in combination. Similarly, processing strategies can include multiprocessing, multitasking, parallel processing, etc.

[0072] In some embodiments of this disclosure, multiple modules 308 may be included within memory 310. Memory 310 may also include a database 312 for storing data. Multiple modules 308 may include a set of instructions that can be executed to cause system 300 to perform any one or more of the methods / processes disclosed herein. Multiple modules 308 may be configured to perform operations of this disclosure, as discussed herein, using data stored in database 312 for event processing in a service-based communication architecture. In embodiments of this disclosure, each of the multiple modules 308 may be a hardware unit that may be external to memory 310. Furthermore, memory 310 may include an operating system 314 for performing one or more tasks of system 300, such as those performed by a general-purpose operating system in a communication domain. In one embodiment of this disclosure, database 312 may be configured to store information required by the multiple modules 308 and one or more processors / controllers 304 for event processing in a service-based communication architecture.

[0073] In embodiments of this disclosure, at least one of the plurality of modules 308 can be implemented using an ML model. ML-related functions can be performed using non-volatile memory, volatile memory, and one or more processors / controllers 304.

[0074] In embodiments of this disclosure, I / O interface 306 may use suitable devices (e.g., but not limited to, a display, keyboard, mouse, touchscreen, microphone, speaker, etc.) to enable input and output to and from system 300.

[0075] Furthermore, this disclosure also envisions a computer-readable medium that includes instructions or receives and executes instructions in response to propagated signals. Additionally, instructions can be sent or received via a network through a communication port or interface or using a bus (not shown). The communication port or interface can be part of one or more processors / controllers 304, or it can be a separate component. The communication port can be created in software or can be a physical connection in hardware. The communication port can be configured to connect to an electronic device, external media, a display, or any other component or combination thereof in the core network 302. The connection to the electronic device can be a physical connection, such as a wired Ethernet connection, or it can be established wirelessly. Similarly, additional connections to other components of the core network 302 can be physical or can be established wirelessly. The network can alternatively be directly connected to the bus. For brevity, the architecture and standard operation of the operating system 314, memory 310, database 312, one or more processors / controllers 304, and I / O interface 306 will not be discussed further.

[0076] Figure 4 A block diagram of multiple modules of a system at the core network for event processing in a service-based communication architecture according to an embodiment of the present disclosure is shown.

[0077] refer to Figure 4 In embodiments of this disclosure, the plurality of modules 308 may include, but are not limited to, a receiving module 402, a creating module 404, a sending module 406, a registering module 408, a providing module 410, and an execution module 412. The plurality of modules 308 may be implemented by suitable hardware and / or software applications.

[0078] In embodiments of this disclosure, the receiving module 402 may be configured to receive from one or more subscriber network functions at a time at at least one request for subscribing to one or more services available at a network entity. In embodiments of this disclosure, the one or more subscriber network functions are categories of network functions in a wireless network related to subscriber management, authentication, and authorization. For example, the one or more services are load balancing services, firewall services, routing services, etc. In embodiments of this disclosure, the one or more services are created by one or more publisher network functions.

[0079] In addition, the creation module 404 can be configured to create subscriptions to one or more services for one or more subscriber network functions based on the received requests.

[0080] Furthermore, the receiving module 402 can be configured to receive one or more event messages from one or more publisher network functions when a subscription to one or more services is created. In embodiments of this disclosure, the one or more event messages represent the occurrence of an event associated with one or more services.

[0081] Furthermore, the sending module 406 can be configured to send one or more event notifications to one or more subscriber network functions upon receiving one or more event messages. In embodiments of this disclosure, one or more event notifications notify one or more subscriber network functions of the occurrence of an event associated with one or more services.

[0082] Furthermore, before receiving at least one request for subscribing to one or more services from one or more subscriber network functions, receiving module 402 may be configured to receive a registration request from each of the one or more subscriber network functions and one or more publisher network functions. In embodiments of this disclosure, receiving registration requests is used to register one or more subscriber network functions and one or more publisher network functions. Therefore, registration module 408 may be configured to register each of the one or more subscriber network functions and one or more publisher network functions based on the received registration requests. Details regarding the registration of one or more subscriber network functions and one or more publisher network functions have been referenced at least in subsequent paragraphs. Figures 6A to 6C A detailed explanation is provided.

[0083] Furthermore, the providing module 410 can be configured to store in a repository a set of events generated by each of one or more subscriber network functions and one or more publisher network functions. In embodiments of this disclosure, the set of events corresponds to events related to: subscription to one or more services, unsubscription to one or more services, notifications sent to one or more subscriber network functions, suspension of subscription to one or more services, and resumption of subscription to one or more services. Furthermore, the providing module 410 can be configured to provide access to the stored set of events to one or more network analytics functions. Details regarding the storage of the set of events in the repository have been referenced at least in subsequent paragraphs. Figure 12 Detailed description.

[0084] Sending module 406 can be configured to receive a set of control plane messages from the one or more publisher network functions. In embodiments of this disclosure, the set of control plane messages is a type of communication used within the network function for controlling and managing network operations. Furthermore, sending module 406 can be configured to generate a set of producer events based on the received set of control plane messages. In embodiments of this disclosure, the set of producer events consists of events generated by one or more producer network functions. Additionally, sending module 406 can be configured to send the generated set of producer events to one or more subscriber network functions that have subscribed to the set of producer events.

[0085] In embodiments of this disclosure, execution module 412 may be configured to receive one or more topic messages from one or more publisher network functions. In embodiments of this disclosure, the one or more topic messages are messages related to mobility, security, session, or any combination thereof. Furthermore, execution module 412 may be configured to receive one or more topic messages from one or more publisher network functions. In embodiments of this disclosure, one or more topic operations include creating, deleting, modifying topics, or any combination thereof.

[0086] Furthermore, execution module 412 can be configured to receive a request from one or more subscriber network functions for obtaining a subscription list. In embodiments of this disclosure, the subscription list corresponds to a list of subscriber functions that have been authorized to access network events and resources. Furthermore, execution module 412 can be configured to send a set of session-related events and a set of mobility-related events to one or more subscriber network functions based on the received request. Additionally, execution module 412 can be configured to receive session requests from one or more subscriber network functions to perform session operations. In embodiments of this disclosure, session operations are pausing session-related events, resuming session-related events, or unsubscribing from mobility-related events. Execution module 412 can also be configured to perform session operations based on the type of session request. For example, when a session request is used to resume session-related events, the network entity resumes session-related events for one or more subscriber network functions. References have been made at least to... Figure 11 The details of the session operation are explained in the following paragraphs.

[0087] Furthermore, receiving module 402 can be configured to receive metadata requests from one or more publisher network functions. In embodiments of this disclosure, the metadata request is based on network function settings and network entity configurations. Network function settings refer to configuration parameters and options that determine the behavior and operation of network functions within a network. Furthermore, receiving module 402 can be configured to determine one or more desired events to be generated by one or more publisher network functions based on the received request. Receiving module 402 can be configured to send a set of network entities and the instance identity (ID) associated with the network entities to one or more publisher network functions when determining one or more desired events. Furthermore, receiving module 402 can be configured to receive one or more desired events from one or more publisher network functions via the set of network entities and the instance ID. In embodiments of this disclosure, one or more desired events include session-related events, mobility-related events, network function-related events, or any combination thereof. Details regarding receiving one or more desired events from one or more publisher network functions have been referenced at least in subsequent paragraphs. Figure 13 A detailed explanation is provided.

[0088] Furthermore, the receiving module 402 can be configured to receive producer information from one or more publisher network functions in a registration message. In embodiments of this disclosure, the producer information includes an instance identifier (ID), a slice type, and release version information associated with one or more publisher network functions. The instance ID corresponds to a unique identifier associated with a specific instance or instantiation of the network function. Additionally, the receiving module 402 can be used to determine an optimal set of network entities from multiple sets of network entities based on one or more network parameters, and to determine an optimal instance ID from multiple IDs. In embodiments of this disclosure, network parameters include operator information, slice information, local event load at each of the multiple sets of network entities, availability status of each of the multiple sets of network entities, etc. The receiving module 402 can be configured to send the determined optimal network entity and the determined optimal instance ID together with a fully qualified domain name (FQDN) or Internet Protocol (IP) address to one or more publisher network functions. Furthermore, the receiving module 402 can be configured to receive one or more events from one or more publisher network functions using the determined optimal network entity, the determined optimal instance ID, and the FQDN or IP address. Details regarding instance IDs and network entity sets have been referenced in subsequent paragraphs. Figure 10A and Figure 10B A detailed explanation is provided.

[0089] Furthermore, receiving module 402 can be configured to determine that the determined optimal network entity and the determined optimal instance ID are ineffective due to one or more errors. Receiving module 402 can be configured to determine another optimal network entity set from multiple network entity sets and another optimal instance ID from multiple IDs based on one or more network parameters. Receiving module 402 can be configured to send the determined other optimal network entity and the determined other optimal instance ID together with the FQDN or IP address to one or more publisher network functions. Additionally, receiving module 402 can be configured to receive one or more events from one or more publisher network functions using the determined other optimal network entity, the determined other optimal instance ID, and the FQDN or IP address.

[0090] Details regarding the operation of System 300 for event handling in a service-based communication architecture have been referenced in subsequent paragraphs. Figures 5A to 5C and Figure 8 A detailed explanation is provided.

[0091] Figures 5A to 5C A block diagram depicting the operation of a system for event processing in a service-based communication architecture according to various embodiments of the present disclosure is shown. Reference has been made to... Figure 3 and Figure 4 The details of system 300 for event handling in a service-based communication architecture are explained.

[0092] refer to Figure 5A EBF 502 (i.e., Event Broker Function (EBF)) handles event functions, i.e., events from multiple network functions. EBF 502 performs a set of functions for multiple network functions. In embodiments of this disclosure, the multiple network functions may include Access and Mobility Management Function (AMF) 504, Session Management Function (SMF) 506, First User Defined Function (UDF) 508, First Network Exposure Function (NEF) 510, Policy Control Function (PCF) 512, Second UDM 514, Second NEF 516, and other network functions 518. In embodiments of this disclosure, the network functions (i.e., AMF 504, SMF 506, UDF 508, and NEF 510) only perform event generation.

[0093] In embodiments of this disclosure, system 300 updates the event exposure service. As a result, multiple network functions notify events only to a single entity (i.e., the network entity). Furthermore, the multiple network functions do not handle event subscription / unsubscription / notification. Additionally, the multiple network functions do not need to consider who or how many event consumers exist or how events are routed to those consumers. In embodiments of this disclosure, the event exposure functions of multiple network functions in core network 302 are aggregated at EBF 502. EBF 502 handles all functions of the event exposure service in a centralized manner. In embodiments of this disclosure, EBF 502 enables the single reasonableness principle. Furthermore, EBF 502 manages only core functions and minimizes the impact on core functions. Additionally, critical resources (such as storage and computing resources) in critical network functions are freed up, thereby reducing processing time. As the number of network functions in core network 302 can grow, EBF 502 can prevent critical network functions managing related activities, such as relaying events to multiple network functions.

[0094] refer to Figure 5B SCP 520 processes event functions, i.e., events from multiple network functions. SCP 520 executes a set of functions for multiple network functions. In embodiments of this disclosure, the multiple network functions may include AMF 504, SMF 506, UDF 508, NEF 510, PCF 512, Authentication Server Function (AUSF) 513, Second NEF 516, and other network functions 518. In 5G core network function deployment model D, by default, all messages between core network functions are routed via SCP 520. In the case of model D, it is not necessary to introduce an event broker function as a separate network function; instead, an event broker function can be introduced as a service within the existing SCP. System 300 enables multiple network functions to act as event generators for generating events. In embodiments of this disclosure, events generated by the multiple network functions are sent directly to SCP 520. Furthermore, event exposure 522 in SCP 520 tracks all subscriptions and unsubscriptions for events. Event exposure 522 also pauses or resumes event subscriptions and manages message delivery.

[0095] Furthermore, Event Data 524 within SCP 520 maintains data on events that can later be used to perform one or more analytical operations using AI / ML models. SCP 520 can be used as a single point where all generated events are stored, enabling the execution of one or more analytical operations. SCP 520 provides a single application programming interface (API) to retrieve information from multiple events, thus reducing latency and accelerating model training.

[0096] refer to Figure 5CThe SCP 520 handles event functions, i.e., events from multiple network functions. In this design of the SCP 520, a router and event tracker 526 are introduced. Since all control plane messages flow through the SCP 520, the router and event tracker 526 can automatically generate events and send them to subscribed network functions. In this design of the SCP 520, network functions do not generate events. The router and event tracker 526 analyze messages and generate events based on the analysis. Network function resources are freed up because multiple network functions are not needed to track events. For example, whenever the SCP 520 detects a control plane message related to a User Equipment (UE) Internet Protocol (IP) change, the SCP 520 automatically sends that information as an event to any consumer network function that may have subscribed to it.

[0097] Figure 6A A block diagram depicting the architecture of an EBF according to an embodiment of the present disclosure is shown. Furthermore, Figure 6B and Figure 6C A flowchart illustrating messages supported by a publisher application programming interface (API) associated with network functions, according to various embodiments of this disclosure, is shown. For brevity, they are explained together. Figures 6A to 6C . Already referenced Figure 4 Details regarding the network functions and registration for one or more subscriber network functions and one or more publisher network functions are explained.

[0098] refer to Figure 6A Publisher API 602 is installed in first network function 604. In embodiments of this disclosure, publisher API 602 includes multiple functions that can be used to register with EBF 606, publish events, or create topics in EBF 606. Furthermore, subscriber API 608 is installed in second network function 610 that wants to subscribe to events. In embodiments of this disclosure, subscriber API 608 includes multiple functions that can be used to register with EBF 606 and start and stop subscriptions. EBF 606 includes topics 611 and exchanges 612. Topic 611 is a logical channel in EBF 606 that allows subscriber API 608 to identify the type of messages that subscriber API 608 is interested in. Furthermore, exchange 612 facilitates message routing within EBF 606 based on the topic to which a message belongs. The protocol used for communication between APIs can be an open-source application layer protocol, such as Application Message Queuing Protocol (AMQP). In embodiments of this disclosure, Figure 6A The publicly available architecture can also be used in SCP.

[0099] refer to Figure 6BAt operation 614, the publisher API 602 in the first network function 604 can send a registration message to EBF 606 to register with the second network function 610. In embodiments of this disclosure, the registration message is as follows:

[0100] register

[0101] {

[0102] Host ID -

[0103] IP address -

[0104] Protocol type -

[0105] }

[0106] Furthermore, at operation 616, the publisher API 602 in the first network function 604 can send event messages to EBF 606 via a publish command. The publish command can be:

[0107] release

[0108] {

[0109] Payload -

[0110] Theme Name -

[0111] Host ID -

[0112] }

[0113] refer to Figure 6C In operation 618, publisher API 602 can send a create topic message to EBF 606 to create a new topic. In embodiments of this disclosure, the create topic message is as follows:

[0114] Create a theme:

[0115] {

[0116] Host ID -

[0117] IP address -

[0118] Theme ID -

[0119] maturity-

[0120] }

[0121] Furthermore, at operation 620, publisher API 602 can send a delete topic message to EBF 606 to delete an existing topic. At operation 622, publisher API 602 can send a modified topic message to EBF 606 to modify an existing topic. In embodiments of this disclosure, publisher API 602 can create multiple topics based on different domains in the network.

[0122] Figure 7A A flowchart illustrating EBF-supported messages according to embodiments of this disclosure is shown. Furthermore, Figure 7B A flowchart illustrating messages supported by a subscriber API associated with network functions according to an embodiment of this disclosure is shown. For brevity, they are explained together. Figure 7A and Figure 7B . Already referenced Figure 4 It explains the details of creating subscriptions for one or more services used for one or more subscriber network functions.

[0123] refer to Figure 7A In operation 702, the notification message is received by the subscriber API 608 in the second network function 610. Furthermore, in operation 704, EBF 606 can configure the publisher API 602 and the subscriber API 608. EBF 606 can set timeouts, keepalive, acknowledgment features, etc. EBF 606 can also set listeners in the subscriber API 608.

[0124] refer to Figure 7B At operation 706, the subscriber API 608 in the second network function 610 can send a registration message to EBF 606 to register with the first network function 604. In embodiments of this disclosure, the registration message is as follows:

[0125] register

[0126] {

[0127] Host ID -

[0128] IP address -

[0129] Protocol type -

[0130] }

[0131] Furthermore, at operation 708, subscriber API 608 can use subscription messages to subscribe to events. In embodiments of this disclosure, the subscriber message is as follows:

[0132] subscription

[0133] {

[0134] Host ID -

[0135] Event Type -

[0136] theme-

[0137] timer

[0138] }

[0139] Figure 8 A flowchart illustrating event handling in a service-based communication architecture according to embodiments of the present disclosure is shown. Reference has been made to... Figure 4 The details of system 300 for event handling in a service-based communication architecture are explained.

[0140] refer to Figure 8 At operations 802A, 802B, and 802C, multiple network functions (such as AMF, EBF, Application Function (AF), and SMF) need to register with the EBF. This is a one-time registration. If a timer expires or the communication address of an NF changes, the network function may have to re-register. At operation 804, the producer network function can create topics based on a domain. At operation 804, the AMF creates mobility-related topics in the EBF. Furthermore, at operations 806A and 806B, multiple network functions can create subscriptions to published topics (e.g., mobility topics). Whenever any event related to that topic occurs, the network function can publish the event to the EBF at operation 808. The publisher network function is unaware of which network functions have already subscribed to the event. At operations 810A and 810B, the EBF notifies the network functions of the occurring event based on a list of subscribed NFs for the topic. If a network function is unavailable, the EBF can retry.

[0141] Figure 9 A block diagram depicting an architecture for network functions in a service-based communication architecture according to embodiments of the present disclosure is shown. Reference has been made to... Figure 4 The details of system 300 for event handling in a service-based communication architecture are explained.

[0142] refer to Figure 9In the current 5G architecture, all network function events are exposed through a single "EventExposure" endpoint for each network function. If system-wide information is needed, multiple network functions must be contacted to generate this inference; for example, at any point, if a user wants all security-related events, they might need to poll the event exposure APIs of all existing network functions. However, network function 902 (i.e., EBF) captures all domain-related information in a single location through network function security agent 904. Security-related events are accessed using network function security agent 904. This isolation allows network function 902 to generate topics for which it is enabled and discards the remaining internally generated events. For example, a consumer can subscribe to all mobility-related events (such as UE location changes, handover, etc.) from mobility agent 906, or a consumer can subscribe to session-related events from session agent 908. Network function 902 can create topics using a create topic command. Network functions can share metadata requests with repository agent 910 and retrieve a list of all available agents. In embodiments of this disclosure, the radio domain agent 912 (i.e., a topic (a separate logical channel) under the event agent) handles all radio-related events, such as radio link failures and changes in the UE's radio connectivity. These topics help subscribers subscribe to only specific types of events.

[0143] Figure 10A A block diagram depicting the architecture of an EBF according to an embodiment of the present disclosure is shown. Figure 10B A flowchart illustrating the selection criteria for the EBF set and instance ID of the repository agent service according to embodiments of this disclosure is shown. For brevity, it is explained together. Figure 10A and Figure 10B .like Figure 4 As explained herein, a set of network entities is associated with a network entity. In embodiments of this disclosure, EBF is a type of network entity. Similarly, a set of EBFs is associated with an EBF.

[0144] refer to Figure 10A and Figure 10B When creating a centralized EBF to handle events, there is a risk to availability and the possibility of losing data stored in the EBF if the EBF fails. As shown in the diagram below, the EBF 1000 design can consist of a cluster of multiple EBF collections, with each collection comprising multiple instances. All instances under an EBF collection maintain the same set of event data for subscribing to, publishing to, and consuming events via network functions. For example, Figure 10A This shows EBF instance ID 1 (represented by 1002) and EBF instance ID N (represented by 1004) for EBF set ID 1 (represented by 1006). Similarly, Figure 10AAlso shown are EBF instance ID 1 (represented by 1008) and EBF instance ID N (represented by 1010) for EBF set ID 2 (represented by 1012). In embodiments of this disclosure, the repository agent 1014 is a microservice within the logical event broker function.

[0145] also, Figure 10B The EBF instance ID 1 (represented by 1016) associated with EBF set ID 3 (represented by 1018) is also shown. In operation 1020, the producer network function (i.e., AMF 1021) sends its instance ID, slice type, and release version information to the storage agent 1014 of EBF 1000 in a registration message. Based on the operator configuration, the provided slice information, and the local event load at each EBF set, storage agent 1014 selects the least loaded and available event agent. In operation 1022, EBF 1000 provides the set and instance ID of the least loaded and available event agents to AMF 1021. In embodiments of this disclosure, the response may also include the FQDN / IP address of the EBF requesting the event. AMF 1021 also includes in the event header the EBF set and instance ID it has received from storage agent 1014 for better event handling. In operation 1024, AMF 1021 creates a topic. AMF 1021 can create single or multiple topics based on events being generated by AMF 1021. For example, AMF 1021 can create mobility and access-related topics in the event broker. In operation 1026, when an event occurs and AMF 1021 is notified, AMF 1021 publishes the event in the corresponding topic. Furthermore, in operation 1028, AMF 1021 begins sending events directly to the EBF instance. In the event of EBF 1000 failure, the storage broker 1014 selects the next best available EBF and assigns its instance ID and FQDN / IP to EBF 1000. With the help of storage broker 1014, the EBF set, and the instance ID, a highly available logical EBF NF can be implemented to handle events.

[0146] Figure 11 A flowchart illustrating the execution of session operations according to an embodiment of this disclosure is shown. Reference has been made to... Figure 4 It explains the details of how session operations are performed.

[0147] refer to Figure 11In embodiments of this disclosure, asynchronous messaging is performed by the EventExposure API of Consumer Network Function 1102, where the peer network function subscribes to a specific event and receives a notification when that event occurs. However, for many events (such as Protocol Data Unit (PDU) session changes or UE location changes), multiple events may exist. It is not possible to suspend such non-critical events in System 300 if the Next Generation Node B (gNB) or Consumer Network Function 1102 fails or if the subscribed NF is overloaded. However, System 300 discloses a call flow (as shown) where the peer network function has the option to suspend or resume a specific event topic, even though Consumer Network Function 1102 has subscribed to that specific event topic. This call flow is helpful in situations such as network function overload or backup / recovery. Utilizing EBF 1104, a sudden network function node failure or signaling storm may not affect asynchronous messaging at Consumer Network Function 1102 because event tracing is delegated to EBF 1104.

[0148] At operation 1106, Consumer Network Function 1102 shares the subscription request list with EBF 1104. Furthermore, at operation 1108, EBF 1104 shares session-related events with Consumer Network Function 1102. At operation 1110, EBF 1104 shares mobility-related events with Consumer Network Function 1102. At operation 1112, Consumer Network Function 1102 suspends session-related events. Furthermore, at operation 1114, Consumer Network Function 1102 resumes session-related events. At operation 1116, Consumer Network Function 1102 unsubscribes from mobility-related events.

[0149] Figure 12 A block diagram depicting the storage of event sets in a library according to an embodiment of the present disclosure is shown. Reference has been made to... Figure 4 The details regarding the storage of event sets in the repository are explained.

[0150] refer to Figure 12 In the current 5G core network architecture, asynchronous messages or events are not stored in a public location for later historical processing. This makes any analysis or AI / ML-related analysis difficult because each event exists in a separate network function. However, this disclosure allows the events of system 300 to be stored in a repository of EBF 1202. For example, the repository could be Network Data and Analytics Function (NWDAF) 1204. Figure 12AMF 1206, SMF 1208, First UDM 1210, First NEF 1212, NWDAF 1204, PCF 1214, Second UDM 1216, Second NEF 1218, and other NF 1220 are equivalent to Figure 5A , Figure 5B and Figure 5C The AMF 504, SMF 506, first UDM 508, first NEF 510, PCF 512, AUSF 513, second NEF 516 and other NF 518.

[0151] Figure 13 A flowchart is shown for receiving one or more desired events from one or more publisher network functions according to an embodiment of this disclosure.

[0152] refer to Figure 13 This illustrates metadata-based request / response communication between Producer Network Function 1302 and EBF 1304. At operation 1306, Producer Network Function 1302 initially sends a metadata request to EBF 1304 based on network function settings and configurations added by the operator or software vendor at EBF 1304. In embodiments of this disclosure, the EBF determines the events that Producer Network Function 1302 needs to generate in its response to the metadata request. Furthermore, at operation 1308, EBF 1304 sends an EBF set and instance ID to Producer Network Function 1302. After parsing the metadata request, Producer Network Function 1302 can begin generating events for an enabled event set, rather than for all events that might occur at the EBF 1304 end of Producer Network Function 1302. For example, at operation 1310, Producer Network Function 1302 shares session-related events with EBF 1304. At operation 1312, Producer Network Function 1302 shares mobility-related events with EBF 1304. In addition, at operation 1314, producer network function 1302 shares security-related events with EBF 1304.

[0153] Figure 14 A schematic representation of a use case scenario depicting a system for improving the security of network functions according to embodiments of this disclosure is shown. Reference has been made to... Figure 4 The details of system 300 for receiving one or more desired events for event processing in a service-based communication architecture are explained.

[0154] refer to Figure 14In existing solutions, asynchronous messages or events are designed using traditional web subscription-notification mechanisms. For example, a subscriber network function can provide a callback Uniform Resource Identifier (URI) requesting that an event be sent to it. Currently, network functions use callback URIs to deliver asynchronous messages to consumer network functions. Furthermore, a compromised network function 1402 can trick a producer network function 1404 into sending events to a URI outside the operator network 1406. The compromised network function 1402 can insert unauthorized URIs that may belong to malicious or third-party network functions (shown as malicious entity 1408). Therefore, it can lead to security vulnerabilities. Consequently, due to the dynamic nature of IP address allocation, authorizing URIs is difficult.

[0155] However, in this disclosure, the event broker function does not use a callback URI to send events to the consumer network function. Instead, the event broker function sends events using the same ID that the consumer network function uses to subscribe to the events. Therefore, a callback URI is not used, and malicious URIs are thus avoided.

[0156] Figure 15 A process flow depicting a method for event handling in a service-based communication architecture according to embodiments of the present disclosure is shown.

[0157] refer to Figure 15 Method 1500 can be executed by system 300 implemented in core network 302, such as Figure 3 and Figure 4 As shown.

[0158] At operation 1502, method 1500 includes: receiving from one or more subscriber network functions at least one request for subscribing to one or more services available at a network entity, wherein the one or more services are created by one or more publisher network functions. In embodiments of this disclosure, a network entity is a network function, an entity located in a Service Communication Agent (SCP) network function, an entity located in a network function of a service-based communication network, or any combination thereof.

[0159] Furthermore, at operation 1504, method 1500 includes creating a subscription to one or more services for one or more subscriber network functions based on the received request.

[0160] Method 1500 further includes at operation 1506: when creating a subscription to one or more services, receiving one or more event messages from one or more publisher network functions, wherein the one or more event messages indicate the occurrence of an event associated with one or more services.

[0161] Furthermore, at operation 1508, method 1500 includes, upon receiving one or more event messages, sending one or more event notifications to one or more subscriber network functions, wherein the one or more event notifications notify the one or more subscriber network functions of the occurrence of an event associated with one or more services.

[0162] Although described in a specific order Figure 15 The operations described above are illustrated, but according to various embodiments of this disclosure, the operations may occur in sequential variations. Furthermore, for the sake of brevity, related operations will not be discussed here. Figure 15 Various operational details have been covered in the related Figures 1 to 4 , Figures 5A to 5C , Figures 6A to 6C , Figure 7A , Figure 7B , Figure 8 , Figure 9 , Figure 10A , Figure 10B and Figures 11 to 14 In the relevant description.

[0163] This disclosure provides various technical advancements based on the key features discussed above. This disclosure simplifies current network function design by removing the event exposure service. Furthermore, the domain-driven design of the event broker function in this disclosure makes it easier to access all domain-related events. This disclosure ensures that network functions can be served by a specific EBF. Furthermore, this disclosure discloses features for pausing or resuming event subscriptions in the event of network overload. Additionally, the event data function stores data from all past events for network analytics. This disclosure discloses a message sequence for accessing metadata stored in the EBF. Furthermore, this disclosure improves the security mechanisms within the EBF.

[0164] Multiple modules 308 can be implemented using any suitable hardware and / or instruction set. Furthermore, Figure 3 The sequential flow shown is inherent, and embodiments may include the addition / omission of operations as needed. In some embodiments of this disclosure, one or more operations performed by multiple modules 308 may be performed by a processor / controller on demand.

[0165] It should be understood that the various embodiments of this disclosure described in the claims and specification can be implemented in hardware, software, or a combination of hardware and software.

[0166] Any such software may be stored in a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores one or more computer programs (software modules), said one or more computer programs including computer-executable instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the methods of this disclosure.

[0167] Any such software may be stored in the form of volatile or non-volatile memory, such as a storage device like read-only memory (ROM), whether erasable or rewritable, or in the form of memory, such as random access memory (RAM), memory chips, devices, or integrated circuits, or stored on an optically or magnetically readable medium, such as an optical disc (CD), a digital versatile disc (DVD), a magnetic disk, or magnetic tape. It should be understood that storage devices and storage media are various embodiments of non-transitory machine-readable storage means suitable for storing one or more computer programs including instructions that, when executed, implement various embodiments of this disclosure. Therefore, various embodiments provide programs including code for implementing the means or methods claimed in any of the claims of this specification, and non-transitory machine-readable storage means for storing such programs.

[0168] Although this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made therein without departing from the spirit and scope of this disclosure as defined by the appended claims and their equivalents.

Claims

1. A method for event handling in a service-based communication architecture implemented in a network entity, the method comprising: Receive at least one request from one or more subscriber network functions for one or more services available at a subscription network entity, wherein the one or more services are created by one or more publisher network functions; Based on the received request, create a subscription to one or more services for one or more subscriber network functions; When creating a subscription to one or more services, one or more event messages are received from one or more publisher network functions, where the one or more event messages indicate the occurrence of an event associated with one or more services; and Upon receiving one or more event messages, one or more event notifications are sent to one or more subscriber network functions, wherein the one or more event notifications notify one or more subscriber network functions of the occurrence of an event associated with one or more services.

2. The method according to claim 1, in, A network entity is at least one of a network function, an entity located in a Service Communication Agent (SCP) network function, and an entity located in a service-based communication network.

3. The method according to claim 1, wherein, Before receiving at least one request for subscribing to one or more services from one or more subscriber network functions, the method includes: Receive registration requests from each of one or more subscriber network functions and one or more publisher network functions; and Register for each of one or more subscriber network features and one or more publisher network features based on the received registration request.

4. The method according to claim 1, further comprising: The repository stores a set of events generated by each of one or more subscriber network functions and one or more publisher network functions, wherein the set of events corresponds to events related to: subscription to one or more services, unsubscription to one or more services, notifications sent to one or more subscriber network functions, suspension of subscription to one or more services, and resumption of subscription to one or more services; Provide access to a stored set of events to one or more network analysis functions, wherein one or more network analysis functions perform one or more analysis operations; Receive a set of control plane messages from one or more publisher network functions; Generate a set of producer events based on the received set of control plane messages; and Send the generated set of producer events to one or more subscriber network functions that have already subscribed to the set of producer events.

5. The method according to claim 1, further comprising: Receive one or more topic messages from one or more publisher network functions; and Perform one or more topic operations based on the type of one or more topic messages received, wherein the one or more topic operations include at least one of creating, deleting, and modifying a topic, and wherein the one or more topic messages are messages related to at least one of mobility, security, and session.

6. The method according to claim 1, further comprising: Receive a request from one or more subscriber network functions to obtain a list of subscriptions; Based on the received request, the session-related event set and the mobility-related event set are sent to one or more subscriber network functions; Receive session requests from one or more subscriber network functions to perform session operations, wherein the session operation is one of pausing session-related events, resuming session-related events, and unsubscribing from mobility-related events; Perform session operations based on the type of session request; Receive metadata requests from one or more publisher network functions, where the metadata requests are based on network function settings and network entity configurations; Based on the received request, determine one or more desired events that will be generated by one or more publisher network functions; Upon identifying one or more desired events, a set of network entities and the instance identity IDs associated with those network entities are sent to one or more publisher network functions; and Receive one or more desired events from one or more publisher network functions via a set of network entities and an instance ID, wherein the one or more desired events include at least one of session-related events, mobility-related events, and network function-related events.

7. The method according to claim 1, further comprising: The registration message receives producer information from one or more publisher network functions, wherein the producer information includes the instance ID associated with one or more publisher network functions, the slice type, and the release version information; The optimal set of network entities is determined from multiple sets of network entities based on one or more network parameters, and the optimal instance ID is determined from multiple IDs. The one or more network parameters include carrier information, slice information, local event load at each of the multiple sets of network entities, and availability status of each of the multiple sets of network entities. Send the determined optimal network entity and the determined optimal instance ID, along with one of the fully qualified domain name (FQDN) and Internet Protocol (IP) address, to one or more publisher network functions. Receive one or more events from one or more publisher network functions by using the determined optimal network entity, the determined optimal instance ID, and one of the FQDN and IP address; The determination of the optimal network entity and the optimal instance ID fails due to one or more errors; Based on one or more network parameters, determine another optimal set of network entities from multiple sets of network entities, and determine another optimal instance ID from multiple IDs; Send the determined other optimal network entity and the determined other optimal instance ID, along with one of the FQDN and IP address, to one or more publisher network functions; and One or more events are received from one or more publisher network functions by using another determined optimal network entity, another determined optimal instance ID, and one of the FQDN and IP address.

8. A system for event processing in a service-based communication architecture, the system comprising: Memory, which stores one or more computer programs; and One or more processors communicatively coupled to the memory The one or more computer programs include computer-executable instructions that, when executed by the one or more processors, cause the system to: Receives at least one request from one or more subscriber network functions for one or more services available at a subscription network entity, wherein the one or more services are created by one or more publisher network functions. Based on the received request, create a subscription to one or more services for one or more subscriber network functions. When creating a subscription to one or more services, one or more event messages are received from one or more publisher network functions, wherein the one or more event messages indicate the occurrence of an event associated with one or more services, and Upon receiving one or more event messages, one or more event notifications are sent to one or more subscriber network functions, wherein the one or more event notifications notify one or more subscriber network functions of the occurrence of an event associated with one or more services.

9. The system according to claim 8, in, A network entity is at least one of a network function, an entity located in a Service Communication Agent (SCP) network function, and an entity located in a service-based communication network.

10. The system according to claim 8, wherein, Before receiving at least one request for subscribing to one or more services from one or more subscriber network functions, the one or more computer programs further include computer-executable instructions that, when executed by the one or more processors, cause the system to: Receive registration requests from each of one or more subscriber network functions and one or more publisher network functions, and Register for each of one or more subscriber network features and one or more publisher network features based on the received registration request.

11. The system according to claim 8, wherein, The one or more computer programs further include computer-executable instructions that, when executed by the one or more processors, cause the system to: The repository stores a set of events generated by each of one or more subscriber network functions and one or more publisher network functions, where each event set corresponds to an event related to: subscription to one or more services, unsubscription to one or more services, notification sent to one or more subscriber network functions, suspension of subscription to one or more services, and resumption of subscription to one or more services. Provides access to a stored set of events to one or more network analysis functions, wherein the network analysis functions perform one or more analysis operations. Receive a set of control plane messages from one or more publisher network functions. The producer event set is generated based on the received control plane message set, and Send the generated set of producer events to one or more subscriber network functions that have already subscribed to the set of producer events.

12. The system according to claim 8, wherein, The one or more computer programs further include computer-executable instructions that, when executed by the one or more processors, cause the system to: Receive one or more topic messages from one or more publisher network functions, and Perform one or more topic operations based on the type of one or more topic messages received, wherein the one or more topic operations include at least one of creating, deleting, and modifying a topic. One or more of the topic messages are messages related to at least one of mobility, security, and session.

13. The system according to claim 8, wherein, The one or more computer programs further include computer-executable instructions that, when executed by the one or more processors, cause the system to: Receives a request from one or more subscriber network functions to obtain a list of subscriptions. Based on the received request, send a set of session-related events and a set of mobility-related events to one or more subscriber network functions. Receives a session request from one or more subscriber network functions to perform a session operation, wherein the session operation is one of pausing a session-related event, resuming a session-related event, or unsubscribing from a mobility-related event. Perform session operations based on the type of session request. Receive metadata requests from one or more publisher network functions, where the metadata requests are based on network function settings and network entity configurations. Based on the received request, determine one or more desired events to be generated by one or more publisher network functions. Upon identifying one or more desired events, a set of network entities and the instance identity IDs associated with those network entities are sent to one or more publisher network functions. Receive one or more desired events from one or more publisher network functions via a set of network entities and an instance ID, wherein the one or more desired events include at least one of session-related events, mobility-related events, and network function-related events.

14. The system according to claim 8, wherein, The one or more computer programs further include computer-executable instructions that, when executed by the one or more processors, cause the system to: The registration message receives producer information from one or more publisher network functions, whereby the producer information includes the instance ID associated with one or more publisher network functions, the slice type, and the release version information. The optimal set of network entities is determined from multiple sets of network entities based on one or more network parameters, and the optimal instance ID is determined from multiple IDs. These network parameters include carrier information, slice information, local event load at each of the multiple sets of network entities, and availability status of each of the multiple sets of network entities. The determined optimal network entity and optimal instance ID, along with one of the fully qualified domain name (FQDN) and Internet Protocol (IP) address, are sent to one or more publisher network functions. Receive one or more events from one or more publisher network functions by using the determined optimal network entity, the determined optimal instance ID, and one of the FQDN and IP address.

15. The system according to claim 14, wherein, The one or more computer programs further include computer-executable instructions that, when executed by the one or more processors, cause the system to: The determination of the optimal network entity and the optimal instance ID failed due to one or more errors. Based on one or more network parameters, determine another optimal set of network entities from multiple sets of network entities, and determine another optimal instance ID from multiple IDs. Send the determined other optimal network entity and the determined other optimal instance ID, along with one of the FQDN and IP address, to one or more publisher network functions, and One or more events are received from one or more publisher network functions by using another determined optimal network entity, another determined optimal instance ID, and one of the FQDN and IP address. The Access and Mobility Management (AMF) function sends the instance ID, slice type, and release version information to the Event Broker Function (EBF) repository in the registration message. Based on the carrier information, slice information, and local event load configuration at each EBF set, select the event broker with the least load and the highest availability; as well as The event handling function provides the AMF with a collection and instance IDs of event brokers that are minimally loaded and available.

Images