Scheduling method, apparatus, system, electronic device, and non-transitory storage medium

Abstract

The application discloses a scheduling method, device, system, electronic equipment and nonvolatile storage medium. Wherein, the method comprises: determining the fifth generation mobile communication technology service quality identifier 5QI bearing attribute corresponding to each terminal device of the access base station network side, and determining the basic priority corresponding to the 5QI bearing attribute; according to the terminal capability information of the terminal device, the first scheduling weight proportion corresponding to the RedCap device in the terminal device is determined; according to the service demand information of the terminal device, the second scheduling weight proportion corresponding to the RedCap device is determined; according to the first scheduling weight proportion and the second scheduling weight proportion, the priority of a plurality of terminal devices located in the same basic priority is sorted, and a target priority sequence is obtained. The application solves the technical problem that different types of RedCap terminal devices are all scheduled according to equal priority at the base station side, which cannot meet the terminal demand in different business scenarios.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of mobile communication and terminal technology, in particular to a scheduling method, device, system, electronic equipment and nonvolatile storage medium. BACKGROUND

[0002] Currently, the NR UE (New Radio User Equipment) and the RedCap UE (Reduced Capability User Equipment) are both scheduled by default according to equal priority at the base station side, and no distinction is made between the two, so that differentiated scheduling cannot be performed for different types of terminal devices. The differentiated scheduling method in the related art generally adopts a manual static configuration of different weight factors, which has the problems of being prone to error, inaccurate, and not applicable to different RedCap service scenarios.

[0003] At present, no effective solution has been proposed for the above problems. SUMMARY

[0004] The embodiments of the present application provide a scheduling method, device, system, electronic equipment and nonvolatile storage medium to at least solve the technical problem that different types of RedCap terminal devices are all scheduled according to equal priority at the base station side, and cannot meet the terminal requirements in different service scenarios.

[0005] According to an aspect of an embodiment of the present application, a scheduling method is provided, comprising: determining a fifth generation mobile communication technology service quality identifier 5QI bearer attribute corresponding to each terminal device accessing a base station network side, and determining a basic priority corresponding to the 5QI bearer attribute, wherein the terminal type of the terminal device includes a reduced capability RedCap device and a new radio NR device, the 5QI bearer attribute is used to represent the latency requirement level of the terminal device, and each type of 5QI bearer attribute corresponds to a basic priority; determining a first scheduling weight proportion corresponding to the RedCap device in the terminal device according to terminal capability information of the terminal device, wherein the first scheduling weight proportion is used to represent the relative difference degree of terminal capability between each RedCap device and NR device; determining a second scheduling weight proportion corresponding to the RedCap device according to service requirement information of the terminal device, wherein the second scheduling weight proportion is used to represent the relative difference degree of service requirement between the RedCap device and the NR device of different service types; and performing priority sorting on a plurality of terminal devices located in the same basic priority according to the first scheduling weight proportion and the second scheduling weight proportion, to obtain a target priority sequence, wherein the target priority sequence is used to indicate the priority order of the communication resource scheduling for the terminal device.

[0006] Optionally, the determining the 5QI bearer attribute corresponding to each terminal device accessing the base station network side comprises: obtaining terminal information reported by the terminal device, wherein the terminal information comprises: terminal type, terminal capability information and service requirement information, the service requirement information comprises: uplink and downlink rate requirement and time delay requirement; determining a time delay interval range corresponding to the time delay requirement of the terminal device, and determining the 5QI bearer attribute corresponding to the time delay interval range as the 5QI bearer attribute corresponding to the terminal device, wherein the 5QI bearer attribute comprises: delay-Critical GBR type, GBR type and non-GBR type.

[0007] Optionally, the base priority comprises: a first base priority, a second base priority and a third base priority, the first base priority is higher than the second base priority, and the second base priority is higher than the third base priority; the determining the base priority corresponding to the 5QI bearer attribute comprises: in a case where the 5QI bearer attribute of the terminal device is delay-Critical GBR, determining that the base priority corresponding to the terminal device is the first base priority; in a case where the 5QI bearer attribute of the terminal device is GBR, determining that the base priority corresponding to the terminal device is the second base priority; and in a case where the 5QI bearer attribute of the terminal device is non-GBR, determining that the base priority corresponding to the terminal device is the third base priority.

[0008] Optionally, the determining the first scheduling weight ratio corresponding to the RedCap device in the terminal device according to the terminal capability information of the terminal device comprises: obtaining the terminal capability information of the RedCap device, wherein the terminal capability information comprises: a number of multiple-input multiple-output (MIMO) streams supported by the terminal device, and uplink / downlink maximum modulation order; determining a first ratio according to the number of MIMO streams, wherein the first ratio is a ratio of the number of MIMO streams supported by the RedCap device to the number of MIMO streams supported by the NR device; determining a second ratio according to the uplink / downlink maximum modulation order, wherein the second ratio is a ratio of the uplink / downlink maximum modulation order corresponding to the RedCap device to the uplink / downlink maximum modulation order corresponding to the NR device; and determining the first scheduling weight ratio corresponding to the RedCap device according to the first ratio and the second ratio.

[0009] Optionally, prioritizing multiple terminal devices at the same basic priority level includes: for terminal devices at the second basic priority level, determining the channel quality parameters and waiting scheduling delay parameters corresponding to each terminal device, wherein the waiting scheduling delay parameter is the ratio of the cache delay of the GBR service data packet of the terminal device to the maximum queuing delay that the GBR service can tolerate; determining the first priority parameter corresponding to each terminal device based on the channel quality parameter, waiting scheduling delay parameter, and the first scheduling weight ratio corresponding to each terminal device; and sorting the terminal devices at the second basic priority level according to the size of the first priority parameter, wherein the larger the first priority parameter, the higher the priority of the terminal device.

[0010] Optionally, based on the service demand information of the terminal device, determining the second scheduling weight ratio corresponding to the RedCap device includes: determining the delay sensitivity level factor corresponding to the RedCap device, wherein the delay sensitivity level factor is the ratio of the delay demand corresponding to the enhanced mobile broadband service of the NR device to the delay demand of the service corresponding to the RedCap device; determining the rate requirement level factor corresponding to the RedCap device, wherein the rate requirement level factor is the ratio of the uplink and downlink rate requirements of the service corresponding to the RedCap device to the uplink and downlink rate requirements corresponding to the enhanced mobile broadband service of the NR device; determining the second scheduling weight ratio corresponding to the RedCap device based on the delay sensitivity level factor and the rate requirement level factor.

[0011] Optionally, prioritizing multiple terminal devices at the same basic priority level also includes: for terminal devices at a third basic priority level, determining the spectrum efficiency, historical average rate, and weighted value corresponding to each terminal device, wherein the spectrum efficiency is used to characterize the channel quality corresponding to the terminal device, and when the terminal device is an NR device, the weighted value is determined by the 5QI value corresponding to the NR device, and when the terminal device is a RedCap device, the weighted value is a preset fixed value; determining the waiting scheduling delay parameter corresponding to each terminal device, wherein the waiting scheduling delay parameter is the ratio of the cache delay of the non-GBR service data packet of the terminal device to the maximum queuing delay that the non-GBR service can tolerate; determining the second priority parameter corresponding to each terminal device based on the spectrum efficiency, historical average rate, weighted value, waiting scheduling delay parameter, first scheduling weight ratio, and second scheduling weight ratio corresponding to each terminal device; and sorting the terminal devices at the third basic priority level according to the size of the second priority parameter, wherein the larger the second priority parameter, the higher the priority of the terminal device.

[0012] Optionally, prioritizing multiple terminal devices at the same basic priority level also includes: for terminal devices at a first basic priority level, determining the delay requirements of each terminal device; and sorting the terminal devices at the first basic priority level based on the delay requirements, wherein the smaller the delay required by the delay requirement, the higher the priority of the terminal device.

[0013] According to another aspect of the embodiment of the present application, a scheduling device is also provided, including: a basic priority determination module, used to determine the fifth-generation mobile communication technology service quality identification 5QI bearer attribute corresponding to each terminal device accessing the base station network side, and determine the basic priority corresponding to the 5QI bearer attribute, wherein the terminal type of the terminal device includes: reduced capability RedCap device and new air interface NR device, the 5QI bearer attribute is used to characterize the delay requirement level of the terminal device, and each type of 5QI bearer attribute corresponds to a basic priority; a first weight determination module, used to determine the first scheduling weight ratio corresponding to the RedCap device in the terminal device based on the terminal capability information of the terminal device, wherein the first A scheduling weight ratio is used to characterize the relative difference in terminal capabilities between each RedCap device and the NR device; a second weight determination module is used to determine the second scheduling weight ratio corresponding to the RedCap device based on the business demand information of the terminal device, wherein the second scheduling weight ratio is used to characterize the relative difference in business requirements between RedCap devices and NR devices of different business types; a target priority determination module is used to prioritize multiple terminal devices at the same basic priority level based on the first scheduling weight ratio and the second scheduling weight ratio to obtain a target priority sequence, wherein the target priority sequence is used to indicate the priority order for scheduling communication resources for the terminal devices.

