CN111049871A - Message pushing method, message management system, server and computer storage medium - Google Patents
Message pushing method, message management system, server and computer storage medium Download PDFInfo
- Publication number
- CN111049871A CN111049871A CN201811199226.3A CN201811199226A CN111049871A CN 111049871 A CN111049871 A CN 111049871A CN 201811199226 A CN201811199226 A CN 201811199226A CN 111049871 A CN111049871 A CN 111049871A
- Authority
- CN
- China
- Prior art keywords
- server
- message
- information
- user information
- preset
- 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.)
- Granted
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
- 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/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
Abstract
The application provides a message pushing method, a message management system, a server and a computer storage medium. The message pushing method comprises the following steps: the first server receives a first message and first user information of a main broadcasting end; the first server acquires preset theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information; the method comprises the steps that a first server obtains label information corresponding to a plurality of preset second user information, and sends a first message, theme group information and the label information to a second server; and the second server processes the first message according to the label information to obtain a second message, and pushes the second message to one or more corresponding audience terminals. By the message pushing method, the pushing message can be processed uniformly according to the second user information, and the processed pushing message is rapidly pushed to the appointed audience.
Description
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a message pushing method, a message management system, a server, and a computer storage medium.
Background
In modern life, the internet is inseparable from people's life. Users watch favorite live celebrities through the Internet, and can also receive push messages related to the live celebrities.
At present, when a message is pushed to a user, a full push mode is mainly adopted, and the full push refers to that after a product on the internet is detected to be updated, a notification message is generated according to the related content of the updated product, and the notification message is sent to all users.
For example, when a main broadcasting end in a live broadcasting system broadcasts, the message management system needs to push broadcast messages to a plurality of audience terminals interested in the main broadcasting end to inform the audience terminals to watch the main broadcasting end's live broadcasting. However, in the current live broadcast system, the message management system cannot identify the country or language of the audience, so that the message management system can only push the broadcast message through one language, and the audience needs to translate the broadcast message when looking up the broadcast message, thereby affecting the experience of the audience; further, the current message management system needs to separately push and play the message to each audience, which is inefficient, even when the anchor finishes playing when receiving the push.
Disclosure of Invention
The application provides a message pushing method, a message management system, a server and a computer storage medium, and mainly solves the technical problem of how to improve the pushing efficiency and pertinence of the message pushing method.
In order to solve the above technical problem, the present application provides a message pushing method, where the message pushing method is applied to a message management system, and the message management system at least includes a first server and a second server; wherein the first server establishes a communication connection with the second server;
the message pushing method comprises the following steps:
the first server receives a first message and first user information of a main broadcasting end;
the first server acquires preset theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information;
the first server acquires label information corresponding to the preset second user information, and sends the first message, the theme group information and the label information to the second server;
and the second server processes the first message according to the label information to obtain a second message, and pushes the second message to a corresponding audience.
In order to solve the above technical problem, the present application further provides a message management system, where the message management system at least includes a first server and a second server; wherein the first server establishes a communication connection with the second server;
the first server is used for receiving a first message and first user information of a main broadcasting terminal;
the first server is further used for acquiring preset theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information;
the first server is further configured to obtain tag information corresponding to the preset second user information, and send the first message, the theme group information, and the tag information to the second server;
and the second server is used for processing the first message according to the label information to obtain a second message and pushing the second message to a corresponding audience.
In order to solve the above technical problem, the present application further provides another message pushing method, where the message pushing method is applied to a first server, and the first server establishes a communication connection with a second server;
the first server receives a first message and first user information of a main broadcasting end;
the first server acquires preset theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information;
the first server acquires label information corresponding to the preset second user information, and sends the first message, the theme group information and the label information to the second server, so that the second server processes the first message according to the label information to obtain a second message, and pushes the second message to a corresponding audience.
In order to solve the technical problem, the application further provides a server, which comprises a communicator and a processor; wherein the communicator is coupled to the processor;
the communicator is used for receiving a first message and first user information of an anchor terminal;
the processor is used for acquiring preset theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information;
the communicator is further configured to acquire tag information corresponding to the preset second user information, and send the first message, the theme group information, and the tag information to the second server, so that the second server processes the first message according to the tag information to obtain a second message, and pushes the second message to a corresponding audience.
To solve the above technical problem, the present application also provides a computer storage medium storing program data that can be executed to implement the above message push method.
Compared with the prior art, the beneficial effects of this application are: the first server receives a first message and first user information of a main broadcasting end; the first server acquires pre-selected theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information; the method comprises the steps that a first server obtains label information corresponding to a plurality of preset second user information, and sends a first message, theme group information and the label information to a second server; and the second server processes the first message according to the label information to obtain a second message, and pushes the second message to the corresponding audience. The first server acquires label information corresponding to a plurality of preset second user information, and can group the second user information so that the second server can process the first message according to the theme group, and the processing efficiency is improved; further, the second server processes the first message according to the tag information, and the processed second message can meet the reference requirement of the audience. By the message pushing method, the pushing message can be processed uniformly according to the second user information, and the processed pushing message is rapidly pushed to the appointed audience.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts. Wherein:
fig. 1 is a schematic flowchart of a first embodiment of a message pushing method according to the present application;
FIG. 2 is a schematic diagram of the message management system of FIG. 1;
FIG. 3 is a schematic diagram of information interaction of the message management system of FIG. 2;
fig. 4 is a flowchart illustrating a second embodiment of the message pushing method of the present application;
fig. 5 is a flowchart illustrating a third embodiment of the message pushing method of the present application;
FIG. 6 is a block diagram of an embodiment of a message management system of the present application;
FIG. 7 is a block diagram of an embodiment of a server of the present application;
FIG. 8 is a schematic structural diagram of an embodiment of a computer storage medium according to the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, 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 application.
The present application provides a message pushing method, which can implement pushing of multiple messages, for example, the message pushing method of the present embodiment can implement and be used for pushing live broadcast messages, specifically please refer to fig. 1 to 3, where fig. 1 is a schematic flow diagram of a first embodiment of the message pushing method of the present application; FIG. 2 is a schematic diagram of the message management system of FIG. 1; fig. 3 is a schematic diagram of information interaction of the message management system in fig. 2.
The message pushing method of the present embodiment is applied to the message management system 20, as shown in fig. 2, the message management system 20 at least includes a first server 23 and a second server 24.
In this embodiment, the anchor 21 and at least one viewer 22 are respectively connected to the message management system 20, and the anchor 21 and the viewer 22 implement the message push method through the message management system 20.
Wherein the spectator 22 establishes communication connections with a first server 23 and a second server 24, respectively, in the message management system 20. In the field of terminals, the spectator terminal 22 may be an intelligent terminal such as a home computer, a smart phone, a tablet computer, etc.; in the field of operating systems, the spectator 22 may be an android client or an IOS client. The viewer side 22 is a consumer of push messages, for example, in a live system, the viewer side 22 watches live content of the anchor side 21, and receives push information such as live information of the anchor side 21.
The anchor 21 is the producer of push messages, and the anchor 21 establishes a communication connection with a first server 23 in the message management system 20. In the field of terminals, the anchor terminal 21 may be an intelligent terminal such as a home computer, a smart phone, a tablet computer, and the like; in the field of operating systems, the anchor 21 may be an android client or an IOS client.
Further, the anchor 21 provides a subscription service, and when the viewer 22 needs to subscribe to the message of the anchor 21, the viewer 22 pays attention to the anchor 21 by selecting the subscription service of the anchor 21. After successful attention, the anchor 21 pushes the generated message to one or more viewers 22 who have paid attention to the anchor 21 through the message management system 20.
The first server 23 may be a message push center, which is responsible for processing push-related content, such as interaction with the second server 24, recording and pushing related messages by multiple viewers 22, sending push at regular time, encapsulating complex technical and business details, etc.; the message push center also opens other services to be directly called, so that other services can be conveniently sent to a plurality of audience terminals 22, for example, the message push center needs to be called to send various types of push when an operation background and a video stream in a live broadcast system are broadcast.
The second server 24 may be a Firebase server, which processes the message sent by the first server 23 and pushes the processed message to a plurality of target audience terminals 22; for example, the Firebase server of the embodiment provides a translation function, and the Firebase server translates the message of the first server 23 according to the country and/or language of the target audience 22, so that the user of the target audience 22 can directly recognize the push message.
As shown in fig. 1, in conjunction with the information interaction diagram of fig. 3, the message pushing method includes the following steps:
s11: the first server receives a first message and first user information of the anchor.
Wherein the anchor 21 generates a first message and sends the first message and the first user information to the first server 23. The first user information is information of the anchor 21, for example, the first user information may be information of an anchor IP, anchor live room information, an anchor ID, and the like.
S12: the first server acquires preset theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information.
The first server 23 stores the first message, and acquires preset theme group information from the anchor 21 according to the first user information, where the theme group information includes a plurality of preset second user information.
Specifically, after receiving the first message and the first user information, the first server 23 sends a request message to the anchor 21, and queries specific information related to the first message. The anchor 21 transmits preset theme group information to the first server 23 according to the request information.
The plurality of second user information in the theme group information correspond to the plurality of spectators 22 having paid attention to the anchor 21, and the message management system 20 pushes the first message to the plurality of spectators 22 corresponding to the second user information. For example, in a live system, the theme group information may include information for a plurality of viewers 22 corresponding to a fan group of the anchor.
Further, the anchor 21 may also send specific information related to the first message. For example, in a live broadcast system, when the anchor 21 broadcasts, the anchor 21 transmits information such as the name of the anchor, the type and title of the game being broadcast, and a scenario for acquiring a multi-language broadcast and push to the first server 23.
S13: the first server acquires label information corresponding to a plurality of preset second user information, and sends the first message, the theme group information and the label information to the second server.
The first server 23 obtains the pre-stored tag information from the database according to the plurality of second user information in the theme group information. The tag information is information representing second user information of a plurality of viewers 22.
Specifically, in the present embodiment, one tag may be set for one theme group. When creating the theme group information for the plurality of second user information, the first server 23 adds tag information of the plurality of viewers 22 who pay attention to the anchor 21 to the theme group information and sets a common tag for the theme group. In other embodiments, a plurality of tags may be set in a theme group, which is not described herein.
After the first server 23 obtains the tag information corresponding to the topic group information, the first server 23 sends the first message, the topic group information, and the tag information to the second server 24. Specifically, the first server 23 calls an interface of the second server 24, and transmits the first message, the topic group information, and the tag information to the second server 24 through the interface.
In the prior art, each time the first server 23 sends the first message, the second user information and the tag information to the second server 24, the interface of the second server 24 needs to be called. The above-described message transmission method is inefficient and requires multiple calls to the interface of the second server 24, consuming a large amount of performance of the second server 24 machine. Further, since the message transmission method described above employs a transmission manner one by one, the time of the first message transmission is delayed. For example, when the push amount is large, the time when the second server 24 receives the first message may be delayed, so that the plurality of viewers 22 cannot timely receive the push information of the anchor 21.
In this embodiment, the message pushing method establishes a theme group, and a plurality of pieces of second user information in the theme group information correspond to one piece of tag information. When the first server 23 sends the first message to the second server 24, the first server 23 only needs to call the interface of the second server 24 once, and the plurality of second user information in the theme group information can be transmitted to the second server 24.
S14: and the second server processes the first message according to the label information to obtain a second message, and pushes the second message to the corresponding audience.
The second server 24 performs unified processing on the first message according to the tag information to obtain a second message. For example, when the second server 24 is a Firebase server, the second server 24 invokes a translation service to translate the first message according to the tag information, so as to obtain a translated second message.
The second server 24 pushes the translated second message to the audience 22 corresponding to the plurality of second user information in the theme group information. Since the tag information corresponds to a plurality of second user information in the theme group information, the spectator terminal 22 may directly recognize the translated second message, so as to prevent the user of the spectator terminal 22 from translating the push message.
Further, the message pushing method of this embodiment adopts a theme group manner, after the first server 23 transmits the first message, the theme group information, and the tag information to the second server 24, the second server 24 can push the corresponding viewer end 22 by using a server cluster with strong performance, and the pushing speed is fast, so that the method is suitable for application scenarios such as launch and push that have high requirements on real-time performance.
By the message pushing method, the first server 23 groups the plurality of second user information by establishing the theme group, and uniformly sends the first message, the theme group information and the tag information to the second server 24, so that the transmission efficiency can be effectively improved, and the performance loss of the second server 24 can be reduced; further, the second server 24 uniformly processes the first message according to the tag information corresponding to the theme group information, and can push different push messages according to different viewer ends 22, thereby improving the pertinence of the message pushing method.
The present application further provides another message pushing method, please refer to fig. 4 specifically, and fig. 4 is a flowchart illustrating a second embodiment of the message pushing method according to the present application.
Similarly, the message pushing method of the present embodiment is applied to the message management system 20 of fig. 2, please refer to fig. 2 specifically, and details are not repeated herein.
On the basis of the first embodiment of the message pushing method, before the step S11 of the message pushing method, the message pushing method of this embodiment further includes the following steps:
s21: the second server receives second user information of the audience.
When the viewer 22 registers or logs in the message management system 20, the viewer 22 needs to send the user account and the user password associated with the viewer 22 to the first server 23. After the first server 23 receives the user account and the user password, the first server 23 performs validity check on the user account and the user password related to the spectator 22, and after the validity check is successful, the first server 23 registers the mapping relationship with the spectator 22.
After the registration is successful, the viewer side 22 inputs and stores the second user information, which includes country information and/or language information of the user.
Further, the spectator terminal 22 sends the second user information to the second server 24 to request to obtain the tag information corresponding to the second user information.
S22: and the second server sends the first label information corresponding to the second user information to the audience.
The second server 24 obtains country information and/or language information in the second user information, and allocates corresponding first tag information according to the country information and/or language information. The second server 24 transmits the first tag information to the corresponding viewer side 22.
For example, in the live broadcast system, the second server 24 assigns a Firebase registration ID to the viewer side 22 according to the country information and/or language information of the viewer side 22, wherein the Firebase registration ID is an ID that marks the country information and/or language information of the device of the viewer side 22. When the Firebase server receives the second message and the Firebase registration ID, the Firebase server can translate or otherwise process the second message according to the Firebase registration ID.
S23: the first server receives second user information and first tag information of the audience.
After the spectator 22 sends the second user information and the first tag information to the first server 23, the first server 23 stores the second user information and the first tag information corresponding to the spectator 22 in the database.
Further, in the message pushing method of the embodiment, the first server 23 sends the second user information of the multiple viewers 22 to the anchor 21, where the multiple viewers 22 have successfully subscribed to the anchor 21. The anchor 21 stores second user information of a plurality of viewers 22.
After the storage is completed, in the subsequent message pushing process, when the second user information of one or more spectators 22 is updated, the message management system 20 needs to update the stored second user information. Specifically, the message pushing method of this embodiment further includes the following steps:
s24: and the first server receives the third user information from the audience terminal and judges whether the third user information is the same as the second user information.
When the audience 22 goes online, the language of the audience 22 changes, the country of the audience 22 changes, and the like, the audience 22 sends the third user information to the first server 23, and calls the binding interface of the first server 23, and the first server 23 needs to check whether the change request is reasonable.
When the verification result is reasonable, the first server 23 receives and judges whether the third user information is the same as the stored second user information of the viewer 22. When the third user information is the same as the second user information, the country information and/or language information of the viewer 22 is not updated, and the first server 23 does not need to modify the stored second user information; when the third user information and the second user information are different, the country information and/or language information of the viewer side 22 is updated, and the process proceeds to step S25.
S25: the first server stores third user information.
When the third user information is different from the stored second user information, the country information and/or language information of the viewer 22 is updated, and the first server 23 deletes the stored second user information and stores the third user information in the database.
Further, when the user information of the spectator terminal 22 is updated, the spectator terminal 22 requests the second server 24 to acquire the first tag information, which also needs to be updated, and the process of acquiring the updated first tag information is the same as the process of acquiring the first tag information, and is not described herein again.
Likewise, the second user information of the spectator end 22 is also stored at the anchor end 21. Specifically, when the second user information in the database of the first server 23 is updated, the first server 23 sends the updated third user information to the anchor 21, and the anchor 21 stores the updated third user information.
In the second user information updating process of the spectator terminal 22 in this embodiment, there are different situations, and the following example is specifically mentioned:
for example, when the first server 23 detects that a plurality of viewers 22 send the same user information, that is, when the same user logs in at the android viewer 22 and the IOS viewer 22 at the same time, the message management system 20 sends the push message to the android viewer 22 and the IOS viewer 22, respectively.
For another example, the first server 23 sequentially detects a plurality of user information sent by the viewer 22, that is, a plurality of users log in the same viewer 22, and the message management system 20 sends the push message to the viewer 22 according to the user information corresponding to the user who logs in the viewer 22 last.
For another example, the first server 23 detects that the country information/language information in the user information sent by the viewer 22 is updated, that is, the viewer 22 switches the country or language, and the message management system 20 translates the push message according to the updated country information/language information and sends the translated push message to the viewer 22.
By the message pushing method, the first server 23 receives the second user information and the first tag information of the multiple spectators 22, and stores the second user information and the first tag information in the database, so that the second server 24 can process the pushed information according to the tag information, thereby improving the pertinence of the message pushing method; further, the first server 23 can detect whether the second user information of one or more spectators 22 is updated in time, and when the second user information of the spectators 22 is updated, the first server 23 can update the user information in the database in time, so as to improve the real-time performance and the practicability of the message pushing method.
The present application further provides another message pushing method, please refer to fig. 5 specifically, and fig. 5 is a schematic flowchart of a third embodiment of the message pushing method of the present application.
Similarly, the message pushing method of the present embodiment is applied to the message management system 20 of fig. 2, please refer to fig. 2 specifically, and details are not repeated herein.
On the basis of the first embodiment of the message pushing method, before the step S12 of the message pushing method, the message pushing method of this embodiment further includes the following steps:
s31: and the first server sets the corresponding second user information as topic group information according to the subscription information.
Wherein the second user information further includes subscription information corresponding to the anchor 21. In the message pushing method of the embodiment, the anchor 21 pushes a message to one or more audience 22 who successfully pay attention to the anchor 21 through the message management system 20. Before that, the viewer side 22 needs to subscribe to the message of the host side 21 by sending the subscription information.
Specifically, the viewer side 22 calls a subscription service and sends subscription information to the first server 23. The first server 23 stores the subscription information and sends the subscription information to the anchor 21. When the anchor 21 generates a message, the anchor 21 acquires the second user information of the target viewer 22 who transmits the message by referring to the stored subscription information, and transmits the second user information and the generated message to the first server 23.
Further, after the first server 23 stores the subscription information, the plurality of second user information is set as topic group information according to the subscription information. For example, when the plurality of viewers 22 pay attention to the anchor 21, the plurality of viewers 22 send the corresponding plurality of subscription information to the first server 23, and the first server 23 establishes a topic group for the plurality of viewers 22 according to the plurality of subscription information.
Since the plurality of subscription information includes the information of the anchor 21, the first server 23 finds the anchor 21 concerned by the plurality of viewers 22 according to the subscription information, and places the second user information of the corresponding plurality of viewers 22 in the theme group information, which may be in the format of "anchor ID".
When the anchor 21 pushes the offline message of the theme group, the first server 23 encapsulates the related information, such as the pushed title, the file, the icon, and the like, into a data packet, and sends the data packet carrying the name of the theme group to the second server 24 to complete the pushing task.
Further, on the basis that the first server 23 establishes the topic group according to the subscription information, the first server 23 may also establish a sub-topic group within the topic group according to the first tag information of the plurality of audience members 22. For example, when the first tag information of the multiple viewers 22 are all the language information, the first server 23 places the second user information of the corresponding multiple viewers 22 in the sub-topic group, and the format may be "anchor ID-language ID".
When the anchor 21 plays, the anchor 21 triggers a live stream callback to notify the first server 23 of the relevant playing information. The first server 23 assembles a multilingual push theme group name, such as "anchor ID-language ID", according to rules of the anchor fan set theme group name, acquires the name of the anchor, the type and title of the played game, and the language of the broadcast push file from other services, arranges these information into data packets and sends the data packets to the first server 23, and the first server 23 calls the push interface of the second server 24 to send the language file to the theme group of the corresponding language, thereby completing the broadcast push.
Further, when the audience 22 logs in, logs out, switches languages or switches countries, the first server 23 interface needs to be called, the second user information and the first tag information of the device are bound or unbound, and meanwhile, the corresponding second user information is added to the theme group or the corresponding theme group is removed. Or, when the viewer 22 pays attention to the anchor 21 or cancels the attention to the anchor 21, the viewer 22 needs to notify the first server 23 to add or remove the corresponding second user information to or from the theme group of the first server 23.
Through the message pushing method, the first server 23 establishes the theme group corresponding to the anchor 21, and places the plurality of second user information in the theme group information according to the subscription information, so as to classify the second user information of the plurality of audience members 22, so that different pushing tasks can be completed according to different theme group information, and the message can be rapidly pushed to the plurality of audience members 22 in the theme group, thereby improving the pertinence and the pushing efficiency of the message pushing method.
The present application further provides a message management system, please refer to fig. 6 specifically, and fig. 6 is a schematic structural diagram of an embodiment of the message management system of the present application.
As shown in fig. 6, the message management system 30 includes at least a first server 33 and a second server 34.
In this embodiment, at least one anchor terminal 31 and at least one viewer terminal 32 are respectively connected to the message management system 30, and the anchor terminal 31 and the viewer terminal 32 implement the message pushing method through the message management system 30.
Specifically, the viewer side 32 establishes communication connections with the first server 33 and the second server 34 of the message management system 30, respectively, and the first server 33 establishes communication connections with the second server 34 and the anchor side 31, respectively.
The first server 33 is configured to receive a first message and first user information of the anchor.
The first server 33 is further configured to obtain preset theme group information from the anchor terminal 31 according to the first user information, where the theme group information includes a plurality of preset second user information.
The first server 33 is further configured to obtain tag information corresponding to a plurality of preset second user information, and send the first message, the theme group information, and the tag information to the second server 34.
The second server 34 is configured to process the first message according to the tag information to obtain a second message, and push the second message to the corresponding viewer 32.
The present application further provides a server, please refer to fig. 7 specifically, and fig. 7 is a schematic structural diagram of an embodiment of the server according to the present application.
The server 700 is the first server 23 disclosed in the above embodiment, and the server 700 establishes a communication connection with a second server.
As shown in fig. 7, the server 700 includes a communicator 71 and a processor 72, wherein the communicator 71 establishes a connection with the processor 72.
The communicator 71 is configured to receive a first message and first user information of the anchor terminal.
The processor 72 is configured to obtain preset theme group information from the anchor according to the first user information, where the theme group information includes a plurality of preset second user information.
The communicator 71 is further configured to obtain tag information corresponding to a plurality of preset second user information, and send the first message, the theme group information, and the tag information to the second server, so that the second server processes the first message according to the tag information to obtain a second message, and pushes the second message to a corresponding viewer.
In the present embodiment, the processor 72 may also be referred to as a CPU (Central Processing Unit). The processor 72 may be an integrated circuit chip having signal processing capabilities. The processor 72 may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor 72 may be any conventional processor or the like.
The present application also provides a computer storage medium, as shown in fig. 8, a computer storage medium 800 stores program data, which can be executed to implement the method described in the message pushing method embodiment of the present application.
The method involved in the message pushing method embodiment of the present application, when implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a device, for example, a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the purpose of illustrating embodiments of the present application and is not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application or are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (10)
1. A message pushing method is applied to a message management system, and the message management system at least comprises a first server and a second server; wherein the first server establishes a communication connection with the second server;
the message pushing method comprises the following steps:
the first server receives a first message and first user information of a main broadcasting end;
the first server acquires preset theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information;
the first server acquires label information corresponding to the preset second user information, and sends the first message, the theme group information and the label information to the second server;
and the second server processes the first message according to the label information to obtain a second message, and pushes the second message to a corresponding audience.
2. The message pushing method according to claim 1, wherein the step of the first server obtaining preset theme group information from the anchor according to the first user information further comprises:
the first server sends request information to the anchor terminal according to the first message;
and the first server receives the theme group information sent by the anchor terminal according to the request information.
3. The message pushing method according to claim 1, wherein before the step of the first server receiving the first message and the first user information of the anchor, the message pushing method further comprises:
the second server receives second user information of the audience terminal;
the second server sends first label information to the audience according to the second user information;
and the first server receives second user information and first label information of the audience.
4. The message pushing method according to claim 3, wherein the second user information further comprises country information and/or language information;
the step of sending the first label information to the audience terminal by the second server according to the second user information further comprises:
and the second server sends the first label information to the audience according to the country information and/or the language information.
5. The message pushing method according to claim 3, wherein after the step of the first server receiving the second user information and the first tag information of the viewer, the message pushing method further comprises:
the first server receives third user information from the audience terminal and judges whether the third user information is the same as the second user information;
the first server stores the third user information when the third user information is different from the second user information.
6. The message pushing method according to claim 3, wherein the second user information further includes subscription information corresponding to the anchor;
before the step of the first server obtaining the preset theme group information according to the first user information, the message pushing method further includes:
and the first server sets the corresponding second user information as the topic group information according to the subscription information.
7. A message management system, characterized in that the message management system comprises at least a first server and a second server; wherein the first server establishes a communication connection with the second server;
the first server is used for receiving a first message and first user information of a main broadcasting terminal;
the first server is further used for acquiring preset theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information;
the first server is further configured to obtain tag information corresponding to the preset second user information, and send the first message, the theme group information, and the tag information to the second server;
and the second server is used for processing the first message according to the label information to obtain a second message and pushing the second message to a corresponding audience.
8. The message pushing method is applied to a first server, and the first server establishes communication connection with a second server;
the first server receives a first message and first user information of a main broadcasting end;
the first server acquires preset theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information;
the first server acquires label information corresponding to the preset second user information, and sends the first message, the theme group information and the label information to the second server, so that the second server processes the first message according to the label information to obtain a second message, and pushes the second message to a corresponding audience.
9. A server, comprising a communicator and a processor, wherein the communicator is coupled to the processor;
the communicator is used for receiving a first message and first user information of an anchor terminal;
the processor is used for acquiring preset theme group information from the anchor terminal according to the first user information, wherein the theme group information comprises a plurality of preset second user information;
the communicator is further configured to acquire tag information corresponding to the preset second user information, and send the first message, the theme group information, and the tag information to the second server, so that the second server processes the first message according to the tag information to obtain a second message, and pushes the second message to a corresponding audience.
10. A computer storage medium storing program data executable to implement the message push method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811199226.3A CN111049871B (en) | 2018-10-15 | 2018-10-15 | Message pushing method, message management system, server and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811199226.3A CN111049871B (en) | 2018-10-15 | 2018-10-15 | Message pushing method, message management system, server and computer storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111049871A true CN111049871A (en) | 2020-04-21 |
| CN111049871B CN111049871B (en) | 2023-04-07 |
Family
ID=70230374
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811199226.3A Active CN111049871B (en) | 2018-10-15 | 2018-10-15 | Message pushing method, message management system, server and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111049871B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113127232A (en) * | 2021-04-19 | 2021-07-16 | 北京京东振世信息技术有限公司 | Message processing method, device, equipment and storage medium |
| CN114710554A (en) * | 2022-03-30 | 2022-07-05 | 北京奇艺世纪科技有限公司 | Message processing method and device, electronic equipment and storage medium |
| CN114710554B (en) * | 2022-03-30 | 2024-04-26 | 北京奇艺世纪科技有限公司 | Message processing method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103973461A (en) * | 2013-02-06 | 2014-08-06 | 阿里巴巴集团控股有限公司 | Notification message pushing method and message server |
| CN104363475A (en) * | 2014-11-14 | 2015-02-18 | 广州华多网络科技有限公司 | Audience grouping association method, device and system |
| CN106412025A (en) * | 2016-09-12 | 2017-02-15 | 福建中金在线信息科技有限公司 | Live broadcast information pushing method, device and system |
| CN107332894A (en) * | 2017-06-23 | 2017-11-07 | 广州市百果园信息技术有限公司 | Live broadcasting method, apparatus and system, server, storage medium |
| CN107749996A (en) * | 2017-09-29 | 2018-03-02 | 上海掌门科技有限公司 | A kind of method and apparatus for being used to push main broadcaster's information to user |
-
2018
- 2018-10-15 CN CN201811199226.3A patent/CN111049871B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103973461A (en) * | 2013-02-06 | 2014-08-06 | 阿里巴巴集团控股有限公司 | Notification message pushing method and message server |
| CN104363475A (en) * | 2014-11-14 | 2015-02-18 | 广州华多网络科技有限公司 | Audience grouping association method, device and system |
| CN106412025A (en) * | 2016-09-12 | 2017-02-15 | 福建中金在线信息科技有限公司 | Live broadcast information pushing method, device and system |
| CN107332894A (en) * | 2017-06-23 | 2017-11-07 | 广州市百果园信息技术有限公司 | Live broadcasting method, apparatus and system, server, storage medium |
| CN107749996A (en) * | 2017-09-29 | 2018-03-02 | 上海掌门科技有限公司 | A kind of method and apparatus for being used to push main broadcaster's information to user |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113127232A (en) * | 2021-04-19 | 2021-07-16 | 北京京东振世信息技术有限公司 | Message processing method, device, equipment and storage medium |
| CN114710554A (en) * | 2022-03-30 | 2022-07-05 | 北京奇艺世纪科技有限公司 | Message processing method and device, electronic equipment and storage medium |
| CN114710554B (en) * | 2022-03-30 | 2024-04-26 | 北京奇艺世纪科技有限公司 | Message processing method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111049871B (en) | 2023-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230396524A1 (en) | Media stream monitoring | |
| CN111836074B (en) | Live wheat-connecting method and device, electronic equipment and storage medium | |
| CN108810657B (en) | Method and system for setting video cover | |
| CN108512814B (en) | Media data processing method, device and system | |
| CN111355971B (en) | Live streaming transmission method and device, CDN server and computer readable medium | |
| CN103179431A (en) | Method for redirecting, transcoding and separating audio/video under VDI (Virtual Desktop Infrastructure) condition | |
| WO2022041731A1 (en) | Message pushing method and apparatus, and electronic device | |
| CN110545327B (en) | Information pushing method and system | |
| CN108200444B (en) | Video live broadcast method, device and system | |
| CN111510756A (en) | Audio and video switching method and device, computer equipment and readable storage medium | |
| WO2017101354A1 (en) | Message pushing system and method | |
| US20160127803A1 (en) | Systems and Methods for Providing an Advertisement Calling Proxy Server | |
| CN110740386A (en) | Live broadcast switching method and device and storage medium | |
| CN103024491A (en) | Video playing method and video playing system of mobile terminal | |
| CN114040232A (en) | Screen projection system, method, electronic device and storage medium | |
| CN111049871B (en) | Message pushing method, message management system, server and computer storage medium | |
| CN110113298B (en) | Data transmission method, device, signaling server and computer readable medium | |
| MX2014012332A (en) | Method for ingesting multiple signals of the same meaning. | |
| US9002974B1 (en) | Script server for efficiently providing multimedia services in a multimedia system | |
| WO2014187397A1 (en) | Multimedia message publishing method and device | |
| WO2016197955A1 (en) | Multimedia stream multicasting method and device | |
| CN111385593A (en) | Cross-platform live content synchronization method and device, storage medium and server | |
| WO2019007027A1 (en) | Video playing method and system, electronic device and readable storage medium | |
| US20150026711A1 (en) | Method and apparatus for video content distribution | |
| CN105847867A (en) | Multimedia live content piloting 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |