CN112491998B - Message pushing method and related equipment - Google Patents
Message pushing method and related equipment Download PDFInfo
- Publication number
- CN112491998B CN112491998B CN202011292318.3A CN202011292318A CN112491998B CN 112491998 B CN112491998 B CN 112491998B CN 202011292318 A CN202011292318 A CN 202011292318A CN 112491998 B CN112491998 B CN 112491998B
- Authority
- CN
- China
- Prior art keywords
- message
- target
- push
- configuration information
- consumption
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/562—Brokering proxy services
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Abstract
The application discloses a message pushing method and related equipment, which are applied to electronic equipment, wherein the method comprises the following steps: receiving a call request of a target interface, wherein the call request carries N consumption messages and N first message type identifiers, the N consumption messages are in one-to-one correspondence with the N first message type identifiers, the call request is used for requesting to push the N consumption messages through the target interface, and N is a positive integer; acquiring first configuration information from a first database based on the interface identifier of the target interface; and pushing the N consumption messages to a message middleware based on the first configuration information and the N first message type identifiers. By adopting the embodiment of the application, the efficiency of message pushing can be improved.
Description
Technical Field
The present disclosure relates to the field of electronic technologies, and in particular, to a message pushing method and related devices.
Background
The message producer is used for providing a message composed of text data of numbers, letters and symbols, the message consumer is used for connecting with the message producer and outputting the message, the message middleware is used for receiving the message from the message producer, storing the message in a message queue of the message middleware and pushing the message in the message queue to the message consumer for processing when appropriate, so that the message middleware is an indispensible part of interaction between the message producer and the message consumer. However, when there are too many messages to be pushed by the message producer, how to improve the efficiency of message pushing is a problem to be solved.
Disclosure of Invention
The embodiment of the application provides a message pushing method and related equipment, which are beneficial to improving the efficiency of message pushing.
In a first aspect, an embodiment of the present application provides a message pushing method, applied to an electronic device, where the method includes:
receiving a call request of a target interface, wherein the call request carries N consumption messages and N first message type identifiers, the N consumption messages are in one-to-one correspondence with the N first message type identifiers, the call request is used for requesting to push the N consumption messages through the target interface, and N is a positive integer;
acquiring first configuration information from a first database based on the interface identifier of the target interface;
and pushing the N consumption messages to a message middleware based on the first configuration information and the N first message type identifiers.
In a second aspect, an embodiment of the present application provides a message pushing device, including:
the receiving unit is used for receiving a call request of a target interface, wherein the call request carries N consumption messages and N first message type identifiers, the N consumption messages are in one-to-one correspondence with the N first message type identifiers, the call request is used for requesting to push the N consumption messages through the target interface, and N is a positive integer;
the acquisition unit is used for acquiring first configuration information from a first database based on the interface identifier of the target interface;
and the pushing unit is used for pushing the N consumption messages to the message middleware based on the first configuration information and the N first message type identifiers.
In a third aspect, an embodiment of the present application provides an electronic device, including a processor, a memory, a communication interface, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the processor, the programs including instructions for performing steps in the method described in the first aspect of the embodiment of the present application.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium, where the computer-readable storage medium stores a computer program for electronic data exchange, where the computer program causes a computer to perform some or all of the steps described in the method according to the first aspect of the embodiments of the present application.
In a fifth aspect, embodiments of the present application provide a computer program product, wherein the computer program product comprises a non-transitory computer readable storage medium storing a computer program, the computer program being operable to cause a computer to perform some or all of the steps described in the method according to the first aspect of the embodiments of the present application. The computer program product may be a software installation package.
It can be seen that, in this embodiment of the present application, an electronic device first receives a call request of a target interface, where the call request carries N consumption messages and N first message type identifiers, the N consumption messages are in one-to-one correspondence with the N first message type identifiers, and the call request is used to request that N consumption messages be pushed through the target interface; then, based on the interface identification of the target interface, acquiring first configuration information from a first database; and finally, pushing the N consumption messages to the message middleware based on the first configuration information and the N first message type identifiers. The electronic equipment acquires the first configuration information from the first database based on the target interface identifier after receiving the N consumption messages, and pushes the N consumption messages to the message middleware at one time based on the first configuration information and the N first message type identifiers instead of pushing the single consumption message, so that the efficiency of message pushing is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
fig. 2 is a schematic flow chart of a message pushing method provided in an embodiment of the present application;
fig. 3 is a schematic structural diagram of another electronic device according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a message pushing device provided in the embodiment of the present application.
Detailed Description
In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
The following will describe in detail.
The terms "first," "second," "third," and "fourth" and the like in the description and in the claims of this application and in the drawings, are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
In the following, some terms in the present application are explained for easy understanding by those skilled in the art.
The electronic device may include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of User Equipment (UE), mobile Station (MS), terminal devices (terminal devices), etc.
As shown in fig. 1, fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device includes a processor, memory, signal processor, transceiver, display screen, speaker, communication interface, random access memory (Random Access Memory, RAM), camera, sensor, and the like. The device comprises a memory, a signal processor, a display screen, a loudspeaker, a RAM, a camera, a sensor and a communication interface, wherein the memory, the signal processor, the display screen, the loudspeaker, the RAM, the camera, the sensor and the communication interface are connected with the processor, and the transceiver is connected with the signal processor.
The display screen may be a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), an Active Matrix Organic Light-Emitting Diode panel (AMOLED), or the like.
The camera may be a common camera, may be an infrared camera, or may be an intelligent camera, which is not limited herein. The camera may be a front camera or a rear camera, which is not limited herein.
Wherein the sensor comprises at least one of: light sensing sensors, gyroscopes, infrared proximity sensors, fingerprint sensors, pressure sensors, etc. Wherein a light sensor, also called ambient light sensor, is used to detect the ambient light level. The light sensor may comprise a photosensitive element and an analog-to-digital converter. The photosensitive element is used for converting the collected optical signals into electric signals, and the analog-to-digital converter is used for converting the electric signals into digital signals. Optionally, the optical sensor may further include a signal amplifier, where the signal amplifier may amplify the electrical signal converted by the photosensitive element and output the amplified electrical signal to the analog-to-digital converter. The photosensitive element may include at least one of a photodiode, a phototransistor, a photoresistor, and a silicon photocell.
The processor is a control center of the electronic device, and is connected with various parts of the whole electronic device by various interfaces and lines, and executes various functions of the electronic device and processes data by running or executing software programs and/or modules stored in the memory and calling data stored in the memory, so that the electronic device is monitored as a whole.
The processor may integrate an application processor and a modem processor, wherein the application processor primarily handles operating systems, user interfaces, applications, etc., and the modem processor primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor.
The memory is used for storing software programs and/or modules, and the processor executes the software programs and/or modules stored in the memory so as to execute various functional applications of the electronic device and data processing. The memory may mainly include a memory program area and a memory data area, wherein the memory program area may store an operating system, a software program required for at least one function, and the like; the storage data area may store data created according to the use of the electronic device, etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
The memory stores a call request instruction of receiving a target interface, a first configuration information acquisition instruction, a consumption message pushing instruction and the like.
The instructions, such as the call request instruction of the target interface, the first configuration information acquisition instruction, and the consumption message pushing instruction, are all used for implementing part or all of the steps of the message pushing method described in the method embodiment described below.
The embodiments of the present application are described in detail below.
As shown in fig. 2, the message pushing method provided in the embodiment of the present application is applied to the above electronic device, and specifically includes the following steps:
step 201: receiving a call request of a target interface, wherein the call request carries N consumption messages and N first message type identifiers, the N consumption messages are in one-to-one correspondence with the N first message type identifiers, the call request is used for requesting to push the N consumption messages through the target interface, and N is a positive integer.
The call request of the target interface is initiated by the external system through other electronic equipment, and the call request of the target interface is used for requesting the internal system of the electronic equipment to push the consumption information of the external system, and the internal system and the external system communicate through the target interface, so that N consumption information can come from the same external system or different external systems.
Wherein the consumption message may be a message consisting of letters, numbers and special symbols.
Wherein the first message type identification may be represented by letters, by numbers, etc.
The N first message type identifiers may have the same message type identifier, or the N first message type identifiers may all be different.
The message middleware comprises at least one message theme, and each message theme comprises at least one message label which is used for further distinguishing message classification under the message theme, so that the N consumption messages can be positioned in the message labels under the same message theme of the message middleware, can be positioned in the same message label under different message themes, and can be positioned in different message labels under different themes.
Step 202: and acquiring first configuration information from a first database based on the interface identification of the target interface.
The interface identifier has uniqueness, is preset and can be specified by a protocol.
The interface identifier may be represented by a number or by a letter, and the electronic device may further include an interface other than the target interface.
Wherein the interface identifier and the first configuration information are stored in the first database in an associated form, so that the first configuration information associated with the interface identifier can be acquired through the interface identifier.
Step 203: and pushing the N consumption messages to a message middleware based on the first configuration information and the N first message type identifiers.
Optionally, the first configuration information further includes M pieces of sub-configuration information, each piece of sub-configuration information includes a second message type identifier, and the M pieces of second message type identifiers include N pieces of first message type identifiers, so that N pieces of target sub-configuration information can be determined from the M pieces of sub-configuration information based on the N pieces of first message types, each piece of target sub-configuration information corresponds to one consumption message, and the first message type of the consumption message corresponding to each piece of target sub-configuration information is the same as the second message type identifier included in each piece of target sub-configuration information. The message type identifier may be the identifier information of the electronic device that sends the consumption message, or may be the identifier of the external system that generates the consumption message, or may be the application software that generates the consumption message, etc.
Optionally, each piece of sub-configuration information may further include a push class, a push manner, a push message theme, and a push message tag.
Wherein a push class is a defined thread for pushing consumed messages.
The pushing mode can be directly pushing to the middleware or pushing to other systems, wherein the other systems push to the target middleware, and the other systems are systems associated with the target middleware.
The push message theme can be an order message, a payment message, a reminding message and the like. Message tags are different types of message topics.
For example, if the push message is order information, the message label may be panda order information, heaven order information, jindong order information, etc.; alternatively, the message tag may be an electrical order, a women's dress order, a cosmetic order, a footwear order, and so on.
It can be seen that, in this embodiment of the present application, an electronic device first receives a call request of a target interface, where the call request carries N consumption messages and N first message type identifiers, the N consumption messages are in one-to-one correspondence with the N first message type identifiers, and the call request is used to request that N consumption messages be pushed through the target interface; then, based on the interface identification of the target interface, acquiring first configuration information from a first database; and finally, pushing the N consumption messages to the message middleware based on the first configuration information and the N first message type identifiers. The electronic equipment acquires the first configuration information from the first database based on the target interface identifier after receiving the N consumption messages, and pushes the N consumption messages to the message middleware at one time based on the first configuration information and the N first message type identifiers instead of pushing the single consumption message, so that the efficiency of message pushing is improved.
In one possible implementation manner, the pushing the N consumption messages into the middleware based on the N target sub-configuration information includes:
sending each consumption message and first indication information to a target push class in each target sub-configuration information correspondingly, wherein the first indication information carries a target push mode, a target push message theme and a target push message label in each target sub-configuration information, and the first indication information is used for indicating the target push class to adopt the target push mode to push each consumption message to the target push message label under the target push message theme in the middleware.
The method comprises the steps of sending a message to a user, wherein a plurality of consumption messages can be pushed to a push message label under the same push message theme, different consumption messages can be pushed to different push message labels under different push message themes, and different consumption messages can be pushed to the same push message label under different push message themes.
Wherein different target push classes are different threads.
It can be seen that in the embodiment of the present application, N consumption messages are pushed simultaneously, which is beneficial to improving the efficiency of message pushing.
In one possible implementation manner, the pushing the N consumption messages into the middleware based on the N target sub-configuration information includes:
determining the data volume of each consumption message;
correspondingly sending each consumption message and second indication information to a target push class in each target sub-configuration information, wherein the second indication information carries the data quantity, the target push class, a target push mode, a target push message theme and a target push message label in each target sub-configuration information, and the second indication information is used for indicating the target push class to push each consumption message to the target push message label under the target push message theme in the message middleware by adopting the target push mode;
receiving third indication information, wherein the third indication information carries the target push message theme and a first push message label, and the third indication information is used for indicating that unoccupied memory capacity in the target push message label under the target push message theme is smaller than the data volume, and each consumption message is stored in the first push message label of the target push message theme in the message middleware, wherein the target push message label and the first push message label are the same type label.
If the data size of the consumption message is smaller than the residual capacity of the target push message label under the target push message subject included in the target sub-configuration information corresponding to the consumption message, the terminal device cannot receive the third indication information.
For example, assuming a data size of 400KB, the target push message topic A includes 3 push message tags (B1, B2, and B3), and the target push message is B3. If the unoccupied memory in B3 is 300KB, the unoccupied memory in B3 is smaller than 400KB, so a push tag B4 with a memory capacity greater than 400KB is established under the target push message subject a, and B3 and B4 are the same type of tag.
The third indication information carries a target push message theme and a first push message label.
For example, if the target push message topic is order information and the target push message label is a jindong order, the first push message label is jindong order 1.
The unoccupied memory capacity is all the free capacity in the target push message label under the target push message theme.
Optionally, the consumption message under the push message theme is cleared after a preset time period.
It can be seen that in the embodiment of the present application, when the data size of the consumption message is too large, a storage space for information is opened up, which is beneficial to avoiding the loss of the consumption message.
In one possible implementation manner, the pushing the N consumption messages into the middleware based on the N target sub-configuration information includes:
correspondingly sending each consumption message and fourth indication information to a target push class in each piece of sub-configuration information, wherein the fourth indication information carries target push time of each consumption message, a target push mode, a target push message theme and a target push message label in each piece of sub-configuration information, and the fourth indication information is used for indicating the target push class to push each consumption message to the target push message label under the target push message theme in the message middleware by adopting the target push mode in the target push time;
and receiving fifth instruction information, wherein the fifth instruction information is used for indicating that the target push class pushes the consumption message to be overtime.
Optionally, the target push time is determined based on the time of receipt of the consumption message and a preset duration.
For example, if the time of receiving the consumption message is 12:25:30 and the preset duration is 2 minutes, the time of pushing the message is 12:25:30.
Optionally, the target push time is determined based on a time of receipt of the consumption message, a preset duration associated with a push message topic corresponding to the consumption message.
For example, if the time of receiving the consumption message 1, the consumption message 2 and the consumption message 3 is 12:25:30am, the push message is mainly the payment information, the associated preset time period is 2 minutes, the push message is mainly the preset time period associated with the reminding information is 1 minute, and the push message is mainly the preset time period associated with the verification information is 3 minutes. Therefore, if the message topic corresponding to the push message 1 is payment information, the push time is 12:27:30am, the message topic corresponding to the push message 2 is reminding information, the push time is 12:26:30am, the message topic corresponding to the push message 3 is verification information, and the push time is 12:27:30am.
In this case, when the consumption message is overtime, the consumption message may be pushed again, and the consumption message pushed again may be the same as or may be different from the consumption message pushed before.
It can be seen that in the embodiment of the present application, the push time is set for each consumption message, which is beneficial to ensuring the authenticity of the consumption message.
In an implementation manner of the present application, after the pushing the N consumption messages to the middleware, the method further includes:
and storing each consumption message and each target sub-configuration information in a second database in an associated mode.
And the consumption information and the target sub-configuration information which are stored in an associated manner have a corresponding relationship.
It can be seen that in the embodiment of the application, the consumption message and the corresponding target sub-configuration information are stored in an associated manner, so that the consumption message can be extracted based on the target sub-configuration information.
Referring to fig. 3, in accordance with the embodiment shown in fig. 2, fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application, as shown in the fig. 3, the electronic device includes a processor, a memory, a communication interface, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for executing the following steps:
receiving a call request of a target interface, wherein the call request carries N consumption messages and N first message type identifiers, the N consumption messages are in one-to-one correspondence with the N first message type identifiers, the call request is used for requesting to push the N consumption messages through the target interface, and N is a positive integer;
acquiring first configuration information from a first database based on the interface identifier of the target interface;
and pushing the N consumption messages to a message middleware based on the first configuration information and the N first message type identifiers.
In an implementation manner of the present application, the first configuration information includes M pieces of sub-configuration information, each piece of sub-configuration information includes a second message type identifier, and M is a positive integer;
in pushing the N consumption messages into message middleware based on the first configuration information and the N first message type identifications, the program includes instructions for performing the steps of:
determining N target sub-configuration information in the M sub-configuration information based on a second message type identifier and the N first message type identifiers, wherein the N target sub-configuration information corresponds to the N consumption messages one by one, and M is larger than or equal to N;
pushing the N consumption messages to the middleware based on the N target sub-configuration information.
In an implementation manner of the present application, each piece of sub-configuration information further includes a push class, a push manner, a push message theme, and a push message label.
In an implementation of the present application, in pushing the N consumption messages into the middleware based on the N target sub-configuration information, the program includes instructions for performing the steps of:
sending each consumption message and first indication information to a target push class in each target sub-configuration information correspondingly, wherein the first indication information carries a target push mode, a target push message theme and a target push message label in each target sub-configuration information, and the first indication information is used for indicating the target push class to adopt the target push mode to push each consumption message to the target push message label under the target push message theme in the middleware.
In an implementation of the present application, in pushing the N consumption messages into the middleware based on the N target sub-configuration information, the program includes instructions for performing the steps of:
determining the data volume of each consumption message;
correspondingly sending each consumption message and second indication information to a target push class in each target sub-configuration information, wherein the second indication information carries the data quantity, the target push class, a target push mode, a target push message theme and a target push message label in each target sub-configuration information, and the second indication information is used for indicating the target push class to push each consumption message to the target push message label under the target push message theme in the message middleware by adopting the target push mode;
receiving third indication information, wherein the third indication information carries the target push message theme and a first push message label, and the third indication information is used for indicating that unoccupied memory capacity in the target push message label under the target push message theme is smaller than the data volume, and each consumption message is stored in the first push message label of the target push message theme in the message middleware, wherein the target push message label and the first push message label are the same type label.
In an implementation manner of the present application, the target interface call request further carries a target push time of each consumption message;
in terms of pushing the N consumption messages into the middleware based on the N target sub-configuration information, the program includes instructions for:
correspondingly sending each consumption message and fourth indication information to a target push class in each piece of sub-configuration information, wherein the fourth indication information carries target push time of each consumption message, a target push mode, a target push message theme and a target push message label in each piece of sub-configuration information, and the fourth indication information is used for indicating the target push class to push each consumption message to the target push message label under the target push message theme in the message middleware by adopting the target push mode in the target push time;
and receiving fifth instruction information, wherein the fifth instruction information is used for indicating that the target push class pushes the consumption message to be overtime.
In an implementation of the present application, after pushing the N consumption messages into the middleware, the program includes instructions for performing the steps of:
and storing each consumption message and each target sub-configuration information in a second database in an associated mode.
It should be noted that, the specific implementation process of this embodiment may refer to the specific implementation process described in the foregoing method embodiment, which is not described herein.
Referring to fig. 4, fig. 4 is a message pushing device provided in an embodiment of the present application, which is applied to an electronic device, and the device includes:
a receiving unit 401, configured to receive a call request of a target interface, where the call request carries N consumption messages and N first message type identifiers, the N consumption messages are in one-to-one correspondence with the N first message type identifiers, the call request is used to request pushing of the N consumption messages through the target interface, and N is a positive integer;
an obtaining unit 402, configured to obtain first configuration information from a first database based on an interface identifier of the target interface;
a pushing unit 403, configured to push the N consumption messages to a message middleware based on the first configuration information and the N first message type identifiers.
In an implementation manner of the present application, the first configuration information includes M pieces of sub-configuration information, each piece of sub-configuration information includes a second message type identifier, and M is a positive integer;
the pushing unit 403 is configured to, in pushing the N consumption messages to a message middleware based on the first configuration information and the N first message type identifiers:
determining N target sub-configuration information in the M sub-configuration information based on a second message type identifier and the N first message type identifiers, wherein the N target sub-configuration information corresponds to the N consumption messages one by one, and M is larger than or equal to N;
pushing the N consumption messages to the middleware based on the N target sub-configuration information.
In an implementation manner of the present application, each piece of sub-configuration information further includes a push class, a push manner, a push message theme, and a push message label.
In an implementation manner of the present application, in pushing the N consumption messages into the middleware based on the N target sub-configuration information, the pushing unit 403 is configured to:
sending each consumption message and first indication information to a target push class in each target sub-configuration information correspondingly, wherein the first indication information carries a target push mode, a target push message theme and a target push message label in each target sub-configuration information, and the first indication information is used for indicating the target push class to adopt the target push mode to push each consumption message to the target push message label under the target push message theme in the middleware.
In an implementation manner of the present application, in pushing the N consumption messages into the middleware based on the N target sub-configuration information, the pushing unit 403 is configured to:
determining the data volume of each consumption message;
correspondingly sending each consumption message and second indication information to a target push class in each target sub-configuration information, wherein the second indication information carries the data quantity, the target push class, a target push mode, a target push message theme and a target push message label in each target sub-configuration information, and the second indication information is used for indicating the target push class to push each consumption message to the target push message label under the target push message theme in the message middleware by adopting the target push mode;
receiving third indication information, wherein the third indication information carries the target push message theme and a first push message label, and the third indication information is used for indicating that unoccupied memory capacity in the target push message label under the target push message theme is smaller than the data volume, and each consumption message is stored in the first push message label of the target push message theme in the message middleware, wherein the target push message label and the first push message label are the same type label.
In an implementation manner of the present application, the target interface call request further carries a target push time of each consumption message;
the pushing unit 403 is configured to, in pushing the N consumption messages to the middleware based on the N target sub-configuration information:
correspondingly sending each consumption message and fourth indication information to a target push class in each piece of sub-configuration information, wherein the fourth indication information carries target push time of each consumption message, a target push mode, a target push message theme and a target push message label in each piece of sub-configuration information, and the fourth indication information is used for indicating the target push class to push each consumption message to the target push message label under the target push message theme in the message middleware by adopting the target push mode in the target push time;
the receiving unit receives fifth instruction information, where the fifth instruction information is used to instruct the target push class to push the consumption message overtime.
In a possible implementation, the message pushing device further comprises a storage unit 404.
In an implementation manner of the present application, the storage unit 404 is configured to:
and storing each consumption message and each target sub-configuration information in a second database in an associated mode.
It should be noted that the receiving unit 401, the acquiring unit 402, the pushing unit 403, and the storage unit 404 may be implemented by a processor.
The present application also provides a computer storage medium storing a computer program that is executed by a processor to implement some or all of the steps of any one of the message pushing methods described in the method embodiments above.
Embodiments of the present application also provide a computer program product, wherein the computer program product comprises a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps described by an electronic device in the above method. The computer program product may be a software installation package.
The steps of a method or algorithm described in the embodiments of the present application may be implemented in hardware, or may be implemented by executing software instructions by a processor. The software instructions may be comprised of corresponding software modules that may be stored in random access Memory (Random Access Memory, RAM), flash Memory, read Only Memory (ROM), erasable programmable Read Only Memory (Erasable Programmable ROM), electrically Erasable Programmable Read Only Memory (EEPROM), registers, hard disk, a removable disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in an access network device, a target network device, or a core network device. It is of course also possible that the processor and the storage medium reside as discrete components in an access network device, a target network device, or a core network device.
Those of skill in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application may be implemented, in whole or in part, in software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a digital video disc (Digital Video Disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.
The foregoing embodiments have been provided for the purpose of illustrating the embodiments of the present application in further detail, and it should be understood that the foregoing embodiments are merely illustrative of the embodiments of the present application and are not intended to limit the scope of the embodiments of the present application, and any modifications, equivalents, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application are included in the scope of the embodiments of the present application.
Claims (9)
1. A message pushing method, applied to an electronic device, the method comprising:
receiving a call request of a target interface, wherein the call request carries N consumption messages and N first message type identifiers, the N consumption messages are in one-to-one correspondence with the N first message type identifiers, the call request is used for requesting to push the N consumption messages through the target interface, and N is a positive integer;
based on the interface identification of the target interface, acquiring first configuration information from a first database, wherein the first configuration information comprises M pieces of sub-configuration information, each piece of sub-configuration information comprises a second message type identification, and M is a positive integer;
pushing the N consumption messages to a message middleware based on the first configuration information and the N first message type identifications, including: determining N target sub-configuration information in the M sub-configuration information based on a second message type identifier and the N first message type identifiers, wherein the N target sub-configuration information corresponds to the N consumption messages one by one, and M is larger than or equal to N; pushing the N consumption messages to the middleware based on the N target sub-configuration information.
2. The method of claim 1, wherein each of the sub-configuration information further comprises a push class, a push manner, a push message topic, and a push message tag.
3. The method of claim 2, wherein pushing the N consumption messages into the middleware based on the N target sub-configuration information comprises:
sending each consumption message and first indication information to a target push class in each target sub-configuration information correspondingly, wherein the first indication information carries a target push mode, a target push message theme and a target push message label in each target sub-configuration information, and the first indication information is used for indicating the target push class to adopt the target push mode to push each consumption message to the target push message label under the target push message theme in the middleware.
4. The method of claim 2, wherein pushing the N consumption messages into the middleware based on the N target sub-configuration information comprises:
determining the data volume of each consumption message;
correspondingly sending each consumption message and second indication information to a target push class in each target sub-configuration information, wherein the second indication information carries the data quantity, the target push class, a target push mode, a target push message theme and a target push message label in each target sub-configuration information, and the second indication information is used for indicating the target push class to push each consumption message to the target push message label under the target push message theme in the message middleware by adopting the target push mode;
receiving third indication information, wherein the third indication information carries the target push message theme and a first push message label, and the third indication information is used for indicating that unoccupied memory capacity in the target push message label under the target push message theme is smaller than the data volume, and each consumption message is stored in the first push message label of the target push message theme in the message middleware, wherein the target push message label and the first push message label are the same type label.
5. The method of claim 2, wherein the target interface call request further carries a target push time for each of the consumption messages;
the pushing the N consumption messages into the middleware based on the N target sub-configuration information includes:
correspondingly sending each consumption message and fourth indication information to a target push class in each piece of sub-configuration information, wherein the fourth indication information carries target push time of each consumption message, a target push mode, a target push message theme and a target push message label in each piece of sub-configuration information, and the fourth indication information is used for indicating the target push class to push each consumption message to the target push message label under the target push message theme in the message middleware by adopting the target push mode in the target push time;
and receiving fifth instruction information, wherein the fifth instruction information is used for indicating that the target push class pushes the consumption message to be overtime.
6. The method of any of claims 3-5, wherein after pushing the N consumption messages into the middleware, the method further comprises:
and storing each consumption message and each target sub-configuration information in a second database in an associated mode.
7. A message pushing apparatus, characterized in that it is applied to an electronic device, said apparatus comprising:
the receiving unit is used for receiving a call request of a target interface, wherein the call request carries N consumption messages and N first message type identifiers, the N consumption messages are in one-to-one correspondence with the N first message type identifiers, the call request is used for requesting to push the N consumption messages through the target interface, and N is a positive integer;
the acquisition unit is used for acquiring first configuration information from a first database based on the interface identifier of the target interface, wherein the first configuration information comprises M pieces of sub-configuration information, each piece of sub-configuration information comprises a second message type identifier, and M is a positive integer;
a pushing unit, configured to push the N consumption messages to a message middleware based on the first configuration information and the N first message type identifiers, where the pushing unit includes: determining N target sub-configuration information in the M sub-configuration information based on a second message type identifier and the N first message type identifiers, wherein the N target sub-configuration information corresponds to the N consumption messages one by one, and M is larger than or equal to N; pushing the N consumption messages to the middleware based on the N target sub-configuration information.
8. An electronic device comprising a processor, a memory, a communication interface, and one or more programs stored in the memory and configured to be executed by the processor, the programs comprising instructions for performing the steps in the method of any of claims 1-6.
9. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program, wherein the computer program is processed to perform the method according to any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011292318.3A CN112491998B (en) | 2020-11-18 | 2020-11-18 | Message pushing method and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011292318.3A CN112491998B (en) | 2020-11-18 | 2020-11-18 | Message pushing method and related equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112491998A CN112491998A (en) | 2021-03-12 |
| CN112491998B true CN112491998B (en) | 2023-08-08 |
Family
ID=74931457
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011292318.3A Active CN112491998B (en) | 2020-11-18 | 2020-11-18 | Message pushing method and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112491998B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113992352A (en) * | 2021-09-27 | 2022-01-28 | 青岛海尔科技有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN114401239B (en) * | 2021-12-20 | 2023-11-14 | 中国平安财产保险股份有限公司 | Metadata transmission method, apparatus, computer device and storage medium |
| CN115543662B (en) * | 2022-11-30 | 2023-03-21 | 苏州浪潮智能科技有限公司 | Method and related device for issuing kafka message data |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014169496A1 (en) * | 2013-04-16 | 2014-10-23 | Tencent Technology (Shenzhen) Company Limited | Method and system for handling message on instant messaging open platform |
| CN104980327A (en) * | 2014-04-03 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Information push method and device |
| CN108011937A (en) * | 2017-11-29 | 2018-05-08 | 努比亚技术有限公司 | Information push method, server, intelligent terminal and computer-readable recording medium |
| CN109151796A (en) * | 2018-08-10 | 2019-01-04 | Oppo广东移动通信有限公司 | NAN equipment finding method, relevant device and computer readable storage medium |
| CN109933439A (en) * | 2019-02-21 | 2019-06-25 | 深圳市珍爱捷云信息技术有限公司 | Method for message transmission, device, computer equipment and storage medium |
| CN111163152A (en) * | 2019-12-26 | 2020-05-15 | 中国平安人寿保险股份有限公司 | Information pushing method and device |
| CN111190747A (en) * | 2019-12-20 | 2020-05-22 | 北京金山云网络技术有限公司 | Message loss detection method and device for message queue |
| CN111245930A (en) * | 2020-01-09 | 2020-06-05 | 深圳壹账通智能科技有限公司 | Cross-platform message pushing method and device, computer equipment and storage medium |
| CN111338814A (en) * | 2020-02-13 | 2020-06-26 | 北京奇艺世纪科技有限公司 | Message processing method and device, storage medium and electronic device |
| CN111381986A (en) * | 2020-03-10 | 2020-07-07 | 北京奇艺世纪科技有限公司 | Message transmission method, system, device, electronic equipment and readable storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9667671B2 (en) * | 2013-05-13 | 2017-05-30 | Xerox Corporation | Method and system for facilitating communication between message consumers and message producers |
-
2020
- 2020-11-18 CN CN202011292318.3A patent/CN112491998B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014169496A1 (en) * | 2013-04-16 | 2014-10-23 | Tencent Technology (Shenzhen) Company Limited | Method and system for handling message on instant messaging open platform |
| CN104980327A (en) * | 2014-04-03 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Information push method and device |
| CN108011937A (en) * | 2017-11-29 | 2018-05-08 | 努比亚技术有限公司 | Information push method, server, intelligent terminal and computer-readable recording medium |
| CN109151796A (en) * | 2018-08-10 | 2019-01-04 | Oppo广东移动通信有限公司 | NAN equipment finding method, relevant device and computer readable storage medium |
| CN109933439A (en) * | 2019-02-21 | 2019-06-25 | 深圳市珍爱捷云信息技术有限公司 | Method for message transmission, device, computer equipment and storage medium |
| CN111190747A (en) * | 2019-12-20 | 2020-05-22 | 北京金山云网络技术有限公司 | Message loss detection method and device for message queue |
| CN111163152A (en) * | 2019-12-26 | 2020-05-15 | 中国平安人寿保险股份有限公司 | Information pushing method and device |
| CN111245930A (en) * | 2020-01-09 | 2020-06-05 | 深圳壹账通智能科技有限公司 | Cross-platform message pushing method and device, computer equipment and storage medium |
| CN111338814A (en) * | 2020-02-13 | 2020-06-26 | 北京奇艺世纪科技有限公司 | Message processing method and device, storage medium and electronic device |
| CN111381986A (en) * | 2020-03-10 | 2020-07-07 | 北京奇艺世纪科技有限公司 | Message transmission method, system, device, electronic equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112491998A (en) | 2021-03-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112491998B (en) | Message pushing method and related equipment | |
| US11509807B2 (en) | Electronic device and method for generating thumbnails based on captured images | |
| US9635268B2 (en) | Electronic device and method for generating thumbnail data | |
| US20150220247A1 (en) | Electronic device and method for providing information thereof | |
| CN111277991B (en) | Operator name display method and device, mobile terminal and storage medium | |
| KR20200015000A (en) | Method for memory leak detection and electronic device thereof | |
| CN113170019A (en) | Caller identification method based on application and terminal equipment | |
| KR102267015B1 (en) | Method for processing data and an electronic device thereof | |
| US20200201518A1 (en) | Method for starting application and electronic device for implementing same | |
| KR102439786B1 (en) | Method for sharing content information and electronic device thereof | |
| CN115687035A (en) | Memory leak detection method and electronic equipment | |
| KR102340251B1 (en) | Method for managing data and an electronic device thereof | |
| EP3084560B1 (en) | Electronic device and operating method thereof | |
| CN106331076A (en) | Advertisement push method and apparatus | |
| KR102133718B1 (en) | Apparatus and method for providing information using barcode | |
| CN116467221B (en) | Pile inserting method and system based on interpreter and related electronic equipment | |
| CN116483734B (en) | Pile inserting method and system based on compiler and related electronic equipment | |
| CN112333087B (en) | Consumption message processing method and related equipment | |
| CN106383870A (en) | Picture playing method and mobile terminal | |
| CN106302821B (en) | Data request method and equipment thereof | |
| CN104796519A (en) | Terminal | |
| EP3910911B1 (en) | Method for service decision distribution among multiple terminal devices and system | |
| CN110570864A (en) | Communication method and system based on cloud server and cloud server | |
| US11934853B2 (en) | Electronic device and operating method thereof | |
| CN114371895A (en) | Terminal device, mail marking method 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 |