CN115103322B

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

Info

Publication number: CN115103322B
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: 2024-05-31
Anticipated expiration: 2042-06-16
Also published as: CN115103322A

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 de-duplication strategy of a subscription event based on a subscription event trigger type in the current subscription information; comparing and de-duplicating current subscription information corresponding to the subscription node related to the subscription event with historical subscription information based on a de-duplication strategy to obtain subscription operation information, wherein the subscription operation information is used for indicating to initiate a request of the corresponding event to be subscribed to a target subscription node; and based on the subscription response information of the target subscription node for the event to be subscribed, the subscription response information is returned to the client so as to respond to the subscription request. The embodiment of the application solves the technical problem that the contents subscribed by a plurality of xApp are repeated, and improves the resource utilization rate of the subscribing nodes.

Description

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

Technical Field

The application relates to the technical field of wireless communication networks, in particular to a subscription merging method, a subscription merging device, electronic equipment, a storage medium and a product.

Background

Currently, a Near-real-time wireless intelligent Controller (O-RAN NEAR REAL TIME RAN INTELLIGENT Controller, near-RT RIC) is arranged in an overall architecture of an O-RAN (Open Radio Access Network ), and a data acquisition process of the Near-real-time wireless intelligent Controller is implemented by adopting a subscription-reporting mode, and a plurality of micro-service applications xApps are supported to subscribe data to a plurality of E2Nodes respectively. However, when one xApp initiates a new subscription to one or more E2Nodes, because of the independence between different xApps, the content subscribed by xApp and the historical successful subscriptions of other xApps are partially/completely repeated, or the new subscription content initiated by multiple xApps is partially/completely repeated, which results in the subscription failure or the repeated acquisition of the same subscription information, which causes an increase of the resource consumption of the E2Node, a decrease of the performance of the E2Node, and even affects the service processing.

Disclosure of Invention

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

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

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 de-duplication strategy of the subscription event based on the subscription event trigger type in the current subscription information;

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

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

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

If the duplication eliminating strategy is based on that the current subscription information and the historical subscription information respectively correspond to the subscription events, duplicated subscription events and related information are removed from the current subscription information, and duplicated subscription events are identified as subscription success events;

And reorganizing the current subscription information after the de-duplication operation into subscription operation information for representing the target subscription node and the corresponding event to be subscribed.

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

initiating a request of a corresponding 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 current subscription information and historical subscription information corresponding to the subscription nodes related to the subscription event based on the de-duplication policy, further includes:

For each subscription node, if the current subscription information of each subscription node has a subscription event inconsistent with the historical subscription information, or the same subscription event in the current subscription information and the historical subscription information is aimed at in the subscription node, determining that the subscription event is not repeated if 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; or alternatively, the first and second heat exchangers may be,

If the first acquisition period and the second acquisition period are in an integer multiple relation for the same subscription event in the subscription node, determining that the subscription event is repeated; wherein the integer multiple relationship includes the first acquisition period being an integer multiple of the second acquisition period, and the second acquisition period being an integer multiple of the first acquisition period.

In one possible implementation, the method further includes:

and when the second acquisition period is integral multiple of the first acquisition period in the subscription node aiming at the same subscription event, subscription modification information is sent 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 de-duplicating current subscription information and historical subscription information corresponding to the subscription nodes related to the subscription event based on the de-duplication policy, further includes:

for each subscription node, if the current subscription information of each subscription node has a subscription event inconsistent with the historical subscription information, or at least one of a call flow identifier and an interface type in the current subscription information of each subscription node is inconsistent with the historical subscription information for the same subscription event, or the call flow identifier and the interface type are consistent for the same subscription event, and when 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 alternatively, the first and second heat exchangers may be,

For the same subscription event, if the call flow identifier and the interface type are 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 alternatively, the first and second heat exchangers may be,

For the same subscription event, the call flow identifier and the interface type are consistent, but when the first interface information transmission direction includes the second interface information transmission direction, the contained part is determined to be repeated, and the part which is not contained is determined to be unrepeated.

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

For each subscription node, determining that the current subscription information of each subscription node has a subscription event inconsistent with the historical subscription information, and determining that the subscription event is not repeated; or alternatively, the first and second heat exchangers may be,

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

In one possible implementation manner, before comparing and deduplicating current subscription information corresponding to the subscription node related to the subscription event with 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 alternatively, the first and second heat exchangers may be,

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 one possible implementation manner, the method 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, in order 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 number of the groups of groups,

And adjusting the subscription identification state of the subscription node related to the subscription event to be the first state identification.

According to another aspect of an embodiment of the present application, there is provided a subscription merging device, 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 de-duplication 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 de-duplicating current subscription information corresponding to the subscription node related to the subscription event with historical subscription information based on the de-duplication strategy to obtain subscription operation information, wherein the subscription operation information is used for indicating to initiate a request of a corresponding event to be subscribed 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, the processor executing 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 embodiments.

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

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

