CN112087475B - Message pushing method and device for cloud platform component application and message server - Google Patents
Message pushing method and device for cloud platform component application and message server Download PDFInfo
- Publication number
- CN112087475B CN112087475B CN201910511664.7A CN201910511664A CN112087475B CN 112087475 B CN112087475 B CN 112087475B CN 201910511664 A CN201910511664 A CN 201910511664A CN 112087475 B CN112087475 B CN 112087475B
- Authority
- CN
- China
- Prior art keywords
- message
- client
- server
- component application
- 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/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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention provides a message pushing method and device for cloud platform component application and a message server, wherein the method is applied to the message server and comprises the following steps: receiving a message sent by a server of at least one component application through a set interface for unifying message standards, and storing the message; and pushing the message to a client corresponding to the user identifier, or pushing the message to at least one client corresponding to the group identifier. The technical scheme provided by the embodiment of the invention can realize unified management and consistent receiving of the messages of the component applications, avoid the condition that the messages of all the component applications are stored in the corresponding positions of the component applications and are difficult to be managed in a unified way, and avoid the problems of difficult unified management and difficult consistent receiving caused by the non-unified message standards due to the independent pushing of the messages.
Description
Technical Field
The embodiment of the invention relates to a message processing technology, in particular to a message pushing method and device for a cloud platform component application and a message server.
Background
With the development of scientific technology, the application range of the cloud platform is wider and wider, and in the face of more and more services, the cloud platform has more and more component applications which need to be configured for the services. The user can log in and access the cloud platform through the client, so that service management, operation and the like are performed.
In the related art, a message of each component application in the cloud platform is sent by a server of the component application. When a user logs in and accesses the cloud platform through the client, messages sent by the server of each component application are stored in the corresponding position of the component application independently, and unified management of the messages of the component applications is difficult to achieve. And the messages of the component applications are respectively and independently pushed to the client side accessing the cloud platform through the server of the component applications, the standards for sending the messages by the server of each component application are different, and particularly when the component applications are more, unified management and consistent receiving of the messages with different standards are difficult to realize.
Disclosure of Invention
The embodiment of the invention provides a message pushing method and device for cloud platform component application and a message server, which can realize unified management and consistent receiving of messages of the component application, avoid the situation that the messages of all the component applications are stored in corresponding positions of the component application and are difficult to be managed in a unified mode, and avoid the problems that the messages are difficult to be managed in a unified mode and difficult to be received in a consistent mode due to the fact that standards are not unified due to the fact that the messages are pushed independently.
In a first aspect, an embodiment of the present invention provides a message pushing method for a cloud platform component application, where the method is applied to a message server, and the method includes:
receiving a message sent by a server of at least one component application through a set interface for unifying message standards, and storing the message;
and pushing the message to a client corresponding to the user identifier, or pushing the message to at least one client corresponding to the group identifier.
In a second aspect, an embodiment of the present invention provides a message pushing apparatus for a cloud platform component application, where the apparatus is configured in a message server, and the apparatus includes:
the receiving/storing module is used for receiving the message sent by the server of at least one component application through a set interface for unifying message standards and storing the message;
and the pushing module is used for pushing the message to the client corresponding to the user identifier or pushing the message to at least one client corresponding to the group identifier.
In a third aspect, an embodiment of the present invention provides a message server, including:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors implement the message pushing method for the cloud platform component application provided by the embodiment of the invention.
In a fourth aspect, a computer-readable storage medium is provided in an embodiment of the present invention, and a computer program is stored on the computer-readable storage medium, where the computer program, when executed by a processor, implements a message pushing method for a cloud platform component application provided in an embodiment of the present invention.
According to the technical scheme provided by the embodiment of the invention, the message server receives the message sent by the server of the component application through the set interface and stores the message, so that the unified storage of the message of the component application can be realized, the condition that the message of each component application is stored in the corresponding position of the component application and is difficult to be managed in a unified manner is avoided, the message server receives the message sent by the server of the component application through the set interface and pushes the message to the client, the message can be pushed according to a unified standard, and the problems that the unified management is difficult and the unified receiving is difficult due to the fact that the standard is not unified due to the independent pushing of the message are avoided.
Drawings
Fig. 1a is a flowchart of a message pushing method for a cloud platform component application according to an embodiment of the present invention;
fig. 1b is a flowchart of a message pushing method for a cloud platform component application according to an embodiment of the present invention;
fig. 2a is a flowchart of a message pushing method for a cloud platform component application according to an embodiment of the present invention;
fig. 2b is a flowchart of a client side push message according to an embodiment of the present invention;
fig. 2c is a flowchart of a message pushing method for a cloud platform component application according to an embodiment of the present invention;
fig. 2d is a flowchart of client feedback provided by an embodiment of the present invention;
fig. 3 is a flowchart of a message pushing method for a cloud platform component application according to an embodiment of the present invention;
fig. 4 is a block diagram of a message pushing apparatus for a cloud platform component application according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a message server according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Fig. 1a is a flowchart of a message pushing method for a cloud platform component application according to an embodiment of the present invention, where the method may be performed by a message pushing apparatus, and the apparatus may be implemented by software and may run on any operating system across platforms. The apparatus may be configured in a message server. The method can be applied to a scene of communication between a server of the component application and a client accessing the cloud platform.
The technical scheme provided by the embodiment of the invention can solve the technical problems in the following scenes: a plurality of component applications are configured in the cloud platform according to the service requirement, wherein messages of the component applications can be sent by the servers of the corresponding component applications. When a user logs in and accesses the cloud platform through a client, messages sent by the server of each component application are stored in the corresponding position of the component application independently, wherein the messages are messages of the component application. Because the messages of each component application are separately stored in different positions, when the messages of the component applications are managed, a user can manage the messages only by accessing the corresponding positions through a client. It is difficult to achieve uniform management of messages of component applications when the messages of each component application are separately deposited. Moreover, messages of the component applications are respectively pushed to the client accessing the cloud platform through the server of the component application, standards for sending the messages by the server of each component application are different, for example, message formats, message categories and the like, and particularly when the component applications are more, it is difficult to achieve unified management and consistent receiving of the messages with different standards.
According to the technical scheme provided by the embodiment of the invention, the message server receives the message sent by the server of the component application through the set interface, stores the message, can realize the unified storage of the message of the component application, can conveniently manage the message of the component application, and avoids the condition that the message of each component application is stored in the corresponding position of the component application to cause difficulty in management; the message server receives the messages sent by the server of the component application through the set interface, can receive the messages with unified standards, pushes the messages to the client, and can push the messages according to the unified standards, so that the problems that the standards are not unified, the management is difficult, and the consistent receiving is difficult due to the fact that the servers of the component application push the messages independently are avoided.
As shown in fig. 1a, the technical solution provided by the embodiment of the present invention includes:
s110: and receiving a message sent by a server of at least one component application through a set interface for unifying message standards, and storing the message.
In the embodiment of the present invention, the component application is an application configured to implement a certain service function in the cloud platform, a message of each component application may be sent by a server of the component application, and a message sent by the server of the component application may be a message sent at a fixed time, or may also be a message sent when a set condition is reached, or may also be a message sent due to other reasons. The message may be a warning type message, or may be an error type message, or may be a notification type message, or may be a promotion type message, or may be a message of another type. The user can know the conditions of the service, the running state and the like of the component application through each message.
In the embodiment of the present invention, the message server may receive, through the setting interface, a message sent by the server of the at least one component application. When the message server receives the message through the set interface, the server of each component application can send the message of the component application according to the rule of the set interface, so that the message of each component application received by the message server is in a uniform format or a uniform standard.
In the embodiment of the present invention, when the message server receives the message sent by the server of each component application, the message server may store the message. Alternatively, the message server may store the message in a database. When the user does not access the cloud platform through the client, the message is not lost, and the service isolation is good.
S120: and pushing the message to a client corresponding to the user identifier, or pushing the message to at least one client corresponding to the group identifier.
In the embodiment of the present invention, the group identifier is a user group identifier, and the group identifier may correspond to one client, or may also correspond to multiple clients. The client can be a browser client, and a user can access the cloud platform through the client.
In the embodiment of the invention, in the process of pushing the message by the message server, if the client is offline, it indicates that the user is not online, the message can be attempted to be pushed, but the message pushing fails. If the client is on line, the user is indicated to be on line, and the message is pushed to be successful. When a client is online, the message server may push a message to the client that is online to cause the client to display the message.
In the embodiment of the invention, the message server stores the message and pushes the message to be unrelated, can guarantee the user is not online, the message will not lose; and when the message server pushes the message to the client, whether the user is online or not is not required to be judged through the user information, the message is directly tried to be pushed to the client corresponding to the user identification or the client corresponding to the group identification, and computing resources can be saved. Fig. 1b may be referred to in detail as a message pushing method according to an embodiment of the present invention.
In the related art, each component application in the cloud platform corresponds to a server of the component application. When a user logs in and accesses the cloud platform through the client, messages sent by the server of each component application are stored in the corresponding position of the component application independently, and unified management of the messages of the component application is difficult to achieve. The message server receives the message sent by the server of the component application and stores the message in a unified way, so that the message of the component application can be managed conveniently, and the condition that the message of each component application is stored in the corresponding position of the component application and is difficult to manage is avoided.
In the related art, messages of each component application are independently pushed to a client accessing a cloud platform through a server of the component application, and the server of each component application sends messages with different standards, such as message formats, message categories, and the like. The message server receives the messages sent by the servers of the component applications through the set interface, can receive the messages with unified standards and push the messages to the client, can push the messages according to the unified standards, and avoids the problems that the messages are difficult to manage and receive consistently due to the fact that the servers of the component applications push the messages independently and the standards are not unified.
In the related art, the server of each component application sends a message to the client accessing the cloud platform, the client logging in the cloud platform can receive the message only through the corresponding interface, and a user is required to trigger the corresponding operation in each component application to check the error message, and when the component applications are more, the error message is difficult to find. The embodiment of the invention uniformly pushes the message to the client side through the message server so as to display the message on the client side, thereby being convenient for finding out error information.
According to the message pushing method provided by the embodiment of the invention, the message server receives the message sent by the server of the component application through the set interface, stores the message, can realize the uniform storage of the message of the component application, avoids the situation that the message of each component application is stored in the corresponding position of the component application and is difficult to manage, receives the message sent by the server of the component application through the set interface and pushes the message to the client, can realize the pushing of the message according to a uniform standard, and avoids the problems that the standard is not uniform due to the independent pushing of the message, so that the management is difficult and the uniform receiving is difficult.
Fig. 2a is a flowchart of a message pushing method for a cloud platform component application according to an embodiment of the present invention, which may be combined with the alternatives in one or more of the foregoing embodiments. In this embodiment, optionally, the technical solution provided in the embodiment of the present invention may further include:
when a connection request of the client is received, authenticating the client;
and when the client authentication is successful, establishing connection with the client.
Optionally, the method may further include: and when the connection with the client is established, inquiring matched unread messages according to the user identification or the group identification corresponding to the client, and feeding the unread messages back to the client.
Optionally, the method may further include: if receiving a read notification of a target message sent by a client, marking the target message as read;
and when the connection with the client is established again, the target message is prohibited from being pushed to the client.
As shown in fig. 2a, the technical solution provided by the embodiment of the present invention includes:
s210: receiving a message sent by a server of at least one component application through a set interface for unifying message standards, storing the message, and defaulting the message to an unread message.
In the embodiment of the invention, the message can be stored in the database, the default message mark is directly unread during storage, and the message reading mark is not updated when the message is failed to be pushed or the feedback of the client is not received. And updating the message as read until the read feedback is received, and not pushing any more.
S220: and pushing the message to a client corresponding to the user identifier, or pushing the message to at least one client corresponding to the group identifier.
S230: and when a connection request of a client is received, authenticating the client.
In the embodiment of the invention, when a user accesses the cloud platform through the client, the client can send a connection request to the message server, wherein the connection request carries the user identifier or the group identifier corresponding to the client. And when the message server receives the connection request of the client, authenticating the client.
The specific authentication process is as follows: and when the message server receives the connection request of the client, sending an authentication notification to the client so that the client sends the authorization key of the client. The message server judges whether the authorization key of the client is the same as the pre-stored authorization key; if the two are the same, the client side is successfully authenticated.
S240: and when the client authentication is successful, establishing connection with the client.
In the embodiment of the invention, when the message server successfully authenticates the client, the connection request sent by the client is processed to establish long connection with the client.
S250: when the connection with the client is established, matched unread messages are inquired according to the user identification or the group identification corresponding to the client, and the unread messages are fed back to the client.
In the embodiment of the invention, when the message server is connected with the client, the unread messages matched with the user identification or the group identification corresponding to the client can be inquired from the database, and the unread messages are fed back to the client, so that the client can display the unread messages, the unread messages are provided for the user, and the user can conveniently know the application condition of each component of the cloud platform. Fig. 2b may be referred to as a flow of pushing a message by a client, and fig. 2c may be referred to as a message pushing method provided in an embodiment of the present invention.
S260: and if a read notification of the target message sent by the client is received, marking the message as read.
In the embodiment of the invention, when a user reads a target message through a client, the operation of clearing the target message can be triggered, and the client sends a read notification of the target message to a message server; when the message server receives a read notification of the target message, the target message is marked as read, thereby updating the database. The client feedback process may refer to fig. 2d.
S270: and when the connection with the client is established again, the target message is prohibited from being pushed to the client.
In the embodiment of the invention, after the target message mark is read, if the message server is connected with the client again, the target message is not sent to the client any more, so that the data flow can be saved, the client can be prevented from repeatedly displaying the read message, and the management of a user is facilitated.
Fig. 3 is a flowchart of a message pushing method for a cloud platform component application according to an embodiment of the present invention, which may be combined with the alternatives in one or more of the foregoing embodiments. In this embodiment, optionally, the technical solution provided in the embodiment of the present invention may further include:
and if a deletion notification of the target message sent by the client corresponding to the group identifier is received, when connection is established with other clients in the group corresponding to the group identifier, the target message is prohibited from being sent to other clients in the group.
As shown in fig. 3, the technical solution provided by the embodiment of the present invention includes:
s310: and receiving a message sent by a server of at least one component application through a set interface for unifying message standards, and storing the message.
S320: and pushing the message to at least one client corresponding to the group identification.
S330: and if receiving a processing notification of a target message sent by the client corresponding to the group identifier, forbidding sending the target message to other clients in the group when establishing connection with other clients in the group corresponding to the group identifier.
In the embodiment of the present invention, when a message server pushes a message to at least one client corresponding to a group identifier, if any user corresponding to the group identifier processes a target message, a client corresponding to the group identifier of a group in which the user is located sends a processing notification of the target message to the message server, and when the message server establishes a connection with other clients in the group corresponding to the group identifier, the sending of the target message to other clients in the group is prohibited, so that the target message is prevented from being provided to other users in the group, and the message is prevented from being repeatedly processed. Alternatively, the processed target message may be a warning type message or an error type message, or the processed target message may be another type of message. For example, if a server of the cloud platform is abnormal, the user a may see an error message of the server abnormality displayed by the client, and restart the server, and then the user B may not see the message through the client, so that restarting the server may be prevented.
Therefore, if the processing notification of the target message sent by the client corresponding to the grouping identifier is received, when the connection is established with other clients in the group corresponding to the grouping identifier, the target message is prohibited from being sent to other clients in the group, so that the repeated processing of the target message can be prevented, and the efficiency is improved.
Fig. 4 is a block diagram of a message pushing apparatus for a cloud platform component application according to an embodiment of the present invention, where the apparatus is configured in a message server, and the apparatus includes: a receiving/storing module 410 and a pushing module 420.
The receiving/storing module 410 is configured to receive, through a set interface for unifying message standards, a message sent by a server of at least one component application, and store the message;
the pushing module 420 is configured to push the message to a client corresponding to the user identifier, or push the message to at least one client corresponding to the group identifier.
Optionally, the apparatus further includes a default module, configured to default the message to an unread message after storing the message.
Optionally, the apparatus further comprises: and the feedback module is used for inquiring the matched unread message according to the user identifier or the group identifier corresponding to the client and feeding back the unread message to the client when the connection with the client is established.
Optionally, the apparatus further comprises: the connection establishing module is used for authenticating the client when receiving a connection request of the client;
and when the client authentication is successful, establishing connection with the client.
Optionally, the apparatus further includes a first prohibiting module, configured to:
if receiving a read notification of a target message sent by a client, marking the target message as read;
and when the connection with the client is established again, the target message is prohibited from being pushed to the client.
Optionally, the apparatus further includes a second disabling module, configured to: and if receiving a processing notification of a target message sent by the client corresponding to the group identifier, forbidding sending the target message to other clients in the group when establishing connection with other clients in the group corresponding to the group identifier.
Alternatively, the processed target message may be any type of message, particularly suitable for warning and error classes.
The device can execute the method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
Fig. 5 is a schematic structural diagram of a message server according to an embodiment of the present invention, and as shown in fig. 5, the message server includes:
one or more processors 510, one processor 510 being illustrated in FIG. 5;
a memory 520;
the message server may further include: an input device 530 and an output device 540.
The processor 510, the memory 520, the input device 530 and the output device 540 in the message server may be connected by a bus or other means, and fig. 5 illustrates the connection by a bus as an example.
The memory 520, which is a non-transitory computer-readable storage medium, may be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to a message pushing method of a cloud platform component application in an embodiment of the present invention (for example, the receiving/storing module 410 and the pushing module 420 shown in fig. 4). The processor 510 executes software programs, instructions and modules stored in the memory 520 to execute various functional applications and data processing of the message server, that is, a message pushing method for a cloud platform component application, which implements the above method embodiments, namely:
receiving a message sent by a server of at least one component application through a set interface for unifying message standards, and storing the message;
and pushing the message to a client corresponding to the user identifier, or pushing the message to at least one client corresponding to the group identifier.
The memory 520 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the message server, and the like. Further, the memory 520 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, memory 520 may optionally include memory located remotely from processor 510, which may be connected to the devices over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 530 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the computer apparatus. The output device 540 may include an interface, and the like.
An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a message pushing method for a cloud platform component application, where the method includes:
receiving a message sent by a server of at least one component application through a set interface for unifying message standards, and storing the message;
and pushing the message to a client corresponding to the user identifier, or pushing the message to at least one client corresponding to the group identifier.
Any combination of one or more computer-readable media may be employed. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. Those skilled in the art will appreciate that the present invention is not limited to the particular embodiments described herein, and that various obvious changes, rearrangements and substitutions will now be apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in some detail by the above embodiments, the invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the invention, and the scope of the invention is determined by the scope of the appended claims.
Claims (9)
1. A message pushing method applied to a cloud platform component is applied to a message server and comprises the following steps:
receiving a message sent by a server of at least one component application through a set interface for unifying message standards, and storing the message;
pushing the message to a client corresponding to the user identifier, or pushing the message to at least one client corresponding to the group identifier;
the user identification or the grouping identification is obtained from a connection request sent by a client to a message server;
the storage message and the push message are not associated with each other, and the messages cannot be lost when the client is not on line; when the message is pushed to the client, the message is directly pushed to the client corresponding to the user identifier or the client corresponding to the group identifier without judging whether the client is on line or not;
and if receiving a processing notification of a target message sent by the client corresponding to the group identifier, forbidding sending the target message to other clients in the group when establishing connection with other clients in the group corresponding to the group identifier.
2. The method of claim 1, after storing the message, further comprising: defaulting the message to an unread message.
3. The method of claim 2, further comprising:
and when the connection with the client is established, inquiring matched unread messages according to the user identification or the group identification corresponding to the client, and feeding the unread messages back to the client.
4. The method of claim 3, further comprising:
when a connection request of the client is received, authenticating the client;
and when the client authentication is successful, establishing connection with the client.
5. The method of claim 3, further comprising:
if receiving a read notification of a target message sent by a client, marking the target message as read;
and when the connection with the client is established again, the target message is prohibited from being pushed to the client.
6. The method of claim 1, wherein the processed target message is a warning type message or an error type message.
7. A message pushing apparatus for a cloud platform component application, the apparatus being configured to a message server, the apparatus comprising:
the receiving/storing module is used for receiving the message sent by the server of at least one component application through a set interface for unifying message standards and storing the message;
the pushing module is used for pushing the message to a client corresponding to the user identifier or pushing the message to at least one client corresponding to the group identifier;
the user identification or the grouping identification is obtained from a connection request sent from a client to a message server;
the stored message and the pushed message are not associated with each other, and the message is not lost when the client is not on line; when the message is pushed to the client, the message is directly pushed to the client corresponding to the user identification or the client corresponding to the group identification without judging whether the client is on line;
a second disabling module to: and if a processing notice of the target message sent by the client corresponding to the group identifier is received, when connection is established with other clients in the group corresponding to the group identifier, the target message is prohibited from being sent to other clients in the group.
8. A message server, comprising:
one or more processors;
a storage device to store one or more programs,
when executed by the one or more processors, cause the one or more processors to implement a message push method for a cloud platform component application as recited in any of claims 1-6.
9. A computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements a message push method for a cloud platform component application according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910511664.7A CN112087475B (en) | 2019-06-13 | 2019-06-13 | Message pushing method and device for cloud platform component application and message server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910511664.7A CN112087475B (en) | 2019-06-13 | 2019-06-13 | Message pushing method and device for cloud platform component application and message server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112087475A CN112087475A (en) | 2020-12-15 |
| CN112087475B true CN112087475B (en) | 2023-01-24 |
Family
ID=73733701
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910511664.7A Active CN112087475B (en) | 2019-06-13 | 2019-06-13 | Message pushing method and device for cloud platform component application and message server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112087475B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115277829B (en) * | 2021-04-29 | 2024-05-24 | 中国移动通信集团终端有限公司 | Message pushing method, device, system, storage medium and electronic equipment |
| CN113569147B (en) * | 2021-07-27 | 2023-09-26 | 北京百度网讯科技有限公司 | Information pushing method, device, electronic equipment and storage medium |
| CN114760296A (en) * | 2022-03-07 | 2022-07-15 | 中银金融科技有限公司 | Information sending method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104717132A (en) * | 2015-02-13 | 2015-06-17 | 腾讯科技（深圳）有限公司 | Information sending method, device and system |
| CN105991692A (en) * | 2015-02-04 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Information pushing method, information display method, and related apparatus and system |
| CN109246220A (en) * | 2018-09-19 | 2019-01-18 | 南方科技大学 | Message pushing system and method |
| CN109428923A (en) * | 2017-08-29 | 2019-03-05 | 努比亚技术有限公司 | Information push method, server, terminal and computer readable storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10666590B2 (en) * | 2013-10-21 | 2020-05-26 | Dropbox, Inc. | Secure sent message identifier |
-
2019
- 2019-06-13 CN CN201910511664.7A patent/CN112087475B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105991692A (en) * | 2015-02-04 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Information pushing method, information display method, and related apparatus and system |
| CN104717132A (en) * | 2015-02-13 | 2015-06-17 | 腾讯科技（深圳）有限公司 | Information sending method, device and system |
| CN109428923A (en) * | 2017-08-29 | 2019-03-05 | 努比亚技术有限公司 | Information push method, server, terminal and computer readable storage medium |
| CN109246220A (en) * | 2018-09-19 | 2019-01-18 | 南方科技大学 | Message pushing system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112087475A (en) | 2020-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112087475B (en) | Message pushing method and device for cloud platform component application and message server | |
| CN109391673B (en) | Method, system and terminal equipment for managing update file | |
| CN113453175B (en) | 5G message processing method and device, computer equipment and storage medium | |
| CN110958119A (en) | Identity verification method and device | |
| CN113271296B (en) | Login authority management method and device | |
| CN113517985B (en) | File data processing method and device, electronic equipment and computer readable medium | |
| CN110839004A (en) | Method and device for access authentication | |
| CN112671844B (en) | Equipment registration method and system | |
| US20220377064A1 (en) | Method and system for managing a web security protocol | |
| KR20220074971A (en) | Blockchain-based data processing method, apparatus and device, and readable storage medium | |
| WO2019095388A1 (en) | Remotely-assisted processing method and device | |
| CN114500630A (en) | Message pushing method, device, system, storage medium and electronic equipment | |
| US10904746B2 (en) | Implementation method, apparatus and system for remote access | |
| CN115840399A (en) | Intelligent building monitoring system based on Internet of things and monitoring method thereof | |
| CN111327680A (en) | Authentication data synchronization method, device, system, computer equipment and storage medium | |
| CN112219416A (en) | Techniques for authenticating data transmitted over a cellular network | |
| CN113873041B (en) | Message transmission method, device, network equipment and computer readable storage medium | |
| CN113709136B (en) | Access request verification method and device | |
| CN106487637A (en) | A kind of processing system of application message, method and application apparatus | |
| EP3293924B1 (en) | Message processing method and device | |
| CN114363408A (en) | Information pushing method and device, computer readable medium and computer equipment | |
| CN114567678A (en) | Resource calling method and device of cloud security service and electronic equipment | |
| CN108200046B (en) | Registration method and device of terminal equipment, terminal equipment and proxy server | |
| CN112272211A (en) | Service request processing method, device and system | |
| WO2019200690A1 (en) | Data protection method, server and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |