CN115103322A

CN115103322A - Subscription merging method, device, electronic equipment, storage medium and product

Info

Publication number: CN115103322A
Application number: CN202210687092.XA
Authority: CN
Inventors: 李占武; 王达; 欧阳晔
Original assignee: Asiainfo Technologies China Inc
Current assignee: Asiainfo Technologies China Inc
Priority date: 2022-06-16
Filing date: 2022-06-16
Publication date: 2022-09-23

Abstract

The embodiment of the application provides a subscription merging method, a subscription merging device, electronic equipment, a storage medium and a product, and relates to the field of wireless communication networks. The method comprises the following steps: acquiring a subscription request sent by at least one client, wherein the subscription request carries at least one subscription event and current subscription information of the subscription event; determining a deduplication strategy of a subscription event based on a subscription event trigger type in current subscription information; based on a deduplication strategy, comparing and deduplicating current subscription information corresponding to a subscription node related to a subscription event with historical subscription information to obtain subscription operation information, wherein the subscription operation information is used for indicating a request for initiating a corresponding event to be subscribed to a target subscription node; and returning subscription response information to the client to respond to the subscription request based on the subscription response information of the target subscription node for the event to be subscribed. The embodiment of the application solves the technical problem that contents subscribed by a plurality of xApp are repeated, and improves the resource utilization rate of the subscribing node.

Description

Subscription merging method, device, electronic equipment, storage medium and product

Technical Field

The present application relates to the field of wireless communication network technologies, and in particular, to a subscription merging method, apparatus, electronic device, storage medium, and product.

Background

At present, an O-RAN (Open Radio Access Network, Open-Radio Access Network) overall architecture is provided with an O-RAN Near real-time wireless Intelligent Controller (Near-RT RIC), a data acquisition process of the Near real-time wireless Intelligent Controller is realized by adopting a subscription-reporting mode, and a plurality of microservice application programs xApps are supported to respectively subscribe data to a plurality of E2 Nodes. However, when one xApp initiates a new subscription to one or more E2Nodes, because different xApps are independent, the subscribed content of the xApp partially/totally repeats with the historical successful subscriptions of other xApps, or the newly subscribed content initiated by multiple xApps at the same time partially/totally repeats, resulting in a failed subscription or repeated collection of the same subscription information, which increases the resource consumption of the E2Node, reduces the performance of the E2Node, or even affects the service processing.

Disclosure of Invention

The embodiment of the application provides a subscription merging method, a subscription merging device, electronic equipment, a storage medium and a product, which are used for solving the technical problem that contents subscribed by a plurality of xApp are repeated and improving the resource utilization rate of a subscription node.

According to an aspect of an embodiment of the present application, there is provided a subscription merging method, including:

the method comprises the steps of obtaining a subscription request sent by at least one client, wherein the subscription request carries at least one subscription event and current subscription information of the subscription event;

determining a deduplication strategy of the subscription event based on a subscription event trigger type in the current subscription information;

based on the duplication-removing strategy, comparing and de-duplicating current subscription information and historical subscription information corresponding to a subscription node related to the subscription event to obtain subscription operation information, wherein the subscription operation information is used for indicating a request for initiating a corresponding event to be subscribed to a target subscription node;

and returning subscription response information to the client based on the subscription response information of the target subscription node for the event to be subscribed so as to respond to the subscription request.

In a possible implementation manner, the comparing and deduplicating current subscription information and historical subscription information corresponding to a subscription node related to the subscription event based on the deduplication policy to obtain subscription operation information includes:

if determining that the subscription events respectively corresponding to the current subscription information and the historical subscription information are repeated based on the deduplication strategy, removing the repeated subscription events and the related information from the current subscription information, and identifying the repeated subscription events as successful subscription events;

and recombining the current subscription information after the deduplication operation into subscription operation information for representing the target subscription node and the corresponding event to be subscribed.

In a possible implementation manner, the returning subscription response information to the client based on the subscription response information of the target subscription node for the event to be subscribed includes:

initiating a corresponding request of an event to be subscribed to the target subscription node according to the subscription operation information, so that the target subscription node returns corresponding subscription response information after responding to the request of the event to be subscribed;

and generating subscription response information for responding to the subscription request according to the subscription success event and the subscription response information, and sending the subscription response information to the client.

In one possible implementation, the subscription event trigger type includes a periodic timer trigger event; the comparing and de-duplicating the current subscription information corresponding to the subscription node related to the subscription event with the historical subscription information based on the de-duplication policy further includes:

for each subscription node, if a subscription event of which the current subscription information is inconsistent with the historical subscription information exists in the current subscription information of the subscription node, or for the same subscription event in the current subscription information and the historical subscription information in the subscription node, a first acquisition period in the current subscription information and a second acquisition period in the historical subscription information are in a non-multiple relation, determining that the subscription event is not repeated; or the like, or, alternatively,

if the first acquisition period and the second acquisition period are in an integral multiple relation for the same subscription event in the subscription node, determining that the subscription event is repeated; wherein the integer-multiple relationship comprises that the first acquisition period is an integer multiple of the second acquisition period, and the second acquisition period is an integer multiple of the first acquisition period.

In one possible implementation, the method further includes:

and when the second acquisition period is an integral multiple of the first acquisition period in the subscription node aiming at the same subscription event, sending subscription modification information to the subscription node corresponding to the subscription event, wherein the subscription modification information is used for indicating that the second acquisition period in the historical subscription information is changed into the first acquisition period in the current subscription information.

In one possible implementation, the subscription event trigger type includes a network interface message trigger event; the comparing and deduplication of the current subscription information and the historical subscription information corresponding to the subscription node related to the subscription event based on the deduplication strategy further includes:

for each subscription node, if a subscription event whose current subscription information is inconsistent with historical subscription information exists, or at least one of a call flow identifier and an interface type in the current subscription information is inconsistent with at least one of a call flow identifier and an interface type in the historical subscription information for the same subscription event in the subscription node, or for the same subscription event, the call flow identifier and the interface type are both consistent, but the transmission direction of first interface information in the current subscription information is completely different from the transmission direction of second interface information in the historical subscription information, determining that the subscription event is not repeated; or the like, or, alternatively,

for the same subscription event, the call flow identifier and the interface type are both consistent, and when the first interface information transmission direction is completely contained in the second interface information transmission direction, the subscription event is determined to be repeated; or the like, or, alternatively,

and aiming at the same subscription event, the call flow identification and the interface type are consistent, and when the first interface information transmission direction comprises the second interface information transmission direction, the included part is determined to be repeated, and the non-included part is determined not to be repeated.

In one possible implementation, the subscription event trigger type includes a measurement comparison trigger event; the comparing and deduplication of the current subscription information and the historical subscription information corresponding to the subscription node related to the subscription event based on the deduplication strategy further includes:

for each subscription node, if the current subscription information of the subscription node has a subscription event inconsistent with the historical subscription information, determining that the subscription event is not repeated; or the like, or, alternatively,

when the current subscription information is consistent with the measurement value, the measurement threshold value and the comparison result determined by the measurement value and the measurement threshold value in the historical subscription information for the same subscription event in the subscription node, determining that the subscription event is repeated; otherwise, it is determined that the subscription event is not repeated.

In a possible implementation manner, before comparing and deduplicating the current subscription information corresponding to the subscription node related to the subscription event and the historical subscription information based on the deduplication policy, the method further includes:

acquiring a subscription state identifier of a subscription node related to the subscription event;

when the subscription state identifier is a first state identifier, changing the first state identifier into a second state identifier so as to trigger comparison and duplication removal of the current subscription information and the historical subscription information; or the like, or, alternatively,

and when the subscription state identifier is a second state identifier, waiting for the second state identifier to be changed into the first state identifier.

In a possible implementation manner, the returning subscription response information to the client based on the subscription response information of the target subscription node for the event to be subscribed so as to respond to the subscription request further includes:

updating corresponding historical subscription information according to subscription response information returned by each target subscription node; and/or the presence of a gas in the atmosphere,

and adjusting the subscription identifier state of the subscription node related to the subscription event to the first state identifier.

According to another aspect of the embodiments of the present application, there is provided a subscription merging apparatus, including:

the subscription request module is used for acquiring a subscription request sent by at least one client, wherein the subscription request carries at least one subscription event and current subscription information of the subscription event;

the strategy selection module is used for determining a deduplication strategy of the subscription event based on the subscription event trigger type in the current subscription information;

the subscription merging module is used for comparing and removing the duplication aiming at the current subscription information and the historical subscription information corresponding to the subscription node related to the subscription event based on the duplication removing strategy to obtain subscription operation information, and the subscription operation information is used for indicating that a corresponding request of the event to be subscribed is initiated to a target subscription node;

and the request response module is used for returning subscription response information to the client based on the subscription response information of the target subscription node for the event to be subscribed so as to respond to the subscription request.

According to another aspect of the embodiments of the present application, there is provided an electronic device, including a memory, a processor, and a computer program stored on the memory, wherein the processor executes the computer program to implement the steps of the method of the above embodiments.

According to another aspect of the embodiments of the present application, there is provided a computer-readable storage medium having stored thereon a computer program, which when executed by a processor, implements the steps of the method of the above-described embodiments.

According to a further aspect of embodiments of the present application, there is provided a computer program product comprising a computer program which, when executed by a processor, performs the steps of the method of the above embodiments.

The technical scheme provided by the embodiment of the application has the following beneficial effects:

the embodiment of the application provides a subscription merging method, which specifically includes obtaining a subscription request sent by at least one client, where the subscription request carries at least one subscription event and current subscription information of the subscription event, determining a deduplication policy of the subscription event based on a subscription event trigger type in the current subscription information, then comparing and deduplicating current subscription information corresponding to a subscription node related to the subscription event with historical subscription information based on the deduplication policy to obtain subscription operation information, where the subscription operation information is used to indicate to initiate a request of a corresponding event to be subscribed to a target subscription node, so as to return subscription response information to the client based on subscription response information of the target subscription node for the event to be subscribed to respond to the subscription request, thus merging the current subscription information with the historical subscription information, the technical problem that content of xApp subscription is repeated in the prior art is solved, the resource utilization rate of the subscription node is improved, and the subscription success rate is improved. Meanwhile, different deduplication strategies are determined according to different subscription event trigger types, so that the expansibility and flexibility are improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below.

FIG. 1 is a block diagram of a computer system according to an embodiment of the present disclosure;

fig. 2 is a schematic structural diagram of a near real-time wireless intelligent controller provided in an embodiment of the present application;

fig. 3 is a schematic flowchart of a subscription merging method according to an embodiment of the present application;

fig. 4 is a flowchart illustrating a subscription merging method according to an exemplary embodiment of the present application;

fig. 5 is a flowchart illustrating a subscription merging method for a periodic timer trigger event according to an exemplary embodiment of the present application;

fig. 6 is a flowchart illustrating a subscription merging method for a network interface message triggering event according to an exemplary embodiment of the present application;

fig. 7 is a flowchart illustrating a subscription merging method for a measurement-to-trigger event according to an exemplary embodiment of the present application;

fig. 8 is a schematic structural diagram of a subscription merging device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Embodiments of the present application are described below in conjunction with the drawings in the present application. It should be understood that the embodiments set forth below in connection with the drawings are exemplary descriptions for explaining technical solutions of the embodiments of the present application, and do not limit the technical solutions of the embodiments of the present application.

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a computer system architecture provided in an embodiment of the present application, where the computer system 1 includes a terminal 20 and a server 10. The terminal 20 and the server 10 are connected through a communication network, and the terminal 20 and the server 10 may be directly or indirectly connected through wired or wireless communication, which is not limited in the present application.

The terminal 20 may be any terminal device installed with an application program, and is loaded with a client running the application program, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, an intelligent wearable device, and the like, which is not limited in this embodiment of the application. Regarding the hardware structure, the terminal 20 includes a display screen, a memory, a processor and an input device, but is not limited thereto.

The server 10 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud service, a cloud database, cloud computing, a cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, content distribution network, and a big data and artificial intelligence platform. The server 10 is in communication connection with a client carried by the terminal 20, so as to provide background services for the application programs developed and running in the terminal 20.