The embodiment of the application provides a subscription merging method, specifically, a subscription request sent by at least one client is obtained, the subscription request carries at least one subscription event and current subscription information of the subscription event, a de-duplication strategy of the subscription event is determined based on a subscription event trigger type in the current subscription information, then the current subscription information corresponding to a subscription node related to the subscription event is compared with and de-duplicated with historical subscription information based on the de-duplication strategy, subscription operation information is obtained, the subscription operation information is used for indicating a request for initiating a corresponding event to be subscribed to a target subscription node, and subscription response information is returned to the client based on subscription response information of the target subscription node for the event to be subscribed, so that the current subscription information and the historical subscription information are combined in a subscription mode, the technical problem that xApp subscription contents are 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 that are required to be used in the description of the embodiments of the present application will be briefly described below.

FIG. 1 is a schematic diagram of a computer system architecture according to an embodiment of the present application;

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

FIG. 3 is a schematic flow chart of a subscription merging method according to an embodiment of the present application;

FIG. 4 is a flow chart of a subscription merging method according to an exemplary embodiment of the present application;

FIG. 5 is a flow chart of a method for subscription merge for periodic timer trigger events according to an exemplary embodiment of the present application;

FIG. 6 is a flow chart of a method for subscription merging for network interface message triggering events according to an exemplary embodiment of the present application;

FIG. 7 is a flow chart of a method for subscription consolidation for measurement alignment triggering events 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 with reference to the drawings in the present application. It should be understood that the embodiments described below with reference to the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application, and the technical solutions of the embodiments of the present application are not limited.

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a computer system architecture according to 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 a wired or wireless communication manner, which is not limited in the present application.

The terminal 20 may be any terminal device that installs an application program, and has a client running the application program, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart wearable device, etc., which is not limited by the embodiment of the present application. Regarding the hardware configuration, 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 cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, a content distribution network, basic cloud computing services such as big data and an artificial intelligence platform. The server 10 is communicatively connected to a client mounted on the terminal 20 so as to provide a background service for an application program 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 units 110 and RICPlatForm units 120. The xApps component 110 (micro-service application component, such as xApp1, xApp, xAppN) is running on the client and is configured to complete radio access network data acquisition, data analysis, control policy/instruction generation, and control issuing processes, such as sending a subscription request to the RICPlatForm component 120, so that the RICPlatForm component 120 initiates the subscription request to the subscribing node. RICPlatForm component 120, which is capable of running on server 10, is connected to xApps component 110 through a plurality of Near-real-time radio intelligent controller Open application programming interfaces, and includes functional modules such as MessagingInfrastructure (message infrastructure module), conflictMitigation (conflict mitigation module), xAppSubscriptionManagement (subscription management module) 121, security module, SDL (shared data layer) 122, and E2Termination123, and implements functions such as message routing distribution, conflict mitigation, xApp subscription management, security, shared data layer, E2 interface management, and E2 message forwarding, respectively. The near real-time wireless intelligent controller further comprises a plurality of subscription nodes 130 (e.g., E2Node1, E2Node2, E2Node n), wherein each subscription Node realizes information interaction with E2Termination through an E2 interface, so xApp receives information sent by the subscription Node after successful subscription to the subscription Node, and xApp can access and control the subscription Node.

Fig. 3 is a flow chart of a subscription merging method according to an embodiment of the present application. An embodiment of the present application provides a subscription merging method for the server 10 shown in fig. 1, specifically applied to RICPlatForm components 120, where the method includes steps S201 to S202.

S201, 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.

It should be noted that, the xApps component running on the client initiates a subscription request to the RICPlatForm component located on the server, and in the initiation process of the subscription request, a plurality of subscription events and current subscription information of the subscription events are carried, where the current subscription information includes a subscription node corresponding to the subscription event, a subscription event trigger type, and a source identifier for characterizing the client initiating the subscription event, but is not limited thereto.

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

In the application, the subscription event trigger types comprise 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 subscription operations is considered, and the expansibility and flexibility of the operations are improved.

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

In the application, the subscription events and the current subscription information thereof are classified according to the subscription nodes to form an Action instance list aiming at each subscription node, namely an information list representing the subscription events and the current subscription information of different subscription nodes.

In some embodiments, before comparing and deduplicating current subscription information corresponding to the subscription node related to the subscription event with historical subscription information 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 a second status identifier (e.g. "subscription ongoing") to indicate that a subscription merging operation based on deduplication policies is triggered. Otherwise, when the subscription status identifier is the second status identifier (such as "subscription in progress"), waiting until the subscription status identifier is changed to the first status identifier (such as "no subscription in progress"). Therefore, in the embodiment, the subscription status identifier for the subscription node is added in the subscription request process, so that the historical subscription information of the subscription node can keep atomicity in a complete subscription process of the subscription node, and the subscription success rate is improved.

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

In the application, historical subscription information of a corresponding subscription node is obtained in a database, wherein the historical subscription information comprises subscription events and subscription information thereof representing successful historical subscription. Then, the current subscription information (i.e., action instance list) in the subscribing node is compared with the historical subscription information according to the deduplication policy. Optionally, if it is determined that the current subscription information and the historical subscription information respectively correspond to the subscription events and have repetition according to the deduplication policy, the repeated subscription events and the current subscription information thereof are removed from the Action instance list of the subscription node, subscription merging is performed, the repeated subscription events are identified as successful subscription events, the subscription events are represented to be successfully subscribed by other clients, the repeated subscription event request is not required to be repeatedly initiated to the subscription node in subsequent subscription operation, the situation that the subscription content between the clients is repeated is avoided, and the resource loss of the subscription node is reduced. Optionally, determining that the subscription events corresponding to the current subscription information and the historical subscription information respectively are not repeated according to the deduplication policy, and reserving the unrepeated subscription events and related current subscription information in the current subscription information of the subscription node so as to execute a request for initiating the unrepeated subscription events to the subscription node. Therefore, the current subscription information (namely, the Action instance list after the duplication removal operation) after the repeated subscription event is removed is recombined to generate 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, the subscription response information is returned to the client so as 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, based on subscription operation information, a request composed of a corresponding event to be subscribed and current subscription information thereof is sent to a target subscription node, so that the target subscription node generates subscription response information, such as subscription success information representing successful subscription response and subscription failure information representing failure of subscription response, after responding to the request. Furthermore, the subscription success event determined to be the occurrence of the subscription repetition and the subscription response information are combined and organized into the subscription response information used 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 method further includes, based on subscription response information of the target subscription node for the event to be subscribed, returning subscription response information to the client in response to the subscription request, and further including:

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

Illustratively, fig. 4 is a flow chart of a subscription merging method provided by an exemplary embodiment of the present application, where the xApps component initiates one or more subscription requests to the RICPlatForm component, so that the RICPlatForm component initiates corresponding subscription requests to the subscribing node. The xApps component sends the subscription request and related information to xAppSubscriptionManagement, then xAppSubscriptionManagement receives the subscription request (i.e., subscription Request message) from xApp component in step S301, selects a deduplication policy according to E2Node and subscription trigger type in SubscriptionRequest message in step S302, breaks up the current subscription information in Subscription Request message, and forming a plurality of Action instance lists according to the E2Node. Then, in step S303, xAppSubscriptionManagement checks whether the current identifier of "E2Node subscription status" is "no subscription in progress", if so, sets the identifier of "E2Node subscription status" as "subscription in progress", and extracts the corresponding history successful subscription Action instance list (i.e. history subscription information) from the database according to the E2Node and the subscription trigger event type; otherwise, waiting. Further, in step S304, xAppSubscriptionManagement compares the Action instance in the E2Node with the information of the successfully subscribed Action instance of the E2Node history one by one according to the deduplication policy (i.e. the deduplication rule in fig. 4). First, the Action instance is considered to be repeated with the history of successful subscribed Action instances according to the deduplication policy, then step 305a is performed: and removing the Action instance from the Action instance list of the E2Node, and defaulting the Action instance subscription result to SUCCESS (i.e. subscribing to a SUCCESS event). Secondly, according to the deduplication policy, the Action instance is considered to be non-duplicate with the history of successful subscriptions to the Action instance, then step 305b is performed: the Action instance in the Action instance list of the E2Node is reserved. Then, in step S306, the subscription message is reorganized from the E2NodeAction instance list after the deduplication operation in step S305 a and step S305 b, and forwarded to the corresponding E2Node via E2 Termination. In step S307, the E2Node feeds back a subscription response message (i.e. subscription response information, such as SUCCESS/FAILURE) to the E2Termination, which forwards the message to xAppSubscriptionManagement. After receiving the subscription response message (SUCCESS/FAILURE) fed back by the E2Node, xAppSubscriptionManagement in step S308 updates the relevant information of the Action instance in the history successful subscription database, sets the identifier of "E2Node subscription status" as "no subscription in progress", combines the Action instance removed in step S305 a with the response message (SUCCESS/FAILURE) fed back by the E2Node according to the subscription result SUCCESS, generates the complete subscription response message of the E2Node, whereby xAppSubscriptionManagement feeds back a subscription answer message to xApp in step 309. In this way, the embodiment of the application solves the problems that the subscribed content and the historical successful subscription exist when one xApp initiates subscription to a plurality of E2 nodes in the intelligent loop of the near real-time wireless access network and the ongoing subscription is repeated.

According to the subscription merging method provided by the embodiment of the application, the subscription request sent by at least one client is obtained, the subscription request carries at least one subscription event and the current subscription information of the subscription event, the de-duplication strategy of the subscription event is determined based on the subscription event triggering type in the current subscription information, then the current subscription information corresponding to the subscription node related to the subscription event is compared with the historical subscription information and de-duplicated based on the de-duplication strategy, the subscription operation information is obtained, the subscription operation information is used for indicating the request for initiating the corresponding event to be subscribed to the target subscription node, so that the subscription response information is returned to the client based on the subscription response information of the target subscription node for the event to be subscribed to respond to the subscription request, the current subscription information and the historical subscription information are combined in a subscription mode, the technical problem that xApp subscribed contents are 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 de-duplicating current subscription information and historical subscription information corresponding to the subscription nodes related to the subscription event based on the de-duplication policy, further includes:

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 does not have subscription repetition, and retaining the subscription event and related information in an Action instance list of the subscription node without de-duplication. If the same subscription event in the subscription node is detected, the collection period (Granularity Period) in the current subscription information is N times (N is an integer greater than 1) of the collection period (Granularity Period) in the historical subscription information, or the collection period (Granularity Period) in the current subscription information is 1/N times (N is an integer greater than 1) of the collection period (Granularity Period) in the historical subscription information, determining that the subscription event is repeatedly subscribed, and removing the duplication is needed, namely, the repeated subscription event and related information are proposed in an Action instance list of the subscription node. If the collection period (Granularity Period) in the current subscription information and the collection period (Granularity Period) in the historical subscription information are in a non-multiple relationship with the same subscription event in the subscription node, determining that the subscription event is not subjected to subscription repetition, and not needing to be duplicated.

In an alternative embodiment, the method further comprises:

Fig. 5 is a schematic flow chart of a subscription merging method for periodic timer triggering events according to an exemplary embodiment of the present application, and xApp1 subscribes E2Node1 and E2Node2 to information acquisition events 1-Action 4 triggered by periodic timers (i.e. acquisition period Granularity Period =2t, t represents a period of time) through RICPlatForm. Specifically, xAppSubMng (i.e., xAppSubscriptionManagement) receives the 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 Action4.

Step 402, checking the identifier values of the "E2Node subscription status" of E2Node1 and E2Node2, if flag_e2node_sub_state= = SUBING (the Flag subscription status is identified as "subscription in progress"), waiting until the identifier is changed to flag_e2node_sub_state= = SUBFIN (the Flag subscription status is identified as "no subscription in progress"), and the party can continue to execute the next step; if flag_e2 node_sub_state= SUBFIN (the status of the characterization subscription is identified as "no ongoing subscription"), the identifier is modified to flag_e2 node_sub_state= SUBING (the status of the characterization subscription is identified as "ongoing subscription"), and the next step is performed.

Step 403, query the database for historical successful subscription records (Action 1-Action 4), the records are as follows ：Action1：E2Node1,Exe_Granularity_Period＝T,Granularity Period＝T,xApp2;Action2：No Found;Action3：E2Node2,Exe_Granularity_Period＝4T,Granularity Period＝4T,xApp3;Action4：No Found.

In contrast, according to the de-duplication strategy corresponding to the triggering event of the periodic timer, subscription and merging are carried out on the historical successful subscription information with repetition, and the specific operation is as follows:

action1: the acquisition period of the subscription is an integral multiple (2 times) of the actual acquisition period of the history successful subscription, determining that the subscription of the Action1 is repeated, executing the subscription combination, and marking the subscription result of the Action1 as SUCCESS;

Action2: unsubscribe is repeated, and subscription merging is not required to be executed;

Action3: the actual collection period of the historical successful subscription is an integer multiple (2 times) of the collection period of the current subscription, then it is determined that the subscription of the Action3 is repeated, subscription modification information needs to be sent to the E2Node2 first, the subscription period of the Action3 is modified to be a collection period Granularity Period =2T of the current subscription (step 404), then subscription merging is executed, and the subscription result is marked as SUCCESS;

action4: unsubscribe is repeated, and subscription merging is not required to be performed.

In steps 405-410, after subscription merging is completed, xAppSubMng sends subscription request related information to E2Node1 and E2Node2 through E2Termination, specifically sending Action2 instance information to E2Node1 (e.g. subscription initiator is xApp, acquisition period is Granularity Period =2t), and sending Action4 instance information to E2Node2 (e.g. subscription initiator is xApp1, acquisition period is Granularity Period =2t). Thus, the E2Node1 and the E2Node2 respond to the received current subscription information, and return a subscription request response message (such as subscription success information for an Action2 instance and subscription success information for an Action4 instance), so that xAppSubMng updates historical successful subscription information in the DataBase after receiving an E2Termination (E2T is shown in fig. 5) forwarding the subscription request response messages from the E2Node1 and the E2Node2 (step 411), and changes the value of the identifier of the "E2Node subscription status" to flag_e2_sub_state= = SUBFIN (the subscription status is marked as "no subscription in progress", step 412). 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,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。

In step 413, xappsubmng sends a subscription request response message to xApp, 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 de-duplicating current subscription information and historical subscription information corresponding to the subscription nodes related to the subscription event based on the de-duplication policy, further includes:

In this embodiment, the subscription event trigger type includes a network interface message trigger event, such as E2SM-NI, i.e. 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, and keeping the subscription event and related information in an Action instance list of the subscription node without de-duplication. If at least one of the call flow identification 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, and no duplication removal is needed. If the subscription event, the call flow identifier and the interface type are the same, but the directions of the interface messages are 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 no duplication is 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 (for example, the first interface information transmission direction is "IN & OUT", and the second interface information transmission direction is "OUT"), the subscription event IN the "OUT" direction is considered to be repeated, and the duplication is needed, while the subscription event IN the "IN" direction is not repeated, and duplication 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 contained IN the second interface information transmission direction (if the first interface information transmission direction is "IN", and the second interface information transmission direction is "IN & OUT"), determining that the subscription event is subscribed and repeated, and needing to remove duplication.

Fig. 6 is a flow chart of a subscription merging method for network interface message triggering events according to an exemplary embodiment of the present application, IN which xApp1 subscribes E2Node1 and E2Node2 to information acquisition events 1 to Action4 triggered by network interface messages (i.e. interfaces of Action1 to Action4 are INTF _a, intf_b, intf_c, intf_d, respectively, and transmission directions of interface messages are IN, IN & Out, out) through RICPlatForm. Specifically, xAppSubMng (i.e. xAppSubscriptionManagement) 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 Action4.

Step 502, checking the identifier values of "E2Node subscription status" of E2Node1 and E2Node2, if flag_e2node_sub_state= SUBING is detected, waiting until the identifier is changed to flag_e2node_sub_state= SUBFIN, and the method can continue to execute the next step; if flag_e2 node_sub_state= SUBFIN is detected, the identifier is modified to flag_e2 node_sub_state= SUBING and the next step is performed.

Step 503, query the database for historical successful subscription records (Action 1-Action 4), which are as follows ：Action1：E2Node1,Call Process＝m,INTF_a,IN,xApp2;Action2：E2Node1,Call Process＝m,INTF_b,IN,xApp2;Action3：E2Node2,Call Process＝m,INTF_c,IN,xApp2;Action4：No Found.

Comparing the repeated historical successful subscription information according to the de-duplication strategy corresponding to the triggering event of the network interface message, and subscribing and merging the repeated historical successful subscription information, wherein the specific operation is as follows:

Action1: the current subscription information is completely the same as the Action1, E2Node1, call process=m, interface identifier INTF _a and interface message transmission direction "IN" IN the history successful subscription record, and then the repetition of the subscription of the Action1 is determined, the subscription combination is executed, and the subscription result of the Action1 is identified as SUCCESS;

Action2: the current subscription information is the same as Action2, E2Node1, call process=m and interface identifier INTF _b IN the history successful subscription record, but the subscription repetition exists when the interface message transmission is the same IN the 'IN' direction, the subscription repetition does not exist IN the 'OUT' direction, the subscription combination is executed on the subscription event IN the 'IN' direction, and the subscription event IN the 'OUT' direction does not need to execute the subscription combination;

Action3: 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 directions of the interface messages are completely different, and if the fact that the Action3 is not subscribed and repeated is confirmed, subscription combination is not needed to be executed;