[0014] According to another aspect of the embodiments of the present application, a scheduling system is further provided, comprising: a terminal device and a base station network side device, wherein the terminal device is configured to report terminal information to the base station network side device, wherein the terminal information comprises: terminal type, terminal capability information and service requirement information, and the terminal type comprises: RedCap device and NR device; the base station network side device is configured to determine a 5QI bearer attribute corresponding to each terminal device accessing the base station network side, and determine a basic priority corresponding to the 5QI bearer attribute, wherein the 5QI bearer attribute is used to represent the latency requirement level of the terminal device, and each type of 5QI bearer attribute corresponds to a basic priority; determine a first scheduling weight ratio corresponding to the RedCap device in the terminal device according to the terminal capability information of the terminal device, wherein the first scheduling weight ratio is used to represent the relative difference degree of terminal capability between each RedCap device and NR device; determine a second scheduling weight ratio corresponding to the RedCap device according to the service requirement information of the terminal device, wherein the second scheduling weight ratio is used to represent the relative difference degree of service requirement between the RedCap device and the NR device of different service types; and perform priority sorting on a plurality of terminal devices located in the same basic priority according to the first scheduling weight ratio and the second scheduling weight ratio, to obtain a target priority sequence, wherein the target priority sequence is used to indicate the priority order of the terminal device for communication resource scheduling.

[0015] According to still another aspect of the embodiments of the present application, an electronic device is further provided, comprising: a memory and a processor, wherein the processor is configured to run a program stored in the memory, and the program is configured to perform the scheduling method when running.

[0016] According to still another aspect of the embodiments of the present application, a non-volatile storage medium is further provided, comprising a stored computer program, wherein a device in which the non-volatile storage medium is located performs the scheduling method by running the computer program.

[0017] According to still another aspect of the embodiments of the present application, a computer program product is further provided, comprising a computer program, and the computer program is configured to perform the steps of the scheduling method when executed by a processor.

[0018] In the embodiment of the present application, the fifth generation mobile communication technology service quality identifier 5QI bearer attribute corresponding to each terminal device of the access base station network side is determined, and the basic priority corresponding to the 5QI bearer attribute is determined, wherein the terminal type of the terminal device includes a reduced capability RedCap device and a new radio NR device, the 5QI bearer attribute is used to represent the delay requirement level of the terminal device, and each type of 5QI bearer attribute corresponds to a basic priority; according to the terminal capability information of the terminal device, a first scheduling weight ratio corresponding to the RedCap device in the terminal device is determined, wherein the first scheduling weight ratio is used to represent the relative difference degree of terminal capability between each RedCap device and NR device; according to the service requirement information of the terminal device, a second scheduling weight ratio corresponding to the RedCap device is determined, wherein the second scheduling weight ratio is used to represent the relative difference degree of service requirement between the RedCap device and the NR device of different service types; according to the first scheduling weight ratio and the second scheduling weight ratio, the priority of a plurality of terminal devices located in the same basic priority is sorted to obtain a target priority sequence, wherein the target priority sequence is used to indicate the priority order of the communication resource scheduling for the terminal device, and through the information interaction between the terminal and the base station side, the capability, rate delay and other service requirement information of different RedCap UEs are accurately obtained at the base station network side, and the bearing attribute is judged when the RedCap UE establishes the 5QI bearing. In the subsequent data scheduling process, the scheduling weight ratio of the RedCap UE relative to the traditional UE and the scheduling weight ratio of the RedCap UE of different services relative to the traditional UE are dynamically calculated, so as to maximize the air interface resource utilization rate and optimize the system network performance under the condition of meeting the differentiated needs of different types of terminal devices and different business application scenarios, thereby solving the technical problem that different types of RedCap terminal devices at the base station side are scheduled according to equal priority, which cannot meet the terminal requirements in different business scenarios. BRIEF DESCRIPTION OF DRAWINGS

[0019] The drawings described herein are used to provide further understanding of the present application, and form a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application, and do not constitute an improper limitation on the present application. In the drawings:

[0020] Figure 1 is a schematic diagram of a scheduling method flow provided by an embodiment of the present application;

[0021] Figure 2 is a schematic diagram of a method flow for differentiated scheduling of a RedCap UE according to an embodiment of the present application;

[0022] Figure 3is a structural schematic diagram of a scheduling device according to an embodiment of the present application.

[0023] Figure 4 is a structural schematic diagram of a scheduling system according to an embodiment of the present application.

[0024] Figure 5 is a hardware structural block diagram of a computer terminal (or electronic device) for implementing a method of scheduling according to an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order for those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should be within the scope of protection of the present application.

[0026] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0027] In order to facilitate those skilled in the art to better understand the embodiments of the present application, some technical terms or nouns related to the embodiments of the present application will be explained as follows:

[0028] Redcap (Reduced Capability): a 5G light technology introduced by 3GPP in R17 version, which can effectively reduce the complexity and cost of the terminal by reducing the working bandwidth, reducing the number of transceiver antennas, and reducing the modulation order.

[0029] 5QI (5G QoS Identifier): is a parameter used to identify the quality of service in 5G network. 5QI represents a set of parameter values, including resource type, priority, reliability, packet loss rate, etc., which are used to control the forwarding process of QoS (Quality of Service) flow.

[0030] Currently, NR UEs and RedCap UEs are both scheduled by default with equal priority at the base station side, that is, they are not distinguished, and the rate difference is only determined by the terminal antenna configuration and bandwidth. With the development of services, differentiated scheduling of RedCap UEs and NR UEs needs to be considered.

[0031] In the related art, differentiated scheduling is generally realized by manually configuring static parameters at the base station side to set different weight factors for the 5QI of traditional NR UEs and RedCap UEs. Specifically, the scheduling priority of the bearer is calculated according to the QoS attribute (QCI / 5QI, Packet Delay Budget, etc.), channel quality information, and weight of the bearer to ensure that users meet the QoS attribute while maximizing system throughput; the slice + 5QI + scheduling weight method is used to support differentiated scheduling, and the scheduling weight affects the scheduling times, for example, 5QI 9 is established for traditional NR UEs, and the weight is set to 0.7, and 5QI 83 is established for RedCap UEs, and the weight is set to 0.4.

[0032] This differentiated scheduling method is rough and simple, prone to errors, inaccurate, and cannot be applied to different RedCap service scenarios. Specifically, the following problems exist: the weight factor is 5QI level, there are many types of RedCap terminals, and the related protocols do not clearly specify which 5QI bearer index different RedCap terminals should correspond to, and manual configuration is prone to errors. It may happen that a RedCap wearable device is manually configured with a weight factor on a certain 5QI, but the actual RedCap service may not take effect on this 5QI, which will cause the problem of not being able to achieve the expected differentiated scheduling. In addition, even if the RedCap terminal type and the 5QI index are matched, the weight is fixed at this time, and cannot match different RedCap service requirements.

[0033] To solve the above problems, the related solutions in the embodiments of the present application are provided, which are described in detail below.

[0034] According to the embodiment of the present application, a method for scheduling is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that here.

[0035] The method embodiment provided by the embodiment of the present application can be executed in a communication system containing a Redcap device.

[0036] Under the above running environment, the embodiment of the present application provides a scheduling method, Figure 1 is a schematic diagram of a method for scheduling according to the embodiment of the present application, as Figure 1 shown, the method comprises the following steps:

[0037] Step S102, determining the fifth generation mobile communication technology service quality identifier 5QI bearing property corresponding to each terminal device accessing the base station network side, and determining the basic priority corresponding to the 5QI bearing property, wherein the terminal type of the terminal device includes: reduced capability RedCap device and new radio NR device, the 5QI bearing property is used to represent the delay requirement level of the terminal device, and each type of 5QI bearing property corresponds to a basic priority;

[0038] Step S104, determining the first scheduling weight proportion corresponding to the RedCap device in the terminal device according to the terminal capability information of the terminal device, wherein the first scheduling weight proportion is used to represent the relative difference degree of terminal capability between each RedCap device and NR device;

[0039] Step S106, determining the second scheduling weight proportion corresponding to the RedCap device according to the service demand information of the terminal device, wherein the second scheduling weight proportion is used to represent the relative difference degree of service demand between the RedCap device and the NR device of different service types;

[0040] Step S108, according to the first scheduling weight proportion and the second scheduling weight proportion, the priority of a plurality of terminal devices located in the same basic priority is sorted to obtain a target priority sequence, wherein the target priority sequence is used to indicate the priority order of the communication resource scheduling for the terminal device.

