CN114979256B - Message pushing method and device, electronic equipment and computer readable medium - Google Patents
Message pushing method and device, electronic equipment and computer readable medium Download PDFInfo
- Publication number
- CN114979256B CN114979256B CN202210545184.4A CN202210545184A CN114979256B CN 114979256 B CN114979256 B CN 114979256B CN 202210545184 A CN202210545184 A CN 202210545184A CN 114979256 B CN114979256 B CN 114979256B
- Authority
- CN
- China
- Prior art keywords
- message
- notification
- attribute
- rule
- pushing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a message pushing method, a device, electronic equipment and a computer readable medium, relating to the technical field of computers, wherein the method comprises the following steps: receiving a message push request, acquiring a corresponding message and a scene registration identifier, and determining a corresponding notification mode based on the scene registration identifier; determining a corresponding notification rule set according to the notification mode, and acquiring a state identifier of each notification rule in the notification rule set; determining a message receiver list according to the state identification, the message and the notification rule; and analyzing the message to obtain corresponding message content, and pushing the message content to each message receiver in the message receiver list. Therefore, a plurality of notification modes are covered, new notification modes can be expanded, a user can change notification rules at any time, the notification rules take effect immediately, and flexibility of message pushing is realized; the users are independent from each other and are not influenced, the complexity of accessing the message pushing system is reduced, and the stability of the message pushing system is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a message pushing method, a device, an electronic device, and a computer readable medium.
Background
At present, a business scene sends a notification, and every new notification mode needs to be developed or connected with other notification platforms, and a personalized notification mode cannot be supported, so that the support of an underlying notification service is needed. Every time a notification mode is added in each service scene, a notification platform service needs to be connected, and the access complexity is increased.
In the process of implementing the present application, the inventor finds that at least the following problems exist in the prior art:
the new notification mode or the change notification mode needs to be adjusted in the service code, has no flexibility of the notification mode, and can cause instability of a message pushing system.
Disclosure of Invention
In view of the above, embodiments of the present application provide a message pushing method, device, electronic apparatus, and computer readable medium, which can solve the problems that the existing new or changed notification mode needs to be adjusted in service codes, has no flexibility of the notification mode, and can cause instability of the message pushing system.
To achieve the above object, according to one aspect of the embodiments of the present application, there is provided a message pushing method, including:
Receiving a message push request, acquiring a corresponding message and a scene registration identifier, and further determining a corresponding notification mode based on the scene registration identifier;
Determining a corresponding notification rule set according to the notification mode, and acquiring a state identifier of each notification rule in the notification rule set;
determining a message receiver list according to the state identification, the message and the notification rule;
Analyzing the message to obtain the corresponding message content, and pushing the message content to each message receiver in the message receiver list.
Optionally, determining the message recipient list includes:
determining attribute identifiers corresponding to the notification rules;
And determining a message receiver list according to the attribute identification, the message and the state identification.
Optionally, determining the message receiver list according to the attribute identifier, the message and the state identifier includes:
And responding to the corresponding extended attribute of the attribute identifier, acquiring a corresponding attribute annotation, and further determining a receiver list according to the attribute annotation, the message and the state identifier.
Optionally, determining the receiver list according to the attribute annotation, the message and the status identifier includes:
And responding to the starting of the state identification corresponding rule, calling a receiver parser to parse the attribute annotation and the message, and further obtaining a receiver list required by a corresponding notification mode.
Optionally, before determining the message recipient list, the method further comprises:
and dynamically rendering the rule configuration page and displaying the rule configuration page based on the notification rule set and the state identification.
Optionally, pushing the message content to each message recipient in the message recipient list includes:
determining attribute identifiers corresponding to the notification rules;
Responding to the corresponding extension attribute of the attribute identifier, and acquiring extension rule content corresponding to the extension attribute;
message content is pushed to each message recipient in the message recipient list based on the extended rule content.
In addition, the application also provides a message pushing device, which comprises:
The receiving unit is configured to receive the message push request, acquire the corresponding message and the scene registration identifier, and further determine the corresponding notification mode based on the scene registration identifier;
The state identifier acquisition unit is configured to determine a corresponding notification rule set according to the notification mode and acquire the state identifier of each notification rule in the notification rule set;
a message receiver list determining unit configured to determine a message receiver list according to the status identifier, the message and the notification rule;
the message pushing unit is configured to analyze the message to obtain corresponding message content, and then push the message content to each message receiver in the message receiver list.
Optionally, the message recipient list determination unit is further configured to:
determining attribute identifiers corresponding to the notification rules;
And determining a message receiver list according to the attribute identification, the message and the state identification.
Optionally, the message recipient list determination unit is further configured to:
And responding to the corresponding extended attribute of the attribute identifier, acquiring a corresponding attribute annotation, and further determining a receiver list according to the attribute annotation, the message and the state identifier.
Optionally, the message recipient list determination unit is further configured to:
And responding to the starting of the state identification corresponding rule, calling a receiver parser to parse the attribute annotation and the message, and further obtaining a receiver list required by a corresponding notification mode.
Optionally, the message pushing device further comprises a dynamic rendering unit configured to:
and dynamically rendering the rule configuration page and displaying the rule configuration page based on the notification rule set and the state identification.
Optionally, the message pushing unit is further configured to:
determining attribute identifiers corresponding to the notification rules;
Responding to the corresponding extension attribute of the attribute identifier, and acquiring extension rule content corresponding to the extension attribute;
message content is pushed to each message recipient in the message recipient list based on the extended rule content.
In addition, the application also provides a message pushing electronic device, which comprises: one or more processors; and the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are enabled to realize the message pushing method.
In addition, the application also provides a computer readable medium, on which a computer program is stored, which when executed by a processor implements the message pushing method as described above.
One embodiment of the above application has the following advantages or benefits: the method and the device acquire the corresponding message and the scene registration identifier by receiving the message push request, and further determine the corresponding notification mode based on the scene registration identifier; determining a corresponding notification rule set according to the notification mode, and acquiring a state identifier of each notification rule in the notification rule set; determining a message receiver list according to the state identification, the message and the notification rule; analyzing the message to obtain the corresponding message content, and pushing the message content to each message receiver in the message receiver list. Therefore, a plurality of notification modes are covered, new notification modes can be expanded, a user can change notification rules at any time, the notification rules take effect immediately, and flexibility of message pushing is realized; the users are independent from each other and are not influenced, the complexity of accessing the message pushing system is reduced, and the stability of the message pushing system is improved.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the application and are not to be construed as unduly limiting the application. Wherein:
Fig. 1 is a schematic diagram of a main flow of a message pushing method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a main flow of a message pushing method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of an execution flow of a message pushing method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of the overall architecture of a message pushing method according to an embodiment of the present application;
Fig. 5 is a schematic diagram of the main units of a message pushing device according to an embodiment of the present application;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present application may be applied;
Fig. 7 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.
Detailed Description
Exemplary embodiments of the present application will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present application are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness. The technical scheme of the application obtains, stores, uses, processes and the like the data, which all meet the relevant regulations of national laws and regulations.
Fig. 1 is a schematic diagram of main flow of a message pushing method according to an embodiment of the present application, where, as shown in fig. 1, the message pushing method includes:
step S101, receiving a message pushing request, obtaining a corresponding message and a scene registration identifier, and further determining a corresponding notification mode based on the scene registration identifier.
In this embodiment, the execution body (for example, may be a server) of the message pushing method may receive the message pushing request by means of a wired connection or a wireless connection. The execution body can acquire the message corresponding to the message pushing request, and can analyze the message to acquire the information such as the message receiver, the content of the message and the like. After receiving the message pushing request, the executing body can acquire the scene registration identifier carried in the request.
Different tenants based on SAAS can acquire the notification rule set through the scene registration identification. A notification rule corresponds to a notification style that contains multiple notification rules, that is, a notification style may correspond to a set of notification rules. For example, the notification mode of sending the mail can configure various notification rules, and send the mail according to the rules. Each mode has general rule attributes such as receiver, push content, timing, instant, etc.; the extended rule attribute of the notification method can be set in different notification modes, and if the station communication has voice broadcasting, the voice broadcasting content and the like can be set.
For example, when the executing body acquires the message, the corresponding notification rule set is acquired through the notification scene registration code (i.e. scene registration identifier) in the message, and the notification rule is traversed. The receiver parser parses the receiver list required by the corresponding notification mode according to the rules, the template parser parses the real notification content of the template through Freemark grammar, and the notification mode parser is selected according to the rules to complete the complete process of pushing the message according to one rule by the tenant in one notification mode under one business scene.
Step S102, determining a corresponding notification rule set according to the notification mode, and acquiring the state identification of each notification rule in the notification rule set.
One notification approach may correspond to multiple notification rules and may correspond to a set of notification rules. After acquiring the notification rule sets, the executing body may determine a status identification of each notification rule in the notification rule sets. The state identifier may be QY or JY, where QY may represent an enabling rule and JY may represent a disabling rule. Based on the status identification of each notification rule, it may be determined whether each notification rule in the notification manner is enabled.
Step S103, determining a message receiver list according to the state identification, the message and the notification rule.
The executing body may determine, based on the status identification, that notification rules have been enabled. The execution body can analyze the enabled notification rule and the message, and then analyze the notification rule and the message to obtain a message receiver list. The notification rule may include information specifying a receiver, timing, time limit, and the like. The message may include information such as a default receiver, push content, etc. The information included in the message and the notification rule in the embodiment of the present application is not particularly limited.
Specifically, before determining the message recipient list, the method further comprises:
and dynamically rendering the rule configuration page and displaying the rule configuration page based on the notification rule set and the state identification.
The user can take effect by enabling/disabling the rules on the provided visual notification rule configuration page, and after the user performs rule configuration on the provided visual notification rule configuration interface, the execution main body dynamically renders and displays the rule page configured by the user based on the configuration rules input by the user, so that the user can clearly configure the rules, the user can modify the configuration rules at any time conveniently, and notification rule configuration is perfected.
Step S104, analyzing the message to obtain the corresponding message content, and pushing the message content to each message receiver in the message receiver list.
Specifically, pushing the message content to each message recipient in the message recipient list includes: determining attribute identifiers corresponding to the notification rules; responding to the corresponding extension attribute of the attribute identifier, and acquiring extension rule content corresponding to the extension attribute; message content is pushed to each message recipient in the message recipient list based on the extended rule content.
For example, the extended rule attribute of the notification method can be set in different notification modes, and if the station message has a voice broadcast, the voice broadcast content and the like can be set.
According to the embodiment, a corresponding message and a scene registration identifier are obtained by receiving a message pushing request, and then a corresponding notification mode is determined based on the scene registration identifier; determining a corresponding notification rule set according to the notification mode, and acquiring a state identifier of each notification rule in the notification rule set; determining a message receiver list according to the state identification, the message and the notification rule; analyzing the message to obtain the corresponding message content, and pushing the message content to each message receiver in the message receiver list. Therefore, a plurality of notification modes are covered, new notification modes can be expanded, a user can change notification rules at any time, the notification rules take effect immediately, and flexibility of message pushing is realized; the users are independent from each other and are not influenced, the complexity of accessing the message pushing system is reduced, and the stability of the message pushing system is improved.
Fig. 2 is a main flow diagram of a message pushing method according to an embodiment of the present application, where, as shown in fig. 2, the message pushing method includes:
Step S201, receiving a message push request, obtaining a corresponding message and a scene registration identifier, and further determining a corresponding notification mode based on the scene registration identifier.
Step S202, determining a corresponding notification rule set according to the notification mode, and acquiring the state identification of each notification rule in the notification rule set.
Step S203, determining an attribute identifier corresponding to the notification rule.
The execution body may determine an attribute identification corresponding to the notification rule. Wherein the attribute identification is used to characterize whether the universal rule attribute or the extended attribute. If the attribute is a general rule attribute, the corresponding attribute identification may be TY, and if the attribute is an extended attribute, the corresponding attribute identification may be KZ. The embodiment of the application does not limit the corresponding relation between the attribute identification and the specific attribute.
Step S204, determining a message receiving side list according to the attribute identification, the message and the state identification.
Specifically, determining a message receiver list according to the attribute identifier, the message and the state identifier includes: and responding to the corresponding extended attribute of the attribute identifier, acquiring a corresponding attribute annotation, and further determining a receiver list according to the attribute annotation, the message and the state identifier.
And an extension rule attribute can be set for the notification mode to realize personalized information pushing. By way of example, the extended rule attribute may include a voice broadcast, a voice broadcast content, etc. of the in-station message, and the extended rule attribute may also include a designated recipient, a transcriber, etc. The embodiment of the application does not limit the content of the extended rule attribute in detail.
For example, the execution body may mark the extended attribute of the notification manner by using the attribute annotation @ NotifyFiled (filled = "attribute encoding (attribute itself may be ignored by default)", description = "attribute description", type = "attribute type", NEEDANALYSIS = "whether dynamic parsing default false" is supported, showFlag = "whether front-end exposes default true", rules = [ rule array ]). The front end dynamically renders rule attribute configuration items of each notification mode. A specific receiver, a transcriber, etc. may be set in the attribute description of the attribute annotation. The message may carry information such as a default receiving party (e.g., a default receiving address). When the execution main body determines that the attribute identifier corresponds to the extension attribute, the corresponding attribute annotation is obtained, the attribute description in the attribute annotation of the notification rule corresponding to the enabling rule is analyzed, the obtained message is analyzed, and finally a receiver list is obtained. That is, parsing the attribute description, message in the attribute annotation of the notification rule in the enabled state to determine the recipient list.
Specifically, determining the list of the receiving party according to the attribute annotation, the message and the state identifier comprises the following steps: and responding to the starting of the state identification corresponding rule, calling a receiver parser to parse the attribute annotation and the message, and further obtaining a receiver list required by a corresponding notification mode.
In step S205, the message is parsed to obtain the corresponding message content, and the message content is pushed to each message receiver in the message receiver list.
The embodiment of the application can cover various notification modes, can expand new notification modes through expanding attributes, can change notification rules at any time by a user, takes effect immediately, and realizes flexibility of message pushing; the users are independent from each other and are not influenced, the complexity of accessing the message pushing system is reduced, and the stability of the message pushing system is improved.
Fig. 3 is an application scenario schematic diagram of a message pushing method according to an embodiment of the present application. The message pushing method provided by the embodiment of the application is applied to a SAAS multi-tenant notification message pushing scene. As shown in fig. 3, when the message is received and authenticated by the authentication center, the message is sent to the message queue pool to wait for pushing, when the message is taken out from the message queue pool, the message is put into the message check pool to check the safety of the message, and when the message is checked and passed, the message is pushed to the rule engine, the rule engine acquires the corresponding notification rule set through the notification scene registration code in the message, and the notification rule is traversed and executed. The receiver parser parses the receiver list required by the corresponding notification mode according to the rules, the template parser parses the real notification content of the template through Freemark grammar, and the notification mode parser is selected according to the rules to complete the complete process of pushing the message according to one rule by the tenant in one notification mode under one business scene.
Fig. 4 is a schematic diagram of an overall architecture of a message pushing method according to an embodiment of the present application. As shown in fig. 4, the overall architecture of the message pushing method is described as follows:
the unified notification platform meets the requirement that the SAAS system sends notifications according to the customized rules for each service scene. A unified notification service API is provided externally. The unified notification platform provides access credentials registered through a scene registration center, different notification modes can be customized in the platform according to different service scenes of different tenants, a receiver is notified, notification content and the like are notified, and online editing Freemark grammar supported notification content and the like are supported
The platform has the functions of rule dynamic analysis, template dynamic rendering, message processing, log monitoring, abnormal alarm and report statistics. The abnormal push data supports online retry pushing and the like. Notification supports multiple modes of instant, timed, cyclic push, etc.
The business system can complete access to a plurality of notification modes at one time only by calling a unified notification service API, so as to achieve flexible change and customized notification pushing.
Specifically, the first step: the scene registration is notified.
The embodiment of the application realizes the pushing of the message through the unified notification platform. The unified notification platform has service notification scene registration capability. Two registration methods are provided: one is to manage page registration through unified platform registration. One is to dynamically complete notification scene registration by using a note @ Notify (code = "xxx notification unique registration code", note = "scene description", source = "system source description") on a method of a service scene code that needs to send notification.
And a second step of: and customizing the template.
And configuring the template, and supporting Freemark grammar writing of template contents. The notification rule uses a specified rule. The actual content of the template is dynamically parsed by the template parser (each attribute of the notification rule includes extended attributes supporting freemark grammar dynamic parsing). And maintaining the defined templates, the template parser and the JSS storage through informing the template management. The JSS storage is an online storage service, and provides management functions of storing, accessing, backing up, sharing and the like of files for users.
And a third step of: and notifying rule configuration, namely configuring a notification mode and rules for multiple tenants.
The unified notification platform supports multiple notification modes, and dynamically renders rule configuration pages. The user only needs to configure rules in a corresponding notification mode. Each notification mode supports configuration of multiple rules, which are validated by enabling/disabling.
Each notification mode rule attribute is divided into a general attribute and an extension attribute, and the general attribute is uniformly defined; the extended attribute is marked by using attribute annotation @ NotifyFiled (filled = "attribute code (default may ignore the use of attribute itself)", description = "attribute description", type = "attribute type", NEEDANALYSIS = "whether dynamic parsing default false" is supported, showFlag = "whether front end shows default true", rules = [ rule array ]). The front end dynamically renders rule attribute configuration items of each notification mode.
In the process of executing message pushing, when an executing body receives message messages from each message source (such as message source 1, message source 2 or message source 3), after passing authentication of an authentication center, the executing body sends the messages to a message queue pool to wait for executing pushing, when the messages are taken out from the message queue pool, the messages are put into a message check pool to check the safety of the messages, and when the messages pass the check, the messages are pushed to a rule engine, the rule engine acquires a corresponding notification rule set through a notification scene registration code in the messages, and the notification rules are executed in a traversing manner. The receiver parser parses the receiver list required by the corresponding notification mode according to the rules, the template parser parses the real notification content of the template through Freemark grammar, and the notification mode parser is selected according to the rules to complete the complete process of pushing the message according to one rule by the tenant in one notification mode under one business scene.
Message pushing can be performed based on a circulation task, a timing task and a retry mechanism after pushing failure, so that individuation, efficiency and accuracy of message pushing are guaranteed.
Message touch: through corresponding message channels, for example: email, SMS, APP, instant messaging software, in-station messaging, etc. to push the message to the intended recipient. If the short message is sent, pushing the short message to the corresponding mobile phone number.
The monitoring center executes log record, abnormal alarm, report statistics and the like of message pushing, so that smooth message pushing is ensured, and meanwhile, the message pushing can be ensured to be tracked.
The embodiment of the application supports frequent change and personalized customization of the notification mode under the complex and changeable business scene of the SAAS platform by integrating various notification modes, such as dynamic extension of rules, template customization and the like, reduces the access complexity of business codes and shields the complete solution of instability caused by system deployment.
According to the embodiment of the application, by providing the SAAS unified notification service platform and integrating a plurality of general notification modes, tenants can customize the notification modes and rules, and the notification in different service scenes is flexible and changeable due to high availability and expandability. The SAAS unified notification platform can be realized; integrating a plurality of notification modes; one-time access, changing a switching notification mode through rules; customizable, expandable, flexible; supporting notification rule dynamic extension attributes; support bulk, single-bar, split or union transmission per recipient, role, organization, etc.
The embodiment of the application provides a scheme for customizing multi-tenant message notification rules, which enables different tenants to set the message notification rules according to own requirements. Covering a plurality of message notification modes, the unified notification platform expands a new notification mode, an accessed service system immediately obtains the capability of the message notification mode, a tenant can change notification rules at any time, the notification rules take effect immediately, and the mutual independence among tenants is not affected.
Fig. 5 is a schematic diagram of main units of a message pushing device according to an embodiment of the present application. As shown in fig. 5, the message pushing apparatus 500 includes a receiving unit 501, a status identifier acquiring unit 502, a message recipient list determining unit 503, and a message pushing unit 504.
The receiving unit 501 is configured to receive a message push request, acquire a corresponding message and a scene registration identifier, and further determine a corresponding notification mode based on the scene registration identifier;
A state identifier obtaining unit 502 configured to determine a corresponding notification rule set according to the notification manner, and obtain a state identifier of each notification rule in the notification rule set;
a message recipient list determining unit 503 configured to determine a message recipient list according to the status identifier, the message, and the notification rule;
The message pushing unit 504 is configured to parse the message to obtain the corresponding message content, and further push the message content to each message recipient in the message recipient list.
In some embodiments, the message recipient list determination unit 503 is further configured to: determining attribute identifiers corresponding to the notification rules; and determining a message receiver list according to the attribute identification, the message and the state identification.
In some embodiments, the message recipient list determination unit 503 is further configured to: and responding to the corresponding extended attribute of the attribute identifier, acquiring a corresponding attribute annotation, and further determining a receiver list according to the attribute annotation, the message and the state identifier.
In some embodiments, the message recipient list determination unit 503 is further configured to: and responding to the starting of the state identification corresponding rule, calling a receiver parser to parse the attribute annotation and the message, and further obtaining a receiver list required by a corresponding notification mode.
In some embodiments, the message pushing device further comprises a dynamic rendering unit, not shown in fig. 5, configured to: and dynamically rendering the rule configuration page and displaying the rule configuration page based on the notification rule set and the state identification.
In some embodiments, the message pushing unit 504 is further configured to: determining attribute identifiers corresponding to the notification rules; responding to the corresponding extension attribute of the attribute identifier, and acquiring extension rule content corresponding to the extension attribute; message content is pushed to each message recipient in the message recipient list based on the extended rule content.
It should be noted that, in the message pushing method and the message pushing device of the present application, there is a corresponding relationship in the implementation content, so the repeated content will not be described.
Fig. 6 illustrates an exemplary system architecture 600 to which a message pushing method or message pushing apparatus of embodiments of the present application may be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 is used as a medium to provide communication links between the terminal devices 601, 602, 603 and the server 605. The network 604 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 605 via the network 604 using the terminal devices 601, 602, 603 to receive or send messages, etc. Various communication client applications such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 601, 602, 603.
The terminal devices 601, 602, 603 may be various electronic devices with a message push processing screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (by way of example only) providing support for message push requests submitted by users using the terminal devices 601, 602, 603. The background management server can receive the message push request, acquire the corresponding message and the scene registration identifier, and further determine the corresponding notification mode based on the scene registration identifier; determining a corresponding notification rule set according to the notification mode, and acquiring a state identifier of each notification rule in the notification rule set; determining a message receiver list according to the state identification, the message and the notification rule; analyzing the message to obtain the corresponding message content, and pushing the message content to each message receiver in the message receiver list. Therefore, a plurality of notification modes are covered, new notification modes can be expanded, a user can change notification rules at any time, the notification rules take effect immediately, and flexibility of message pushing is realized; the users are independent from each other and are not influenced, the complexity of accessing the message pushing system is reduced, and the stability of the message pushing system is improved.
It should be noted that, the message pushing method provided in the embodiment of the present application is generally executed by the server 605, and accordingly, the message pushing device is generally disposed in the server 605.
It should be understood that the number of terminal devices, networks and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, there is illustrated a schematic diagram of a computer system 700 suitable for use in implementing an embodiment of the present application. The terminal device shown in fig. 7 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment of the present application.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU) 701, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM703, various programs and data required for the operation of the computer system 700 are also stored. The CPU701, ROM702, and RAM703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input section 706 including a keyboard, a mouse, and the like; an output section 707 including a Cathode Ray Tube (CRT), a liquid crystal credit authorization query processor (LCD), and the like, and a speaker, and the like; a storage section 708 including a hard disk or the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. The drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read therefrom is mounted into the storage section 708 as necessary.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 709, and/or installed from the removable medium 711. The above-described functions defined in the system of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 701.
The computer readable medium shown in the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium may include, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented in software or in hardware. The described units may also be provided in a processor, for example, described as: a processor includes a receiving unit, a status identifier obtaining unit, a message recipient list determining unit, and a message pushing unit. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
As another aspect, the present application also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs, and when the one or more programs are executed by one device, the device receives a message pushing request, acquires a corresponding message and a scene registration identifier, and further determines a corresponding notification mode based on the scene registration identifier; determining a corresponding notification rule set according to the notification mode, and acquiring a state identifier of each notification rule in the notification rule set; determining a message receiver list according to the state identification, the message and the notification rule; analyzing the message to obtain the corresponding message content, and pushing the message content to each message receiver in the message receiver list.
According to the technical scheme of the embodiment of the application, a plurality of notification modes can be covered, a new notification mode can be expanded, a user can change the notification rule at any time, the notification rule takes effect immediately, and the flexibility of message pushing is realized; the users are independent from each other and are not influenced, the complexity of accessing the message pushing system is reduced, and the stability of the message pushing system is improved.
The above embodiments do not limit the scope of the present application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application should be included in the scope of the present application.
Claims (6)
1. A message pushing method, comprising:
receiving a message push request, acquiring a corresponding message and a scene registration identifier, and further determining a corresponding notification mode based on the scene registration identifier;
determining a corresponding notification rule set according to the notification mode, and acquiring a state identifier of each notification rule in the notification rule set;
Determining an attribute identifier corresponding to the notification rule, responding to the attribute identifier corresponding to the extension attribute, obtaining a corresponding attribute annotation, responding to the state identifier corresponding rule starting, and calling a receiver analyzer to analyze the attribute annotation and the message, thereby obtaining a message receiver list required by a corresponding notification mode;
Analyzing the message to obtain corresponding message content, and pushing the message content to each message receiver in the message receiver list based on a circulation task, a timing task and a retry mechanism after a push failure.
2. The method of claim 1, wherein prior to the obtaining the list of message recipients required for the corresponding notification means, the method further comprises:
And dynamically rendering a rule configuration page and displaying the rule configuration page based on the notification rule set and the state identification.
3. The method of claim 1, wherein pushing the message content to each message recipient in the list of message recipients based on a loop task, a timing task, and a retry mechanism after a push failure comprises:
Responding to the attribute identification corresponding to the extension attribute, and acquiring extension rule content corresponding to the extension attribute;
Pushing the message content to each message recipient in the message recipient list based on the extended rule content.
4. A message pushing device, comprising:
The receiving unit is configured to receive the message pushing request, acquire a corresponding message and a scene registration identifier, and further determine a corresponding notification mode based on the scene registration identifier;
the state identifier acquisition unit is configured to determine a corresponding notification rule set according to the notification mode and acquire the state identifier of each notification rule in the notification rule set;
A message receiver list determining unit configured to determine an attribute identifier corresponding to the notification rule, respond to the attribute identifier corresponding to the extension attribute, obtain a corresponding attribute annotation, respond to the state identifier corresponding rule enablement, and call a receiver parser to parse the attribute annotation and the message, thereby obtaining a message receiver list required by a corresponding notification mode;
The message pushing unit is configured to analyze the message to obtain corresponding message content, and then push the message content to each message receiver in the message receiver list based on a circulation task, a timing task and a retry mechanism after a push failure.
5. A message pushing electronic device, comprising:
One or more processors;
Storage means for storing one or more programs,
When executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-3.
6. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210545184.4A CN114979256B (en) | 2022-05-19 | 2022-05-19 | Message pushing method and device, electronic equipment and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210545184.4A CN114979256B (en) | 2022-05-19 | 2022-05-19 | Message pushing method and device, electronic equipment and computer readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114979256A CN114979256A (en) | 2022-08-30 |
| CN114979256B true CN114979256B (en) | 2024-06-18 |
Family
ID=82985986
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210545184.4A Active CN114979256B (en) | 2022-05-19 | 2022-05-19 | Message pushing method and device, electronic equipment and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114979256B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN120223666A (en) * | 2023-12-27 | 2025-06-27 | 华为技术有限公司 | Method for notifying synchronization and electronic equipment |
| CN117857623B (en) * | 2024-03-04 | 2024-05-03 | 深圳市芯科云科技有限公司 | Method and system for distributing notification messages by intelligent equipment |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111835837A (en) * | 2020-06-28 | 2020-10-27 | 中国船舶重工集团公司第七一六研究所 | Message pushing method and system with multi-terminal adaptation |
Family Cites Families (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101694708A (en) * | 2009-11-06 | 2010-04-14 | 金蝶软件（中国）有限公司 | Method and device for enabling encoding rules |
| US8788602B1 (en) * | 2011-09-12 | 2014-07-22 | Google Inc. | Method and system for providing notifications for specific messages |
| US9094356B2 (en) * | 2011-12-15 | 2015-07-28 | Visa International Service Association | Supplemental alert system and method |
| US9667734B2 (en) * | 2013-12-09 | 2017-05-30 | Electronics And Telecommunications Research Institute | Push notification-based remote control method and apparatus for the same |
| CN103873173B (en) * | 2014-03-27 | 2016-09-28 | 北京悦龙数字广播传媒科技有限责任公司 | Digital propelling movement type broadcasting method based on wireless digital broadcasting technology |
| CN104954469B (en) * | 2015-06-19 | 2018-07-24 | 长沙廖氏软件科技有限公司 | A kind of heterogeneous system information switching method |
| US10187486B1 (en) * | 2016-03-17 | 2019-01-22 | Google Llc | Systems and methods for automatic extension of information from a first network to a second network |
| CN107368376B (en) * | 2017-05-31 | 2021-02-05 | 无锡雅座在线科技股份有限公司 | Message sending method and device, expansion method and terminal |
| CN107864174B (en) * | 2017-07-03 | 2021-07-20 | 华南理工大学 | A rule-based linkage method for IoT devices |
| CN107302597B (en) * | 2017-08-17 | 2020-06-16 | 北京星选科技有限公司 | Message file pushing method and device |
| CN108848142B (en) * | 2018-05-31 | 2022-05-31 | 康键信息技术（深圳）有限公司 | Message pushing method and device, computer equipment and storage medium |
| CN111800445B (en) * | 2019-04-09 | 2023-02-28 | Oppo广东移动通信有限公司 | Message push method, device, storage medium and electronic equipment |
| CN111010426A (en) * | 2019-11-27 | 2020-04-14 | 江苏苏宁物流有限公司 | Message pushing method and device |
| CN113360815B (en) * | 2020-03-04 | 2024-10-18 | 北京沃东天骏信息技术有限公司 | Request retry method and device |
| CN111818467A (en) * | 2020-06-22 | 2020-10-23 | 北京思特奇信息技术股份有限公司 | Method and system for message notification |
| CN112367241A (en) * | 2020-10-16 | 2021-02-12 | 北京五八信息技术有限公司 | Message generation and message transmission method, device, equipment and computer readable medium |
| CN112367246B (en) * | 2020-10-30 | 2022-06-17 | 深圳壹账通智能科技有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN112437000A (en) * | 2020-11-16 | 2021-03-02 | 平安信托有限责任公司 | Message queue pushing method and device, computer equipment and storage medium |
| CN113590715B (en) * | 2021-07-30 | 2025-01-28 | 工银科技有限公司 | Blockchain-based information push method, device, equipment, medium and program product |
| CN113641474B (en) * | 2021-08-13 | 2024-03-15 | 广州虎牙科技有限公司 | Task scheduling method and device and computer readable storage medium |
| CN113704004B (en) * | 2021-08-30 | 2023-09-29 | 北京百度网讯科技有限公司 | Method, device, equipment and storage medium for realizing notification service |
| CN114513483A (en) * | 2022-01-14 | 2022-05-17 | 上海万物新生环保科技集团有限公司 | Message notification method and device based on service system |
| CN114513762B (en) * | 2022-01-29 | 2024-04-19 | 中国建设银行股份有限公司 | Service processing method, device, electronic equipment and computer readable medium |
-
2022
- 2022-05-19 CN CN202210545184.4A patent/CN114979256B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111835837A (en) * | 2020-06-28 | 2020-10-27 | 中国船舶重工集团公司第七一六研究所 | Message pushing method and system with multi-terminal adaptation |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114979256A (en) | 2022-08-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112311841B (en) | Information pushing method and device, electronic equipment and computer readable medium | |
| CN107491382B (en) | Log output method and device | |
| CN107302597B (en) | Message file pushing method and device | |
| CN111930534A (en) | Data calling method and device and electronic equipment | |
| US12067136B2 (en) | Display method, display device, and electronic device | |
| CN114979256B (en) | Message pushing method and device, electronic equipment and computer readable medium | |
| CN112445868A (en) | Service message processing method and device | |
| CN109218041B (en) | Request processing method and device for server system | |
| CN110704833A (en) | Data permission configuration method, device, electronic device and storage medium | |
| CN108549586B (en) | Information processing method and device | |
| CN110619101B (en) | Method and apparatus for processing information | |
| CN109981546B (en) | Method and device for acquiring remote call relation between application modules | |
| CN111382039A (en) | Method, device, electronic equipment and storage medium for reporting user behavior event | |
| CN110442416B (en) | Method, electronic device and computer-readable medium for presenting information | |
| CN110708238B (en) | Method and apparatus for processing information | |
| CN113282590A (en) | Interface joint debugging method and device based on 5G message | |
| CN112131832A (en) | Method, device and electronic device for reminding task status of online document | |
| CN111314351A (en) | Anti-crawler data processing method and device, electronic equipment and storage medium | |
| CN114253520B (en) | Interface code generation method and device | |
| CN111460020B (en) | Method, device, electronic equipment and medium for resolving message | |
| CN110830662B (en) | Outbound telephone data generation method and device | |
| CN111367592B (en) | Information processing method and device | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN115022266A (en) | Group member adding method, device, equipment and medium | |
| CN113296771A (en) | Page display method, device, equipment and computer readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |