A multi-server channel flow control method and system under a disaster scenario

Abstract

The application provides a multi-server channel flow control method in a disaster scenario, characterized by comprising: acquiring different types of incoming calls; performing scene type determination on the incoming calls; wherein the scene types include a normal scene and a disaster scene, the normal scene is a scene before a disaster occurs, and the disaster scene is a scene after the disaster occurs; performing communication scheduling according to the scene types; wherein when the scene type is the normal scene, normal scene communication scheduling is performed, and when the scene type is the disaster scene, disaster scene communication scheduling is performed; performing communication channel allocation and flow priority control to obtain a backup channel number. Through the above technical solution, the urgency of service transmission in the system can be accurately evaluated, the number of backup channels can be accurately estimated, channel scheduling and flow priority allocation when a disaster event occurs can be better realized, and a backup channel can be quickly assisted to restore communication in a disaster area.

Description

Technical Field

[0001] This invention relates to the field of channel scheduling technology, and specifically to a multi-server channel traffic control method and system in disaster scenarios. Background Technology

[0002] Catastrophic events, such as tsunamis and earthquakes, have a tremendous impact on communication networks. When a catastrophic event occurs, all active and waiting clients or traffic are forced to abruptly exit the system, rendering it inoperable. To cope with the impact of sudden catastrophic events on communication networks, research on channel scheduling and traffic priority allocation in catastrophic queuing models is crucial for improving network communication efficiency. Currently, various priority strategies have been proposed, such as channel protection strategies, threshold strategies, preemptive priority strategies, and non-preemptive priority strategies. However, these strategies have limited applicability to catastrophic queuing model scenarios because they cannot address the suddenness and correlation characteristics of incoming information flows.

[0003] Therefore, considering more reasonable models to describe channel scheduling and traffic prioritization in catastrophic queuing models can help allocate more reasonable importance to different types of services (such as video, voice, image, data, etc.) in application scenarios, thereby improving system service efficiency. Summary of the Invention

[0004] In view of this, this invention proposes a multi-server channel flow control method and system for disaster scenarios. A multi-server disaster retry queuing model is constructed based on a phase-type (PH) distribution of retry counts and a preemptive repetition priority strategy. This model divides the communication system operation into normal / disaster scenarios, using a more general Markovian Arrival Process (MMAP) and PH distribution to describe the arrival and service processes of all types of incoming calls, respectively. By proving that the Markov chain satisfies asymptotically quasi-Toeplitz Markov chains (AQTMC), the proposed model accurately simulates the disaster retry queuing process based on a level-dependent quasi-birth-death (LDQBD) process. Furthermore, the traversal conditions of the basic Markov chain are obtained, and a multi-objective optimization problem is formulated using the non-dominated sorted genetic algorithm-II (NSGA-II) method to obtain the optimal number of backup channels.

[0005] According to one aspect of the present invention, a multi-server channel traffic control method in a disaster scenario is provided, characterized by comprising: S101: acquiring different types of incoming calls; S102: determining the scenario type of the incoming calls; wherein the scenario type includes normal scenarios and disaster scenarios, the normal scenario being the situation before the disaster occurs, and the disaster scenario being the situation after the disaster occurs; S103: performing communication scheduling for the scenario type; wherein, when the scenario type is the normal scenario, normal scenario communication scheduling is performed, and when the scenario type is the disaster scenario, disaster scenario communication scheduling is performed; S104: performing communication channel allocation and traffic priority control to obtain the number of backup channels.

[0006] Further, the normal scenario communication scheduling includes: S103.11: determining the type of the incoming call, whether it is a new call or a switching call; S103.12: when the call type is a new call and all channels are occupied when it arrives, the new call is added to a channel with unlimited capacity and a retry service is initiated; S103.13: when the call type is a switching call and all channels are occupied when it arrives, the switching call is lost.

[0007] Further, the disaster scenario communication scheduling includes: S103.21: determining the type of the incoming call, which is a handover call, a new call, or an emergency call; S103.22: if the call type is an emergency call and all channels are occupied only by emergency calls, then the arriving emergency call is lost; S103.23: if the call type is an emergency call and all channels are occupied only by handover calls, then the emergency call will preempt the service of the handover call and start service at its location; S103.24: if the call type is an emergency call and all channels are occupied and at least one call is occupied by a new call, then the emergency call will preempt the service of the new call and start service at its location.

