Request processing method, device and equipment for realizing gatekeeper group load balancing

By determining the main gatekeeper and the backup gatekeeper based on the available resources of the gatekeeper group in the video conferencing system, and broadcasting location requests to other gatekeeper groups if necessary, the insufficient load balancing of the gatekeeper group in traditional technology is solved. The problem has improved the fault tolerance and resource utilization of video conferencing systems.

CN118900255APending Publication Date: 2024-11-05BEIJING RONGXUN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411013367.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-26
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

In traditional technology, the gatekeeper groups of video conferencing systems cannot automatically load balancing, resulting in low fault tolerance and low resource utilization in communication systems under high concurrency.

Method used

When receiving the registration request from the conference terminal, find the target gatekeeper group and calculate the current available resources of each gatekeeper, determine the main gatekeeper and the backup gatekeeper, and broadcast the location request to other gatekeeper groups when receiving the call request. , handle call requests for load balancing.

Benefits of technology

It improves the flexibility of the video conferencing process, improves the fault tolerance and resource utilization of the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118900255A_ABST
    Figure CN118900255A_ABST
Patent Text Reader

Abstract

The invention discloses a request processing method, device and equipment for realizing gatekeeper group load balancing, and relates to the technical field of communication, the method comprises the following steps: when a registration request sent by a conference terminal is received, searching a target gatekeeper group based on the registration request, and calculating current available resources corresponding to each gatekeeper in the target gatekeeper group; determining a main gatekeeper and a standby gatekeeper in the target gatekeeper group according to the current available resources, and processing the registration request based on the main gatekeeper and the standby gatekeeper; when a call request sent by the conference terminal after registration is completed is received and the called number is not in the target gatekeeper group, broadcasting a position request to other gatekeeper groups; and if a position confirmation message returned by other gatekeeper groups according to the position request is received, processing the call request based on the position confirmation message. The flexibility of gatekeeper group service is improved on the premise of increasing the call volume and the reliability in the video conference process, and then the fault-tolerant capability and the resource utilization rate of the system are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a request processing method, device and equipment for implementing gatekeeper group load balancing. Background Art

[0002] The gatekeeper (GK) in the video conferencing system is a key component that plays a core role in the H.323 protocol stack. In order to ensure the continuity and stability of video conferencing services, the high availability design of the gatekeeper is essential, including distributed architecture, redundant deployment, and failover. The gatekeeper plays a vital role in the video conferencing system, and its high availability is the key to ensuring service quality.

[0003] Due to the changes in call volume during video conferencing, the gatekeeper group capacity in traditional technology cannot automatically balance the load, resulting in low fault tolerance and low resource utilization of the communication system in the actual video conferencing process under high concurrency conditions. Summary of the invention

[0004] The main purpose of the present application is to provide a request processing method, device and equipment for realizing gatekeeper group load balancing, aiming to solve the technical problem that traditional technology cannot automatically load balance the gatekeeper group capacity.

[0005] To achieve the above object, the present application provides a request processing method for realizing gatekeeper group load balancing, the method comprising the following steps:

[0006] When receiving a registration request sent by a conference terminal, searching a target gatekeeper group based on the registration request, and calculating the current available resources corresponding to each gatekeeper in the target gatekeeper group;

[0007] Determine a primary gatekeeper and a backup gatekeeper in the target gatekeeper group according to the currently available resources, and process the registration request based on the primary gatekeeper and the backup gatekeeper;

[0008] When receiving a call request sent by the conference terminal after completing registration and the called number is not in the target gatekeeper group, broadcasting a location request to other gatekeeper groups;

[0009] If a location confirmation message returned by the other gatekeeper group according to the location request is received, the call request is processed based on the location confirmation message.

[0010] In one embodiment, when receiving a registration request sent by a conference terminal, searching a target gatekeeper group based on the registration request and calculating currently available resources corresponding to each gatekeeper in the target gatekeeper group includes:

[0011] When receiving a registration request sent by a conference terminal, confirming the registration number segment of the conference terminal according to the registration request, and searching for a target gatekeeper group corresponding to the registration number segment;

[0012] Obtaining currently available bandwidth, currently available CPU resources, and currently available memory resources corresponding to each gatekeeper in the target gatekeeper group;

[0013] The currently available resources corresponding to each gatekeeper in the target gatekeeper group are calculated according to the currently available bandwidth, the currently available CPU resources and the currently available memory resources.

[0014] In one embodiment, the step of determining a primary gatekeeper and a backup gatekeeper in the target gatekeeper group according to the currently available resources, and processing the registration request based on the primary gatekeeper and the backup gatekeeper includes:

[0015] Determine the gatekeeper with the largest currently available resources in the target gatekeeper group as the primary gatekeeper, and determine the other gatekeepers in the target gatekeeper group except the primary gatekeeper as backup gatekeepers;

[0016] Determine the currently available gatekeeper in the target gatekeeper group through the primary gatekeeper, and calculate the first priority order based on the distance between the currently available gatekeeper and the conference terminal and the number of remaining terminals allowed to be registered by the current device of the currently available gatekeeper;