[0041] Through the above steps, through the information exchange between the terminal and the base station, the base station network side accurately obtains the service demand information such as the capabilities, rate and delay of different RedCap UEs, and determines the bearer attributes when the RedCap UE establishes a 5QI bearer. In the subsequent data scheduling process, the scheduling weight ratio of the RedCap UE relative to the traditional UE, as well as the scheduling weight ratio of different services of the RedCap UE relative to the traditional UE, are dynamically calculated. This achieves the purpose of maximizing the utilization of air interface resources and optimizing system network performance while meeting the differentiated needs of different types of terminal devices and different service application scenarios. This solves the technical problem that different types of RedCap terminal devices are currently scheduled according to equal priority on the base station side, which cannot meet the terminal requirements in different service scenarios.

[0042] The scheduling method in steps S102 to S108 of the embodiment of the present application is further introduced below.

[0043] Figure 2 is a schematic diagram of a method flow for differentiated scheduling of a RedCap UE provided in an embodiment of the present application, such as Figure 2 As shown, the embodiment of the present application realizes the acquisition of RedCap terminal type, terminal capability, service demand information and other data on the network side through the interaction between the information reporting module of the terminal device and the information acquisition module on the base station network side. Then, the bearer identification module on the base station network side determines the 5QI bearer attributes according to the delay sensitivity level requirements; and the scheduling control module calculates the scheduling priority of the RedCapUE according to the above-mentioned terminal type, terminal capability, 5QI bearer attributes, rate requirement level and other information.

[0044] Among them, in the process of calculating the scheduling priority of RedCap UE, the scheduling priority can be roughly sorted according to the 5QI bearer attributes, such as delay-Critical GBR>GBR>non-GBR; then the priorities of traditional NR UE and RedCap UE in GBR and non-GBR services can be finely differentiated, including: calculating the scheduling weight ratio of RedCap UE relative to traditional NR UE according to terminal type and terminal capability, and calculating the relative scheduling weight ratio between different services of RedCap UE according to the delay requirement level and rate requirement level. Figure 2 The method flow shown in is further described in detail.

[0045] Firstly, the base station network side obtains terminal information reported by the RedCap terminal in the process of terminal device UE access, wherein the terminal information includes: terminal type, terminal capability information and service demand information, the terminal type includes: RedCap UE and traditional NR UE, the terminal capability information includes: multiple-input multiple-output stream number (MIMO stream number), uplink / downlink maximum modulation order, and the service demand information includes: uplink / downlink rate requirement R AppScen , delay requirement T AppScen .

[0046] For example, assuming that there are multiple RedCap terminal devices: vehicle Tbox intelligent cockpit, industrial wireless sensor AGV, vehicle video call, industry video monitoring, smart watch and traditional commercial terminal device belonging to NR UE, which access the 5G network together. After the terminal devices report the terminal information, the base station network side obtains the following information:

[0047] The vehicle Tbox intelligent cockpit reports the terminal type as RedCap terminal, supports 1 stream in uplink and downlink, the highest modulation order of downlink is 256QAM, the highest modulation order of uplink is 64QAM, the delay requirement is 20ms, and the downlink rate requirement is 50Mbps;

[0048] The industrial wireless sensor AGV reports the terminal type as RedCap terminal, supports 1 stream in uplink and downlink, the highest modulation order of uplink and downlink is 64QAM, the delay requirement is 50ms, and the downlink rate requirement is 5Mbps;

[0049] The vehicle video call reports the terminal type as RedCap terminal, supports 1 stream in uplink and downlink, the highest modulation order of uplink and downlink is 64QAM, the delay requirement is 100ms, and the uplink and downlink rate requirement is 10Mbps;

[0050] The industry video monitoring reports the terminal type as RedCap terminal, supports 1 stream in uplink and downlink, the highest modulation order of uplink and downlink is 64QAM, the delay requirement is 500ms, and the rate requirement is 4Mbps;

[0051] The smart watch reports the terminal type as RedCap terminal, supports 1 stream in uplink and downlink, the highest modulation order of uplink and downlink is 64QAM, the delay requirement is 800ms, and the rate requirement is 1Mbps;

[0052] The traditional commercial terminal reports the terminal type as ordinary NR terminal, supports 1 stream in uplink, supports 2 streams in downlink, and the highest modulation order of uplink and downlink is 256QAM.

[0053] After the terminal device successfully accesses the NR cell, when the network side establishes a 5QI bearer for the RedCap UE, the bearer discrimination module can discriminate the corresponding 5QI bearer attribute of each terminal device according to the latency sensitivity level requirement of each terminal device, that is, determine the corresponding 5QI bearer attribute of each terminal device accessing the network side of the base station, and the specific steps are as follows.

[0054] In some embodiments of the present application, determining the corresponding 5QI bearer attribute of each terminal device accessing the network side of the base station includes the following steps: obtaining the terminal information reported by the terminal device, wherein the terminal information includes: terminal type, terminal capability information and service requirement information, and the service requirement information includes: uplink and downlink rate requirement and latency requirement; determining the latency interval range corresponding to the latency requirement of the terminal device, and determining the 5QI bearer attribute corresponding to the latency interval range as the corresponding 5QI bearer attribute of the terminal device, wherein the 5QI bearer attribute includes: delay-Critical GBR type, GBR type, and non-GBR type.

[0055] Specifically, in the embodiments of the present application, the corresponding relationship between the latency interval range corresponding to the latency requirement and the 5QI bearer attribute is as follows: if the latency requirement is in the 20-50ms level, the 5QI bearer attribute is delay-Critical GBR; if the latency requirement is in the 50-150ms level, the 5QI bearer attribute is GBR; if the latency requirement is in the 150-1s level, the 5QI bearer attribute is non-GBR.

[0056] For example, the vehicle Tbox intelligent cockpit reports that the terminal type is a RedCap terminal, the latency requirement is 20ms, and it is in the 20-50ms level, so the corresponding 5QI bearer attribute is delay-Critical GBR; the industrial wireless sensor AGV reports that the terminal type is a RedCap terminal, the latency requirement is 50ms, and it is in the 20-50ms level, so the corresponding 5QI bearer attribute is delay-Critical GBR; the vehicle video call reports that the terminal type is a RedCap terminal, the latency requirement is 100ms, and it is in the 50-150ms level, so the corresponding 5QI bearer attribute is GBR; the industry video monitoring reports that the terminal type is a RedCap terminal, the latency requirement is 500ms, and it is in the 150-1s level, so the corresponding 5QI bearer attribute is non-GBR.

[0057] After that, the network side will calculate the scheduling priority of the RedCap UE in the uplink and downlink data scheduling process of the RedCap UE. First, the scheduling priority can be roughly sorted according to the 5QI bearer attribute of each terminal device, that is, the basic priority corresponding to the 5QI bearer attribute is determined, and the specific steps are as follows.

[0058] In some embodiments of the present application, the basic priority includes a first basic priority, a second basic priority, and a third basic priority, the first basic priority is higher than the second basic priority, and the second basic priority is higher than the third basic priority; determining the basic priority corresponding to the 5QI bearer attribute includes the following steps: in the case that the 5QI bearer attribute of the terminal device is delay-Critical GBR, determining that the basic priority corresponding to the terminal device is the first basic priority; in the case that the 5QI bearer attribute of the terminal device is GBR, determining that the basic priority corresponding to the terminal device is the second basic priority; in the case that the 5QI bearer attribute of the terminal device is non-GBR, determining that the basic priority corresponding to the terminal device is the third basic priority.

[0059] Specifically, according to the 5QI bearer attribute, the service priority of the traditional NR user equipment and the RedCap user equipment is roughly sorted, and is judged to be three levels: the priority level of the RedCap user delay-Critical_GBR service is the highest (i.e. the first basic priority), the priority level of the GBR service of the traditional NR user equipment and the RedCap user equipment is the second highest (i.e. the second basic priority), and the priority level of the non-GBR service of the traditional NR user equipment and the RedCap user equipment is the lowest (i.e. the third basic priority).

[0060] For example, the 5QI bearer of the vehicle-mounted Tbox intelligent cockpit and the industrial wireless sensor AGV belongs to the delay-critical GBR bearer, and the scheduling priority is the highest, which is the first basic priority. The 5QI bearer of the vehicle-mounted video call belongs to the GBR bearer, and the scheduling priority is the second highest, which is the second basic priority. The 5QI bearer of the industry video monitoring and smart watch belongs to the non-GBR bearer, and the scheduling priority is the lowest, which is the third basic priority.

[0061] After rough sorting to obtain the basic priority corresponding to each terminal device, further priority sorting can be performed on multiple terminal devices under the same basic priority, which will be further introduced below.

[0062] For terminal devices under the first basic priority, i.e. multiple RedCap user devices of delay-Critical GBR service, they can be sorted according to the size of delay requirement, the smaller the required delay, the higher the priority; otherwise, the lower the priority, which is as follows.