[0008] Furthermore, S104 also includes: obtaining the total number of backup channels based on a multi-objective optimization strategy, calculated using the following formula:

[0009]

[0010] Where S represents the total number of channels, K represents the total number of backup channels, and λ ε and μ ε P represents the average arrival rate and average service rate of emergency calls, respectively. ε , as well as These represent the blocking probability of emergency calls, the blocking probability of new calls / handover calls, and the preemption probability of emergency calls, respectively. ∈1, ∈2, and ∈3 represent probability thresholds that are adjustable based on network size and performance, and their values ​​range from 0 to 1.

[0011] According to a second aspect of the present invention, a multi-server channel traffic control system for disaster scenarios is provided, comprising: an acquisition module for acquiring different types of incoming calls; a determination module connected to the acquisition module for determining the scenario type of the incoming calls; wherein the scenario type includes normal scenarios and disaster scenarios, the normal scenario being the situation before a disaster occurs, and the disaster scenario being the situation after a disaster occurs; a scheduling module connected to the determination module for performing communication scheduling based on the scenario type; wherein when the scenario type is the normal scenario, normal scenario communication scheduling is performed, and when the scenario type is the disaster scenario, disaster scenario communication scheduling is performed; and a control module connected to the scheduling module for communication channel allocation and traffic priority control, and obtaining the number of backup channels.

[0012] Furthermore, the normal scenario communication scheduling includes: determining the type of the incoming call, whether it is a new call or a switching call; when the call type is a new call and all channels are occupied upon arrival, the new call is added to a channel with unlimited capacity and a retry service is initiated; and when the call type is a switching call and all channels are occupied upon arrival, the switching call is lost.

[0013] Furthermore, the disaster scenario communication scheduling includes: determining the type of the incoming call, which is a handover call, a new call, or an emergency call; if the call type is an emergency call and all channels are occupied only by the emergency call, then the arriving emergency call is lost; if the call type is an emergency call and all channels are occupied only by the handover call, then the emergency call will preempt the service of the handover call and start service at its location; and if the call type is an emergency call and all channels are occupied and at least one call is occupied by a new call, then the emergency call will preempt the service of the new call and start service at its location.

[0014] Furthermore, the control module is also used to: obtain the total number of backup channels based on a multi-objective optimization strategy, calculated using the following formula:

[0015]

[0016] Where S represents the total number of channels, K represents the total number of backup channels, and λ ε and μ ε P represents the average arrival rate and average service rate of emergency calls, respectively. ε , as well as These represent the blocking probability of emergency calls, the blocking probability of new calls / handover calls, and the preemption probability of emergency calls, respectively. ∈1, ∈2, and ∈3 represent probability thresholds that are adjustable based on network size and performance, and their values ​​range from 0 to 1.

[0017] This invention addresses the shortcomings of existing technologies by proposing a multi-server disaster queuing model for channel scheduling. This model effectively addresses the burstiness and correlation characteristics of incoming information flows, avoids overestimating or underestimating system performance, and can simultaneously handle three types of incoming calls: handover calls, new calls, and emergency calls. Furthermore, this model can reasonably assess the urgency of service transmissions in the system and accurately estimate the number of backup channels, thereby better enabling channel scheduling and traffic priority allocation in communication networks during disaster events. When a disaster occurs, it can quickly assist in constructing backup channels for restoring communication in the affected areas.

[0018] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, the preferred embodiments of the present invention are described in detail below with reference to the accompanying drawings. Attached Figure Description

[0019] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings:

[0020] Figure 1 A flowchart of the method of the present invention is shown.

[0021] Figure 2 A system block diagram of the present invention is shown. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this invention, and not all of them. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0023] First, combine Figure 1 The process of this invention is explained. For example... Figure 1As shown, a multi-server channel traffic control method in a disaster scenario includes: S101: acquiring different types of incoming calls; S102: determining the scenario type of the incoming calls; wherein, the scenario type includes normal scenarios and disaster scenarios, the normal scenario being the situation before the disaster occurs, and the disaster scenario being the situation after the disaster occurs; S103: performing communication scheduling for the scenario type; wherein, when the scenario type is the normal scenario, normal scenario communication scheduling is performed, and when the scenario type is the disaster scenario, disaster scenario communication scheduling is performed; S104: ending the scheduling, completing communication channel allocation and traffic priority control, and obtaining the number of backup channels.

[0024] The above methods will be discussed in detail below.

[0025] S101: Obtain different types of incoming calls.

