CN111835837B - Message pushing method and system with multi-terminal adaptation - Google Patents
Message pushing method and system with multi-terminal adaptation Download PDFInfo
- Publication number
- CN111835837B CN111835837B CN202010596749.2A CN202010596749A CN111835837B CN 111835837 B CN111835837 B CN 111835837B CN 202010596749 A CN202010596749 A CN 202010596749A CN 111835837 B CN111835837 B CN 111835837B
- Authority
- CN
- China
- Prior art keywords
- message
- service
- unified
- messenger
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- 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]
-
- 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/06—Message adaptation to terminal or network requirements
-
- 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/06—Message adaptation to terminal or network requirements
- H04L51/063—Content adaptation, e.g. replacement of unsuitable content
-
- 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/42—Mailbox-related aspects, e.g. synchronisation of mailboxes
-
- 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/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a message pushing method and a system with multi-terminal adaptation, wherein the method comprises the following steps: packaging various messengers in a PAAS service to serve as a unified message push service; the unified message push service receives a message sending request of the business application, pushes the message to the receiving sides of different types of terminals, and stores the message to a database; and receiving a self-defined messenger registration request, and adding the messenger self-defined by the service application into the unified message push service. The invention provides a unified instant message push service facing different types of terminals, an application system can push the notification message to users of different types of terminals in different modes at one time through the message push service, and simultaneously provides a message push extension mechanism, so that an application developer is allowed to add the message notification mode of the application developer without recompiling and deploying a push service program package, and hard coding is avoided. The invention has the advantages of more flexible message pushing, enhanced maintainability, higher compatibility and the like.
Description
Technical Field
The invention belongs to the technical field of message pushing, and particularly relates to a message pushing method and system with multi-terminal adaptation.
Background
The current cloud application generally faces the problem of adapting to the use of different types of terminals, and the modes of receiving application messages on different terminals are various. In the traditional message pushing process, only one sending terminal can be selected, the form is too single for service application, and all terminal users cannot be guaranteed to receive the pushed message at one time. Meanwhile, the traditional application message pushing service belongs to hard coding, developers can place the message pushing service in business application, and only the developers can recompile and deploy a message pushing program package when modification and service extension are needed to be carried out on message pushing in the later period, so that the operation is relatively complex and not flexible enough.
Disclosure of Invention
The present invention provides a message push method and system with multi-port adaptation for solving the above problems in the prior art.
The technical solution for realizing the purpose of the invention is as follows: a message push method with multi-port adaptation, the method comprising the steps of:
encapsulating various messengers in a PAAS service, and recording the PAAS service as a unified message push service; the messenger is a message pushing mode or component;
the unified message push service receives a message sending request of the business application and pushes a message corresponding to the request to a receiving party of different types of terminals.
Further, the encapsulating of multiple messengers in one PAAS service includes the specific process:
constructing a plurality of messenger combinations, each combination including one or more messengers;
constructing a plurality of message channels, wherein each message channel comprises one or more messenger combinations;
and encapsulating the plurality of message channels in PAAS service.
Further, encapsulating multiple messengers in one PAAS service further includes:
constructing a plurality of uniform message templates;
constructing a mapping template between the unified message template and each messenger message template;
establishing mapping relations among all unified message templates, all mapping templates and all messenger message templates;
and encapsulating the unified message template, the mapping template, each messenger message template and the mapping relation in PAAS service.
Further, the pushing of the message corresponding to the request to the receiving sides of the different types of terminals includes the following specific processes:
the unified message pushing service acquires message parameters in the message sending request, wherein the message parameters comprise message content, an appointed message channel, a unified message template and a receiver;
the unified message pushing service starts the appointed message channel and pushes the message content to a receiving party through the appointed message channel; in the process, aiming at the messenger in the appointed message channel, the unified message pushing service converts the unified message template into each messenger message template through the mapping template according to the mapping relation.
Further, the method further comprises:
and storing the message into a message database while pushing the message corresponding to the request to the receivers of different types of terminals.
Further, the method further comprises:
judging the state of the receiver when receiving the message, if the state is the online state, marking the state of the message in the message database as online receiving; if the message is in the offline state, the state of the message in the message database is marked as offline receiving.
Further, the method further comprises:
the unified message pushing service receives a self-defined messenger registration request of the service application and adds a messenger self-defined by the service application to the unified message pushing service through a messenger interface defined by the unified message pushing service.
A message push system with multi-port adaptation, the system comprising:
the unified message pushing service construction module is used for encapsulating various messengers in one PAAS service to form unified message pushing service; the messenger is a message pushing mode or component;
and the message sending module is used for receiving a message sending request of the service application and triggering the unified message pushing service to push the message corresponding to the request to the receiving sides of different types of terminals.
Further, the system further comprises a storage module, configured to store the message in a message database while the unified message push service pushes the message corresponding to the message sending request to the recipients of different types of terminals;
the system also comprises an information marking module which is used for judging the state when the receiver receives the message, and if the state is the online state, marking the state of the message in the message database as online receiving; if the message is in the offline state, the state of the message in the message database is marked as offline receiving.
Further, the system also comprises a messenger registration module used for receiving a self-defined messenger registration request of the business application, and the unified message push service adds the messenger self-defined by the business application to the unified message push service through a messenger interface defined by the unified message push service.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
encapsulating various messengers in a PAAS service, and recording the service as a unified message push service; the messenger is a message pushing mode or component;
the unified message push service receives a message sending request of the business application and pushes a message corresponding to the request to a receiving party of different types of terminals.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
encapsulating various messengers in a PAAS service, and recording the PAAS service as a unified message push service; the messenger is a message pushing mode or component;
the unified message push service receives a message sending request of the business application and pushes a message corresponding to the request to a receiving party of different types of terminals.
Compared with the prior art, the invention has the remarkable advantages that: 1) The message pushing is more flexible. Compared with the traditional message pushing mode, the invention allows the application developer to add own message pushing, can establish a message channel and freely combine different messengers, and provides a flexible mode to allow the user to define the message sending mode by himself. 2) Maintainability is enhanced. In the invention, hard coding is avoided, and the message is pushed and encapsulated into a PAAS service, so that when modification or service expansion is required, an application developer defines new messenger implementation in own application project without recompiling and deploying a push service program package. 3) The compatibility is higher. The invention provides a message template, meets the requirements of an Internet short message platform such as subscription message, ali, tencent, baidu and the like of a WeChat applet, and can send messages to a plurality of different types of terminals in one message pushing process.
The present invention is described in further detail below with reference to the attached drawing figures.
Drawings
Fig. 1 is a schematic diagram of an instant messaging architecture of different types of terminals in an embodiment.
Fig. 2 is a flowchart of a message pushing method for multi-port adaptation in an embodiment.
FIG. 3 is a diagram illustrating a unified message template and messenger message template configuration mapping, according to an embodiment.
Io messenger push message process diagram of an intra-site socket in one embodiment.
Io is based on socket.io in one embodiment.
Fig. 6 is a schematic diagram of a message pushing system with multi-port adaptation in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
In one embodiment, in conjunction with fig. 1 and 2, there is provided a message pushing method for multi-port adaptation, the method comprising the steps of:
step S01, encapsulating various messengers in a PAAS service, and recording the service as a unified message push service; the messenger is a message pushing mode or component;
here, the messenger includes a short message, a mail, a WeChat, and socket.
And step S02, the unified message pushing service receives a message sending request of the service application and pushes the message corresponding to the request to receivers of different types of terminals.
Further, in one embodiment, the step S01 encapsulates multiple messengers into one PAAS service, and the specific process includes:
step S011, constructing a plurality of messenger combinations, wherein each combination comprises one or more messengers;
step S012, constructing a plurality of message channels, wherein each message channel comprises one or a plurality of messenger combinations;
illustratively, for example, the A channel sends messages by using a short message platform messenger and a mail platform messenger, and the B channel sends messages by using a WeChat applet messenger and socket.
Step S013, encapsulating said multiple message channels in PAAS service.
By adopting the scheme of the embodiment, different messengers can be freely combined, a plurality of message channels with different messenger combinations can be created, a plurality of different message combination sending modes can be realized, a flexible mode is provided, a user is allowed to define the sending mode of the message by himself, hard coding in a code is avoided, and the maintainability of the system is enhanced.
Further, in one embodiment, with reference to fig. 3, step S01 encapsulates multiple messengers in one PAAS service, and the specific process further includes:
step S014, constructing a plurality of unified message templates;
step S015, constructing a mapping template between the unified message template and each messenger message template;
step S016, establishing the mapping relation among all unified message templates, all mapping templates and all messenger message templates;
and S017, packaging the unified message template, the mapping template, each messenger message template and the mapping relation in PAAS service.
The scheme of the embodiment is adopted, so that the template functions of some messengers (some messengers can use the message template to limit the message sending content, such as the subscription message of the WeChat applet, the Internet short message platforms of Ali, tencent, baidu and the like) are compatible, a uniform template is provided for the message templates from different messengers, and the compatibility and the universality of the method are improved.
Further, in one embodiment, in step S02, the pushing the message corresponding to the request to the receiving party of the different types of terminals includes:
step S021, the unified message pushing service acquires message parameters in the message sending request, wherein the message parameters comprise message content, a designated message channel, a unified message template and a receiver;
here, the message parameters further include ID, title and data attribute of the message, the ID is a unique number of the message, and the data is a key-value pair list for replacing placeholders in the message template to generate final message content and link path.
Step S022, the unified message push service starts the appointed message channel and pushes the message content to a receiver through the appointed message channel; in this process, with reference to fig. 3, for the messenger in the specified message channel, the unified message push service converts the unified message template into each messenger message template through the mapping template according to the mapping relationship.
Further, in one embodiment, the method further comprises:
and S03, pushing the message corresponding to the request to the receivers of the different types of terminals, and storing the message into a message database.
By adopting the scheme of the embodiment, the historical information is convenient to trace.
Further, in one embodiment, the method further comprises:
step S04, judging the state of the receiver when receiving the message, if the state is the online state, marking the state of the message in the message database as online receiving; if the message is in the offline state, the state of the message in the message database is marked as offline receiving.
By adopting the scheme of the embodiment, the message state can be checked in real time.
Here, the steps S02, S03, and S04 are not limited to the above sequential execution, and may be executed in synchronization.
Further, in one embodiment, the method further comprises:
and step S05, the unified message pushing service receives the self-defined messenger registration request of the service application and adds the messenger self-defined by the service application to the unified message pushing service through a messenger interface defined by the unified message pushing service.
By adopting the scheme of the embodiment, an extension mechanism is provided, so that an application developer is allowed to define new messenger implementation in own application project without recompiling and deploying a platform unified service push service program package. An application developer can define messenger implementation service classes in its own application and develop its REST API interface. Extended service messengers may also be added to the message channel for use.
As a specific example, in one embodiment, the multi-port adapted message pushing of the present invention is further described:
with reference to fig. 4, the push service is built based on a socket.io open source framework (MIT open source protocol) of NodeJs, and is responsible for maintaining long connection with the client, subscribing to message events of the message queue, and forwarding messages of the message queue forward.
The message push implementation mode in the system of the B/S framework is mainly kept in long connection with a server side in a browser WebSocket mode or a LongPoll mode and the like. In an elastic computing architecture of a platform, a browser of a user is kept connected with a Pod of an API gateway, a plurality of API gateways Pod exist in a cluster, and a back-end application service cannot know which Pod the browser of the user is connected to and directly send a message, so that a message queue middleware is needed. All API gateway Pod subscribe the message on the message queue, the back-end application service sends the message to the message queue, triggers the subscription event, informs the API gateway Pod, the API gateway Pod inquires whether the long connection with the target user exists, and if so, the message is pushed to the front end.
The in-station socket and IO push service supports multi-application multi-session multi-channel message push, a Namespace (Namespace) is allocated to each application inside the socket and IO service, and different sessions from the same user are classified into the same Room (Room) under the Namespace. Messages are sent in units of namespace + room, pushed to the terminal browser connected for each session in the room, as shown in fig. 5.
In one embodiment, in conjunction with fig. 6, there is provided a multi-port adapted message pushing system, the system comprising:
the unified message pushing service construction module is used for encapsulating various messengers in one PAAS service to form unified message pushing service; the messenger is a message pushing mode or component;
and the message sending module is used for receiving a message sending request of the service application and triggering the unified message pushing service to push the message corresponding to the request to the receiving sides of different types of terminals.
Further, in one embodiment, the system further includes a storage module, configured to store the message in a message database while the unified message push service pushes the message corresponding to the message sending request to the recipients of different types of terminals.
Further, in one embodiment, the system further includes an information marking module, configured to determine a state when the receiving party receives the message, and mark the state of the message in the message database as online reception if the state is online; if the message is in the offline state, the state of the message in the message database is marked as offline receiving.
Further, in one embodiment, the system further includes a messenger registration module, configured to receive a customized messenger registration request of the service application, where the unified message push service adds a messenger customized to the service application to the unified message push service through a messenger interface defined by the unified message push service.
For specific limitations of the multi-end adapted message pushing system, reference may be made to the above limitations on the multi-end adapted message pushing method, which is not described in detail herein. All or part of the modules in the message pushing system with multi-terminal adaptation can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
encapsulating various messengers in a PAAS service, and recording the PAAS service as a unified message push service; the messenger is a message pushing mode or component;
the unified message push service receives a message sending request of the business application and pushes a message corresponding to the request to a receiving party of different types of terminals.
Further, in one embodiment, the processor, when executing the computer program, further performs the following steps:
and storing the message into a message database while pushing the message corresponding to the request to the receivers of the different types of terminals.
Further, in one embodiment, the processor when executing the computer program further performs the steps of:
judging the state of the receiver when receiving the message, if the state is the online state, marking the state of the message in the message database as online receiving; if the message is in the offline state, the state of the message in the message database is marked as offline receiving.
Further, in one embodiment, the processor, when executing the computer program, further performs the following steps:
the unified message pushing service receives a self-defined messenger registration request of the service application and adds a messenger self-defined by the service application to the unified message pushing service through a messenger interface defined by the unified message pushing service.
For specific definition description of each step, reference may be made to the above definition of the message pushing method for multi-port adaptation, which is not described herein again.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
encapsulating various messengers in a PAAS service, and recording the service as a unified message push service; the messenger is a message pushing mode or component;
the unified message push service receives a message sending request of the business application and pushes a message corresponding to the request to a receiving party of different types of terminals.
Further, in one embodiment, the computer program when executed by the processor further performs the steps of:
and storing the message into a message database while pushing the message corresponding to the request to the receivers of different types of terminals.
Further, in one embodiment, the computer program when executed by the processor further performs the steps of:
judging the state of the receiver when receiving the message, if the state is the online state, marking the state of the message in the message database as online receiving; if the message is in the offline state, the state of the message in the message database is marked as offline receiving.
Further, in one of the embodiments, the computer program when executed by the processor further performs the steps of:
the unified message push service receives a self-defined messenger registration request of the business application and adds a messenger self-defined by the business application to the unified message push service through a messenger interface defined by the unified message push service.
For the specific definition description of each step, reference may be made to the above definition of the message pushing method for multi-port adaptation, which is not described in detail herein.
The invention encapsulates various message pushing modes into one PAAS service according to the requirement and the current situation of application message pushing, and provides a unified instant message pushing service facing different types of terminals. The application system can push the notification message to users of different types of terminals in different modes at one time through the message push service, and meanwhile, the invention provides a message push extension mechanism to allow an application developer to add the message notification mode of the application developer without recompiling and deploying a push service program package, thereby avoiding hard coding. In conclusion, the invention has the advantages of more flexible message pushing, enhanced maintainability, higher compatibility and the like.
The foregoing illustrates and describes the principles, general features, and advantages of the present invention. It will be understood by those skilled in the art that the present invention is not limited to the embodiments described above, which are described in the specification and illustrated only to illustrate the principle of the present invention, but that various changes and modifications may be made therein without departing from the spirit and scope of the present invention, which fall within the scope of the invention as claimed. The scope of the invention is defined by the appended claims and equivalents thereof.
Claims (8)
1. A message push method with multi-port adaptation, the method comprising the steps of:
encapsulating various messengers in a PAAS service, and recording the PAAS service as a unified message push service; the messenger is a message pushing mode or component;
the unified message push service receives a message sending request of a business application and pushes a message corresponding to the request to a receiving party of different types of terminals;
the method for encapsulating multiple messengers in one PAAS service comprises the following specific processes:
constructing a plurality of messenger combinations, each combination including one or more messengers;
constructing a plurality of message channels, wherein each message channel comprises one or more messenger combinations;
encapsulating the plurality of message channels in PAAS service;
constructing a plurality of uniform message templates;
constructing a mapping template between the unified message template and each messenger message template;
establishing mapping relations among all the uniform message templates, all the mapping templates and all the messenger message templates;
and encapsulating the unified message template, the mapping template, each messenger message template and the mapping relation in PAAS service.
2. The message pushing method of claim 1, wherein the message corresponding to the request is pushed to the receiving sides of different types of terminals, and the specific process includes:
the unified message pushing service acquires message parameters in the message sending request, wherein the message parameters comprise message content, an appointed message channel, a unified message template and a receiver;
the unified message pushing service starts the appointed message channel and pushes the message content to a receiving party through the appointed message channel; in the process, aiming at the messenger in the appointed message channel, the unified message pushing service converts the unified message template into each messenger message template through the mapping template according to the mapping relation.
3. The multi-ended adapted message pushing method according to claim 2, characterized in that said method further comprises:
and storing the message into a message database while pushing the message corresponding to the request to the receivers of the different types of terminals.
4. The multi-ended adapted message pushing method according to claim 3, characterized in that said method further comprises:
judging the state of the receiver when receiving the message, if the state is on-line, marking the state of the message in the message database as on-line receiving; if the message is in the offline state, the state of the message in the message database is marked as offline receiving.
5. The multi-port adapted message pushing method according to claim 1, wherein said method further comprises:
the unified message push service receives a self-defined messenger registration request of the business application and adds a messenger self-defined by the business application to the unified message push service through a messenger interface defined by the unified message push service.
6. A push system based on the multi-port adapted message push method according to any of claims 1 to 5, characterized in that the system comprises:
the unified message pushing service construction module is used for encapsulating various messengers in one PAAS service to form unified message pushing service; the messenger is a message pushing mode or component;
and the message sending module is used for receiving a message sending request of the service application and triggering the unified message pushing service to push the message corresponding to the request to the receiving sides of different types of terminals.
7. The multi-terminal adapted message pushing system according to claim 6, further comprising a storage module, configured to store the message in a message database while the unified message pushing service pushes the message corresponding to the message sending request to the recipients of different types of terminals;
the system also comprises an information marking module which is used for judging the state when the receiver receives the message, and if the state is the online state, marking the state of the message in the message database as online receiving; if the message is in the offline state, the state of the message in the message database is marked as offline receiving.
8. The multi-terminal adapted message pushing system according to claim 7, further comprising a messenger registration module for receiving a customized messenger registration request of the service application, wherein the unified message pushing service adds a messenger customized to the service application to the unified message pushing service through a messenger interface defined by the unified message pushing service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010596749.2A CN111835837B (en) | 2020-06-28 | 2020-06-28 | Message pushing method and system with multi-terminal adaptation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010596749.2A CN111835837B (en) | 2020-06-28 | 2020-06-28 | Message pushing method and system with multi-terminal adaptation |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111835837A CN111835837A (en) | 2020-10-27 |
| CN111835837B true CN111835837B (en) | 2023-04-07 |
Family
ID=72898254
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010596749.2A Active CN111835837B (en) | 2020-06-28 | 2020-06-28 | Message pushing method and system with multi-terminal adaptation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111835837B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112367433A (en) * | 2020-11-09 | 2021-02-12 | 苏州云网通信息科技有限公司 | Method for integrating multiple PaaS call platforms |
| CN112420217B (en) * | 2020-11-30 | 2023-07-28 | 腾讯科技（深圳）有限公司 | Message pushing method, device, equipment and storage medium |
| CN112764795B (en) * | 2021-01-21 | 2022-02-18 | 奇秦科技(北京)股份有限公司 | Service-oriented cross-platform and cross-terminal information publishing system and method |
| CN113852667A (en) * | 2021-08-27 | 2021-12-28 | 青岛海尔科技有限公司 | Message pushing method and device, storage medium and electronic device |
| CN114363409B (en) * | 2022-01-05 | 2023-09-22 | 厦门市易联众易惠科技有限公司 | A multi-channel configurable unified message management method, platform and system |
| CN114979255A (en) * | 2022-05-16 | 2022-08-30 | 浪潮云信息技术股份公司 | A unified messaging platform system |
| CN114979256B (en) * | 2022-05-19 | 2024-06-18 | 北京京东乾石科技有限公司 | Message pushing method and device, electronic equipment and computer readable medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9578085B2 (en) * | 2011-02-28 | 2017-02-21 | Unwired Nation | Mobile application system |
| CN105227595B (en) * | 2014-06-09 | 2019-09-03 | 阿里巴巴集团控股有限公司 | A kind of message method and equipment |
| US10951723B2 (en) * | 2017-10-03 | 2021-03-16 | International Business Machines Corporation | Theme-based push notifications |
| CN110601952B (en) * | 2018-06-12 | 2022-12-27 | 北京京东尚科信息技术有限公司 | Multi-channel message notification sending method and device |
-
2020
- 2020-06-28 CN CN202010596749.2A patent/CN111835837B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN111835837A (en) | 2020-10-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111835837B (en) | Message pushing method and system with multi-terminal adaptation | |
| US8539097B2 (en) | Intelligent message processing | |
| US9479400B2 (en) | Servlet API and method for XMPP protocol | |
| US10404641B2 (en) | Internet e-mail bridge | |
| CN113242272B (en) | MQTT service cluster-based session processing method and system | |
| CN102395115A (en) | Method and system for managing message threads in converged IP messaging service | |
| CN112527523B (en) | Distributed message delivery method and system for high performance computing multi-cloud | |
| CN111901230B (en) | Internet of things gateway and system supporting equipment access verification and equipment access verification method | |
| CN114500633B (en) | Data forwarding method, related device, program product and data transmission system | |
| WO2022120806A1 (en) | Multi-cloud distributed messaging method and system for high performance computing | |
| CN105260842B (en) | Communication method and system between heterogeneous ERP systems | |
| CN106487644A (en) | A kind of communication means and system | |
| CN110740161A (en) | system and method for adapting converged communication | |
| CN111431790B (en) | Instant messaging method, device, system and storage medium | |
| US20230326457A1 (en) | Messaging System For A Virtual Assistant | |
| CN115334155B (en) | Message queue proxy method and device | |
| CN106126349A (en) | A kind of remote invocation method, message-oriented middleware cluster and system | |
| CN109547333A (en) | Instant communicating method and device | |
| CN101238435A (en) | peer-to-peer communication system | |
| CN108040000A (en) | A kind of information transferring method and equipment | |
| CN115225482A (en) | Method and device for configuring Pod network based on Kubernetes | |
| CN114938296A (en) | Global exit method and system for multi-project single sign-on | |
| CN117135156B (en) | Edge cluster nano-tube method, system, computer readable storage medium and electronic equipment based on publish/subscribe message protocol | |
| CN110008036A (en) | Data transmission method and device | |
| CN114513509B (en) | MQTT-based wi-sun network data acquisition method and 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 | ||
| CB02 | Change of applicant information |
Address after: 222001 No.18 Shenghu Road, Lianyungang City, Jiangsu Province Applicant after: The 716th Research Institute of China Shipbuilding Corp. Applicant after: CSIC Information Technology Co.,Ltd. Address before: 222001 No.18 Shenghu Road, Lianyungang City, Jiangsu Province Applicant before: 716TH RESEARCH INSTITUTE OF CHINA SHIPBUILDING INDUSTRY Corp. Applicant before: CSIC Information Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 222001 No.18 Shenghu Road, Lianyungang City, Jiangsu Province Patentee after: The 716th Research Institute of China Shipbuilding Corp. Patentee after: China Shipbuilding Digital Information Technology Co.,Ltd. Address before: 222001 No.18 Shenghu Road, Lianyungang City, Jiangsu Province Patentee before: The 716th Research Institute of China Shipbuilding Corp. Patentee before: CSIC Information Technology Co.,Ltd. |