Network resource scheduling method and apparatus, electronic device, medium, and program product

Abstract

This application provides a network resource scheduling method, apparatus, electronic device, medium, and program product, relating to the field of communications. The method includes: determining the device type and service characteristics of a terminal device accessing the network; the device type includes lightweight terminals and enhanced terminals; the service characteristics include service type, service data packet transmission frequency, and mobility patterns; then, based on the determined device type and service characteristics, classifying the services of the terminal device into corresponding service clusters to determine the service cluster to which the terminal device's services belong; finally, dynamically scheduling network resources for the corresponding terminal device based on the device type, service cluster, and the current network load of the partial bandwidth BWP. This application embodiment can dynamically guarantee the resource needs of terminal devices, collaboratively ensure the user experience of different terminals under limited resource conditions, and ensure the normal operation of multiple services in scenarios where RedCap / eRedCap and eMBB coexist.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a network resource scheduling method, apparatus, electronic device, medium, and program product. Background Technology

[0002] In 5G / 5G-A networks, mMTC (Massive Machine-Type Communications) has always been a key application scenario, and it extends to 6G with applications such as ultra-large-scale connectivity and ubiquitous connectivity. To meet the needs of medium-to-high speed, low power consumption, and low cost 5G applications, RedCap / eRedCap technologies have emerged. 3GPP Release 17 defines the RedCap standard, and Release 18 defines the eRedCap standard. Currently, RedCap technology is mainly used in actual networks, while eRedCap is still in the early stages of industrial development and technical testing.

[0003] As RedCap terminal devices become more abundant and their applications expand, and eRedCap gradually becomes commercially available, a large number of eMBB, RedCap / eRedCap terminal devices will share limited network resources. Therefore, how to achieve reasonable scheduling of network resources in scenarios where RedCap / eRedCap terminal devices and eMBB terminal devices coexist has become an urgent technical problem to be solved. Summary of the Invention

[0004] This application provides a network resource scheduling method, apparatus, electronic device, medium, and program product, which can achieve reasonable scheduling of network resources in scenarios where RedCap / eRedCap terminal devices and eMBB terminal devices coexist. The technical solution is as follows: According to one aspect of the embodiments of this application, a network resource scheduling method is provided, the method comprising: Determine the device type of the terminal equipment accessing the network and the service characteristics of the services. Device types include lightweight terminals and enhanced terminals, and service characteristics include service type, service data packet transmission frequency, and mobility patterns. Based on the determined device type and service characteristics, the services of the terminal device are classified into corresponding service clusters to determine the service cluster to which the terminal device's services belong; Based on the device type, service cluster, and the current network load of the partial bandwidth BWP, network resources are dynamically scheduled for the corresponding terminal devices.

[0005] In one possible implementation, the service characteristics of the terminal devices accessing the network are determined, including: The service type of the terminal device is obtained by evaluating its data transmission direction and service data packet size based on the terminal device's identification information. The frequency of service data packet transmission and the stability of data transmission of the terminal device are evaluated based on the identification information of the terminal device to obtain the frequency of service data packet transmission of the terminal device. Based on the multiple moving positions of the terminal device within a predetermined period, its moving range or moving radius is determined, and the moving pattern of the terminal device is obtained.

[0006] In one possible implementation, based on the determined device type and service characteristics, the services of the terminal device are categorized into service clusters to determine the service cluster to which the terminal device's services belong, including: The service type, service data packet transmission frequency, and movement pattern are normalized to obtain the service feature vector; Based on the service feature vector, the probability of each service of the terminal device of this type belonging to each service cluster is determined, and the services are classified into service clusters according to the probability to obtain the service cluster to which the terminal device's services belong.

[0007] In one possible implementation, network resources are dynamically scheduled for the corresponding terminal device based on the device type, service cluster, and current network load of the BWP, including: The service weight of the target service is determined based on the queuing status of the target service on the terminal device according to the service cluster and device type. Determine the business priority of the target business based on business weight; Based on service priority and the current network load of BWP, network resources are dynamically allocated to the corresponding terminal devices.

[0008] In one possible implementation, the business priority of the target business is determined based on business weights, including: Determine the business value density of the target business based on its business weight; The scheduling priority of target services is determined based on the service value density.

[0009] In one possible implementation, network resources are dynamically scheduled for the corresponding terminal devices based on service priority and the current network load of the BWP, including: When the current network load of BWP is determined to be less than or equal to the preset resource leniency threshold, network resources are dynamically allocated to the corresponding terminal devices according to the service priority of the target service through the efficiency-first network resource scheduling mode. When the current network load of BWP is determined to be greater than or equal to the preset resource shortage threshold, network resources are dynamically allocated to the corresponding terminal devices according to the service priority of the target service through a grouped round-robin network resource scheduling mode. When it is determined that the current network load of BWP is greater than the preset resource easing threshold and less than the preset resource strain threshold, network resources are dynamically allocated to the corresponding terminal devices according to the service priority of the target service through a hybrid network resource scheduling mode. The hybrid network resource scheduling mode is a combination of the efficiency-first network resource scheduling mode and the group round-robin network resource scheduling mode.

[0010] According to another aspect of the embodiments of this application, a network resource scheduling apparatus is provided, the apparatus comprising: The first processing module is used to determine the device type of the terminal device accessing the network and the service characteristics of the service. The device type includes lightweight terminals and enhanced terminals, and the service characteristics include service type, service data packet transmission frequency and movement pattern. The second processing module is used to classify the services of the terminal device into corresponding service clusters based on the determined device type and service characteristics, and to determine the service cluster to which the terminal device's services belong. The third processing module is used to dynamically schedule network resources for the corresponding terminal devices based on the device type, service cluster, and the current network load of the partial bandwidth BWP.

[0011] In one possible implementation, when determining the service characteristics of the terminal device accessing the network, the first processing module is used to: The service type of the terminal device is obtained by evaluating its data transmission direction and service data packet size based on the terminal device's identification information. The frequency of service data packet transmission and the stability of data transmission of the terminal device are evaluated based on the identification information of the terminal device to obtain the frequency of service data packet transmission of the terminal device. Based on the multiple moving positions of the terminal device within a predetermined period, its moving range or moving radius is determined, and the moving pattern of the terminal device is obtained.

[0012] In one possible implementation, when the second processing module categorizes the services of the terminal device into corresponding service clusters based on the determined device type and service characteristics, and determines the service cluster to which the terminal device's services belong, it is used to: The service type, service data packet transmission frequency, and movement pattern are normalized to obtain the service feature vector; Based on the service feature vector, the probability of each service of the terminal device belonging to each service cluster is determined, and the services are classified into service clusters according to the probability to obtain the service cluster to which the terminal device's services belong.

[0013] In one possible implementation, when the third processing module dynamically schedules network resources for the corresponding terminal device based on the device type, service cluster, and current BWP network load, it is used to: The service weight of the target service is determined based on the queuing status of the target service on the terminal device according to the service cluster and device type. Determine the business priority of the target business based on business weight; Based on service priority and the current network load of BWP, network resources are dynamically allocated to the corresponding terminal devices.

[0014] In one possible implementation, when determining the business priority of the target business based on business weights, the third processing module is used for: Determine the business value density of the target business based on its business weight; The scheduling priority of target services is determined based on the service value density.

[0015] In one possible implementation, when the third processing module dynamically schedules network resources for the corresponding terminal device based on service priority and the current network load of the BWP, it is used to: When the current network load of BWP is determined to be less than or equal to the preset resource leniency threshold, network resources are dynamically allocated to the corresponding terminal devices according to the service priority of the target service through the efficiency-first network resource scheduling mode. When the current network load of BWP is determined to be greater than or equal to the preset resource shortage threshold, network resources are dynamically allocated to the corresponding terminal devices according to the service priority of the target service through a grouped round-robin network resource scheduling mode. When it is determined that the current network load of BWP is greater than the preset resource easing threshold and less than the preset resource strain threshold, network resources are dynamically allocated to the corresponding terminal devices according to the service priority of the target service through a hybrid network resource scheduling mode. The hybrid network resource scheduling mode is a combination of the efficiency-first network resource scheduling mode and the group round-robin network resource scheduling mode.

[0016] According to another aspect of the present application, an electronic device is provided, comprising: a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the network resource scheduling method described above.

[0017] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, wherein when a computer program is executed by a processor, it implements the steps of the network resource scheduling method described above.

[0018] According to another aspect of the embodiments of this application, a computer program product is provided, which, when executed by a processor, implements the steps of the network resource scheduling method described above.

[0019] The beneficial effects of the technical solution provided in this application are as follows: by identifying the device type and service characteristics of eMBB terminals and RedCap / eRedCap terminals, classifying them based on service clusters, and comprehensively considering factors such as service characteristics, performance requirements, and BWP carrying efficiency, network resources can be dynamically scheduled. This enables dynamic protection of the resource requirements of RedCap / eRedCap and eMBB, ensuring not only the user experience of eMBB terminals and RedCap / eRedCap terminals under limited resource conditions, but also the normal operation of multiple services in scenarios where RedCap / eRedCap and eMBB coexist. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0021] Figure 1 A flowchart illustrating a network resource scheduling method provided in an embodiment of this application; Figure 2 This is a schematic diagram of the structure of a network resource scheduling device provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0022] The embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the embodiments described below with reference to the accompanying drawings illustrate some embodiments in which the principles of this application can be adopted, and are exemplary descriptions used to explain the technical solutions of the embodiments of this application. They do not constitute a limitation on the technical solutions of the embodiments of this application. On the contrary, this application includes all modifications, variations and equivalents falling within the scope of the appended claims.

[0023] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used in the embodiments of this application may also include plural forms and should be broadly interpreted as “a kind” or “a class” rather than limited to the meaning of “an.” Furthermore, the term “the” should be understood to include both singular and plural forms unless the context clearly indicates otherwise. Additionally, the term “according to” should be understood as “at least partially based on…”, and the term “based on” should be understood as “at least partially based on…”, unless the context clearly indicates otherwise.

[0024] The terms "comprising," "including," "having," etc., as used in the embodiments of this application refer to the presence of the presented features, information, data, steps, operations, elements, components, and / or components, but do not exclude the presence of other features, information, data, steps, operations, elements, components, and / or combinations thereof.

[0025] The terms "first," "second," etc., used in the embodiments of this application are used to distinguish different features, information, data, steps, operations, elements, components, devices, modules, or units by name, but do not indicate the spatial arrangement, temporal order, or interdependence of these features, information, data, steps, operations, elements, components, devices, modules, or units, nor are they used to limit these devices, modules, or units to necessarily being different devices, modules, or units. The term "and / or" includes any one and all combinations of one or more of the associated listed terms, for example, "A and / or B" indicates implementation as "A," or implementation as "A," or implementation as "A and B." The term "multiple" refers to two or more, and other quantifiers are similar.

[0026] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0027] First, let me introduce and explain some of the terms used in this application: RedCap: Reduced Capability, a lightweight technology; eRedCap: Enhanced Reduced Capability, an enhanced lightweight technology; eMBB: Enhanced Mobile Broadband; mMTC: Massive Machine-Type Communications; MC: Massive Communication; UC: Ubiquitous Connectivity; BWP: Bandwidth Part; UE: User Equipment; RSRP: Reference Signal Receiving Power; SINR: Signal to Interference plus Noise Ratio; UL: Up Load; DL: Download; RB: Resource Block; CCE: Control Channel Elements; PDSCH: Physical Downlink Shared Channel; PUSCH: Physical Uplink Shared Channel; AL: Aggregation Level; 5QI: 5G Quality of Service Identifier, is an important parameter in 5G networks used to identify different service types and service quality requirements. It determines key performance indicators such as data transmission priority, rate, and latency, thereby ensuring that different types of services receive appropriate service guarantees.

[0028] Terminal devices that can access the network may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptops, cordless phones, smartphones, smartwatches, digital cameras, etc.

[0029] With the emergence of a large number of eMBB and RedCap / eRedCap terminal devices sharing limited resources in the network, the resource selection or scheduling methods for eMBB and RedCap / eRedCap terminal devices include the following: Method 1: Treat RedCap and eMBB terminal devices equally, differing only in the frequency resources available to them. For example, eMBB terminal devices can utilize the entire 2.6GHz band, while RedCap terminal devices can only use the 2.6GHz BWP resources with software functionality enabled. There is no significant difference between RedCap and eMBB terminal devices in terms of frequency residency policies and resource scheduling priorities.

[0030] Method 2: Set scheduling priorities based on business and performance metrics, such as 5QI, penetration rate, and scheduling failure rate. For example, dynamically adjust priorities based on the scheduling failure rate, increasing the priority of RedCap terminal devices with high failure rates. In terms of scheduling methods, consider prioritizing the allocation of eMBB terminal devices outside the preset scheduling frequency domain range of RedCap terminal devices. Alternatively, the basic priority depends on 5QI, while also incorporating weighting factors such as terminal capability, latency, and rate. Under the same priority, further sorting is performed by considering factors such as channel quality and spectral efficiency to determine the final target priority.

[0031] However, current 3GPP standards only provide macro-level guidance for RedCap terminal equipment in terms of resource capabilities, bandwidth limitations, and protocol simplification. When eMBB and RedCap terminal equipment share scheduling resources, they lack fine-grained dynamic scheduling strategies and optimization methods. Existing scheduling strategies are generally based on spectrum fairness design, failing to fully utilize the differences in latency sensitivity and bandwidth requirements of different services, easily leading to inefficient service guarantees and increased interference. Furthermore, RedCap technology is primarily applied in scenarios such as video conferencing, vehicle-to-everything (V2X) connectivity, wearable devices, industrial sensing, and power control. Considering the potential future upgrade from 4G to 5G RedCap / eRedCap modules, it will support a wider range of applications. On the one hand, these application scenarios differ greatly in performance requirements such as main transmission directions (uplink / downlink), service rates, connection scale, and latency sensitivity. On the other hand, even in video conferencing and V2X scenarios that also include video services, the requirements for video service transmission are not entirely the same. Therefore, when using a single indicator such as 5QI to differentiate services, there may be situations where multiple different services are mapped to the same 5QI value, resulting in insufficient differentiation of services and the masking of service differences. Moreover, applying the same 5QI strategy to RedCap / eRedCap terminal devices and eMBB terminal devices can easily lead to a mismatch between the protection effect and service requirements, thus reducing the effectiveness of experience protection.

[0032] In response to the above situation, this application proposes a network resource scheduling method, apparatus, electronic device, medium, and program product. The technical solutions of this application and their effects are explained below through the description of several exemplary embodiments. It should be noted that the following embodiments can be referenced, borrowed from, or combined with each other. Identical terms, similar features, and similar implementation steps in different embodiments will not be repeated.

[0033] Figure 1 This is a flowchart illustrating the network resource scheduling method provided in the embodiments of this application, as shown below. Figure 1As shown, the method includes: step S110, determining the device type and service characteristics of the terminal devices accessing the network, where the device type includes lightweight terminals and enhanced terminals, and the service characteristics include service type, service data packet transmission frequency, and mobility patterns; step S120, classifying the services of the terminal devices into corresponding service clusters based on the determined device type and service characteristics, and determining the service cluster to which the terminal device's services belong; and step S130, dynamically scheduling network resources for the corresponding terminal devices based on the device type, service cluster, and the current network load of the partial bandwidth BWP.

[0034] In one implementation, determining the device type of a terminal device accessing the network is equivalent to distinguishing the user type of the terminal device, that is, determining whether the terminal device accessing the network is an eMBB terminal (i.e., an enhanced terminal) or a RedCap / eRedCap terminal (i.e., a lightweight terminal). This determination process can be achieved when the terminal obtains the RedCap identifier through msg1, msg3, or UE capability information during the access phase, and the distinction between eMBB terminals and RedCap / eRedCap terminals is made based on this RedCap identifier. For example, if the RedCap identifier is obtained, its device type is determined to be a lightweight terminal (such as a RedCap / eRedCap terminal); if the RedCap identifier is not obtained, its device type is determined to be an enhanced terminal (such as an eMBB terminal).

[0035] Determine the service characteristics of terminal devices accessing the network, i.e., identify the service types of eMBB terminals and RedCap / eRedCap terminals. In practical applications, the service characteristics of terminal devices accessing the network can be determined by service type, frequency of service data packet transmission, and mobility patterns (or mobility habits).

[0036] After determining the device type and service characteristics of the terminal devices accessing the network, the services of the terminal devices can be classified into service clusters (or soft classification of service clusters) based on the identified device type and service characteristics. This determines the service cluster to which the terminal devices belong, that is, the various services of the terminal devices are assigned to their respective service clusters.

[0037] After obtaining the service characteristics and soft classification of various services of the terminal equipment accessing the network, a certain amount of network resources (such as RB) can be pre-allocated to the terminal equipment as a safety net. The amount of pre-allocated network resources can be allocated separately based on statistics of each cell. Furthermore, to ensure that the minimum CCE of the services of the terminal equipment accessing the network matches the service plane safety net RB, and to avoid situations such as control plane commands being issued but data being unable to be scheduled, or data resources being idle but no users using them, the minimum reserved CCE resources are calculated based on the AL constraints of CCE (3GPP standard). .

[0038] Next, network resources are dynamically allocated to the terminal devices based on their device type, service cluster, and the current network load of the partial bandwidth BWP. During this allocation process, network resources can be dynamically allocated to the corresponding terminal devices based on their service characteristics, performance requirements, and network operating conditions.

[0039] This application provides a network resource scheduling method for scenarios where RedCap / eRedCap terminals and eMBB terminals coexist. By identifying the device types and service characteristics of eMBB terminals and RedCap / eRedCap terminals, classifying them based on service clusters, and comprehensively considering factors such as service characteristics, performance requirements, and BWP carrying efficiency, network resources are dynamically scheduled. This allows for dynamic guarantee of the resource needs of RedCap / eRedCap and eMBB, not only ensuring the user experience of eMBB terminals and RedCap / eRedCap terminals under limited resource conditions, but also ensuring the normal operation of multiple services in scenarios where RedCap / eRedCap and eMBB coexist.

[0040] In one possible implementation of this application, determining the service characteristics of a terminal device accessing the network includes: evaluating the data transmission direction and service data packet size of the terminal device based on its identification information to obtain the service type of the terminal device; evaluating the service data packet transmission frequency and data transmission stability of the terminal device based on its identification information to obtain the service data packet transmission frequency of the terminal device; and determining its movement range or movement radius based on multiple movement positions of the terminal device within a predetermined period to obtain the movement pattern of the terminal device.

[0041] Specifically, the service type of a terminal device can be determined by evaluating attributes such as data transmission direction and service data packet size based on the terminal device's identification information (e.g., terminal ID). During the evaluation process, the service data packet size can be normalized to [-1, 1]. The larger the service data packet, the closer the absolute value is to 1; the smaller the service data packet, the closer the absolute value is to 0. A positive sign indicates downlink transmission, and a negative sign indicates uplink transmission.

[0042] In practical applications, the normalization method can be calculated using the following approach:

[0043] In the above formula, To normalize business data packets, For business data packets, This refers to the reference service data packet, and can take the maximum value. , These represent the small packet threshold and the normalization threshold, respectively. , These represent the bulk threshold and the normalized bulk threshold, respectively. and These are used to adjust the stretching coefficient; the larger the value, the greater the differentiation between long-tail small packages and large packages. and These are the connection values, ensuring K(u) The three segments of the function it contains are continuous.

[0044] The above calculation method can take into account the differences between IoT small packet services and eMBB large packet services.

[0045] Specifically, the frequency of service data packet transmission by the terminal device can be obtained by evaluating the frequency of service data packet transmission and the stability of transmission events based on the terminal device's identification information (such as terminal ID). During the evaluation process, the frequency of service data packet transmission can be normalized to [-1, 1]. The higher the frequency of service data packet transmission, the closer the absolute value is to 1; the lower the frequency of service data packet transmission, the closer the absolute value is to 0. Here, a positive sign indicates stable transmission within the period, and a negative sign indicates random transmission within the period.

[0046] In practical applications, the normalization method can be calculated using the following approach:

[0047] in, Indicates transmission frequency. This indicates the reference transmission frequency, which can be the highest frequency. Indicates the normalized transmission frequency; Indicates transmission stability. Indicates the difference in transmission intervals. This indicates the threshold for transmission interval difference.

[0048] Specifically, the movement patterns or habits of terminal devices can be estimated by considering multiple movement locations of the terminal device within a predetermined period (e.g., two weeks, one month), and then normalized. The movement location (i.e., the terminal device's location) can be estimated using the RSRP and SINR data of the access cell and several neighboring cells over a period of time. User movement habits can be evaluated based on the convex hull area or turning radius, for example, through the following aspects:

[0049] in, ConvexHull Represents the convex hull; Indicates the user's location. Indicates average user location; This indicates the reference moving area, and the maximum area can be taken.

[0050] In one possible implementation, based on the determined device type and service characteristics, corresponding service clusters are classified, including: normalizing the service type, service data packet transmission frequency, and mobility patterns to obtain a service feature vector; determining the probability that each service of the terminal device belongs to each service cluster based on the service feature vector, and classifying each service into a service cluster based on the probability to obtain the service cluster to which the terminal device's service belongs.

[0051] In the process of classifying various services of terminal devices into service clusters based on the determined device type and service characteristics, the first step is to unify the measurement of service characteristics to obtain the corresponding service feature vectors. Specifically, to avoid dimensional or scale shifts, the service type (denoted as K), service data packet transmission frequency (denoted as F), and mobility habits (denoted as M) are linearly mapped to [0,1] to perform a unified distance metric. The specific processing is as follows:

[0052] Thus, the business feature vector is obtained. .

[0053] Next, the cluster centers of various business clusters are obtained. Specifically, the cluster centers of various business clusters can be obtained based on historical data through clustering algorithms (such as K-means, DBSCAN, etc.) or through manual experience (such as taking the mean). The cluster centers of the business clusters are shown in Table 1 below: Table 1. Example of a cluster center for a business cluster.

[0054] The next step is to calculate the distance between the service feature vector and any service cluster using weighted Euclidean distance. cluster center In one example, the distance can be calculated as follows:

[0055] in, Let represent the weighting coefficients, and be constrained. The weighting coefficients can be output using classification algorithms (such as SVM) or optimization algorithms (such as genetic algorithms).

[0056] In the process of classifying business clusters, softmax can be used to evaluate the probability of each business pair belonging to each business cluster. In one example, the probability of any business pair belonging to a particular business cluster can be calculated as follows: Belonging to any business cluster The probability of:

[0057] in, This is the attenuation factor, controlling the sensitivity of distance to the home service cluster. A larger value means the probability of being associated with a more distant service cluster decreases more rapidly. Therefore, it is possible to obtain the attenuation factor for any service cluster. For the classification probability vector of each business cluster .

[0058] In one possible implementation, network resources are dynamically scheduled for the corresponding terminal devices based on device type, service cluster, and the current network load of the partial bandwidth BWP. This includes: determining the service weight of the target service based on the queuing status of the target service on the terminal devices of the service cluster and device type; determining the service priority of the target service based on the service weight; and dynamically scheduling network resources for the corresponding terminal devices based on the service priority and the current network load of the BWP. Determining the service priority of the target service based on the service weight may include: determining the service value density of the target service based on the service weight; and determining the scheduling priority of the target service based on the service value density.

[0059] In one possible implementation, network resources are dynamically scheduled for terminal devices based on service priority and the current network load of the BWP. This includes: when the current network load of the BWP is determined to be less than or equal to a preset resource leniency threshold, network resources are dynamically scheduled for the corresponding terminal device according to the service priority of the target service using an efficiency-first network resource scheduling mode; when the current network load of the BWP is determined to be greater than or equal to a preset resource stress threshold, network resources are dynamically scheduled for the corresponding terminal device according to the service priority of the target service using a group-based round-robin network resource scheduling mode; when the current network load of the BWP is determined to be greater than a preset resource leniency threshold and less than a preset resource stress threshold, network resources are dynamically scheduled for the corresponding terminal device according to the service priority of the target service using a hybrid network resource scheduling mode, wherein the hybrid network resource scheduling mode is a combination of the efficiency-first network resource scheduling mode and the group-based round-robin network resource scheduling mode.

[0060] In one example, dynamic scheduling of network resources can be achieved according to the following process: (1) Determine the current BWP load status to select / switch the network resource scheduling mode; For UL and DL directions, they need to be judged separately. This can be achieved by using BW utilization rate L and preset resource leniency threshold L. relax Preset resource shortage threshold L tig The judgment is performed on t, and the following three states are identified: L L relax This indicates that network resources are plentiful and BWP load is low; L L tig The 't' indicates that network resources are strained and BWP is under high load. L relax <L<L tig The value 't' indicates that network resources are neither too tight nor too loose, and the BWP load is moderate.

[0061] (2) Calculate business weights When calculating service weights, the performance requirements of the service cluster and the queuing status of the target service can be comprehensively considered to ultimately calculate the service weight. Essentially, the service weight of the target service is determined based on the queuing status of the target service according to the service cluster and device type. The following calculation formula can be used:

[0062] in, It is the global weight of the business cluster, taking into account business strategies or SLA guarantee requirements; It is an adjustment factor for the target business based on queuing time.

[0063] (3) Calculate and rank the business value density. The service value density is calculated by comprehensively considering factors such as the service weights of RedCap / eRedCap and eMBB, cross-BWP persistence costs, and BWP handover stickiness, thereby determining the scheduling priority. Essentially, the service value density of the target service is determined based on its service weight; and the scheduling priority of the target service is determined based on its service value density. In one example, the service value density is calculated as follows:

[0064] in, Indicates business x In BWP b Business value density on This indicates the overall bias towards RedCap / eRedCap services and eMBB services, using terminal type. g Indicates, that is ; Indicates business x Required RB resources; Indicates business x Cross-BWP scheduling to b The resulting throughput loss coefficient; Indicates business xThe height penalty value for switching from the current BWP to another BWP.

[0065] on the one hand, The larger the value, the earlier the corresponding service will be scheduled; on the other hand, the scheduling granularity... q To prevent high-value, high-density services from consuming all available resources and hindering the scheduling of other urgent services, the following measures are taken:

[0066] in, Indicates business x In BWP b The number of RBs in the last scheduling.

[0067] (4) When the BWP load is low, it enters the network resource scheduling mode that prioritizes efficiency. Low BWP load indicates that the current network load of the BWP is less than or equal to the preset resource leniency threshold. At this time, network resources can be dynamically allocated to the terminal device according to the service priority of the target service through the efficiency-first network resource scheduling mode.

[0068] Specifically, a backup RB and corresponding CCE resources are pre-allocated to the resident RedCap / eRedCap services. Then, RedCap / eRedCap and eMBB services compete for network resources based on service value density (i.e., service priority) (i.e., dynamic scheduling of network resources for terminal devices).

[0069] It should be noted that if a certain service consistently has a high priority, multiple rounds of network resource allocation can be performed, but this is subject to the upper limit of the resources that can be acquired in a single cycle. Restrictions.

[0070] (5) BWP load is high, enters the network resource scheduling mode of group round-robin. High BWP load indicates that the current network load of the BWP is greater than or equal to the preset resource shortage threshold. At this time, network resources can be dynamically allocated to terminal devices according to the service priority of the target service through a grouped round-robin network resource scheduling mode.

[0071] Specifically, network resources are pre-allocated according to the device type of the terminal equipment. Considering the minimum network resource guarantee conditions for resident services, network resources can be pre-allocated according to the following methods:

[0072] in, For a moment t， BWP b Give device type g The network resources pre-allocated to the terminal devices require For a moment t Equipment type g The total network resources required by the terminal devices. For device type g The sum of the business weights of the terminal devices, For a moment t BWP b Scheduled resources.

[0073] It should be noted that intra-group network resource scheduling follows the principles of service value density (equivalent to service priority) and... limit.

[0074] (6) The BWP load is moderate, and it enters the hybrid network resource scheduling mode. A moderate BWP load indicates that the current network load of the BWP is greater than the preset resource slack threshold and less than the preset resource shortage threshold. At this time, network resources can be dynamically allocated to terminal devices according to the service priority of the target service through a hybrid network resource scheduling mode. The hybrid network resource scheduling mode is a combination of the efficiency-first network resource scheduling mode and the group round-robin network resource scheduling mode.

[0075] Specifically, based on the BWP load ratio, network resources can be allocated between efficiency-priority scheduling and packet-based round-robin scheduling. In other words, network resources are divided into two parts: one part for efficiency-priority scheduling and the other for packet-based round-robin scheduling. See below:

[0076] in, For network resources where efficiency is the priority, Network resources are used for group rotation. The corresponding network resources can be scheduled for the services of RedCap / eRedCap terminal devices and eMBB terminal devices according to the calculation methods in (4) and (5) above.

[0077] As can be seen, the method in this application comprehensively considers the multidimensional differences in services, highlighting service types, frequency of service occurrences, and spatial mobility, which helps improve adaptability to atypical services and achieve more granular, multidimensional, and intelligent service perception. Moreover, the adaptive scheduling, which prioritizes high-efficiency throughput under low load and ensures latency and fairness under high load, not only improves the fineness and dynamic response capability of scheduling, but also optimizes resource carrying efficiency and ensures multi-service experience in scenarios where RedCap / eRedCap and eMBB coexist.

[0078] This application provides a network resource scheduling device, such as... Figure 2As shown, the device 200 may include: a first processing module 201, a second processing module 202, and a third processing module 203, wherein, The first processing module 201 is used to determine the device type of the terminal device accessing the network and the service characteristics of the service. The device type includes lightweight terminals and enhanced terminals, and the service characteristics include service type, service data packet transmission frequency and movement pattern. The second processing module 202 is used to classify the services of the terminal device into corresponding service clusters according to the determined device type and service characteristics, and to determine the service cluster to which the services of the terminal device belong. The third processing module 203 is used to dynamically schedule network resources for the corresponding terminal devices based on the device type, service cluster, and the current network load of the partial bandwidth BWP.

[0079] In one possible implementation, when determining the service characteristics of the terminal device accessing the network, the first processing module is used to: The service type of the terminal device is obtained by evaluating its data transmission direction and service data packet size based on the terminal device's identification information. The frequency of service data packet transmission and the stability of data transmission of the terminal device are evaluated based on the identification information of the terminal device to obtain the frequency of service data packet transmission of the terminal device. Based on the multiple moving positions of the terminal device within a predetermined period, its moving range or moving radius is determined, and the moving pattern of the terminal device is obtained.

[0080] In one possible implementation, when the second processing module categorizes the services of the terminal device into corresponding service clusters based on the determined device type and service characteristics, and determines the service cluster to which the terminal device's services belong, it is used to: The service type, service data packet transmission frequency, and movement pattern are normalized to obtain the service feature vector; Based on the service feature vector, the probability of each service of the terminal device belonging to each service cluster is determined, and the services are classified into service clusters according to the probability to obtain the service cluster to which the terminal device's services belong.

[0081] In one possible implementation, when the third processing module dynamically schedules network resources for the corresponding terminal device based on the device type, service cluster, and current BWP network load, it is used to: The service weight of the target service is determined based on the queuing status of the target service on the terminal device according to the service cluster and device type. Determine the business priority of the target business based on business weight; Based on service priority and the current network load of BWP, network resources are dynamically allocated to the corresponding terminal devices.

[0082] In one possible implementation, when determining the business priority of the target business based on business weights, the third processing module is used for: Determine the business value density of the target business based on its business weight; The scheduling priority of target services is determined based on the service value density.

[0083] In one possible implementation, when the third processing module dynamically schedules network resources for the corresponding terminal device based on service priority and the current network load of the BWP, it is used to: When the current network load of BWP is determined to be less than or equal to the preset resource leniency threshold, network resources are dynamically allocated to the corresponding terminal devices according to the service priority of the target service through the efficiency-first network resource scheduling mode. When the current network load of BWP is determined to be greater than or equal to the preset resource shortage threshold, network resources are dynamically allocated to the corresponding terminal devices according to the service priority of the target service through a grouped round-robin network resource scheduling mode. When it is determined that the current network load of BWP is greater than the preset resource easing threshold and less than the preset resource strain threshold, network resources are dynamically allocated to the corresponding terminal devices according to the service priority of the target service through a hybrid network resource scheduling mode. The hybrid network resource scheduling mode is a combination of the efficiency-first network resource scheduling mode and the group round-robin network resource scheduling mode.

[0084] The network resource scheduling device of this application embodiment can execute the network resource scheduling method shown in the above embodiments of this application. The implementation principle is similar. The actions performed by each module in the device of each embodiment of this application correspond to the steps in the method of each embodiment of this application. For detailed functional descriptions of each module of the device, please refer to the descriptions in the corresponding methods shown above, which will not be repeated here.

[0085] This application provides an electronic device, including a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the steps of a network resource scheduling method.

[0086] In one alternative embodiment, an electronic device is provided, such as Figure 3 As shown, Figure 3The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of this application.

[0087] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0088] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 3 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0089] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium capable of carrying or storing computer programs and capable of being read by a computer, without limitation herein.

