A method and apparatus for handling open events of 5G network elements

Abstract

This application provides a method for handling open events in a 5G core network registration center network element. Applied to a core network registration center network element, upon receiving a target event sent by another network element within the core network registration center, the method first determines whether the target event meets a management policy. If the target event meets the management policy, it is processed according to a preset processing flow, and the corresponding processing result is sent to the target address pointed to by the processing result. The event processing method and apparatus provided in this application can uniformly process the events sent by various network elements in the core network registration center network element, eliminating the need to develop and execute event processing code for each network element individually. This allows for more rational resource utilization and cost control.

Description

Technical Field

[0001] This application relates to the field of 5G technology, and in particular to a method, apparatus, computer equipment, computer-readable storage medium, and computer program product for handling open events of 5G core network elements. Background Technology

[0002] Current mainstream 5G core network registration center network element products all adopt the SBA (Service Based Architecture) architecture. Based on the service design concept, it decomposes the original network functions to form various service providers on the network. The various functions of the control plane of the core network registration center network element adopt the HTTP 2.0 protocol. 5G core network registration center network element products draw on cloud-native architecture, adopting technologies such as microservices, network function virtualization, separation of control plane and user plane, network slicing, edge computing, and open network capabilities.

[0003] Because each network element in the 5G core network registration center needs to implement standard event disclosure functions according to 3GPP standards, which generally include event subscription and event publishing, each network element needs to develop a set of code to execute the event disclosure function processing flow. This is not conducive to cost control. Summary of the Invention

[0004] This application provides a method for handling open events of 5G core network elements, which can uniformly process different events published by different network elements and feed back the processed results to the corresponding network elements. This avoids the need to develop a set of code to execute the event open function processing flow for each network element, thereby achieving the goal of cost control.

[0005] In a first aspect, embodiments of this application provide a method for handling open events of 5G core network elements, applied to core network registration center elements, the method comprising:

[0006] Receive target events sent by target network elements within the core network registration center network element;

[0007] Determine whether the target event meets the management policy, wherein the management policy is used to limit the processing flow of the target event;

[0008] If the target event satisfies the management policy, the target event is processed according to the preset processing flow, and the corresponding processing result is sent to the target address pointed to by the processing result.

[0009] The event processing method provided in this application is applied to a core network registration center network element. When a target event is received from a network element within the core network registration center network element, it first determines whether the target event meets the management policy. If the target event meets the management policy, it processes the target event according to a preset processing flow and sends the corresponding processing result to the target address pointed to by the processing result. The event processing method provided in this application can uniformly process the events sent by various network elements in the core network registration center network element, eliminating the need to develop and execute event processing code for each network element individually. This allows for more rational use of resources and controls costs. Attached Figure Description

[0010] Figure 1 This is an exemplary embodiment of the present application illustrating an application scenario diagram of a 5G core network registration center network element open event handling method;

[0011] Figure 2 This is a network architecture diagram illustrating an exemplary embodiment of this application;

[0012] Figure 3 This is a flowchart illustrating an exemplary embodiment of a 5G network element open event handling method.

[0013] Figure 4 This is a flowchart illustrating an exemplary embodiment of a 5G network element open event handling method.

[0014] Figure 5 This is a flowchart illustrating an exemplary embodiment of a 5G network element open event handling method.

[0015] Figure 6 This is a flowchart illustrating an exemplary embodiment of a 5G network element open event handling method.

[0016] Figure 7 This is a flowchart illustrating an exemplary embodiment of a 5G network element open event handling method.

[0017] Figure 8 This is a flowchart illustrating an exemplary embodiment of a 5G network element open event handling method.

[0018] Figure 9 This is a flowchart illustrating an exemplary embodiment of a 5G network element open event handling method.

[0019] Figure 10 This is a flowchart illustrating an exemplary embodiment of a 5G network element open event handling method.

[0020] Figure 11 This is a flowchart illustrating an exemplary embodiment of a 5G network element open event handling method.

[0021] Figure 12 This is a flowchart illustrating an exemplary embodiment of a 5G network element open event processing device. Detailed Implementation

[0022] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.

[0023] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the embodiments of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0024] It should be understood that although the terms first, second, third, etc., may be used to describe various information in the embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0025] The terminology used in the embodiments of this application is for the purpose of describing specific embodiments only and is not intended to limit the embodiments of this application. Unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the ordinary meaning understood by those skilled in the art to which the embodiments of this application pertain. The terms "first," "second," and similar words used in the specification and claims of this application do not indicate any order, quantity, or importance, but are only used to distinguish different components. Similarly, the terms "a" or "one," etc., do not indicate a quantity limitation, but rather indicate the presence of at least one. "A plurality" or "several" indicates two or more.

[0026] The word "includes" or similar terms means that the elements or objects preceding "includes" or "include" cover the elements or objects listed after "includes" or "includes" and their equivalents, and do not exclude other elements or objects. The word "communication connection" or similar terms are not limited to physical or mechanical communication connections, and can include electrical communication connections, whether direct or indirect.