[0063] In some embodiments of the present application, the priority sorting of the multiple terminal devices under the same basic priority further includes the following steps: for the terminal devices under the first basic priority, determining the delay requirement of each terminal device; sorting the terminal devices under the first basic priority according to the delay requirement, wherein the smaller the delay required by the delay requirement, the higher the priority of the terminal device.

[0064] For example, the delay requirement of the vehicle Tbox intelligent cockpit with delay-Critical GBR attribute is 20ms, which is higher than the delay requirement of 50ms of the industrial wireless sensor AGV with delay-Critical GBR attribute. Therefore, the priority of the vehicle Tbox intelligent cockpit is higher than that of the industrial wireless sensor AGV.

[0065] For terminal devices under the second basic priority, i.e. the priority sorting of traditional NR UE and RedCap UE in GBR service, the calculation is as follows:

[0066] Priority GBR =f(CQI)*f(delay)*W RedCap

[0067] Wherein, f(CQI) represents the channel quality parameter corresponding to the terminal device, f(delay) represents the waiting scheduling delay parameter, which is the ratio of the buffer delay of the GBR service data packet of the terminal device to the maximum queuing delay that the GBR service can tolerate, W RedCap represents the first scheduling weight ratio of RedCap UE relative to traditional NR UE, which is effective only for RedCap users. For traditional UE, the value is 1.

[0068] The determination process of the above-mentioned first scheduling weight ratio W RedCap is as follows.

[0069] In some embodiments of the present application, the first scheduling weight ratio corresponding to the RedCap device in the terminal device is determined according to the terminal capability information of the terminal device, including the following steps: obtaining the terminal capability information of the RedCap device, wherein the terminal capability information includes the number of multiple-input multiple-output (MIMO) streams supported by the terminal device, and the maximum modulation order of uplink / downlink; determining a first ratio according to the number of MIMO streams, wherein the first ratio is the ratio of the number of MIMO streams supported by the RedCap device to the number of MIMO streams supported by the NR device; determining a second ratio according to the maximum modulation order of uplink / downlink, wherein the second ratio is the ratio of the maximum modulation order of uplink / downlink corresponding to the RedCap device to the maximum modulation order of uplink / downlink corresponding to the NR device; and determining the first scheduling weight ratio corresponding to the RedCap device according to the first ratio and the second ratio.

[0070] Specifically, the first scheduling weight ratio W RedCap is calculated according to the following formula:

[0071]

[0072] wherein the number of MIMO streams RedCap UE represents the number of MIMO streams of the RedCap UE, the number of MIMO streams 传统NR UE represents the number of MIMO streams supported by the NR device, and maxQAM RedCap UE represents the maximum modulation order of uplink / downlink corresponding to the RedCap device, and maxQAM 传统NR UE represents the maximum modulation order of uplink / downlink corresponding to the conventional NR device.

[0073] After the first scheduling weight ratio W RedCap is calculated, the terminal devices located in the second basic priority can be further prioritized, and the specific steps are as follows.

[0074] In some embodiments of the present application, prioritizing the plurality of terminal devices located in the same basic priority includes: for the terminal devices located in the second basic priority, determining the channel quality parameter and the waiting scheduling delay parameter corresponding to each terminal device, wherein the waiting scheduling delay parameter is the ratio of the buffer delay of the GBR service data packet of the terminal device to the maximum queuing delay that the GBR service can tolerate; and determining the first priority parameter (Priority GBR); and the terminal devices under the second basic priority are sorted according to the size of the first priority parameter, wherein the greater the first priority parameter is, the higher the priority of the terminal device is.

[0075] For example, the RedCap car video call (CVC) and the VoNR service of the conventional commercial terminal both belong to GBR bearers, and the scheduling priority of the two can be determined according to Priority GBR = f (CQI) * f (delay) * W RedCap The calculation is as follows, and the uplink and downlink scheduling priority between the two is illustrated as follows.

[0076] For example, in the downlink scheduling process, the scheduling priority Priority CVC_GBR The formula is as follows:

[0077]

[0078] The scheduling priority Priority UE_GBR = f UE (CQI) * f UE (delay) * 1;

[0079] It is assumed that condition 1 is met: at this time, the car video call terminal and the commercial terminal are located in the same channel condition, that is, f CVC (CQI) = f UE (CQI), and f CVC (delay) = f UE (delay), the downlink scheduling priority of the car video call terminal is 1 / 8 of the downlink scheduling priority of the commercial terminal VoNR service. The downlink scheduling priority between the car video call terminal and the commercial terminal VoNR service is: the commercial terminal VoNR service is prior to the car video call terminal.

[0080] It is assumed that condition 2 is met: at this time, the car video call terminal and the commercial terminal are located in different channel conditions, and the channel condition of the car video call terminal is better than that of the commercial terminal, for example, f CVC (CQI) = 8 * f UE (CQI), and the waiting scheduling delay factor of the car video call terminal is higher than that of the commercial terminal, for example, f CVC (delay) = 2 * f UEIf f (CQI) = 2*f (CQI) and f (delay) = 2*f (delay), the downlink scheduling priority of the vehicle video call terminal is twice the scheduling priority of the commercial terminal VoNR service. The downlink scheduling priority order between the vehicle video call terminal and the commercial terminal VoNR service is: the vehicle video call terminal is prior to the commercial terminal VoNR service.

[0081] In the uplink scheduling process, the scheduling priority Priority of the 5QI bearer of the vehicle video call CVC_GBR As shown in the following formula:

[0082]

[0083] The scheduling priority Priority of the VoNR service of the traditional commercial terminal UE_GBR = f UE (CQI) * f UE (delay) * 1;

[0084] Assuming that condition 3 is met: at this time, the vehicle video call terminal and the commercial terminal are located in the same channel condition, that is, f CVC (CQI) = f UE (CQI), and f CVC (delay) = f UE (delay), the uplink scheduling priority of the vehicle video call terminal is 1 / 4 of the scheduling priority of the commercial terminal VoNR service. The uplink scheduling priority order between the vehicle video call terminal and the commercial terminal VoNR service is: the commercial terminal VoNR service is prior to the vehicle video call terminal.

[0085] Assuming that condition 4 is met: at this time, the vehicle video call terminal and the commercial terminal are located in different channel conditions, and the channel condition of the vehicle video call terminal is better than that of the commercial terminal, such as f CVC (CQI) = 8*f UE (CQI), and the waiting scheduling delay factor of the vehicle video call terminal is higher than that of the commercial terminal, such as f CVC (delay) = 2*f UE (delay), the uplink scheduling priority of the vehicle video call terminal is 4 times the scheduling priority of the commercial terminal VoNR service. The uplink scheduling priority order between the vehicle video call terminal and the commercial terminal VoNR service is: the vehicle video call terminal is prior to the commercial terminal VoNR service.

[0086] For terminal devices under the third basic priority, that is, the priority order of traditional NR UEs and RedCap UEs in non-GBR services is as shown in the following formula:

[0087]

[0088] wherein, eff represents the spectral efficiency corresponding to the terminal device, used to represent the channel quality of the UE, a represents the capacity factor of the EPF scheduling algorithm (Enhanced Proportional Fair, enhanced proportional fair scheduling algorithm), g represents the channel quality of the terminal device, and f(delay) represents the ratio of the buffer delay of the non-GBR service data packet of the terminal device to the maximum queuing delay that the non-GBR service can tolerate, W represents the scheduling priority weight (i.e., the weight value) of different 5QIs in the non-GBR service, which is only effective for traditional UEs, and the value is 1 for RedCap UEs, r represents the historical average rate of the UE, and f(delay) represents the waiting scheduling delay parameter. 5QI RedCap AppScen AppScen

[0089] AppScen AppScen AppScen AppScen The specific steps for determining the second scheduling weight ratio are as follows.

[0090] In some embodiments of the present application, the second scheduling weight ratio corresponding to the RedCap device is determined according to the service demand information of the terminal device, including the following steps: determining the latency sensitivity level factor corresponding to the RedCap device, wherein the latency sensitivity level factor is the ratio of the latency demand corresponding to the enhanced mobile broadband service of the NR device to the latency demand of the service corresponding to the RedCap device; determining the rate demand level factor corresponding to the RedCap device, wherein the rate demand level factor is the ratio of the uplink and downlink rate demand of the service corresponding to the RedCap device to the uplink and downlink rate demand corresponding to the enhanced mobile broadband service of the NR device; and determining the second scheduling weight ratio corresponding to the RedCap device according to the latency sensitivity level factor and the rate demand level factor.

