阅读说明：本技术 数据处理方法、装置、系统、服务器及介质 (Data processing method, device, system, server and medium ) 是由 杜海涛 于 2020-11-16 设计创作，主要内容包括：本公开关于一种数据处理方法、装置、系统、服务器及介质；第一服务器能够获得第一组号以及第二组号,第一组号是第一服务器所在分组的组号,第二组号为获得交互数据的至少一个第二服务器所属分组的组号,所以第一服务器具有“鉴别分组”的功能；若第一组号与第二组号相同,第一服务器可以响应第一请求。若第一组号与第二组号不同,第一服务器不响应第一请求,从而避免了相关机构对应的客户端可以向任一服务器发送第一请求,任一服务器即使不属于获得交互数据的至少一个第二服务器所属分组,也只能被动响应第一请求的情况。减少了服务器仅为一个客户端提供交互数据的情况,节约了服务器资源。(The present disclosure relates to a data processing method, apparatus, system, server, and medium; the first server can obtain a first group number and a second group number, wherein the first group number is the group number of a group where the first server is located, and the second group number is the group number of a group to which at least one second server obtaining the interactive data belongs, so that the first server has the function of identifying the group; the first server may respond to the first request if the first group number is the same as the second group number. If the first group number is different from the second group number, the first server does not respond to the first request, so that the situation that a client corresponding to a relevant mechanism can send the first request to any server and the server can only passively respond to the first request even if the server does not belong to a group to which at least one second server for obtaining interactive data belongs is avoided. The situation that the server only provides interactive data for one client is reduced, and server resources are saved.)

1. A data processing method applied to a first server comprises the following steps:

receiving a first request sent by a client; the first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting interactive data corresponding to the first identifier;

acquiring a first group number of a group to which the first server belongs from a preset configuration file; the configuration file comprises configuration information corresponding to at least one packet, wherein the configuration information corresponding to each packet comprises a group number of the packet and an Internet Protocol (IP) address of at least one server contained in the packet;

calculating to obtain a second group number based on the first identifier, wherein the second group number is a group number of a group to which at least one second server belongs, and the second server is used for acquiring the interactive data;

if the first group number is not the same as the second group number, refusing to respond to the first request;

and responding to the first request if the first group number is the same as the second group number.

2. The data processing method according to claim 1, wherein the IP address of the server is a virtual IP address, and the virtual IP address includes a public network IP address of a load balancing server as a data forwarding medium between the server and the client and a port number corresponding to the server;

the step of receiving the first request sent by the client comprises the following steps:

receiving the first request from the client, which is forwarded by a load balancing server; the destination address in the first request is a private network IP address of the first server, and the destination address in the first request is replaced by the load balancing server from the virtual IP address of the first server to the private network IP address;

the step of obtaining the first group number of the group to which the first server belongs from a preset configuration file comprises:

and acquiring the first group number of the group to which the public network IP address of the load balancing server belongs from the preset configuration file.

3. A data processing method is applied to a load balancing server and comprises the following steps:

receiving a first request sent by a client; the first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting to obtain interactive data corresponding to the first identifier; the destination address of the first request is a virtual Internet Protocol (IP) address of the first server; the virtual IP address comprises a public network IP address of the load balancing server and a port number corresponding to the first server;

replacing the virtual IP address in the destination address of the first request with a target private network IP address corresponding to a port number contained in the virtual IP address according to a preset corresponding relation between at least one port number and the private network IP address;

sending the first request with the destination address being the target private network IP address to the first server;

receiving a first message containing the interactive data fed back by the first server; the source address of the first message is the IP address of the target private network; the first message is a response message for the first request under the condition that a first group number is the same as a second group number, the first group number is a group number of a group to which the first server belongs, the second group number is a group number of a group to which at least one second server belongs calculated based on the first identifier, and the second server is used for acquiring the interactive data;

replacing the source address of the first message with the virtual IP address from the target private network IP address to obtain a second message;

and sending the second message to the client.

4. A data processing apparatus, applied to a first server, comprising:

the first receiving module is configured to receive a first request sent by a client; the first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting interactive data corresponding to the first identifier;

the first acquisition module is configured to acquire a first group number of a group to which the first server belongs from a preset configuration file; the configuration file comprises configuration information corresponding to at least one packet, wherein the configuration information corresponding to each packet comprises a group number of the packet and an Internet Protocol (IP) address of at least one server contained in the packet;

a calculating module configured to calculate a second group number based on the first identifier obtained by the first receiving module, where the second group number is a group number of a group to which at least one second server belongs, and the second server is used to obtain the interactive data;

the first processing module is configured to refuse to respond to the first request if the first group number obtained by the first obtaining module is different from the second group number obtained by the calculating module;

the second processing module is configured to respond to the first request if the first group number obtained by the first obtaining module is the same as the second group number calculated by the calculating module.

5. A data processing device applied to a load balancing server comprises:

the third receiving module is configured to receive the first request sent by the client; the first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting to obtain interactive data corresponding to the first identifier; the destination address of the first request is a virtual Internet Protocol (IP) address of the first server; the virtual IP address comprises a public network IP address of the load balancing server and a port number corresponding to the first server;

a first changing module configured to replace the virtual IP address in the destination address of the first request with a target private network IP address corresponding to a port number included in the virtual IP address according to a preset correspondence between at least one port number and a private network IP address;

a second sending module configured to send the first request with a destination address of the target private network IP address to the first server;

a fourth receiving module, configured to receive a first packet containing the interaction data fed back by the first server; the source address of the first message is the IP address of the target private network; the first message is a response message for the first request under the condition that a first group number is the same as a second group number, the first group number is a group number of a group to which the first server belongs, the second group number is a group number of a group to which at least one second server belongs calculated based on the first identifier, and the second server is used for acquiring the interactive data;

a second changing module configured to replace the source address of the first packet received by the fourth receiving module with the virtual IP address from the target private network IP address to obtain a second packet;

and the third sending module is configured to send the second message obtained by the second changing module to the client.

6. A first server, comprising:

a first processor;

a first memory for storing the first processor-executable instructions;

wherein the first processor is configured to execute the instructions to implement the data processing method of any of claims 1 to 2.

7. A load balancing server, comprising:

a second processor;

a second memory for storing the second processor-executable instructions;

wherein the second processor is configured to execute the instructions to implement the data processing method of claim 3.

8. A data processing system, comprising: a database, at least one client, at least one group, one of said groups comprising at least one first server; wherein the database is configured to store configuration files, and each of the first servers is configured to execute the data processing method according to any one of claims 1 to 2.

9. A storage medium, wherein instructions in the storage medium, when executed by a first processor of a first server, enable the first server to perform a data processing method according to any one of claims 1 to 2.

10. A storage medium, wherein instructions in the storage medium, when executed by a processor of a load balancing server, enable the load balancing server to perform the data processing method of claim 3.

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a data processing method, apparatus, system, server, and medium.

Background

The user can watch the live broadcast through the live broadcast room displayed by the client, and in the process of watching the live broadcast, the user needs to watch interactive data, such as data representing the audience to watch the main broadcast, and data such as voice, characters or pictures sent by the audience in the live broadcast room, besides the data (audio data and/or video data) of the main broadcast.

In the related art, the process of requesting interactive data through a client is as follows: the client can randomly send a request for acquiring interactive data corresponding to the unique identifier of the live broadcast room to the server based on a public network IP (Internet Protocol Address) Address of any server, the server responds to the request, acquires the interactive data corresponding to the unique identifier from the database, and sends the interactive data to the client.

Because the client randomly selects the server to obtain the interactive data, the situation that the server only provides the interactive data corresponding to a certain live broadcast room for one client often occurs, and resource waste is caused.

Disclosure of Invention

The present disclosure provides a data processing method, apparatus, system, server, and medium, to at least solve a problem in the related art that if a group to which a server responding to a related mechanism belongs is not a group corresponding to the target group number, the server needs to additionally obtain interactive data in a live broadcast room a. The technical scheme of the disclosure is as follows:

according to a first aspect of the embodiments of the present disclosure, there is provided a data processing method, applied to a first server, including: receiving a first request sent by a client; the first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting interactive data corresponding to the first identifier;

acquiring a first group number of a group to which the first server belongs from a preset configuration file; the configuration file comprises configuration information corresponding to at least one packet, wherein the configuration information corresponding to each packet comprises a group number of the packet and an Internet Protocol (IP) address of at least one server contained in the packet;

calculating to obtain a second group number based on the first identifier, wherein the second group number is a group number of a group to which at least one second server belongs, and the second server is used for acquiring the interactive data;

if the first group number is not the same as the second group number, refusing to respond to the first request;

and responding to the first request if the first group number is the same as the second group number.

With reference to the first aspect, in a first possible implementation manner, the IP address of the server is a virtual IP address, where the virtual IP address includes a public network IP address of a load balancing server serving as a data forwarding medium between the server and a client and a port number corresponding to the server;

the step of receiving the first request sent by the client comprises the following steps:

receiving the first request from the client, which is forwarded by a load balancing server; the destination address in the first request is a private network IP address of the first server, and the destination address in the first request is replaced by the load balancing server from the virtual IP address of the first server to the private network IP address;

the step of obtaining the first group number of the group to which the first server belongs from a preset configuration file comprises:

and acquiring the first group number of the group to which the public network IP address of the load balancing server belongs from the preset configuration file.

With reference to the first aspect, in a second possible implementation manner, before the step of receiving the first request sent by the client, the method further includes:

receiving a second request from the client, which is forwarded by the load balancing server, wherein a destination address carried by the second request is the private network IP address; the destination address in the second request is replaced by the load balancing server from the virtual IP address of the first server to the private IP address; the second request is for establishing a communication connection with the first server;

if the second request is responded, generating a first response message, wherein the first response message is used for representing that the communication connection with the client is successfully established; the source address of the first response message is the private network IP address;

sending the first response message to the load balancing server so that the load balancing server sends a second response message to the client, wherein the second response message is the response message of the load balancing server after the load balancing server replaces the source address of the first response message with the virtual IP address of the first server from the private IP address.

With reference to the first aspect, in a third possible implementation manner, the configuration file further includes a total number of the packets; the step of calculating a second number based on the first identifier comprises:

acquiring the total number from the preset configuration file;

and calculating to obtain a second group number based on the first identification and the total number.

With reference to the first aspect, in a fourth possible implementation manner, the IP address of the server is a public network IP address; the step of obtaining the first group number of the group to which the first server belongs from a preset configuration file comprises:

and acquiring the first group number of the group to which the public network IP address of the first server belongs from the preset configuration file.

With reference to the first aspect, in a fifth possible implementation manner, the configuration information corresponding to each group further includes a state corresponding to each server, where a state corresponding to one server is whether the server is in a state to be deleted, and if the first group number is the same as the second group number, the step of responding to the first request includes:

responding to the first request if the first group number is the same as the second group number and the first server already creates a business entity object corresponding to the live broadcast room;

if the first group number is the same as the second group number and the first server does not create a business entity object corresponding to the live broadcast room, acquiring the state of the first server from the database;

and responding to the first request if the state of the first server is a first state, wherein the first state is that the first server is not in a state to be deleted.

With reference to the first aspect, in a sixth possible implementation manner, after the step of obtaining the state of the first server from the database if the first group number is the same as the second group number and the first server does not create a service entity object corresponding to the live broadcast, the method further includes:

and if the state of the first server is a second state, refusing to respond to the first request, wherein the second state is that the first server is in a state to be deleted.

According to a second aspect of the embodiments of the present disclosure, there is provided a data processing method applied to a load balancing server, including: receiving a first request sent by a client; the first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting to obtain interactive data corresponding to the first identifier; the destination address of the first request is a virtual Internet Protocol (IP) address of the first server; the virtual IP address comprises a public network IP address of the load balancing server and a port number corresponding to the first server;

replacing the virtual IP address in the destination address of the first request with a target private network IP address corresponding to a port number contained in the virtual IP address according to a preset corresponding relation between at least one port number and the private network IP address;

sending the first request with the destination address being the target private network IP address to the first server;

receiving a first message containing the interactive data fed back by the first server; the source address of the first message is the IP address of the target private network; the first message is a response message for the first request under the condition that a first group number is the same as a second group number, the first group number is a group number of a group to which the first server belongs, the second group number is a group number of a group to which at least one second server belongs calculated based on the first identifier, and the second server is used for acquiring the interactive data;

replacing the source address of the first message with the virtual IP address from the target private network IP address to obtain a second message;

and sending the second message to the client.

With reference to the second aspect, in a first possible implementation manner, before the step of receiving the first request sent by the client, the method further includes:

acquiring at least partial configuration information corresponding to a group to which the load balancing server belongs, wherein the at least partial configuration information comprises the first group number and a virtual IP address of a server which takes the load balancing server as a data forwarding medium of a client;

storing the at least partial configuration information to the database;

and setting a private network IP address which takes the load balancing server as a virtual IP address of the server of the data forwarding medium of the client.

With reference to the second aspect, in a second possible implementation manner, after the step of storing the at least partial configuration information in the database, the method further includes:

if a first operation that a first target server is added in the group to which the load balancing server belongs is detected, setting a corresponding relation between a private network IP address of the first target server and a port number of the first target server;

generating a third request, wherein the third request is used for indicating the database to add the virtual IP address of the first target server in the configuration information of the group to which the load balancing server belongs;

sending the third request to the database.

With reference to the second aspect, in a third possible implementation manner, after the step of storing the at least partial configuration information in the database, the method further includes:

if a second operation of deleting a second target server contained in the group to which the load balancing server belongs is detected, generating a fourth request, wherein the fourth request is used for indicating the database to delete the virtual IP address of the second target server in the configuration information of the group to which the load balancing server belongs;

sending the fourth request to the database.

With reference to the second aspect, in a fourth possible implementation manner, the configuration information corresponding to the group to which the load balancing server belongs further includes a state corresponding to at least one server, and the state corresponding to one server is whether the server is in a state to be deleted; if a second operation of deleting a second target server included in the group to which the load balancing server belongs is detected, generating a fourth request step, including:

if the second operation of deleting a second target server contained in the group to which the load balancing server belongs is detected, generating a fifth request; the fifth request is used for instructing the database to switch the second target server from a first state to a second state, the first state is that the second target server is not in a state to be deleted, and the second state is that the second target server is in a state to be deleted;

sending the fifth request to the database;

and generating the fourth request at a first preset time after the fifth request is generated.

According to a third aspect of the embodiments of the present disclosure, there is provided a data processing apparatus applied to a first server, including:

the first receiving module is configured to receive a first request sent by a client; the first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting interactive data corresponding to the first identifier;

the first acquisition module is configured to acquire a first group number of a group to which the first server belongs from a preset configuration file; the configuration file comprises configuration information corresponding to at least one packet, wherein the configuration information corresponding to each packet comprises a group number of the packet and an Internet Protocol (IP) address of at least one server contained in the packet;

a calculating module configured to calculate a second group number based on the first identifier obtained by the first receiving module, where the second group number is a group number of a group to which at least one second server belongs, and the second server is used to obtain the interactive data;

the first processing module is configured to refuse to respond to the first request if the first group number obtained by the first obtaining module is different from the second group number obtained by the calculating module;

the second processing module is configured to respond to the first request if the first group number obtained by the first obtaining module is the same as the second group number calculated by the calculating module.

With reference to the third aspect, in a first possible implementation manner, the IP address of the server is a virtual IP address, where the virtual IP address includes a public network IP address of a load balancing server as a data forwarding medium between the server and a client and a port number corresponding to the server, and the first receiving module is specifically configured to:

a first receiving unit configured to receive the first request from the client forwarded by a load balancing server; the destination address in the first request is a private network IP address of the first server, and the destination address in the first request is replaced by the load balancing server from the virtual IP address of the first server to the private network IP address;

the first acquisition module is specifically configured to: a first obtaining unit, configured to obtain, from the preset configuration file, the first group number of the packet to which the public network IP address of the load balancing server belongs.

With reference to the third aspect, in a second possible implementation manner, the method further includes:

a second receiving module, configured to receive a second request from the client, where the second request is forwarded by the load balancing server, and a destination address carried in the second request is the private network IP address; the destination address in the second request is replaced by the load balancing server from the virtual IP address of the first server to the private IP address; the second request is for establishing a communication connection with the first server;

a first generating module configured to generate a first response message in response to the second request received by the second receiving module, where the first response message is used to indicate that the communication connection with the client is successfully established; the source address of the first response message is the private network IP address;

a first sending module configured to send the first response message generated by the first generating module to the load balancing server, so that the load balancing server sends a second response message to the client, where the second response message is the response message after the load balancing server replaces the source address of the first response message with the virtual IP address of the first server from the private IP address.

With reference to the third aspect, in a third possible implementation manner, the configuration file further includes a total number of the packets; the computing module is specifically configured to:

a second obtaining unit configured to obtain the total number from the preset configuration file;

a calculating unit configured to calculate a second group number based on the first identifier and the total number obtained by the second obtaining unit.

With reference to the third aspect, in a fourth possible implementation manner, the IP address of the server is a public network IP address, and the first obtaining module is specifically configured to:

a third obtaining unit, configured to obtain, from the preset configuration file, the first group number of the packet to which the public network IP address of the first server belongs.

With reference to the third aspect, in a fifth possible implementation manner, the configuration information corresponding to each group further includes a state corresponding to each server, where the state corresponding to one server is whether the server is in a state to be deleted, and the second processing module is specifically configured to:

a first response unit, configured to respond to the first request if the first group number obtained by the first obtaining module is the same as the second group number calculated by the calculating module, and the first server has already created a service entity object corresponding to the live broadcast room;

a fourth obtaining unit, configured to obtain, if the first group number obtained by the first obtaining module is the same as the second group number calculated by the calculating module, and the first server does not create a service entity object corresponding to the live broadcast room, a state of the first server from the database;

a second responding unit, configured to respond to the first request if the state of the first server obtained by the fourth obtaining unit is a first state, where the first state is that the first server is not in a state to be deleted.

With reference to the third aspect, in a sixth possible implementation manner, the method further includes:

a third processing module, configured to reject to respond to the first request if the state of the first server obtained by the fourth obtaining unit is a second state, where the second state is a state in which the first server is to be deleted.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a data processing apparatus applied to a load balancing server, including: the third receiving module is configured to receive the first request sent by the client; the first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting to obtain interactive data corresponding to the first identifier; the destination address of the first request is a virtual Internet Protocol (IP) address of the first server; the virtual IP address comprises a public network IP address of the load balancing server and a port number corresponding to the first server;

a first changing module configured to replace the virtual IP address in the destination address of the first request with a target private network IP address corresponding to a port number included in the virtual IP address according to a preset correspondence between at least one port number and a private network IP address;

a second sending module configured to send the first request with a destination address of the target private network IP address to the first server;

a fourth receiving module, configured to receive a first packet containing the interaction data fed back by the first server; the source address of the first message is the IP address of the target private network; the first message is a response message for the first request under the condition that a first group number is the same as a second group number, the first group number is a group number of a group to which the first server belongs, the second group number is a group number of a group to which at least one second server belongs calculated based on the first identifier, and the second server is used for acquiring the interactive data;

a second changing module configured to replace the source address of the first packet received by the fourth receiving module with the virtual IP address from the target private network IP address to obtain a second packet;

and the third sending module is configured to send the second message obtained by the second changing module to the client.

With reference to the fourth aspect, in a first possible implementation manner, the method further includes:

a second obtaining module, configured to obtain at least partial configuration information corresponding to a packet to which the load balancing server belongs, where the at least partial configuration information includes the first group number and a virtual IP address of a server that uses the load balancing server as a data forwarding medium with a client;

a storage module configured to store the at least partial configuration information to the database;

a first setting module configured to set the load balancing server as a private network IP address corresponding to a virtual IP address of a server of a data forwarding medium of a client.

With reference to the fourth aspect, in a second possible implementation manner, the method further includes:

a second setting module configured to set a correspondence between a private network IP address of a first target server and a port number of the first target server if a first operation of adding the first target server to a packet to which the load balancing server belongs is detected;

a second generation module configured to generate a third request, where the third request is used to instruct the database to add the virtual IP address of the first target server in the configuration information of the group to which the load balancing server belongs;

a third sending module configured to send the third request to the database.

With reference to the fourth aspect, in a third possible implementation manner, the method further includes: further comprising:

a third generating module, configured to generate a fourth request if a second operation of deleting a second target server included in a packet to which the load balancing server belongs is detected, where the fourth request is used to instruct the database to delete a virtual IP address of the second target server in configuration information of the packet to which the load balancing server belongs;

a fourth sending module configured to send the fourth request generated by the third generating module to the database.

With reference to the fourth aspect, in a fourth possible implementation manner, the configuration information corresponding to the group to which the load balancing server belongs further includes a state corresponding to at least one server, and the state corresponding to one server is whether the server is in a state to be deleted; the third generation module is specifically configured to:

a first generating unit, configured to generate a fifth request if the second operation of deleting a second target server included in the group to which the load balancing server belongs is detected; the fifth request is used for instructing the database to switch the second target server from a first state to a second state, the first state is that the second target server is not in a state to be deleted, and the second state is that the second target server is in a state to be deleted;

a transmitting unit configured to transmit the fifth request generated by the first generating unit to the database;

a second generating unit configured to generate the fourth request a first preset time period after the fifth request is generated.

According to a fifth aspect of embodiments of the present disclosure, there is provided a first server, including: a first processor; a first memory for storing the first processor-executable instructions; wherein the first processor is configured to execute the instructions to implement the data processing method of the first aspect.

According to a sixth aspect of the embodiments of the present disclosure, there is provided a load balancing server, including: a second processor; a second memory for storing the second processor-executable instructions; wherein the second processor is configured to execute the instructions to implement the data processing method of the second aspect.

According to a seventh aspect of embodiments of the present disclosure, there is provided a data processing system comprising: a database, at least one client, at least one group, one of said groups comprising at least one first server; wherein the database is configured to store configuration files, and each of the first servers is configured to execute the data processing method according to the first aspect.

With reference to the seventh aspect, in a first possible implementation manner, the configuration information corresponding to each group includes a state corresponding to at least one server, and the state corresponding to one server is whether the server is in a state to be deleted; the data processing system further comprises an API server;

the API server configured to:

calculating to obtain the second group number based on the first identification;

acquiring configuration information corresponding to the group with the second group number from the database every second preset time;

updating configuration information corresponding to the self-stored grouping with the second group number based on the configuration information obtained from the database;

and sending the virtual IP address of the server in the first state in the configuration information corresponding to the group with the second group number to the client, wherein the server in the first state is not in a state to be deleted.

With reference to the seventh aspect, in a second possible implementation manner, the configuration information corresponding to each group includes a state corresponding to at least one server, and the state corresponding to one server is whether the server is in a state to be deleted; the data processing system further includes an API Upjack server, the database further configured to:

receiving a request of the API server for acquiring the configuration file;

and sending the virtual IP address of the server in the first state in the at least one group contained in the configuration file, the group number corresponding to the at least one group and the total number of the groups to the API server, wherein the first state of one server means that the server is not in a state to be deleted.

According to an eighth aspect of embodiments of the present disclosure, there is provided a storage medium, wherein instructions that, when executed by a first processor of a first server, enable the first server to perform the data processing method according to the first aspect.

According to a ninth aspect of the embodiments of the present disclosure, there is provided a storage medium, wherein instructions when executed by a processor of a load balancing server enable the load balancing server to perform the data processing method according to the second aspect.

According to a tenth aspect of the embodiments of the present disclosure, there is provided a computer program product, which is directly loadable into an internal memory of a computer, for example, a first memory included in the first server according to the fifth aspect, and contains software codes, and which, when loaded and executed by the computer, is capable of implementing the data processing method according to the first aspect.

According to an eleventh aspect of the embodiments of the present disclosure, there is provided a computer program product, which is directly loadable into an internal memory of a computer, for example, a second memory included in the load balancing server according to the above sixth aspect, and contains software codes, and which, when loaded and executed by the computer, is capable of implementing the data processing method according to the second aspect.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

in the data processing method provided by the embodiment of the disclosure, after receiving a first request, a first server acquires a first group number of a group to which the first server belongs from a preset configuration file; calculating to obtain a second group number based on a first identifier carried by the first request, wherein the second group number is a group number of a group to which at least one second server belongs, the second server is used for acquiring the interactive data, and the first server has a function of identifying the group as the first group number and the second group number can be acquired by the first server; if the first group number is the same as the second group number, the first server is said to belong to the group with the second group number, and therefore the first server can respond to the first request. If the first group number is different from the second group number, it is described that the first server does not belong to the group with the group number being the second group number, and therefore, the first server does not respond to the first request, that is, the embodiment of the present disclosure utilizes the function of "authenticating the group" of the first server, so that only the group with the group number being the second group number can respond to the first request, and the servers in other groups cannot respond to the first request, thereby avoiding a situation that a client corresponding to a relevant organization can send the first request to any server, and any server can only passively respond to the first request even if not belonging to the group with the group number being the second group number. The situation that the server only provides interactive data for one client is reduced, and server resources are saved.

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 disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.

FIG. 1 is a signaling diagram illustrating a method of data processing in accordance with an exemplary embodiment;

FIG. 2 is an architecture diagram illustrating a first application scenario in accordance with an illustrative embodiment;

FIG. 3 is an architecture diagram illustrating a second application scenario in accordance with an illustrative embodiment;

FIG. 4 is a flow chart illustrating a method of data processing in accordance with an exemplary embodiment;

FIG. 5 is a flow diagram illustrating a data processing method applied to a load balancing server in accordance with an illustrative embodiment;

FIG. 6 is a signaling diagram illustrating another data processing method in accordance with an example embodiment;

fig. 7 is a signaling diagram illustrating a method of updating configuration information corresponding to a packet in accordance with an example embodiment;

FIG. 8 is a signaling diagram illustrating yet another method of updating configuration information corresponding to a packet in accordance with an exemplary embodiment;

FIG. 9 is a flow chart illustrating yet another method of data processing in accordance with an exemplary embodiment;

FIG. 10 is a block diagram illustrating a data processing apparatus applied to a first server according to an example embodiment;

FIG. 11 is a block diagram illustrating a data processing apparatus applied to a load balancing server in accordance with an illustrative embodiment;

fig. 12 is a block diagram illustrating a method for the first server 14 according to an example embodiment;

fig. 13 is a block diagram illustrating a method for a load balancing server 31 according to an example embodiment.

Detailed Description

In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

Before explaining the technical scheme provided by the embodiment of the present disclosure, the related technologies and application scenarios related to the embodiment of the present disclosure will be explained in detail.

First, a description will be given of a related art to which an embodiment of the present disclosure may relate.

A user watches live broadcast through a live broadcast room displayed by the client, and the client requests an Application Program Interface (API) server for two types of data, wherein the first type of data is live broadcast data (the live broadcast data includes at least one of audio data and video data) played in the live broadcast room, and the second type of data is interactive data corresponding to the live broadcast room, for example, data representing that the audience plays a main broadcast, and data such as voice, characters, or pictures sent by the audience in the live broadcast room. In an embodiment, the interactive data corresponding to the live broadcast room may be obtained according to the first identifier of the live broadcast room.

For example, the API server may feed back, to the client, a pull address corresponding to a CDN (Content Delivery Network) server, so that the client obtains live data from the CDN server based on the pull address.

For example, the API server may feed back, to the client, an IP Address (Internet Protocol Address) of a server to which the client can establish a communication connection, so that the client and the server establish a communication connection, and send, to the server, a request for obtaining interactive data corresponding to a live broadcast room based on the communication connection; and after receiving the request, the server sends the obtained interactive data to the client through communication connection. For example, the API server feeds back an IP address of the server to the client, and after obtaining the IP address, the client establishes a long connection with the server, and sends a request for data interaction to the server through the long connection; after receiving the request, the server feeds back interactive data, and the interactive data is transmitted to the client through the long connection.

The following describes a process of acquiring interactive data by a client in the related art in detail. The related art to which the disclosed embodiments may relate relates to an API server 11, a database 12, at least one client 13, and at least one server 14.

The client 13 may be an application client or a web page version client, for example.

For example, the API server 11 may be a server, a server cluster composed of a plurality of servers, or a cloud computing server center.

For example, the server 14 may be a server, a server cluster composed of a plurality of servers, or a cloud computing server center.

Illustratively, the database 12 is accessible to both the API server 11 and the server 14.

Fig. 1 is a signaling diagram of a data processing method in the related art, which includes the following steps S101 to S110 in implementation.

One client 13, two servers 14 are shown in fig. 1. Fig. 1 is only an example, and the number of the clients 13 and the servers 14 in practical application may be set according to practical requirements.

In step S101, the client 13 generates an address acquisition request for acquiring an IP address of the server; the address acquisition request is sent to the API server 11.

Illustratively, the destination address carried by the address obtaining request is a public network IP address of the API server 11, and the source address is a public network IP address of the electronic device where the client 13 is located.

The expression form of the address obtaining request may be, for example, a message, and may be, for example, an HTTP (HyperText Transfer Protocol) request message, or an HTML (text Markup Language) request message, or an XML (Extensible Markup Language) request message, or a json (javascript Object notification) request message, or a custom message.

The public network IP address of the client 13 mentioned in the embodiment of the present disclosure refers to a public network IP address of an electronic device where the client is located.

The electronic device where the client is located may be any electronic product that can perform human-computer interaction with a user through one or more modes of a keyboard, a touch pad, a touch screen, a remote controller, voice interaction or handwriting equipment, for example, a mobile phone, a tablet computer, a palm computer, a personal computer, a wearable device, a smart television, and the like.

The address acquisition request carries a first identifier of the live broadcast room displayed by the client, and the first identifier may be, for example, a room number of the live broadcast room or an ID of a main broadcast of the live broadcast room.

In step S102, the API server 11 obtains the configuration file from the database 12 in response to the address acquisition request.

The configuration file comprises configuration information corresponding to at least one group, and the configuration information corresponding to each group comprises a group number of the group and a public network IP address of at least one server contained in the group.

Illustratively, the configuration file further includes a total number of the at least one packet, i.e., a number of packets.

In an optional implementation manner, a plurality of machine rooms can be provided, and different machine rooms are located at different geographical positions, for example, the machine room 1 is located in shanghai, and the machine room 2 is located in beijing; one or more servers are provided in one machine room.

In an alternative implementation, one or more rooms may be located in the same geographic location.

It will be appreciated that different clients may be located in different geographic locations or the same geographic location. In one example, server A1 is located in the same geographic location as the client and server A2 is located in a different geographic location than the client, then a first speed at which the client interacts data with server A1 is greater than a second speed at which the client interacts data with server A2. In a special case, if the network status of the server a1 is poor, the first speed may be less than or equal to the second speed.

In an alternative implementation, to meet the general and special cases described above, the servers contained in the rooms are grouped, one group containing at least one server in each room.

Suppose that a total of 3 computer rooms are respectively computer room 1, computer room 2 and computer room 3, and computer room 1 is provided with 4 servers, which are respectively: server a1, server a2, server A3, server a 4; 3 servers are arranged in the machine room 2; server B1, server B2, server B3; be provided with 3 servers in computer lab 3, be respectively: server C1, server C2, and server C3.

Can be divided into 3 packets, packet 1 includes: server a1, server B1, server C1; the packet 2 includes: server a2, server A3, server B2, server C2; the packet 3 includes: server a4, server B3, and server C3. At this time, the total number of the at least one packet, i.e., the number of packets, is 3.

In step S103, the API server 11 determines a second group number based on the first identifier.

In an alternative implementation, the API server 11 may calculate the second group number based on the first identifier and the total number.

For example, assuming that the first identifier is a anchor ID of a live broadcast, the process of calculating the second group number based on the first identifier and the total number may include steps a1 to a 2.

In step a1, a hash value of the ID of the anchor is obtained, int hash — clientip.

In step a2, the total number is modulo by a hash value, e.g., the total number is represented by a variable NUM, int index ═ hash% NUM (); wherein index is the second group number. Alternatively, NUM can be any positive integer, such as 64.

For example, the first identifier and the total number may be subjected to a preset operation to obtain the second number. The preset operation comprises at least one of multiplication, division, addition and weighted average.

In step S104, the API server 11 transmits the public network IP address of the server included in the packet whose group number is the second group number to the client 13.

In the embodiment of the present disclosure, a group with a group number of the second group number is referred to as a second group, and a server included in the second group is referred to as a target server. Although fig. 1 illustrates an example in which the number of servers included in the second packet is 2, fig. 1 is merely an example, and the number of servers included in the second packet is not limited.

In step S105, the client 13 transmits a second request to the public IP address of each destination server 14.

The second request is for requesting establishment of a communication connection with a target server. For each target server, the source address carried by the second request is the public network IP address of the client 13, and the destination address carried by the second request is the public network IP address of the target server.

Since the API server 11 only sends the public network IP address of the server in the group with the group number of the second group number to the client 13, the client 13 can only communicate with the server in the group with the group number of the second group number, that is, the client 13 can only obtain the interactive data through any server in the group with the group number of the second group number, that is, the second group number calculated by the API server is the group number of the group to which the server that obtains the interactive data belongs.

In step S106, for each target server 14, if the second request is accepted, a first response message for accepting the second request is generated; the first response message is sent to the client 13.

In step S106, for each target server 14, the destination address carried in the first response message is the public network IP address of the client, and the source address carried in the first response message is the public network IP address of the target server.

In step S107, the client 13 receives the first response message fed back by each target server, maintains the communication connection with the target server 14 corresponding to the first response message, and disconnects the communication connection with another target server. The first response message is the first response message received by the client, that is, the first response message received earliest.

In the embodiment of the present disclosure, the target server of the communication connection maintained by the client 13 is referred to as a first server.

Assume that one of the two servers shown in fig. 1 is the first server described above. As shown in fig. 1, the client 13 disconnects the communication with one of the servers and maintains the communication with the other server. The rectangular dashed box shown in fig. 1 represents the communication connection that the client 11 maintains, and the server that maintains the communication connection with the client 11 at this time is referred to as the first server.

In step S108, the client 13 sends a first request to the first server 14 based on the public network IP address of the first server 14.

The first request is used for requesting the interactive data corresponding to the first identification.

The first request may be represented in the form of a message, and may be, for example, an HTTP (HyperText Transfer Protocol) request message, an HTML (HyperText Markup Language) request message, an XML (Extensible Markup Language) request message, a json (javascript Object notification) request message, or a custom message.

The following describes the format of the HTTP request message as an example. The HTTP request message consists of a request line, a request header, an empty line and a request packet body.

Illustratively, the first identifier may be located at the request header.

In step S109, the first server 14 responds to the first request after receiving the first request.

Illustratively, the process of responding to the first request includes: detecting whether a business entity object corresponding to the live broadcast room is established or not; if the object is created, the client 13 is associated with the business entity object; if not, a service entity object corresponding to the live broadcast room is created, and the client 13 is associated with the service entity object.

Illustratively, the business entity object may be a message broadcasting room.

Illustratively, the association between the client 13 and the business entity object means that the business entity object stores the network connection information of the client 13. Illustratively, the network connection information includes: at least one of a physical address (MAC address, medium access control address) and a public network IP address.

Illustratively, a business entity object is a component for obtaining interaction data.

In step S110, the first server 14 obtains the interaction data corresponding to the first identifier from the database 12 through the business entity object, and sends a message containing the interaction data to the client 13.

Illustratively, the process of sending interactive data in the live broadcast room by each user watching the live broadcast data comprises the following steps: each user sends the interactive data to the API server through the client 13; the API server stores the interaction data in the database 12.

Illustratively, the communication connection between the first server and the client 13 may be a long connection, so during the live broadcast, the business entity object in the first server may obtain the interaction data from the database 12 and send the interaction data to the client 13 until the live broadcast is finished.

In the related art data processing method shown in fig. 1 described above, there are two technical problems as follows:

the first technical problem is that: a related mechanism needs to obtain interactive information corresponding to a first identifier of a live broadcast room, for example, a main broadcast subscription mechanism needs to obtain data enjoyed by audiences in the live broadcast room for a main broadcast so as to determine whether the main broadcast has subscription value; the related mechanism can directly send a request for acquiring interactive data corresponding to the first identifier of the live broadcast room to the server based on the public network IP address of any server.

The client of the relevant organization does not need to go through the steps from S101 to S107, and the client corresponding to the relevant organization can obtain the public network IP address of each server, and can directly execute the steps from S108 to S110; that is, the client of the relevant organization may directly send the first request to any server, and any server will respond to the first request after receiving the first request.

In the following description, the live broadcast room is taken as the live broadcast room a, and it is assumed that the second group number obtained by the API server based on the first identifier corresponding to the live broadcast room a is the group number 1. Assuming that the client corresponding to the relevant agency sends a first request to the server a included in the group with group number 2, the server a may respond to the first request.

Since the server in the group with the group number of group number 2 does not need to create the service entity object corresponding to the live broadcast room a and does not need to obtain the interactive data corresponding to the first identifier of the live broadcast room a according to steps S101 to S110, the server in the group with the group number of group number 2 needs to additionally maintain the service entity object corresponding to the live broadcast room a and additionally obtain the interactive data corresponding to the first identifier of the live broadcast room a.

And if the server in the group with the group number of group number 2 only receives the first request sent by one client corresponding to the relevant mechanism, that is, the service entity object created by the server in the group with the group number of group number 2 only serves one client, which results in the waste of resources.

The second technical problem is that: the number of public network IP addresses is limited, and a public network IP address is set for each server, so that more public network IP addresses are consumed.

There are various possible application scenarios of the data processing method provided by the embodiment of the present disclosure, and the embodiment of the present disclosure provides, but is not limited to, the following two scenarios.

A first application scenario is shown in fig. 2.

Fig. 2 is an architecture diagram of a first application scenario, which may be applied to the data processing method provided by the embodiment of the present disclosure, as shown in fig. 2, according to an exemplary embodiment. The first application scenario includes: API server 11, database 12, at least one client 13, and at least one server 14.

Fig. 2 shows 2 clients 13 and 2 servers 14, fig. 2 is only an example, and the number of the clients 13 and the servers 14 in practical application may be set according to practical requirements.

In a first application scenario, the configuration file stored in the database 12 includes configuration information corresponding to at least one packet, and the configuration information corresponding to each packet includes a group number of the packet and a public network IP address of at least one server included in the packet.

Any of the clients 13 may communicate with the API server 11 based on a wired network or a wireless network. Any of the clients 13 may communicate with the server 14 based on a wired network or a wireless network. The database 12 is accessible to both the API server 11 and the server 14.

The interactive process of the API server 11, the database 12, the at least one client 13 and the at least one server 14 in the first application scenario includes steps S101 to S108, the following steps a1, a2, A3, a 109, a 110 and a 4.

In a first application scenario, for each client 13, the server 14 corresponding to the first response message received by the client 13 in the "at least one server 14" is the first server 14.

In step a1, the first server 14 obtains the first group number of the group to which the first server belongs from the configuration file pre-stored in the database 12.

In step a2, the first server 14 calculates a second group number based on the first identifier.

In step a3, the first server 14 determines whether the first group number is the same as the second group number, and if so, performs step S109; if not, go to step A4.

In step a4, the response to the first request is denied.

Illustratively, if the first group number is not the same as the second group number, the first server 14 disconnects the communication with the client 11.

The first server 14 has the function of "authenticating packets" since it has access to the first group number as well as the second group number. The function of "identifying the group" is to identify whether the group in which the server obtains the interactive data belongs to the same group. If the two groups are the same, it means that the first server 14 has "right" to obtain the interactive data corresponding to the first identifier. If the two identifiers are not in the same group, it means that the first server 14 does not have the "authority" to acquire the interactive data corresponding to the first identifier. Thereby avoiding the situation that a client corresponding to the relevant organization can send a first request to any server, and any server must respond to the first request even if the server does not belong to the group to which at least one server acquiring the interactive data belongs. That is, the first application scenario solves the first technical problem in the related art shown in fig. 1.

A second application scenario is shown in fig. 3.

Fig. 3 is an architecture diagram illustrating a second application scenario according to an exemplary embodiment, and as shown in fig. 3, the data processing method provided by the embodiment of the present disclosure may be applied to the application scenario. The second application scenario includes: API server 11, database 12, at least one client 13, at least one server 14, and at least one load balancing server 31.

Fig. 3 shows 1 client 13, 1 server 14, and 1 load balancing server 31, and fig. 3 is only an example, and the number of clients 13, servers 14, and load balancing servers 31 in an actual application may be set according to actual requirements.

Any of the clients 13 may communicate with the API server 11 based on a wired network or a wireless network. Any of the clients 13 may communicate with the server 14 based on a wired network or a wireless network.

The database 12 is accessible to the API server 11, the server 14, and the load balancing server 31.

The load balancing server 31 may be one server, a server cluster composed of a plurality of servers, or a cloud computing server center.

In order to solve the second technical problem in the technical solution shown in fig. 1, in the second application scenario, instead of allocating a public network IP address to each server, a private network IP address is allocated to each server, but since the client 13 and the server do not belong to the same local area network, the client 13 cannot access the server based on the private network IP address of the server, and therefore, the second application scenario introduces a load balancing server as an intermediary for transmitting data (including request and interaction data) between the client 13 and the server.

For example, the load balancing server may be a four-tier load balancing server.

Typically, the total number of load balancing servers is less than the total number of servers 14.

In the second application scenario, for example, the configuration file stored in the database 12 includes configuration information corresponding to at least one packet, where the configuration information corresponding to each packet includes a group number of the packet and a virtual IP address of at least one server included in the packet, and the virtual IP address of one server includes a public network IP address of a load balancing server serving as a data forwarding medium for the server and the client and a port number corresponding to the server.

The function of the load balancing server is explained below, and the process of forwarding data by the load balancing server as an intermediary includes steps B1 to B5. The following description takes an example that the client sends the first information, and the first information may be, for example, the first request or the second request mentioned in the embodiments of the present disclosure. The second information fed back by the corresponding server may be information corresponding to the first information mentioned in the embodiment of the present disclosure, for example, if the first information is the first request, the second information is a message including the interactive data; if the first information is the second request, the second information is the first response message.

In step B1, the client 11 sends a first message, where the source address carried by the first message is the public IP address of the client 11, and the destination address is the virtual IP address a of the server.

In step B2, after receiving the first information, the load balancing server obtains the private network IP address a corresponding to the port number included in the virtual IP address a based on the pre-stored correspondence between at least one port number and the private network IP address.

In step B3, the load balancing server replaces the destination address in the first information with a private network IP address a, that is, the source address of the replaced first information is the public network IP address of the client 11, and the destination address is the private network IP address a; and sending the replaced first information to a server.

In step B4, the server receives the replaced first information and returns second information to the load balancing server, where the source address of the second information is the private network IP address a and the destination address is the public network IP address of the client 11.

In step B5, the load balancing server receives the second information, obtains a port number a corresponding to the private network IP address a based on a pre-stored correspondence between at least one port number and the private network IP address, replaces the source address of the second information with a virtual IP address a (including the port number a), and the source address of the replaced second information is the virtual IP address a and the destination address is the public network IP address of the client terminal 11; the replaced second information is sent to the client 13.

In conjunction with the functions of the load balancing server, the embodiments of the present disclosure add the load balancing server, so that the load balancing server acts as an intermediary for transmitting data (including requests and interactive data) between the client 13 and the server 14. Since the number of load balancing servers in each group is smaller than the number of servers, the number of public network IP addresses allocated to the load balancing servers is smaller than the number of public network IP addresses allocated to the servers in the related art shown in fig. 1, thereby saving the public network IP addresses.

The interactive process of the API server 11, the database 12, the at least one client 13, the at least one server 14, and the at least one load balancing server 31 included in the second application scenario is similar to the interactive process of the API server 11, the database 12, the at least one client 13, and the at least one server 14 included in the first implementation environment, except that the data interaction between the client 11 and the server 14 is forwarded by the load balancing server, and a destination address carried by information sent by the client 11 to the server 14 is not a public network IP address of the server but a virtual IP address of the server, and a source address carried by information sent by the load balancing server 14 to the client 11 is not a public network IP address of the server but a virtual IP address of the server.

In the second application scenario, for each client 13, the server 14 corresponding to the first response message received by the client 13 in the "at least one server 14" is the first server 14.

That is, the second application scenario solves the first technical problem and the second technical problem in the technical solution shown in fig. 1 at the same time.

Those skilled in the art should appreciate that the above-described clients and servers are merely exemplary, and that other existing or future clients and servers may be included within the scope of the present disclosure, as applicable, and are hereby incorporated by reference.

The following describes a data processing method provided by the embodiment of the present disclosure with reference to the first application scenario and the second application scenario, and introduces a technical solution provided by the embodiment of the present disclosure with reference to the drawings.

Fig. 4 is a flowchart illustrating a data processing method for any one of the first server in the first application scenario or the second application scenario, according to an exemplary embodiment, where the method includes the following steps S41 to S47.

In step S41, the first server 14 receives the first request sent by the client 13.

The first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting to acquire interactive data between users in the live broadcast room.

In step S42, the first server 14 obtains the first group number of the group to which the first server belongs from the configuration file stored in advance in the database 12.

The configuration file comprises configuration information corresponding to at least one group, and the configuration information corresponding to each group comprises a group number of the group and an IP address of at least one server contained in the group.

For the first application scenario, the IP address of one server is illustratively a public network IP address.

For the second application scenario, the IP address of one server is a virtual IP address, and the virtual IP address includes a public network IP address of the load balancing server and a port number of the server.

For the second application scenario, the IP address of a server includes a virtual IP address and a private IP address.

In step S43, the first server 14 calculates a second group number based on the first identifier, where the second group number is a group number of a group to which at least one second server belongs, and the second server is configured to obtain the interactive data.

Illustratively, the way in which the first server 14 calculates the group number based on the first identifier is the same as the way in which the API server 11 calculates the group number based on the first identifier, so the second group number obtained in step S43 is the group number of the group to which at least one second server belongs.

For example, if the first group number is the same as the second group number, the first server is any one of the at least one second server; if the first group number and the second group number are different, the first server is different from any server of the at least one second server.

In step S44, the first server 14 compares the first group number with the second group number, and performs step S45 if the first group number is different from the second group number, and performs step S46 if the first group number is the same as the second group number.

The first server 14 has the function of "authenticating packets" since it has access to the first group number as well as the second group number. The function of "identifying the group" is to identify whether the preset group where the server is located and the group where the at least one server obtaining the interactive data belongs are the same group. If the packets are the same, it means that the first server 14 has "right" to obtain the interactive data of the live broadcast. If the two groups are not in the same group, it means that the first server 14 does not have the "right" to acquire the interactive data of the live broadcast room.

In step S45, the first server 14 refuses to respond to the first request.

Illustratively, the refusal of the first server 14 to respond to the first request may include: the first server 14 ignores or discards the first request and does not create a business entity object corresponding to the live broadcast based on the first request.

In step S46, the first server 14 responds to the first request.

For example, the process of the first server 14 responding to the first request may refer to the description of step S109, which is not described herein again.

Illustratively, if a business entity object in the first server corresponding to the live broadcast room obtains interactive data corresponding to the first identifier of the live broadcast room, the first server sends the obtained interactive data to the client through the communication connection.

In the data processing method provided by the embodiment of the disclosure, after receiving a first request, a first server acquires a first group number of a group to which the first server belongs from a preset configuration file, wherein the first group number is a group number of a preset group in which the first server is stored in a database; calculating to obtain a second group number based on a first identifier carried by the first request, wherein the second group number is a group number of a group to which at least one second server belongs, the second server is used for acquiring the interactive data, and the first server has a function of identifying the group as the first group number and the second group number can be acquired by the first server; if the first group number is the same as the second group number, the first server belongs to the group with the group number of the second group number, and therefore the first server can respond to the first request. If the first group number is different from the second group number, it is described that the first server does not belong to the group with the group number being the second group number, and therefore, the first server does not respond to the first request, that is, the embodiment of the present disclosure utilizes the "authentication group" function of the first server, so that the server with the group number being the second group number can respond to the first request, and the servers in other groups cannot respond to the first request, thereby avoiding a situation that a client corresponding to a relevant organization can send the first request to any server, and any server can only passively respond to the first request even if not belonging to the group with the group number being the second group number. Namely, the first technical problem in the related art shown in fig. 1 is solved.

Before describing the interaction process among the API server 11, the database 12, the at least one client 13, the at least one server 14, and the at least one load balancing server 31 included in the second application scenario, the load balancing server is introduced.

Fig. 5 is a flowchart illustrating a data processing method applied to a load balancing server, which includes the following steps S51 to S56 in an implementation process according to an exemplary embodiment.

In step S51, the load balancing server 31 receives the first request sent by the client.

The first request carries a first identifier of a live broadcast room displayed by the client. And the destination address in the first request is the virtual IP address of the first server.

In step S52, the load balancing server 31 replaces the virtual IP address of the first server in the destination address of the first request with the target private network IP address of the first server according to the preset correspondence between at least one port number and the private network IP address.

In the embodiment of the disclosure, the private network IP address of the first server is referred to as a target private network IP address.

And the target private network IP address of the first server is a private network IP address corresponding to the port number contained in the virtual IP address of the first server.

In step S53, the load balancing server 31 sends the first request to the first server 14.

The destination address of the first request in step S53 is the destination private network IP address of the first server.

In step S54, the load balancing server 31 receives the first message containing the interactive data fed back by the first server 14.

Wherein, the source address of the first message is the target private network IP address of the first server; the first message is a response message for the first request under the condition that a first group number is the same as a second group number, the first group number is a group number of a group to which the first server belongs, and the second group number is a group number of a group to which the second server for acquiring the interactive data belongs, which is calculated based on the first identifier.

In step S55, the load balancing server 31 replaces the source address in the first packet with the virtual IP address of the first server from the target private network IP address based on the pre-stored correspondence between at least one port number and the private network IP address, so as to obtain a second packet.

In step S56, the load balancing server 31 sends the second message to the client.

In the data processing method applied to the load balancing server provided by the embodiment of the present disclosure, the load balancing server may obtain the interactive data only when the first server detects that the first group number is the same as the second group number, and the load balancing server may not obtain the interactive data when the first server detects that the first group number is different from the second group number. I.e. the server has the function of "authenticating packets".

The disclosed embodiment adds a load balancing server, so that the load balancing server acts as an intermediary for data (including requests and interactive data) transmitted between the client 13 and the server. Since the number of load balancing servers in each group is smaller than the number of servers, the number of public network IP addresses allocated to the load balancing servers in the embodiment of the present disclosure is smaller than the number of public network IP addresses allocated to the servers in the related art shown in fig. 1, thereby saving the public network IP addresses.

The following describes the interaction process between the API server 11, the database 12, the at least one client 13, the at least one server 14, and the at least one load balancing server 31 included in the second application scenario.

Fig. 6 is a signaling diagram illustrating another data processing method applied to a second application scenario according to an exemplary embodiment, and the method includes the following steps S601 to S620 in implementation.

In step S601, the client 13 generates an address acquisition request for acquiring an IP address of the server; the address acquisition request is sent to the API server 11.

Illustratively, the destination address carried by the address obtaining request is a public network IP address of the API server 11, and the source address is a public network IP address of the electronic device where the client 13 is located. The address acquisition request carries the first identifier.

In step S602, the API server 11 obtains a configuration file from the database 12.

For the description of the configuration file, reference may be made to the description of the configuration file in the second application scenario, which is not described herein again.

For example, the expression form of the configuration file can be an array, a table, a structure or a linked list. In order to make the configuration files mentioned in the embodiments of the present disclosure more understandable to those skilled in the art, the following description takes the expression of the configuration files as a table as an example.

Assuming that the total number of packets is 2, the group numbers of the 2 packets are group number 1 and group number 2, respectively, and the packet with the group number of group number 1 includes server a1, server a2, server A3, server a4, load balancing server B1, and load balancing server B2. The group with group number 2 contains server a5, server a6, server a7, and load balancing server B3.

Wherein, the public network IP address of the load balancing server B1 is 10.1.1.1; the public network IP address of the load balancing server B2 is 10.1.1.2; the virtual IP address of server a1 is 10.1.1.1: 8081; the virtual IP address of server a2 is 10.1.1.1: 8082; the virtual IP address of server a3 is 10.1.1.2: 8083; the virtual IP address of server a4 is 10.1.1.2: 8084.

the public network IP address of the load balancing server B3 is 10.1.1.3, and the virtual IP address of the server a5 is 10.1.1.3: 8081; the virtual IP address of server a6 is 10.1.1.3: 8085; the virtual IP address of server a7 is 10.1.1.3: 8082. illustratively, the configuration files are shown in table 1.

TABLE 1 configuration files

As shown in table 1, since the virtual IP address of the server includes the public network IP address of the load balancing server, for example, the configuration file may not need to separately store the public network IP address of the load balancing server, and for example, the configuration file may separately store the public network IP address of the load balancing server, which is not specifically limited in this disclosure.

By way of example, a group may include one or more load balancing servers. In an optional implementation manner, if one group includes a plurality of load balancing servers, different load balancing servers are located in different geographical locations; in an alternative implementation, if a group includes multiple load balancing servers, the geographical locations of the different load balancing servers may be the same.

In step S603, the API server 11 determines a second group number based on the first identifier.

Specifically, refer to the description of step S103, which is not described herein again.

In step S604, the API server 11 transmits the virtual IP address of the destination server included in the packet whose group number is the second group number to the client 13.

In the embodiment of the present disclosure, a packet whose group number is the second group number is referred to as a second packet. The server that the second packet contains is referred to as the target server. The second packet may contain any positive integer number of destination servers, such as 1, 2, 3, 4, …, etc.

Only the target server in the second packet, which has the fastest communication connection with the client 11, i.e., the first server 14 retained by the client in step S613, is shown in fig. 6.

In step S605, the client 13 transmits a second request to each virtual IP address of the destination server.

The second request is for requesting establishment of a communication connection with a target server. For each target server, the source address carried by the second request is the public network IP address of the client 13, and the destination address carried by the second request is the virtual IP address of the target server.

It can be understood that, since the virtual IP address of the target server includes the public network IP address of the corresponding load balancing server and the port number of the target server, the second request sent by the client to the virtual IP address of each target server is sent to the corresponding load balancing server.

If the second packet includes one load balancing server, the second requests respectively sent by the client to the virtual IP addresses of the target servers are received by the load balancing server.

Taking the second group number as group number 2 in table 1 as an example, the group includes one load balancing server B3, and the second requests sent by the client 13 to the server a5, the server a6 and the server a7 are received by the load balancing server B3.

If the second packet includes at least two load balancing servers, then the second requests respectively sent by the client to the virtual IP addresses of the target servers are respectively received by the at least two load balancing servers.

Taking the second group number as the group number 1 in table 1 as an example, the group includes the load balancing server B1 and the load balancing server B2, and the second request sent by the client 13 to the server a1 or the server a2 is received by the load balancing server B1; the second request sent by the client 13 to server A3 or server A4 is received by load balancing server B2.

For any load balancing server included in the second packet, the operation performed for each received second request is the same, and the following steps S606 to S613 are included in the implementation process of the operation performed by any load balancing server for one second request, which is described below by taking as an example the operation performed by any load balancing server for one second request.

In step S606, the load balancing server 31 receives the second request sent by the client 13; and determining the private network IP address corresponding to the destination address in the second request from the preset corresponding relation between at least one port number and the private network IP address.

The private network IP address corresponding to the destination address is the private network IP address corresponding to the port number in the virtual IP address included in the destination address.

In step S607, the load balancing server 31 replaces the destination address in the second request with the private IP address of the target server, and transmits the changed second request to the corresponding target server 14.

In step S608, if the target server 14 responds to the second request, a first response message is generated, where the first response message is used to characterize that the communication connection with the client is successfully established; and the source address of the first response message is the private network IP address of the target server.

The successfully established communication connections are characterized in fig. 6 by a rectangular dashed border.

In step S609, the target server 14 transmits a first response message to the load balancing server 31. The source address in the first response message is the private network IP address of the target server, and the destination address in the first response message is the public network IP address of the client 13.

In step S610, after receiving the first response message, the load balancing server 31 determines, from the preset correspondence between at least one port number and the private network IP address, a port number corresponding to the private network IP address of the destination server included in the source address in the first response message.

In step S611, the load balancing server 31 replaces the source address in the first response message with the virtual IP address of the target server, and obtains a second response message.

The virtual IP address of the target server includes the public network IP address of the load balancing server 31 and the port number corresponding to the private network IP address of the target server determined in step S610.

In step S612, the load balancing server 31 sends a second response message to the client 13.

Each load balancing server performs the above steps S606 to S612 for the received one second request, so that the client 13 can receive a plurality of second response messages.

Illustratively, the target server and the load balancing server are in the same local area network, and therefore, the load balancing server and the target server may interact based on the private network IP address.

In step S613, the client 13 receives the second response messages fed back by the plurality of servers, retains the communication connection with the target server that has the earliest time when the second response messages are received, and disconnects the communication connection with the other target servers.

In the embodiment of the present disclosure, the target server corresponding to the communication connection reserved by the client 13 is referred to as a first server.

The first server shown in fig. 6 is any target server in the second group. In the embodiment of the disclosure, the private network IP address of the first server is called a target private network IP address.

In step S614, the client 13 sends a first request to the first server based on the virtual IP address of the first server.

In step S615, the load balancing server 31 replaces the destination address of the first request with the target private network IP address of the first server according to the preset corresponding relationship between at least one port number and the private network IP address, and sends the changed first request to the first server 14.

And the target private network IP address of the first server is a private network IP address corresponding to the port number contained in the virtual IP address of the first server.

In step S616, the first server 14 receives the first request, and obtains the first group number of the packet to which the public network IP address of the load balancing server 31 belongs from the preset configuration file.

It will be appreciated that since the load balancing server 31 that forwards the first request to the first server belongs to the same group as the first server, the group to which the first server belongs may be determined based on the group to which the load balancing server belongs.

In an alternative implementation, the configuration file related to step S616 includes the private IP address and the virtual IP address of each server. The implementation manner of step S616 may also be: the first server 14 receives the first request, and obtains a first group number of a packet to which the private IP address of the first server belongs from a preset configuration file.

The configuration file is still described by taking the expression form of the configuration file as a table.

Assuming that the total number of packets is 2, the group numbers of the 2 packets are group number 1 and group number 2, respectively, the packet with group number 1 contains server a1, server a2, server A3, server a4, load balancing server B1, and load balancing server B2. The group with group number 2 contains server a5, server a6, server a7, and load balancing server B3.

Wherein, the public network IP address of the load balancing server B1 is 10.1.1.1; the public network IP address of the load balancing server B2 is 10.1.1.2; the virtual IP address of server a1 is 10.1.1.1: 8081 private network IP address 192.0.0.1; the virtual IP address of server a2 is 10.1.1.1: 8082, private network IP address 192.0.0.2; the virtual IP address of server a3 is 10.1.1.2: 8083 private network IP address 192.0.0.3; the virtual IP address of server a4 is 10.1.1.2: 8084 private network IP address 192.0.0.4.

The public network IP address of the load balancing server B3 is 10.1.1.3, and the virtual IP address of the server a5 is 10.1.1.3: 8081 private network IP address 192.0.0.5; the virtual IP address of server a6 is 10.1.1.3: 8085 private network IP address 192.0.0.6; the virtual IP address of server a7 is 10.1.1.3: 8082 the private network IP address is 192.0.0.7. Then, exemplary, the configuration file is shown in table 2.

TABLE 2 configuration files

In step S617, the first server 14 calculates a second group number based on the first identifier.

For the description of step S617, refer to the description of step S43, and are not described herein.

In step S618, the first group number and the second group number are compared, if the first group number and the second group number are the same, step S619 is performed, and if the first group number and the second group number are not the same, step S620 is performed.

In step S619, the first server responds to the first request.

Optionally, the operation of responding to the first request may refer to step S46, which is not described herein again.

In step S620, the response to the first request is denied.

For the description of step S620, refer to step S45, which is not described herein.

Based on the technical solution shown in fig. 6, the load balancing server is added in the embodiment of the present disclosure, so that the load balancing server serves as an intermediary for transmitting data (including request and interactive data) between the client 13 and the server. Since the number of load balancing servers in each group is smaller than the number of servers, the number of public network IP addresses allocated to the load balancing servers in the embodiment of the present disclosure is smaller than the number of public network IP addresses allocated to the servers in the related art shown in fig. 1, thereby saving the public network IP addresses.

In an alternative implementation manner, in the second application scenario, a specific implementation procedure of the load balancing server 31 sending the obtained interaction data to the client is shown in steps C1 to C4.

In step C1, the first server 14 obtains the interactive data corresponding to the first identifier of the live broadcast room, and generates a first message carrying the interactive data.

In an alternative implementation, the business entity object corresponding to the first identifier in the first server 14 obtains the interaction data from the database 12.

In step C2, the first server 14 sends the first message to the load balancing server 31.

The source address of the first packet is the destination private network IP address of the first server 14, and the destination address is the public network IP address of the client 13.

In an optional implementation manner, the business entity object corresponding to the first identifier may store network connection information of the client 13.

Illustratively, after the business entity object obtains the interactive data, the interactive data is sent to the clients corresponding to all the network connection information stored in the business entity object.

In step C3, after the load balancing server 31 receives the first packet, it determines, from the preset corresponding relationship between at least one port number and the private network IP address, a port number corresponding to the target private network IP address of the first server included in the source address of the first packet. And replacing the source address of the first message by the virtual IP address of the first server from the target private network IP address to obtain a second message.

The virtual IP address of the first server includes the public network IP address of the load balancing server 31 and the port number corresponding to the target private network IP address of the first server.

In step C4, the load balancing server 31 sends the second message to the client 13.

It is understood that before the live broadcast of the live broadcast is not finished, the server 14 obtains the interaction data corresponding to the first identifier of the live broadcast, and then transmits the interaction data according to steps C1 to C4.

In the second application scenario, for example, the configuration file stored in the database 12 may be set in the database 12 in advance.

In a second application scenario, the configuration file stored in the database 12 may be set based on the load balancing server, for example.

It is understood that the configuration file stored in the setting database 12 is the configuration information corresponding to each group in the setting configuration file. In an optional embodiment, for each group, the configuration information corresponding to the group may be set based on any load balancing server included in the group, that is, the configuration information corresponding to the corresponding group may be set by the load balancing server included in each group, so as to achieve the purpose of setting the configuration file stored in the database.

In an optional embodiment, for each packet, if the packet includes one load balancing server, the load balancing server may set configuration information corresponding to the packet based on the load balancing server; if the packet includes at least two load balancing servers, each load balancing server can set the virtual IP address in the packet to contain the relevant information of the server of the public network IP address of the load balancing server.

