CN108737218B - Automatic verification method and device for message push arrival rate - Google Patents
Automatic verification method and device for message push arrival rate Download PDFInfo
- Publication number
- CN108737218B CN108737218B CN201810593553.0A CN201810593553A CN108737218B CN 108737218 B CN108737218 B CN 108737218B CN 201810593553 A CN201810593553 A CN 201810593553A CN 108737218 B CN108737218 B CN 108737218B
- Authority
- CN
- China
- Prior art keywords
- message
- server
- callback
- messages
- pushing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1859—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast adapted to provide push services, e.g. data channels
-
- 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
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses an automatic verification method and device for message push arrival rate, wherein the method comprises the following steps: the simulation client sends a trigger request to the server so that the server pushes messages to the plurality of clients; receiving callback messages sent by a server after the server pushes messages to a plurality of clients by using a callback interface registered in the server in advance, and storing the contents of the callback messages to a local database; determining the message pushing quantity according to the contents of the callback messages stored in the local database, and comparing and checking the message pushing quantity with a preset expected result; and carrying out statistical display on the normally arrived pushing results which pass the comparison verification. The embodiment of the invention can truly and directly feed back the message pushing capability of the current server and whether the message is backlogged, and the whole process is automatic without manual intervention, thereby having real-time property.
Description
Technical Field
The embodiment of the invention relates to the technical field of network communication, in particular to an automatic verification method and device for message push arrival rate.
Background
This scenario is often encountered in Instant Messaging (IM) IM interface testing: how to check the arrival rate of the sent message and the receiving time of the other party when a plurality of people are on line simultaneously and high in concurrence. This scenario is actually a measure of the interface performance of asynchronous calls, and taking WeChat as an example, a message sent out will be returned to a client (client) successfully, but this does not mean that the message has already been sent to the other party. Meanwhile, the method is the most direct scene for measuring the pushing capability of the IM background server.
Currently, a direct method for combining the scene in the prior art is to count the push log of the server at the background, check how many messages are pushed in the log, and how many messages are pushed in each message.
However, the method in the prior art cannot perform automatic verification, and meanwhile, the efficiency of processing large file logs is not high, the method does not have real-time performance, and the large file logs are only pushed out, and whether the corresponding client really receives the notification or not is not known.
In view of this, how to automatically check the message push arrival rate becomes a technical problem to be solved at present.
Disclosure of Invention
Because the existing method has the above problems, the embodiments of the present invention provide an automatic verification method and apparatus for message push arrival rate.
In a first aspect, an embodiment of the present invention provides an automatic checking method for a message push arrival rate, including:
the method comprises the steps that a simulation client sends a trigger request to a server so that the server pushes messages to a plurality of clients;
receiving callback messages sent by the server after the server pushes messages to a plurality of clients by using a callback interface registered in the server in advance, and storing the contents of the callback messages to a local database;
determining the message pushing quantity according to the contents of the callback messages stored in the local database, and comparing and checking the message pushing quantity with a preset expected result;
and carrying out statistical display on the normally arrived pushing results which pass the comparison verification.
Optionally, the content of the callback message includes: whether to push the message to the client and to which client the message was pushed.
Optionally, after receiving, by using a callback interface registered in advance in the server, a callback message sent after the server pushes a message to a plurality of clients, and storing the content of the callback message in a local database, the method further includes:
and if the preset time period is exceeded, determining that the pushing of the message is not completed according to the content of the callback message stored in the local database, displaying an error, recording the number of the messages which are pushed, and going to a message task queue to check which examples the message which is not pushed is in.
Optionally, before receiving, by using a callback interface pre-registered in the server, a callback message sent after the server pushes a message to a plurality of clients, the method further includes:
and sending a registration request to a server so that the server registers a callback interface according to the registration request.
In a second aspect, an embodiment of the present invention further provides an automatic checking apparatus for a message push arrival rate, including:
the simulation module is used for simulating a client to send a trigger request to a server so that the server pushes messages to a plurality of clients;
the receiving module is used for receiving callback messages sent by the server after the server pushes the messages to the plurality of clients by utilizing a callback interface registered in the server in advance, and storing the contents of the callback messages to a local database;
the verification module is used for determining the message pushing quantity according to the contents of the callback messages stored in the local database and comparing and verifying the message pushing quantity with a preset expected result;
and the display module is used for counting and displaying the normally arrived pushing results which pass the comparison and verification.
Optionally, the content of the callback message includes: whether to push the message to the client and to which client the message was pushed.
Optionally, the apparatus further comprises:
and the display module is used for determining that message pushing is not completed according to the contents of the callback messages stored in the local database after a preset time period is exceeded, displaying an error, recording the number of the messages which are pushed completely, and going to a message task queue to check which examples the messages which are not pushed completely belong to.
Optionally, the apparatus further comprises:
and the sending module is used for sending a registration request to the server so that the server registers a callback interface according to the registration request.
In a third aspect, an embodiment of the present invention provides an electronic device, including: a processor, a memory, a bus, and a computer program stored on the memory and executable on a first processor;
the processor and the memory complete mutual communication through the bus;
the processor, when executing the computer program, implements the method described above.
In a fourth aspect, an embodiment of the present invention provides a non-transitory computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the above method.
It can be known from the above technical solutions that the embodiment of the present invention provides an automatic verification method and apparatus for message push arrival rate, which send a trigger request to a server through a simulation client to make the server push messages to a plurality of clients, receive callback messages sent after the server pushes messages to the plurality of clients by using a callback interface pre-registered in the server, store the contents of the callback messages in a local database, determine the message push quantity according to the contents of the callback messages stored in the local database, compare the message push quantity with a preset expected result for verification, and statistically display the normally arrived push results through the comparison verification, thereby being capable of truly and directly feeding back the message push capability of the current system (server) and whether the messages have backlog, and realizing full automation without manual intervention, has real-time performance.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for automatically checking an arrival rate of a message push according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an automatic checking apparatus for message push arrival rate according to an embodiment of the present invention;
fig. 3 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The following further describes embodiments of the present invention with reference to the accompanying drawings. The following examples are only for illustrating the technical solutions of the present invention more clearly, and the protection scope of the present invention is not limited thereby.
Fig. 1 shows a schematic flowchart of an automatic verification method for an arrival rate of message pushing according to an embodiment of the present invention, and as shown in fig. 1, the automatic verification method for an arrival rate of message pushing according to the embodiment includes:
and S1, the simulation client sends a trigger request to the server so that the server pushes the message to the plurality of clients.
It will be appreciated that the server is pushing messages to multiple clients asynchronously.
It can be understood that, in the prior art, after the client sends the trigger request to the server, the server pushes the message to the multiple clients, in this embodiment, a verifier (the verifier may be a server/processor, etc.) is added locally to the server, and the verifier simulates the client sending the trigger request to the server, so that the server pushes the message to the multiple clients.
S2, receiving a callback message sent by the server after pushing the message to a plurality of clients by using a callback (callback) interface registered in the server in advance, and storing the content of the callback message in a local database.
Specifically, the content of the callback message may include: whether to push the message to the client and to which client the message was pushed, etc.
S3, determining the message pushing quantity according to the content of the callback message stored in the local database, and comparing and checking the message pushing quantity with a preset expected result.
And S4, carrying out statistical display on the normally arrived pushing results passing the comparison check.
It can be understood that, in this step, the arrival rate of the message push can be counted.
The method for automatically verifying the message push arrival rate provided by this embodiment simulates the client sending a trigger request to the server to make the server send messages to a plurality of clients by adding a verifier, receives callback messages sent after the server pushes messages to the plurality of clients by using a callback interface pre-registered in the server, and stores the contents of the callback messages in a local database, determining the message pushing quantity according to the contents of the callback messages stored in the local database, comparing the message pushing quantity with a preset expected result for verification, performing statistical display on the normally arrived pushing results passing the verification, therefore, the message pushing capacity of the current system (server) can be really and directly fed back, whether the message is overstocked or not can be really and directly fed back, the whole process is automatic, manual intervention is not needed, and the real-time performance is realized.
Further, on the basis of the above embodiment, before the step S2, the method according to this embodiment may further include a step not shown in the figure:
sending a registration request to a server, so that the server registers a callback (callback) interface according to the registration request.
Thus, the step S2 may receive, by using the callback interface, a callback message sent after the server pushes a message to a plurality of clients.
Further, on the basis of the above embodiment, after the step S2, the method of this embodiment may further include a step not shown in the figure:
and if the pushing of the message is not completed according to the contents of the callback message stored in the local database after the preset time period is exceeded, displaying an error, recording the number of the messages which are pushed, and going to a message task queue (kafka) to check which examples the message which is not pushed belongs to.
In a specific application, for example, the preset time period may be 10 minutes, which is not limited in this embodiment and may be set according to an actual situation.
It can be understood that the message task removal queue checks which instances the messages that are not pushed are, and can determine which instances have a larger number of messages that are not consumed, so that the module that needs to be optimized can be known.
The automatic verification method for the message push arrival rate provided by the embodiment can truly and directly feed back the message push capability of the current system (server) and whether the message has backlog, is automatic in the whole process, does not need manual intervention, and has real-time performance.
Fig. 2 is a schematic structural diagram of an automatic checking apparatus for a message push arrival rate according to an embodiment of the present invention, and as shown in fig. 2, the automatic checking apparatus for a message push arrival rate according to the embodiment includes: the simulation module 21, the receiving module 22, the verification module 23 and the display module 24; wherein:
the simulation module 21 is configured to simulate a client sending a trigger request to a server, so that the server pushes a message to multiple clients;
the receiving module 22 is configured to receive, by using a callback (callback) interface pre-registered in the server, a callback message sent by the server after pushing a message to a plurality of clients, and store the content of the callback message in a local database;
the checking module 23 is configured to determine the message pushing quantity according to the content of the callback message stored in the local database, and compare the message pushing quantity with a preset expected result for checking;
the display module 24 is configured to perform statistical display on the normally-reached push result passing the comparison and verification.
It can be understood that, in the prior art, after a client sends a trigger request to a server, the server pushes a message to a plurality of clients, in this embodiment, a verifier (i.e., an automatic verification device for the message push arrival rate in this embodiment) is added locally to the server, and the simulation module 21 in the verifier simulates that the client sends the trigger request to the server, so that the server pushes the message to the plurality of clients; the receiving module 22 receives a callback message sent by the server after the server pushes a message to a plurality of clients by using a callback interface registered in the server in advance, and stores the content of the callback message in a local database; the checking module 23 determines the message pushing quantity according to the content of the callback message stored in the local database, and compares the message pushing quantity with a preset expected result for checking; the display module 24 performs statistical display on the normally-reached push result passing the comparison check.
In a specific application, the content of the callback message may include: whether to push the message to the client and to which client the message was pushed, etc.
It will be appreciated that the server is pushing messages to multiple clients asynchronously.
It is understood that the presentation module 24 may count the arrival rate of the message push.
The present embodiment provides an automatic checking device for message push arrival rate, where a trigger request is sent to a server by a simulation client, so that the server pushes messages to a plurality of clients, a callback interface pre-registered in the server is used to receive callback messages sent after the server pushes messages to the plurality of clients, the contents of the callback messages are stored in a local database, the number of message pushes is determined according to the contents of the callback messages stored in the local database, the number of message pushes is compared with a preset expected result for checking, and a normally-arriving push result obtained through the comparison for checking is statistically displayed, so that the message push capability of a current system (server) can be truly and directly fed back, and whether a message has backlog or not, and the whole process is automated without manual intervention and has real-time performance.
Further, on the basis of the above embodiment, the apparatus of this embodiment may further include:
the sending module is used for sending a registration request to the server so that the server registers a callback interface according to the registration request.
Therefore, the receiving module 22 may receive the callback message sent after the server pushes the message to the multiple clients by using the callback interface.
Further, on the basis of the above embodiment, the apparatus of this embodiment may further include:
and the display module is used for determining that message pushing is not completed according to the contents of the callback messages stored in the local database after a preset time period is exceeded, displaying an error, recording the number of the messages which are pushed, and going to a message task queue (kafka) to check which examples the messages which are not pushed belong to.
In a specific application, for example, the preset time period may be 10 minutes, which is not limited in this embodiment and may be set according to an actual situation.
It can be understood that the display module goes to the message task queue to see which instances the messages that are not pushed are, and can determine which instances have a larger number of messages that are not consumed, so that the module that needs to be optimized can be known.
The automatic checking device for the message push arrival rate provided by the embodiment can truly and directly feed back the message push capability of the current system (server) and whether the message has backlog, is automatic in the whole process, does not need manual intervention, and has real-time performance.
The automatic checking apparatus for message push arrival rate of this embodiment may be configured to implement the technical solution of the foregoing method embodiment, and the implementation principle and the technical effect are similar, which are not described herein again.
Fig. 3 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention, and as shown in fig. 3, the electronic device may include: a processor 301, a memory 302, a bus 303, and computer programs stored on the memory 302 and operable on the processor 301;
wherein, the processor 301 and the memory 302 complete the communication with each other through the bus 303;
when the processor 301 executes the computer program, the method provided by the above method embodiment is implemented, for example, including: the method comprises the steps that a simulation client sends a trigger request to a server so that the server pushes messages to a plurality of clients; receiving callback messages sent by the server after the server pushes messages to a plurality of clients by using a callback interface registered in the server in advance, and storing the contents of the callback messages to a local database; determining the message pushing quantity according to the contents of the callback messages stored in the local database, and comparing and checking the message pushing quantity with a preset expected result; and carrying out statistical display on the normally arrived pushing results which pass the comparison verification.
An embodiment of the present invention provides a non-transitory computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program implements the method provided by the above method embodiment, for example, the method includes: the method comprises the steps that a simulation client sends a trigger request to a server so that the server pushes messages to a plurality of clients; receiving callback messages sent by the server after the server pushes messages to a plurality of clients by using a callback interface registered in the server in advance, and storing the contents of the callback messages to a local database; determining the message pushing quantity according to the contents of the callback messages stored in the local database, and comparing and checking the message pushing quantity with a preset expected result; and carrying out statistical display on the normally arrived pushing results which pass the comparison verification.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus, and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means/systems for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element. The terms "upper", "lower", and the like, indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience in describing the present invention and simplifying the description, but do not indicate or imply that the referred devices or elements must have a specific orientation, be constructed and operated in a specific orientation, and thus, should not be construed as limiting the present invention. Unless expressly stated or limited otherwise, the terms "mounted," "connected," and "connected" are intended to be inclusive and mean, for example, that they may be fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood by those skilled in the art according to specific situations.
In the description of the present invention, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description. Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present invention is not limited to any single aspect, nor is it limited to any single embodiment, nor is it limited to any combination and/or permutation of these aspects and/or embodiments. Moreover, each aspect and/or embodiment of the present invention may be utilized alone or in combination with one or more other aspects and/or embodiments thereof.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present invention, and they should be construed as being included in the following claims and description.
Claims (6)
1. A method for automatically checking message push arrival rate is characterized by comprising the following steps:
the method comprises the steps that a simulation client sends a trigger request to a server so that the server pushes messages to a plurality of clients;
receiving callback messages sent by the server after the server pushes messages to a plurality of clients by using a callback interface registered in the server in advance, and storing the contents of the callback messages to a local database;
determining the message pushing quantity according to the contents of the callback messages stored in the local database, and comparing and checking the message pushing quantity with a preset expected result;
carrying out statistical display on the normally arrived pushing results which pass the comparison and verification;
the contents of the callback message include: whether to push the message to the client and to which client the message was pushed;
after receiving, by using a callback interface pre-registered in the server, a callback message sent by the server after pushing a message to a plurality of clients, and storing the content of the callback message in a local database, the method further includes:
if the message pushing is not completed according to the contents of the callback messages stored in the local database after the preset time period is exceeded, displaying an error, recording the number of the messages which are pushed, and going to a message task queue to check which examples the messages which are not pushed belong to;
and determining the module needing to be optimized according to the number of the messages which are not pushed completely of the example.
2. The method of claim 1, wherein before receiving the callback message sent by the server after pushing the message to the plurality of clients by using the callback interface pre-registered in the server, the method further comprises:
and sending a registration request to a server so that the server registers a callback interface according to the registration request.
3. An apparatus for automatic verification of message push arrival rate, comprising:
the simulation module is used for simulating a client to send a trigger request to a server so that the server pushes messages to a plurality of clients;
the receiving module is used for receiving callback messages sent by the server after the server pushes the messages to the plurality of clients by utilizing a callback interface registered in the server in advance, and storing the contents of the callback messages to a local database;
the verification module is used for determining the message pushing quantity according to the contents of the callback messages stored in the local database and comparing and verifying the message pushing quantity with a preset expected result;
the display module is used for carrying out statistical display on the normally arrived pushing results which pass the comparison and verification;
the contents of the callback message include: whether to push the message to the client and to which client the message was pushed;
the device further comprises:
the display module is used for determining that message pushing is not completed according to the contents of the callback messages stored in the local database after a preset time period is exceeded, displaying an error, recording the number of the messages which are pushed, and going to a message task queue to check which examples the messages which are not pushed are in;
and determining the module needing to be optimized according to the number of the messages which are not pushed completely of the example.
4. The apparatus of claim 3, further comprising:
and the sending module is used for sending a registration request to the server so that the server registers a callback interface according to the registration request.
5. An electronic device, comprising: a processor, a memory, a bus, and a computer program stored on the memory and executable on the processor;
the processor and the memory complete mutual communication through the bus;
the processor, when executing the computer program, implements the method of claim 1 or 2.
6. A non-transitory computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, implements the method of claim 1 or 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810593553.0A CN108737218B (en) | 2018-06-11 | 2018-06-11 | Automatic verification method and device for message push arrival rate |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810593553.0A CN108737218B (en) | 2018-06-11 | 2018-06-11 | Automatic verification method and device for message push arrival rate |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108737218A CN108737218A (en) | 2018-11-02 |
| CN108737218B true CN108737218B (en) | 2020-12-01 |
Family
ID=63932772
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810593553.0A Active CN108737218B (en) | 2018-06-11 | 2018-06-11 | Automatic verification method and device for message push arrival rate |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108737218B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109657152B (en) * | 2018-12-27 | 2021-02-19 | 北京顺丰同城科技有限公司 | Push message sending method and device, electronic equipment and readable storage medium |
| CN110248030B (en) * | 2019-05-22 | 2022-05-17 | 深圳壹账通智能科技有限公司 | Method, device, equipment and storage medium for testing short message compensation mechanism |
| CN110620699B (en) * | 2019-08-02 | 2021-12-28 | 北京字节跳动网络技术有限公司 | Message arrival rate determination method, device, equipment and computer readable storage medium |
| CN111327915A (en) * | 2020-02-21 | 2020-06-23 | 北京字节跳动网络技术有限公司 | Method and device for determining message arrival rate |
| CN112887397B (en) * | 2021-01-22 | 2022-10-11 | 山东众阳健康科技集团有限公司 | Message pushing method and system based on interface |
| CN113177178A (en) * | 2021-04-30 | 2021-07-27 | 北京深演智能科技股份有限公司 | Message processing method and device, nonvolatile storage medium and processor |
| CN114448968B (en) * | 2021-12-15 | 2023-01-10 | 广州市玄武无线科技股份有限公司 | Pushed amount checking method and device, electronic equipment and storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101345415B1 (en) * | 2011-01-31 | 2014-01-29 | 주식회사 케이티 | Method for transmitting push message, mobile terminal receiving the push message and system thereof |
| CN102868726B (en) * | 2012-08-23 | 2015-07-22 | 北京神鹰城讯科技有限公司 | Method and system for publishing Internet information |
| CN105791352B (en) * | 2014-12-24 | 2020-05-29 | 深圳市腾讯计算机系统有限公司 | Message pushing method and system for application |
| CN107528922A (en) * | 2017-09-29 | 2017-12-29 | 深圳市金立通信设备有限公司 | A kind of information push method, terminal and computer-readable recording medium |
-
2018
- 2018-06-11 CN CN201810593553.0A patent/CN108737218B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108737218A (en) | 2018-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108737218B (en) | Automatic verification method and device for message push arrival rate | |
| CN103067884B (en) | A kind of processing method of warning message and device | |
| CN109656700A (en) | Distributed link tracking, system, equipment and storage medium under multi-tenant | |
| CN108572970B (en) | Structured data processing method and distributed processing system | |
| US10505881B2 (en) | Generating message envelopes for heterogeneous events | |
| CN112367345A (en) | Data processing method, server device and computer readable storage medium | |
| CN113157545A (en) | Method, device and equipment for processing service log and storage medium | |
| US9973306B2 (en) | Freshness-sensitive message delivery | |
| CN114064208A (en) | Method and device for detecting application service state, electronic equipment and storage medium | |
| CN110806960A (en) | Information processing method and device and terminal equipment | |
| CN105634929A (en) | Instant messaging method and device based on web page | |
| CN113609088A (en) | File processing method, device and equipment | |
| CN107316494A (en) | A kind of abnormal treating method and apparatus in parking lot | |
| CN110737655A (en) | Method and device for reporting data | |
| US11451463B2 (en) | System and method for interactivity testing of text-based customer communications | |
| CN113098978B (en) | Data transmission method, device and medium | |
| CN110875832A (en) | Abnormal service monitoring method, device and system and computer readable storage medium | |
| CN112860770B (en) | Report generation method, report generation device, electronic equipment and storage medium | |
| CN111401819B (en) | Intersystem data pushing method and system | |
| CN114615325A (en) | Message pushing method and device, computer equipment and storage medium | |
| CN110213322B (en) | Content publishing processing method, client and server for community | |
| CN110134547B (en) | Middleware-based repeated data deleting method and related device | |
| CN111290897A (en) | Asynchronous storage test method, electronic device, computer equipment and storage medium | |
| CN104935492A (en) | E-mail verification method, device and system | |
| CN110543470A (en) | Message early warning method and device, storage medium and electronic device |
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 | ||
| CB02 | Change of applicant information |
Address after: 100088 Building 3 332, 102, 28 Xinjiekouwai Street, Xicheng District, Beijing Applicant after: Qianxin Technology Group Co.,Ltd. Address before: 100015 Jiuxianqiao Chaoyang District Beijing Road No. 10, building 15, floor 17, layer 1701-26, 3 Applicant before: Beijing Qi'anxin Technology Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |