Emergency scene pre-tightening message scheduling optimization method based on load awareness

Abstract

The invention relates to the field of 5G communication, and discloses an emergency scene pre-tightening message scheduling optimization method based on load awareness, and the method comprises the following steps: scheduling priority, and dynamically modifying a pre-tightening message scheduling period according to whether a pre-tightening message load is busy; detecting a pre-tightening message scheduling condition; detecting whether the pre-tightening message is stuck or not; the base station dynamically modifies the priority and the scheduling period, under the condition that the normal operation state and energy consumption of a cell are not affected as much as possible, the high-load emergency scene pre-tightening message scheduling efficiency is greatly optimized, and the probability that newly-added early warning messages cannot be scheduled due to delay is greatly reduced.

Description

Technical Field

[0001] The present application belongs to the field of 5G communication transmission technology, and in particular, relates to a method for optimizing pre-tightening message scheduling in emergency scenarios based on load perception. Background Art

[0002] In 5G communications, emergency messages are notified by the RRC (Radio Resource Control) layer to the MAC (Medium Access Control) layer through F1 messages, and then the MAC performs corresponding scheduling.

[0003] Due to the pre-tensioned messages such as ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert Service Detection Reference Signal), there is the possibility of concurrency and fragmentation.

[0004] In a busy scheduling scenario where multiple pre-tensioning messages need to be sent, general manufacturers configure the SI scheduling cycle length to be set by themselves. Regardless of the current pre-tensioning message load and whether the channel quality is good or not, if the SI scheduling cycle is statically fixed, in the prior art, one OtherSI schedules one pre-tensioning message. This may cause the newly added pre-tensioning message to be delayed for tens of seconds, which is not in line with the original design of the warning message. The scheduling of the previous pre-tensioning message has always failed, or there are multiple pre-tensioning messages that have been broadcast multiple times but have not reached the maximum number of broadcasts, and they are stuck before the new pre-tensioning message is added and cannot be scheduled. Summary of the invention

[0005] The embodiment of the present application provides a method for optimizing the scheduling of pre-tightening messages for emergency scenarios based on load perception, which aims to solve the technical problems raised by the background technology.

[0006] The technical solution adopted by the present invention is: In the first aspect, the present application provides a method for optimizing the scheduling of pre-tightening messages in emergency scenarios based on load perception. In the scheduling of 5G pre-tightening messages, the emergency message is notified to the MAC layer by the RRC layer through the F1 message, and then the MAC performs corresponding scheduling. The pre-tightening message needs to be concurrent and fragmented, and the pre-tightening message is scheduled through OtherSI; the calculation process is optimized by adding the following parameters, including but not limited to the number of retransmissions RPMC, the minimum number of broadcasts PMBC, the maximum number of retransmission failures MRPT, the scheduling number PMSC, the cooling cycle PMCP, the load scheduling number PMTC and the total time threshold of periodic scheduling PMST; in the scheduling process, the number of fragments is used as the minimum statistical unit, including the following steps: S1. Check whether the number of pre-tightening messages required for scheduling in the current cell has reached PMTC; S2. Estimate the total time required to broadcast all current preload messages once, and determine whether it is greater than PMST, then start a new round of optimization; S3. If the RPMC of any pre-tightening message is greater than the MRPT and greater than the PMBC*priority index, then after extending the PMCP of the pre-tightening message, continue to estimate the total time required for all current pre-tightening messages to be broadcast once, and determine whether it is greater than the PMST; S4. If it is greater than PMST, extend the scheduling period PMCP for the remaining pre-tightening messages whose PMSC is greater than PMBC*priority index, and continue to estimate the total time required for all current pre-tightening messages to be broadcast once, and observe whether it is greater than PMST; S5. If it continues to be greater than PMST, extend the scheduling period PMCP for the remaining pre-tightening messages whose PMSC is greater than PMBC index, and continue to estimate the total time required to broadcast all current pre-tightening messages once to observe whether it is greater than PMST; S6. If it is greater than PMST, extend the scheduling period PMCP for the remaining pre-tightening messages whose PMSC is not 0, and continue to estimate the total time required for broadcasting all current pre-tightening messages once to observe whether it is greater than PMST; S7. If it is still greater than PMST, recalculate the priority of the remaining preloaded messages according to the RPMC size, and perform the next scheduling task with the new priority; S8. After the scheduling is normal, that is, when it is less than PMST, the OtherSI cycle configuration will be automatically switched; S9. In the above process, if all preload messages need to add PMCP, then all messages will not add PMCP and directly transition to step 6.

