Invitation object information matching method and device, computer device, and storage medium

Abstract

The application relates to an invitation object information matching method and device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: acquiring an invitation success prompt message, extracting an invitation object identifier and an invitation business processing node identifier carried in the invitation success prompt message; generating invitation object note information based on a preset note generation rule and according to the invitation object identifier; generating an add note information request based on the invitation business processing node identifier and the invitation object note information, and pushing; acquiring a note addition completion prompt message, acquiring an already invited object set corresponding to the invitation business processing node identifier; finding a local storage identifier corresponding to an invitation object in the already invited object set according to the invitation object note information; and associating and storing the local storage identifier of the invitation object with the invitation object identifier, thereby completing the matching of valid multi-terminal invitation object information.

Description

Technical Field

[0001] This application relates to the field of computer processing technology, and in particular to a method, apparatus, computer device, storage medium, and computer program product for matching invitation object information. Background Technology

[0002] With the development of computer technology and the advancement of communication equipment, communication between people has become more convenient, and businesses can also communicate directly with invited parties based on communication software.

[0003] Currently, businesses use various communication channels to deliver messages to potential recipients, such as SMS, email, and instant messaging software. In scenarios where content is sent directly, each message is sent to only one recipient. However, this method is inefficient when dealing with a large number of recipients. To address this, some technologies have proposed using mass messaging to achieve efficient message forwarding.

[0004] However, mass messaging can generally only be implemented on the same instant messaging software. Since the invitation recipient information is stored differently on different processing terminals, it's impossible to achieve batch message forwarding across different processing terminals. Therefore, there is an urgent need to match invitation recipient information across multiple terminals so that, upon successful matching, messages can be sent to a large number of recipients based on the invitation recipient list. Summary of the Invention

[0005] Therefore, it is necessary to provide an effective method, apparatus, computer device, computer-readable storage medium, and computer program product for matching invitation information across multiple terminals, addressing the technical problem of ineffective matching of invitation information.

[0006] Firstly, this application provides a method for matching information of invitees. The method includes:

[0007] Get the invitation success message and extract the invitation target identifier and invitation business processing node identifier carried in the invitation success message;

[0008] Based on the pre-set annotation generation rules and according to the invitation object identifier, generate invitation object remarks information;

[0009] Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to add remarks information and push it;

[0010] Get the notification message indicating that the notes have been added, and get the set of invited objects corresponding to the invitation business processing node identifier;

[0011] Based on the remarks of the invited objects, find the local storage identifier corresponding to the invited object in the set of invited objects;

[0012] The local storage identifier of the invitee is associated with the invitee identifier and stored together.

[0013] In one embodiment, generating invitation object remarks based on pre-set remarks generation rules and according to the invitation object identifier includes: generating invitation object remarks based on pre-set remarks generation rules and according to the invitation object identifier and the invitation business processing node identifier.

[0014] In one embodiment, after associating the local storage identifier of the invitee with the invitee identifier, the method further includes: generating a request to delete the remarks based on the invitee business processing node identifier and the invitee remarks information, and pushing it; obtaining a reminder message indicating that the remarks have been deleted, and pushing a matching completion reminder message.

[0015] In one embodiment, the method further includes: storing the local storage identifier of the associated invitation object and the invitation object identifier in a matching database; or, adding a matching identifier to the local storage identifier of the associated invitation object and the invitation object identifier.

[0016] In one embodiment, the method further includes: periodically acquiring the invitation business processing node and the set of invited objects corresponding to the invitation business processing node; querying the set of invited objects to determine the identifiers of unmatched invited objects in the set of invited objects; and proceeding to the step of generating invitation object remarks information based on pre-set note generation rules and according to the invitation object identifiers.

[0017] In one embodiment, associating the local storage identifier of the invitee with the invitee identifier includes: associating the local storage identifier of the invitee with the invitee identifier in the matching database; based on this, querying the set of invited objects to determine the unmatched invitee identifiers in the set of invited objects includes: querying the set of invited objects according to the matching database to determine the invitee identifiers in the set of invited objects that were not found in the matching database, thereby obtaining the unmatched invitee identifiers.

[0018] In one embodiment, associating the local storage identifier of the invitee with the invitee identifier includes: adding a matching identifier to the associated local storage identifier of the invitee and the invitee identifier; based on this, querying the set of invited objects to determine the unmatched invitee identifier in the set of invited objects includes: querying the matching identifier of the invitee identifier according to the invitee identifier in the set of invited objects; when the matching identifier of the invitee identifier does not exist, the invitee identifier is determined to be an unmatched invitee identifier.

[0019] Secondly, this application also provides an invitation recipient information matching device. The device includes:

[0020] The acquisition module is used to acquire invitation success notification messages and extract the invitation object identifier and invitation business processing node identifier carried in the invitation success notification messages;

[0021] The generation module is used to generate invitation object remarks information based on pre-set annotation generation rules and the invitation object identifier;