Fig. 2 is a schematic structural diagram of a near real-time wireless intelligent controller according to an embodiment of the present application, where the near real-time wireless intelligent controller includes a plurality of xApps components 110 and a ricpltform component 120. The xApps component 110 (micro service application components, such as xApp1, xApp2, xAppN) operates on the client, and is configured to complete the radio access network data acquisition, data analysis, control policy/instruction generation, and control issuing processes, for example, send a subscription request to the riclatform component 120, so that the riclatform component 120 initiates the subscription request to the subscription node. The ricpltform component 120, which may be run on the server 10, is connected to the xApps component 110 through a plurality of Near-RT RIC Open APIs (Near real-time wireless intelligent controller Open application programming interfaces), and includes functional modules such as message infrastructure module, conflict notification module, xappbscription management module 121, Security module, SDL (shared data layer) 122, and E2Termination123, which respectively implement functions such as message routing distribution, collision notification, xApp subscription management, Security, shared data layer, E2 interface management, and E2 message forwarding. The near real-time wireless intelligent controller further includes a plurality of subscribing nodes 130 (e.g., E2Node1, E2Node2, E2Node n), each subscribing Node implements information interaction with E2Termination through E2 interface, so that xApp receives information sent by the subscribing Node after subscribing to the subscribing Node is successful, and xApp can access and control the subscribing Node.

Fig. 3 is a flowchart illustrating a subscription merging method according to an embodiment of the present application. The embodiment of the present application provides a subscription merging method, which is used in the server 10 described in fig. 1, and is specifically applied to the ricpltform component 120, and the method includes steps S201 to S202.

S201, obtaining a subscription request sent by at least one client, wherein the subscription request carries at least one subscription event and current subscription information of the subscription event.

It should be noted that the xApps component running on the client initiates a subscription request to the ricpltform component disposed in the server, and in the process of initiating the subscription request, the xApps component also carries a plurality of subscription events and current subscription information of the subscription events, where the current subscription information includes a subscription node corresponding to the subscription event, a subscription event trigger type, and a source identifier used for representing the client initiating the subscription event, but is not limited thereto.

S202, determining a deduplication strategy of the subscription event based on the subscription event trigger type in the current subscription information.

In the present application, the subscription event trigger type includes a periodic timer trigger event, a network interface message trigger event, and a measurement comparison trigger event. The received subscription events are classified according to the subscription event trigger types, so that different deduplication strategies are selected according to different subscription event trigger types, the influence of the subscription event trigger conditions on the subscription operation is considered, and the expandability and flexibility of the operation are improved.

S203, based on the deduplication strategy, comparing current subscription information corresponding to the subscription node related to the subscription event with historical subscription information and performing deduplication to obtain subscription operation information, wherein the subscription operation information is used for indicating that a corresponding request of the event to be subscribed is initiated to a target subscription node.

In the application, the subscription events and the current subscription information are classified according to subscription nodes to form an Action instance list for each subscription node, that is, an information list representing the subscription events and the current subscription information of different subscription nodes.

In some embodiments, before comparing and deduplication of current subscription information and historical subscription information corresponding to a subscription node related to the subscription event based on the deduplication policy, the method further includes:

In this embodiment, the subscription status identifiers of all subscription nodes are detected before deduplication, so that when the subscription status identifier is a first status identifier (e.g., "no ongoing subscription"), the subscription status identifier is updated to be a second status identifier (e.g., "ongoing subscription"), so as to indicate that subscription merging operation based on the deduplication policy is triggered. Otherwise, when the subscription status identifier is the second status identifier (e.g., "subscription in progress"), the method waits until the subscription status identifier is changed to the first status identifier (e.g., "no subscription in progress"). Therefore, in the present embodiment, the subscription status identifier for the subscription node is added in the subscription request process, so as to ensure that the historical subscription information of the subscription node can keep atomicity in a complete subscription process of the subscription node, and improve the success rate of subscription.

In some embodiments, the comparing, based on the deduplication policy, and for the current subscription information corresponding to the subscription node related to the subscription event with the historical subscription information and performing deduplication to obtain subscription operation information includes:

if the fact that the subscription events respectively corresponding to the current subscription information and the historical subscription information are repeated is determined based on the duplication elimination strategy, the repeated subscription events and the related information are eliminated from the current subscription information, and the repeated subscription events are marked as successful subscription events;

In the application, historical subscription information of a corresponding subscription node is obtained in a database, and the historical subscription information comprises a subscription event representing successful historical subscription and subscription information thereof. Then, comparing the current subscription information (i.e. Action instance list) in the subscription node with the historical subscription information according to the deduplication strategy. Optionally, it is determined according to a deduplication policy that there is duplication in subscription events corresponding to current subscription information and historical subscription information, the duplicate subscription events and current subscription information thereof are removed from an Action instance list of the subscription node, subscription merging is performed, the duplicate subscription events are identified as subscription success events, it is represented that the subscription events have been successfully subscribed by other clients, a request for the duplicate subscription events does not need to be repeatedly sent to the subscription node in subsequent subscription operations, a situation that subscription contents between clients are duplicated is avoided, and resource loss of the subscription node is reduced. Optionally, if it is determined according to the deduplication policy that the subscription events corresponding to the current subscription information and the historical subscription information are not duplicated, the non-duplicated subscription event and the relevant current subscription information are retained in the current subscription information of the subscription node, so as to execute a request for initiating the non-duplicated subscription event to the subscription node. Therefore, the subscription information is recombined by the current subscription information (namely, the Action instance list after the deduplication operation) after the subscription events determined as the duplicates are eliminated, so as to generate the subscription operation information, wherein the subscription operation information records a target subscription node, an event to be subscribed corresponding to the target subscription node, and the current subscription information of the event to be subscribed.

S204, based on the subscription response information of the target subscription node for the event to be subscribed, returning subscription response information to the client to respond to the subscription request.

In some embodiments, the returning subscription response information to the client based on the subscription response information of the target subscription node for the event to be subscribed includes:

In the application, a request composed of a corresponding event to be subscribed and current subscription information thereof is sent to a target subscription node based on the subscription operation information, so that the target subscription node generates subscription response information after responding to the request, such as subscription success information representing successful subscription response and subscription failure information representing failed subscription response. Furthermore, the subscription success event determined as the occurrence of the subscription repetition and the subscription response information are combined and organized into the subscription response information for responding to the subscription request, so that the problem of the subscription repetition is solved, the subscription request of the user can be accurately responded, and the resource utilization rate of the subscription node is improved.

In some embodiments, the returning subscription response information to the client based on the subscription response information of the target subscription node for the event to be subscribed in response to the subscription request further includes:

updating corresponding historical subscription information according to subscription response information returned by each target subscription node; and/or the presence of a gas in the gas,

In this embodiment, after receiving subscription response information (e.g., subscription success information) returned by the target subscription node, the historical subscription information corresponding to the subscription node is updated with the subscription event and the current subscription information thereof. And, the subscription status identifier of the relevant subscription node in the current operation is adjusted from the second status identifier (e.g., "subscription in progress") to the first status identifier (e.g., "no subscription in progress"), so as to wait for the next subscription request.

Exemplarily, fig. 4 is a schematic flow diagram of a subscription merging method provided in an exemplary embodiment of the present application, where an xApps component initiates one or more subscription requests to a ricpltform component, so that the ricpltform component initiates a corresponding subscription request to a subscription node. The xApps component sends the Subscription Request and the related information to the xappsubstinguishmanager, then the xappsubstinguishmanager receives the Subscription Request (i.e. the Subscription Request message) from the xApp component in step S301, and in step S302, selects the deduplication policy according to the E2Node and the Subscription trigger type in the Subscription Request message, and breaks up the current Subscription information in the Subscription Request message, and forms a plurality of Action instance lists according to the E2 Node. Then, the xappsubscribeionmanagement in step S303 checks whether the current "E2 Node subscription status" identifier is "no ongoing subscription", if so, sets the "E2 Node subscription status" identifier as "subscription ongoing subscription", and extracts a corresponding history successful subscription Action instance list (i.e. history subscription information) from the database according to the E2Node and the type of the subscription trigger event; otherwise, wait. Further, in step S304, the xappsubscribeionmanagement compares the Action instances in the E2Node with the historical successful subscribed Action instance information of the E2Node one by one according to the deduplication policy (i.e., the deduplication rule in fig. 4). First, if the Action instance is considered to be repeated with the history successfully subscribed Action instance according to the deduplication policy, step 305a is executed: the Action instance is removed from the Action instance list of the E2Node, and the subscription result of the Action instance is SUCCESS (namely the successful subscription event) by default. Secondly, if the Action instance is considered not to be repeated with the history successful subscription Action instance according to the deduplication strategy, executing the step 305 b: and reserving the Action instance in the Action instance list of the E2 Node. Then, in step S306, the subscription message is reassembled from the list of E2Node action instances after the deduplication operations in

steps

305a and 305b, and is forwarded to the corresponding E2Node via E2 Termination. In step S307, the E2Node feeds back the subscription response message (i.e., subscription response information, such as SUCCESS/FAILURE) to E2Termination, and the E2Termination forwards the message to xappsubstinguishmanagement. After the xappsubscribermanagement receives the subscription response message (SUCCESS/FAILURE) fed back by E2Node in step S308, it updates the information related to the Action instance in the history successful subscription database, sets the identifier of "E2 Node subscription state" as "no ongoing subscription", and merges the Action instance removed in step 305a with the response message (SUCCESS/FAILURE) fed back by E2Node according to the subscription result SUCCESS, and generates the complete subscription response message of E2Node, so that the xappbscriptionmanement feeds back the subscription response message to xApp in step S309. In this way, the embodiments of the present application solve the problem that when one xApp initiates a subscription to multiple E2nodes, the subscribed content and the historical successful subscription are repeated and the subscription in progress is repeated in a near real-time radio access network intelligent loop.

The subscription merging method provided in the embodiment of the application, by obtaining a subscription request sent by at least one client, where the subscription request carries at least one subscription event and current subscription information of the subscription event, determining a deduplication policy of the subscription event based on a subscription event trigger type in the current subscription information, and then comparing and deduplicating current subscription information corresponding to a subscription node related to the subscription event with historical subscription information based on the deduplication policy to obtain subscription operation information, where the subscription operation information is used to indicate to initiate a request of a corresponding event to be subscribed to a target subscription node, so as to return subscription response information to the client to respond to the subscription request based on subscription response information of the target subscription node for the event to be subscribed, and thus subscribe and merge the current subscription information and the historical subscription information, the technical problem that content of xApp subscription is repeated in the prior art is solved, the resource utilization rate of the subscription node is improved, and the subscription success rate is improved. Meanwhile, different deduplication strategies are determined according to different subscription event trigger types, so that the expansibility and flexibility are improved.

In some embodiments, the subscription event trigger type comprises a periodic timer trigger event; the comparing and deduplication of the current subscription information and the historical subscription information corresponding to the subscription node related to the subscription event based on the deduplication strategy further includes:

for each subscription node, if a subscription event which is inconsistent with the historical subscription information exists in the current subscription information of the subscription node, or for the same subscription event in the current subscription information and the historical subscription information, a first acquisition period in the current subscription information and a second acquisition period in the historical subscription information are in a non-multiple relation, determining that the subscription event is not repeated; or the like, or a combination thereof,

In this embodiment, the subscription event trigger type includes a periodic timer trigger event, such as E2SM-KPM, i.e. E2 interface service mode is a key performance measure. If the current subscription information has a subscription event inconsistent with the historical subscription information for a subscription node, determining that the subscription event is not repeated without duplication removal, namely, keeping the subscription event and related information in an Action instance list of the subscription node. If the same subscription event in the subscription node, the acquisition Period (Granularity Period) in the current subscription information is N times (N is an integer greater than 1) the acquisition Period (Granularity Period) in the historical subscription information, or the acquisition Period (Granularity Period) in the current subscription information is 1/N times (N is an integer greater than 1) the acquisition Period (Granularity Period) in the historical subscription information, it is determined that the subscription event has repeated subscriptions and needs to be deduplicated, that is, the repeated subscription event and related information are proposed in the Action instance list of the subscription node. If the acquisition Period (Granularity Period) in the current subscription information and the acquisition Period (Granularity Period) in the historical subscription information are in a non-multiple relation in the same subscription event in the subscription node, determining that the subscription event is not repeated without repetition and without repetition.

In an optional embodiment, the method further comprises:

and when the second acquisition period is an integral multiple of the first acquisition period for the same subscription event in the subscription node, sending subscription modification information to the subscription node corresponding to the subscription event, wherein the subscription modification information is used for indicating that the second acquisition period in the historical subscription information is changed into the first acquisition period in the current subscription information.

For example, fig. 5 is a flowchart of a subscription and merging method for a periodic timer trigger event according to an exemplary embodiment of the present application, and illustrates an example in which xApp1 subscribes, to E2Node1 and E2Node2, information acquisition events Action1 to Action4 triggered by a periodic timer (that is, an acquisition Period is a hierarchical Period of 2T, where T represents a Period of time) through riclatform. Specifically, xAppSubMng (i.e., xappsubscribermanagement) receives a subscription message sent by xApp1 (step 401), where the content subscribed to E2Node1 is Action1 and Action2, and the content subscribed to E2Node2 is Action3 and Action 4.

Step 402, checking the identifier value of "E2 Node subscription status" of E2Node1 and E2Node2, and if detecting Flag _ E2Node _ Sub _ State ═ subscribe (the characterization subscription status Flag indicates "subscription in progress"), waiting until the identifier is changed to Flag _ E2Node _ Sub _ State ═ SUBFIN (the characterization subscription status Flag indicates "no subscription in progress"), so as to continue to execute the next step; if detecting Flag _ E2Node _ Sub _ State ═ SUBFIN (the characterization subscription status Flag is "no ongoing subscription"), modify the identifier to Flag _ E2Node _ Sub _ State ═ SUBING (the characterization subscription status Flag is "ongoing subscription"), and execute the next step.

Step 403, querying a database for a history successful subscription record (Action 1-Action 4), which is as follows: action 1: e2Node1, Exe _ Granularity _ Period ═ T, Granularity Period ═ T, xApp 2; action 2: no Found; action 3: e2Node2, Exe _ Granularity _ Period is 4T, Granularity Period is 4T, xApp 3; action 4: no Found.

And comparing the subscription information with the repeated historical successful subscription information according to the deduplication strategy corresponding to the periodic timer trigger event, and subscribing and combining the repeated historical successful subscription information, wherein the specific operations are as follows:

action 1: if the acquisition cycle of the current subscription is integral multiple (2 times) of the actual acquisition cycle of the historical successful subscriptions, determining that the actions 1 are repeated in subscription, executing subscription combination, and identifying the subscription result of the Action1 as SUCCESS;

action 2: unsubscribe repeatedly, do not need to carry out subscription and amalgamate;

action 3: if the actual collection Period of the successful historical subscription is an integral multiple (2 times) of the collection Period of the current subscription, determining that the Action3 subscription is repeated, sending subscription modification information to the E2Node2, modifying the subscription Period of the Action3 into the collection Period of the current subscription, which is the Period of 2T (step 404), then executing subscription merging, and identifying the subscription result as SUCCESS;

action 4: unsubscribed repeats, and subscription merging need not be performed.

In step 405-. Thus, E2Node1 and E2Node2 respond to the received current subscription information and return a subscription request response message (e.g. subscription success information for Action2 instance and subscription success information for Action4 instance), so that xAppSubMng updates the historical successful subscription information in the DataBase (step 411) after receiving E2Termination (E2T shown in fig. 5) and forwards the subscription request response message from E2Node1 and E2Node2, and changes the value of "E2 Node subscription status" identifier to Flag _ E2Node _ Sub _ State ═ SUBFIN (characterizing that the subscription status is identified as "no ongoing subscription", step 412). At this time, the history successful subscription information of the actions 1-4 in the history successful subscription information is updated to the following information:

Action1：E2Node1,Exe_Granularity_Period＝T,

Granularity Period＝T,xApp2

Granularity Period＝2T,xApp1；

Action2：E2Node1,Exe_Granularity_Period＝2T,

Granularity Period＝2T,xApp1；

Action3：E2Node2,Exe_Granularity_Period＝2T,

Granularity Period＝4T,xApp3

Granularity Period＝2T,xApp1；

Action4：E2Node2,Exe_Granularity_Period＝2T,

Granularity Period＝2T,xApp1。

step 413, xAppSubMng sends a subscription request response message to xApp1, specifically:

E2Node1：Action1(SUCCESS)，Action2(SUCCESS)；

E2Node2：Action3(SUCCESS)，Action3(SUCCESS)。

in some embodiments, the subscription event trigger type comprises a network interface message trigger event; the comparing and deduplication of the current subscription information and the historical subscription information corresponding to the subscription node related to the subscription event based on the deduplication strategy further includes:

for the same subscription event, when the call flow identifier and the interface type are both consistent, but the first interface information transmission direction is completely contained in the second interface information transmission direction, determining that the subscription event is repeated; or the like, or a combination thereof,

and for the same subscription event, the call flow identifier and the interface type are consistent, and when the first interface information transmission direction comprises the second interface information transmission direction, the included part is determined to be repeated, and the non-included part is determined to be not repeated.

In this embodiment, the subscription event trigger type includes a network interface message trigger event, such as E2SM-NI, that is, the E2 interface service mode is a network interface. If the current subscription information has a subscription event inconsistent with the historical subscription information for a subscription node, determining that the subscription event is not subscribed and repeated without repetition removal, namely, keeping the subscription event and related information in an Action instance list of the subscription node. If at least one of the call flow identifier and the interface type in the current subscription information is different in the same subscription event in the subscription node, the subscription event is considered to be unsubscribed and repeated without duplication removal. If the subscription event, the call flow identifier and the interface type are the same, but the interface message direction is different (if the transmission direction of the first interface information IN the current subscription information is "IN", and the transmission direction of the second interface information IN the historical subscription information is "OUT"), the subscription event is considered to be unsubscribed and repeated, and duplicate removal is not needed. If the subscription event, the call flow identifier and the interface type are the same, but the first interface information transmission direction includes the second interface information transmission direction (if the first interface information transmission direction is "IN & OUT", and the second interface information transmission direction is "OUT"), it is considered that the subscription event subscription IN the "OUT" direction is repeated and duplication removal is needed, and the subscription event IN the "IN" direction does not have repeated subscription and duplication removal is not needed. If the subscription event, the call flow identifier, and the interface type are the same, but the first interface information transmission direction is completely included IN the second interface information transmission direction (for example, the first interface information transmission direction is "IN", and the second interface information transmission direction is "IN & OUT"), it is determined that the subscription event subscription is repeated, and deduplication is required.