[0007] In step S3, the priority index is determined as the scheduling priority and the pre-stress message scheduling period is dynamically modified according to whether the pre-stress message load is busy.

[0008] In step S1, when it is found that the load is too high, the OtherSI cycle configuration will be automatically switched.

[0009] In a second aspect, the present application provides a computer program for implementing the method described in the first aspect.

[0010] Compared with the prior art, the embodiments of the present application have the following beneficial effects: in the scenario where the pre-tightening message scheduling is busy and the new pre-tightening message cannot be scheduled for a long time, it provides favorable guarantees. Without affecting the normal operation and energy consumption of the cell, the pre-tightening message scheduling efficiency of the high-load emergency scenario is greatly optimized, and the probability of the new warning message being unable to be scheduled for a long time is greatly reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0012] Figure 1 It is a schematic diagram of the process provided in the embodiment of the present application. DETAILED DESCRIPTION

[0013] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0014] In 5G pre-tension message scheduling, all pre-tension messages are scheduled through OtherSI.

[0015] New parameters: Retransmissions pretension messages count (RPMC) Pretension messages minimum broadcast count (PMBC) Maximum retransmissions pretension threshold (MRPT) Pretension messages schedule count threshold (PMSC) Pretension messages cooling period (PMCP) Pretension messages total count (PMTC) Pretension messages total cycle schedule time threshold (PMST) The present application provides a method for optimizing the scheduling of pre-tightening messages in emergency scenarios based on load perception. In the scheduling of 5G pre-tightening messages, the emergency message is notified to the MAC layer by the RRC layer through the F1 message, and then the MAC performs corresponding scheduling. The pre-tightening message needs to be concurrent and fragmented, and the pre-tightening message is scheduled through OtherSI; the calculation process is optimized by adding the following parameters, including but not limited to the number of retransmissions RPMC, the minimum number of broadcasts PMBC, the maximum number of retransmission failures MRPT, the scheduling number PMSC, the cooling period PMCP, the load scheduling number PMTC and the total time threshold of periodic scheduling PMST; in the scheduling process, the number of fragments is used as the minimum statistical unit, including the following steps: S1. Check whether the number of pre-tightening messages required for scheduling in the current cell has reached PMTC; S2. Estimate the total time required to broadcast all current preload messages once, and determine whether it is greater than PMST, then start a new round of optimization; S3. If the RPMC of any pre-tightening message is greater than the MRPT and greater than the PMBC*priority index, then after extending the PMCP of the pre-tightening message, continue to estimate the total time required for all current pre-tightening messages to be broadcast once, and determine whether it is greater than the PMST; S4. If it is greater than PMST, extend the scheduling period PMCP for the remaining pre-tightening messages whose PMSC is greater than PMBC*priority index, and continue to estimate the total time required for all current pre-tightening messages to be broadcast once, and observe whether it is greater than PMST; S5. If it continues to be greater than PMST, extend the scheduling period PMCP for the remaining pre-tightening messages whose PMSC is greater than PMBC index, and continue to estimate the total time required to broadcast all current pre-tightening messages once to observe whether it is greater than PMST; S6. If it is greater than PMST, extend the scheduling period PMCP for the remaining pre-tightening messages whose PMSC is not 0, and continue to estimate the total time required for broadcasting all current pre-tightening messages once to observe whether it is greater than PMST; The PMBC index can be defined based on the past data of the base station. In steps S4, S5, and S6, it corresponds to a guaranteed scheduling that discards some pre-tightening messages. For example, PMBC is set to x=5; the priority index is set to y=5. S4 represents the logical relationship between PMSC>xy, S5 represents PMSC>x, and S6 represents PMSC>0.

[0016] S7. If it is still greater than PMST, recalculate the priority of the remaining preloaded messages according to the RPMC size, and perform the next scheduling task with the new priority; S8. After the scheduling is normal, that is, when it is less than PMST, the OtherSI cycle configuration will be automatically switched; S9. In the above process, if all preload messages need to add PMCP, then all messages will not add PMCP and directly transition to step 6.

[0017] In step S3, the priority index is determined as the scheduling priority and the pre-stress message scheduling period is dynamically modified according to whether the pre-stress message load is busy.

[0018] In step S1, when it is found that the load is too high, the OtherSI cycle configuration will be automatically switched.

[0019] Embodiment 1 The base station is configured with one cell, and the SI period of the cell is set to 640ms. Set PMBC to 5, MRPT to 4, PMCP to 30s, PMTC to 120, and PMST to 3s In the current scenario, 20 ETWS messages with 64 fragments are being sent in parallel.

[0020] 15 of the messages have been broadcast more than 50 times, but have not reached the maximum number of retransmissions. The failure rate of 3 messages is almost 80%, and there are only two newly added pre-tightening messages. Adopt new scheduling algorithm for optimization.

[0021] The base station will first modify the OtherSI period to 320ms, then schedule 5 times according to the two new pre-tightening messages, and then schedule in sequence according to the broadcast failure rate priority.

[0022] This method can ensure the successful broadcast of each pre-tightening message in extreme cases where scheduling is restricted, and avoid the situation where some pre-tightening messages cannot be scheduled for a long time. It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0023] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0024] An embodiment of the present application also provides a network device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor implements the steps in any of the above-mentioned method embodiments when executing the computer program.

[0025] An embodiment of the present application provides a computer program product. When the computer program product runs on a mobile terminal, the mobile terminal can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0026] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the camera / terminal device, recording medium, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0027] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0028] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0029] In the embodiments provided in the present application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0030] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0031] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for optimizing the scheduling of pre-tightening messages in emergency scenarios based on load perception. In the scheduling of 5G pre-tightening messages, the emergency message is notified to the MAC layer by the RRC layer through the F1 message, and then the MAC performs corresponding scheduling. The pre-tightening message needs to be concurrent and fragmented, and the pre-tightening message is scheduled through OtherSI; the calculation process is optimized by adding the following parameters, including but not limited to the number of pre-tightening message retransmissions RPMC, the minimum number of pre-tightening message broadcasts PMBC, the maximum number of pre-tightening message retransmission failures MRPT, the number of pre-tightening message scheduling PMSC, the pre-tightening message cooling period PMCP, the number of pre-tightening message load scheduling PMTC and the total time threshold for pre-tightening message period scheduling PMST; in the scheduling process, the number of fragments is used as the minimum statistical unit, characterized in that, The steps include: S1. Check whether the number of pre-tightening messages required for scheduling in the current cell has reached PMTC; S2. Estimate the total time required to broadcast all current preload messages once, and determine whether it is greater than PMST, then start a new round of optimization; S3. If the RPMC of any pre-tightening message is greater than the MRPT and greater than the PMBC*priority index, then after extending the PMCP of the pre-tightening message, continue to estimate the total time required for all current pre-tightening messages to be broadcast once, and determine whether it is greater than the PMST; S4. If it is greater than PMST, extend the scheduling period PMCP for the remaining pre-tightening messages whose PMSC is greater than PMBC*priority index, and continue to estimate the total time required for all current pre-tightening messages to be broadcast once, and observe whether it is greater than PMST; S5. If it continues to be greater than PMST, extend the scheduling period PMCP for the pre-tightening messages whose PMSC is greater than PMBC index in the remaining pre-tightening messages, and continue to estimate the total time required to broadcast all the current pre-tightening messages once, and observe whether it is greater than PMST; S6. If it is still greater than PMST, extend the scheduling period PMCP for the remaining pre-tightening messages whose PMSC is not 0, and continue to estimate the total time required for broadcasting all current pre-tightening messages once to observe whether it is greater than PMST; S7. If it is still greater than PMST, recalculate the priority of the remaining preloaded messages according to the RPMC size, and use the new priority to schedule the next task. S8. After the scheduling is normal, that is, when it is less than PMST, the OtherSI cycle configuration will be automatically switched; S9. In the above process, if all preload messages need to add PMCP, then all messages will not add PMCP and directly transition to step 6.

2. The method for optimizing the scheduling of emergency scenario pre-tightening messages based on load perception according to claim 1, characterized in that: In step S3, the priority index is determined as the scheduling priority and the pre-stress message scheduling period is dynamically modified according to whether the pre-stress message load is busy.

3. The method for optimizing the scheduling of emergency scenario pre-tightening messages based on load perception according to claim 1, characterized in that: In step S1, when it is found that the load is too high, the OtherSI cycle configuration will be automatically switched.

4. A computer program, characterized in that Implement the method as claimed in claim 1.

Images