[0022] The push module is used to generate and push a request to add remarks based on the invitation business processing node identifier and the remarks information of the invitation object.

[0023] The acquisition module is also used to acquire the notification message indicating that the note addition is complete, and to acquire the set of invited objects corresponding to the invitation business processing node identifier;

[0024] The search module is used to find the local storage identifier corresponding to the invited object in the set of invited objects based on the invited object's remarks information;

[0025] The association module is used to associate the local storage identifier of the invitee with the invitee identifier.

[0026] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0027] Get the invitation success message and extract the invitation target identifier and invitation business processing node identifier carried in the invitation success message;

[0028] Based on the pre-set annotation generation rules and according to the invitation object identifier, generate invitation object remarks information;

[0029] Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to add remarks information and push it;

[0030] Get the notification message indicating that the notes have been added, and get the set of invited objects corresponding to the invitation business processing node identifier;

[0031] Based on the remarks of the invited objects, find the local storage identifier corresponding to the invited object in the set of invited objects;

[0032] The local storage identifier of the invitee is associated with the invitee identifier and stored together.

[0033] Fourthly, this application also provides a computer-readable storage medium. This computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0034] Get the invitation success message and extract the invitation target identifier and invitation business processing node identifier carried in the invitation success message;

[0035] Based on the pre-set annotation generation rules and according to the invitation object identifier, generate invitation object remarks information;

[0036] Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to add remarks information and push it;

[0037] Get the notification message indicating that the notes have been added, and get the set of invited objects corresponding to the invitation business processing node identifier;

[0038] Based on the remarks of the invited objects, find the local storage identifier corresponding to the invited object in the set of invited objects;

[0039] The local storage identifier of the invitee is associated with the invitee identifier and stored together.

[0040] Fifthly, this application also provides a computer program product. This computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0041] Get the invitation success message and extract the invitation target identifier and invitation business processing node identifier carried in the invitation success message;

[0042] Based on the pre-set annotation generation rules and according to the invitation object identifier, generate invitation object remarks information;

[0043] Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to add remarks information and push it;

[0044] Get the notification message indicating that the notes have been added, and get the set of invited objects corresponding to the invitation business processing node identifier;

[0045] Based on the remarks of the invited objects, find the local storage identifier corresponding to the invited object in the set of invited objects;

[0046] The local storage identifier of the invitee is associated with the invitee identifier and stored together.

[0047] The aforementioned method, apparatus, computer equipment, storage medium, and computer program product for matching invitation object information includes: obtaining an invitation success notification message; extracting the invitation object identifier and the invitation business processing node identifier carried in the invitation success notification message; generating invitation object remark information based on pre-set remark generation rules and the invitation object identifier; generating and pushing an add remark information request based on the invitation business processing node identifier and the invitation object remark information; obtaining a remark addition completion notification message; obtaining the set of invited objects corresponding to the invitation business processing node identifier; searching for the local storage identifier corresponding to the invitation object in the set of invited objects based on the invitation object remark information; and associating and storing the local storage identifier of the invitation object with the invitation object identifier. When an invitation is successfully made, the entire solution adds a note to the invitee that is related to the invitee's identifier. After the note is made, the system searches for the local storage identifier of the invitee that is marked with the note from the locally stored set of invited invitees. Then, the local storage identifier of the invitee is associated with the invitee's identifier and stored together, thus completing the effective matching of invitee information across multiple terminals. Attached Figure Description

[0048] To more clearly illustrate the technical solutions in the embodiments of this application or the conventional technology, the drawings used in the description of the embodiments or the conventional technology will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0049] Figure 1 This is an application environment diagram of the invitation object information matching method in one embodiment;

[0050] Figure 2 This is a flowchart illustrating an invitation object information matching method in one embodiment;

[0051] Figure 3 This is a flowchart illustrating the invitation object information matching method in another embodiment;

[0052] Figure 4 This is a flowchart illustrating the invitation object information matching method in yet another embodiment;

[0053] Figure 5 This is a structural block diagram of an invitation object information matching device in one embodiment;

[0054] Figure 6 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0055] It should be noted that the user information (including but not limited to user device information, user personal information, invitation target identifier, invitation business processing node identifier, and the set of invited targets corresponding to the invitation business processing node identifier) ​​and data (including but not limited to data used for analysis, stored data, and displayed data) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0056] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0057] Bulk messaging generally only works on the same instant messaging software. Because the invitation information for instant messaging software is stored differently on different processing terminals, it's impossible to achieve batch message forwarding across different processing terminals. For example, the user identifier stored in the WeChat Work PC (Personal Computer) client is inconsistent with the userid officially defined by WeChat Work, thus preventing features like PRA (Robotic Process Automation), PRA bulk messaging, aggregated chat, and posting to Moments. Aggregated chat refers to a server-provided webpage that allows users to chat with multiple WeChat Work accounts and multiple friends simultaneously within a single page.