[0091] Specifically, the latency sensitivity level factor b AppScen eMBB AppScen ​​​​​​​​​​i.e. the ratio of latency requirement of typical enhanced mobile broadband, eMBB, service and latency requirement of different RedCap applications, which is only valid for RedCap users. For example, when the application scenario is mobile police / mobile government / safe office (200ms), β AppScen = T eMBB / T MP ; when the application scenario is logistics transportation / video monitoring (500ms), β AppScen = T eMBB / T VS ; when the application scenario is wearable device / shared device (800ms), β AppScen = T eMBB / T WD .

[0092] The value of the rate requirement level factor δ AppScen is R AppScen / R eMBB , i.e. the ratio of rate requirement of different RedCap applications and rate requirement of typical eMBB service, which is only valid for RedCap users. For example, when the application scenario is mobile police / mobile government / safe office (10-50Mpbs), δ AppScen = R MP / R eMBB ; when the application scenario is logistics transportation / video monitoring (2-4Mbps / 7.5-25Mbsp), δ AppScen = R VS / R eMBB ; when the application scenario is wearable device / shared device (1-2Mbps), δ AppScen = R WD / R eMBB .

[0093] After the first scheduling weight ratio W RedCap and the second scheduling weight ratio β AppScen * δ AppScen are calculated, the terminal devices located at the third basic priority can be further prioritized, and the specific steps are as follows.

[0094] In some embodiments of the present application, the priority ranking of the plurality of terminal devices located at the same basic priority further includes the following steps: for the terminal devices located at the third basic priority, determining the spectrum efficiency, the historical average rate and the weighted value corresponding to each terminal device, wherein the spectrum efficiency is used to represent the channel quality corresponding to the terminal device, in the case that the terminal device is an NR device, the weighted value is determined by the 5QI value corresponding to the NR device, in the case that the terminal device is a RedCap device, the weighted value is a preset fixed value; determining the waiting scheduling delay parameter corresponding to each terminal device, wherein the waiting scheduling delay parameter is the ratio of the cache delay of the non-GBR service data packet of the terminal device to the maximum queuing delay that the non-GBR service can tolerate; determining the second priority parameter corresponding to each terminal device according to the spectrum efficiency, the historical average rate, the weighted value, the waiting scheduling delay parameter, the first scheduling weight proportion and the second scheduling weight proportion corresponding to each terminal device; and ranking the terminal devices at the third basic priority according to the size of the second priority parameter, wherein the larger the second priority parameter is, the higher the priority of the terminal device is.

[0095] For example, the eMBB services of the industry video surveillance (IVS), the smart watch (WD) and the traditional commercial terminal all belong to non-GBR bearers, and the scheduling priorities of the three can be calculated according to the formula The following is an example of the calculation of the uplink and downlink scheduling priorities between the three.

[0096] For example, in the downlink scheduling process, the scheduling priority Priority IVS _ non-GBR as shown in the following formula:

[0097]

[0098] In the downlink scheduling process, the scheduling priority Priority WD _ non-GBR as shown in the following formula:

[0099]

[0100] According to experience, the rate and delay demand T eMBB ≤400ms, R eMBB ≤10Mbps of the daily eMBB service (web browsing, WeChat, short video, etc.) of the traditional commercial terminal. Therefore, in the present embodiment, it is assumed that the scheduling weight factor configuration γ 5QI of the commercial terminal is 0.7; then in the downlink scheduling process, the scheduling priority PriorityUE non-GBR As shown in the following formula:

[0101]

[0102] Assuming that condition 5 is met: the industry video monitoring terminal, smart watch and commercial terminal eMBB service are located in the same channel condition, i.e. IVS = eff WD = eff UE , and r IVS = r WD = r UE , and f IVS (delay) = f WD (delay) = f UE (delay), the scheduling priority of the industry video monitoring terminal: the scheduling priority of the smart watch: the scheduling priority of the commercial terminal eMBB service = 0.04:0.025:0.7 = 40:25:700. The scheduling priority of the industry video monitoring terminal, smart watch and commercial terminal eMBB service is sorted as: the commercial terminal eMBB service is prior to the industry video monitoring terminal, and the industry video monitoring terminal is prior to the smart watch.

[0103] Assuming that condition 6 is met: the industry video monitoring terminal, smart watch and commercial terminal eMBB service are located in different channel conditions, and the channel conditions of the industry video monitoring terminal and smart watch are better than the commercial terminal, for example IVS = eff WD = 8*eff UE , and r IVS = r WD = r UE , the waiting scheduling delay factor of the industry video monitoring terminal and smart watch is higher than that of the commercial terminal, for example IVS (delay) = f WD (delay) = 2*f UE (delay), the scheduling priority of the industry video monitoring terminal: the scheduling priority of the smart watch: the scheduling priority of the commercial terminal eMBB service = 0.64:0.4:0.7 = 64:40:70. The scheduling priority of the industry video monitoring terminal, smart watch and commercial terminal eMBB service is sorted as: the commercial terminal eMBB service is prior to the industry video monitoring terminal, and the industry video monitoring terminal is prior to the smart watch.

[0104] In the uplink scheduling process, the scheduling priority Priority IVS non-GBR As shown in the following formula:

[0105] ​​

[0106] In the uplink scheduling process, the scheduling priority Priority of the smart watch WD non-GBR As shown in the following formula:

[0107]

[0108] According to experience, the rate and delay requirement T of the daily conventional commercial terminal eMBB service (browsing web pages, WeChat, short video, etc.) eMBB ≤400ms, R eMBB ≤10Mbps. Therefore, in the present embodiment, it is assumed that the scheduling weight factor configuration γ of the commercial terminal 5QI =0.7; then in the uplink scheduling process, the scheduling priority Priority of the conventional commercial terminal eMBB service UE non-GBR As shown in the following formula:

[0109]

[0110] It is assumed that condition 7 is met: the industry video monitoring terminal, the smart watch and the commercial terminal eMBB service are located in the same channel condition, i.e. IVS =eff WD =eff UE , and r IVS =r WD =r UE , and f IVS (delay) =f WD (delay) =f UE (delay), then the scheduling priority of the industry video monitoring terminal: the scheduling priority of the smart watch: the scheduling priority of the commercial terminal eMBB service = 0.08:0.05:0.7 = 8:5:70. The uplink scheduling priority of the industry video monitoring terminal, the smart watch and the commercial terminal eMBB service is: the commercial terminal eMBB service is prior to the industry video monitoring terminal, and the industry video monitoring terminal is prior to the smart watch.

[0111] It is assumed that condition 8 is met: the industry video monitoring terminal, the smart watch and the commercial terminal eMBB service are located in different channel conditions, and the channel conditions of the industry video monitoring terminal and the smart watch are better than those of the commercial terminal, for example IVS =eff WD =8*eff UE , and r IVS =r WD =r UE The waiting scheduling delay factor of the industry video monitoring terminal and the smart watch is higher than that of the commercial terminal, for example​​IVS (delay) = f WD (delay) = 2*f UE (delay), the scheduling priority of the industry video monitoring terminal: the scheduling priority of the smart watch: the scheduling priority of the commercial terminal eMBB service = 1.28:0.8:0.7 = 128:80:70. The uplink scheduling priority of the industry video monitoring terminal, the smart watch and the commercial terminal eMBB service is sorted as: the industry video monitoring terminal is prior to the smart watch, and the smart watch is prior to the commercial terminal eMBB service.

[0112] In the coexistence of the above-mentioned multiple RedCap terminal devices: vehicle-mounted Tbox intelligent cockpit, industrial wireless sensor AGV, vehicle-mounted video call, industry video monitoring, smart watch and traditional commercial terminal devices belonging to NR UE, assuming that the above-mentioned conditions 1, 3, 5, 7 are met, the downlink scheduling priority of each terminal device is sorted as: the first basic priority (vehicle-mounted Tbox intelligent cockpit > industrial wireless sensor AGV) > the second basic priority (commercial terminal VoNR service > vehicle-mounted video call terminal) > the third basic priority (commercial terminal eMBB service > industry video monitoring terminal > smart watch); the uplink scheduling priority is sorted as: the first basic priority (vehicle-mounted Tbox intelligent cockpit > industrial wireless sensor AGV) > the second basic priority (commercial terminal VoNR service > vehicle-mounted video call terminal) > the third basic priority (commercial terminal eMBB service > industry video monitoring terminal > smart watch).

[0113] If it is assumed that the above-mentioned conditions 2, 4, 6, 8 are met, the downlink scheduling priority of each terminal device is sorted as: the first basic priority (vehicle-mounted Tbox intelligent cockpit > industrial wireless sensor AGV) > the second basic priority (vehicle-mounted video call terminal > commercial terminal VoNR service) > the third basic priority (commercial terminal eMBB service > industry video monitoring terminal > smart watch); the uplink scheduling priority is sorted as: the first basic priority (vehicle-mounted Tbox intelligent cockpit > industrial wireless sensor AGV) > the second basic priority (vehicle-mounted video call terminal > commercial terminal VoNR service) > the third basic priority (industry video monitoring terminal > smart watch > commercial terminal eMBB service).