Exemplarily, fig. 6 is a flowchart of a subscription merging method for network interface message trigger events according to an exemplary embodiment of the present application, and an example is described by using xApp1 to subscribe to E2Node1 and E2Node2 through riclatform, where the network interface messages (i.e., interfaces of Action1 to Action4 are INTF _ a, INTF _ b, INTF _ c, and INTF _ d, and transmission directions of the interface messages are IN, IN & Out, and Out, respectively) to trigger information acquisition events Action1 to Action 4. Specifically, xappsubpmng (that is, xappsubportionmanagement) receives the subscription message sent by xApp1 (step 501), where the content subscribed to E2Node1 is Action1 and Action2, and the content subscribed to E2Node2 is Action3 and Action 4.

Step 502, checking the identifier value of "E2 Node subscription status" of E2Node1 and E2Node2, and if Flag _ E2Node _ Sub _ State ═ SUBING is detected, waiting until the identifier is changed to Flag _ E2Node _ Sub _ State ═ subinfin, so that the next step can be executed; if Flag _ E2Node _ Sub _ State ═ SUBFIN is detected, the identifier is modified to Flag _ E2Node _ Sub _ State ═ SUBING, and the next step is performed.

Step 503, querying the database for history successful subscription records (Action 1-Action 4), as follows: action 1: e2Node1, Call Process m, INTF _ a, IN, xApp 2; action 2: e2Node1, Call Process m, INTF _ b, IN, xApp 2; action 3: e2Node2, Call Process m, INTF _ c, IN, xApp 2; action 4: no Found.

And comparing according to the deduplication strategy corresponding to the network interface message trigger event, subscribing and combining repeated historical successful subscription information, and specifically operating as follows:

action 1: if the current subscription information is completely the same as actions 1, E2Node1, Call Process m, interface identifier INTF _ a and interface message transmission direction "IN the history successful subscription record, determining that the subscriptions of actions 1 are repeated, executing subscription merging, and identifying that the subscription result of the Action1 is SUCCESS;

action 2: the current subscription information is the same as Action2, E2Node1, Call Process m and interface identification INTF _ b IN the history successful subscription record, but the same interface message transmission 'IN' direction exists subscription repetition, and the 'OUT' direction does not exist subscription repetition, so that subscription merging is executed for the subscription events IN the 'IN' direction, and the subscription events IN the 'OUT' direction do not need to be executed subscription merging;

action 3: if the current subscription information is the same as Action3, E2Node2, Call Process m and interface identifier INTF _ b in the history successful subscription record, but the transmission direction of the interface message is completely different, it is determined that Action3 is not subscribed repeatedly, and subscription merging does not need to be executed;

action 4: unsubscribed repeats, and subscription merger need not be performed.

In step 505-. Thus, E2Node1 and E2Node2 respond to the received current subscription information and return the subscription request reply message (such as the subscription success information for the instance of Action2, the subscription success information for the instance of Action3, and the subscription success information for the instance of Action4), so that xAppSubMng, after receiving E2Termination (E2T shown in fig. 6) and forwarding the subscription request reply message from E2Node1 and E2Node2, updates the historical successful subscription information in DataBase (step 510), and changes the value of "E2 Node subscription status" identifier of E2Node1 and E2Node2 to Flag _ E2Node _ Sub _ State ═ SUBFIN (characterization subscription status identifier is "no ongoing subscription", step 511). At this time, the history successful subscription information of the actions 1 to 4 in the history successful subscription information is updated to the following information:

Action1：E2Node1,Call Process＝m,INTF_a,IN,

xApp2,

xApp1；

Action2：E2Node1,Call Process＝m,INTF_b,IN,

xApp2,

xApp1,

E2Node1,Call Process＝m,INTF_b,OUT,

xApp1；

Action3：E2Node2,Call Process＝m,INTF_c,IN,

xApp2,

E2Node2,Call Process＝m,INTF_c,OUT,

xApp1；

Action4：E2Node2,Call Process＝m,INTF_d,IN,

xApp1。

step 512, xAppSubMng sends a subscription request response message to xApp1, specifically:

E2Node1：Action1(SUCCESS)，Action2(SUCCESS)；

E2Node2：Action3(SUCCESS)，Action3(SUCCESS)。

in some embodiments, the subscription event trigger type comprises a measurement versus trigger event; the comparing and deduplication of the current subscription information and the historical subscription information corresponding to the subscription node related to the subscription event based on the deduplication strategy further includes:

in the subscription node, when the current subscription information is consistent with the measurement value and the measurement threshold value in the historical subscription information and the comparison result determined by the measurement value and the measurement threshold value aiming at the same subscription event, determining that the subscription event is repeated; otherwise, it is determined that the subscription event is not repeated.

In this embodiment, the subscription event trigger type includes a measurement versus trigger event, such as E2SM-RC, i.e. the E2 interface service mode is radio access network controlled. If the current subscription information has a subscription event inconsistent with the historical subscription information for a subscription node, determining that the subscription event is not subscribed and repeated without repetition removal, namely, keeping the subscription event and related information in an Action instance list of the subscription node. If the current subscription information is consistent with the measurement threshold value and the measurement reporting condition (such as equal to or greater than the threshold value/less than the threshold value/greater than or equal to the threshold value/less than or equal to the threshold value) in the historical subscription information in the same subscription event in the subscription node, determining that the subscription event is repeatedly sent and read and the duplicate is required to be removed, namely removing the duplicate subscription event and related information from an Action instance list of the subscription node. If the current subscription information is inconsistent with at least one of the measurement threshold value and the measurement reporting condition (such as equal to or greater than the threshold value/less than the threshold value/greater than or equal to the threshold value/less than or equal to the threshold value) in the historical subscription information in the same subscription event in the subscription node, the subscription event is considered to be unsubscribed and repeated without duplication.

For example, fig. 7 is a flowchart of a subscription merging method for measurement comparison trigger events according to an exemplary embodiment of the present application, and an example is described in which xApp1 subscribes, to E2Node1 and E2Node2, information collection events 1 to Action4 triggered by measurement values exceeding thresholds (that is, measurement items are TestItm _ a, TestItm _ b, TestItm _ c, TestItm _ d, and the exceeding threshold conditions are > TH _ a, > < TH _ b, < TH _ c, < ═ TH _ d, respectively) through ricpltform. Specifically, xappsubpmng (that is, xappsubportionmanagement) receives the subscription message sent by xApp1 (step 601), where the content subscribed to E2Node1 is Action1 and Action2, and the content subscribed to E2Node2 is Action3 and Action 4.

