WO2019136840A1

WO2019136840A1 - Bullet screen posting time control method and system, and storage medium and electronic device

Info

Publication number: WO2019136840A1
Application number: PCT/CN2018/081283
Authority: WO
Inventors: 周志刚; 张文明; 陈少杰
Original assignee: 武汉斗鱼网络科技有限公司
Priority date: 2018-01-09
Filing date: 2018-03-30
Publication date: 2019-07-18
Also published as: CN108307244A; CN108307244B

Abstract

Disclosed are a bullet screen posting time control method and system, a storage medium and an electronic device, which relate to the field of mobile Internet applications. The method comprises: using, in a Native layer of an Android system, the language C++ to establish a queue for storing bullet screens to be sent; a live broadcast client logging in to a server, and the server encrypting pre-set posting interval time data of a current live broadcast client login user and then sending same to the live broadcast client; the live broadcast client decrypting the posting interval time data, and calculating a time interval between a current bullet screen to be sent and the previous bullet screen successfully sent by the user and comparing same with a posting interval time obtained by means of decryption; and sequentially removing, from the queue, the bullet screens to be sent and sending same to the server, and the server calculating time intervals between the received bullet screens to be sent and the previous bullet screen successfully sent by the user and comparing same with a pre-set time interval. The present invention can effectively limit the posting interval time of a user.

Description

Barrage speaking time control method, storage medium, electronic device and system

Technical field

The present invention relates to the field of mobile internet applications, and in particular, to a barrage speaking time control method, a storage medium, an electronic device and a system.

Background technique

At present, with the development of the mobile Internet, live broadcasts are more and more popular among the public. The live broadcast of the audience during the live broadcast enhances the interaction between the anchor and the audience, so more and more viewers pass. Send a barrage to participate in the live broadcast, and strengthen interaction and communication with the anchor.

However, some viewers reduce the quality of the barrage of the entire live broadcast platform by frequently sending advertisement barrage or malicious vulgarity. At the same time, some hackers use illegal means to send a large amount of barrage information to maliciously attack the anchor platform, so that the live broadcast platform The server is avalanche due to excessive pressure, which affects the viewer's normal viewing of the live broadcast or damage to the live platform.

Summary of the invention

In view of the deficiencies in the prior art, an object of the present invention is to provide a method for controlling the speaking time of a barrage, which can effectively limit the interval of speaking of a user.

In order to achieve the above object, the technical solution adopted by the present invention includes:

Create a queue for storing the barrage to be sent;

The live client logs in to the server, and the server encrypts the preset live broadcast client login interval data and sends it to the live client.

The live client decrypts the interval data of the speech, and calculates the time interval between the current to-be-transmitted barrage and the successful transmission of the barrage of the user, and compares with the interval of the speech obtained by the decryption. If it is smaller, the current to-be-transmitted bomb is discarded. If the screen is not less than, the current to-be-sending barrage is added to the queue;

The slave to be sent from the queue is sent to the server in turn, and the server calculates the time interval between the received salvage screen and the user successfully transmitting the bullet screen and compares it with the preset time interval. If it is less than, the device is discarded. If the screen is not less than, send the to-be-sent bullet to all live clients to complete the successful transmission of the to-be-sending barrage.

Based on the above technical solutions,

Create a queue for storing the to-be-sending barrage in the native layer of the Android system using the C++ language;

Writing an interface for adding a user-entered blank to be sent to the queue at the Native layer;

For the to-be-transmitted bullets stored in the queue, each of the to-be-sending bullets includes a member variable for indicating the time when the salvage to be sent is added to the queue;

The time interval between the time when the live broadcast client joins the pre-queue using the to-be-sending barrage and the sending time of the user successfully sending the barrage is calculated;

The server calculates the time interval between the pre-join queue time of the received to-be-sending barrage and the transmission time of the user successfully sending the barrage.

On the basis of the foregoing technical solution, the live client logs in to the server, and the live client and the server generate the public key and the private key by using an asymmetric algorithm;