And aiming at each group, setting is respectively carried out through all the load balancing servers contained in the group, so that the aim of setting the configuration file stored in the database is fulfilled.

In an alternative implementation manner, before the technical solution shown in fig. 4, fig. 5, or fig. 6 is executed, the configuration information stored in the database 12 needs to be set first, and for any load balancing server, the process of setting the configuration information of the group to which the load balancing server belongs based on the load balancing server includes the following step D1.

In step D1, at least partial configuration information corresponding to the group to which the load balancing server belongs is obtained.

The at least partial configuration information includes a first group number of a packet to which the load balancing server belongs, and a virtual IP address of a server that uses the load balancing server as a data forwarding medium with a client.

For example, if the group with the group number of the first group number includes one load balancing server, based on that load balancing server may set all configuration information corresponding to the group with the group number of the first group number, where all configuration information refers to information of all servers in the group with the group number of the first group number, taking table 1 as an example for explanation, it is assumed that the group with the group number of group number 2 includes load balancing server B3, server a5, server a6, and server a 7; server a5, server a6, and server a7 use load balancing server B3 as their data forwarding medium with clients, so all servers, i.e., server a5, server a6, and server a7, can be set based on load balancing server B3, with their respective corresponding port numbers. The "at least partial allocation information" in the step D1 is all allocation information corresponding to the group having the first group number.

For example, if a packet with a first group number includes at least two load balancing servers, optionally, each load balancing server may be able to set a port number of a server that serves as a data forwarding medium with the client; the following description will be made by taking table 1 as an example. Load balancing server B1, load balancing server B2, server a1, server a2, server A3 and server a4 belong to one group, but server a1 and server a2 use load balancing server B1 as their data forwarding media with clients, so server a1 can set the port numbers of server a1 and server a2 based on load balancing server B1, but server A3 and server a4 use load balancing server B2 as their data forwarding media with clients, and server A3 and server a4 based on load balancing server B2 can set the port numbers of server A3 and server a 4.

For example, if the group with the group number of the first group number includes at least two load balancing servers, optionally, each load balancing server may set all configuration information corresponding to the group where the load balancing server is located, and still taking table 1 as an example, based on the load balancing server B1, port numbers corresponding to the server a1, the server a2, the server A3, and the server a4 can be set.

Illustratively, the method further includes a step D2 of storing the at least partial configuration information in the database 12.

And performing corresponding setting operation aiming at the load balancing server contained in each group to obtain a configuration file.

In an optional implementation manner, for each load balancing server, a corresponding relationship between at least one port number and a private network IP address needs to be preset, so that the load balancing server can be used as an intermediary between the client 13 and the server. Taking the packet with group number 1 in table 1 as an example, for the load balancing server B1, the load balancing server B1 needs to store the port number of server a1 and the private network IP address of server a1, and the port number of server a2 and the private network IP address of server a 2; the load balancing server B2 needs to store the port number of server A3 and the private network IP address of server A3, and the port number of server a4 and the private network IP address of server a 4.

In an optional implementation manner, for each load balancing server, a corresponding relationship between a port number of the server and a private network IP address of the server may be set on the load balancing server; the virtual IP address of the server may be set on the load balancing server to include the public network IP address of the load balancing server and the port number of the server.

In an alternative implementation, for each group, the server included in the group may be changed, that is, the configuration file stored in the configured database may be changed. The reason why the server included in one packet is changed may be as follows.

The first reason is that: one or more servers in the group fail and the failed server is removed from the group.

The second reason is that: one or more servers are added to the group.

For a third reason, one or more servers in one group are migrated to another group.

In order to realize that the server still has the function of "identifying packets" after the server contained in the packet is changed, and the load balancing server still has the function of serving as an intermediary between the client 13 and the server, the embodiment of the disclosure further provides a method for updating the configuration file stored in the database, and a method for updating the corresponding relationship between at least one port number and the private network IP address stored in the load balancing server. The method provided by the embodiment of the disclosure can be applied to two scenarios.

The first scenario is: a first target server is added in one group. The method can be applied to a load balancing server, and the method comprises the following steps E1 to E4 in the implementation process.

In step E1, if the load balancing server 31 detects a first operation of adding a first target server to its own packet, the corresponding relationship between the private IP address of the first target server and the port number of the first target server is set.

The correspondence between at least one port number stored by the load balancing server and the private network IP address is updated, via step E1.

In step E2, a third request is generated, where the third request is used to instruct the database to add the virtual IP address of the first target server to the configuration information of the packet to which the load balancing server 31 belongs.

In step E3, the third request is sent to the database 12.

Accordingly, in step E4, after the database 12 receives the third request, the virtual IP address of the first target server is added to the configuration information corresponding to the packet to which the load balancing server 31 belongs.

Assume that the configuration file is shown in table 1. Assuming that the group number corresponding to the group to which the load balancing server 31 belongs is group number 1, assuming that the load balancing server 31 is load balancing server B1, the first target server is server a5, and the port number of server a5 is 8085, then the updated configuration file stored in the database is as shown in table 3.

TABLE 3 configuration files

The second scenario is: the second destination server included in a packet is deleted. There are various implementations in the second scenario, and the embodiments of the present disclosure provide, but are not limited to, the following two.

The first implementation manner may be applied to a load balancing server, and the method includes the following steps F1 to F3 in implementation.

In step F1, if the load balancing server 31 detects a second operation of deleting a second target server included in the packet to which the load balancing server belongs, a fourth request is generated, where the fourth request is used to instruct the database to delete the virtual IP address of the second target server in the configuration information of the packet to which the load balancing server 31 belongs.

In step F2, the fourth request is sent to the database.

Correspondingly, in step F3, after the database receives the fourth request, the virtual IP address of the second target server in the configuration information corresponding to the packet to which the load balancing server 31 belongs is deleted.

Assume that the configuration file is shown in table 1. Assuming that the group number corresponding to the group to which the load balancing server 31 belongs is group number 1, assuming that the load balancing server is load balancing server B1, and the second target server is server a2, the updated configuration file stored in the database is as shown in table 4.

Table 4 configuration file

In the first implementation manner, if a fourth request for deleting the second target server included in the packet to which the load balancing server 31 belongs is detected, the virtual IP address of the second target server stored in the database 12 is immediately deleted.

In an optional implementation manner, if the load balancing server detects the second operation, the corresponding relationship between the port number of the second target server and the private network IP address of the second target server, which is stored by the load balancing server, is deleted.

In an optional embodiment, if the load balancing server detects the second operation, the corresponding relationship between the port number of the second target server and the private network IP address of the second target server, which is stored by the load balancing server, may not be deleted. Because the configuration information corresponding to the packet to which the load balancing server belongs stored in the database does not include the virtual IP address of the second target server, if the API server obtains the configuration file from the database again, the API server does not obtain the virtual IP address of the second target server, that is, the client does not receive the virtual IP address of the second target server any more, that is, no new client sends any request to the virtual IP address of the second target server. That is, the correspondence between the port number of the second target server and the private network IP address of the second target server, which is stored in the load balancing server, is useless, and the execution of the whole technical scheme is not affected if the port number is deleted or not deleted.

If the second target server and one or more clients have already established communication connection before deleting the virtual IP address of the second target server stored in the database, but the second target server does not receive the first request, the second target server does not receive the first request after deleting the virtual IP address of the second target server stored in the database, and the second target server determines that the first group number is different from the second group number because the configuration information corresponding to the packet to which the load balancing server belongs stored in the database does not include the virtual IP address of the second target server, and therefore, the client does not respond to the first request, so that the client needs to perform the steps shown in fig. 6 again. To avoid this, a second implementation is provided.

The second implementation may be applied to a load balancing server, and the method includes the following steps G1 to G3 in implementation.

In step G1, if the second operation of deleting the second target server included in the group to which the load balancing server 31 belongs is detected, a fifth request is generated; the fifth request is used for instructing the database to switch the second target server from a first state to a second state, the first state is that the second target server is not in a state to be deleted, and the second state is that the second target server is in a state to be deleted.

The configuration information corresponding to the packet to which the load balancing server 31 belongs further includes a state corresponding to at least one server, and the state corresponding to one server is whether the server is in a state to be deleted.

Illustratively, the first state and the second state may be represented by different characters, for example, the first state is represented by 0 and the second state is represented by 1.

In an alternative implementation manner, although the fifth request is detected, the fifth request is not a request for deleting the second target server, and in an actual application, the second target server is still located in the group to which the load balancing server 31 belongs, that is, the second target server does not remove the group to which the load balancing server belongs, that is, the second target server is in a state to be deleted.

In step G2, the fifth request is sent to the database.

For example, assuming that the database 12 may have sent the virtual IP address of the second target server to client a1, client a2, and client A3 based on the API server before the state of the second target server switches from the first state to the second state, client a1, client a2, and client A3 may establish a communication connection with the second target server.

After the state of the second target server is switched to the second state, if the client a4 accesses the database 12 based on the API server, the database 12 does not transmit the virtual IP address of the server in the second state (for example, the second target server) to the client a4, and therefore, the client a4 cannot establish a communication connection with the second target server. A client like client a4 is referred to in the disclosed embodiments as a "new" client.

That is, in the embodiment of the present disclosure, by setting the state of the server in the configuration file stored in the database, after the server is in the second state, no "new" client establishes a communication connection with the server, and the server only keeps the communication connection established with one or more clients when the server is in the first state.

In step G3, the fourth request is generated a first preset time period after the fifth request is generated.

For example, the first preset duration may be a maximum value of the predicted live broadcast durations in the live broadcast rooms corresponding to all the service entity objects that have been created in the second target server, that is, the fifth request is generated only after the live broadcasts in the live broadcast rooms corresponding to all the service entity objects that have been created in the second target server are all completed.

For example, the first preset time period may be any time such as 3 hours, 1 day, 2 days, 3 days, and the like, which is not limited in this respect by the embodiment of the present disclosure.

For example, before sending the fourth request to the database, the client 13 may still obtain the interaction data corresponding to the first identifier of the live broadcast displayed by the client 13 based on the second target server. That is, before the live broadcast of the live broadcast room displayed by the client 13 is finished, the second target server is still in the group to which the load balancing server belongs, so that the situation that the client 13 executes the steps shown in fig. 6 again is avoided.

For example, in a first preset time after the fifth request is generated, live broadcasts in live broadcasts corresponding to all service entity objects created on the second target server have all been ended, so that the hardware device, which is the second target server, may remove the group to which the load balancing server belongs.

In an optional implementation manner, if the load balancing server detects the fourth request, the corresponding relationship between the port number of the second target server and the private network IP address of the second target server, which is stored by the load balancing server, is deleted.

In an optional embodiment, after the load balancing server detects the fourth request, the corresponding relationship between the port number of the second target server and the private network IP address of the second target server, which is stored by the load balancing server, may not be deleted.

The above-mentioned embodiment refers to that "the database does not send the virtual IP address of the server in the second state to the client", which may be applied to various scenarios, and the following description will take the second target server as an example.

In the embodiment of the present disclosure, the packet corresponding to the first group number is a first packet.

In a first scenario, before the API server obtains the configuration file, the state of the second target server in the configuration information corresponding to the first packet stored in the database has been switched to the second state.

Fig. 7 is a signaling diagram illustrating a method for updating configuration information corresponding to a packet according to an exemplary embodiment, where the method includes steps S701 to S708.

In the method shown in fig. 7, the configuration file stored in the database 12 includes configuration information corresponding to at least one group, and the configuration information corresponding to each group further includes a state corresponding to at least one server. And the state corresponding to one server is whether the server is in a state to be deleted or not.

In step S701, if the load balancing server 31 detects a second operation of deleting the second target server included in the packet in which it is located, a fifth request is generated.

The fifth request is used for instructing the database to switch the second target server from a first state to a second state, the first state is that the second target server is not in a state to be deleted, and the second state is that the second target server is in a state to be deleted.

In step S702, the load balancing server 31 sends the fifth request to the database 12.

In step S703, after receiving the fifth request, the database 12 sets the state of the second target server in the configuration information corresponding to the group in which the load balancing server 31 is located to the second state.

Assume that the configuration file is shown in table 1. Assuming that the group number corresponding to the first group is group number 1, the load balancing server is load balancing server B1, and the second target server is server a2, the updated configuration file stored in the database is shown in table 5.

TABLE 5 configuration files

In step S704, if the API server 11 receives the address obtaining request sent by the client 13, it sends a seventh request for obtaining the configuration file to the database 12.

In step S705, the database 12 receives the seventh request, and sends the virtual IP address of the server in the first state included in the configuration file to the API server.