[0026] S is defined as the total number of channels in the system, which responds when there is an incoming call or a call in the communication system.

[0027] S102: Determine the scenario type for the incoming call.

[0028] The scenario types include normal scenarios and disaster scenarios. Normal scenarios refer to the situation before a disaster occurs, while disaster scenarios refer to the situation after a disaster occurs. Under normal circumstances, the system will provide service to all incoming calls; however, in a disaster scenario, the system will crash, clearing all active and pending calls.

[0029] Catastrophic queuing models are a driving force in cutting-edge wireless technologies, particularly in communications and cellular networks. In this type of catastrophic queuing model, different categories of services (e.g., video, voice, image, data, etc.) are assigned different importance categories, and their services are thus implemented according to appropriate prioritization strategies.

[0030] This invention utilizes a multi-server catastrophic retry queuing model based on a phase-type (PH) distribution of retry counts and a preemptive repetition priority strategy to determine the scenario type. The model categorizes communication system operation into normal and catastrophic scenarios, using a more generalized Markovian Arrival Process (MMAP) and PH distribution to describe the arrival and service processes of all types of incoming calls. By proving that the Markov chain satisfies asymptotically quasi-Toeplitz Markov chains (AQTMC), the proposed model accurately simulates the catastrophic retry queuing process based on a level-dependent quasi-birth-death (LDQBD) process.

[0031] S103: Perform communication scheduling for the aforementioned scenario type.

[0032] When the scenario type is the normal scenario, normal scenario communication scheduling is performed; when the scenario type is the disaster scenario, disaster scenario communication scheduling is performed.

[0033] Normal scenario communication scheduling includes: determining the type of incoming call, whether it is a new call or a switching call; if the call type is a new call and all channels are occupied when it arrives, the new call is added to a channel with unlimited capacity and a retry service is initiated; if the call type is a switching call and all channels are occupied when it arrives, the switching call is lost.

[0034] In a normal scenario, incoming heterogeneous calls are classified into two categories (k=2): handover calls and new calls. These two types of calls have different arrival and service procedures, following MMAP and PH distributions respectively, and have different parameters. If all channels are occupied when a new call arrives, the new call will join an infinite-capacity track (virtual space) and is referred to as a retry call. Retry calls after PH distribution can either retry service or exit the system without obtaining service. It is assumed that the retry rate θ is the optimal rate when the number of retry calls l is between 0 and M. lOnce this number exceeds M, the retry rate is considered to be θ. When a handover call arrives at the system and all available channels are occupied, one of two scenarios may occur. In the first scenario, if all channels are occupied by the handover call, the arriving handover call will be lost from the system. In the second scenario, if at least one of the occupied channels is occupied by a new call, the arriving handover call will be given priority over the ongoing new call. The handover call begins its service in place of the preempted new call, and the preempted new call joins the track.

[0035] Disaster scenario communication scheduling includes: determining the type of incoming call, which is a handover call, a new call, or an emergency call; if the call type is an emergency call and all channels are occupied only by emergency calls, the incoming emergency call is lost; if the call type is an emergency call and all channels are occupied only by handover calls, the emergency call will preempt the service of the handover call and start service at its location; if the call type is an emergency call and all channels are occupied and at least one call is occupied by a new call, the emergency call will preempt the service of the new call and start service at its location.

[0036] The proposed model is affected by catastrophic events such as tsunamis and earthquakes. With the occurrence of these catastrophic events, all calls in the system (calls in service and calls waiting for service) leave the system prematurely, rendering the system inactive. Since catastrophic events are inherently sudden, MMAP is an appropriate representation of the disaster arrival phase. Failed channels are repaired immediately after the PH distribution. In this invention, when the entire system collapses and all channels fail, K backup channels will begin providing service at a low rate. Once one of the failed channels is repaired, these backup channels will cease operation. Arriving calls are considered to have been lost from this point until all channels are fixed. The occurrence of a disaster leads to an emergency in the affected area. Therefore, incoming heterogeneous calls are now classified into three categories (k=3): handover calls, new calls, and emergency calls. The arrival and service processes of all types of calls follow MMAP and PH distributions with different parameters, respectively. To provide emergency service in disaster situations, emergency calls should have a general priority. Here, it is assumed that emergency calls are given priority over handover and new calls. When an emergency call arrives at the system, one of the following three scenarios may occur:

[0037] 1. When an arriving emergency call finds that all channels are occupied by emergency calls only, the arriving emergency call will be lost from the system.