In steps 505-509, after subscription combining is completed, xAppSubMng sends subscription request related information to E2Node1 and E2Node2 through E2Termination, specifically, sends Action2 instance information to E2Node1 (e.g., subscription initiator is xApp, interface is INTF _b, message flow is CallProcess =m, message direction is "OUT"), sends Action3 instance information to E2Node2 (e.g., subscription initiator is xApp1, interface is INTF _c, message flow is CallProcess =m, message direction is "OUT") and Action4 instance information (e.g., subscription initiator is xApp, interface is INTF _d, message flow is CallProcess =m, message direction is "OUT"). Thus, the E2Node1 and the E2Node2 respond to the received current subscription information, and return a subscription request response message (such as subscription success information for an Action2 instance, subscription success information for an Action3 instance, and subscription success information for an Action4 instance), so that xAppSubMng updates historical successful subscription information in the DataBase (step 510) after receiving an E2Termination (shown as E2T in fig. 6) to forward the subscription request response messages from the E2Node1 and the E2Node2, and changes the values of the "E2Node subscription status" identifiers of the E2Node1 and the E2Node2 to flag_e2_sub_state= = SUBFIN (the subscription status is marked as "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。

in step 512, the xappsubmng sends a subscription request response message to xApp, specifically:

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

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

In some embodiments, the subscription event trigger type includes a measurement alignment trigger event; the comparing and de-duplicating current subscription information and historical subscription information corresponding to the subscription nodes related to the subscription event based on the de-duplication policy, further includes:

In this embodiment, the subscription event trigger type includes a measurement comparison trigger event, such as E2SM-RC, i.e. the E2 interface service mode is radio access network control. 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, and keeping the subscription event and related information in an Action instance list of the subscription node without de-duplication. If the current subscription information is consistent with the measurement threshold value and the measurement reporting condition (such as equal to/greater than/less than/greater than/equal to/less than/equal to) in the historical subscription information in the same subscription event in the subscription node, determining that the subscription event is repeatedly transmitted, and removing the repeated subscription event and related information from an Action instance list of the subscription node. If the same subscription event in the subscription node is inconsistent with at least one of the measurement threshold value and the measurement reporting condition (such as equal to/greater than/less than/greater than/equal to/less than/equal to) in the current subscription information and the historical subscription information, the subscription event is considered to be unsubscribed and repeated, and no duplication is needed.

Fig. 7 is a flowchart of a subscription merging method for measurement alignment triggering events according to an exemplary embodiment of the present application, in which xApp1 subscribes E2Node1 and E2Node2 to information acquisition events Action1 to Action4 triggered by measurement values exceeding a threshold (i.e. the measurement items are TestItm _a, testitm_b, testitm_c, testitm_d, respectively) and exceeding the threshold conditions are > th_a, > =th_b, < th_c, <=th_d, respectively) through RICPlatForm. Specifically, xAppSubMng (i.e. xAppSubscriptionManagement) 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 Action4.

Step 602, checking the identifier values of "E2Node subscription status" of E2Node1 and E2Node2, if flag_e2node_sub_state= SUBING is detected, waiting until the identifier is changed to flag_e2node_sub_state= SUBFIN, and the method can continue to execute the next step; if flag_e2 node_sub_state= SUBFIN is detected, the identifier is modified to flag_e2 node_sub_state= SUBING and the next step is performed.

Step 603, query the database for history successful subscription records (Action 1-Action 4), the records are as follows: action1: e2node1, testItm _a > th_a, xApp2; action2: no Found; action3: no Found; action4: no Found.

Comparing the repeated historical successful subscription information according to the de-duplication strategy corresponding to the measurement comparison triggering event, and carrying out subscription combination, wherein the specific operation is as follows:

Action1: the current subscription information is completely the same as the Action1 and E2Node1, the measurement item TestItem _a, the measurement threshold TH_a and the measurement threshold direction ">" (namely the comparison result of the measurement item and the measurement threshold) in the history successful subscription record, the repetition of the subscription of the Action1 is determined, the subscription combination is executed, and the subscription result of the Action1 is marked as SUCCESS;

action3: unsubscribe is repeated, and subscription merging is not required to be executed;

In steps 605-609, after subscription merging is completed, xAppSubMng sends subscription request related information to E2Node1 and E2Node2 through E2Termination, specifically sending Action2 instance information to E2Node1 (e.g. subscription initiator is xApp1, trigger condition is TestItm _b > =th_b), sending Action3 instance information to E2Node2 (e.g. subscription initiator is xApp1, trigger condition is TestItm _c < th_c), and Action4 instance information (e.g. subscription initiator is xApp1, trigger condition is TestItm _d < =th_d). Thus, the E2Node1 and the E2Node2 respond to the received current subscription information, and return a subscription request response message (such as subscription success information for an Action2 instance, subscription success information for an Action3 instance, and subscription success information for an Action4 instance), so that xAppSubMng updates historical successful subscription information in the DataBase (step 610) after receiving an E2Termination (E2T is shown in fig. 7) to forward the subscription request response messages from the E2Node1 and the E2Node2, and changes the values of the "E2Node subscription status" identifiers of the E2Node1 and the E2Node2 to flag_e2_sub_state= = SUBFIN (step 611). 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,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 reply message to xApp, specifically:

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

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

Fig. 8 is a schematic structural diagram of a subscription merging device according to an embodiment of the present application, where the subscription merging device 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 selection module 702, configured to determine a deduplication policy of the subscription event based on a subscription event trigger type in the current subscription information;

The subscription merging module 703 is configured to compare and remove duplication from current subscription information and historical subscription information corresponding to a subscription node related to the subscription event based on the duplication removal policy, to obtain subscription operation information, where the subscription operation information is used to instruct to initiate a request of a corresponding event to be subscribed to a target subscription node;

And 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 merge module 703 includes:

The de-duplication unit is used for removing repeated subscription events and related information from the current subscription information and identifying the repeated subscription events as successful subscription events if the subscription events corresponding to the current subscription information and the historical subscription information are determined to be repeated based on the de-duplication strategy;