[0090] The memory 4003 stores computer programs that execute embodiments of this application, and its execution is controlled by the processor 4001. The processor 4001 executes the computer programs stored in the memory 4003 to implement the steps shown in the foregoing method embodiments.

[0091] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the steps and corresponding content of the aforementioned method embodiments.

[0092] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the steps and corresponding content of the aforementioned method embodiments.

[0093] It should be understood that although arrows indicate various operation steps in the flowcharts of this application's embodiments, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of this application's embodiments, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all steps in each flowchart, based on the actual implementation scenario, may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and this application's embodiments do not limit this.

[0094] The above description is only an optional implementation method for some implementation scenarios of this application. It should be noted that for those skilled in the art, other similar implementation methods based on the technical concept of this application without departing from the technical concept of this application also fall within the protection scope of the embodiments of this application.

Claims

1. A network resource scheduling method, characterized in that, include: The device type of the terminal equipment accessing the network and the service characteristics of the services are determined. The device type includes lightweight terminals and enhanced terminals, and the service characteristics include service type, service data packet transmission frequency, and mobility patterns. Based on the determined device type and service characteristics, the services of the terminal device are categorized into service clusters to determine the service cluster to which the terminal device's services belong. Based on the device type, the service cluster, and the current network load of the partial bandwidth BWP, network resources are dynamically scheduled for the corresponding terminal device.

2. The method according to claim 1, characterized in that, The service characteristics of the terminal devices accessing the network include: The service type of the terminal device is obtained by evaluating its data transmission direction and service data packet size based on the identification information of the terminal device. The frequency of service data packet transmission and the stability of data transmission of the terminal device are evaluated based on the identification information of the terminal device to obtain the frequency of service data packet transmission of the terminal device. Based on the multiple moving positions of the terminal device within a predetermined period, its moving range or moving radius is determined, thereby obtaining the moving pattern of the terminal device.

3. The method according to claim 1 or 2, characterized in that, The step of classifying the services of the terminal device into service clusters based on the determined device type and service characteristics, and determining the service cluster to which the terminal device's services belong, includes: The service type, the frequency of service data packet transmission, and the movement pattern are normalized to obtain a service feature vector; Based on the service feature vector, the probability that each service of the terminal device of the device type belongs to each service cluster is determined, and the services are classified into service clusters according to the probability to obtain the service cluster to which the terminal device's services belong.

4. The method according to claim 1, characterized in that, The step of dynamically scheduling network resources for the corresponding terminal device based on the device type, the service cluster, and the current network load of the BWP includes: The service weight of the target service is determined based on the queuing status of the target service of the terminal device of the service cluster and the device type. The business priority of the target business is determined based on the business weight; Based on the service priority and the current network load of the BWP, network resources are dynamically scheduled for the corresponding terminal devices.

5. The method according to claim 4, characterized in that, Determining the business priority of the target business based on the business weight includes: The business value density of the target business is determined based on the business weight. The scheduling priority of the target service is determined based on the service value density.

6. The method according to claim 4, characterized in that, The step of dynamically scheduling network resources for the corresponding terminal device based on the service priority and the current network load of the BWP includes: When the network load of the current BWP is determined to be less than or equal to a preset resource leniency threshold, network resources are dynamically allocated to the corresponding terminal device according to the service priority of the target service through an efficiency-first network resource scheduling mode. When the network load of the current BWP is determined to be greater than or equal to a preset resource shortage threshold, network resources are dynamically allocated to the corresponding terminal device according to the service priority of the target service through a grouped round-robin network resource scheduling mode. When it is determined that the current network load of the BWP is greater than the preset resource easing threshold and less than the preset resource strain threshold, network resources are dynamically allocated to the corresponding terminal device according to the service priority of the target service through a hybrid network resource scheduling mode. The hybrid network resource scheduling mode is a combination of the efficiency-first network resource scheduling mode and the group round-robin network resource scheduling mode.

7. A network resource scheduling device, characterized in that, include: The first processing module is used to determine the device type of the terminal device accessing the network and the service characteristics of the service. The device type includes lightweight terminals and enhanced terminals, and the service characteristics include service type, service data packet transmission frequency, and movement pattern. The second processing module is used to classify the services of the terminal device into corresponding service clusters according to the determined device type and service characteristics, and to determine the service cluster to which the services of the terminal device belong. The third processing module is used to dynamically schedule network resources for the corresponding terminal device based on the device type, the service cluster, and the current network load of the partial bandwidth BWP.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-6.

Images