The generated public key is exchanged between the live client and the server, and the live client and the server use the newly obtained public key and the original private key to generate a key, and the key generated by the live client and the server is the same.

Based on the foregoing technical solution, the server uses the generated key and combines the DES encryption algorithm to encrypt the interval time data sent to the current live client login user;

The live broadcast client uses global variables to save the interval data of the speech sent by the server;

The live client obtains the global variable for saving the interval data of the utterance, and uses the generated key and the DES encryption algorithm to decrypt the encrypted interval time data to obtain the utterance interval.

Based on the foregoing technical solution, the server calculates the MD5 value by using the generated key and the sending time of the successfully transmitted barrage, and uses the MD5 value as the key value of the DES encryption algorithm for the current live client login user. The interleave time data is encrypted.

The present invention also provides a storage medium having stored thereon a computer program that, when executed by a processor, implements the method described above.

The present invention also provides an electronic device comprising a memory and a processor having stored thereon a computer program running on a processor, the processor executing the computer program to implement the method described above.

The invention also provides a barrage speaking time control system, comprising:

Creating a module for creating a queue for storing a to-be-sending barrage using the C++ language in the native layer of the Android system;

a data sending module, configured to: when the live client logs in to the server, the server encrypts the preset current live client login user interval interval data and sends the data to the live client;

a judging module, configured to enable the live client to decrypt the interleave time data, and calculate a time interval between the current to-be-transmitted barrage and the user's last successful transmission of the barrage, and compare with the interleave time obtained by the decryption, if less than , the current to-be-sending barrage is discarded, and if not less than, the current to-be-sending barrage is added to the queue;

The barrage sending execution module is configured to sequentially send the to-be-transmitted barrage from the queue and send it to the server, and the server calculates the time interval between the received to-be-transmitted barrage and the user's last successful transmission of the barrage and compares with the preset time interval. If the value is less than, the to-be-sending barrage is discarded. If it is not less than, the to-be-sending barrage is sent to all live broadcast clients to complete the successful transmission of the to-be-sending barrage.

On the basis of the foregoing technical solution, the creating module is further configured to: at the Native layer, write an interface for adding a to-be-sent to be sent by the user to the queue; for each to-be-transmitted barrage stored in the queue, each to be sent The barrage includes a member variable for indicating the time when the barrage to be sent is added to the queue.

On the basis of the foregoing technical solution, the judging module calculates the time interval between the time when the barrage is to be sent to the queue and the sending time of the user successfully sending the barrage; the barrage sending execution module uses the received to be sent. The pre-join queue time of the barrage is calculated from the time when the user sends the barrage successfully.

Compared with the prior art, the present invention has the advantages of: creating a queue for storing the to-be-sending barrage, and the live client and the server determine whether the current to-be-sending barrage meets the speaking interval time based on the user speaking interval time, and satisfying It will be sent to all live broadcast clients to accurately control the time interval of each barrage to be sent by the user, reduce the computing resource pressure of the server, save bandwidth resource consumption of the live broadcast platform, and reduce the generation of illegal barrage. The user's normal viewing of the live broadcast, and to some extent, the loss of bandwidth consumption of the live broadcast platform.

DRAWINGS

1 is a flowchart of a method for controlling a speaking time of a barrage according to an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed ways

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

Referring to FIG. 1 , an embodiment of the present invention provides a method for controlling the speaking time of a barrage, which is applicable to a live broadcast client running on an Android system, and flexibly controls the barrage time of a live client login user to avoid high concurrency. The barrage impacts the server. In the embodiment of the present invention, the server refers to the barrage server of the live broadcast company. Specific includes:

S1: Create a queue for storing the barrage to be sent in the native layer of the Android system using the C++ language. The Native layer is the native framework in the Android system, which is typically implemented in C or C++. In the embodiment of the present invention, a queue for sending a network data packet is developed by using the C++ language, and the to-be-sending barrage waiting for the user to be sent to the server in the live client is placed in the queue in order, thereby realizing the middle layer. In the network sending logic, the thread that is written by the thread is continuously taken out from the queue and sent to the server through the Socket (socket).

This step specifically includes:

S101: Writing a data structure of a barrage, the structure mainly encapsulating related information contained in the barrage to be sent, so that the network sending thread can take out the to-be-sending barrage and directly send it to the server. The data structure is:

StructDanmu

{

Uint64_t startTime;

String danmudata;

}

StruttDanmu is used to define the data as a barrage structure; Uint64_t startTime is used to define a member variable to indicate the time when the barrage to be sent is added to the queue, that is, for each barr to be sent stored in the queue, each barr to be sent Contains a member variable for indicating the time when the salute to be sent is added to the queue, and records the time when the sent barrage is added to the queue; string is used to define a string variable to mark the content of the barrage to be sent, that is, to record the barrage to be sent. Specific text, expressions, etc.

S102: Write a queue for storing a to-be-sending barrage, the queue can be delivered by another thread (such as an interface editing operation of the user to edit the to-be-sending barrage), and the queue's own thread is taken out from the queue to be sent. Barrage to send to the server. The queue uses the list container of the STL container. The STL container is a common container in the C++ language. The list container is a linked list, which can efficiently insert the bullet bar and the barrage operation from the linked list. The bar container stores the barrage. The data structure of the above-mentioned bullet to be sent. It can be understood that the barrage to be sent is stored in the queue in the form of a data structure.

Regarding the queue, the specific implementation is:

Write a class of a queue containing a member variable list<Danmu> for storing the to-be-sending barrage, and writing an interface for the user to input the to-be-sent bullet bar to be queued at the native layer, thereby facilitating the slave queue Take out the barrage to be sent or add the bar to be sent to the queue. The class specific code is:

Class Cqueue

{

Public:

Danmu*GetDanmu()

{

Lock(m_mutex);//Locks the mutex variable to prevent other threads from adding tasks and tasks to the queue at the same time.

If(m_listTask.empt())

{return NULL;}//If there are no tasks in the queue, the returned task is empty.

Danmu*pTask=m_listTask.front();//Retrieve a task from the head of the task queue.

m_listTask.pop_front();// Remove the task from which the header was taken out of the queue.

}

Void AddDanmu(Danmu*pTask)

{

Lock(m_mutex);//Locks the mutex variable to prevent other threads from adding tasks to the queue at the same time.

S103: If the subsequent to-be-sent bullet is added to the queue, then:

m_listTask.push_back(pTask);//Add a task to the task queue and join the end of the task queue.

}

Private:

Time m_lasttime; / / Define a moment when the last barrage was added to the queue.

List<Danmu*>m_listTask;//Define a list container to store the task Danmu.

Mutexm_mutex;//Define a mutex variable to ensure that the operation of the task queue is thread-safe. When multiple threads operate on a queue at the same time, the mutex variable guarantee operations are performed in sequential order.

}

S104: Write a function for creating a thread, specifically by calling the Android system API function CreateThread, wherein the important parameter is the address of the thread function, the thread function is the entire execution logic of the thread, and defines a thread class. :

Class Thread

{

Private:

Cqueuem_queue;

}

The thread class mainly stores a task queue to mark the task queue of the thread, so that the thread object can obtain the task queue of the thread.

S105: writing a specific thread function, the thread function is a loop structure, and the task is continuously taken out from the task queue to execute, if there is no task, the sleep is performed until the task to be executed is a task that exits the thread loop, then the thread Execution will be terminated. The specific implementation is as follows:

While(True)//Create a loop to get the task execution from the task queue.

{

Danmu*pTask=queue.GetDanmu();//Create a task queue object Cqueue queue; take a barrage from the queue to the variable pTask

If(pDanmu==NULL)// This branch indicates that the fetched task is empty, indicating that there are no executable tasks in the task queue at this time. Then at this point, it goes to sleep state, and the CPU resources are given out to other threads.

{

Sleep(10);//call system function sleep 10 milliseconds

}

Else

}

In an embodiment, when the barrage to be sent is taken out from the queue, the time interval between the two times to be sent from the queue to be sent to the barrage is compared with the time interval of the user's speech. If not, the discard is discarded. If it is less than, the retrieved barrage is sent to the server.