[0017] A gatekeeper is selected from the primary gatekeeper and the backup gatekeeper based on the first priority order as a registration gatekeeper to process the registration request.

[0018] In one embodiment, after the step of determining a primary gatekeeper and a backup gatekeeper in the target gatekeeper group according to the currently available resources, and processing the registration request based on the primary gatekeeper and the backup gatekeeper, the step further includes:

[0019] If it is detected that the main gatekeeper is abnormal or a new gatekeeper appears in the target gatekeeper group, competition information is sent to the target gatekeeper group to select a new main gatekeeper and a new backup gatekeeper from the target gatekeeper group, and all gatekeepers in the target gatekeeper group are connected to the same database server;

[0020] The new master gatekeeper is commanded to refresh the group information table corresponding to the target gatekeeper group, wherein the group information table is used to record the information of all gatekeepers in the target gatekeeper group, and the new backup gatekeeper is commanded to record the address of the new master gatekeeper.

[0021] In one embodiment, if a location confirmation message returned by the other gatekeeper group according to the location request is received, before the step of processing the call request based on the location confirmation message, the step further includes:

[0022] When the other gatekeeper group receives the location request, determining whether to receive the call according to the number of concurrent calls allowed remaining by the current devices of the other gatekeeper group;

[0023] If so, a second priority order is calculated according to the distance between the other gatekeeper groups and the conference terminal and the number of concurrent calls remaining allowed for the current device, and a location confirmation message returned by the other gatekeeper groups based on the second priority order is received.

[0024] In one embodiment, if a location confirmation message returned by the other gatekeeper group according to the location request is received, the step of processing the call request based on the location confirmation message includes:

[0025] If a location confirmation message returned by the other gatekeeper group according to the location request is received, the location confirmation message is returned to the target gatekeeper group, wherein the location confirmation message includes the gatekeeper address of the highest priority gatekeeper;

[0026] The forwarding IP and the forwarding port are determined according to the admission confirmation message received in the target gatekeeper group, and the call request is processed based on the forwarding IP and the forwarding port.

[0027] In addition, to achieve the above-mentioned purpose, the present application also proposes a request processing device for realizing gatekeeper group load balancing, and the request processing device for realizing gatekeeper group load balancing includes:

[0028] A data calculation module, configured to, when receiving a registration request sent by a conference terminal, search for a target gatekeeper group based on the registration request, and calculate the current available resources corresponding to each gatekeeper in the target gatekeeper group;

[0029] A first processing module, configured to determine a primary gatekeeper and a backup gatekeeper in the target gatekeeper group according to the currently available resources, and process the registration request based on the primary gatekeeper and the backup gatekeeper;

[0030] A request broadcast module, configured to broadcast a location request to other gatekeeper groups when a call request is received from the conference terminal after registration is completed and the called number is not in the target gatekeeper group;

[0031] The second processing module is configured to process the call request based on the location confirmation message if a location confirmation message returned by the other gatekeeper group according to the location request is received.

[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a request processing device for implementing gatekeeper group load balancing, the device comprising: a memory, a processor, and a request processing program for implementing gatekeeper group load balancing stored on the memory and executable on the processor, the request processing program for implementing gatekeeper group load balancing being configured to implement the steps of the request processing method for implementing gatekeeper group load balancing as described above.

[0033] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and on which is stored a request processing program for implementing gatekeeper group load balancing. When the request processing program for implementing gatekeeper group load balancing is executed by a processor, the steps of the request processing method for implementing gatekeeper group load balancing as described above are implemented.

[0034] In addition, to achieve the above-mentioned purpose, the present invention also provides a computer program product, which includes a request processing program for implementing gatekeeper group load balancing, and when the request processing program for implementing gatekeeper group load balancing is executed by a processor, it implements the steps of the request processing method for implementing gatekeeper group load balancing as described above.

[0035] The present application searches for a target gatekeeper group based on the registration request when receiving a registration request from a conference terminal, and calculates the current available resources corresponding to each gatekeeper in the target gatekeeper group; determines the primary gatekeeper and the backup gatekeeper in the target gatekeeper group based on the current available resources, and processes the registration request based on the primary gatekeeper and the backup gatekeeper; broadcasts a location request to other gatekeeper groups when receiving a call request from the conference terminal after completing the registration and the called number is not in the target gatekeeper group; and processes the call request based on the location confirmation message if a location confirmation message returned by the other gatekeeper group based on the location request is received. Since the above method of the present application determines the primary gatekeeper and the backup gatekeeper based on the calculated current available resources corresponding to each gatekeeper in the target gatekeeper group, and processes the registration request from the conference terminal based on the primary gatekeeper and the backup gatekeeper, and processes the call request from the conference terminal through the location confirmation message returned by other gatekeeper groups based on the location request, the elasticity of the gatekeeper group service can be effectively improved under the premise of increasing the call volume and reliability of the video conference process, thereby improving the fault tolerance and resource utilization of the communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 A schematic diagram of the structure of a request processing device for implementing gatekeeper group load balancing in a hardware operating environment involved in an embodiment of the present application;

[0037] Figure 2 A flowchart of a first embodiment of a request processing method for implementing gatekeeper group load balancing in this application;

[0038] Figure 3 A schematic diagram of the basic networking structure of the GK group in the request processing method for implementing gatekeeper group load balancing in this application;

[0039] Figure 4 A flowchart of a second embodiment of a request processing method for implementing gatekeeper group load balancing in this application;

[0040] Figure 5 A flowchart of a third embodiment of a request processing method for implementing gatekeeper group load balancing in this application;

[0041] Figure 6 This is a structural block diagram of the first embodiment of the request processing device for implementing gatekeeper group load balancing in the present application.

[0042] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0043] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0044] Reference Figure 1 , Figure 1 A schematic diagram of the structure of a request processing device for implementing gatekeeper group load balancing in the hardware operating environment involved in the embodiment of the present application.

[0045] like Figure 1As shown, the request processing device for implementing gatekeeper group load balancing may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (Wireless-Fidelity, Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM), or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk storage. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0046] Those skilled in the art will understand that Figure 1 The structure shown in does not constitute a limitation on the request processing device for implementing gatekeeper group load balancing, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0047] like Figure 1 As shown, the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and a request processing program for implementing gatekeeper group load balancing.

[0048] exist Figure 1 In the request processing device for implementing gatekeeper group load balancing shown, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the request processing device for implementing gatekeeper group load balancing in the present application can be set in the request processing device for implementing gatekeeper group load balancing, and the request processing device for implementing gatekeeper group load balancing calls the request processing program for implementing gatekeeper group load balancing stored in the memory 1005 through the processor 1001, and executes the request processing method for implementing gatekeeper group load balancing provided in the embodiment of the present application.

[0049] The present application embodiment provides a request processing method for realizing gatekeeper group load balancing, referring to Figure 2 , Figure 2 This is a flow chart of the first embodiment of the request processing method for implementing gatekeeper group load balancing in the present application.

[0050] In this embodiment, the request processing method for implementing gatekeeper group load balancing includes the following steps:

[0051] Step S10: when a registration request sent by a conference terminal is received, a target gatekeeper group is searched based on the registration request, and currently available resources corresponding to each gatekeeper in the target gatekeeper group are calculated.

[0052] It should be noted that the execution subject of the method of this embodiment can be a terminal device with data calculation, data processing and program running functions, such as a smart phone, a computer, etc., or an electronic device with the same or similar functions, such as the request processing device for realizing gatekeeper group load balancing. The following takes the request processing device for realizing gatekeeper group load balancing (hereinafter referred to as the processing device) as an example to illustrate this embodiment and the following embodiments.

[0053] It is understandable that the above conference terminal can be a video conference terminal, such as a desktop conference terminal, a split conference terminal, an integrated conference terminal, etc., and this embodiment does not limit this. In particular, the above video conference terminal needs to support the H.323 protocol, which is a standard protocol stack that provides good conditions for the further development of Internet phone and video phone conference systems and system compatibility.

[0054] It should be understood that the above target gatekeeper group includes a gatekeeper group (also called a GK group) of several gatekeepers (Gatekeeper, GK). Each GK group is responsible for the terminal registration process of a number segment in the video conference. Figure 3 , Figure 3 This is a schematic diagram of the basic networking structure of the GK group in the request processing method for implementing gatekeeper group load balancing in this application. Figure 3 In the above, the guiding GK can be built into the above processing device, and its role is to serve as the registration entrance for all terminals, and to guide the domain GK configured according to the number segment of the registered terminal to the corresponding GK group for actual registration and calling. In addition, the GK group can be composed of several GKs, such as Figure 3 GK Group 1 and GK Group 2 in the example are both composed of 4 GKs (i.e., the primary GK, the secondary GK, the third GK, and the fourth GK), and all GKs are connected to the database server. RRQ (Registration Request) refers to a registration request, and ARQ (Automatic Repeat reQuest) refers to an automatic resend request.

[0055] Step S20: determining a primary gatekeeper and a backup gatekeeper in the target gatekeeper group according to the currently available resources, and processing the registration request based on the primary gatekeeper and the backup gatekeeper.

[0056] It should be noted that the above-mentioned main gatekeeper can be responsible for managing the first-level gatekeepers belonging to the operator, and is responsible for address resolution between the first-level gatekeepers, intercommunication and address exchange between video conferencing networks of different operators; the above-mentioned backup gatekeeper is a redundant device of the main gatekeeper, used to take over its duties when the main gatekeeper fails or cannot work normally. It can keep in sync with the main gatekeeper so that it can seamlessly take over its work when the main gatekeeper fails.

[0057] Step S30: When a call request is received from the conference terminal after completing registration and the called number is not in the target gatekeeper group, a location request is broadcast to other gatekeeper groups.

[0058] It should be noted that the above-mentioned other gatekeeper groups refer to the gatekeeper groups other than the above-mentioned target gatekeeper group in the communication system where the video conference is located. The above-mentioned location request is LRQ (Location Request). LRQ is a signaling message in the H.323 protocol, which is used to request the gatekeeper to provide the contact information of the terminal with a specific E.164 address or H.323ID.

[0059] Step S40: If a location confirmation message returned by the other gatekeeper group according to the location request is received, the call request is processed based on the location confirmation message.

[0060] It is understandable that when a conference terminal wants to establish communication with a terminal in another area, it will send an LRQ message to the gatekeeper of the local area to request the IP address and port information of the target terminal. If the target terminal has been registered with its gatekeeper, the gatekeeper will respond to the request by sending an LCF (Location Confirm) message to provide the required contact information; if the request fails, the gatekeeper will send an LRJ (Location Reject) message to indicate that the contact information cannot be provided or the target terminal is not registered.

[0061] In a specific implementation, the load balancing of the GK group can be completed by processing the above registration request and the above call request. Through the load balancing of the GK group, the connection requests of the video conference participants can be intelligently distributed to different gatekeepers to avoid single-point overload and improve the processing capacity of the overall system. Exemplarily, the load balancing process of the GK group can be implemented based on the following principles. The total number of registrable terminals and the number of concurrent calls of the main GK and the GK need to be determined according to the resources of each GK and the network bandwidth. The GK groups need to continuously broadcast competition messages to ensure that there is always a main GK online. When the terminal registers the GK, it receives the GCF message of the preferred GK, which carries the AlternateGKs field. In this field, multiple records are separated by ",". needToRegister indicates that if the terminal is connected to the backup GK, it needs to initiate admissionRequest (ARQ) again. In order to do load, it is recommended to require the terminal to register again. The smaller the priority weight value, the higher the priority. In order to achieve load balancing, each GK needs to limit the total number of registered terminals and the number of concurrent calls. If the number exceeds the upper limit, access denial is required and resourceUnavailable is returned. Unless password registration is not required, the terminal's registration GRQ (Gatekeeper Request) and RRQ messages will carry timestamps, which the GK uses to determine the distance from the registered terminal. In addition, GK traffic can be diverted according to the registered number segment, using a unified entrance for registration, and then distributed to nodes close to its business to avoid cross-GK calls as much as possible.

[0062] This embodiment, when receiving a registration request sent by a conference terminal, searches for a target gatekeeper group based on the registration request, and calculates the current available resources corresponding to each gatekeeper in the target gatekeeper group; determines the primary gatekeeper and the backup gatekeeper in the target gatekeeper group based on the current available resources, and processes the registration request based on the primary gatekeeper and the backup gatekeeper; when receiving a call request sent by the conference terminal after completing the registration and the called number is not in the target gatekeeper group, broadcasts a location request to other gatekeeper groups; if a location confirmation message returned by the other gatekeeper group according to the location request is received, the call request is processed based on the location confirmation message. Since the above method of this embodiment determines the primary gatekeeper and the backup gatekeeper according to the calculated current available resources corresponding to each gatekeeper in the target gatekeeper group, and processes the registration request sent by the conference terminal according to the primary gatekeeper and the backup gatekeeper, and processes the call request sent by the conference terminal through the location confirmation message returned by other gatekeeper groups according to the location request, the elasticity of the gatekeeper group service can be effectively improved under the premise of increasing the call volume and reliability of the video conference process, thereby improving the fault tolerance and resource utilization of the communication system.

[0063] refer to Figure 4 , Figure 4 This is a flow chart of a second embodiment of a request processing method for implementing gatekeeper group load balancing in the present application.

[0064] In a feasible implementation manner, the step S10 may include:

[0065] Step S101: when a registration request sent by a conference terminal is received, the registration number segment of the conference terminal is confirmed according to the registration request, and a target gatekeeper group corresponding to the registration number segment is searched.

[0066] Step S102: obtaining the currently available bandwidth, currently available CPU resources and currently available memory resources corresponding to each gatekeeper in the target gatekeeper group.

[0067] Step S103: Calculate the currently available resources corresponding to each gatekeeper in the target gatekeeper group according to the currently available bandwidth, the currently available CPU resources and the currently available memory resources.

[0068] In a specific implementation, the currently available resources can be calculated based on the following formula:

[0069] Res = P1*available bandwidth + P2*available CPU resources + P3*available memory resources

[0070] Among them, Res represents the currently available resources mentioned above, P1, P2, and P3 are custom coefficients and their values ​​can be determined according to the emphasis on weight items in actual conditions.

[0071] In a feasible implementation manner, the step S20 may include:

[0072] Step S201: Determine the gatekeeper with the largest currently available resources in the target gatekeeper group as the primary gatekeeper, and determine the other gatekeepers in the target gatekeeper group except the primary gatekeeper as backup gatekeepers.

[0073] It should be understood that the above-mentioned main network keeper is the main GK, and the above-mentioned backup network keeper is the backup GK. The GK group can broadcast contention messages regularly, and the contention messages need to include the available resources of each GK and the current master and backup status of the GK. Among them, the GK with the largest available resources becomes the main GK. After the main GK is confirmed, it will not change easily unless it is offline. At the same time, the main GK obtains broadcast messages from other GKs, refreshes the GK group information table, and records the available backup GK information. The backup GK needs to record the address of the main GK.

[0074] Step S202: determining the currently available gatekeeper in the target gatekeeper group through the primary gatekeeper, and calculating a first priority order based on the distance between the currently available gatekeeper and the conference terminal and the number of remaining terminals allowed to be registered by the current device of the currently available gatekeeper.

[0075] Step S203: Select a gatekeeper from the primary gatekeeper and the backup gatekeeper based on the first priority order as a registration gatekeeper to process the registration request.

[0076] In the specific implementation, when the terminal registers, it sends a GRQ to the guiding GK. The guiding GK searches for the domain GK group through the registration number prefix and forwards the GRQ message to all GKs in the domain GK group. All GKs in the GK group estimate the distance from the terminal through the GRQ message carrying the timestamp and the time when the GRQ message is received. The main GK lists the available GKs of the GK group in the AlternateGK field in the GCF (GateKeeper Confirmation) message according to the GK priority, and attaches the priority. Other GKs in the GK group return a GRJ (Gatekeeper Reject) to the guiding GK. The guiding GK receives the GCF message returned by the main GK of the GK group and forwards the message to the terminal. The terminal performs RRQ registration according to the address of the AlternateGK field in the GCF message. When receiving the RRQ registration message, it is necessary to determine whether to accept the registration based on the total number of registered terminals remaining for the current device of this GK and the number of concurrent calls remaining for the current device. If the upper limit is exceeded, resourceUnavailable is returned to guide the terminal to select other GKs in the backup GK list for registration. In the GCF response message, the GK priority is calculated as follows:

[0077] Priority = (K1*the total number of terminals allowed to be registered on the current device+K2*the distance to the terminal)

[0078] Among them, Priority represents the GK registration priority, K1 and K2 are custom coefficients and their values ​​can be determined according to the emphasis on the weight item in actual conditions. The above GK registration priorities are arranged in order, that is, the above first priority order is obtained.

[0079] In a feasible implementation manner, after step S20, the following may also be included:

[0080] Step S21: If it is detected that the main gatekeeper is abnormal or a new gatekeeper appears in the target gatekeeper group, competition information is sent to the target gatekeeper group to select a new main gatekeeper and a new backup gatekeeper from the target gatekeeper group. All gatekeepers in the target gatekeeper group are connected to the same database server.

[0081] Step S22: command the new master gatekeeper to refresh the group information table corresponding to the target gatekeeper group, the group information table is used to record the information of all gatekeepers in the target gatekeeper group, and command the new backup gatekeeper to record the address of the new master gatekeeper.

[0082] In the specific implementation, if the main GK is abnormal, it is necessary to re-select the main GK through the competition message, and refresh the GK group information table of the new main GK. The backup GK needs to record the address of the new main GK. To maintain data consistency, all GKs in the GK group are connected to the same database server, and all number release data and registration and call data are shared. If a new GK device is introduced, the competition message broadcast is also carried out regularly. The main GK refreshes the GK group information table and records the available backup GK information. The new backup GK needs to record the address of the main GK.

[0083] This embodiment confirms the registration number segment of the conference terminal according to the registration request when receiving a registration request from the conference terminal, and searches for the target gatekeeper group corresponding to the registration number segment; obtains the currently available bandwidth, currently available CPU resources and currently available memory resources corresponding to each gatekeeper in the target gatekeeper group; calculates the currently available resources corresponding to each gatekeeper in the target gatekeeper group according to the currently available bandwidth, the currently available CPU resources and the currently available memory resources; determines the gatekeeper with the largest currently available resources in the target gatekeeper group as the primary gatekeeper, and determines the other gatekeepers in the target gatekeeper group except the primary gatekeeper as backup gatekeepers; determines the currently available gatekeepers in the target gatekeeper group through the primary gatekeeper, and based on the currently available gatekeepers A first priority order is calculated based on the distance from the conference terminal and the number of remaining registered terminals allowed by the current device of the currently available gatekeeper; based on the first priority order, a gatekeeper is selected from the main gatekeeper and the backup gatekeeper as a registered gatekeeper to process the registration request; if it is detected that the main gatekeeper is abnormal or a new gatekeeper appears in the target gatekeeper group, competition information is sent to the target gatekeeper group to select a new main gatekeeper and a new backup gatekeeper from the target gatekeeper group, and all gatekeepers in the target gatekeeper group are connected to the same database server; the new main gatekeeper is ordered to refresh the group information summary table corresponding to the target gatekeeper group, the group information summary table is used to record the information of all gatekeepers in the target gatekeeper group, and the new backup gatekeeper is ordered to record the address of the new main gatekeeper. The above method of this embodiment selects a gatekeeper from the main gatekeeper and the backup gatekeeper as the registration gatekeeper to process the registration request through the first priority order calculated based on the distance between the current available gatekeeper and the conference terminal and the number of remaining allowed registration terminals of the current device of the current available gatekeeper, thereby ensuring that the registration request can be processed in a timely and effective manner; at the same time, when an abnormality occurs in the main gatekeeper or a new gatekeeper appears in the target gatekeeper group, a new main gatekeeper and a new backup gatekeeper are selected from the target gatekeeper group, thereby ensuring the continuity and stability of the video conferencing service.

[0084] refer to Figure 5 , Figure 5This is a flow chart of a third embodiment of a request processing method for implementing gatekeeper group load balancing in the present application.

[0085] In a feasible implementation manner, before step S40, the following may also be included:

[0086] Step S31: When the other gatekeeper group receives the location request, it determines whether to receive the call according to the number of concurrent calls remaining allowed by the current devices of the other gatekeeper group.

[0087] Step S32: If yes, calculate a second priority order according to the distance between the other gatekeeper groups and the conference terminal and the number of concurrent calls remaining allowed for the current device, and receive a location confirmation message returned by the other gatekeeper groups based on the second priority order.

[0088] In a specific implementation, the second priority order may be calculated based on the following process:

[0089] Priority' = (K3*the number of concurrent calls allowed by the current device+K4*the distance to the called terminal)

[0090] Among them, Priority' represents the GK call priority, K3 and K4 are custom coefficients and their values ​​can be determined according to the emphasis on the weight item in actual conditions. The above GK call priorities are arranged in order to obtain the above second priority order.

[0091] In a feasible implementation manner, the step S40 may include:

[0092] Step S401: if a location confirmation message returned by the other gatekeeper group according to the location request is received, the location confirmation message is returned to the target gatekeeper group, wherein the location confirmation message includes the gatekeeper address of the highest priority gatekeeper.

[0093] Step S402: determining a forwarding IP and a forwarding port according to the admission confirmation message received in the target gatekeeper group, and processing the call request based on the forwarding IP and the forwarding port.

[0094] In a specific implementation, when a terminal makes a call, it can send an ARQ message to the currently used registered GK. The currently registered GK queries the called number. If it is not in the current GK group, it needs to send an LRQ message to the guiding GK, which will query it. The guiding GK forwards the LRQ to other GK groups for broadcasting. When other GK groups receive the LRQ message, they need to determine whether to accept the call based on the number of concurrent calls allowed by the current device of this GK, and report it to the main GK. The main GK returns the LCF to the guiding GK based on the call priority reported by the GK group, and carries the GK address with the highest call priority (that is, the gatekeeper address of the highest priority gatekeeper mentioned above) in the LCF. The guiding GK returns the received LCF address to the original GK group, and determines whether there are any signaling and media forwarding requirements. In the ACF (Admission Confirmation) message returned to the original GK group, if forwarding is required, the address uses the forwarding IP and forwarding port of the guiding GK; if forwarding is not required, the forwarding IP and forwarding port of the GK in the target GK group are used to avoid the inevitable media forwarding when H460.18 is enabled. Finally, the call request sent by the conference terminal can be processed based on the above forwarding IP and forwarding port.

[0095] This embodiment determines whether to receive the call according to the number of concurrent calls remaining allowed by the current device of the other gatekeeper group when the other gatekeeper group receives the location request; if so, calculates the second priority order according to the distance between the other gatekeeper group and the conference terminal and the number of concurrent calls remaining allowed by the current device, and receives the location confirmation message returned by the other gatekeeper group based on the second priority order; if a location confirmation message returned by the other gatekeeper group according to the location request is received, returns the location confirmation message to the target gatekeeper group, the location confirmation message containing the gatekeeper address of the highest priority gatekeeper; determines the forwarding IP and forwarding port according to the access confirmation message received from the target gatekeeper group, and processes the call request based on the forwarding IP and the forwarding port. The above method of this embodiment determines the forwarding IP and forwarding port according to the location confirmation message returned by the other gatekeeper group according to the location request, and processes the call request issued by the conference terminal based on the forwarding IP and the forwarding port, thereby ensuring that the call request can be processed in a timely and effective manner.

[0096] In addition, an embodiment of the present application also proposes a storage medium, on which is stored a request processing program for implementing gatekeeper group load balancing. When the request processing program for implementing gatekeeper group load balancing is executed by a processor, the steps of the request processing method for implementing gatekeeper group load balancing as described above are implemented.

[0097] Reference Figure 5 , Figure 5 This is a structural block diagram of the first embodiment of the request processing device for implementing gatekeeper group load balancing in the present application.

[0098] like Figure 5 As shown, the request processing device for implementing gatekeeper group load balancing proposed in the embodiment of the present application includes:

[0099] The data calculation module 601 is used to find the target gatekeeper group based on the registration request when receiving the registration request sent by the conference terminal, and calculate the current available resources corresponding to each gatekeeper in the target gatekeeper group;

[0100] A first processing module 602, configured to determine a primary gatekeeper and a backup gatekeeper in the target gatekeeper group according to the currently available resources, and process the registration request based on the primary gatekeeper and the backup gatekeeper;

[0101] A request broadcast module 603, configured to broadcast a location request to other gatekeeper groups when a call request is received from the conference terminal after registration is completed and the called number is not in the target gatekeeper group;

[0102] The second processing module 604 is configured to process the call request based on the location confirmation message if a location confirmation message returned by the other gatekeeper group according to the location request is received.

[0103] This embodiment, when receiving a registration request sent by a conference terminal, searches for a target gatekeeper group based on the registration request, and calculates the current available resources corresponding to each gatekeeper in the target gatekeeper group; determines the primary gatekeeper and the backup gatekeeper in the target gatekeeper group based on the current available resources, and processes the registration request based on the primary gatekeeper and the backup gatekeeper; when receiving a call request sent by the conference terminal after completing the registration and the called number is not in the target gatekeeper group, broadcasts a location request to other gatekeeper groups; if a location confirmation message returned by the other gatekeeper group according to the location request is received, the call request is processed based on the location confirmation message. Since the above method of this embodiment determines the primary gatekeeper and the backup gatekeeper according to the calculated current available resources corresponding to each gatekeeper in the target gatekeeper group, and processes the registration request sent by the conference terminal according to the primary gatekeeper and the backup gatekeeper, and processes the call request sent by the conference terminal through the location confirmation message returned by other gatekeeper groups according to the location request, the elasticity of the gatekeeper group service can be effectively improved under the premise of increasing the call volume and reliability of the video conference process, thereby improving the fault tolerance and resource utilization of the communication system.

[0104] Based on the first embodiment of the request processing device for implementing gatekeeper group load balancing of the present application, a second embodiment of the request processing device for implementing gatekeeper group load balancing of the present application is proposed.

[0105] In this embodiment, the data calculation module 601 is also used to, when receiving a registration request issued by a conference terminal, confirm the registration number segment of the conference terminal according to the registration request, and search for the target gatekeeper group corresponding to the registration number segment; obtain the currently available bandwidth, currently available CPU resources and currently available memory resources corresponding to each gatekeeper in the target gatekeeper group; calculate the currently available resources corresponding to each gatekeeper in the target gatekeeper group according to the currently available bandwidth, the currently available CPU resources and the currently available memory resources.

[0106] Furthermore, the first processing module 602 is also used to determine the gatekeeper with the largest currently available resources in the target gatekeeper group as the main gatekeeper, and determine the other gatekeepers in the target gatekeeper group except the main gatekeeper as backup gatekeepers; determine the currently available gatekeepers in the target gatekeeper group through the main gatekeeper, and calculate the first priority order based on the distance between the currently available gatekeeper and the conference terminal and the number of remaining registered terminals allowed by the current device of the currently available gatekeeper; based on the first priority order, select a gatekeeper from the main gatekeeper and the backup gatekeeper as the registration gatekeeper to process the registration request.

[0107] Furthermore, the first processing module 602 is also used to send competition information to the target gatekeeper group if it is detected that the main gatekeeper has an abnormality or a new gatekeeper appears in the target gatekeeper group, so as to select a new main gatekeeper and a new backup gatekeeper from the target gatekeeper group, and all gatekeepers in the target gatekeeper group are connected to the same database server; command the new main gatekeeper to refresh the group information table corresponding to the target gatekeeper group, and the group information table is used to record the information of all gatekeepers in the target gatekeeper group, and command the new backup gatekeeper to record the address of the new main gatekeeper.

[0108] Furthermore, the second processing module 604 is also used to determine whether to receive the call based on the remaining number of concurrent calls allowed by the current device of the other gatekeeper group when the other gatekeeper group receives the location request; if so, calculate the second priority order based on the distance between the other gatekeeper group and the conference terminal and the remaining number of concurrent calls allowed by the current device, and receive the location confirmation message returned by the other gatekeeper group based on the second priority order.

[0109] Furthermore, the second processing module 604 is also used to return the location confirmation message to the target gatekeeper group if it receives a location confirmation message returned by the other gatekeeper group based on the location request, and the location confirmation message includes the gatekeeper address of the highest priority gatekeeper; determine the forwarding IP and forwarding port according to the access confirmation message received from the target gatekeeper group, and process the call request based on the forwarding IP and the forwarding port.

[0110] Other embodiments or specific implementation methods of the request processing device for implementing gatekeeper group load balancing in the present application can refer to the above-mentioned method embodiments and will not be repeated here.

[0111] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0112] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0113] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory / random access memory, a disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0114] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A request processing method for realizing gatekeeper group load balancing, characterized in that: The method comprises the following steps: When receiving a registration request sent by a conference terminal, searching a target gatekeeper group based on the registration request, and calculating the current available resources corresponding to each gatekeeper in the target gatekeeper group; Determine a primary gatekeeper and a backup gatekeeper in the target gatekeeper group according to the currently available resources, and process the registration request based on the primary gatekeeper and the backup gatekeeper; When receiving a call request sent by the conference terminal after completing registration and the called number is not in the target gatekeeper group, broadcasting a location request to other gatekeeper groups; If a location confirmation message returned by the other gatekeeper group according to the location request is received, the call request is processed based on the location confirmation message.

2. The request processing method for realizing gatekeeper group load balancing according to claim 1, characterized in that: The step of searching a target gatekeeper group based on the registration request and calculating the currently available resources corresponding to each gatekeeper in the target gatekeeper group when a registration request sent by the conference terminal is received includes: When receiving a registration request sent by a conference terminal, confirming the registration number segment of the conference terminal according to the registration request, and searching for a target gatekeeper group corresponding to the registration number segment; Obtaining currently available bandwidth, currently available CPU resources, and currently available memory resources corresponding to each gatekeeper in the target gatekeeper group; The currently available resources corresponding to each gatekeeper in the target gatekeeper group are calculated according to the currently available bandwidth, the currently available CPU resources and the currently available memory resources.

3. The request processing method for realizing gatekeeper group load balancing according to claim 1, characterized in that: The step of determining a primary gatekeeper and a backup gatekeeper in the target gatekeeper group according to the currently available resources, and processing the registration request based on the primary gatekeeper and the backup gatekeeper includes: Determine the gatekeeper with the largest currently available resources in the target gatekeeper group as the primary gatekeeper, and determine the other gatekeepers in the target gatekeeper group except the primary gatekeeper as backup gatekeepers; Determine the currently available gatekeeper in the target gatekeeper group through the primary gatekeeper, and calculate the first priority order based on the distance between the currently available gatekeeper and the conference terminal and the number of remaining terminals allowed to be registered by the current device of the currently available gatekeeper; A gatekeeper is selected from the primary gatekeeper and the backup gatekeeper based on the first priority order as a registration gatekeeper to process the registration request.

4. The request processing method for realizing gatekeeper group load balancing according to claim 1, characterized in that: After the step of determining the primary gatekeeper and the backup gatekeeper in the target gatekeeper group according to the currently available resources, and processing the registration request based on the primary gatekeeper and the backup gatekeeper, the method further includes: If it is detected that the main gatekeeper is abnormal or a new gatekeeper appears in the target gatekeeper group, competition information is sent to the target gatekeeper group to select a new main gatekeeper and a new backup gatekeeper from the target gatekeeper group, and all gatekeepers in the target gatekeeper group are connected to the same database server; The new master gatekeeper is commanded to refresh the group information table corresponding to the target gatekeeper group, wherein the group information table is used to record the information of all gatekeepers in the target gatekeeper group, and the new backup gatekeeper is commanded to record the address of the new master gatekeeper.

5. The request processing method for realizing gatekeeper group load balancing according to claim 1, characterized in that: If a location confirmation message returned by the other gatekeeper group according to the location request is received, before the step of processing the call request based on the location confirmation message, the method further includes: When the other gatekeeper group receives the location request, determining whether to receive the call according to the number of concurrent calls allowed remaining by the current devices of the other gatekeeper group; If so, a second priority order is calculated according to the distance between the other gatekeeper groups and the conference terminal and the number of concurrent calls remaining allowed for the current device, and a location confirmation message returned by the other gatekeeper groups based on the second priority order is received.

6. The request processing method for realizing gatekeeper group load balancing according to claim 1, characterized in that: If a location confirmation message returned by the other gatekeeper group according to the location request is received, the step of processing the call request based on the location confirmation message comprises: If a location confirmation message returned by the other gatekeeper group according to the location request is received, the location confirmation message is returned to the target gatekeeper group, wherein the location confirmation message includes the gatekeeper address of the highest priority gatekeeper; The forwarding IP and the forwarding port are determined according to the admission confirmation message received in the target gatekeeper group, and the call request is processed based on the forwarding IP and the forwarding port.

7. A request processing device for realizing gatekeeper group load balancing, characterized in that: The request processing device for realizing gatekeeper group load balancing includes: A data calculation module, configured to, when receiving a registration request sent by a conference terminal, search for a target gatekeeper group based on the registration request, and calculate the current available resources corresponding to each gatekeeper in the target gatekeeper group; A first processing module, configured to determine a primary gatekeeper and a backup gatekeeper in the target gatekeeper group according to the currently available resources, and process the registration request based on the primary gatekeeper and the backup gatekeeper; A request broadcast module, configured to broadcast a location request to other gatekeeper groups when a call request is received from the conference terminal after registration is completed and the called number is not in the target gatekeeper group; The second processing module is configured to process the call request based on the location confirmation message if a location confirmation message returned by the other gatekeeper group according to the location request is received.

8. A request processing device for implementing gatekeeper group load balancing, characterized in that: The device includes: a memory, a processor, and a request processing program for implementing gatekeeper group load balancing stored in the memory and executable on the processor, wherein the request processing program for implementing gatekeeper group load balancing is configured to implement the steps of a request processing method for implementing gatekeeper group load balancing as described in any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, on which is stored a request processing program for implementing gatekeeper group load balancing. When the request processing program for implementing gatekeeper group load balancing is executed by a processor, the steps of the request processing method for implementing gatekeeper group load balancing as described in any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a request processing program for implementing gatekeeper group load balancing, and when the request processing program for implementing gatekeeper group load balancing is executed by a processor, the steps of the request processing method for implementing gatekeeper group load balancing as claimed in any one of claims 1 to 6 are implemented.