Data processing method and device, medium and program product
By deploying a data processing device between the business management system and the client and utilizing message queue and push template technology, the problem of interface resource occupation when the business management system sends messages is solved, thus improving the user experience.
Patent Information
- Application Number
- CN202510699930.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-28
- Publication Date
- 2025-09-12
AI Technical Summary
When the business management system sends event messages to the client, if there are many messages, a large amount of interface resources will be occupied, resulting in a poor user experience.
A data processing device is deployed between the business management system and the client, and the message sending request is stored in the message queue and a node identifier is generated. The push template and client are determined based on the target information, and the information is sent to the client after filling in the target text, thereby reducing the number of calls to the interface.
This reduces the occupation of interface resources by the business management system and improves user experience.
Smart Images
Figure CN120639714A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of data processing technology, and in particular to a data processing method, device, medium, and program product. Background Art
[0002] Currently, when an enterprise's business management system communicates with a client, the business management system needs to call an interface corresponding to each client to send a corresponding event message to the corresponding client.
[0003] However, when the above method is used to send event messages to the client, if a large number of event messages need to be sent, a large amount of interface resources will be occupied, resulting in a poor user experience.
[0004] Therefore, how to reduce the interface resources occupied when the business management system sends event messages to the client has become an urgent problem to be solved. Summary of the Invention
[0005] In order to solve the above technical problems or at least partially solve the above technical problems, the present disclosure provides a data processing method, device, medium and program product.
[0006] The present disclosure provides a data processing method, comprising: upon receiving a message sending request sent by a business management system, storing the message sending request in a message queue and generating a node identifier corresponding to the message sending request; wherein one message sending request corresponds to one project; based on target information, determining a push template and at least one client; wherein the target information includes one or more items of the node identifier and the configuration information of the project; filling the target text in the message sending request in the push template to obtain push information; and sending the push information to the client.
[0007] Optionally, when a message sending request is received from a business management system, the message sending request is stored in a message queue, and a node identifier corresponding to the message sending request is generated, including: when a message sending request is received from a business management system, obtaining a system module for sending a message sending request in the business management system, and storing the message sending request in a message queue; based on the message type, business action and system module corresponding to the message sending request, generating a node identifier corresponding to the message sending request.
[0008] Optionally, the target information includes a node identifier, a node identifier corresponds to a message type, a business action and a system module, and the system module is a module in the business management system that sends message sending requests; based on the target information, a push template and at least one client are determined, including: querying the first relationship table based on the message type, business action and system module corresponding to the node identifier, determining the push template corresponding to the node identifier, and at least one client.
[0009] Optionally, the target information includes a node identifier and configuration information; based on the target information, a push template and at least one client are determined, including: querying a second relationship table based on the configuration information, the message type corresponding to the node identifier, the business action and the system module, to determine the push template corresponding to the node identifier and at least one client.
[0010] Optionally, the target text in the message sending request is filled in the push template to obtain push information, including: obtaining the sending content carried in the message sending request; performing keyword extraction on the sending content to obtain at least one actual keyword; obtaining the actual keyword that is the same as the pre-stored theoretical keyword; filling the actual keyword that is the same as the pre-stored theoretical keyword into the push template to obtain push information.
[0011] Optionally, obtaining the actual keyword identical to the pre-stored theoretical keyword includes: calculating the similarity between the actual keyword and each pre-stored theoretical keyword; and determining the theoretical keyword identical to the actual keyword as the theoretical keyword corresponding to the maximum similarity.
[0012] Optionally, the message queue includes a Kafka message queue.
[0013] The present disclosure also provides a data processing device, including: a processing unit, which is used to store the message sending request in a message queue when receiving a message sending request sent by a business management system, and generate a node identifier corresponding to the message sending request; wherein, one message sending request corresponds to one project; the processing unit is also used to determine a push template and at least one client based on target information; wherein, the target information includes one or more of the node identifier and the configuration information of the project; the processing unit is also used to fill the target text in the message sending request in the push template to obtain push information; the processing unit is also used to control the transceiver unit to send push information to the client.
[0014] The present disclosure also provides an electronic device, which includes: a processor; a memory for storing processor-executable instructions; and a processor for reading executable instructions from the memory and executing the instructions to implement the data processing method provided by the present disclosure.
[0015] The present disclosure also provides a computer-readable storage medium, which stores a computer program for executing the data processing method provided by the present disclosure.
[0016] The present disclosure also provides a computer program product, including a computer program, which implements the data processing method provided in the present disclosure when executed by a processor.
[0017] The technical solution provided by the present disclosure deploys the data processing device provided by the present disclosure between the business management system and the client, so that when the data processing device receives a message sending request sent by the business management system, it stores the message sending request in a message queue and generates a node identifier corresponding to the message sending request. It can be seen that the business management system does not need to call the interface corresponding to the client to send the message sending request. Instead, it directly sends the corresponding message sending request to the data processing device, which stores the received message sending request in the message queue, reducing the number of calls to the interface by the business management system and thereby reducing the interface resource usage of the business management system. Thereafter, based on the target information, a push template and at least one client are determined; the target text in the message sending request is filled into the push template to obtain push information; and the push information is sent to the client. Because the number of calls to the interface by the business management system is reduced when using the data processing method provided by the present disclosure to send promotion information, the interface resource usage of the business management system can be reduced, solving the problem of how to reduce the interface resources occupied when the business management system sends event messages to the client.
[0018] It should be understood that the content described in this section is not intended to identify the key or important features of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0020] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0021] Figure 1 1 is a flow chart showing a data processing method according to the present embodiment;
[0022] Figure 2 Schematic diagram of a scenario of a data processing method provided by this embodiment is exemplarily shown in FIG.
[0023] Figure 3 exemplarily shows a structural diagram of a message reaching a server of a data processing method provided by this embodiment;
[0024] Figure 4 FIG2 exemplarily shows a second flow chart of a data processing method provided by this embodiment;
[0025] Figure 5 FIG3 exemplarily shows a flow chart of a data processing method provided by this embodiment;
[0026] Figure 6 FIG4 exemplarily shows a fourth flow chart of a data processing method provided by this embodiment;
[0027] Figure 7 FIG5 exemplarily shows a flow chart of a data processing method provided by this embodiment;
[0028] Figure 8 6 is a flowchart of a data processing method provided by this embodiment;
[0029] Figure 9 Schematic diagram of the structure of the data processing device provided by this embodiment is shown in FIG.
[0030] Figure 10 Schematic diagram of the structure of the electronic device provided by this embodiment is exemplarily shown in FIG. DETAILED DESCRIPTION
[0031] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features therein can be combined with each other in the absence of conflict.
[0032] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.
[0033] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.
[0034] In some examples, a business action in an embodiment of the present disclosure refers to a specific operation or behavior performed during a business process, typically a business-related operation, such as a trigger button such as submit or save.
[0035] Figure 1 This is a flow chart of a data processing method provided by an embodiment of the present disclosure. The method can be executed by a data processing device, wherein the data processing device can be implemented using software and / or hardware and can generally be integrated into a message reaching server. Figure 1 As shown, the method mainly includes the following steps:
[0036] S11. When receiving a message sending request sent by the business management system, store the message sending request in a message queue and generate a node identifier corresponding to the message sending request; wherein one message sending request corresponds to one project.
[0037] In some examples, the scenario diagram of the data processing method provided by the embodiment of the present disclosure is as follows: Figure 2 As shown, it includes a server 1 for providing a business management system, a message reaching server 2 and a client 3. Among them, the server 1 is used to send the message sending request that the business management system needs to send to the message reaching server 2. The message reaching server 2 is used to store the message sending request in the message queue when receiving the message sending request sent by the business management system, and generate a node identifier corresponding to the message sending request. The message reaching server 2 determines the push template and at least one client 3 based on the target information. The message reaching server 2 fills the target text in the message sending request in the push template to obtain the push information; the message reaching server 2 sends the push information to the client 3.
[0038] In some examples, the network structure of the message reaching server 2 is as follows Figure 3 As shown, it includes: a capability building module, an event module, a reach module and a storage module; the event module is used to store the message sending request in the message queue when receiving the message sending request sent by the business management system, and generate a node identifier corresponding to the message sending request. The template adapter module of the capability building module is used to periodically read the node identifier and configuration information from the message queue of the event module. After obtaining the node identifier and configuration information, the dimension matching module in the capability building module determines the push template and at least one client based on the target information obtained by the template adapter module. Afterwards, the template adapter module fills the target text in the message sending request in the push template to obtain the push information. The reach module sends the push information to the client based on the push information generated by the capability building module.
[0039] In some examples, the client may be an electronic device with a deployed application installed. When the electronic device is turned on, the application is started, and a communication connection is established between the application and the message reaching server 2, so that the message reaching server 2 can send the promotion information to the client.
[0040] In some examples, the storage module includes a database (MySQL), a remote dictionary service (RemoteDictionary Server, Redis), and an open source stream processing platform Kafka.
[0041] In some examples, the capability building module also includes a subscription / blocking capability submodule, which is used to subscribe to or block messages selected by the user, such as providing a sending time limit (for example, only allowing sending at 8 am and 10 pm to avoid harassing broker / client users) and a delayed message function.
[0042] In some examples, the capability building module also includes a reminder function submodule, which is used to remind users of messages that have been subscribed and set as reminders.
[0043] In some examples, the capability building module further includes a sending time control submodule, which is used to send push information according to a set sending time.
[0044] In some examples, the capability building module further includes a sending frequency control submodule, which is used to send push information according to a set sending frequency.
[0045] In some examples, the capability building module further includes a delayed message sending submodule, which is used to delay sending push information according to a set delay time.
[0046] In some examples, the capability building module also includes a message trace submodule, which is used to record and store the sent push information.
[0047] In some examples, the capability building module further includes a callback function submodule, which is used to call back a corresponding function to execute a corresponding function.
[0048] In some examples, the message reaching server 2 establishes a communication connection with the client via a wired or wireless manner, such as: the message reaching server 2 establishes a communication connection with the client via the Hypertext Transfer Protocol (HTTP).
[0049] S12. Determine a push template and at least one client based on target information; wherein the target information includes one or more of a node identifier and project configuration information.
[0050] In some examples, the memory of the message reaching server 2 pre-stores a first relationship table including message types, business actions and system modules corresponding to node identifiers, and push templates and clients.
[0051] Illustratively, the first relationship table is shown in Table 1.
[0052] Table 1
[0053]
[0054]
[0055] In this way, when the message reaches server 2 and needs to determine the push template and at least one client based on the target information, the first relationship table can be read from the memory, and then the first relationship table can be queried based on the message type, business action and system module corresponding to the node identifier to determine the push template corresponding to the node identifier and at least one client.
[0056] In some examples, the memory of the message reaching server 2 pre-stores a second relationship table containing configuration information, message types corresponding to node identifiers, business actions and system modules, and push templates and clients.
[0057] Exemplarily, the configuration information includes the project name and the target population, and the second relationship table is shown in Table 1.
[0058] Table 2
[0059]
[0060] Therefore, when the message reaches server 2 and needs to determine the push template and at least one client based on the target information, the second relationship table can be read from the memory, and then the second relationship table can be queried based on the message type, business action and system module corresponding to the node identifier to determine the push template corresponding to the node identifier and at least one client.
[0061] In some examples, the message type includes any one of pushMessage service, IM instant messaging, SMS, voice outbound call, long link (strong earthquake), and public account message.
[0062] In some examples, different clients can process different message types, so based on the message type, a client that can process the message type can be determined.
[0063] In some examples, the target information can be input into a processing model for processing to obtain a push template and at least one client. The training process of the processing model includes:
[0064] Obtain first training sample data and a first marking result of the first training sample data, wherein the first training sample data includes historical target information, and the first marking result includes a push template corresponding to the historical target information and at least one client.
[0065] The first training sample data is input into the first neural network model for learning to obtain a first prediction result of the first neural network model for the first training sample data.
[0066] Based on the first prediction result and the first labeling result, the network parameters of the first neural network model are adjusted until the first neural network model converges to obtain a processing model.
[0067] S13. Fill the target text in the message sending request in the push template to obtain push information.
[0068] In some examples, points that can be filled are reserved in the push template, so that the target text can be filled into the corresponding points to obtain push information.
[0069] In some examples, when filling the target text in the message sending request into the push template, the sending content carried in the message sending request can be obtained; keywords are extracted from the sending content to obtain at least one actual keyword; actual keywords that are the same as pre-stored theoretical keywords are obtained; and actual keywords that are the same as pre-stored theoretical keywords are filled into the push template to obtain push information.
[0070] In some examples, the target text in the message sending request can be input into the filling model for processing to obtain the push information. The training process of the filling model includes:
[0071] Obtain second training sample data and a second marking result of the second training sample data, wherein the second training sample data includes a historical target text and a push template, and the second marking result includes push information.
[0072] The second training sample data is input into the second neural network model for learning to obtain a second prediction result of the second neural network model.
[0073] Based on the second prediction result and the second labeling result, the network parameters of the second neural network model are adjusted until the second neural network model converges to obtain a filling model.
[0074] S14: Send push information to the client.
[0075] As can be seen from the foregoing, the technical solution provided by the embodiments of the present disclosure deploys the data processing device provided by the present disclosure between the business management system and the client. Thus, upon receiving a message send request from the business management system, the data processing device stores the message send request in a message queue and generates a node identifier corresponding to the message send request. It can be seen that the business management system does not need to call the interface corresponding to the client to send the message send request. Instead, it directly sends the corresponding message send request to the data processing device, which then stores the received message send request in the message queue. This reduces the number of calls to the interface by the business management system and, in turn, reduces the interface resource usage of the business management system.
[0076] In some possible implementation examples, combined with Figure 1 ,like Figure 4 As shown, the above S11 can be specifically implemented through the following S110 and S111.
[0077] S110 . Upon receiving a message sending request from the business management system, obtain a system module for sending the message sending request in the business management system, and store the message sending request in a message queue.
[0078] In some examples, by storing message sending requests in a message queue, the message reaching server 2 can concurrently process message sending requests sent by the business management system, without the need for the business management system to call an interface to send corresponding push information to the client, thereby improving the user experience.
[0079] In some examples, a system module corresponds to a job node. A job flow includes multiple job nodes, and each job node in the business management system generates a corresponding message sending request when running.
[0080] S111 . Generate a node identifier corresponding to the message sending request based on the message type, business action, and system module corresponding to the message sending request.
[0081] As can be seen from the above, the technical solution provided by the embodiment of the present disclosure deploys the data processing device provided by the present disclosure between the business management system and the client, so that when the data processing device receives the message sending request sent by the business management system, it obtains the system module for sending the message sending request in the business management system, and stores the message sending request in the message queue. Based on the message type, business action and system module corresponding to the message sending request, a node identifier corresponding to the message sending request is generated. It can be seen that the business management system does not need to call the interface corresponding to the client to send the message sending request, but directly sends the corresponding message sending request to the data processing device, and the data processing device stores the received message sending request in the message queue, thereby reducing the number of calls to the interface by the business management system, thereby reducing the occupation of interface resources by the business management system.
[0082] In some feasible examples, the target information includes a node identifier, a node identifier corresponds to a message type, a business action and a system module, and the system module is a module in the business management system that sends a message sending request; Figure 1 ,like Figure 5 As shown, the above S12 can be specifically implemented through the following S120.
[0083] S120: Query the first relationship table based on the message type, business action, and system module corresponding to the node identifier to determine the push template corresponding to the node identifier and at least one client.
[0084] As can be seen from the above, the technical solution provided by the embodiment of the present disclosure queries the first relationship table based on the message type, business action and system module corresponding to the node identifier to determine the push template corresponding to the node identifier and at least one client. Therefore, the push template corresponding to the node identifier and at least one client can be accurately determined based on the node identifier. There is no need for the business management system to call the interface corresponding to the client to send a message sending request, and the push information can be sent to the client, which reduces the number of calls to the interface by the business management system, thereby reducing the occupation of interface resources by the business management system.
[0085] In some examples, the target information includes node identification and configuration information; Figure 1 ,like Figure 6 As shown, the above S12 can be specifically implemented through the following S121.
[0086] S121. Query the second relationship table based on the configuration information, the message type corresponding to the node identifier, the service action, and the system module to determine the push template corresponding to the node identifier and at least one client.
[0087] As can be seen from the above, the technical solution provided by the embodiment of the present disclosure queries the second relationship table based on the configuration information, the message type corresponding to the node identifier, the business action, and the system module to determine the push template corresponding to the node identifier and at least one client. Therefore, the push template corresponding to the node identifier and at least one client can be accurately determined based on the node identifier. There is no need for the business management system to call the interface corresponding to the client to send a message sending request, and the push information can be sent to the client, which reduces the number of calls to the interface by the business management system, thereby reducing the occupation of the interface resources by the business management system.
[0088] In some possible implementation examples, combined with Figure 1 ,like Figure 7 As shown, the above S13 can be specifically implemented through the following S130-S133.
[0089] S130, obtaining the sending content carried in the message sending request;
[0090] S131, extract keywords from the sent content to obtain at least one actual keyword;
[0091] S132, obtaining actual keywords that are identical to pre-stored theoretical keywords;
[0092] S133: Fill the actual keywords that are the same as the pre-stored theoretical keywords into the push template to obtain push information.
[0093] As can be seen from the above, the technical solution provided by the embodiment of the present disclosure obtains the sending content carried in the message sending request; performs keyword extraction on the sending content to obtain at least one actual keyword; obtains actual keywords that are identical to pre-stored theoretical keywords; and fills the actual keywords that are identical to the pre-stored theoretical keywords into the push template to obtain push information. There is no need for the business management system to call the interface corresponding to the client to send a message sending request, and the push information can be sent to the client, reducing the number of calls to the interface by the business management system and thereby reducing the occupation of interface resources by the business management system.
[0094] In some possible implementation examples, combined with Figure 7 ,like Figure 8 As shown, the above S132 can be specifically implemented through the following S1320 and S1321.
[0095] S1320: Calculate the similarity between the actual keyword and each pre-stored theoretical keyword.
[0096] In some examples, when calculating the similarity between an actual keyword and each pre-stored theoretical keyword, the actual keyword can be first converted into a first vector and the theoretical keyword can be converted into a second vector. Then, a target distance, such as Euclidean distance or Manhattan distance, can be calculated between the first vector and each second vector. The target distance is then used as the similarity between the actual keyword corresponding to the first vector and the theoretical keyword corresponding to the second vector.
[0097] Alternatively, the cosine similarity between the first vector and each second vector is calculated, and then the cosine similarity is used as the similarity between the actual keyword corresponding to the first vector and the theoretical keyword corresponding to the second vector.
[0098] S1321. Determine the theoretical keyword that is the same as the actual keyword as the theoretical keyword corresponding to the maximum similarity.
[0099] As can be seen from the above, the technical solution provided by the embodiment of the present disclosure obtains the sending content carried in the message sending request; performs keyword extraction on the sending content to obtain at least one actual keyword; calculates the similarity between the actual keyword and each pre-stored theoretical keyword, and determines that the theoretical keyword that is the same as the actual keyword is the theoretical keyword corresponding to the greatest similarity; and fills the actual keyword that is the same as the pre-stored theoretical keyword into the push template to obtain push information. There is no need for the business management system to call the interface corresponding to the client to send a message sending request, and the push information can be sent to the client, which reduces the number of calls to the interface by the business management system, thereby reducing the occupation of the interface resources by the business management system.
[0100] In some possible implementations, the message queue includes a Kafka message queue.
[0101] As can be seen from the foregoing, the technical solution provided by the embodiments of the present disclosure deploys the data processing device provided by the present disclosure between the business management system and the client, so that when the data processing device receives a message sending request from the business management system, it stores the message sending request in a Kafka message queue and generates a node identifier corresponding to the message sending request. It can be seen that the business management system does not need to call the interface corresponding to the client to send the message sending request. Instead, it directly sends the corresponding message sending request to the data processing device, which then stores the received message sending request in the Kafka message queue. This reduces the number of calls to the interface by the business management system and, in turn, reduces the interface resource usage of the business management system.
[0102] Corresponding to the aforementioned data processing method, the present disclosure further provides a data processing device, Figure 9This is a structural diagram of a data processing device provided by an embodiment of the present disclosure. The device can be implemented by software and / or hardware and can generally be integrated into an electronic device, such as Figure 9 As shown, the data processing device includes: a processing unit 201 and a transceiver unit 202.
[0103] The processing unit 201 is used to store the message sending request in the message queue and generate a node identifier corresponding to the message sending request when receiving the message sending request sent by the business management system; wherein, one message sending request corresponds to one project; the processing unit 201 is also used to determine the push template and at least one client based on the target information; wherein, the target information includes one or more of the node identifier and the configuration information of the project; the processing unit 201 is also used to fill the target text in the message sending request in the push template to obtain push information; the processing unit 201 is also used to control the transceiver unit 202 to send push information to the client.
[0104] In some feasible examples, the processing unit 201 is specifically used to obtain the system module that sends the message sending request in the business management system when the transceiver unit 202 receives the message sending request sent by the business management system, and store the message sending request in the message queue; the processing unit 201 is specifically used to generate a node identifier corresponding to the message sending request based on the message type, business action and system module corresponding to the message sending request.
[0105] In some feasible examples, the target information includes a node identifier, a node identifier corresponds to a message type, a business action and a system module, and the system module is a module in the business management system that sends a message sending request; the processing unit 201 is specifically used to query the first relationship table based on the message type, business action and system module corresponding to the node identifier, determine the push template corresponding to the node identifier, and at least one client.
[0106] In some feasible examples, the target information includes a node identifier and configuration information; the processing unit 201 is specifically used to query the second relationship table based on the configuration information, the message type corresponding to the node identifier, the business action and the system module, and determine the push template corresponding to the node identifier, and at least one client.
[0107] In some feasible examples, the processing unit 201 is specifically used to obtain the sending content carried in the message sending request received by the transceiver unit 202; the processing unit 201 is specifically used to extract keywords from the sending content to obtain at least one actual keyword; the processing unit 201 is specifically used to obtain the actual keyword that is the same as the pre-stored theoretical keyword; the processing unit 201 is specifically used to fill the actual keyword that is the same as the pre-stored theoretical keyword into the push template to obtain push information.
[0108] In some feasible examples, the processing unit 201 is specifically used to calculate the similarity between the actual keyword and each pre-stored theoretical keyword; the processing unit 201 is specifically used to determine the theoretical keyword that is the same as the actual keyword as the theoretical keyword corresponding to the maximum similarity.
[0109] In some possible implementations, the message queue includes a Kafka message queue.
[0110] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and its role will not be repeated here.
[0111] Of course, the data processing device provided by the embodiment of the present invention includes but is not limited to the above modules. For example, the data processing device may further include a storage unit 203. The storage unit 203 may be used to store program codes of the data processing device, and may also be used to store data generated during the operation of the data processing device, such as diagnostic data.
[0112] An embodiment of the present invention provides a structural diagram of an electronic device, such as Figure 10 The electronic device shown may include: at least one processor 51 , a memory 52 , a communication interface 53 and a communication bus 54 .
[0113] The following is a detailed introduction to the various components of electronic equipment:
[0114] The processor 51 is the control center of the electronic device and can be a single processor or a collective term for multiple processing elements. For example, the processor 51 is a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention, such as one or more DSPs or one or more field programmable gate arrays (FPGAs).
[0115] In a specific implementation, as an embodiment, the processor 51 may include one or more CPUs, such as CPU0 and CPU1 included in the CPU. Also, as an embodiment, the electronic device may include multiple processors, such as the CPU including processor 51 and processor 55. Each of these processors may be a single-core processor (Single-CPU) or a multi-core processor (Multi-CPU). The processor here may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
[0116] The memory 52 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 52 may be independent and connected to the processor 51 via a communication bus 54. The memory 52 may also be integrated with the processor 51.
[0117] In a specific implementation, the memory 52 is used to store the data of the present invention and execute the software program of the present invention. The processor 51 can execute various functions of the air conditioner by running or executing the software program stored in the memory 52 and calling the data stored in the memory 52.
[0118] The communication interface 53 uses any transceiver or other device for communicating with other devices or communication networks, such as a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), a terminal, or the cloud. The communication interface 53 may include a transceiver unit to implement acquisition and reception functions.
[0119] Communication bus 54 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. This bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, a single thick line is used, but this does not imply that there is only one bus or only one type of bus.
[0120] As an example, combining Figure 9 The function implemented by the transceiver unit 202 of the data processing device is the same as that of the communication interface 53, the function implemented by the processing unit 201 in the data processing device is the same as that of the processor 51, and the function implemented by the storage unit 203 in the data processing device is the same as that of the memory 54.
[0121] An embodiment of the present invention provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the method in any embodiment.
[0122] An embodiment of the present invention provides a computer program product. When the computer program product is run on a computer, the computer is enabled to perform any method in any embodiment.
[0123] The foregoing description is intended only to provide specific embodiments of the present disclosure, intended to enable those skilled in the art to understand and implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the embodiments described herein, but rather to be construed in the broadest manner consistent with the principles and novel features disclosed herein.
Claims
1. A data processing method, characterized in that: include: Upon receiving a message sending request sent by the business management system, storing the message sending request in a message queue and generating a node identifier corresponding to the message sending request; wherein one message sending request corresponds to one project; Determine a push template and at least one client based on target information; wherein the target information includes one or more of the node identifier and the configuration information of the project; Filling the target text in the message sending request in the push template to obtain push information; Send the push information to the client.
2. The data processing method according to claim 1, wherein: When receiving a message sending request sent by a service management system, storing the message sending request in a message queue and generating a node identifier corresponding to the message sending request include: Upon receiving a message sending request from a business management system, obtaining a system module in the business management system that sends the message sending request, and storing the message sending request in a message queue; A node identifier corresponding to the message sending request is generated based on the message type, the service action, and the system module corresponding to the message sending request.
3. The data processing method according to claim 1, wherein: The target information includes the node identifier, where one node identifier corresponds to a message type, a service action, and a system module, and the system module is a module in the service management system that sends the message sending request; The step of determining a push template and at least one client based on target information includes: The first relationship table is queried based on the message type, business action, and system module corresponding to the node identifier to determine the push template corresponding to the node identifier and at least one client.
4. The data processing method according to claim 3, wherein: The target information includes the node identifier and the configuration information; The step of determining a push template and at least one client based on target information includes: The second relationship table is queried based on the configuration information, the message type corresponding to the node identifier, the service action, and the system module to determine the push template corresponding to the node identifier and at least one client.
5. The data processing method according to claim 1, wherein: Filling the target text in the message sending request in the push template to obtain push information includes: Obtaining the sending content carried in the message sending request; Performing keyword extraction on the sent content to obtain at least one actual keyword; Obtaining actual keywords that are identical to pre-stored theoretical keywords; The actual keywords that are the same as the pre-stored theoretical keywords are filled into the push template to obtain push information.
6. The data processing method according to claim 5, characterized in that: The step of obtaining the actual keyword that is the same as the pre-stored theoretical keyword includes: Calculating the similarity between the actual keyword and each of the pre-stored theoretical keywords; The theoretical keyword that is the same as the actual keyword is determined as the theoretical keyword corresponding to the maximum similarity.
7. The data processing method according to any one of claims 1 to 6, characterized in that: The message queue includes a Kafka message queue.
8. An electronic device, characterized in that: The electronic device comprises: a storage device having a computer program stored thereon; A processing device, configured to execute the computer program in the storage device to implement the steps of the data processing method according to any one of claims 1 to 7.
9. A computer-readable storage medium, characterized in that The storage medium stores a computer program, and the computer program is used to execute the data processing method according to any one of claims 1 to 7.
10. A computer program product, characterized in that The computer program comprises a computer program which, when executed by a processor, implements the data processing method according to any one of claims 1 to 7.