[0027] Before describing the technical solutions of the embodiments of this application, the application scenarios of the embodiments of this application will first be described with reference to the accompanying drawings.

[0028] See Figure 1 , Figure 1 This diagram illustrates an application scenario for a 5G network element open event processing method provided in this application embodiment. In this method, each network element 100 in the core network registration center network element is communicatively connected to the core network registration center network element 200. Each network element sends events that need to be processed to the core network registration center network element 200 via the network. The core network registration center network element 200 then sends the corresponding processing results to the network element or to its resource pool.

[0029] Among them, the core network registration center network element 200 can specifically be an NRF network element. The method of this application specifically provides a general event open function service through the registration center. This service can be implemented in the registration center through software code. On the one hand, it creates an event subscription channel for event consumers, and on the other hand, it creates a publishing channel for event producers. The event open function service manages all event information subscribed by consumers and creates corresponding event subscription proxy instances. Once an event producer publishes an event, the event open function service organizes and transforms the data through the event publishing module and publishes it to the message bus. The message bus matches according to rules and passes the event information to the subscription proxy instance. The subscription proxy instance matches according to the information of the subscription request. If a match is found, it creates a task through the task management module. The task includes related thread pool resources, network resources, and memory resources. After creation, the task information is passed to a third party.

[0030] The event consumers mainly include network elements in the control plane core network registration center: AMF, SMF, PCF, AUSF, UDM, UDR, NSSF, etc. They create HTTP requests, and the parameters in the request should include the network element identifier, event type, maximum number of event reports, event reporting timeout, event reporting period, callback address, etc. After receiving the subscription request, the event opening function service creates a subscription instance and subscription policy, and generates a unique identifier for the subscription, which is implemented using UUID. The event opening function service generates standard subscription event session information, creates a session through the event bus client, and identifies the subscription content of the session.

[0031] Event producers include control plane core network registration center elements such as AMF, SMF, PCF, AUSF, UDM, UDR, and NSSF. When an event producer detects events such as UE connection changes, UE status changes, or signaling processing anomalies, it connects to the Event Open Function Service and transmits the event information to it. After receiving the event information from the event producer, the Event Open Function Service performs data verification and processing. Upon completion, it connects to the message bus through an event client, creates a session, and publishes the event information. The message bus, based on the event information, adapts to the relevant session that requires the event and sends it to the relevant subscription agent module through the session. The subscription agent module matches and filters the data; if a match is found, it calls the task management module and transmits the task information.

[0032] The registration center network element creates relevant thread pool resources, network resources, and memory resources based on the task information to execute the task until the task succeeds or fails.

[0033] The registration center network element may include various processing modules, such as an event processing module. This event processing module can be execution logic code configured on any network element to perform event processing steps; it can also be a standalone server with execution logic code configured to perform event processing steps; or it can be execution logic code configured on a server cluster, etc. This application does not limit the scope of these modules. In this case, each network element can send the events that need to be processed to the event processing module of the core network registration center network element 200 via the network, and the event processing module will determine the corresponding processing result.

[0034] Before describing the 5G core network registration center element open event handling method provided in this application, the network architecture of the core network registration center element will be introduced first, such as... Figure 2 As shown, Figure 2 Here is a diagram of a core network registration center network element architecture:

[0035] Among them, NSSF, NEF, NRF, PCF, UDM, AF, AUSF, AMF, SMF, SCP, and UPF are all network elements. NSSF is the network slice selection function network element, NEF is the network open function network element, NRF is the network repository function network element (core network registration center network element), PCF is the control policy function network element, UDM is the same data management network element, AF is the application function network element, AUSF is the authentication server function network element, AMF is the access and mobility management function network element, SMF is the session management function network element, SCP is the network element, and UPF is the user plane function network element. DN stands for data network, such as operator services, Internet access, or third-party services. UE stands for User Equipment. (R)AN stands for Access Network (AN) or Radio Access Network. Nnssf, Nnef, Nnrf, Npcf, Nudm, Nausf, Namf, and Nsmf are all interfaces.

[0036] Current core network registration center network element products all adopt the SBA architecture. In this service-based design, original network functions are broken down into various service providers on the network. The various functions within the core network registration center network element use the HTTP / 2.0 protocol. Core network registration center network element products draw inspiration from cloud-native architectures, employing technologies such as microservices, network function virtualization, separation of control and user planes, network slicing, edge computing, and open network capabilities.

[0037] According to 3GPP standards, core network registration center elements are required to implement standard event exposure functions, which generally include event subscription, unsubscription, subscription modification, and subscription notification. The processing flow for each core network registration center element's event exposure function is generally the same: handling subscription requests from third-party services, creating subscription instances based on the requests, configuring the resources required by the subscription instances, recording subscription information, and then notifying third parties via callbacks when events change within the network element. In this process, only the business data differs. Therefore, developing a similar event handling mechanism execution logic for each network element increases development costs and reduces program maintainability and scalability.