Since the API server does not receive the virtual IP address of the server in the second state (e.g., the second target server), the virtual IP address of the server in the second state is not sent to the client 13, so that the client 13 cannot perform any data interaction with the server in the second state.

It will be appreciated that since the virtual IP address of the second target server is still included in the configuration file stored by the database 12, the first group number may still be obtained from the configuration file stored by the database after the second target server receives the first request.

In an alternative implementation, the implementation of step S705 may include: the database sends all contents contained in the configuration file to an API server; the API server transmits the virtual IP address of the server in the first state included in the packet in which the load balancing server 31 is located to the client.

In step S706, a fourth request is generated for a first preset duration after the fifth request is generated.

For the description of the first preset duration, refer to the description of the step G3 for the first preset duration, which is not described herein again.

In step S707, the fourth request is sent to the database 12.

In step S708, after receiving the fourth request, the database 12 deletes the virtual IP address of the second target server in the configuration information corresponding to the packet where the load balancing server 31 is located.

In an optional implementation manner, after the load balancing server generates and obtains the fourth request, the load balancing server deletes the correspondence between the port number of the second target server and the private network IP address of the second target server, which is stored in the load balancing server.

In the second scenario, in this scenario, the API server already obtains the configuration file including the virtual IP address of the second target server, but before the API server sends the configuration information corresponding to the packet in which the load balancing server 31 is located to the client 13, the API server already updates the configuration information corresponding to the packet in which the load balancing server 31 is located, which is stored by the API server, based on the configuration information corresponding to the packet in which the load balancing server 31 is located, that is, before the API server sends the configuration information corresponding to the packet in which the load balancing server 31 is located to the client 13, the state of the second target server in the configuration file stored by the API server is the second state.

For example, in the second scenario, the database may send the virtual IP address of the server in the first state in the configuration file to the API server, or the database may have a function of sending all the contents in the configuration file (regardless of whether the state of the server is the first state or the second state) to the API server.

Fig. 8 is a signaling diagram illustrating another method for updating configuration information corresponding to a packet according to an exemplary embodiment, where a packet with a second group number is assumed to be a second packet, and the method includes steps S601 to S603, steps S701 to S703, step S81, step S82, and steps S706 to S708.

For example, step S603 is not sequentially executed from step S701 to step S703, for example, step S603 may be executed before step S701, or executed when step S701, step S702, or step S703 is executed.

In step S81, the API server 11 acquires, from the database 12, configuration information corresponding to a group whose group number is the second group number every second preset duration, and updates configuration information corresponding to a group whose group number is the second group number stored in the API server 11 based on the configuration information acquired from the database.

For example, the second preset time period may be determined based on actual conditions, for example, 1 second, 2 seconds, and the like.

For example, the API server 11 may update the state of the second target server in the configuration information corresponding to the second packet stored in the API server 11 from the first state to the second state.

In step S82, if the API server 11 does not transmit the configuration information corresponding to the packet whose group number is the second group number to the client 13, the virtual IP address of the server in the first state in the configuration information corresponding to the packet whose group number is the second group number is transmitted to the client 13.

It is understood that the client 13 cannot perform any data interaction with the second target server because the client 13 cannot obtain the virtual IP address of the second target server in the second state.

In an alternative implementation, if the API server 11 has sent the configuration information corresponding to the group with the group number being the second group number to the client 13 before executing step S81, the client 13 may establish a communication connection with the second target server and may send the first request to the second target server.

It can be understood that, since the configuration information corresponding to the packet with the group number of the second group number in the configuration file stored in the database 12 still includes the virtual IP address of the second target server, after the second target server receives the first request, the first group number corresponding to the packet to which the second target server belongs can still be obtained from the configuration file stored in the database.

In the third scenario, the client has already obtained the configuration information including the virtual IP address of the second destination server corresponding to the packet with the group number of the second group number.

For example, in the third scenario, the database may have a function of transmitting only the contents of the configuration file except for all the contents of the server in the second state to the API server, or the database may have a function of transmitting all the contents of the configuration file (regardless of whether the state of the server is the first state or the second state) to the API server.

For example, in the third scenario, the API server may have the functions of step S81 and step S82, or the API server does not have the function of step S81.

Fig. 9 is a flowchart illustrating still another data processing method according to an exemplary embodiment, the method including steps S601 to S604, steps S701 to S703, steps S605 to S617, and steps S91 to S95 in implementation.

In steps S601 to S618, the client 11 reserves the first server of the communication connection as the second target server.

In step S701 to step S703, there is no sequential execution order with step S605 to step S617. Steps S601 to S618, S701 to S703 are not shown in fig. 9.

In step S91, if the first group number is the same as the second group number, the second target server 14 determines whether itself has created the service entity object corresponding to the live broadcast, and if so, performs step S92, otherwise, performs step S93.

In step S92, the second target server 14 responds to the first request.

In step S93, the second target server 14 obtains the status of the second target server from the configuration file stored in the database 12, and if the status of the second target server is the first status, step S94 is performed, and if the status of the second target server is the second status, step S95 is performed.

In step S94, the second target server 14 creates a business entity object corresponding to the live broadcast room, and responds to the first request.

In step S95, the second target server 14 refuses to respond to the first request.

In summary, in the technical solution provided in the embodiment of the present disclosure, if the virtual IP address of the server in the second state (for example, the second target server) is sent to the client 11, the second target server is prevented from creating a new service entity object by the above technical solution, so that after the second target server is in the second state, only the created service entity object is maintained.

The following describes an interaction process between the API server 11, the database 12, the at least one client 13, and the at least one server 14 included in the first application scenario. Wherein the database 12 is used for storing configuration files.

In the technical solution shown in fig. 6 related to the second application scenario, two implementation manners of "obtaining the first group number of the packet to which the first server belongs from the preset configuration file" are described, and one implementation manner is to obtain the first group number of the packet to which the public network IP address of the load balancing server belongs from the preset configuration file; one is to acquire a first group number of a packet to which a private network IP address of the first server belongs from a preset configuration file.

In addition to the above two ways, in a first application scenario, the present disclosure further provides a following way, "obtaining, from a preset configuration file, a first group number of a group to which the first server belongs" includes: and acquiring the first group number of the group to which the public network IP address of the first server belongs from a preset configuration file.

The configuration file is still described by taking the expression form of the configuration file as a table.

Assuming that the total number of packets is 2, the group numbers of 2 packets are group number 1 and group number 2, respectively, a packet with group number 1 contains server a1, server a2, server A3, and server a 4. The group with group number 2 contains server a5, server a6, and server a 7.

Wherein, the public network IP address of the server A1 is 10.1.1.1; the public network IP address of the server A2 is 10.1.1.2; the public network IP address of the server A3 is 10.1.1.3; the public network IP address of server a4 is 10.1.1.4. The public network IP address of the server A5 is 10.1.1.5; the IP address of the server A6 public network is 10.1.1.6; the public network IP address of server a7 is 10.1.1.7. Then, exemplary, the configuration file is shown in table 6.

TABLE 6 configuration files

In an alternative implementation manner, in the first application scenario, the specific implementation process of the first server executing step S110 includes steps H1 to H2.

In step H1, the first server 14 obtains the interactive data corresponding to the first identifier of the live broadcast room, and generates a first message carrying the interactive data.

The source address carried by the first message is the public network IP address of the server, and the destination address is the public network IP address of the client 13.

In step H2, the first server 14 sends the first message to the client 13.

In a first application scenario, the configuration file stored in the database 12 may be set in the database 12 by a human, for example.

In an alternative implementation, for each group, the server included in the group may be changed, that is, the configuration file stored in the database may be changed.

In a first application scenario, in order that a server included in a group still has a function of "identifying the group" after the server is changed, the embodiment of the present disclosure further provides a method for updating a configuration file stored in a database, and the method provided by the embodiment of the present disclosure corresponds to two scenarios. The following description will be given taking a packet in which a server change occurs as a first packet as an example, and the other packets are similar.

The first scenario is: a first target server is added in the first group. The method comprises the following steps J1 to J2 in the implementation process.

In step J1, the database 12 detects a third request instructing the database to add the public network IP address of the first target server in the configuration information of the first packet.

The third request in the first application scenario corresponds to the third request in the second application scenario, and the difference is that the third request in the first application scenario (without load balancing server) corresponds to a public network IP address, the third request is not an option sent by the load balancing server to the database 12, the third request is generated by the database 12 itself, and the third request in the second application scenario (with load balancing server) corresponds to a private network IP address.

For example, the public network IP address of the first target server may be artificially added to the configuration information corresponding to the first packet stored in the database 12.

In step J2, the database 12 adds the public network IP address of the first destination server to the configuration information corresponding to the first packet.

The second scenario is: the second target server is deleted in the first group. There are various implementations of the above method, and the embodiments of the present disclosure provide, but are not limited to, the following two.

A first implementation can be applied to a database, and the method includes the following step K1 in implementation.

In step K1, if the database 12 detects a fourth request, the fourth request is used to instruct the database to delete the public network IP address of the second target server in the configuration information of the first packet, and delete the public network IP address of the second target server in the configuration information corresponding to the first packet.

The fourth request in the first application scenario corresponds to the fourth request in the second application scenario, and the difference is that the fourth request in the first application scenario (without load balancing server) corresponds to a public network IP address, the fourth request is not sent to the database 12 by the load balancing server, optionally, the fourth request is generated by the database 12 itself, and the fourth request in the second application scenario (with the load balancing server) corresponds to a private network IP address.

Illustratively, the public network IP address of the second target server in the configuration information corresponding to the first packet stored in the database 12 is deleted manually.

The second implementation may be applied to a database, and the method includes the following steps L1 to L2 in implementation.

In step L1, if the database 12 detects the fifth request, it switches the second target server from the first state to the second state, and prohibits sending the public network IP address of the second target server in the second state to the client.

The functions of the fifth request in the first application scenario and the fifth request in the second application scenario are the same, and they may be referred to each other, and are not described herein again.

However, the first application scenario does not include a load balancing server, so the fifth request is not sent to the database 12 by the load balancing server, and may alternatively be generated by the database itself.

In step L2, after the first preset duration after the fifth request is detected, the database 12 deletes the public network IP address of the second target server in the configuration information corresponding to the first packet.

For the description of the steps L1 to L2, reference may be made to the description of the steps G1 to G3, which is not repeated here.

In a first application scenario, the above-mentioned "the database prohibits sending the public network IP address of the second target server in the second state to the client" corresponds to multiple scenarios, and the embodiments of the present application provide, but are not limited to, the following three scenarios.

In a first scenario, before the API server obtains the configuration file, the state of the second target server in the configuration information corresponding to the first packet stored in the database has been switched to the second state. The method for updating the configuration information corresponding to the first packet includes the following steps M1 to M4.

In step M1, if the database 12 detects the fifth request, the status of the second target server in the configuration information corresponding to the first group is set to the second status.

In step M2, if the API server 11 receives the address obtaining request sent by the client 13, it sends a seventh request for obtaining the configuration file to the database 12.

In step M3, the database 12 sends all the contents contained in the configuration file except the public network IP address of the server in the second state to the API server.

For the description of step M3, refer to the description of step S705, which is not described herein.

In step M4, after detecting the fifth request for a first preset duration, the database 12 deletes the public network IP address of the second target server in the configuration information corresponding to the first packet.

For the related description of step M1 to step M4, refer to the related description of step S701 to step S708, which is not described herein again.

A second scenario, in this scenario, the API server has already obtained a configuration file containing a public network IP address of the second target server, but before the API server sends the configuration information corresponding to the first packet to the client 13, the API server has already updated the configuration information corresponding to the first packet stored in the API server itself based on the configuration information corresponding to the first packet stored in the database, that is, before the API server sends the configuration information corresponding to the first packet to the client 13, the status of the second target server in the configuration file stored in the API server is the second status.

For example, in the second scenario, the database may have a function of sending all contents in the configuration file to the API server except for the public network IP address of the server in the second state, or the database may have a function of sending all contents in the configuration file to the API server (regardless of whether the state of the server is the first state or the second state).

In an alternative implementation manner, the method for updating the configuration information corresponding to the first packet includes the following steps N1 to N2.

In step N1, the API server 11 updates, every second preset duration, the configuration information corresponding to the first group stored in the API server 11 based on the configuration information corresponding to the first group with the first group number acquired from the database 12.

In step N2, if the API server 11 does not send the configuration information corresponding to the first packet to the client 13, the public network IP address of the server in the first state in the first packet is sent to the client 13.

It can be understood that the client 13 cannot perform any data interaction with the second target server because the client 13 cannot obtain the public network IP address of the second target server in the second state.

In a third scenario, in this scenario, the client has already obtained configuration information corresponding to the first packet and including the public network IP address of the second target server.

For example, in a third scenario, the database may have a function of sending the server in the first state in the configuration file to the API server outside the public network IP address, or the database may have a function of sending all the contents in the configuration file (regardless of whether the state of the server is the first state or the second state) to the API server.

For example, in the third scenario, the API server may have the functions based on step N1 and step N2, or the API server does not have the functions of step N1 and step N2.

In an alternative implementation, it is assumed that the client 11 retains the first server of the communication connection as the second target server. The data processing method includes, in implementation, steps S101 to S104, step M1, steps S105 to S108, steps S42 to S43, and steps S91 to S95.

For details, reference may be made to the description of the corresponding steps, which is not described herein again.

The method is described in detail in the embodiments disclosed in the present application, and the method of the present application can be implemented by using various types of apparatuses, so that various apparatuses are also disclosed in the present application, and specific embodiments are given below for detailed description.

Fig. 10 is a block diagram illustrating a data processing apparatus applied to a first server according to an exemplary embodiment. Referring to fig. 10, the apparatus includes a first receiving module 1001, a first obtaining module 1002, a calculating module 1003, a first processing module 1004, and a second processing module 1005.

A first receiving module 1001 configured to receive a first request sent by a client; the first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting interactive data corresponding to the first identifier;

a first obtaining module 1002, configured to obtain, from a preset configuration file, a first group number of a group to which the first server belongs; the configuration file comprises configuration information corresponding to at least one packet, wherein the configuration information corresponding to each packet comprises a group number of the packet and an Internet Protocol (IP) address of at least one server contained in the packet;

a calculating module 1003, configured to calculate a second group number based on the first identifier obtained by the first receiving module, where the second group number is a group number of a group to which at least one second server belongs, and the second server is used to obtain the interactive data;

a first processing module 1004 configured to reject to respond to the first request if the first group number obtained by the first obtaining module is different from the second group number calculated by the calculating module;

a second processing module 1005 configured to respond to the first request if the first group number obtained by the first obtaining module is the same as the second group number calculated by the calculating module.

In an optional implementation manner, the IP address of the server is a virtual IP address, where the virtual IP address includes a public network IP address of a load balancing server as a data forwarding medium between the server and a client and a port number corresponding to the server, and the first receiving module is specifically configured to:

a first receiving unit configured to receive the first request from the client forwarded by a load balancing server; the destination address in the first request is a private network IP address of the first server, and the destination address in the first request is replaced by the load balancing server from the virtual IP address of the first server to the private network IP address;

the first acquisition module is specifically configured to: a first obtaining unit, configured to obtain, from the preset configuration file, the first group number of the packet to which the public network IP address of the load balancing server belongs.

In an optional implementation, the data processing apparatus further comprises: a second receiving module, configured to receive a second request from the client, where the second request is forwarded by the load balancing server, and a destination address carried in the second request is the private network IP address; the destination address in the second request is replaced by the load balancing server from the virtual IP address of the first server to the private IP address; the second request is for establishing a communication connection with the first server;

a first generating module configured to generate a first response message in response to the second request received by the second receiving module, where the first response message is used to indicate that the communication connection with the client is successfully established; the source address of the first response message is the private network IP address;

a first sending module configured to send the first response message generated by the first generating module to the load balancing server, so that the load balancing server sends a second response message to the client, where the second response message is the response message after the load balancing server replaces the source address of the first response message with the virtual IP address of the first server from the private IP address.

In an optional implementation, the configuration file further includes a total number of the packets; the computing module is specifically configured to:

a second obtaining unit configured to obtain the total number from the preset configuration file;

a calculating unit configured to calculate a second group number based on the first identifier and the total number obtained by the second obtaining unit.

In an optional implementation manner, the IP address of the server is a public network IP address, and the first obtaining module is specifically configured to:

a third obtaining unit, configured to obtain, from the preset configuration file, the first group number of the packet to which the public network IP address of the first server belongs.

In an optional implementation manner, the configuration information corresponding to each of the groups further includes a state corresponding to each server, where the state corresponding to one server is whether the server is in a state to be deleted, and the second processing module is specifically configured to:

a first response unit, configured to respond to the first request if the first group number obtained by the first obtaining module is the same as the second group number calculated by the calculating module, and the first server has already created a service entity object corresponding to the live broadcast room;

a fourth obtaining unit, configured to obtain, if the first group number obtained by the first obtaining module is the same as the second group number calculated by the calculating module, and the first server does not create a service entity object corresponding to the live broadcast room, a state of the first server from the database;

a second responding unit, configured to respond to the first request if the state of the first server obtained by the fourth obtaining unit is a first state, where the first state is that the first server is not in a state to be deleted.

In an optional implementation, the data processing apparatus further comprises:

a third processing module, configured to reject to respond to the first request if the state of the first server obtained by the fourth obtaining unit is a second state, where the second state is a state in which the first server is to be deleted.

With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Fig. 11 is a block diagram illustrating a data processing apparatus applied to a load balancing server according to an example embodiment. Referring to fig. 11, the apparatus includes a third receiving module 1101, a first changing module 1102, a second transmitting module 1103, a fourth receiving module 1104, a second changing module 1105, and a third transmitting module 1106.

A third receiving module 1101 configured to receive a first request sent by a client; the first request carries a first identifier of a live broadcast room displayed by the client, and the first request is used for requesting to obtain interactive data corresponding to the first identifier; the destination address of the first request is a virtual Internet Protocol (IP) address of the first server; the virtual IP address comprises a public network IP address of the load balancing server and a port number corresponding to the first server;

a first changing module 1102 configured to replace the virtual IP address in the destination address of the first request with a target private network IP address corresponding to a port number included in the virtual IP address according to a preset correspondence between at least one port number and a private network IP address;

a second sending module 1103 configured to send the first request having a destination address of the target private network IP address to the first server;

a fourth receiving module 1104, configured to receive a first packet containing the interaction data fed back by the first server; the source address of the first message is the IP address of the target private network; the first message is a response message for the first request under the condition that a first group number is the same as a second group number, the first group number is a group number of a group to which the first server belongs, the second group number is a group number of a group to which at least one second server belongs calculated based on the first identifier, and the second server is used for acquiring the interactive data;

a second changing module 1105, configured to replace the source address of the first packet received by the fourth receiving module with the virtual IP address from the target private network IP address, so as to obtain a second packet;

a third sending module 1106, configured to send the second packet obtained by the second changing module to the client.

In an optional implementation, the data processing apparatus further comprises: a second obtaining module, configured to obtain at least partial configuration information corresponding to a packet to which the load balancing server belongs, where the at least partial configuration information includes the first group number and a virtual IP address of a server that uses the load balancing server as a data forwarding medium with a client;

a storage module configured to store the at least partial configuration information to the database;

a first setting module configured to set the load balancing server as a private network IP address corresponding to a virtual IP address of a server of a data forwarding medium of a client.

In an optional implementation, the data processing apparatus further comprises: a second setting module configured to set a correspondence between a private network IP address of a first target server and a port number of the first target server if a first operation of adding the first target server to a packet to which the load balancing server belongs is detected;

a second generation module configured to generate a third request, where the third request is used to instruct the database to add the virtual IP address of the first target server in the configuration information of the group to which the load balancing server belongs;

a third sending module configured to send the third request to the database.

In an optional implementation, the data processing apparatus further comprises: a third generating module, configured to generate a fourth request if a second operation of deleting a second target server included in a packet to which the load balancing server belongs is detected, where the fourth request is used to instruct the database to delete a virtual IP address of the second target server in configuration information of the packet to which the load balancing server belongs;

a fourth sending module configured to send the fourth request generated by the third generating module to the database.

In an optional implementation manner, the configuration information corresponding to the group to which the load balancing server belongs further includes a state corresponding to at least one server, and the state corresponding to one server is whether the server is in a state to be deleted; the third generation module is specifically configured to:

a first generating unit, configured to generate a fifth request if the second operation of deleting a second target server included in the group to which the load balancing server belongs is detected; the fifth request is used for instructing the database to switch the second target server from a first state to a second state, the first state is that the second target server is not in a state to be deleted, and the second state is that the second target server is in a state to be deleted;

a transmitting unit configured to transmit the fifth request generated by the first generating unit to the database;

a second generating unit configured to generate the fourth request a first preset time period after the fifth request is generated.

With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Fig. 12 is a block diagram illustrating a method for the first server 14 according to an example embodiment.

As shown in fig. 12, the first server 14 includes, but is not limited to: a first processor 1201, a first memory 1202, a network interface 1203, an I/O controller 1204, and a communication bus 1205.

It should be noted that, as those skilled in the art will appreciate, the structure of the first server shown in fig. 12 does not constitute a limitation to the server, and the first server may include more or less components than those shown in fig. 12, or may combine some components, or may have different component arrangements.

The following describes the components of the first server 14 in detail with reference to fig. 12:

the first processor 1201 is a control center of the first server, connects various parts of the entire first server using various interfaces and lines, and performs various functions of the first server and processes data by running or executing software programs and/or modules stored in the first memory 1202 and calling data stored in the memory 12502, thereby integrally monitoring the first server. The first processor 1201 may include one or more processing units; optionally, the first processor 1201 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, an application program, and the like, and the modem processor mainly processes wireless communication. It is to be understood that the above-described modem processor may not be integrated into the first processor 1201.

The first processor 1201 may be a Central Processing Unit (CPU), or an application Specific Integrated circuit (asic), or one or more Integrated circuits configured to implement embodiments of the present invention, etc.;

the first storage 1202 may include Memory, such as a Random-Access Memory (RAM) 12021 and a Read-Only Memory (ROM) 12022, and may also include a mass storage device 12023, such as at least 1 disk storage. Of course, the server may also include hardware needed for other services.

The first memory 1202 is configured to store the executable instructions of the first processor 1201. The first processor 1201 is configured to perform any of the steps of the embodiments of the data processing method applied to the first server.

A wired or wireless network connection 1203 is configured to connect the first server 14 to a network.

The first processor 1201, the first memory 1202, the network interface 1203, and the I/O controller 1204 may be connected to each other by a communication bus 1205, which may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc.

In an exemplary embodiment, the first server 14 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described electronic resource transmission method.

In an exemplary embodiment, there is also provided a storage medium comprising instructions, such as the first memory 1202 comprising instructions, executable by the first processor 1201 of the first server 14 to perform the above method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, a computer program product is also provided, which is directly loadable into an internal memory of a computer, such as the first memory 1202 described above, and contains software code, and which, when loaded and executed by a computer, is able to carry out any of the data processing methods described above.

Fig. 13 is a block diagram illustrating a method for a load balancing server 31 according to an example embodiment.

As shown in fig. 13, the load balancing server 31 includes but is not limited to: a second processor 1301, a second memory 1302, a network interface 1303, an I/O controller 1304, and a communication bus 1305.

It should be noted that, as those skilled in the art can understand, the structure of the load balancing server 31 shown in fig. 13 does not constitute a limitation to the server, and the load balancing server 31 may include more or less components than those shown in fig. 13, or combine some components, or arrange different components.

The following describes each component of the load balancing server 31 in detail with reference to fig. 13:

the second processor 1301 is a control center of the load balancing server 31, connects various parts of the entire first server using various interfaces and lines, and performs various functions and processes of the load balancing server 31 by running or executing software programs and/or modules stored in the second memory 1302 and calling data stored in the memory 13502, thereby performing overall monitoring of the load balancing server 31. The second processor 1301 may include one or more processing units; optionally, the second processor 1301 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application program, and the like, and the modem processor mainly processes wireless communication. It is to be appreciated that the modem processor described above may not be integrated into the second processor 1301.

The second processor 1301 may be a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present invention, or the like;

the secondary storage 1302 may include Memory, such as a Random-Access Memory (RAM) 13021 and a Read-Only Memory (ROM) 13022, and may also include a mass storage device 13023, such as at least 1 disk storage. Of course, the server may also include hardware needed for other services.

The second memory 1302 is configured to store the executable instructions of the second processor 1301. The second processor 1301 is configured to execute any one of the steps in the data processing method embodiment applied to the load balancing server.

A wired or wireless network interface 1303 is configured to connect the load balancing server 31 to the network.

The second processor 1301, the second memory 1302, the network interface 1303 and the I/O controller 1304 may be connected to each other via a communication bus 1305, which may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc.

In an exemplary embodiment, the load balancing server 31 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described electronic resource transmission method.

In an exemplary embodiment, a storage medium comprising instructions, such as the second memory 1302 comprising instructions, executable by the second processor 1301 of the load balancing service 31 to perform the method described above is also provided. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, a computer program product is also provided, which is directly loadable into an internal memory of a computer, such as the second memory 1302 described above, and contains software code, and which, when loaded and executed by a computer, is able to carry out any of the data processing methods described above.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is 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 present disclosure is limited only by the appended claims.