[0038] 2. If, at the time of arrival of an emergency call, all channels are occupied by a handover call, the handover call service will be preempted, and the emergency call will begin receiving service in place of the preempted handover call.

[0039] 3. If, at the time of arrival of an emergency call, all channels are occupied and at least one channel is occupied by a new call, the emergency call will preempt the service of the new call and begin service at its location.

[0040] S104: End scheduling, complete communication channel allocation and traffic priority control, and obtain the number of backup channels.

[0041] This section uses the NSGA-II method to formulate a multi-objective optimization problem to obtain the optimal number of backup channels. Details are as follows:

[0042] min K

[0043]

[0044] Where S represents the total number of channels, K represents the total number of backup channels, and λ ε and μ ε P represents the average arrival rate and average service rate of emergency calls, respectively. ε , as well as These represent the blocking probability of emergency calls, the blocking probability of new calls / handover calls, and the preemption probability of emergency calls, respectively. As performance factors characterizing the target network, ∈1, ∈2, and ∈3 represent probability thresholds that are adjustable based on network size and performance, with values ​​ranging from 0 to 1.

[0045] According to another aspect of the present invention, a multi-server channel traffic control system for disaster scenarios is also provided, comprising:

[0046] Acquisition module: Used to acquire different types of incoming calls.

[0047] Determination module: connected to the acquisition module, used to determine the scenario type of the incoming call; wherein, the scenario type includes normal scenario and disaster scenario, the normal scenario is the situation before the disaster occurs, and the disaster scenario is the situation after the disaster occurs.

[0048] Scheduling module: connected to the determination module, used for communication scheduling based on the scenario type; wherein, when the scenario type is the normal scenario, normal scenario communication scheduling is performed, and when the scenario type is the disaster scenario, disaster scenario communication scheduling is performed.

[0049] The normal scenario communication scheduling includes: determining the type of the incoming call, whether it is a new call or a switching call; when the call type is a new call and all channels are occupied when it arrives, the new call is added to a channel with unlimited capacity and a retry service is initiated; and when the call type is a switching call and all channels are occupied when it arrives, the switching call is lost.

[0050] The disaster scenario communication scheduling includes: determining the type of the incoming call, which is a handover call, a new call, or an emergency call; if the call type is an emergency call and all channels are occupied only by emergency calls, the arriving emergency call is lost; if the call type is an emergency call and all channels are occupied only by handover calls, the emergency call will preempt the service of the handover call and start service at its location; and if the call type is an emergency call and all channels are occupied and at least one call is occupied by a new call, the emergency call will preempt the service of the new call and start service at its location.

[0051] Control module: Connected to the scheduling module, used to end scheduling, complete communication channel allocation and traffic priority control, and obtain the number of backup channels.

[0052] The total number of backup channels is obtained based on a multi-objective optimization strategy, and the calculation formula is as follows:

[0053]

[0054] Where S represents the total number of channels, K represents the total number of backup channels, and λ ε and μ ε P represents the average arrival rate and average service rate of emergency calls, respectively. ε , as well as These represent the blocking probability of emergency calls, the blocking probability of new calls / handover calls, and the preemption probability of emergency calls, respectively. ∈1, ∈2, and ∈3 represent probability thresholds that are adjustable based on network size and performance, and their values ​​range from 0 to 1.

[0055] The method proposed in this invention has at least the following significant technical effects: 1) Based on the burstiness and correlation characteristics of the incoming information flow, a more generalized PH distributed retry count is used, so as not to overestimate or underestimate the allocation priority of the system for critical traffic; 2) The proposed multi-server disaster queuing model based on PH distributed retry count and preemptive repeat priority strategy adopts a multi-level partitioning strategy to divide all system incoming calls into normal and disaster scenarios, and defines the three types of incoming calls to be processed as handover calls, new calls, and emergency calls; 3) The solution of the optimal number of backup channels is transformed into a multi-objective optimization problem using the non-dominated sorting genetic algorithm NSGA-II.

[0056] Compared to traditional multi-server disaster queuing models, the multi-server disaster queuing model proposed in this invention, based on PH distributed retries and a preemptive repetitive priority strategy, uses a more universally applicable labeled Markov arrival process to describe channel scheduling and traffic priority control in communication systems during disasters. This model can accurately assess the urgency of service transmissions in the system and accurately estimate the number of backup channels, thereby better realizing channel scheduling and traffic priority allocation in communication networks during disaster events. When a disaster occurs, it can quickly assist in building backup channels for restoring communication in the affected areas.

[0057] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other.

[0058] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Any simple modifications, equivalent changes, and alterations made to the above embodiments based on the technical essence of the present invention shall still fall within the scope of the technical solution of the present invention.

Claims

1. A multi-server channel traffic control method in a disaster scenario, characterized in that, include: S101: Obtain different types of incoming calls; S102: Determine the scenario type of the incoming call; The scenario types include normal scenarios and disaster scenarios. The normal scenario is the situation before a disaster occurs, and the disaster scenario is the situation after a disaster occurs. S103: Perform communication scheduling for the aforementioned scenario type; Specifically, when the scenario type is the normal scenario, normal scenario communication scheduling is performed; when the scenario type is the disaster scenario, disaster scenario communication scheduling is performed. S104: Perform communication channel allocation and traffic priority control to obtain the number of backup channels; S104 further includes: obtaining the total number of backup channels based on a multi-objective optimization strategy, calculated using the following formula: ， in, Indicates the total number of channels. Indicates the total number of backup channels. and These represent the average arrival rate and average service rate of emergency calls, respectively. , as well as These represent the probability of blocking an emergency call, the probability of blocking a new call / handover call, and the probability of preemption for an emergency call, respectively. This represents a probability threshold that is adjustable based on network size and performance, and its value ranges from 0 to 1.

2. The method as described in claim 1, characterized in that, The normal scenario communication scheduling includes: S103.11: Determine the type of the incoming call, whether it is a new call or a switched call; S103.12: When the call type is a new call and all channels are occupied when the call arrives, the new call is added to a channel with unlimited capacity and a retry service is initiated. S103.13: When the call type is a handover call and all channels are occupied when the call arrives, the handover call is lost.

3. The method as described in claim 1, characterized in that, The disaster scenario communication scheduling includes: S103.21: Determine the type of the incoming call, whether it is a switching call, a new call, or an emergency call; S103.22: When the call type is an emergency call and all channels are occupied only by emergency calls, the arriving emergency call is lost; S103.23: When the call type is an emergency call and all channels are occupied only by the handover call, the emergency call will preempt the service of the handover call and start service at its location; S103.24: When the call type is an emergency call and all channels are occupied and at least one call is occupied by a new call, the emergency call will preempt the service of the new call and start service at its location.

4. A multi-server channel traffic control system for disaster scenarios, characterized in that, include: Acquisition module: Used to acquire different types of incoming calls; Determination module: connected to the acquisition module, used to determine the scenario type of the incoming call; The scenario types include normal scenarios and disaster scenarios. The normal scenario is the situation before a disaster occurs, and the disaster scenario is the situation after a disaster occurs. Scheduling module: connected to the determination module, used for communication scheduling based on the scenario type; Specifically, when the scenario type is the normal scenario, normal scenario communication scheduling is performed; when the scenario type is the disaster scenario, disaster scenario communication scheduling is performed. Control module: Connected to the scheduling module, used for communication channel allocation and traffic priority control, and to obtain the number of backup channels; The control module is also used to: obtain the total number of backup channels based on a multi-objective optimization strategy, calculated using the following formula: ， in, Indicates the total number of channels. Indicates the total number of backup channels. and These represent the average arrival rate and average service rate of emergency calls, respectively. , as well as These represent the probability of blocking an emergency call, the probability of blocking a new call / handover call, and the probability of preemption for an emergency call, respectively. This represents a probability threshold that is adjustable based on network size and performance, and its value ranges from 0 to 1.

5. The system as described in claim 4, characterized in that, The normal scenario communication scheduling includes: Determine the type of the incoming call: a new call or a switched call; When the call type is a new call and all channels are occupied upon arrival, the new call is added to a channel with unlimited capacity, and a retry service is initiated; and The handover call is lost when the call type is a handover call and all channels are occupied upon arrival.

6. The system as described in claim 4, characterized in that, The disaster scenario communication scheduling includes: Determine the type of the incoming call: a switching call, a new call, or an emergency call; If the call type is an emergency call and all channels are occupied only by emergency calls, the incoming emergency call will be lost. When the call type is an emergency call and all channels are occupied only by the handover call, the emergency call will preempt the handover call's service and begin service at its location; and When the call type is an emergency call and all channels are occupied and at least one call is occupied by a new call, the emergency call will preempt the service of the new call and start service at its location.

Images