CN108093147B - Distributed multi-stage scheduling method and equipment - Google Patents
Distributed multi-stage scheduling method and equipment Download PDFInfo
- Publication number
- CN108093147B CN108093147B CN201611037399.6A CN201611037399A CN108093147B CN 108093147 B CN108093147 B CN 108093147B CN 201611037399 A CN201611037399 A CN 201611037399A CN 108093147 B CN108093147 B CN 108093147B
- Authority
- CN
- China
- Prior art keywords
- scheduling server
- partner
- system information
- scheduling
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
Abstract
The embodiment of the invention provides a distributed multi-stage scheduling method and equipment, which comprise the following steps: acquiring system information of a partner scheduling server, and storing the system information; the system information comprises a system identifier and an access address of a partner scheduling server; the partner scheduling server is a scheduling server in the same wide area network as the first scheduling server; receiving a call request of a terminal; acquiring a system identifier contained in the call request, and judging whether the system identifier is the same as the system identifier of the first scheduling server or not; if not, according to the stored system information, obtaining an access address of the dispatching server matched with the system identifier, and sending the call request to the dispatching server matched with the system identifier according to the access address. The embodiment of the invention can improve the flexibility and reliability of scheduling, improve the communication quality and reduce the data processing delay.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a distributed multi-level scheduling method and equipment.
Background
In a private network scheduling system, multiple scheduling systems often need to be cascaded in multiple levels, an upper scheduling system needs to command and schedule a lower scheduling system, and the lower scheduling system needs to report services such as data, voice, short messages and the like to the upper scheduling system. Fig. 1 is a schematic diagram of a scheduling system in the prior art. In the prior art, a lower-level scheduling system server (hereinafter referred to as a scheduling server) is connected with a higher-level scheduling server step by step to form a tree-like connection graph taking a top-level scheduling server as a root node. For example, the primary scheduling server is connected with two secondary scheduling servers, and the secondary scheduling servers are respectively connected with the tertiary scheduling server. The calling of the client is transmitted from the superior dispatching server to the subordinate dispatching server step by step, thereby realizing the cross-step and multi-level dispatching. For example, a first terminal initiates a call to a second terminal under a third-level scheduling server, the call is forwarded from a first-level scheduling server to a second-level scheduling server, the call is forwarded to the third-level scheduling server by the second-level scheduling server, and the call is initiated to the second terminal by the third-level scheduling server. In the call scheduling method and system in the prior art, the call initiated by the terminal needs to be transferred layer by layer in the scheduling server of the middle hierarchy, thereby reducing the communication quality and increasing the data processing delay. If the scheduling server of the middle hierarchy fails, the upper scheduling server and the lower scheduling server cannot realize the scheduling function, resulting in call failure. Therefore, the method provided by the prior art has the defects of low call quality, long data processing delay and low reliability.
Disclosure of Invention
The embodiment of the invention provides a distributed multi-stage scheduling method and equipment, which can improve the flexibility and reliability of scheduling, improve the call quality and reduce the data processing delay.
In a first aspect, an embodiment of the present invention provides a method for distributed multi-level scheduling, where the method includes: acquiring system information of a partner scheduling server, and storing the system information; the system information comprises a system identifier and an access address of a partner scheduling server; the partner scheduling server is a scheduling server in the same wide area network as the first scheduling server; receiving a call request of a terminal; acquiring a system identifier contained in the call request, and judging whether the system identifier is the same as the system identifier of the first scheduling server or not; if not, according to the stored system information, obtaining an access address of the dispatching server matched with the system identifier, and sending the call request to the dispatching server matched with the system identifier according to the access address.
In some embodiments, the method further comprises: sending system information of the first scheduling server to a multicast address of the wide area network; the system information includes a system identification and an access address of the first scheduling server.
In some embodiments, the obtaining the system information of the partner scheduling server includes: receiving multicast information, and acquiring system information of a partner scheduling server contained in the multicast information; wherein the multicast information is sent by a partner scheduling server to a multicast address of the wide area network.
In some embodiments, the obtaining the system information of the partner scheduling server includes: acquiring an access address of a partner scheduling server from the stored system information; sending a system information exchange request to the partner scheduling server according to the access address; and receiving system information sent by the partner scheduling server, wherein the system information is the system information of other partner scheduling servers stored by the partner scheduling server.
In some embodiments, the method further comprises: and sending the system information of other partner scheduling servers saved by the first scheduling server to a partner scheduling server.
In some embodiments, the method further comprises: and sending a report message to a second scheduling server according to the stored system information and the system identifier and the access address of the second scheduling server, wherein the report message at least comprises the access address of the first scheduling server.
In a second aspect, an embodiment of the present invention provides a scheduling server device, where the scheduling server device includes: the acquisition module is used for acquiring system information of a partner scheduling server; the system information comprises a system identifier and an access address of a partner scheduling server; the partner scheduling server is a scheduling server in the same wide area network as the first scheduling server; the storage module is used for storing the system information of the partner scheduling server; the receiving module is used for receiving a call request of a terminal; the judging module is used for acquiring a system identifier contained in the call request and judging whether the system identifier is the same as the system identifier of the first scheduling server or not; and the sending module is used for acquiring the access address of the dispatching server matched with the system identifier according to the system information stored by the storage module if the calling request is different from the calling request, and sending the calling request to the dispatching server matched with the system identifier according to the access address.
In some embodiments, the sending module is further configured to: sending system information of the first scheduling server to a multicast address of the wide area network; the system information includes a system identification and an access address of the first scheduling server.
In some embodiments, the obtaining module is specifically configured to:
receiving multicast information, and acquiring system information of a partner scheduling server contained in the multicast information; wherein the multicast information is sent by a partner scheduling server to a multicast address of the wide area network.
In some embodiments, the obtaining module is specifically configured to: acquiring an access address of a partner scheduling server from the stored system information; sending a system information exchange request to the partner scheduling server according to the access address; and receiving system information sent by the partner scheduling server, wherein the system information is the system information of other partner scheduling servers stored by the partner scheduling server.
In some embodiments, the sending module is further configured to: and sending the system information of other partner scheduling servers saved by the first scheduling server to a partner scheduling server.
In some embodiments, the sending module is further configured to: and sending a report message to a second scheduling server according to the stored system information and the system identifier and the access address of the second scheduling server, wherein the report message at least comprises the access address of the first scheduling server.
In a third aspect, an embodiment of the present invention provides an apparatus for distributed multi-level scheduling, comprising a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs configured to be executed by the one or more processors include instructions for: acquiring system information of a partner scheduling server, and storing the system information; the system information comprises a system identifier and an access address of a partner scheduling server; the partner scheduling server is a scheduling server in the same wide area network as the first scheduling server; receiving a call request of a terminal; acquiring a system identifier contained in the call request, and judging whether the system identifier is the same as the system identifier of the first scheduling server or not; if not, according to the stored system information, obtaining an access address of the dispatching server matched with the system identifier, and sending the call request to the dispatching server matched with the system identifier according to the access address.
In some embodiments, the processor is further specifically configured to execute the one or more programs including instructions for: sending system information of the first scheduling server to a multicast address of the wide area network; the system information includes a system identification and an access address of the first scheduling server.
In some embodiments, the processor is further specifically configured to execute the one or more programs including instructions for: receiving multicast information, and acquiring system information of a partner scheduling server contained in the multicast information; wherein the multicast information is sent by a partner scheduling server to a multicast address of the wide area network.
In some embodiments, the processor is further specifically configured to execute the one or more programs including instructions for: acquiring an access address of a partner scheduling server from the stored system information; sending a system information exchange request to the partner scheduling server according to the access address; and receiving system information sent by the partner scheduling server, wherein the system information is the system information of other partner scheduling servers stored by the partner scheduling server.
In some embodiments, the processor is further specifically configured to execute the one or more programs including instructions for: and sending the system information of other partner scheduling servers saved by the first scheduling server to a partner scheduling server.
In some embodiments, the processor is further specifically configured to execute the one or more programs including instructions for: and sending a report message to a second scheduling server according to the stored system information and the system identifier and the access address of the second scheduling server, wherein the report message at least comprises the access address of the first scheduling server.
According to the distributed multi-level scheduling method and device provided by the embodiment of the invention, the scheduling server can acquire the system information of the partner scheduling server in the same wide area network as the scheduling server, and store the system information. When a call request is received, the call request can be sent to a dispatching server matched with the system identifier according to the system identifier contained in the call request, so that direct dispatching of an upper-layer dispatching server and a lower-layer dispatching server is realized, data processing delay is reduced, and the conversation quality is improved. In addition, because the dispatching server of the invention stores the system information of each partner dispatching server, the upper layer dispatching server and the lower layer dispatching server can directly interact, the fault of any one-level dispatching server does not influence the dispatching call between the upper and lower dispatching servers, thereby improving the reliability and flexibility of dispatching.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic diagram of a prior art dispatch system;
fig. 2 is a server connection topology diagram of a scheduling system according to an embodiment of the present invention;
fig. 3 is a flowchart of a distributed multi-level scheduling method according to an embodiment of the present invention;
fig. 4 is a schematic diagram of an implementation manner of adding a scheduling server to an overlay network according to an embodiment of the present invention;
fig. 5 is a schematic diagram illustrating another implementation manner of joining an overlay network by a scheduling server according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a distributed multi-level scheduling method according to another embodiment of the present invention;
fig. 7 is a schematic diagram of a dispatch server device according to an embodiment of the present invention;
fig. 8 is a schematic diagram of a distributed multi-level scheduling apparatus according to an embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a distributed multi-stage scheduling method and equipment, which can improve the flexibility and reliability of scheduling, improve the call quality and reduce the data processing delay.
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 2, a connection topology diagram of a scheduling system server provided in the embodiment of the present invention is shown. In the embodiment of the invention, each scheduling server and the scheduling server in the same wide area network are partner scheduling servers, and a plurality of scheduling servers form a scheduling system which is in a peer-to-peer network structure. The dispatch server may join the overlay network of the dispatch system by multicasting system information over the wide area network and exchanging system information with partner dispatch servers. As shown in fig. 2, the logistics link topology in the overlay network is a peer-to-peer network structure, a logical tree structure is formed on the service logic, and each scheduling server and the scheduling server in the same wan are partner scheduling servers. Any scheduling server can directly initiate scheduling services such as individual calling/group calling and the like to a subordinate scheduling server through the unique system identification of each scheduling server. As shown in fig. 2, the primary scheduling server may be connected to the secondary scheduling server, or may be directly connected to the tertiary scheduling server.
The distributed multi-level scheduling method is described below with reference to fig. 3 to 6.
Referring to fig. 3, a flowchart of a method for distributed multi-level scheduling according to an embodiment of the present invention is shown, where the method is applied to a first scheduling server, and may include:
s301, the first scheduling server acquires system information of a partner scheduling server and stores the system information; the system information comprises a system identifier and an access address of a partner scheduling server; the partner scheduling server is a scheduling server in the same wide area network as the first scheduling server.
In some embodiments, after the first scheduling server is started, the system information of the first scheduling server may be sent to a wide area network multicast address where the first scheduling server is located at regular time. The system information includes a system identification and an access address of the first scheduling server. Therefore, other scheduling servers which are positioned in the same wide area network and receive the multicast information can acquire the system information of the first scheduling server and store the system information.
In some embodiments, the first scheduling server obtaining the system information of the partner scheduling server includes: receiving multicast information, and acquiring system information of a partner scheduling server contained in the multicast information; wherein the multicast information is sent by a partner scheduling server to a multicast address of the wide area network. For example, the first scheduling server may listen to a multicast address, and store the system information of the partner scheduling server included in the received multicast information to the local.
Referring to fig. 4, a schematic diagram of an implementation manner of adding a scheduling server to an overlay network according to an embodiment of the present invention is provided. Taking fig. 4 as an example, after the first scheduling server is started, the first scheduling server may send multicast information at regular time, and send local system information at regular time to the multicast address, so that other scheduling servers receiving the multicast information may obtain and store the system information of the first scheduling server. The system information may include, for example, a system identification and an access address of the first dispatch server. And the first scheduling server monitors the multicast address at the same time and judges whether multicast information is received or not. And if the multicast information is received, saving the system information of the partner scheduling server contained in the multicast information into a local system information list. The local system information list may be a hash table indexed by system identification (system ID). Of course, other forms are possible, and are not limited herein.
In some embodiments, the obtaining the system information of the partner scheduling server includes: acquiring an access address of a partner scheduling server from the stored system information; sending a system information exchange request to the partner scheduling server according to the access address; and receiving system information sent by the partner scheduling server, wherein the system information is the system information of other partner scheduling servers stored by the partner scheduling server. For example, the first dispatch server may periodically interact with the partner system via a chat (gossip) protocol for respective system information. The gossip protocol is a way of easily communicating with other networks of the network and interacting information through timing. For example, the system information stored by the first scheduling server includes system information of the second scheduling server, the third scheduling server, and the fourth scheduling server. Then, it may acquire the access addresses of the second scheduling server, the third scheduling server, and the fourth scheduling server, and send system information exchange requests to the second scheduling server, the third scheduling server, and the fourth scheduling server, respectively, to request the scheduling servers to exchange system information therewith. Taking the second scheduling server as an example, assuming that the system information stored by the second scheduling server includes the system information of the first scheduling server, the fifth scheduling server and the sixth scheduling server, after receiving the system information exchange request, the system information may be sent to the first scheduling server. The first dispatch server may update the local system information using the system information, such that the first dispatch server adds the system information of the fifth dispatch server and the sixth dispatch server.
In some embodiments, the first scheduling server may also send system information of other partner scheduling servers saved by the first scheduling server to a partner scheduling server. It should be noted that, the first scheduling server may actively send the local system information to the partner scheduling server through the gossip protocol, or may send the local system information to the partner scheduling server in response to a system information exchange request of the partner scheduling server.
The description will be given by taking fig. 5 as an example. Referring to fig. 5, a schematic diagram of another implementation manner of adding a scheduling server to an overlay network according to an embodiment of the present invention is provided. After the first scheduling server is started, the system information of the partner scheduling server can be read from the configuration file and added into the local system information list. The first dispatch server may exchange system information with the partner dispatch server via gossip protocol timing. For example, the first scheduling server sends a system information exchange request to the partner scheduling server at regular time to request the system information list stored by the partner scheduling server. And the first scheduling server stores the received system information list sent by the partner scheduling server into a local system information list so as to update the local system information list. And the first scheduling server sends all the stored local system information lists to the partner scheduling server.
Through the mode, the scheduling server can acquire the system information of other scheduling servers.
S302, the first dispatching server receives a call request of the terminal.
For example, the first dispatch server may be a primary dispatch server. The call request contains a system identification of the dispatch server.
S303, the first dispatching server obtains the system identifier contained in the call request, and judges whether the system identifier is the same as the system identifier of the first dispatching server.
In specific implementation, each scheduling server has a unique system identifier. When receiving the terminal call, the first dispatch server may determine whether the terminal call is a local call through the system identifier included in the call request, that is, determine whether the system identifier included in the call request is the same as the local system identifier. If the call is the same as the call, the call is forwarded to the call opposite terminal.
S304, if the system information is different, the first dispatching server acquires the access address of the dispatching server matched with the system identifier according to the stored system information, and sends the calling request to the dispatching server matched with the system identifier according to the access address.
Since the first dispatch server maintains system information for other partner dispatch servers. Therefore, the system information corresponding to the system identifier can be retrieved through the system identifier corresponding to the call request. And further, acquiring an access address of the dispatching server matched with the system identifier, and sending the call request to the dispatching server matched with the system identifier according to the access address.
In some embodiments, the method further comprises: and sending a report message to a second scheduling server according to the stored system information and the system identifier and the access address of the second scheduling server, wherein the report message at least comprises the access address of the first scheduling server.
In order to facilitate those skilled in the art to more clearly understand the embodiments of the present application in a specific context, the following describes the embodiments of the present application with a specific example. It should be noted that the specific example is only to make the present invention more clearly understood by those skilled in the art, but the embodiments of the present invention are not limited to the specific example.
Referring to fig. 6, a signaling flow diagram of distributed multi-level scheduling according to an embodiment of the present invention is provided. In fig. 6, the numbers of the steps are not shown, and the scheduling system in the figure may also be referred to as a scheduling system server or a scheduling server.
S601, the client sends a call request.
For example, the client initiates a call to terminal 811021 under the primary and tertiary dispatch systems 101. Wherein the call request contains a system identification of the three-level dispatch system 101.
S602, after receiving the call request, the primary scheduling system 001 retrieves the system information list, obtains the system information corresponding to the system ID of the call request, and determines that the call target is the tertiary scheduling system 101.
S603, the primary dispatching system 001 sends the call request to the tertiary dispatching system 101 according to the system information of the tertiary dispatching system 101.
S604, the third-level dispatching system 101 initiates a call to the terminal 811021 after receiving the call request.
And S605, the third-level dispatching system 101 replies a call response to the first-level dispatching system 001.
S606, the primary scheduling system 001 replies the call response to the client.
As can be seen from the example shown in fig. 6, after receiving a call from a client to the terminal 811021 under the third-level scheduling system 101, the first-level scheduling system 001 may determine information of the third-level scheduling system corresponding to the call by retrieving the local system information list, and forward the call. In this example, the first-level dispatch system directly forwards the call to the third-level dispatch system, thereby realizing the cross-level call. And the secondary scheduling system does not participate in the whole process. Therefore, data processing time delay can be reduced, the call quality is improved, and the flexibility and the reliability of scheduling are improved.
The following describes a device corresponding to the method provided by the embodiment of the present invention.
Referring to fig. 7, a schematic diagram of a dispatch server device according to an embodiment of the present invention is provided. The apparatus may include:
an obtaining module 701, configured to obtain system information of a partner scheduling server; the system information comprises a system identifier and an access address of a partner scheduling server; the partner scheduling server is a scheduling server in the same wide area network as the first scheduling server.
A saving module 702, configured to save the system information of the partner scheduling server.
A receiving module 703, configured to receive a call request of a terminal.
A determining module 704, configured to obtain a system identifier included in the call request, and determine whether the system identifier is the same as the system identifier of the first scheduling server.
A sending module 705, configured to, if the system information is different from the system identifier stored in the storing module, obtain an access address of the scheduling server matched with the system identifier according to the system information stored in the storing module, and send the call request to the scheduling server matched with the system identifier according to the access address.
In some embodiments, the sending module 705 is further configured to: sending system information of the first scheduling server to a multicast address of the wide area network; the system information includes a system identification and an access address of the first scheduling server.
In some embodiments, the obtaining module 701 is specifically configured to:
receiving multicast information, and acquiring system information of a partner scheduling server contained in the multicast information; wherein the multicast information is sent by a partner scheduling server to a multicast address of the wide area network.
In some embodiments, the obtaining module 701 is specifically configured to: acquiring an access address of a partner scheduling server from the stored system information; sending a system information exchange request to the partner scheduling server according to the access address; and receiving system information sent by the partner scheduling server, wherein the system information is the system information of other partner scheduling servers stored by the partner scheduling server.
In some embodiments, the sending module 705 is further configured to: and sending the system information of other partner scheduling servers saved by the first scheduling server to a partner scheduling server.
In some embodiments, the sending module 705 is further configured to: and sending a report message to a second scheduling server according to the stored system information and the system identifier and the access address of the second scheduling server, wherein the report message at least comprises the access address of the first scheduling server.
Referring to fig. 8, a block diagram of a data communication device according to another embodiment of the present invention is shown. The method comprises the following steps: at least one processor 801 (e.g., CPU), memory 802, and at least one communication bus 803 for enabling communications among the devices. The processor 801 is used to execute executable modules, such as computer programs, stored in the memory 802. The Memory 802 may comprise a high-speed Random Access Memory (RAM) and may further comprise a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. One or more programs are stored in the memory and configured to be executed by the one or more processors 801 include instructions for:
acquiring system information of a partner scheduling server, and storing the system information; the system information comprises a system identifier and an access address of a partner scheduling server; the partner scheduling server is a scheduling server in the same wide area network as the first scheduling server; receiving a call request of a terminal; acquiring a system identifier contained in the call request, and judging whether the system identifier is the same as the system identifier of the first scheduling server or not; if not, according to the stored system information, obtaining an access address of the dispatching server matched with the system identifier, and sending the call request to the dispatching server matched with the system identifier according to the access address.
In some embodiments, the processor 801 is specifically configured to execute the one or more programs including instructions for: sending system information of the first scheduling server to a multicast address of the wide area network; the system information includes a system identification and an access address of the first scheduling server.
In some embodiments, the processor 801 is further specifically configured to execute the one or more programs including instructions for: receiving multicast information, and acquiring system information of a partner scheduling server contained in the multicast information; wherein the multicast information is sent by a partner scheduling server to a multicast address of the wide area network.
In some embodiments, the processor 801 is further specifically configured to execute the one or more programs including instructions for: acquiring an access address of a partner scheduling server from the stored system information; sending a system information exchange request to the partner scheduling server according to the access address; and receiving system information sent by the partner scheduling server, wherein the system information is the system information of other partner scheduling servers stored by the partner scheduling server.
In some embodiments, the processor 801 is further specifically configured to execute the one or more programs including instructions for: and sending the system information of other partner scheduling servers saved by the first scheduling server to a partner scheduling server.
In some embodiments, the processor 801 is further specifically configured to execute the one or more programs including instructions for: and sending a report message to a second scheduling server according to the stored system information and the system identifier and the access address of the second scheduling server, wherein the report message at least comprises the access address of the first scheduling server.
The arrangement of each unit or module of the device of the present invention can be implemented by referring to the methods shown in fig. 3 to 6, which are not described herein again.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It will be understood that the invention 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 invention is only limited by the appended claims
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element. The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described device embodiments are merely illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort. The foregoing is directed to embodiments of the present invention, and it is understood that various modifications and improvements can be made by those skilled in the art without departing from the spirit of the invention.
Claims (12)
1. A distributed multi-level scheduling method applied to a first scheduling server, the method comprising:
acquiring system information of a partner scheduling server, and storing the system information; the system information comprises a system identifier and an access address of a partner scheduling server; the partner scheduling server is a scheduling server in the same wide area network as the first scheduling server;
receiving a call request of a terminal;
acquiring a system identifier contained in the call request, and judging whether the system identifier is the same as the system identifier of the first scheduling server or not;
if not, according to the stored system information, obtaining an access address of the dispatching server matched with the system identifier, and sending the call request to the dispatching server matched with the system identifier according to the access address.
2. The method of claim 1, further comprising:
sending system information of the first scheduling server to a multicast address of the wide area network; the system information includes a system identification and an access address of the first scheduling server.
3. The method of claim 1 or 2, wherein the obtaining system information of the partner scheduling server comprises:
receiving multicast information, and acquiring system information of a partner scheduling server contained in the multicast information; wherein the multicast information is sent by a partner scheduling server to a multicast address of the wide area network.
4. The method of claim 1, wherein obtaining system information of a partner dispatch server comprises:
acquiring an access address of a partner scheduling server from the stored system information;
sending a system information exchange request to the partner scheduling server according to the access address;
and receiving system information sent by the partner scheduling server, wherein the system information is the system information of other partner scheduling servers stored by the partner scheduling server.
5. The method of claim 1, further comprising:
and sending the system information of other partner scheduling servers saved by the first scheduling server to a partner scheduling server.
6. The method of claim 1, further comprising:
and sending a report message to a second scheduling server according to the stored system information and the system identifier and the access address of the second scheduling server, wherein the report message at least comprises the access address of the first scheduling server.
7. A dispatch server apparatus, the apparatus comprising:
the acquisition module is used for acquiring system information of a partner scheduling server; the system information comprises a system identifier and an access address of a partner scheduling server; the partner scheduling server is a scheduling server which is in the same wide area network as the first scheduling server;
the storage module is used for storing the system information of the partner scheduling server;
the receiving module is used for receiving a call request of a terminal;
the judging module is used for acquiring a system identifier contained in the call request and judging whether the system identifier is the same as the system identifier of the first scheduling server or not;
and the sending module is used for acquiring the access address of the dispatching server matched with the system identifier according to the system information stored by the storage module if the calling request is different from the calling request, and sending the calling request to the dispatching server matched with the system identifier according to the access address.
8. The device of claim 7, wherein the sending module is further configured to:
sending system information of the first scheduling server to a multicast address of the wide area network; the system information includes a system identification and an access address of the first scheduling server.
9. The device of claim 7, wherein the obtaining module is specifically configured to:
receiving multicast information, and acquiring system information of a partner scheduling server contained in the multicast information; wherein the multicast information is sent by a partner scheduling server to a multicast address of the wide area network.
10. The device of claim 7, wherein the obtaining module is specifically configured to:
acquiring an access address of a partner scheduling server from the stored system information; sending a system information exchange request to the partner scheduling server according to the access address; and receiving system information sent by the partner scheduling server, wherein the system information is the system information of other partner scheduling servers stored by the partner scheduling server.
11. The device of claim 7, wherein the sending module is further configured to:
and sending the system information of other partner scheduling servers saved by the first scheduling server to a partner scheduling server.
12. An apparatus for distributed multi-level scheduling, comprising a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for:
acquiring system information of a partner scheduling server, and storing the system information; the system information comprises a system identifier and an access address of a partner scheduling server; the partner scheduling server is a scheduling server which is in the same wide area network as the first scheduling server;
receiving a call request of a terminal;
acquiring a system identifier contained in the call request, and judging whether the system identifier is the same as the system identifier of the first scheduling server or not;
if not, according to the stored system information, obtaining an access address of the dispatching server matched with the system identifier, and sending the call request to the dispatching server matched with the system identifier according to the access address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611037399.6A CN108093147B (en) | 2016-11-23 | 2016-11-23 | Distributed multi-stage scheduling method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611037399.6A CN108093147B (en) | 2016-11-23 | 2016-11-23 | Distributed multi-stage scheduling method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108093147A CN108093147A (en) | 2018-05-29 |
| CN108093147B true CN108093147B (en) | 2020-09-25 |
Family
ID=62168662
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611037399.6A Active CN108093147B (en) | 2016-11-23 | 2016-11-23 | Distributed multi-stage scheduling method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108093147B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113645251B (en) * | 2021-08-24 | 2023-05-23 | 北京英创思信息技术有限公司 | Data transmission method and device suitable for cross-regional service |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008019540A1 (en) * | 2006-08-11 | 2008-02-21 | Zte Corporation | Method for realizing route based on position in digital trunked call |
| CN101150786A (en) * | 2006-09-19 | 2008-03-26 | 大唐移动通信设备有限公司 | Cluster communication network system and call method based on this system |
| CN101228736A (en) * | 2005-12-28 | 2008-07-23 | 中兴通讯股份有限公司 | Connecting and controlling method and device for automatically exchanging optical network multicast business |
| CN102480425A (en) * | 2010-11-30 | 2012-05-30 | 中兴通讯股份有限公司 | Method and system for message router in peer-to-peer (P2P) network |
| CN103166922A (en) * | 2011-12-12 | 2013-06-19 | 中国移动通信集团公司 | Call request processing method, system and device in peer to peer overlay network |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8938498B2 (en) * | 2009-04-03 | 2015-01-20 | Qualcomm Incorporated | Uninterruptable group communication sessions within a wireless communications system |
-
2016
- 2016-11-23 CN CN201611037399.6A patent/CN108093147B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101228736A (en) * | 2005-12-28 | 2008-07-23 | 中兴通讯股份有限公司 | Connecting and controlling method and device for automatically exchanging optical network multicast business |
| WO2008019540A1 (en) * | 2006-08-11 | 2008-02-21 | Zte Corporation | Method for realizing route based on position in digital trunked call |
| CN101150786A (en) * | 2006-09-19 | 2008-03-26 | 大唐移动通信设备有限公司 | Cluster communication network system and call method based on this system |
| CN102480425A (en) * | 2010-11-30 | 2012-05-30 | 中兴通讯股份有限公司 | Method and system for message router in peer-to-peer (P2P) network |
| CN103166922A (en) * | 2011-12-12 | 2013-06-19 | 中国移动通信集团公司 | Call request processing method, system and device in peer to peer overlay network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108093147A (en) | 2018-05-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109618005B (en) | Method for calling server and proxy server | |
| US8838703B2 (en) | Method and system for message processing | |
| US9535805B2 (en) | Resilient routing for session initiation protocol based communication systems | |
| US8155672B2 (en) | Scalable geo-location event processing | |
| CN110971698B (en) | Data forwarding system, method and device | |
| US20130254415A1 (en) | Routing requests over a network | |
| CN101447989B (en) | System and method for an improved high availability component implementation | |
| CN108062243B (en) | Execution plan generation method, task execution method and device | |
| CN113727464B (en) | Method and device for establishing high concurrent call of SIP streaming media server | |
| CN103475566A (en) | Real-time message exchange platform and distributed cluster establishment method | |
| CN104509073A (en) | Discovering ip multicast group memberships in software defined networks | |
| CN107689878A (en) | TCP length connection SiteServer LBSs based on name scheduling | |
| CN104811371A (en) | Brand-new instant messaging system | |
| CN113259423B (en) | Method and device for client networking access in P2P system | |
| CN114338063B (en) | Message queue system, service processing method and computer readable storage medium | |
| CN111935314B (en) | Block chain system, message transmission method and device | |
| CN106210058A (en) | A kind of reverse proxy method of multi-core parallel concurrent | |
| CN106970843B (en) | Remote calling method and device | |
| US8514840B2 (en) | Call distribution in a direct-communication network | |
| CN108093147B (en) | Distributed multi-stage scheduling method and equipment | |
| CN107438098B (en) | Dynamic content distribution method and system | |
| CN110582757A (en) | Intermediate device for network routing of data messages | |
| CN103703745A (en) | Method and apparatus for interconnecting a user agent to a cluster of servers | |
| US8359354B1 (en) | Methods for providing a status to devices in a distributed system | |
| CN115037785B (en) | Instant communication system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |