CN111901227A - Simple and lightweight message real-time pushing system and implementation method thereof - Google Patents
Simple and lightweight message real-time pushing system and implementation method thereof Download PDFInfo
- Publication number
- CN111901227A CN111901227A CN202010757700.0A CN202010757700A CN111901227A CN 111901227 A CN111901227 A CN 111901227A CN 202010757700 A CN202010757700 A CN 202010757700A CN 111901227 A CN111901227 A CN 111901227A
- Authority
- CN
- China
- Prior art keywords
- message
- identifier
- microprocessor
- app client
- unique
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 24
- 238000004891 communication Methods 0.000 claims abstract description 17
- 238000001514 detection method Methods 0.000 claims description 28
- 238000012790 confirmation Methods 0.000 claims description 21
- 238000004140 cleaning Methods 0.000 claims description 15
- 230000032683 aging Effects 0.000 claims description 5
- 230000000737 periodic effect Effects 0.000 claims 1
- 238000003032 molecular docking Methods 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 3
- 239000000284 extract Substances 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000018109 developmental process Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- LDSJMFGYNFIFRK-UHFFFAOYSA-N 3-azaniumyl-2-hydroxy-4-phenylbutanoate Chemical compound OC(=O)C(O)C(N)CC1=CC=CC=C1 LDSJMFGYNFIFRK-UHFFFAOYSA-N 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
- H04L51/043—Real-time or near real-time messaging, e.g. instant messaging [IM] using or handling presence information
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a simple and lightweight real-time message pushing system and an implementation method thereof, belonging to the technical field of mobile internet instant message pushing, wherein the system comprises an APP client, an instant message system and a message pushing platform, wherein the APP client communicates with the instant message system through a wireless network according to a full-duplex communication mode, and the instant message system communicates with the message pushing platform through the wireless network according to the full-duplex communication mode; the APP client is a user mobile device APP; the instant messaging system is a back-end server system that provides communication services. The simple and light message real-time pushing system and the implementation method thereof avoid the problems of message unreachable after the mobile terminal is recovered or message loss after the network is disconnected and reconnected, and can provide a message pushing platform to ensure that the message can be reached in any situation, the service docking is simple and easy, the service is light and fast, and the message can be reached in real time.
Description
Technical Field
The invention relates to the technical field of instant message pushing of mobile internet, in particular to a simple and light message real-time pushing system and an implementation method thereof.
Background
The mobile internet is a necessary product of the development of the PC internet, and combines both mobile communication and the internet into a whole. It is a general term for the technology, platform, business model and application of the internet combined with and practiced by mobile communication technology. The network inherits the advantages of opening, sharing and interacting with the internet at any time and any place, is a new generation of open telecommunication basic network which is nationwide, takes broadband IP as a technical core and can simultaneously provide high-quality telecommunication services such as voice, fax, data, images, multimedia and the like, and the wireless access is provided by operators, and the internet enterprises provide various mature applications.
In the last decade accompanied by the rapid development of mobile internet, wireless mobile office has become the trend of times, and "information intercommunication" is the lowest "threshold" of a piece of mobile office software.
Because the mobile phone system restricts that any APP stays in the background for a certain time and is recycled by the system, how to achieve the 'information intercommunication message must be achieved' is a technical problem that must be overcome, and at present, a method for solving the technical problem does not exist, so that a simple and lightweight real-time message pushing system and an implementation method thereof are urgently needed to solve the problem.
Disclosure of Invention
The invention aims to provide a simple and light message real-time pushing system and an implementation method thereof, which can avoid the problems of message unreachable after a mobile terminal is recovered or message loss after network disconnection and reconnection and the like, can provide a message pushing platform to ensure that the message can be reached in any situation, and has simple service docking, light and quick service and real-time message reaching so as to solve the problems provided in the background technology.
In order to achieve the purpose, the invention provides the following technical scheme:
a simple and lightweight real-time message pushing system comprises an APP client, an instant message system and a message pushing platform, wherein the APP client communicates with the instant message system through a wireless network in a full-duplex communication mode, and the instant message system communicates with the message pushing platform through the wireless network in the full-duplex communication mode;
the APP client is a user mobile device APP;
the instant message system is a back-end server system providing communication service;
and the message pushing platform is a background server system which pushes a message body generated by the APP client side A in the instant message system to the APP client side B through the message pushing platform.
Further, the APP client carries a terminal device information identifier and a user information identifier, and the instant messaging system carries a device information identifier.
Further, a microprocessor, a storage module, a judgment unit and an execution unit are arranged on the message pushing platform, the instant message system is electrically connected with the microprocessor, the output end of the microprocessor is electrically connected with the input end of the storage module, the output end of the storage module is electrically connected with the input end of the judgment unit, the judgment unit is electrically connected with the microprocessor, and the output end of the microprocessor is electrically connected with the input end of the execution unit.
Further, the message pushing platform is provided with a detection unit and a cleaning unit, the microprocessor is electrically connected with the detection unit, the output end of the detection unit is electrically connected with the input end of the storage module, the output end of the microprocessor is also electrically connected with the input end of the cleaning unit, and the output end of the cleaning unit is electrically connected with the input end of the storage module.
According to another aspect of the present invention, there is provided a simple and lightweight method for implementing a message real-time push system, including the following steps:
s10: establishing connection between an instant message system and an APP client, wherein the APP client carries a terminal equipment information identifier and a user information identifier to log in the instant message system;
s20: establishing connection between a message pushing platform and an instant message system, wherein the instant message system carries equipment information registration message pushing platform;
s30: grouping and storing equipment information by using an equipment ID unique identifier in the message pushing platform, generating an unordered unique sequence identifier, and generating an identity authentication unique identifier by using a cryptographic algorithm;
s40: establishing connection between an instant message system and a message pushing platform, and recording a unique equipment identifier and a unique identity authentication identifier after the instant message system obtains a response of the message pushing platform;
s50: and establishing connection between the APP client and the instant message system, and returning the identity authentication unique identifier to the APP client by the instant message system.
Further, S30 includes the following steps:
s301: establishing connection between a microprocessor and an instant message system, wherein the microprocessor receives an equipment information identifier carried by the instant message system;
s302: the judging unit is respectively connected with the storage module and the microprocessor, and whether the equipment information identifier carried by the instant message system received by the microprocessor is the unique identity authentication identifier in the storage module is judged by the judging unit;
s303: the microprocessor is connected with a judging unit, and the judging unit feeds back the judging result to the microprocessor after judging;
s304: the execution unit is connected with the microprocessor, and if the equipment information identifier carried by the instant message system received by the microprocessor is the unique identity authentication identifier, the execution unit executes a command of storing the unique identity authentication identifier by the storage module;
s305: and the execution unit is connected with the microprocessor, and the equipment information identifier carried by the instant message system received by the microprocessor is not the unique identity authentication identifier, so that the execution unit can clear the equipment information identifier carried by the instant message system received by the microprocessor.
Further, S304 includes the steps of:
s3041: the detection unit is connected with the microprocessor, and the microprocessor controls the detection unit to detect the storage space of the storage module;
s3042: the storage module is connected with the detection unit, the detection unit detects the storage space of the storage module, and the detection result is fed back to the microprocessor.
S3043: after the detection unit detects the storage space of the storage module is not full, the execution unit executes the command of the storage module for storing the unique identity authentication identification.
S3044: after the detection unit detects that the storage space of the storage module is full, the cleaning unit cleans the storage space of the storage module according to a priority algorithm and stores a new identity authentication unique identifier in the storage module.
Further, when the message pushing platform pushes information to the APP client, the APP client triggers an ACK confirmation event after receiving the information and sends the ACK confirmation event to the message pushing platform, and the message pushing platform clears the period retransmission aging queue after receiving the ACK confirmation event.
Compared with the prior art, the invention has the beneficial effects that:
the invention relates to a simple and light message real-time pushing system and an implementation method thereof, wherein a user APP client A sends an instant message to a user APP client B, the instant message system can recognize the current state of the user APP client B, if the user APP client B verifies that a user information identifier is in a background state, the instant message system assembles the message, the message pushing platform fixes a message body and then sends the message body to a message pushing platform, the message pushing platform extracts the unique device identifier serial number from the message body to verify device information, if the message is healthy, the message is pushed to the user APP client B according to the device identifier information, when the message pushing platform pushes the message to the APP client, the APP client triggers an ACK confirmation event after receiving the message and sends the ACK confirmation event to the message pushing platform, the message pushing platform clears a period re-aging queue after receiving the ACK confirmation event, the problems that the message is not reachable after the mobile terminal is recovered or the message is lost after the network is disconnected and reconnected and the like are solved, a message pushing platform can be provided to ensure that the message can be reached in any condition, the service is simple and easy to connect, the service is light and quick, and the message can be reached in real time.
Drawings
FIG. 1 is a diagram of a simple and lightweight message real-time push system according to the present invention;
FIG. 2 is a block diagram of a simple and lightweight real-time message pushing system according to the present invention;
FIG. 3 is a timing diagram illustrating a user APP client registration process in accordance with the present invention;
FIG. 4 is a flowchart of a user APP client registration process of the present invention;
FIG. 5 is a flowchart illustrating authentication of a user APP client according to the present invention;
FIG. 6 is a timing diagram of message acknowledgement in accordance with the present invention;
FIG. 7 is an overall flow chart of message pushing according to the present invention;
FIG. 8 is a detailed flow chart of the push platform interior of the present invention;
FIG. 9 is a diagram of a user APP client identity authentication module of the present invention;
fig. 10 is a diagram of an identity authentication unique identifier storage module of the present invention.
In the figure: 1. an APP client; 2. an instant messaging system; 3. a message push platform; 31. a microprocessor; 32. a storage module; 33. a judgment unit; 34. an execution unit; 35. a detection unit; 36. and a cleaning unit.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
Referring to fig. 1-2, a simple and lightweight real-time message pushing system includes an APP client 1, an instant message system 2, and a message pushing platform 3, where the APP client 1 communicates with the instant message system 2 in a full-duplex communication manner through a wireless network, the instant message system 2 communicates with the message pushing platform 3 in the full-duplex communication manner through the wireless network, the APP client 1 carries a terminal device information identifier and a user information identifier, and the instant message system 2 carries a device information identifier;
the APP client 1 is a user mobile device APP;
the instant message system 2 is a back-end server system providing communication service;
the message pushing platform 3 is a background server system for pushing a message body generated by the APP client 1A in the instant message system 2 to the APP client 1B through the message pushing platform 3.
When the APP client 1 logs in, the strategy identification information is registered in the instant message system 2, the equipment identification information in the strategy is registered in the message pushing platform 3, the message pushing platform 3 responds to the unique and time-efficient identity authentication identification and contains the current equipment unique identification in the message pushing platform 3, and the APP client 1 directly conducts legal identity verification to the message pushing platform 3 according to the responded identity authentication unique identification.
When the messages of the user APP client 1 are intercommunicated, the instant message system 2 captures the user strategy identification of the message receiver and throws the messages into the message pushing platform 3, and the message pushing platform 3 finds the corresponding device information according to the unique device identifier responded before and pushes the messages to the user APP client 1.
The message pushing platform 3 is provided with a microprocessor 31, a storage module 32, a judging unit 33 and an executing unit 34, the instant message system 2 is electrically connected with the microprocessor 31, an output end of the microprocessor 31 is electrically connected with an input end of the storage module 32, an output end of the storage module 32 is electrically connected with an input end of the judging unit 33, the judging unit 33 is electrically connected with the microprocessor 31, and an output end of the microprocessor 31 is electrically connected with an input end of the executing unit 34.
Referring to fig. 3 to fig. 8, in order to better show the implementation flow of the simple and lightweight message real-time pushing system, the embodiment now proposes an implementation method of the simple and lightweight message real-time pushing system, which includes the following steps:
s10: establishing connection between an instant message system 2 and an APP client 1, wherein the APP client 1 carries a terminal equipment information identifier and a user information identifier to log in the instant message system 2;
s20: establishing a connection between the message pushing platform 3 and the instant message system 2, wherein the instant message system 2 carries equipment information to register the message pushing platform 3;
s30: the information pushing platform 3 stores the equipment information in a grouping mode by using the unique equipment ID identification, generates an unordered unique sequence identification and then generates an unique identity authentication identification through a cryptographic algorithm;
s40: establishing connection between the instant message system 2 and the message pushing platform 3, and recording the unique equipment identifier and the unique identity authentication identifier after the instant message system 2 receives the response of the message pushing platform 3;
s50: the APP client 1 is connected with the instant message system 2, and the instant message system 2 returns the unique identity authentication identifier to the APP client 1.
The user APP client 1A sends an instant message to the user APP client 1B, the instant message system 2 can recognize the current state of the user APP client 1B, if the user APP client 1B verifies that the user information identifier is in a background state, the instant message system 2 assembles the message, the message pushing platform 3 fixes the message body and then sends the message body to the message pushing platform 3, the message pushing platform 3 extracts the equipment unique identifier serial number from the message body to verify the equipment information, if the message is healthy, the message is pushed to the user APP client 1B according to the equipment identifier information, when the message pushing platform 3 pushes the message to the APP client 1, the APP client 1 triggers an ACK confirmation event after receiving the message, and sends the ACK confirmation event to the message pushing platform 3, the message pushing platform 3 clears a period re-sending aging queue after receiving the ACK confirmation event, and avoids the problems that the message is not reachable after the mobile terminal is recovered or the message is lost after network disconnection and reconnection, the message pushing platform 3 can be provided to ensure that the message can be reached in any situation, the service docking is simple, the service is light and fast, and the message can be reached in real time.
Referring to fig. 9, S30 includes the steps of:
s301: establishing connection between the microprocessor 31 and the instant message system 2, and receiving the equipment information identifier carried by the instant message system 2 by the microprocessor 31;
s302: the judging unit 33 is respectively connected with the storage module 32 and the microprocessor 31, and the judging unit 33 is used for judging whether the equipment information identifier carried by the instant message system 2 received by the microprocessor 31 is an identity authentication unique identifier in the storage module 32;
s303: the microprocessor 31 is connected with the judging unit 33, and the judging unit 33 feeds back the judgment result to the microprocessor 31 after judging;
s304: the execution unit 34 is connected with the microprocessor 31, and if the device information identifier carried by the instant message system 2 received by the microprocessor 31 is the unique identity authentication identifier, the execution unit 34 executes a command of storing the unique identity authentication identifier in the storage module 32;
s305: the execution unit 34 is connected to the microprocessor 31, and if the device information identifier carried by the instant message system 2 received by the microprocessor 31 is not the unique identity authentication identifier, the execution unit 34 will clear the device information identifier carried by the instant message system 2 received by the microprocessor 31.
The microprocessor 31 receives the device information identifier carried by the instant message system 2, and the determining unit 33 determines whether the device information identifier carried by the instant message system 2 received by the microprocessor 31 is the unique identifier for identity authentication in the storage module 32, if the device information identifier is the unique identifier for identity authentication, the executing unit 34 will execute the command of the storage module 32 for storing the unique identifier for identity authentication, and if the device information identifier is not the unique identifier for identity authentication, the executing unit 34 will clear the device information identifier carried by the instant message system 2 received by the microprocessor 31.
Example two
A simple and light message real-time pushing system comprises an APP client 1, an instant message system 2 and a message pushing platform 3, wherein the APP client 1 communicates with the instant message system 2 through a wireless network in a full-duplex communication mode, the instant message system 2 communicates with the message pushing platform 3 through the wireless network in the full-duplex communication mode, the APP client 1 carries a terminal equipment information identifier and a user information identifier, and the instant message system 2 carries an equipment information identifier;
the APP client 1 is a user mobile device APP;
the instant message system 2 is a back-end server system providing communication service;
the message pushing platform 3 is a background server system for pushing a message body generated by the APP client 1A in the instant message system 2 to the APP client 1B through the message pushing platform 3.
The message pushing platform 3 is provided with a microprocessor 31, a storage module 32, a judging unit 33 and an executing unit 34, the instant message system 2 is electrically connected with the microprocessor 31, an output end of the microprocessor 31 is electrically connected with an input end of the storage module 32, an output end of the storage module 32 is electrically connected with an input end of the judging unit 33, the judging unit 33 is electrically connected with the microprocessor 31, and an output end of the microprocessor 31 is electrically connected with an input end of the executing unit 34.
The message pushing platform 3 is provided with a detection unit 35 and a cleaning unit 36, the microprocessor 31 is electrically connected with the detection unit 35, the output end of the detection unit 35 is electrically connected with the input end of the storage module 32, the output end of the microprocessor 31 is also electrically connected with the input end of the cleaning unit 36, and the output end of the cleaning unit 36 is electrically connected with the input end of the storage module 32.
In order to better show the implementation flow of the simple and lightweight message real-time pushing system, this embodiment now provides an implementation method of the simple and lightweight message real-time pushing system, including the following steps:
s10: establishing connection between an instant message system 2 and an APP client 1, wherein the APP client 1 carries a terminal equipment information identifier and a user information identifier to log in the instant message system 2;
s20: establishing a connection between the message pushing platform 3 and the instant message system 2, wherein the instant message system 2 carries equipment information to register the message pushing platform 3;
s30: the information pushing platform 3 stores the equipment information in a grouping mode by using the unique equipment ID identification, generates an unordered unique sequence identification and then generates an unique identity authentication identification through a cryptographic algorithm;
s40: establishing connection between the instant message system 2 and the message pushing platform 3, and recording the unique equipment identifier and the unique identity authentication identifier after the instant message system 2 receives the response of the message pushing platform 3;
s50: the APP client 1 is connected with the instant message system 2, and the instant message system 2 returns the unique identity authentication identifier to the APP client 1.
S30 includes the steps of:
s301: establishing connection between the microprocessor 31 and the instant message system 2, and receiving the equipment information identifier carried by the instant message system 2 by the microprocessor 31;
s302: the judging unit 33 is respectively connected with the storage module 32 and the microprocessor 31, and the judging unit 33 is used for judging whether the equipment information identifier carried by the instant message system 2 received by the microprocessor 31 is an identity authentication unique identifier in the storage module 32;
s303: the microprocessor 31 is connected with the judging unit 33, and the judging unit 33 feeds back the judgment result to the microprocessor 31 after judging;
s304: the execution unit 34 is connected with the microprocessor 31, and if the device information identifier carried by the instant message system 2 received by the microprocessor 31 is the unique identity authentication identifier, the execution unit 34 executes a command of storing the unique identity authentication identifier in the storage module 32;
s305: the execution unit 34 is connected to the microprocessor 31, and if the device information identifier carried by the instant message system 2 received by the microprocessor 31 is not the unique identity authentication identifier, the execution unit 34 will clear the device information identifier carried by the instant message system 2 received by the microprocessor 31.
Referring to fig. 10, S304 includes the steps of:
s3041: the detection unit 35 is connected with the microprocessor 31, and the microprocessor 31 controls the detection unit 35 to detect the storage space of the storage module 32;
s3042: the storage module 32 is connected with the detection unit 35, the detection unit 35 detects the storage space of the storage module 32, and the detection result is fed back to the microprocessor 31.
S3043: after the detection of the detecting unit 35, if the storage space of the storage module 32 is not full, the executing unit 34 will execute the command of the storage module 32 storing the unique identification of the identity authentication.
S3044: after the detection of the detecting unit 35, if the storage space of the storage module 32 is full, the cleaning unit 36 cleans the storage space of the storage module 32 according to the priority algorithm, and stores the new identity authentication unique identifier in the storage module 32.
The microprocessor 31 controls the detection unit 35 to detect the storage space of the storage module 32, the detection unit 35 detects the storage space of the storage module 32, and feeds back the detection result to the microprocessor 31, if the storage space of the storage module 32 is not full, the execution unit 34 executes the command of storing the unique identity authentication identifier in the storage module 32, and if the storage space of the storage module 32 is full, the cleaning unit 36 cleans up the storage space of the storage module 32 according to a priority algorithm, and stores the new unique identity authentication identifier in the storage module 32.
Further, when the message push platform 3 pushes information to the APP client 1, after the APP client 1 receives the information, an ACK confirmation event is triggered and sent to the message push platform 3, and after the message push platform 3 receives the ACK confirmation event, the period retransmission aging queue is cleared.
The embodiment of the application is described in detail by a message real-time must-reach implementation method based on 'worktreasure' converged communication:
the 'worktreasure' is a set of communication software, solution and application system oriented to the mobile internet and used for fusing communication, business office and business social contact.
The components in the example correspond to the invention:
the APP client 1 is a worktreasure client, and is hereinafter referred to by gzbApp;
the APP server is a working treasure server, and is hereinafter referred to by gzbServer;
the message pushing platform 3 is a working treasure pushing server, and is hereinafter referred to by a gzbPush;
other pronouns used in this example are:
pushDeviceId device push unique identifier
PushToken-pushing identity authentication unique identifier
Description of policy information:
| policy value | Description of the invention | Terminal device |
| deviceId | Device ID | IOS/Android |
| deviceToken | Message push Token | IOS/Addroid |
| voipToken | Voip | IOS |
| pushType | APP release environment | IOS |
| isActive | APP client front and back end | IOS/Android |
| isShowMsgDigest | Message non-disturbing | IOS/Android |
| badge | Reminding red dot count | IOS/Android |
| sound | Sound equipment | IOS/Android |
| appId | APNS certificate ID | IOS |
Supporting the docking of a cloud platform, wherein the specific working process of the example is as follows:
enterprise information is applied to a gzbPush management platform to obtain a push license and a message encryption public key; the gzbApp and the gzbServer are integrated into a gzbPush-sdk; after logging in a gzbServer, a gzbApp reports policy information and user information, and the gzbServer registers gzbPush with equipment information to obtain pushdeviceId and pushToken; storing pushDeviceId binding policy information to a gzbServer service, and returning pushToken to a gzbApp; the Android client side gzbApp receives the pushToken request gzbPush to establish a push link channel after passing legal identity verification; when the gzbApp messages are intercommunicated, the gzbServer checks and judges whether the gzbApp is switched back to the background or not according to the user information of the message receiver; the integrated SDK tool is called by the gzbServer to fill and write the public key, the pushDeviceId and the message structure body into a tool method to obtain a gzbPush inherent data parameter body and send the gzbPush inherent data parameter body; after receiving the message, the gzbApp immediately triggers a confirmation notification event callback to the gzbPush to sense that the message arrives, and if the confirmation event callback gzbPush is not found within a certain time, an automatic retransmission mechanism is triggered to ensure that the message arrives certainly.
Supporting privatization deployment, wherein the specific working process of the instance is as follows:
downloading a gzbPush-rpm package from a work treasure warehouse; installing a local service by one key, starting a gzbPush service by one key, and supporting port customization; the gzbApp and the gzbServer are integrated into a gzbPush-sdk; after logging in a gzbServer, a gzbApp reports policy information and user information, and the gzbServer registers gzbPush with equipment information to obtain pushdeviceId and pushToken; the Android client side gzbApp receives the pushToken request gzbPush to establish a push link channel after passing legal identity verification; the gzbServer does not call the SDK by authentication, and a filling message structure body can fill a RabbitMQ-RPC or a direct HTTP method provided by the gzbPush to initiate message pushing; after receiving the message, the gzbApp immediately triggers a confirmation notification event callback to the gzbPush to sense that the message arrives, and if the confirmation event callback is not received within a certain time, the gzbPush triggers an automatic retransmission mechanism to ensure that the message arrives certainly.
To sum up, the simple and lightweight real-time message pushing system and the implementation method thereof of the present invention, a user APP client 1 a sends an instant message to a user APP client 1 b, the instant message system 2 recognizes the current state of the user APP client 1 b, if the user APP client 1 b verifies that the user information identifier is in a background state, the instant message system 2 assembles the message, the message pushing platform 3 fixes the message body and then sends the message body to the message pushing platform 3, the message pushing platform 3 extracts the device information from the message body to verify the device information with the unique device identifier serial number, if the message exists healthily, the message is pushed to the user APP client 1 b according to the device identifier information, when the message pushing platform 3 pushes the message to the APP client 1, after the APP client 1 receives the message, an ACK confirmation event is triggered and an ACK confirmation event is sent to the message pushing platform 3, the message pushing platform 3 clears the period retransmission aging queue after receiving the ACK confirmation event, avoids the problems that the message is inaccessible after the mobile terminal is recovered or the message is lost after the network is disconnected and reconnected, and the like, can provide the message pushing platform 3 to ensure that the message can be reached in any situation, the service docking is simple, the service is light and fast, and the message can be reached in real time.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art should be able to cover the technical solutions and the inventive concepts of the present invention within the technical scope of the present invention.
Claims (8)
1. A simple and lightweight real-time message pushing system is characterized by comprising an APP client (1), an instant message system (2) and a message pushing platform (3), wherein the APP client (1) communicates with the instant message system (2) through a wireless network in a full-duplex communication manner, and the instant message system (2) communicates with the message pushing platform (3) through the wireless network in the full-duplex communication manner;
the APP client (1) is a user mobile device APP;
the instant message system (2) is a back-end server system providing communication service;
the message pushing platform (3) is a background server system which pushes a message body generated by the APP client (1) A in the instant message system (2) to the APP client (1) B through the message pushing platform (3).
2. The simple and lightweight real-time message pushing system according to claim 1, wherein the APP client (1) carries a terminal device information identifier and a user information identifier, and the instant message system (2) carries a device information identifier.
3. The simple and lightweight real-time message pushing system according to claim 1, wherein a microprocessor (31), a storage module (32), a judgment unit (33) and an execution unit (34) are disposed on the message pushing platform (3), the instant message system (2) is electrically connected to the microprocessor (31), an output of the microprocessor (31) is electrically connected to an input of the storage module (32), an output of the storage module (32) is electrically connected to an input of the judgment unit (33), the judgment unit (33) is electrically connected to the microprocessor (31), and an output of the microprocessor (31) is electrically connected to an input of the execution unit (34).
4. A simple and lightweight real-time message pushing system as claimed in claim 3, wherein a detection unit (35) and a cleaning unit (36) are provided on the message pushing platform (3), the microprocessor (31) is electrically connected to the detection unit (35), an output of the detection unit (35) is electrically connected to an input of the storage module (32), an output of the microprocessor (31) is also electrically connected to an input of the cleaning unit (36), and an output of the cleaning unit (36) is electrically connected to an input of the storage module (32).
5. A method for implementing a simple and lightweight real-time message pushing system according to any one of claims 1 to 4, comprising the following steps:
s10: carrying a terminal device information identifier and a user information identifier for login;
s20: registering the information of the carried equipment;
s30: the unique ID of the equipment is grouped to store equipment information, and after a disordered unique sequence identifier is generated, an identity authentication unique identifier is generated through a cryptographic algorithm;
s40: recording the unique identification of the equipment and the unique identification of the identity authentication after response;
s50: and returning the unique identification of the identity authentication.
6. The method for implementing the simple and lightweight real-time message pushing system according to claim 5, wherein the step S30 includes the following steps:
s301: carrying equipment information identification;
s302: judging whether the received equipment information identifier is an identity authentication unique identifier or not;
s303: after the judgment, the judgment result is fed back;
s304: if the carried equipment information identifier is the unique identity authentication identifier, executing a command for storing the unique identity authentication identifier;
s305: and if the carried equipment information identifier is not the unique identity authentication identifier, cleaning the carried equipment information identifier.
7. The method for implementing the simple and lightweight message real-time push system according to claim 6, wherein S304 comprises the following steps:
s3041: detecting a storage space;
s3042: and detecting the storage space and feeding back the detection result.
S3043: and if the storage space is not full, executing a command for storing the unique identification of the identity authentication.
S3044: and if the storage space is full, cleaning the storage space according to a priority algorithm, and storing the new identity authentication unique identifier in the storage space.
8. The method for implementing the simple and lightweight real-time message pushing system according to claim 5, wherein when pushing the message, after receiving the message, triggering an ACK confirmation event and sending the ACK confirmation event, and after receiving the ACK confirmation event, clearing the periodic retransmission aging queue.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010757700.0A CN111901227A (en) | 2020-07-31 | 2020-07-31 | Simple and lightweight message real-time pushing system and implementation method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010757700.0A CN111901227A (en) | 2020-07-31 | 2020-07-31 | Simple and lightweight message real-time pushing system and implementation method thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111901227A true CN111901227A (en) | 2020-11-06 |
Family
ID=73182840
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010757700.0A Pending CN111901227A (en) | 2020-07-31 | 2020-07-31 | Simple and lightweight message real-time pushing system and implementation method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111901227A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113302881A (en) * | 2020-12-01 | 2021-08-24 | 百果园技术(新加坡)有限公司 | Method, device, chat terminal, server and storage medium for realizing online chat |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103973648A (en) * | 2013-01-31 | 2014-08-06 | 中兴通讯股份有限公司 | Application data push method, device and system |
| US20140365523A1 (en) * | 2013-06-07 | 2014-12-11 | Apple Inc. | Push subscriptions |
| CN106790728A (en) * | 2017-03-30 | 2017-05-31 | 北京深思数盾科技股份有限公司 | information push method and system |
| CN107087033A (en) * | 2017-05-17 | 2017-08-22 | 深圳市小牛在线互联网信息咨询有限公司 | Information push method, device, storage medium and computer equipment |
| CN107689988A (en) * | 2017-08-18 | 2018-02-13 | 广州市百果园信息技术有限公司 | A kind of method, apparatus, electronic equipment and the terminal device of message push |
| CN108989187A (en) * | 2018-07-27 | 2018-12-11 | 深信服科技股份有限公司 | Mail instant alerts system and method |
| CN110661889A (en) * | 2019-11-06 | 2020-01-07 | 杭州涂鸦信息技术有限公司 | Push message synchronization and compensation method and system of iOS (Internet operating System) end |
-
2020
- 2020-07-31 CN CN202010757700.0A patent/CN111901227A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103973648A (en) * | 2013-01-31 | 2014-08-06 | 中兴通讯股份有限公司 | Application data push method, device and system |
| US20140365523A1 (en) * | 2013-06-07 | 2014-12-11 | Apple Inc. | Push subscriptions |
| CN106790728A (en) * | 2017-03-30 | 2017-05-31 | 北京深思数盾科技股份有限公司 | information push method and system |
| CN107087033A (en) * | 2017-05-17 | 2017-08-22 | 深圳市小牛在线互联网信息咨询有限公司 | Information push method, device, storage medium and computer equipment |
| CN107689988A (en) * | 2017-08-18 | 2018-02-13 | 广州市百果园信息技术有限公司 | A kind of method, apparatus, electronic equipment and the terminal device of message push |
| CN108989187A (en) * | 2018-07-27 | 2018-12-11 | 深信服科技股份有限公司 | Mail instant alerts system and method |
| CN110661889A (en) * | 2019-11-06 | 2020-01-07 | 杭州涂鸦信息技术有限公司 | Push message synchronization and compensation method and system of iOS (Internet operating System) end |
Non-Patent Citations (2)
| Title |
|---|
| LIN_HENRY: "IM即时通讯", 《URL:HTTPS://BLOG.CSDN.NET/LIN_HENRY/ARTICLE/DETAILS/106568480》 * |
| 永不止步-FIGHTING: "APNS（Apple Push Notification services）", 《HTTPS://BLOG.CSDN.NET/BAIDU_33440774/ARTICLE/DETAILS/94725314》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113302881A (en) * | 2020-12-01 | 2021-08-24 | 百果园技术(新加坡)有限公司 | Method, device, chat terminal, server and storage medium for realizing online chat |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105491084B (en) | Car networking system and its control method based on OTA agreement | |
| US8769262B2 (en) | VPN connection system and VPN connection method | |
| CN104125141B (en) | A kind of method for pushing of notification message, server and system | |
| CN100421431C (en) | Method for realizing instant message communication | |
| CN109905312B (en) | Message pushing method, device and system | |
| CN105991412B (en) | Information push method and device | |
| KR101646379B1 (en) | Communication device of vehicle | |
| CN101860716A (en) | Wireless video conference terminal reaccess system and method | |
| WO2013078823A1 (en) | Method and device for sending instant message | |
| CN113543281B (en) | Voice communication method and voice communication device | |
| CN103036885B (en) | Sip server overload protective device and method | |
| CN107872588B (en) | Call processing method, related device and system | |
| CN101977358A (en) | Method, device and equipment for transmitting data short messages | |
| JP2006279636A (en) | Consistency guarantee management system for inter-client communication log | |
| CN108366176A (en) | A kind of charging method of terminal applies, apparatus and system | |
| WO2012126286A1 (en) | Aaa server status detection method and system | |
| CN104702647A (en) | Information request method and information request system | |
| CN105165035A (en) | Transmission of multimedia message doubled with transmission of text message | |
| CN111901227A (en) | Simple and lightweight message real-time pushing system and implementation method thereof | |
| CN106330513A (en) | Processing method and apparatus for tr069 protocol information | |
| CN101001213B (en) | Short message transmission system and method | |
| CN114500237B (en) | Communication method and system | |
| CN101778055B (en) | Message processing method and network entity | |
| CN101729436A (en) | Method for acquiring messages and convergence message service system | |
| CN102761845B (en) | Method for carrying out remote control by using short message, and network integration 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201106 |
|
| RJ01 | Rejection of invention patent application after publication |