CN113301379A - Live broadcast list updating method, device, system and storage medium - Google Patents
Live broadcast list updating method, device, system and storage medium Download PDFInfo
- Publication number
- CN113301379A CN113301379A CN202110579240.1A CN202110579240A CN113301379A CN 113301379 A CN113301379 A CN 113301379A CN 202110579240 A CN202110579240 A CN 202110579240A CN 113301379 A CN113301379 A CN 113301379A
- Authority
- CN
- China
- Prior art keywords
- server
- list
- live
- changed
- version information
- 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
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/21—Server components or server architectures
- H04N21/218—Source of audio or video content, e.g. local disk arrays
- H04N21/2187—Live feed
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/231—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/242—Synchronization processes, e.g. processing of PCR [Program Clock References]
Abstract
The embodiment of the application provides a live list updating method, wherein the live list comprises live information corresponding to each anchor currently being played, and the method comprises the following steps: when the first server determines that the live broadcast list is changed, the first server acquires the changed live broadcast list from the database server, updates the changed live broadcast list locally and sends a notice to each second server in the same local area network; and after receiving the notification, the second server acquires the changed live list from the first server and updates the changed live list locally. The method provided by the embodiment of the application can solve the technical problem that the live broadcast list occupies too much bandwidth of the database server when being updated.
Description
Technical Field
The embodiment of the application relates to the technical field of live broadcast, in particular to a live broadcast list updating method, device, system and storage medium.
Background
In the related art, the latest live list is stored in the database server, and in order to ensure that the provided live list is latest, the server that needs to provide the live list will access the database server regularly to obtain the latest live list from the database server. However, a large number of servers need to update the live list, and when a large number of servers access the database server at the same time, bandwidth of the database server is insufficient, so that a problem of delay in updating the live list occurs.
Disclosure of Invention
In order to solve the problems in the related art, embodiments of the present application provide a live list updating method, apparatus, system, and storage medium, which can solve the technical problem that a database server occupies too much bandwidth when a live list is updated.
According to a first aspect of an embodiment of the present application, a live list updating method is provided, where the live list includes live information corresponding to each anchor currently being played, and the method includes:
when the first server determines that the live broadcast list is changed, the first server acquires the changed live broadcast list from the database server, updates the changed live broadcast list locally and sends a notice to each second server in the same local area network;
and after receiving the notification, the second server acquires the changed live list from the first server and updates the changed live list locally.
Optionally, the local area network includes a plurality of the first servers, and each of the first servers sends a notification to each of the second servers after completing the update of the live list.
Optionally, the notification sent by the first server carries first version information of a currently stored live broadcast list of the first server;
the second server obtains the changed live list from the first server, and the method includes:
and the second server compares second version information of a live list currently stored by the second server with the first version information, and if the first version information is newer than the second version information, the changed live list is acquired from the first server.
Optionally, the method further includes:
and after the second server finishes updating the live list, updating the second version information into the first version information.
Optionally, the determining, by the first server, that the live list is changed includes:
and the first server determines that the live list is changed according to the received list change message, wherein the list change message is sent by the third server when the live list stored in the database server is changed.
Optionally, the list change message carries new version information of the live broadcast list, where the new version information is generated by the third server when the live broadcast list stored in the database server is changed;
the method further comprises the following steps:
and after the first server finishes updating the live list, updating the first version information of the live list currently stored by the first server into the new version information.
Optionally, the obtaining, by the first server, the changed live list from the database server includes:
and the first server compares the first version information with the new version information, and if the new version information is newer than the first version information, a changed live broadcast list is obtained from a database server.
Optionally, the first server sends a notification to each of the second servers in a timed broadcast manner.
According to a second aspect of embodiments of the present application, there is provided a live list updating system, including:
the database server is used for storing a live broadcast list, and the live broadcast list comprises live broadcast information corresponding to each anchor broadcast currently being played;
the first server is used for acquiring the changed live broadcast list from the database server when the live broadcast list is determined to be changed, updating the changed live broadcast list locally and sending a notice to each second server in the same local area network;
and each second server is used for acquiring the changed live list from the first server after receiving the notification, and updating the changed live list locally.
According to a third aspect of the embodiments of the present application, there is provided a live list updating method applied to a first server, the method including:
when the live list is determined to be changed, obtaining a changed live list from a database server, and updating the changed live list locally;
sending a notification to each second server in the same local area network;
and after receiving a request of the second server for acquiring the live list, transmitting the changed live list to the second server initiating the request, so that the second server can update the changed live list locally.
According to a fourth aspect of the embodiments of the present application, there is provided a live list updating apparatus, where the live list includes live information corresponding to respective anchor broadcasts currently being played, the apparatus including:
the acquisition module is used for acquiring a changed live broadcast list from a database server and updating the changed live broadcast list locally when the live broadcast list is determined to be changed;
the notification module is used for sending a notification to each second server in the same local area network;
and the transmission module is used for transmitting the changed live broadcast list to the second server initiating the request after receiving the request of the second server for acquiring the live broadcast list, so that the second server can update the changed live broadcast list locally.
According to a fifth aspect of embodiments of the present application, there is provided a computer-readable storage medium storing a computer program which, when executed by a processor, implements any one of the methods provided by the embodiments of the present application.
The technical scheme provided by the application can comprise the following beneficial effects:
according to the live list updating method provided by the embodiment of the application, when the live list is changed, the first server accesses the database server to obtain the changed live list, other second servers do not need to access the database server, and the changed live list can be obtained from the first server.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments consistent with the embodiments of the application and, together with the description, serve to explain the principles of the embodiments of the application.
Fig. 1 is a first scene diagram of live list update provided in an embodiment of the present application.
Fig. 2 is a first flowchart of a live list updating method provided in an embodiment of the present application.
Fig. 3 is a second scene diagram of live list update provided in the embodiment of the present application.
Fig. 4 is a schematic structural diagram of a live list updating system according to an embodiment of the present application.
Fig. 5 is a second flowchart of a live list updating method provided in an embodiment of the present application.
Fig. 6 is a schematic structural diagram of a live list updating apparatus according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the examples of the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the embodiments of the application, as detailed in the appended claims.
The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the present application. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present application to describe various information, the information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the embodiments of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The live list includes a plurality of pieces of live information, and each piece of live information may correspond to one anchor currently being played. The live information may include a variety of content, and in one example, the live information may include a nickname of the anchor, a name of the live room, a number of viewers in the live room, an address of the video stream, and so on.
In the live broadcast application, there are many situations that the server needs to provide the live broadcast list, for example, when the client needs to display the live broadcast list, the client will obtain the live broadcast list from the server, and therefore, the server needs to store the latest live broadcast list to provide the live broadcast list to the client. Since the live list is changed frequently, the server needs to update its stored live list frequently to ensure that the provided live list can be the latest live list.
In the related art, the latest live list is stored in the database server, and in order to ensure that the provided live list is latest, the server that needs to provide the live list will access the database server regularly to obtain the latest live list from the database server. However, a large number of servers need to update the live list, and when a large number of servers access the database server at the same time, bandwidth of the database server is insufficient, so that a problem of delay in updating the live list occurs. Referring to fig. 1, fig. 1 is a scene diagram of live list update provided in an embodiment of the present application.
In one embodiment, multiple database servers may be deployed, and the multiple database servers may form a master-slave node therebetween, thereby increasing the bandwidth of the database servers. However, this approach greatly increases the cost of the database server, and data synchronization between the master node and the slave node also has a delay, which affects the consistency of the externally provided live list.
An embodiment of the present application provides a live list updating method, which may be referred to fig. 2, where fig. 2 is a first flowchart of the live list updating method provided in the embodiment of the present application, and the method includes:
s202, when the live broadcast list is determined to be changed, the first server obtains the changed live broadcast list from the database server, updates the changed live broadcast list locally, and sends a notice to each second server in the same local area network.
And S204, after receiving the notification, the second server acquires the changed live broadcast list from the first server and updates the changed live broadcast list locally.
A server is a kind of computer that can be used to store data and can also implement various functions by executing computer programs. The first server may be any server with logic operation capability, and may obtain the changed live broadcast list from the database server when it is determined that the live broadcast list is changed.
The database server may be a server installed with database software, and may be configured to store data. In one embodiment, the database of the database server may include a cache database, such as a Redis database. Because the cache database stores data based on the memory, the data reading and writing speed is high, and the reading and writing efficiency of the live broadcast list can be improved.
Other servers besides the database server can access the database server and perform operations such as adding, deleting, searching and modifying on the data stored in the database server. In one embodiment, the third server may make changes to the live listings stored in the database server by accessing the database server. There are many situations where the live list needs to be changed, such as a new anchor being played, an anchor ending a live, an anchor changing a live room name, etc. Here, the third server may be any server that needs to change the live list.
For convenience of understanding, it is possible for example that the third server may be an opening server, i.e. the third server is responsible for providing the opening service for the anchor. When a certain anchor is broadcast through an anchor client, the anchor client can send the live broadcast information of the anchor to a broadcast server, the broadcast server can access a database server while providing broadcast service for the anchor, and a piece of live broadcast information corresponding to the anchor is added to a live broadcast list stored by the database server, so that the live broadcast list is changed.
After the first server obtains the changed live list from the database server, the changed live list may be updated to the local, for example, may be stored in a local process cache. The first server may then send notifications to the second servers of the same lan.
The first server may establish a local area network with a plurality of second servers, for example, the first server may be deployed in a computer room with a plurality of second servers, and the servers in the same computer room may communicate via the local area network.
The second server may be any server that needs to provide the live list to the outside, and since the live list needs to be provided to the outside, the second server needs to store the latest live list locally. After receiving the notification sent by the first server, the second server may obtain the changed live list from the first server, so that the locally stored live list may be updated to the latest changed live list.
According to the live list updating method provided by the embodiment of the application, when the live list is changed, the first server accesses the database server to obtain the changed live list, other second servers do not need to access the database server, and the changed live list can be obtained from the first server.
In one embodiment, a plurality of the first servers may be deployed, that is, a plurality of servers with logical operation capability may be selected as the first servers in the same local area network. Each first server can acquire the changed live list from the database server when the live list is changed, and can send a notification to each second server, so that the second servers can acquire the changed live list according to the notification. By arranging the plurality of first servers, the robustness of live list updating can be improved, and when one first server fails, live list updating can still be completed through other first servers.
When a plurality of first servers are provided, it may be that, due to network congestion or the like, each first server cannot synchronously acquire the live broadcast list from the database server, so that different live broadcast lists stored by different first servers may be different. However, when the live lists stored by different first servers are different, an accident that the second server updates the old version of the live list to the local may occur.
For example, two first servers a and B may be deployed, where the live list stored by the first server a is the latest version V3The first server B does not update the live list in time due to some abnormal events, and the locally stored live list is the old version V2Is received. Since both the first server a and the first server B will send the notification to each of the second servers, for a certain second server, it may receive the notification from the first server a first and obtain V from the first server a3If the version of the live list is updated locally but then the second server receives the notification from the first server B, the V obtained from the first server B may be mistakenly obtained2The live list of versions is updated locally.
In order to avoid the foregoing problem, in an embodiment, when the first server sends the notification, the first server may additionally send first version information of a live broadcast list currently stored by the first server, and the second server may also obtain the first version information after receiving the notification, compare the first version information with second version information of a live broadcast list currently stored by the second server itself, and determine whether to obtain the live broadcast list from the first server that sent the notification according to a comparison result. If the comparison result is that the first version information is newer than the second version information of the first version information, the live broadcast list can be obtained from the first server, the obtained live broadcast list is updated to the local, and if the comparison result is that the first version information is not newer than the second version information of the first version information (including two cases that the two version information are equal and the first version information is older than the second version information), the live broadcast list does not need to be obtained from the first server.
It will be appreciated that there are a number of ways in which old and new versions of information may be compared. For example, in one example, it may be predetermined that the version information of the new version is numerically larger than the version information of the old version, for example, the version information of a live list is V4Version information of a live list is V3Then the corresponding numerical value V can be determined to be larger4Is the latest version. Of course, it is also possible to agree that the version information of the new version is numerically smaller than the version information of the old version, and in the foregoing example, V is3Live list of version is new to V4A live list of versions. Different ways for judging whether the version is new or old can be set according to different appointed ways, which is not limited in the present application.
After the second server completes updating of the live list every time, namely after the second server acquires the changed live list from the first server and updates the changed live list to the local, the second version information of the live list currently stored by the second server can be updated to the first version information corresponding to the changed live list.
There are a number of ways for the first server to determine when a change to the live list has occurred. In one embodiment, the first server may determine that the live list has been changed according to the received list change message. Here, the list change message may be issued by the third server when changing the live list stored in the database server. The third server has already been described in the foregoing, and is not described in detail here. When the third server accesses the database server and changes the live list in the database server, a list change message can be generated and sent to the message queue. The first server may receive a list change message from the message queue and may determine that the live list in the database server has changed.
The first server may also have other ways to determine whether the live list has changed. For example, the first server may access the database server at regular time, query the version information of the live broadcast list currently stored by the database server, and compare the version information with the version information of the live broadcast list currently stored by the first server, so as to determine whether the live broadcast list is changed.
In an embodiment, when the live list stored in the database server is changed, the third server may further generate new version information of the live list, and the new version information may be carried by the list change message. For example, the version of the current live listThe information is V5When the third server changes the live list, the third server can generate new version information V of the live list6And sends the new version information V6And sending the data to the first server. After receiving the list change information, the first server acquires the changed live broadcast list from the database server and updates the live broadcast list to the local, and the first version information of the live broadcast list currently stored by the first server can be updated to the received new version information.
In an embodiment, in order to avoid an abnormality and improve robustness of live broadcast update, after receiving the new version information, the first server may further compare the new version information with first version information of a live broadcast list currently stored by the first server. If the comparison result is that the new version information is newer than the first version information, the live broadcast list after the change can be obtained from the database server to be updated locally, and if the comparison result is that the new version information is the same as the first version information or is older than the first version information, the live broadcast list does not need to be obtained from the database server to be updated.
As described above, the first server may send a notification to each second server after updating the changed live list to the local. In one embodiment, the first server may employ a timed broadcast when sending the notification. For example, in one example, the first server may broadcast the notification to the respective second servers via UDP (User Datagram Protocol) Protocol every 100 ms.
An embodiment is provided below, and reference may be made to fig. 3, where fig. 3 is a second scene diagram of live list update provided in the embodiment of the present application. In this embodiment, when the live list stored in the database server is changed, the third server may generate a list change event, and may generate new version information V of the live listnSending a list change message to a message queue, wherein the list change message carries the new version information Vn。
The first servers (3 are shown in the figure, and any one of the first servers is taken as an example for explanation here) can acquire the columns from the message queueThe table change information can be changed, and the new version information V carried in the table change information can be changednFirst version information V of live broadcast list currently stored with the first version information VlA comparison is made. If the comparison result is Vn＞V1Then, the changed live broadcast list can be obtained from the database server, the changed live broadcast list is stored in the local cache, and the first version information V of the currently stored live broadcast list can be updatedlFor the new version information Vn。
The first server may broadcast a notification to each second server (6 are shown in the figure) at regular time through UDP protocol, where the broadcast notification carries first version information V of a live broadcast list currently stored by the first serverl。
After receiving the notification of any first server, the second server may send the first version information V carried in the notificationlSecond version information V of live list currently stored with itselftMaking a comparison if Vl＞VtThen, the changed live broadcast list may be obtained from the first server that sends the notification, the changed live broadcast list may be stored in the local service process cache, and the second version information V of the currently stored live broadcast list may be updated at the same timetFor the received first version information Vl。
According to the live list updating method provided by the embodiment of the application, when the live list is changed, the first server accesses the database server to obtain the changed live list, other second servers do not need to access the database server, and the changed live list can be obtained from the first server.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a live list updating system provided in an embodiment of the present application, where the system may include:
a database server 410, configured to store a live broadcast list, where the live broadcast list includes live broadcast information corresponding to each anchor broadcast currently being broadcast;
the first server 420 is configured to, when it is determined that the live broadcast list is changed, obtain a changed live broadcast list from the database server, update the changed live broadcast list locally, and send a notification to each second server in the same local area network;
and each of the second servers 430 is configured to, after receiving the notification, obtain the changed live list from the first server, and update the changed live list locally.
In one embodiment, the number of the first servers may be more than one. In one embodiment, the system may further include a third server, which may be configured to make changes to the live list in the database server, triggering a list change event.
The system provided by the embodiment of the present application, wherein the steps performed by different servers can be combined with the various embodiments provided in the foregoing. For specific implementation of these embodiments, reference may be made to the related description in the foregoing, and details are not described herein.
The live broadcast list updating system provided by the embodiment of the application has the advantages that when the live broadcast list is changed, the first server accesses the database server to obtain the changed live broadcast list, other second servers do not need to access the database server, and the changed live broadcast list can be obtained from the first server.
Referring to fig. 5, fig. 5 is a second flowchart of a live list updating method provided by an embodiment of the present application, where the method may be applied to a first server, and the method includes:
s502, when the live list is determined to be changed, the changed live list is obtained from the database server, and the changed live list is updated locally.
And S504, sending the notification to each second server in the same local area network.
S506, after receiving the request of the second server for acquiring the live list, transmitting the changed live list to the second server initiating the request, so that the second server can update the changed live list locally.
Regarding the steps performed by the first server, various embodiments have been provided in the foregoing, and detailed descriptions of these embodiments are also provided, and are not repeated here.
According to the live list updating method provided by the embodiment of the application, when the live list is changed, the first server accesses the database server to obtain the changed live list, other second servers do not need to access the database server, and the changed live list can be obtained from the first server.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a live list updating apparatus provided in an embodiment of the present application, where the apparatus includes:
an obtaining module 610, configured to obtain a changed live broadcast list from a database server and update the changed live broadcast list locally when it is determined that the live broadcast list is changed;
a notification module 620, configured to send a notification to each second server in the same local area network;
a transmission module 630, configured to transmit the changed live list to the second server initiating the request after receiving the request of the second server for acquiring the live list, so that the second server updates the changed live list locally.
For the steps performed by the live list updating apparatus, reference may be made to various embodiments of the steps performed by the first server provided in the foregoing, and details are not described herein again.
The live broadcast list updating device provided by the embodiment of the application has the advantages that when the live broadcast list is changed, the device can access the database server to obtain the changed live broadcast list, other second servers do not need to access the database server, and the changed live broadcast list can be obtained from the device.
Embodiments of the present application further provide a computer-readable storage medium, which stores a computer program, where the computer program is executed by a processor, and any one of the methods provided in the embodiments of the present application is provided.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present application. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing description of specific embodiments of the present application has been presented. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
As long as there is no conflict or contradiction between the technical features provided in the above embodiments, a person skilled in the art may combine the technical features according to actual situations to form various embodiments. While the present document is intended to be limited to the details and not by way of limitation, it is understood that various embodiments are also within the scope of the disclosure of the embodiments of the present application.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the embodiments of the application following, in general, the principles of the embodiments of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the embodiments of the application pertain. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the embodiments of the application being indicated by the following claims.
It is to be understood that the embodiments of the present application are not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the embodiments of the present application is limited only by the following claims.
The above description is only for the purpose of illustrating the preferred embodiments of the present application and is not intended to limit the present application, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present application shall be included in the scope of the present application.
Claims (12)
1. A live list updating method is characterized in that a live list comprises live information corresponding to each anchor currently being played, and the method comprises the following steps:
when the first server determines that the live broadcast list is changed, the first server acquires the changed live broadcast list from the database server, updates the changed live broadcast list locally and sends a notice to each second server in the same local area network;
and after receiving the notification, the second server acquires the changed live list from the first server and updates the changed live list locally.
2. The method of claim 1, wherein the local area network comprises a plurality of the first servers, and wherein each of the first servers sends a notification to each of the second servers after the update of the live list is completed.
3. The method according to claim 2, wherein the notification sent by the first server carries first version information of a live list currently stored by the first server;
the second server obtains the changed live list from the first server, and the method includes:
and the second server compares second version information of a live list currently stored by the second server with the first version information, and if the first version information is newer than the second version information, the changed live list is acquired from the first server.
4. The method of claim 3, further comprising:
and after the second server finishes updating the live list, updating the second version information into the first version information.
5. The method of claim 1, wherein the first server determines that the live list has changed, comprising:
and the first server determines that the live list is changed according to the received list change message, wherein the list change message is sent by the third server when the live list stored in the database server is changed.
6. The method of claim 5, wherein the list change message carries new version information of the live list, the new version information being generated by the third server when changing the live list stored in the database server;
the method further comprises the following steps:
and after the first server finishes updating the live list, updating the first version information of the live list currently stored by the first server into the new version information.
7. The method of claim 6, wherein the first server obtains the changed live list from a database server, and comprises:
and the first server compares the first version information with the new version information, and if the new version information is newer than the first version information, a changed live broadcast list is obtained from a database server.
8. The method of claim 1, wherein the first server sends the notification to each of the second servers by way of a timed broadcast.
9. A live listing update system, the system comprising:
the database server is used for storing a live broadcast list, and the live broadcast list comprises live broadcast information corresponding to each anchor broadcast currently being played;
the first server is used for acquiring the changed live broadcast list from the database server when the live broadcast list is determined to be changed, updating the changed live broadcast list locally and sending a notice to each second server in the same local area network;
and each second server is used for acquiring the changed live list from the first server after receiving the notification, and updating the changed live list locally.
10. A live list updating method applied to a first server, the method comprising:
when the live list is determined to be changed, obtaining a changed live list from a database server, and updating the changed live list locally;
sending a notification to each second server in the same local area network;
and after receiving a request of the second server for acquiring the live list, transmitting the changed live list to the second server initiating the request, so that the second server can update the changed live list locally.
11. A live list updating apparatus, wherein the live list includes live information corresponding to respective anchor broadcasts currently being played, the apparatus comprising:
the acquisition module is used for acquiring a changed live broadcast list from a database server and updating the changed live broadcast list locally when the live broadcast list is determined to be changed;
the notification module is used for sending a notification to each second server in the same local area network;
and the transmission module is used for transmitting the changed live broadcast list to the second server initiating the request after receiving the request of the second server for acquiring the live broadcast list, so that the second server can update the changed live broadcast list locally.
12. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method according to any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110579240.1A CN113301379B (en) | 2021-05-26 | 2021-05-26 | Live broadcast list updating method, device, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110579240.1A CN113301379B (en) | 2021-05-26 | 2021-05-26 | Live broadcast list updating method, device, system and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113301379A true CN113301379A (en) | 2021-08-24 |
| CN113301379B CN113301379B (en) | 2022-10-04 |
Family
ID=77325241
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110579240.1A Active CN113301379B (en) | 2021-05-26 | 2021-05-26 | Live broadcast list updating method, device, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113301379B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1481635A (en) * | 2000-10-26 | 2004-03-10 | 普里斯梅迪亚网络有限公司 | Method and appts. for large payload distribution in network |
| WO2008134972A1 (en) * | 2007-04-29 | 2008-11-13 | Huawei Technologies Co., Ltd. | Method, system and server for realizing list information synchronization |
| CN102571923A (en) * | 2011-12-13 | 2012-07-11 | 中国电子科技集团公司第十五研究所 | Data synchronization system and method |
| CN106302780A (en) * | 2016-08-25 | 2017-01-04 | 北京京东尚科信息技术有限公司 | The method of cluster device bulk transfer data, Apparatus and system, server |
| CN107133234A (en) * | 2016-02-29 | 2017-09-05 | 阿里巴巴集团控股有限公司 | The method of data cached renewal, apparatus and system |
| CN109189460A (en) * | 2018-11-20 | 2019-01-11 | 北京千丁互联科技有限公司 | offline firmware upgrade system and method |
| CN109862376A (en) * | 2019-02-28 | 2019-06-07 | 广州华多网络科技有限公司 | Live content jettison system, method, apparatus, listserv and storage medium |
| CN110659121A (en) * | 2019-09-24 | 2020-01-07 | 北京达佳互联信息技术有限公司 | Task data acquisition method and device, task configuration method and device and server |
| CN110933448A (en) * | 2019-11-29 | 2020-03-27 | 广州市百果园信息技术有限公司 | Live list service system and method |
| JP2020052871A (en) * | 2018-09-28 | 2020-04-02 | Kddi株式会社 | Information management apparatus, information management system, and information management method |
-
2021
- 2021-05-26 CN CN202110579240.1A patent/CN113301379B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1481635A (en) * | 2000-10-26 | 2004-03-10 | 普里斯梅迪亚网络有限公司 | Method and appts. for large payload distribution in network |
| WO2008134972A1 (en) * | 2007-04-29 | 2008-11-13 | Huawei Technologies Co., Ltd. | Method, system and server for realizing list information synchronization |
| CN102571923A (en) * | 2011-12-13 | 2012-07-11 | 中国电子科技集团公司第十五研究所 | Data synchronization system and method |
| CN107133234A (en) * | 2016-02-29 | 2017-09-05 | 阿里巴巴集团控股有限公司 | The method of data cached renewal, apparatus and system |
| CN106302780A (en) * | 2016-08-25 | 2017-01-04 | 北京京东尚科信息技术有限公司 | The method of cluster device bulk transfer data, Apparatus and system, server |
| JP2020052871A (en) * | 2018-09-28 | 2020-04-02 | Kddi株式会社 | Information management apparatus, information management system, and information management method |
| CN109189460A (en) * | 2018-11-20 | 2019-01-11 | 北京千丁互联科技有限公司 | offline firmware upgrade system and method |
| CN109862376A (en) * | 2019-02-28 | 2019-06-07 | 广州华多网络科技有限公司 | Live content jettison system, method, apparatus, listserv and storage medium |
| CN110659121A (en) * | 2019-09-24 | 2020-01-07 | 北京达佳互联信息技术有限公司 | Task data acquisition method and device, task configuration method and device and server |
| CN110933448A (en) * | 2019-11-29 | 2020-03-27 | 广州市百果园信息技术有限公司 | Live list service system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113301379B (en) | 2022-10-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4732661B2 (en) | How to synchronize the client database with the server database | |
| CN109542529B (en) | Function name-based point burying method and device, computer equipment and storage medium | |
| CN108156252B (en) | Data access method and device, server and client | |
| CN110048896B (en) | Cluster data acquisition method, device and equipment | |
| CN111273963B (en) | Application program configuration information generation method and device, computer equipment and medium | |
| CN113094430B (en) | Data processing method, device, equipment and storage medium | |
| CN102868550A (en) | Total network flow scheduler and method for querying domain name resolution record by using total network flow scheduler | |
| CN107025257B (en) | Transaction processing method and device | |
| US20190172063A1 (en) | Service displaying method and terminal | |
| CN113301379B (en) | Live broadcast list updating method, device, system and storage medium | |
| CN108366097A (en) | Resource access control method and system | |
| CN114422591B (en) | Point-to-point communication method, data communication system, computer device, and storage medium | |
| WO2022033291A1 (en) | Ranking list service system, ranking list generation method, server, and storage medium | |
| CN111367921A (en) | Data object refreshing method and device | |
| US20070038746A1 (en) | Event management methods and systems | |
| CN114205354A (en) | Event management system, event management method, server, and storage medium | |
| CN111600958B (en) | Service discovery system, service data management method, server, and storage medium | |
| CN102118421A (en) | Peer-to-peer network and method for restarting peer nodes | |
| CN117097744B (en) | Information synchronization method, controlled device, control device and electronic device | |
| CN105677704A (en) | Information arrangement method and device, and information management method and device | |
| CN115004662A (en) | Data synchronization method, data synchronization device, data storage system and computer readable medium | |
| US11277473B1 (en) | Coordinating breaking changes in automatic data exchange | |
| CN113423095B (en) | Information interaction method and device and electronic equipment | |
| CN116340380A (en) | Recommendation system and recommendation method | |
| CN116827966B (en) | Data processing method and system |
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 |