Step 602, checking the identifier value of "E2 Node subscription status" of E2Node1 and E2Node2, and if detecting Flag _ E2Node _ Sub _ State ═ subang, waiting until the identifier is changed to Flag _ E2Node _ Sub _ State ═ SUBFIN, so that the next step can be executed; if it is detected that Flag _ E2Node _ Sub _ State ═ SUBFIN, the identifier is modified to Flag _ E2Node _ Sub _ State ═ SUBING, and the next step is performed.

Step 603, querying a database for history successful subscription records (Action 1-Action 4), which are as follows: action 1: e2Node1, TestItm _ a > TH _ a, xApp 2; action 2: no Found; action 3: no Found; action 4: no Found.

And then, comparing the duplicate removal strategies corresponding to the measurement comparison trigger events, subscribing and combining repeated historical successful subscription information, and specifically operating as follows:

action 1: if the current subscription information is completely the same as actions 1, E2Node1, TestItem _ a, threshold value TH _ a and threshold value direction "> (namely the comparison result of the measurement item and the threshold value) in the history successful subscription record, determining that the actions 1 subscription is repeated, executing subscription combination and marking the subscription result of the Action1 as SUCCESS;

action 3: unsubscribe repeatedly, do not need to carry out subscription and amalgamate;

action 4: unsubscribed repeats, and subscription merger need not be performed.

In step 605-. Thus, E2Node1 and E2Node2 respond to the received current subscription information and return the subscription request reply message (such as the subscription success information for the instance of Action2, the subscription success information for the instance of Action3, and the subscription success information for the instance of Action4), so that xAppSubMng updates the historical successful subscription information in DataBase (step 610) after receiving E2Termination (E2T shown in fig. 7) and forwarding the subscription request reply message from E2Node1 and E2Node2, and changes the value of "E2 Node subscription status" identifier of E2Node1 and E2Node2 to Flag _ E2Node _ Sub _ State ═ SUBFIN (step 611). At this time, the history successful subscription information of the actions 1-4 in the history successful subscription information is updated to the following information:

Action1：E2Node1,TestItm_a>TH_a,

xApp2,

xApp1；

Action2：E2Node1,TestItm_b>＝TH_b,

xApp1；

Action3：E2Node2,TestItm_c<TH_c,

xApp1；

Action4：E2Node2,TestItm_d<＝TH_d,

xApp1。

step 612, xAppSubMng sends a subscription request response message to xApp1, specifically:

E2Node1：Action1(SUCCESS)，Action2(SUCCESS)；

E2Node2：Action3(SUCCESS)，Action3(SUCCESS)。

fig. 8 is a schematic structural diagram of a subscription merging apparatus according to an embodiment of the present application, where the subscription merging apparatus 700 includes:

a subscription request module 701, configured to obtain a subscription request sent by at least one client, where the subscription request carries at least one subscription event and current subscription information of the subscription event;

a policy selecting module 702, configured to determine a deduplication policy of the subscription event based on a subscription event trigger type in the current subscription information;

a subscription merging module 703, configured to compare and deduplicate current subscription information corresponding to a subscription node related to the subscription event with historical subscription information based on the deduplication policy to obtain subscription operation information, where the subscription operation information is used to indicate to initiate a request of a corresponding event to be subscribed to a target subscription node;

a request response module 704, configured to return subscription response information to the client based on the subscription response information of the target subscription node for the event to be subscribed, so as to respond to the subscription request.

In some embodiments, the subscription consolidation module 703 includes:

a duplicate removal unit, configured to remove duplicate subscription events and related information from the current subscription information and identify the duplicate subscription events as successful subscription events if it is determined that the subscription events corresponding to the current subscription information and the historical subscription information are duplicate based on the duplicate removal policy;

and the recombining unit is used for recombining the current subscription information after the deduplication operation into the subscription operation information used for representing the target subscription node and the corresponding event to be subscribed.

In some embodiments, request response module 704 includes:

a target subscription node response unit, configured to initiate a corresponding request for an event to be subscribed to the target subscription node according to the subscription operation information, so that the target subscription node returns corresponding subscription response information after responding to the request for the event to be subscribed;

and the subscription response information generating unit is used for generating subscription response information used for responding to the subscription request according to the subscription success event and the subscription response information, and sending the subscription response information to the client.

In some embodiments, the subscription consolidation module 703 includes:

a first duplication-removal-policy unrepeated-judgment unit, configured to determine, for each subscription node, that a subscription event is not duplicated if a subscription event exists in current subscription information of the subscription node, the subscription event being inconsistent with historical subscription information, or a first acquisition period in the current subscription information and a second acquisition period in the historical subscription information are in a non-multiple relationship for a same subscription event in the current subscription information and the historical subscription information in the subscription node;

a first duplication removal strategy repetition judgment unit, configured to determine that the subscription event is duplicated if the first acquisition period and the second acquisition period are in an integer multiple relationship for the same subscription event in the subscription node; wherein the integer-multiple relationship comprises that the first acquisition period is an integer multiple of the second acquisition period, and the second acquisition period is an integer multiple of the first acquisition period.

In some embodiments, the first deduplication strategy repetition determination unit includes:

and a subscription information modification unit, configured to send subscription modification information to a subscription node corresponding to the subscription event when the second acquisition period is an integer multiple of the first acquisition period for the same subscription event in the subscription node, where the subscription modification information is used to indicate that the second acquisition period in the historical subscription information is changed to the first acquisition period in the current subscription information.

In some embodiments, the subscription merge module 703 includes:

a second duplication-removal-policy non-duplication-determination unit, configured to determine, for each subscription node, that a subscription event is not duplicated if there is a subscription event whose current subscription information is inconsistent with historical subscription information, or at least one of a call flow identifier and an interface type in the current subscription information and the historical subscription information is inconsistent with the same subscription event in the subscription node, or the call flow identifier and the interface type are both consistent with each other for the same subscription event, but a transmission direction of first interface information in the current subscription information is completely different from a transmission direction of second interface information in the historical subscription information;

a second duplication-elimination-policy duplication-judgment unit, configured to determine that, for a same subscription event, the call flow identifier and the interface type are both consistent, but the first interface information transmission direction is completely included in the second interface information transmission direction, the subscription event is duplicated;

and a second duplication removal strategy processing unit, configured to determine that the included part is subscription duplication and that the uncontained part is subscription duplication if the call flow identifier and the interface type are both consistent for the same subscription event but the first interface information transmission direction includes the second interface information transmission direction.

In some embodiments, the subscription merge module 703 includes:

a third duplication-removing-policy unrepeated-judging unit, configured to determine, for each subscription node, that a subscription event whose current subscription information is inconsistent with historical subscription information exists, that the subscription event is not duplicated;

a third duplication elimination strategy duplication judgment unit, configured to determine that a subscription event is duplicated when, for a same subscription event, a measurement value in current subscription information and historical subscription information, a measurement threshold value, and a comparison result determined by the measurement value and the measurement threshold value are all consistent in the subscription node; otherwise, determining that the subscription event is not repeated.

In some embodiments, the subscription merging apparatus 700 further includes:

a subscription status identifier obtaining unit, configured to obtain a subscription status identifier of a subscription node related to the subscription event;

a trigger duplicate removal unit, configured to change the first state identifier to a second state identifier when the subscription state identifier is a first state identifier, so as to trigger comparison and duplicate removal between the current subscription information and historical subscription information;

and the waiting unit is used for waiting for the second state identifier to be changed into the first state identifier when the subscription state identifier is the second state identifier.

In some embodiments, request response module 704 further includes:

the information updating unit is used for updating corresponding historical subscription information according to the subscription response information returned by each target subscription node;

and the identifier adjusting unit is used for adjusting the subscription identifier state of the subscription node related to the subscription event to the first state identifier.

The apparatus of the embodiment of the present application may execute the method provided by the embodiment of the present application, and the implementation principle is similar, the actions executed by the modules in the apparatus of the embodiments of the present application correspond to the steps in the method of the embodiments of the present application, and for the detailed functional description of the modules of the apparatus, reference may be specifically made to the description in the corresponding method shown in the foregoing, and details are not repeated here.

An embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory, where the processor executes the computer program to implement the steps of the subscription merging method, and as compared with the related art, the electronic device may implement: the current subscription information and the historical subscription information are subscribed and combined, the technical problem that the content of the xApp subscription is repeated in the prior art is solved, the resource utilization rate of the subscription node is improved, and the subscription success rate is improved. Meanwhile, different deduplication strategies are determined according to different subscription event trigger types, so that the expansibility and flexibility are improved.

In an alternative embodiment, an electronic device is provided, as shown in fig. 9, the electronic device 800 shown in fig. 9 comprising: a processor 801 and a memory 803. Wherein the processor 801 is coupled to a memory 803, such as via a bus 802. Optionally, the electronic device 800 may further include a transceiver 804, and the transceiver 804 may be used for data interaction between the electronic device and other electronic devices, such as transmission of data and/or reception of data. It should be noted that the transceiver 804 is not limited to one in practical applications, and the structure of the electronic device 800 is not limited to the embodiment of the present application.

The Processor 801 may be a CPU (Central Processing Unit), a general-purpose Processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 801 may also be a combination of computing functions, e.g., comprising one or more microprocessors, a combination of a DSP and a microprocessor, or the like.

Bus 802 may include a path that transfers information between the above components. The bus 802 may be a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus 802 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 9, but this does not indicate only one bus or one type of bus.

The Memory 803 may be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), a magnetic Disc storage medium, other magnetic storage devices, or any other medium that can be used to carry or store a computer program and that can be Read by a computer, without limitation.

The memory 803 is used for storing computer programs for executing the embodiments of the present application, and is controlled by the processor 801 to execute the computer programs. The processor 801 is adapted to execute computer programs stored in the memory 803 to implement the steps shown in the foregoing method embodiments.

Embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, and when being executed by a processor, the computer program may implement the steps and corresponding contents of the foregoing method embodiments.

Embodiments of the present application further provide a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps and corresponding contents of the foregoing method embodiments may be implemented.

The foregoing is only an optional implementation manner of a part of implementation scenarios in this application, and it should be noted that, for those skilled in the art, other similar implementation means based on the technical idea of this application are also within the protection scope of the embodiments of this application without departing from the technical idea of this application.

Claims

1. A subscription merging method, comprising:

based on the duplication removal strategy, comparing current subscription information corresponding to a subscription node related to the subscription event with historical subscription information and removing duplication to obtain subscription operation information, wherein the subscription operation information is used for indicating a request for initiating a corresponding event to be subscribed to a target subscription node;

2. The method according to claim 1, wherein the comparing and deduplication of the current subscription information and the historical subscription information corresponding to the subscription node related to the subscription event based on the deduplication policy to obtain subscription operation information includes:

3. The method according to claim 2, wherein the returning subscription response information to the client based on the subscription response information of the target subscription node for the event to be subscribed comprises:

4. The method of claim 2, wherein the subscription event trigger type comprises a periodic timer trigger event; the comparing and deduplication of the current subscription information and the historical subscription information corresponding to the subscription node related to the subscription event based on the deduplication strategy further includes:

5. The method of claim 4, further comprising:

6. The method of claim 2, wherein the subscription event trigger type comprises a network interface message trigger event; the comparing and deduplication of the current subscription information and the historical subscription information corresponding to the subscription node related to the subscription event based on the deduplication strategy further includes:

7. The method of claim 2, wherein the subscription event trigger type comprises a measurement versus trigger event; the comparing and deduplication of the current subscription information and the historical subscription information corresponding to the subscription node related to the subscription event based on the deduplication strategy further includes:

in the subscription node, when the current subscription information is consistent with the measurement value and the measurement threshold value in the historical subscription information and the comparison result determined by the measurement value and the measurement threshold value aiming at the same subscription event, determining that the subscription event is repeated; otherwise, determining that the subscription event is not repeated.

8. The method according to claim 1, wherein before comparing and deduplicating current subscription information corresponding to a subscription node related to the subscription event with historical subscription information based on the deduplication policy, the method further comprises:

9. The method according to claim 8, wherein the returning subscription response information to the client to respond to the subscription request based on the subscription response information of the target subscription node for the event to be subscribed, further comprises:

10. A subscription merging apparatus, comprising:

11. An electronic device comprising a memory, a processor and a computer program stored on the memory, characterized in that the processor executes the computer program to implement the steps of the method of any of claims 1-9.

12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 9.

13. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1-9 when executed by a processor.