CN113691618A - Message notification method, device, message center and storage medium - Google Patents
Message notification method, device, message center and storage medium Download PDFInfo
- Publication number
- CN113691618A CN113691618A CN202110969828.8A CN202110969828A CN113691618A CN 113691618 A CN113691618 A CN 113691618A CN 202110969828 A CN202110969828 A CN 202110969828A CN 113691618 A CN113691618 A CN 113691618A
- Authority
- CN
- China
- Prior art keywords
- message
- server
- address information
- notification
- content
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
Abstract
The disclosure discloses a message notification method, a message notification device, a message center and a storage medium, and belongs to the technical field of internet. The method comprises the following steps: responding to the resource transfer completion notification, and determining push address information corresponding to a server for any server to be notified by the message to be pushed, wherein the resource transfer completion notification comprises information content to be pushed; determining a message pushing component corresponding to the server based on the pushing address information; based on the message pushing component, acquiring target information content corresponding to the server from the information content to be pushed; and pushing the target information content to the server based on the message pushing component and the pushing address information. According to the scheme, the target information content can be pushed to the server through the message pushing component based on the pushing address information, so that a notification interface of the server is not required to be acquired for development when the information content is pushed, the development process is reduced, and the message pushing efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a message notification method, a message notification apparatus, a message center, and a storage medium.
Background
After the resource transfer is completed, the resource transfer platform needs to push the resource transfer result to other services, so that the other services can perform corresponding operations based on the resource transfer result. For example, after the resource transfer is completed, the resource transfer result needs to be pushed to the account checking service, so that the account checking service checks and corrects the resource value of the account related to the resource transfer service.
In the related technology, different other services provide notification interfaces used by the service, when pushing resource transfer results, the resource transfer platform respectively calls the notification interfaces of each service, generates resource transfer result notifications based on the corresponding notification interfaces, and pushes the resource transfer results to the corresponding other services through the notification interfaces.
In the related art, because the notification interfaces used by different other services are different, the notification interface of each service needs to be compiled each time a message is pushed, and a resource transfer result notification is obtained, so that the resource transfer result can be pushed to other services, and therefore, one service needs to be compiled each time a message is notified, and the development cost is high.
Disclosure of Invention
The embodiment of the disclosure provides a message notification method, a message notification device, a message center and a storage medium, and improves the message pushing efficiency. The technical scheme is as follows:
in one aspect, a message notification method is provided, and the method includes:
responding to a resource transfer completion notification, and determining push address information corresponding to any server to be notified by a message to be pushed, wherein the resource transfer completion notification comprises information content to be pushed;
determining a message pushing component corresponding to the server based on the pushing address information;
based on the message pushing component, acquiring target information content corresponding to the server from the information content to be pushed;
and pushing the target information content to the server based on the message pushing component and the pushing address information.
In another aspect, a message notification apparatus is provided, the apparatus including:
a first determining module, configured to determine, in response to a resource transfer completion notification, push address information corresponding to any server notified by a message to be pushed, where the resource transfer completion notification includes information content to be pushed;
the second determining module is used for determining a message pushing component corresponding to the server based on the pushing address information;
the acquisition module is used for acquiring target information content corresponding to the server from the information content to be pushed based on the message pushing component;
and the pushing module is used for pushing the target information content to the server based on the message pushing component and the pushing address information.
In another aspect, a message center is provided that includes one or more processors and one or more memories having at least one program code stored therein, the at least one program code being loaded and executed by the one or more processors to implement the operations performed by the message notification method as described in the method embodiments of the disclosure.
In another aspect, a non-transitory computer-readable storage medium is provided, in which at least one program code is stored, the at least one program code being loaded and executed by a processor to implement operations performed by a message notification method as described in method embodiments of the present disclosure.
In another aspect, a computer program product or a computer program is provided, the computer program product or the computer program comprising computer program code, the computer program code being stored in a computer readable storage medium. The processor of the terminal reads the computer program code from the computer-readable storage medium, and executes the computer program code, so that the terminal performs the message notification method provided in the various alternative implementations of the above-described aspects.
In the embodiment of the disclosure, the message pushing components are respectively configured for the servers to be notified by the message to be pushed, so that when the target information content is pushed to any server, only the message pushing component corresponding to the server needs to be acquired, and the target information content can be pushed to the server through the message pushing component based on the pushing address information, so that the notification interface of the server does not need to be acquired for development when the information content is pushed, thereby reducing the development process and improving the efficiency of message pushing.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
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 disclosure.
FIG. 1 is a diagram illustrating a system architecture in accordance with one illustrative embodiment of the present disclosure in which a message notification method is implemented;
FIG. 2 is a flow diagram illustrating a message notification method in accordance with an exemplary embodiment;
FIG. 3 is a flow diagram illustrating a method of message notification in accordance with an exemplary embodiment;
FIG. 4 is a flow diagram illustrating a method of message notification in accordance with an exemplary embodiment;
FIG. 5 is a block diagram illustrating a message notification apparatus in accordance with an exemplary embodiment;
fig. 6 is a diagram illustrating a structure of a message center according to an example embodiment.
Detailed Description
To make the objects, technical solutions and advantages of the present disclosure more apparent, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a diagram illustrating a system architecture in accordance with one message notification method, according to an exemplary embodiment of a portion of the present disclosure. The system architecture diagram includes a terminal 10, a resource transfer server 20, a service server 30, and a message center 40. The terminal 10 has a target application installed therein, and the target application is an application for resource transfer. The resource transfer server 20 is a background server for the target application. The service server 30 is a server corresponding to the upstream and downstream services of the resource transfer process. After the resource transfer, the message center 40 sends a message notification to the service server 30 based on the resource transfer result. It should be noted that the message center 40 is a message center 40 integrated in the in-resource transfer server, or the message center 40 is a separate server, which is not particularly limited in the embodiment of the present disclosure.
In response to the resource transfer instruction, the terminal 10 transmits a resource transfer request to the resource transfer server 20, and the resource transfer server 20 performs resource transfer based on the resource transfer request. After the resource transfer is completed, resource transfer information is generated and sent to the message center 40. The message notification is pushed to the service server 30 through the message center 40. The service server 30 notifies the execution of the service corresponding to the service server 30 based on the received message. The resource transfer process can be a resource transfer process for online shopping, online payment, transfer, embodying or credit card repayment and the like through a target application program. For example, the resource transfer process is a transfer process, and the resource transfer information includes a transfer amount, transfer account information, collection account information, and the like. The message center 40 transmits the resource transfer information to the result notification server for transmitting a resource transfer completion notification to the terminal 10. For another example, the resource transfer process is a resource transfer process generated by online shopping, in which a user can use a resource coupon, so that the message center 40 transmits the resource transfer information to a coupon cancellation server for canceling the resource coupon of the account based on the resource transfer information generated by the resource transfer process including coupon use information.
The terminal 10 is a mobile phone, a computer, or a wearable device. The resource transfer server 20, the service server 30, and the message center 40 may be a single server, a server cluster composed of a plurality of servers, or a cloud server, and the like, which is not particularly limited in the embodiment of the present disclosure.
Fig. 2 is a flowchart illustrating a message notification method according to an exemplary embodiment, as shown in fig. 2, the message notification method including the steps of:
step 201: responding to a resource transfer completion notification, and determining push address information corresponding to any server to be notified by a message to be pushed, wherein the resource transfer completion notification comprises information content to be pushed.
Step 202: and determining a message pushing component corresponding to the server based on the pushing address information.
Step 203: and acquiring target information content corresponding to the server from the information content to be pushed based on the message pushing component.
Step 204: and pushing the target information content to the server based on the message pushing component and the pushing address information.
In some embodiments, the obtaining, based on the message pushing component, the target information content corresponding to the server from the information content to be pushed includes:
acquiring a message notification protocol corresponding to the message pushing component;
determining a content field which is allowed to be pushed by the message pushing component based on a message notification protocol of the message pushing component;
and determining target information content corresponding to the content field which is allowed to be pushed by the message pushing component from the resource transfer completion notice to be pushed.
In some embodiments, the method further comprises:
determining content demand information of a plurality of servers to be notified by the push message;
for each piece of content demand information, determining a content field corresponding to each piece of information content in the content demand information;
and generating a message pushing component corresponding to the server based on a message notification protocol and a content field corresponding to the content demand information.
In some embodiments, the determining push address information corresponding to the server includes:
acquiring a message notification template corresponding to the server; analyzing the message notification template to obtain push address information corresponding to the server; alternatively, the first and second electrodes may be,
acquiring an address information list; and analyzing the address information list to obtain at least one piece of push address information.
In some embodiments, the method further comprises:
responding to the received server adding request, and acquiring the push address information of the server to be added;
and adding the server to be added into the address information list based on the push address information of the server to be added.
In some embodiments, the determining, based on the push address information, a message push component corresponding to the server includes:
analyzing the pushed address information to obtain a component identifier;
and acquiring a message pushing component corresponding to the component identification.
In some embodiments, after the pushing the target information content to the server based on the message component and the push address information, the method further comprises:
and responding to the push failure notification, and re-executing the step of determining the push address information corresponding to the server until the target information content is successfully transmitted.
In some embodiments, the method further comprises:
generating a push failure notification in response to receiving a reception failure message sent by the server; alternatively, the first and second electrodes may be,
and generating a push failure notice in response to not receiving the receiving notice result within the preset time.
In the embodiment of the disclosure, the message pushing components are respectively configured for the servers to be notified by the message to be pushed, so that when the target information content is pushed to any server, only the message pushing component corresponding to the server needs to be acquired, and the target information content can be pushed to the server through the message pushing component based on the pushing address information, so that the notification interface of the server does not need to be acquired for development when the information content is pushed, thereby reducing the development process and improving the efficiency of message pushing.
Fig. 3 is a flowchart illustrating a message notification method according to an exemplary embodiment, as shown in fig. 3, the message notification method including the steps of:
step 301: and responding to the resource transfer completion notification, and for any server to be notified by the push message, the message center determines push address information corresponding to the server.
The resource transfer completion notification includes information content to be pushed. The any server is a service server for performing other services based on the resource transfer completion notification. In some embodiments, the message center stores a server identification of a server to be notified by the push message, and determines, in response to the resource transfer completion notification, the server to be notified by the push message based on the stored server identification. In some embodiments, the resource transfer completion notification carries a server identifier of a server to be notified by a push message, and in response to receiving the resource transfer completion notification, the server to be notified by the push message is determined based on the server identifier carried by the resource transfer completion notification.
The push address information is a push address of the server. For each server, the server is configured with corresponding push address information, and the push address information is used for the message center to send message content to be pushed to the corresponding server based on the push address information. In some embodiments, the push address information is push address information determined based on a message notification template. Correspondingly, the process of determining the push address information by the message center is as follows: the message center acquires a message notification template corresponding to the server; and analyzing the message notification template to obtain the push address information corresponding to the server.
The message notification template is a message notification template corresponding to the server. Accordingly, the message center stores a plurality of message notification templates. In this step, the message center determines a message notification template to be analyzed from a plurality of stored message notification templates based on the correspondence between the server identifier and the message notification template according to the server identifier of the server to be notified of the message, and analyzes the message notification template to obtain the push address information of the server.
Referring to fig. 4, after receiving the resource transfer completion notification, the message center determines to accept the push service corresponding to the resource transfer completion notification. The message center obtains the message notification template and analyzes the message notification template to obtain an analysis result. Wherein, the analysis result includes the push address information. The analysis result may include account information related to the resource transfer, priority information of the resource transfer completion notification, other configuration information, and the like.
Correspondingly, before the step, the message center acquires the message notification template of each server. In some embodiments, for each server, the server obtains configuration content of the message notification template, generates the message notification template based on the configuration content, sends the generated notification template to the message center, and the message center receives the message notification template sent by the server and stores the message notification template and the server identifier correspondingly.
In the implementation mode, the message notification template is analyzed by acquiring the message notification template corresponding to the server to obtain the push address information, so that the efficiency of acquiring the message push address is improved, and the efficiency of message notification is further improved.
In some embodiments, the message center obtains a list of address information; and analyzing the address information list to obtain at least one piece of push address information.
In this implementation, the message center stores an address information list. The address information list includes the corresponding relationship between the push address information of the server and the server identifier. And after receiving the resource transfer completion notification, the message center determines to accept the push service corresponding to the resource transfer completion notification. And calling the stored address information list, determining the service identifier of the server to be notified by the push message, and determining the push address information corresponding to the server identifier from the address information list according to the server identifier.
When a new server is added to the resource transfer system, the push address information of the newly added server is added to the address list. The process is as follows: in response to receiving a server adding request, the message center acquires push address information of a server to be added; and adding the server to be added into the address information list based on the pushed address information of the server to be added.
In the implementation mode, when a new server is added, the pushed address information of the added server needs to be sent to the message center, and the pushed address information is added to the address information list through the message center, so that the process of adding the new server is simplified.
In addition, the message center can quickly search the pushed address information based on the address information list by storing the pushed address information in the form of the address information list, so that the efficiency of determining the pushed address information by the message center is improved, and the message notification efficiency is further improved.
Step 302: and the message center determines a message pushing component corresponding to the server based on the pushing address information.
The push address information comprises a component identifier, and the message center can determine a message push component corresponding to the server based on the component identifier. The process is as follows: the message center analyzes the pushed address information to obtain a component identifier; the acquisition component identifies the corresponding message push component.
In the implementation mode, the message pushing component is determined through the component identification in the pushing address information, so that the accuracy of determining the message pushing component is improved.
The push address information includes information such as protocol form information, service information corresponding to the server, and component identification. For example, the format of the push address information is: thrift/http/… appkey port/version. The third/http is a prefix of a push address, and represents protocol form information, for example, if the protocol form information is third, it is determined that the message notification protocol is a third protocol, and if the protocol form information is http, it is determined that the message notification protocol is an http protocol. The Appkey is used to locate the service on line in the message center, and the port is used to determine the corresponding interface method. Version is a component identifier of a message pushing component corresponding to the server, and in some embodiments, the component identifier includes a Version number of the message pushing component, and is used for notifying Version isolation after content upgrading of the message center, distinguishing an encryption scheme, and the like. For example, the push address information is: and (3) thick: // com. xxxx. pay. xx.com: 1658/1.0.
Before the step, the message center generates a message pushing component corresponding to each server based on each server. The message pushing component may be an SDK (Software Development Kit) for pushing resource transfer completion notifications to each server. The message center generates a message pushing component corresponding to each server according to message content and a message notification protocol required by each server, and in the step, the message center calls the message component corresponding to the server. The process of generating the message pushing component by the message center is realized by the following steps (1) to (3), and comprises the following steps:
(1) the message center determines content demand information for a plurality of servers to be notified by the push message.
Different servers correspond to different services, and because different services have different content demand information, in this step, the message center determines the content demand information of the server based on the services corresponding to different servers. For example, the server is a message notification server, that is, a server for pushing a message such as completion of resource transfer to the terminal. The content requirement information of the server includes information contents such as a resource transfer value, an account number involved in resource transfer, resource transfer time, and the like. For another example, the server is a coupon cancellation server, that is, a server for canceling a coupon used by a user in the resource transfer process. The content requirement information of the server includes information content such as whether to use the coupon in the resource transfer process, identification of the used coupon, and the like.
(2) For each content demand information, the message center determines a content field corresponding to each information content in the content demand information.
The resource transfer completion notification is composed of a plurality of content fields, and based on the message notification protocol, the content fields representing different information contents are added to the field positions specified by the message notification protocol to obtain the resource transfer completion notification. In this step, the message center determines, based on each information content in the content requirement information, a corresponding content field of the information content in the resource transfer completion notification.
(3) And the message center generates a message pushing component corresponding to the server based on the message notification protocol and the content field corresponding to the content demand information.
In this step, the message center determines, based on the message notification protocol, a field identifier of a content field corresponding to the content requirement information in the resource transfer completion notification, and generates, based on the field identifier, a message pushing component corresponding to the server. Wherein, the field identification is an identification which uniquely identifies the content field based on the message notification protocol. For example, the field identification is field location information of the content field in the message completion notification, and the like.
For example, for a content field corresponding to the content requirement information, a field position corresponding to the content field is marked as a first numerical value, and field positions corresponding to other content fields are marked as second numerical values. Wherein the first value is different from the second value. For example, the first value is 1, the second value is 0, and so on.
In the implementation manner, a content field corresponding to the content demand information of each server is determined in advance, and then a message pushing component corresponding to the server is generated according to the content field, so that the message pushing component is called later, and related information content is pushed to the server based on the message pushing component.
Step 303: and the message center acquires a message notification protocol corresponding to the message pushing component.
Wherein, the message notification protocol corresponding to the push component indicates the protocol version used by the message push component. In some embodiments, the message center parses the push address information to obtain a message notification protocol corresponding to the message push component. In this implementation manner, the message center caches the analysis result of the push address information, and in this step, the message notification protocol corresponding to the message push component is obtained from the cache. In some embodiments, the message center acquires component information of the message pushing component, and acquires a message notification protocol corresponding to the message pushing component from the component information.
Step 304: the message center determines the content fields that the message pushing component allows for pushing based on the message notification protocol.
In this step, the message center determines field location tag information corresponding to the message pushing component, and determines a content field that the message pushing component allows to push based on the message notification protocol and the field location tag information.
For example, the message notification protocol specifies that the field position of the content field allowed to be pushed is marked as 1, and the other field positions are marked as 0, in this step, the message center determines that the content field with the field position identification information of 1 is the content field allowed to be pushed by the message pushing component.
Step 305: and the message center determines the target information content corresponding to the content field which is allowed to be pushed by the message pushing component from the resource transfer completion notice to be pushed.
In this step, the message center obtains the field content of the field based on the content field that the message pushing component allows to push, and obtains the target information content.
Step 306: and the message center pushes the target information content to the server based on the message pushing component and the pushing address information.
In this step, with continued reference to fig. 4, the message center adds the target message content to the message notification template to obtain a notification message pushed to the server, and pushes the target information content carried in the notification message to the server through the message pushing function of the message pushing component.
In the implementation mode, the target information content is packaged in the message pushing component for pushing, message notification and logic processing decoupling is achieved, the message content is fixed but logic processing is customized, and therefore notification dynamic access is achieved, the effect of customized processing is achieved, and meanwhile maintenance cost of message pushing is reduced.
It should be noted that, after receiving the target information content pushed by the message center, the server feeds back a notification result to the message center. In response to the push failure notification, the message center again performs step 301 to push the target information content to the server based on the message component and the push address information.
In the implementation mode, retry is carried out after the message pushing fails, and the message loss is prevented.
The pushing failure notification includes receiving a notification generated by a reception failure message, or receiving no notification generated by a notification result within a preset time. Accordingly, in response to receiving the reception failure message sent by the server, the message center generates a push failure notification. Continuing to refer to fig. 4, wherein the message center receives the notification result fed back by the server, analyzes the notification result to obtain an analysis result, and determines that the target information content fails to be pushed in the case that the analysis result is a reception failure message; and determining that the target information content is successfully pushed under the condition that the analysis result is the successful receiving message.
Or, in response to not receiving the reception notification result within the preset time, the message center generates a push failure notification. And after the message center pushes the target information content, timing is started, and if a notification result fed back by the server is not received within a preset time, the failure of pushing the target information content is determined. The preset time is set according to needs, and in the embodiment of the present application, the preset time is not specifically limited.
In the implementation mode, whether the notification message is successfully sent or not is verified in multiple modes, so that the comprehensiveness of verification is improved, and the accuracy of whether the notification of the notification message is successfully sent or not is improved.
It should be noted that, the number of servers to be notified by the push message is set according to needs, and this is not particularly limited in the embodiment of the present disclosure. And if the number of the servers to be notified by the message to be pushed is multiple, pushing the message notification to the multiple servers respectively. In some embodiments, the message center pushes message notifications to the multiple servers simultaneously. In some embodiments, the message center pushes message notifications to the plurality of servers in sequence. The order in which the message center sequentially pushes the message notifications to the plurality of servers is set according to needs, which is not specifically limited in this embodiment of the application. For example, the message center pushes message notifications to multiple servers in a random order. Alternatively, the message center pushes the message notifications to the plurality of servers in the order of addition of the servers. In addition, for each server, the process of the message center pushing the message notification to the server is implemented by step 301 and step 306, which are not described herein again.
In the embodiment of the disclosure, the message pushing components are respectively configured for the servers to be notified by the message to be pushed, so that when the target information content is pushed to any server, only the message pushing component corresponding to the server needs to be acquired, and the target information content can be pushed to the server through the message pushing component based on the pushing address information, so that the notification interface of the server does not need to be acquired for development when the information content is pushed, thereby reducing the development process and improving the efficiency of message pushing.
Fig. 5 is a block diagram illustrating a message notification apparatus according to an example embodiment, as shown in fig. 5, the message notification apparatus including:
a first determining module 501, configured to determine, in response to a resource transfer completion notification, for any server notified by a message to be pushed, push address information corresponding to the server, where the resource transfer completion notification includes information content to be pushed;
a second determining module 502, configured to determine, based on the push address information, a message push component corresponding to the server;
a first obtaining module 503, configured to obtain, based on the message pushing component, a target information content corresponding to the server from the information content to be pushed;
a pushing module 504, configured to push the target information content to the server based on the message pushing component and the pushing address information.
In some embodiments, the first obtaining module 503 includes:
a first obtaining unit, configured to obtain a message notification protocol corresponding to the message pushing component;
a first determining unit, configured to determine, based on a message notification protocol of the message pushing component, a content field that the message pushing component allows to be pushed;
a second determining unit, configured to determine, from the notification of completing the resource transfer to be pushed, a target information content corresponding to a content field that the message pushing component allows pushing.
In some embodiments, the apparatus further comprises:
the third determining module is used for determining content demand information of a plurality of servers to be notified by the push message;
the fourth determining module is used for determining a content field corresponding to each information content in the content demand information for each content demand information;
and the first generation module is used for generating a message pushing component corresponding to the server based on the message notification protocol and the content field corresponding to the content demand information.
In some embodiments, the first determining module 501 includes:
a second obtaining unit, configured to obtain a message notification template corresponding to the server; analyzing the message notification template to obtain the push address information corresponding to the server; alternatively, the first and second electrodes may be,
a third obtaining unit, configured to obtain an address information list; and analyzing the address information list to obtain at least one piece of push address information.
In some embodiments, the apparatus further comprises:
the second acquisition module is used for responding to the received server adding request and acquiring the push address information of the server to be added;
and the adding module is used for adding the server to be added into the address information list based on the push address information of the server to be added.
In some embodiments, the second determining module 502 includes:
the analysis unit is used for analyzing the push address information to obtain a component identifier;
and the fourth acquisition unit is used for acquiring the message pushing component corresponding to the component identifier.
In some embodiments, the first determining module 501 is further configured to re-determine, in response to the push failure notification, the push address information corresponding to the server until the target information content is successfully sent.
In some embodiments, the apparatus further comprises:
the second generation module is used for responding to the received receiving failure message sent by the server and generating a pushing failure notice; alternatively, the first and second electrodes may be,
and the third generating module is used for responding to the situation that the receiving notification result is not received in the preset time and generating the pushing failure notification.
In the embodiment of the disclosure, the message pushing components are respectively configured for the servers to be notified by the message to be pushed, so that when the target information content is pushed to any server, only the message pushing component corresponding to the server needs to be acquired, and the target information content can be pushed to the server through the message pushing component based on the pushing address information, so that the notification interface of the server does not need to be acquired for development when the information content is pushed, thereby reducing the development process and improving the efficiency of message pushing.
It should be noted that: the message notification apparatus provided in the foregoing embodiment only exemplifies the division of the above functional modules when notifying a message, and in practical applications, the above function allocation may be completed by different functional modules according to needs, that is, the internal structure of the terminal is divided into different functional modules to complete all or part of the above described functions. In addition, the message notification apparatus and the message notification method provided in the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments and are not described herein again.
Fig. 6 is a schematic structural diagram of a message center according to an embodiment of the present disclosure, where the message center 600 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 601 and one or more memories 602, where the memory 602 stores at least one instruction, and the at least one instruction is loaded and executed by the processor 601 to implement the message notification method provided by the foregoing method embodiments. Certainly, the message center 600 may further include components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input and output, and the message center 600 may further include other components for implementing functions of the device, which is not described herein again.
In some embodiments, a computer-readable storage medium is further provided, in which at least one program code is stored, and the at least one program code is loaded and executed by the terminal to implement the message notification method in the above embodiments. The computer readable storage medium may be a memory. For example, the computer-readable storage medium may be a ROM (Read-Only Memory), a RAM (Random Access Memory), a CD-ROM (Compact Disc Read-Only Memory), a magnetic tape, a floppy disk, an optical data storage device, and the like.
In some embodiments, a computer program product or computer program is provided, the computer program product or computer program comprising computer program code stored in a computer readable storage medium. The processor of the terminal reads the computer program code from the computer-readable storage medium, and executes the computer program code, so that the terminal performs the message notification method provided in the various alternative implementations of the above-described aspects.
In some embodiments, the computer program according to the embodiments of the present application may be deployed to be executed on one computer device or on multiple computer devices located at one site, or may be executed on multiple computer devices distributed at multiple sites and interconnected by a communication network, and the multiple computer devices distributed at the multiple sites and interconnected by the communication network may constitute a block chain system
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above disclosure is intended to cover alternative embodiments of the disclosure, and not to limit the disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.
Claims (11)
1. A message notification method, the method comprising:
responding to a resource transfer completion notification, and determining push address information corresponding to any server to be notified by a message to be pushed, wherein the resource transfer completion notification comprises information content to be pushed;
determining a message pushing component corresponding to the server based on the pushing address information;
based on the message pushing component, acquiring target information content corresponding to the server from the information content to be pushed;
and pushing the target information content to the server based on the message pushing component and the pushing address information.
2. The method according to claim 1, wherein the obtaining, based on the message pushing component, the target information content corresponding to the server from the information content to be pushed comprises:
acquiring a message notification protocol corresponding to the message pushing component;
determining a content field which is allowed to be pushed by the message pushing component based on a message notification protocol of the message pushing component;
and determining target information content corresponding to the content field which is allowed to be pushed by the message pushing component from the resource transfer completion notice to be pushed.
3. The method of claim 2, further comprising:
determining content demand information of a plurality of servers to be notified by the push message;
for each piece of content demand information, determining a content field corresponding to each piece of information content in the content demand information;
and generating a message pushing component corresponding to the server based on a message notification protocol and a content field corresponding to the content demand information.
4. The method of claim 1, wherein the determining push address information corresponding to the server comprises:
acquiring a message notification template corresponding to the server; analyzing the message notification template to obtain push address information corresponding to the server; alternatively, the first and second electrodes may be,
acquiring an address information list; and analyzing the address information list to obtain at least one piece of push address information.
5. The method of claim 4, further comprising:
responding to the received server adding request, and acquiring the push address information of the server to be added;
and adding the server to be added into the address information list based on the push address information of the server to be added.
6. The method of claim 1, wherein the determining a message pushing component corresponding to the server based on the pushing address information comprises:
analyzing the pushed address information to obtain a component identifier;
and acquiring a message pushing component corresponding to the component identification.
7. The method of claim 1, wherein after the pushing the target information content to the server based on the message component and the push address information, the method further comprises:
and in response to the push failure notification, re-executing the step of determining the push address information corresponding to the server until the step of successfully transmitting the target information content.
8. The method of claim 7, further comprising:
generating a push failure notification in response to receiving a reception failure message sent by the server; alternatively, the first and second electrodes may be,
and generating a push failure notice in response to not receiving the receiving notice result within the preset time.
9. A message notification apparatus, characterized in that the apparatus comprises:
a first determining module, configured to determine, in response to a resource transfer completion notification, push address information corresponding to any server notified by a message to be pushed, where the resource transfer completion notification includes information content to be pushed;
the second determining module is used for determining a message pushing component corresponding to the server based on the pushing address information;
the acquisition module is used for acquiring target information content corresponding to the server from the information content to be pushed based on the message pushing component;
and the pushing module is used for pushing the target information content to the server based on the message pushing component and the pushing address information.
10. A message center, characterized in that the message center comprises one or more processors and one or more memories having stored therein at least one program code, which is loaded and executed by the one or more processors to implement the operations executed by the message notification method according to any one of claims 1 to 8.
11. A non-transitory computer-readable storage medium having stored therein at least one program code, the at least one program code being loaded into and executed by a processor to perform operations performed by the message notification method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110969828.8A CN113691618B (en) | 2021-08-23 | 2021-08-23 | Message notification method, device, message center and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110969828.8A CN113691618B (en) | 2021-08-23 | 2021-08-23 | Message notification method, device, message center and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113691618A true CN113691618A (en) | 2021-11-23 |
| CN113691618B CN113691618B (en) | 2022-07-15 |
Family
ID=78581505
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110969828.8A Active CN113691618B (en) | 2021-08-23 | 2021-08-23 | Message notification method, device, message center and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113691618B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114374697A (en) * | 2022-01-14 | 2022-04-19 | 瀚云科技有限公司 | System and method for pushing road vehicle passing information, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007109986A1 (en) * | 2006-03-27 | 2007-10-04 | Alibaba Group Holding Limited | Message reliable informing method and apparatus between systems |
| CN105978788A (en) * | 2016-04-27 | 2016-09-28 | 努比亚技术有限公司 | Message pushing device and method thereof |
| CN111371847A (en) * | 2020-02-21 | 2020-07-03 | 杭州数梦工场科技有限公司 | Payment message notification system, service server and payment server |
| CN112288556A (en) * | 2019-07-10 | 2021-01-29 | 腾讯科技（深圳）有限公司 | Method and device for resource transfer, and method and device for initiating resource transfer |
| CN112367246A (en) * | 2020-10-30 | 2021-02-12 | 深圳壹账通智能科技有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN112967043A (en) * | 2021-03-30 | 2021-06-15 | 北京三快在线科技有限公司 | Resource transfer method, device, equipment and storage medium |
-
2021
- 2021-08-23 CN CN202110969828.8A patent/CN113691618B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007109986A1 (en) * | 2006-03-27 | 2007-10-04 | Alibaba Group Holding Limited | Message reliable informing method and apparatus between systems |
| CN105978788A (en) * | 2016-04-27 | 2016-09-28 | 努比亚技术有限公司 | Message pushing device and method thereof |
| CN112288556A (en) * | 2019-07-10 | 2021-01-29 | 腾讯科技（深圳）有限公司 | Method and device for resource transfer, and method and device for initiating resource transfer |
| CN111371847A (en) * | 2020-02-21 | 2020-07-03 | 杭州数梦工场科技有限公司 | Payment message notification system, service server and payment server |
| CN112367246A (en) * | 2020-10-30 | 2021-02-12 | 深圳壹账通智能科技有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN112967043A (en) * | 2021-03-30 | 2021-06-15 | 北京三快在线科技有限公司 | Resource transfer method, device, equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114374697A (en) * | 2022-01-14 | 2022-04-19 | 瀚云科技有限公司 | System and method for pushing road vehicle passing information, electronic equipment and storage medium |
| CN114374697B (en) * | 2022-01-14 | 2024-03-01 | 瀚云科技有限公司 | Road passing information pushing system, method, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113691618B (en) | 2022-07-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107784552B (en) | Information push task execution method and device, computer equipment and storage medium | |
| CN110602056B (en) | Service parameter transmission method and device | |
| CN112948835B (en) | Applet risk detection method and device | |
| CN109819023B (en) | Distributed transaction processing method and related product | |
| CN111694797A (en) | File uploading and analyzing method, device, server and medium | |
| CN113806037A (en) | Service calling method and device, storage medium and electronic equipment | |
| CN111597110A (en) | Page testing method and device, electronic equipment and storage medium | |
| CN107368334B (en) | Business plug-in interaction system and method | |
| CN113691618B (en) | Message notification method, device, message center and storage medium | |
| CN116668520A (en) | Gateway-based service arrangement method, system, equipment and storage medium | |
| CN114301970B (en) | Service calling method, device, electronic equipment and storage medium | |
| CN111488286B (en) | Method and device for independently developing Android modules | |
| CN112732547B (en) | Service testing method and device, storage medium and electronic equipment | |
| CN109194734B (en) | Message pushing method and device, server and readable storage medium | |
| CN113268360A (en) | Request processing method, device, server and storage medium | |
| CN112558950A (en) | System interface generation method and device | |
| CN109086145B (en) | Data generation method and device and computer storage medium | |
| CN111611065A (en) | Calling method and device of machine learning algorithm, storage medium and electronic equipment | |
| CN111078571A (en) | Test method for simulation response, terminal device and computer readable storage medium | |
| CN115794927B (en) | Service function expansion method and system | |
| CN113852627B (en) | Extensible payment message processing method and device and electronic equipment | |
| CN111131471B (en) | Operation method and device of service system and electronic equipment | |
| CN111381985B (en) | Heterogeneous system data calling method, device, equipment and storage medium | |
| CN116126714A (en) | Data acceptance method, device, electronic equipment and computer storage medium | |
| CN115964287A (en) | Message testing method, device, equipment and storage 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 |