S2: The live client logs in to the server. The server encrypts the preset live broadcast client login interval data and sends it to the live client. The server may need to flexibly set the interval between each user, such as 30s and 10s. Etc. Of course, for high-level VIP users, high-quality users or house management, the interval between them can be set to 0s, and for users who frequently send illegal advertisements, the interval between barrage speeches is other users. Many times.

S201: The live client logs in to the server, and the live client and the server generate the public key and the private key by using an asymmetric algorithm. Further, each time the live client logs in to the server, a pair of public and private keys are generated to ensure each time. The public key and the private key are different, so as to ensure the security of the data transmission during the interval. In the embodiment of the present invention, the private key of the live client and the server is generated by using a random number, and then RSA (public key encryption algorithm) is called to generate a corresponding public key.

For the public and private keys generated by the live client:

1, generate a random number, the corresponding code is anddata = rand (); that is, by calling the Android system function rand to generate a random number Randdata.

2. Generate the Md5 value as a private key based on the random number. The corresponding code is:

ClientPrivatekey=Md5.Create(Randdata)

That is, the Md5 value is calculated for the random number by calling the interface Md5.Create of the Md5 function, thereby obtaining the private key data.

3. Calculate the public key, the corresponding code is:

ClientPublickey=RSA.CreatePair(ClientPrivatekey);

That is, the RSA generation pairing key interface RSA.CreatePair is called to generate the public key.

At this point, the generation of the public key and private key of the live client is completed.

For server generated public and private keys:

2. Generate the Md5 value as a private key based on the random number and the number of user IDs. The corresponding code is:

ServerPrivatekey=Md5.Create(Randdata+Uid)

That is, by calling the Md5.Create interface of the Md5 function, the Md5 value is calculated together with the spliced random number and the number of user IDs, thereby obtaining the private key data.

3. Calculate the public key, the corresponding code is:

ServerPublickey=RSA.CreatePair(ServerPrivatekey);

At this point, the generation of the server public key and private key is completed.

S202: The generated public key is exchanged between the live client and the server, and the live client and the server use the newly obtained public key and the original private key to generate a key, and the key generated by the live client and the server is the same. That is, the server and the client exchange their respective public key information to generate a shared secret key, and the shared secret key generated by the client and the server is the same value. specific:

1. Exchange public keys. The server sends the server's public key ServerPublickey to the client. The client sends the client's public key ClientPublickey to the server.

2. The client generates a shared secret key. The corresponding code is: ShareKey=RSA.CreateShareKey(ServerPublickey, ClientPrivatekey).

3. The server generates a shared secret key. The corresponding code is: ShareKey=RSA.CreateShareKey(ClientPublickey, ServerPrivatekey).

At this point, both the client and the server complete the generation of the key ShareKey, and the client and the server's secret Key are the same.

S203: The server encrypts the speaking interval time data sent to the current live client login user by using the generated key and the DES encryption algorithm. After the live client logs in to the server, the server reads the interval between the users logging in to the live client and encrypts the key obtained before, so as to ensure the security of the data in the network transmission and prevent the hacker from getting the user. The interval data is spoken and the data is tampered to bypass the detection of the barrage transmission interval by the live client. The server uses the DES encryption algorithm to encrypt the user's speaking interval data. The corresponding code is:

encryptData=DES.encrypt("time",ShareKey);

DES.encrypt is the encryption interface of the encryption algorithm DES; the parameter "time" is the interval of the user's speech; the parameter ShareKey is the shared key generated by the previous step; the return value encryptData is the generated encrypted result. The encrypted speech interval time data is sent to the live client through the network.

S204: The live broadcast client uses the global variable to save the encrypted interleave time data sent by the server, and does not decrypt the data for the time being. The live client uses the global variable to protect the encrypted encryptData sent by the server to ensure the security of the data in the memory. . The code to save encryptData using global variables is: G_encryptData=encryptData.

In an implementation manner, the server encrypts the interval data of the speech sent to the live client, and the server calculates the MD5 value by using the generated key and the sending time of the successfully transmitted barrage, and uses the MD5 value as the MD5 value. The key value of the DES encryption algorithm encrypts the interval data of the current live client login user, and the subsequent live server uses the algorithm to decrypt the encrypted speech interval data. specific:

Key=Md5.Create(time2+ShareKey)

G_encryptData=DES.encrypt(time,key)

Use the calculated sharekey and the time of the successful transmission of the barrage to calculate the MD5 value, and use the md5 value as the key value during encryption to ensure that the encryption value is always changing every time, further improving the threshold of being hacked.

S3: The live client decrypts the interval data of the speaking interval. Specifically, the live client obtains the global variable for saving the interval data of the speaking interval, and simultaneously decrypts the encrypted interval data by using the generated key and the DES encryption algorithm to obtain the speaking interval. Time, the decryption code is Time=DES.decrypt(G_encryptData,ShareKey);

Then, the time interval between the current to-be-transmitted barrage and the user's last successful transmission of the barrage is calculated, and compared with the interval of the speeches obtained by the decryption. If it is less than, the current to-be-sending barrage is discarded. If not less, the current The barrage to be sent is added to the queue.

After the user successfully sends a barrage to all live clients via the server, the server will record the time when the barrage was successfully sent and notify all live clients, so when the user edits the barrage to be sent in the live client and clicks to send The button is used to add the bar to be sent to the queue. At this time, the time when the bar to be sent to the queue is sent and the time when the user has successfully sent the barrage is calculated, and the time interval is obtained, for example, The time to send the barrage to the queue is time2, and the time of sending the barrage successfully sent is time1, then the time interval between the two is time2-time1=elapse, and then the time interval between the speeches obtained by the decryption is compared. If the value is less than, the current to-be-sending barrage is discarded, and the user is prompted to have a speaking interval limit. If not, the current to-be-sending barrage is added to the queue.

When the to-be-sending barrage is pre-joined to the queue, it is judged whether the time of sending the barrage time satisfies the speaking interval of the user. Since the code developed by the JAVA layer is easily reversed by the hacker, the core speech interval judging function is moved to the native layer. It is safer to use C and C++ language development, in order to allow Java code running in JVM (Java Virtual Machine) and Native code (mainly C or C++) running outside JVM to communicate with Native layer. Writers can use JNI (Java Native Interface) to call Native code from Java programs, and Java code from Native programs, so that programmers can package low-level code logic to higher-order ones. In the program framework, while achieving high performance and high efficiency, the high abstraction of the code framework is ensured, and the network transmission barrage function is also moved to the Native layer. This paper designs the network layer queue to store the bombs sent by the client. Screen, and judge the transmission interval of the barrage at the network layer, ensuring the interval between the live client and the user's barrage Between the accuracy of the judgment.

S4: sequentially sending out the to-be-sent bullets from the queue and sending them to the server, and the server calculates the time interval between the received salvage screen and the user successfully sending the bullets and compares them with the preset time interval, and the server sends the time to the barrage. The detection is performed again. If it is less than, the to-be-sending barrage is discarded. If it is not less than, the to-be-sending barrage is sent to all live clients to complete the successful transmission of the to-be-sending barrage.

The live broadcast client uses the time when the to-be-sending barrage is pre-joined to the queue and the time interval for the user to send the barrage successfully. The server uses the pre-join queue time of the received barrage to be sent and the user successfully sends the barrage. The transmission time is calculated by the time interval.

The barrage speaking time control method of the present invention creates a queue for storing the barrage to be sent. After the live client logs in to the server, the server encrypts the current user's speech interval time data and sends it to the live client, so that the live client When the end user sends the to-be-sending barrage, it determines whether the current to-be-sending barrage meets the interval of the speech interval based on the obtained interleave interval. If it is not satisfied, the end user discards, and the satisfied to-be-sending barrage is sent to the server, and the server will again If the judgment is made, it will be sent to all live broadcast clients to accurately control the time interval of each barrage to be sent by the user, reduce the computing resource pressure of the server, and save bandwidth resource consumption of the live broadcast platform and reduce illegal bombs. The generation of the screen ensures the normal viewing of the live broadcast by the user and the loss of bandwidth consumption of the live broadcast platform to a certain extent.

In addition, in accordance with the above-described barrage speaking time control method, the present invention further provides a storage medium on which a computer program is stored, and when the computer program is executed by the processor, the barrage speaking time control method described in the above embodiments is implemented. step. It should be noted that the storage medium includes a U disk, a mobile hard disk, a ROM (Read-Only Memory), a RAM (Random Access Memory), a disk or an optical disk, and the like. The medium of the code.

Referring to FIG. 2, in accordance with the above-described barrage speaking time control method, the present invention further provides an electronic device including a memory and a processor, wherein the memory stores a computer program running on the processor, and when the processor executes the computer program, The barrage speaking time control method of each of the above embodiments is implemented.

The invention also provides a barrage speaking time control system based on the above-mentioned barrage speaking time control method, which comprises a creating module, a data sending module, a judging module and a barrage sending and executing module.

The creation module is used to create a queue for storing the to-be-sending barrage in the native layer of the Android system using the C++ language; the data sending module is used to log in to the server when the live client logs in, and the server will preset the interval of the current live client login user to speak. The data is encrypted and sent to the live client; the judging module is configured to enable the live client to decrypt the interleave time data, and calculate the time interval between the current to-be-transmitted barrage and the user's last successful transmission of the barrage, and the speech obtained by decryption Interval time comparison, if it is less than, the current to-be-sending barrage is discarded. If it is not less than, the current to-be-sending barrage is added to the queue; the barrage sending execution module is used to sequentially retrieve the to-be-sent of the barrage from the queue and send it to the server. The server calculates the time interval between the received to-be-transmitted barrage and the user's last successful transmission of the barrage and compares it with the preset time interval. If it is less than, it discards the to-be-transmitted barrage. If it is not less than, it sends the to-be-send barrage to All live broadcast clients complete the successful sending of the to-be-sending barrage.

The creation module is further configured to write an interface for adding the user-entered to-be-transmitted bulletscreen to the queue at the Native layer; for the to-be-transmitted bullet-screen to be sent in the queue, each of the to-be-sent bullets is included to indicate the to-be-sent The barrage is added to the member variable of the queue time. The judging module calculates the time interval between the time when the barrage is to be sent to the queue and the sending time of the user successfully sending the barrage; the barrage sending execution module uses the pre-joining queue time of the received barrage to be sent and the user is successfully posted. Send the time of transmission of the barrage calculation interval.

In the barrage speaking time control system of the embodiment of the present invention, after the live client logs in to the server, the data sending module causes the server to encrypt the current interval time data of the current user and send the data to the live client, so that the live client user is sent to be sent. When the barrage is performed, it is judged whether the current to-be-transmitted barrage meets the interval of the speech interval based on the obtained interval of the speech. If it is not satisfied, the discard is discarded, and the satisfied barrage to be sent is sent to the server, and the server will judge again. It will be sent to all live broadcast clients of the barrage through the barrage sending execution module, which can accurately control the time interval of each barrage to be sent by the user, reduce the computing resource pressure of the server, and save the bandwidth resource consumption of the live broadcast platform and reduce The production of illegal barrage ensures the normal viewing of the live broadcast by the user and the loss of bandwidth consumption of the live broadcast platform to a certain extent.

The present invention is not limited to the above embodiments, and those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. These improvements and retouchings are also considered as protection of the present invention. Within the scope. The contents not described in detail in the present specification belong to the prior art well known to those skilled in the art.

Claims

A barrage speaking time control method is applicable to a live broadcast client running on an Android system, and is characterized in that:

Create a queue for storing the barrage to be sent;

The live client logs in to the server, and the server encrypts the preset live broadcast client login interval data and sends it to the live client.