[0038] In response to the above problems, such as Figure 3 As shown, Figure 3 This application provides a method for handling open events of 5G core network registration center network elements, which is applied to... Figure 1 Taking the core network registration center network element shown as an example, the event handling method includes the following steps:

[0039] Step S301: Receive the target event sent by the target network element within the core network registration center network element;

[0040] The event handling method provided in this application embodiment can be executed by the event handling module within the core network registration center network element. First, the structure of the event handling module that executes the event handling method is described, such as... Figure 4 As shown, Figure 4 This is a structural diagram of the event handling module, consisting of... Figure 4 As can be seen, the event handling module includes an event exchange layer, an event handling layer, and a data transmission layer.

[0041] The event exchange layer includes event subscription interfaces and event publishing interfaces. The event subscription interface further includes subscription creation interfaces, subscription modification interfaces, and subscription cancellation interfaces. The subscription creation interface, subscription modification interface, and subscription cancellation interface need to transmit the unique identifier of each network element to distinguish the subscription events sent by each network element.

[0042] The event publishing interface is mainly called by various network elements in the core network registration center so that when business data changes, each network element in the core network registration center can send its unique identifier information and the changed business data to the event processing module by calling the event publishing interface.

[0043] The event handling module also includes an event handling layer, which includes a subscription management unit, a task management unit, and an event publishing unit.

[0044] The subscription management unit includes a subscription event ID allocation subunit, a subscription agent management subunit, and a first message bus client. The event ID allocation subunit assigns IDs to subscription request events sent by various network elements for subsequent querying, deletion, and other operations. The subscription management subunit creates processing windows for subscription request events, deletes and modifies subscription request events, and performs matching and filtering operations on business data. The message bus client accesses and retrieves data from the resource pool in the data transmission layer. The first message bus client retrieves data corresponding to the subscription request events sent by various network elements from the message bus in the data transmission layer.

[0045] The task management unit includes a task configuration management subunit, thread pool resources, network resources, and memory resources. The task configuration management subunit is used to initialize thread pool resources, network resources, and memory resources. Thread pool resources are responsible for creating corresponding threads for sending the processing results of subscribed request events, and for destroying the threads occupied after successfully sending the processing results. Network resources are used to create network clients and send the processing results to the corresponding network elements through these clients. Memory resources are used to cache the processing results.

[0046] The event processing layer also includes an event publishing unit, which includes a context management subunit, an event publishing management subunit, and a second message bus client.

[0047] The context management subunit is used to perform operations such as decrypting, verifying, and assigning IDs to the publication events sent by various network elements.

[0048] Event release management is used to review the legitimacy of released events, filter out data that needs to be kept confidential, and set permissions for business data in released events.

[0049] The second message bus client is used to send the processed published events to the message bus of the data transmission layer.

[0050] The event processing module also includes a data transmission layer, which comprises a message bus. The message bus primarily stores service data sent by various network elements and encapsulates and transmits this data according to a preset encapsulation protocol (e.g., JSON). Additionally, the message bus can create, modify, and delete sessions between the subscription management unit and the event publishing unit. Furthermore, the message bus can forward service data through matching sessions.

[0051] Based on the above description of the event processing module, the event processing module can receive target events sent by any network element (i.e., the target network element) within the core network registration center network element through the event subscription interface or event publishing interface of the event exchange layer. The target event can be a subscription request event from the event consumer or a publishing event from the event producer; of course, the event subscription interface and event publishing interface of the event processing module can also simultaneously receive subscription request events and publishing events sent by different network elements or the same network element. This application does not limit this in any way.

[0052] Step S302: Determine whether the target event meets the management policy. The management policy is used to limit the processing flow of the target event.

[0053] The management strategy is a criterion used to define the handling process for target events. By determining whether a target event meets the management strategy, the handling process for that event is determined, allowing for different processes to be used for different target events, thereby improving the efficiency of target event handling. It should be noted that the methods for determining whether different target events meet the management strategy differ. The following examples illustrate how to determine whether a target event meets the management strategy:

[0054] like Figure 5 As shown, Figure 5 An optional method embodiment provided by this application for determining whether a target event satisfies a management policy when the target event is a subscription request event, the method embodiment includes the following steps:

[0055] Step S501: Match the content of the subscription request event with the historical records, which include multiple subscription requests sent by different network elements; if the match fails, proceed to step S502; if the match succeeds, proceed to step S503.

[0056] When a core network registration center element receives a subscription request event from a target network element, it first needs to match the content of the subscription request event with the content of historical subscription requests. That is, it compares the specific content of the subscription request event with the specific content of each historical subscription request to determine whether there is a case where the content of the subscription request event is the same as the content of at least one of the historical subscription requests. If so, the match is considered successful; otherwise, the match is considered unsuccessful.

[0057] If the subscription request event sent by the target network element has already been sent to the core network registration center network element, the core network registration center network element does not need to process the subscription request event according to the preset processing procedure. Instead, it queries the reason why the target network element has not received the corresponding processing result and performs targeted processing.

[0058] It should be noted here that if the subscription request event sent by the target network element successfully matches the historical records, the possible reasons are that during the process of the core network registration center network element sending the processing result to the target network element, there was a network failure, no idle thread, or a problem with the target network element's receiver. As long as the reason why the target network element did not receive the processing result is determined, the solution can be targeted.

[0059] By matching subscription request events with historical records, duplicate processing of the same subscription request event can be avoided, thereby saving resources in the event processing module.

[0060] Step S502: Determine whether the subscription request event satisfies the management policy;

[0061] Therefore, if it is determined that the subscription request event fails to match the historical records, it can be determined that the subscription event meets the management policy. This means that the subscription request event can be the first time that the target network element sends the subscription request event to the core network registration center network element. Then, the subscription request event sent by the target network element is processed according to the preset processing procedure, and the corresponding processing result is sent to the target network element.

[0062] Step S503: Determine that the subscription request event does not meet the management policy.

[0063] Conversely, if the content of the subscription request event is successfully matched with the historical records, it can be determined that the subscription request event does not meet the management policy, meaning that there is no need to process the subscription request event through the preset processing flow.

[0064] It should be noted here that if the event handling module within the core network registration center determines whether a subscription request event meets the management policy, and the architecture of the event handling module is as follows... Figure 4 As shown, the event handling module can determine whether the subscription request event satisfies the management policy through the resource management unit in the event handling layer. Furthermore, it can determine whether the subscription request event satisfies the management policy through the subscription agent management subunit in the resource management unit.

[0065] In another embodiment, such as Figure 6 As shown, after the event handling module receives a subscription request event sent by the target network element, it also includes the following steps:

[0066] Step S601: Assign a first identification number to the subscription request event;

[0067] Upon receiving a subscription request event from a target network element, the subscription request event can be assigned a first identification number (i.e., ID) by the subscription event ID allocation subunit in the resource management unit. By assigning a first identification number to each subscription request event, each network element and each subscription request event can be distinguished, so that the subscription request event can be queried, deleted, modified, etc. when needed in the future.

[0068] Step S602: After determining that the subscription request does not meet the management policy, locate the subscription request based on the first identity identifier and delete the subscription request.

[0069] In this case, after the event handling module determines that the subscription request does not meet the management policy, it can search for the subscription request based on the first identity of the subscription request event through the subscription agent management subunit and delete the subscription request.

[0070] In yet another embodiment, such as Figure 7 As shown, if the subscription agent management subunit determines that the subscription request event does not meet the management policy, it can perform the following steps:

[0071] Step S701: Determine whether the number of times the subscription request event has been received exceeds a first threshold; if it exceeds the first threshold, proceed to step S702; if it does not exceed the first threshold, proceed to step S703.

[0072] In cases where a subscription request event does not meet the management policy, the number of times the target network element sends the subscription request event to the event processing module can be determined, and this number can be compared with a preset first threshold. This application determines the continued processing of subscription request events by comparing the number of times with the preset first threshold, avoiding multiple processing of the same subscription request event and thus avoiding resource waste. It should be noted that this comparison process can be performed through the subscription agent management subunit of the subscription management unit.

[0073] Step S702: Return a first message to the target network element. The first message is used to indicate to the target network element that the subscription request event has been processed.

[0074] Once the first threshold is exceeded, a message is sent to the target network element to indicate that the subscription request event has been processed.

[0075] Step S703: Determine whether the processing result corresponding to the subscription request event has timed out; if it has timed out, proceed to step S704; if it has not timed out, proceed to step S705.

[0076] Furthermore, after the core network registration center element determines the number of times the processing result of the already processed subscription request event has exceeded the first threshold, it continues to determine whether the processing result has been sent out timed out. That is, whether the core network registration center element sent the processing result of the subscription request event to the target network element within the agreed time period. This application, by judging whether the processing result has exceeded the time limit, can avoid repeatedly sending the processing result of the subscription request event, thus avoiding resource waste. It should be noted that if this step is executed by the event processing module within the core network registration center element, then determining whether the processing result of the subscription request has exceeded the time limit can be executed by the subscription agent management subunit of the subscription management unit.

[0077] Step S704: Return a second message to the target network element. The second message is used to indicate to the target network element that it is retransmitting.

[0078] In this process, after determining that the processing result has timed out, a second message prompting retransmission can be sent to the target network element, and corresponding resources can be allocated for the processing result of the subscription request event to retransmit the processing result of the subscription request event.

[0079] Step S705: Return a third message to the target network element. The third message is used to prompt the target network element to wait.