[0114] In the embodiments of the present application, a coexistence scenario of a plurality of different types of Redcap terminals and conventional general commercial terminals is described, and the following is introduced: first, how to perform coarse sorting of scheduling priority according to 5QI bearer attributes; second, according to terminal type and terminal capability, calculate the scheduling weight ratio of RedCap UE relative to conventional UE; and finally, according to the delay requirement level and the rate requirement level, calculate the specific implementation process of the scheduling weight ratio of different services of RedCap UE relative to conventional UE. It should be noted that the embodiments of the present application scheme not only include the above embodiments, but also may include embodiments simpler than the above, such as Redcap terminal types less than the above types, and may also include embodiments more complex than the above, such as Redcap terminal types more than the above types. However, the calculation principle of the differentiated scheduling priority of RedCap UE and conventional UE, and different RedCap applications is consistent.

[0115] Through information interaction between the terminal and the base station side, the present application scheme can accurately obtain the capability, rate, delay and other service requirement information of different RedCap UEs, and dynamically calculate the scheduling weight ratio of RedCap UE relative to conventional UE according to the difference in the number of MIMO streams and the highest modulation order of conventional UE and RedCap UE, and accurately calculate the scheduling weight ratio of different services of RedCap UE relative to conventional UE according to the difference in the delay requirement and rate requirement of different services of RedCap UE and conventional UE, thereby realizing dynamic calculation of the weight factor, adapting to different RedCap terminal capabilities and service requirements, and the process is simple and efficient, and solves the problem that the associated 5QI and the actual 5QI established for the RedCap UE do not match when manually configuring the RedCap weight factor.

[0116] According to the embodiments of the present application, an embodiment of a scheduling device is also provided. Figure 3 is a structural schematic diagram of a scheduling device provided by the embodiments of the present application. As shown in Figure 3 , the device comprises:

[0117] The basic priority determination module 30 is configured to determine the fifth generation mobile communication technology service quality identifier 5QI bearer attribute corresponding to each terminal device accessing the base station network side, and determine the basic priority corresponding to the 5QI bearer attribute, wherein the terminal type of the terminal device includes a reduced capability RedCap device and a new radio NR device, the 5QI bearer attribute is used to represent the delay requirement level of the terminal device, and each type of 5QI bearer attribute corresponds to a basic priority.

[0118] The first weight determination module 32 is configured to determine a first scheduling weight ratio corresponding to the RedCap device in the terminal device according to the terminal capability information of the terminal device, wherein the first scheduling weight ratio is used to represent the relative difference degree of terminal capability between each RedCap device and the NR device.

[0119] The second weight determination module 34 is configured to determine a second scheduling weight ratio corresponding to the RedCap device according to the service requirement information of the terminal device, wherein the second scheduling weight ratio is used to represent the relative difference degree of service requirement between the RedCap device of different service types and the NR device.

[0120] The target priority determination module 36 is configured to perform priority sorting on a plurality of terminal devices located in the same basic priority according to the first scheduling weight ratio and the second scheduling weight ratio, and obtain a target priority sequence, wherein the target priority sequence is used to indicate the priority order of the terminal device for communication resource scheduling.

[0121] Optionally, determining the 5QI bearer attribute corresponding to each terminal device of the access base station network side comprises: obtaining the terminal information reported by the terminal device, wherein the terminal information comprises: terminal type, terminal capability information and service requirement information, and the service requirement information comprises: uplink and downlink rate requirement and delay requirement; determining the delay interval range corresponding to the delay requirement of the terminal device, and determining the 5QI bearer attribute corresponding to the delay interval range as the 5QI bearer attribute corresponding to the terminal device, wherein the 5QI bearer attribute comprises: delay-sensitive guaranteed bit rate delay-Critical GBR type, guaranteed bit rate GBR type and non-guaranteed bit rate non-GBR type.

[0122] Optionally, the basic priority comprises: a first basic priority, a second basic priority and a third basic priority, the first basic priority is higher than the second basic priority, and the second basic priority is higher than the third basic priority; determining the basic priority corresponding to the 5QI bearer attribute comprises: in the case that the 5QI bearer attribute of the terminal device is delay-Critical GBR, determining that the basic priority corresponding to the terminal device is the first basic priority; in the case that the 5QI bearer attribute of the terminal device is GBR, determining that the basic priority corresponding to the terminal device is the second basic priority; and in the case that the 5QI bearer attribute of the terminal device is non-GBR, determining that the basic priority corresponding to the terminal device is the third basic priority.

[0123] Optionally, determining the first scheduling weight ratio corresponding to the RedCap device in the terminal device according to the terminal capability information of the terminal device comprises: obtaining the terminal capability information of the RedCap device, wherein the terminal capability information comprises: a number of multiple-input multiple-output (MIMO) streams supported by the terminal device, and a maximum modulation order of uplink / downlink; determining a first ratio according to the number of MIMO streams, wherein the first ratio is a ratio of the number of MIMO streams supported by the RedCap device to the number of MIMO streams supported by the NR device; determining a second ratio according to the maximum modulation order of uplink / downlink, wherein the second ratio is a ratio of the maximum modulation order of uplink / downlink corresponding to the RedCap device to the maximum modulation order of uplink / downlink corresponding to the NR device; and determining the first scheduling weight ratio corresponding to the RedCap device according to the first ratio and the second ratio.

[0124] Optionally, the priority sorting of the plurality of terminal devices located in the same basic priority comprises: for the terminal devices located in the second basic priority, determining a channel quality parameter and a waiting scheduling delay parameter corresponding to each terminal device, wherein the waiting scheduling delay parameter is a ratio of a buffer delay of a GBR service data packet of the terminal device to a maximum queuing delay that can be tolerated by the GBR service; determining a first priority parameter corresponding to each terminal device according to the channel quality parameter, the waiting scheduling delay parameter, and the first scheduling weight ratio corresponding to each terminal device; and sorting the terminal devices located in the second basic priority according to the size of the first priority parameter, wherein the higher the first priority parameter, the higher the priority of the terminal device.

[0125] Optionally, determining the second scheduling weight ratio corresponding to the RedCap device according to the service requirement information of the terminal device comprises: determining a delay sensitivity level factor corresponding to the RedCap device, wherein the delay sensitivity level factor is a ratio of a delay requirement of an enhanced mobile broadband (eMBB) service of the NR device to a delay requirement of a service corresponding to the RedCap device; determining a rate requirement level factor corresponding to the RedCap device, wherein the rate requirement level factor is a ratio of an uplink / downlink rate requirement of the service corresponding to the RedCap device to an uplink / downlink rate requirement of the eMBB service of the NR device; and determining the second scheduling weight ratio corresponding to the RedCap device according to the delay sensitivity level factor and the rate requirement level factor.

[0126] Optionally, the priority ranking of the plurality of terminal devices under the same base priority further comprises: for the terminal devices under the third base priority, determining the spectrum efficiency, the historical average rate, and the weighted value corresponding to each terminal device, wherein the spectrum efficiency is used to represent the channel quality corresponding to the terminal device, the weighted value is determined by the 5QI value corresponding to the NR device in the case that the terminal device is an NR device, and the weighted value is a preset fixed value in the case that the terminal device is a RedCap device; determining the waiting scheduling delay parameter corresponding to each terminal device, wherein the waiting scheduling delay parameter is the ratio of the cache delay of the non-GBR service data packet of the terminal device to the maximum queuing delay that can be tolerated by the non-GBR service; determining the second priority parameter corresponding to each terminal device according to the spectrum efficiency, the historical average rate, the weighted value, the waiting scheduling delay parameter, the first scheduling weight proportion, and the second scheduling weight proportion of each terminal device; and ranking the terminal devices under the third base priority according to the size of the second priority parameter, wherein the higher the second priority parameter is, the higher the priority of the terminal device is.

[0127] Optionally, the priority ranking of the plurality of terminal devices under the same base priority further comprises: for the terminal devices under the first base priority, determining the latency requirement of each terminal device; and ranking the terminal devices under the first base priority according to the latency requirement, wherein the smaller the latency requirement is, the higher the priority of the terminal device is.

[0128] It should be noted that each module in the above scheduling apparatus can be a program module (for example, a set of program instructions for implementing a certain specific function) or a hardware module. For the latter, it can be in the form of, but not limited to, a processor, or the functions of the above modules are implemented by a processor.

[0129] It should be noted that the scheduling apparatus provided in the present embodiment can be used to execute the scheduling method shown in the present embodiment, and therefore the related explanations and descriptions of the above scheduling method are also applicable to the present embodiment, which will not be described here again. Figure 1

[0130] According to the present embodiment, an embodiment of a scheduling system is also provided. Figure 4 is a structural schematic diagram of a scheduling system provided by the present embodiment. As shown in the figure, the system comprises a terminal device 40 and a base station network side device 42, wherein the terminal device 40 comprises a terminal information reporting module, and the base station network side device 42 comprises a terminal information obtaining module, a bearer distinguishing module, and a scheduling control module. Figure 4

[0131] ​​The terminal device 40 is configured to report terminal information to the base station network side device, wherein the terminal information comprises a terminal type, terminal capability information and service demand information, and the terminal type comprises a reduced capability RedCap device and a new radio NR device.

[0132] The base station network side device 42 is configured to determine a fifth generation mobile communication technology service quality identifier 5QI bearer attribute corresponding to each terminal device 40 accessing the base station network side, and determine a basic priority corresponding to the 5QI bearer attribute, wherein the 5QI bearer attribute is used to represent a latency requirement level of the terminal device 40, each type of 5QI bearer attribute corresponds to a basic priority; determine a first scheduling weight ratio corresponding to the RedCap device in the terminal device 40 according to the terminal capability information of the terminal device 40, wherein the first scheduling weight ratio is used to represent a relative difference degree of terminal capability between each RedCap device and NR device; determine a second scheduling weight ratio corresponding to the RedCap device according to the service demand information of the terminal device 40, wherein the second scheduling weight ratio is used to represent a relative difference degree of service demand between the RedCap device and the NR device of different service types; and perform priority sorting on a plurality of terminal devices 40 located in the same basic priority according to the first scheduling weight ratio and the second scheduling weight ratio, to obtain a target priority sequence, wherein the target priority sequence is used to indicate a priority order of communication resource scheduling for the terminal device 40.

[0133] It should be noted that each module in the above scheduling system can be a program module (for example, a program instruction set for implementing a certain specific function) or a hardware module. For the latter, it can be in the following form, but is not limited to this: the form of each module is a processor, or the functions of each module are implemented by a processor.

[0134] It should be noted that the scheduling system provided in the present embodiment can be used to execute the scheduling method shown in the present embodiment, and therefore the related explanations of the above scheduling method also apply to the present embodiment, which will not be described here. Figure 1

[0135] According to the present embodiment, an embodiment of an electronic device is also provided. Figure 5 A hardware structure block diagram of a computer terminal (or electronic device) for implementing the scheduling method is shown. As shown in FIG. 8, the computer terminal comprises a processor 801, a memory 802, a bus 803, a communication interface 804 and a power supply 805. Figure 5 ​As shown, the computer terminal 50 (or electronic device) may include one or more (502a, 502b, ..., 502n are used to illustrate) processors 502 (the processor 502 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 504 for storing data, and a transmission device 506 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It will be understood by those skilled in the art that Figure 5 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 5 More or fewer components than shown, or with Figure 5 Different configurations shown.

[0136] It should be noted that the one or more processors 502 and / or other data processing circuits described above may generally be referred to herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuitry may be a single independent processing module, or may be incorporated in whole or in part into any of the other components of the computer terminal 50 (or electronic device). As described in the embodiments of the present application, the data processing circuitry serves as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0137] The memory 504 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the scheduling method in the embodiment of the present application. The processor 502 executes various functional applications and data processing by running the software programs and modules stored in the memory 504, that is, implementing the above-mentioned scheduling method. The memory 504 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 504 may further include a memory remotely located relative to the processor 502, and these remote memories may be connected to the computer terminal 50 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0138] The transmission device 506 is configured to receive or send data via a network. The network can include a wireless network provided by a communication provider of the computer terminal 50. In one example, the transmission device 506 includes a network interface controller (NIC) that can connect to other network devices through a base station to communicate with the Internet. In one example, the transmission device 506 can be a radio frequency (RF) module that is configured to communicate with the Internet wirelessly.

[0139] The display can be a liquid crystal display (LCD) that is touch screen, for example, which can enable a user to interact with a user interface of the computer terminal 50 (or electronic device).

[0140] The embodiment of the present application further provides a non-volatile storage medium, and the non-volatile storage medium comprises a stored computer program, wherein a device where the non-volatile storage medium is located executes the following scheduling method by running the computer program: determining fifth generation mobile communication technology service quality identifier 5QI bearer attributes corresponding to each terminal device of an access base station network side, and determining a basic priority corresponding to the 5QI bearer attributes, wherein terminal types of the terminal device include a reduced capability RedCap device and a new radio NR device, the 5QI bearer attributes are used to represent a time delay requirement level of the terminal device, and each type of 5QI bearer attribute corresponds to a basic priority; determining a first scheduling weight proportion corresponding to the RedCap device in the terminal device according to terminal capability information of the terminal device, wherein the first scheduling weight proportion is used to represent a relative difference degree of terminal capability between each RedCap device and the NR device; determining a second scheduling weight proportion corresponding to the RedCap device according to service requirement information of the terminal device, wherein the second scheduling weight proportion is used to represent a relative difference degree of service requirement between the RedCap device and the NR device of different service types; and performing priority sorting on a plurality of terminal devices located in the same basic priority according to the first scheduling weight proportion and the second scheduling weight proportion, to obtain a target priority sequence, wherein the target priority sequence is used to indicate a priority order of communication resource scheduling for the terminal device.

[0141] The embodiment of the application further provides a computer program product comprising a computer program, which, when executed by a processor, implements the steps of the scheduling method described in various embodiments of the application: determining fifth generation mobile communication technology quality of service identifier 5QI bearer attributes corresponding to each terminal device on the network side of an access base station, and determining a basic priority corresponding to the 5QI bearer attributes, wherein the terminal type of the terminal device includes a reduced capability RedCap device and a new radio NR device, the 5QI bearer attribute is used to represent the latency requirement level of the terminal device, and each type of 5QI bearer attribute corresponds to a basic priority; determining a first scheduling weight ratio corresponding to the RedCap device in the terminal device according to terminal capability information of the terminal device, wherein the first scheduling weight ratio is used to represent the relative difference degree of terminal capability between each RedCap device and the NR device; determining a second scheduling weight ratio corresponding to the RedCap device according to service requirement information of the terminal device, wherein the second scheduling weight ratio is used to represent the relative difference degree of service requirements between the RedCap device and the NR device of different service types; and performing priority sorting on a plurality of terminal devices located in the same basic priority according to the first scheduling weight ratio and the second scheduling weight ratio, to obtain a target priority sequence, wherein the target priority sequence is used to indicate the priority order of the terminal device for communication resource scheduling.

[0142] The above sequence numbers of the embodiments of the application are only for description, and do not represent the advantages or disadvantages of the embodiments.

[0143] In the above embodiments of the application, the description of each embodiment has its own emphasis, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0144] In the several embodiments provided by the present application, it should be understood that the disclosed technology can be implemented in other ways. Of course, the unit described as the division is only a logical function division, and there can be other division manners in actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, unit or module, and can be electrical or other forms.

[0145] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on multiple units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0146] In addition, each function unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software function unit.

[0147] When the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.

[0148] The above is only the preferred embodiment of the present application, and it should be pointed out that, for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, and these improvements and refinements should be regarded as the protection scope of the present application.

Claims

1. A scheduling method, characterized by, The method comprises the steps of: determining the fifth generation mobile communication technology service quality identifier 5QI bearer attribute corresponding to each terminal device on the network side of the access base station, and determining the basic priority corresponding to the 5QI bearer attribute, wherein the terminal type of the terminal device comprises a reduced capability RedCap device and a new radio NR device, the 5QI bearer attribute is used to represent the delay requirement level of the terminal device, and each type of the 5QI bearer attribute corresponds to a basic priority; determining the first scheduling weight ratio corresponding to the RedCap device in the terminal device according to terminal capability information of the terminal device, wherein the terminal capability information comprises a multiple-input multiple-output stream number supported by the terminal device, and uplink / downlink maximum modulation order, the first scheduling weight ratio is used to represent the relative difference degree of terminal capability between each RedCap device and the NR device; the step of determining the first scheduling weight ratio corresponding to the RedCap device in the terminal device comprises: determining a first ratio value according to the multiple-input multiple-output stream number, wherein the first ratio value is a ratio of the multiple-input multiple-output stream number supported by the RedCap device to the multiple-input multiple-output stream number supported by the NR device; determining a second ratio value according to the uplink / downlink maximum modulation order, wherein the second ratio value is a ratio of the uplink / downlink maximum modulation order corresponding to the RedCap device to the uplink / downlink maximum modulation order corresponding to the NR device; and determining the first scheduling weight ratio corresponding to the RedCap device according to the first ratio value and the second ratio value; determining the second scheduling weight ratio corresponding to the RedCap device according to service requirement information of the terminal device, wherein the second scheduling weight ratio is used to represent the relative difference degree of service requirement between the RedCap device and the NR device of different service types; performing priority sorting on a plurality of terminal devices located in the same basic priority according to the first scheduling weight ratio and the second scheduling weight ratio, to obtain a target priority sequence, wherein the target priority sequence is used to indicate the priority order of the terminal device for communication resource scheduling.

2. The scheduling method of claim 1, wherein, The method comprises the steps of: obtaining terminal information reported by the terminal device, wherein the terminal information comprises the terminal type, the terminal capability information and the service requirement information, and the service requirement information comprises uplink / downlink rate requirement and delay requirement; determining a delay interval range corresponding to the delay requirement of the terminal device, and determining the 5QI bearer attribute corresponding to the delay interval range as the 5QI bearer attribute corresponding to the terminal device, wherein the 5QI bearer attribute comprises a delay-sensitive guaranteed bit rate delay-Critical GBR type, a guaranteed bit rate GBR type and a non-guaranteed bit rate non-GBR type.

3. The scheduling method of claim 2, wherein, The base priorities include: a first base priority, a second base priority, and a third base priority, the first base priority is higher than the second base priority, and the second base priority is higher than the third base priority; determining the base priority corresponding to the 5QI bearer attribute includes: In a case where the 5QI bearer attribute of the terminal device is delay-Critical GBR, determining that the base priority corresponding to the terminal device is the first base priority; In a case where the 5QI bearer attribute of the terminal device is GBR, determining that the base priority corresponding to the terminal device is the second base priority; In a case where the 5QI bearer attribute of the terminal device is non-GBR, determining that the base priority corresponding to the terminal device is the third base priority.

4. The scheduling method of claim 3, wherein, The priority sorting of the plurality of terminal devices located in the same base priority includes: For the terminal devices located in the second base priority, determining a channel quality parameter and a waiting scheduling delay parameter corresponding to each terminal device, wherein the waiting scheduling delay parameter is a ratio of a buffer delay of GBR service data packets of the terminal device to a maximum queuing delay that can be tolerated by GBR service; determining a first priority parameter corresponding to each terminal device according to the channel quality parameter, the waiting scheduling delay parameter, and the first scheduling weight proportion corresponding to each terminal device; sorting the terminal devices in the second base priority according to the size of the first priority parameter, wherein the larger the first priority parameter is, the higher the priority of the terminal device is.

5. The scheduling method of claim 3, wherein, Determining the second scheduling weight proportion corresponding to the RedCap device according to the service requirement information of the terminal device includes: determining a delay sensitivity level factor corresponding to the RedCap device, wherein the delay sensitivity level factor is a ratio of a delay requirement corresponding to an enhanced mobile broadband service of the NR device to a delay requirement of a service corresponding to the RedCap device; determining a rate requirement level factor corresponding to the RedCap device, wherein the rate requirement level factor is a ratio of an uplink and downlink rate requirement of a service corresponding to the RedCap device to an uplink and downlink rate requirement corresponding to an enhanced mobile broadband service of the NR device; determining the second scheduling weight proportion corresponding to the RedCap device according to the delay sensitivity level factor and the rate requirement level factor.

6. The scheduling method of claim 5, wherein, The priority sorting of the plurality of terminal devices located in the same base priority also includes: For the terminal devices located under the third basic priority, determine the spectral efficiency corresponding to each terminal device, the historical average rate, and the weighting value, wherein the spectral efficiency is used to represent the channel quality corresponding to the terminal device, in the case of NR device, the weighting value is determined by the 5QI value corresponding to the NR device, in the case of RedCap device, the weighting value is a preset fixed value; Determine the waiting scheduling delay parameter corresponding to each terminal device, wherein the waiting scheduling delay parameter is the ratio of the buffer delay of the non-GBR service data packet of the terminal device to the maximum queuing delay that the non-GBR service can tolerate; According to the spectral efficiency, the historical average rate, the weighting value, the waiting scheduling delay parameter, the first scheduling weight ratio, and the second scheduling weight ratio corresponding to each terminal device, determine the second priority parameter corresponding to each terminal device; According to the size of the second priority parameter, sort the terminal devices under the third basic priority, wherein the larger the second priority parameter is, the higher the priority of the terminal device is.

7. The scheduling method of claim 3, wherein, The priority sorting of the plurality of terminal devices located under the same basic priority further includes: For the terminal devices located under the first basic priority, determine the delay requirement of each terminal device; According to the delay requirement, sort the terminal devices under the first basic priority, wherein the smaller the delay requirement requires, the higher the priority of the terminal device is.

8. A scheduling apparatus characterized by comprising: It includes: A basic priority determination module is configured to determine the fifth generation mobile communication technology service quality identifier (5QI) bearer attribute corresponding to each terminal device accessing the base station network side, and determine the basic priority corresponding to the 5QI bearer attribute, wherein the terminal type of the terminal device includes a reduced capability (RedCap) device and a new radio (NR) device, the 5QI bearer attribute is used to represent the delay requirement level of the terminal device, and each type of the 5QI bearer attribute corresponds to a basic priority. The first weight determination module is configured to determine a first scheduling weight ratio corresponding to the RedCap device in the terminal device according to terminal capability information of the terminal device, wherein the terminal capability information includes a number of multiple-input multiple-output (MIMO) streams supported by the terminal device, a maximum uplink / downlink modulation order, and the first scheduling weight ratio is used to represent a relative difference degree of terminal capability between each RedCap device and the NR device; the determination of the first scheduling weight ratio corresponding to the RedCap device in the terminal device includes: determining a first ratio value according to the number of MIMO streams, wherein the first ratio value is a ratio of the number of MIMO streams supported by the RedCap device to the number of MIMO streams supported by the NR device; determining a second ratio value according to the maximum uplink / downlink modulation order, wherein the second ratio value is a ratio of the maximum uplink / downlink modulation order corresponding to the RedCap device to the maximum uplink / downlink modulation order corresponding to the NR device; and determining the first scheduling weight ratio corresponding to the RedCap device according to the first ratio value and the second ratio value; The second weight determination module is configured to determine a second scheduling weight ratio corresponding to the RedCap device according to service requirement information of the terminal device, wherein the second scheduling weight ratio is used to represent a relative difference degree of service requirement between the RedCap device and the NR device of different service types; The target priority determination module is configured to perform priority sorting on a plurality of terminal devices located in the same basic priority according to the first scheduling weight ratio and the second scheduling weight ratio, to obtain a target priority sequence, wherein the target priority sequence is used to indicate a priority order of communication resource scheduling for the terminal devices.

9. A dispatch system characterized by, The terminal device and the base station network side device are included, wherein The terminal device is configured to report terminal information to the base station network side device, wherein the terminal information includes a terminal type, terminal capability information, and service requirement information, and the terminal type includes a reduced capability (RedCap) device and a new radio (NR) device. ​ The base station network side device is configured to determine a fifth generation mobile communication technology service quality identifier (5QI) bearer attribute corresponding to each terminal device accessing the base station network side, and determine a basic priority corresponding to the 5QI bearer attribute, wherein the 5QI bearer attribute is used to represent a latency requirement level of the terminal device, and each type of 5QI bearer attribute corresponds to a basic priority; determine a first scheduling weight ratio corresponding to the RedCap device in the terminal device according to terminal capability information of the terminal device, wherein the terminal capability information includes a multiple-input multiple-output stream number supported by the terminal device, and an uplink / downlink maximum modulation order, and the first scheduling weight ratio is used to represent a relative difference degree of terminal capability between each RedCap device and the NR device; the determination of the first scheduling weight ratio corresponding to the RedCap device in the terminal device includes: determining a first ratio value according to the multiple-input multiple-output stream number, wherein the first ratio value is a ratio of the multiple-input multiple-output stream number supported by the RedCap device to the multiple-input multiple-output stream number supported by the NR device; determining a second ratio value according to the uplink / downlink maximum modulation order, wherein the second ratio value is a ratio of the uplink / downlink maximum modulation order corresponding to the RedCap device to the uplink / downlink maximum modulation order corresponding to the NR device; determining the first scheduling weight ratio corresponding to the RedCap device according to the first ratio value and the second ratio value; determining a second scheduling weight ratio corresponding to the RedCap device according to service requirement information of the terminal device, wherein the second scheduling weight ratio is used to represent a relative difference degree of service requirement between the RedCap device and the NR device of different service types; and performing priority sorting on a plurality of terminal devices located in the same basic priority according to the first scheduling weight ratio and the second scheduling weight ratio, to obtain a target priority sequence, wherein the target priority sequence is used to indicate a priority order of communication resource scheduling for the terminal device.

10. An electronic device, comprising: Comprise: A memory and a processor, the processor is used to run the program stored in the memory, wherein the program runs to execute the scheduling method of any one of claims 1 to 7.

11. A non-volatile storage medium, comprising: The non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the scheduling method of any one of claims 1 to 7 by running the computer program.

12. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the scheduling method of any one of claims 1 to 7.

Images