CN114363408A - Information pushing method and device, computer readable medium and computer equipment - Google Patents
Information pushing method and device, computer readable medium and computer equipment Download PDFInfo
- Publication number
- CN114363408A CN114363408A CN202111666535.9A CN202111666535A CN114363408A CN 114363408 A CN114363408 A CN 114363408A CN 202111666535 A CN202111666535 A CN 202111666535A CN 114363408 A CN114363408 A CN 114363408A
- Authority
- CN
- China
- Prior art keywords
- information
- pushing
- push
- requester
- information 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.)
- Withdrawn
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The present disclosure relates to an information push method, an information push apparatus, a computer readable medium, and a computer device, wherein the method comprises: receiving information pushing requests sent by all the service modules, wherein the information pushing requests comprise requesting parties and pushing channels, generating different types of information pushing tasks according to different pushing channels, and executing the information pushing tasks to push information to the requesting parties, wherein the types correspond to the pushing channels. The unified gateway interface protocol with the interfaces connected with different service modules and different channels is provided, information of different service modules and different channels is pushed in a unified mode, data generated in the information pushing process are recorded, unified storage and management of the data are facilitated, when the channel gateway interface protocol of each service line is modified or service is upgraded, repeated development of research and development maintenance personnel is avoided, and labor cost is saved.
Description
Technical Field
The present disclosure relates to the field of information notification, and in particular, to an information pushing method, an information pushing apparatus, a computer-readable medium, and a computer device.
Background
In the current internet environment, when a user uses various application servers, the user often receives various information pushes from different channels of each service line of the system. The information push may be verification code push in user registration and login links, and may also be security confirmation information push in ordering links; for example, common channels for pushing information include WeChat, flybook, SMS, and email. In order to implement information push in various channels, the application server needs to communicate with interface protocols in different channels, which may be different, for example, the Mail uses Simple Mail Transfer Protocol (SMTP), and the micro-messaging uses a Hypertext Transfer Protocol (HTTP) short connection and a Transmission Control Protocol (TCP) long connection. Therefore, in the existing information push, each service line needs to be connected with different interface protocols, information in different channels is separately pushed, which is tedious, and when a gateway interface protocol is modified or service is upgraded, research and development maintenance personnel of all service lines need to synchronously modify or upgrade, which consumes manpower, and data management and storage are scattered.
Disclosure of Invention
The present disclosure aims to provide an information pushing method, an information pushing apparatus, a computer readable medium, and a computer device, which are used to solve the problems of a cumbersome information pushing process caused by non-uniform gateway interface protocols of different service lines and different channels, and a high cost caused by repeated development when a channel gateway interface protocol of each service line is modified or a service is upgraded.
In a first aspect, the present disclosure provides an information pushing method, including: receiving information pushing requests sent by all service modules; the information pushing request comprises a requesting party and a pushing channel; based on the history record in the information pushing log, filtering the received information pushing request, and keeping the effective information pushing request; generating different types of information pushing tasks according to different pushing channels aiming at the effective information pushing request; wherein the type corresponds to the push channel; and executing the information pushing task to push information to the requester.
Optionally, the method further comprises: and performing data conversion on the information of at least one requester to generate an encrypted character string corresponding to the requester.
Optionally, the filtering the received information pushing request based on the history record in the information pushing log includes: respectively acquiring information of a requester contained in each information pushing request; counting the times of the information push requests sent by the same requester in a specified time period in the history record of the information push log; and if the number of times of the information push requests sent by the same requester in the specified time period is less than or equal to a preset threshold value, determining the information push requests sent by the requester as valid information push requests.
Optionally, the information push request further includes service type information, and after the step of receiving the information push request sent by each service module, the method further includes: respectively acquiring the information of the service type corresponding to the requester in each information push request; and if the service type corresponding to the requester is not suitable for the corresponding service module, determining the information push request sent by the requester as an invalid information push request.
Optionally, the step of generating different types of information push tasks according to different push channels includes: calling an information pushing template corresponding to the pushing channel according to the information pushing request, wherein the information pushing template comprises pushing format information suitable for the pushing channel; and generating an information pushing task based on the information pushing request and the corresponding information pushing template.
Optionally, the step of sending the information push content in the corresponding information push template to the requester includes: determining a corresponding sender thread according to the type of the information pushing task; and sending the information push content in the information push template to the requester through the sender thread.
Optionally, after the step of executing the information pushing task to push information to the requester, the method further includes: receiving a result of pushing information to the requester; the result comprises push success or push failure; recording the result of pushing information to generate an information pushing log; the log comprises at least one of the result, the information of the requester, the information pushing task, an information pushing template, information pushing time and information pushing duration.
Optionally, the method further comprises: and storing the information push log into a database.
In a second aspect, the present disclosure provides an information pushing apparatus, including: the receiving module is used for receiving the information pushing requests sent by the service modules; the information pushing request comprises a requesting party and a pushing channel; the filtering module is used for filtering the received information pushing request based on the history record in the information pushing log and reserving an effective information pushing request; the processing module is used for generating different types of information pushing tasks according to different pushing channels aiming at the effective information pushing request; wherein the type corresponds to the push channel; and the execution module is used for executing the information pushing task so as to push information to the requester.
In a third aspect, the present disclosure provides a computer-readable medium, on which a computer program is stored, which, when being executed by a processing apparatus, realizes the steps of the aforementioned information push method.
In a fourth aspect, the present disclosure provides a computer device comprising: a storage device having a computer program stored thereon; and the processing device is used for executing the computer program in the storage device so as to realize the steps of the information pushing method.
According to the technical scheme, the application server receives information pushing requests sent by all the service modules, the information pushing requests comprise requesters and pushing channels, different types of information pushing tasks are generated according to the different pushing channels, the types correspond to the pushing channels, and the information pushing tasks are executed so as to push information to the requesters. The unified gateway interface protocol with the interfaces connected with different service modules and different channels is provided, information of different service modules and different channels is pushed in a unified mode, data generated in the information pushing process are recorded, unified storage and management of the data are facilitated, when the channel gateway interface protocol of each service line is modified or service is upgraded, repeated development of research and development maintenance personnel is avoided, and labor cost is saved.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale. In the drawings:
fig. 1 is a schematic structural diagram of a computer system provided in an exemplary embodiment of the present disclosure.
Fig. 2 is a flowchart of an information pushing method according to an exemplary embodiment of the present disclosure.
Fig. 3 is a flowchart of another information pushing method according to an exemplary embodiment of the present disclosure.
Fig. 4 is a flowchart of sub-steps of step S305 provided by an exemplary embodiment of the present disclosure.
Fig. 5 is a block diagram of an information pushing apparatus according to an exemplary embodiment of the present disclosure.
FIG. 6 illustrates a block diagram of an electronic device in accordance with an exemplary embodiment.
FIG. 7 is a block diagram illustrating another electronic device in accordance with an example embodiment.
Description of the reference numerals
120-a terminal; 140-application server; 20-an information pushing device; 201-a receiving module; 203-a processing module; 204-a filter module; 205-an execution module; 400-an electronic device; 401-a processor; 402-a memory 403; -a multimedia component; 404-input/output (I/O) interface; 405-a communication component; 500-an electronic device; 522-a processor; 532-a memory; 526-power supply components; 550-a communication component; 558-input/output (I/O) interface.
Detailed Description
The following detailed description of specific embodiments of the present disclosure is provided in connection with the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present disclosure, are given by way of illustration and explanation only, not limitation.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Fig. 1 shows a schematic structural diagram of a computer system provided by an exemplary embodiment of the present disclosure, which includes a terminal 120 and an application server 140.
The terminal 120 and the application server 140 are connected to each other through a wired or wireless network.
The terminal 120 may include at least one of a smartphone, a laptop, a desktop, a tablet, a smart speaker, and a smart robot.
The terminal 120 includes a display; the display is used for displaying the information pushed by the application server 140.
The terminal 120 includes a first memory and a first processor. The first memory stores a first program; the first program is called and executed by the first processor to display the information pushed by the application server 140. The first memory may include, but is not limited to, the following: random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Read-Only Memory (EPROM), and electrically Erasable Read-Only Memory (EEPROM).
The first processor may be comprised of one or more integrated circuit chips. Alternatively, the first Processor may be a general purpose Processor, such as a Central Processing Unit (CPU) or a Network Processor (NP).
The application server 140 includes a second memory and a second processor. The second memory stores a second program, and the second program is called by the second processor to implement the information pushing method provided by the present disclosure. Optionally, the second memory may include, but is not limited to, the following: RAM, ROM, PROM, EPROM, EEPROM. Alternatively, the second processor may be a general purpose processor, such as a CPU or NP.
The application server may be at least one of a notebook computer, a desktop computer, a tablet computer, an intelligent sound box and an intelligent robot, may be an independent physical server, and may also be a server cluster or a distributed system formed by a plurality of physical servers. The terminal may be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like. The terminal and the application server may be directly or indirectly connected through wired or wireless communication, and the disclosure is not limited herein.
Illustratively, the application server is provided with a server of a business system, the server can provide various businesses, for example, a sky-eye search system for querying enterprise information, the businesses provided by the sky-eye search system may include, but are not limited to, registration, login, enterprise query, and the like, and the business system may push information to a user terminal queried by using the business system when needed. The terminal can be provided with applications such as WeChat, flybook, short message and mail, the applications can receive information pushed by a business system on the application server side, and the terminal can be provided with a client of the business system for a user to use.
Referring to fig. 2, fig. 2 is a flowchart of an information pushing method according to an exemplary embodiment of the disclosure. The method is performed by a computer device, for example, by an application server in the computer system shown in fig. 1. The information pushing method shown in fig. 2 includes the following steps:
in step S201, an information push request sent by each service module is received.
The business module refers to each functional module of the business system, such as a sky-eye searching system comprising a query module, a financial module and other functional modules. The information push request comprises a requester and a push channel.
The requesting party is a user account using the service system, when the user uses the service system on the terminal, the user will firstly communicate with the service system of the application server, and at this time, the service system of the application server obtains the user account, and the user account includes an account id of the user and an account name of the user.
For example, when a user logs in a sky-eye check at a mobile phone terminal, the sky-eye check server needs to send an authentication short message to the user mobile phone terminal, a requesting party is an account of the user mobile phone terminal, and a requested party is the sky-eye check server. For another example, the requesting party may be the terminal in fig. 1, and the requested party may be the application server in fig. 1.
The push channel in the information push request refers to a push channel of the user terminal, and the user terminal refers to a terminal used by the user account. The push channel of the user terminal can be a channel such as a mailbox, a short message and a WeChat, and the push channel can be obtained according to information of a requesting party, for example, if a user logs in a service system by using a mailbox account, the obtained user account is the mailbox of the user, for example, if the user logs in the service system by using a WeChat account, the obtained user account is the WeChat of the user. The requested party, namely the service system server can determine a corresponding push channel according to the user account.
In step S202, based on the history in the information push log, filtering the received information push request, and retaining the valid information push request therein;
in step S203, different types of information push tasks are generated according to different push channels.
Illustratively, the push channel may be a channel such as a mailbox, a short message, a WeChat, and then call an information push template corresponding to each channel such as the mailbox, the short message, the WeChat, and the like to generate an information push task. The information pushing template comprises specific information format information, wherein the information format information specifically comprises text content, theme type, text style and the like.
Illustratively, the push channel is WeChat, and the service system calls an information push template corresponding to the WeChat to generate an information push task corresponding to the WeChat. If the pushing channel is a mailbox, the service system calls an information pushing template corresponding to the mailbox to generate an information pushing task corresponding to the mailbox channel.
In step S204, an information push task is performed to push information to the requester.
And determining a corresponding information pushing template according to the information pushing task, and then sending the information format information in the corresponding information pushing template to the requester.
Referring to fig. 3, fig. 3 is a flowchart illustrating another information pushing method according to an exemplary embodiment of the disclosure. The method is performed by a computer device, for example, a terminal or a server in the computer system shown in fig. 1.
It should be noted that the content of the information pushing method shown in fig. 3 is the same as the content of the information pushing method shown in fig. 2, and the parts that are not mentioned in fig. 3 may refer to the description of fig. 2, and are not described again here. The information pushing method shown in fig. 3 includes the following steps:
in step S301, an information push request sent by each service module is received.
The information push request includes the aforementioned requester and the push channel, and the details which are not mentioned above can be referred to the foregoing description, and are not described herein again.
For example, the RPC protocol may be called to receive an information push request sent by each service module. The rpc (remote procedure call) protocol is a remote procedure call protocol, which is a protocol that requests services from remote computer programs over a network without knowledge of the underlying network technology. The RPC Protocol assumes the existence of some Transmission protocols, such as Transmission Control Protocol (TCP) or User Datagram Protocol (UDP), for carrying information data between communication programs. In the Open System Interconnection Reference Model (OSI), RPC spans the transport layer and the application layer. RPC makes it easier to develop applications including network distributed multiprogrammers. RPC protocol calls refer to process communication between different machines, and programs do not need to care about which machine a certain remote service is executed on, and remote service calls are the same as local service calls. Thus, invoking the RPC protocol masks the complexity of the underlying communication, providing transparency of the communication in a distributed system.
In step S302, the information of the requesting party included in each information push request is acquired respectively.
The information of the requesting party includes user account information, the user account refers to a user account using the service system, the user account information includes at least one of an account id of the user, an account name of the user, an International Mobile Equipment Identity (IMEI) of the user terminal, a physical Address or a Media Access Control Address (Media Access Control Address), an ip Address and a port number of the user terminal, a service type used by the user terminal, and a push channel of the user terminal, and the user terminal refers to a terminal where the user account is located. The service type can be registration service, login service, inquiry service, etc., and the information communication channel type used by the terminal can be mailbox, short message, etc.
It should be noted that, the service system of the application server may obtain information of multiple requesters simultaneously, for example, 10, 20, and the like, which is not limited by this disclosure.
It should be noted that, after the service system of the application server acquires the information of the requester, the service system further performs data conversion on the acquired information of the requester to generate an encrypted string corresponding to the requester. Illustratively, the information of the requester can be encrypted. Such encryption schemes include, but are not limited to, MD5 encryption, symmetric encryption, or asymmetric encryption. In a preferred embodiment, the present disclosure employs MD5 encryption.
In step S303, in the history of the information push log, the number of times of information push requests sent by the same requester in a specified time period is counted.
The specified time period may be 10 minutes, or 60 minutes, or 24 hours.
The number of times of information push requests sent by the same requester in a specified time period is recorded, and illustratively, the number of times of information push requests sent by the same requester of each service module in the specified time period is recorded.
In step S304, if the number of times of the information push requests sent by the same requester in the specified time period is less than or equal to the predetermined threshold, the information push request sent by the requester is determined to be a valid information push request.
The predetermined threshold is determined according to specific service modules and information of the requesting party, where different service modules correspond to different request limit times, for example, the querying module only allows the same requesting party to send 10 information push requests within one day, and the requesting party only has 5 request times for the querying module, so the predetermined threshold for the querying module of the requesting party is 5 times.
And if the number of times of the information push requests sent by the same requester in the specified time period is lower than a preset threshold value, determining the information push requests sent by the requester as valid information push requests. That is, the information push request sent by the requester does not exceed the frequency limit of the service module, the information push request sent by the requester is an effective information push request. If the number of times of the information push requests sent by the same requester in the specified time period is greater than the predetermined threshold, the information push request sent by the requester is determined to be an invalid information push request, at this time, the requester may be prompted, for example, a prompt such as "request frequency exceeds a limit, please try again later" is sent to the requester, and the execution of step S304 is exited.
Specifically, the request number may be checked according to an identifier capable of uniquely identifying the terminal where the user account is located, for example, the identifier may be, but is not limited to, an IMEI code, a MAC address, an IP address, and the like.
It should be noted that, in this step, information of the service type of the requestor, that is, the service authority of the requestor, which service modules the requestor has request authority, which service modules the requestor does not have request authority, is also obtained, and when the requestor does not have the request authority of the service module, the information push request sent by the requestor is determined to be an invalid information push request.
In step S305, different types of information push tasks are generated according to different push channels.
It should be noted that step S305 includes sub-step S3051 and sub-step S3052, and a detailed process of generating the information pushing task will be described in detail in the sub-steps. Referring to fig. 4, fig. 4 is a flowchart illustrating sub-steps of step S305 according to an exemplary embodiment of the disclosure.
In the substep S3051, an information push template corresponding to the push channel is invoked according to the information push request, where the information push template includes push format information adapted to the push channel.
Illustratively, the pushing channel may be a channel such as a mailbox, a short message, a WeChat, a flybook, a nail, and the like, and then the information pushing template corresponding to each channel such as the mailbox, the short message, the WeChat, the flybook, the nail, and the like is called to generate the information pushing task. The information pushing template comprises specific information format information, wherein the information format information specifically comprises text content, theme type, text style and the like.
In sub-step S3052, an information push task is generated based on the information push request and the corresponding information push template.
The information pushing task comprises a pushing channel and requester information, wherein the requester information comprises an account id and a used account name.
Illustratively, the push channel is WeChat, and the service system calls an information push template corresponding to the WeChat to generate an information push task corresponding to the WeChat. If the pushing channel is a mailbox, the service system calls an information pushing template corresponding to the mailbox to generate an information pushing task corresponding to the mailbox channel.
In step S306, an information push task is performed to push information to the requester.
Determining a corresponding pushing channel and information of a requester according to the information pushing task, determining an information pushing template according to the pushing channel, and then sending information format information in the corresponding information pushing template to the requester.
For example, the push channel is WeChat, the service system connects to a WeChat client according to the WeChat account id and the account name of the requester, invokes an information push template corresponding to the WeChat, performs related adjustment on push format information in the information push template to obtain final sending content, for example, adjusts an account to the WeChat account of the requester, and then pushes the adjusted sending content to the WeChat client.
For example, the push channel is a flybook, the service system connects to a flybook client according to a unique key of the flybook and an open ID of a requester, invokes an information push template corresponding to the flybook, performs related adjustment on push format information in the information push template to obtain final sending content, for example, an account is adjusted to the flybook open ID of the requester, and then pushes the adjusted sending content to the flybook client.
For example, the push channel is a mail, the service system connects to the mail client according to the mail requester ID, invokes an information push template corresponding to the mail, performs relevant adjustment on push format information in the information push template, such as adjustment of text content, theme type, text style, and the like, to obtain final transmission content, and then pushes the adjusted transmission content to the mail client.
It should be noted that, in this step, pushing information to the requester may be completed by a plurality of sub-threads in one thread, specifically, one information pushing thread may be created, where the information pushing thread includes a plurality of sending sub-threads, and the sending sub-threads include, but are not limited to, a micro-mail sub-thread, a flybook sub-thread, a mail sub-thread, and a short message sub-thread. And then, according to the information pushing task, determining a corresponding sending sub-thread, and sending the pushing format information in the information pushing template to the requester through the sending sub-thread.
In step S307, the result of pushing information to the requester is received.
And receiving and recording a push information result returned by the requester, wherein the push information result comprises push success or push failure.
In step S308, the result of pushing information is recorded to generate an information push log.
The information push log comprises at least one of the result of information push, the information of a requester, an information push task, an information push template, information push time and information push duration.
And packaging the information push log generated by pushing the information each time, and storing the information push log into a database so as to facilitate subsequent query and be beneficial to unified storage and management of the data.
In summary, the information pushing method provided in the exemplary embodiment of the present disclosure includes: receiving information pushing requests sent by all the service modules, wherein the information pushing requests comprise requesting parties and pushing channels, generating different types of information pushing tasks according to different pushing channels, and executing the information pushing tasks to push information to the requesting parties, wherein the types correspond to the pushing channels. The unified gateway interface protocol with the interfaces connected with different service modules and different channels is provided, information of different service modules and different channels is pushed in a unified mode, data generated in the information pushing process are recorded, unified storage and management of the data are facilitated, when the channel gateway interface protocol of each service line is modified or service is upgraded, repeated development of research and development maintenance personnel is avoided, and labor cost is saved.
Fig. 5 is a block diagram of an information pushing apparatus according to an exemplary embodiment of the present disclosure. Referring to fig. 5, the apparatus 20 includes a receiving module 201, a processing module 203, a filtering module 204, and an executing module 205.
A receiving module 201, configured to receive information push requests sent by the service modules; the information pushing request comprises a requesting party and a pushing channel;
the filtering module 204 is configured to filter the received information pushing request based on a history record in the information pushing log, and retain an effective information pushing request therein;
the processing module 203 is configured to generate different types of information push tasks according to different push channels for an effective information push request; wherein the type corresponds to the push channel;
an executing module 205, configured to execute the information pushing task to push information to the requesting party.
Optionally, the processing module 203 is further configured to perform data conversion on information of at least one of the requesters to generate an encrypted string corresponding to the requester.
Optionally, the processing module 203 is further configured to obtain information of a requester included in each information push request respectively;
counting the times of the information push requests sent by the same requester in a specified time period in the history record of the information push log;
and if the number of times of the information push requests sent by the same requester in the specified time period is less than or equal to a preset threshold value, determining the information push requests sent by the requester as valid information push requests.
Optionally, the receiving module 201 is further configured to obtain information of a service type corresponding to a requester included in each information push request;
and if the service type corresponding to the requester is not suitable for the corresponding service module, determining the information push request sent by the requester as an invalid information push request.
Optionally, the processing module 203 is further configured to invoke an information pushing template corresponding to the pushing channel according to the information pushing request, where the information pushing template includes pushing format information suitable for the pushing channel;
and generating an information pushing task based on the information pushing request and the corresponding information pushing template.
Optionally, the processing module 203 is further configured to determine a corresponding sender thread according to the type of the information pushing task;
and sending the information push content in the information push template to the requester through the sender thread.
Optionally, the processing module 203 is further configured to receive a result of pushing information to the requester; the result comprises push success or push failure;
recording the result of pushing information to generate an information pushing log; the log comprises at least one of the result, the information of the requester, the information pushing task, an information pushing template, information pushing time and information pushing duration.
Optionally, the executing module 205 is further configured to store the information push log in a database.
Fig. 6 is a block diagram illustrating an electronic device 400 according to an example embodiment. As shown in fig. 6, the electronic device 400 may include: a processor 401 and a memory 402. The electronic device 400 may also include one or more of a multimedia component 403, an input/output (I/O) interface 404, and a communications component 405.
The processor 401 is configured to control the overall operation of the electronic device 400, so as to complete all or part of the steps in the information pushing method. The memory 402 is used to store various types of data to support operation at the electronic device 400, such as instructions for any application or method operating on the electronic device 400 and application-related data, such as contact data, transmitted and received messages, pictures, audio, video, and so forth. The Memory 402 may be implemented by any type of volatile or non-volatile Memory device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk or optical disk. The multimedia components 403 may include a screen and an audio component. Wherein the screen may be, for example, a touch screen and the audio component is used for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may further be stored in the memory 402 or transmitted through the communication component 405. The audio assembly also includes at least one speaker for outputting audio signals. The I/O interface 404 provides an interface between the processor 401 and other interface modules, such as a keyboard, mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 405 is used for wired or wireless communication between the electronic device 400 and other devices. Wireless Communication, such as Wi-Fi, bluetooth, Near Field Communication (NFC), 2G, 3G, 4G, NB-IOT, eMTC, or other 5G, etc., or a combination of one or more of them, which is not limited herein. The corresponding communication component 405 may therefore include: Wi-Fi module, Bluetooth module, NFC module, etc.
In an exemplary embodiment, the electronic Device 400 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for performing the information pushing method described above.
In another exemplary embodiment, a computer readable storage medium including program instructions, which when executed by a processor, implement the steps of the information pushing method described above, is also provided. For example, the computer readable storage medium may be the memory 402 comprising program instructions executable by the processor 401 of the electronic device 400 to perform the information pushing method described above.
Fig. 7 is a block diagram illustrating another electronic device 500 in accordance with an example embodiment. For example, the electronic device 500 may be provided as a server. Referring to fig. 7, the electronic device 500 comprises a processor 522, which may be one or more in number, and a memory 532 for storing computer programs executable by the processor 522. The computer programs stored in memory 532 may include one or more modules that each correspond to a set of instructions. Further, the processor 522 may be configured to execute the computer program to perform the information push method described above.
Additionally, the electronic device 500 may also include a power component 526 and a communication component 550, the power component 526 may be configured to perform power management of the electronic device 500, and the communication component 550 may be configured to enable communication, e.g., wired or wireless communication, of the electronic device 500. In addition, the electronic device 500 may also include input/output (I/O) interfaces 558. The electronic device 500 may operate based on an operating system, such as Windows Server, stored in the memory 532TM，Mac OS XTM，UnixTM，LinuxTMAnd so on.
In another exemplary embodiment, a computer readable storage medium including program instructions, which when executed by a processor, implement the steps of the information pushing method described above, is also provided. For example, the non-transitory computer readable storage medium may be the memory 532 described above including program instructions that are executable by the processor 522 of the electronic device 500 to perform the information push method described above.
In another exemplary embodiment, a computer program product is also provided, which contains a computer program executable by a programmable apparatus, the computer program having code portions for performing the information pushing method described above when executed by the programmable apparatus.
The preferred embodiments of the present disclosure are described in detail with reference to the accompanying drawings, however, the present disclosure is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solution of the present disclosure within the technical idea of the present disclosure, and these simple modifications all belong to the protection scope of the present disclosure.
It should be noted that, in the foregoing embodiments, various features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various combinations that are possible in the present disclosure are not described again.
In addition, any combination of various embodiments of the present disclosure may be made, and the same should be considered as the disclosure of the present disclosure, as long as it does not depart from the spirit of the present disclosure.
Claims (11)
1. An information pushing method, comprising:
receiving an information pushing request sent by each service module, wherein the information pushing request comprises a requesting party and a pushing channel;
based on the history record in the information pushing log, filtering the received information pushing request, and keeping the effective information pushing request;
generating different types of information pushing tasks according to different pushing channels aiming at the effective information pushing request; wherein the type corresponds to the push channel;
and executing the information pushing task to push information to the requester.
2. The method according to claim 1, wherein the filtering the received information push request based on a history record in an information push log comprises:
respectively acquiring information of a requester contained in each information pushing request;
counting the times of the information push requests sent by the same requester in a specified time period in the history record of the information push log;
and if the number of times of the information push requests sent by the same requester in the specified time period is less than or equal to a preset threshold value, determining the information push requests sent by the requester as invalid information push requests.
3. The method according to claim 1, wherein the information push request further includes service type information, and after the step of receiving the information push request sent by each service module, the method further includes:
respectively acquiring the information of the service type corresponding to the requester in each information push request;
and if the service type corresponding to the requester is not suitable for the corresponding service module, determining the information push request sent by the requester as an invalid information push request.
4. The method according to claim 1, wherein the step of generating different types of information push tasks according to different push channels comprises:
calling an information pushing template corresponding to the pushing channel according to the information pushing request, wherein the information pushing template comprises pushing format information suitable for the pushing channel;
and generating an information pushing task based on the information pushing request and the corresponding information pushing template.
5. The method of claim 1, further comprising:
and performing data conversion on the information of at least one requester to generate an encrypted character string corresponding to the requester.
6. The method of claim 1, wherein the step of sending the information push content in the corresponding information push template to the requesting party comprises:
determining a corresponding sender thread according to the type of the information pushing task;
and sending the information push content in the information push template to the requester through the sender thread.
7. The method of claim 1, wherein after the step of executing the information pushing task to push information to the requesting party, the method further comprises:
receiving a result of pushing information to the requester; the result comprises push success or push failure;
recording the result of pushing information to generate an information pushing log; the log comprises at least one of the result, the information of the requester, the information pushing task, an information pushing template, information pushing time and information pushing duration.
8. The method of claim 7, further comprising:
and storing the information push log into a database.
9. An information pushing apparatus, comprising:
the receiving module is used for receiving the information pushing requests sent by the service modules; the information pushing request comprises a requesting party and a pushing channel;
the filtering module is used for filtering the received information pushing request based on the history record in the information pushing log and reserving an effective information pushing request;
the processing module is used for generating different types of information pushing tasks according to different pushing channels aiming at the effective information pushing request; wherein the type corresponds to the push channel;
and the execution module is used for executing the information pushing task so as to push information to the requester.
10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processing means, carries out the steps of the method according to any one of claims 1 to 8.
11. A computer device, comprising:
a storage device having a computer program stored thereon;
processing means for executing the computer program in the storage means to carry out the steps of the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111666535.9A CN114363408A (en) | 2021-12-31 | 2021-12-31 | Information pushing method and device, computer readable medium and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111666535.9A CN114363408A (en) | 2021-12-31 | 2021-12-31 | Information pushing method and device, computer readable medium and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114363408A true CN114363408A (en) | 2022-04-15 |
Family
ID=81105322
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111666535.9A Withdrawn CN114363408A (en) | 2021-12-31 | 2021-12-31 | Information pushing method and device, computer readable medium and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114363408A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115866030A (en) * | 2022-10-17 | 2023-03-28 | 北京达佳互联信息技术有限公司 | Content pushing method, device, equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019019642A1 (en) * | 2017-07-24 | 2019-01-31 | 深圳壹账通智能科技有限公司 | Application information pushing method and apparatus, and computer device and storage medium |
| CN110601952A (en) * | 2018-06-12 | 2019-12-20 | 北京京东尚科信息技术有限公司 | Multi-channel message notification sending method and device |
| WO2021159393A1 (en) * | 2020-02-13 | 2021-08-19 | 深圳市欢太科技有限公司 | Information pushing method and apparatus, and server and storage medium |
| CN113839977A (en) * | 2020-06-24 | 2021-12-24 | 顺丰科技有限公司 | Message pushing method and device, computer equipment and storage medium |
-
2021
- 2021-12-31 CN CN202111666535.9A patent/CN114363408A/en not_active Withdrawn
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019019642A1 (en) * | 2017-07-24 | 2019-01-31 | 深圳壹账通智能科技有限公司 | Application information pushing method and apparatus, and computer device and storage medium |
| CN110601952A (en) * | 2018-06-12 | 2019-12-20 | 北京京东尚科信息技术有限公司 | Multi-channel message notification sending method and device |
| WO2021159393A1 (en) * | 2020-02-13 | 2021-08-19 | 深圳市欢太科技有限公司 | Information pushing method and apparatus, and server and storage medium |
| CN113839977A (en) * | 2020-06-24 | 2021-12-24 | 顺丰科技有限公司 | Message pushing method and device, computer equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115866030A (en) * | 2022-10-17 | 2023-03-28 | 北京达佳互联信息技术有限公司 | Content pushing method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3484125B1 (en) | Method and device for scheduling interface of hybrid cloud | |
| JP7389791B2 (en) | Implementing Compliance Settings with Mobile Devices to Adhere to Configuration Scenarios | |
| JP5429912B2 (en) | Authentication system, authentication server, service providing server, authentication method, and program | |
| CN111416867B (en) | Message processing method, server and computer storage medium between different devices | |
| TWI761385B (en) | Device configuration method, device, and system | |
| CN112311841B (en) | Information pushing method and device, electronic equipment and computer readable medium | |
| US11128677B2 (en) | Network call method, server, call terminal, network call system, and storage medium | |
| CN109154968B (en) | System and method for secure and efficient communication within an organization | |
| CN108289074B (en) | User account login method and device | |
| CN112087475B (en) | Message pushing method and device for cloud platform component application and message server | |
| CN114363408A (en) | Information pushing method and device, computer readable medium and computer equipment | |
| CN109391658B (en) | Account data synchronization method and equipment, storage medium and terminal thereof | |
| EP3854023B1 (en) | System and method for message transmission and retrieval using blockchain | |
| CN112613933A (en) | Invoice data processing method and device, storage medium and electronic equipment | |
| CN114500630A (en) | Message pushing method, device, system, storage medium and electronic equipment | |
| CN112364334A (en) | Single sign-on method and device, electronic equipment and storage medium | |
| WO2018214795A1 (en) | Call indication method, device and system | |
| US20230032867A1 (en) | Certificate revocation at datacenters | |
| CN116244682A (en) | Database access method, device, equipment and storage medium | |
| CN112257039B (en) | Identity attribute adding method and device and electronic equipment | |
| CN115840399A (en) | Intelligent building monitoring system based on Internet of things and monitoring method thereof | |
| CN114339628A (en) | Method, device, storage medium and product for sending 5G rich media message | |
| CN115297066B (en) | Resource dynamic cooperation method, device, server and medium | |
| US11743218B2 (en) | Message capture in a multi channel communication environment | |
| US11601271B2 (en) | Cloud-based removable drive encryption policy enforcement and recovery key management |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20220415 |