[0080] In this process, after determining that the processing result has not been sent within the timeout period, a third message prompting the target network element to wait can be sent to avoid the target network element repeatedly sending subscription request events, thus avoiding waste of resources.

[0081] It should be noted here that if this step is executed by the event processing module within the core network registration center network element, the event processing module can send a second or third message to the target network element through the task management unit.

[0082] Step S303: If the target event meets the management policy, process the target event according to the preset processing flow, and send the corresponding processing result to the target address pointed to by the processing result.

[0083] The preset processing flow can be a processing flow that matches the target event. Different target events correspond to different preset processing flows. The following is a detailed explanation of the process of processing the target event:

[0084] In another embodiment, such as Figure 8 As shown, Figure 8 This application provides an exemplary embodiment of an optional method for determining that a subscription request event satisfies a management policy. The method embodiment includes the following steps:

[0085] Step S801: If it is determined that the subscription request event meets the management policy, then obtain the processing result of the subscription request event from the message bus;

[0086] Since the message bus of the data transmission layer stores the service data of each target network element, the event processing module can obtain the processing result of the subscription request event sent by the target network element from the message bus of the data transmission layer through the first message bus client after determining that the subscription request event sent by the target network element meets the management policy, that is, after the target network element has not sent an event with the same content as the subscription request event to the event processing module.

[0087] Step S802: Allocate target resources to the results of the subscription request event based on the current network element scale and configuration parameters. The target resources include thread resources and network resources.

[0088] When the event processing module obtains the processing result of the subscription request event sent by the target network element, it can allocate corresponding thread resources and network resources to the processing result of the subscription request event through the task management unit, so as to send the processing result of the subscription request event to the target network element through threads and network.

[0089] Step S803: Determine the interface address of the target network element based on the unique identifier;

[0090] The unique identifier is a marker carried by the target network element when sending a subscription request event to distinguish different target network elements. The event handling module can determine the interface address of the target network element using its unique identifier after successfully allocating thread and network resources for the subscription request event.

[0091] The event processing module may pre-store an information table, which includes unique identifiers of each network element that can communicate with the event processing module and the interface addresses of each network element corresponding to its unique identifier. When the event processing module needs to send a processing result to a target network element, it can read the information table from the corresponding memory address to determine the interface address of the target network element based on the information table and the target network element's unique identifier. Of course, the event processing module may have other methods for determining the interface address of the target network element, and this application does not limit this method.

[0092] Step S804: Send the processing result of the subscription request event to the interface address of the target network element through thread resources and network resources.

[0093] When the thread pool resources and network resources in the task management unit are available, the event processing module can use the allocated thread resources and network resources to send the processing results corresponding to the subscription request event to the interface address of the target network element, so that the target network element can perform the corresponding analysis and processing operations based on the received processing results.

[0094] During the allocation of thread and network resources for processing results, the event handling module may have idle threads and network resources. In such cases, the corresponding thread and network resources can be allocated to the processing results to ensure timely transmission to the target network element. However, there may be instances where the event handling module currently lacks idle threads and corresponding network resources. In such cases, the following processing steps apply.

[0095] In another embodiment, such as Figure 9 As shown, it includes the following steps:

[0096] Step S901: If the processing result of the subscription request event is not allocated to thread resources and network resources, then memory resources are allocated to the processing result of the subscription request event.

[0097] The task management unit also includes memory resources. Failure to allocate target resources may be due to the event processing module currently lacking idle threads and / or having no network connection. In such cases, to avoid redundant processing of subscription request events and wasting resources, memory resources can be allocated to the processing results of the subscription request events.

[0098] Step S902: Cache the processing results of the subscription request event using memory resources;

[0099] If the event handling module allocates corresponding memory resources for the processing results of the subscription request event, and the processing results of the subscription request event have not yet been allocated to the target resources, the processing results of the subscription request event can be cached using memory resources first. This can avoid the situation of repeated processing caused by the inability to provide timely feedback.

[0100] Step S903: After allocating thread resources and network resources for the processing result of the subscription request event, the cached processing result of the subscription request event is sent to the interface address of the target network element through the thread resources and network resources.

[0101] If the event handling module has corresponding thread resources and network resources, it can send the processing result of the subscription request event stored in memory to the interface address of the target network element after allocating target resources for the subscription request event.

[0102] In another embodiment, after the processing result of the cached subscription request event is sent to the interface address of the target network element via the target resource, the processing result is deleted from memory.

[0103] In order to save storage space and improve the performance of the event processing module, this application may delete the processing result of the subscription request event stored in memory after it has been sent to the interface address of the target network element, so as to release memory resources and facilitate the storage of processing results of other subscription request events.

[0104] Similarly, after sending the processing results to the target network element's interface address using thread and network resources, the thread and network resources are released. This allows for the transmission of processing results for other subscription request events using the released thread and network resources, achieving more efficient resource utilization and improving the processing efficiency of the event handling module.

[0105] like Figure 10 As shown, Figure 10 An optional method embodiment provided by this application for determining whether a target event satisfies a management policy when the target event is a published event, the method embodiment includes the following steps:

[0106] The target event is a published event, which carries a unique identifier for the target network element. Determining whether the target event meets the management policy includes:

[0107] Step S1001: Obtain the key corresponding to the unique identifier of the target network element, and decrypt the published event using the key;

[0108] During operation, each network element generates various business data. To avoid losses due to the leakage of its own business data, each network element encrypts each published event when sending it to the event processing module.

[0109] The event processing module may contain a table storing the unique identifiers of each network element and the corresponding keys. Since the target network element carries its unique identifier when sending a published event to the event processing module, when the target event sent by the target network element is a published event, the key can be determined from the table based on the target network element's unique identifier. This key is then used to decrypt the published event sent by the target network element, thereby obtaining the service data sent by the target network element. Alternatively, this application may obtain the key corresponding to the unique identifier of the target network element through the context management subunit of the event processing layer and use the key to decrypt the published event.

[0110] Step S1002: Verify the publication event after the decryption operation;

[0111] The purpose of validating the published event after decryption is to determine whether the decrypted published event conforms to a preset format, whether it matches the service of the target network element, and whether decryption was successful. Validation of the published event after decryption can be achieved by comparing the decrypted published event with a correct published event; if the comparison is successful, the validation is successful; if the comparison fails, the validation fails. Of course, other validation methods are possible, and this application does not impose the following limitations on them. It should be noted that validating the published event after decryption can be an operation performed by the context management subunit within the event publishing unit.

[0112] Step S1003: If the verification is successful, obtain the event publishing rule corresponding to the unique identifier;

[0113] The event processing module may contain an information table that stores the unique identifiers of each network element and the corresponding time-based publishing rules. Event publishing rules may include, for example, that type A data can be published, type B data cannot be published, type C data requires encrypted publishing, and multiple transmissions of business data should be merged for publication.

[0114] The event processing module can retrieve the event publishing rule corresponding to the unique identifier of the target network element from the information table after successfully verifying the published event after the decryption operation using the above method.

[0115] Step S1004: Determine whether the published event after the decryption operation meets the event publishing rules; if it does, proceed to step S1005; if it does not, proceed to step S1006.

[0116] After determining the corresponding event publishing rules, the next step is to determine whether the decrypted published event meets the rules. This involves identifying the publishable, non-publishable, non-formatted, encrypted, merged, and deleted data from the service data to be sent by the target network element. It should be noted that this determination can be made through the time-based publishing management subunit within the event publishing unit.

[0117] Step S1005: Determine if the published event meets the management policy;

[0118] Step S1006: Determine that the published event does not meet the management policy.

[0119] Therefore, the event handling module can determine that the published event meets the management policy if it is determined that the decrypted published event meets the published rules; conversely, it can determine that the published event does not meet the management policy if it is determined that the decrypted published event does not meet the published rules.

[0120] In another embodiment, such as Figure 11 As shown, it also includes:

[0121] Step S1101: Assign a second identity number to the published event;

[0122] The event processing module can assign a corresponding second identification number to the published event through the context management subunit after receiving the published event sent by the target network element. This facilitates the differentiation of each published event and also allows for quick retrieval of the published event through the second identification number when subsequent operations such as querying, modifying, or deleting the published event are required, thereby improving the efficiency of processing published events.

[0123] Step S1102: After determining that the published event does not meet the management policy, the published event is located by the second identity number and then deleted.

[0124] In this module, after assigning a second identity number to each published event, the event handling module can search for the published event by the second identity number and delete it after determining that the published event does not meet the management policy, thereby freeing up space in the event handling module.

[0125] In another embodiment, if it is determined by the above method that the publication event sent by the target network element meets the management policy, the publication event can be sent to the message bus of the data transmission layer through the second message bus client.

[0126] In another embodiment, if it is determined by the above method that the published event sent by the target network element does not meet the management policy, the decrypted published event can be processed according to the corresponding event publishing rules to process the decrypted published event into a published event that meets the event publishing rules, and the published event that meets the event publishing rules can be sent to the message bus of the data transmission layer through the second message bus client.

[0127] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0128] Based on the same inventive concept, this application also provides a control terminal 100 for implementing the above-mentioned method. The solution provided by the control terminal 100 is similar to the solution described in the above method. Therefore, the specific limitations of one or more embodiments of the control terminal 100 provided below can be found in the limitations of the receiving method above, and will not be repeated here.

[0129] In one embodiment, such as Figure 12 As shown, a 5G core network registration center network element open event processing device is provided. The device is located in the core network registration center network element and includes: a receiving module 1201, a judging module 1202 and a processing module 1203.

[0130] The receiving module 1201 is used to receive target events sent by the target network element within the core network registration center network element;

[0131] The judgment module 1202 is used to determine whether the target event meets the management policy, and the management policy is used to limit the processing flow of the target event;

[0132] The processing module 1203 is used to process the target event according to a preset processing flow when the target event meets the management policy, and send the corresponding processing result to the target address pointed to by the processing result.

[0133] In another embodiment, the determination module 1202 is specifically used to match the content of the subscription request event with the historical records, which include multiple subscription requests sent by different network elements;

[0134] If a match fails, it is determined that the subscription request event satisfies the management policy;

[0135] If a match is found, it is determined that the subscription request event does not meet the management policy.

[0136] In another embodiment, the event handling apparatus further includes a return determination module.

[0137] The return module is used to determine whether the number of times subscription request events have been received exceeds a first threshold.

[0138] If the first threshold is exceeded, a first message is returned to the target network element. The first message is used to indicate to the target network element that the subscription request event has been processed.

[0139] If the first threshold is not exceeded, determine whether the processing result corresponding to the subscription request event has timed out.

[0140] If a timeout occurs, a second message is returned to the target network element, which is used to indicate to the target network element that it is retransmitting;

[0141] If the timeout has not occurred, a third message is returned to the target network element, which is used to prompt the target network element to wait.

[0142] The processing module 1203 is specifically used to obtain the processing result of the subscription request event from the message bus if it is determined that the subscription request event meets the management policy.

[0143] Based on the current network element scale and configuration parameters, target resources are allocated to the processing results of subscription request events. Target resources include thread resources and network resources.

[0144] The interface address of the target network element is determined based on the unique identifier;

[0145] The processing results of the subscription request event are sent to the interface address of the target network element through thread resources and network resources.

[0146] In another embodiment, the processing module 1203 is further configured to allocate memory resources for the processing result of the subscription request event if the processing result of the subscription request event is not allocated to thread resources and network resources.

[0147] The results of processing subscription request events are cached using memory resources;

[0148] After allocating target resources for the processing results of subscription request events, the cached processing results of subscription request events are sent to the interface address of the target network element through thread resources and network resources.

[0149] In another embodiment, the processing module 1203 is further configured to delete the processing result from the memory resource after sending the processing result of the cached subscription request event to the interface address of the target network element through the target resource.

[0150] In another embodiment, the processing module 1203 is further configured to release the thread resources and network resources after sending the processing result to the interface address of the target network element through thread resources and network resources.

[0151] In another embodiment, the event handling apparatus further includes an allocation module.

[0152] The allocation module is used to assign a first identification number to subscription request events;

[0153] After determining that the subscription request does not meet the management policy, the subscription request is located based on the first identity identifier and then deleted.

[0154] In another embodiment, the judgment module 1202 is further configured to obtain the key corresponding to the unique identifier of the target network element, and to decrypt the published event using the key;

[0155] Verify the published event after the decryption operation;

[0156] If the verification is successful, retrieve the event publishing rules corresponding to the unique identifier;

[0157] Determine whether the published event after the decryption operation meets the event publication rules;

[0158] If the conditions are met, then the published event is deemed to satisfy the management policy.

[0159] If the conditions are not met, then the published event is determined to not meet the management policy.

[0160] In another embodiment, the processing module 1203 is further configured to publish the publishing event to the message bus after determining that the publishing event meets the management policy.

[0161] In another embodiment, the allocation module is further configured to assign a second identity number to the published event; after determining that the published event does not meet the management policy, the module searches for the published event using the second identity number and deletes the published event.

[0162] In addition, this embodiment also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the event handling method of any of the above embodiments.

[0163] Additionally, this embodiment also provides a computer program product, including a computer program that, when executed by a processor, implements the event handling method of any of the above embodiments.

[0164] It is readily understood that, based on the several embodiments provided in this application, those skilled in the art can combine, split, or reorganize the embodiments of this application to obtain other embodiments, none of which exceed the protection scope of this application.

[0165] The above detailed embodiments further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above are merely specific embodiments of the embodiments of this application and are not intended to limit the protection scope of the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the embodiments of this application should be included within the protection scope of the embodiments of this application.

Claims

1. A method for handling open events of 5G core network elements, characterized in that, The method, applied to network repository functional elements, includes: Receive a target event sent by a target network element that is communicatively connected to the network repository function network element. The target event is a subscription request event or a publish event, and the publish event carries a unique identifier of the target network element. Determine whether the target event meets the management policy. The management policy is used to limit the processing flow of the target event. When the target event is a subscription request event, determining whether the target event meets the management policy includes: matching the content of the subscription request event with the historical records, which include multiple subscription requests sent by different network elements. If the match fails, it is determined that the subscription request event satisfies the management policy; If a match is found, it is determined that the subscription request event does not satisfy the management policy; When the target event is a publication event, determining whether the target event meets the management policy includes: obtaining a key corresponding to the unique identifier of the target network element, and decrypting the publication event using the key; Verify the published event after the decryption operation; If the verification is successful, obtain the event publishing rule corresponding to the unique identifier; Determine whether the published event after the decryption operation satisfies the event publication rules; If the conditions are met, then the published event is determined to satisfy the management policy; If not, then the published event is determined to not satisfy the management policy; When the target event satisfies the management policy, the target event is processed according to a preset processing flow, and the corresponding processing result is sent to the target address pointed to by the processing result. Specifically, when the target event is a subscription request event, processing the target event according to the preset processing flow and sending the corresponding processing result to the target address pointed to by the processing result includes: If it is determined that the subscription request event satisfies the management policy, the processing result of the subscription request event is obtained from the message bus; Based on the current network element scale and configuration parameters, target resources are allocated to the results of subscription request events. Target resources include thread resources and network resources. The interface address of the target network element is determined based on the unique identifier carried by the subscription request event; The processing result of the subscription request event is sent to the interface address of the target network element through thread resources and network resources; When the target event is a published event, the step of processing the target event according to a preset processing flow includes: If it is determined that the published event satisfies the management policy, then the published event is published to the message bus.

2. The method according to claim 1, characterized in that, The method further includes, before receiving the target event sent by the target network element that is communicatively connected to the network repository function network element, the method further includes: Create an event open functionality service, including: creating event subscription channels for event consumers, creating publishing channels for event producers, and creating corresponding event subscription proxy instances for all event consumers to manage all event information subscribed to by consumers.

3. The event handling method according to claim 1, characterized in that, After determining that the subscription request event does not satisfy the management policy, the method further includes: Determine whether the number of times the subscription request event is received exceeds a first threshold; If the first threshold is exceeded, a first message is returned to the target network element, which is used to indicate to the target network element that the subscription request event has been processed. If the first threshold is not exceeded, then determine whether the processing result corresponding to the subscription request event has timed out. If a timeout occurs, a second message is returned to the target network element, which is used to indicate to the target network element that it is retransmitting; If the timeout has not occurred, a third message is returned to the target network element, which is used to prompt the target network element to wait.

4. The event handling method according to claim 3, characterized in that, The target resource also includes memory resources, and the method further includes: If the processing result of the subscription request event is not allocated to the thread resources and network resources, then memory resources are allocated to the processing result of the subscription request event. The processing results of the subscription request event are cached using the memory resources; After allocating the target resource for the processing result of the subscription request event, the cached processing result of the subscription request event is sent to the interface address of the target network element through the thread resource and network resource.

5. The event handling method according to claim 4, characterized in that, The method further includes: After sending the processing result of the cached subscription request event to the interface address of the target network element through the target resource, the processing result is deleted from the memory resource.

6. The event handling method according to any one of claims 1-5, characterized in that, The method further includes: Assign a first identification number to the subscription request event; After determining that the subscription request does not meet the management policy, the subscription request is located based on the first identity identifier and then deleted.

7. A 5G core network element open event processing device, characterized in that, Network elements configured in the network repository function include: The receiving module is configured to receive target events sent by a target network element that is communicatively connected to the network repository function network element. The target events are subscription request events or publish events, and the publish events carry a unique identifier of the target network element. The judgment module is used to determine whether the target event meets the management policy. The management policy is used to limit the processing flow of the target event. In the case that the target event is a subscription request event, the judgment of whether the target event meets the management policy includes: matching the content of the subscription request event with the historical records, which include multiple subscription requests sent by different network elements. If the match fails, it is determined that the subscription request event satisfies the management policy; If a match is found, it is determined that the subscription request event does not satisfy the management policy; When the target event is a publication event, determining whether the target event meets the management policy includes: obtaining a key corresponding to the unique identifier of the target network element, and decrypting the publication event using the key; Verify the published event after the decryption operation; If the verification is successful, obtain the event publishing rule corresponding to the unique identifier; Determine whether the published event after the decryption operation satisfies the event publication rules; If the conditions are met, then the published event is determined to satisfy the management policy; If not, then the published event is determined to not satisfy the management policy; The processing module is configured to process the target event according to a preset processing flow when the target event satisfies the management policy, and send the corresponding processing result to the target address pointed to by the processing result. Specifically, when the target event is a subscription request event, processing the target event according to the preset processing flow and sending the corresponding processing result to the target address pointed to by the processing result includes: If it is determined that the subscription request event satisfies the management policy, the processing result of the subscription request event is obtained from the message bus; Based on the current network element scale and configuration parameters, target resources are allocated to the results of subscription request events. Target resources include thread resources and network resources. The interface address of the target network element is determined based on the unique identifier carried by the subscription request event; The processing result of the subscription request event is sent to the interface address of the target network element through thread resources and network resources; When the target event is a published event, the step of processing the target event according to a preset processing flow includes: If it is determined that the published event satisfies the management policy, then the published event is published to the message bus.

Images