and the reorganization unit is used for reorganizing the current subscription information after the de-duplication operation into subscription operation information for representing the target subscription node and the corresponding event to be subscribed.

In some embodiments, the request response module 704 includes:

A target subscription node response unit, configured to initiate a request for a corresponding 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 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 merge module 703 includes:

The first deduplication strategy unrepeated judging unit is used for determining that the subscription event is unrepeated if the current subscription information of each subscription node has a subscription event inconsistent with the historical subscription information or the same subscription event in the current subscription information and the historical subscription information is aimed at in the subscription node, and the first acquisition period in the current subscription information and the second acquisition period in the historical subscription information are in a non-multiple relationship;

The first duplication elimination strategy duplication judgment unit is used for determining that the subscription event is duplicated if the first acquisition period and the second acquisition period are in integer multiple relation for the same subscription event in the subscription node; wherein the integer multiple relationship includes the first acquisition period being an integer multiple of the second acquisition period, and the second acquisition period being an integer multiple of the first acquisition period.

In some embodiments, the first deduplication policy repetition determination unit comprises:

And the subscription information modification unit is used for sending subscription modification information to the subscription node corresponding to the subscription event when the second acquisition period is integral multiple of the first acquisition period in the subscription node aiming at the same 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 some embodiments, the subscription merge module 703 includes:

The second deduplication strategy unrepeated judging unit is used for determining that the subscription event is unrepeated when the transmission direction of the first interface information in the current subscription information is completely different from the transmission direction of the second interface information in the historical subscription information for each subscription node, or at least one of the call flow identification and the interface type in the current subscription information and the historical subscription information is not consistent for the same subscription event in the subscription node, or the call flow identification and the interface type are consistent for the same subscription event;

The second duplication eliminating strategy duplication judging unit is used for determining duplication of the subscription event when the call flow identifier and the interface type are consistent for the same subscription event, but the first interface information transmission direction is completely contained in the second interface information transmission direction;

And the second de-duplication policy processing unit is used for determining that the contained part is subscribed and duplicated and determining that the non-contained part is not subscribed and duplicated when the call flow identification and the interface type are consistent for the same subscription event but the first interface information transmission direction contains the second interface information transmission direction.

In some embodiments, the subscription merge module 703 includes:

the third deduplication strategy unrepeated judging unit is used for determining that the subscription event is unrepeated when the current subscription information of each subscription node has the subscription event inconsistent with the historical subscription information;

the third duplication eliminating strategy duplication judging unit is used for determining that the subscription event is duplicated when the measured value, the measurement threshold value and the comparison result determined by the measured value and the measurement threshold value in the current subscription information and the historical subscription information are consistent for the same subscription event in the subscription node; otherwise, determining that the subscription event is not repeated.

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

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

the trigger de-duplication unit is used for changing the first state identifier into the second state identifier when the subscription state identifier is the first state identifier, so that the current subscription information and the historical subscription information are compared by triggering and de-duplication;

And the waiting unit is used for waiting for changing the second state identifier into the first state identifier when the subscription state identifier is the second state identifier.

In some embodiments, the request response module 704 further includes:

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

And the identification adjustment unit is used for adjusting the subscription identification state of the subscription node related to the subscription event to the first state identification.

The device of the embodiment of the present application may perform the method provided by the embodiment of the present application, and its implementation principle is similar, and actions performed by each module in the device of the embodiment of the present application correspond to steps in the method of the embodiment of the present application, and detailed functional descriptions of each module of the device may be referred to the descriptions in the corresponding methods shown in the foregoing, which are not repeated herein.

The embodiment of the application provides an electronic device, which comprises a memory, a processor and a computer program stored on the memory, wherein the processor executes the computer program to realize the steps of a subscription merging method, and compared with the related technology, the method can realize the following steps: the current subscription information and the historical subscription information are combined in a subscription manner, so that the technical problem that xApp subscribed contents in the prior art are repeated 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 includes: a processor 801 and a memory 803. The processor 801 is coupled to a memory 803, such as via a bus 802. Optionally, the electronic device 800 may further comprise 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, etc. It should be noted that, in practical applications, the transceiver 804 is not limited to one, 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 ), general purpose Processor, DSP (DIGITAL SIGNAL Processor, data signal Processor), ASIC (Application SPECIFIC INTEGRATED Circuit), FPGA (Field Programmable GATE ARRAY ) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules and circuits described in connection with this disclosure. The processor 801 may also be a combination of computing functions, e.g., including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

Bus 802 may include a path to transfer information between the aforementioned components. Bus 802 may be a PCI (PERIPHERAL COMPONENT INTERCONNECT, peripheral component interconnect standard) bus or an EISA (Extended Industry Standard Architecture ) bus, or the like. Bus 802 may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 9, but not only one bus or one type of bus.

The Memory 803 may be, without limitation, ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, RAM (Random Access Memory ) or other type of dynamic storage device that can store information and instructions, EEPROM (ELECTRICALLY ERASABLE PROGRAMMABLE READ ONLY MEMORY ), CD-ROM (Compact Disc Read Only Memory, compact disc Read Only Memory) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, blu-ray discs, etc.), magnetic disk storage media, 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.

The memory 803 is used to store a computer program for executing an embodiment of the present application and is controlled to be executed by the processor 801. The processor 801 is arranged 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 having a computer program stored thereon, which when executed by a processor, implements the steps of the foregoing method embodiments and corresponding content.

The embodiment of the application also provides a computer program product, which comprises a computer program, wherein the computer program can realize the steps and corresponding contents of the embodiment of the method when being executed by a processor.

The foregoing is merely an optional implementation manner of some of the implementation scenarios of the present application, and it should be noted that, for those skilled in the art, other similar implementation manners based on the technical ideas of the present application are adopted without departing from the technical ideas of the scheme of the present application, and the implementation manner is also within the protection scope of the embodiments of the present application.

Claims

1. A subscription consolidation method, comprising:

determining a de-duplication strategy of the subscription event based on a subscription event trigger type in the current subscription information, wherein the subscription event trigger type comprises a periodic timer trigger event;

Based on the deduplication policy, comparing and deduplicating current subscription information corresponding to the subscription node related to the subscription event with historical subscription information to obtain subscription operation information, wherein the subscription operation information comprises: if the duplication eliminating strategy is based on that the current subscription information and the historical subscription information respectively correspond to the subscription events, duplicated subscription events and related information are removed from the current subscription information, and duplicated subscription events are identified as subscription success events; recombining the current subscription information after the de-duplication operation into subscription operation information for representing a target subscription node and corresponding events to be subscribed, wherein the subscription operation information is used for indicating a request for initiating the corresponding events to be subscribed to the target subscription node;

Based on the subscription response information of the target subscription node for the event to be subscribed, subscription response information is returned to the client so as to respond to the subscription request;

The comparing and de-duplicating current subscription information and historical subscription information corresponding to the subscription nodes related to the subscription event based on the de-duplication policy, further includes:

For each subscription node, if the same subscription event in the current subscription information and the historical subscription information is aimed at in the subscription node, a first collection period in the current subscription information and a second collection period in the historical subscription information are in a non-multiple relation, and determining that the subscription event is not repeated; or alternatively, the first and second heat exchangers may be,

2. The method according to claim 1, 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:

3. The method of claim 1, wherein the comparing and de-duplicating current subscription information and historical subscription information corresponding to the subscription nodes related to the subscription event based on the de-duplication policy, further comprises:

for each subscription node, if the current subscription information of the subscription node has the subscription event inconsistent with the historical subscription information, determining that the subscription event is not repeated.

4. A method according to claim 3, characterized in that the method further comprises:

5. The method of claim 1, wherein the subscription event trigger type comprises a network interface message trigger event; the comparing and de-duplicating current subscription information and historical subscription information corresponding to the subscription nodes related to the subscription event based on the de-duplication policy, further includes:

6. The method of claim 1, wherein the subscription event trigger type comprises a measurement alignment trigger event; the comparing and de-duplicating current subscription information and historical subscription information corresponding to the subscription nodes related to the subscription event based on the de-duplication policy, further includes:

7. The method of claim 1, wherein the comparing and de-duplicating current subscription information and historical subscription information corresponding to the subscription nodes related to the subscription event based on the de-duplication policy further comprises:

8. The method of claim 7, 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 to, in response to the subscription request, further comprises:

9. A subscription consolidation apparatus, comprising:

the policy selection module is used for determining a de-duplication policy of the subscription event based on a subscription event trigger type in the current subscription information, wherein the subscription event trigger type comprises a periodic timer trigger event;

The subscription merging module is configured to compare and remove duplication from current subscription information and historical subscription information corresponding to a subscription node related to the subscription event based on the duplication removal policy, to obtain subscription operation information, and includes: if the duplication eliminating strategy is based on that the current subscription information and the historical subscription information respectively correspond to the subscription events, duplicated subscription events and related information are removed from the current subscription information, and duplicated subscription events are identified as subscription success events; recombining the current subscription information after the de-duplication operation into subscription operation information for representing a target subscription node and corresponding events to be subscribed, wherein the subscription operation information is used for indicating a request for initiating the corresponding events to be subscribed to the target subscription node;

If the first acquisition period and the second acquisition period are in an integer 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;

10. 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 carry out the steps of the method according to any one of claims 1-8.

11. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method according to any of claims 1-8.

12. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method according to any of claims 1-8.