[0058] It is evident that there is an urgent need to match the invitation information from multiple platforms so that, once a match is successful, information can be sent to a large number of invitation recipients based on the invitation list.

[0059] The invitation target information matching method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated on server 104 or placed on the cloud or other network servers. When a user responds to an invitation request on terminal 102, agreeing to add the invitation processing node as a friend, a successful invitation message is pushed. Server 104 receives the successful invitation message, extracts the invitation object identifier and the invitation processing node identifier carried in the message; generates invitation object remarks based on pre-defined note generation rules and the invitation object identifier; generates an add note information request based on the invitation processing node identifier and the invitation object remarks information, and pushes it; receives a note addition completion notification message, obtains the set of invited objects corresponding to the invitation processing node identifier; finds the local storage identifier corresponding to the invited object in the set of invited objects based on the invitation object remarks information; and associates and stores the local storage identifier of the invited object with the invitation object identifier. The terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, and smart in-vehicle systems. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted devices. The server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0060] In one embodiment, such as Figure 2 As shown, a method for matching invitation recipient information is provided, which can be applied to... Figure 1 Taking the server in the example, the following steps are included:

[0061] Step 202: Obtain the invitation success message and extract the invitation object identifier and invitation business processing node identifier carried in the invitation success message.

[0062] In this context, the "invitation target" refers to the user to be invited, which can be an employee or user of the company. The "invitation target identifier" is a unique identifier for the invitee, allowing direct identification of the unique invitee. For example, if the invitee is a user of the company, the identifier is the user identifier, which identifies the unique user. The "invitation target business processing node" refers to the management personnel specifically responsible for invitation processing, such as customer service representatives or account managers responsible for communicating with users. The invitation success message carries both the invitation target identifier and the invitation business processing node identifier. In this embodiment, the execution entity is the enterprise system's server. The invitation target identifier is a unique identifier generated by the instant messaging application server for the invitee, such as a user's userid in WeChat Work. The userid is obtained through the official WeChat Work interface and is used for user identification and authentication when interacting with the official WeChat Work API. The instant messaging application can be any application software capable of real-time communication, such as WeChat Work, and the instant messaging application server is the server that deploys the instant messaging service.

[0063] Specifically, when the invitee agrees to the invitation request from the invitation service processing node on the terminal operation interface, the terminal generates and pushes an agreement notification message to the instant messaging application server. The instant messaging application server then obtains the invitee's identifier and the invitation service processing node identifier based on the agreement notification message, adds the invitee's identifier and the invitation service processing node identifier as friends, generates an invitation success notification message based on the invitee's identifier and the invitation service processing node identifier, and sends the invitation success notification message to the server. When the server receives the invitation success notification message, it extracts the invitee's identifier and the invitation service processing node identifier carried in the invitation success notification message.

[0064] Furthermore, when the server uses Windows hook technology to obtain the invitation success message, it extracts the invitation object identifier and the invitation business processing node identifier carried in the message. Hook is a system mechanism provided by Windows to replace the "interrupt" in DOS. After hooking a specific system event, once the hooked event occurs, the program that hooked the event will receive a system notification, allowing it to respond to the event immediately.

[0065] Step 204: Generate invitation object remarks information based on the pre-set remarks generation rules and the invitation object identifier.

[0066] The pre-set annotation generation rule is a rule generated on the server to add annotations to the local information of the invitee. The pre-set annotation generation rule includes an invitee identifier and an annotation identifier. The annotation identifier in this embodiment differs from the annotation identifier added to friends in current instant messaging applications.

[0067] Specifically, the server obtains the pre-installed annotation generation rules from local storage, then generates invitation object annotation information based on the invitation object identifier, and stores the invitation object annotation information in association with the invitation object identifier.

[0068] Step 206: Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to add remarks information and push it.

[0069] Specifically, the server generates a request to add notes based on the invitation business processing node identifier and the notes information of the invitation object, and pushes it to the instant messaging application server. This allows the instant messaging application server to add notes to the invitation objects in the address book of the invitation business processing node according to the request. Once the notes are successfully added, a note addition completion prompt message is generated and pushed to the server.

[0070] Step 208: Obtain the notification message indicating that the remarks have been added, and obtain the set of invited objects corresponding to the invitation business processing node identifier.

[0071] Specifically, the server listens for and responds to the notification message sent by the instant messaging application server indicating that the addition of notes is complete. Then, it extracts the invitation business processing node identifier carried in the notification message, calls the hook interface, queries the locally stored invitation business processing node identifier for invited objects, and generates a set of invited objects.

[0072] Step 210: Based on the remarks information of the invited object, find the local storage identifier corresponding to the invited object in the set of invited objects.

[0073] Specifically, the server obtains the remarks information of the set of invited objects corresponding to the invitation business processing node identifier, and then calls the hook interface in the local data to find the local storage identifier of the invitation object with the remarks information of the invitation object.

[0074] Step 212: Associate the local storage identifier of the invited object with the identifier of the invited object.

[0075] Specifically, the server associates the local storage identifier of the invited object with the identifier of the invited object.

[0076] In the above-described method for matching invitation object information, the following steps are taken: A successful invitation notification message is obtained; the invitation object identifier and the invitation business processing node identifier carried in the message are extracted; invitation object note information is generated based on pre-set note generation rules and the invitation object identifier; an add note information request is generated and pushed based on the invitation business processing node identifier and the invitation object note information; a note addition completion notification message is obtained; the set of invited objects corresponding to the invitation business processing node identifier is obtained; the local storage identifier corresponding to the invited object in the set of invited objects is searched based on the invitation object note information; and the local storage identifier of the invited object is associated with the invitation object identifier. In this entire scheme, upon successful invitation, invitation object note information related to the invitation object identifier is added to the invited object. After the note is completed, the local storage identifier of the invited object with the note information is searched from the locally stored set of invited objects, and then the local storage identifier of the invited object is associated with the invitation object identifier, thus completing effective multi-terminal invitation object information matching.

[0077] In an optional embodiment, generating invitation object remarks based on pre-set remarks generation rules and according to the invitation object identifier includes: generating invitation object remarks based on pre-set remarks generation rules and according to the invitation object identifier and the invitation business processing node identifier.

[0078] The pre-set annotation generation rules include the invitation object identifier, the invitation business processing node identifier, and the remarks identifier.

[0079] Specifically, the server obtains the pre-installed annotation generation rules from local storage, then generates invitation object annotation information based on the invitation object identifier and the invitation business processing node identifier, and stores the invitation object annotation information in association with the invitation object identifier.

[0080] In this embodiment, invitation object notes are generated using the invitation object identifier and the invitation business processing node identifier. Subsequently, these identifiers allow for more efficient local location of the invitation object and retrieval of its local storage identifier, improving the efficiency of matching the local storage identifier of the invitation object. Compared to matching based on the invitation object's nickname and avatar, this method improves matching accuracy.

[0081] In an optional embodiment, such as Figure 3 As shown, after associating and storing the local storage identifier of the invitation object with the invitation object identifier, it also includes:

[0082] Step 302: Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to delete remarks information and push it.

[0083] Specifically, the server generates a request to delete notes based on the invitation business processing node identifier and the notes information of the invitation object, and pushes it to the instant messaging application server. This allows the instant messaging application server to delete the notes of the invitation object in the address book of the invitation business processing node based on the request to delete the notes. When the notes are successfully deleted, a note deletion completion prompt message is generated and pushed to the server.

[0084] Step 304: Obtain the notification message indicating that the deletion of the remarks is complete, and push the notification message indicating that the matching is complete.

[0085] Specifically, the server listens for and responds to the note deletion completion notification message sent by the instant messaging application server, and then generates a matching completion notification message for the enterprise administrator.

[0086] In this embodiment, the invitation object's local storage identifier is associated with the invitation object's identifier and then the invitation object's note information is deleted as soon as possible, so that the user is unaware of this process.

[0087] In an optional embodiment, the method further includes: storing the local storage identifier of the associated invitation object and the invitation object identifier in a matching database; or, adding a matching identifier to the local storage identifier of the associated invitation object and the invitation object identifier.

[0088] Specifically, after the server associates and stores the local storage identifier of the invitee with the invitee identifier, it can also simultaneously store the associated local storage identifier and invitee identifier in the matching database. Alternatively, a matching identifier can be added to the associated local storage identifier and invitee identifier to improve the efficiency of querying invitee matching information.

[0089] In an optional embodiment, the above method further includes: periodically acquiring the invitation business processing node and the set of invited objects corresponding to the invitation business processing node; querying the set of invited objects to determine the identifiers of unmatched invited objects in the set of invited objects; and proceeding to the step of generating invitation object remarks information based on pre-set annotation generation rules and according to the invitation object identifiers.

[0090] Specifically, sometimes instant messaging application servers may fail to return a successful invitation message after a friend is successfully added. As a result, the server may not receive the successful invitation message. Therefore, the server can be set up to perform a scheduled matching task to periodically retrieve all invitation business processing nodes in the enterprise. Based on the invitation business processing node identifier, the server can retrieve the set of invited objects for each invitation business processing node and then sequentially determine whether there are any unmatched invited objects in the set of invited objects for each invitation business processing node. When an unmatched invited object is found, the identifier of the unmatched invited object in the invited object set is determined. Then, this unmatched invited object identifier is matched and identified as the invited object identifier. Based on pre-set annotation generation rules and the invited object identifier, invited object annotation information is generated. Based on the invited business processing node identifier and the invited object annotation information, an add annotation information request is generated and pushed. A annotation addition completion notification message is obtained, and the invited object set corresponding to the invited business processing node identifier is obtained. Based on the invited object annotation information, the local storage identifier corresponding to the invited object in the invited object set is found. The local storage identifier of the invited object is associated with the invited object identifier. Based on the invited business processing node identifier and the invited object annotation information, a delete annotation information request is generated, and a delete annotation completion notification message is pushed. A matching completion notification message is also pushed to improve the invited object matching success rate.

[0091] In an optional embodiment, associating the local storage identifier of the invitee with the invitee identifier includes: associating the local storage identifier of the invitee with the invitee identifier in the matching database; based on this, querying the set of invited objects to determine the unmatched invitee identifiers in the set of invited objects includes: querying the set of invited objects according to the matching database to determine the invitee identifiers in the set of invited objects that were not found in the matching database, thereby obtaining the unmatched invitee identifiers.

[0092] Specifically, after the server associates and stores the local storage identifier of the invited object with the inviter identifier, it can also simultaneously store the associated local storage identifier of the invited object and the inviter identifier in the matching database. Then, when querying whether an invited object matches, the server queries the matching database for each invited object identifier in the set of invited objects. If an invited object has matched, the matching database can retrieve the matching information of that invited object. If an invited object has not matched, the matching database cannot retrieve the matching information of that invited object, meaning that the matching information of that invited object does not exist. In this case, the server retrieves the identifier of the invited object, thus obtaining the identifier of the unmatched invited object.

[0093] In this embodiment, by storing the matched invitation objects in the matching data, the database's efficient retrieval and query capabilities can quickly find the identifiers of unmatched invitation objects, thereby improving the success rate and efficiency of invitation object matching.

[0094] In an optional embodiment, associating the local storage identifier of the invitee with the invitee identifier includes: adding a matching identifier to the associated local storage identifier of the invitee and the invitee identifier; based on this, querying the set of invited objects to determine the unmatched invitee identifier in the set of invited objects includes: querying the matching identifier of the invitee identifier according to the invitee identifier in the set of invited objects; when the matching identifier of the invitee identifier does not exist, the invitee identifier is determined to be an unmatched invitee identifier.

[0095] Specifically, the server adds a matching identifier to the local storage identifier of the associated invitation object and the invitation object identifier. Then, when querying whether the invited objects match, it queries the matching identifier of the invitation object identifier based on the invitation object identifier in the set of invited objects; when the matching identifier of the invitation object identifier exists, it indicates that the invited objects have been matched; when the matching identifier of the invitation object identifier does not exist, it is determined that the invitation object identifier is an unmatched invitation object identifier.

[0096] In this embodiment, a matching identifier is added to the already matched invitation object, which can quickly find the identifier of the unmatched invitation object, thereby improving the success rate and efficiency of the invitation object matching.

[0097] To facilitate understanding of the technical solutions provided in the embodiments of this application, such as Figure 4 As shown, the method for matching invitation recipient information provided in this application embodiment will be briefly described using the complete invitation recipient information matching process:

[0098] (1) Obtain the invitation success message and extract the invitation object identifier and invitation business processing node identifier carried in the invitation success message.

[0099] (2) Generate invitation object remarks information based on the pre-set remarks generation rules and the invitation object identifier.

[0100] (3) Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to add remarks information and push it.

[0101] (3) Obtain the notification message indicating that the note has been added, and obtain the set of invited objects corresponding to the invitation business processing node identifier.

[0102] (4) Based on the remarks of the invited object, find the local storage identifier corresponding to the invited object in the set of invited objects.

[0103] (5) Associate the local storage identifier of the invitee with the invitee identifier.

[0104] (6) Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to delete remarks information and push it; obtain the remarks deletion completion prompt message and push the matching completion prompt message.

[0105] (7) Periodically obtain the invitation business processing node and the set of invited objects corresponding to the invitation business processing node; query the set of invited objects to determine the identifier of the unmatched invited object in the set of invited objects; proceed to the step of generating invitation object remarks based on the pre-set annotation generation rules and according to the invitation object identifier.

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

[0107] Based on the same inventive concept, this application also provides an invitation object information matching device for implementing the invitation object information matching method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more of the invitation object information matching device embodiments provided below can be found in the limitations of the invitation object information matching method described above, and will not be repeated here.

[0108] In one embodiment, such as Figure 5 As shown, an invitation target information matching device is provided, including: an acquisition module 502, a generation module 504, a push module 506, a search module 508, and an association module 510, wherein:

[0109] The acquisition module 502 is used to acquire the invitation success message and extract the invitation object identifier and the invitation business processing node identifier carried in the invitation success message.

[0110] The generation module 504 is used to generate invitation object remarks information based on pre-set remarks generation rules and according to the invitation object identifier.

[0111] The push module 506 is used to generate and push a request to add remarks based on the invitation business processing node identifier and the remarks information of the invitation object.

[0112] The acquisition module 502 is also used to acquire the note addition completion prompt message and the set of invited objects corresponding to the invitation business processing node identifier.

[0113] The lookup module 508 is used to find the local storage identifier corresponding to the invited object in the set of invited objects based on the invited object's remarks information.

[0114] The association module 510 is used to associate the local storage identifier of the invitation object with the invitation object identifier.

[0115] In one embodiment, the generation module 504 is further configured to generate invitation object remarks information based on pre-set remarks generation rules and according to the invitation object identifier and the invitation business processing node identifier.

[0116] In one embodiment, the invitation object information matching device further includes a deletion module, which is used to generate a request to delete the remarks information based on the invitation business processing node identifier and the remarks information of the invitation object, and push it; obtain a reminder message for the completion of the remarks deletion, and push a reminder message for the completion of the matching.

[0117] In one embodiment, the association module 510 is further configured to store the local storage identifier of the associated invitation object and the invitation object identifier in the matching database; or, to add a matching identifier to the local storage identifier of the associated invitation object and the invitation object identifier.

[0118] In one embodiment, the invitation object information matching device further includes a timed query module, which is used to periodically obtain the invitation business processing node and the set of invited objects corresponding to the invitation business processing node; query the set of invited objects to determine the identifiers of unmatched invitation objects in the set of invited objects; and proceed to the step of generating invitation object remarks information based on pre-set note generation rules and according to the invitation object identifiers.

[0119] In one embodiment, the timed query module is further configured to associate the local storage identifier of the invited object with the invite object identifier and store it in the matching database; query the set of invited objects according to the matching database, determine the invite object identifier in the set of invited objects that are not found in the matching database, and obtain the unmatched invite object identifier.

[0120] In one embodiment, the timed query module is further configured to add a matching identifier to the local storage identifier of the associated invitation object and the invitation object identifier; query the matching identifier of the invitation object identifier based on the invitation object identifier in the set of invited objects; and determine that the invitation object identifier is an unmatched invitation object identifier when the matching identifier of the invitation object identifier does not exist.

[0121] Each module in the aforementioned invitation target information matching device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0122] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 6 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores data such as the set of invited objects and pre-set annotation generation rules. The network interface communicates with external terminals via a network connection. When executed by the processor, the computer program implements an invited object information matching method.

[0123] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0124] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0125] Get the invitation success message and extract the invitation target identifier and invitation business processing node identifier carried in the invitation success message;

[0126] Based on the pre-set annotation generation rules and according to the invitation object identifier, generate invitation object remarks information;

[0127] Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to add remarks information and push it;

[0128] Get the notification message indicating that the notes have been added, and get the set of invited objects corresponding to the invitation business processing node identifier;

[0129] Based on the remarks of the invited objects, find the local storage identifier corresponding to the invited object in the set of invited objects;

[0130] The local storage identifier of the invitee is associated with the invitee identifier and stored together.

[0131] In one embodiment, when the processor executes the computer program, it further implements the following steps: generating invitation object remark information based on pre-set remark generation rules and according to the invitation object identifier, including: generating invitation object remark information based on pre-set remark generation rules and according to the invitation object identifier and the invitation business processing node identifier.

[0132] In one embodiment, when the processor executes the computer program, it further implements the following steps: after associating and storing the local storage identifier of the invitation object with the invitation object identifier, it further includes: generating a request to delete the remarks information based on the invitation business processing node identifier and the remarks information of the invitation object, and pushing it; obtaining a reminder message indicating that the remarks have been deleted, and pushing a matching completion reminder message.

[0133] In one embodiment, when the processor executes the computer program, it further performs the following steps: storing the local storage identifier of the associated invitation object and the invitation object identifier into a matching database; or, adding a matching identifier to the local storage identifier of the associated invitation object and the invitation object identifier.

[0134] In one embodiment, when the processor executes the computer program, it further implements the following steps: periodically acquiring the invitation business processing node and the set of invited objects corresponding to the invitation business processing node; querying the set of invited objects to determine the identifier of the unmatched invited object in the set of invited objects; and proceeding to the step of generating invitation object remarks information based on pre-set annotation generation rules and according to the invitation object identifier.

[0135] In one embodiment, when the processor executes the computer program, it further implements the following steps: storing the local storage identifier of the invitee as an association with the invitee identifier includes: storing the local storage identifier of the invitee as an association with the invitee identifier in the matching database; based on this, querying the set of invited objects to determine the unmatched invitee identifiers in the set of invited objects includes: querying the set of invited objects according to the matching database to determine the invitee identifiers in the set of invited objects that were not found in the matching database, thereby obtaining the unmatched invitee identifiers.

[0136] In one embodiment, when the processor executes the computer program, it further implements the following steps: associating the local storage identifier of the invitation object with the invitation object identifier includes: adding a matching identifier to the associated stored local storage identifier of the invitation object and the invitation object identifier; querying the set of invited objects to determine the unmatched invitation object identifier in the set of invited objects includes: querying the matching identifier of the invitation object identifier based on the invitation object identifier in the set of invited objects; when the matching identifier of the invitation object identifier does not exist, determining that the invitation object identifier is an unmatched invitation object identifier.

[0137] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0138] Get the invitation success message and extract the invitation target identifier and invitation business processing node identifier carried in the invitation success message;

[0139] Based on the pre-set annotation generation rules and according to the invitation object identifier, generate invitation object remarks information;

[0140] Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to add remarks information and push it;

[0141] Get the notification message indicating that the notes have been added, and get the set of invited objects corresponding to the invitation business processing node identifier;

[0142] Based on the remarks of the invited objects, find the local storage identifier corresponding to the invited object in the set of invited objects;

[0143] The local storage identifier of the invitee is associated with the invitee identifier and stored together.

[0144] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: generating invitation object remark information based on pre-set remark generation rules and according to the invitation object identifier, including: generating invitation object remark information based on pre-set remark generation rules and according to the invitation object identifier and the invitation business processing node identifier.

[0145] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: after associating and storing the local storage identifier of the invitation object with the invitation object identifier, it further includes: generating a request to delete the remarks information based on the invitation business processing node identifier and the remarks information of the invitation object, and pushing it; obtaining a reminder message indicating that the remarks have been deleted, and pushing a matching completion reminder message.

[0146] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: storing the local storage identifier of the associated invitation object and the invitation object identifier into a matching database; or, adding a matching identifier to the local storage identifier of the associated invitation object and the invitation object identifier.

[0147] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: periodically acquiring the invitation business processing node and the set of invited objects corresponding to the invitation business processing node; querying the set of invited objects to determine the identifier of the unmatched invited object in the set of invited objects; and proceeding to the step of generating invitation object remarks information based on pre-set annotation generation rules and according to the invitation object identifier.

[0148] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: storing the local storage identifier of the invitee in association with the invitee identifier includes: storing the local storage identifier of the invitee in association with the invitee identifier in the matching database; based on this, querying the set of invited objects to determine the unmatched invitee identifiers in the set of invited objects includes: querying the set of invited objects according to the matching database to determine the invitee identifiers in the set of invited objects that were not found in the matching database, thereby obtaining the unmatched invitee identifiers.

[0149] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: associating the local storage identifier of the invitation object with the invitation object identifier includes: adding a matching identifier to the associated stored local storage identifier of the invitation object and the invitation object identifier; querying the set of invited objects to determine the unmatched invitation object identifier in the set of invited objects includes: querying the matching identifier of the invitation object identifier based on the invitation object identifier in the set of invited objects; when the matching identifier of the invitation object identifier does not exist, determining that the invitation object identifier is an unmatched invitation object identifier.

[0150] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0151] Get the invitation success message and extract the invitation target identifier and invitation business processing node identifier carried in the invitation success message;

[0152] Based on the pre-set annotation generation rules and according to the invitation object identifier, generate invitation object remarks information;

[0153] Based on the invitation business processing node identifier and the invitation object's remarks information, generate a request to add remarks information and push it;

[0154] Get the notification message indicating that the notes have been added, and get the set of invited objects corresponding to the invitation business processing node identifier;

[0155] Based on the remarks of the invited objects, find the local storage identifier corresponding to the invited object in the set of invited objects;

[0156] The local storage identifier of the invitee is associated with the invitee identifier and stored together.

[0157] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: generating invitation object remark information based on pre-set remark generation rules and according to the invitation object identifier, including: generating invitation object remark information based on pre-set remark generation rules and according to the invitation object identifier and the invitation business processing node identifier.

[0158] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: after associating and storing the local storage identifier of the invitation object with the invitation object identifier, it further includes: generating a request to delete the remarks information based on the invitation business processing node identifier and the remarks information of the invitation object, and pushing it; obtaining a reminder message indicating that the remarks have been deleted, and pushing a matching completion reminder message.

[0159] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: storing the local storage identifier of the associated invitation object and the invitation object identifier into a matching database; or, adding a matching identifier to the local storage identifier of the associated invitation object and the invitation object identifier.

[0160] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: periodically acquiring the invitation business processing node and the set of invited objects corresponding to the invitation business processing node; querying the set of invited objects to determine the identifier of the unmatched invited object in the set of invited objects; and proceeding to the step of generating invitation object remarks information based on pre-set annotation generation rules and according to the invitation object identifier.

[0161] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: storing the local storage identifier of the invitee in association with the invitee identifier includes: storing the local storage identifier of the invitee in association with the invitee identifier in the matching database; based on this, querying the set of invited objects to determine the unmatched invitee identifiers in the set of invited objects includes: querying the set of invited objects according to the matching database to determine the invitee identifiers in the set of invited objects that were not found in the matching database, thereby obtaining the unmatched invitee identifiers.

[0162] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: associating the local storage identifier of the invitation object with the invitation object identifier includes: adding a matching identifier to the associated stored local storage identifier of the invitation object and the invitation object identifier; querying the set of invited objects to determine the unmatched invitation object identifier in the set of invited objects includes: querying the matching identifier of the invitation object identifier based on the invitation object identifier in the set of invited objects; when the matching identifier of the invitation object identifier does not exist, determining that the invitation object identifier is an unmatched invitation object identifier.

[0163] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0164] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0165] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. An invitation object information matching method characterized by comprising: The method comprises: obtaining an invitation success prompt message, extracting an invitation object identifier and an invitation service processing node identifier carried in the invitation success prompt message; generating invitation object note information based on a preset note generation rule and according to the invitation object identifier; generating an add note information request based on the invitation service processing node identifier and the invitation object note information, and pushing the add note information request; obtaining a note addition completion prompt message, and obtaining an already invited object set corresponding to the invitation service processing node identifier; according to the invitation object note information, finding a local storage identifier corresponding to an invitation object in the already invited object set; storing the local storage identifier of the invitation object and the invitation object identifier in association; obtaining an invitation service processing node and an already invited object set corresponding to the invitation service processing node in a timely manner; querying the already invited object set to determine an unmatched invitation object identifier in the already invited object set; and entering the step of generating invitation object note information based on a preset note generation rule and according to the invitation object identifier; the step of storing the local storage identifier of the invitation object and the invitation object identifier in association comprises: storing the locally stored local storage identifier of the invitation object and the invitation object identifier in a matching database; the step of querying the already invited object set to determine an unmatched invitation object identifier in the already invited object set comprises: querying the already invited object set according to the matching database to determine an invitation object identifier in the already invited object set that is not queried in the matching database, to obtain an unmatched invitation object identifier.

2. The method of claim 1, wherein, the step of generating invitation object note information based on a preset note generation rule and according to the invitation object identifier comprises: generating invitation object note information based on a preset note generation rule and according to the invitation object identifier and the invitation service processing node identifier.

3. The method of claim 1, wherein, after the step of storing the local storage identifier of the invitation object and the invitation object identifier in association, the method further comprises: generating a delete note information request based on the invitation service processing node identifier and the invitation object note information, and pushing the delete note information request; obtaining a note deletion completion prompt message, and pushing a matching completion prompt message.

4. The method of claim 3, wherein, the step of storing the local storage identifier of the invitation object and the invitation object identifier in association further comprises: adding a matching identifier to the locally stored local storage identifier of the invitation object and the invitation object identifier.

5. The method of claim 1, wherein, the step of storing the local storage identifier of the invitation object and the invitation object identifier in association comprises: adding a matching identifier to the locally stored local storage identifier of the invitation object and the invitation object identifier; the step of querying the already invited object set to determine an unmatched invitation object identifier in the already invited object set comprises: querying a matching identifier of the invitation object identifier according to the invitation object identifier in the already invited object set; when the matching identifier of the invitation object identifier does not exist, determining that the invitation object identifier is an unmatched invitation object identifier.

6. An invitation object information matching apparatus characterized by comprising: the device comprises: The acquisition module is used to acquire the invitation success message and extract the invitation object identifier and the invitation business processing node identifier carried in the invitation success message. The generation module is used to generate invitation object remarks information based on pre-set remarks generation rules and according to the invitation object identifier; The push module is used to generate and push a request to add remarks based on the invitation business processing node identifier and the remarks information of the invitation object; The acquisition module is also used to acquire the note addition completion prompt message and acquire the set of invited objects corresponding to the invitation business processing node identifier; The search module is used to search for the local storage identifier corresponding to the invited object in the set of invited objects based on the invited object's remarks information; The association module is used to associate and store the local storage identifier of the invitation object with the invitation object identifier; The scheduled query module is used to periodically retrieve the invitation business processing node and the set of invited objects corresponding to the invitation business processing node; The invited object set is queried to identify the unmatched invited object identifiers in the invited object set; then the step of generating invited object remarks information based on the pre-set annotation generation rules and the invited object identifiers is performed. The association module is also used to store the local storage identifier of the invitation object and the invitation object identifier in the matching database; The timed query module is also used to query the set of invited objects according to the matching database, determine the identifier of the invited object in the set of invited objects that is not found in the matching database, and obtain the identifier of the unmatched invited object.

7. The apparatus of claim 6, wherein, The generation module is also used to: generate invitation object remarks information based on pre-set remarks generation rules and according to the invitation object identifier and the invitation business processing node identifier.

8. The apparatus of claim 6, wherein, The device further includes: The deletion module is used to generate a request to delete the remarks based on the identifier of the invitation business processing node and the remarks information of the invitation object, and push it; obtain the remarks deletion completion prompt message, and push the matching completion prompt message. 9.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-8 when the computer program is executed by the processor. When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images