The live client decrypts the interval data of the speech, and calculates the time interval between the current to-be-transmitted barrage and the successful transmission of the barrage of the user, and compares with the interval of the speech obtained by the decryption. If it is smaller, the current to-be-transmitted bomb is discarded. If the screen is not less than, the current to-be-sending barrage is added to the queue;

The slave to be sent from the queue is sent to the server in turn, and the server calculates the time interval between the received salvage screen and the user successfully transmitting the bullet screen and compares it with the preset time interval. If it is less than, the device is discarded. If the screen is not less than, send the to-be-sent bullet to all live clients to complete the successful transmission of the to-be-sending barrage.
A barr speaking time control method according to claim 1, wherein:

Create a queue for storing the to-be-sending barrage in the native layer of the Android system using the C++ language;

Writing an interface for adding a user-entered blank to be sent to the queue at the Native layer;

For the to-be-transmitted bullets stored in the queue, each of the to-be-sending bullets includes a member variable for indicating the time when the salvage to be sent is added to the queue;

The time interval between the time when the live broadcast client joins the pre-queue using the to-be-sending barrage and the sending time of the user successfully sending the barrage is calculated;

The server calculates the time interval between the pre-join queue time of the received to-be-sending barrage and the transmission time of the user's last successful transmission of the barrage.
A barr speaking time control method according to claim 1, wherein:

The live client logs in to the server, and the live client and the server generate the public and private keys using asymmetric algorithms.

The generated public key is exchanged between the live client and the server, and the live client and the server use the newly obtained public key and the original private key to generate a key, and the key generated by the live client and the server is the same.
A barr speaking time control method according to claim 3, wherein:

The server encrypts the speaking interval data sent to the current live client login user by using the generated key and the DES encryption algorithm;

The live broadcast client uses global variables to save the interval data of the speech sent by the server;

The live client obtains the global variable for saving the interval data of the utterance, and uses the generated key and the DES encryption algorithm to decrypt the encrypted interval time data to obtain the utterance interval.
A barr speaking time control method according to claim 3, wherein:

The server uses the generated key to calculate the MD5 value together with the sending time of the successfully transmitted barrage, and uses the MD5 value as the key value of the DES encryption algorithm to encrypt the floor interval data of the current live client login user.
A storage medium having stored thereon a computer program, wherein the computer program is executed by a processor to implement the method of any one of claims 1 to 5.
An electronic device comprising a memory and a processor, the memory having stored thereon a computer program running on the processor, wherein the processor executes the computer program to implement the method of any one of claims 1 to method.
A barrage speaking time control system, comprising:

Creating a module for creating a queue for storing a to-be-sending barrage using the C++ language in the native layer of the Android system;

a data sending module, configured to: when the live client logs in to the server, the server encrypts the preset current live client login user interval interval data and sends the data to the live client;

a judging module, configured to enable the live client to decrypt the interleave time data, and calculate a time interval between the current to-be-transmitted barrage and the user's last successful transmission of the barrage, and compare with the interleave time obtained by the decryption, if less than , the current to-be-sending barrage is discarded, and if not less than, the current to-be-sending barrage is added to the queue;

The barrage sending execution module is configured to sequentially send the to-be-transmitted barrage from the queue and send it to the server, and the server calculates the time interval between the received to-be-transmitted barrage and the user's last successful transmission of the barrage and compares with the preset time interval. If the value is less than, the to-be-sending barrage is discarded. If it is not less than, the to-be-sending barrage is sent to all live broadcast clients to complete the successful transmission of the to-be-sending barrage.
A barrage speaking time control system according to claim 8, wherein the creating module is further configured to write an interface for adding a user-entered barrage to be sent to the queue at the Native layer; The to-be-sending barrage in the queue, each bar-to-send barrage includes a member variable for indicating the time when the barrage to be sent is queued.
The barrage speaking time control system according to claim 9, wherein the judging module calculates the time interval between the time when the barrage to be sent is pre-joined into the queue and the sending time of the user successfully sending the barrage; The barrage sending execution module uses the received pre-join queue time of the to-be-transmitted barrage to calculate the time interval between the sending time of the user successfully sending the barrage.